Develop Bugs

Having a problem with rooting this phone.

Ok. I have installed the Wugfresh toolkit. And I have installed the drivers correct I think. So I click on unlock in the tool kit. It tells me to plug my phone in. So I do it. I see my device listed on top of the first screen. Then click YES I see mg device. But when it boot my phone into bootloader and then ask me do i see my device. I don't see it. Everytime it boots into bootloader it doesn't read mg device. So what am I doin wrong. Thanks abunch. I'm really ready to get Thomas phone unclocked and rooted.
Sent from my Galaxy Nexus using XDA

snapper915 said:
Ok. I have installed the Wugfresh toolkit. And I have installed the drivers correct I think. So I click on unlock in the tool kit. It tells me to plug my phone in. So I do it. I see my device listed on top of the first screen. Then click YES I see mg device. But when it boot my phone into bootloader and then ask me do i see my device. I don't see it. Everytime it boots into bootloader it doesn't read mg device. So what am I doin wrong. Thanks abunch. I'm really ready to get Thomas phone unclocked and rooted.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Did you read the directions?
but sounds like you don't have sdk set up right.....but I don't use tool kits....easy to do yourself without tool kit
Setup sdk
Fastboot oem unlock
Fastboot flash recovery
Flash super user from recovery
Sent from my Galaxy Nexus using Tapatalk 2

Epix4G said:
Did you read the directions?
but sounds like you don't have sdk set up right.....but I don't use tool kits....easy to do yourself without tool kit
Setup sdk
Fastboot oem unlock
Fastboot flash recovery
Flash super user from recovery
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
How do i set up sdk. Lol. I thought I had it.
Sent from my Galaxy Nexus using XDA

snapper915 said:
Ok. I have installed the Wugfresh toolkit. And I have installed the drivers correct I think. So I click on unlock in the tool kit. It tells me to plug my phone in. So I do it. I see my device listed on top of the first screen. Then click YES I see mg device. But when it boot my phone into bootloader and then ask me do i see my device. I don't see it. Everytime it boots into bootloader it doesn't read mg device. So what am I doin wrong. Thanks abunch. I'm really ready to get Thomas phone unclocked and rooted.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
You did not setup the drivers correctly. Once the phone boots into the bootloader there is an additional driver that needs to be installed. I forget the exact one but it is included in the toolkit. You probably have some unknown device in your device manager that you need to install the included drivers for in the WugFresh toolkit.
I had the same issue when I first started.

HeCareth said:
You did not setup the drivers correctly. Once the phone boots into the bootloader there is an additional driver that needs to be installed. I forget the exact one but it is included in the toolkit. You probably have some unknown device in your device manager that you need to install the included drivers for in the WugFresh toolkit.
I had the same issue when I first started.
Click to expand...
Click to collapse
Oh ok. Let me look there. Hopefully I can figure this mess out. Lol
Sent from my Galaxy Nexus using XDA

Download PDAnet and install it. This will solve the driver issue. Your issue is that your computer is not recognizing the phone as an ADB interface.

I was having the same problem and corrected it by plugging my phone into the USB port on the back of my PC rather than the one on the front. You can also contact WugFresh for assistance if you still can't figure it out. I had to follow the instructions on manually installing the drivers to my PC.

How do I relock boot loader for insurance

I am getting a replacement nexus and I am on 4.1 ROM (Verizon gnex) and need to go back to unrooted and all. How do I do it. Plz someone shoot me the link I have 2 more days too send it in thank u
Sent from my Galaxy Nexus using xda premium

frankiedizzle87 said:
I am getting a replacement nexus and I am on 4.1 ROM (Verizon gnex) and need to go back to unrooted and all. How do I do it. Plz someone shoot me the link I have 2 more days too send it in thank u
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Code:
fastboot oem lock

AshtonTS said:
Code:
fastboot oem lock
Click to expand...
Click to collapse
i have a new computer i have to start from scratch as far as adb and all. And i am so lost right now. when i finished re downloading ADB and did cmd and check ADB devices my nexus didnt show up

frankiedizzle87 said:
i have a new computer i have to start from scratch as far as adb and all. And i am so lost right now. when i finished re downloading ADB and did cmd and check ADB devices my nexus didnt show up
Click to expand...
Click to collapse
You gotta install adb driver for Nexus. For my computer, when I enabled usb debugging, it downloaded the driver for me (odd enough) but if your computer doesn't do that, you can Google around to get the exe file for you to install. Just make sure the Nexus has usb debugging on, or it doesn't let you install the driver (from my experience)
Sent from my Galaxy Nexus using xda app-developers app

frankiedizzle87 said:
i have a new computer i have to start from scratch as far as adb and all. And i am so lost right now. when i finished re downloading ADB and did cmd and check ADB devices my nexus didnt show up
Click to expand...
Click to collapse
Go to the development section and get the toolkit. Install all the required drivers. Lock her back up
Sent from my SGH-T999 using xda premium

uoY_redruM said:
Go to the development section and get the toolkit. Install all the required drivers. Lock her back up
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
ok i just went back to cm9 in a panic thinking no jelly bean drivers or something i dunno why i thought that. I will go into dev section and look for some drivers. The site that it gave says KIES is having issues so i cant even download kies. Can i still get drivers with out it? and when i did uSB debugging i still could not load drivers it said failed.

frankiedizzle87 said:
ok i just went back to cm9 in a panic thinking no jelly bean drivers or something i dunno why i thought that. I will go into dev section and look for some drivers. The site that it gave says KIES is having issues so i cant even download kies. Can i still get drivers with out it? and when i did uSB debugging i still could not load drivers it said failed.
Click to expand...
Click to collapse
It doesn't matter what you're currently on. You will completely nuke your phone when you fastboot the images onto your device anyway.

ok my computer currently recognizes my phone now and i know how to re lock my bootloader what rom should i put it on so they dont know i was rooted before relocking the bootloader. I thought locking it would set it back to default but i was wrong i just had cm9 with a locked bootloader lol i think they would know from that but seriously. What rom should i put to just make my phone 100000% stock

frankiedizzle87 said:
ok my computer currently recognizes my phone now and i know how to re lock my bootloader what rom should i put it on so they dont know i was rooted before relocking the bootloader. I thought locking it would set it back to default but i was wrong i just had cm9 with a locked bootloader lol i think they would know from that but seriously. What rom should i put to just make my phone 100000% stock
Click to expand...
Click to collapse
The stock ROM, there's a full factory restore through Odin. Its in one of the stickies.

You can do everything using gnex toolkit v7.0.
Sent from my Galaxy Nexus using xda premium

Download the factory image from Google and flash to stock
https://developers.google.com/android/nexus/images
Sent from my Galaxy Nexus using xda app-developers app

frankiedizzle87 said:
ok my computer currently recognizes my phone now and i know how to re lock my bootloader what rom should i put it on so they dont know i was rooted before relocking the bootloader. I thought locking it would set it back to default but i was wrong i just had cm9 with a locked bootloader lol i think they would know from that but seriously. What rom should i put to just make my phone 100000% stock
Click to expand...
Click to collapse
So you got everything stock except the ROM? So you got stock recovery and everything? If you do, first of all, download the stock rom from google site (there should be few versions, that, you gotta find it out) then you need to download clockwork mod recovery (assuming that you got fastboot and adb) now just boot into cwm on your phone and flash the stock rom. By doing this, you're not over writing the recovery but you can still use the cwm
Also you gotta unlock first lol
Sent from my Galaxy Nexus using xda app-developers app

[Q] Sorry for being a noob, rooting question

Just got the GNex, coming from droid charge and was wondering if Odin can be used to root this phone? I only ask because I'm used to it from the Charge. If it can, is it simple like flashing superuser? Sorry if this is the dumbest question ever. I was searching the forums for the answer, but didnt find one.

cnoevl21 said:
Just got the GNex, coming from droid charge and was wondering if Odin can be used to root this phone? I only ask because I'm used to it from the Charge. If it can, is it simple like flashing superuser? Sorry if this is the dumbest question ever. I was searching the forums for the answer, but didnt find one.
Click to expand...
Click to collapse
Not sure if you can use Odin to root this phone but, I know it's super easy to root using fastboot. Just make sure you have the drivers installed
Sent from my Galaxy Nexus using Tapatalk 2

No, we don't use ODIN for anything except a last-resort restore attempt on a "bricked" device.
Rooting is done via the command line: http://forum.xda-developers.com/showthread.php?t=1529058

You are given the easier way, fastboot and adb. Take advantage of it. Odin should not be used unless you bricked your phone somehow and can't even get to the recovery. Welcome to galaxy nexus. You'll get used to fastboot commands real fast, real quick
Swyped on my Galaxy Nexus running AOKP with Franco Kernel

Tried using fast boot to unlock bootloader bit it won't seem to work. I checked off usb debugging, went into c promt on my pc after dl fast boot and installing proper drivers but wen I type fastboot-windows oem unlock it says it's not a proper prompt. That's why I asked abt Odin. Guess I'll look deeper and figure something, I'll check out the link that was left in the reply, maybe I can get rooted that way. Thanks for the replies everyone.
Sent from my Galaxy Nexus using xda app-developers app

cnoevl21 said:
Tried using fast boot to unlock bootloader bit it won't seem to work. I checked off usb debugging, went into c promt on my pc after dl fast boot and installing proper drivers but wen I type fastboot-windows oem unlock it says it's not a proper prompt. That's why I asked abt Odin. Guess I'll look deeper and figure something, I'll check out the link that was left in the reply, maybe I can get rooted that way. Thanks for the replies everyone.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
You're holding it wrong.
Sent from my i9250

cnoevl21 said:
Tried using fast boot to unlock bootloader bit it won't seem to work. I checked off usb debugging, went into c promt on my pc after dl fast boot and installing proper drivers but wen I type fastboot-windows oem unlock it says it's not a proper prompt. That's why I asked abt Odin. Guess I'll look deeper and figure something, I'll check out the link that was left in the reply, maybe I can get rooted that way. Thanks for the replies everyone.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I think a bit more reading is called for.
1) USB Debugging has no impact on being able to use fastboot commands;
2) To use fastboot commands, your device needs to be booted into the bootloader;
3) There are two drivers for your device (contained in the same package): a fastboot driver and an ADB driver. If you installed the ADB driver, it does not necessarily mean you installed the fastboot driver;
4) You need to be booted into the bootloader to install the fastboot driver;
5) You need to execute fastboot commands from the same folder you to which you downloaded fastboot.exe. For example, if you downloaded fastboot.exe to C:\junk, and you are trying to type in "fastboot flash yadayadayada" at the C:> prompt, it will not work. If you are at the C:> prompt, you need to type "cd junk" to get you in the right directory, and then your command prompt will change to C:\junk>

cnoevl21 said:
Tried using fast boot to unlock bootloader bit it won't seem to work.
Click to expand...
Click to collapse
Are you getting an error? If so, what is it?
What happens when you type "fastboot devices" at the command prompt (without the quotes)?

Might be another dumb question, but do you have the Android SDK installed on your computer?
Sent from my Galaxy Nexus using xda premium

Pierceye said:
Might be another dumb question, but do you have the Android SDK installed on your computer?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
You don't need the SDK to use fastboot as long as you gave the one file, i.e., fastboot.exe

bk201doesntexist said:
You're holding it wrong.
Sent from my i9250
Click to expand...
Click to collapse
Go to where fastboot and adb are. If have win7 press shift and right click mouse at same time. Choose open command window here.
Type and press enter after each
adb devices
(Should get a serial)
adb reboot reboot-bootloader
(Should reboot)
Fastboot reboot reboot-fastboot
(Not sure if needed but I do anyway)
fastboot oem unlock
*Shaolin Shadowboxing*

efrant said:
I think a bit more reading is called for.
1) USB Debugging has no impact on being able to use fastboot commands;
2) To use fastboot commands, your device needs to be booted into the bootloader;
3) There are two drivers for your device (contained in the same package): a fastboot driver and an ADB driver. If you installed the ADB driver, it does not necessarily mean you installed the fastboot driver;
4) You need to be booted into the bootloader to install the fastboot driver;
5) You need to execute fastboot commands from the same folder you to which you downloaded fastboot.exe. For example, if you downloaded fastboot.exe to C:\junk, and you are trying to type in "fastboot flash yadayadayada" at the C:> prompt, it will not work. If you are at the C:> prompt, you need to type "cd junk" to get you in the right directory, and then your command prompt will change to C:\junk>
Click to expand...
Click to collapse
Or go to where you saved your fastboot.exe, right click in the blank space of the folder without selecting anything, then Open command window here:good:

i just got my nexus today and unlocked and rooted it within 20 odd mins.. using galaxy nexus toolkit.. it was a breeze throughout the process...

vivek2701 said:
i just got my nexus today and unlocked and rooted it within 20 odd mins.. using galaxy nexus toolkit.. it was a breeze throughout the process...
Click to expand...
Click to collapse
And did you learn a lot about the process and how to flash by using the toolkit?

vivek2701 said:
i just got my nexus today and unlocked and rooted it within 20 odd mins.. using galaxy nexus toolkit.. it was a breeze throughout the process...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1529058

efrant said:
And did you learn a lot about the process and how to flash by using the toolkit?
Click to expand...
Click to collapse
I sense a hint of sarcasm in that... or is it just me :silly:.

Step away from the toolkit and noROM gets hurts...
*Shaolin Shadowboxing*

efrant said:
And did you learn a lot about the process and how to flash by using the toolkit?
Click to expand...
Click to collapse
I was in a hurry n found this the best noob guide with step by step instructions .. is using toolkit not the best method?
Sent from my Galaxy Nexus using xda premium

vivek2701 said:
I was in a hurry n found this the best noob guide with step by step instructions .. is using toolkit not the best method?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
See signature...
*Step Away From The Toolkit And NoROM Gets Hurt*

Learn fastboot and never use a toolkit.

[Q] Recovery

My Verizon nexus is stuck in boot loop. My volume up button does not work so i cant get into fast boot. Is there any other way that i can get into recovery to nandroid? Or any odin methods i can use to get it back without erasing internal storage preferably? If there is no way possible then i assume i will have to flash stock images.
-Thanks much

Take a look at this... It may give you some guidance.
http://forum.xda-developers.com/showthread.php?t=1827685
Sent from my Galaxy Nexus using xda app-developers app

wisefreakz said:
Take a look at this... It may give you some guidance.
http://forum.xda-developers.com/showthread.php?t=1827685
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
why would you suggest an unsupported tool to reflash/update a fw, of a Nexus? just because it's made by samsung, doesnt mean that samsung supports it, and the flashing through odin.
OP, use FASTBOOT, it's the tool Google INSTRUCTS you to use to recover a Nexus device to factory status.
http://forum.xda-developers.com/showthread.php?t=1626895

bk201doesntexist said:
why would you suggest an unsupported tool to reflash/update a fw, of a Nexus? just because it's made by samsung, doesnt mean that samsung supports it, and the flashing through odin.
OP, use FASTBOOT, it's the tool Google INSTRUCTS you to use to recover a Nexus device to factory status.
http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Really?? Can you read well??
1) his vol up is not working... So no ADB for fastboot commands.
2) i used the word GUIDANCE... Way different from YOU HAVE TO or MANDATORY.
Giz...
Sent from my Galaxy Nexus using xda app-developers app

Weel, in order to reach the recovery is quite simple. If i'm not wrong, you just have to install correctly adb driver in your pc and, once installed the driver and plugged in the device, you just have to open cmd or terminal or whatelse depending on your os and write "adb reboot bootloader" without "
Or even easier (but you need root), install rom toolbox (both free or pay, your choice) and inside there's an option to choose where to reboot, bootloader, recovery or simple reboot.
EDIT: @wisefreakz: fastboot it's necessary only for fastboot command, for adb command the device could be running (ie when you get a bootloop you're not in fastboot but, instead of pulling off the battery it's better to prompt a good adb reboot), isn't it?

Thanks much. I used the link provided. Since I'm back on cna I can boot from the power menus. Appreciate your time
Sent from my Galaxy Nexus using xda app-developers app

[Q] "Error: Device not found" in adb.

Hello friends,
I'm trying to install cyanogenmod and no matter what I do I consistently get the device not found error when I try to use "adb push cm-10.2.0-RC1-endeavoru.zip \sdcard\"
I know that in the cyanogenmod install guide it says it's probable that it's a driver issue. I've looked around for a good 2 hours trying to find what it might be, so I've tried reinstalling htc sync, I've tried uninstalling htc sync and using koush's universal adb driver, but nothing seems to work.
When using "adb devices" it doesn't give me the error, it just gives me "List of devices attached" which is empty. (I'm not sure if this is what it is supposed to do though)
Attached img of what I've been doing.
USB debugging is on. It's been automatically turned on whenever I connect it to my PC since I updated to 4.2.2 anyway.
I have no idea where to go from here. Any help would be appreciated.

Aireon said:
Hello friends,
I'm trying to install cyanogenmod and no matter what I do I consistently get the device not found error when I try to use "adb push cm-10.2.0-RC1-endeavoru.zip \sdcard\"
I know that in the cyanogenmod install guide it says it's probable that it's a driver issue. I've looked around for a good 2 hours trying to find what it might be, so I've tried reinstalling htc sync, I've tried uninstalling htc sync and using koush's universal adb driver, but nothing seems to work.
When using "adb devices" it doesn't give me the error, it just gives me "List of devices attached" which is empty. (I'm not sure if this is what it is supposed to do though)
Attached img of what I've been doing.
USB debugging is on. It's been automatically turned on whenever I connect it to my PC since I updated to 4.2.2 anyway.
I have no idea where to go from here. Any help would be appreciated.
Click to expand...
Click to collapse
mount the sdcard inside the recovery and copy the rom

Mr Hofs said:
mount the sdcard inside the recovery and copy the rom
Click to expand...
Click to collapse
Sorry, I'm completely new to this. Do you mean normal recovery from bootloader or a custom recovery that I should of done but completely skipped due to my ignorance? (I also haven't unlocked bootloader so I'm assuming that's a misstep as well?)
Because all I get when I do the normal recovery is a picture of a phone with a red triangle and "!" combo.
Thanks

Yeah to install a custom rom it's mandatory to unlock the bootloader and install a custom recovery. And what i can tell from your post it that you really are a novice on things. Some tips ?
1: never start without a full battery
2: learn fastboot + commands
3: always make a stock rom nandroid backup before starting flashing !
Read up in this forum. Under the stickys there are some nifty guides. If you have questions after that just ask here.

Mr Hofs said:
Yeah to install a custom rom it's mandatory to unlock the bootloader and install a custom recovery. And what i can tell from your post it that you really are a novice on things. Some tips ?
1: never start without a full battery
2: learn fastboot + commands
3: always make a stock rom nandroid backup before starting flashing !
Read up in this forum. Under the stickys there are some nifty guides. If you have questions after that just ask here.
Click to expand...
Click to collapse
Thanks for the tips!
After a while of toiling to try and unlock the boot loader manually and getting stuck at the load error for Unlock_code.bin, I found Hasoon2000's tool, so he is my god for now.
My query that I have is, Do I need a custom recovery like ClockWorkMod to create a nandroid back up? Because all I get when I try to go into recovery from the bootloader is this (img attached, not mine because I don't have another camera in the house but luckily I managed to find one on google img.)
I can't find anything saying that I do need a custom recovery, but then again it's not working when I try without one, so I'm not too sure where to go from here.
Thanks again

Please read carefully what i write, i know exactly what to do !
You need a custom recovery !

Sorry to be back again so soon but I'm stuck again, haha.
When I try to flash cwm I get "error: cannot load 'recovery.img'". When I try to use Hasoon2000's tool kit to do it for me it doesn't work either as it just says device not found and in the second command window it says that it can't load it's .img file either.
The recovery.img is in the same location as fastboot. My phone is in Fastboot in bootloader.
I'm typing "r:\Android\adt\sdk\platform-tools\fastboot flash recovery recovery.img". Trying to auto complete recovery.img using tab does nothing (if that might indicate some sort of problem).
The only thing I can think of is that the MTP drivers never install properly but I read on this forum that it shouldn't affect fastboot.

If you are on windows you must select camera as usb option
Sent from my GT-I8190 using xda app-developers app
---------- Post added at 02:25 AM ---------- Previous post was at 02:22 AM ----------
I mean windows 8
Sent from my GT-I8190 using xda app-developers app

robindebruin said:
If you are on windows you must select camera as usb option
Sent from my GT-I8190 using xda app-developers app
---------- Post added at 02:25 AM ---------- Previous post was at 02:22 AM ----------
I mean windows 8
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Ah, I probably should of said it earlier, sorry. I'm using windows 7.

And did you install java jdk and driver
Sent from my GT-I8190 using xda app-developers app

robindebruin said:
And did you install java jdk and driver
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
If javaj jdk is just normal java then yes. In programs and features it's called Java 7 Update 45?
Do you mean the phone drivers on my PC?
Edit: Noticed jdk was the dev kit. Downloaded and installed. Will try again.
Edit2: Still not working, same errors.

Jre is normal java jdk is the development kit
and yes that drivers
Sent from my GT-I8190 using xda app-developers app

robindebruin said:
Jre is normal java jdk is the development kit
and yes that drivers
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
I just updated the phone drivers (without HTC sync) from http://forum.xda-developers.com/showthread.php?t=2376761 to 4.2.0.001 from the 4.0 version I had that HTC sync had installed previously for some reason.
Shows up in fastboot devices now. Still doesn't show up in adb devices. Still getting the can't load recovery.img error.
Would it be worth it to try doing it on another computer?

Yes and plz post results
Sent from my GT-I8190 using xda app-developers app

robindebruin said:
Yes and plz post results
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Ok so I still couldn't do it manually on the other computer. Got the same errors as with the first. I tried flashing with Hasoon2000's tool again and noticed that it was trying to flash CWM.img while the recovery for it was actually called recovery.img. Renamed it to CWM.img and it flashed perfectly.
I assume it would of done the same on the original PC I tried it on.
No idea why it wouldn't work when I tried it manually, but yolo. Hasoon2000 is love. Hasoon2000 is life.

Holy hell Hasoon2000 has saved me again.
I flashed the kernal by accident and it got stuck in boot. So i just sideloaded the rom in H2K's tool and everything turned up Milhouse.

Yay congrats
Sent from my GT-I8190 using xda app-developers app

And if it says can not load recovery that means it's named differently or that it's not placed in the same dir of the fastboot files. A common error is that people hide filename extensions in windows. Then rename the recovery to recovery.img.img and then it won't be found by fastboot

Mr Hofs said:
And if it says can not load recovery that means it's named differently or that it's not placed in the same dir of the fastboot files. A common error is that people hide filename extensions in windows. Then rename the recovery to recovery.img.img and then it won't be found by fastboot
Click to expand...
Click to collapse
Hmmm, I'm not sure what it would of been as a tried flashing recovery.img.img as well. But everything worked out well in the end .
Thank you both the help.

Glad to hear that it worked
Sent from my GT-I8190 using xda app-developers app