Small update to build SU4TL-49. Not Marshmallow. Claims "security patches and improved network performance."
How to Update with an Unlocked Bootloader
The update will only work if you have a 100% unmodified stock rom and recovery menu. If you're on CF's rom and you want to update to the latest version of that, see his page for details on how to do that.
1. Backup all data. Just in case. Definitely do this if you're coming from CM13 or RR. I don't remember if the OTA wipes your data or not.
2. Download this SU4TL-44 100% stock flashable zip here: http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-44-100-stock-t3320815
3. Download the SU4TL-44 stock recovery menu here: https://mega.nz/#!L1AkQD4T!qoZIlLa-wuUBLMEi_gE574meiHd6Pehb34a-x3Gb-V8
4. Boot into TWRP.
5. Flash the file you downloaded in step 2 by selecting Install and browsing to the file.
6. In TWRP, select Install, followed by install image, and select the recovery image that you downloaded in step 3. Tell it to flash it to recovery, and flash it.
7. If you're coming from CM13 or RR, do a factory reset in TWRP. If you're coming from a modified stock rom, I still recommend this, but it's not mandatory.
8. Reboot to recovery to confirm that you see the stock recovery menu (a dead android with the words "no command").
9. Boot the phone normally.
10. The OTA update should appear. Take it and let it do its thing.
You now have a 100% stock, bootloader still unlocked, SU4TL-49 phone. If you want TWRP back so you can start flashing stuff again, keep reading.
11. Download and install Sunshine from here: http://theroot.ninja/
12. Download your preferred version of TWRP. The current stable version is here: https://dl.twrp.me/quark/. If you want baybutcher27's modded version that includes lots of handy additional features, you can get that here: http://forum.xda-developers.com/showpost.php?p=66877208&postcount=116
13. Download Flashify from the play store.
14. Open Sunshine and follow the instructions until it gains temp root. Disregard the message that says it isn't compatible with SU4TL-49.
15. Open Flashify, select Recovery Image, then browse to the version of TWRP that you downloaded in step 11. Flash it.
16. Reboot to recovery. You should see TWRP's lovely smiling face staring back at you.
How to Install the SU4TL-49 Modem Only
1. [HIGHLY RECOMMENDED] Flash the modded TWRP I mentioned earlier, select backup, backup only your modem.
2. Flash Computerfreek274's modem package that you can get here: https://www.androidfilehost.com/?fid=24545070682210570
3. If you have GPS or other modem-related issues, try flashing this to fix them: https://www.androidfilehost.com/?fid=24531035584725320
4. If you decide you don't like the new modem, restore the backup you made in step 1.
Troubleshooting
Issue: You followed all of the steps, but you still get an error when you try to take the OTA.
Solution: Backup your data and perform a factory reset using the stock recovery menu. You can do this by rebooting to recovery like you do when you want to boot TWRP, and when you see the "no command" screen, hold the power button and press volume up. Then select factory reset and do it.
silly question.
I am with bootloader unlocked and rooted, with stock rom.
My XT1254 show that an update is available .xxxx.49
May I update the smartphone, by itself (no TWRP, that I have installed )
Will it relock my bootloader?
lukappaseidue said:
silly question.
I am with bootloader unlocked and rooted, with stock rom.
My XT1254 show that an update is available .xxxx.49
May I update the smartphone, by itself (no TWRP, that I have installed )
Will it relock my bootloader?
Click to expand...
Click to collapse
He just said it won't lock your bootloader
lukappaseidue said:
silly question.
I am with bootloader unlocked and rooted, with stock rom.
My XT1254 show that an update is available .xxxx.49
May I update the smartphone, by itself (no TWRP, that I have installed )
Will it relock my bootloader?
Click to expand...
Click to collapse
Taking the update is perfectly safe as long as you are unlocked. However, if you are rooted, the update will fail. You must first flash a completely unmodified stock rom.
This will take you back to full stock: http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-44-100-stock-t3320815
Thank you. I think it is worth waiting for MM, or full updated rom
grazie
Original Motorola DROID Turbo receives a security update from Verizon
http://www.phonearena.com/news/Orig...ceives-a-security-update-from-Verizon_id81089
Original Motorola DROID Turbo receives a security update from Verizon
3 May 2016, 18:19, by Alan F.
We hate to take all of the fun out of your life, but if you happen to own the Motorola DROID Turbo and you receive the update from Verizon that is heading your way, the phone is not receiving Android 6.0. Better that we shoot down all hopes now before you start believing that the new files contain the latest Android build.
The update brings the latest Android security software to the DROID Turbo and it also adds improvements to call performance. Just because this is the OG Turbo doesn't make it totally irrelevant. Verizon still offers the device as a mid-range handset priced at $480.
Verizon suggests that after receiving the notification that your Turbo has received the update, you make sure that the phone is connected to a Wi-Fi network or a strong Verizon cellular signal before starting the updating process. Also, your battery should be fully charged before you start the update.
On Motorola's support page, it says that the Motorola DROID Turbo is still slated to receive Android 6.0 "pending partner support." Which means that if you still own this phone, you need to keep pushing Verizon to support an update to Android 6.0.
Click to expand...
Click to collapse
Whose done this and any difference?
Sent from my XT1254 using XDA-Developers mobile app
This update appeared to have disabled VoLTE.
molanjami said:
This update appeared to have disabled VoLTE.
Click to expand...
Click to collapse
VoLTE still working fine for me.
Sent from my XT1254 using XDA-Developers mobile app
Haha maybe they finally properly patched stagefright. Someone should check that.
My guess is security patch = patched exploit that sunshine uses, mayyyybe patched stagefright if Moto could be bothered to find a dev with absolutely nothing else to do.
Did a restore of the modem backup provided, rebooted phone and everything working as it should. sadly didnt improve my signal any, but thats what happens living in the boonies.
Flashed it on Resurrection Remix 5.6.8 05/08 build
It went fine for me but I backed up my SU44 Modem to be safe, and I wanna remind everyone to do the same, its always wise to be safe
TheSt33v said:
Haha maybe they finally properly patched stagefright. Someone should check that.
My guess is security patch = patched exploit that sunshine uses, mayyyybe patched stagefright if Moto could be bothered to find a dev with absolutely nothing else to do.
Click to expand...
Click to collapse
I ran Stagefright Detector after the update and it reported CVE-2015-6602 as a vulnerability.
Sent from my Droid Turbo using Tapatalk
helobubba88 said:
I ran Stagefright Detector after the update and it reported CVE-2015-6602 as a vulnerability.
Click to expand...
Click to collapse
Wow. Now that's lazy.
TheSt33v said:
Haha maybe they finally properly patched stagefright. Someone should check that.
My guess is security patch = patched exploit that sunshine uses, mayyyybe patched stagefright if Moto could be bothered to find a dev with absolutely nothing else to do.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my XT1254 using XDA-Developers mobile app
Nitefire77 said:
Did a restore of the modem backup provided, rebooted phone and everything working as it should. sadly didnt improve my signal any, but thats what happens living in the boonies.
Flashed it on Resurrection Remix 5.6.8 05/08 build
It went fine for me but I backed up my SU44 Modem to be safe, and I wanna remind everyone to do the same, its always wise to be safe
Click to expand...
Click to collapse
did you just flash the zip with the modded twrp or is there a special procedure. mine keeps failing
quantum tao said:
did you just flash the zip with the modded twrp or is there a special procedure. mine keeps failing
Click to expand...
Click to collapse
Extract the zip to /sdcard/TWRP/backups/[your phone's serial number]. Then boot twrp, select restore, and restore the backup.
quantum tao said:
did you just flash the zip with the modded twrp or is there a special procedure. mine keeps failing
Click to expand...
Click to collapse
^What St33vo said. Just restore modem from the extracted zip in your twrp folder. Keep it in the Sut49 folder once unzipped so you can select it under restore.
You don't need to wipe caches or anything. Just restore and reboot
TheSt33v said:
Extract the zip to /sdcard/TWRP/backups/[your phone's serial number]. Then boot twrp, select restore, and restore the backup.
Click to expand...
Click to collapse
Nitefire77 said:
^What St33vo said. Just restore modem from the extracted zip in your twrp folder. Keep it in the Sut49 folder once unzipped so you can select it under restore.
You don't need to wipe caches or anything. Just restore and reboot
Click to expand...
Click to collapse
thanks, that worked. i guess i'm too tired to do simple file operations. i thought it was an installable zip.
lukappaseidue said:
Thank you. I think it is worth waiting for MM, or full updated rom
grazie
Click to expand...
Click to collapse
Seen VZ update the razr hd to close a unlock and never released another update again. Still hoping this is not the case.
BBB
add two
Sent from my XT1254 using Tapatalk
realbbb said:
Seen VZ update the razr hd to close a unlock and never released another update again. Still hoping this is not the case.
BBB
add two
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Well very shortly before this update was released, people were talking about getting soak test invites. If the soak test was for this update, that's the shortest soak test in human history, and why would you need a soak test for such a tiny update? I'm still hopeful that we'll see a marshmallow soak leak relatively soon.
Related
Here's the new update that came out today - XNPH25R. This has the assert junk removed so you can flash it in TWRP.
NOTHING has been changed in this other than the ability to flash it in TWRP.
Reboot to recovery, flash .zip. Reboot to system. Nothing fancy required. *Flash SuperSU if you want root access.
https://www.4shared.com/download/4UoLVwKIce/cm-bacon-XNPH25R_fix.zip?lgfp=3000
I'm getting binary update script error by flashing with TWRP
I flashed the stock OTA in TWRP right from my phone. Go to Developer settings adn uncheck the update CM recovery setting and OTA will flash in TWRP. I kept root. I'm not sure if the 4.4 update will kill root, but I doubt it. Thanks for providing the zip!
With the option to update CM recovery via OTAs does that mean we can take OTAs with TWRP installed?
Hey Guys Can I flash this zip file through CWM ???? Please suggest...........
Update = flashed the official cm-11.0-XNPH22R-bacon-signed file & then received the OTA & it's installed successfully even with CWM install.
iamacronym said:
With the option to update CM recovery via OTAs does that mean we can take OTAs with TWRP installed?
Click to expand...
Click to collapse
I think you have to disable that option in developer settings menu, if you want to be able to flash the OTA with TWRP.
Works for me
Updated it using TWRP but once booted it tells me there's an udpate, over and over... update in TWRP seems to work (no fails, only message is "radio image updated")
I flashed the file and when I reboot i´m still on XNPH22R and it also does prompt for the update. I flashed it on twrp, everything seemed ok
Flashed the file with both TWRP and Philz, no error but the Rom version is still 22R !
Can someone post the stock recovery img please?
ToRvaLDs said:
Flashed the file with both TWRP and Philz, no error but the Rom version is still 22R !
Can someone post the stock recovery img please?
Click to expand...
Click to collapse
Yeah I get the same issue where it shows as the flashing being successful,but reboots back to 22R.
housry23 said:
I flashed the stock OTA in TWRP right from my phone. Go to Developer settings adn uncheck the update CM recovery setting and OTA will flash in TWRP. I kept root. I'm not sure if the 4.4 update will kill root, but I doubt it. Thanks for providing the zip!
Click to expand...
Click to collapse
Which folder was the OTA located in? Is it the cache one at root level?
Sent from N5 or OPO
truckroot said:
Which folder was the OTA located in? Is it the cache one?
Sent from N5 or OPO
Click to expand...
Click to collapse
I couldn't tell you. I got a notification that an update was available, tapped install and it booted into twrp and installed the update. I had to reinstall xposed but kept root and twrp.
Sent from my OnePlus One
housry23 said:
I couldn't tell you. I got a notification that an update was available, tapped install and it booted into twrp and installed the update. I had to reinstall xposed but kept root and twrp.
Sent from my OnePlus One
Click to expand...
Click to collapse
OK thx. Wasn't sure if u had to navigate to a certain folder when twrp booted up. Stock OTAs in a custom recovery is new territory for me.
Sent from N5 or OPO
truckroot said:
OK thx. Wasn't sure if u had to navigate to a certain folder when twrp booted up. Stock OTAs in a custom recovery is new territory for me.
Sent from N5 or OPO
Click to expand...
Click to collapse
I would say it's new territory for all of us. I do have the option to update cm recovery unchecked in developer settings.
Sent from my OnePlus One
housry23 said:
I would say it's new territory for all of us. I do have the option to update cm recovery unchecked in developer settings.
Sent from my OnePlus One
Click to expand...
Click to collapse
True. I have that unchecked and also had the system update apk frozen just out of habit.
Leave it to CM to allow OTAs to be installed thru twrp/cwm. Living this phone more and more each day.
Sent from N5 or OPO
Is it supposed to be about 23.55 mb only? Everytime i flash nothing changes...
Sent from my One using XDA Free mobile app
truckroot said:
Which folder was the OTA located in? Is it the cache one at root level?
Sent from N5 or OPO
Click to expand...
Click to collapse
The downloaded OTA is located in \cache and can be flashed trough TWPR. Unfortunately I get an error of missing apks in \system due to deleting some of them (CM File Manager, PrintSpooler, ...).
I'll try to throw them back to \system and retry flashing.
Nope nope nope, doesn't work. He says blabla build.prop because of changed DPI, but it gave me an error on executing the update binary anyway.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what happens when you try to flash the original OTA .zip in TWRP. When flashing the provided zip in OP I don't get an error but like everybody said it doesn't update to 25.
fiz:ik said:
Nope nope nope, doesn't work. He says blabla build.prop because of changed DPI, but it gave me an error on executing the update binary anyway.
Click to expand...
Click to collapse
Someone has the original build.prop? We can try to restore it and update.
ToRvaLDs said:
Someone has the original build.prop? We can try to restore it and update.
Click to expand...
Click to collapse
I've got it. Do you need? Texdroider DPI makes an backup of the original build.prop. I restored it and the issue is solved but nevertheless the update binary can't be executed.
Flashed CWM over TWRP: with CWM same problem. I restored original build.prop and it's still complaining about in the build prop.
Okay, seems that my backup of build.prop isn't the stock build.prop but an updated version with DPI of 380, damn. Can anyone upload the original one?
Can you upload the original build.prop please? Are you sure that the old file has the correct cm revision?
Inviato dal mio One utilizzando Tapatalk
I don't know if this is the appropriate place to post this, but I was looking all over for this OTA update and couldn't find it, finally was able to nab it off a friends XT1045 before he installed it, pulled it directly from the cache folder immediately after downloading the update. Hopefully this can help someone else...
File: Blur_Version.21.11.56.peregrine_retus.retus.en.US.zip
Download: https://goo.gl/VN3ObF
Size: 414.7 MB
MD5: 235297354b4f511ac2f4b469304f8b3f
SHA-1: d5ddf230cc98ab5935505f2b323e68e3a70b42d1
Guide coming shortly
Cheers
How is this installed?
Sent from my XT1045 using XDA Free mobile app
Travisholt92 said:
How is this installed?
Sent from my XT1045 using XDA Free mobile app
Click to expand...
Click to collapse
I'm not sure but i think that you need to go back to 4.4.4 Stock KK ROM from your device... Then flash the standard recovery (No TWRP or CWM) and on normal recovery you flash the zip
Go back to stock 4.4.4 and download this file. Reboot into recovery, select "install update.zip" choose the file, and install.
Checked today and my XT1045 had the 5.1 update available. The phone was recently flashed back to stock 4.4.4. Forgot I installed TWRP recovery and changed the boot logo. I started the update which then restarted the phone. TWRP started loading which got me a little worried but then saw it used an AOSP recovery script and TWRP handled it just fine. Once the phone finished loading I could see it was running Lollipop. However, I did get a Motorola message saying the update couldn't be applied or something and that no changes were made. It clearly did apply as checking the version info confirms it. The update did wipe the recovery and the boot logo I flashed. So got the bootloader unlock warning screen again. Though I only saw that after I tried going into recovery. The first few reboots didn't show it.
TadMSTR said:
Checked today and my XT1045 had the 5.1 update available. The phone was recently flashed back to stock 4.4.4. Forgot I installed TWRP recovery and changed the boot logo. I started the update which then restarted the phone. TWRP started loading which got me a little worried but then saw it used an AOSP recovery script and TWRP handled it just fine. Once the phone finished loading I could see it was running Lollipop. However, I did get a Motorola message saying the update couldn't be applied or something and that no changes were made. It clearly did apply as checking the version info confirms it. The update did wipe the recovery and the boot logo I flashed. So got the bootloader unlock warning screen again. Though I only saw that after I tried going into recovery. The first few reboots didn't show it.
Click to expand...
Click to collapse
Nice, i think still the safest mode is with stock recovery.
But TWRP FTW so i'm glad you found a way to install it without flash the stock recovery
I was running stock 4.4.4 firmware, but was unlocked, had twrp installed, and was rooted. It let me download the update fine, but upon clicking install, after the phone rebooted it would just get stuck in twrp. if i rebooted from there it would just say update failed. so then i went back and flashed stock recovery and tried again. now it would reboot into stock recovery, the install would get about half way then it would fail and boot back into the rom. the weird part is the phone would not stay powered on for more than 30 seconds before automatically powering itself down and trying to install the update again, so it was kind of stuck in a very long continuous boot loop if you will. i don't quite recall how i got it out of this continuous loop but eventually i did and booted up the stock recovery and attempted to flash the zip. failed again. got an error about install-recovery.sh having unexpected contents. so i went back and downloaded the full stock 4.4.4 rom, flashed recovery, boot, motoboot, logo, and the 3 system files via mfastboot (i did not have to erase userdata) and then booted into stock recovery and tried flashing the update again and it finally succeeded. i did not have to re-lock the phone at any point.
i will try to throw together a quick guide in a few outlining the above process for anyone who's trying to apply this update and having similar issues. here's what a successful update through stock recovery should look like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Pupet_Master said:
Nice, i think still the safest mode is with stock recovery.
But TWRP FTW so i'm glad you found a way to install it without flash the stock recovery
Click to expand...
Click to collapse
If I was thinking I would have went back to stock recovery first by doing a full restore to 4.4.4. I did have to update TWRP to 2.8.7.0 as 2.8.3.0 is based on 4.4.4 and gave me the weird screen flicker now that the bootloader is on 5.1. Going to TWRP 2.8.7.0 fixed it.
Is there anywhere to download 4.4.4 firmware (ret.us) faster than 50 kbps?
Sent from my XT1045 using XDA Free mobile app
Travisholt92 said:
Is there anywhere to download 4.4.4 firmware (ret.us) faster than 50 kbps?
Sent from my XT1045 using XDA Free mobile app
Click to expand...
Click to collapse
I think some of them are uploaded to Mega, you would have to look for the links and check if it matchs your version. I don't remember who posted the mirrors..
Travisholt92 said:
Is there anywhere to download 4.4.4 firmware (ret.us) faster than 50 kbps?
Sent from my XT1045 using XDA Free mobile app
Click to expand...
Click to collapse
Would have done this sooner but misunderstood what you needed. Here it is on my Mega account.
RETUS_XT1045_4.4.4_KXB21.14-L1.56_cid9_CFC.xml
https://mega.nz/#!sVAVXZ5Q!tsWQDyW7GXsbFhqqQVWFz1BISNJMblOv_6cxElAPxP0
My moto g xt1045 is running on KK4.4.4 Stock ROM.
I get the notification for lolipop 5.1 updates (23.21.37.en.US) but the file downloaded to /cache directory is Blur_Version.21.11.56.peregrine_retus.retus.en.US.zip
But my current system version is 21.11.56.peregrine_retus.retus.en.US retus, running stock recovery but still gets error and no update done.
Any clue what can be the issue? Is it the wrong file downloaded for lolipop 5.1 updates (23.21.37.en.US)?
TadMSTR said:
Would have done this sooner but misunderstood what you needed. Here it is on my Mega account.
RETUS_XT1045_4.4.4_KXB21.14-L1.56_cid9_CFC.xml
https://mega.nz/#!sVAVXZ5Q!tsWQDyW7GXsbFhqqQVWFz1BISNJMblOv_6cxElAPxP0
Click to expand...
Click to collapse
Wow, Thank you!! I was able to run the OTA update after installing this as per the instructions in this thread:
http://forum.xda-developers.com/moto-g/general/guide-moto-g-4g-lte-xt1045-restore-to-t2826112
Hmmmm...Stock xt1045 4.4.4 > 5.1 install aborted?
Hi all - Have a totally stock xt1045 running 4.4.4 (21.12.63.peregrine_att.att.en.US att) and trying to install this 5.1 update via stock recovery ends in an install aborted multiple times. Have downloaded and bit checked the upgrade file multiple times. Am I missing something really dumb perhaps?
Any ideas appreciated.
Littlalex
can anyone please share the install-recovery.sh from unrooted XT1045 of KK4.4.4
Anyone have a custom recovery for XT1045 5.1?
Thank you!
---------- Post added at 06:41 PM ---------- Previous post was at 06:38 PM ----------
TadMSTR said:
Would have done this sooner but misunderstood what you needed. Here it is on my Mega account.
RETUS_XT1045_4.4.4_KXB21.14-L1.56_cid9_CFC.xml
https://mega.nz/#!sVAVXZ5Q!tsWQDyW7GXsbFhqqQVWFz1BISNJMblOv_6cxElAPxP0
Click to expand...
Click to collapse
littlalex said:
Hi all - Have a totally stock xt1045 running 4.4.4 (21.12.63.peregrine_att.att.en.US att) and trying to install this 5.1 update via stock recovery ends in an install aborted multiple times. Have downloaded and bit checked the upgrade file multiple times. Am I missing something really dumb perhaps?
Any ideas appreciated.
Littlalex
Click to expand...
Click to collapse
Try reinstalling 4.4.4 using the firmware and instructions in the posts above yours.
Thanks!
Thanks Tesla74...I plead old age senility!!
Littlalex
littlalex said:
Thanks Tesla74...I plead old age senility!!
Littlalex
Click to expand...
Click to collapse
Note that after you reinstall 4.4.4 that you'll have to update Motorola Update Services via Google Play before you'll be able to download the new update.
Failure with 4.4.4 stuff
Tesla74 - Followed the instructions but using the 4.4.4 file and from the first mfastboot command I got an error "(bootloader) Preflash validation failed/
FAILED (remote failure)." Got two more similar errors as I went on (huh - what a dope!) But phone is still booting normally w/4.4.4
Think I'll wait for the official OTA...I'm no stranger to this but am still a virgin with this phone
Thanks again
Littlalex
littlalex said:
Tesla74 - Followed the instructions but using the 4.4.4 file and from the first mfastboot command I got an error "(bootloader) Preflash validation failed/
FAILED (remote failure)." Got two more similar errors as I went on (huh - what a dope!) But phone is still booting normally w/4.4.4
Think I'll wait for the official OTA...I'm no stranger to this but am still a virgin with this phone
Thanks again
Littlalex
Click to expand...
Click to collapse
Sorry it didn't work for you. Make sure that Motorola Update Services from Google Play is up to date, otherwise you won't get the OTA update.
Alright.
I had this problem for a while and I figured out how to flash the update without the need to factory reset or change the update script of the update file.
Even if you get the user/release-keys error message. EXAMPLE:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You have to be using the latest lollipop release before updating. That means you have to be on YOG7DAS2K1 before attempting.
This worked out for me. But it might not work for you. I do not believe it can destroy your phone and switch some satellites off, but still, not responsible if it did so.
Requirments:
You have to have TWRP now or you at least have ROOT and any flashing app like flashify.
Download COS 13 update file. here https://www.androidfilehost.com/?fid=24459283995316311
Download the latest CyanogenMod Recovery https://download.cyanogenmod.org/?device=bacon
Download the cm-12.1-YOG7DAS2K1 full ROM [url]https://www.androidfilehost.com/?fid=24369303960686198[/URL]
Guide:
Make sure the update cyanogen recovery option is checked in developer options.
Flash CyanogenMod Recovery downloaded before.
Reboot into it.
Use the update function in CyanogenMod Recovery and choose cm-12.1-YOG7DAS2K1 as the update file. It might take a while.
Now reboot to your phone. When booted and running, reboot to recovery.
Now you are running COS recovery. Update with the incremental.
That is it.
I hope this works out for you.
EXTRA: How to ROOT and have TWRP as a recovery:
Requirements:
A laptop.
Download TWRP and adb drivers on the laptop and the SuperSU and TWRP on your phone
Download Oneplus One TWRP Recovery [url]https://dl.twrp.me/bacon/twrp-3.0.2-0-bacon.img.html[/URL]
Get any adb divers. This one suffice [url]http://forum.xda-developers.com/google-nexus-5/development/adb-fb-apx-driver-universal-naked-t2513339[/URL]
Download the latest SuperSu [url]https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip[/URL]
Guide:
Reboot into bootloader: you can do this in many ways. A simple google search will show you how. Easiest way is to turn the phone off and hold the volume up and power long enough for the phone to boot into bootloader.
Connect your phone to your laptop
Run the adb: I assume you are using windows of course. First put the TWRP .img file in this folder. Hold shift and right click in the folder downloaded above. A 'Open command window here' option will be there. Click it and write in the window
Code:
fastboot boot twrp-3.0.2-0-bacon.img
. A hint: you can just write twrp and hit TAB, it will complete the filename. Or you can rename the downloaded file to just twrp.img
Check your phone, you will be running TWRP temporarily. You now have the option to ROOT only by flashing the SuperSU file downloaded on your phone. If you reboot now you will lose TWRP and get back to the official COS Recovery. If you want TWRP for good flash the TWRP file downloaded on your phone before.
I hope this is easy. It actually is. just follow it step by step.
If you could provide us the guide to root and come back to twrp I would be extremely happy
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
fastboot flash latest twrp and flash SuperSU BETA
THANK the post if I deserve
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
if you need a guide to root, this means you are not rooted, and if you are not rooted most probably you already have stock recovery, which means you can just install the OTA update without any issues.
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
Added as requested. I hope you find it easy.
y2kkingboy said:
Added as requested. I hope you find it easy.
Click to expand...
Click to collapse
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).
bisio971 said:
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).
Click to expand...
Click to collapse
Yeah. I mad a mistake there. Thank you and glad it helped.
If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?
thinleytsering9 said:
If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?
Click to expand...
Click to collapse
As I stated before you have to be on COS 12.1 YOG7DAS2K1. This method should not format your phone or remove any data as there is no factory reset step.
As for the link they are all over the place now. I used the official one. I'll link it for your convenience.
can anyone please pull the stock recovery from COS 13, not 12. I kinda screwed up while updating and now stuck in bootloop.
Update: The issue is resolved. The issue was because of SuperSu 2.46. Installing the latest TWRP and SuperSu 2.66 fixed it. Marshmallow is now rooted!
Thank you very much! After going back to stock and still not receiving the update for more than a week (well at least it felt like a week, Lol) I decided to flash a full COS 13 zip floating around. Instantly liked the new ROM but it had root/symlink issues only to be resolved when flashing a custom kernel it seems. Not what I really wanted so then I stumbled onto your thread and this technique worked 100%! I was on DAS2K1 (flashed thru a custom recovery) already and had several failed attempts flashing just the incremental outright (thru stock recovery)., but by flashing DAS2K1 thru stock recovery first as you suggest then the incremental seems to do the trick.
I did it all the steps, but my phone doesn't not start. After optimizing aplications I have bootloop at "cyanogen modready".
L.E. I think the problem was one of old aplications. After a clean install everything works.
This is the best thing Oneplus one i ever experience.COS13 give my Oneplus one a new breathe of life .This update better than crap lolipop.No Bug for me until now,only google play service need to update twice in play store,its auto reboot itself twice and wholla,super speed UX.The best thing i ever have.I apply update from CM-12-0-YNG1TAS17L Build LRX22G using this method and it works flawlessly
I don't need to factory reset or wipe cache .
I flash full stock ROM cm-12.1-YOG7DAS2K1 and apply update through CyanogenMod Recovery only and nothing else.
Now my oneplus one is rooted and TWRP install using ADB and its fly.All rooted apps is working together with Adaway.
Thanks Cyanogen team for make this 2 years old flagship killer a beast .
Only thing not satisfied is gone signal and wifi status (connectivity indicator ).I need to swipe down to see my transfer data working (what a bummer ).
Thanks so much for this magical guide (y2kkingboy) Yours truly Oneplus one diehard fan.
I was already on cm-12.1-YOG7DAS2K1, however rooted. So even if I had been offered the OTA it would have failed.
Your guide got me updated, first time with no problems.
6.0.1 is such an improvement on 5.1.1, I tried a couple of other 6.0 roms, however this has by far been the most stable and bug free.
Cheers for the tutorial!
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
#sychrome# said:
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.
InsaneNutter said:
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2522762
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
I had tried this before and it did not work for me. Kept getting an error saying "the signature file was not a complete file" and therefore it didn't flash. But it may have been editing error on my part. This method works just fine and no need to give up your data either.
Having tried many other ways, I got it done with this instruction.
Thank you!
marxu said:
Having tried many other ways, I got it done with this instruction.
Thank you!
Click to expand...
Click to collapse
Glad I helped.
Let me start out by saying I have spent hours searching and reading about this subject, and can't find straight answers to what I'm asking here.
So search wasn't my friend on these questions.
1)I am not clear on whether or not to install su.zip (arm) after unlocking bootloader and installing latest lineage version. In rahulsnair's post, he has a link for su.zip (arm) download, but then he says a few lines down: don't install any superuser packages.
2)I can't find a clear recent link on what package to install to get the stock N image and modem, the only one I found was dated October 2016 by sam sundar (Blur_Version.24.31.64.athene.retail.en.US.zip), is this the right one?
3)Do I even need to install that, or will the phone auto update to Nougat (moto xt1644)?
4) Will I be able to tether with this rom? (I am still on a legacy Verizon unlimited plan) rahulsnair also said in his post "Go to Settings>Developement Settings>Root access and select "Apps Only"", will this allow tether too?
Thanks in advance.
bovineyard said:
Let me start out by saying I have spent hours searching and reading about this subject, and can't find straight answers to what I'm asking here.
So search wasn't my friend on these questions.
1)I am not clear on whether or not to install su.zip (arm) after unlocking bootloader and installing latest lineage version. In rahulsnair's post, he has a link for su.zip (arm) download, but then he says a few lines down: don't install any superuser packages.
2)I can't find a clear recent link on what package to install to get the stock N image and modem, the only one I found was dated October 2016 by sam sundar (Blur_Version.24.31.64.athene.retail.en.US.zip), is this the right one?
3)Do I even need to install that, or will the phone auto update to Nougat (moto xt1644)?
4) Will I be able to tether with this rom? (I am still on a legacy Verizon unlimited plan) rahulsnair also said in his post "Go to Settings>Developement Settings>Root access and select "Apps Only"", will this allow tether too?
Thanks in advance.
Click to expand...
Click to collapse
Someone feel free to correct me on any of these
1) Flash SU.zip or SuperSU (or your root manager of choice) if you desire root. The history seems to be that CM14.1/early days of Lineage OS had root built-in (hence the warning towards the end of the post), but sometime in January the official Lineage team removed built in root access and moved it to a flashable separate zip, meaning you have to install it as an addon.
2)Looks like that file was the soak test from October, I wouldn't recommend installing it as although you get Nougat, it's a dead end upgrade path. You've got a couple of options:
a)Flash the fastboot NPJ25.93-14 Nougat stock update (v7.0, Dec 2016 security update) from https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369. This is as far as I can tell a complete ROM that appears to be signed by Motorola.
b)You could look at flashing the TWRP radio and Nougat files from here https://forum.xda-developers.com/moto-g4/development/fxz-athene-twrp-flashable-fastboots-t3562147, seems they work.
3) Depends on how long you're willing to wait for Nougat to arrive in the US, there are a few reports of a soak test in the US occurring! https://forum.xda-developers.com/moto-g4-plus/how-to/nougat-update-apparently-rolling-t3566271
4)No idea about tethering, seems from the official thread it worked for XT1642 (EU/UK Plus) but wasn't on XT1644 devices. You could try though with the newest build. Also, check robot_head's thread on suggestions on how to get Wi-Fi tethering working. https://forum.xda-developers.com/moto-g4-plus/help/wifi-tether-xt1625-t3543061 I think you have to uninstall SuperSU or other root managers if you wish to use Magisk for this, as Magisk takes over root management (as I recall!).
As always, good luck
I'm assuming bootloader needs to be unlocked to use this method? If so, is there a way to apply the latest xt1644 nougat update before unlocking bootloader? Thanks
bovineyard said:
I'm assuming bootloader needs to be unlocked to use this method? If so, is there a way to apply the latest xt1644 nougat update before unlocking bootloader? Thanks
Click to expand...
Click to collapse
Which method were you referring to? If it's the update to Nougat, bootloader status doesn't really matter (OTAs may still install if you have a stock recovery/kernel/system with an unlocked bootloader, and the fastboot method will also install if your bootloader is unlocked). For everything else, yes you will need an unlocked bootloader (and thereby voiding your warranty).
You could either wait until the Nougat update arrives and then update via OTA, then unlock, or flash the fastboot ROM before or after unlocking, honestly up to you. So long as your bootloader is the only thing that's been modified, OTAs should be okay - anything else and a fastboot ROM may be required.
Okay, so I got the bootloader unlocked, and I have got the latest Nougat firmware installed (NPJ25.93-14), flashed through fastboot, and I can't get TWRP to install through fastboot, Ive tried two different downloads, please see screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bovineyard said:
Okay, so I got the bootloader unlocked, and I have got the latest Nougat firmware installed (NPJ25.93-14), flashed through fastboot, and I can't get TWRP to install through fastboot, Ive tried two different downloads, please see screenshot.
Click to expand...
Click to collapse
You've got the TWRP recovery installed, those errors are normal (I imagine because we don't have the right cryptographic keys). At the end of each command, you'll note [OKAY] is present, so the flash worked, ensure you reboot into recovery after flashing to prevent the stock recovery overwriting. Afterwards, TWRP should persist on your device. You may wish to use the adb command 'adb reboot recovery' to accomplish this or boot into recovery via the bootloader.
Got this ROM running, working great! Thanks for all of the efforts!
One but one but I have is: in Phone-settings-calls, when you select calls (to setup voicemail, etc.,), com.android.phone force closes. My device is the xt1644, rom is the Lineage March 06 build. Latest modem (Dec 2016) and firmware were flashed before flashing Lineage. Verizon is the service provider.
One request I have is the ability to turn off Album art on the lock screen. Had that I my Nexus 6 with the Pure Nexus Substratum Rom by Beanstown and others.
When I go to about phone in my settings then update, I get a message that says IN2025_11.C.11 is ready to be downloaded and installed. When I click download and install it fills up the bar about 10% then crashes and says it was unable to be installed. Anyone have any advice or the update I can download to take care of it locally?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I installed it on mine today. So far so good, but I haven't been using it a bunch.
mkennedy455 said:
I installed it on mine today. So far so good, but I haven't been using it a bunch.
Click to expand...
Click to collapse
Did yours update normally? Did you have to local upgrade?
I just did the ota through system update in settings.. I read on here that there was an update so I manually checked and it showed up so installed it and it worked I was on open beta 1 Android 12 not rooted used incremental update. I used oxygen updater to install the beta I was on before. I'm a little confused because I thought I had to factory reset to go back to stable builds. Is this actually a stable build now or is it still a beta?
mkennedy455 said:
I just did the ota through system update in settings.. I read on here that there was an update so I manually checked and it showed up so installed it and it worked I was on open beta 1 Android 12 not rooted used incremental update. I used oxygen updater to install the beta I was on before. I'm a little confused because I thought I had to factory reset to go back to stable builds. Is this actually a stable build now or is it still a beta? View attachment 5565839
Click to expand...
Click to collapse
As far as I know its a stable but its only being rolled out to the beta users at the moment. I could be wrong
mkennedy455 said:
I just did the ota through system update in settings.. I read on here that there was an update so I manually checked and it showed up so installed it and it worked I was on open beta 1 Android 12 not rooted used incremental update. I used oxygen updater to install the beta I was on before. I'm a little confused because I thought I had to factory reset to go back to stable builds. Is this actually a stable build now or is it still a beta? View attachment 5565839
Click to expand...
Click to collapse
Idk why mine wont let me update through updates even tho it shows it there
it simply because you're rooted.. it's already known from a long time.
there're 2 way if you wanna update from OTA:
1. simple uninstall magisk, and restore image. then do update. then back install magisk again
2. localupdate again C.10 and because you're now lose root, then you should be able to update fine
dewa5227 said:
it simply because you're rooted.. it's already known from a long time.
there're 2 way if you wanna update from OTA:
1. simple uninstall magisk, and restore image. then do update. then back install magisk again
2. localupdate again C.10 and because you're now lose root, then you should be able to update fine
Click to expand...
Click to collapse
Oh alright. How would I install magisk again since I wont be able to patch ota?
dewa5227 said:
it simply because you're rooted.. it's already known from a long time.
there're 2 way if you wanna update from OTA:
1. simple uninstall magisk, and restore image. then do update. then back install magisk again
2. localupdate again C.10 and because you're now lose root, then you should be able to update fine
Click to expand...
Click to collapse
Did what you said, it updated. Rebooted. Then after a reboot again my phone only boots into recovery now....
H411UCIN093NIC said:
Did what you said, it updated. Rebooted. Then after a reboot again my phone only boots into recovery now....
Click to expand...
Click to collapse
what step that you actually do ?
If you like to do an OTA;
Go to Magisk, uninstall Magisk - restore Image
Download and Install the OTA but DONT reboot
Go to Magisk, install magisk to inactive slot after ota
Reboot
xtcislove said:
If you like to do an OTA;
Go to Magisk, uninstall Magisk - restore Image
Download and Install the OTA but DONT reboot
Go to Magisk, install magisk to inactive slot after ota
Reboot
Click to expand...
Click to collapse
Thank you
H411UCIN093NIC said:
Did what you said, it updated. Rebooted. Then after a reboot again my phone only boots into recovery now....
Click to expand...
Click to collapse
Try to change slot via fastboot
xtcislove said:
Try to change slot via fastboot
Click to expand...
Click to collapse
Yea I tried that. I had to use msm tool loose all data then start from scratch apply all updates then I was able to do what you said and it worked. I'm on the latest A12 with root but unfortunately I lost all data in the meantime.
Installing magisk in an inactive slot will result in a softbrick.
Maruli said:
Installing magisk in an inactive slot will result in a softbrick.
Click to expand...
Click to collapse
So lets say I am on the latest Android 11 stable build and I want to flash the C11 stable Android 12 build (full zip, not incremental) and keep root and data. Is there a way to do that?
Previously as others have said, we restore images in Magisk. Install the OTA, then direct install Magisk, then to inactive slot, reboot, and all is well. Does this no longer work? Can someone please give a full explanation of their understanding?
xgerryx said:
So lets say I am on the latest Android 11 stable build and I want to flash the C11 stable Android 12 build (full zip, not incremental) and keep root and data. Is there a way to do that?
Previously as others have said, we restore images in Magisk. Install the OTA, then direct install Magisk, then to inactive slot, reboot, and all is well. Does this no longer work? Can someone please give a full explanation of their understanding?
Click to expand...
Click to collapse
Do you have the IN2021 version? Because NA/global doesn't have a full ROM yet. I can only confirm what the guy above me has experienced - installing magisk (v24.3) into the updated slot will result in a softbrick. Without that step it's working fine (I managed to switch slots in fastboot and redo the update from previous slot again).
It seems like the boot.img from the IN2021 C11 ROM does work with the IN2025 software, since I couldn't extract the incremental OTA and patch the boot.img. That actually saved my phone and I almost used MSM tool.
Maybe it's different if you update from A11 to A12 - I updated from OB1 C10 to C11 and magisk messes something up in the process.
Maruli said:
Do you have the IN2021 version? Because NA/global doesn't have a full ROM yet. I can only confirm what the guy above me has experienced - installing magisk (v24.3) into the updated slot will result in a softbrick. Without that step it's working fine (I managed to switch slots in fastboot and redo the update from previous slot again).
It seems like the boot.img from the IN2021 C11 ROM does work with the IN2025 software, since I couldn't extract the incremental OTA and patch the boot.img. That actually saved my phone and I almost used MSM tool.
Maybe it's different if you update from A11 to A12 - I updated from OB1 C10 to C11 and magisk messes something up in the process.
Click to expand...
Click to collapse
Thanks, that helps a lot. I think I'm going to wait until the dust settles because I need my phone available for work. I can't be stuck in a bootloop for 3 hours trying to fix it.
I tried to extract the BOOT.IMG from the OTA file, trying many tools without success, although in the log of one of the extraction tools it told me that the boot had 100MB, in the output only a boot.img appeared with 0MB