Develop Bugs

Rooting on x64 Windows 7

Hey,
All im wondering is if anyone has tried rooting on 64bit windows 7 and if it went ok??
Thanks

I had no problems. Rooted my (unlocked) Desire. Worked flawlessly, used this guide:
http://forum.xda-developers.com/showthread.php?t=696189

Eggcake said:
I had no problems. Rooted my (unlocked) Desire. Worked flawlessly, used this guide:
http://forum.xda-developers.com/showthread.php?t=696189
Click to expand...
Click to collapse
Thanks alot going to try this later tonight Which ROM you using btw?

I spent two hours last night using both googles drivers and the drivers from HTC sync to no avail can ADB / Fastboot but doesn't recognise phone when in recovery so can't complete the root.

Zero problems on windows x64 7 ultimate, works fine.

I just installed HTC Sync (maybe Reboot needed)? Phone had no problems with it afterwards.
Just make sure you don't plug your phone into a front panel or something similar - try to avoid this. Plug it in on the back if possible.
And I'm using Amer Bravox V4.1 - really nice ROM imho, everything you need is included. Waiting for a good 2.2 ROM, the ones available are still too buggy for me.

sub7seven said:
I spent two hours last night using both googles drivers and the drivers from HTC sync to no avail can ADB / Fastboot but doesn't recognise phone when in recovery so can't complete the root.
Click to expand...
Click to collapse
Do you have HTC Sync, and the SDK installed?
Also once you complete step 1 of the rooting process you should now not need to use a PC. What rooting method were you using?
Edit: To the OP, just to confirm what others have said. I've rooted with no problems on Win7 64bit.

64 bit USB driver won't recognize my phone

I bought a new laptop and it's 64 bit running Windows 7. I'm trying to install the 64 bit USB driver & get it to recognize my phone but it simply won't work.
The following two things keep running and running with the words "installing driver software" after them:
CDC Abstract Control Model (ACM)
S3C6410 Android ADB
I have no idea how to get this to work so any advice is greatly appreciated!
ps - USB debugging is checked in my application settings.

There are lots of people having problems with 64 bit windows nit recognizing the epic. My suggestion is to try.another USB cable. I use my wife's evo cable and it works fine for me. Good luck man just keep trying. Try different ports, cables and also check.to.make sure the USB slot is clear from any obstructions.
Sent From My Evo Killer!

musclehead84 said:
There are lots of people having problems with 64 bit windows nit recognizing the epic. My suggestion is to try.another USB cable. I use my wife's evo cable and it works fine for me. Good luck man just keep trying. Try different ports, cables and also check.to.make sure the USB slot is clear from any obstructions.
Sent From My Evo Killer!
Click to expand...
Click to collapse
I've done all those things.

Install the 32-bit drivers even if you're on a 64 bit computer

iSaint said:
Install the 32-bit drivers even if you're on a 64 bit computer
Click to expand...
Click to collapse
I was going to try that but didn't want to screw anything up...so that should work then?

droid newb said:
I was going to try that but didn't want to screw anything up...so that should work then?
Click to expand...
Click to collapse
Yes, I have 64bit computer and mine works with 32bit drivers.

Doing the same thing with 32 bit that it does with 64 bit.

droid newb said:
Doing the same thing with 32 bit that it does with 64 bit.
Click to expand...
Click to collapse
Here is a link to the drivers I installed on my Win 7 Ultimate 64bit machine. (i put them on my google documents site)
https://docs.google.com/leaf?id=0B8DFupwiCOXyMGViMDJmY2MtMGU4YS00MGY5LWFkOGItNjkyMDY3MjkyNjgx&hl=en
I have had no issues using odin or mass storage.
Hope this helps, good luck

jdelano said:
Here is a link to the drivers I installed on my Win 7 Ultimate 64bit machine. (i put them on my google documents site)
https://docs.google.com/leaf?id=0B8DFupwiCOXyMGViMDJmY2MtMGU4YS00MGY5LWFkOGItNjkyMDY3MjkyNjgx&hl=en
I have had no issues using odin or mass storage.
Hope this helps, good luck
Click to expand...
Click to collapse
That's the same one I've been trying all this time. I just don't understand why this won't work.

The ACS Module has never installed for me but my device works fine

watermoore said:
The ACS Module has never installed for me but my device works fine
Click to expand...
Click to collapse
So would you be able to Odin back to stock if you needed to?

droid newb said:
That's the same one I've been trying all this time. I just don't understand why this won't work.
Click to expand...
Click to collapse
When you ran the setup for the driver, did you run it as administrator?
Right click on setup.exe and select that option from the menu.
Sorry you're having such a bad time, that has got to be mega-frustrating.
I've read also, that some people run the 32 bit drivers on win 7 64bit and they report that they work for them just fine.

hey man i feel your pain. I have been having the same exact problems as you. I also have tried the 64 bit/32bit drivers, uninstalling/reinstalling them, everything i can think of or have been told to do to no avail. It use to work fine until i got the first froyo update eb13 and ever since its been like this. My laptop keeps telling me to replace my device.
I did get on a computer at work with win XP and i plugged my phone into it and the device installed but im not sure about the drivers. Im limited to what i can do at work. So maybe it has something to do with windows 7 cause my laptop is brand new as most people having this problem are to.

Did the drivers change after the EC05 update. Neither of my computers will recognize my phone now after I updated the modem. I even tried reinstalling the links you have in this post and updating drivers and still a no go.

I just had this problem recently. It wasn't the drivers - instead, it was the USB port I was using. If you're on a desktop, try a usb port on the back of the pc. If you're on a laptop, give all the usb ports a go.
Sent from my SPH-D700 using XDA Premium App

I am on a laptop and i have repeatedly try all usb ports and still a no go. It really seems like something changed after EB13 cause i never had a problem before.

dazednconfused1144 said:
Did the drivers change after the EC05 update. Neither of my computers will recognize my phone now after I updated the modem. I even tried reinstalling the links you have in this post and updating drivers and still a no go.
Click to expand...
Click to collapse
Nope; I have a win7 ultimate 32 laptop and a win 7 ultimate 64 desktop. Both see my phone just fine. Same drivers from when I first rooted after xmas to DK28 from 2.1.
I have heard of people having an issue with something bent on the phone's usb connector, it stops from getting full connection.

I'm having the same issue, but I can connect when I uncheck USB debugging. With it checked, it won't connect. I'm trying to root with 2.5.5...

jerbeck24 said:
I'm having the same issue, but I can connect when I uncheck USB debugging. With it checked, it won't connect. I'm trying to root with 2.5.5...
Click to expand...
Click to collapse
That worked!!!!!!!!!!!
Wooooooooooooooooooo!!!!!!!!!!!!!!!!!!!

droid newb said:
That worked!!!!!!!!!!!
Wooooooooooooooooooo!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
No problem...problem for me is, it needs to be checked in order to root...
I'm just going to odin back to EB13 and CWM3 and restore my latest back up of ACS 1.0.2

[Guide][TOOL] FASTBOOTROOT (deprecated)

(DEPRECATED)
I no longer support or care to support this is someone wants to take over and deal with this and the complaints go for it. It has not been tried on the 2.2.2 version of android in case you want to try it.
Tired of all those funky ways of rooting? Wanna just push a button and be rooted?
Guess what I've got something for you.
Introducing FastbootRoot (patent not pending) for the virgin mobile optimus v
FastbootRoot was designed with simplicity in mind. The easy to use ui makes rooting your lg optimus easy and quick without all those adb commands. It takes the guess work out ( is this right, what does he mean by that? ) of rooting your phone.
Features:
flash a custom recovery
this feature only flashes a custom recovery without rooting your phone giving you the ability to back up your current system without root. I put this in here in case of needing to return the phone for warranty matters
flash the entire shebang
This flashes a new boot image, a new system image*, and custom recovery.
Revert to stock
thanks to destundead we now have the stock system image and boot combined with my stock recovery we are good to go
New experimental install windows xp fastboot drivers
My goal is to fully automate this process and to make this as painless as possible for the new users. This new feature is untested and will either work or it won't. Give me some feedback if it does or doesn't.
--------------------------How to Use--------------------------
Download fastbootroot from here and place it on your desktop.
Download the usb drivers from here
On your phone turn on usb debugging by pushing menu, then settings, then applications, then development, and then usb debugging.
Install the drivers ( I find that rebooting after the drivers have been installed will install a whole new set of drivers. I recommend this method)
unzip fastbootroot and inside double click the fastbootroot file. Make your selection and your done.
Here's a video on using it and a little explanation
watch it here
WHAT THE FUTURE HOLDS:
no need to install usb drivers
Enjoy this and remember this works fully on windows 7 and I tested it myself. No matter what there's always room for user error though in which case I take no responsibility if things go wrong.
PROBLEMS AND COMPLAINTS
Some people are reporting problems like drivers not installing or other things. First off if you have a problem you need to state exactly what operating system you are using (windows 7, windows vista, or windows xp).
This only works with the virgin mobile optimus v. Make sure you have the virgin mobile optimus v (not a optimus t, m or a picture of the v pasted on top of a w490)
Tell me what you did exactly don't lie. I know from experience when someone says, 'I did this I definitely didn't do that', whether or not they are holding something back. The more info you can give the better if your holding something back that's gonna delay the process.
This is free. I ask for donations but they aren't required at all. So when your asking for more things remember this is free.
Like my work donate to me herehttps://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=FEP8NQ8J49MX8
*the new system image is stock with root, flash_image and busybox installed

It's fully automated?
Sent from my VM670 using XDA App

overthinkingme said:
It's fully automated?
Sent from my VM670 using XDA App
Click to expand...
Click to collapse
yep the only thing that you gotta do is download fastbootroot and the lg drivers. It will take care of everything else for you. I will say that I've tested this and my earlier variant of it quite a few times. I even made a video for the other one.

Downloading this now. will give it a try. Thanks!
--bornagainpenguin

This is for lg optimus v for virgin mobile, right?
Sent from my SGH-T959 using Tapatalk

i get a write error suspended reset port change on my phone when trying to run this? it says waiting on device on the fast boot system? any ideas what im doin wrong thanks

shaynes vibrant said:
i get a write error suspended reset port change on my phone when trying to run this? it says waiting on device on the fast boot system? any ideas what im doin wrong thanks
Click to expand...
Click to collapse
your in fastboot by now you should be good unless you did something crazy. What will happen is windows will automatically install the fastboot drivers and do it's thing and you'll be good

Asadullah said:
your in fastboot by now you should be good unless you did something crazy. What will happen is windows will automatically install the fastboot drivers and do it's thing and you'll be good
Click to expand...
Click to collapse
This does not seem to be happening. How can I abort the fastboot procedure so I can reboot and try again?
--bornagainpenguin

Hello? Please someone be there who can help me!
The detection sequence you describe did not work, Windows is not finding the drivers properly. Is it safe to reboot the machine while in fastboot? Can I unplug the USB without bricking my phone?
--bornagainpenguin

If nothing has flashed, I'm sure you're fine. It dependant on how far it got .
Would op mind posting the manual way to root through fast boot?
Sent from my VM670 using XDA App

bornagainpenguin said:
Hello? Please someone be there who can help me!
The detection sequence you describe did not work, Windows is not finding the drivers properly. Is it safe to reboot the machine while in fastboot? Can I unplug the USB without bricking my phone?
--bornagainpenguin
Click to expand...
Click to collapse
yes your okay to unplug your phone the process either works all the way or not at all I'm confused as to why it didn't install the drivers though. I guess I'll just have to add them to the batch

overthinkingme said:
If nothing has flashed, I'm sure you're fine. It dependant on how far it got .
Click to expand...
Click to collapse
How do I know?
Right now the screen says:
Code:
Fastboot mode started
gpio_12c: invalid khz: 0
b1: i2c write error
udc_start()
-- suspend --
--reset --
-- portchange --
-- reset --
-- portchange --
STALL GET_DESCRIPTOR 128 6 1006 0 18
-- reset --
-- portchange --
-- reset --
-- portchange --
I removed the battery and the phone restarted without issues. Not sure why things did not go the way they're supposed to--could it be because I had the drivers from the ROMTOOLS package installed before? NOTE: Prior to trying this procedure I uninstalled all of those and rebooted before installing the drivers linked here.
Another thought, OP says he is running Windows Seven; I am on Windows XP. Could this have anything to do with my trouble?
--bornagainpenguin
UPDATE: I tried installing the drivers included with the ROMTOOLS package and my phone was recognized again. No luck when trying to run fastboot. Not sure why this is happening or why I am unable to use the drivers OP linked to. They seem to install when clicked but the system doesn't seem to think the drivers apply to this phone for some reason...

Okay what happened was your fastboot drivers didn't install correctly I'm in the process of uploading a video to show you how to install the fastboot drivers.
I wrote this while before your last post yes there is a problem with windows xp. It doesn't download them like it would on windows 7. I can test all day long on windows 7 but not on xp. The method in the video should work for xp users

Asadullah said:
Okay what happened was your fastboot drivers didn't install correctly I'm in the process of uploading a video to show you how to install the fastboot drivers
Click to expand...
Click to collapse
I appreciate the effort, but unless the video is closed captioned it may not do me much good. I am hard of hearing (one of the reasons why I picked this phone was its high T4 rating which works well with my hearing aids and telecoil adapter --think headphones for hard of hearing people) so cannot always hear audio on videos very good.
--bornagainpenguin

bornagainpenguin said:
I appreciate the effort, but unless the video is closed captioned it may not do me much good. I am hard of hearing (one of the reasons why I picked this phone was its high T4 rating which works well with my hearing aids and telecoil adapter --think headphones for hard of hearing people) so cannot always hear audio on videos very good.
--bornagainpenguin
Click to expand...
Click to collapse
It's recorded in 780 hd using camstasia. Even if you can't hear it you'll be able to follow along the process is very simple

http://www.youtube.com/watch?v=aTE30yd-P_U
here's the video

I've integrated the fastboot drivers into the next release for windows xp I need a beta tester before I release this.

Does this just root our existing system, or does it install a whole new rooted image (requiring us to reinstall all of our programs and settings)?
I have XP, by the way. If it just roots, I would be willing to beta test (but if it doesn't work, if it doesn't work, I want to be able to get back to where I was as my phone works well).

This is F*****KIN GREAT!!!! Thanks!!

I'm having bootloop issues and I see a post here which suggests that one way to fix the situation is with fastboot. Do you know if fastboot can help me? If so, how?
--bornagainpenguin

ADB working in Android, but not in clockworkmod

I'm trying to install clockworkmod and root, by following the guide here:
http://forum.xda-developers.com/showthread.php?t=2022270
Everything is going well until I reboot into clockworkmod, at which point my computer fails to recognize the Nexus 7 for ADB, and I can't continue.
The weird thing is, after installing the ADB drivers from Asus' website on my Windows 7 PC, it connects perfectly in Windows. However, in clockworkmod, it just shows up in my Windows Device Manager with a yellow exclamation mark next to it.
Anyone knows what the problem might be?

Okay, solved my own problem.
Dunno what the problem was. I also tried installing the official Google drivers from the SDK to no avail. Fixed it by using the PDANet drivers here:
http://www.junefabrics.com/android/download.php
Now all is well.

manekineko said:
Okay, solved my own problem.
Dunno what the problem was. I also tried installing the official Google drivers from the SDK to no avail. Fixed it by using the PDANet drivers here:
http://www.junefabrics.com/android/download.php
Now all is well.
Click to expand...
Click to collapse
Thanks verrrrrrrrrrryyyy much guy. It solved my problem:
http://forum.xda-developers.com/showthread.php?p=46754283
You are awsome for share your knowledge.

Nexus 7 wont connect to computer via MTP

When I connect my Nexus 7 to my windows 7 computer it is not recognized in MTP, but is when I change it to PTP. When I connect my 1st gen Nexus 7 to the same computer it is recognized fine and I am able to transfer files. I have all the drivers installed and adb works when I am in PTP I just cant transfer any files. Has anyone else experienced this problem or is there maybe something wrong with my Nexus?

Check out this thread. I was experiencing similar issues although I didn't test out PTP .
Sent from my Galaxy Nexus using xda app-developers app

Disregard. I figured it out. It was a driver issue after all.

How did you fix it? I have the same problem. Is root needed to view transfer files via USB?

My N7 2013 won't connect with my Macbook Pro. I already have the Android File Transfer app, which works fine with my Nexus 4, but it won't recognize the Nexus 7 2013. It charges, but no connection. Anyone have any ideas?

lucastmw said:
My N7 2013 won't connect with my Macbook Pro. I already have the Android File Transfer app, which works fine with my Nexus 4, but it won't recognize the Nexus 7 2013. It charges, but no connection. Anyone have any ideas?
Click to expand...
Click to collapse
Might be a silly question but did you enable USB debugging in developer tools.
Sent from my Galaxy Nexus using xda premium

jmileti said:
Might be a silly question but did you enable USB debugging in developer tools.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes, I tried it with debugging on and off.

thaliagoo said:
How did you fix it? I have the same problem. Is root needed to view transfer files via USB?
Click to expand...
Click to collapse
Root is not needed to transfer files via USB. I just uninstalled the previous driver and updated to the latest and that worked for me.

No matter what, I always keep getting error code 10, device cannot be started when I install the new nexus 7 drivers Android ADB device (from the previous posts- Nexus 7 root). I'm not even trying to root, just trying to install drivers correctly.

thaliagoo said:
No matter what, I always keep getting error code 10, device cannot be started when I install the new nexus 7 drivers Android ADB device (from the previous posts- Nexus 7 root). I'm not even trying to root, just trying to install drivers correctly.
Click to expand...
Click to collapse
These are the drivers I used... http://developer.android.com/sdk/win-usb.html

fixed mine by just forcing it to reinstall the drivers.

fstbusa said:
fixed mine by just forcing it to reinstall the drivers.
Click to expand...
Click to collapse
How did you force it do that? I've actually never ran into this problem. Windows 8 is what I'm running.

dirtyfingers said:
These are the drivers I used... http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
It is definitely a driver issue. I had to uninstall my drivers and then manually install others, because I had a Nexus 7 2012. Those drivers were showing up as *up to date* according to windows, but the device was not working. Total clean install worked to correct it.

Xirix12 said:
How did you force it do that? I've actually never ran into this problem. Windows 8 is what I'm running.
Click to expand...
Click to collapse
In device manager, go to the properties of each android device. I had one near the top of the list and one lower under portable devices. Click update driver and navigate to your updated drivers folder.
It should update them. The device listed under portable devices had mtp as part of the title so I figured that one was the problem.
Sent from my Nexus 7 using xda app-developers app

To anybody who comes to this thread looking for help.
Go to device manager, and under devices remove the Google ADB Driver. This drove me nuts. All of my nexus devices wouldn't connect because they lacked an external SD.
Sent from my Nexus 7 using XDA Premium HD app

I've tried every suggestion in all of these threads so far & nothing worked. Even after I deleted the ADB drivers, windows 7 would automatically reinstall them. When I tried to update the drivers, win7 said they already had the best drivers (ADB).
Here's what worked for me:
I had to turn off USB debugging, delete the ADB drivers in Device Manager, then reboot the device while it's still plugged in. Windows recognized the device as an MTP device & installed the drivers before it even fully booted.

i installed the drivers from the link in this thread and still no luck, i am running the latest paranoid android rom, and tried it on 8 different computers with 23 different cables and no luck - would it help if i flashed a stock rom ? otherwise i dont know what to do - any help would be appreciated, thanks, chris
edit flashed a stock rom and now it is working again - came right up on my pc, i am selling it today to buy the 32gb and just wanted to get me twrp backups off it

golfinggino said:
i installed the drivers from the link in this thread and still no luck, i am running the latest paranoid android rom, and tried it on 8 different computers with 23 different cables and no luck - would it help if i flashed a stock rom ? otherwise i dont know what to do - any help would be appreciated, thanks, chris
edit flashed a stock rom and now it is working again - came right up on my pc, i am selling it today to buy the 32gb and just wanted to get me twrp backups off it
Click to expand...
Click to collapse
I have the same problem. When I was using stock ROM I could connect fine to my PC. When I installed CM10.2 I can not longer connect. i have no problem when I try it with my phone though.

huizingajm said:
I have the same problem. When I was using stock ROM I could connect fine to my PC. When I installed CM10.2 I can not longer connect. i have no problem when I try it with my phone though.
Click to expand...
Click to collapse
After helping someone with Paranoid ROM, I think the problem you are experiencing may be on the ROM/kernel side. Part of the problem is the custom ROM was sending out different USB IDs from stock. I was able to help them force the recognition of the MTP device from a driver standpoint on windows, but the MTP device wouldn't start up when windows tried to initialize it.

sfhub said:
After helping someone with Paranoid ROM, I think the problem you are experiencing may be on the ROM/kernel side. Part of the problem is the custom ROM was sending out different USB IDs from stock. I was able to help them force the recognition of the MTP device from a driver standpoint on windows, but the MTP device wouldn't start up when windows tried to initialize it.
Click to expand...
Click to collapse
I switched kernels to stock to jassy to tiny. None of them work so it has to be the ROM. I am just going to use WiFi transfer of files. Nothing major right now while everything is still new to 4.3.