yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Winesnob:
So am I. For fun, decided to give Verizon a call this evening. Spoke with Scott, who initially said the problem was between Samsung and Google. I disagreed, stating that source code was available from Google but had not been approved by Verizon yet. After spending 10 minutes or so on hold while Scott "looked into the issue" he came back told me that I was correct and Verizon was the holdup. According to his technical manager, Verizon is not yet happy with certain aspects of the Jellybean build and will not approve it for release yet.

From the horse's mouth, and the first time a service rep actually admitted to me that it was Verizon's fault. And so we wait.

[And for a few of the readers out there - I'm on stock 4.0.4 and the call did not drop nor did the mic mute.]:D
[Samsung Galaxy Nexus] efrant:
Although that is good info, and I am sure you are correct, the bottom line is: it makes no difference, nor does it matter. Whether it's Samsung that's the problem, or whether it is Google, what does it change? The source is out, so someone who wants JB can compile it. Someone who wants to wait, can do that as well. But making a stink about it is probably a waste of time and effort in my opinion.
[Samsung Galaxy Nexus] tailsthecat3:
If I could compile it, I would.
[Samsung Galaxy Nexus] efrant:
You could compile it yourself (http://xdaforums.com/showthread.php?t=1386615 and it would be a great learning experience) or you could use one of the ROM's in the Sprint Dev section, or you could ask one of the Sprint devs to compile you a straight AOSP build with no mods. The choice is yours.
[Samsung Galaxy Nexus] tailsthecat3:
Sounds fun! I don't have the system for that. :(
[Samsung Galaxy Nexus] oldblue910:
Verizon mysid JRO03O from IMM76Q: http://android.clients.google.com/p....signed-mysid-JRO03O-from-IMM76Q.4a91da6c.zip

This is a testing build. All the credit goes to El Madhatter.
[Samsung Galaxy Nexus] efrant:
Great, thank! First post updated.
[Samsung Galaxy Nexus] tailsthecat3:
This update is awesome. This zip flashed the new radios and I got a signal seemingly twice as fast as before upon boot up. Everything is nice and smooth. Didn't check on the bootloader version though. Multitasking is a dream now.
[Samsung Galaxy Nexus] oldblue910:
Courtesy of forum member dark vertical, here's the mysidspr Jelly Bean update: http://android.clients.google.com/p...7ebe470d64e7.update_mysidspr_FG01_to_FH05.zip
[Samsung Galaxy Nexus] chaotic646:
When I try this on my sprint nexus it says cannot load 'cwm.img'. I chose the cwm from the second link for cdma/lte devices, renamed, and placed it on the root of my sdcard along with the update. Any suggestions?

EDIT: Never mind, just got the OTA!
[Samsung Galaxy Nexus] efrant:
Glad you got it!

By the way, the CWM that you tried is not for toroplus, it is for toro.
[Samsung Galaxy Nexus] chaotic646:
Oh ok...is there one for the toroplus in case I need it in the future?
[Samsung Galaxy Nexus] efrant:
Use CWM or TWRP for your device. You can probably find links to them in the Sprint Dev section.
[Samsung Galaxy Nexus] rashire:
Thanks! Just got the FH05 mysidspr update in for jellybean with the revised method 1. Went in perfectly. CWM persisted, and CWM also saved my su.
[Samsung Galaxy Nexus] Rakeesh_j:
So either one works with method 1? You don't need a specific version?
[Samsung Galaxy Nexus] efrant:
I believe the latest versions of CWM and TWRP will work. (I put that note in there, as the touch-based CWM recoveries post 5.5.0.x and pre 6.x caused issued. I don't have a toroplus device, so I can't tell you if either or both will work. Try them out and let us know. Either it will work and install the update, or it won't and nothing will happen.
[Samsung Galaxy Nexus] wraithdu:
I used a slightly different method on my Verizon Nexus... I booted into Clockwork with 'fastboot boot cwm_whatever.img', made sure /cache was mounted, then used the root adb shell to copy the OTA to the /cache partition. Then 'adb reboot recovery' to boot stock recovery and install the OTA. No problems or compatibility issues that way.
[Samsung Galaxy Nexus] Rakeesh_j:
Modified method 1 works with TWRP 2.2.2.0 (which is the latest as of this posting.)
[Samsung Galaxy Nexus] efrant:
Thanks, I will make a note of that in the first post.
[Samsung Galaxy Nexus] :
My friend says thank you very much :)
[Samsung Galaxy Nexus] cyclonemon:
Please update

this link is OTA of yakjuxw from IMM76K(4.0.4) to JRO03C(4.1.1)

In Thailand Area

http://android.clients.google.com/p...ad6c75080.update_yakjuxw_IMM76K_to_JRO03C.zip

160.26 MB
[Samsung Galaxy Nexus] efrant:
Thank you. First post updated.

I know a lot of folks have been waiting for that one!
[Samsung Galaxy Nexus] chrone:
Thanks for the update. I believe all GNex sold in Indonesia are using yakjuxw build too.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Cool! What radio did you guys get with yakjuxw?

Also, I can't believe nobody has posted the final yakjuux OTA URL... I guess everybody savvy has already moved to yakju! :laugh:
[Samsung Galaxy Nexus] chrone:
Same as yakju/takju, XXLF1. Still having too many wakeups from com.android.phone though, 307 times in 23 hours. :/

Ericson builds the majority of our 2G/3G networks here, perhaps that's why Samsung uses XX baseband.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] efrant:
First post updated with official yakjuux Jelly Bean update (JRO03C-from-ICL53F).
[Samsung Galaxy Nexus] nkhatri50:
Hi,

I have an unlocked and rooted Verizon Galaxy Nexus running 4.0.4 with Build Number IMM76K. I also have CWM for recovery. What I want to do, if I understand the first post, is to flash mysid 76Q and then mysid JRO03O to get Jelly Bean. Method 3C seems to be the easiest way. Can I use it even though I have an unlocked bootloader? And do I have to wipe any of the cache (I ask because I remember having to do that to my Hero when I flashed Cyanogen to it)?

Thanks!
[Samsung Galaxy Nexus] efrant:
Yes and yes. And You can wipe cache if you want but not required. Remember to flash the su zip right after flashing the second update to retain root.
[Samsung Galaxy Nexus] johndawace:
Which one is my devices?
[Samsung Galaxy Nexus] spaceman860:
maguro

Sent from my BAKED Nexus
[Samsung Galaxy Nexus] efrant:
You are running yakjujp. There is no JB update yet for the build you are currently running.
[Samsung Galaxy Nexus] johndawace:
So? What am I do upgrade to JB 4.1 ?
[Samsung Galaxy Nexus] efrant:
You can either wait for the update to become available. or convert to yukju as per this guide.
[Samsung Galaxy Nexus] oldblue910:
Efrant, the official Verizon Gnex support site (http://www.verizonwireless.com/galaxynexussupport) has been updated with official documentation. That means the JB update is a go. You may as well color code the JRO03O from IMM76Q green and remove the bit about it being a testing build. I've got aLogCat installed on my phone running IMM76K so if nobody else gets it first, I'll grab the JRO03O from IMM76K link when it comes.
[Samsung Galaxy Nexus] Rican7:
Logcat Grep

I'm currently doing the Android community a good deed. :)
[Samsung Galaxy Nexus] waylo:
I'll give it another try.

I did initially use window's native zip browser to delete+replace, so that may have done some silly things. Trying again with 7-zip.

EDIT: Oh, the updater script a few pages back is not with the latest OTA! You may want to update, or at least differentiate which update it can be used with.
[Samsung Galaxy Nexus] FormelLMS:
for the first round of the latest Rom. I think, there's no difference.
[Samsung Galaxy Nexus] Mautflucht:
I compared both zips and besides the signature and updater files, I found only one difference: the file '/system/vendor/firmware/smc_pa_wvdrm.ift' is included as a complete file in the new version and applied as a patch in the old one (/patch/system/vendor/firmware/smc_pa_wvdrm.ift.p)
[Samsung Galaxy Nexus] waylo:
Looks like I finally got it running... after 15+ reboots/etc!

1. Had to use 7-zip to edit the existing .zip file

2. Had to use notepad++ to edit the updater-script as I'm in Win7. Notepad and WordPad did not work and resulted in a "Status 6" error due to the updater-script not being in a unix-friendly format

EDIT:

Yay, looks like I'm updated to... V4.0.1?!?!

So, kernel version is updated. But build # is still on ITL41F, and version is still 4.0.1. Is it possible the build.prop wasn't updated, but everything else was?

Bootloader is updated too. And browing through system directories it looks like framework and others folders have dates from right now.

So, looks like files were updated, just the 'about phone' display was not.

EDIT2:

Looking at the update script, looks like it can only update whatever is pure stock. So by removing all the assert checks, it will proceed with framework and library replacements, but any other system apps or system editable files that have been altered will be left alone. I did add some revisions to my build.prop, so that's why it didn't get updated.

Could someone with an official yakju ICL53F build.prop share?
[Samsung Galaxy Nexus] Mautflucht:
That's mine, updated to 4.0.2 using the initial first version.
[Samsung Galaxy Nexus] FormelLMS:
Isn't it better to use the old build.prop, when you wanna update to the newest one?

yakju ICL53F from ITL41F

What do you think? I've read, that I don't have the full update, when I uncheck the assert checks? Do I have to update again? Whats going on, when I wannado next updates?
[Samsung Galaxy Nexus] efrant:
This is why I don't recommend removing the asserts for anything besides the radio and/or bootloader...
[Samsung Galaxy Nexus] FormelLMS:
And what would you suggest? Pushing the old build.prop and reflashing the latest update?

Do you think, this is a good idea?

Or can I see, if my apps are updated?

Send from my iphone5s
[Samsung Galaxy Nexus] efrant:
Well, if you know what files were not updated, you could replace them with the ones from the ICL53F build.

Otherwise, your best bet is probably just to re-flash the ICL53F image from here
[Samsung Galaxy Nexus] waylo:
Excellent points all around efrant.

For me, I'd forgotten how many system apks and such I'd modified (not THAT many, but it was hard to recall what exactly). I suppose one can run the minimally modified updater-script with the update .zip, and just note each warning separately, go back and copy the original over, repeat. (But I was feeling a tad too lazy for that =P) To my recollection, I probably had just altered my MMS.apk and build.prop.

After the fact, it looks like some of the patch files are just patches, and not apk replacements. So, it's essential that the originals are "original."

One important thing to note, which isn't entirely clear, is while it checks to make sure the files it will update are there, that it won't remove any additional system apks you've added.
[Samsung Galaxy Nexus] efrant:
Although I'm not 100% certain, I'm pretty sure that it will not remove any additional files that you have added. It certainly does not remove the root files, so I doubt that it will remove other system apps that you have installed. What it will do, however, is change the permissions on the files, so some may not work properly until you change the permissions back to what you had them before.
[Samsung Galaxy Nexus] hongkongtom:
Great job OP, thanks for getting these things together.

Yet, another question though, if I were to flash Full (not OTA) Stock rom coming from earlier stock rom but same yakju version, would it be possible to flash without wiping( or at least keeping internal storage?)

Assuming I've already rooted, unlocked,CWM, custom kernel (these could be reverted anyway)

Thx

Sent from my Galaxy Nexus

ICL53F (JameBond 1.2-307)

4.0.2

Rooted & CWM

Stock rom
[Samsung Galaxy Nexus] efrant:
I suppose it's possible if you only flash the system.img file, and not the userdata.img file, but who knows what additional files Google will add to the /data partition in the future, so it wouldn't be my preferred method. Using ota updates is safer and just as simple.
[Samsung Galaxy Nexus] youchi1:
Hi, I followed all the steps in number two. Unfortunately it did not work because I used the wrong zip. My problem now is that I cannot access my /sdcard file for a second time to change the zip. Any idea on how to find the folder in windows explorer when I connect my phone?
[Samsung Galaxy Nexus] efrant:
What do you mean you can't access the /sdcard file? When you start the steps from the beginning, you should be able to see it in CWM, no?
[Samsung Galaxy Nexus] phexren:
Hi,

I currently have stock yakjuux ITL41F 4.0.1 rooted with the bootloader unlocked and CWM installed. I've tried flashing to ICL53F using the instructions provided but I get the error "installation aborted". Does this method work for yakjuux ROMS?

Thanks
[Samsung Galaxy Nexus] efrant:
There is no OTA update to ICL53F for yakjuux. Where did you get the idea that there was?
[Samsung Galaxy Nexus] phexren:
From a misreading of your original post. My apologies...
[Samsung Galaxy Nexus] k_myk:
URL for yakjuXW:

http://android.clients.google.com/p...26c617b15.update_yakjuxw_ITL41F_to_ICL53F.zip

I wonder wtf is "proxima" o.O
[Samsung Galaxy Nexus] oldblue910:
...and would there happen to be an entry in there that contains JRO03O-from-IMM76K? ;)
[Samsung Galaxy Nexus] Rican7:
haha, not yet, unfortunately

I'm gonna keep trying to do the Google Services Framework cache clearing. Maybe that'll work. :P

---------- Post added at 03:38 PM ---------- Previous post was at 02:57 PM ----------

http://android.clients.google.com/packages/ota/verizon_prime/60fc80848c8e.signed-mysid-JRO03O-from-IMM76K.60fc8084.zip

You LOVE me, internet. :P
[Samsung Galaxy Nexus] efrant:
You da man!

EDIT: First post updated.
[Samsung Galaxy Nexus] oldblue910:
THANK YOU! I'm mirroring on randomphantasmagoria.com as I speak.
[Samsung Galaxy Nexus] Rican7:
Thank you!

I see you added me to the "thanks" section in the first post.

Thanks for the props!

:D
[Samsung Galaxy Nexus] thepolishguy:
Thanks. I returned to stock and thought I could patiently wait for the update. But of course I couldn't. Thanks for helping a brother out.
[Samsung Galaxy Nexus] dureyes:
Galaxy Nexus on IMM76K

Done, it worked like a charm. All OK and loving Jelly Bean goodness. Thank you.
[Samsung Galaxy Nexus] Surin1221:
Rooted without bootloader unlock, updated from IMM76K and this is working like a dream. Have to wonder why VZW would wait so long for JB cuz this is great
[Samsung Galaxy Nexus] kibmcz:
Here is the Yakjuux ITL41F to JRO03C captured from my Sasktel (Bell) Galaxy Nexus).

http://android.clients.google.com/p...7fbb476c7.update_yakjuux_ITL41F_to_JRO03C.zip
[Samsung Galaxy Nexus] efrant:
Great, thank you!!

First post updated.
[Samsung Galaxy Nexus] HisDudeness710:
Thank You

Excellent! The update could not have gone more smoothly.
[Samsung Galaxy Nexus] jimhois:
which method to flash

I have the IMM76K Build. My bootloader is unlocked I have root and cwm touch 5.8.0.2 installed. which method should i use to flash to 60fc80848c8e.signed-mysid-JRO03O-from-IMM76K.60fc8084.zip

-Jim
[Samsung Galaxy Nexus] efrant:
Whichever one you want! Pick the easiest one for you. Prob 3c...
[Samsung Galaxy Nexus] jimhois:
CWM

As I understand, I can't use cwm 5.8.0.2 touch, Do I need to go to a different version of CWM?
[Samsung Galaxy Nexus] Zepius:
you can use it, but there have been some problems reported with it.

generally go with the non-touch CWM.. i think its 5.5.x.x
[Samsung Galaxy Nexus] Edwrib:
JRO03R is out, anyone got?
[Samsung Galaxy Nexus] efrant:
There is no JRO03R OTA. Latest for maguro is JRO03C and latest for toro is JRO03O.
[Samsung Galaxy Nexus] Edwrib:
This will no be available as OTA?

https://developers.google.com/android/nexus/drivers#magurojro03r
[Samsung Galaxy Nexus] efrant:
The latest source pushed to AOSP is JRO03R I believe. There's is no OTA, and there likely won't be to that version - next ota will probably be newer.
[Samsung Galaxy Nexus] tailsthecat3:
So, I saw some binaries posted for the Toro listed as JRO03R. Not sure if it's been posted or what this means for the future...

https://developers.google.com/android/nexus/drivers#toro
[Samsung Galaxy Nexus] Winesnob:
Probably not much. The Nexus S 4G was updated with build JRO03R, so my guess is the CDMA binaries were the primary culprit for the change.
[Samsung Galaxy Nexus] ciprianruse88:
do i have to flash gapps if i want to update to latest jelly bean release?and to update to jro03c i don't have to delete anything from the arhive like it says here ''2) Open the archive and delete the recovery folder; EDIT: Do NOT do this step if it is the JRO03C or JRN84D updates you are using.''...sorry,i've just moved from my s2 to gnex and thing are new here.
[Samsung Galaxy Nexus] efrant:
1) These updates are for stock ROMs only. So if you have a stock ROM, gapps are included.

2) Just follow the steps and you will be fine.
[Samsung Galaxy Nexus] PitBeast:
Today yakjuxe updates IMM76K -> JRO03C hxxp://android.clients.google.com/packages/ota/samsung_proxima_yakjuxe/d7334b6f4cac.update_yakjuxe_IMM76K_to_JRO03C.zip
[Samsung Galaxy Nexus] shakalaca:
yakjuzs update to Jelly Bean

Got OTA today, from IMM76K to JRO03C

hxxp://android.clients.google.com/packages/ota/samsung_proxima_yakjuzs/0de88f024193.update_yakjuzs_IMM76K_to_JRO03C.zip
[Samsung Galaxy Nexus] efrant:
Thanks shakalaca! First post updated.
[Samsung Galaxy Nexus] demzzy:
hmmm is there gonna be an ota update for yakju to 4.1.2 also?
[Samsung Galaxy Nexus] osm0sis:
I wouldn't hold your breath, but it's a possibility.
[Samsung Galaxy Nexus] oldblue910:
Just like the previous OTAs there will be an update for yakju, takju and mysid. You can take that to the bank.
[Samsung Galaxy Nexus] tailsthecat3:
Can't wait to flash.
[Samsung Galaxy Nexus] mbirth:
A factory image for the takju maguro is already available: https://developers.google.com/android/nexus/images#takju … an official OTA can't be far away…
[Samsung Galaxy Nexus] shakalaca:
M420 (yakjukr) IMM76K to JRO03C

FYI :)

hxxp://android.clients.google.com/packages/ota/samsung_proxima_yakjukr/9af1e0fc82a1.update_yakjukr_IMM76K_to_JRO03C.zip
[Samsung Galaxy Nexus] efrant:
You da man! Thanks. First post updated.
[Samsung Galaxy Nexus] segv11:
A factory image before the corresponding OTA? That's very unusual, and very cool. Thanks, JBQ!

Sent from my Bugless toro Beast.
[Samsung Galaxy Nexus] oldblue910:
Believe it or not, though rare, this isn't the first time it's happened. Google actually released factory images of Gingerbread 2.3.6/GRK39F for the Korean Nexus S despite it never being officially released as an OTA for that device variant. Officially, that model was stuck on 2.3.4/GRJ22 until being upgraded to Ice Cream Sandwich. On a slightly humorous note, that M200 Korean variant of the Nexus S gets updates at an unbelievably slow pace. It's subject to carrier approval (SK Telecom I believe) and that approval process is so slow, it makes Verizon and Sprint look downright speedy by comparison. Generally when the Nexus S worldwide models get an OTA, the Korean model has sometimes taken 3-4 months to receive the same OTA. It's insane.
[Samsung Galaxy Nexus] kibmcz:
The odd part is wheres yakju?? I guess international one is 2nd rate to the play store sold one LOL.
[Samsung Galaxy Nexus] olenchenko:
Hes anybody tried (installed) 4.1.2? What is the impression?
[Samsung Galaxy Nexus] efrant:
If I remember correctly, this was the norm for the Nexus One: the factory images were always available before any OTA was rolled out.
[Samsung Galaxy Nexus] nunomeneses:
As i already posted received today the 4.1.2 ota update on Yakju
[Samsung Galaxy Nexus] efrant:
Can you post the file name please?
[Samsung Galaxy Nexus] demzzy:
guess he didnt get the update after all.. ?
[Samsung Galaxy Nexus] efrant:
He did, but didn't get a chance to get the URL. He just flashed back to 4.1.1 and is waiting for the OTA.
[Samsung Galaxy Nexus] demzzy:
damn... guess the wait continues..
[Samsung Galaxy Nexus] nunomeneses:
Yes and i'm not having any luck to force update... :\
[Samsung Galaxy Nexus] WizardBGR:
Factory Image "yakju" 4.1.2 (JZO54K) for Galaxy Nexus "maguro" (GSM/HSPA+)

Factory Image "takju" 4.1.2 (JZO54K) for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet)
[Samsung Galaxy Nexus] oper.debian:
waiting OTA
[Samsung Galaxy Nexus] sheeksta:
two questions

What's the difference for beween IMM76Q and IMM76K for Toro?

Also, the files look like full ROMs, are they really not? 155MB for a toro zip seems like a full rom. Can i format my partitions and install this fresh?
[Samsung Galaxy Nexus] efrant:
1) IMM76Q is the same as IMM76K except that it has the local device search disabled.

2) These are not full ROMs. Go to Google's developer page (linked in my signature) for the full ROMs.
[Samsung Galaxy Nexus] nkrick:
I believe it was reported by multiple outlets earlier this year that the Play Store (takju) version would be the first to get future updates (that is until the next Nexus phone is released). Someone correct me if I am wrong, but I think the only difference between takju and yakju is the inclusion of Google Wallet on takju. I haven't researched it, because I have a takju, but I think you can flash a full takju image on yakju without any problems and then use takju OTA updates from then on.
[Samsung Galaxy Nexus] matteventu:
Why none of the person that recevied OTA has posted the url? D:
[Samsung Galaxy Nexus] demzzy:
damn.. still nothing?
[Samsung Galaxy Nexus] Grant2k:
London, yakju
[Samsung Galaxy Nexus] coredump00:
Please try to get the URL.
[Samsung Galaxy Nexus] tailsthecat3:
One day closer to Google releasing the toro images. Can't wait to flash!
[Samsung Galaxy Nexus] demzzy:
did you manage to pull the url?
[Samsung Galaxy Nexus] X1iser:
OTA 4.1.2 yakju JZO54K-from-JRO03C

http://android.clients.google.com/p....signed-yakju-JZO54K-from-JRO03C.24a9a760.zip

;)
[Samsung Galaxy Nexus] Edwrib:
Ty!!!
[Samsung Galaxy Nexus] demzzy:
good job!.. thank you!
[Samsung Galaxy Nexus] extremus90:
thanks x1user :good:
[Samsung Galaxy Nexus] spaceman860:
Efrant just a suggestion with method 1 after step 7 add flash super SU ZIP then reboot then to get custom recovery back use ROM manager to flash CWM recovery or Goo manager to flash TWRP recovery this will automatically rename recovery from boot.p file

Sent from my BAKED N7
[Samsung Galaxy Nexus] Edwrib:
If I rename my yakju to takju and flash this OTA, will brick anything?

Ty.
[Samsung Galaxy Nexus] msavic6:
If I use method 2(stock recovery, unlocked boot loader)

Will CWM remain on my device after the install of the update.zip or will it be temporarily booted?
[Samsung Galaxy Nexus] hboyer:
stoockboot JZO54K cwm flashable

Hi efrant!

Could you provide us again, as you have done before, with the extracted stock kernel cwm flashable for JZO54K?

(in order to be prepared for future firmware updates ;) )

Thanks in advance!
[Samsung Galaxy Nexus] extremus90:
Edwir installed yakju or takju isly the same ;)
[Samsung Galaxy Nexus] hboyer:
where to get super su.zip ?
[Samsung Galaxy Nexus] efrant:
I tried to cover that in note 6. I can maybe try to make it clearer.

Not sure what you are asking. yakju updates are for yakju builds. takju updates are for takju builds. One will not work on the other.
[Samsung Galaxy Nexus] spaceman860:
cwm-JZO54K-stockboot.zip

http://db.tt/kvslK4yQ

http://xdaforums.com/showthread.php?t=1538053

[29.08.2012] SuperSU v0.96

Sent from my BAKED Nexus
[Samsung Galaxy Nexus] hboyer:
THANKS m8 :)
[Samsung Galaxy Nexus] anewbieuser:
Downloaded and flashed! Thanks a lot!
[Samsung Galaxy Nexus] efrant:
CWM will not remain on your device.
[Samsung Galaxy Nexus] Edwrib:
They are the same but recovery don't flash takju over yakju because build prop.

Idk if files are different from takju to yakju, so idk if a takju ota will patch correctly in yakju.

---------- Post added at 04:20 PM ---------- Previous post was at 04:14 PM ----------

But if I change the build.prop and flash takju over yakju, they will patch correctly?