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
I am currently using N7 FHD (2013) with JWR66N 4.3 jellybean. I have just UNLOCKED BOOTLOADER but NOT ROOT or install any RECOVERY.
ALL ARE STOCK ROM, STOCK RECOVERY JUST BOOTLOADER UNLOCKED.
After that I got a CLEAN (Wiped) nexus. and I got a 5X MB OTA from google and I reboot. but after that, the android robot lied down and showing a RED ! icon and "ERROR".
I rebooted my device, it starts up normally.
IS THAT I CANNOT USE OTA AFTER UNLOCKED THE BOOTLOADER????
WHAT IS THE CURRENT NEWEST BUILD NUMBER FOR NEXIS 7 2013 FHD 32GB??
how can I get that OTA again???
If you really didn't modify or remove any of the stock files, then you are probably suffering from the JWR66N won't update to JSS15J problem mystery we are trying to figure out here:
http://forum.xda-developers.com/showthread.php?t=2380258
We know that it is caused by a file on your tablet being different than what is expected and we know how to workaround the problem. We just don't know why it is happening in the first place.
If you want to help solve the mystery, post on that thread.
If you just want to get JSS15J it may be quicker to just use the JSS15J factory restore here:
http://developers.google.com/android/nexus/images#razor
(factory restore will wipe your data so back up first)
Thanks for your info.
I think i can re unlock my bootloader again.
I am afraid that BL unlocked cant enjoy OTA and now i understand thats the OTA file error from google and not mine.
But google is still so stupid that they cant reconize my OLD (non full HD 2012) nexus and new 2013 nexus. They both have same names in google play store. Thats weird
Sent from my Nexus 4 using xda app-developers app
I think you understood properly, but I didn't answer your question directly, so to be clear, the OTA, under normal circumstances, would work fine on a tablet with unlocked bootloader (unless files were modified or removed)
What we are trying to figure out is why for some tablets there is a rare occurrence of a file not matching the shipped set of files that everyone else has. It is usually just one file, /system/app/PrebuiltGmsCore.apk, but there was one example of someone having the same issue with /system/lib/libchromeview.so
Hi folks! Just received a 2013 Nexus 7 from my fiancé as a birthday gift. I wanted it for quite specific purposes so was hoping I could ask a few questions here and get pointed in the right direction before I start using this thing
I intend to mainly use the tablet for remote play with my PS4 and emulating old console games. Since I want to connect a PS4 controller to it wirelessly I'm told I need to root the device. I'm guessing this is an easy process and there are some guides on the site here?
The main thing I was after advice about is firmware updates. The system came on 4.3 and has already downloaded an update for 4.4.2 but I haven't installed that yet. Is this firmware fine to upgrade to? Any performance issues? I've heard people saying that upgrading their Nexus to 5+ (Lollipop?) has created a load of performance issues and this should be avoided? Also, if I upgrade to a certain firmware version can I lock myself out of being able to root the device? I'm pretty sure all of the apps I was planning on using work no 4.3 so I have no reason to upgrade at all but if I can go safely to a higher firmware that is reliable with no performance issues I may as well?
First time using an Android device so sorry if my questions come off as a little stupid. Also, wasn't sure if I should post this here or if it should be on the Q&A board so sorry if I've got that wrong!
As far as I know, the problems with lollipop were the standard number of complaints that come with any new release. Well, I'm not really positive, but lollipop seems fine to me and I think most people have upgraded by now. I would go for it because I think it's really fun to use.... Plus you can always revert if you choose.
As far as rooting, you never need to worry about not being able to do it... Rooting your Nexus 7 will always be easy. The by-hand method is fun and relatively simple, or you can just use the toolkit in the forum to do it even easier.
^Yeah I'll echo that. Lollipop is good. The people having problems don't know what they're doing. Flash the factory image.
If you want root you can use cfautoroot or simply flash twrp with fastboot then flash the su.zip
Personally, I'd stick go for 4.4.4, as 5, 5.0.1 & 5.0.2 all have a memory leak issue. You may also find more emulator compatability as Kit Kat has been around a year longer than Lollipop. The only downside to KK over L is the battery life is a little worse IMO.
I dont think the memory leak issue is a result of someone not knowing what they are doing etc.
Thanks for all the advice everyone
yosmokinman said:
^Yeah I'll echo that. Lollipop is good. The people having problems don't know what they're doing. Flash the factory image.
If you want root you can use cfautoroot or simply flash twrp with fastboot then flash the su.zip
Click to expand...
Click to collapse
I'm fairly competent with computers (as I should be with a degree in computer science!) but this is all like a foreign language to me. I guess I'm better sticking with the toolkit for now until I'm familiar with all the lingo?
Masteryates said:
Personally, I'd stick go for 4.4.4, as 5, 5.0.1 & 5.0.2 all have a memory leak issue. You may also find more emulator compatability as Kit Kat has been around a year longer than Lollipop. The only downside to KK over L is the battery life is a little worse IMO.
I dont think the memory leak issue is a result of someone not knowing what they are doing etc.
Click to expand...
Click to collapse
Thanks. This is the sort of advice I was after and is why I mentioned what I was planning on using it for. The device has already downloaded 4.4.2 and wants to update to that. Is there a way I can manually go to 4.4.4? I'm worried it will just request an update from the Google server and try to jump straight to a version of 5
chunk3rvd said:
Thanks. This is the sort of advice I was after and is why I mentioned what I was planning on using it for. The device has already downloaded 4.4.2 and wants to update to that. Is there a way I can manually go to 4.4.4? I'm worried it will just request an update from the Google server and try to jump straight to a version of 5
Click to expand...
Click to collapse
If you unlock the bootloader then familiarise yourself with ADB and flashing factory images, you can manually flash any version of Android (That has been availible for your device,) manually. You dont need to be rooted to do this.
It also allows you to go back when you've made the mistake of updating, (but does wipe all of your data!)
It ended up offering me the updates incrementally anyway. I went from 4.3 > 4.4.2 > 4.4.3 > 4.4.4 which I'm currently on and will leave it there for now. It's downloaded 5.0.2 but I've skipped the install for the time being
Think I need to do a little reading up before I root the device as I haven't got a clue what some of you are talking about haha. Thanks for all the advice so far though
No problems.
I've had a few Nexus devices and never felt the need to root them. :angel:
yosmokinman said:
^Yeah I'll echo that. Lollipop is good. The people having problems don't know what they're doing. Flash the factory image.
If you want root you can use cfautoroot or simply flash twrp with fastboot then flash the su.zip
Click to expand...
Click to collapse
The majority of problems stem from Qualcomms crappy broken mess Adreno gpu drivers, hence the delayed
rollouts of Android for the Nexus 4 and 7 that both use the Adreno 320, don't be suprised if the Nexus 4 and 7 get a
Android 5.1.1 release instead.
For ppl new to nexus devices, wugfresh nexus root toolkit is a great tool until you get the hang of adb and fastboot. With a nexus you can always switch between android versions. You can always root, or go back to older versions of android. Updating to newer versions never hurts anything because you can always go back. Its a developers device so its very versatile. Try lollipop if you like, (I love it) and if its not your thing, just flash back to 4.4.4. I love this tablet.
madbat99 said:
For ppl new to nexus devices, wugfresh nexus root toolkit is a great tool until you get the hang of adb and fastboot. With a nexus you can always switch between android versions. You can always root, or go back to older versions of android. Updating to newer versions never hurts anything because you can always go back. Its a developers device so its very versatile. Try lollipop if you like, (I love it) and if its not your thing, just flash back to 4.4.4. I love this tablet.
Click to expand...
Click to collapse
You for got to mention the disclaimer if your tab came with 5.x.x out of box you cant go back to KK. Also a lot of us who recently bought Nexus 7, I have 3 that I have acquired, came with 5.0.1 installed are having issues with partitions/memory mounting in recovery. Some sort of revision done in the latest batch sent out. If his tab came with 5.0.1 or higher and has his bootloader at FLO 4.04 he may have problems trying to go back with either bootloops and what not.
masterchiefb117 said:
... with 5.0.1 installed are having issues with partitions/memory mounting in recovery...
Click to expand...
Click to collapse
Seems to be solved in TWRP_multirom_(flo|deb)_20150328 (updated to 2.8.6.0)
See http://forum.xda-developers.com/showpost.php?p=45886569&postcount=1