Develop Bugs

Issues Updating OS Versions

Hello all, I am still fairly new to the root/Android scene and I've run into a problem.
Firstly, my Nexus' bootloader is unlocked and I'm running and older Franco.Kernel (4.0.1 and 1.4GHZ OC). Now, the problem is, my phone has notified me that a newer OS version is available. When I go to install it, the phone reboots but right after - the little Droid appears with a red caution sign and the phone stays that way until the battery is pulled.
What am I missing here? Any help is greatly appreciated.
P.S. I'm a n00b.

Try relocking bootloader then installing update. And then unlock again.
Sent from my Galaxy Nexus using Tapatalk

anton2009 said:
Try relocking bootloader then installing update. And then unlock again.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
No... He's not going to be able to update just because he locked the bootloader.
---------- Post added at 08:46 PM ---------- Previous post was at 08:45 PM ----------
Redefined81 said:
Hello all, I am still fairly new to the root/Android scene and I've run into a problem.
Firstly, my Nexus' bootloader is unlocked and I'm running and older Franco.Kernel (4.0.1 and 1.4GHZ OC). Now, the problem is, my phone has notified me that a newer OS version is available. When I go to install it, the phone reboots but right after - the little Droid appears with a red caution sign and the phone stays that way until the battery is pulled.
What am I missing here? Any help is greatly appreciated.
P.S. I'm a n00b.
Click to expand...
Click to collapse
In order to properly take an OTA and have it install you're going to have to be on the stock ROM, recovery, radios, everything. You can be unlocked and rooted, but you can't have changed anything else. Because you've flashed another kernel, you're probably going to have to flash the update manually.

heifica 798.
martonikaj said:
No... He's not going to be able to update just because he locked the bootloader.
---------- Post added at 08:46 PM ---------- Previous post was at 08:45 PM ----------
In order to properly take an OTA and have it install you're going to have to be on the stock ROM, recovery, radios, everything. You can be unlocked and rooted, but you can't have changed anything else. Because you've flashed another kernel, you're probably going to have to flash the update manually.
Click to expand...
Click to collapse
Thanks! How and where would I go about doing this?
Sorry, but remember, I'm still really new to all of this.

Redefined81 said:
Thanks! How and where would I go about doing this?
Sorry, but remember, I'm still really new to all of this.
Click to expand...
Click to collapse
I'd pass that question to someone more knowledgeable than I on the subject. I wouldn't wanna give you improper guidance. Not sure how your custom kernel comes in to play when flashing.
All I know is you won't be able to take the regular OTA in your current state.

Here is your info on how to get back to stock.
http://forum.xda-developers.com/showthread.php?t=1366806

El Daddy said:
Here is your info on how to get back to stock.
http://forum.xda-developers.com/showthread.php?t=1366806
Click to expand...
Click to collapse
Is this going to un-root and/or lock my bootloader again?

You should have learned how to go back to stock before flashing anything...

El Daddy said:
Here is your info on how to get back to stock.
http://forum.xda-developers.com/showthread.php?t=1366806
Click to expand...
Click to collapse
That is overkill. Just go here: http://code.google.com/android/nexus/images.html and download the version of Android you are using. Extract the boot.img file from within, and flash that with fastboot. Now you are back to the stock kernel, and the update will install automatically (assuming of course that you did not make other changes).
EDIT: You will not lose root, your bootloader will still be unlocked, and all of your data/settings will still be there.

efrant said:
That is overkill. Just go here: http://code.google.com/android/nexus/images.html and download the version of Android you are using. Extract the boot.img file from within, and flash that with fastboot. Now you are back to the stock kernel, and the update will install automatically (assuming of course that you did not make other changes).
EDIT: You will not lose root, your bootloader will still be unlocked, and all of your data/settings will still be there.
Click to expand...
Click to collapse
Thank you so much!
I know I may seem a tad annoying, but I just don't want to mess up my phone, lol!
How do I go about installing this?
I DL Fastboot & it's drivers. Extract the IMG (just so you know, I'm currently yakjuxx, not yakju - does that matter?) to the same directory as Fastboot then enter my phone into Fastboot mode. The thing is, I'm unfamiliar with the command prompts to get it going. I'll be doing it on Windows 7. Help would be appreciated!.
I know I've asked a lot, and I thank you.

Redefined81 said:
Thank you so much!
I know I may seem a tad annoying, but I just don't want to mess up my phone, lol!
How do I go about installing this?
I DL Fastboot & it's drivers. Extract the IMG (just so you know, I'm currently yakjuxx, not yakju - does that matter?) to the same directory as Fastboot then enter my phone into Fastboot mode. The thing is, I'm unfamiliar with the command prompts to get it going. I'll be doing it on Windows 7. Help would be appreciated!.
I know I've asked a lot, and I thank you.
Click to expand...
Click to collapse
I'm not sure it matters if you are yakju or yakjuux (as I think all the stock GSM kernels for ITFL41F are the same), but just to be sure, go here and download my nandroid back up of yakjuux ITL41F. In the archive, you will find a boot.img file (which is the file you need). Extract it.
All you have to do it put the boot.img file in the same directory as your fastboot.exe file, reboot your device into fastboot mode, and plug it into your PC. Open a command prompt in that directory and type fastboot devices to make sure you PC recognizes your device. Then type fastboot flash boot boot.img
Done.
Now, obviously this assumes that you already have the drivers set up properly...

efrant said:
I'm not sure it matters if you are yakju or yakjuux (as I think all the stock GSM kernels for ITFL41F are the same), but just to be sure, go here and download my nandroid back up of yakjuux ITL41F. In the archive, you will find a boot.img file (which is the file you need). Extract it.
All you have to do it put the boot.img file in the same directory as your fastboot.exe file, reboot your device into fastboot mode, and plug it into your PC. Open a command prompt in that directory and type fastboot devices to make sure you PC recognizes your device. Then type fastboot flash boot boot.img
Done.
Now, obviously this assumes that you already have the drivers set up properly...
Click to expand...
Click to collapse
Fastboot can flash boot.imgs, awesome, I likely would've been a muppet and made a CWM zip. I learn something new that I love about my GN every day.

mudferret said:
Fastboot can flash boot.imgs, awesome, I likely would've been a muppet and made a CWM zip. I learn something new that I love about my GN every day.
Click to expand...
Click to collapse
The "fastboot flash" command is specifically for flashing full images to partitions on the device, e.g., system, userdata, boot, recovery, bootloader, radio, splash1, etc.

Bootloader dumping?

Hi Everyone,
I'm about to install the new PRIMELA03 bootloader but want to retain a backup of my existing bootloader (PRIMEKK14). Unfortunately, there isn't a downloadable image of PRIMEKK14 anywhere on these forums, so I was wondering if anyone has experience with dumping an existing bootloader? ...Unfortunately, there isn't too much information on this topic either.
Thanks!

EDIT: Never mind.

theSpam said:
Hi Everyone,
I'm about to install the new PRIMELA03 bootloader but want to retain a backup of my existing bootloader (PRIMEKK14). Unfortunately, there isn't a downloadable image of PRIMEKK14 anywhere on these forums, so I was wondering if anyone has experience with dumping an existing bootloader? ...Unfortunately, there isn't too much information on this topic either.
Thanks!
Click to expand...
Click to collapse
Why would you want to do that? You can just download the stock image from here:
https://dl.google.com/dl/android/aosp/yakju-icl53f-factory-89fccaac.tgz
Open the archive and there's your bootloader.

Diger36 said:
Why would you want to do that? You can just download the stock image from here:
https://dl.google.com/dl/android/aosp/yakju-icl53f-factory-89fccaac.tgz
Open the archive and there's your bootloader.
Click to expand...
Click to collapse
Thanks for replying, but I had a look at your link and the bootloader included with that package is not PRIMEKK14. It is instead PRIMEKK15...

PRIMEKK15 is the bootloader that was bundled into the yakjuux (CDN units) 4.0.2 update, and it came shipped with my unit on 4.0.2. So if you are concerned in terms of warranty, KK15 should be good enough to revert to, as it's a bootloader your phone could have received by stock OTA update.

theSpam said:
Thanks for replying, but I had a look at your link and the bootloader included with that package is not PRIMEKK14. It is instead PRIMEKK15...
Click to expand...
Click to collapse
What version are you on and what ROM? Did you install it yourself? Is it a Google or a carrier image.
The bootloader is in the images. You can find all Google factory images here.
https://code.google.com/intl/nl-NL/android/nexus/images.html

Diger36 said:
What version are you on and what ROM? Did you install it yourself? Is it a Google or a carrier image.
The bootloader is in the images. You can find all Google factory images here.
https://code.google.com/intl/nl-NL/android/nexus/images.html
Click to expand...
Click to collapse
He is running a yakjuux build, not a yakju build. All the builds you linked to are yakju, not yakjuux, and the 14 bootloader did NOT come with any yakju build.
Sent from my Galaxy Nexus using Tapatalk

theSpam said:
Hi Everyone,
I'm about to install the new PRIMELA03 bootloader but want to retain a backup of my existing bootloader (PRIMEKK14). Unfortunately, there isn't a downloadable image of PRIMEKK14 anywhere on these forums, so I was wondering if anyone has experience with dumping an existing bootloader? ...Unfortunately, there isn't too much information on this topic either.
Thanks!
Click to expand...
Click to collapse
So I had a gander at the updater-script that updates the bootloader found in an OTA update file. It uses some sort of command to write the .img file to two partitions on the GN: xloader and sbl. If you really want to dump the KK14 bootloader, what you can do is dump those two partitions. This should allow you to replace those partitions at a later point. I would not be able to tell you how to make an image that is flashable in fastboot out of those two images.
To dump those partitions, plug your device into your computer, and open a command prompt in the same directory as your adb.exe file. Then type the following (you need root obviously):
adb shell
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/xloader of=/sdcard/xloader_raw.img
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/sbl of=/sdcard/sbl_raw.img
exit
exit
adb pull /sdcard/xloader_raw.img
adb pull /sdcard/sbl_raw.img
Now you have those two files on your computer as backup. I will try to do some more research to see how those two files roll up into a bootloader image.

If you find the thread with the yakjuux OTA update.zip to 4.0.2, that's where you can find KK15. Honestly I'd say that's good enough as a revert option because it's what you'd have had if you'd gotten the OTA to 4.0.2.
Sent from my Galaxy Nexus using Tapatalk

cmstlist said:
If you find the thread with the yakjuux OTA update.zip to 4.0.2, that's where you can find KK15. Honestly I'd say that's good enough as a revert option because it's what you'd have had if you'd gotten the OTA to 4.0.2.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Yeah, I agree. Unless there is something specific about having KK14 that he wants.

efrant said:
He is running a yakjuux build, not a yakju build. All the builds you linked to are yakju, not yakjuux, and the 14 bootloader did NOT come with any yakju build.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
That is exactly why I asked him what ROM or build he had since I know those are only yakju builds (it are the Google factory ones, duh), seems you already knew he was on yajkjuux. Glad you guys could help him out
Sent from my Galaxy Nexus using xda premium

cmstlist said:
PRIMEKK15 is the bootloader that was bundled into the yakjuux (CDN units) 4.0.2 update, and it came shipped with my unit on 4.0.2. So if you are concerned in terms of warranty, KK15 should be good enough to revert to, as it's a bootloader your phone could have received by stock OTA update.
Click to expand...
Click to collapse
There's nothing specific about KK14 that I want (I certainly don't have a warranty with my device). I just merely want a copy for my archival purposes.
efrant said:
So I had a gander at the updater-script that updates the bootloader found in an OTA update file. It uses some sort of command to write the .img file to two partitions on the GN: xloader and sbl. If you really want to dump the KK14 bootloader, what you can do is dump those two partitions. This should allow you to replace those partitions at a later point. I would not be able to tell you how to make an image that is flashable in fastboot out of those two images.
To dump those partitions, plug your device into your computer, and open a command prompt in the same directory as your adb.exe file. Then type the following (you need root obviously):
adb shell
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/xloader of=/sdcard/xloader_raw.img
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/sbl of=/sdcard/sbl_raw.img
exit
exit
adb pull /sdcard/xloader_raw.img
adb pull /sdcard/sbl_raw.img
Now you have those two files on your computer as backup. I will try to do some more research to see how those two files roll up into a bootloader image.
Click to expand...
Click to collapse
Thanks for the research Once I get a chance to pull the two partitions, I'll post them here.
As well, what OTA package did you examine for the above information?

theSpam said:
[snip]
As well, what OTA package did you examine for the above information?
Click to expand...
Click to collapse
I can't remember the specific one (prob yakju IMM76D from ICL53F), but any OTA package that has a bootloader inside will show you how it flashes it.
As for dumping, given that we know that the bootloader image is written somehow split between xloader and sbl, we know those are what we have to dump. The command dd will dump partitions, so that is what I used in my instructions above.
Sent from my Galaxy Nexus using Tapatalk

Double post.

[GUIDE]Factory Images (JB-ICS) [maguro][toro][toroplus]

Hello everyone,
i decide to write this guide and to collect all the future Factory Images for Galaxy Nexus (maguro [GSM/GSPA+], toro[VZW CDMA/LTE], toroplus[Sprint CDMA/LTE])
Once installed them you retourn 100% stock.
This is usefull in case you don't want to wait official OTA or you have to use warranty for some problem or you like a really clean install.
Since Android 4.0 IceCreamSandwich you can't install OTA via update.zip method in stock recovery because is no more possible. If you try via stock recovery you get "error status 7" (this problem is corrected only if you use ClockWorkMod Recovery).
Then is necessary to use Factory Image provided by Google.
Factory Images:​
JDQ39 Android 4.2.2 Factory Image "yakju" for Galaxy Nexus (maguro GSM/HSPA+)
MD5 Checksum 2fe041ac195086ef09274204c7e265e2
JZO54K Android 4.1.2 Factory Image "yakju" for Galaxy Nexus (maguro GSM/HSPA+)
MD5 Checksum cc710f1539765c6ab7fbb8f50b69f0d6
IMM76I Android 4.0.4 Factory Image "yakju" for Galaxy Nexus (maguro GSM/HSPA+)
MD5 Checksum 31447212fb4fb00aab4ef8bdc78e7ffb
JDQ39 Android 4.2.2 Factory Image "takju" for Galaxy Nexus (maguro GSM/HSPA+ with Google Wallet installed [notice, if you live outside US it simply disappears])*
MD5 Checksum 2fae8a6f50016e83f232fbb2d099fd42
JZO54K Android 4.1.2 Factory Image "takju" for Galaxy Nexus (maguro GSM/HSPA+ with Google Wallet installed [notice, if you live outside US it simply disappears])
MD5 Checksum 4e79a918a9a366166d0c23f99cc240db
IMM76I Android 4.0.4 Factory Image "takju" for Galaxy Nexus (maguro GSM/HSPA+ with Google Wallet installed [notice, if you live outside US it simply disappears])
MD5 Checksum 26ede55c44b503e4ab02969c22fa16e1
JRO03O Android 4.1.1 Factory Image "mysid" for Galaxy Nexus (toro VZW CDMA/LTE)
MD5 Checksum 1df6a2a7385c4745193fe82bf2a87f78
IMM76K Android 4.0.4 Factory Image "mysid" for Galaxy Nexus (toro VZW CDMA/LTE)
MD5 Checksum e76c6fe7d2bc799e5a6168f9dcb8c4ca
FH05 Android 4.1.1 Factory Image "mysidspr" for Galaxy Nexus (toroplus Sprint CDMA/LTE)
MD5 Checksum 7b3c4c37dd64a664427d3829e2491bee
NOTICE: If you have any GSM Galaxy Nexus (for example european version Yakjuxw, Yakjusc ecc... or other GSM version branded by Samsung) you can ALWAYS safely flash Yakju or Takju images provided by google, in order to get future OTA in time, directly from Google and not from Samsung)​
How to install:​
Requirements:
-Android SDK
-Java JDK
-Platform-Tools
-Unlocked bootloader ("fastboot oem unlock" pay attention, wipes everything, also your data)
-experience with adb and fastboot​
NOTICE: If you never used the sdk, the jdk, fastboot and adb, before installing the factory image YOU HAVE TO FOLLOW some guide here on XDA in order to get sdk and unlocked bootloader.
Now you can proceed to install the Factory Image
On Windows:​
1) copy the ecxtracted files (two times with 7zip) on android-sdk/platform-tools/ (this is important, if you dont unzip it, dont complain about "radio couldnt be loaded")
2) run a cmd and moves in "platform-tools" folder
3) write those command:
4A) If you are coming from a custom rom, this wipe your data/cache:
adb reboot bootloader
fastboot flash bootloader bootloader-maguro or toro or toroplus-********.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro or toro or toroplus-********.img
fastboot reboot-bootloader
fastboot -w update image-********.zip
if you want relock the bootloader (not necessary, only for warranty) do also these two step:
fastboot reboot-bootloader
fastboot oem lock
4B) If you are coming from another stock rom (official older OTA unrooted), this doen't wipe your data/cache:
adb reboot bootloader
fastboot flash bootloader bootloader-maguro or toro or toroplus-********.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro or toro or toroplus-********.img
fastboot reboot-bootloader
fastboot update image-********.zip
if you want relock the bootloader (not necessary, only for warranty) do also these two step:
fastboot reboot-bootloader
fastboot oem lock
On Linux, Mac:​
1) copy the ecxtracted files (two times with 7zip) on android-sdk/platform-tools/ (this is important, if you dont unzip it, dont complain about "radio couldnt be loaded")
2) run a terminal and moves in "platform-tools" folder
3) write those command:
chmod +x flash-all.sh
./flash-all.sh
"flash-all.sh" wipes your data (it contains fastboot -w update, if you want to remove/change it edit with notepad++)
"flash-base.sh" flashes only the bootloader and the radio.
NOTICE:
1) Instead of ******** you have to put the name of the files you download.
2) somebody is aking why "adb reboot bootloader" each passages. Is not essential, but some people think it is better because you use the updated bootloader, maybe is only a superstition.​
PLEASE LEAVE ME A THANKS ​
WARNING! DON'T DO THESE THING IF YOU DON'T KNOW WHAT YOU ARE DOING. I'M NOT RESPONSIBLE OF BRICKED GALAXY NEXUS OR SIMILAR​

While it is a nice guide there is one already and its a sticky
http://forum.xda-developers.com/showthread.php?t=1626895
Sent from my Galaxy Nexus using Tapatalk 2

In old guide on XDA you needed to unzip the main folder and unzip and unzip the image-takju-jro03c.zip file to to get the boot.img , userdata.img and so on and you flash everything manually
so my question is >> in the old guide when you use Fastboot flash userdata userdata.img << this will wipe everything on the sdcard so is this the case here ? because i can see that useing the command fastboot -w update image-takju-jro03c.zip can avoid erasing everything is that right?
and thanks of course for the great guide

D3VI0US said:
In old guide on XDA you needed to unzip the main folder and unzip and unzip the image-takju-jro03c.zip file to to get the boot.img , userdata.img and so on and you flash everything manually
so my question is >> in the old guide when you use Fastboot flash userdata userdata.img << this will wipe everything on the sdcard so is this the case here ? because i can see that useing the command fastboot -w update image-takju-jro03c.zip can avoid erasing everything is that right?
and thanks of course for the great guide
Click to expand...
Click to collapse
I never used this guide because is not "transparent", I mean, my passages are the one that Google suggest. That guide is good but there are lots of thing that are a plus and not only using Google factory image. This is the way to use them. The other guide is a plus for advanced users. When you type -w it erases your internal memory (data and apps, this is in theory, I always use stock ROM than I never wiped with fast boot, maybe copy your SD on PC to prevent damage) bye
Sent from my Galaxy Nexus using xda premium

Not quite sure how your guide is more transparent or for beginners than efrant's is...
I followed his numerous times with no issues.
Its one thing to provide an alternative guide for those who wish to use it, it's another to knock someone elses work..

What's the difference with enfant's guide because I've been using his for the longest time. Is the command update image-xxxxxxx.zip recommended by Google? It's much shorter than flashing all the files individually but I dunno.
Sent from my Galaxy Nexus using Tapatalk 2

prinzhernan said:
What's the difference with enfant's guide because I've been using his for the longest time. Is the command update image-xxxxxxx.zip recommended by Google? It's much shorter than flashing all the files individually but I dunno.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Use intuition. Why Google should have done an extra zip to extract when they created the command fast boot update? Why complicate things when they are simple? If you exclude reboot commands you need only 3 commands with same effect!
Sent from my Galaxy Nexus using xda premium

ale.landra91 said:
I never used this guide because is not "transparent", I mean, my passages are the one that Google suggest. That guide is good but there are lots of thing that are a plus and not only using Google factory image. This is the way to use them. The other guide is a plus for advanced users. When you type -w it erases your internal memory (data and apps, this is in theory, I always use stock ROM than I never wiped with fast boot, maybe copy your SD on PC to prevent damage) bye
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Not sure what you mean by "not only using Google factory image". Everything I mention in that guide is from Google, except the driver (which is originally from Samsung, but repackaged by 1wayjonny).
prinzhernan said:
What's the difference with enfant's guide because I've been using his for the longest time. Is the command update image-xxxxxxx.zip recommended by Google? It's much shorter than flashing all the files individually but I dunno.
Click to expand...
Click to collapse
The difference between this and my guide is that I have included ALL the steps to flash stock, from installing the drivers and downloading any needed files (the SDK and JDK are not needed by the way) to flashing your device. Additionally, as is stated in the first post of my thread, I have expanded all the steps and eliminated all scripts, so that people can see what is actually happening for the purposes of learning. For example, executing one command which actually flashes four images behind the scenes is not as valuable to learning as executing each command individually.
Included in the factory image is a script that flashes everything at once. Do you learn anything from it? Not really. There is no difference between using the fastboot update command to flash a bunch of images in a zip file, and flashing each image with the fastboot flash command. The difference is for instructional purposes.

efrant said:
Not sure what you mean by "not only using Google factory image". Everything I mention in that guide is from Google, except the driver (which is originally from Samsung, but repackaged by 1wayjonny).
The difference between this and my guide is that I have included ALL the steps to flash stock, from installing the drivers and downloading any needed files (the SDK and JDK are not needed by the way) to flashing your device. Additionally, as is stated in the first post of my thread, I have expanded all the steps and eliminated all scripts, so that people can see what is actually happening for the purposes of learning. For example, executing one command which actually flashes four images behind the scenes is not as valuable to learning as executing each command individually.
Included in the factory image is a script that flashes everything at once. Do you learn anything from it? Not really. There is no difference between using the fastboot update command to flash a bunch of images in a zip file, and flashing each image with the fastboot flash command. The difference is for instructional purposes.
Click to expand...
Click to collapse
Which I believe is better for beginners...
But what do I know... OH WAIT... I used to be one.
Bottomline, use the one you want... or are more comfortable with.
One thing to remember however... if you end up screwing your device up... efrants procedure will pinpoint exactly where you went wrong or what step it caused issues at.

efrant said:
Not sure what you mean by "not only using Google factory image". Everything I mention in that guide is from Google, except the driver (which is originally from Samsung, but repackaged by 1wayjonny).
The difference between this and my guide is that I have included ALL the steps to flash stock, from installing the drivers and downloading any needed files (the SDK and JDK are not needed by the way) to flashing your device. Additionally, as is stated in the first post of my thread, I have expanded all the steps and eliminated all scripts, so that people can see what is actually happening for the purposes of learning. For example, executing one command which actually flashes four images behind the scenes is not as valuable to learning as executing each command individually.
Included in the factory image is a script that flashes everything at once. Do you learn anything from it? Not really. There is no difference between using the fastboot update command to flash a bunch of images in a zip file, and flashing each image with the fastboot flash command. The difference is for instructional purposes.
Click to expand...
Click to collapse
simply they are different guide. My intention was porting my nexus s guide to galaxy nexus and not writing a poem. Few passages to use the images in the correct and simplest way. Then users choose to use your or mine with same results I never said that you are wrong, is only an alternative of lot of ways

can anyone upload the 4.1.1 yakju factory image for the galaxy nexus on any site because google's links aren't working for me please help i need it so bad

jamil-m77 said:
can anyone upload the 4.1.1 yakju factory image for the galaxy nexus on any site because google's links aren't working for me please help i need it so bad
Click to expand...
Click to collapse
sorry i dont have it. Does it work now?

OP updated! Sorry for the delay

OP updated with new 4.1.2!

OP updated

Hi, can someone get me factory image for 4.1.1 maguro? In fact, stock recovery will do the trick. Does the build number matter if a want only stock recovery? Thanks

M4t3s said:
Hi, can someone get me factory image for 4.1.1 maguro? In fact, stock recovery will do the trick.
Click to expand...
Click to collapse
See here, courtesy of oldblue910.
M4t3s said:
Does the build number matter if a want only stock recovery? Thanks
Click to expand...
Click to collapse
Yes it does.

I remove link last week because google deleted it and i havent it stored on PC
Sent from my Galaxy Nexus using xda premium

Took me FOREVER to get this to work because I had to use "./fastboot" instead of just "fastboot", but it saved my ass! Thanks a lot.

op updated!

[FASTBOOT][GSM][4.1.2] Rooted Factory Images

I have modified the Yakju Galaxy Nexus factory images by completely wiping my Nexus, restoring using the factory images supplied by Google, rooting them and repacking the images with root intact.
After trying so many ROMs that are available, sometimes I think, especially considering the latest releases from Google, that stock is the way to go. Flashing it using these images is my preferred method, being the cleanest, and I have provided these for your convenience as I haven’t seen them anywhere else only ever seen flashable ROMs (i.e. from Recovery) based on the factory images, etc...
These are:
Factory Images “yakju” for Galaxy Nexus “maguro” (GSM/HSPA+)
Android 4.1.2 (JZO54K) with SU binary only
Android 4.1.2 (JZO54K) with SU binary and SuperSU app
Download links are here. MD5 and SHA1 sums are listed so you can check the downloads.
You have to use Fastboot to flash these to your device. The only requirement is that your device's bootloader is unlocked, which you can easily do, but be warned that this will wipe your user data as will flashing these factory images.
To Unlock Bootloader (in the terminal):
Code:
fastboot oem unlock
Unzip the factory image and just run the flash-all.sh in a Linux terminal or flash-all.bat in the Windows command line.

thanks 'mate! I'm gonna try this out in a bit last time I was on stock was still 4.1.1, and my current custom ROM is still on that version.
What are actually the differences of 4.1.1 and 4.1.2? Just thought you had any idea.. :cyclops:

In 4.1.2 I've noticed better battery life like others have reported and notifications can now be expanded and shrunk if you hold on them and drag up and down.
Sent from my Galaxy Nexus using Tapatalk 2

rhed said:
thanks 'mate! I'm gonna try this out in a bit last time I was on stock was still 4.1.1, and my current custom ROM is still on that version.
What are actually the differences of 4.1.1 and 4.1.2? Just thought you had any idea.. :cyclops:
Click to expand...
Click to collapse
Google the changelog..............
Gave you the fishing rod, fish yourself.
https://www.google.com.sg/search?q=...65784e5eeb7334&bpcl=35466521&biw=1360&bih=643

It would be really helpful if someone could help how to install this using a Mac?

Now that's more like it:good: People should start using fastboot more often other than toolkits:good:Learn to install drivers on your computer. Thanks for posting :highfive: I just hope people take the time and learn it..

harisn said:
It would be really helpful if someone could help how to install this using a Mac?
Click to expand...
Click to collapse
I'm not 100% sure as I have never used a Mac for that but there's a good guide here.

Hey, thanks for the links, just want to ask, if I'm already rooted and unlocked my bootloader, if I flash this via fastboot, will it erase my apps/internal memory/photos and such? Quite curious it's just the unlocking the bootloader that deletes all data. Will like inquiries. Thanks!

MoZuFi93 said:
Hey, thanks for the links, just want to ask, if I'm already rooted and unlocked my bootloader, if I flash this via fastboot, will it erase my apps/internal memory/photos and such? Quite curious it's just the unlocking the bootloader that deletes all data. Will like inquiries. Thanks!
Click to expand...
Click to collapse
If you just run the script as is, it will wipe everything. The best thing to do is just flash the system.img if you want to retain your data.
"fastboot flash system system.img"
Sent from my Galaxy Nexus using Tapatalk 2

chickenfeeder said:
If you just run the script as is, it will wipe everything. The best thing to do is just flash the system.img if you want to retain your data.
"fastboot flash system system.img"
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks a lot!

How to turn Galaxy Nexus from Yakju to Yakjuxw without trace?

Hi. I've searched, but not found a thread about this. I need to bring my phone from yakju to yakjuxw due to warranty purposes.
Can anyone link me a noob step by step guide to yakjuxw?

install fastboot drivers and the files if you don't have them.
http://galaxynexusroot.com/galaxy-n...iversal-guidegsmverizonsprintwindowslinuxmac/
And then:
Download this:
https://code.google.com/p/galaxynex...ame=stock yakjuxw 4.0.1 fastboot.rar&can=2&q=
Extract the files into fastboot folder
Method 1:
and boot your Nexus into fastboot mode then use flash-all.bat file to make it automatically flashing Yakjuxw!
It will wipe everything!
Method 2:
To keep files e.g. Music or pictures...:
You need CWM.
Boot into CWM and wipe factory data reset and then boot into fastboot mode and open CMD and locate to the fastboot files folder and copy/paste these commands into CMD (Command prompt)
Code:
fastboot flash radio radio-maguro-i9250xxkk1.img
fastboot reboot-bootloader
fastboot flash bootloader bootloader-maguro-primekj10.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot
Next time post your question into Q&A section..

https://developers.google.com/android/nexus/images
The stock images here are straight from Google, includes stock images for other nexus devices too..

Mach3.2 said:
https://developers.google.com/android/nexus/images
The stock images here are straight from Google, includes stock images for other nexus devices too..
Click to expand...
Click to collapse
But they are all yakju and takju, so that wouldn't really help him achieve what he want.
The solution has, however, already been given, but seriously it doesn't matter whether it's yakju or not. They are all official roms signed with the official keys, so your warranty is fine as long as it's bootloader locked and unrooted.

mortenmhp said:
But they are all yakju and takju, so that wouldn't really help him achieve what he want.
The solution has, however, already been given, but seriously it doesn't matter whether it's yakju or not. They are all official roms signed with the official keys, so your warranty is fine as long as it's bootloader locked and unrooted.
Click to expand...
Click to collapse
Oh, I misred it, I thought he is trying to go to yakju..
Beamed from my Maguro.

Does anybody has 4.2.1 factory image for yakjuxw? or do i have to go for incremental update only?

chhapil said:
Does anybody has 4.2.1 factory image for yakjuxw? or do i have to go for incremental update only?
Click to expand...
Click to collapse
Is there even any Yakjuxw 4.2.x available?
At least ICS is here:
http://forum.xda-developers.com/showthread.php?t=1625700
By flashing those you get ICS Yakjuxw 4.0.2 which should be upgradeable to JB...