Related
I have an error updating with the OTA 4.0.2. GSM Galaxy Nexus.
I have only my phone rooted, and no Wallet installed or something. The error it's only that when the device restarts, it starts the installation, and then a "dead" Android appears with an exclamation sign on it. It fully block the device, and I have to put the battery out and restart.
I have tried so many times, each time OTA comes up.
Some help? Thank you.
Chaosblast said:
I have an error updating with the OTA 4.0.2. GSM Galaxy Nexus.
I have only my phone rooted, and no Wallet installed or something. The error it's only that when the device restarts, it starts the installation, and then a "dead" Android appears with an exclamation sign on it. It fully block the device, and I have to put the battery out and restart.
I have tried so many times, each time OTA comes up.
Some help? Thank you.
Click to expand...
Click to collapse
Are you sure you are not in standard recovery mode? When the droid appears: push Volume up+power and you should have the stock recovery mode...
Diger36 said:
Are you sure you are not in standard recovery mode? When the droid appears: push Volume up+power and you should have the stock recovery mode...
Click to expand...
Click to collapse
I'm sure. When the droid appears (I've attached the image) it doesn't respond to any button. I've tried V.up + Power, V.down + Power, and V.up+V.down+Power. Nothing happens.
I have ClockworkMod installed, version 5.5.0.2.
Chaosblast said:
I'm sure. When the droid appears (I've attached the image) it doesn't respond to any button. I've tried V.up + Power, V.down + Power, and V.up+V.down+Power. Nothing happens.
I have ClockworkMod installed, version 5.5.0.2.
Click to expand...
Click to collapse
Now that IS weird. The screenshot you took is indeed the screen you get in Stock Recovery and pressing Volume up + Power simultaniously should bring you into the recovery menu.
If not: I'm afraid this problem is over my head. Sorry about that... Maybe anyone else?
Chaosblast said:
I have an error updating with the OTA 4.0.2. GSM Galaxy Nexus.
I have only my phone rooted, and no Wallet installed or something. The error it's only that when the device restarts, it starts the installation, and then a "dead" Android appears with an exclamation sign on it. It fully block the device, and I have to put the battery out and restart.
I have tried so many times, each time OTA comes up.
Some help? Thank you.
Click to expand...
Click to collapse
You can use OTA updates when your phone is rooted. When you try to install the OTA update it looks for the stock bootlader. Because you have rooted the install wont complete when it gets to your modded bootloader.
The only way to update is put a 4.0.2 or 4.0.3 rom on your sd card and flash using CWM.
jd1001 said:
You can use OTA updates when your phone is rooted. When you try to install the OTA update it looks for the stock bootlader. Because you have rooted the install wont complete when it gets to your modded bootloader.
The only way to update is put a 4.0.2 or 4.0.3 rom on your sd card and flash using CWM.
Click to expand...
Click to collapse
Is that true? Even if you didn't install CWM, are on Stock recovery and all you did was unlock fastboot and root the phone? I guess then you should be able to install the OTA updates flawlessly or am I wrong?
jd1001 said:
You can use OTA updates when your phone is rooted. When you try to install the OTA update it looks for the stock bootlader. Because you have rooted the install wont complete when it gets to your modded bootloader.
The only way to update is put a 4.0.2 or 4.0.3 rom on your sd card and flash using CWM.
Click to expand...
Click to collapse
Unlocked bootloader doesn't prevent OTA updates.
---------- Post added at 08:47 AM ---------- Previous post was at 08:46 AM ----------
Diger36 said:
Is that true? Even if you didn't install CWM, are on Stock recovery and all you did was unlock fastboot and root the phone? I guess then you should be able to install the OTA updates flawlessly or am I wrong?
Click to expand...
Click to collapse
If all you did was unlock the bootloader and root and didn't install CWM recovery, different modem or anything else like that than you should be able to do the OTA.
jhuynh said:
Unlocked bootloader doesn't prevent OTA updates.
---------- Post added at 08:47 AM ---------- Previous post was at 08:46 AM ----------
If all you did was unlock the bootloader and root and didn't install CWM recovery, different modem or anything else like that than you should be able to do the OTA.
Click to expand...
Click to collapse
Oh ok I thought that was the issue! So it's when you install a custom recovery that the OTA updates won't work. Sorry for the incorrect info.
Having a custom recovery allows you to flash packages that are not signed by the same party as the ROM on your phone. What this means is that if you don't have a custom recovery, you can only install updates from your ROM signer. Pure yakju builds are released from Google. The other yakju derivatives are carrier and OEM releases.
AFAIK, only Google (yakju) has released the 4.0.2 update for GSM, so you can only install the update on yakju if you have a stock recovery. If you have a custom recovery you have the option to bypass the signature verification process...
danger-rat said:
Having a custom recovery allows you to flash packages that are not signed by the same party as the ROM on your phone. What this means is that if you don't have a custom recovery, you can only install updates from your ROM signer. Pure yakju builds are released from Google. The other yakju derivatives are carrier and OEM releases.
AFAIK, only Google (yakju) has released the 4.0.2 update for GSM, so you can only install the update on yakju if you have a stock recovery. If you have a custom recovery you have the option to bypass the signature verification process...
Click to expand...
Click to collapse
Thanks for that. I got bootloader and recovery mixed up!
Thanks all of you guys. That should be the problem. Then I delete the CWM and then update with the OTA. Then I reinstall the CWM and that should be fine.
It's weird because I my cousin has installed the OTA, and he had also rooted his Galaxy Nexus, and I think he also changed the recovery.
Anyway, it's good to know. Thanks again.
I don't think you understood me:
Having CWM let's you flash the update, but you may have to turn off signature verification to do so.
The problem is, the update has only been released for the yakju firmware, so if you want the update you probably want to make sure that you have the yakju firmware installed (use Android System Info or similar app).
It's possible that the update can be forced to flash on other non-yakju builds, but I can't say for sure...
danger-rat said:
I don't think you understood me:
Having CWM let's you flash the update, but you may have to turn off signature verification to do so.
The problem is, the update has only been released for the yakju firmware, so if you want the update you probably want to make sure that you have the yakju firmware installed (use Android System Info or similar app).
It's possible that the update can be forced to flash on other non-yakju builds, but I can't say for sure...
Click to expand...
Click to collapse
I don't want to flash any update via CWM for now. I prefer doing that by the official way until I see some ROM that I like.
I understand what you mean of the firmware. But I think I haven't changed the firmware. I mean, I have only unlocked the bootloader, rooted, and then installed CWM. I don't think that changes my firmware.
By the way, I have installed Android System Info, and checked it. But I don't know how to stay sure. I have attached the screenshot.
Thank you.
Understood.
Looks like you have yakju...
If you want the update to auto install, then yes, you will need the stock recovery.
Personally, I find it easier to flash the update manually than to switch recovery...
danger-rat said:
Understood.
Looks like you have yakju...
If you want the update to auto install, then yes, you will need the stock recovery.
Personally, I find it easier to flash the update manually than to switch recovery...
Click to expand...
Click to collapse
It's true, but where can I find the exact update (not the full ROM) in a zip package? I don't know how to get it from the OTA, and didn't find it on the forum either.
I want to be sure it's the correct update for my version and only the 4.0.1 to 4.0.2 package.
Bump! Could you answer my last question? It's the last one and all this thread is done.
Thank you.
I have exactly the same problem that Chaos, i tried to do the same as you told him but the problem persist, each time that i try to upgrade 4.04 by OTA it stopped and appair the android with the red exclamation on it.
I have the Nexus rooted and the stock recovery flashed
Hi guys, each time that I try to upgrade 4.04 by OTA, it stopped and appear the Android with the red exclamation on it.
I've used the 'WugFresh unlocked toolkit' to root/unlock Galaxy Nexus.
For install OTA 4.0.4 from Google, I need to lock the phone again?
If I back to default configs - using WugFresh again - the OTA, and after the root/unlock, work without problems?
Thanks.
That's the stock recovery you're seeing.
What images have you changed?
If you revert to the stock ones (radio/bootloader/etc) you should get the OTA.
Jubakuba said:
That's the stock recovery you're seeing.
What images have you changed?
If you revert to the stock ones (radio/bootloader/etc) you should get the OTA.
Click to expand...
Click to collapse
Why dont you show this guy the light and let him flash google factory image by himself..
OP: there you go http://forum.xda-developers.com/showthread.php?p=23229558
Galaxy Nexus AOKP m5 Franco kernel m3
Thank you, guys.
RaptorHawk said:
Hi guys, each time that I try to upgrade 4.04 by OTA, it stopped and appear the Android with the red exclamation on it.
I've used the 'WugFresh unlocked toolkit' to root/unlock Galaxy Nexus.
For install OTA 4.0.4 from Google, I need to lock the phone again?
If I back to default configs - using WugFresh again - the OTA, and after the root/unlock, work without problems?
Thanks.
Click to expand...
Click to collapse
You are seen that screen because you have something on your device that is not stock. (Unlocked and rooted makes no difference.)
To be 100% sure that an OTA update will install automatically, you need to have all of the following:
1) the radio that came with the ROM that you are using;
2) the stock recovery that came with the ROM that you are using;
3) the stock kernel that came with the ROM that you are using;
4) all of the original files in /system that came with the ROM that you are using.
Have a look at the thread here. It is for manual installation of an update, but the requirements still apply to an automatic update OTA.
So if I uninstalled apps to the system and do the lock/unroot, this will cause problems when I try to upgrade from version 4.0.2 to version 4.0.4?
I uninstalled Google Maps, Youtube and Earth.
RaptorHawk said:
So if I uninstalled apps to the system and do the lock/unroot, this will cause problems when I try to upgrade from version 4.0.2 to version 4.0.4?
I uninstalled Google Maps, Youtube and Earth.
Click to expand...
Click to collapse
You are not reading at all at what efrant says and you havent looked at the link i provided.. Until you do so you wont go farther
Galaxy Nexus AOKP m5 Franco kernel m3
Yes, I read, but maybe I did not quite understand ...
To recap: I used Wug's Toolkit and now I can no longer install the 4.0.4 update official Google OTA. So I would like to know how to undo it, install 4.0.4 and then apply the Wug toolkit again.
According to the links, I need to undo the changes before, but I can not undo the root by Wug's Toolkit, because he can not download a file, appear an error message that could not be found.
What I wonder is, how to get back to what it was prior to applying the 4.0.4 update and then do the root again? Is that possible?
Thanks.
Forget about toolkits, follow this guide please
http://forum.xda-developers.com/showthread.php?p=25477039
Galaxy Nexus AOKP m5 Franco kernel m3
RaptorHawk said:
Yes, I read, but maybe I did not quite understand ...
To recap: I used Wug's Toolkit and now I can no longer install the 4.0.4 update official Google OTA. So I would like to know how to undo it, install 4.0.4 and then apply the Wug toolkit again.
According to the links, I need to undo the changes before, but I can not undo the root by Wug's Toolkit, because he can not download a file, appear an error message that could not be found.
What I wonder is, how to get back to what it was prior to applying the 4.0.4 update and then do the root again? Is that possible?
Thanks.
Click to expand...
Click to collapse
There are two ways to get 4.0.4:
1) Flash a full 4.0.4 ROM, which is what the link msedek posted is.
2) Upgrade 4.0.2 to 4.04, which is the link I posted a couple of posts back.
In the first case, you easily end up with a clean install, but your data is erased (so back up before)
In the second case, you need to make sure that you undo any modifications you made to the /system partition, the kernel, the radio, and the recovery. Then you apply the update, and you will have an upgraded ROM with all your data and settings intact.
RaptorHawk said:
So if I uninstalled apps to the system and do the lock/unroot, this will cause problems when I try to upgrade from version 4.0.2 to version 4.0.4?
I uninstalled Google Maps, Youtube and Earth.
Click to expand...
Click to collapse
Actually, this is true. I was having the same issues. When i rooted, I deleted system apps I did not want. For weeks and weeks I kept receiving the popup message saying that the update to 4.0.4 was available. When attempting to upgrade, it would always fail on reboot.
Just two days ago, I received the upgrade notice again. I immediately went into Recovery mode, and attempted to manually install the update file from the system directory. When I did, I received an error right away saying the update could not find "TabletBooks.apk" (I deleted Google Play Books since I dont use it).
I reinstalled a clean image of 4.0.2 I made with ROM Manager weeks ago, then applied the update to 4.0.4 again, and it ran smoothly with no errors, since all System apps were installed with the clean image I saved.
Hope this helps...
PaisanNYC said:
Actually, this is true. I was having the same issues. When i rooted, I deleted system apps I did not want. For weeks and weeks I kept receiving the popup message saying that the update to 4.0.4 was available. When attempting to upgrade, it would always fail on reboot.
Just two days ago, I received the upgrade notice again. I immediately went into Recovery mode, and attempted to manually install the update file from the system directory. When I did, I received an error right away saying the update could not find "TabletBooks.apk" (I deleted Google Play Books since I dont use it).
I reinstalled a clean image of 4.0.2 I made with ROM Manager weeks ago, then applied the update to 4.0.4 again, and it ran smoothly with no errors, since all System apps were installed with the clean image I saved.
Hope this helps...
Click to expand...
Click to collapse
If you are going to install a clean image anyway, it doesn't make much sense to install 4.0.2 and upgrade to 4.0.4. Just install the 4.0.4 image immediately...
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
If you are going to install a clean image anyway, it doesn't make much sense to install 4.0.2 and upgrade to 4.0.4. Just install the 4.0.4 image immediately...
Click to expand...
Click to collapse
Because you cant just download the full 4.0.4 image and install it via Recovery, can you? I thought you can only install the full image via ADB?
I was able to do all of this while sitting down in the lil boys room, doing my business LOL
PaisanNYC said:
Because you cant just download the full 4.0.4 image and install it via Recovery, can you? I thought you can only install the full image via ADB?
I was able to do all of this while sitting down in the lil boys room, doing my business LOL
Click to expand...
Click to collapse
LOL!
Well, I'm not sure where you got a stock 4.0.2 CWM-flashable file, but FYI, you can flash 4.0.4 the same way if you have a 4.0.4 CWM-flashable file (or just replace the 4.0.2 image with the 4.0.4 image in the same CWM-flashable file.
efrant said:
LOL!
Well, I'm not sure where you got a stock 4.0.2 CWM-flashable file, but FYI, you can flash 4.0.4 the same way if you have a 4.0.4 CWM-flashable file (or just replace the 4.0.2 image with the 4.0.4 image in the same CWM-flashable file.
Click to expand...
Click to collapse
Thanks, that's good to know! I come from HTC phones (G1, Nexus One, etc), so Samsung and modding is kinda new to me.
I had a CWM-flashable 4.0.2 file because ROM Manager created the image for me when I first rooted and wanted a backup of a clean stock ROM. I wouldnt even know where to find a CWM-flashable 4.0.4 file on the web. I only know of the stock source files Google has posted. I read that those files can only be flashed with ADB on a PC.
Thanks again!
PaisanNYC said:
Thanks, that's good to know! I come from HTC phones (G1, Nexus One, etc), so Samsung and modding is kinda new to me.
I had a CWM-flashable 4.0.2 file because ROM Manager created the image for me when I first rooted and wanted a backup of a clean stock ROM. I wouldnt even know where to find a CWM-flashable 4.0.4 file on the web. I only know of the stock source files Google has posted. I read that those files can only be flashed with ADB on a PC.
Thanks again!
Click to expand...
Click to collapse
Oh, you were referring to a CWM backup. I understand now.
But regardless, you can still flash the Google images via CWM, they just have to be packaged up in a CWM-flashable zip.
Sent from my Galaxy Nexus using Tapatalk 2
Thanks for all help. I'm succesfull flash my GNex.
Hello Guys
To start off , i was on YAKJUUX version on 4.0.1 ICS stock
i converted my YAKJUUX in to YAKJU using this http://forum.xda-developers.com/showthread.php?t=1626895
Now i am running YAKJU version 4.0.4 IMM76I
while doing this backed up my 4.0.1 by using Clockwork Mod.
I took 2 backups namely one of the stock 4.0.1 before updating and one after of 4.0.4 after updating
Question: How do i restore to the versions that i backed up if i want to ?
After this
I tried to update to Jelly bean 4.1.1 yakju JRO03C from IMM76I using this link http://forum.xda-developers.com/showthread.php?t=1419170
After following the thread meticulously, the Recovery mode only shows an Android with open stomach and a red exclamation mark !
Then i tried to use my brain (which i regret) i used command prompt to Boot CWM: fastboot boot recovery-clockwork-5.5.0.2-maguro.img and then tried to flash that .zip file ( yakju JRO03C from IMM76I: http://android.clients.google.com/p....signed-yakju-JRO03C-from-IMM76I.f946a412.zip )
It didnt work .. the adnroid said " INSTALLATION ABORTED" so i cut my losses and here i am querying you guys !
NOW I DONT KNOW WHAT TO DO ! ... ANY SUGGESTIONS?
PS : I WANT JELLY BEAN and dont want to go to a candy shop !
My phone originally came with Yakjuux, lovely right?
My question is, why would you want to restore to it?
I highly advise you to pick up the GNex Tool Kit by mskip, set it up, and reflash stock 4.0.4 yakju.
It's very simple, and easy to use. If you are not sure, read tutorials! Take your time!
You will be prompt with a Jelly Bean OTA soon after you complete this. You need FULL STOCK for the official update to work.
Hence: Reflash Stock.
Assuming you backed up by going in to clockworkmod, then choosing "backup", simply go back in to CWM and choose "restore" (I think the option is actually called "backup/restore"
You obviously need your backup folder on your phone to do this.
DevilishSerpent said:
My phone originally came with Yakjuux, lovely right?
My question is, why would you want to restore to it?
I highly advise you to pick up the GNex Tool Kit by mskip, set it up, and reflash stock 4.0.4 yakju.
It's very simple, and easy to use. If you are not sure, read tutorials! Take your time!
You will be prompt with a Jelly Bean OTA soon after you complete this. You need FULL STOCK for the official update to work.
Hence: Reflash Stock.
Click to expand...
Click to collapse
To answer your first question, i would intend to restore to the previous version if the current builds for Jelly Bean are not stable... just want to have security to go back to in case something goes wrong.
.
I really dont want to root my phone as i use this for official purposes .. so unlocking the bootloader is the farthest i can go..
in my current situation would i be getting an OTA on to my device? if yes then would it be able to be installed with no issues?
Matt08642 said:
Assuming you backed up by going in to clockworkmod, then choosing "backup", simply go back in to CWM and choose "restore" (I think the option is actually called "backup/restore"
You obviously need your backup folder on your phone to do this.
Click to expand...
Click to collapse
Well i copied the back up on to a separate USB and i am trying to restore it back on to my phone again.
TO do that , i have to copy in to the phones` SD ... its not letting me do that !
any idea how i can get around that?
Also, How do i put in Jelly Bean?
dushrox said:
To answer your first question, i would intend to restore to the previous version if the current builds for Jelly Bean are not stable... just want to have security to go back to in case something goes wrong.
.
I really dont want to root my phone as i use this for official purposes .. so unlocking the bootloader is the farthest i can go..
in my current situation would i be getting an OTA on to my device? if yes then would it be able to be installed with no issues?
Click to expand...
Click to collapse
You do not need to root your phone to reflash to 4.0.4 Yakju via Tool Kit. All you need to do is unlock your bootloader, flash, lock bootloader.
You can back up Yakju 4.0.4, then update to JB. No root is required. Requires 3 minutes of your time, at most. There will be no issues if installed properly.
DevilishSerpent said:
You do not need to root your phone to reflash to 4.0.4 Yakju via Tool Kit. All you need to do is unlock your bootloader, flash, lock bootloader.
You can back up Yakju 4.0.4, then update to JB. No root is required. There will be no issues if installed properly.
Click to expand...
Click to collapse
Roger
I`ll get on it and keep u updated .. Thanks
dushrox said:
Roger
I`ll get on it and keep u updated .. Thanks
Click to expand...
Click to collapse
No problem. If you run into any issues you can send me a message and I will walk you through.
Hi all...
After scouring the Q&A forum and following directions for the remedies I've found I still have no luck getting the OTA to install correctly. I know you've all heard it a million times already - OTA downloads and verifies then I get red exclamation man down DROID a third of the way through the install.
I've used Wug's toolkit to flash back to stock and all that.
Before using the toolkit I was already stock but I had unlocked my bootloader to get from 4.0.1 yakjuxw or whatever to 4.0.4 yakju.
So since then I've re locked the bootloader and am still stock and not sure what the hell to do. Pleeease help!
At this point I just want to make it so I can get OTAs with no issue. I don't need root right now but will probably do it in the future for CM10.
Here's what my about reads:
Galaxy Nexus 4.0.4
Baseband version: I9250XXKK6
Kernal version: 3.0.8-gda6252b
Build number IMM76I
I apologize in advance for any noob questions.
Thanks!
You have the wrong radio to accept the normal 4.0.4 OTA for yakju devices. You need to flash XXLA2, which also requires your bootloader be unlocked.
Also, for future reference, the bootloader can be unlocked and you can still retrieve and auto-install OTAs just fine. OTA's don't care about your bootloader unlock status. I wouldn't recommend relocking your bootloader if you ever intend to change your phone in any way in the future, as you'll just have to unlock it again.
martonikaj said:
You have the wrong radio to accept the normal 4.0.4 OTA for yakju devices. You need to flash XXLA2, which also requires your bootloader be unlocked.
Also, for future reference, the bootloader can be unlocked and you can still retrieve and auto-install OTAs just fine. OTA's don't care about your bootloader unlock status. I wouldn't recommend relocking your bootloader if you ever intend to change your phone in any way in the future, as you'll just have to unlock it again.
Click to expand...
Click to collapse
Thanks for the reply!
Please correct me if I'm wrong...
So I can use Wug's to unlock my bootloader again but it'll wipe the phone?
And the radio I can find and download somewhere then I flash through Wug's somehow also?
I really appreciate the help
RiG14LA said:
Thanks for the reply!
Please correct me if I'm wrong...
So I can use Wug's to unlock my bootloader again but it'll wipe the phone?
And the radio I can find and download somewhere then I flash through Wug's somehow also?
I really appreciate the help
Click to expand...
Click to collapse
Yes unlocking the bootloader will wipe your device again.
Don't use the toolkit. Flash it via fastboot. You can download the 4.0.4 images from Google and extract the radio, or find it from one of the radio aggregator threads.
Use this thread with step by step instructions: http://forum.xda-developers.com/showthread.php?t=1626895
You'll need Part D, step 7 to flash the radio.
martonikaj said:
Yes unlocking the bootloader will wipe your device again.
Don't use the toolkit. Flash it via fastboot. You can download the 4.0.4 images from Google and extract the radio, or find it from one of the radio aggregator threads.
Use this thread with step by step instructions: http://forum.xda-developers.com/showthread.php?t=1626895
You'll need Part D, step 7 to flash the radio.
Click to expand...
Click to collapse
Alrighty...
I will give it a shot tomorrow!
Thanks again for the guidance.
I kept getting errors about my ICS (specifically, gps.conf) not being stock when I tried to install the OTA via CWM, and nothing I did would solve it.
You could extract the radio and flash it as above (though better way is to just google xxla2 radio file), and if that still doesn't work, do what I did.
The easy way is to just download the factory image, open the compressed file, and drag out system.img. All i did was flash over system.img, essentially replacing system files but keeping all your current data. Kind of like restoring Android OS to the way it's supposed to be.
martonikaj said:
Yes unlocking the bootloader will wipe your device again.
Don't use the toolkit. Flash it via fastboot. You can download the 4.0.4 images from Google and extract the radio, or find it from one of the radio aggregator threads.
Use this thread with step by step instructions: http://forum.xda-developers.com/showthread.php?t=1626895
You'll need Part D, step 7 to flash the radio.
Click to expand...
Click to collapse
I can't get fast boot to work.
It won't show that it recognizes my nexus when I type in fastboot devices.
Are you available on Google chat to help?
fixed my issue by using instructions i found on dottech.org. i'd post the link but i can't yet. you are welcome to PM me if you think it would help you.
thanks again for everyone's help.
i ran the OTA without a hitch.
so am i correct in assuming that i will now be able to run all future OTAs without an issue?
RiG14LA said:
fixed my issue by using instructions i found on dottech.org. i'd post the link but i can't yet. you are welcome to PM me if you think it would help you.
thanks again for everyone's help.
i ran the OTA without a hitch.
so am i correct in assuming that i will now be able to run all future OTAs without an issue?
Click to expand...
Click to collapse
assuming you do not modify any system files or change radios/kernels, then yes you would get all OTAs fine.
Hello all,
Just did an OTA update to JRO03O after unrooting and relocking my phone. Then went to Root Toolkit 1.5.3 to root and unlock the new ROM but the only option there was JRO03H to select for my Verizon phone. Can I select this "H" version (or the last choice, which is MYSID-TORO;Android*.*) to root and unlock it? Or must I wait for my specific build to appear?
Do you use fastboot? I avoid toolkits like the plague because you learn nothing from them. Try using fastboot to flash a custom recovery(CWM or TWRP), then just flash the latest superuser zip from clockworkmod.
Edit: don't quote me though, the only time I've ever been stock is the first 30 minutes owning my Gnex. I just bypass the rooting process by flashing a custom ROM.
~~~~There is no spoon~~~~
shag_on_e said:
Do you use fastboot? I avoid toolkits like the plague because you learn nothing from them. Try using fastboot to flash a custom recovery(CWM or TWRP), then just flash the latest superuser zip from clockworkmod.
~~~~There is no spoon~~~~
Click to expand...
Click to collapse
hmm never really used anything but toolkits, could you point me to a tutorial on how to do the fastboot / superuser? I thought that you'd need to be rooted before you could install a custom recovery / superuser on your phone. I also thought that on any phone that you have to unlock the bootloader before doing anything with recovery as well. could you or someone enlighten me?
thanks!
Shukero
Here ya go, this is the tutorial I used in the beginning, still gold to this day. And you don't have to be rooted to flash a recovery from the bootloader, boot straight to recovery, then flash a custom ROM. No root needed. The bootloader does need to be unlocked first though but there's nothing to it. Just follow this guide.
http://wiki.rootzwiki.com/Samsung_Galaxy_Nexus_(toro)#IMM76K
~~~~There is no spoon~~~~
A little off topic, but is JRO03O the OTA version? I haven't taken it yet, but the most recent AOSP branch is for JRO03R, which comes after O
yes the ota is jro03o
Read forum rules before posting
This is not development
Thread moved
javroch said:
A little off topic, but is JRO03O the OTA version? I haven't taken it yet, but the most recent AOSP branch is for JRO03R, which comes after O
Click to expand...
Click to collapse
for gsm, yes, it's JRO03R
sent from my i9250