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
Related
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!
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...
I'll keep a list of firmware and modems here, with TWRP flashable zip files and images. If using stock everything or your recovery won't boot, you may flash the images with fastboot, and the complete rom is flashable with stock recovery!
Information
Complete ROM - Flash in stock or custom recovery to return to stock or update/downgrade.
Firmware Only - Flashes all the firmware without the rom. Useful when using a custom rom and want the latest firmware, without OxygenOS.
Modem Only - Flashes only the modem and nv. This is helpful for finding what modem has best coverage for you, without rom incompatibilities.
Stock Recovery Image - Recovery.img for the oxygenOS recovery, for going completely back to stock!
Stock Boot Image - Unmodifed boot.img from the update, useful to remove systemless mods, when you have no backup!
Downloads
Oxygen OS 4.0.1 Stable - Android 7.0 - Dec 1, 2016 Security Patch
Complete Rom
Oxygen OS 4.0 Stable - Android 7.0 - Dec 1, 2016 Security Patch
Complete Rom
Oxygen OS 4.0 Beta 1 - Android 7.0 - Dec 1, 2016 Security Patch
Complete Rom
Oxygen OS 4.0 Beta (Leak) - Android 7.0 - Dec 1, 2016 Security Patch
Complete Rom SHA1: fe19283bd5f430bbe2204fd06a2d78da41ea9144
Firmware Only SHA1: 588ed503145ec53a407aecc67d6d0ade1b2e7c03
Radio Only SHA1: a8bd8548de97c84dc989c9c4f8e506c1abe606f3
Stock Boot Image SHA1: ac2053594ae2885cfaa256ec9193b7e113c55a20
Oxygen OS 3.5.4 - Android 6.0.1 - Nov 1, 2016 Security Patch
Complete Rom SHA1: 1380614b2c731d85e0db22fe71f25f89cf250dc8
Firmware Only SHA1: 9ef51803a6be428033f058bf6fd7ab7f3541c3e4
Radio Only SHA1: 15d8e580f093894573daa7b5bce45dd133625bf7
Stock Recovery Image SHA1: 7b14e9b0c2045051a50e7bb61d940d3876b0957e
Stock Boot Image SHA1: 791cdb794c65364d64614f7ae2c95b63f27cf8eb
Oxygen OS 3.5.3 - Android 6.0.1 - Nov 1, 2016 Security Patch
Complete ROM SHA1: d4c91b79c8f7e1e822913772db5493957b47bd5e
Firmware only SHA1 : 120308b5d675f3b481442ad15d688227847a9046
Modem/Radio Only SHA1: 9f1c4142bf55b23140f3f42ff4a31da319d9884c
Stock Recovery Image SHA1: 7b14e9b0c2045051a50e7bb61d940d3876b0957e
Stock Boot Image SHA1: 34b523e20bd473f60150a473c8d510db5b031cc4
If you notice anything missing, feel free to notify me and i'll add it.
Might be a stupid question, but are any of those flashable in TWRP to update from 3.5.1 stock rom that has been rooted?
Edit : I did my homework and kept digging on the forum :
The Complete ROM can be "installed" in TWRP to update the current stock rom.
Thank you for this! I was excited and unlocked bootloader and rooted as soon as I had it out of the box, then the OTA didn't work. Was able to flash this and get to 3.5.3 .
andreq85 said:
Might be a stupid question, but are any of those flashable in TWRP to update from 3.5.1 stock rom that has been rooted?
Edit : I did my homework and kept digging on the forum :
The Complete ROM can be "installed" in TWRP to update the current stock rom.
Click to expand...
Click to collapse
Sorry for the confusion. I added descriptions in the OP for all 3 zips!
Thank you!
Would you be able to add md5 or sha1 sums for the files as well so that we can be sure no bits or bytes are lost during download?
Hi, my phone app won't work on my 3t so therefore I gave no calling capabilities. I have TWRP and I'm rooted. I also have Xposed installed. Would flashing any of the three files help recover my calling capability? And if so, which file should I flash? Also I'd prefer to keep all my phone data so would flashing any of these need a system wipe first?
fureshyu said:
Hi, my phone app won't work on my 3t so therefore I gave no calling capabilities. I have TWRP and I'm rooted. I also have Xposed installed. Would flashing any of the three files help recover my calling capability? And if so, which file should I flash? Also I'd prefer to keep all my phone data so would flashing any of these need a system wipe first?
Click to expand...
Click to collapse
Flash the xposed uninstaller or just turn off xposed to see if that fixes the issue.
954wrecker said:
Flash the xposed uninstaller or just turn off xposed to see if that fixes the issue.
Click to expand...
Click to collapse
I tried disabling Xposed and uninstalling it, both didn't work. Any other suggestions? At this point I'm willing to go back to stock everything but I'm not sure if that will fix the issue.
Does anyone have a mirror of the Complete ROM 3.5.3?
i've tried to download this multiple times, different devices, different internet sources. And it keeps failing halfway through.
After installling TWRP and following the directions to boot back into the OS i was succesful. but i wanted to start fresh so i ran a Factory wipe from TWRP and can no longer boot into the OS. I was hoping flashing the zip will correct my issue.
btn21 said:
Thank you!
Would you be able to add md5 or sha1 sums for the files as well so that we can be sure no bits or bytes are lost during download?
Click to expand...
Click to collapse
I added the SHA1 sums, thanks for the tip.
pyrochance said:
Does anyone have a mirror of the Complete ROM 3.5.3?
i've tried to download this multiple times, different devices, different internet sources. And it keeps failing halfway through.
After installling TWRP and following the directions to boot back into the OS i was succesful. but i wanted to start fresh so i ran a Factory wipe from TWRP and can no longer boot into the OS. I was hoping flashing the zip will correct my issue.
Click to expand...
Click to collapse
Enjoy https://mega.nz/#!mBEAyaYC!BuIzRqKb6YdCKtr1B5zb1XNeiYANxHAWvIm_wLGhYck
I might delete this in a few days though.
BTW while you're at it can you validate the SHA1 for me, I never did. If you know of a better place to upload mirrors for these roms lmk and I'll reupload it.
sengook said:
Enjoy https://mega.nz/#!mBEAyaYC!BuIzRqKb6YdCKtr1B5zb1XNeiYANxHAWvIm_wLGhYck
I might delete this in a few days though.
BTW while you're at it can you validate the SHA1 for me, I never did. If you know of a better place to upload mirrors for these roms lmk and I'll reupload it.
Click to expand...
Click to collapse
Thank you! you're awesome!
I am downloading it now. i'll let you know if the SHA1 matches.
sengook said:
Enjoy https://mega.nz/#!mBEAyaYC!BuIzRqKb6YdCKtr1B5zb1XNeiYANxHAWvIm_wLGhYck
I might delete this in a few days though.
BTW while you're at it can you validate the SHA1 for me, I never did. If you know of a better place to upload mirrors for these roms lmk and I'll reupload it.
Click to expand...
Click to collapse
pyrochance said:
Thank you! you're awesome!
I am downloading it now. i'll let you know if the SHA1 matches.
Click to expand...
Click to collapse
I can confirm that the SHA1 is correct. agani thank you for the mirror.
pyrochance said:
I can confirm that the SHA1 is correct. agani thank you for the mirror.
Click to expand...
Click to collapse
Is this a flashable zip for twrp?
turbo1781 said:
Is this a flashable zip for twrp?
Click to expand...
Click to collapse
Yep...you can read the description on the OP
Hey can I flash the stock ROM and keep root and everything as is? I just want to go back to stock. I forgot to make a backup.
killuminati206 said:
Hey can I flash the stock ROM and keep root and everything as is? I just want to go back to stock. I forgot to make a backup.
Click to expand...
Click to collapse
No, it writes over /system and /boot. You can flash the rom and then supersu to keep root though.
Have you any plan for a flashable stock kernel (3.5.3) with modules? Thanks.
I'm oxgenOS 3.5.3
Rooted
phone will not connect to Wi-Fi my phone doesn't have a Wi-Fi signal around the area or at.home can I download one of the modules. Wi-Fi turns on
pyrochance said:
Does anyone have a mirror of the Complete ROM 3.5.3?
Click to expand...
Click to collapse
Here you go:
https://www.androidfilehost.com/?fid=313042859668277044
I uploaded it myself, it's the full 3.5.3 from OnePlus servers.
sengook said:
Enjoy https://mega.nz/#!mBEAyaYC!BuIzRqKb6YdCKtr1B5zb1XNeiYANxHAWvIm_wLGhYck
I might delete this in a few days though.
BTW while you're at it can you validate the SHA1 for me, I never did. If you know of a better place to upload mirrors for these roms lmk and I'll reupload it.
Click to expand...
Click to collapse
There is no better place than the above.
Enjoy
Hello everyone!
We are pushing out the incremental roll-out of OxygenOS 5.0, our first official Android O OTA update for the OnePlus 3 and 3T. Here are some of the highlights of this build:
System
Update to Android O (8.0)
Added Parallel Apps
Added Picture in Picture
Added Auto-fill
Added Smart text selection
New Quick Settings design
Updated security patch to September
Launcher
Added notification dots
New app folder design
Now able to upload photos directly to Shot on OnePlus
For those who were on previous versions for OnePlus 3 and 3T, we appreciate your active feedback and attempts to reach out to us. With your help, we have been able to better optimize and improve several key areas. Thank you for your patience and as always, we look forward to hearing your continued feedback in the bug reporting forum here: https://forums.oneplus.net/feedback/.
As always, this OTA will be incremental. The OTA will reach a small percentage of users today, and we'll begin a broader rollout in a few days.
Your feedback is appreciated. We may not always be able to respond to every comment in the forums, but please be assured that we take your comments and feedback seriously. Hope you enjoy and let us know how you feel about the update in the comments below.
Never Settle :fingers-crossed:
>>>> Confused on How to take logs, look here
Downloads:
OOS 5.0 Full Zip: Official
Unified TWRP By @eng.stk
SuperSU | Magisk
Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing one of the above full OTA zips in recovery.
Installation Methods
Before we start:-
This method is only for the OnePlus 3T.
Follow the steps correctly otherwise you may brick your device. I am not responsible for any damage to your device, please ensure that your device is at least 60% charged to prevent the accidental shutdown in-between the update process.
Download the necessary files from the post above and follow as below
PS: Dirty flash is fine if you are running a previous OOS version or any rom based on OOS, else if you come from a custom rom Clean Flash is recommended.
********************* For Stock Non Rooted Users with Stock Recovery *****************
1. Download the appropriate OTA from above link and place it in the root folder.
2. Navigate to Settings > System Updates > Settings Icon > Local Upgrade & Select the OTA File
3. Once selected system would prompt upgrade now
4. Select upgrade now and system would reboot in stock recovery and flash the OTA
5. The installer would itself flash the OTA and reboot the device.
The Device will reboot and your OnePlus 3T is now running on the latest OxygenOS 5.0 firmware & OS based on 8.0 Oreo.
PS: The first boot may take some time so keep calm and wait for it to boot.
* After flash is successful go back to recovery and a wipe of cache is recommended.
* If in any case flash is unsuccessful the system would prompt you to download the full 1.4GB zip.
* Download that and follow the same process as above.
************************ For Rooted Users with TWRP Recovery ************************
Download the required files from Post 2
Once you have downloaded all the required files on you device, please follow as below :good:
1. Update TWRP to the ones provided above by flashing the downloaded image :good:
2. Reboot Recovery and Take a Nandroid of your existing ROM :good:
(Note: Nandroid from 3.0.4-1 cant be restored on older version or and visa-versa)
3. Wipe > Advance Wipe > Select Dalvik & Cache > Swipe to Wipe :good:
4. Install Menu > Select OOS 5.0 Full Rom Zip > Swipe to Flash :good:
5. Flash the provided SuperSU/Magisk to maintain root (Optional)
6. Wipe Dalvik & Cache
7. Reboot System and Enjoy OxygenOS 5.0 Firmware & Latest OOS based on 8.0 Oreo :fingers-crossed:
The first boot may take some time as the system would boot twice due to flash of supersu so keep calm :fingers-crossed:
PS: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing one of the above full OTA zips in recovery.
here we go! nice :good:
Yeah got the ota notification 20 mins ago
Is the alert slider now fixed?
Seansmit17 said:
Yeah got the ota notification 20 mins ago
Click to expand...
Click to collapse
None here yet, could u upload the OTA zip?
OOS 3.5.3 to 3.5.4 incremental OTA @Funk Wizard
OnePlus3TOxygen_28_OTA_027-029_patch_1612131737_17e7161d2b234949.zip
eng.stk said:
OOS 3.5.4 OTA @Funk Wizard
OnePlus3TOxygen_28_OTA_027-029_patch_1612131737_17e7161d2b234949.zip
Click to expand...
Click to collapse
Thanks buddy :good:
So did the T mobile issue is fixed now. Please let me know as I am on ATT and soon porting to T mobile
eng.stk said:
OOS 3.5.4 OTA @Funk Wizard
OnePlus3TOxygen_28_OTA_027-029_patch_1612131737_17e7161d2b234949.zip
Click to expand...
Click to collapse
OTA's wont install unless you have stock recovery, right?
Tried to install it through TWRP directly and the install ended with an ERROR: 7. Same thing happened while installing it from Settings -> System update -> Local upgrade, since it brings you to the same recovery/TWRP which ends up with ERROR 7 also
I guess in order to install this update and get back TWRP and ROOT, I have to:
1. flash stock recovery;
2. boot into system;
3. install this OTA update from Settings -> System update -> Local upgrade;
4. re-flash TWRP while in fastboot through ADB;
5. flash latest superSU in TWRP.
jemeljsh said:
OTA's wont install unless you have stock recovery, right?
Tried to install it through TWRP directly and the install ended with an ERROR: 7. Same thing happened while installing it from Settings -> System update -> Local upgrade, since it brings you to the same recovery/TWRP which ends up with ERROR 7 also
I guess in order to install this update and get back TWRP and ROOT, I have to:
1. flash stock recovery;
2. boot into system;
3. install this OTA update from Settings -> System update -> Local upgrade;
4. re-flash TWRP while in fastboot through ADB;
5. flash latest superSU in TWRP.
Click to expand...
Click to collapse
I have successfully installed the OTA from TWRP and updated the installation process on the OP
I don't see update yet. Is it normal?
Wysłane z mojego SM-T815 przy użyciu Tapatalka
Funk Wizard said:
I have successfully installed the OTA from TWRP and updated the installation process on the OP
Click to expand...
Click to collapse
Well, for some reason I get that Error 7. Even with stock recovery the install fails. I have no idea why..
Edit. Its (reason for Error 7) gotta be the root.
jemeljsh said:
Well, for some reason I get that Error 7. Even with stock recovery the install fails. I have no idea why..
Edit. Its (reason for Error 7) gotta be the root.
Click to expand...
Click to collapse
indeed the reason for error 7 is root.
You have to overwrite the system partition by flashing full 3.5.3 full rom followed by 3.5.4 OTA or just dirty flash 3.5.4 full zip.
Both Installation methods are mentioned on the OP with download links.
masi0 said:
I don't see update yet. Is it normal?
Wysłane z mojego SM-T815 przy użyciu Tapatalka
Click to expand...
Click to collapse
The roll-out is incremental, you can find the zips on the OP if you want to flash it manually along with the instructions already tested by me.
Is there a method of flashing this zip on stock unrooted rom?
Wysłane z mojego SM-T815 przy użyciu Tapatalka
Do you recommend? Better in something that 3.5.3?
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
Does Flashfire work with OnePlus 3T? Did anyone try it?
masi0 said:
Is there a method of flashing this zip on stock unrooted rom?
Wysłane z mojego SM-T815 przy użyciu Tapatalka
Click to expand...
Click to collapse
Yes, i have modified the update process for you, look here
liver20 said:
Do you recommend? Better in something that 3.5.3?
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
Click to expand...
Click to collapse
I always recommend to stay on the latest if official, you can check the changelog in the OP
Hi,
quick files that many of us waiting for
OnePlus 8T, 11.0.1.2 KB05BA KB2003
Newest (20.10.2020) OTA:
https://drive.google.com/file/d/1uKV_j8yIQLPeIRJkf1KIUlJcIaH8BppR/view?usp=sharing
boot.img (stock)
https://drive.google.com/file/d/12VopoB984YmJHUJuqMBA4jyID1Sp_sPQ/view?usp=sharing
boot.img (patched, checked, working)
https://drive.google.com/file/d/1V4esvmJCBkwskq2shfWcylPL53h4dd_2/view?usp=sharing
=======================================
You like it?
paypal.me/widmak
=======================================
Thanks!
Thanks. But where's the guide or howto, that the title says ?
I flashed your patched boot image, but no Magisk is detected in either stable or canary Magisk Manager. There might be an issue.
EDIT: Confirmed that the issue is on your end. Patched the image myself and flashed it, with Magisk being detected by Magisk Manager.
https://drive.google.com/file/d/1yw5Fwgy0_ArPD_itnZ66nmdWA2NapFPg/view
This boot image works.
Any idea to flash the EU rom from India?
felata said:
Any idea to flash the EU rom from India?
Click to expand...
Click to collapse
Download the full OTA zip, keep it in internal storage outside any folders.
Go to System -> System Updates
Click the gear icon, select local upgrade
Then, select the downloaded Full OTA zip.
Install and reboot.
Done.
theincognito said:
Download the full OTA zip, keep it in internal storage outside any folders.
Go to System -> System Updates
Click the gear icon, select local upgrade
Then, select the downloaded Full OTA zip.
Install and reboot.
Done.
Click to expand...
Click to collapse
The system says that it won't allow downgrade
Which magisk did you use please?
Alvincyq said:
The system says that it won't allow downgrade
Click to expand...
Click to collapse
If you updated to the Indian/Global 11.0.1.2 before doing this, you only have 2 options:
1. Wait for the next OOS update, but when the Indian/Global update comes, don't update.
Instead, wait for the full update zip of the EU to be available, and then follow the steps in the previous comment.
2. Unlock bootloader, flash the full OTA zip of any variant via fastboot, and relock the bootloader.
elliottweaver said:
I flashed your patched boot image, but no Magisk is detected in either stable or canary Magisk Manager. There might be an issue.
EDIT: Confirmed that the issue is on your end. Patched the image myself and flashed it, with Magisk being detected by Magisk Manager.
https://drive.google.com/file/d/1yw5Fwgy0_ArPD_itnZ66nmdWA2NapFPg/view
This boot image works.
Click to expand...
Click to collapse
Your file did not work for me but i modified the stock file from the first post myself and that worked. i guess there is something coded into the file by magisk that is depended on the phone.
theincognito said:
Download the full OTA zip, keep it in internal storage outside any folders.
Go to System -> System Updates
Click the gear icon, select local upgrade
Then, select the downloaded Full OTA zip.
Install and reboot.
Done.
Click to expand...
Click to collapse
I'm on Kb2005 and I'm only able to get an incremental update. Can I pull the bin file from that update
Was there an OTA specific to models outside of the U.S.? I see at least two variations are already getting an update but nothing is available yet for my US (KB2005) variant I got today.
MNoisy said:
Was there an OTA specific to models outside of the U.S.? I see at least two variations are already getting an update but nothing is available yet for my US (KB2005) variant I got today.
Click to expand...
Click to collapse
I have KB2005 as well. No updates for me. I tried to just boot the images posted in the other thread with no luck.
northmendo said:
I have KB2005 as well. No updates for me. I tried to just boot the images posted in the other thread with no luck.
Click to expand...
Click to collapse
Unless OnePlus is very different from the other major manufactures, you definitely do not want to use a patched boot image from a different model variation of software/firmware. At best it will cause major issues.. At worst, it will brick it.
If Oneplus is different, I would love some feedback on why and what they do from other users.
MNoisy said:
Unless OnePlus is very different from the other major manufactures, you definitely do not want to use a patched boot image from a different model variation of software/firmware. At best it will cause major issues.. At worst, it will brick it.
If Oneplus is different, I would love some feedback on why and what they do from other users.
Click to expand...
Click to collapse
Correctish, you don't want to flash it. You can just boot the image. If successful it'll just boot the phone. If unsuccessful it will hang and you can just force reboot. No damage can because because it's not writing the boot image to the phones storage. Kinda like booting from a flash drive. The code is
Code:
fastboot boot /path/boot.img
If you boot a patched boot image you will have access to a rooted phone until you reboot. I.E. just enough time to flash magisk on the installed boot image.
Hope that makes sense.
northmendo said:
Correctish, you don't want to flash it. You can just boot the image. If successful it'll just boot the phone. If unsuccessful it will hang and you can just force reboot. No damage can because because it's not writing the boot image to the phones storage. Kinda like booting from a flash drive. The code is
Code:
fastboot boot /path/boot.img
If you boot a patched boot image you will have access to a rooted phone until you reboot. I.E. just enough time to flash magisk on the installed boot image.
Hope that makes sense.
Click to expand...
Click to collapse
I am familiar with how it works but with brands like HTC and Samsung, if we use a boot.img from a different variation, it will not work or even brick it. Thanks for the heads up! It sounds like there is more room for error for testing with OnePlus and modifying the system.
Can someone please provide a link to the Magisk Manager that 's working with this bootimage?
Edit: Found it, got root but it doesn't pass SafetyNet...
epr said:
Can someone please provide a link to the Magisk Manager that 's working with this bootimage?
Edit: Found it, got root but it doesn't pass SafetyNet...
Click to expand...
Click to collapse
Which one was it? My Magisk is not working either. I assumed it was because the kb2005 was only an incremental update. I have the canary version from github. Is there another for oneplus?
MNoisy said:
Which one was it? My Magisk is not working either. I assumed it was because the kb2005 was only an incremental update. I have the canary version from github. Is there another for oneplus?
Click to expand...
Click to collapse
Downloaded it from github: https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
epr said:
Downloaded it from github: https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
Click to expand...
Click to collapse
Yeah, same one. And it worked on the incremental Ota for kb2005?
Do you mind posting the patched boot.img?
Thank you!
MNoisy said:
Yeah, same one. And it worked on the incremental Ota for kb2005?
Do you mind posting the patched boot.img?
Thank you!
Click to expand...
Click to collapse
Don't know for KB2005, mine is KB2003.
I used stock boot.img from OP and patched it myself, all already patched files didn't work.