Related
Was wondering when I get my galaxy nexus this Friday, can I root using the Verizon lte method? Or will it screw my phone up? Also putting roms on my phone, none will be compatible right? This thread is realty going to get confusing, with 3 different phones using it. Thanks
Sent from my PC36100 using Tapatalk 2
Do it the correct way and do not use a toolkit.
Code:
adb reboot bootloader
fastboot oem unlock (this causes a data wipe and you must re-enable usb debugging)
download a toro recovery image locally to PC
download su.zip from link below to sdcard
adb reboot bootloader
fastboot boot recoveryname.img
flash su.zip from clockwork.
Rooted and rooted.
Or if you want it to be permanent, boot up after rooted and rename install-recovery.sh under system/etc.
Then go back to fastboot
Code:
adb reboot bootloader
fastboot flash recovery recoveryname.img
fastboot reboot
Find files here:
http://www.droid-life.com/2012/02/06/how-to-root-android-4-0-4-on-the-galaxy-nexus/
adrynalyne said:
Do it the correct way and do not use a toolkit.
Click to expand...
Click to collapse
if only more people did their rooting this way...
So there will be no roms for sprints version for a while right? Also I ordered casemates barely there case(Verizon) do you think it will fit?
Sent from my PC36100 using Tapatalk 2
globen said:
So there will be no roms for sprints version for a while right? Also I ordered casemates barely there case(Verizon) do you think it will fit?
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
Verizon cases will most likely be perfect. No way to know for sure though.
Also, Sprint roms should be very easy to come out with. Depends on how complete the device tree for Sprint is on AOSP.
We will need a system dump for proprietaries though to get the ones Google will not provide.
globen said:
Was wondering when I get my galaxy nexus this Friday, can I root using the Verizon lte method? Or will it screw my phone up? Also putting roms on my phone, none will be compatible right? This thread is realty going to get confusing, with 3 different phones using it. Thanks
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
Really wish they'd separate this section =/
GSM/CDMA is bad enough.
But yes, the method will work.
BUT you may need a new CWM.img...that hasn't been released yet (and won't be until someone gets their hands on the phone.
Either way.
Use the link stickied above.
Same link in my sig.
I'll keep it updated if it needs to be changed upon release.
Sprint will still be using Toro I believe.
Verison Cases
Got my Sprint Galaxy Nexus the other day. Just bought a rockfish case - stating it was for Verison GN. Just to let U know, as expected... The case fits perfect!!!
Awaiting patiently (not really) to get this new puppy rooted!~~~
adrynalyne said:
Verizon cases will most likely be perfect. No way to know for sure though.
Also, Sprint roms should be very easy to come out with. Depends on how complete the device tree for Sprint is on AOSP.
We will need a system dump for proprietaries though to get the ones Google will not provide.
Click to expand...
Click to collapse
I'm running AOKP with the CMPlus kernel. I want to encrypt my phone. Every time I try to start the encryption an android appears and the phone reboots. Then it doesn't even try to activate encryption. What can I do to get it encrypted?
Sent from my Galaxy Nexus using xda premium
I guess be glad it is failing. Don't encrypt if on custom rom, it will become difficult to flash ever again (without a full device wipe) and nandroids won't even work after.
good day.
chopper the dog said:
I guess be glad it is failing. Don't encrypt if on custom rom, it will become difficult to flash ever again (without a full device wipe) and nandroids won't even work after.
good day.
Click to expand...
Click to collapse
I'm aware of the difficulty that cones with encryption but since I rooted to record business calls, encryption is a really good idea. Any idea how to get it working? Thanks
Sent from my Galaxy Nexus using xda premium
Don't use a custom kernel, report issue to AOKP dev team.
Sent from my i9250
bk201doesntexist said:
Don't use a custom kernel, report issue to AOKP dev team.
Sent from my i9250
Click to expand...
Click to collapse
I didn't know you couldn't use a custom kernel. I'll try it with straight AOKP
Edit: Even with the stock kernel from AOKP it fails. Phone just reboots. AOKP site also seems to be down right now.
fbiryujin said:
I didn't know you couldn't use a custom kernel. I'll try it with straight AOKP
Edit: Even with the stock kernel from AOKP it fails. Phone just reboots. AOKP site also seems to be down right now.
Click to expand...
Click to collapse
Could be your recovery.
Sent from my Galaxy Nexus using Tapatalk 2
geoffcorey said:
Could be your recovery.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm using the latest CWM for Galaxy Nexus. What should I use? Thanks
fbiryujin said:
I'm using the latest CWM for Galaxy Nexus. What should I use? Thanks
Click to expand...
Click to collapse
Try going back to stock recovery and see if encryption works. Also, you could try twrp and see if it works there as well.
Sent from my Galaxy Nexus using Tapatalk 2
geoffcorey said:
Try going back to stock recovery and see if encryption works. Also, you could try twrp and see if it works there as well.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'll try TWRP first, but if that fails, how do I get stock recovery back? (I'm using the GSM maguro if that makes a difference)
fbiryujin said:
I'll try TWRP first, but if that fails, how do I get stock recovery back? (I'm using the GSM maguro if that makes a difference)
Click to expand...
Click to collapse
To get stock recovery, find your stock 4.0.4 google image and flash the recovery using fastboot.
Sent from my Galaxy Nexus using Tapatalk 2
geoffcorey said:
To get stock recovery, find your stock 4.0.4 google image and flash the recovery using fastboot.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Even with stock recovery it doesn't work.
Edit: Just tried it with CM9 nightly as well, and the same thing happens. I'd really like to get encryption working.
fbiryujin said:
Even with stock recovery it doesn't work.
Edit: Just tried it with CM9 nightly as well, and the same thing happens. I'd really like to get encryption working.
Click to expand...
Click to collapse
Try going back to stock 4.0.4 ics and encrypting there. If it works, there are some test recoveries that support encryption and you could possibly flash a custom rom on top of it.
Sent from my Galaxy Nexus using Tapatalk 2
geoffcorey said:
Try going back to stock 4.0.4 ics and encrypting there. If it works, there are some test recoveries that support encryption and you could possibly flash a custom rom on top of it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks. I'll give it a shot.
i would advise against that;
check this thread, 2nd post
bk201doesntexist said:
i would advise against that;
check this thread, 2nd post
Click to expand...
Click to collapse
Thanks for the warning but I'm aware of that. The latest TWRP can work with encrypted /sdcard though. Plus if I get stuck, I'm told "fastboot erase userdata" will format /sdcard and remove the encryption.
Just bought my Nexus a little over a week ago as to an S3 can't seem to update to jelly bean for some reason though..help?
Sent from my Galaxy Nexus using xda app-developers app
Lol. Just download the Tool Kit and the official Google 4.1.1 firmware that is available from their site (Links are in Development Section | Official Firmware links) make sure you know if your's is maguro or toro, then download the respective firmware and flash it via ToolKit.
Misledz said:
Lol. Just download the Tool Kit and the official Google 4.1.1 firmware that is available from their site (Links are in Development Section | Official Firmware links) make sure you know if your's is maguro or toro, then download the respective firmware and flash it via ToolKit.
Click to expand...
Click to collapse
Don't use a toolkit. Learn how to unlock bootloader and fastboot on your own as it is better than having it spoon fed
Did you try going into Settings > Apps > All Applications > Google Services Framework & Clear cache / Clear data? Sometimes doing that will make it work. Try that. Don't use a toolkit...
Misledz said:
Lol. Just download the Tool Kit and the official Google 4.1.1 firmware that is available from their site (Links are in Development Section | Official Firmware links) make sure you know if your's is maguro or toro, then download the respective firmware and flash it via ToolKit.
Click to expand...
Click to collapse
Let's not forget needs about toroplus.. don't need Verizon stuff on sprint. Adb is so easy! Use that! Toolkit is for halfa++ corner cutters
After you clear cache go to your dialer and type *#*#checkin#*#* and wait for confirmation then immediately go to settings about phone and update.
Based on the screen shot, it's gsm but build number isn't there. What build is the Op on? So far it's only yakju/takju, yakjuxw, yakjuxe, and yakjuzs that have jb so if he's on a different build and really want jb, then he needs to flash but if he can wait, then he has to wait still
Sent from my Galaxy Nexus using Tapatalk 2
you just unlock bootloader using toolkit
Sent from my Galaxy Nexus using Tapatalk 2
arrish4 said:
you just unlock bootloader using toolkit
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Stop that. Hold-your-hand-kits are bad.
Sent from my Galaxy Nexus using xda premium
arrish4 said:
you just unlock bootloader using toolkit
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Don't you look out for traffic when crossing the road?
Someone already got knocked over and you still want to try cross a highway.
Pics not showing on my end....and three simple words
fastboot oem unlock
Doesn't get easier than that.
And if just trying to get updates then do the checkin dialer. It forces the update to push
I was stuck on 4.0.3 for a week and just got tired of waiting and just rooted and loaded the stock 4.1.1 rom. This was my first time rooting and loading the rom. Wasn't hard at all.
Sent from my Galaxy Nexus using xda app-developers app
Misledz said:
Lol. Just download the Tool Kit and the official Google 4.1.1 firmware that is available from their site (Links are in Development Section | Official Firmware links) make sure you know if your's is maguro or toro, then download the respective firmware and flash it via ToolKit.
Click to expand...
Click to collapse
how do I check whether mine's maguro or toro?
RoyJ said:
Did you try going into Settings > Apps > All Applications > Google Services Framework & Clear cache / Clear data? Sometimes doing that will make it work. Try that. Don't use a toolkit...
Click to expand...
Click to collapse
tried that doesn't work. What's wrong with a toolkit? Everybody's telling me not to use it...
thephantom said:
Based on the screen shot, it's gsm but build number isn't there. What build is the Op on? So far it's only yakju/takju, yakjuxw, yakjuxe, and yakjuzs that have jb so if he's on a different build and really want jb, then he needs to flash but if he can wait, then he has to wait still
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Here. Trying my best not to root or whatever for now. Stock for now!
Sent from my Galaxy Nexus using xda app-developers app
Seems to be a yakjuxw from the new screen shot. Since you have gsm, it's maguro. You should be getting the jb update already
Sent from my Nexus 7 using Tapatalk 2
JC0406 said:
how do I check whether mine's maguro or toro?
tried that doesn't work. What's wrong with a toolkit? Everybody's telling me not to use it...
Here. Trying my best not to root or whatever for now. Stock for now!
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
You don't need to root it to load the factory image from Google. You only need the bootloader unlocked and you can do it through fastboot. Really very simple That's your best bet. As far as the first toolkit, I don't think there's any harm in using it specially if you're just going to use it to flash the factory image and unlock bootloader.
Try going to menu, options, applications, scroll over to all applications and clear data on Google services framework, Then go to about phone, system updates. That's what I did for the ota jb.
Sent from my Galaxy Nexus using xda app-developers app
rock7632 said:
You don't need to root it to load the factory image from Google. You only need the bootloader unlocked and you can do it through fastboot. Really very simple That's your best bet. As far as the first toolkit, I don't think there's any harm in using it specially if you're just going to use it to flash the factory image and unlock bootloader.
Click to expand...
Click to collapse
Hmm okay thanks. That will void the warranty won't it? Is there a thread about it already in the development thread?
evostevo1 said:
Try going to menu, options, applications, scroll over to all applications and clear data on Google services framework, Then go to about phone, system updates. That's what I did for the ota jb.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Tried that already. Doesn't work.
Sent from my Galaxy Nexus using xda app-developers app
Do check out the threads made by efrant so you can see the processes for it. They're very simple and you'll learn a lot as well.
Sent from my Galaxy Nexus using Tapatalk 2
JC0406 said:
Hmm okay thanks. That will void the warranty won't it? Is there a thread about it already in the development thread?
Click to expand...
Click to collapse
Not really. If you want to claim warranty, you can always lock the bootloader. And just use the toolkit from the thread in the development section. Remember you only have to do 2 things, unlock bootloader and flash factory image for 4.1.2.
zephiK said:
Don't use a toolkit. Learn how to unlock bootloader and fastboot on your own as it is better than having it spoon fed
Click to expand...
Click to collapse
I would agree with you completely. But I feel you're going to spend more time explaining it to someone who would rather take the easier way out than do all that. Yesterday had to explain to a 40 year old, father of two what adb was that I felt he was probably not ready to start sipping from the advanced user's method. I spent an hour trying to explain everything, what more if there was no toolbox?
Sent from my Galaxy Nexus using Tapatalk 2
Misledz said:
I would agree with you completely. But I feel you're going to spend more time explaining it to someone who would rather take the easier way out than do all that. Yesterday had to explain to a 40 year old, father of two what adb was that I felt he was probably not ready to start sipping from the advanced user's method. I spent an hour trying to explain everything, what more if there was no toolbox?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I agree with you, but if there is no toolkit, it won't be like this, people will have to learn adb and fastboot. Forces the newbs to learn adb and fastboot.
Well since it seem like he only look at posts recommending toolkits, his on you guys...............
And yes, wrong section, questions goes to the Q&A section.
Beamed from my Grouper.
Hi,
I have GNex for about 2 months now so I decided to root it. I did it ok and everything worked fine. But than
I decided to install custom kernel so I did it. Well after that I cant boot my Nexus, its stuck at its first boot animation
with white Google in a middle and little lock in a bottom. Only thing I can do is go to bootloader and acces recovery mod.
I tried to do pretty much everything in a recovery menu but its still not booting.
What can I do to restore stock rom with stock kernel or I dont know what can helps here. Pleas I will be realy greatful I am
a little bit noob to this
Reflash your ROM if you have any on your SD card. Also you can use a toolkit and flash the factory image.
Sent from my Galaxy Nexus using Tapatalk 2
droidmakespwn said:
Reflash your ROM if you have any on your SD card. Also you can use a toolkit and flash the factory image.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
My internal storage is empty, no ROMs or any factory images on it.
toolkit is a good idea but I dont have turned on USB debugging, isnt that problem?
But I will try
I don't think it matters if you are flashing the stock image. You can also Odin in a worst case scenario thing.
Sent from my Galaxy Nexus using Tapatalk 2
SPyxOff said:
My internal storage is empty, no ROMs or any factory images on it.
toolkit is a good idea but I dont have turned on USB debugging, isnt that problem?
But I will try
Click to expand...
Click to collapse
good lord do not use a toolkit.
go back to stock: http://forum.xda-developers.com/showthread.php?t=1626895
there's instructions on how to root there as well.
droidmakespwn said:
I don't think it matters if you are flashing the stock image. You can also Odin in a worst case scenario thing.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thank you very much sir, you saved my life! :good::good::good::good::laugh:
I am in your debt for sure!
GNexus fully working and prepared for rooting again, now without any other stupid activity around it
Zepius said:
good lord do not use a toolkit.
go back to stock: http://forum.xda-developers.com/showthread.php?t=1626895
there's instructions on how to root there as well.
Click to expand...
Click to collapse
I understand the hatred for toolkits because it causes complacency but its extremely easy to fix a device using it. Everyone should know how to use adb but I have used both and they both have worked perfectly for me.
Sent from my Galaxy Nexus using Tapatalk 2
droidmakespwn said:
I understand the hatred for toolkits because it causes complacency but its extremely easy to fix a device using it. Everyone should know how to use adb but I have used both and they both have worked perfectly for me.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
im sorry, but if you think typing a few commands in to flash the stock images is hard, you really are lazy.
I never said it was hard. What is your major grief with toolkits? How is using a toolkit any different than flashing someone else's ROM? You can compile it yourself but its much more efficient to just flash and go. This will be my last response unless the OP has any more issues he needs help with. Good luck with fixing your phone no matter what method you would like to use.
Sent from my Galaxy Nexus using Tapatalk 2
droidmakespwn said:
I never said it was hard. What is your major grief with toolkits? How is using a toolkit any different than flashing someone else's ROM? You can compile it yourself but its much more efficient to just flash and go. This will be my last response unless the OP has any more issues he needs help with. Good luck with fixing your phone no matter what method you would like to use.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
because when the toolkit fails, it fails hard and then the user of said toolkit has no idea how to fix anything and posts threads on here saying "i bricked my phone and used such and such toolkit"
the people helping them have no idea where to even begin to try and troubleshoot the problem as you dont know the failure point. the toolkit just says "complete" or "done"
that is my major beef with toolkits.
SPyxOff said:
Hi,
I have GNex for about 2 months now so I decided to root it. I did it ok and everything worked fine. But than
I decided to install custom kernel so I did it. Well after that I cant boot my Nexus, its stuck at its first boot animation
with white Google in a middle and little lock in a bottom. Only thing I can do is go to bootloader and acces recovery mod.
I tried to do pretty much everything in a recovery menu but its still not booting.
What can I do to restore stock rom with stock kernel or I dont know what can helps here. Pleas I will be realy greatful I am
a little bit noob to this
Click to expand...
Click to collapse
bro. same problem here. wht can I do
nadun911 said:
bro. same problem here. wht can I do
Click to expand...
Click to collapse
You can read the thread instead of necrobumping.
Sent from my Nexus
I rooted my Gnex GSM yesterday using Nexus Root Toolkit. After doing this I found that my pull down menu lags annoyingly when I'm in an app. Does anyone have any idea what the problem could be. I've cleared my cache and dalvik cache as instructed by my friend. But that hasn't done anything to my phone really. Thanks:good:
First, post in the right section.
Superuser/root access has nothing to do with "lag".
a maguro wrote this.
beekay201 said:
First, post in the right section.
Superuser/root access has nothing to do with "lag".
a maguro wrote this.
Click to expand...
Click to collapse
what section would that be? I didn't see a rlevant section so I just posted in the general section. So how would one explain that before I rooted, my pull down menu was a smooth transition, and after rooting it isn't?
The Q&A section obviously since your asking a question.
Sent from my Galaxy Nexus using xda premium
And now comes that part: OP, are you using superuser or supersu?
a manta wrote this.
beekay201 said:
And now comes that part: OP, are you using superuser or supersu?
a manta wrote this.
Click to expand...
Click to collapse
wouldnt know, used a toolkit.
I'n using SuperSU. It is really annoying to see that when I use my pull down menu that it's not a smooth transition
I have same problem many times, than i wiped all even system and flash custom ROM. After few months and few flashing problem was back. So wipe all internal memory if you ask me. Install custom ROM. If you wipe all andcan`t boot phone use QtADB while in recovery to copy zip and gapps to your phone. Google it...
Alienns said:
I have same problem many times, than i wiped all even system and flash custom ROM. After few months and few flashing problem was back. So wipe all internal memory if you ask me. Install custom ROM. If you wipe all andcan`t boot phone use QtADB while in recovery to copy zip and gapps to your phone. Google it...
Click to expand...
Click to collapse
thanks but this process seems so long. there must be a direct thing that's affecting it
I flashed JDQ39 through fastboot, rooted it, I see no such lag.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
beekay201 said:
I flashed JDQ39 through fastboot, rooted it, I see no such lag.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yeah, I flashed that too and rerooted. Still there, but it's less frequent. I'll see what happens
Tez_Nexus said:
Yeah, I flashed that too and rerooted. Still there, but it's less frequent. I'll see what happens
Click to expand...
Click to collapse
I guess the real question is what ROM you flashed and what Kernel is running.
Some ROM's run faster on Gnex than others.
Personally I have been running AOKP and XenonHD back and forth for some time and have a little lag here and there, but that is because I am able to add and change so much on the ROM. Sometimes changing the kernel helps as well.
At the end of the day it's all about what you are doing and what ROM/Kernel combination give you the user experience you like.
Sorry to say, what you are asking is more of an Art than an exact science when it comes to use and feel.