[wadles]

Hey guys-need some help ASAP. Short of the long, I bought a craigslist desktop pc a while back with windows 7 ulitmate (I know...never again). It crashed after a while and a tech guy at work got me XP. All seemed well. So I finally decided to make the time to unlock/root. I can't even get my pc to recognize my gnex. I've been messing around and searched the net for about 2 hours. I've downloaded wmp 11, the mtp (mtppk12), and restarted. I've checked the "enable USB debugging" on the handset. I keep getting the "found unknown hardware wizard" and I still get an error. Where am I going wrong? I have a laptop but it's old (have a nice work laptop I can't use for this). This desktop is getting close to going out the window lol. Hoping it's something simple. Appreciate it...didn't think this warrants it's own thread but perhaps. My apologies if it does.

EDIT: it does now say portable device...but when I double click it opens and emty galaxy nexus folder. Downloaded the Sammy USB drivers. Now it recognized my device, as in no wizard prompt, but empty folder. What should I be selecting? Sorry this is embarrassing lol

Gotta download the wugs toolbox or whatever it's called and install it. Then run it to help your over recognize the phone and also help you root and stuff. Hope it helps. Aloha!

[ConTejas]

Thanks guys. Yes, I've downloaded the usb drivers from Sammy now. I've done all the reading on unlocking/rooting to feel comfortable, or at least I was, but I wanted to start by backing up my pictures to my PC. I will definitely be using Wug's Toolkit (and donating) but not even being able to see my pictures to copy them was disconcerting. After installing the Sammy drivers, and with my phone unlocked (doah!) I see internal storage with some folders in MTP mode. I can see the screenshots I took of my homescreens with the intention of using them after rooting, but I can't find my pictures in the folder (or in PTP mode). I guess I'll start with Jerry's non-rooted backup now that my device is recognized and hopefully learn wtf I'm doing along the way. Appreciate the quick responses...sorry to hack the thread.

EDIT: Think I just overreacted super noob style. Jerry's backup wonder machine doing its thing at the moment...then onto Wug's. Pumped.

[macmitten]

Being on stock os is hard to theme. a lot more work is involved. Best bet is to flash a popular rom like aokp liquid they have good theme support.


Sent from my Galaxy Nexus using Xparent Cyan Tapatalk 2

Sweet! I have the aokp now... could I flash the 4.0.4 radios over this rom? Sorry for the noob questions ahead of time.

[davey11]

Sweet! I have the aokp now... could I flash the 4.0.4 radios over this rom? Sorry for the noob questions ahead of time.

Flash away. Won't be a problem.

This post courtesy of Tapatalk2

[JEvoUser]

We have the same/similar package available in the RADIOS guide in the development/flashing subforum



What happened?



zero neck's radio guide in the flashing subforum!



Let me look around. Another user here said they flashed a version of SU.zip for 4.0.4. You would need that to re-root.

I've read that OTA RootKeeper has been hit or miss, BTW. If you want to keep root, I suggest waiting for a "rooted" version of this--which will undoubtedly come out soon, along with 85 different roms with the merged changes--or waiting until the proper files can be updated (superuser, etc.).

Well I forgot to use root keeper the first time so my superuser was not working and I was a little nervous I goofed my phone because computer was not detecting when searching adb devices but turns out I just forgot to turn on usb debugging :-). Otherwise it would have been a bad day thanks though.

[rreich49]

I waited forever to root my Gnex and finally did it today. Everything went fairly smoothly until I attempted to flash this update. I'm sitting here looking at a picture of a hat on my phone.

Am I screwed?

[zero neck]

what exactly did you do and what file/method did you use?

[dmmarck]

I waited forever to root my Gnex and finally did it today. Everything went fairly smoothly until I attempted to flash this update. I'm sitting here looking at a picture of a hat on my phone.

Am I screwed?

Need more details please.

Sent from my Galaxy Nexus using Xparent Cyan Tapatalk 2

[bbudnick5001]

He must be talking about the background of cwm. I bet he deactivated one of those buttons from trying to scroll up and down and then when he pushed the power button to select the options disappeared. It happened to me a few times at first. Now cwm touch is my friend

Sent from my Galaxy Nexus using Android Central Forums

[zedorda]

I waited forever to root my Gnex and finally did it today. Everything went fairly smoothly until I attempted to flash this update. I'm sitting here looking at a picture of a hat on my phone.

Am I screwed?

It seems you may of disabled the BACK button within CWM then hit the power button and the screen went blank other than the hat? If so hit the power button again will bring everything back then play with the vol+ and vol- till it says the BACK button is enabled at the bottom. Then the power button will work correctly.

I suggest you upgrade to the touch CWM it doesn't do this.

[psunami]

I've been trying to apply the 4.0.4 update to my non-rooted/non-unlocked Nexus and every time I try to enter Recovery Mode, the phone hangs on the Google logo. Anyone seen anything like this? I have all of the files in place for the upgrade, it just won't ever get me to a point where I can select the update.zip file that I have in place.

Thanks.

[bbudnick5001]

I think there is a totally different process to update without unlocking and rooting.

Sent from my Galaxy Nexus using Android Central Forums

[psunami]

yep. I know there is a different process, and that is what I followed. One of the last steps is to enter the recovery mode to select the update.zip file that you have to upload to the phone via adb. When I attempt to access the recovery mode, the phone locks at the Google logo. Apparently this is a pretty rare error. Looks like I will have to either do a wipe of my phone or wait until the OTA update goes live though.

[ConTejas]

yep. I know there is a different process, and that is what I followed. One of the last steps is to enter the recovery mode to select the update.zip file that you have to upload to the phone via adb. When I attempt to access the recovery mode, the phone locks at the Google logo. Apparently this is a pretty rare error. Looks like I will have to either do a wipe of my phone or wait until the OTA update goes live though.

I suggest you forgo the "official" update and unlock/root and flash a custom rom and the new radios (kernel/theme/etc if you want). If you can follow the steps required to do this on a stock gnex you will have absolutely no problem unlocking and rooting. Rooting isn't some bad word that only evil hackers can or care to do. I spent hours reading etc (which was overkill imo now). but it's very simple. I've done it both the long way and the toolkit (did toolkit first, which is completely noob proof and walks you step by step and relocked it to do it long way for fun). Let me tell you my device was amazing stock, but it's an absolute stable beast now. I couldn't care less about OTA updates now or ever again. I plan on keeping this device for a long time...and it'll always be top notch thanks to the amazing dev community. Just my 2 cents

[psunami]

Oh, I have no problem with rooting or unlocking devices, but my work denies our phones on our Enterprise mobile management software if they are unlocked or rooted.
That was my primary reason to try the work around.

Eventually I will just give in and root the device though. I can't wait on those radios and software updates forever...

Thanks.

[Dr0me]

Oh, I have no problem with rooting or unlocking devices, but my work denies our phones on our Enterprise mobile management software if they are unlocked or rooted.
That was my primary reason to try the work around.

Eventually I will just give in and root the device though. I can't wait on those radios and software updates forever...

Thanks.

I was in the same boat. I used the strifejester method without unlocking or rooting. Good enterprise still worked after the update.

[ConTejas]

^^^^As The Dude would say, "that's a bummer man." Totally understand the work issue.

[bplewis24]

Oh, I have no problem with rooting or unlocking devices, but my work denies our phones on our Enterprise mobile management software if they are unlocked or rooted.
That was my primary reason to try the work around.

Eventually I will just give in and root the device though. I can't wait on those radios and software updates forever...

Thanks.

How do they know if it's unlocked and/or rooted?

Brandon

[tk-093]

How do they know if it's unlocked and/or rooted?

Brandon

Most MDM products can detect a jailbroken or Rooted device and take some type of action. I'm the Good admin at my office and I catch devices from time to time.

[psunami]

Airwatch agent that runs on the device can detect it. Not sure how it does, but if the phone is rooted, it will not allow connection to the company email, etc.

[sparkey949]

Thanks a million! Sick of waiting for an update from VZW that'll probably never come.
Updated and working great, the improvements are profound!
Thanks again!!!

[dmmarck]

I have updated the original post with the new OTA package. It appears that this is the same exact OTA package from before, so we'll see if they take it down. As always, the mirrors will be active.

http://www.androidcentral.com/third-...ailable-google

[ruh-roh-raggy]

I have updated the original post with the new OTA package. It appears that this is the same exact OTA package from before, so we'll see if they take it down. As always, the mirrors will be active.

http://www.androidcentral.com/third-...ailable-google

I could be wrong, but unless I had some sort of download mishap when this was leaked a few weeks ago, this new file appears to be bigger. The previous download shows 29,881KB, but this latest file shows 40,750KB. As I said, my download could have been wonky. Dunno.

[huxley_knew]

I could be wrong, but unless I had some sort of download mishap when this was leaked a few weeks ago, this new file appears to be bigger. The previous download shows 29,881KB, but this latest file shows 40,750KB. As I said, my download could have been wonky. Dunno.

If yours is wonky, then so is mine. 40,750 here as well.

[Cyber Warrior]

Nope think you're right... I remember the last one being around 30kb as well.