Re: [REF] [HOW-TO] [GSM & CDMA] Official Google OTA update URLs -- Latest: JOP40D / 4

---

The takju update has been mirrored on randomphantasmagoria.com.

Sent from my Nexus 7 using Tapatalk HD

Is it possible to receive the ota running with unlocked bootloader?

Yes. Unlocked, rooted, no problem, you just may need to root it again after the OTA since it will change the permissions of the su binary.

CWM 6.x will protect the su permissions so I recommend flashing it as your recovery and then applying the OTA patch from there.

Originally Posted by osm0sis

Yes. Unlocked, rooted, no problem, you just may need to root it again after the OTA since it will change the permissions of the su binary.

CWM 6.x will protect the su permissions so I recommend flashing it as your recovery and then applying the OTA patch from there.

Strange..i didn't get the ota,clean system,no root and unlocked bootloader (of course i switched to takju). So,after many tries, i flashed the ota package through cwm. Going to see what's changed

Originally Posted by ogre_x

Takju is out:

http://android.clients.google.com/pa...D.472aafeb.zip

Source: https://plus.google.com/u/0/10387627...ts/3coHFSrFeQq

Thanks, First post updated.

R: [REF] [HOW-TO] [GSM & CDMA] Official Google OTA update URLs -- Latest: JDQ39 / 4.2

---

Since I was tired to wait for the yakju updates, I decided to move to takju following the instructions here

http://forum.xda-developers.com/show....php?t=1995263

Then I installed the JDQ39 takju update with TWRP, and everything was fine. I had just to reflash superSU to gain root.

No data loss and no problem found so far.

Originally Posted by Angelakaro

Strange..i didn't get the ota,clean system,no root and unlocked bootloader (of course i switched to takju). So,after many tries, i flashed the ota package through cwm. Going to see what's changed

Yeah getting the OTA notification is random and can take forever, this has nothing to do with device configuration though. Luckily, running custom recovery makes it so we can all get it regardless.

Re: [REF] [HOW-TO] [GSM & CDMA] Official Google OTA update URLs -- Latest: JDQ39 / 4.

---

I have been using Franco Kernel with JB 4.2.1. I flashed back to stock kernel and tried to flash OTA 4.2.2, but get an error message concerning power.tuna.so.

Did a search and found that at post 1893, osm0sis said the following:

Originally Posted by osm0sis

Go to /system/lib/hw/ and move power.tuna.so.fkbak to power.tuna.so, then everything should work fine. Make sure you move the file, not copy, since you'll want franco.Kernel to back up the new one too, and the script only does that when .fkbak doesn't already exist.

Need clarification. How does one move power.tuna.so.fkbak to power.tuna.so ??!! Arent those two files ? Shouldnt there be a folder involved? I am using Root Explorer.

Thanks.

UPDATE: Figured it out myself ! I deleted power.tuna.so and then renamed power.tuna.so.fkbak to power.tuna.so using Root Explorer. Successfully updated to JDQ39 !

Originally Posted by bagl0312

Since I was tired to wait for the yakju updates, I decided to move to takju following the instructions here

http://forum.xda-developers.com/show....php?t=1995263

Then I installed the JDQ39 takju update with TWRP, and everything was fine. I had just to reflash superSU to gain root.

No data loss and no problem found so far.

Just wondering. if I am a yakju on 4.2.1, can I still flash it to takju 4.2.1 with the factory image? of does it need to be an upgrade from say 4.2? Coz the instruction in the post from your link was an upgrade.

R: [REF] [HOW-TO] [GSM & CDMA] Official Google OTA update URLs -- Latest: JDQ39 / 4.2

---

Originally Posted by anewbieuser

Just wondering. if I am a yakju on 4.2.1, can I still flash it to takju 4.2.1 with the factory image? of does it need to be an upgrade from say 4.2? Coz the instruction in the post from your link was an upgrade.

You can "upgrade" to takju 4.2.1 even if you are already using yakju 4.2.1
Worked perfectly for me without data loss. I had to reflash the TWRP recovery using fastboot, since the above procedure overwrite it with stock recovery