Develop Bugs

[Download] Android 4.2 (JOP40C) for the GSM Galaxy Nexus

if you are on a GSM Galaxy Nexus, it is time for you to enjoy some Android 4.2.
from the thread [ROM][OTA][GSM][JB] Android 4.2 JOP40C: Rooted Busybox Odexed (11/13/12)
Features
The latest Android OS, 4.2 Jellybean build JOP40C
Insecure boot.img (allows for elevated commands such as adb remount)
Rooted with the latest su binary and SuperSU app
Busybox 1.20.2 installed for increased functionality of root applications and terminal commands
Odexed version also available for purists
Credits
Google - for developing Jellybean, the best version of Android yet!
Chainfire - for quickly updating SuperSU for Jellybean!
Goo.im - a great host and resource for developers and the Android community in general
Anyone I may have missed - thanks for all your contributions!
Requirements
GSM Galaxy Nexus (GT-i9250) - your version does not matter (yakju, takju, etc)
ClockworkMod or TeamWin Recovery
Screenshots
{
"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"
}
Instructions
1. If you are on any 4.0.x ROM, it is highly suggested you do a full factory reset (wipe data/cache in recovery) prior to flashing Jellybean!
2. If you are upgrading from a 4.1.2 JB ROM you may be able to just wipe cache and dalvik cache.
Wipe accordingly as outlined above
Use your recovery to flash the ROM file
Do NOT flash any gapps - they are all included
Optionally, flash the baseband (radio) update if you'd like the newest one
Reboot - be patient, the initial boot may take a few minutes
Downloads
Primary Link (Goo.im)
Click to expand...
Click to collapse
So alangrig made zip for takju and yakju update via CWM: preserves CWM and Root permission. Just don't forget in CWM after update before reboot choose fix SU. Works flawlessy
Download link:
takju (works great)
yakju (looks like it has a bootloop bug)
Make sure to make back up.
I take no responsibilities for any outcome.
This update works flawlessly on my Gnexus takju and version
Click to expand...
Click to collapse
official takju - aosp | OTA
Make sure you follow the methods below.
Method 1
Note: the method 1 below will work just fine for JB — but you will need to re-flash CWM, and rename /system/etc/install-recovery.sh once you are booted.
1) Download the correct update for your build on to your computer;
2) Open the archive and delete the recovery folder; EDIT: Do NOT do this step if it you are using any Jelly Bean update, i.e., JRN84D or newer.
3) Copy the file to /sdcard on your device;
4) Reboot into CWM;
5) Select “install zip from sdcard”;
6) Select “choose zip from sdcard”;
7) Select the update the you just copied to your device;
8) Wait until it completes. Reboot. Done.
Method 2 – Stock recovery installed, Unlocked bootloader
1) Download the correct update for your build on to your computer;
2) Copy the file to /sdcard on your device;
3) Download CWM from here and place it on your computer in the same directory as your fastboot binary. For CDMA/LTE devices, use this version;
4) Rename the CWM image to cwm.img
5) Reboot into fastboot mode;
6) Open a command prompt in the same directory;
7) Type fastboot devices to make sure your device is recognized;
8) Type fastboot boot cwm.img
9) Select “install zip from sdcard”;
10) Select “choose zip from sdcard”;
11) Select the update the you just copied to your device;
12) Wait until it completes. Reboot. Done.
Method 3 – Stock recovery locked bl, no root
1) Reboot your device into the stock recovery (i.e., the screen with the Android on its back with the “!”;
2) Access the stock recovery menu by pressing power and volume up;
3) Select “Apply update from ADB”;
4) Download the correct update for your build and place it in the same directory as your ADB binary;
5) Open a command prompt in the same directory as your ADB binary;
6) Type adb devices to make sure that your device is recognized;
7) Type adb sideload name-of-file.zip
8) Reboot. Done.
Please note: your device should also be running build JZO54K before trying to install the update manually.
Aditional Information
About the Galaxy Nexus versions (by the user dcrin3): link
-----
Developer Options are hidden in 4.2, just go to: Settings, About phone, tap "Build number" 7 times.
-----
----------------------------------------------
Haven't tried it yet, this info is based on this source

awesome...

This helps takes the sting of not getting the N4 ordered tonight. Thanks
Sent from my Galaxy Nexus using xda premium

Im on JZO54K build with CWM Touch ;Rooted. How do i get 4.2 on the phone ? Could you clarify this ?

Yakju or Takju?
Hey guys, Does it matter if were on Takju or Yakju? And I have TWRP installed. Will I have to reflash that after I am finished or will this take away Root completely?
Thanks!

ASSMO said:
Hey guys, Does it matter if were on Takju or Yakju? And I have TWRP installed. Will I have to reflash that after I am finished or will this take away Root completely?
Thanks!
Click to expand...
Click to collapse
for yakju users it is working for some and isnt for others.. i recommend you flash the takju google image and then flash this update
---------- Post added at 01:21 PM ---------- Previous post was at 01:19 PM ----------
suttaroom said:
Im on JZO54K build with CWM Touch ;Rooted. How do i get 4.2 on the phone ? Could you clarify this ?
Click to expand...
Click to collapse
follow these instructions..
Maroon Mushroom said:
-make sure you're on the latest STOCK android image for TAKJU
-move .zip to your phone
-boot into CWM recovery
-install zip from SD card
-choose the fie
the install takes a few minutes.
Click to expand...
Click to collapse

What if I am rooted, have a custom rom and dont want to lose CWM?

tymonn said:
What if I am rooted, have a custom rom and dont want to lose CWM?
Click to expand...
Click to collapse
you need to be stock takju 4.1.2, you can be rooted but you will lose root and you will lose cwm as well but it will take you 5 mins to root and flash cwm so not that big of a deal

One more question!
I have, yakju, should I flash factory 4.1.2 for yakju then go to this??

make sure you're on the latest STOCK android image for TAKJU
Click to expand...
Click to collapse
how could we know we're in lates image or else?
how can we flash lates build if we arnt on the correct build?

ASSMO said:
I have, yakju, should I flash factory 4.1.2 for yakju then go to this??
Click to expand...
Click to collapse
no you need to flash google takju 4.1.2 image

gonna give it a shot! Thanks!

HDRAGON said:
how could we know we're in lates image or else?
how can we flash lates build if we arnt on the correct build?
Click to expand...
Click to collapse
use toolkit to flash takju 4.1.2

k786 said:
you need to be stock takju 4.1.2, you can be rooted but you will lose root and you will lose cwm as well but it will take you 5 mins to root and flash cwm so not that big of a deal
Click to expand...
Click to collapse
same situation with takju/maguro:4.1.2/JZO54K rooted and CWM touch.. so the file which is present in the download link at the start of the -topic ..
Install zip from sd card.. and this should work.. minus the root? yes

Android 4.2 Jelly Bean OTA (JOP40C) already rolling out to GSM Samsung Galaxy Nexus
​

jackpham said:
Android 4.2 Jelly Bean OTA (JOP40C) already rolling out to GSM Samsung Galaxy Nexus​If you own a GSM Samsung Galaxy Nexus, it might behoove you to check your device settings right about now, as we’re starting to see reports on the Interwebz that Android 4.2 (aka Jelly Bean) is in the process of rolling already. The boys over at Android Police have spotted posts on both Google+ and Twitter, with users already posting screenshots of build JOP40C installed on their phones.
​The update brings along with it the awesome new Photosphere feature (which I’m still trying to perfect my hand at), as well as Gesture Typing support, but unfortunately does not include multiple user support, like the Nexus 7 and Nexus 10 versions of the OS will offer. Don’t be surprised if we see it ported over to the phone though, as we all know how the Android development community works. Even if we don’t really need the function, I’m sure someone will make it happen, just because they can.
Sprint and Verizon GNex owners, you already know the drill. Even though your device is a Nexus, you’re still going to have to wait a bit until your respective carriers get all the details sorted out.
As for you GSM owners, feel free to check for the update now. Be sure to stop back and let us know if you’ve already gotten it, and how it’s treating you if you’re already rocking it.
​
Click to expand...
Click to collapse
whats the point of posting this?
---------- Post added at 01:47 PM ---------- Previous post was at 01:46 PM ----------
suttaroom said:
same situation with takju/maguro:4.1.2/JZO54K rooted and CWM touch.. so the file which is present in the download link at the start of the -topic ..
Install zip from sd card.. and this should work.. minus the root? yes
Click to expand...
Click to collapse
yes..

jackpham said:
Android 4.2 Jelly Bean OTA (JOP40C) already rolling out to GSM Samsung Galaxy Nexus​
Click to expand...
Click to collapse
What font is that?? It's like sorta 3d and it was tripping my eyes out!
Sent from my Galaxy Nexus using Tapatalk 2

Thanks a bundle bhai.. will try now!

it;s not working for me....i am on the rom that should run this.... a little help please?

installation aborted ?!? Or is it required to rename it to update.zip??!

[Q] Android Red Triangle

Hi all
I have phone Galaxy Nexus and I am having trouble updating ota where it after receiving the update must be recovery is stock and when I tried to retrieve recovery (With Galaxy Nexus ToolKit) does not work with me and show this is Death robot. I've access to Root and Recovery before ( CWM ) and Bootloader is open & I have a Custom Kernel
NOw How To Retrieval The stock recovery ??
sorry for my English
{
"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"
}

ahmedsaber20005 said:
Hi all
I have phone Galaxy Nexus and I am having trouble updating ota where it after receiving the update must be recovery is stock and when I tried to retrieve recovery (With Galaxy Nexus ToolKit) does not work with me and show this is Death robot. I've access to Root and Recovery before ( CWM ) and Bootloader is open & I have a Custom Kernel
NOw How To Retrieval The stock recovery ??
sorry for my English
Click to expand...
Click to collapse
Manually flash the latest factory image, job done!

EddyOS said:
Manually flash the latest factory image, job done!
Click to expand...
Click to collapse
This is not a logical solution every time issue a new version of Android will be forced to do so and I have to take copies of the software, games and music and then restored again!!

What is the main reason for this problem?? And what is the solution

ahmedsaber20005 said:
This is not a logical solution every time issue a new version of Android will be forced to do so and I have to take copies of the software, games and music and then restored again!!
Click to expand...
Click to collapse
True, but it's always worth making a backup with Titanium to restore if required. That or make sure you keep the stock recovery after each build is released

EddyOS said:
True, but it's always worth making a backup with Titanium to restore if required. That or make sure you keep the stock recovery after each build is released
Click to expand...
Click to collapse
I always do that, but sometimes we need cwm formal and sometimes I need to air updates

4 Up

that is the stock recovery. something else on your phone is not stock and therefore it is failing.

ahmedsaber20005 said:
4 Up
Click to expand...
Click to collapse
1. Don't bump threads
2. Have you edited/deleted any system files? If so, there's your issue

EddyOS said:
1. Don't bump threads
2. Have you edited/deleted any system files? If so, there's your issue
Click to expand...
Click to collapse
No just root

Zepius said:
that is the stock recovery. something else on your phone is not stock and therefore it is failing.
Click to expand...
Click to collapse
I am have root&unlock bootloder&custom kernel+Busy box
That all

ahmedsaber20005 said:
I am have root&unlock bootloder&custom kernel+Busy box
That all
Click to expand...
Click to collapse
you have a custom kernel and busy box. those 2 things modify system files.
YOU ARE NOT ON A STOCK ROM.
the ota will never work until you return those things to stock (good luck finding all the things busy box changes.)

Zepius said:
you have a custom kernel and busy box. those 2 things modify system files.
YOU ARE NOT ON A STOCK ROM.
the ota will never work until you return those things to stock (good luck finding all the things busy box changes.)
Click to expand...
Click to collapse
If I uninstall this kernel and basybox and flash the stock recovery wiil be working ? Or I should to flash a new factory image?

ahmedsaber20005 said:
If I uninstall this kernel and basybox and flash the stock recovery wiil be working ? Or I should to flash a new factory image?
Click to expand...
Click to collapse
Just flash a system image, so simple

flash the factory images is the best. busybox is known to update system files and just uninstalling it will not revert the changes.

Thanks All For Help me put I have a little questions
1-Does Root Make Errors With OTA ?
2- If I want to flash image factory with Odin or toolkit?
3-If I install custom recovery and I want to back to stock can I do this with toolkit or other?
Thanks

1. Yes
2. Neither - learn to do it manually
3. Flash manually using the stock recovery in the factory image

EddyOS said:
1. Yes
2. Neither - learn to do it manually
3. Flash manually using the stock recovery in the factory image
Click to expand...
Click to collapse
Is there a way combines the powers of Root and ota Together ?? Will the program help on that?
https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper&hl=en

No, that only masks root so some apps can run. It won't make any difference to the phone with regards to OTAs. Basically, if you're going to unlock the phone just go custom and ignore OTAs

EddyOS said:
No, that only masks root so some apps can run. It won't make any difference to the phone with regards to OTAs. Basically, if you're going to unlock the phone just go custom and ignore OTAs
Click to expand...
Click to collapse
please dont spread mis-information.
root alone does not stop you from getting OTAs, as i have root and nothing else and get OTAs just fine and they install just fine.. root does allow you to modify system files which can cause OTAs to fail.
what you did mention about rootkeeper is correct. it just masks root to allow certain apps to run and allow a easy way to return root after an OTA.

[STOCK][C69XX][4.3] Update to 14.2.A.0.290 [Root & XZDR][LB/UB][16/1/2014]

{
"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"
}
Requirements:
Flashtool 0.9.13 by @Androxyde
XZDualRecovery 2.7.43 BETA or newer.
Current rooted FW version: 14.1.G.1.534 and 14.1.G.2.257 .
Special features:
SuperSU integrated in system, FULL ROOT!
XZDualRecovery 2.7.71 BETA (CWM & PhilZ Touch & TWRP) pre-installed;
init.d support (read how to enable)
For both locked and unlocked bootloaders!
In the following guide I suggest you use an external SDCard but that's just good practice, you can use your internal storage or even an USB OTG storage device in TWRP if you like to install, that's no problem!... If you are modding and the likes, best is to have an external sdcard, just for safeties sake.
If you are unable to download torrent files directly, have http://zbigz.com/ do it for you!
How to update to 14.2.A.0.290:
If you attempted this before, make sure you delete XZDR.prop from the XZDualRecovery folder to make sure it will not cause a bootloop.
Files:
For C6902: Download C6902_14.2.A.0.290.flashable.zip (Bittorrent: 905MB) and C6902_14.2.A.0.290_Stripped.ftf (21MB)
For C6903: Download C6903_14.2.A.0.290.flashable.zip (Bittorrent: 784MB) and C6903_14.2.A.0.290_Stripped.ftf (21MB)
For C6906: Download C6906_14.2.A.0.290.flashable.zip (Bittorrent: 849MB) and C6906_14.2.A.0.290_Stripped.ftf (21MB)
For C6943: Download C6943_14.2.A.0.290.flashable.zip (Bittorrent: 863MB) and C6943_14.2.A.0.290_Stripped.ftf (21MB)
Save them somewhere you remember;
Put 'C69XX_14.2.A.0.290.flashable.zip' on (the external) SDcard1;
Put 'C69XX_14.2.A.0.290_Stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in TWRP and don't forget to backup the contents of 'SDCard' (the internal storage!);
Install XZDualRecovery 2.7.74 or newer from PC.
In TWRP -> Wipe -> advanced Wipe Tick/Check:
Dalvik-Cache
System
Cache
Data
Then 'Swipe to Right' to make it happen and go back to the TWRP home screen;
Flash 'C69XX_14.2.A.0.290.flashable.zip' in TWRP (if you have an old C6903 flashable package, be sure to flash the patch from post 2 now!)
NOTE: do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C69XX_14.2.A.0.290_Stripped.ftf';
Now reboot to system;
Once you get to the language select screen, reboot to TWRP (no need to finish the guide);
Restore the backup of DATA only, when done go back to the TWRP home screen;
In TWRP -> Wipe -> advanced Wipe Tick/Check Dalvik-cache;
Reboot to system.
The first boot will be slow and after a long wait at the boot animation you will see Android start optimizing the apps on your phone.
Video Guide:
NOTE: This guide is based on an older guide which has since been updated a few times, but it will give you a general idea.
shem2409 said:
Click to expand...
Click to collapse
Enjoy! :laugh:
Known XZDualRecovery Issues:
Busybox Updater/Installer: If you have XZDualRecovery installed, un-install any Busybox updating app/tool as most if not all of them will install a version of busybox which does not support the lzma compression applets XZDualRecovery depends on. The version installed together with XZDualRecovery is very stable and I have yet to hear anyone complain about it's stability.
How to report errors:
Please, before shouting out "It doesn't work!!1!" or "I lost root!" or even "My phone reboots when remounting /system RW!!" try the following:
Restore any JB 4.2.2 FTF using any means you are familiar with so you can try again.
Root it using any means you are familiar with.
Install XZDualRecovery and then try to update again using TWRP.
If it still fails something from there on: LOGS!!.
NOTE: The important ones can be found in /cache/recovery and in /sdcard1/XZDualRecovery, pack them up and send them to me or attach them to your bug report.
Thank you
XDA:DevDB Information
[STOCK][C69XX][4.3] Update to 14.2.A.0.290 [Root & XZDR][LB/UB][16/1/2014], a ROM for the Sony Xperia Z1
Contributors
[NUT]
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 14.1.G.1.534 and 14.1.G.2.257
Based On: STOCK
Version Information
Status: Beta
Current Beta Version: 16/1/2014
Beta Release Date: 2014-01-16
Created 2013-12-19
Last Updated 2014-01-16

ROM Patches
For those who have this ROM installed or downloaded with the mutilated root and 40 second reboot bug in recovery or have it installed with a semi-root situation:
C6903_14.2.A.0.290.patch.zip (8.9MB)
Follow the ROM flash guide in the OP and flash the patch right after flashing the ROM zip.
This will patch your ROM release to have XZDualRecovery BETA (2.7.71). It will patch/fix root as well. It should be small enough to quickly flash using TWRP, as long as you do it right after entering it.

FAQ & Tips and Tricks
Easy switching between locked and unlocked bootloader states!
NOTE: USE TWRP ONLY for this guide.
NOTE 2: You NEED to have XZDualRecovery 2.7.43 or higher to make this work.
Create a backup, including the Trim Area (TA!)
Unlock your bootloader
Restore backup without TA
Create a new backup of your UNLOCKED TA
Restore the previous TA backup to relock your phone.
Done :good:
Now you can switch between locked and unlocked bootloaders quick and painless: no more system wipes and you can basically do whatever you want
How to enable init.d support:
Open a filemanager app and navigate to the location where the XZDualRecovery folder is located and go in to it. Open XZDR.prop as a text file and set dr.initd.active to true.
NOTE: For this guide ROM it means the init.d script called 99SuperSUDaemon will kick in to action, so it's best to disable (by setting chmod 644) /system/etc/install-recovery.sh for the time being or to clear it's contents.
Done
Downgrading to a 4.2 ROM:
Download C6903_14.1.G.1.534_[NUT].ftf (Bittorrent: 770MB) and flash it using FlashTool. I've also added the FTF to the downloads page on the DevDB tab, this will allow straight downloads as well.
This FTF will allow you to downgrade to .534 without loss of your IMEI :good:
Thanks to @mharckk and @MohammadAG for the workaround which contributed to the creation of this FTF.

About to download and flash now.

I'll do a deodex package for this ROM tomorrow, it's late now

How did u get FULL ROOT dude?

jackie099 said:
How did u get FULL ROOT dude?
Click to expand...
Click to collapse
Please remove the OP quote from your post, thanks
If you have an earlier version to update from, which has been rooted and has recovery, it's not hard to do

Big hugs man. Thanks. Much appreciated!!!
Sent from my C6903 using XDA Premium 4 mobile app

Hey Man, Good Job. Is this update tweeked to instal apps data to external memory by default?

eclyptos said:
Hey Man, Good Job. Is this update tweeked to instal apps data to external memory by default?
Click to expand...
Click to collapse
Nope, This is really a rooted stock rom with recovery, what you do to it after installing it is entirely up to you

[NUT] said:
Nope, This is really a rooted stock rom with recovery, what you do to it after installing it is entirely up to you
Click to expand...
Click to collapse
The root is not working on 4.3 until now. Is it? Even after flashing supersu on a unlocked bootloader we get partially rooted system partition. The busybox is not working either.

Can u upload it not in torrent? Thankyou
Gesendet von meinem C6903 mit Tapatalk

Sumedha Kapoor said:
The root is not working on 4.3 until now. Is it? Even after flashing supersu on a unlocked bootloader we get partially rooted system partition. The busybox is not working either.
Click to expand...
Click to collapse
On 4.3 SuperSU is to be daemonized, which means it gets turned in to a service. This ROM does that.
On the 4.3 Journalists & Commercial release for the XZ and ZL the root method I used is working flawlessly now Initially on these releases I made a booboo, which I fixed with an update package. The cause for the need of this fix has been removed before building this package, it should be properly rooted and working OK
Remember, Recovery has been integrated, which will work just as well even if root would still bugger out, so then I will find a solution and make it work in the end, if needed

[NUT] said:
On 4.3 SuperSU is to be daemonized, which means it gets turned in to a service. This ROM does that.
On the 4.3 Journalists & Commercial release for the XZ and ZL the root method I used is working flawlessly now Initially on these releases I made a booboo, which I fixed with an update package. The cause for the need of this fix has been removed before building this package, it should be properly rooted and working OK
Remember, Recovery has been integrated, which will work just as well even if root would still bugger out, so then I will find a solution and make it work in the end, if needed
Click to expand...
Click to collapse
Can you send me a flashable zip with the recovery and this rooting method that you mentioned above? I have a deodexed, zipaligned, rooted, busyboxed, tweaked and debloated purely stock rom. I will see if I could fix the partial root in it. Plus it would be easier for me and others who already have a rom to fix their issues with it. Thanks.

Sumedha Kapoor said:
Can you send me a flashable zip with the recovery and this rooting method that you mentioned above? I have a deodexed, zipaligned, rooted, busyboxed, tweaked and debloated purely stock rom. I will see if I could fix the partial root in it. Plus it would be easier for me and others who already have a rom to fix their issues with it. Thanks.
Click to expand...
Click to collapse
+1

Sumedha Kapoor said:
Can you send me a flashable zip with the recovery and this rooting method that you mentioned above? I have a deodexed, zipaligned, rooted, busyboxed, tweaked and debloated purely stock rom. I will see if I could fix the partial root in it. Plus it would be easier for me and others who already have a rom to fix their issues with it. Thanks.
Click to expand...
Click to collapse
Lets see what people's experiences are with the existing package, once confirmed working, I will release the base zip for devs to use

Do we have to flash the ftf after flashing the zip or can we just flash the zip? Also, after successfully flashing, do we have to backup TA partition, unlock bootloader, then restore or since Sony fixed it can we just unlock without restoring TA?

TheKnux said:
Do we have to flash the ftf after flashing the zip or can we just flash the zip? Also, after successfully flashing, do we have to backup TA partition, unlock bootloader, then restore or since Sony fixed it can we just unlock without restoring TA?
Click to expand...
Click to collapse
It's a stock ROM, so unlocking is not required. But if you had an unlocked bootloader, restoring it first might be wise.
Just stick to the flash order in the guide, that should be fine.

[NUT] said:
It's a stock ROM, so unlocking is not required. But if you had an unlocked bootloader, restoring it first might be wise.
Just stick to the flash order in the guide, that should be fine.
Click to expand...
Click to collapse
Will do. Now that the BL unlock is fixed theres no reason not to unlock it, that's why I asked. The more I do to it, the merrier.

If i have already updated to official 4.3, do i need to downgrade to 4.2.2, in order to get working recovery then flash your 4.3?
Sent from my C6903 using Tapatalk

[Rogers/Fido] Lollipop Update Issues/Solutions

Rogers released the OTA update for Canadian M8 today, Feb 3. My M8 was rooted, and I previously modified some files. As a result, I encountered errors during the update. The following is what I did to resolve the problems and successfully updated to Lollipop. Please be aware that my data was completely wiped in the process, and so remember to backup important files.
First of all, when your OTA update process failed, you would see the green triangle in recovery turned to red. At that point, you should hold the vol+ button, and tap once on the power button. It will show an error log.
Error 1 - Unexpected content
The update checks for integrity of the current files, and would report error and stop when it detected any system files that had been modified. Please note that just because your M8 is rooted, you still may not get this error, as it depends on whether any files were modified after root. But if it the update ran into this problem, you would see the following error message:
Verifying current system...
"___(some file name)____" has unexpected content
Solution to Error 1 -
One could try to restore individual file back to stock, but I chose to flash the entire rom back to stock. For Rogers, there is no RUU file, and so I could only use a TWRP nandroid image. This is the procedure I followed:
1. Using this toolkit, unlock bootloader, and flash to install TWRP recovery. I used the custom recovery option, to install the latest TWRP (2.8.4.0; link can be found in my 2nd post below);
2. Restore to the 3rd TWRP image with HBoot 3.19 in this post,
3. Flash back stock recovery (*must be recovery from 4.4.4 or 5.0.1. If not, you will run into Error 2 below)
I use the recovery embeded in the 5.0.1 OTA update file downloaded. According to this post, it is down by:
downloading the OTA file; when it ask to install, select install later. Connect your device to PC, open the Internal Storage with PC explorer, browse to Download folder, you'll have the OTA.zip there. Copy that OTA.zip to PC, open it with 7-zip then open firmware.zip that you see inside, extract out the recovery.img
Error 2 - Outdated recovery*
Prior to the loading the updated rom, the installation software checks the version of the existing boot loader. It is expecting the version from either Android 4.4.4 or 5.0.1. If one of these is not found, you will get the following error:
Package expects build fingerprint of htc/rogers/wwe/htc_m8:4.4.4/KTU84P/401507.4:user/release-keys or htc/rogers_wwe/htc_m8:5.0.1/LRx22C/4463267.2:user/release-keys; this device has htc/rogers_wwe/htc_m8:4.4.2/KOT49H/318414.17:user/release-keys.
{
"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"
}
The solution is to simply update the recovery from the OTA zip file as described above. Make sure your bootloader is unlocked first.
[Update] Alternative to doing the OTA update to Lollipop, here is the TWRP nandroid backup with Lollipop 5.0.1 for Rogers.
To gain root after Lollipop, go directly to the next post.
Finally, you could also change recovery back to stock recovery for 5.0.1 (attached in the nandroid backup above).

Rooting lollipop
After updating to Lollipop, you could re-root it using the same method as in kitkat. However, make sure you use the latest version of TWRP and SuperSU:
openrecovery-twrp-2.8.4.0-m8.img (link) and
UPDATE-SuperSU-v2.45.zip (link)
The M8 Toolkit available in the xda forum still works in helping me to flash the custom recovery.

Any requirements to flash the stock recovery?

MarwanSamirIbraheem said:
Any requirements to flash the stock recovery?
Click to expand...
Click to collapse
For an OTA? Yes. You need stock recovery.

xunholyx said:
For an OTA? Yes. You need stock recovery.
Click to expand...
Click to collapse
I want to install OTA. But when it begins to install it boots into bootloader and nothing happen.
so I want to install stock recovery to flash this OTA. And my question is.. is there any requirements to do to install "the stock recovery" first?
I have TWRP, bootloader Unlocked, S-on and rooted.

Must be fully stock, right recovery installed. No modified system files, deleted or freezed apps.

MarwanSamirIbraheem said:
I want to install OTA. But when it begins to install it boots into bootloader and nothing happen.
so I want to install stock recovery to flash this OTA. And my question is.. is there any requirements to do to install "the stock recovery" first?
I have TWRP, bootloader Unlocked, S-on and rooted.
Click to expand...
Click to collapse
Unlocked bootloader needed. S-on is fine.

Also rooted is ok.

ikeny said:
Unlocked bootloader needed. S-on is fine.
Click to expand...
Click to collapse
It's already Unlocked bootloader. BTW the software status: Modified .. not official
and there is something strange. I tried to install the Lollipop OTA with ADB and it didn't work but after this the information in the bootloader changed to: os: 4.16.401.10 15 but the software is 4.4.4 .. How?!

MarwanSamirIbraheem said:
I want to install OTA. But when it begins to install it boots into bootloader and nothing happen.
so I want to install stock recovery to flash this OTA. And my question is.. is there any requirements to do to install "the stock recovery" first?
I have TWRP, bootloader Unlocked, S-on and rooted.
Click to expand...
Click to collapse
Go to this thread for downloads and instructions on how to find the recovery you need, and how to flash it.

MarwanSamirIbraheem said:
I tried to install the Lollipop OTA with ADB and it didn't work...!
Click to expand...
Click to collapse
Did you try to just run the OTA under system update? Post the error message (Vol up + Pwr button).

ikeny said:
Did you try to just run the OTA under system update? Post the error message (Vol up + Pwr button).
Click to expand...
Click to collapse
I will try to download NanDroid backup. Thanks alot for responding!
---------- Post added at 12:40 AM ---------- Previous post was at 12:08 AM ----------
xunholyx said:
Go to this thread for downloads and instructions on how to find the recovery you need, and how to flash it.
Click to expand...
Click to collapse
I'm downloading a Stock Nandroid Backup for my phone now. should i unroot the phone first or what because i want it full stock after restoring this backup.
Or should i restore it and install a stock recovery too? is the backup comes with the stock recovery? i want to make sure all of this.
Can you tell me step by step what to do here?

MarwanSamirIbraheem said:
I'm downloading a Stock Nandroid Backup for my phone now. should i unroot the phone first or what because i want it full stock after restoring this backup.
Or should i restore it and install a stock recovery too? is the backup comes with the stock recovery? i want to make sure all of this.
Can you tell me step by step what to do here?
Click to expand...
Click to collapse
First, you do not need to unroot first. The Nandroid backup will wipe everything including traces of root.
Nandroid restore however won't replace your boot loader. Read my first post again. The step by step guide is already there, under Soultion of Error 1.

UniversalKID said:
Not if the nandroid backup is rooted.
Click to expand...
Click to collapse
This is probably correct. I haven't used the stock backups, so I can't say for sure. The backups are taken with a custom recovery, after all. That usually points to rooted.
But...
You install the custom recovery before you flash superuser, so the backups can be made before root is actually gained. There's a good chance they are. Like I said, I don't use them. S-Off and such.
And there is no way to tell if the backup is rooted for sure, from the downloads I have seen.
So make your own backup, and flash the stock nandroid. You can always go back to the way you were. You rooted already once, right? You can do it again.

UniversalKID said:
Not if the nandroid backup is rooted.
Click to expand...
Click to collapse
I can't speak for others. But the one linked in my first post is not rooted, and it works fine with OTA update to Lollipop.

ikeny said:
I can't speak for others. But the one linked in my first post is not rooted, and it works fine with OTA update to Lollipop.
Click to expand...
Click to collapse
After installing the OTA update of 5.0.1 version, Wi-Fi doesn't open.
it says turning on then after 2 minutes say Error, what is this?

MarwanSamirIbraheem said:
After installing the OTA update of 5.0.1 version, Wi-Fi doesn't open.
it says turning on then after 2 minutes say Error, what is this?
Click to expand...
Click to collapse
Try doing a factory reset at boot loader.

MarwanSamirIbraheem said:
After installing the OTA update of 5.0.1 version, Wi-Fi doesn't open.
it says turning on then after 2 minutes say Error, what is this?
Click to expand...
Click to collapse
Ana labess fe nafs 7warak
All I need is stock recovery instead of TWRP... Is it easy to do?
And Did the lollipop work fine?Wifi problem still there?

Adham L. Alfy said:
Ana labess fe nafs 7warak
All I need is stock recovery instead of TWRP... Is it easy to do?
And Did the lollipop work fine?Wifi problem still there?
Click to expand...
Click to collapse
If you knew how to install TWRP custom recovery, then it is easy to revert back to stock recovery. Same method, just flash the new img file.
No WiFi issue with my lollipop. I did do a factory reset though.

ikeny said:
If you knew how to install TWRP custom recovery, then it is easy to revert back to stock recovery. Same method, just flash the new img file.
No WiFi issue with my lollipop. I did do a factory reset though.
Click to expand...
Click to collapse
Is there a possibility to brick my phone if I install an incompatibly stock recovery with my phone version.... I mean how safe is the procedure? Regardless wiping my data (doesn't matter to me)

OTA update after rooting

Hi. I have just rooted my Pixel 2 XL with Magisk after reading the guides here on XDA. This is my first Android phone and my first time rooting so I'm trying to figure out the update situation here. How would I go about installing version 8.1 when I get the OTA update for it? Would I have to wipe my device again and reinstall Magisk?
On a side note, does anyone know if MinMinGuard on systemless Xposed breaks SafetyNet?
Thanks in advance.

Unroot, apply OTA, re-root.

I have not yet done this myself, I will soon though. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips

dyingearth said:
Unroot, apply OTA, re-root.
Click to expand...
Click to collapse
Can you install OTA with unlocked bootloader?

dyingearth said:
Unroot, apply OTA, re-root.
Click to expand...
Click to collapse
Thanks. Would this remove all of my data?

darkfire404 said:
Thanks. Would this remove all of my data?
Click to expand...
Click to collapse
OTA does not remove your data. What you do want to do is to download the factory image to get the 8.1 boot.img after you're done with OTA. You can then follow instruction on rooting it.
Basically to apply 8.1 OTA, get the previous boot.img and reapply it to your phone:
Unroot:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Apply OTA
download the OTA zip
follow instruction at https://developers.google.com/android/ota for apply ota
Reroot
download 8.1 image. extract it to get boot.img.
follow instruction for magisk

dyingearth said:
OTA does not remove your data. What you do want to do is to download the factory image to get the 8.1 boot.img after you're done with OTA. You can then follow instruction on rooting it.
Basically to apply 8.1 OTA, get the previous boot.img and reapply it to your phone:
Unroot:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Apply OTA
download the OTA zip
follow instruction at https://developers.google.com/android/ota for apply ota
Reroot
download 8.1 image. extract it to get boot.img.
follow instruction for magisk
Click to expand...
Click to collapse
This looks good. But for following section:
Code:
Unroot:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
can I get only the stock 8.0 boot.img (I would like to avoid downloading 1 GB+ of stock 8.0 image to get 50 MB of boot.img, if that's possible at all)?
Oh I see an option in Magisk Manager, never mind my question
{
"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"
}
Nitin

turboencab said:
I have not yet done this myself, I will soon though. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
Did it work?

Cowbell_Guy said:
Did it work?
Click to expand...
Click to collapse
I don't know, I got impatient and sideloaded the OTA. I essentially followed the procedure listed by dyingearth in post #6 above.

Just went to do this but Magisk says Stock Backup Doesn't Exist... I didn't delete anything, anyone know why this would happen? And now the question is... How do I go about getting an update with forking my phone? I don't mind freshly doing it all over from scratch, but would like to get Magisk to backup the stock stuff so that when I follow the OTA instrustions on the Magisk link tips it would work.

OTA
I'm on rooted Pixel XL 2 already on 8.1, can I take the security patch, or do I need to unroot before taking the update?
nitin.chobhe said:
This looks good. But for following section:
Code:
Unroot:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
can I get only the stock 8.0 boot.img (I would like to avoid downloading 1 GB+ of stock 8.0 image to get 50 MB of boot.img, if that's possible at all)?
Oh I see an option in Magisk Manager, never mind my question
Nitin
Click to expand...
Click to collapse

Bump

Following.
My 2xl unrooted today. On it's own. Went to break around 3 and had magisk notification about installing 15.3zip which I was already on. Looked in manager and it showed not installed. Have been reading yesterday about updating while rooted. Checked system update and shows available update today. So I tried to install but failed. Looks like I'll have to wait till after work....at 7pm!!

After taking ota update with magisk installed did not reboot through Magisk so I lost root. Magisk is still on phone but not installed. How to reinstall? Do I need to reflash or can I just hit install on app? Will gladly provide more info aas needed. I have searched and did not find a exact answer to my problem. Build number pq3a.190801.002

You need to sideload ota manually for updates

prot- said:
You need to sideload ota manually for updates
Click to expand...
Click to collapse
I can't figure out how it took the ota in the first place with no errors. I found the guide on how to do the ota with it installed but after i got the ota. When I open the Magisk it says i can install Magisk and Magisk Manager from the app. Im worried it will mess something up.

The quickest and simplest way to update your phone monthly:
- download the stock taimen image for current month
- unzip and edit the 'flash-all.bat' file by removing/deleting the '-w' from the code. Removing the '-w' ensures that your data is NOT wiped
- boot into bootloader and run the 'flash-all' script from your adb folder
- after it completes the update, let the phone boot into Android
- restart and boot into TWRP. Note: decryption is broken for some people (like me), you will need to remove your PIN code before booting into TWRP
- flash Magisk 19.3 or whatever you prefer (and any additional apps you such as Vanced YouTube, etc.)
- Reboot into rooted phone
- Add your PIN code (or whatever security measure you want to use)
If you need a more detailed information, please check the main rooting thread.

OP follow this exactly, and you will have no problems. https://forum.xda-developers.com/showpost.php?p=80039116&postcount=778