Related
This has probably been answered before by one or two people, but I'd rather know from the whole lot of you brave souls who have switched from yakjuux to yakju.
I'm specifically wondering from those of you that have done the COMPLETE switchover to the yakju build... that includes ALL things that come with it, including it's radio.
I know we can flash the KL1 radio on top, but I'm not looking to do that. I want the entire thing to be from Google, and keep it as such. From what I understand, when you have the yakju build, and the KL1 radio, you will not get OTA updates automatically, thus having to flash manually. On the flip side, if its a complete yakju, including the radio that comes with it, you will get the OTA updates automatically.
So here's the questions:
1. Have any of you flashed the yakju build on your phones KEEPING THE RADIO that is a part of that build? If so, what are your experiences with reception/data specifically on the Bell Network? Any difference that you've noticed?
2. Am I wrong in my thinking? If you did flash yakju, then the KL1 radio, will you definitely receive OTA updates automatically? As in no real user intervention other than clicking "update"?
I want to be sure before I do this, because I cannot find a complete image of the yakjuux build that includes everything including the bootloader in case something goes wrong/or doesn't update the way a true Google experience should.
Please let me now.
Thanks
I am running stock 4.0.2 with everything from the official image. No problem with signal. What is your worry?
Sent from my Galaxy Nexus using XDA App
superlj said:
I am running stock 4.0.2 with everything from the official image. No problem with signal. What is your worry?
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Just want to make sure the radio from the official build works properly with Bell.
Don't really want to create a Frankenstein build so too speak by adding different radios
Sent from my Galaxy Nexus using Tapatalk
I changed mine to yakju shortly after I got the phone, about two weeks ago.
I haven't noticed any difference with the radio, good or bad. Still no issues with reception or anything dropping out.
Can't tell you about the OTA updates though, haven't received anything yet to go past 4.0.2. If/when I do, I'll update my reply to help everyone else out.
torradan said:
I changed mine to yakju shortly after I got the phone, about two weeks ago.
I haven't noticed any difference with the radio, good or bad. Still no issues with reception or anything dropping out.
Can't tell you about the OTA updates though, haven't received anything yet to go past 4.0.2. If/when I do, I'll update my reply to help everyone else out.
Click to expand...
Click to collapse
Thank you for your reply. Just to clarify, you are using the stock radio that came with yakju? I think its KK or something? Or did you change over to KL1?
greeced said:
Thank you for your reply. Just to clarify, you are using the stock radio that came with yakju? I think its KK or something? Or did you change over to KL1?
Click to expand...
Click to collapse
bump. bump.
why are you so worried about receiving ota automatically? since you are on xda and know how to flash you will always have the latest build. Being in canada we usually are slow to get updates(Galaxy Nexus is still on 4.0.1 here) so whats the point in waiting for ota. if you are planning to flash an update now why not do it again when a new one comes out.
btw to answer your questions about the radio, the stock one,XXKK6, will work fine with bell although UGKL1 seems to work better for me on Fido. UGKL1 is probably the radio that your phone has now. it was on my stock fido GN.
I flashed the entire package, including the xxkk6 radio.. Works perfectly fine on Rogers, no comment for Bell but should be fine. Just try it, flash it back if you don't like it. Takes all of 2 minutes.
From what I understand (and I'm still new to this as well) you need to use the radio that comes with the official image otherwise you won't get OTA updates associated with that rom.
Newbie account so I can't post links yet but search "galaxy nexus upgrade to official roms yakju build" and its the leemn wordpress blog that says:
"After flashing to yakju build, you can still receive notification of the OTA updates.If you have flashed the radio, system, userdata and boot partitions, and you still have the stock recovery (or have flashed it) from the 4.0.2 image, you will be able to install the updates. However, if you flash a different radio, or different kernel , or a custom recovery, you will need to flash back the stock ones first before being able to install the update."
That's the whole thing.
When I was on the SGS, I tried a while slew of custom roms as well as the European beta builds.
I wasn't worried about doing that because there was always a way to go back to KG3, by spoofing the firmware to make KIES think it was on JL2. KIES would download KG3 officially back to the phone.
I always seemed to revert back to stock because none of the beta or custom roms seemed to work efficiently for me the way the stock one did.
I know, I'm strange.
So that experience brings me here. Without an official download of the yakjuux build available (bootloader image), there really is no going back if something just doesn't work as intended. (remember, we all use our phones differently).
That's why the fright. I just don't want to get to the point that this Canadian incarnation starts having an identity crisis.
Sent from my Galaxy Nexus using Tapatalk
I flashed it all.
Works great. No issues. I also wanted 100% stock and so far, i am very happy with it.
greeced said:
Thank you for your reply. Just to clarify, you are using the stock radio that came with yakju? I think its KK or something? Or did you change over to KL1?
Click to expand...
Click to collapse
Sorry missed your question, but I'm using the KL1 radio.
I am with Fido and have complete 4.0.2 stock rom. I had some strange issues with signals but everything is fine after I changed to a new SIM.
Sent from my Galaxy Nexus using XDA App
greeced said:
That's the whole thing.
When I was on the SGS, I tried a while slew of custom roms as well as the European beta builds.
I wasn't worried about doing that because there was always a way to go back to KG3, by spoofing the firmware to make KIES think it was on JL2. KIES would download KG3 officially back to the phone.
I always seemed to revert back to stock because none of the beta or custom roms seemed to work efficiently for me the way the stock one did.
I know, I'm strange.
So that experience brings me here. Without an official download of the yakjuux build available (bootloader image), there really is no going back if something just doesn't work as intended. (remember, we all use our phones differently).
That's why the fright. I just don't want to get to the point that this Canadian incarnation starts having an identity crisis.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I'm not sure what the problem is. When you unlock your bootloader, you just do a nandroid backup, and it backups up your system, data, recovery and boot partitions. The radio is already available. So you can always go back to "stock" yakjuux in case yakju doesn't work (which it obviously does for Canadian users). I've even posted a nandroid backup of my yakjuux build before I flashed yakju. There is a thread in the general section. And to address your concern about "always reverting to stock", yakju IS the stock ROM, it is not a beta or a custom ROM.
The bootloader has nothing to do with yakju or yakjuux or whatever. It will not affect anything related to getting an OTA update or installing an OTA update. Keep your current bootloader if you are worried about not having a backup, and go ahead and flash all of the other images (after backing up your originals of course). That way, you can always return to your yakjuxx if you think there is a problem. Just because you didn't flash the bootloader that came with the latest yakju image does not at all mean you are not using yakju, and I would not call it a "frankenbuild" -- think of the bootloader as the BIOS in a computer. You computer is running Windows regardless if you are using an ASUS P5Q motherboard, or an ABIT IP5 motherboard -- both have different BIOS, but the OS is still Windows. Same with a GN -- you are running yakju regardless of whether you bootloader is 10, 14, 15, etc.
EDIT: To specifically address your question number 2 -- if you flash the system, data and boot images from yakju, you are running yakju, and you will receive the notification for an OTA update when it is available. However, you will not be able to have it install automatically if you don't have the radio image that came with the yakju build and a stock recovery (they are all the same). You can, however, flash those back as soon as you receive the OTA update notification and it will install automatically. Bootloader has no relevance whatsoever.
Great explanation. Thank you efrant. You've answered everything I've needed to know
Sent from my Galaxy Nexus using Tapatalk
Well finally took the plunge and went to yakju from yakjuux. Although my experience wasn't as seemless as everyone elses, so I thought I'd tell everyone just in case someone else runs in to the same problem.
For starters: I followed efrants excellent procedure from this exact post. However it also must be noted that I decided to use the 41F (4.0.1) firmware from Google's images instead of the 53F (4.0.2) image. I did this because I wanted to experience an update. lol
Now, at first I had to try several drivers in order for my Windows 7 laptop to even see the phone with the "fastboot devices" command. I finally found one that works. Coincidentally, one driver will work on one machine, but won't on the next, I have no idea why. After finally getting the right one, I proceeded:
I did all steps to the letter, but skipped steps 4,5 and 12, as the post says they were optional and I didn't really want to lose my bootloader and recovery in case I wanted to revert back to yakjuux.
After completing all steps but those, I did the final "fastboot reboot" and the phone restarted.
Here's where the ride began:
When it restarted, it seemed like everything was fine. It took a while to find Bell's settings, but it was ok. It then said an update to 4.0.2. was available.
Upon the reboot and install, the phone shut off, and rebooted twice, after the second time, I had an android on the ground with its chest open and a RED exclamationed triangle above it. My thoughts were "uh oh". I waited and waited, and nothing was happening. Pressing power and holding it down, wouldn't help.... After approx 5 mins I was about to do a battery pull, and it restarted itself, but remained on the 41F update.
Each restart would say it was upgrading, but never did.. always stayed on 41F.
So I went back and did everything in the procedure, not omitting anything this time (goodbye yakjuux bootloader!) and it went off without a hitch... This time my android figure was standing up, very much alive and getting a heart transplant.
So here I am.. Yakju configured and using the yakju KK6 radio. All seems well. Haven't decided if I'm going to put the KL1 radio on as yet, but thats for another day.
Thanks again efrant for all your help and patience with me.
@greeced Welcome to yakju. I doubt you will ever go back to yakjuux.
Sent from my Galaxy Nexus using Tapatalk
Well, I have been on yakju for a few days now and I can say no problems whatsoever.
At first I felt as if it was slightly Laggy, but that seemed to correct itself after a day or so. Not sure why, but the phone is just as quick as before now.
As for the radio, I wanted to stay completely stock, and that included the radio. So my phone is running the stock KK6 that came with the update, and I noticed my DBM levels are just as good as before if not better. So I don't feel the need to flash KL1.
Overall very happy that I'm now Pure Google.
One thing to note:
When I was on my SGS, I always factory reset after every flash, which always seemed to speed up the experience of the new ROM.
I think that should be the case for all firmware updates, including googles.
It's a painful process to redo everything, but well worth it in my opinion.
I mean think about it, installing a fresh copy of windows always performs better than doing an upgrade of windows, so that should be the same here.
We are dealing with computers after all.
At any rate. Just thought I'd update my experience in case anyone else who is on bell felt apprehensive like me.
Sent from my Galaxy Nexus using Tapatalk
greeced said:
Well, I have been on yakju for a few days now and I can say no problems whatsoever.
At first I felt as if it was slightly Laggy, but that seemed to correct itself after a day or so. Not sure why, but the phone is just as quick as before now.
Click to expand...
Click to collapse
I think the general consensus is that ICL53F is more laggy that ITL41F or ITL41D, so it is not a yakju vs yakjuux issue, it is a 4.0.1 vs 4.0.2 issue.
greeced said:
As for the radio, I wanted to stay completely stock, and that included the radio. So my phone is running the stock KK6 that came with the update, and I noticed my DBM levels are just as good as before if not better. So I don't feel the need to flash KL1.
Click to expand...
Click to collapse
Radio performance varies with a huge number of factors. If you are happy with how one radio works, use it. If you want to see if another one is better, try it. If you don't like it, flash back. It takes all of 30 secs to flash a radio.
greeced said:
[snip]
When I was on my SGS, I always factory reset after every flash, which always seemed to speed up the experience of the new ROM.
I think that should be the case for all firmware updates, including googles.
It's a painful process to redo everything, but well worth it in my opinion.
I mean think about it, installing a fresh copy of windows always performs better than doing an upgrade of windows, so that should be the same here.
Click to expand...
Click to collapse
If you believe this, then I suggest that you do not flash older builds and OTA update to a newer ones. This process adds more files to your ROM, and is not as clean as flashing the latest build from Google's factory image site.
When the next version of Android is released, the full version will likely be available on Google's factory image site shortly before OTA's for yakju start rolling out.* If you don't mind redoing your settings, apps, etc., it is better (and faster) to flash the full build, instead of updating your current build.
*My assumption based on release dates for previous versions.
Question efrant.
I relocked my bootloader purposely.
If I wanted to test other radios does the bootloader need to be unlocked?
If it does, no big deal, I just won't do it
Sent from my Galaxy Nexus using Tapatalk
Hey guys,
I recently got a Galaxy Nexus, and wanted to play around with it. It's still on the 4.0.1 stock ROM (yakjuux build). Haven't made any tweaks to it beyond the basics (removed vibration, disabled data since I don't have a data plan, etc).
Basically, what are the benefits of flashing the 4.0.2 factory image (from Google, can't link it yet)? And how would I go about it? My guess is, I'll need to place the files on the phone, then flash it using flash-all.sh. Or would it be better to just pick a custom ROM and go with that instead of flashing the yakju build?
The benefits of straight yakju are that you should get updates first (faster than yakju** people anyways).
Custom ROMs offer more than stock but bring their own issues/tweaking. Go read every one of the 1000000 threads on "stock vs. custom ROM" (think there's one going on in Q&A right now, actually).
If you want to switch from yakjuux to yakju, follow this guide: http://forum.xda-developers.com/showpost.php?p=21113773&postcount=195
I personally used this one to flash my Canadian model to yakju and it works great. It uses your PC (or Mac) + fastboot to flash the items in order. Be sure to follow all of the steps and flash all of the items. In order to receive OTAs (if that's important to you) you need them to all be flashed. Changing one (like recovery or radio) will stop OTAs.
If you need more info, the guide is pulled from this thread: http://forum.xda-developers.com/showthread.php?t=1464881
Sweet, thanks. That worked great.
I did notice a weird thing after rooting where my phone remained awake constantly even with the screen turned off. Not sure if it fixed itself though. I'll check again to see if the problem persists.
edit: It seems to be fixed now. Awesome.
I am a little bit concerned.
I have a GSM Unlocked Galaxy Nexus, and I know ICS 4.0.4 was released Mar 29. A lot of people have received their updates via OTA, but I have still not received mine. Every time I click "Check Now" on the software update, it tells me I am currently on the current version 4.0.2, which I know is not true.
I am pretty sure I have stock YAKJU firmware, but how I got was from flashing. At first my firmware was not Yakju, but from this site I was able to flash my phone and get Yakju. For some reason I am thinking what I flashed is not Google's Yakju but something else, even though the poster said it was stock.
I have been waiting for a long time, and still nothing, I really do not want to do it manually either, because I know it will erase everything on my phone.
My baseband is 19250XXKK6
Any suggestions? I mean I could wait longer, but idk when or if it will even update
P.S.
I know this is my first post, but I will try and be as active as I can on this site
Thanks!
Why wait (I don't know how / if you'll get the update, you might not)? Flash either the 4.0.4 factory image or a 4.0.4 rom and you're done.
smooth4lyfe said:
I am a little bit concerned.
I have a GSM Unlocked Galaxy Nexus, and I know ICS 4.0.4 was released Mar 29. A lot of people have received their updates via OTA, but I have still not received mine. Every time I click "Check Now" on the software update, it tells me I am currently on the current version 4.0.2, which I know is not true.
I am pretty sure I have stock YAKJU firmware, but how I got was from flashing. At first my firmware was not Yakju, but from this site I was able to flash my phone and get Yakju. For some reason I am thinking what I flashed is not Google's Yakju but something else, even though the poster said it was stock.
I have been waiting for a long time, and still nothing, I really do not want to do it manually either, because I know it will erase everything on my phone.
My baseband is 19250XXKK6
Any suggestions? I mean I could wait longer, but idk when or if it will even update
P.S.
I know this is my first post, but I will try and be as active as I can on this site
Thanks!
Click to expand...
Click to collapse
"Check Now" asks "Is *my* phone scheduled be updated?" rather than "Is an update available?"
OTA update are not all at once. I got mine yesterday- just be patient. It's not a huge difference, anyway, so just chill and don't think about it. It's not good to get so worried about a software update
I do not mind flashing 4.0.4 rom, but I have some questions
1. I do not want a custom rom because I still want OTA updates...is there the stock 4.0.4 rom I can flash? (Link?)
2. Will it erase all my stuff? (Not a big problem if it does, Ill back everything up
Have you tried this? Also, this app will tell you if you have yakju or something else.
luftrofl said:
"Check Now" asks "Is *my* phone scheduled be updated?" rather than "Is an update available?"
OTA update are not all at once. I got mine yesterday- just be patient. It's not a huge difference, anyway, so just chill and don't think about it. It's not good to get so worried about a software update
Click to expand...
Click to collapse
lol I know I just like having the most recent/updated stuff...maybe I will wait if its not that big of a difference, but because I flashed mine to YAKJU, thats why I am worried if I will even get the update or not
anton2009 said:
Have you tried this? Also, this will tell you if you have yakju or something else.
Click to expand...
Click to collapse
Yes I have checked with that app and it says I have YAKJU
Ah sorry. Weird link. I meant to link to this.
Hey Guys,
I'm riding on this thread with the same question.
I was previously running Yakjuwx and got fedup of waiting for Samsung to throw me a bone so I flashed to Yakju the other day.
I did, however, flashed it to 4.0.2 instead of 4.0.4, and then re-locked the bootloader again. My reason for doing so is to see if Google will officially recognize my device as a stock Yakju and offer an upgrade to 4.0.4 from there without me having to do a manual flash...if it allows me an official update I can safely assume that from here on out, Google's got my back for subsequent updates rather than having to do a flash everytime an update comes along.
Till now I've not received any news via OTA though. I've cleared the data of my Google Service Framework and restarted the phone a few times, but I'm still at 4.0.2.
Am wondering if I did something wrong. I've attached a screencap of my GNEX for reference. If you can't see, it:
Android Version
4.0.2
Baseband Version
I9250XXKK6
Kernel Version
3.0.8-gaaa2611
[email protected] 28 #1
Build Number
ICL53F
Anyone able to offer any assistance as to how I can "force" Google to give me an OTA?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
luftrofl said:
"It's not a huge difference, anyway"
Click to expand...
Click to collapse
2 coppers: 4.0.4 is a hell of a lot better than 4.0.2.
Screen rotation lag is fixed
Faster overall response times, esp with the stock browser
Extremely stable (random reboots)
I actually ran stock rogers 4.0.2 and refused to root and one day out of nowhere my gnex started bootlooping. Unlocked, cwm, 4.0.4 factory , rooted + power apps and I'm not looking back. This thing is a monster now lol
Sent from my Galaxy Nexus using xda premium
Also, would the serial number along with the bootloader being relocked be the reason why Google isn't updating my phone?
Attaching this information as well:
yeahyeahright said:
Hey Guys,
I'm riding on this thread with the same question.
I was previously running Yakjuwx and got fedup of waiting for Samsung to throw me a bone so I flashed to Yakju the other day.
I did, however, flashed it to 4.0.2 instead of 4.0.4, and then re-locked the bootloader again. My reason for doing so is to see if Google will officially recognize my device as a stock Yakju and offer an upgrade to 4.0.4 from there without me having to do a manual flash...if it allows me an official update I can safely assume that from here on out, Google's got my back for subsequent updates rather than having to do a flash everytime an update comes along.
Till now I've not received any news via OTA though. I've cleared the data of my Google Service Framework and restarted the phone a few times, but I'm still at 4.0.2.
Am wondering if I did something wrong. I've attached a screencap of my GNEX for reference. If you can't see, it:
Android Version
4.0.2
Baseband Version
I9250XXKK6
Kernel Version
3.0.8-gaaa2611
[email protected] 28 #1
Build Number
ICL53F
Anyone able to offer any assistance as to how I can "force" Google to give me an OTA?
Click to expand...
Click to collapse
I also have yakju on ICL53F tried that framework clear method - no luck - it seems that people with ICL53F have trouble getting the update
albert95 said:
I also have yakju on ICL53F tried that framework clear method - no luck - it seems that people with ICL53F have trouble getting the update
Click to expand...
Click to collapse
As covered previously in other threads, it seems as though the original IMM76D 4.0.4 OTA has been stopped because it causes radio drop-out problems with the screen off. Since the new OTA IMM76I has been pushed to fix these issues, we assume that there will be an OTA for 4.0.2 people straight to IMM76I 4.0.4.
You can always manually apply IMM76D then IMM76I if you want.
smooth4lyfe said:
I am a little bit concerned.
I have a GSM Unlocked Galaxy Nexus, and I know ICS 4.0.4 was released Mar 29. A lot of people have received their updates via OTA, but I have still not received mine. Every time I click "Check Now" on the software update, it tells me I am currently on the current version 4.0.2, which I know is not true.
I am pretty sure I have stock YAKJU firmware, but how I got was from flashing. At first my firmware was not Yakju, but from this site I was able to flash my phone and get Yakju. For some reason I am thinking what I flashed is not Google's Yakju but something else, even though the poster said it was stock.
I have been waiting for a long time, and still nothing, I really do not want to do it manually either, because I know it will erase everything on my phone.
My baseband is 19250XXKK6
Any suggestions? I mean I could wait longer, but idk when or if it will even update
P.S.
I know this is my first post, but I will try and be as active as I can on this site
Thanks!
Click to expand...
Click to collapse
Google rolls out the updates over a period of months. Yes, MONTHS. So, you could get it immediately, or you could get it in a few weeks from now. Now, you have two choices: 1) wait for Google to push it to your device; or 2) update it yourself by reading this thread.
By the way, as others have mentioned, locking or unlocking your bootloader has no impact on the OTA notification or update, but by locking it, you have just made your life more difficult.
efrant said:
Google rolls out the updates over a period of months. Yes, MONTHS. So, you could get it immediately, or you could get it in a few weeks from now. Now, you have two choices: 1) wait for Google to push it to your device; or 2) update it yourself by reading this thread.
By the way, as others have mentioned, locking or unlocking your bootloader has no impact on the OTA notification or update, but by locking it, you have just made your life more difficult.
Click to expand...
Click to collapse
Haha I know the feeling of waiting. I tried to manually flash 4.0.4 and ended up with an infinite boot loop animation. Something must have obviously gone wrong, but I was able to get 4.0.2 back on it and get up and running.
I'm now trying to just patiently wait for 4.0.4, but it's tough. I am very wary of trying to flash 4.0.4 on my handset again just because I don't want to end up with the infinite boot loop again. I check every night for a new update, do the checkin thing on the dialer, but no luck.
I am just hoping that I didn't screw anything up when I unsuccessfully tried to flash 4.0.4 that has somehow put my handset "out of favor" with google in terms of receiving the OTA update.
cyrusxs said:
[snip]
Haha I know the feeling of waiting. I tried to manually flash 4.0.4 and ended up with an infinite boot loop animation. Something must have obviously gone wrong, ...
Click to expand...
Click to collapse
That's because you didn't use my guide here.
cyrusxs said:
I check every night for a new update, do the checkin thing on the dialer, but no luck.
Click to expand...
Click to collapse
That does nothing. Assuming you are connected to Google's services (i.e., blue bars instead of gray), you'll get notified when your number comes up.
cyrusxs said:
I am just hoping that I didn't screw anything up when I unsuccessfully tried to flash 4.0.4 that has somehow put my handset "out of favor" with google in terms of receiving the OTA update.
Click to expand...
Click to collapse
I doubt you did.
efrant said:
Google rolls out the updates over a period of months. Yes, MONTHS. So, you could get it immediately, or you could get it in a few weeks from now. Now, you have two choices: 1) wait for Google to push it to your device; or 2) update it yourself by reading this thread.
By the way, as others have mentioned, locking or unlocking your bootloader has no impact on the OTA notification or update, but by locking it, you have just made your life more difficult.
Click to expand...
Click to collapse
Thanks Efrant.
I'm looking to take the more natural route cause I'm not much of a modder, the whole idea of me sticking to stock is to debunk the illusion a number of non-Android users have (including my friends) that they need to root and mod their phones in order to get it to perform adequately like iOS, and I like to prove that they don't have to, and that stock Android caters perfectly fine to the majority.
When you mean locking made things more difficult though, are you referring that it means I will have to redo the whole unlocking thing again if I wanted to perform a mod, or do you mean once I re-locked the phone, it can no longer be unlocked via the original method anymore? Cause if it's the former, I'm not that much concern as mentioned in my first para, but if it's the latter then..oops. =\
yeahyeahright said:
[snip]
When you mean locking made things more difficult though, are you referring that it means I will have to redo the whole unlocking thing again if I wanted to perform a mod, or do you mean once I re-locked the phone, it can no longer be unlocked via the original method anymore? Cause if it's the former, I'm not that much concern as mentioned in my first para, but if it's the latter then..oops. =\
Click to expand...
Click to collapse
Yes, I was referring to the former. The only thing that an unlocked bootloader affects is your ability to use fastboot commands. It does not mean you are modded, or rooted, or not stock. You ARE stock, you are NOT rooted, and there are no mods. But, you do have the ability to back up your data properly, you do have the ability to recovery any data in case something happens to your device, and a few other worthwhile features which you don't have if your bootloader is locked.
Now, you could always unlock if you need to, but that defeats the purpose, as everytime you unlock your bootloader, it does a complete wipe of your device, including /sdcard.
As an example, say you had some treasured photos on your device, which you have yet to back up to the cloud or wherever, and your locked-bootloader, unmodded, unrooted phone goes into a bootloop (which has happened). How are you going to get those photos off your device? You can't -- you are screwed. It order to retrieve them you need an unlocked bootloader... but to unlock your bootloader will wipe everything... See where I'm going here... Catch-22. With an unlocked bootloader, there are ways to recover those files.
efrant said:
Yes, I was referring to the former. The only thing that an unlocked bootloader affects is your ability to use fastboot commands. It does not mean you are modded, or rooted, or not stock. You ARE stock, you are NOT rooted, and there are no mods. But, you do have the ability to back up your data properly, you do have the ability to recovery any data in case something happens to your device, and a few other worthwhile features which you don't have if your bootloader is locked.
Now, you could always unlock if you need to, but that defeats the purpose, as everytime you unlock your bootloader, it does a complete wipe of your device, including /sdcard.
As an example, say you had some treasured photos on your device, which you have yet to back up to the cloud or wherever, and your locked-bootloader, unmodded, unrooted phone goes into a bootloop (which has happened). How are you going to get those photos off your device? You can't -- you are screwed. It order to retrieve them you need an unlocked bootloader... but to unlock your bootloader will wipe everything... See where I'm going here... Catch-22. With an unlocked bootloader, there are ways to recover those files.
Click to expand...
Click to collapse
Ah I see, thanks for the advice! I see the problems you highlighted regarding unlocking the bootloader again, I didn't have that problem cause I backed up my photos via dropbox auto upload and did a second backup, including 3rd party apps and data via MyBackup Pro, then unloaded the backup via usb onto my computer.
Guess since I've locked it for now there's no point unlocking it again, I'll wait until Google decides to drop me a bone and get me up to 4.0.4 then, for now 4.0.2's still a blast.
Thanks!
yeahyeahright said:
Ah I see, thanks for the advice! I see the problems you highlighted regarding unlocking the bootloader again, I didn't have that problem cause I backed up my photos via dropbox auto upload and did a second backup, including 3rd party apps and data via MyBackup Pro, then unloaded the backup via usb onto my computer.
Guess since I've locked it for now there's no point unlocking it again, I'll wait until Google decides to drop me a bone and get me up to 4.0.4 then, for now 4.0.2's still a blast.
Thanks!
Click to expand...
Click to collapse
Yeah, you knew that your data was going to be erased, so you used MyBackup. What happens in 2 months when you have more data on your device, and your device decides not to boot past the boot animation (not likely, but certainly possible)? Unless you back-up your app data and contents of your /sdcard automatically (like you do your photos) or on a daily basis, you will lose something. Just sayin'.
That's why I recommend to everyone to unlock the bootloader as soon as you take your device out of the box for the first time, even before you boot into the OS. Boot into the fastboot mode, unlock and be done with it. Never worry about it again. Even if you never plan to root or mod or install custom roms. It may save that one piece of data that you really wanted to keep, but forgot to backup.
Hi guys,
I used the GNEX toolkit to unlock my bootloader and then flash to 4.0.2 yakju. I'm just wondering why I'm not getting an OTA for 4.0.4 or 4.0.3. I've tried clearing the data in GoogleFrameWorkServices. I've also flashed stock recovery.
Did I do something wrong, or is there actually no update?. P.S I'm in Australia.
Any help would be greatly appreciated.
Im in the same boat.
I have flashed the completely stock 4.0.4 ROM from Google Code. I have not received the IMM76I update yet.
I have cleared the framework cache too and still nothing.
I live in Melbourne (australia) and I am assuming that the update to yakju devices works on a country-by-country basis.
IF I don't receive it soon, I am just going to hope Google Code gets updated and I will just reflash a the newer version.
I do not want to root the phone or using work-around methods to install an update. I like having a completely stock phone with a locked bootloader.
(Marshallaw.. Why not just download the 4.0.4 update from Google Code and flash using Fastboot? Atleast that way, you know your on the latest Android version and have a better chance of receiving the IMM76I update, or if worst comes to worst, just wait until Google Code is updated to the latest version and flash that?)
The way Google updates their devices is pretty pathetic. You would think they would push the update to every stock YAKJU device everywhere and not be so selective. My old Nexus S received 4.0.4 update and my stock Galaxy Nexus never received it, so I had to manually flash. Very stupid.
Simmo3D said:
[snip]
IF I don't receive it soon, I am just going to hope Google Code gets updated and I will just reflash a the newer version.
I do not want to root the phone or using work-around methods to install an update. I like having a completely stock phone with a locked bootloader.
Click to expand...
Click to collapse
I think you are confusing a few things:
1) What is posted on Google Code (as you put it), are NOT updates -- they are complete, full ROMs.
2) What is posted here are incremental update that UPDATE your existing ROM.
There is a difference between the two, despite the end result being the same.
3) Having an unlocked bootloader or a locked bootloader does not mean you are stock or are not stock -- it has nothing to do with it at all. You are not adding or taking away anything from the firmware on the device...
4) You say you do not want to use a work around to flash the update, but you are using a work around to flash a full ROM? Something there doesn't compute for me.
5) Flashing a stock update file does not make you any less/more stock than flashing a full ROM.
I don't think you understand what I meant.. Im hoping Google updated their full ROM with the IMM76I kernel and bug fixes...
hence, I am waiting for an updated full ROM that 'includes' the latest kernel update.
e.g. Google Code features :
4.0.1 (ITL41D) and 4.0.1 (ITL41F). I am waiting for
4.0.4 (IMM76D) and 4.0.4 (IMM76I) to be posted on their site.
I also know that having a locked bootloader does not make it stock, but my point was I am on stock 4.0.4 with a locked bootloader, so I am waiting for an OTA so I don't need to re-install all my files/apps.
But if I don't receive the OTA update, I will be reflashing the entire ROM once its available on Google Code.
Simmo3D said:
I don't think you understand what I meant.. Im hoping Google updated their full ROM with the IMM76I kernel and bug fixes...
hence, I am waiting for an updated full ROM that 'includes' the latest kernel update.
e.g. Google Code features :
4.0.1 (ITL41D) and 4.0.1 (ITL41F). I am waiting for
4.0.4 (IMM76D) and 4.0.4 (IMM76I) to be posted on their site.
I also know that having a locked bootloader does not make it stock, but my point was I am on stock 4.0.4 with a locked bootloader, so I am waiting for an OTA so I don't need to re-install all my files/apps.
But if I don't receive the OTA update, I will be reflashing the entire ROM once its available on Google Code.
Click to expand...
Click to collapse
Well, I'm not sure if this is it but here's the OTA package for IMM76I from IMM76D. It might just be a test build which was only pushed to small portion of users to test it which would explain not everyone getting it.
And Marshalllaw, you've already begun to flash things and mess around, why not just flash the stock build of 4.0.4 straight away rather than relying on an OTA?
Simmo3D said:
[snip]
I also know that having a locked bootloader does not make it stock, but my point was I am on stock 4.0.4 with a locked bootloader, so I am waiting for an OTA so I don't need to re-install all my files/apps.
But if I don't receive the OTA update, I will be reflashing the entire ROM once its available on Google Code.
Click to expand...
Click to collapse
Ok, but you do realize that manually installing the IMM76I update (which you can do right now, although requires an unlocked bootloader) ends you up at the exact same place the flashing the IMM76I image when it comes out (and it will still require an unlocked bootloader). So whether you install the update, or what for the full image, you will still wipe, and you will end up at the same place -- you will just get there sooner with the update.
OK but how do you flash this with fastboot once I unlock my boot loader. I need to boot with CWM don't I?
Sent from my Galaxy Nexus using xda premium
Simmo3D said:
OK but how do you flash this with fastboot once I unlock my boot loader. I need to boot with CWM don't I?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Correct, you do. But booting CWM is different from flashing CWM. When you boot it, you are not "writing" anything to your device - you are only loading the kernel and ramdisk into your device's RAM. It only boots CWM one time - as soon as you reboot, it is no longer there, as it was never flashed - it just existed in RAM.
Additionally, even if you did flash it, it still wouldn't be there when you rebooted, because EVERY OTA update adds two files to your device that automatically re-flash the stock recovery on EVERY boot of your device.
Unlawful said:
Well, I'm not sure if this is it but here's the OTA package for IMM76I from IMM76D. It might just be a test build which was only pushed to small portion of users to test it which would explain not everyone getting it.
And Marshalllaw, you've already begun to flash things and mess around, why not just flash the stock build of 4.0.4 straight away rather than relying on an OTA?
Click to expand...
Click to collapse
Hi Unlawful. Yeah I can always flash it directly to 4.0.4, its more that this is my first Android phone / first experience messing with bootloaders and roms. I was more so just wondering if the lack of OTA update to either 4.0.3 or 4.0.4 was that i've screwed something up or that the update has not been pushed to all devices.
My device info is: 19250XXKK6, ICL35F. Its basically the same as when I first bought it but not Yakjuwx. I more or less flashed to Yakju because people were saying that you could get OTA updates faster or something.
Thanks for the help, sorry if this is a noob question.
I wouldn't be too sure though I would really doubt it's something that you did. Have you pressed 'Check Now' somewhere in settings to check whether there's an update?
Unlawful said:
I wouldn't be too sure though I would really doubt it's something that you did. Have you pressed 'Check Now' somewhere in settings to check whether there's an update?
Click to expand...
Click to collapse
Yeah I hit check now and it always says I'm the most up to date. I tried clearing data in google services framework and then hitting check now. Nothing changed.
I just find it odd that I wouldn't get an OTA for 4.0.3.
I used the GNEX toolkit to flash the stock rom which I got from developers.google.com/android/nexus/images. I read online that someone thought that 4.0.4 was pulled from OTA, but I would have thought I would get 4.0.3. I'm nervous that I've messed something up lol
marshalllaw said:
Yeah I hit check now and it always says I'm the most up to date. I tried clearing data in google services framework and then hitting check now. Nothing changed.
I just find it odd that I wouldn't get an OTA for 4.0.3.
I used the GNEX toolkit to flash the stock rom which I got from developers.google.com/android/nexus/images. I read online that someone thought that 4.0.4 was pulled from OTA, but I would have thought I would get 4.0.3. I'm nervous that I've messed something up lol
Click to expand...
Click to collapse
4.0.3 was never released in OTA form.
Unlawful said:
I wouldn't be too sure though I would really doubt it's something that you did. Have you pressed 'Check Now' somewhere in settings to check whether there's an update?
Click to expand...
Click to collapse
That does not work. You will have to wait until Google decides it's time for your IMEI to receive it...
marshalllaw said:
Yeah I hit check now and it always says I'm the most up to date. I tried clearing data in google services framework and then hitting check now. Nothing changed.
I just find it odd that I wouldn't get an OTA for 4.0.3.
I used the GNEX toolkit to flash the stock rom which I got from developers.google.com/android/nexus/images. I read online that someone thought that 4.0.4 was pulled from OTA, but I would have thought I would get 4.0.3. I'm nervous that I've messed something up lol
Click to expand...
Click to collapse
You did not mess anything up. As martonikaj said, there was never any 4.0.3 update.
Updates are not rolled out to everyone all at once. It could take seconds or MONTHS before you get the OTA, after the first person gets it.
Awesome . Thanks for the help guys.
Having an Android is great for all the exploring you can do, finding out how it works though can be a bit daunting.
Sorry for the noob question!.
I just bought GNex, and I'm already a bit angry. I know what most of you will say, but I'd like an answer to something I couldn't find on the forum.
Basically, I booted the phone and thought I'll just update from it's stock firmware to 4.2.1, I go to update menu and system detects an update... to 4.1. No worries I think, maybe I have to do it one step at a time, so I download and restart. But mid way through the update I get a screen with a dead Droid and an exclamation mark over it. What is going on?
I've read threads about update, and how to rush the update and get it directly from google, but as far as I know, my device is a stock "maguro" with stock "yakju" soft (no additional letter here). Check for yourself, here's a screenshot:
http://i48.tinypic.com/257jaqc.png
What I am afraid of is that even if I root, and push the update it will still freeze during it.
Please advise, as I couldn't find an answer to fix this thing, and I would prefer not to be forced to root/unlock bootloader to do it if not necessary.
Thank you for your help.
Just found something peculiar - so my device is "maguro" (GSM), but the stock firmware it came with is 4.0.4 yakju version, build IMM76K.
I checked different firmwares, and it seems that build was only released for mysid devices (the CDMA/LTE for Verizon/Sprint). huh...
I doubt you'd have a CDMA /LTE rom successfully running on a GSM phone. That's usually when the device becomes a paperweight. I highly suggest efrants guides to updates, stickied at the top of the forum. I know i've heard that yakju is always a bit behind takju, also depending on locale. And i do believe updates are done incrementally. But if you're getting some unknown error in the ota, your primary option is to unlock and root, then DIY. Otherwise, it sounds like you wont be getting any updates. If you're concerned about losing data, there was a method for ICS unlocking without wipe, a vulnerability. Look for it, and read!
bodh said:
I doubt you'd have a CDMA /LTE rom successfully running on a GSM phone. That's usually when the device becomes a paperweight. I highly suggest efrants guides to updates, stickied at the top of the forum. I know i've heard that yakju is always a bit behind takju, also depending on locale. And i do believe updates are done incrementally. But if you're getting some unknown error in the ota, your primary option is to unlock and root, then DIY. Otherwise, it sounds like you wont be getting any updates. If you're concerned about losing data, there was a method for ICS unlocking without wipe, a vulnerability. Look for it, and read!
Click to expand...
Click to collapse
Thanks. Already done it, updated to latest takju version. I would suggest adding and information about errors with OTA, and directing people to efrants guide.
Who knows why, but sometimes the otas just fail. I've had it happen myself, even when i think i havent modified anything. Anyway, glad to hear about your success!