• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Galaxy Nexus Watering Hole

zx10droid said:
so now that i got that sorted out... just need to start reading and familiarize myself with rom flashing, or am i making this harder than it is and its as simple as going through "download rom" in rom manager and then "install rom" there as well
Click to expand...

you can download them from anywhere, doesn't have to be through rom manager. you can also flash them directly through CWM without using rom manager. just reboot into recovery wipe data/cache/dalvik, choose install .zip from SD, find your file (usually in the download folder), and load. easy as can be.
 
woodstorm said:
It's not a perma root yet. You have to flash clockwork via ROM Manager every time if you want to get to CWR otherwise it sends you to normal recovery. I did it too. lol
Click to expand...

For those having trouble with this I posted mskips guide from XDA a while back. It's really simple and thorough and explains all of it very well. I don't know if this applies to the method/s that some are using to unlock, root, cwm, but worth mentioning. His guide requires no SDK setup and takes about 15 minutes to complete. From his guide: IMPORTANT: There is an auto recovery restore system on Android that will reflash the Stock Recovery on a reboot if you flash CWM on a Stock Rom. If you plan on booting back into Android before entering CWM Recovery then you need to delete the file 'recovery-from-boot.p' from /system (mount /system as R/W first using Root Explorer or another app from the Market) BEFORE flashing CWM Recovery to stop it being overwritten.
 
woodstorm said:
Ya know, after going through this, I am starting to see why they lock bootloaders. lol
Click to expand...

i have rooted so many android devices that it all seems normal to me now. i remember the "scary moments" during my first few attempts, but seeing as how i will not do it until a stock image and solid recovery have been released, i know i can fix almost anything i mess up.

here is my list to date:
4 Motorola Droids
2 HTC Incredibles
1 Motorola Droid 2
2 Motorola Droid X's
1 Motorola Atrix
3 HTC Thunderbolts
1 Samsung Stratosphere
1 Samsung Galaxy Nexus
2 Viewsonic G-Tablets
5 B&N Nook Colors

:eek:
 
zx10droid said:
so now that i got that sorted out... just need to start reading and familiarize myself with rom flashing, or am i making this harder than it is and its as simple as going through "download rom" in rom manager and then "install rom" there as well
Click to expand...

It's simple really. I dislike using ROM manager for flashing ROMs. Some love it ymmv. When your ready to flash feel free to ask ;)
 
zx10droid said:
COMPLETELY agree about swiftkey being buggy. my favorite, most useful android purchase just isnt as nice as id like it to be yet :( i dont like that everytime i use something that requires the keyboard, a keyboard logo shows up in the notification bar either.
Click to expand...

I figured out what the keyboard logo is for. In Gingerbread and before you could long press on text entry to change input methods. With the keyboard in the notification bar you tap on it to change input.
 
jbdan said:
Android OS right? Idk what it's supposed to say but I'm basing my battery life on a days and nights use. I can make it through the day on my usage. This is stock battery.

I'm on auto bright too. Do we know if this is a known issue the Android os wrongly keeping the phone awake and using excess battery? I'm asking. : D
Click to expand...


Yes Android OS.

As to the question: I have read threads here and XDA which point this out.

Too lazy to link but it is being talked about.

The great news about having ICS and 4G LTE and a Nexus???

BEST OS EVER, 28 down and 19 up, Removable NFC enabled battery!

jmar
 
jmartino5920 said:
Yes Android OS.

As to the question: I have read threads here and XDA which point this out.

Too lazy to link but it is being talked about.

The great news about having ICS and 4G LTE and a Nexus???

BEST OS EVER, 28 down and 19 up, Removable NFC enabled battery!

jmar
Click to expand...

I've read it too didn't know if I had missed something. The Eris (yeah way back) had a dreaded sleep issue those that had it can relate. This is nothing like that from what I gather.

I'm with ya the speedtest are off the charts on 4g!

The thing that has really blown me away lately? The ability to multitask to my hearts content with the right capactive "apps running launcher". I can whiz in and out of all my forums and browser tabs with a quick touch! Amazing!
 
jbdan said:
For those having trouble with this I posted mskips guide from XDA a while back. It's really simple and thorough and explains all of it very well. I don't know if this applies to the method/s that some are using to unlock, root, cwm, but worth mentioning. His guide requires no SDK setup and takes about 15 minutes to complete. From his guide: IMPORTANT: There is an auto recovery restore system on Android that will reflash the Stock Recovery on a reboot if you flash CWM on a Stock Rom. If you plan on booting back into Android before entering CWM Recovery then you need to delete the file 'recovery-from-boot.p' from /system (mount /system as R/W first using Root Explorer or another app from the Market) BEFORE flashing CWM Recovery to stop it being overwritten.
Click to expand...

ok, so if i read this correctly i need to get root explorer(which i already have), fid the file mentioned and delete it? then flash cwm through rom manager again to make it stick?
 
zx10droid said:
ok, so if i read this correctly i need to get root explorer(which i already have), fid the file mentioned and delete it? then flash cwm through rom manager again to make it stick?
Click to expand...

If you used mskips guide 100% yes. If you used another method to unlock, root, flash cwm, I'd still say yes, but I'm not 100% because I have no idea how you rooted. You could have run a root method that deletes this automatically maybe? idk as I used mskips guide. See if that file is present with file explorer or root explorer :)
 
zx10droid said:
lol, ok, so im going to give a full rundown of what i have done in the order i did it to ensure it was correct...

1)installed all the sdk and correct drivers
2)got into fastboot and did oem unlock to unlock bootloader
3)downloaded the modaco superboot zip and put it inside my sdk tools under a folder i made(gnex superboot)
4)booted phone into fastboot using volume +- and power while plugged into cpu
5)double clicked file within the superboot file i downloaded called "install-superboot-windows.bat" , it automatically did everything from there
6)reboot phone and ensured superuser was there and indeed it was
7)downloaded ROM manager
8)opened rom manager and selected "flash clockworkmod recovery", and it now shows as 5.5.0.4 was the current and latest recovery
9)opened root explorer and renamed the recovery file to ***.bak
Click to expand...

here are the steps i took...

edit: instead of deleting the stock recovery, i read in a thread it as just as easy to rename it and leave it there, then i could easily delete the fake extension i added onto it if needed
 
zx10droid said:
instead of deleting the stock recovery, i read in a thread it as just as easy to rename it and leave it there, then i could easily delete the fake extension i added onto it if needed
Click to expand...

That is correct. Ok I see. So your still getting the stock recovery to come back issue?
 
jbdan said:
#9) ? What recovery file did you rename to .bak?

Did you check and see if that file 'recovery-from-boot.p' was there in /system?
Click to expand...

yes, it was there and instead of deleting it, i just added .bak to the end of the filename, as per what i read in another thread, ive since rebooted 3-4 times, and cwm comes up when selecting recovery so i guess its sticking now. cant say thanks enough for your help and patience, as well as everyone else who helped
 
zx10droid said:
yes, it was there and instead of deleting it, i just added .bak to the end of the filename, as per what i read in another thread, ive since rebooted 3-4 times, and cwm comes up when selecting recovery so i guess its sticking now
Click to expand...

Yup you should be good to go. And I love to help if I can, no problem ;)
 
I can't tell if my screen is defective or I'm just too used to my laptop's super bright screen... :( I should really go to a Verizon store and compare
 
zx10droid said:
yes, it was there and instead of deleting it, i just added .bak to the end of the filename, as per what i read in another thread, ive since rebooted 3-4 times, and cwm comes up when selecting recovery so i guess its sticking now. cant say thanks enough for your help and patience, as well as everyone else who helped
Click to expand...

i just did this for good measure as well. looks like we finally have a way to make CWM stick for everyone!
 
You must log in or register to reply here.
Back
Top Bottom