CM11S official & untouched image collection

CM11S official & untouched image collection - ONE General

2014.10.16.: Update!
MICa.fighter said:
Hy guys! As you might noticed, the links in the OP which are pointing to the official files on the CM server don't work any more thanks to CM. I was sure this will come, but i still wanted to use the official links as long as they are working. I would change the links to my mirrors in the OP, but @Spannaa already made mirrors in his thread: Mirrors for official CM11S roms & OTA updates. I don't see any reason to have 2 threads with mirrors of the same files, so i taught I would keep this thread as a discussion on how to use those official files. I will modify the OP in the coming days accordingly.
Click to expand...
Click to collapse
I will keep the OP as it is for now, and I will modify it a little in the coming days!
Hy guys, i have seen posts about different versions of CM11S, but I haven't seen a collection of them. I collect all the stock images i can, so i taught i would share it with you guys. As the thread title says, these are official and untouched images of the stock CM11S. I share the official links where it is available. I will share four kind of files:
1. Recovery flashable zips of the complete ROMz: these are the oldschool .zip images that you can flash through recovery.
2. Fastboot images of the complete ROMz: these are fastboot.zip files, that should be used through fastboot. You need to set up Android SDK for fastboot on your computer and you also need to unlock your phone's bootloader in order to use them. For setting up the Android SDK and unlocking your bootloader, please follow this guide: [GUIDE] OnePlus One - How to Unlock Bootloader, Install Custom Recovery and Root, until you complete the first step: 1. Unlocking Bootloader. After that you have to put the fastboot.zip file into your platform-tools folder (its explained in the previous link), and extract it there, but also keep the zip there because you need that too. After that, you may follow the instructions of the Open Post of this thread: CyanogenMod 11S.
Note: The conventional fastboot oem unlock which unlocks the bootloader will wipe your phone. You can make backup before that with Helium app or through adb. Neither of them requires root.
Note: The last command in the CyanogenMod 11S thread's open post is:
Code:
fastboot update -w cm-11.0-XNPH25R-bacon-signed-fastboot.zip
The command will wipe your phone because of the "-w" option.
Note: if you get the error message during flashing in fastboot:
Code:
FAILED (remote: data too large)
Then you are probably not on the latest Android SDK with the latest required tools: Android SDK Tools, Android SDK Platform-tools, Android Support Library, Google USB Driver.
Click to expand...
Click to collapse
3. Stock kernel images: these are .img files of the stock kernel images. You can flash these in fastboot like this:
Code:
fastboot flash boot boot.img
If the filename is for example g7389215.img then it looks like this:
Code:
fastboot flash boot g7389215.img
4. Latest OTA incremental update zip: I will also share the latest OTA zip file. The CM11S OTAs are incremental updates, that means you need to be on the latest version before applying an update. Incremental means it only updates the changed files since the last update.
So for example the latest OTA ATM is XNPH33R. Before that was the XNPH30O. If you want to use the XNPH33R OTA zip you need to be on XNPH30O, because that is the latest version before the XNPH33R OTA (check reference table below). If you apply the OTA on an earlier version (for example, XNHP25R), the installation will be aborted most probably. Or if you succeed with the installation, it will break stuff most probably.
You can also grab the latest OTA update zip after you recieved the OTA file and downloaded it. You can find it in the cache of your phone and you will need root access. If you want to make a copy you should do so before you install the OTA.
Wipe the cache then you can flash the OTA update zip through recovery.
Reference table
ROM version / release date / kernel version
XNPH22R / 2014.06.06. / dunno
XNPH25R / 2014.07.03. / geb9c0a5
XNPH30O / 2014.08.11. / g7389215
XNPH33R / 2014.08.21. / g0ad30e5
XNPH38R / 2014.10.07. / g33fa374
Links
1. Recovery flashable zips of the complete ROMz:
XNPH22R
XNPH25R
XNPH33R
2. Fastboot images of the complete ROMz:
XNPH22R
XNPH25R
XNPH30O
XNPH33R
XNPH38R
3. Stock kernel images:
XNPH22R
XNPH25R
XNPH30O
XNPH33R
XNPH38R / torrent magnet mirror
4. Latest OTA incremental update zip:
XNPH38R
Also here are the previous OTA incremental update zips:
same rule, check reference table, only use it if you are on the latest previous version! Its incremental.
XNPH33R
XNPH30O
Njoy!
You might also be interested in zephiK's modem collection of recovery flashable zips for the One: http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734

Thanks was waiting for something like this.

While I appreciate this, the 33R Kernel isn't working... I tried flashing with fastboot and no go.... I'm on 33R from OTA. I'm rooted and I currently have Franco Kernel installed... (And TWRP recovery)
To reiterate, it flashes fine but when I go to boot up it stays at the One+ logo screen

How did you try it exactly?

MICa.fighter said:
How did you try it exactly?
Click to expand...
Click to collapse
flashing with adb through fastboot

You can use rashr app https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools works like a charm

Nomelas said:
While I appreciate this, the 33R Kernel isn't working... I tried flashing with fastboot and no go.... I'm on 33R from OTA. I'm rooted and I currently have Franco Kernel installed... (And TWRP recovery)
To reiterate, it flashes fine but when I go to boot up it stays at the One+ logo screen
Click to expand...
Click to collapse
You are right, the file is broken, I'm sorry. I'm going to update the OP soon with working kernel image. I'm also going to share the latest OTA grabbed from cache.
Edit: updated OP with the new 33R links, and fixed the broken kernel image. I also explained how to use the kernel images.

Thank you so much

Great post op :good:
Waiting the recovery flashable zip of XNPH33R to download. ( I am currently on XNPH22R, unlocked bootloader, with TWRP)
I am going to flash the zip through recovery ( and then flash modem from zephiK's post).
I don't need to do anything with the kernel images ( I am guessing they are there for another reason), right?

mhxmhx said:
I don't need to do anything with the kernel images ( I am guessing they are there for another reason), right?
Click to expand...
Click to collapse
You don't need the kernel images.
All the rom zip files has a kernel (boot.img). The reason i posted the kernel images separately too because custom kernel users sometimes need them. If they want to go back to stock kernel or just want to keep a backup, they don't need to download ~460MB for just the kernel image, they can download only the kernel image which is 5-10 MB.

Thank you for your work!

Thanks a lot, after flashing few mods and custom kernel my phone feels laggy, I must go back to stock

After @zephiK modem list, this is one more most usefull thread Thanks !!

So could I just flash the 33r update from stock recovery if I'm on 25r? Or do I need to update to 30O then 33r

Added to OnePlus One Resources Compilation Roll-Up Thread
[INDEX]OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon

jherring002 said:
So could I just flash the 33r update from stock recovery if I'm on 25r? Or do I need to update to 30O then 33r
Click to expand...
Click to collapse
The OTA Update is incremental, which means it only updates the files that changed from the last update, in this case XNPH30O. So you sould NOT try to flash the OTA Update of 33R if you are not on 30O.
If you want to update to 33R from 25R, there are a couple of options, for example:
A) update to 30O through OTA, then you can just flash the 33R OTA update, OR
B) download the 33R full rom zip, reboot to recovery, wipe cache and flash away OR
C) make a backup of your apps and settings, through adb, or Titanium Backup, or with Helium (TB requires root), then download the 33R fastboot.zip and flash through fastboot as described in the first post. If you already have the bootloader unlocked you can skip that step. After you are done, boot up the phone, then restore your backup. The flashing method described in the open post of CyanogenMod 11S thread will wipe your phone.
The "safest" method is A, the "cleanest" method is C.
timmaaa said:
Added to OnePlus One Resources Compilation Roll-Up Thread
[INDEX]OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
Click to expand...
Click to collapse
I'm out of thanks so i thank you here timmaaa :good:

Is there a flashable 30O file via recovery?

jherring002 said:
Is there a flashable 30O file via recovery?
Click to expand...
Click to collapse
Unfortunately no, but I can upload the 30O original OTA zip for you i grabbed that from cache too. You can flash it on 25R after a cache wipe. Or use it with the 25R recovery flashable zip: flash 25R zip then 30O OTA zip.

MICa.fighter said:
Unfortunately no, but I can upload the 30O original OTA zip for you i grabbed that from cache too. You can flash it on 25R after a cache wipe.
Click to expand...
Click to collapse
That would be nice. I went from 33r to 25r to see the difference in battery.
It's not that different so I wanted to go back, but when I check for ota there is not one. Says in up to date.

jherring002 said:
That would be nice. I went from 33r to 25r to see the difference in battery.
It's not that different so I wanted to go back, but when I check for ota there is not one. Says in up to date.
Click to expand...
Click to collapse
Okay I'm gonna upload the 30O OTA zip too, it will be available in the first post in a few minitues. If you want to go back to 33R you could also use the 33R full rom zip, just wipe cache and you can flash it on 25R. Make a backup before it, but i don't think there would be any problem.
Edit: Done!

Related

[ROM][OTA] Mirrors for official Cyanogen roms and OTA updates

Now Cyanogen have shut down, links to official roms, updates & kernels are no longer available so 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 zips, signed zips, boot-debuggable images and OTA incremental update zips.
Signed fastboot 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. There's a great guide by @Heisenberg here.
Signed flashable zips: Normal, stock or TWRP recovery flashable zips that won't overwrite your data partition.
Boot-debuggable images: These are boot images (kernels) that enable adb root and the developer menu options.
To be flashed via fastboot. (e.g.fastboot flash boot cm-11.0-XNPH05Q-bacon-boot-debuggable.img)
OTA incremental update zips: These are stock 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. Note: there are two different versions of some OTA updates.
Fastboot images
cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot.zip
cm-13.1.1-ZNH2KAS2X1-bacon-signed-fastboot.zip
cm-13.1-ZNH2KAS254-bacon-signed-fastboot.zip
cm-13.1-ZNH2KAS1KN-bacon-signed-fastboot.zip
cm-13.0-ZNH0EAS2JK-bacon-signed-fastboot.zip
cm-12.1-YOG7DAS2K1-bacon-signed-fastboot.zip
cm-12.1-YOG4PAS3JL-bacon-signed-fastboot.zip
cm-12.1-YOG4PAS2QL-bacon-signed-fastboot.zip
cm-12.1-YOG4PAS1N0-bacon-signed-fastboot.zip
cm-12.0-YNG1TAS2XK-bacon-signed-fastboot.zip
cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip
cm-12.0-YNG1TAS17L-bacon-signed-fastboot.zip
cm-12.0-YNG1TAS0YL-bacon-signed-fastboot.zip
cm-11.0-XNPH05Q-bacon-signed-fastboot.zip
cm-11.0-XNPH44S-bacon-signed-fastboot.zip
cm-11.0-XNPH38R-bacon-signed-fastboot.zip
cm-11.0-XNPH33R-bacon-signed-fastboot.zip
cm-11.0-XNPH30O-bacon-signed-fastboot.zip
cm-11.0-XNPH25R-bacon-signed-fastboot.zip
cm-11.0-XNPH22R-bacon-signed-fastboot.zip
cm-11.0-XNPH22Q-bacon-signed-fastboot.zip
Signed flashable zips
cm-13.1.2-ZNH2KAS3P0-bacon-signed.zip
cm-13.1.1-ZNH2KAS2X1-bacon-signed.zip
cm-13.1-ZNH2KAS254-bacon-signed.zip
cm-13.1-ZNH2KAS1KN-bacon-signed.zip
cm-13.0-ZNH0EAS2JK-bacon-signed.zip
cm-12.1-YOG7DAS2K1-bacon-signed.zip
cm-12.1-YOG4PAS3JL-bacon-signed.zip
cm-12.1-YOG4PAS2QL-bacon-signed.zip
cm-12.1-YOG4PAS1N0-bacon-signed.zip
cm-12.0-YNG1TAS2XK-bacon-signed.zip
cm-12.0-YNG1TAS2I3-bacon-signed.zip
cm-12.0-YNG1TAS17L-bacon-signed.zip
cm-12.0-YNG1TAS0YL-bacon-signed.zip
Unofficial-cm-11.0-XNPH05Q-bacon-signed.zip
Unofficial-cm-11.0-XNPH44S-bacon-signed.zip
Unofficial-cm-11.0-XNPH38R-bacon-signed.zip
cm-11.0-XNPH33R-bacon-signed.zip
cm-11.0-XNPH25R-bacon-signed.zip
cm-11.0-XNPH22R-bacon-signed.zip
Boot-debuggable images
cm-13.1.2-ZNH2KAS3P0-bacon-boot-debuggable.img
cm-13.1.1-ZNH2KAS2X1-bacon-boot-debuggable.img
cm-13.1-ZNH2KAS254-bacon-boot-debuggable.img
cm-13.1-ZNH2KAS1KN-bacon-boot-debuggable.img
cm-13.0-ZNH0EAS2JK-bacon-boot-debuggable.img
cm-12.1-YOG7DAS2K1-bacon-boot-debuggable.img
cm-12.1-YOG4PAS3JL-bacon-boot-debuggable.img
cm-12.1-YOG4PAS2QL-bacon-boot-debuggable.img
cm-12.1-YOG4PAS1N0-bacon-boot-debuggable.img
cm-12.0-YNG1TAS2XK-bacon-boot-debuggable.img
cm-12.0-YNG1TAS2I3-bacon-boot-debuggable.img
cm-12.0-YNG1TAS17L-bacon-boot-debuggable.img
cm-12.0-YNG1TAS0YL-bacon-boot-debuggable.img
cm-11.0-XNPH05Q-bacon-boot-debuggable.img
cm-11.0-XNPH44S-bacon-boot-debuggable.img
cm-11.0-XNPH38R-bacon-boot-debuggable.img
cm-11.0-XNPH33R-bacon-boot-debuggable.img
cm-11.0-XNPH30O-bacon-boot-debuggable.img
cm-11.0-XNPH25R-bacon-boot-debuggable.img
cm-11.0-XNPH22R-bacon-boot-debuggable.img
OTA incremental update zips
ZNH2KAS2X1 -> ZNH2KAS3P0: cm-bacon-3c3f0aca9b-to-2b5f277d1c-signed.zip
ZNH2KAS254 -> ZNH2KAS2X1: cm-bacon-9f339bddf2-to-3c3f0aca9b-signed.zip
ZNH2KAS1KN -> ZNH2KAS254: cm-bacon-ced5430fc0-to-9f339bddf2-signed.zip
ZNH0EAS2JK -> ZNH2KAS1KN: cm-bacon-64003595ee-to-ced5430fc0-signed.zip
ZNH0EAS26M -> ZNH0EAS2JK: cm-bacon-e36dd78050-to-64003595ee-signed.zip
YOG7DAS2K1 -> ZNH0EAS2JK: cm-bacon-cee4e8702d-to-64003595ee-signed.zip
YOG7DAS2K1 -> ZNH0EAS26M: cm-bacon-cee4e8702d-to-e36dd78050-signed.zip
YOG4PAS3JL -> YOG7DAS2K1: cm-bacon-d91bf047f5-to-cee4e8702d-signed.zip
YOG4PAS2QL -> YOG4PAS3JL: cm-bacon-49d90510ef-to-d91bf047f5-signed.zip
YOG4PAS1N0 -> YOG4PAS2QL: cm-bacon-7be76f9310-to-49d90510ef-signed.zip
YOG4PAS1N0 -> YOG4PAS2QL: cm-bacon-7c535cd450-to-49d90510ef-signed.zip
YNG1TAS2XK -> YOG4PAS1N0: cm-bacon-62151320e9-to-7be76f9310-signed.zip
YNG1TAS2I3 -> YOG4PAS1N0: cm-bacon-30bd462d41-to-7be76f9310-signed.zip
YNG1TAS2I3 -> YOG4PAS1N0: cm-bacon-30bd462d41-to-7c535cd450-signed.zip
YNG1TAS17L -> YNG1TAS2I3: cm-bacon-e816218e8a-to-30bd462d41-signed.zip
XNPH05Q -> XNPH05Q: cm-bacon-5229c4ef56-to-7ecda8da86-signed.zip
XNPH44S -> XNPH05Q: cm-bacon-5fa8c79c0b-to-5229c4ef56-signed.zip
XNPH38R -> XNPH44S: cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
XNPH33R -> XNPH38R: cm-bacon-3628510d76-to-ac1ccf7921-signed.zip
XNPH30O -> XNPH33R: cm-bacon-4f280f505a-to-3628510d76-signed.zip
XNPH30O -> XNPH30O: cm-bacon-0428073396-to-4f280f505a-signed.zip
XNPH25R -> XNPH30O: cm-bacon-d22b777afa-to-4f280f505a-signed.zip
XNPH25R -> XNPH30O: cm-bacon-d22b777afa-to-0428073396-signed.zip
XNPH22R -> XNPH25R: cm-bacon-03d77315ea-to-d22b777afa-signed.zip
TWRP & SuperSU
Latest TWRP custom recovery
Latest Stable SuperSU

Really useful... Keep up!
TaP 1+1

Thank you for your work!

There's already a thread for this here:
http://forum.xda-developers.com/showthread.php?t=2857110
Transmitted via Bacon

timmaaa said:
There's already a thread for this here:
http://forum.xda-developers.com/showthread.php?t=2857110
Transmitted via Bacon
Click to expand...
Click to collapse
I know, but most of the older CM official links don't work anymore.
I've mirrored them and added a lot more if that's OK.
Sent from my OnePlus One...

Spannaa said:
I know.
Most of the official links don't work anymore - that's why I've mirrored them...
Sent from my OnePlus One...
Click to expand...
Click to collapse
Why not just work with the original OP instead of duplicating threads?
Transmitted via Bacon

timmaaa said:
Why not just work with the original OP instead of duplicating threads?
Click to expand...
Click to collapse
I did consider that but, since these links are all to mirrors of the originals rather than links to the original CM downloads themselves, I decided to keep it separate to avoid confusion.
If @MICa.fighter wants to use any of these links in his thread, he's more than welcome to.

Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon

What's the debugble version is so diferent?

jgcaap said:
What's the debugble version is so diferent?
Click to expand...
Click to collapse
They're not the full ROM - boot-debuggable images are just boot images (kernels) that enable adb root and the developer menu options.

Spannaa said:
I did consider that but, since these links are all to mirrors of the originals rather than links to the original CM downloads themselves, I decided to keep it separate to avoid confusion.
If @MICa.fighter wants to use any of these links in his thread, he's more than welcome to.
Click to expand...
Click to collapse
Thank you for the mirrors.
I wanted to use the links to the original CM downloads as long as they are available, so it is unquestionable they are the official files.
Since you already made mirrors, i don't think there is any reason for me to make mirrors in the other thread. Maybe i will find a different purpose for that thread, for example using the official files.

MICa.fighter said:
Thank you for the mirrors.
I wanted to use the links to the original CM downloads as long as they are available, so it is unquestionable they are the official files.
Since you already made mirrors, i don't think there is any reason for me to make mirrors in the other thread. Maybe i will find a different purpose for that thread, for example using the official files.
Click to expand...
Click to collapse
Hopefully the official links will return at some point - official downloads are always better and more trusted than mirrors.
At least the official 33R & 38R fastboot links still work.
Shame that the 33R signed flashable doesn't and there isn't a 38R signed flashable yet.

Since CM don't appear to have released an official recovery flashable zip for 38R, I've put together an unofficial version in the same format as the 33R one but using the extracted system.img from the 38R fastboot zip and other files from both this zip and the OTA zip.
Unofficial-cm-11.0-XNPH38R-bacon-signed.zip
I've tested it a few times but the usual disclaimer still applies

if i install the unofficial 38r, will i recieve upcoming ota like usual ?

kimikim0 said:
if i install the unofficial 38r, will i recieve upcoming ota like usual ?
Click to expand...
Click to collapse
Yes, as long as you're on CM11S you should have no issues receiving updates.
Transmitted via Bacon

Added XNPH38R -> XNPH44S OTA incremental update zip to post #1

Thanks for the work, updated like a charm.

In on 25r and no updates OTA?
Sent from my One using Tapatalk

friendlybiker said:
In on 25r and no updates OTA?
Click to expand...
Click to collapse
If you're on 25R, you can update to whatever version you want by flashing consecutive OTA incremental update zips.
Just make sure that you flash the right ones in the right order and I'd recommend re-booting between each flash.

I just messed with power and volume down and looks like it goes to TWRP, how do I do a backup on stock prior to flashing?
Sent from my One using Tapatalk

[OTA Update] Stagefright & Security Patch for GPE 5.1 Firmware (LMY47M.M001)

Hello guys!
This is the OTA file containing some security fixes for that Stagefright bullcrap and some stability fixes too.
You need to be on Android 5.1 GPE Firmware, compilation number LMY47M.M001.
Put the *.ZIP on the internal storage, then go to Settings > About Phone > System Updates and this will be applied. (This is NOT 5.1.1, it's just 5.1. No bigger System updates seem to be planned for Moto G GPE, since this device is 18 months old now). 
NOTE: This wont flash in any other ROM or Firmware. Also, this wont flash on TWRP, CWM or any other custom recovery. You need to have stock AOSP recovery from GPE firmware.
Click to expand...
Click to collapse
CHEERS!!!
LINK ¯\_(ツ)_/¯

I'd like to include this patch in my GPE ROMs. It would be helpful if someone could do a fresh install of the GPE Firmware, apply this OTA Update and then make a TWRP Backup or System Dump via ADB:
adb shell
su
busybox tar czvf /sdcard/systemdump.tgz /system
exit
exit
adb pull /sdcard/systemdump.tgz
Note: No personal data will be included.

lost101 said:
I'd like to include this patch in my GPE ROMs. It would be helpful if someone could do a fresh install of the GPE Firmware, apply this OTA Update and then make a TWRP Backup or System Dump via ADB:
adb shell
su
busybox tar czvf /sdcard/systemdump.tgz /system
exit
exit
adb pull /sdcard/systemdump.tgz
Note: No personal data will be included.
Click to expand...
Click to collapse
what partitions should i include in the twrp backup?

Chandresh204 said:
what partitions should i include in the twrp backup?
Click to expand...
Click to collapse
Boot, Modem and System.

Thanks ! I had a notification for this update but could not install it because of non-stock recovery.... I will try to flash it manually.
EDIT : Trying to flash it with TWRP and have this message : "Error executing updater binary in zip '/sdcard/update.zip'
EDIT 1 : Also this message : "Package expects build fingerprint of motorola/falcon_gpe/falcon_umts:5.1/LMY47M.M001/6:user/release-keys or motorola/falcon_gpe/falcon_umts:5.1/LMY47M.M003/8:user/release-keys;
this device has motorola/falcon_retuglb/falcon_umts:4.3/14.10.0Q3.X-84-16/6:user/release-keys" ...
This is weird because i'm on 5.1 GPE and have compilation number LMY47M.M001 in "About the phone"...
What can I do ?

Euphorion said:
Thanks ! I had a notification for this update but could not install it because of non-stock recovery.... I will try to flash it manually.
EDIT : Trying to flash it with TWRP and have this message : "Error executing updater binary in zip '/sdcard/update.zip'
EDIT 1 : Also this message : "Package expects build fingerprint of motorola/falcon_gpe/falcon_umts:5.1/LMY47M.M001/6:user/release-keys or motorola/falcon_gpe/falcon_umts:5.1/LMY47M.M003/8:user/release-keys;
this device has motorola/falcon_retuglb/falcon_umts:4.3/14.10.0Q3.X-84-16/6:user/release-keys" ...
This is weird because i'm on 5.1 GPE and have compilation number LMY47M.M001 in "About the phone"...
What can I do ?
Click to expand...
Click to collapse
You need to have:
1. Untouched System partition (that means NO ROOT, nor ROOTED AND THEN UNROOTED System partion)
2. Stock AOSP recovery fron GPE Firmware...
So I'd reccomend you to reflash the entire GPE firmware, then apply this patch! :fingers-crossed:

MarckozZ said:
You need to have:
1. Untouched System partition (that means NO ROOT, nor ROOTED AND THEN UNROOTED System partion)
2. Stock AOSP recovery fron GPE Firmware...
So I'd reccomend you to reflash the entire GPE firmware, then apply this patch! :fingers-crossed:
Click to expand...
Click to collapse
Ok, thanks for your reply. And what is the easiest way to reflash the gpe firmware ? I followed this tutorial ( http://forum.xda-developers.com/moto-g/general/guide-flash-android-5-1-lollipop-gpe-t3071960 ) six months ago to convert my non-GPE XT1032 with android 5.0.2 to the GPE variant with android 5.1. Sorry for my questions, I'm a total noob.

Euphorion said:
Ok, thanks for your reply. And what is the easiest way to reflash the gpe firmware ? I followed this tutorial ( http://forum.xda-developers.com/moto-g/general/guide-flash-android-5-1-lollipop-gpe-t3071960 ) six months ago to convert my non-GPE XT1032 with android 5.0.2 to the GPE variant with android 5.1. Sorry for my questions, I'm a total noob.
Click to expand...
Click to collapse
you should have the GPE firmware zip, then unzip the file, put the contents in the folder which contains fastboot files, then uncompress the zip file in the attachments below, put the bat file in the same folder as the firmware files,
Then Run the bat file, voila!! you'll be on clean GPE 5.1.
Then setup the moto G and apply the stage fright update when notified.
Then flash the stock motorola radio/modem files to get back signal
then flash twrp to get root.

@lost101 i made the twrp backup, it is 1.34 GB. Clean firmware with just the update installed and not flashed asian modem files.
uploading the zip file which is 725 MB in size.

Thanks for the OTA link
Modified OTA zip for Moto G converted to GPE : https://www.androidfilehost.com/?fid=24052804347815541 i won't check baseband version before install. Tested http://i.imgur.com/Gnt3Y97.jpg and working http://i.imgur.com/GiYOFEo.jpg

TCattd said:
Thanks for the OTA link
Modified OTA zip for Moto G converted to GPE : https://www.androidfilehost.com/?fid=24052804347815541 i won't check baseband version before install. Tested http://i.imgur.com/Gnt3Y97.jpg and working http://i.imgur.com/GiYOFEo.jpg
Click to expand...
Click to collapse
what has been modified on this? does this work with custom recovery ?
Edit 1: my bad, didn't check the screenshots first, it does work with twrp. Now my question is, will it install even if the phone is rooted?

Chandresh204 said:
what has been modified on this? does this work with custom recovery ?
Click to expand...
Click to collapse
Just the initial version/modem check on updater-script. You can compare both zips if you want (original OTA and modified OTA).
And of course it works with a custom recovery. Check the two proofs, please. Was installed and tested using TWRP... :/

TCattd said:
Just the initial version/modem check on updater-script. You can compare both zips if you want (original OTA and modified OTA).
And of course it works with a custom recovery. Check the two proofs, please. Was installed and tested using TWRP... :/
Click to expand...
Click to collapse
sorry, forgot to check the screenshots, it does work with twrp. My question is will it still update even when i am rooted?

Chandresh204 said:
sorry, forgot to check the screenshots, it does work with twrp. My question is will it still update even when i am rooted?
Click to expand...
Click to collapse
Don't know.
Was tested with a clean 5.1 installation (using GPE 5.1 ROM (Untouched) (484mb) from http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 ) so, no root.
You can always unroot from inside SuperSU settings, then update with the modified OTA and afterwards install SuperSU again before restart from TWRP.

TCattd said:
Thanks for the OTA link
Modified OTA zip for Moto G converted to GPE : https://www.androidfilehost.com/?fid=24052804347815541 i won't check baseband version before install. Tested http://i.imgur.com/Gnt3Y97.jpg and working http://i.imgur.com/GiYOFEo.jpg
Click to expand...
Click to collapse
Very thanks for this modified OTA.
Since I was using custom recovery and root I have to flash clean GPE 5.1 firmware and set it up from ground just to install this update.
You just saved few hours for me. :good:

TCattd said:
Thanks for the OTA link
Modified OTA zip for Moto G converted to GPE : https://www.androidfilehost.com/?fid=24052804347815541 i won't check baseband version before install. Tested http://i.imgur.com/Gnt3Y97.jpg and working http://i.imgur.com/GiYOFEo.jpg
Click to expand...
Click to collapse
I can add this to the OP if you want!

MarckozZ said:
I can add this to the OP if you want!
Click to expand...
Click to collapse
No problem

Chandresh204 said:
you should have the GPE firmware zip, then unzip the file, put the contents in the folder which contains fastboot files, then uncompress the zip file in the attachments below, put the bat file in the same folder as the firmware files,
Then Run the bat file, voila!! you'll be on clean GPE 5.1.
Then setup the moto G and apply the stage fright update when notified.
Then flash the stock motorola radio/modem files to get back signal
then flash twrp to get root.
Click to expand...
Click to collapse
I reflashed everything and it worked. Thanks for your help.

Mine does not work (I am using TRWP). It gives an error say that the calendar.apk has unexpected content...

Can I Ota update while rooted on stock firmware

I am currently on stock rom but rooted. An Ota update popped up can I update without bootloop

I would like to know the same thing

Naruto101 said:
I am currently on stock rom but rooted. An Ota update popped up can I update without bootloop
Click to expand...
Click to collapse
stkman32 said:
I would like to know the same thing
Click to expand...
Click to collapse
No you can't take an OTA if you have any modifications to /system (root). Have a look at my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

I got an 8MB update for the november patch. Being on TWRP and root i need to convert back to stock before i can have it leave me alone? Is there a way to flash the patch without doing that?

Thanks for answering my question

roughriduz said:
I got an 8MB update for the november patch. Being on TWRP and root i need to convert back to stock before i can have it leave me alone? Is there a way to flash the patch without doing that?
Click to expand...
Click to collapse
No way around it, any modifications will cause the update to fail.

Heisenberg said:
No way around it, any modifications will cause the update to fail.
Click to expand...
Click to collapse
@amoeller had me flash the modified boot.img for MDB08M then flash the MDB08M system.img and vendor.img from the factory image. I rebooted bootloader, the booted to TWRP and re-flashed supersu. I am now on the November patch without having to remove TWRP and all works well. My user data was also untouched.

roughriduz said:
@amoeller had me flash the modified boot.img for MDB08M then flash the MDB08M system.img and vendor.img from the factory image. I rebooted bootloader, the booted to TWRP and re-flashed supersu. I am now on the November patch without having to remove TWRP and all works well. My user data was also untouched.
Click to expand...
Click to collapse
User data should never be affected during an OTA anyway.

This is actually the first time I've unlocked a phones bootloader and stuck with the stock rom. I usually use some kind of popular rom with it's own built in OTA (CM/Viper One)
How often do you guys actually update your phones for OTA? It seems like a real hassle

GloriousGlory said:
This is actually the first time I've unlocked a phones bootloader and stuck with the stock rom. I usually use some kind of popular rom with it's own built in OTA (CM/Viper One)
How often do you guys actually update your phones for OTA? It seems like a real hassle
Click to expand...
Click to collapse
I am rooted now so I'll wait a while before updating an ota until there's a big deal of info. However, in the past if I was sticking with stock there's usually at least one developer who posts the updates with root and stuff built in so you can easily flash with twrp. So I'm kind of waiting for that. That or cataclysm or another awesome rom that's close to stock.

GloriousGlory said:
This is actually the first time I've unlocked a phones bootloader and stuck with the stock rom. I usually use some kind of popular rom with it's own built in OTA (CM/Viper One)
How often do you guys actually update your phones for OTA? It seems like a real hassle
Click to expand...
Click to collapse
I wait for factory image for that build and flash over the new images when they become available (provided that root can still be achieved). Some will do a clean wipe and start fresh with the new build and reload in their apps and user data, others will just dirty flash the updated system (and boot/bootloader or whatever else was changed too).
If you think about it, it really isn't all that different from taking an OTA, the difference is that we're applying the commands to flash instead of having it automated. It's not that big of a trade off in my book.

I have 2 questions...
What is the easiest way to make flashing updates a breeze if I have mods in /system partition? I have heard of "freezing" them. Or is the only option... to delete every mod and flash updates? If so, should I keep a note of every change I make to/system?
And last... Should I make a backup of any file i am replacing or overwriting in /system? And if so, do I have to put them back how they were before flashing an update?

Delete

If you're rooted then you need to download the full factory image, extract system and vendor and flash those. Reflash SuperSU.

roughriduz said:
@amoeller had me flash the modified boot.img for MDB08M then flash the MDB08M system.img and vendor.img from the factory image. I rebooted bootloader, the booted to TWRP and re-flashed supersu. I am now on the November patch without having to remove TWRP and all works well. My user data was also untouched.
Click to expand...
Click to collapse
It’s probably easier and quicker just to flash stock factory images separately instead of having to jump through hoops with OTAs. Like I told @roughriduz just flash the updated partition(s) that were updated like system.img, vendor.img, or whatever and just flash SuperSU in TWRP after.
The steps @roughriduz took was
1. Download and extract latest factory image.
2. Download matching modified boot.img for that build (For example MDB08M).
3. Flash system, vendor, and any other partitions (like radios, etc) with fastboot if they were updated in the OTA. Don’t bother to flash stock recovery because we’re not using an OTA. Flashing userdata.img is just like a factory reset.
4. Boot directly into TWRP and flash SuperSU.
5. Reboot and profit.
This method gives you the latest stock build rooted with TWRP while keeping your data because I hate having to redo my phone.

amoeller said:
It’s probably easier and quicker just to flash stock factory images separately instead of having to jump through hoops with OTAs. Like I told @roughriduz just flash the updated partition(s) that were updated like system.img, vendor.img, or whatever and just flash SuperSU in TWRP after.
The steps @roughriduz took was
1. Download and extract latest factory image.
2. Download matching modified boot.img for that build (For example MDB08M).
3. Flash system, vendor, and any other partitions (like radios, etc) with fastboot if they were updated in the OTA. Don’t bother to flash stock recovery because we’re not using an OTA. Flashing userdata.img is just like a factory reset.
4. Boot directly into TWRP and flash SuperSU.
5. Reboot and profit.
This method gives you the latest stock build rooted with TWRP while keeping your data because I hate having to redo my phone.
Click to expand...
Click to collapse
A couple questions:
1. Step 1 refers to the latest factory image that contains the update, correct?
2. Step two refers to the boot.img that contains root?
3. At what point in this process do you flash the modified boot.img, before or after applying the other images?
Thanks for your help!

JimmyJunk said:
A couple questions:
1. Step 1 refers to the latest factory image that contains the update, correct?
2. Step two refers to the boot.img that contains root?
3. At what point in this process do you flash the modified boot.img, before or after applying the other images?
Thanks for your help!
Click to expand...
Click to collapse
1. Latest factory image is the latest factory image from the nexus factory images page. It's not an update like ota, but rather the entire image they would return you to stock if all is flashed.
2. Flashing a modified boot does not give you root. You still have to flash SU, so saying the modified boot contains root isn't right.
3. I flash boot first unless there is an updated bootloader.

JimmyJunk said:
A couple questions:
1. Step 1 refers to the latest factory image that contains the update, correct?
2. Step two refers to the boot.img that contains root?
3. At what point in this process do you flash the modified boot.img, before or after applying the other images?
Thanks for your help!
Click to expand...
Click to collapse
1. This can be whatever the latest factory image is at the moment. It’s currently MDB08M. All the OTA does is update your phone to whatever build it was made for. Factory images already have previously released updates built into them. You can upgrade but avoid downgrading unless you want to factory reset your phone.
2. I’m referring to the boot.img without root by @mrRobinson found https://www.androidfilehost.com/?fid=24269982086992320 although this process can be used for systemless root also. For systemless root you wouldn’t flash SuperSU in TWRP but instead sideload the SuperSU APK as per Chainfire’s instructions and use the matching systemless root boot.img
3. I don’t think it matters but as long as you have the matching modified boot.img with the system.img installed before you restart, you should be fine.

amoeller said:
It’s probably easier and quicker just to flash stock factory images separately instead of having to jump through hoops with OTAs. Like I told @roughriduz just flash the updated partition(s) that were updated like system.img, vendor.img, or whatever and just flash SuperSU in TWRP after.
The steps @roughriduz took was
1. Download and extract latest factory image.
2. Download matching modified boot.img for that build (For example MDB08M).
3. Flash system, vendor, and any other partitions (like radios, etc) with fastboot if they were updated in the OTA. Don’t bother to flash stock recovery because we’re not using an OTA. Flashing userdata.img is just like a factory reset.
4. Boot directly into TWRP and flash SuperSU.
5. Reboot and profit..
Click to expand...
Click to collapse
What the heck did I do wrong here? I just tried to apply the November OTA update to my MBD08K build, it didn't work, and now I am in the process of doing a full reset and rebuild of my phone (flash-all of factory images from Google)
Here are the notes I made as I attempted to follow the procedure in this thread:
Code:
- Download latest build for MBD08K from https://developers.google.com/android/nexus/images?hl=en
- Extract boot.img, system.img, vendor.img to C:\adb (or wherever where adb and fastboot are
installed). You have to
- Right-click, open command window here
- Ensure USB debugging is enabled on phone (grant permissions on phone if you get the popup)
- In command prompt, "adb devices"
- Should see serial number and "device"
- type "adb reboot bootloader"
- Should get to bootloader screen with little android man lying down with hatch open
- type "fastboot devices" - should see your serial # again and "fastboot" beside it.
- type "fastboot flash boot boot.img"
- type "fastboot flash system system.img"
- type "fastboot flash vendor vendor.img"
- Use volume keys to boot into recovery (in my case TWRP)
- Swipe to allow modifications
- Install -> SuperSU.zip that you should have on your phone from last time.
- Reboot system
I saw a red "your phone is corrupt" scary message on startup... took a while to boot. Couldn't get past the dancing circles.
Interrupted boot, rebooted to fastboot, tried to flash old modified boot.img
Booted again, got encryption unsuccessful warning
Flashed most recent boot.img again, stuck booting forever
try again:
- flash system.img
- flash vendor.img
- flash boot.img (modified)
reboot to recovery - your device can't be checked for corruption (yellow warning instead of red)
- swipe to allow modifications
- reboot with TWRP, swipe to install SuperSU
- Encryption unsuccessful. Prompt to factory reset. Click OK. Boots through TWRP.
Give up, start flashing factory images.
EDIT: I might be the stupidest person alive. I think I should have been using the files for MDB08M. Arggghhhh. Someone please confirm I am an idiot.
Edit 2: Factory reset worked, I am at MDB08M. Now rooting again... grr. At least I backed up all my apps & settings to Google Drive with TB.
Edit 3: Rooted and restoring all apps with TB. If anyone has any insight into where I F'ed up I'd appreciate it.

Need help to create a TWRP update from OTA

I just receveid an OTA update, but the installation stuck because the system is rooted.
I found the update.zip file on my Handy, but it contains some directory (Meta-inf, patch and system) and a big file update.app that I believe contais all the update file.
Is it possible to extract the file from update.app and then create an update that can I launche from TWRP? And if so how could I do it?
Thanks

You can't.
flash back a stock recovery.

After ulocking bootloader and root the OTA didn't work with original recovery that's why I wanto to create an update that works with TWRP

did you try?

ItalianWolf said:
did you try?
Click to expand...
Click to collapse
Yes I reinstalled the original recovery that you can find in t he root package and I completely unroot the phone using the unroot command in SuperSu.
Then I launch the update but after reboot it stuck at 11%, so I create the dload folder in my handy memory and copied there the content of update.zip and then forced the update. In this case, after reboot, it load until 99% that it reboot, but the installed version is still the 170 and not the 188.

Here worked, from post #393 to # 397 and #400
Stock recovery in root zip maybe too old.
Edit:
Ops perhaps it work on full update packages.

ItalianWolf said:
Here worked, from post #393 to # 397 and #400
Stock recovery in root zip maybe too old.
Edit:
Ops perhaps it work on full update packages.
Click to expand...
Click to collapse
What does here mean?
Which thread?
Thanks

Harlock1978 said:
What does here mean?
Which thread?
Thanks
Click to expand...
Click to collapse
Sorry, forgot link: http://forum.xda-developers.com/p8l...-lite-android-6-0-marshmallow-t3305550/page40

You need the Huawei Update Extractor Tool, and do the following:
Load the UPDATE.APP file inside the HUET
Extract boot.img, system.img, and cust.img, from UPDATE.APP inside the HUET
Flash the respective files via Fastboot

so if I am on Marshmallow beta, should I flash the recovery that comes with the marshmallow or the recovery of the B052 rom ?

AmINoS007 said:
so if I am on Marshmallow beta, should I flash the recovery that comes with the marshmallow or the recovery of the B052 rom ?
Click to expand...
Click to collapse
If you have to, flash the B052 recovery... you can always flash the Marshmallow recovery if it doesn't let you update.
I only flashed boot.img, cust.img, and system.img, when I upgraded; didn't flash Marshmallow's recovery at all.
Don't think you can even get OTA updates on the Marshmallow beta anyway (even via a normal bootloader-locked device).

Sorry for my late answer but I was travelling only with a Mac and I couldn't use Huaweu Update extractor.
This are the file that you can find in UpdateApp 188:
00.SHA256rsa.img
01.crc.img
02.curver.img
03.verlist.img
04.efi.img
05.fastboot1.img
06.boot.img
07.recovery.img
08.recovery2.img
11.cache.img
13.dtimage.img
14.dsp.img
15.fastboot.img
16.hifi.img
17.mcuimage.img
18.modemimage.img
19.modemnvm1.img
20.teeos.img
21.trustfirmware.img
And also the following directory:
META-INF
patch
system
Which file should I install, I didn't find a system.img and there are two different recovery
Thanks

You should not install any OTA with TWRP...
Flash back the stock recovery, update, then flash the twrp again, it's way easier and more secure, than doing a flashable zip from an OTA update without knowing what to do with the file within.
The OTA updates usually doesn't contain the SYSTEM.IMG file you are looking for, it contains individual files and scripts to patch up the current system partition to work with the new update.
From the two recoveries you should use the RECOVERY.IMG (the one without the 2 in it).
But again, I do recommend to flash the original recovery(not the one in the update), do the update, and put twrp back.

Where can I find the original recovery from ALE-L21C432B170, so that I can flash the original recovery again?
TIA

I found the original recovery and flashed it then I did a complete unroot and tried again to do the OTA update but it stopped at 11%.
Is there a different way to update?

[guide]Upgrade to MM(with any custom Rom)

Because it's coming soon my Rom.I write this manual
The transition to Beta 6.0 full custom bikes(RR,CM, or in my case HegsagonOS and BlurOS)
1.Install all necessary driver
https://software.intel.com/ru-ru/android/articles/intel-usb-driver-for-android-devices?page=1
------------------------
https://drive.google.com/file/d/0B0MKgCbUM0itVVFWRC02Q0VBQnc/view
----------------
http://4pda.ru/forum/index.php?showtopic=657946&st=1020#entry41321160
---------------------
http://4pda.ru/forum/index.php?showtopic=657946&st=6510#entry51065375
----------
If you do not get to download it I will attach to this post
----------
Mirror:
https://yadi.sk/d/NQCiY--IsQjBr
--------
2.Download Asus Flash tool
https://yadi.sk/d/NQCiY--IsQjBr
3.Download Raw rom
For Z00A-https://yadi.sk/d/4cuw246vryaZA
For Z008-https://yadi.sk/d/Y51bbCIZsVaMf
-----------
4.Download the full Rom
Z00A-http://4pda.ru/pages/go/?u=http://d...ga=1.150456565.29281456.1461158714&e=39450652
Z008-http://4pda.ru/pages/go/?u=http://d...ga=1.213705175.29281456.1461158714&e=39450652
-----------
5.Download FOTA to update to 6.0
Z00A-https://mega.nz/#!KsAmkYwD!Aci3fETLz...kolc15kuM50hAo
Z008-https://yadi.sk/d/TMssexxtsVuqK
------------
All can now proceed to the installation
1.Go in Twrp do a full wipe(data,cache,dalvik,system)
2.After this go in bootloader and connect our device.
3.As soon as he settles in to Asus Flash Tool hold the path to the Raw Rom and flash
4.After flashing it will load you into the Rom
5.Go into stock recovery using the bootloader,if you see a dead robot, hold down the volume+ and the power button(about 5-10 seconds)
6.After that, our Full Rom, rename to update
7.In recovery click on adb update(or differently)
Code:
Write in Adb
Adb kill-server
Adb devices(if written sideload,then you are on the right track)
Adb sideload update.zip
The process is long,about 30 minutes
8.After you have written Xref 2.08(or another value)
9.Reboot to Rom and throw the Fota the root the device,restart and get the status bar on the triangle is and est our updates,agree with everything and updated(do not touch!!!)
10.After upgrading Happy):good:

Thank you, although this link fails to load for me >
5.Download FOTA to update to 6.0
Z00A- https://cloud.mail.EN/public/FpaM/UrDAUTcYn

timbernot said:
Thank you, although this link fails to load for me >
5.Download FOTA to update to 6.0
Z00A- https://cloud.mail.EN/public/FpaM/UrDAUTcYn
Click to expand...
Click to collapse
Fixed:fingers-crossed:

Thanks for the guide. But I am lost. Can you please be more specific for the part where flashing custom starts?
Because everybody wants to know how to flash custom roms on MM beta.

Russiamen said:
Fixed:fingers-crossed:
Click to expand...
Click to collapse
Hi, thanks for your work, but do not understand the step six and seven, I do not understand what to write in adb . I 'm sorry, I 'm a newbie .
Thanks for your help

Yousvel said:
Thanks for the guide. But I am lost. Can you please be more specific for the part where flashing custom starts?
Because everybody wants to know how to flash custom roms on MM beta.
Click to expand...
Click to collapse
Try use Dual boot patcher

Can i flash this rom via lollipop twrp?

[email protected] said:
Can i flash this rom via lollipop twrp?
Click to expand...
Click to collapse
yea)

Definitely I need to learn russian lol
Registering in 4pda without any russian comprehension is a hard task
EDIT: WTF? I cant pass by a russian captcha! looooooooooool

====================================================================
1.Go in Twrp do a full wipe(data,cache,dalvik,system)
2.After this go in bootloader and connect our device.
3.As soon as he settles in to Asus Flash Tool hold the path to the Raw Rom and flash
4.After flashing it will load you into the Rom
5.Go into stock recovery using the bootloader,if you see a dead robot, hold down the volume+ and the power button(about 5-10 seconds)
6.After that, our Full Rom, rename to update
7.In recovery click on adb update(or differently)
===================================================
A few questions to help me clear my confusion ?
4.After flashing it will load you into the Rom = .184 stock rom from raw .184 ?
6.After that, our Full Rom, rename to update and sideload = .184 stock rom
Any particular reason why we would need to sideload stock .184 rom -- when we are in .184 stock before putting FOTA 6.0 to internal ?
is it patched the 2nd .184 ?

@Russiamen did you make modifications in the 'full rom' zip file, or is it the same zip file that we can download from Asus site?
And I have the same doubts that @timbernot 's ones.
There is an newer MM build (V4.21.40.78_20160624_7972). Could I flash it instead the provided FOTA?

do you have a download link for 78?

after this steps the rom will rooted or have to root it?

Thank you for your guide
but raw rom link has not any file for z00a
i found this
https://mega.nz/#!KsAmkYwD!Aci3fETLz0NwdIOqcr1Bf6pAi_MPQkolc15kuM50hAo

Trying to flash raw image didnt worked. Error attached

For Z008-https://yadi.sk/d/Y51bbCIZsVaMf this link not working plz fix this link there showing "nothing found"

The Raw link for Z00A says "nothing found," and the FOTA for the Z00A says it needs a decryption key.

So this guide is to update your bootloader to the marshmallow firmware. So you can install Marshmallow based ROMS?
The reason I'm asking is because i've Unlocked my bootloader and installed the latest version of TWRP 3.02.0 Z00A and I was on android 5.0 on stock ZenUI. I'm getting Error 7 everytime I try to install a ROM. I'm certain i'm installing the correct ROM for the device. I've also wiped the device, cleared the cache, ect. And still nothing. Any suggestions? Thanks for the help.

hello，my zenfone ze551ml might be going to upgrade to mm 6.0， please tell me is it marshmallow stock rom camera better than 5.0？ is it 6.0 have setting sd card become internal storage？ is it 6.0 have mass big storage not just mtp when connected to pc ？
Sent from my S660 using XDA Premium 4 mobile app

Database Users

welcome