I am a n00b.
Just today I changed my phone from yakjuux to yakju, and it all seemed to go smoothly.
I am receiving texts, and everything seems to be working, and when I was trying to update to jelly bean OTA, everything was going well, until a little red triangle popped up over the little android, and my phone restarted with no change. I flashed my original radio image (UGLA4) so Im not sure whats up with that. If anyone has any suggestions about how I can fix this it would be greatly appreciated.
If not, I would like to restore my phone to yakjuux using a backup I made using this website: http://forum.xda-developers.com/showpost.php?p=21266325&postcount=239 as a guide. I have all the files saved onto my laptop, but Im unsure about how to use them and restore my phone to its original state (yakjuux)
Many thanks
lechickenwing said:
I am a n00b.
Just today I changed my phone from yakjuux to yakju, and it all seemed to go smoothly.
I am receiving texts, and everything seems to be working, and when I was trying to update to jelly bean OTA, everything was going well, until a little red triangle popped up over the little android, and my phone restarted with no change. I flashed my original radio image (UGLA4) so Im not sure whats up with that. If anyone has any suggestions about how I can fix this it would be greatly appreciated.
If not, I would like to restore my phone to yakjuux using a backup I made using this website: http://forum.xda-developers.com/showpost.php?p=21266325&postcount=239 as a guide. I have all the files saved onto my laptop, but Im unsure about how to use them and restore my phone to its original state (yakjuux)
Many thanks
Click to expand...
Click to collapse
You are seeing the little red triangle because you have an image that is not stock. You need to do the optional steps to get the ota (i.e., you need to flash the bootloader, radio and recovery). Go back to the convert to yakju guide and do them.
P.S. why did you not flash the JB images instead of the ICS images??
Sent from my Galaxy Nexus using Tapatalk 2
thanks
efrant said:
You are seeing the little red triangle because you have an image that is not stock. You need to do the optional steps to get the ota (i.e., you need to flash the bootloader, radio and recovery). Go back to the convert to yakju guide and do them.
P.S. why did you not flash the JB images instead of the ICS images??
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I flashed the bootloader, radio and recovery(I probably should have mentioned that in my initial post). Do I need to download a new image to flash onto my device? And how can I tell if its stock? I got my factory image from the link from your guide.
Im not sure why I didnt flash the JB images... I'll blame it on my n00bery.
Redoing
lechickenwing said:
I flashed the bootloader, radio and recovery(I probably should have mentioned that in my initial post). Do I need to download a new image to flash onto my device? And how can I tell if its stock? I got my factory image from the link from your guide.
Im not sure why I didnt flash the JB images... I'll blame it on my n00bery.
Click to expand...
Click to collapse
Will there be any problems if I follow all the steps in your guide, and pretty much redo everything? I would flash the bootloader, flash the same radio (UGLA4), flash the data paritition, flash the system partition, flash the kernel and flash the recovery the only difference being that I would use the JB image rather than the ICS image.
Thanks again
lechickenwing said:
Will there be any problems if I follow all the steps in your guide, and pretty much redo everything? I would flash the bootloader, flash the same radio (UGLA4), flash the data paritition, flash the system partition, flash the kernel and flash the recovery the only difference being that I would use the JB image rather than the ICS image.
Thanks again
Click to expand...
Click to collapse
There will be no issues. Note that if you flash the UGLA4 radio, the next OTA update will not install. You will need to flash the XXLF1 radio before attempting to install the next OTA update. (That is probably why you are seeing the red triangle -- the OTA is expecting to see the XXLA2 radio, and it is seeing the UGLA4. If you want the update to JB to install, just flash the XXLA2 radio, and the update will install.)
radio
efrant said:
There will be no issues. Note that if you flash the UGLA4 radio, the next OTA update will not install. You will need to flash the XXLF1 radio before attempting to install the next OTA update. (That is probably why you are seeing the red triangle -- the OTA is expecting to see the XXLA2 radio, and it is seeing the UGLA4. If you want the update to JB to install, just flash the XXLA2 radio, and the update will install.)
Click to expand...
Click to collapse
Im worried about not flashing the original radio... Im with wind mobile, and I heard that ugla4 is designed to fix roaming issues with winds service. If I switch the radio to xxla2, Im worried that I might get some of these roaming issues and a rather expensive bill.... thoughts?
lechickenwing said:
Im worried about not flashing the original radio... Im with wind mobile, and I heard that ugla4 is designed to fix roaming issues with winds service. If I switch the radio to xxla2, Im worried that I might get some of these roaming issues and a rather expensive bill.... thoughts?
Click to expand...
Click to collapse
Flash the XXLA2, install the update, then flash back your UGLA4 if you feel it necessary...
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Flash the XXLA2, install the update, then flash back your UGLA4 if you feel it necessary...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
After updating to JB, I got prompted to update the OS to 4.1.2 and tried the OTA. For some reason it worked even though i wasn't using the corresponding stock radio image, and now I'm being prompted to do another OTA update (4.2.1). Seeing as the OTA worked last time, I tried to do it once more with the 4.2.1. update, but i ran into the same problem as last time: a little red triangle appeared over the little green android. So I did what you suggested, and flashed the xxla02 radio, and then tried to install the OTA but the little red triangle appeared again. So my question is; are there new corresponding stock boot, radio, and recovery images for JZO54K? If so, i probably still have the boot, radio, and recovery images that were stock to JRO03C.
I figure that if i flash the new stock boot radio and recovery images, the OTA should go smoothly. Any thoughts? Or should I just manually flash the 4.2.1 update that i can download from the google developers website ?
lechickenwing said:
After updating to JB, I got prompted to update the OS to 4.1.2 and tried the OTA. For some reason it worked even though i wasn't using the corresponding stock radio image, and now I'm being prompted to do another OTA update (4.2.1). Seeing as the OTA worked last time, I tried to do it once more with the 4.2.1. update, but i ran into the same problem as last time: a little red triangle appeared over the little green android. So I did what you suggested, and flashed the xxla02 radio, and then tried to install the OTA but the little red triangle appeared again. So my question is; are there new corresponding stock boot, radio, and recovery images for JZO54K? If so, i probably still have the boot, radio, and recovery images that were stock to JRO03C.
I figure that if i flash the new stock boot radio and recovery images, the OTA should go smoothly. Any thoughts? Or should I just manually flash the 4.2.1 update that i can download from the google developers website ?
Click to expand...
Click to collapse
Not all updates will update the radio or boot images, but some will. If you are on 4.1.2, for future updates to work, including 4.2.1, you need the boot, recovery and Radio images from 4.1.2.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Not all updates will update the radio or boot images, but some will. If you are on 4.1.2, for future updates to work, including 4.2.1, you need the boot, recovery and Radio images from 4.1.2.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks efrant, youre a legend. Do you by chance know what the stock radio image for 4.1.2 is? And the boot and recovery images can be downloaded from the google developers web site right?
lechickenwing said:
Thanks efrant, youre a legend. Do you by chance know what the stock radio image for 4.1.2 is? And the boot and recovery images can be downloaded from the google developers web site right?
Click to expand...
Click to collapse
I think it is xxlf1. Go to randomphantasmagoria.com. Oldblue910 has mirrored all the old factory images there.
Sent from my Galaxy Nexus using Tapatalk 2
Related
Nexus CM Blog: Sprint Galaxy Nexus Radio Images
Fix OTA upgrade to FD02 with these *fixed* FC12 radio images.
If you run CM9, AOKP, CNA or other custom Android, you may will want to flash directly to FD02.
Thanks to considerable help from winner00 and testers in channel freenode #gn-sprint we managed to figure out the real cause of the OTA upgrade failures plaguing us. We also have extracted and thoroughly tested fastboot and CWM/TWRP flashable .zip's of both FC12 and FD02 radios in the link above. The Nexus CM blog will maintain vigorously tested fastboot and flashable .zip's for all current and future toroplus radio firmware.
What broke OTA?
In short, this was the forum community's fault.
The initial leaked FC12 factory restore has a LTE radio image that does not match the radio that shipped on the Sprint Galaxy Nexus. As a result, the FD02 OTA upgrade fails. Please stop bothering Sprint stores for phone repairs/replacements.. Fortunately you can now easily fix these issues with the heavily tested downloads available from the link above. Please verify the md5sums before you attempt to flash with either fastboot, CWM or TWRP.
Follow the CyanogenMod Sprint Galaxy Nexus Google+ page for the latest development news and to interact with the developers!.
Don't want to clutter the thread with thanks and +1's but, u know...... this works and works well. I will no longer flash leaked radios, lol.
The sprint gnex community is growing daily, yay.
Stickied for now. It will need to be maintained with future radios as well.
Thanks
FNM
Flashed both CDMA and LTE radios in fastboot. Everything works great! Wish they would open up LTE here in Dallas! Probably going to flash CM9. I miss CM since I got rid of the EVO!
Glad you guys could find the legit FC12 radios! My phone is very happy now.
Man got me right before I odined thanks for this.
Know this is mostly for people who are running other roms, but if you're stock with an unlocked bootloader, you might consider applying this zip, which will bring you up to full FD02.
http://forum.xda-developers.com/showthread.php?t=1635104
Real happy to see these great devs including op and mod from the epic community now working on this amazing device. Really in love with it. Pretty sad, I know. Good to know I'm not alone though.
jwischka said:
Know this is mostly for people who are running other roms, but if you're stock with an unlocked bootloader, you might consider applying this zip, which will bring you up to full FD02.
http://forum.xda-developers.com/showthread.php?t=1635104
Click to expand...
Click to collapse
Nice!
Thanks for this Wayne. Should be very helpful to a lot of us! Works great!
Sent from my Sprint Galaxy Nexus CDMA using xda premium
wtogami said:
What broke OTA?
In short, this was the forum community's fault.
The initial leaked FC12 factory restore has a LTE radio image that does not match the radio that shipped on the Sprint Galaxy Nexus. As a result, the FD02 OTA upgrade fails. Please stop bothering Sprint stores for phone repairs/replacements.. Fortunately you can now easily fix these issues with the heavily tested downloads available from the link above. Please verify the md5sums before you attempt to flash with either fastboot, CWM or TWRP.
Click to expand...
Click to collapse
For what it's worth, I have a stock phone with unlocked bootloader and root and the OTA fails for me. I never flashed the FC12 radios, I never flashed any ROMs. I got the OTA yesterday and it fails with Status 7.
joypunk said:
For what it's worth, I have a stock phone with unlocked bootloader and root and the OTA fails for me. I never flashed the FC12 radios, I never flashed any ROMs. I got the OTA yesterday and it fails with Status 7.
Click to expand...
Click to collapse
Same here, Stock sprint Gnex, Unlocked and rooted. But failed the OTA update.
joypunk said:
For what it's worth, I have a stock phone with unlocked bootloader and root and the OTA fails for me. I never flashed the FC12 radios, I never flashed any ROMs. I got the OTA yesterday and it fails with Status 7.
Click to expand...
Click to collapse
I had the same issue -- unlocked but never installed other radios, everything stock. I even went back to locked stock by odin and still couldn't get the OTA. I called Sprint and the guy told me to go to the store. The store tried the OTA and it failed. That tech told me they had an email that said many people had issues installing the OTA but they couldn't manually update until May 17th.
They ended up swapping the phone for me and we updated it right there in the store.
The bonus was that I had spent about $5 of my Google wallet money and when I set up the new phone I got the whole $10 again.
meatgel said:
I had the same issue -- unlocked but never installed other radios, everything stock. I even went back to locked stock by odin and still couldn't get the OTA. I called Sprint and the guy told me to go to the store. The store tried the OTA and it failed. That tech told me they had an email that said many people had issues installing the OTA but they couldn't manually update until May 17th.
They ended up swapping the phone for me and we updated it right there in the store.
The bonus was that I had spent about $5 of my Google wallet money and when I set up the new phone I got the whole $10 again.
Click to expand...
Click to collapse
You got lucky I cant see them replacing phones for that. The root method you used I would be curious about as well as it probably altered system files that were to be updated.
Paleryder said:
You got lucky I cant see them replacing phones for that. The root method you used I would be curious about as well as it probably altered system files that were to be updated.
Click to expand...
Click to collapse
I used the GNEX toolkit to root, so if that's the problem a lot more people would be having it. Plus I returned to stock with ODIN, wouldn't that put it back to stock with no altered system files?
What I have been reading the radios were either corrupt or a different version that was originally shipped.I'm assuming the Odin radios were having the same issue. The official CM9 peeps have posted correct radios
Sent from my Galaxy Nexus using Tapatalk 2
If I am on AOKP Rom, should I update to FD02?
holy hell thank you guys so much for this helped me out!
I was on Skank CM9 Kand with FD01 radios. I flashed these FD12 radios restored a stock nandroid I made and fastboot flashed a stock radio IMG it worked perfectly and I recieved the full update. Thanks
Odd issue im having after a fastboot oem unlock and a sucessful twrp 2.1.2 toro plus recovery flash it wont stick keeps reverting to stock recovery.
I did reboot into system before installing and then flash. I was even able to make a nandroid but after booting into recovery Im back on a stock recovery :/
any ideas
ty
Paleryder said:
I was on Skank CM9 Kand with FD01 radios. I flashed these FD12 radios restored a stock nandroid I made and fastboot flashed a stock radio IMG it worked perfectly and I recieved the full update. Thanks
Odd issue im having after a fastboot oem unlock and a sucessful twrp 2.1.2 toro plus recovery flash it wont stick keeps reverting to stock recovery.
I did reboot into system before installing and then flash. I was even able to make a nandroid but after booting into recovery Im back on a stock recovery :/
any ideas
ty
Click to expand...
Click to collapse
On the stock ROM there is a script that restores stock recovery upon reboot. I believe it's in /system named recovery-from-boot. Either erase that file or rename it to recovery-from-boot.bak.
I keep getting the new OTA IMM76I update for my Sprint Galaxy Nexus and every time it downloads & starts to install it just opens up TWRP recovery and nothing happens...
I tried to use the Nexus Toolkit as well and do exactly what it says but get hung up on "waiting for device" after it extracts the files and everything...
I've been searching for 4 hours to try to get this update done because my calls keep dropping...
is it because I have the Franco Kernel installed on a rooted device?
no ROM or anything, just rooted with the Franco Kernel...
I tried like hell to find the stock kernel but couldn't...
DAMN this is aggravating
could someone PLEASE either explain or point to a link where it explains how to deal with this issue?
HATE having a brand new phone and the calls keep dropping....
I know there are "lots of threads on this issue" already but none clearly explain how to fix THIS issue...
please hep me out...thanks in advance.
http://forum.xda-developers.com/showthread.php?p=20843237
While the above link is for how to manually install updates, the reasons why an ota update won't install are the same: if you want it to install ota, you need: the stock kernel, stock recovery, stock radio, and stock rom (with no original files missing/modified). Additionally, all of these have to be the same version.
Maybe you could also get the ota update file name for us as well.
Sent from my Galaxy Nexus using Tapatalk 2
does the stock radio stay the same after root?
like I said, all I changed was the kernel...so I'd have to flash the stock kernel to install the update, correct?
another issue I'm having is damn CWM....I have TWRP on here now and when I go to flash CWM through ROM Manager it get all the way to the end, freezes then fails...can't seem to get CWM installed for my life.
also what is all this "yakju, takju, etc..."??
I'm new to this device from an Evo 4G where we just download & flash and all updates work..never had an issue like this.
my device is v4.0.4., build Imm76D.L700FC12
baseband L700.05 V.FC12/L700.FC12
on the bootloader I saw "toro" on there so I'm guessing that's because it hasn't been updated, correct?
thanks.
broad_st_bully said:
does the stock radio stay the same after root?
like I said, all I changed was the kernel...so I'd have to flash the stock kernel to install the update, correct?
Click to expand...
Click to collapse
If all you changed is the kernel, then all you have to do is flash the stock kernel.
efrant said:
If all you changed is the kernel, then all you have to do is flash the stock kernel.
Click to expand...
Click to collapse
would you have the stock kernel?
can't seem to find it...
Try the GN root kit. You'll find it in the dev section. That will get you back on stock kernel.
Sent from my Galaxy Nexus using Tapatalk 2
You need to have stock recovery too.
broad_st_bully said:
would you have the stock kernel?
can't seem to find it...
Click to expand...
Click to collapse
Unfortunately I do not (I don't own a Sprint device), but I'm sure that it is floating around somewhere.
Hey!
So i bought a used nexus which has yakju.
It got 4.0.2 and it says "You should upgrade you system to 4.0.4" and when i start the installation it reboots. Then i get a android symbol that has like a blue thing in it's stomach and is standing up.
But when it gets to maybe 10-15 % he goes more far away and lays down with a big red thing over his stomach and then i have to plug my battery out to start it again.When i look for a new system update it says my system is up to date, but it still says 4.0.2.
I'm not really sure what to do, so hopefully somebody can help me.
Thanks in advance.
You aren't completely stock. Read this for more info: http://forum.xda-developers.com/showthread.php?t=1419170
El Daddy said:
You aren't completely stock. Read this for more info: http://forum.xda-developers.com/showthread.php?t=1419170
Click to expand...
Click to collapse
So i guess i should use this method? Cause i got a unlocked bootloader.
Method 2 - Stock recovery installed, Unlocked bootloader
Correct. Coming from 4.0.2 you should use the yakju IMM76I from ICL53F OTA
If I were you, I'd flash an insecure boot image, then CWM and just flash that way, or via Odin (Odin is the n00b-friendliest)
familyguy59 said:
If I were you, I'd flash an insecure boot image, then CWM and just flash that way, or via Odin (Odin is the n00b-friendliest)
Click to expand...
Click to collapse
Not sure what you are trying to suggest, but the OP wants to upgrade his ROM to 4.0.4, not flash a new/clean 4.0.4 ROM. Flashing an insecure boot image will cause the update to fail.
Sent from my Galaxy Nexus using Tapatalk 2
So when i got my galaxy nexus about 3 weeks ago I rooted and unlocked the boot loader but stuck with the stock rom. My radio was FC12 for both CDMA and LTE. I didn't have any issues with those radios. My through put was around .6 - .7mbps down. I kept getting the message to do the OTA upgrade which was annoying so i manually flashed FD02 via fastboot. My throughput went to crap and was only getting like .02mbps. So this is what i did. I flashed back to stock recovery, flashed back to FC12 relocked my boot loader and did a full stock restore via the android OS. I still cannot install the OTA upgrade. Is there something I am missing? My plan was to go totally stock grab the updates and then reroot and unlock again.
Thanks and sorry if this has been asked but i did searched and couldn't find a similar situation.
also for a good funny for ya i forgot that unlocking again wipe everything so i lost all my pics and movies and backups That's what happens when you work on stuff with 2 rug rats running around and bugging you when you are doing something.
Wrong section this is for development please ask questions in q and a.
I think there is a stock fd02 tar that you need to flash through Odin... http://forum.xda-developers.com/showthread.php?t=1620036
You could have reflashed the fc12 radios through fastboot.
Sent From My Sprint Galaxy Nexus via XDA Premium
zachl said:
So when i got my galaxy nexus about 3 weeks about I rooted and unlocked the boot loader but stuck with the stock rom. My radio was FC12 for both CDMA and LTE. I didn't have any issues with those radios. My through put was around .6 - .7mbps down. I kept getting the message to do the OTA upgrade which was annoying so i manually flashed FD02 via fastboot. My throughput went to crap and was only getting like .02mbps. So this is what i did. I flashed back to stock recovery, flashed back to FC12 relocked my boot loader and did a full stock restore via the android OS. I still cannot install the OTA upgrade. Is there something I am missing? My plan was to go totally stock grab the updates and then reroot and unlock again.
Thanks and sorry if this has been asked i searched and couldn't find a similar situation.
also for a good funny for ya i forgot that unlocking again wipe everything so i lost all my pics and movies and backups That's what happens when you work on stuff with 2 rug rats running around and bugging you when you are doing something.
Click to expand...
Click to collapse
Flash this to update the radios, then flash this to update the system files.
Thats the radio update that I used originally. Also I did flash back to the FC12 i just don't want to keep seeing the OTA message. Also were did we get this other update file? I'm not a big fan of putting .zips and custom ROM's on my phone since you don't really know whats in them...sorry in my line of work its something people rarely thing about when just willy nilly installing things to their phones/computers.
Well if you don't want to do any of what they told you to do, I would think your only other option is taking the phone in to Sprint and having them flash for you.
zachl said:
Thats the radio update that I used originally. Also I did flash back to the FC12 i just don't want to keep seeing the OTA message. Also were did we get this other update file? I'm not a big fan of putting .zips and custom ROM's on my phone since you don't really know whats in them...sorry in my line of work its something people rarely thing about when just willy nilly installing things to their phones/computers.
Click to expand...
Click to collapse
LOL because if it does have stuff containing "harmful" things... they will be sued. I've never had any issue flashing ANYTHING to my phone. I guess your one of those people who think somebody is wiretapping your LAN line huh? or your internet and now your phone?.... seriously we are only providing help... take it or leave it.
zachl said:
Thats the radio update that I used originally. Also I did flash back to the FC12 i just don't want to keep seeing the OTA message. Also were did we get this other update file? I'm not a big fan of putting .zips and custom ROM's on my phone since you don't really know whats in them...sorry in my line of work its something people rarely thing about when just willy nilly installing things to their phones/computers.
Click to expand...
Click to collapse
I made it. If you don't want to flash it, don't.
It's taken from the OTA, with the updater script modified such that it doesn't check or update the bootloader, recovery, or radios. The stock script won't work if a) you've unlocked your bootloader, b) done anything to your recovery, or c) don't have the original radios. Hence, your update is failing. That file won't.
I made it because I was tired of seeing the OTA update message. Your options are to flash that zip, or ODIN and lose all your data. It doesn't matter to me which you choose.
Not Development!
Thread Moved
FNM
Sent from my SPH-D700 using xda premium
I have unlocked, rooted, and installed Clockwork Recovery on my Galaxy Nexus (GSM, Wind Canada), and now I want to flash 4.0.4 yakju.
My current bootloader is PRIMEKK15 and my current radio baseband is UGLA4
Is flashing 4.0.4 yakju as simple as downloading the image found on google's site (yakju-imm76i-factory-8001e72f.tgz), putting it on the phone, going to Clockwork Mod, navigating to "install zip from SDcard", then choosing yakju-imm76i-factory-8001e72f.tgz, or do I have to open the tgz, then open the tar inside, and then extract this zip and install that in CWM http://i.imgur.com/wXC64.png
Since it's not a custom ROM like AOKP or CM, do I have to wipe data/factory reset in clockwork? Do I have to flash gapps?
Do I have to flash the new bootloader and radio baseband found in 4.0.4 separately?
Also, some people report reception problems with the baseband included in 4.0.4. If I want to go back to UGLA4, is that possible? I would be using the CWM "radio.img" for UGLA4 found here http://forum.xda-developers.com/showpost.php?p=23149491&postcount=139
I think that's all the questions I have, lol.
Well first off, if you're going to do it I'd just recommend you wait for the 4.1.1 image for the GSM GNex to drop. If you're really ansy, then you could flash 4.0.4 and you'll still get the OTA, but just something to think about.
Now to the question, no, you don't flash it like a ROM in CWM recovery. If you wish to completely move to yakju (or takju) to get on the Google update line (not sure why else you'd do it), you need to flash the images via fastboot. All parts of the images. It's important to have the proper bootloader and radio if you intend to receive and automatically install OTA updates. If you don't, you won't be able to install it as it checks for the radio and bootloader as part of the install process.
Follow this guide from Efrant, it's gold: http://forum.xda-developers.com/showthread.php?t=1626895
Don't use a toolkit!
Also, some people report reception problems with the baseband included in 4.0.4. If I want to go back to UGLA4, is that possible? I would be using the CWM "radio.img" for UGLA4 found here http://forum.xda-developers.com/show...&postcount=139
Click to expand...
Click to collapse
I haven't heard about any issues with the latest 4.0.4 radio outside of isolated problems. You can change the radio if you want (via fastboot, rly quick), but as I said, it'll stop you from auto-installing OTAs (which is why you went to yakju, isn't it?). You'll also get a new radio with 4.1.1.
Hmm, I might not even bother, seeing as to get the updates I'd lose CWM and root. Perhaps I will just wait for 4.1 like you said and install that.
By the way, since I am on 4.0.2 but I have CWM, does that mean even if my yakjuux build got 4.0.4 OTA, I wouldn't get notified (because of the custom recovery)??
EDIT: Say Google puts up a 4.1 image next week, I would just need to download it and follow the same steps that are outlined in that post (flashing all the different images in fastboot)?
Matt08642 said:
Hmm, I might not even bother, seeing as to get the updates I'd lose CWM and root. Perhaps I will just wait for 4.1 like you said and install that.
Click to expand...
Click to collapse
You can flash CWM and root it again after going to yakju, but you'll have to update manually (no auto-installing OTA) after that. You have to pull the image and flash it, and use an app like "OTA root keeper" to hold onto root.
By the way, since I am on 4.0.2 but I have CWM, does that mean even if my yakjuux build got 4.0.4 OTA, I wouldn't get notified (because of the custom recovery)??
Click to expand...
Click to collapse
You'll be notified, but the update won't install. It requires stock recovery to auto-install.
Cool. In that case, I will just wait for JB, then once I flash that image myself, I will reflash CWM and root my phone again.
Thanks for the help, and thanks for the link to that thread!
Matt08642 said:
Cool. In that case, I will just wait for JB, then once I flash that image myself, I will reflash CWM and root my phone again.
Thanks for the help, and thanks for the link to that thread!
Click to expand...
Click to collapse
No problem.
Sent from my Galaxy Nexus using xda premium