Develop Bugs

[Q] GNex on Stock ICS 4.03; can't root or flash

Hey guys i bought a GNex off a Google employee and the phone came stock with 4.03. I've already unlocked the bootloader but can't get the phone rooted or flash with a different rom. I've even tried to upgrade to 4.04 that was just released but it will not let me upgrade.
Is there a way i can flash to 4.02? any help will be greatly appreciated

maluthug said:
Hey guys i bought a GNex off a Google employee and the phone came stock with 4.03. I've already unlocked the bootloader but can't get the phone rooted or flash with a different rom. I've even tried to upgrade to 4.04 that was just released but it will not let me upgrade.
Is there a way i can flash to 4.02? any help will be greatly appreciated
Click to expand...
Click to collapse
Have you rooted and installed CWM Recovery?

cannot root the phone, i've tried and phone just hangs

Have you downloaded the gnex toolkit in the development thread and tried that?
Sent from my Galaxy Nexus using xda premium

tried the wugfresh and the gnex toolkit 5.2; wont let me root 4.03

Have you installed a custom recovery?

which custom recovery? cwm recovery will not work without root access correct?

you can not have cwm recovery without root. do u have a GSM or LTE GN?

LTE version
I cant seem to find a way to root 4.0.3

maluthug said:
which custom recovery? cwm recovery will not work without root access correct?
Click to expand...
Click to collapse
Incorrect.
Root access gives you write access to the OS, which is separate from recovery. The standard root method for a Nexus device is to remove security from the bootloader, which then allows you to install non-signed images. You then install a custom recovery image. The custom recovery allows you to flash non-signed OS changes, which means you can flash the su binary and busybox (giving you root)...
You need to use fastboot to flash cwm, then you can install su and busybox...

ok gotcha, i was under the stupid assumption that i needed to gain root access to install a custom recovery. im going to give it a shot and see what happens

If you want to install recovery from the OS, then you would need an insecure/rooted OS. If you want to install recovery from the bootloader, then you would need an insecure/unlocked bootloader...

danger-rat said:
If you want to install recovery from the OS, then you would need an insecure/rooted OS. If you want to install recovery from the bootloader, then you would need an insecure/unlocked bootloader...
Click to expand...
Click to collapse
thanks so much, got recovery on there and updated the phone and rooted it as well. appreciate the help

Same here
Same thing happened to me. I installed the Gnex toolkit and unlocked the bootloader. Then I tried to root the phone: It restarted and I turned on USB debugging as it said and nothing happened.
So you're saying that I can skip the rooting and "Rename Recovery Restore File" before I "Flash CWM Recovery". After that I can try rooting through Gnex Toolkit 5.2?

Can I flash CWM on Non-Rooted Nexus, but Unlocked Bootloader?

Hey.
Title says all.
Or should I just boot into recovery without flashing when I need to do it on the toolkit?
Also, for flashing kernels do they require root?
Thanks!

Cwm can be flashed on non-rooted as long ad its unlocked.
Sent from my Galaxy Nexus

ok thanks man and do you know if kernels require root? To install?
edit: Tried to flash CWM and it said "an error occurred while attempting to run privileged commands!" Looks like it requires su.

Without root, you'll have to do it via fastboot. Go to clockworkmod site and download the one for your phone, your call as for touch version or not. Place it in the same directory as fastboot, then "fastboot flash recovery <filename>".

Alright thanks Johan. Do you know if flashing kernels requires root?

No, but you'll have to go into CWM (or use fastboot) to flash one, meaning you can't just use rom manager or other apps that install stuff.

Alright, thanks.

Root is only require inside the os. Everything else can be done with just unlocking.
Sent from my Galaxy Nexus

[Q] Nexus Factory image, can I flash it like a ROM?

So the Verizon 4.0.4 Factory Image was just published by Google, so I downloaded it to my phone for safe keeping. I'm just curious, if I install a custom ROM and I want to go back to stock ICS can I just flash this file like a ROM? Also will I loose root if I do that?
This is what I'm talking about.

Yes you loose root and custom recovery.
CM9 kang powered by TRINITY

actually, no... you have to flash it using fastboot commands, flashing image by image:
fastboot flash bootloader bootloaderxxxxx.img
fastboot flash system systemxxxx.img
fastboot flash recovery recoveryxxx.img
etc, etc, etc...
your phone will be exactly like never touched, that means of course, stock with no root or custom recovery.

barbac666 said:
Yes you loose root and custom recovery.
CM9 kang powered by TRINITY
Click to expand...
Click to collapse
thiagodark said:
actually, no... you have to flash it using fastboot commands, flashing image by image:
fastboot flash bootloader bootloaderxxxxx.img
fastboot flash system systemxxxx.img
fastboot flash recovery recoveryxxx.img
etc, etc, etc...
your phone will be exactly like never touched, that means of course, stock with no root or custom recovery.
Click to expand...
Click to collapse
Thank you, so when I rooted my phone it created a recovery image, and that's what I would want to use to go back to "stock + keeping root"
Right?

Yes make a nandroid backup in CWM , and if you want to go back restore this.
In CWM go to backup and restore.
CM9 kang powered by TRINITY

Big Cam said:
Thank you, so when I rooted my phone it created a recovery image, and that's what I would want to use to go back to "stock + keeping root"
Right?
Click to expand...
Click to collapse
don't understand exactly what you mean... the thing is:
"root" means that you have access to root files/partitions, that is it, but the usual way to get root is: unlock bootloader, flash custom recovery using fastboot, flash root file.
now you have a "stock" phone with root access and custom recovery (usually custom recovery is replaced by stock one in the first reboot) and you end with a stock phone + root! that is exactly what you want!
as barbac666 said, you should make a nandroid backup as soon as you flash your custom recovery, even before root it!
why don't you use the tool kit available in dev section?

It's alot easier if you use the Nexus tool kit v7, It makes it alot easier by placing the image file in the specific folder and just tapping a key. Then again it's best to keep a placed copy elsewhere as the image tends to get wiped/deleted after flashing (to avoid conflict with other image files).

thiagodark said:
don't understand exactly what you mean... the thing is:
"root" means that you have access to root files/partitions, that is it, but the usual way to get root is: unlock bootloader, flash custom recovery using fastboot, flash root file.
now you have a "stock" phone with root access and custom recovery (usually custom recovery is replaced by stock one in the first reboot) and you end with a stock phone + root! that is exactly what you want!
as barbac666 said, you should make a nandroid backup as soon as you flash your custom recovery, even before root it!
why don't you use the tool kit available in dev section?
Click to expand...
Click to collapse
I think I got it. I think I slightly misunderstood the true meaning of root.
All I've done so far is unlock the bootloader and flashed the recovery that was instructed in this thread. So the recovery image I flashed there, replaced my "stock" one, but after doing a reboot, the stock recovery replaced my custom one? So I'm now stock with an unlocked bootloader and root?
As for the toolkit, I'm going to look into it, I was just looking to root, and followed the guide I found.

thiagodark said:
don't understand exactly what you mean... the thing is:
"root" means that you have access to root files/partitions, that is it, but the usual way to get root is: unlock bootloader, flash custom recovery using fastboot, flash root file.
now you have a "stock" phone with root access and custom recovery (usually custom recovery is replaced by stock one in the first reboot) and you end with a stock phone + root! that is exactly what you want!
as barbac666 said, you should make a nandroid backup as soon as you flash your custom recovery, even before root it!
why don't you use the tool kit available in dev section?
Click to expand...
Click to collapse
You dont need to flash cwm to get it running. If its only needed to flash su/superuser.apk, you may 'fastboot boot cwm.img', it will take you to cwm.
Misledz said:
It's alot easier if you use the Nexus tool kit v7, It makes it alot easier by placing the image file in the specific folder and just tapping a key. Then again it's best to keep a placed copy elsewhere as the image tends to get wiped/deleted after flashing (to avoid conflict with other image files).
Click to expand...
Click to collapse
Why doesnt he use the toolkit? Because it's better for them if people learn how to do this manually. Scripts are helpful, but dont teach you anything.
Sent from my i9250

bk201doesntexist said:
Why doesnt he use the toolkit? Because it's better for them if people learn how to do this manually. Scripts are helpful, but dont teach you anything.
Sent from my i9250
Click to expand...
Click to collapse
That's exactly why I wanted to do it like that.
On my LG Revolution there was pretty much only one root method and it was a one click, so I've never rooted manually. I'm happy I did.
I have Rom ToolBox Pro that I bought when I had my Revolution so I have access to boot to recovery and manage ROM's. I was just curious about the Google image file.
So at this point, is there really a reason for the Toolbox? Since I'm rooted already, I can do backups from CWM Recovery as well as flashing ROM's and Kernals. I've only ever done this from CWM on the phone so I'm used to doing it on the phone. I read most of the thread and it seams most helpful in the rooting/unlocking process.

[Q] root through odin not working

i just bought an ssg2 which was apparently unlocked. trying to root it through odin but it doesnt do anything. as soon as i click start all it does is nothing. it is running stock gingerbread.
any input dudes?

Phone recognized by the PC? Correct drivers installed on the PC? Have you followed the steps properly?

You need to flash a custom recovery first, something like Clockwork Recovery or TWRP (I think that's right?), and flash a root binary through that, in your case it would be a file called 'su-3.0.5' (that's for gingerbread).
There are tons of guides here on how to install a custom boot recovery and how to root, find one that you understand and follow it.

not sure what to do from here?

ok, I got stock 4.4.4 but with root, bootloader is locked..
I wanna be able to receive the OTA update what do I need to do in order to be able to receive that?
or do I need to unlock the bootloader, install a recovery and flash lollipop threw that?

If you have stock system, kernel, and recovery, (no altered system files, either) being rooted won't keep you from getting the OTA. Locked/unlocked bootloader doesn't matter. If you rooted with SuperSu, just use its settings to uninstall root (you'll lose it anyway). However, I think you have to unlock bootloader to reroot, which, of course, will wipe your device. The OTA zip is now available for adb sideload if you're interested.

nvm got stock recovery back on, lol still learning, is it better to side load or can i use flash stock + unroot on the nexus root toolkit v1.9.3 to do the same?

Cobra11Murderer said:
nvm got stock recovery back on, lol still learning, is it better to side load or can i use flash stock + unroot on the nexus root toolkit v1.9.3 to do the same?
Click to expand...
Click to collapse
OTA won't wipe regardless of how you get it--over the air or sideloaded. Wug's will wipe unless you tell it not to (Options>Flash Stock>Enable no wipe). He also has the LRX21P build available. IMO, one way isn't better than another.

ok, I just tried to sideload and looks like i got a driver issue :\ lol followed the steps in the installation guide and did the test.. it works great up till i go into stock recovery and hit sideload lol then it disconnects and tells me no driver found...
i might just try flash stock + unroot and choosing LRX21P, that wont lock my bootloader correct? and should I be a little worried that the driver cant be found for that specific thing? thanks for all the help btw!

You probably already did all this, but you have to specifically send command to lock boot loader. I don't get how your device wasn't recognized through stock recovery but is on NRT, but it doesn't matter. Just use the kit which is what you probably did.

What you should do is back up what you need and want, then unlock the bootloader. You're not gonna get root without it on Android L since it requires a custom kernel.

Cobra11Murderer said:
ok, I just tried to sideload and looks like i got a driver issue :\ lol followed the steps in the installation guide and did the test.. it works great up till i go into stock recovery and hit sideload lol then it disconnects and tells me no driver found...
i might just try flash stock + unroot and choosing LRX21P, that wont lock my bootloader correct? and should I be a little worried that the driver cant be found for that specific thing? thanks for all the help btw!
Click to expand...
Click to collapse
Based on this, I assumed you unlocked your bootloader since first posting. NRT recognizes the device, right? Have you gotten it all sorted out yet.

idk why adb sideloading would kick the connection out, then the pc would say nexus 7 but wrong driver?, anyways i just went ahead and flashed the factory image using flash stock + unroot since I had it all backed up anyways, and that went great now I got lollipop on it, and should be able to root no probs now
thanks everyone, I hope i dont have a issue with adb again, im not sure if it was the samsung cord or what but it kept disconnecting at that part asking for a driver.. funny thing everything from bootloader, fastboot and all worked great with the driver that I installed using the steps in the toolkit..

Glad it's all good. Root with the toolkit. Just for the heck of it, you may want to try running CMD from wug's ADB folder. I've experienced just the opposite with older versions of the kit. NRT wouldn't recognize device. I'd go to CMD and device recognized. Return to NRT, all good again.

alrighty will do!, thanks for all your help