Database Users

Nexus S Official factory images for 9020t & 9023

http://code.google.com/android/nexus/images.html#yakju
https://groups.google.com/forum/?fromgroups#!topic/android-building/b50nY_onbP4

^Thanks.
This can be flashed via CWM recovery ?
(after a 'fastboot oem lock/unlock' ?)

No. They are fastboot images. If you're not sure what these are and how to use them then I would not mess with them.

^ gotcha
can someone please put up a tutorial/guide to do this.
I really want to try this.

The shell script gives you the exact fastboot commands to run if you want to do it manually. And it will restore your phone to a true factory state with 4.0.4.

if i will use the factory img the baseband version in bootloader will be change? i see now i9020xxkl1 but my nexus is i9023?

I was wondering the same .. In the zip it says :require board=herring
require version-bootloader=I9020XXJK1|I9020XXKA3|I9020XXKI1|I9020XXKL1
require version-baseband=I9020XXJK8|I9020XXKB1|I9020XXKD1|I9020XXKF1|I9020XXKI1|I9020UCKB2|I9020UCKD1|I9020UCKF1|I9020UCKJ1|I9020KRKB3|M200KRKC1
So it should be okay , because when I reboot into the bootloader of my phone it says :
Bootloader version: I9020XXKL1
Baseband version : I9020XXKI1
My phone actually is a I9023 so I gues the images are okay to flash on a I9023

Just noticed that the full ROM version for Nexus S is 4.0.4 IMM76D. Wouldn't be better to flash this complete rom instead of the partial patch OTA which is clearly giving troubles?

HELPPPPP
can someone please put up a tutorial/guide to do this.
I really want to try this.

i wrote a guide
http://forum.xda-developers.com/showthread.php?t=1572307

goldy_rocky said:
can someone please put up a tutorial/guide to do this.
I really want to try this.
Click to expand...
Click to collapse
(No time to write a full tutorial right now but...) I'd say...
Pls wait for someone experimented to confirm what I say because I couldn't try it to confirm it works right now... And also try it at your own risk...
If your bootloader is not unlocked, follow PART 1 & PART 2 of this tutorial. (you will loose data)
(Note that ADB is not in tools folder anymore but in /platform-tools so that's where the part2 cmd as to be runned from)
Then if windows (I guess you would know what to do if on Linux) use 7zip to extract (2 times) all files from the archive.
Then copy the files to the /platform-tools folder.
The open a command prompt in that folder (shift+right click>open a command prompt here).
Then use the commands provided in the .sh script to flash all files (you can read it easily with Notepad++ for instance) one by one...
Note I don't think you can run the "sleep 5" cmd manually but you can of course wait 5' manually .
Code:
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-soju-imm76d.zip
I'm not really sure if bootloader will be locked at this time but my guess is no so just reboot the bootloader ("fastboot reboot-bootloader" or shut down the device then "Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button" and look for the "LOCK STATE - LOCKED" or "LOCK STATE - UNLOCKED").
If "LOCK STATE - UNLOCKED" you may want to lock the bootloader again, just follow part2 again and replace "fastboot oem unlock" by "fastboot oem lock"
EDIT :
ale.landra91 said:
i wrote a guide
http://forum.xda-developers.com/showthread.php?t=1572307
Click to expand...
Click to collapse
You just made me feel so useless ...

First of all, the credits goes to "a2b". I am only put his work here via a link.
Secondly, PLEASE KEEEP IN YOUR MIND THAT NEITHER ME OR "a2b" IS RESPONSABLE FOR ANY LOSS OF YOURS IF YOUR PHONE GET BRICKED.
The thrid, I have tried the method on my Nexus i9023. It works perfectly for me. BUT, I cannot gurentee it works for everyone.
Okay, I just flashed the factory img according to a2b's tutorial for Galaxy Nexus. But for me I just needed to change the names for few files. If you cannot figure out what to change, I suggest you follow albundy2010's advice on post #3
Good luck!
http://androidtobe.blogspot.com/2011/12/galaxy-nexus-installing-ics-402-from.html

Seems most are not familiar with doing this so here are some things you should know.
Doing this will wipe EVERYTHING off your phone. Yes, everything including /sdcard.
Do not be a fool and flash these images to the 4g.
I am not certain about this and if you it and your phone gets messed up do not blame me.
The 9020a should be able to run this factory image. Check to see what version of the bootloader you have. If it matches one of the bootloaders in the .sh script you should be fine. I would NOT flash the bootloader included in this factory image myself. Since I do not know for sure if they are the same for both GSM models. If you follow the guide minus the parts where you flash the bootloader and the radio image I believe it will work.
Again if you try this and it breaks your phone that is on you. I am not responsible for it. I do not have a 9020a to test this on and verify it. I am fairly certain it will work perfectly. If anybody tries it let me/us know the outcome.

is there any specific advantage in flashing the factory image as opposed to flashing the incremental update ? I successfully flashed 4.0.4 using CWR over a full rom installation of 4.0.3 back from December. I wonder if there may be some subtle differences that maybe make it a bit better option to install the factory image ?

mindwalkr said:
is there any specific advantage in flashing the factory image as opposed to flashing the incremental update ? I successfully flashed 4.0.4 using CWR over a full rom installation of 4.0.3 back from December. I wonder if there may be some subtle differences that maybe make it a bit better option to install the factory image ?
Click to expand...
Click to collapse
No
Sent from my Nexus S using XDA App

I used the flash-all.sh script from the factory image file and it didn't wipe the sdcard. Backed it up beforehand anyway just in case. Recovery was broken on reboot. Flashed CWM recovery and all good. i9023.

Stock Nexus 4 - 4.4 OTA not working

Hi forum,
this is my first post here and I am writing this on behalf of my missis, so bear with me should I not state the obvious or ask too easy stuff. I am normally an iOS user and have not had frequent contact with updating / flashing / rooting Android devices.
The Nexus 4 in question is completely stock, nothing has ever been rooted / flashed or updated. The device runs 4.3 (JWR66Y) for some time now (I know, I know... but she is rather non-technical) and for quite some time it's failing to accept the OTA update of KitKat 4.4 (KRT16S). The device downloads the update in the background and notifies about it's existence in the notification area. From there you are able to agree to the update, the device reboots, the update process starts to run and then it just fails with the image of the lying Android mascot just stating "Error".
From there you can just reboot the handset normally into Android OS. Subsequent attempts of the update continue to fail, even after a factory reset.
I have now tried to manually update with the following file http :// android.clients.google.com/packages/ota/google_mako/c7d8660af65b878835d5248252f51dcbf53c2001.signed-two-step.signed-occam-KRT16S-from-JWR66Y.d1b99704.zip and the ADB toolset from the official Android SDK Bundle on Linux. I can properly get the device into recovery mode, get it to the point where it accepts sideloads and then I just issue adb sideload <filename of the above mentiond .zip>. So far, so standard.
The file transfers, update starts but it aborts the install because an existing file does not match the expected content: EMMC:/dev/block/platform/msm_sdcc.1/by-name/modem
Google research suggest this is the case if you have rooted the device before or tampered in some way with the bootloader. No such thing happened here - this is the most standard Android device possible. It hasn't even been attached to a PC before.
I also find various requests to extract the radio.img or modem.img from the stock JWR66Y image and flash it with fastboot. On the one hand I am not sure how do this (all tutorials I can find do this as part of a complete, destructive flashback which I am not seeking to do) and on the other hand I fail to understand how this file's checksum can deviate from the expected value. Is it corrupted or has it been updated by the provider? The handset has been bought regularly directly from Google and is used in Germany. Reverting it to a file from the stock factory image will not cause any problems with the modem?
Any pointers or help are well appreciated.

What is the baseband version listed in settings -> about phone?
If your radio version isn't the listed:
Code:
M9615A-CEFWMAZM-2.0.1700.84
or any of the ones listed here: Nexus 4 Stock Roms - XDA wiki you may actually have a version that noone else does. (or possibly a modded version)
Assuming you have already unlocked your bootloader, it would be:
Code:
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
with the radio extracted from the JWR66Y factory image, if you wish to update via ota.
If you have not unlocked your bootloader, then you will not be able to update at all unless you unlock it and wipe your data.
(as you mentioned the contents of the baseband do not match the expected one)
-------------------------------------------------------------------------------------------------------------------------------------------
If it's not any of the above versions, you could possibly have a previously unknown version.
If that's the case, could you dump it before updating?
To do that, the simplest way would be to boot a custom recovery (such as clockworkmod) with the following:
Code:
fastboot boot <path to recovery.img>
and after it loads
Code:
adb shell dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/newmodem.img
-------------------------------------------------------------------------------------------------------------------------------------------
If you wish to manually update, you can download the KTU84P factory image and flash it on top of your existing rom with the following commands:
(extract the contents of image-occam-ktu84p.zip from occam-ktu84p-factory-b6ac3ad6.zip)
Code:
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.03.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
and that'll force update it without wiping data. Keep in mind you MUST flash both the bootloader and radio together or you will not be able to use cellular services.

Android Nougat on Moto Z (All Unlocked Versions)

I was encouraged to make a separate thread for this, so I did.
Here we're going to try and port the Verizon Nougat update to all Moto Z phones.
I said I'd upload the code into GitHub to make it easier to change stuff, but that got too confusing so I just used Google Drive lol. Anyway, let's get started.
I'll start by editing the update script in the zip, and I'll need somebody to verify that it works. Just be forewarned that things might break (thus the alpha status). If things break, there are other threads with all the Marshmallow stock zip files, flash that and try again. Make sure to check those threads before you flash though, because if you break your phone and then check those threads to find your zip just to realize that they don't have your zip, then you're screwed. Please, please, please, PLEASE make a backup of your ROM. I'm here to fix problems with this ROM, not to fix your phone because you didn't backup your data.
Backup Without TWRP or Unlocked Bootloader (When you're trying to prepare for a bootloader unlock)
http://forum.xda-developers.com/showpost.php?p=69821066&postcount=38​
Alternative method :
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-unlocked-versions-t3552210
spicial thanks to @papampi​
Downloads:​Verizon Stock Unzipped: https://drive.google.com/open?id=0ByioJuadKHC6c3BkMnVydDRzQlk
EU Unzipped (WIP) by @erfanoabdi (See Post #17): https://drive.google.com/open?id=0B3HUyyOqyhD1N3FfQ2YyREhvdDA
Main Verizon Firmware Lolinet: https://mirrors.lolinet.com/firmware/moto/griffin/official/VZW/XT1650_GRIFFIN_VERIZON_6.0.1_MCLS24.246-36-3_cid2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Main Verizon Firmware Google Drive: https://drive.google.com/open?id=0ByioJuadKHC6MjJDXzhJSXlBaDA
Downloading Zips from Google Drive
http://forum.xda-developers.com/showpost.php?p=69821121&postcount=39​
New Downlaod Link :
Main RETMX Firmware : https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Main TELUS Firmware (NPL25.86-30) : https://mirrors.lolinet.com/firmwar..._subsidy-TELUS_regulatory-DEFAULT_CFC.xml.zip
Main RETUS Firmware (NPLS25.86-17-3-8) : https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Installation Guide:​Download and extract Main TELUS Firmware on PC
Make Sure You have backup of your whole Device [System, Boot, OEM, Data, Internal Storage]
Flash System, Boot, OEM, Fsg, Modem Partitons :
Code:
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
(continue it it has more chunks ...)
fastboot flash oem oem.img
fastboot flash fsg fsg.mbn
fastboot flash modem NON-HLOS.bin
fastboot erase cache
(fastboot erase userdata) (Not Needed But Recommanded)
Boot into TWRP :
Code:
fastboot boot twrp.img
(or flash it)
use adb sideload (Advanced -> ADB Sideload) and flash this ZIP from attachments to Disable Force-Encryption (Not needed but Recommanded)
Code:
adb sideload UPDATE-AnyKernel2.zip
wait to complete flashing
ROOT : (OPTIONAL)
Follow this Guide : https://forum.xda-developers.com/moto-z/how-to/guide-how-to-root-moto-z-supersu-t3551113
use adb sideload (Advanced -> ADB Sideload) and flash this ZIP from attachments to get systemless Root access
Code:
adb sideload superuser-r259.zip
Reboot
(For Rooted Guys) install phh's SuperUser From PlayStore : https://play.google.com/store/apps/details?id=me.phh.superuser&hl=en
(it's working and confirmed on XT1650-03 and 05, RETUS, EU, CN, ...)
ENJOY
After Installing Nougat With This Method You Can take Back to Stock Marshmallow Or Install New CM14.1 Builds This is safest and Easiest Method To Install Stock Nougat on Moto Z​
Why not help out XDA and spam click a few ads? (and then close the tabs cuz who really wants to buy stuff from ads lol. Either way, XDA gets money just for you clicking on them )​
XDA:DevDB Information
Android Nougat, ROM for the Moto Z
Contributors
SoulDJ673, erfanoabdi
ROM OS Version: 7.x Nougat
Based On: Stock Verizon Nougat OTA.zip
Version Information
Status: Stable
Created 2016-11-24
Last Updated 2017-07-16

Updates
Update 5:
Added erfanoadbi's EU port to the downloads list. We need testers!
Update 6:
When I added erfanoabdi as a contributor it reset this post lol. I've fixed it as much as I could though.
Update 7:
The system.data.patch file finished uploading on the Verizon Unzipped Link
Update 8:
Added installation instructions for the EU test to the OP
Update 9:
Added an alternative link for the Verizon firmware as some people were having problems with the first link
Update 10:
Added Google Zip Downloading and ADB Backup Information to OP
Update 11:
EU Test doesn't work
Update 12:
EU Test works now thanks to erfanoadbi's awesome work
Update 13:
Added stuff about Moto Voice error to OP​

ADB and Sideload​
If you don't know how to sideload, you'll first have to have adb installed on your pc. If you're on Windows, refer to @Snoop05's post here: http://forum.xda-developers.com/show....php?t=2588979 and download the installer for adb and fastboot. If you're on a Mac, refer to @AshtonTS's post here: http://forum.xda-developers.com/show....php?t=1917237. Also, be sure to throw these awesome people some thanks
For my fellow peoples on Linux:
Ubuntu: sudo apt-get install android-tools-adb android-tools-fastboot
Arch Linux: sudo pacman -S android-tools
Red Hat and others: You people are straight up savages and probably already know how to get a hold of it lol.
Open your terminal, the command prompt for Windows users, and cd to wherever the adb binary is (Linux users don't have to do this because it's already in your path, unless you installed it some way other than the package manager). Move the ota.zip to that directory. Enable USB debugging on the Moto (Settings > About Phone > Click Build Number 7 times, then Settings > Developer Options > USB Debugging) and then plug the Moto into your PC. Type "adb reboot recovery" (Mac users type "./adb reboot recovery"), and then wait. (If this doesn't work, look on the Moto and see if there's an authentication dialogue) On the Moto you'll soon see the Android robot lying on it's back and a red triangle above that. The screen will read "No command". Press and hold the power button for 2-3 seconds and then quickly also press Volume up and then release both buttons. On mine I have to do this button pressing thingy a few times, but eventually the recovery menu will come up. When it does, use the volume buttons to go down to the "Apply update via ADB" option and press the power button to select it. Go back to the computer and type "adb sideload ota.zip" (Mac users don't forget the "./" at the front) and it'll start to sideload the zip onto the phone. After that just wait and soon it'll install Nougat. (Ofc now we know that this isn't always the case)

I imagine the intention is to flash this from stock recovery rather than TWRP? I get E:footer is wrong E:Signature verification failed Installation Aborted

Stock recovery won't mount either the internal or external storage, and using adb sideload it just says
"unable to load ota.zip"
It doesn't appear to even try to open or verify the file itself, maybe it's too large?
I tried sideloading twrp.zip, just to see if it would do Anything at all, and that file is loaded and rejected (because my bootloader is locked)
I have reteu, not verizon, but I should at least get an error message.
Maybe I just have to wait, they claim to have begun rolling out world wide, but I've been hammering that update button once an hour since monday...

Via TWRP it gets stuck as it's expecting the Google folder in META-INF>Com. I added it from the original OTA and it's throwing up Griffin product name errors. Going to try a few things.

H00pyFr00d said:
I imagine the intention is to flash this from stock recovery rather than TWRP? I get E:footer is wrong E:Signature verification failed Installation Aborted
Click to expand...
Click to collapse
Yes, stock recovery is the goal but if you have TWRP then you can use that. Just know that the modem files and stuff are strictly for Verizon, so I wouldn't try to force flash it until I get those replaced.

H00pyFr00d said:
Going to try a few things.
Click to expand...
Click to collapse
Ok great

Shadowdancer123 said:
Stock recovery won't mount either the internal or external storage, and using adb sideload it just says
"unable to load ota.zip"
It doesn't appear to even try to open or verify the file itself, maybe it's too large?
I tried sideloading twrp.zip, just to see if it would do Anything at all, and that file is loaded and rejected (because my bootloader is locked)
I have reteu, not verizon, but I should at least get an error message.
Maybe I just have to wait, they claim to have begun rolling out world wide, but I've been hammering that update button once an hour since monday...
Click to expand...
Click to collapse
To be on the safe side, yeah I'd wait until the official OTA comes out. If you want it early tho that's cool too, just upload your current stock rom and I can play switcheroo on some necessary files.

With the limited backup capabilities of unrooted android and scarcity of fastboot rom files..
I'm just gonna sit here and click refresh on the update button. XD

Shadowdancer123 said:
With the limited backup capabilities of unrooted android and scarcity of fastboot rom files..
I'm just gonna sit here and click refresh on the update button. XD
Click to expand...
Click to collapse
Lol true. I'm gonna keep trying tho

SoulDJ673 said:
I was encouraged to make a separate thread for this, so I did.
Here we're going to try and port the Verizon Nougat update to all Moto Z phones.
I said I'd upload the code into GitHub to make it easier to change stuff, but that got too confusing so I just used Google Drive lol. Anyway, let's get started.
I'll start by editing the update script in the zip, and I'll need somebody to verify that it works. Just be forewarned that things might break (thus the alpha status). If things break, there are other threads with all the Marshmallow stock zip files, flash that and try again. Make sure to check those threads before you flash though, because if you break your phone and then check those threads to find your zip just to realize that they don't have your zip, then you're screwed. Please, please, please, PLEASE make a backup of your ROM. I'm here to fix problems with this ROM, not to fix your phone because you didn't backup your data.
Now that we've gotten that out of the way, here's the link to download it: null
Just so you know, if you try downloading it before around 13:00 EST, you won't have the full thing. My internet isn't the best, so it's gonna take a while.
Happy Thanksgiving everyone
Update:
Internet Crashed :/
Update 2:
I got most of the ota to upload but not all of it, but now as a wonderful Thanksgiving present I've got more drama in my life :/. I'll take a break for a day or two, hopefully Moto doesn't send out the rest of the OTAs so my attempts are for nothing.
XDA:DevDB Information
Android Nougat, ROM for the Moto Z
Contributors
SoulDJ673
ROM OS Version: 7.x Nougat
Based On: Stock Verizon Nougat OTA.zip
Version Information
Status: Alpha
Created 2016-11-24
Last Updated 2016-11-24
Click to expand...
Click to collapse
Hi @SoulDJ673, thanks for working on this project.
could you please give me list of files on this zip? is it contains "system.new.dat"?
could you please only upload "system.new.dat" for me, this shouldn't be heavy too mach
thanks again
_________
Sorry,
i found your uploaded zip here http://forum.xda-developers.com/showpost.php?p=69764157&postcount=42

I am going to make a flashable zip to night. It will probably work with EU version. Need to investigate..

janjan said:
I am going to make a flashable zip to night. It will probably work with EU version. Need to investigate..
Click to expand...
Click to collapse
Awesome, Thanks a lot.

Needing Only One or Two Small Files
erfanoabdi said:
Hi @SoulDJ673, thanks for working on this project.
could you please give me list of files on this zip? is it contains "system.new.dat"?
could you please only upload "system.new.dat" for me, this shouldn't be heavy too mach
thanks again
_________
Sorry,
i found your uploaded zip here http://forum.xda-developers.com/showpost.php?p=69764157&postcount=42
Click to expand...
Click to collapse
Sorry I didn't answer, where I'm at it was around 4 AM and I was too tired to do anything, and also I've been having some issues in my life rn. But, things are better so I'll be more present. For the future though, if you ever just need a small file I just added a Google Drive link with the unzipped ota so that way you won't have to download the whole 1.5GB zip

EU Version
janjan said:
I am going to make a flashable zip to night. It will probably work with EU version. Need to investigate..
Click to expand...
Click to collapse
Thanks a lot, it's been hard trying to even think of ways to port this without having any of the devices I'm trying to port it to lol. If it works, throw me a link and I'll put it in the header post and add you as a contributor.

SoulDJ673 said:
Sorry I didn't answer, where I'm at it was around 4 AM and I was too tired to do anything, and also I've been having some issues in my life rn. But, things are better so I'll be more present. For the future though, if you ever just need a small file I just added a Google Drive link with the unzipped ota so that way you won't have to download the whole 1.5GB zip
Click to expand...
Click to collapse
No problem bro
Thanks
But let me tell you you can't just patch updater-script to make it working on any unlocked devices.
As I see and tested on this zip file, Motorola OTA is working with system.patch.dat which means you have to find head system.img and patch this OTA file on it, I mean all files on this zip is only patchable on "mcls24.246-36-3" system firmware
So you(we) have to patch them on device and make backup of system partition and use it to flash via fastboot or emulate this progress some where else (other rooted device or Android emulator)
So far
I got mcls24.246-36-3 firmware and flashed on my device (everything looks fine)
And I started flashing system.patch.dat and system.new.dat on it but no success
I can verify system patch (very good) but I can't patch it
It seems this is bug of the TWRP I'm going to build google stock recovery without verification check and tell you result's.
I'll upload my works maybe it's useful
main firmware : https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
my zip : https://drive.google.com/open?id=0B3HUyyOqyhD1N3FfQ2YyREhvdDA

erfanoabdi said:
No problem bro
Thanks
But let me tell you you can't just patch updater-script to make it working on any unlocked devices.
As I see and tested on this zip file, Motorola OTA is working with system.patch.dat which means you have to find head system.img and patch this OTA file on it, I mean all files on this zip is only patchable on "mcls24.246-36-3" system firmware
So you(we) have to patch them on device and make backup of system partition and use it to flash via fastboot or emulate this progress some where else (other rooted device or Android emulator)
So far
I got mcls24.246-36-3 firmware and flashed on my device (everything looks fine)
And I started flashing system.patch.dat and system.new.dat on it but no success
I can verify system patch (very good) but I can't patch it
It seems this is bug of the TWRP I'm going to build google stock recovery without verification check and tell you result's.
I'll upload my works maybe it's useful
main firmware : https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
my zip : https://drive.google.com/open?id=0B3HUyyOqyhD1N3FfQ2YyREhvdDA (waiting for system.patch.dat)
Click to expand...
Click to collapse
Ok awesome, as for the updater-script, I didn't think that'd work but I thought maybe it could be a start. I'm still kinda new to this tbh. Thanks for the info though, it'll help me get better with this kind of stuff. I'm very skilled in Linux but Android is kinda different so it's a bit of a learning curve lol.

nice
papampi said:
Awesome, Thanks a lot.
Click to expand...
Click to collapse
thank you

Installation Guide Added on OP, Please test it

[ZE552KL/Z012DC] Canadian Thread - Unlock, Root, Update to Nougat

This thread will be for the Canadian version of ZE552KL, and will be updated with specific info relevant to Z012DC model found in Canada (Canada Computers, Staples, other retailers). It has WW SKU number.
It took me a while and some searching to figure all steps out. I also modified Asus N and M firmware to remove version checks. Without this step - i was stuck with error 7 in TWRP. The only difference between Z012D and Z012DC seems to be in Fastboot and ADB drivers, TWRP recovery, system images seem to work well so far.
Steps:
1. Download Fastboot and ADB Drivers. For me usb driver on ZE552KL Asus download page didn't work. Select "Only install driver", you do not need to update your drivers via DRP.
Fastboot driver (for Vendor VID_18D1&PID_D00D): http://drivers.drp.su/Telephone/Hua...03.00/Huawei-FORCED-Allx64-2.00.03.00-drp.exe
ADB Driver (for VID_18D1&PID_D002): http://drivers.drp.su/Telephone/Leshcat/WinAll/Leshcat-WinAll-drp.exe
2. Save the following files on your External SD Card:
Modified M image UL-ASUS_Z012D-WW-13.20.10.152-user.zip
Modified N image UL-ASUS_Z012D-WW-14.2015.1701.8-user.zip
SuperSU - latest version from here
no-verity-opt-encrypt-5-1.zip. Give thanks to @kaffeine1 , without him - we would all be stuck with black screens
3. Save ADB and Fastboot files on your computer, and extract; give thanks to @snowwolf725
4. Download newer recovery (TWRP 3.1.0) from here
5. Unlock bootloader via unofficial unlock method; give thanks to @snowwolf725
6. Get into fastboot by turning off the phone, and pressing volume up + power. Install recovery that you downloaded in step #4:
Code:
fastboot flash recovery twrp-3.1.0-0-Z012D.img
7. Follow the steps this guide by @kaffeine1 . Skip the steps of downloading Nougat and Marshmallow firmware from Asus site, as you have already downloaded and saved both firmwares in Step #2 . Also skip the last step - do not reboot into Nougat, but go back to fastboot mode.
8. Root Nougat - follow steps under #2 here:
https://forum.xda-developers.com/zenfone-3/how-to/twrp-recovery-3-0-2-root-zenfone-3-t3569926
How to update to the latest version of OS:
1. Go to Asus Site, download latest WW image UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip
2. Extract UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip\META-INF\com\google\android\updater_script , edit, remove first two lines, and put back into the zip file (e.g. using 7zip)
3. Extract from above zip file boot.img , and flash it via: fastboot flash boot boot.img
4. Flash recovery: fastboot flash recovery twrp-3.1.0-0-Z012D.img
5. Reboot into recovery, and flash:
- Firmware that you modified in #2
- no-verity-opt-encrypt-5.1.zip
- Latest SuperSU
- Rooted.zip (from step #8 above)
6. Reboot mobile, and enjoy new version!
Phone info as purchased:
Model Number: ASUS_Z012DC
Android version: 6.0.1
Baseband version: M3.10.42-Libra_080001
Build number: MMB29P.WW_Phone-13.20.10.152-20161222
Manufacture date (on the box): January 2017
Latest version - UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip
Model Number: ASUS_Z012DC
Android version: 7.0
Baseband version: M3.10.47-Libra_080001
Build number: NRD90M.WW_Phone-14.2020.1703.28-20170410
Special thanks to:
- @jcadduono for TWRP recovery
- @snowwolf725 for guide unlock bootloader
- @kaffeine1 for guide how to upgrade to N from M

Reserved for future use

can i follow this step for ZE520KL ?

I got my self a canadian vertion ZE552KL, but i can´t seem to fully unlock the boot loader, it goes onto fastboot, but it does not allow me to flash anything it gives a permision denied .
when i tried to flash fw from sdcard gives a error: the the sku is "WW_" and mine is ""
have you came across this problem.
how can it be solved?
thanks

lastremnant said:
can i follow this step for ZE520KL ?
Click to expand...
Click to collapse
no, I do not think so. these are different phones.

DilipRB said:
I got my self a canadian vertion ZE552KL, but i can´t seem to fully unlock the boot loader, it goes onto fastboot, but it does not allow me to flash anything it gives a permision denied .
when i tried to flash fw from sdcard gives a error: the the sku is "WW_" and mine is ""
have you came across this problem.
how can it be solved?
thanks
Click to expand...
Click to collapse
try first flashing 6.0.1 firmware from asus site and then modified 7.0 firmware. if the error is when flashing 6.0 fw - try modified 6.0. and do paste specific rrror.

anterus said:
no, I do not think so. these are different phones.
Click to expand...
Click to collapse
nevermind sir, it worked for me

Strange things do happen!!!
anterus said:
try first flashing 6.0.1 firmware from asus site and then modified 7.0 firmware. if the error is when flashing 6.0 fw - try modified 6.0. and do paste specific rrror.
Click to expand...
Click to collapse
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????

DilipRB said:
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????
Click to expand...
Click to collapse
backup those zips, open with winrar or another app. open meta-inf/android/google/updater-script with notepad++ try deleting from ifelse until ) );
save and let winrar save new update

lastremnant said:
backup those zips, open with winrar or another app. open meta-inf/android/google/updater-script with notepad++ try deleting from ifelse until ) );
save and let winrar save new update
Click to expand...
Click to collapse
Tryed that, and got footer error...
seems that to modifying the script file and then recompresing will change the compretion check algorithem. giving a footer error.
i should try pakaging the apk again...
there was a program to do so but i cant recall which...
thks

DilipRB said:
Tryed that, and got footer error...
seems that to modifying the script file and then recompresing will change the compretion check algorithem. giving a footer error.
i should try pakaging the apk again...
there was a program to do so but i cant recall which...
thks
Click to expand...
Click to collapse
i found it ...
apktool from :
https://forum.xda-developers.com/showthread.php?t=1989533
Sorry this was for apks... but i guess same principle aplies... when i can i shall try and post the outcome

DilipRB said:
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????
Click to expand...
Click to collapse
I noticed that in some cases TWRP doesn't "stick", and gets overridden by default bootloader. Specific check is essentially useless - just to prevent flash of improper image. Just remove the check in the new FW, or use modified FW that has the check removed. I think in your case you can just re-flash TWRP since your bootloader is unlocked?

I tryed several TWRP 3.02 and 3.10 if a boot imge ... if entered bootloader with volum key + power it says all ok but booting never happens... if i enter bootloader trough adb it stucks until i disconnect and reconnect usb cable. when trying to flash. fast boot returns error not have permision and side load error secttion 7 on UL modified or else footer w
error after passing check. i shall try modiffying UL 13.20.10 and see what happens

DilipRB said:
I tryed several TWRP 3.02 and 3.10 if a boot imge ... if entered bootloader with volum key + power it says all ok but booting never happens... if i enter bootloader trough adb it stucks until i disconnect and reconnect usb cable. when trying to flash. fast boot returns error not have permision and side load error secttion 7 on UL modified or else footer w
error after passing check. i shall try modiffying UL 13.20.10 and see what happens
Click to expand...
Click to collapse
flash modified images through twrp - with links in OP

Well my wife liked the phone so much, that she "kindly requested" me to gift it to her... now she is the proud owner of a canadian vertion of ZE552KL and i got myself a ZS570KL
thanks a lot for all your help.
P.D. : i think she was not happy with the time i was spending with the device.

I know this is going to sound super dumb, but the unofficial bootloader unlock still triggers the bootup message and voids the warranty, right?

This might be even dumber... But my guess is that the official app to unlock boot loader, does more than unlock,
My guess is that it also register with asus mobile, the fact that for your device has been unlocked...

DilipRB said:
This might be even dumber... But my guess is that the official app to unlock boot loader, does more than unlock,
My guess is that it also register with asus mobile, the fact that for your device has been unlocked...
Click to expand...
Click to collapse
That's what some manufacturers do, like Motorola and HTC. But from back when I unlocked the BL on my Zenfone 2 Laser, I remember that all it did (as far as I could tell) was unlock the bootloader and set a flag in the bootloader that made it say it was unlocked that couldn't be reversed. No need for fancy registration systems when you can just boot up the phone and take a look.

What was modified in your N-image firmware file? There is now a newer version that I'd like to install. Can you provide an updated modified file for version WW-14.2020.1703.28 or give the steps needed to modify it myself?

Jarrick said:
What was modified in your N-image firmware file? There is now a newer version that I'd like to install. Can you provide an updated modified file for version WW-14.2020.1703.28 or give the steps needed to modify it myself?
Click to expand...
Click to collapse
Updated OP with instructions regarding how to upgrade to the latest version of N - just tested steps myself. Should be applicable to all future versions of N posted on Asus site. Enjoy!

Lineage OS 13 Port for BLU_Studio_XL_2

:good:
I have cm13 ported over from different Phone (Blu Life_Max) and booting.
already working
1. wifi
2. camera but not video camera
3. bluetooth audio
4. loud speaker audio
5. FM Radio
6. cell in sim1 and sim2 slot, but sim2 only gets H+ speed(5-10Mbps)
SIm1 gets 4G(LTE) speeds on test 50Mbps Both tests with freedomPop
known issue (mostly camera related)
1. videocamera causes camera crash
2. selfie-camera not available **Fixed with V6**
3. panarama shot crashes camera
4. NFC not able to turn on (stock rom did not have NFC, so this may not be possible to work) : next update may remove this **fixed in V5**
V7 -- Hassome permission changes in boot.img that were found in logcat, for "SMI"
still not working videocamera
To install:
1. Must be bootloader unlocked
.
How to Unlock Bootloader via Fastboot
1. Setup ADB and Fastboot on your PC.
2. Enable USB debugging and OEM Unlock on your Android device.
3. Connect your device to the PC with a USB cable.
4. Open a command window on your PC.
5. Boot your device into bootloader mode using the following command:
Code:
adb reboot bootloader
└ You may get a request to authorize USB debugging on the device, accept it.
6. Once your device is in bootloader mode, issue the following command to unlock bootloader:
Code:
fastboot oem unlock
You get a confirmation screen on your device. Press Volume Up button to highlight Yes and press Power button to select it.
This will begin bootloader unlocking process, which shouldn’t last more than couple of minutes.
7. Once bootloader is unlocked, your device will reboot into bootloader mode. You need to boot it into system now using the command below:
Code:
fastboot reboot
During reboot, your device will go through a factory reset and then finally boot into system.
2. Install included twrp(New kernel for recovery allows touchscreen to work)
***PRIOR RELEASES NEED TO USE LOPESTOM RECOVERY TO INSTALL***
Due to different moint point descriptions Future versions(If they come) will use block number moints to be compatible with both
******V-7-Block is compatible with both recoveries
1. make sure developer options is enabled
2. Reboot to bootloader
Code:
adb reboot bootloader
3. Test recovery works for your device
(example commands assume you have the vampirefo version of recovery downloaded to the desktop)
Code:
Fastboot boot Desktop/recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img
4. If recovery boots good, then return to bootloader and flash (commands work from in booted twrp)
These steps are what I find to be best order to prevent the stock rom from replacing the stock recovery on boot.
Code:
fastboot flash recovery Desktop/recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img
fastboot boot Desktop/recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img
adb wait-for-device
adb reboot recovery
3. If first install. do wipe and wipe system too. If Updating no wipe needed
Sources:
Rom not built for this device Built for Blu Life-Max --no thread to link, sorry
Rom uses the stock kernel, pulled from oem device (studio_XL_2)
keeping a git of files swapped to make rom work
https://github.com/mrmazakblu/BLU_Studio-XL-2_port_from_Life-Max
kernel source for recovery:
https://github.com/mrmazakblu/Blu_studio-XL_2_kernel_source
Other projects for Studio_XL_2:
Reserrection Remix Port
XDA:DevDB Information
blu-studio-xl-2, ROM for all devices (see above for details)
Contributors
mrmazak, Thanks to vampirefo --building donor rom
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: BLU-Studio-XL-2--BLU_S0270UU_V09_GENERIC
Based On: Lineage OS
Version Information
Status: Testing
Created 2017-10-30
Last Updated 2017-11-30

New TWPR kernel
Reserved

TWRP touchscreen
new kernel for TWRP allows touchscreen to work when recovery is flashed to device.
thanks to @vampirefo for finding a fix for Life-Max. Same fix worked here too.
New kernel is also put into @lopestom twrp.
Choose either one they both work.

Thanks for porting. I'm looking forward to testing it with my Studio XL2

killer13666 said:
I tried flashing it like you said and this is what happened....
Code:
Installing zip file '/external_sd/BLU_Studio-XL-2_port_from_Life-Max-V-7.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Update binary zip
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
Target: Blu Studio XL 2
Target: Blu Studio XL 2Check if system is already mounted
Check if system is already mountedcould not detect filesystem for /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system, assuming ext4could not detect filesystem for /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system at /system: No such file or directorymount: failed to mount /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system at /system: No such file or directoryRunning backup script for update installsabout to run program [/tmp/install/bin/backuptool.sh] with 2 args
Running backup script for update installs
run_program: child exited with status 127
unmount of /system failed; no such volumeChecking if Data is compatableunmount of /system failed; no such volume
Checking if Data is compatable
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
You have an installed system that isn't signed with this build's key, aborting...
run_program: child exited with status 124
script aborted: Can't install this package on top of incompatible data. Please try another package or run a factory reset
Can't install this package on top of incompatible data. Please try another package or run a factory reset
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
I:Install took 14 second(s).
Error installing zip file '/external_sd/BLU_Studio-XL-2_port_from_Life-Max-V-7.zip'
Updating partition details...
Click to expand...
Click to collapse
Do not know why you have failed to mount /system error could be because you have /system set to be read only.
In install directions it says need to wipe /data
and
also advanvance wipe /system
second error says imcompatable /data == this means you did not wipe data before installing.
Please continue here in the rom thread.

mrmazak said:
Do not know why you have failed to mount /system error could be because you have /system set to be read only.
In install directions it says need to wipe /data
and
also advanvance wipe /system
second error says imcompatable /data == this means you did not wipe data before installing.
Please continue here in the rom thread.
Click to expand...
Click to collapse
I figured out what the problem was. For some reason, the recovery image you supplied wasn't mounting the system partition properly. I used a different image and the ROM flashed perfectly

killer13666 said:
I figured out what the problem was. For some reason, the recovery image you supplied wasn't mounting the system partition properly. I used a different image and the ROM flashed perfectly
Click to expand...
Click to collapse
please let me know which one worked for you and which one did not.
I think I was using the one marked 3.1.1 (vampirefo) but now I am not sure.
I may do independet testing again on both, but would appreciate your input.
Just confirmed there is a problem with the combination of the update-binary used in these install zips and the vampirefo recovery. The fix can be either i use different update-binary file or you use lopestom recovery.
**EDIT**
Problem was with the my updateer-script. I put fixed install packages up.

Thanks for the port my version is v06.0.04.00_generic 16/06/2017
I have a unlocked phone from best buy
I keep seeing everyone say v09 mine has updated twice wondering if it will work on mine or if I need to update somehow

ahnuts72 said:
Thanks for the port my version is v06.0.04.00_generic 16/06/2017
I have a unlocked phone from best buy
I keep seeing everyone say v09 mine has updated twice wondering if it will work on mine or if I need to update somehow
Click to expand...
Click to collapse
I dont see any version of my stock OS that is similar to that number you have.
When I had stock installed, In the settings screen, about phone listed the build version as
Code:
BLU_S0270UU_V09_GENERIC
This port is for Blu_Studio_XL_2 make sure that is device you have.
If you look in the build.prop you will get more information about the device.
if you want to , you can pull the build.prop and post it , so I can see
Code:
adb pull /system/build.prop Desktop\build-prop.txt
then attach the file here.

According to the device in about phone mine is studio xl 2 and that was what the box said when I purchased the phone at best buy

And this one shows the version

And this one shows the version

Wrong pic

ahnuts72 said:
Wrong pic
Click to expand...
Click to collapse
The dates show it is a newer software than what I had, but this should still work, as long as you are still able to unlock the bootloader.

In the developer options I have a setting that says oem unlocking allow the bootloader to be unlocked will that work or will I have to still do it from adb

ahnuts72 said:
In the developer options I have a setting that says oem unlocking allow the bootloader to be unlocked will that work or will I have to still do it from adb
Click to expand...
Click to collapse
here is guide.
https://www.theandroidsoul.com/unlock-bootloader-via-fastboot-android/
the unlocking does do a complete wpe on the data part of the phone. so if you have pictures or music or any files you want to keep , make sure to copy first. Also to be safe , if you have external sdcard in , take it out before doing unlock
****
****
Must complete the unlock as the guide shows includeing the reboot, so stock recovery does its wipe, I t is important part of the unlock.
**
**
after unlocked,
to flash recovery, enable developer options again, enable usb debugging. authorize adb connection to your pc-
Code:
adb reboot bootloader
fastboot boot recovery.img
**recovery.img = "full path to the downloaded recovery"
**example if you downloaded the vampire based recovery and you downloaded to the desktop**
Code:
fastboot boot Desktop/recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img
after booted to recovery and it works return to bootloader and flash it to phone. I allways recomend this boot first method to verify it recovery works. You cant be certain every od will work on every device. Better safe than sorry.
select reboot menu from recovery and then select reboot bootloader.
Due to a securety measure android has (recovery-from-boot) when replacing recvoery to need to boot directly to new recovery to prevent the android system from replacing it with stock version. so I use the steps below
Code:
fastboot flash recovery Desktop/recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img
fastboot boot Desktop/recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img
adb wait-for-device
adb reboot recovery
.

Android 6 or 7, plus install questions
Hi, I have rooted several phones but the procedure keeps getting more difficult. I see the instructions for installing recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img but I am curious what is on this image .... will it be rooted and if so, what version of Android is bundled? Will the phone then support Xposed and Xprivacy?
From what I can determine, the video camera is not working with your most recent release, V8, is this correct?
Thank you for your assistance!

Donphillipe said:
Hi, I have rooted several phones but the procedure keeps getting more difficult. I see the instructions for installing recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img but I am curious what is on this image .... will it be rooted and if so, what version of Android is bundled? Will the phone then support Xposed and Xprivacy?
From what I can determine, the video camera is not working with your most recent release, V8, is this correct?
Thank you for your assistance!
Click to expand...
Click to collapse
LineageOS 13 is android 6
there is no V8 only upto V7
video recording does not work
Lineage has root built in. Enable it in developer options
I do not know about xposed I not use it
Donphillipe said:
" I see the instructions for installing recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img but I am curious what is on this image "
Click to expand...
Click to collapse
That image is TWRP recovery only
I have not been working on this anymore.
I have ported "better" Resurection rom based on android 7 , have been using it as a daily use phone for just over a month now
https://forum.xda-developers.com/android/development/-t3699638

I appreciate your patience with someone who only dabbles in this hobby. When you say that the install image is TWRP only, what exactly does this mean?
I know I have owned several BLU phones and each time I tried to install a high-end recovery tool in the past, the list of supported phones on the recovery software list would never include my BLU device, saying something to the order of the source needing to be recompiled (as I recall) or something to that order which never seemed to happen. So are there additional steps for getting the phone to the point it will take this image other than the steps you outlined for unlocking the boot loader? Or what do I need to be aware of?
Also, do you have a backup of the factory image available in case something goes wrong, with basic instructions on how to recover the phone back to the factory version? Or is there something I can install or do on this phone to create a backup copy on my own?
Again I am sorry to have to ask for what to some appears a simple procedure. I do appreciate your going to the effort when you have already contributed so much with your images. Thank you!

Donphillipe said:
I appreciate your patience with someone who only dabbles in this hobby. When you say that the install image is TWRP only, what exactly does this mean?
I know I have owned several BLU phones and each time I tried to install a high-end recovery tool in the past, the list of supported phones on the recovery software list would never include my BLU device, saying something to the order of the source needing to be recompiled (as I recall) or something to that order which never seemed to happen. So are there additional steps for getting the phone to the point it will take this image other than the steps you outlined for unlocking the boot loader? Or what do I need to be aware of?
Also, do you have a backup of the factory image available in case something goes wrong, with basic instructions on how to recover the phone back to the factory version? Or is there something I can install or do on this phone to create a backup copy on my own?
Again I am sorry to have to ask for what to some appears a simple procedure. I do appreciate your going to the effort when you have already contributed so much with your images. Thank you!
Click to expand...
Click to collapse
The recovery image (TWRP) works for this device.
Yes recovery images, just like android roms are specific to each different device. This one has been edited to work for Studio XL 2
The TWRP is a custum recovery needed to install the custom ROM
The steps are complete, you shouldn't need anything else (need adb and fastboot)
Yes stock recovery image is available. Installing back to stock recovery is same steps as installing custom recovery.
both can be done as described with fastboot. Or both can be installed using SPFT (smart phone flash tool)