Related
Now CM appear to have disabled their links to official roms, updates & kernels for older builds, I've mirrored them all on AndroidFileHost and put the links in one post so that they're easy to find.
There are different files for each ROM: signed fastboot flashable zips, signed zips, OTA incremental update zips., boot-debuggable images and stock recovery images.
Signed fastboot flashable zips: These contain the complete rom and can overwrite everything including your data partition. These cannot be flashed via recovery - extract their contents and flash via fastboot. Due to changes in bootloader, don't use them to upgrade from CM 11S to CM 12S or downgrade from CM 12S to CM 11S.
Signed zips: Normal recovery-flashable zips that contains just the system and kernel (they won't overwrite your data partition).
OTA incremental update zips: These are recovery-flashable zips that update your rom to a newer version. To check which version you are running, look at the ro.build.version.incremental line in your /system/build.prop file and then update incrementally.
Boot-debuggable images: These are boot images (kernels) that enable adb root and the developer menu options. To be flashed via fastboot.
Stock recovery images: These are stock recovery images which are recommended for applying OTA incremental update zips. To be flashed via fastboot.
NOTE: Both Yureka & Yureka Plus share same firmware, but don't use pre-cm-12.0-YNG1TAS34J builds on Yureka Plus - the device will be soft-bricked!
Signed fastboot flashable zips
cm-12.1-YOG4PAS8A4-tomato-signed-fastboot-a7a306cebd.zip
cm-12.1-YOG4PAS3JM-tomato-signed-fastboot.zip
cm-12.0-YNG1TAS34J-tomato-signed-fastboot.zip
cm-12.0-YNG1TAS1K0-tomato-signed-fastboot.zip
cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip
cm-11.0-XNPH05Q-tomato-signed-fastboot.zip
cm-11.0-XNPH52O-tomato-signed-fastboot.zip
Signed zips
cm-12.1-YOG4PAS8A4-tomato-signed-224c88c4ef.zip
cm-12.1-YOG4PAS3JM-tomato-signed.zip
cm-12.0-YNG1TAS34J-tomato-signed.zip
cm-12.0-YNG1TAS1K0-tomato-signed.zip
cm-12.0-YNG1TAS0W0-tomato-signed.zip
cm-11.0-XNPH05Q-tomato-signed.zip
OTA incremental update zips
YOG4PAS8A4 from YOG4PAS3JM: cm-tomato-04864afef4-to-5242dd42b2-signed.zip
YOG4PAS6ZA from YOG4PAS3JM: cm-tomato-04864afef4-to-f758a6e288-signed.zip
YOG4PAS3JM from YNG1TAS34J: cm-tomato-c991cd279d-to-04864afef4-signed.zip
YOG4PAS3JM from YNG1TAS1K0: cm-tomato-00b2e333e8-to-04864afef4-signed.zip
YNG1TAS34J from YNG1TAS1K0: cm-tomato-00b2e333e8-to-c991cd279d-signed.zip
YNG1TAS1K0 from YNG1TAS0W0: cm-tomato-56deeca328-to-00b2e333e8-signed.zip
XNPH05Q from XNPH52O: cm-tomato-efbb5514a1-to-9828f8e9cc-signed.zip
Boot-debuggable images
cm-12.1-YOG4PAS8A4-tomato-boot-debuggable-8bc066a691.img
cm-12.1-YOG4PAS3JM-tomato-boot-debuggable.img
cm-12.0-YNG1TAS34J-tomato-boot-debuggable.img
cm-12.0-YNG1TAS1K0-tomato-boot-debuggable.img
cm-12.0-YNG1TAS0W0-tomato-boot-debuggable.img
cm-11.0-XNPH05Q-tomato-boot-debuggable.img
cm-11.0-XNPH52O-tomato-boot-debuggable.img
Stock recovery images
cm-12.1-YOG4PAS8A4-tomato-recovery.img
cm-12.1-YOG4PAS3JM-tomato-recovery.img
cm-12.0-YNG1TAS34J-tomato-recovery.img
cm-12.0-YNG1TAS1K0-tomato-recovery.img
cm-12.0-YNG1TAS0W0-tomato-recovery.img
cm-11.0-XNPH05Q-tomato-recovery.img
cm-11.0-XNPH52O-tomato-recovery.img
Credits
@Spannaa for the inspiration.
@AndroidFileHost for the hosting.
YU for the device.
Cyanogen for making the OS.
Reserved for future.
First post updated; added YNG1TAS1K0 build.
Can't flash the YNG1TAS1K0 from YNG1TAS0W0 ota update,
Installations error on custom recovery and stock recovery too
how do i verify that latest S1k0 fastboot update is authentic sir??
you said that they have disabled the updates so any way to verify?
sal_rc said:
Can't flash the YNG1TAS1K0 from YNG1TAS0W0 ota update,
Installations error on custom recovery and stock recovery too
Click to expand...
Click to collapse
This is a common symptom noticed by other users. In that use, use the full update zip i.e cm-12.0-YNG1TAS1K0-tomato-signed.zip.
milav said:
how do i verify that latest S1k0 fastboot update is authentic sir??
you said that they have disabled the updates so any way to verify?
Click to expand...
Click to collapse
I haven't told that CM has disabled the updates; instead they periodically removes old updates. Files related to YNG1TAS1K0 are directly grabbed from CM server, so they are 100% authentic.
Titokhan said:
This is a common symptom noticed by other users. In that use, use the full update zip i.e cm-12.0-YNG1TAS1K0-tomato-signed.zip.
Should I do factory reset too afterwards?
Click to expand...
Click to collapse
@sal_rc
Not mandatory, but you can.
Titokhan said:
@sal_rc
Not mandatory, but you can.
Click to expand...
Click to collapse
my bootloader will be locked again? Right?
@sal_rc
No, flashing OTA will not re-lock the bootloader.
Titokhan said:
@sal_rc
No, flashing OTA will not re-lock the bootloader.
Click to expand...
Click to collapse
I was afraid I'd have to do it all over again
Thanks anyways
Titokhan said:
This is a common symptom noticed by other users. In that use, use the full update zip i.e cm-12.0-YNG1TAS1K0-tomato-signed.zip.
I haven't told that CM has disabled the updates; instead they periodically removes old updates. Files related to YNG1TAS1K0 are directly grabbed from CM server, so they are 100% authentic.
Click to expand...
Click to collapse
thnks bro as being latest update i request you to provide fastboot link direct from cm server old links can be on androidfilehost thats good
thnks for links btw dnlding latest fastboot files now
cheers
What are these bootable image??
I am in twrp recovery with sandy kernel in lollipop 5... Can you please tell how to go back to stock recovery for the updating latest ota. Thanks in advance
Titokhan said:
Reserved for future.
Click to expand...
Click to collapse
hey bro i am on 5.0.2.i want to flash stock kernel can you please tell me which one should i flash ? and which process should i follow ?
using fastboot but what is the command ?
@m_rajaganesh
Depends on the build version; it would be better to install latest stock recovery via fastboot & then flash the full OTA manually.
@ashish_zarekar
Tell me the exact build number. Choose the appropriate one & flash:
Code:
fastboot -i 0x1ebf flash boot boot.img
Titokhan said:
@m_rajaganesh
Depends on the build version; it would be better to install latest stock recovery via fastboot & then flash the full OTA manually.
@ashish_zarekar
Tell me the exact build number. Choose the appropriate one & flash:
Code:
fastboot -i 0x1ebf flash boot boot.img
Click to expand...
Click to collapse
build number is "LRX22G"
cyanogen os version "12.0-YNG1TAS1K0".
ashish_zarekar said:
build number is "LRX22G"
cyanogen os version "12.0-YNG1TAS1K0".
Click to expand...
Click to collapse
Then download cm-12.0-YNG1TAS1K0-tomato-signed-fastboot.zip, extract boot.img from it & flash.
Titokhan said:
Then download cm-12.0-YNG1TAS1K0-tomato-signed-fastboot.zip, extract boot.img from it & flash.
Click to expand...
Click to collapse
can i download direct boot.img from your list and flash it via fastboot ?
Hi guys,
would someone with Android 7.0 final build be so kind and send me a TWRP backup of the vendor parition/bootloader/radio?
I built AOSP for the Nexus 5X, but it is no good without the according blobs, and factory images are not online yet
Thanks for your help!
Here's the OTA image with all those files you need:
https://android.googleapis.com/pack.../cd8d8f775bcdb6a76a496a3a664caba0b9ed47f9.zip
sprremix said:
Here's the OTA image with all those files you need:
https://android.googleapis.com/pack.../cd8d8f775bcdb6a76a496a3a664caba0b9ed47f9.zip
Click to expand...
Click to collapse
Ah yes, I can install the previous factory image and flash OTA. Thanks for the idea :good:
Factory images for 5X are now online.
miisterlim said:
Factory images for 5X are now online.
Click to expand...
Click to collapse
And brick phones
Factory image works just fine, make sure you have the latest fastboot and adb, and give it time.
@petrus764 where to download the latest fastboot?
Thank you for your understanding.
Danielf85 said:
@petrus764 where to download the latest fastboot?
Thank you for your understanding.
Click to expand...
Click to collapse
I use minimal adb and fastboot which comes with version 1.0.35 rc and that works for me.
http://forum.xda-developers.com/showthread.php?t=2317790
Apparently there's a newer version too, 1.0.36 which you can get from here http://forum.xda-developers.com/htc-one/general/tool-updated-adb-version-1-0-32-fastboot-t2932160
of course the latest is always available via the android sdk, but who can be bothered download all of that just for adb and fastboot.
Hi I am new to the Nexus 5x and need assistance. I dont know what factory image from https://developers.google.com/android/images#bullhead I need if I have metro pcs. And every time I need to go into custom recovery do I need to flash it threw bootloader with the custom rom folder in the adb folder? Please someone help me I am really confused
HaxUrMom69 said:
Hi I am new to the Nexus 5x and need assistance. I dont know what factory image from https://developers.google.com/android/images#bullhead I need if I have metro pcs. And every time I need to go into custom recovery do I need to flash it threw bootloader with the custom rom folder in the adb folder? Please someone help me I am really confused
Click to expand...
Click to collapse
Factory images are universal for this device. All carriers are supported. Just flash the June factory image.
You can flash the boot, system, recovery, and vendor images through TWRP. Those same images can be flashed in the bootloader. Radio and bootloader images must be flashed in bootloader. Does that answer your question? If not, read my guide and see if that resolves your questions:
https://forum.xda-developers.com/showthread.php?t=3206930
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Factory images are universal for this device. All carriers are supported. Just flash the June factory image.
You can flash the boot, system, recovery, and vendor images through TWRP. Those same images can be flashed in the bootloader. Radio and bootloader images must be flashed in bootloader. Does that answer your question? If not, read my guide and see if that resolves your questions:
https://forum.xda-developers.com/showthread.php?t=3206930
Click to expand...
Click to collapse
So when you install a new rom you don't need to flash the vendor image also? Because some ROMs say to also flash vendor image when installing a rom
tactical bacon said:
So when you install a new rom you don't need to flash the vendor image also? Because some ROMs say to also flash vendor image when installing a rom
Click to expand...
Click to collapse
This is covered in-depth with FAQ #9 of my link above. But in short, each monthly security update brings a new vendor image that must be installed. Each time your rom updates to a new month's security update, you need to install that vendor image. If you flash back to a previous month's rom, you need to flash that respective vendor image. Only exception is if your rom includes the vendor image in the rom zip.
Sent from my Nexus 5X using Tapatalk
Sorry one last question. I am on the latest security update stock, if I was to flash the latest AOSP extended on the latest security update all I would have to do is flash the ROM and gapps? But when the new security update is added to the ROM then I would flash the vendor image. Sorry if I'm asking to many questions but I don't want to run into a problem.
tactical bacon said:
Sorry one last question. I am on the latest security update stock, if I was to flash the latest AOSP extended on the latest security update all I would have to do is flash the ROM and gapps? But when the new security update is added to the ROM then I would flash the vendor image. Sorry if I'm asking to many questions but I don't want to run into a problem.
Click to expand...
Click to collapse
You're fine, ask away! Yes to both questions. Let's say the July security update is released for your custom rom. You would flash the July vendor.img then your rom and then that's it.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
You're fine, ask away! Yes to both questions. Let's say the July security update is released for your custom rom. You would flash the July vendor.img then your rom and then that's it.
Click to expand...
Click to collapse
Just one more thing. I just realized there is no sd slot. where would I put the ROM and gapps
tactical bacon said:
Just one more thing. I just realized there is no sd slot. where would I put the ROM and gapps
Click to expand...
Click to collapse
I have my stuff in subfolders inside /sdcard
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
I have my stuff in subfolders inside /sdcard
Click to expand...
Click to collapse
Thanks for the help. I just flashed asop extended and everything works fine. Do you have a recommended ROM for stability?
Simple question
The August radio included in the developer image is horrible! Lots of battery life wasted.
Sent from my Pixel XL using Tapatalk
abuttino said:
Simple question
The August radio included in the developer image is horrible! Lots of battery life wasted.
Click to expand...
Click to collapse
You can flash any radio you want. I'm currently running DP3 radio and modem. The May update radio is also really good for me.
Golf c said:
You can flash any radio you want. I'm currently running DP3 radio and modem. The May update radio is also really good for me.
Click to expand...
Click to collapse
Do you just download the full file and extract the radio file and push through ADB or is there separate .zip files to flash? Thanks
john7760 said:
Do you just download the full file and extract the radio file and push through ADB or is there separate .zip files to flash? Thanks
Click to expand...
Click to collapse
Download the full file and extract the radio and modem. I do both. I don't know if that's necessary but it makes me feel better. I fastboot it.
fastboot flash radio -- slot all radio.img
Golf c said:
Download the full file and extract the radio and modem. I do both. I don't know if that's necessary but it makes me feel better. I fastboot it.
fastboot flash radio -- slot all radio.img
Click to expand...
Click to collapse
I've flashed the boot to a & b to be able to sideload, but i'm not sure on the command for "slot all" to use. Is it the same? I've been less that impressed with the last couple of radio/modem's as far as signal goes for me in my area.
john7760 said:
I've flashed the boot to a & b to be able to sideload, but i'm not sure on the command for "slot all" to use. Is it the same? I've been less that impressed with the last couple of radio/modem's as far as signal goes for me in my area.
Click to expand...
Click to collapse
Radios are really hit and miss For me too. Im on tmobile and the tmobile radios have been horrible for me. The May update radio has been the best. The slot all fastboot command is just one command instead of three commands.
Where are you guys getting the radios from? I can't find any of the new ones, because all of the threads that I have found on here have not been updated in a while.
Probably a stupid one to ask, but does flashing the vendor image update the modem?
Thanks!
bigal1542 said:
Where are you guys getting the radios from? I can't find any of the new ones, because all of the threads that I have found on here have not been updated in a while.
Probably a stupid one to ask, but does flashing the vendor image update the modem?
Thanks!
Click to expand...
Click to collapse
We are extracting them from the Google factory images
Golf c said:
We are extracting them from the Google factory images
Click to expand...
Click to collapse
Hi , can you just upload this radios and modem files ?
i search a lot in this forum and cant find any radios or modem updates ....
thanks
daniking said:
Hi , can you just upload this radios and modem files ?
i search a lot in this forum and cant find any radios or modem updates ....
thanks
Click to expand...
Click to collapse
.
They are found within googles factory images. From google site download image that contains radio you want, unzip it and you will find radio and modem images.
I'm on stock vzw, 8.0, locked bootloader..... Can I flash the radio & modem from the 8.1 preview? If so would I need to flash anything else (bootloader, etc....)?
TIA
TheCelt said:
I'm on stock vzw, 8.0, locked bootloader..... Can I flash the radio & modem from the 8.1 preview? If so would I need to flash anything else (bootloader, etc....)?
TIA
Click to expand...
Click to collapse
You can't flash anything with a locked bootloader
Born<ICs said:
.
They are found within googles factory images. From google site download image that contains radio you want, unzip it and you will find radio and modem images.
Click to expand...
Click to collapse
Thanks. But can you just give me a link of that?
daniking said:
Thanks. But can you just give me a link of that?
Click to expand...
Click to collapse
. Factory images.
https://developers.google.com/android/images#marlin
If you want to repost this internal OTA to other websites (other than XDA itself), please ask me for permission, thanks.
Click to expand...
Click to collapse
WARNING!
This is early internal test build, so LATER OTA UPDATES CAN'T BE GUARANTEED!
If you don't have unlocked bootloader, you'll unable to roll back to stable build!
Please be careful when testing!
Click to expand...
Click to collapse
Now I think it's time to bring you back to canary labs faster than beta labs.
Internal build version: CTL-4040-0-00WW-B01
It will be updated from: CTL-354K-0-00WW-B01, which is not pushed to public
As I've warned before - having an unlocked bootloader is strongly recommended.
So recent builds removed handy 874 dialing codes, we have to install them under recovery or Nokia Extensions.
UPDATE: Thanks everyone. To fix microphone bug, please disable the microphone permission of the "Google" app.
You'll lose "OK Google" ability, but you can make telephone call properly.
Click to expand...
Click to collapse
Let me tell you how to verify:
1. Dial *#*#227#*#* to check current Version. If older than CTL-354J-0-00WW-B01 (check if the letter is greater than J), update to 354J before proceed.
FYI, 354J is August 2019 Security Update.
Alternately, you can use command "fastboot oem getversions" under fastboot mode / Download mode to check current firmware version.
If newer than 354J (probably 354N when this post released), you'll need to downgrade your phone back to at most 354H - which can't be done easily without unlocked bootloader.
2. Install CTL-354K-0-00WW-B01-354J-0-00WW-B01-update.zip with Nokia Extensions OTA Update module or adb sideload under recovery.
3. Reboot your phone.
4. Install CTL-4040-0-00WW-B01-354K-0-00WW-B01-update.zip with Nokia Extensions OTA Update module or adb sideload under recovery.
5. Reboot your phone.
That's it.
If minor fixes released, I will upload them as well, then use the same method to install it.
To root the phone, you may want to use Magisk 20 released October 12th, 2019 or newer.
Download link:
Full OTA link (CTL-408B-0-00WW-B03-update.zip): https://android.googleapis.com/pack.../29ad191f90eedc643ed008dc06c81ed3c5b5565a.zip
Following link now discontinued.
https://www.androidfilehost.com/?w=files&flid=299362
Dude I Did Not Find TA-1097 NOKIA 7.1?
[email protected]! said:
Dude I Did Not Find TA-1097 NOKIA 7.1?
Click to expand...
Click to collapse
Packages are identical, regardless of TA-1085, 1095, 1096, 1097, 1100.
Anybody try this? It's everything ok? No issues?
Sent from my TA-1021 using Tapatalk
Support for Project Mainline?
Will this update (or perhaps a future update) for the Nokia 7.1 to Android 10 support Project Mainline?
I ask because I’ve read in some places that only devices that ship with Android 10 can support Project Mainline, and in other places that devices upgraded to Android 10 can support Project Mainline.
Hello, There is an issue with going from 4080 to 408A. Noticed it's also uploaded twice, but not sure what the issue is. I get a sideload package zip error.
hikari_calyx said:
Packages are identical, regardless of TA-1085, 1095, 1096, 1097, 1100.
Click to expand...
Click to collapse
How to get its TWRP image?
UPDATE:
1. To users who have installed 4090: Please rollback the phone to 408B B01, and wait for the full OTA link to 408B B03.
2. To users who have installed 408B B01: Please rollback the phone to 408A then install 408A to 408B B03 package instead.
3. To users who have 354P currently, you can update to 408B B03 directly.
You can confirm the current build by dialing *#*#7837#*#*, expected output should look like this:
Version: 00WW_3_54P-B01
Click to expand...
Click to collapse
How to rollback?
1. Enter fastboot mode / download mode
2. Check your current slot by using "fastboot getvar current-slot"
3. If current slot is A, then execute:
Code:
fastboot --set-active=b oem HALT
4. If current slot is B, then execute:
Code:
fastboot --set-active=a oem HALT
5. Disconnect the phone and boot to recovery mode.
6. To users rollback from 408B B01, you can apply update package to 408B B03 here. To users rollback from 4090 B01, you may perform factory reset.
Zip package ota Android 10?! Anyone? [emoji1]
Sent from my Nokia 7.1 using Tapatalk
Full OTA link:
https://android.googleapis.com/pack.../29ad191f90eedc643ed008dc06c81ed3c5b5565a.zip
CTL-408B-0-00WW-B03-update.zip
Thx Calyx, work on every 7.1? ta-1095?!
Sent from my Nokia 7.1 using Tapatalk
dex87xda said:
Thx Calyx, work on every 7.1? ta-1095?!
Sent from my Nokia 7.1 using Tapatalk
Click to expand...
Click to collapse
It works on any version of Nokia 7.1, regardless of TA-1085, 1095, 1096, 1097, 1100.
is there diffence between this OTA and updated with CTL-408B-0-00WW-B03-354P-0-00WW-B01-update.zip????
There is different file size??
No difference
Sent from my TA-1021 using Tapatalk
hikari_calyx said:
It works on any version of Nokia 7.1, regardless of TA-1085, 1095, 1096, 1097, 1100.
Click to expand...
Click to collapse
Hi. Can the stable OTA be sideloaded over any Android Pie version or do we specifically need to be on 3.54P?
I would greatly appreciate any direction attempting to move from 4080 to 408A. When I try to sideload with adb in recovery I'm getting a package zip error and it will not update. I do have an unlocked bootloader and I've tried resetting the phone with twrp but not having any luck.
i have version ctl-256a-0-00ww-b07 . i need a file to update to android 9 then 10 using ADB sideload method .. thx HIKari