Related
I was wondering, I have rooted my phone using Chainfire's CF-Autoroot.
Normally this will disable OTA updates, I'm aware of that.
But is there some way to manually flash the monthly security updates that Samsung releases each month ?
(or at least they say they are going to release them each month).
Is there a source somewhere where we can download them and flash then using Odin or TWRP ?
No you didnt root. There isnt full root for s7 yet
vipercoyote said:
No you didnt root. There isnt full root for s7 yet
Click to expand...
Click to collapse
Are you sure ? Because when I check manually for updates, I get the message stating that my phone has changed (root) and so updates cannot be downloaded and installed. It says that I need to try to download it via a PC tool from Samsung.
vipercoyote said:
No you didnt root. There isnt full root for s7 yet
Click to expand...
Click to collapse
There is for the International version.
vipercoyote said:
No you didnt root. There isnt full root for s7 yet
Click to expand...
Click to collapse
There very well is for the Exynos version/type and the reason I'm tempted to get it after prices have dropped a bit :
Check it here: http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
Ok guys, now that we have established that root is available and working for the European version (which I have)...
Anyone know if the monthly patches from Samsung/Google will be available for download somewhere, so we can flash it manually and still be up-to-date ?
I would like to know this as well. I would guess they could be flashed with Odin?
I would like to know this. I am on the W8 variant rooted with autoroot and wondering how will I go about updating to new patches.
Sent from my SM-G930W8 using Tapatalk
I love Android.
you should flash your firmware via Odin to unroot, apply OTA, root again with auto root.
exploreresp said:
you should flash your firmware via Odin to unroot, apply OTA, root again with auto root.
Click to expand...
Click to collapse
Yes, I am aware of this possibility.
I was just hoping in applying the monthly patch without full flash (which completely wipes the phone).
Indeed, flashing will reset the phone...I found that the hard way last night.
There is a topic on S7edge forum about Chainfire's FlashFire app. It claims that can flash without resetting the phone.
Did not try it but I will follow the discussions there. Would be perfect to flash a new f/w and not have the phone reset. ( like good old times
Maybe it is possible to prevent the userdata and internal storage to be wiped by flashing the official firmware ?
Anyone has succeeded to do so ?
I managed to download the complete new firmware G935FXXU1APD3 from Sammobile and flashed it with ODIN with the phone in download mode.
It did not overwrite any of my personal data or apps and the phone worked as before however you will need to root again afterwards, but that doesn't take long anyway.
The only other thing I had to do was copy the mixer_paths and mixer_gain files to the SD card then replace them as the new firmware overrides the volume hack if you have it in place.
Keith
I guess that's what Chainfire trying to achieve with Flashfire. To be able to directly flash the Updates without having to manually backup/restore anything. Let's see how this goes. As of today you could flash the full oding images within flashfire.
Will definitely try when the next update for my phone variant comes.
I did take a TWRP backup just in case but was pleasantly surprised when the phone booted back to where it was.
I can confirm that the Flashfire method can be used for updates. Grab the update package, flash it through flashfire, and even select the "ever root" option to maintain root. Works great!
databoy2k said:
I can confirm that the Flashfire method can be used for updates. Grab the update package, flash it through flashfire, and even select the "ever root" option to maintain root. Works great!
Click to expand...
Click to collapse
How did you get the update package? When trying to search for an update on the phone it says I modified it.
Or did you load an full stock rom?
brotbuexe said:
How did you get the update package? When trying to search for an update on the phone it says I modified it.
Or did you load an full stock rom?
Click to expand...
Click to collapse
Grabbed a full stock rom, extracted the modem and system packages, and flashed them specifically through flashfire. A link to the full stock rom was posted on the Canadian S7 thread in the discussion forum.
HI I was wondering if anyone could help verify that the downgrade is possible from 6.0 to 5.0 OK4. I used Odin to flash the stock OK4 firmware to my phone when I was on the 6.0MM firmware and I just want some one that is willing to test what I did just to verify that I wasn't just lucky.
What I did was while on 6.0 I setup ADB for the phone, rebooted to download mode and used Odin3-v3.10.6 to flash G900PVPU3BOK4_G900PSPT3BOK4_G900PVPU3BOK4_HOME.tar (got this from sammobile). When phone rebooted it got stuck at the boost logo screen for longer than I liked so I used "ADB reboot recovery" command and in recovery did a factory reset and then booted into system and I am having no issues. So can some one else test this so that I know it is a 100% way to downgrade?
I just flashed the OK4 tar via odin to go back to stock and take the MM update again. I wiped everything but internal and external storage in TWRP first. It's currently downloading the MM update.
i've successfully taken the PCA update twice, and used ODIN to go back to OK4 and update once again.
the bootloader does not appear to lock firmware.
pyrochance said:
i've successfully taken the PCA update twice, and used ODIN to go back to OK4 and update once again.
the bootloader does not appear to lock firmware.
Click to expand...
Click to collapse
So you just odin back to ok4? No other steps required?
Sent from my SM-G900P using Tapatalk
djxn40 said:
So you just odin back to ok4? No other steps required?
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
Correct, because when you odin OK4 it restores the stock recovery and everything else etc, so everything is stock again, system status is official etc. then you can either download the OTA as normal or take the zip from your thread and update from stock recovery. i've done it both methods.
pyrochance said:
Correct, because when you odin OK4 it restores the stock recovery and everything else etc, so everything is stock again, system status is official etc. then you can either download the OTA as normal or take the zip from your thread and update from stock recovery. i've done it both methods.
Click to expand...
Click to collapse
I assumed you couldn't revert. That's awesome though thanks
Sent from my SM-G900P using Tapatalk
I can also confirm that too, I just did a downgrade to OK4, after I unsuccessfully tried to downgrade to OA6. I assume that pyrochance (http://forum.xda-developers.com/showpost.php?p=66266625&postcount=138) is right.
If i was helpful, feel free to hit the thanks button on those posts
Are you rooted? I'm not rooted, and from BOK4 I was not able to downgrade via Odin to an earlier firmware that supports towelroot. I am now on Android 6 (OTA). Question - on Android 6 is it now possible to downgrade to an earlier firmware (without root, and without tripping knox)? If so is it only to BOK4? Thanks in advance.
ZedDedd said:
Are you rooted? I'm not rooted, and from BOK4 I was not able to downgrade via Odin to an earlier firmware that supports towelroot. I am now on Android 6 (OTA). Question - on Android 6 is it now possible to downgrade to an earlier firmware (without root, and without tripping knox)? If so is it only to BOK4? Thanks in advance.
Click to expand...
Click to collapse
Yes. You can only downgrade to OK4. If you weren't able to go to a previous version when on OK4 why would you be able to once beyond it?
Kreatur3 said:
Yes. You can only downgrade to OK4. If you weren't able to go to a previous version when on OK4 why would you be able to once beyond it?
Click to expand...
Click to collapse
Thanks Kreatur3, was thinking that with the new firmware they might have relaxed their restriction on downgrading. I would think that with any new official firmware, they could pretty much do whatever they want, like even take out all protections and allow you to root without tripping knox (which I know they wouldn't), or am I misunderstanding something?
ZedDedd said:
Thanks Kreatur3, was thinking that with the new firmware they might have relaxed their restriction on downgrading. I would think that with any new official firmware, they could pretty much do whatever they want, like even take out all protections and allow you to root without tripping knox (which I know they wouldn't), or am I misunderstanding something?
Click to expand...
Click to collapse
They could allow it but won't. It's obvious with the direction they are going with the s7. I can see why maybe providers don't want you to have that power but don't know why the manufacturer cares. Beyond the pressure from cell phone companies. I don't care about knox personally. I'm way beyond the warranty period and trip it every time the day I gety phones.
highspeedfelon said:
HI I was wondering if anyone could help verify that the downgrade is possible from 6.0 to 5.0 OK4. I used Odin to flash the stock OK4 firmware to my phone when I was on the 6.0MM firmware and I just want some one that is willing to test what I did just to verify that I wasn't just lucky.
What I did was while on 6.0 I setup ADB for the phone, rebooted to download mode and used Odin3-v3.10.6 to flash G900PVPU3BOK4_G900PSPT3BOK4_G900PVPU3BOK4_HOME.tar (got this from sammobile). When phone rebooted it got stuck at the boost logo screen for longer than I liked so I used "ADB reboot recovery" command and in recovery did a factory reset and then booted into system and I am having no issues. So can some one else test this so that I know it is a 100% way to downgrade?
Click to expand...
Click to collapse
You are a life saver it feels like i have been searching for a fix for ages and then my path led to here.
I am confirming i have downgraded successfully and i was on 6.0.1 MM tried OA6 and few more nothing worked but the OK4.
Thank You
alphadude said:
You are a life saver it feels like i have been searching for a fix for ages and then my path led to here.
I am confirming i have downgraded successfully and i was on 6.0.1 MM tried OA6 and few more nothing worked but the OK4.
Thank You
Click to expand...
Click to collapse
You are welcome.
I'm having a bit of trouble. I was on MM, then the phone started freezing up. So I went back to OK4 but I can't get past the Samsung boot up logo. It stays on there forever and doesn't move past it. I even tried to replays through Odin multiple times but still not working. I'm stuck.
I've only had two phones prior to this but I have always unlocked the boot loader / rooted the device / installed a custom recovery / installed custom ROMS.
I believe with my MOTO X 1st gen this disabled the OTA updates.
Is that the case with the Honor 8? I'm wondering if it is worth it to install TWRP at this point as there seems to be so little in the way of kernels and ROMS.
Would I still be able to use SU or Xposed modules without Root?
What is the best move with this phone?
I have unlocked my bootloader as well as rooted my Honor 8. The only way to get SU and Xposed is by doing both of these procedures(root involves getting TWRP).
As for any Xposed modules, I tried amplify+greenify but instead of getting better battery life, my standby time decreased significantly. I am not sure why, but for some reason my Cell standby was showing to be eating a ton of my battery. Another big problem was that the dialer app would not let me call anyone, it kept crashing whenever I tried to. Both problems were fixed after I managed to get amplify+greenify uninstalled. Currently I am just running YouTube AdAway and MinMinGuard which seem to work fine.
So at this point, is it worth unlocking bootleader, installing TWRP, and rooting your phone? Well if there are certain Xposed modules that you really want then sure, and if there are certain apps you like that require root, then yes go ahead and root your phone. Note that if you try any OTA updates, you will have to remove TWRP as having your phone automatically restart and try to install the update wont work.
Imagine that the Honor 8 receives an update to say, Nougat, what is the pathway to update for someone who has rooted their phone. Will the OTA be able to be flashed if a .zip is provided here? Would we need to flash an entirely new ROM?
This is what I faced with my MOTO X. When Marshmallow came out there was talk... but no one was working on the at phone any longer so was never able to update.
pairustwo said:
Imagine that the Honor 8 receives an update to say, Nougat, what is the pathway to update for someone who has rooted their phone. Will the OTA be able to be flashed if a .zip is provided here? Would we need to flash an entirely new ROM?
This is what I faced with my MOTO X. When Marshmallow came out there was talk... but no one was working on the at phone any longer so was never able to update.
Click to expand...
Click to collapse
It doesnt matter whether or not your phone is rooted. You will get updates the same way, through OTA. Of course you can find .zip files to flash(although personally I am struggling to get the latest update flashed through TWRP).
The real question is for how long will we be receiving updates? Nougat is pretty much guaranteed with the new EMUI update. Huawei/Honor has promised up to 2 years of updates from what I have heard, but who knows what that actually means. They have also have a "partnership" with XDA, and the phone is decently popular so I am sure there will be a few roms, just not as many as say a OP3.
Why are people trying to flash via TWRP if the OTA updates still work after rooting and unlocking the boot loader?
pairustwo said:
Why are people trying to flash via TWRP if the OTA updates still work after rooting and unlocking the boot loader?
Click to expand...
Click to collapse
Okay so I just figured it out, but for the OTA update to work after rooting and having a non-stock recovery, you need to go to Settings->Updater->Menu(located on the bottom)->Download latest full package.
The full package is ~1.6GB and the regular update is ~280mb. The full package will work even if you have TWRP installed. But if you want the regular 280mb update, you need to get rid of TWRP and go back to a stock recovery.
Of course you will need to reinstall TWRP and root your phone again after doing this update.
Rakeen70210 said:
Okay so I just figured it out, but for the OTA update to work after rooting and having a non-stock recovery, you need to go to Settings->Updater->Menu(located on the bottom)->Download latest full package.
The full package is ~1.6GB and the regular update is ~280mb. The full package will work even if you have TWRP installed. But if you want the regular 280mb update, you need to get rid of TWRP and go back to a stock recovery.
Of course you will need to reinstall TWRP and root your phone again after doing this update.
Click to expand...
Click to collapse
I see the full package but I cant click on this, nothing is happened when I click on this.
Nas42O said:
I see the full package but I cant click on this, nothing is happened when I click on this.
Click to expand...
Click to collapse
I am not sure what you mean. Do you mean you can see the text "Download latest full package" but it is greyed out? If so please check to see if you arent currently at the latest version. If there is another problem, you might want to try to find a .zip of the full package and flash it that way.
Rakeen70210 said:
I am not sure what you mean. Do you mean you can see the text "Download latest full package" but it is greyed out? If so please check to see if you arent currently at the latest version. If there is another problem, you might want to try to find a .zip of the full package and flash it that way.
Click to expand...
Click to collapse
Yes , not greyed , but red color , and cant click on this .
I downloaded a full update of B31 about 1.77giga , just copy to the phone and flash it in twrp ?
Nas42O said:
Yes , not greyed , but red color , and cant click on this .
I downloaded a full update of B31 about 1.77giga , just copy to the phone and flash it in twrp ?
Click to expand...
Click to collapse
The exact latest update that I currently have is FRD-L04C567B150. I am not sure where you got your update but I suggest you just flash back to a complete stock image and try to update again from there.
Rakeen70210 said:
The exact latest update that I currently have is FRD-L04C567B150. I am not sure where you got your update but I suggest you just flash back to a complete stock image and try to update again from there.
Click to expand...
Click to collapse
its normal , you live in India no ?
i'm live in European country , so update are different .. Last update for us is FRD-L04C432B130
Nas42O said:
its normal , you live in India no ?
i'm live in European country , so update are different .. Last update for us is FRD-L04C432B130
Click to expand...
Click to collapse
No I am in the US. I am not sure about the EU version, but yes if you can find a .zip update file just put it on your phone and go into TWRP to install it. Might wanna make a backup too and wipe cache too just in case.
So if i download the full package in update and install it, bootloader will still be open? No full wipe? And later i only need to install twrp and root the phone again?
Palindrom87 said:
So if i download the full package in update and install it, bootloader will still be open? No full wipe? And later i only need to install twrp and root the phone again?
Click to expand...
Click to collapse
Updating or wiping your phone does not lock the Bootloader. The only way to lock the Bootloader again is by doing it manually yourself.
Yes after doing a full update you will need to reinstall TWRP as it will be replaced with the stock recovery and then re-root your phone again.
Rakeen70210, you sound really confident about doing full updates after rooting. Will these full updates also replace the kernel?
palendrome87 and NAS420 could you guys report back with any success or errors you have flashing full updates?
Where can one download full updates for Honor 8?
pairustwo said:
Rakeen70210, you sound really confident about doing full updates after rooting. Will these full updates also replace the kernel?
palendrome87 and NAS420 could you guys report back with any success or errors you have flashing full updates?
Where can one download full updates for Honor 8?
Click to expand...
Click to collapse
Seeing as how the full update package was ~1.65GB in size, I think its ok to assume that it replaces everything with the stock Honor 8 image. So yes it will replace the kernel too.
For downloading full updates, the only way I got mine was an OTA directly from the phone itself. Look at my previous comments to see how I got this update. If for some reason you cant update, check if your model is ready for an update. If it is and you cant update, try to flash back to a stock image. You should be able to find one on this site or anywhere else.
Flash stock recovery will lock boot loader ?
Nas42O said:
Flash stock recovery will lock boot loader ?
Click to expand...
Click to collapse
No, the only way to lock the bootloader is to manually lock it yourself using a similar operation to unlocking it.
Rakeen70210 said:
No, the only way to lock the bootloader is to manually lock it yourself using a similar operation to unlocking it.
Click to expand...
Click to collapse
I thought the same thing, but after taking the full OTA update my bootloader was locked again. If you want to update I would suggest first making a full backup to the external SD card in TWRP.
Then , its better to download à full update ( update.zip) ,copy to root of the phone , reboot in twrp and flash it ? Anyone already did it ?
Moto G4 Plus US Variant XT1644
Build# MPJ24.139-64 Android 6.0.1
Stock Unmodified TWRP Backup
Stock Recovery.img & Logo.bin
Description:
I could not find ANY stock images for the US XT1644 variant so I made my own for others that have modified their system partition and wish to restore to a factory state and take the 7.0 update. Backup created on a factory reset unmodified stock build (not previously rooted/xposed/modified in any way) via fastboot booting TWRP w/system write disabled. Stock recovery and logo extracted via DD from stock rooted rom after TWRP backup was made. I pulled the recovery and logo images as these are the most commonly modified partitions (other than the system). This backup will work if you stayed on 6.0.1 and rooted/exposed/changed boot logo/etc. If you played with the 7.0 updates made for other variants, I honestly don't know if this will work for you to take the OTA as the bootloader/modem were likely modified - Test and let us know.
Directions:
-Have ADB working on your PC (google it, not getting into that here)
-Download TWRP backup here: https://mega.nz/#F!vBgU3QJB!R5J5RgZkvUiWHwmIfN6BkA
-Move backup to your proper TWRP backup location on your sd or external sd
-Restore backup via TWRP and reboot
-Download stock recovery & logo images here: https://mega.nz/#F!eBpB3Z5C!J6hoLKdfcObSLavWCsLnyw
-Power off device/plug into pc/hold volume down for 5 seconds/press and hold power & volume down until fastboot appears
-Move files to adb location (Windows) or open terminal where you downloaded the files (Linux) on your pc
-Verify connection
Code:
fastboot devices
-Restore stock recovery:
Code:
fastboot flash recovery recovery.img
-Restore stock logo (if you changed it previously to get rid of warning):
Code:
fastboot flash logo logo.bin
-Reboot and enjoy stock 6.0.1 and be able to take OTA
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Click to expand...
Click to collapse
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Sent from my XT1575 using Tapatalk
annoyingduck said:
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Click to expand...
Click to collapse
I Will flash stock xt1644 firmware 64, then i restore your backup
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
pupamonkey said:
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
Click to expand...
Click to collapse
It's not available, we're still waiting for it, that's why we flashing stock firmware again
Thanks for doing this! It's essentially what I did to get the marshmallow update (restore stock system & boot via TWRP, then recovery & logo via fastboot).
Please let us know when you see moto/Lenovo push out the nougat update via OTA!
Sent from my Moto G4 Plus using Tapatalk
you are the champ!! i have exact same model but i am yet to update to 64 release as i just got the phone today. Just doing some research before i grease my hands! thanks man!
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
bmeek said:
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
Click to expand...
Click to collapse
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
where to check?
i have the us variant from best buy as well , but i twicked it a lot .
How can i know when a nougat release is available? where can i check .
panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
Click to expand...
Click to collapse
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Hymizzle said:
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Click to expand...
Click to collapse
If you flash a XT1625-XT1644 firmware and you use it "normally" on a XT1644, at some point you will have ghost touch even with low brightness, but...
For upgrading, I'll recommend flashing XT1625-XT1644, (cause there's no
...139-64 XT1644 firmware, just a firmware for both)
Flash it via fastboot, boot it up, flash TWRP recovery, wipe the full system with it, download the TWRP backup that was posted here, restore it, then via fastboot flash the stock recovery (for removing TWRP) and stock logo, then you will have MPJ24.139-64 with no problems, just waiting for nougat OTA for retus version.
Here's the link for retus firmwares: https://mirrors.lolinet.com/firmware/moto/athene/official/RETUS/
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
TheDude1998 said:
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
Click to expand...
Click to collapse
Yeah I wouldn't think so, but thanks for letting us know.
Sent from my XT1575 using Tapatalk
getting the Nougat OTA
annoyingduck said:
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
Click to expand...
Click to collapse
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Click to expand...
Click to collapse
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
dedik46 said:
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
Click to expand...
Click to collapse
Yes your bootloader will still be unlocked unless you specifically enter the oem lock command. Read the tutorials, they all explain how to keep your bootloader unlocked.
Sent from my XT1575 using Tapatalk
bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
vishnureddy17 said:
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
Click to expand...
Click to collapse
Which of these 5 download? .
I'm running a Canadian Pixel on 7.1, I just unrooted so I could do the OTA to 7.1.1.
The update will download but fails while installing.
I'd like to flash the update myself but I'm unsure how. I'm running Ubuntu. Any help?
Thanks!
Sent from my Pixel using XDA-Developers Legacy app
Hi.. is the update like 200+ mb? if so mine does the SAME thing. Mine is (NDE63X) and you WONT find a OTA or a image for 7.1.1. NO clue
Have either of you tried the OTA images from Google's developer site?
Doesn't bootloader have to be locked to take the OTA? Don't do this if your on Verizon veriant.
Konfuzion said:
Doesn't bootloader have to be locked to take the OTA? Don't do this if your on Verizon veriant.
Click to expand...
Click to collapse
NO it doesn't have to be locked. I don't think there is a Verizon variant in Canada either which is what the OP says they have.
I mentioned the Verizon veriant because people other than the OP will read what I posted.
christanya99 said:
I'm running a Canadian Pixel on 7.1, I just unrooted so I could do the OTA to 7.1.1.
The update will download but fails while installing.
I'd like to flash the update myself but I'm unsure how. I'm running Ubuntu. Any help?
Thanks!
Click to expand...
Click to collapse
See below.
Zeblade said:
Hi.. is the update like 200+ mb? if so mine does the SAME thing. Mine is (NDE63X) and you WONT find a OTA or a image for 7.1.1. NO clue
Click to expand...
Click to collapse
Download fastboot from Google and unzip it.
https://developer.android.com/studio/releases/platform-tools.html
Download the latest full factory images from here and unzip it into your fastboot folder. Edit the flashall bat file and remove the -w so you save your apps and data. Run flashall.Bat You will be stock not rooted and no TWRP when you are done. Put back those items if you want.
https://developers.google.com/android/images
You cannot take OTAs directly once you root, even if you completely unroot. You'll need to sideload (or use the edited factory image as in the post above mine). It's not very difficult, there's a nice guide over here: https://forum.xda-developers.com/pixel/how-to/twrp-root-nmf26u-sideload-guide-t3531616
You'll need to re-root/reinstall TWRP if you want to use that functionality again.