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.

I need to return my device - I relocked it, flashed stock, but...

I need to return my Nexus and I did a stock flash, unrooted, and oem lock.
The original phone has these settings:
Baseband (Android 4.0.2):
I9250UGLA4
Kernel:
3.0.8-gaaa2611
[email protected]#1
Build Number:
ICL53F.I9250UGLA4
This is what my phone has:
Baseband (Android 4.0.2):
I9250XXKK6
Kernel:
3.0.8-gaaa2611
[email protected]#1
Build Number:
ICL53F
How do I get my version to have the same baseband as the 1st listed settings, and change the build #?

Its because your phone came with a non-yakju version of ICS, and you flashed it back to a stock yakju image.
You can flash the old radio (just unlock again and fastboot flash it), but the only way to properly change the build number is to have someone give you the image for that specific build it had out of the box, and flash that.
Honestly it shouldn't matter. As far as they care, ICS is ICS and the bootloader is locked. That's all they care about for a warranty/return claim.

Is it possible to find the build I need online?
I did some searches and found these:
http://forum.xda-developers.com/showpost.php?p=23131447&postcount=121
http://code.google.com/android/nexus/images.html
Am I able to restore it back to factory without have to be rooted?

martonikaj said:
You can flash the old radio (just unlock again and fastboot flash it), but the only way to properly change the build number is to have someone give you the image for that specific build it had out of the box, and flash that.
Click to expand...
Click to collapse
Once I unlock it and flash the old radio, can I think re-lock it?
Also, (n00b question here, sorry) how do you fastboot flash?

unity04 said:
Is it possible to find the build I need online?
I did some searches and found these:
http://forum.xda-developers.com/showpost.php?p=23131447&postcount=121
Click to expand...
Click to collapse
That's just an update.
http://code.google.com/android/nexus/images.html
Click to expand...
Click to collapse
Those are stock yakju images. You're already on those. Google doesn't post the non-yakju builds.
Am I able to restore it back to factory without have to be rooted?
Click to expand...
Click to collapse
If you get ahold of the proper build you want to go to, there's no rooting involved. It'll just be some fastboot flashing just like before.
unity04 said:
Once I unlock it and flash the old radio, can I think re-lock it?
Click to expand...
Click to collapse
Of course. You can unlock and relock the bootloader all you want.
Also, (n00b question here, sorry) how do you fastboot flash?
Click to expand...
Click to collapse
Plenty of guides here. You download ADB and Fastboot files and your device drivers, and use the command line (Terminal on OSX) to call a few Fastboot commands which flashes the files to the device.
BUT as I said, it really doesn't matter. They don't care that you're returning a device that has yakju instead of yakjuxw (or whatever). They don't even know what that means. They care that it has stock ICS and a locked bootloader. As I said, you can flash the radio because its easily done and readily available, but even that's probably overkill.

I think I found what I'm looking for:
http://forum.xda-developers.com/showthread.php?t=1405345
The second post has the UGLA4 radio img. Is that what I need?

Update: I flashed the above radio and now this is what I have:
Baseband (Android 4.0.2):
I9250UGLA4
Kernel:
3.0.8-gaaa2611
[email protected]#1
Build Number:
ICL53F
The only thing missing is the .I9250UGLA4 at the end of the ICL53F on the Build Number... any idea on how to get that there?

unity04 said:
Update: I flashed the above radio and now this is what I have:
Baseband (Android 4.0.2):
I9250UGLA4
Kernel:
3.0.8-gaaa2611
[email protected]#1
Build Number:
ICL53F
The only thing missing is the .I9250UGLA4 at the end of the ICL53F on the Build Number... any idea on how to get that there?
Click to expand...
Click to collapse
Restore this backup in CWM: http://forum.xda-developers.com/showpost.php?p=23784381&postcount=1

Do I need to be rooted/unlocked bootloader to flash in CWM?

it will be amazing if they care or find out about it..... dont worry too much.

unity04 said:
Do I need to be rooted/unlocked bootloader to flash in CWM?
Click to expand...
Click to collapse
Since you flashed a google stock image back to your phone and relocked the bootloader then you will have to unlock the bootloader and flash cwm in order to flash the cwm file. No need to root. Once you have flashed cwm then you can reboot into android, copy the zip file across to your virtual sd card and flash it. You can unlock/relock the bootloader and flash cwm via the ToolKit if you want to take the easy path.
As previous posters have said as long as your bootloader is locked then they wont really care about anything else. Of course there 'is' a minute chance your phone may be handled be some anal techie who will check every detail so if you want to be 100% sure then flashing the cwm image is your safest bet.
After flashing the cwm rom you will want to flash back the stock recovery image and relock the bootloader. Both those tasks can be done via the ToolKit too
Mark.

unity04 said:
Do I need to be rooted/unlocked bootloader to flash in CWM?
Click to expand...
Click to collapse
It does NOT matter if your bootloader is locked or not.
It does NOT matter if you have root or not.
All that matters is that you have CWM installed.
After you restore that backup, there is nothing else you need to do, unless your bootloader is unlocked -- then just relock it.
No need to flash a stock recovery -- the backup includes the stock recovery.

I really wouldn't worry about it, after mine went wrong I had to take it to a Samsung repair shop in York, so I returned it to stock, locked the boot loader, then when I got it back the boot loader was unlocked! Mine then got sent off to Samsung another 2 times with the boot loader left unlocked, like others say I don't think anyone will check

[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!

Flashed FLO bootloader on DEB

In my haste to flash the latest stock image, I accidentally downloaded the FLO 6.0.1 and flashed the bootloader. I can access the bootloader just fine, but when I try to flash the correct DEB version, it never updates the stats to show DEB.. it still shows that the FLO bootloader is installed.
Anyone know of another way to fix this issue?
Thank

jseaton said:
In my haste to flash the latest stock image, I accidentally downloaded the FLO 6.0.1 and flashed the bootloader. I can access the bootloader just fine, but when I try to flash the correct DEB version, it never updates the stats to show DEB.. it still shows that the FLO bootloader is installed.
Anyone know of another way to fix this issue?
Thank
Click to expand...
Click to collapse
If my memory serves me right, I undid the same thing on a Nexus 7 (2012). You need to locate a script that tells you step by step how to erase and reload everything, including the correct bootloader and system.img. You'd need to search this forum for the script 'cause I can't remember where. Do it by command lines if you could. It's safer than using the automated AIOs. Good luck.

graphdarnell said:
If my memory serves me right, I undid the same thing on a Nexus 7 (2012). You need to locate a script that tells you step by step how to erase and reload everything, including the correct bootloader and system.img. You'd need to search this forum for the script 'cause I can't remember where. Do it by command lines if you could. It's safer than using the automated AIOs. Good luck.
Click to expand...
Click to collapse
Thanks for the reply. I actually did the flashing manually with fastboot commands. I tried the same with the right version, but when I'm in the bootloader it still shows as FLO.
I can boot to stock Android fine after flashing via fastboot, but when I try to flash something that is custom for DEB, it fails.
Sent from my Nexus 6 using Tapatalk

Turns out I'm an idiot. The bootloader is the same between flo and deb. Saw that it should report the bootloader as FLO-x.xx :
https://android.googlesource.com/de...ory-images/generate-factory-images-package.sh
Code:
source ../../../common/clear-factory-images-variables.sh
BUILD=937116
DEVICE=deb
PRODUCT=razorg
VERSION=kot49h
SRCPREFIX=signed-
BOOTLOADER=flo-04.02
RADIO=deb-g00_2.37.0_1024
source ../../../common/generate-factory-images-common.sh