Develop Bugs

TMobile US 3.6.390 Upgrade

I just wanted to split this discussion from the leaked ROM thread. From what I have gathered and understand, this newest update is the US equivalent of the Europe 2.51 update. I know many of you have already upgraded your devices to this, so users like me who are late/slow to the game, aren't there yet. In my case I still had the stock 3.6.160 up until last night. I know many have had the concern about 2.51 and not being able to go back. Has US TMobile done us a favor by releasing this OTA update? It would seem to me that this is now a sanctioned update, so anything from here on out would be officially supported and updated. It also seems that if the US and Europe version are the same, any thing that works for 2.51, would work for the US version. Like the 3.4.2 Nandroid backups. It should just be a matter of a simple restore and everything should work, correct? Sorry if I seem a little off. Prior to this device all of mine have been HTC devices which didn't have the locked bootloader. So this concept of of firmware/roms is a little off to me. I haven't had a chance to test any of this yet, I just want to know if the theory is correct. If I'm wrong please point me in the right direction. I'd like to be able to contribute to this forum constructively, especially as I am in charge of deploying DEFYs on our corporate network. The nice part of this is my Director is all for rooting our phones. He looks at in the manner that we need to do what needs to be done. If a phone gets bricked in the process, well we will just buy another. Warranty really isn't a concern.I'd like to get playing on it this weekend, especially with Froyo.

runeblade said:
It would seem to me that this is now a sanctioned update, so anything from here on out would be officially supported and updated.
Click to expand...
Click to collapse
Nope.
The only update for the US DEFY is an incremental one (still 2.1) and it has only been released to 500 or so users according to the offical Tmo forums.
They are testing that one now.
The official froyo for DEFY is probably still a couple/few months away from public release, but let us hope they get it out faster.
More info in this thread:
http://forum.xda-developers.com/showthread.php?t=931212

The Incremental has been released to the wild. Both of my Defy's received it OTA. I also know this is not an OS upgrade. Still stuck at 2.1. But my understanding was that the US update changes the boot loader to the same one as the Europe 2.51 update. If this is indeed true it would mean that we should be able to boot any of the 2.2 Roms out there without using the European update. Thats what I'm trying to confirm/Deny.

I registered for the "testing update", and received it this morning. Overall the phone is so much smoother. I'm now using Blur instead of ADW or LP. As a matter of fact all scrolling is smoother. The homescreens, app drawer, lock screen, widgets. Everything. Before the update if I was on Wi-Fi and sent a MMS I would get a delay, and have both icons in the notification bar for Wi-Fi and 3G, but now they send instantly, and I only have the Wi-Fi icon. Battery seems to be lasting longer today too which is one of the included functions. I'm impressed overall with what they did.

I was on of the very first few to get the Official 3.6.360 and while yes some things have improved. I decided to do a wipe after I had installed it. And I notice something interesting. No more root, Z4Root (using 1.3.0 which is what I used the first time I rooted this phone) no longer works, unexpected failure. So yea the have changed something... I run down the ADB route and see what that turns up.
I will have go the ADB route to get back to rootville.

darknetone said:
I was on of the very first few to get the Official 3.6.360 and while yes some things have improved. I decided to do a wipe after I had installed it. And I notice something interesting. No more root, Z4Root (using 1.3.0 which is what I used the first time I rooted this phone) no longer works, unexpected failure. So yea the have changed something... I run down the ADB route and see what that turns up.
I will have go the ADB route to get back to rootville.
Click to expand...
Click to collapse
I noticed the same thing. No more root access after the update. I tried to re-root with z4root, super 1 click to no avail. Not familiar with the ADB process. Kinda nervous to be honest. First Android phone and all. Had it 2 weeks. Hopefully a new 1 click method comes from one smarter than I soon.

That's interesting. I noticed right off the bat that Z4Root no longer worked, so I ran Super1click, and that worked fine for me. The only thing I haven't done is wipe the phone, but at this point it doesn't sound like I'm going too.

runeblade said:
That's interesting. I noticed right off the bat that Z4Root no longer worked, so I ran Super1click, and that worked fine for me. The only thing I haven't done is wipe the phone, but at this point it doesn't sound like I'm going too.
Click to expand...
Click to collapse
Did you need to do anything special with Super1click, or was it as simple as z4root? Can you just run it, and wait for it to finish? I mean I read some stuff that you may need to do the "turn debug off, turn it on, turn it off" thing with it because some phones give a "waiting for device". If you did certain steps other than just clicking root can you share? Thanks.

Nope. Just downloaded it, ran as admin and let it do its magic. Short and simple.

runeblade said:
Nope. Just downloaded it, ran as admin and let it do its magic. Short and simple.
Click to expand...
Click to collapse
How long did it take? I tried it, but it keeps hanging on "waiting for device..."

Mine as well. Just keeps saying waiting. It got further once but stuck in a loop and came back to waiting. I unmount the sd, put it in debug, not sure what usb mode to use or where this admin option is found though. Quite frustrated since the bloatware I froze with Titanium Backup is back and all my root permissions are one. Any help for a newAndroid guy would be awesome.

Make sure when you have it connected to your machine that you are in Portal mode, as well as making sure that your machine is actually picking up the MDB interface. I know with mine it took a couple of plug ins to get it to actually install correctly.

bobbyphoenix said:
How long did it take? I tried it, but it keeps hanging on "waiting for device..."
Click to expand...
Click to collapse
I think your problem might be that you're running it in USB "None" mode (as you would if running ADB). This is a common mistake. With Super1Click, you have to run it in "Portal" mode.
Plug your phone into the computer. You'll get "USB Connection" in your notification bar at the top. Then pull the notification bar down and click "USB connection". Click "Motorola Phone Portal". Then make sure "USB Debugging" is on (in Menu key > Settings > Applications > Development). Now run Super1Click as administrator. Click "Root".
It still takes a while in between steps, especially at the various "Waiting for device" stages. But if you did all the initial steps above, it should work properly. Just BE PATIENT.

cargohook said:
I think your problem might be that you're running it in USB "None" mode (as you would if running ADB). This is a common mistake. With Super1Click, you have to run it in "Portal" mode.
Plug your phone into the computer. You'll get "USB Connection" in your notification bar at the top. Then pull the notification bar down and click "USB connection". Click "Motorola Phone Portal". Then make sure "USB Debugging" is on (in Menu key > Settings > Applications > Development). Now run Super1Click as administrator. Click "Root".
It still takes a while in between steps, especially at the various "Waiting for device" stages. But if you did all the initial steps above, it should work properly. Just BE PATIENT.
Click to expand...
Click to collapse
Everyone keeps saying 'as administrator'. There is no option in S1C for that. Nor on my phone. How do I execute this as admin? Am I just being dumb?
Edit: Does this mean as computer admin? Like head honcho on the pc?

This is based on the assumption you are using windows 7 or vista. You right click on the program and in the drop down menu select Run as Administrator. It will then open up the program.

slipknotfn said:
Everyone keeps saying 'as administrator'. There is no option in S1C for that. Nor on my phone. How do I execute this as admin? Am I just being dumb?
Edit: Does this mean as computer admin? Like head honcho on the pc?
Click to expand...
Click to collapse
Exactly, "Head Honcho of the computer"! Do what runeblade said.

cargohook said:
I think your problem might be that you're running it in USB "None" mode (as you would if running ADB). This is a common mistake. With Super1Click, you have to run it in "Portal" mode.
Plug your phone into the computer. You'll get "USB Connection" in your notification bar at the top. Then pull the notification bar down and click "USB connection". Click "Motorola Phone Portal". Then make sure "USB Debugging" is on (in Menu key > Settings > Applications > Development). Now run Super1Click as administrator. Click "Root".
It still takes a while in between steps, especially at the various "Waiting for device" stages. But if you did all the initial steps above, it should work properly. Just BE PATIENT.
Click to expand...
Click to collapse
Yep. That was my problem. Didn't have it in portal mode. As soon as I did, it went fast. It went through a bunch of steps. I see it says "Running psneuter... ROOTED" It should be almost done. It's on "Reading OS Version properties..." now, and it's been there for like 10 minutes now.

cargohook said:
Exactly, "Head Honcho of the computer"! Do what runeblade said.
Click to expand...
Click to collapse
What if one were running, say, XP? Then head honcho would work? I have no computer here that has 7 or Vista. Just my old, trusty laptop. Thanks for all your help.
And which version of S1C? The one for 2.51 or the 1.63 version?

The 2.51 version.

runeblade said:
The 2.51 version.
Click to expand...
Click to collapse
where is that version? I'm using 1.6.3 and it's still stuck on "reading OS" thing.

[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

[Q] AlpharevX, not working... [SOLVED]

Ok I'm a HTC noob so please bear with me. I setup adb-sdk environment and windows environment variable. After that I obtained Alpharevx and ran it. Everything went fine and I entered the beta key. But then after
'Beta key accepted - thank you for participating!'
, nothing happens. It just stops. Any idea how to get this thing going?

Did you run AlphaRevx as an administrator ... given you're on Vista or Windows7?
Is the phone in USB debugging mode?
Is the Android software on your phone 2.2.1? If it's 2.3 then the AlphaRevX will not work :/

JWhetstone02 said:
Did you run AlphaRevx as an administrator ... given you're on Vista or Windows7?
Is the phone in USB debugging mode?
Is the Android software on your phone 2.2.1? If it's 2.3 then the AlphaRevX will not work :/
Click to expand...
Click to collapse
Thanks
Yes my phone is frogyo.
Yes it's in USB debugging mode.
Yes ran as an admin because I disabled the protection so basically all apps as admin on my windows 7.

I've read in the AlphaRevX thread where some people have had to do it multiple times before it Roots their phone. Maybe try that?

Thank you. I will try more :O I hope this won't brick my phone. I heard HTC devices can't recover from brick. With SGS you could just odin back from whatever mess you are in.

Is the phone set to charge only? Also is htc sync uninstalled?
Sent from my Incredible 2 using Tapatalk

Yea it seems a lot of Fascinated people are coming to an Incredible phone Many many mentionings on here about yall fazzy people making the switch, per choice or replacement

4GivenByChrist said:
Is the phone set to charge only? Also is htc sync uninstalled?
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
Yes, set to charge only mode.
Yes, removed everything and used the drivers from alpharevx's site.
JWhetstone02 said:
Yea it seems a lot of Fascinated people are coming to an Incredible phone Many many mentionings on here about yall fazzy people making the switch, per choice or replacement
Click to expand...
Click to collapse
Yea, I just got mine as a replacement after a year of use. So far I'm happy because the screen is up to par with SAmoled. People always hype up SAmoled but imho, SLCD on Dinc2 is not far behind.

Hey, so I am new to this board. I myself have a Dinc2 arriving soon. My brother just got his. We are both former fascinate owners. After researching and following some how to's, my brother was rooting his phone and he got stuck while attempting to get recovery after S-off. He cannot post, but here is what stated happened:
Hey I'm having a problem with my incredible 2.
Before activating the phone (avoiding the 2.3 update) I tried rooting my phone.
1) I downloaded alpharedex and generated the code
2) downloaded the recovery mode application onto the phone
3) and placed the SU zip folder onto my phone
I was stopped at step 3 because the volume down power button procedure was not working. Instead the phone powered on normally. I attempted it many more times and it would not work.
After spending some time on it, I said screw it, I just want to use the phone. So i activated it and OK'd the 2.3 update. It shut down my phone and began to download the file but it was stopped with a exclamation point in a red triangle. I tried doing a hard reset (volume up and power button) but that did not work. So i was forced to take out the battery. When I powered up the phone again, it continued the download: the phone shut down, it began to download and froze up like last time.
Click to expand...
Click to collapse
Okay, so yes I know he shouldn't have done this. After consulting with me, I was able to get him into recovery by attempting the volume down + power procedure about a dozen more times.
Should he install the super user package and reboot? Or should he do something now to fix the OTA auto reboot problem while he still has recovery?
Edit: Because he is in recovery, could he just factory reset and flash a new rom? Apparently, when he boots the phone normally it gets to the home screen and then instantaneously reboots and attempts to install the OTA. That is where it locks up.

If he installs a rom it should block the update. Any custom rom will have superuser built in, and I know at least CM7 has OTA blocking built in as well.
Oh, and it sounds like his trouble booting into hboot with power and volume down is because fastboot is enabled. It can be turned off in settings»power.

k_nivesout said:
If he installs a rom it should block the update. Any custom rom will have superuser built in, and I know at least CM7 has OTA blocking built in as well.
Oh, and it sounds like his trouble booting into hboot with power and volume down is because fastboot is enabled. It can be turned off in settings»power.
Click to expand...
Click to collapse
But the problem is that now he can't get into settings.... damn.maybe a factory reset is best if that's possible.
Sent from my Incredible 2 using Tapatalk

deaffob said:
Yes, set to charge only mode.
Yes, removed everything and used the drivers from alpharevx's site.
Yea, I just got mine as a replacement after a year of use. So far I'm happy because the screen is up to par with SAmoled. People always hype up SAmoled but imho, SLCD on Dinc2 is not far behind.
Click to expand...
Click to collapse
You have it working yet? If not I would uninstall the drivers you got and then download and install HTC sync. Then uninstall just htc sync leaving your drivers. Then try again. That wokred for me when I was unlocking a friends phone.
Sent from my Incredible 2 using Tapatalk

deaffob, you seem to be pretty computer literate, if it keeps giving you issues, boot ubuntu from a flash drive and do it that way. I messed with windows for a couple hours, and it took me all of 20 minutes to install ubuntu to my flash drive, boot into it and root.

bik2101 said:
But the problem is that now he can't get into settings.... damn.maybe a factory reset is best if that's possible.
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
That is what I was hoping for, but I don't think there is a factory reset option in Recovery that doesn't wipe the current rom he is on.
I was pretty sure flashing a rom with superuser in it would solve it, and it sounds like that might be the answer.
Only problem now is somehow getting the rom on to the SD card. I might have to have him swap SD cards in my phone, add the rom to the SD card, and then swap back.

I fixed it by going to alpharev IRC and got a great help from attn1! He was very helpful late at night.
To those of who'd like to know, this was my situation:
-Windows 7 64bit with admin control turned off=everything has admin rights.
-Fastboot off(tried on too)
-installed HTC Sync's driver.
-tried HTC driver that's posted on AlpharevX's website.
-HTC Sync was uninstalled.
-It was froyo
-Correct HBOOT(obvious because the whole point of getting the beta key was to prevent someone using the hack with the wrong version of HBOOT)
-Tried 3 different USB ports.
-ADB SDK was installed
-JDK was installed
-environment variable path for ADB SDK was set.
-tried reinstalling the HTC Driver twice, each time uninstalling with Revo Uninstaller to clean up registry.
So even after all these, the hack still did not work. So attn1 suggested that I should try it different computer or download the flash version of Ubuntu and try it in there. I tried it on my old lap with Windows 7 64 installed. I haven't used the laptop that much so the Windows was pretty clean and new.
It worked on that laptop. The lesson is, no matter how much you take care of your windows system, I practically baby my computer and do everything to keep the optimum performance, it will get screwed up after some time. I would've never thought that it'd be my desktop Windows that was the problem.
So if you are having a problem, please try Ubuntu as that's probably the best bet.

PeterGunz said:
That is what I was hoping for, but I don't think there is a factory reset option in Recovery that doesn't wipe the current rom he is on.
I was pretty sure flashing a rom with superuser in it would solve it, and it sounds like that might be the answer.
Only problem now is somehow getting the rom on to the SD card. I might have to have him swap SD cards in my phone, add the rom to the SD card, and then swap back.
Click to expand...
Click to collapse
but there's still the problem of not being able to turn fast boot off, which i think is needed to be able to get into recovery..

get into recovery
To get into Recovery EVERY time, simply do a battery
pull beforehand. That does it.

JWhetstone02 said:
Yea it seems a lot of Fascinated people are coming to an Incredible phone Many many mentionings on here about yall fazzy people making the switch, per choice or replacement
Click to expand...
Click to collapse
+1
Yep! And I'm happy I made the switch, the SLCD screen is not bad and has more accurate color reproduction and plus who uses the SAMOLED at 100% brightness anyways..-nobody really lol.
Also HTC sense imho is waay more useable with good functionalities like the ever so good integration of Facebook compared to TW. I still can't get over that since I was conned into thinking that the Fascinate had in-app pictures but atlas it was a link to the website.. whereas HTC has that and more plus notifications!
Sorry I'm just thoroughly impressed especially since this is my first HTC Device. ^__^
Plus the rotating capacitive buttons is just super cool... :3 Now to make it work when using the camera app... >.> Anybody know if this mod exists yet?
Sent from my ADR6350 using XDA App-Dinc2 switched from a Fascinate.. :3

michaelbsheldon said:
To get into Recovery EVERY time, simply do a battery
pull beforehand. That does it.
Click to expand...
Click to collapse
You can download a program from the Market called quickboot It allows you to reboot into recovery without doing a battery pull. this is what I use right now in replace of the 4-in-1 reboot menu

I just got su on mine. I am an Android beginner so my experience may help. My system is a laptop running Win 7. I had installed synch and then following advice removed it with all drivers. I installed the htc USB drivers, and plugged in the phone in the proper mode. AlphaRevX will not work. So (this may be vital) reinstalled synch with drivers. Then removed synch. Got AlphaRevX to do its thing at once. So the other drivers must be there!

Trying to Root - Driver install issue

I've literally tried every method on the internet to root the GSM Galaxy Nexus and I keep getting stuck at the very beginning: I can't get past the driver step and making sure the computer recognizes the phone as an ADB device. I've tried Samsung driver install, pdaNET drivers and just about any other method and I still can't get my computer to show that the device is a ADB device and therefore cannot root the phone.
Its a Play Store Galaxy Nexus running 4.0.4
all help is incredibly appreciated. I've been working on this problem since Friday.
I'm on a 64bit Windows 7 on a Dell XPS 15 computer

Jubakuba said:
If your Command Prompt displays the message "waiting for device" your driver wasn't successfully installed.
Close the Command Prompt window and open Device manager while your phone is still plugged in. (Search for it using the search option).
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Samsung driver with the newest date and install it. Now retry the code above.
Click to expand...
Click to collapse
Try this.

I've tried updating via device manager. The problem is, it always says its up to date or when I manually select one it still doesn't work. Should I just not pick the newest driver? Pick an older version when selecting a new driver?
EDIT: also, another issue is that with Wug's when it searches for the adb device is searches in an odd folder that doesn't exist and I can't figure out how to change where it looks
Sent from my Galaxy Nexus using xda app-developers app

Or download the GNex Toolkit. Was having driver issues as well today (they were installed but for some strange reason Windows didn't recognize it anymore) and used the ones that come with this toolkit to reinstall through device manager. Of course as always with these things, use at your own risk, fiddling with drivers can be tricky .

What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.

Cilraaz said:
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Click to expand...
Click to collapse
When I use WugFresh and check for ADB it checks a nonexistent directory and returns an error. I found another method on google (I think the webpage was Foolproof method or something) and I check through command prompt and when I do it says List of Devices: then a blank line underneath
EDIT: just installed the GNex toolkit and drivers, plugged in, adb devices and it returned the blank line
EDIT 2.0: I just witnessed the most beautiful thing in the world. I plugged in again and it miraculously worked. I think I might tear up and cry a little

Yeah, for some reason the USB Driver in the Android SDK does NOT work. This was incredibly frustrating when I was trying to unlock my phone originally. I spent probably 30 minutes googling and trying different driver downloads.
I have attached the ones I used that DO work.

So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck

The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there

Gunthy` said:
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Click to expand...
Click to collapse
I don't think the pre-rooted ROMs get OTAs, or do they? I've been trying to root on stock so I can still get OTAs and I like how stable it is. I've messed with other ROMs on other phones and I almost always go to stock or CM but I'd rather stick to stock on this for now

Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...

i actually delete any driver and use the pdanet works just fine, i had the same problem that you. is just mather of patience.

Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok

Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Maybe not. SuperSU has a feature to keep root when installing an OTA.
The 4th Derivative said:
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Click to expand...
Click to collapse
Man.. as easy as this:
Go to bixie's jb rom thread, he has there linked a supersu+busybox cwm flashable zip, dl that and copy it to the device. Dl also a non-touch cwm image.
Unlock your bootloader, bla bla follow guides on how to set up/use fastboot, BOOT cwm (not flash it) with 'fastboot boot cwm.img', flash that supersu zip, reboot. Done, you rooted jb, install voodoo root keeper or something, back up root. Thats one way how to root a Nexus. You can even relock your bootloader after you finished customizing.
Sent from my i9250

Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier

The 4th Derivative said:
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
Click to expand...
Click to collapse
hey, i have the same problem as you do on updating the usb driver. mind telling me how you do it? thanks!

I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus

The 4th Derivative said:
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
its okay already. i have found the solution. thanks

The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
EDIT

Now I've DONE It! (Help...please?)

So with my wake up automatic update message this morning I decided to use Rumrunner and finally root. Couldn't have worked better honestly. Got in through Root Explorer, killed off the stuff I didn't want from the bloat and then got rid of the sounds and wallpapers I never use. Perfect, just as good as an experience as I had when I did the DInc2. Then I decided to make it even 'better' by getting rid of those annoying .odex files. I wiped them all, I don't know what I was thinking, I'm an idiot. I have a great phone that now can't get past the Verizon screen. How can I fix this as my wife is not amused with the cost associated with my stupidity. The laptop doesn't recognize the phone as even being there anymore. Is this a lost cause?

mySStery_machine said:
So with my wake up automatic update message this morning I decided to use Rumrunner and finally root. Couldn't have worked better honestly. Got in through Root Explorer, killed off the stuff I didn't want from the bloat and then got rid of the sounds and wallpapers I never use. Perfect, just as good as an experience as I had when I did the DInc2. Then I decided to make it even 'better' by getting rid of those annoying .odex files. I wiped them all, I don't know what I was thinking, I'm an idiot. I have a great phone that now can't get past the Verizon screen. How can I fix this as my wife is not amused with the cost associated with my stupidity. The laptop doesn't recognize the phone as even being there anymore. Is this a lost cause?
Click to expand...
Click to collapse
Can you boot in to recovery or bootloader (holding power+vol down)?
Sent from my HTC6500LVW using XDA Premium 4 mobile app

That I can

mySStery_machine said:
So with my wake up automatic update message this morning I decided to use Rumrunner and finally root. Couldn't have worked better honestly. Got in through Root Explorer, killed off the stuff I didn't want from the bloat and then got rid of the sounds and wallpapers I never use. Perfect, just as good as an experience as I had when I did the DInc2. Then I decided to make it even 'better' by getting rid of those annoying .odex files. I wiped them all, I don't know what I was thinking, I'm an idiot. I have a great phone that now can't get past the Verizon screen. How can I fix this as my wife is not amused with the cost associated with my stupidity. The laptop doesn't recognize the phone as even being there anymore. Is this a lost cause?
Click to expand...
Click to collapse
Put the stock odexed rom from my thread in development section in your adb/fastboot directory on your PC.
Enter Recovery, assuming you installed a custom recovery.
If not, do that first, using the links in Flyhalfs threads in our Verizon One Original Dev section.
In Recovery go to Advanced in TWRP I believe and do adb sideload > swipe to sideload.
Then you will need to enter in terminal: adb sideload filename.zip from within the fastboot directory with the stock file in that same directory.
Use the filename of the zip you are sideloading. Once its done pushing, it will flash the rom and then you can reboot.

I had tried straight off after the root to install CWM and it gave the option to do TWRP. I had a blank black screen and then kind of stalled so I forced it into the bootloader screen and just reset. In the present time if I attempt the recovery selection it just stalls again, a black yet obviously backlit screen. My new download of ADB does not look the same as it had when I did the last phone either. I don't know what I've fouled up here.

I'll send it out at this point to make the pain go away and have someone undo it.

mySStery_machine said:
I'll send it out at this point to make the pain go away and have someone undo it.
Click to expand...
Click to collapse
I can try and walk you through getting fastboot or adb set up so that you can try fixing it on your end.
It's also pretty well laid out in guides on Google.
If you really wanted to have it fixed for you, I'm about 12 hours or so south of where you are if you wanted to mail it here and back.
Up to you, hit me up via PM if you decide you wanna mail it.
Otherwise, myself and/or others will gladly help you undo it I'm sure man.
Then you wouldn't have to be without it for a few days.

You must be near my wife's family then in Santa Cruz. I can't be down without a phone long and I run a repair facility (NOT PHONES OBVIOUSLY) so my days smoke me mentally, today was case in point. I will try to collect myself get the DInc2 running and charged (which was the only reason I traded) and see about tackling it tomorrow night. If you would, please send me a PM with your number and I will call if I have need of adult supervision when attempting it once again. Funny thing is, is that I had already downloaded and dropped your .15 debloated into ADB for flash before even posting here.

mySStery_machine said:
You must be near my wife's family then in Santa Cruz. I can't be down without a phone long and I run a repair facility (NOT PHONES OBVIOUSLY) so my days smoke me mentally, today was case in point. I will try to collect myself get the DInc2 running and charged (which was the only reason I traded) and see about tackling it tomorrow night. If you would, please send me a PM with your number and I will call if I have need of adult supervision when attempting it once again. Funny thing is, is that I had already downloaded and dropped your .15 debloated into ADB for flash before even posting here.
Click to expand...
Click to collapse
Sounds good, I'll shoot you my gmail/Hangout info and we can get you squared away I'm sure.
Yeah, I'm up above there just a little, about 2 and a half hours or so from there.

Sounds good, I'm ready to tackle tonight whenever and for however long it takes.

Ok, have deleted and redownloaded the ADB files, yours as well as the TWRP. I have the recovery and your file chilling out in C:\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools . What now my new found savior?

Ok, knocked out the TWRP stuff myself and can get it to sideload screen but the command promp screen shows this when trying to push it over: C:\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb sideload 1.10.605.15_M7_WL_JB_50_VZW_Deodex_Full.zip
* cannot read '1.10.605.15_M7_WL_JB_50_VZW_Deodex_Full.zip' *

mySStery_machine said:
Ok, knocked out the TWRP stuff myself and can get it to sideload screen but the command promp screen shows this when trying to push it over: C:\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb sideload 1.10.605.15_M7_WL_JB_50_VZW_Deodex_Full.zip
* cannot read '1.10.605.15_M7_WL_JB_50_VZW_Deodex_Full.zip' *
Click to expand...
Click to collapse
Double check the md5 of the downloaded file.
Also shorten the path to the file, at least the folder names leading up to it, so that it's more direct.
Less chance of error or too deep of a path.
Something Like:
C:\Android\sdk\sdk\platform-tools>adb sideload 1.10.605.15_Deodex_Full.zip
Click to expand...
Click to collapse
You will have to rename a directory and a file or so to get it like that and this may not be the issue, but should certainly eliminate potential for issues.

Getting a 'device not found' error and the HTC driver when rebooting says did not load. I see on the MOUNT tab in TWRP different options, one of which is System which was not ticked should I click that and let it go try?

mySStery_machine said:
Getting a 'device not found' error and the HTC driver when rebooting says did not load. I see on the MOUNT tab in TWRP different options, one of which is System which was not ticked should I click that and let it go try?
Click to expand...
Click to collapse
Yeah try that, you may need to grab HTC Sync and install it if you haven't if your existing drivers aren't cooperating.

MD5 was corrupt, I finally got it to push.

Used pdaNet for drivers.

mySStery_machine said:
Used pdaNet for drivers.
Click to expand...
Click to collapse
Cool, glad that worked.
If you have any further issues or success, let me know.
Sounds like you should be good to go though.

Downloading another version to see if I can get the info across and get this One cooking again!

So should I do the other .zips below the post with your links for the firmware?