Hello.
I have a few questions about firmware (MIUI) updates on a root device with an unlocked bootloader and stock ROM.
I know that when the bootloader is unlocked and the device is rooted, OTAs updates don't work.
1. Where can I find that a new version of the miui firmware has been released ? Link please.
2. What should the update file look like? size, file type.
3. How is the new firmware updated? method please.
4. So if the above mentioned firmware update can be installed, I ask if everything in the device remains the same, applications, data, etc.?
That's all I wanted to ask, thank you very much.
Look for xiaomifirmwareupdate on google.
On that site you will find latest firmware files for alioth PocoF3/redmi k40.
You will have a small file ~300mb.You update using TWRP.Just flash the archive and wipe cache.
I don't have twrp.
I'm following a topic about twrp, it's still an alpha version and from what I've read, it's still fully inoperable and backups and restores not work.
I thought that the firmware update (zip) could flash normally from the system, from the phone environment, where the updates are managed.
"still an alpha version and from what I've read, it's still fully inoperable" agree with you
jkmaxfli said:
I don't have twrp.
I'm following a topic about twrp, it's still an alpha version and from what I've read, it's still fully inoperable and backups and restores not work.
I thought that the firmware update (zip) could flash normally from the system, from the phone environment, where the updates are managed.
Click to expand...
Click to collapse
It works for firmware update.You cannot update the firmware from within android.
You could use fastboot to flash the images of the firmware one by one .
jkmaxfli said:
I don't have twrp.
I'm following a topic about twrp, it's still an alpha version and from what I've read, it's still fully inoperable and backups and restores not work.
I thought that the firmware update (zip) could flash normally from the system, from the phone environment, where the updates are managed.
Click to expand...
Click to collapse
Idk what u read.. Backups and restore work perfectly, I just did one backup and restore 2 days ago.
LiNe1771 said:
Idk what u read.. Backups and restore work perfectly, I just did one backup and restore 2 days ago.
Click to expand...
Click to collapse
It is interesting that you can back up and restore.
There were two questions in the topic about whether backup and restore worked and no one was able to answer. It is an official topic and it should be heard there that it can be fully backed up and restored.
is the 168 hrs waiting time when unlocking the bootloader a luck-based thing or will it always ask you to wait 168 hours?
Guan Le said:
is the 168 hrs waiting time when unlocking the bootloader a luck-based thing or will it always ask you to wait 168 hours?
Click to expand...
Click to collapse
Mostly 168 hours.
Old-registered lucky users can have instant unlock, very rare though.
Some bad credit/ unknown reasons Mi-account users can have 360 hours.
168 hours was a minimal time for xiaomi to plants something
LiNe1771 said:
Idk what u read.. Backups and restore work perfectly, I just did one backup and restore 2 days ago.
Click to expand...
Click to collapse
I already have Twrp.
Before the backup, did you check what specifically to make the recovery fully functional?
jkmaxfli said:
I already have Twrp.
Before the backup, did you check what specifically to make the recovery fully functional?
Click to expand...
Click to collapse
You can simply download the OTA, install it manually within the official updater (click the three dot when you're in the update app and choose manual install, then select the OTA in your file manager). After update is installed, DO NOT REBOOT DIRECTLY. Go then on magisk, click on install and choose the OTA way. Don't remember the exact word because my Magisk is in french. By this way, Magisk will install himself on the other partition (a or b, depends of your current partition in the moment of the update) so after the OTA, you will keep Magisk. It's possible because Poco f3 has 2 partition, a and b. On some phone, you have only one partition so you can't do this way.
jkmaxfli said:
I already have Twrp.
Before the backup, did you check what specifically to make the recovery fully functional?
Click to expand...
Click to collapse
By the way, if you don't see the tree dot, tap multiple tile on the miui logo in updater. So you unlock additional update feature
But I asked what all needs to be checked in twrp recovery in order to back it up.
Of course, thank you for the above instructions.
jkmaxfli said:
But I asked what all needs to be checked in twrp recovery in order to back it up.
Of course, thank you for the above instructions.
Click to expand...
Click to collapse
I know, I just gave you a another way to update
DeathStroke47 said:
Go buy a oneplus device if you love oxygen os
Click to expand...
Click to collapse
a little off topic, right?
Related
Hi all, please correct me if I placed this at the wrong thread.
I recently was flasing my phone with stock roms due to some technical difficulties I had. I realize the system will create an Android folder in my ext SD card. Is this normal? Do I need to be worry about it?
By the way, I am currently using 3.32.707.9 as my ROM, when I check my OS version in bootloader, there isn't anything there. Why is that so?
Can I flash back a lower version of ROM? For instance, 1.54.707.7
Thanks for helping in advance!
My responses below, in red font:
jkidz91 said:
I recently was flasing my phone with stock roms due to some technical difficulties I had. I realize the system will create an Android folder in my ext SD card. Is this normal? Do I need to be worry about it? Totally normal, no need to worry.
By the way, I am currently using 3.32.707.9 as my ROM, when I check my OS version in bootloader, there isn't anything there. Why is that so? This is usually due to using an older version of TWRP (known bug). This number is useful for determining your current firmware version (hboot, radio, etc.) but you can also determine that by looking at the hboot number and radio numbers themselves
Can I flash back a lower version of ROM? For instance, 1.54.707.7 Yes. Usually, you want the ROM version (1.x, 2.x etc.) to correspond to your current firmware. But its usually been found that a higher number firmware will usually work with older (smaller number) ROMs
Click to expand...
Click to collapse
redpoint73 said:
My responses below, in red font:
Click to expand...
Click to collapse
Which version of TWRP should I be using for now?
How do I verify which firmware am I using?
jkidz91 said:
Which version of TWRP should I be using for now?
How do I verify which firmware am I using?
Click to expand...
Click to collapse
What are your current hboot and radio baseband numbers?
Do you know what Android version you were on (4.4.2, 4.4.3, etc.) before you unlocked the bootloader and started flashing ROMs?
redpoint73 said:
What are your current hboot and radio baseband numbers?
Do you know what Android version you were on (4.4.2, 4.4.3, etc.) before you unlocked the bootloader and started flashing ROMs?
Click to expand...
Click to collapse
Current hboot is 3.19.0.0000
Radio baseband: 1.25.21331147A1.06G_20.69.4196.01_F
Previously should be on 4.4.2...I guess...ROM version 1.54.707.7
jkidz91 said:
Current hboot is 3.19.0.0000
Radio baseband: 1.25.21331147A1.06G_20.69.4196.01_F
Previously should be on 4.4.2...I guess...ROM version 1.54.707.7
Click to expand...
Click to collapse
Your hboot and radio numbers indicate your phone was either purchased with Lollipop firmware, or updated to LP firmware at some point.
You should use the latest version TWRP 2.8.7.
redpoint73 said:
Your hboot and radio numbers indicate your phone was either purchased with Lollipop firmware, or updated to LP firmware at some point.
You should use the latest version TWRP 2.8.7.
Click to expand...
Click to collapse
Yea, I upgraded to LP through phone update once.
Btw, I installed the latest version of TWRP as u said and was prompt by it by saying "TWRP has detected an unmodified system partition" and for permission to allow modifications...should I allow it?
jkidz91 said:
Yea, I upgraded to LP through phone update once.
Btw, I installed the latest version of TWRP as u said and was prompt by it by saying "TWRP has detected an unmodified system partition" and for permission to allow modifications...should I allow it?
Click to expand...
Click to collapse
I haven't seen this before, its a new feature for 2.8.7 (which you can have Googled just as easily as I just did):
we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery.
https://twrp.me/site/update/2015/06/22/twrp-2.8.7.0-released.html
Its actually not at all clear anymore what you are trying to do. You've posted in 2 or 3 different threads, asking about flashing firmware, running the RUU, or now you've flashed TWRP and maybe flashing an old 1.54 based ROM? Can't tell what your plan or end goal is at this time; and I'm not sure you know either.
redpoint73 said:
I haven't seen this before, its a new feature for 2.8.7 (which you can have Googled just as easily as I just did):
we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery.
https://twrp.me/site/update/2015/06/22/twrp-2.8.7.0-released.html
Its actually not at all clear anymore what you are trying to do. You've posted in 2 or 3 different threads, asking about flashing firmware, running the RUU, or now you've flashed TWRP and maybe flashing an old 1.54 based ROM? Can't tell what your plan or end goal is at this time; and I'm not sure you know either.
Click to expand...
Click to collapse
Basically my goal is to update my phone to LP..sorry for the confusion caused. I have managed to update the phone according to the link you gave as for the TWRP, I did some Google search as well...and decided not to allow the function...am I doing correct on this?
jkidz91 said:
Basically my goal is to update my phone to LP..sorry for the confusion caused. I have managed to update the phone according to the link you gave
Click to expand...
Click to collapse
Meaning you updated by RUU?
jkidz91 said:
as for the TWRP, I did some Google search as well...and decided not to allow the function...am I doing correct on this?
Click to expand...
Click to collapse
So you updated (apparently) to LP by RUU. Now what are you trying to do? Its still not clear.
Are you trying to root? If so, I'd allow the change, and then flash SuperSU 2.46 to root.
The text and link I provided is pretty clear about the mentioned TWRP function. The main reason to say "no" is to have a fully stock image, of which you can make a nandroid backup. Otherwise, you will probably want to pick "yes".
redpoint73 said:
Meaning you updated by RUU?
So you updated (apparently) to LP by RUU. Now what are you trying to do? Its still not clear.
Are you trying to root? If so, I'd allow the change, and then flash SuperSU 2.46 to root.
The text and link I provided is pretty clear about the mentioned TWRP function. The main reason to say "no" is to have a fully stock image, of which you can make a nandroid backup. Otherwise, you will probably want to pick "yes".
Click to expand...
Click to collapse
Correct me if I am wrong, if I would want to later on update my phone to higher OS, I should not allow TWRP to mount the system..correct?
Currently my situation is, I did not allow TWRP to do the mounting and I rooted the phone...and everything is working fine so far...does that mean I am safe?
jkidz91 said:
Correct me if I am wrong, if I would want to later on update my phone to higher OS, I should not allow TWRP to mount the system..correct?
Currently my situation is, I did not allow TWRP to do the mounting and I rooted the phone...and everything is working fine so far...does that mean I am safe?
Click to expand...
Click to collapse
If its working fine (for whatever purposed you need root), than you're good.
Although obviously, if you want to modify the system partition in the future, you will need write protection for that partition disabled.
You can always make a stock TWRP backup (which you should do, anyway) with the system unmounted, to return to for future OTA. Or return to stock using the RUU.
You also need the stock recovery to update by OTA. So your phone is not going to OTA update (update will fail) in its present configuration (with TWRP installed), regardless.
redpoint73 said:
If its working fine (for whatever purposed you need root), than you're good.
Although obviously, if you want to modify the system partition in the future, you will need write protection for that partition disabled.
You can always make a stock TWRP backup (which you should do, anyway) with the system unmounted, to return to for future OTA. Or return to stock using the RUU.
You also need the stock recovery to update by OTA. So your phone is not going to OTA update (update will fail) in its present configuration (with TWRP installed), regardless.
Click to expand...
Click to collapse
I need the Titanium backup to recover my apps and data ><
Hmmm..TWRP backup of the ROM...this is what you are talking about right?
Before that, does that mean that if the system has been tampered before, the OTA will not go in? This is what the link you gave just now talking about?
About the stock recovery, I am fully aware of this
I am really sorry if I keep causing trouble to you...I just want to double confirm...I have spent few days just to get my phone for working right...really exhausting to the mind ><
jkidz91 said:
Hmmm..TWRP backup of the ROM...this is what you are talking about right?
Before that, does that mean that if the system has been tampered before, the OTA will not go in? This is what the link you gave just now talking about?
Click to expand...
Click to collapse
Yes, the new feature seems to be aimed at ensuring the ROM is untampered, for making a full "stock" backup for OTA purposes.
jkidz91 said:
I am really sorry if I keep causing trouble to you...
Click to expand...
Click to collapse
No trouble at all. If I didn't enjoy helping, I wouldn't bother responding.
redpoint73 said:
Yes, the new feature seems to be aimed at ensuring the ROM is untampered, for making a full "stock" backup for OTA purposes.
No trouble at all. If I didn't enjoy helping, I wouldn't bother responding.
Click to expand...
Click to collapse
Got it! Whenever I do back up, do I need to back up the data? As I already got the Titanium to backup all my user apps.
What I am saying is the recovery let me choose what to back up...I chose only system, and boot i think...
redpoint73 said:
No trouble at all. If I didn't enjoy helping, I wouldn't bother responding.
Click to expand...
Click to collapse
Hi, after updating to Lollipop and using it for past few days, everything seems to be working fine...however, I have got a slight issue with Facebook app...whenever I am on my mobile data, I will have error loading the latest news feed. It is working fine on WiFi.
I have tested loading other apps with Mobile Data only...and they are working fine...I have researched online and some said I shall do a factory reset before and after a major update to OS...should I do this?
jkidz91 said:
Got it! Whenever I do back up, do I need to back up the data? As I already got the Titanium to backup all my user apps.
What I am saying is the recovery let me choose what to back up...I chose only system, and boot i think...
Click to expand...
Click to collapse
If the intent was to just backup a "stock ROM" than no need to backup user data.
If the intent is to make a recovery image, that you can just revert to and start using with no (or very little other actions) than backup data. But as you said, you can restore data (at least app data) with Titanium.
---------- Post added at 09:06 AM ---------- Previous post was at 09:04 AM ----------
jkidz91 said:
Hi, after updating to Lollipop and using it for past few days, everything seems to be working fine...however, I have got a slight issue with Facebook app...whenever I am on my mobile data, I will have error loading the latest news feed. It is working fine on WiFi.
I have tested loading other apps with Mobile Data only...and they are working fine...I have researched online and some said I shall do a factory reset before and after a major update to OS...should I do this?
Click to expand...
Click to collapse
If you updated by RUU then no need to factory reset. RUU already wiped all partitions, in a much more comprehensive way than factory reset.
Try clearing app cache for Facebook; or uninstalling Facebook app, and reinstalling, without restore data for that app with Titanium.
redpoint73 said:
If you updated by RUU then no need to factory reset. RUU already wiped all partitions, in a much more comprehensive way than factory reset.
Try clearing app cache for Facebook; or uninstalling Facebook app, and reinstalling, without restore data for that app with Titanium.
Click to expand...
Click to collapse
Tried doing so...not working...anyway, can I run the RUU again to wipe off the entire phone and set up as new?
jkidz91 said:
Tried doing so...not working...anyway, can I run the RUU again to wipe off the entire phone and set up as new?
Click to expand...
Click to collapse
You can run the RUU until the cows come home, if you want.
redpoint73 said:
You can run the RUU until the cows come home, if you want.
Click to expand...
Click to collapse
What does that mean? >< i tried to do it...it failed...should I just download a stock 4.19.707.2 rom and flash it?
So I've stayed at 2.19.40.20 because I wanted to wait to see if a better way to unlock the bootloader would be found, but I've given up and unlocked my bootloader (the unoffical way).
I want to get up to speed and update to the latest OTA.
Can I just flash the latest one or do I need to download every one til the newest update and sideload them individually?
If I have to do each one can I just load them one after the other, or do I need to reboot the phone and let it fully load to the OS for every update?
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
DiGecko said:
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
Click to expand...
Click to collapse
Azdinflash said:
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
Click to expand...
Click to collapse
Yes that should do it.
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
The_wolf88 said:
Yes that should do it.
Click to expand...
Click to collapse
Azdinflash said:
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
Click to expand...
Click to collapse
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
DiGecko said:
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
Click to expand...
Click to collapse
Does unrooting include removing Xposed?
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Wait, if I flash the 1.1 gig stock ROM, do I lose everything in the internal memory?
DiGecko said:
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Click to expand...
Click to collapse
I did a little digging, and it seems that the bootloop was fixed a few days ago:
http://forum.xda-developers.com/zenfone2/general/guide-to-install-xposed-installer-t3116476/page26
J M L said:
There's a new Xposed out, v78, which claims to fix a bootloop on 5.0 roms due to a security fix. I haven't tried it yet because I'm running a backup. Here is the thread and changelog.
We want the sdk21-x86 version.
Installed with no problem in TWRP with the flash able zip. Took a few minutes to boot, but seems to be working.
Click to expand...
Click to collapse
Good to know. No, you would not loose anything, at least I did not. Everything migrated over without any issues.
So I've gotten through sideloading the current version with no hiccups. Booted into system fine, it's the right version in the About section, and my internal memory came through intact.
I've flashed TWRP, and booted into it to install SuperSU when I got this message: "TWRP may have detected an unmodified system partition"
It explains that I can keep it as read only and make it easier to take official updates, but then TWRP will not be able to stop the stock ROM from replacing it and will not offer to root my device.
Should I keep it "Read Only" or should I allow the modification?
Just read about details about HUAWEI's new stock recovery called eRecovery. It seems users can no longer roll back and forth between stock ROMs, can only roll back to certain available versions.
Always keep your ROM latest: by using eRecovery, HUAWEI will no longer provide individual update.app file for manual update via SD. If EMUI system become unusable, eRecovery can help to update to latest Stock ROM to recover, during this process, user data may be wiped (like a full wipe in TWRP).
What if I want to downgrade?
If during the recovery process, eRecovery still can detect an earlier version of EMUI than your current version, then you can flash it, as a downgrade.
If during the recovery process, eRecovery detects the same version of EMUI as current one, then you have to flash it.
nice info...liked your signature as well buddy :good:
Be aware, i (and other members too) never saw this method working fine. Someone can say the inverse?
RedSkull23 said:
Be aware, i (and other members too) never saw this method working fine. Someone can say the inverse?
Click to expand...
Click to collapse
Old news mate. May be it was working on MM
shashank1320 said:
Old news mate. May be it was working on MM
Click to expand...
Click to collapse
Ouch, didn't noticed OP date. But, if Huawei removed firmwares from their site, where this recovery would obtain files so? Better to remain on fully safe methods like TWRP backups
RedSkull23 said:
Ouch, didn't noticed OP date. But, if Huawei removed firmwares from their site, where this recovery would obtain files so? Better to remain on fully safe methods like TWRP backups
Click to expand...
Click to collapse
TWRP back-up is always best when messed up.
Seeing all over the section people messing up and then want to rollback but with no file
shashank1320 said:
TWRP back-up is always best when messed up.
Seeing all over the section people messing up and then want to rollback but with no file
Click to expand...
Click to collapse
To me it is the first thing that someone should do as installed a custom recovery
RedSkull23 said:
To me it is the first thing that someone should do as installed a custom recovery
Click to expand...
Click to collapse
Yup but many are not following these things and messing badly.
Hi,
This guide is based in my first post about how to do it with the Moto G4: http://forum.xda-developers.com/moto-g4/how-to/guide-simple-ota-update-rooted-unlocked-t3510126
(Read it for full info).
Then, here the updated info for the Moto G5+:
1) If you are in NPN25.137-33 and like to apply the last OTA, but you have rooted and/or flashed a custom recovery (TWRP) + custom kernel, then you can.
2) Requirements: original SYSTEM and BOOT partitions. If you have flashed another version, then restore the originals. You can use any backups from you, or you can download from here: http://drive.google.com/open?id=0B6-Tz_7kDyxsZnVNa0pldnhndG8
(Thank you to GtrCraft: http://forum.xda-developers.com/showpost.php?p=72387571&postcount=15)
3) To apply the OTA download this ZIP and install it from the TWRP recovery (it's not required to have the TWRP flashed, you can start it from the fastboot util): http://www.sendspace.com/file/7w75rw
This file is the original OTA (shared by the user olive23) and patched by me to remove the check for the fingerprint of the running firmware. Then it can run over the TWRP.
Warning: Don't install this OTA if you don't have the exact version of the required firmware.
4) After install the OTA, reboot and check the new version. At that point the ROM isn't rooted. Then, you need to re-root.
That's all!
Tried flashing and it fails.
You need stock recovery to flash OTA's
GtrCraft said:
You need stock recovery to flash OTA's
Click to expand...
Click to collapse
Isn't that the point of this post? He said he patched the OTA update so it could be flashed with TWRP.
3) To apply the OTA download this ZIP and install it from the TWRP recovery (it's not required to have the TWRP flashed, you can start it from the fastboot util): http://www.sendspace.com/file/7w75rw
This file is the original OTA (shared by the user olive23) and patched by me to remove the check for the fingerprint of the running firmware. Then it can run over the TWRP.
Click to expand...
Click to collapse
bvsbutthd101 said:
Isn't that the point of this post? He said he patched the OTA update so it could be flashed with TWRP.
Click to expand...
Click to collapse
Well the OTA isn't meant for reteu firmware. So that will bring problems with it
bvsbutthd101 said:
Tried flashing and it fails.
Click to expand...
Click to collapse
Because isn't for your device OR you have modified SYSTEM or BOOT.
GtrCraft said:
You need stock recovery to flash OTA's
Click to expand...
Click to collapse
FALSE!
GtrCraft said:
Well the OTA isn't meant for reteu firmware. So that will bring problems with it
Click to expand...
Click to collapse
TRUE! :silly:
manos78 said:
Because isn't for your device OR you have modified SYSTEM or BOOT.
Click to expand...
Click to collapse
Installing TWRP and rooting doesn't change the SYSTEM or BOOT right? Must just not be for my device then. I have the US 4gb model (XT1687)
bvsbutthd101 said:
Must just not be for my device then. I have the US 4gb model (XT1687)
Click to expand...
Click to collapse
Probably. This OTA is from user "olive23".
I don't have (still) received any OTA in my XT1685 (EU 3/32).
manos78 said:
Probably. This OTA is from user "olive23".
I don't have (still) received any OTA in my XT1685 (EU 3/32).
Click to expand...
Click to collapse
Here's the OTA for the US 4gb model if you're interested. :good:
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
bvsbutthd101 said:
Installing TWRP and rooting doesn't change the SYSTEM or BOOT right? Must just not be for my device then. I have the US 4gb model (XT1687)
Click to expand...
Click to collapse
I have the same US model and this is supposed to be for it but it didn't work for me either, got errors during flash of OTA zip in TWRP that various partitions weren't accessible &/or verifiable. Even tried it a second time after a full restore to stock and had similar errors. I restored SYSTEM too (not sure that our rooting process works for systemless yet, meaning it would change SYSTEM), so that wasn't the problem in my case. Restored stock again and will wait to see if I get OTA normally.
bvsbutthd101 said:
Here's the OTA for the US 4gb model if you're interested. :good:
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
Click to expand...
Click to collapse
So did you get this OTA normally as a system update, indicating that we should be receiving it now?
Dahenjo said:
I have the same US model and this is supposed to be for it but it didn't work for me either, got errors during flash of OTA zip in TWRP that various partitions weren't accessible &/or verifiable. Even tried it a second time after a full restore to stock and had similar errors. I restored SYSTEM too (not sure that our rooting process works for systemless yet, meaning it would change SYSTEM), so that wasn't the problem in my case. Restored stock again and will wait to see if I get OTA normally.
So did you get this OTA normally as a system update, indicating that we should be receiving it now?
Click to expand...
Click to collapse
I got the update weeks ago. I've been postponing until someone makes it's flashable. I ripped it from my phone when I got it so yes, it's from my phone.
bvsbutthd101 said:
I got the update weeks ago. I've been postponing until someone makes it's flashable. I ripped it from my phone when I got it so yes, it's from my phone.
Click to expand...
Click to collapse
Thanks. I wonder why I haven't gotten anything and had phone since it came out on 3/31. I'm on NPN25.137-33 with a 4GB XT1687 from Amazon ($299 full-price without ads) on AT&T if carrier matters. Rooted or not we should still get the notifications as you have.
Dahenjo said:
Thanks. I wonder why I haven't gotten anything and had phone since it came out on 3/31. I'm on NPN25.137-33 with a 4GB XT1687 from Amazon ($299 full-price without ads) on AT&T if carrier matters. Rooted or not we should still get the notifications as you have.
Click to expand...
Click to collapse
Yeah I got mine the day it came out from amazon, using on Verizon.
Here is a flashable stock zip based on reteu firmware:
https://drive.google.com/open?id=0B6-Tz_7kDyxsU2NlTERsSzZsalk
U have*67 files??
Same Here
US variant XT1687 4/64GB on Sprint but no OTA notification. Maybe I should just wait another week before flashing this. Not sure if there is something in the SIM the server notices and stops updates on some carriers. But maybe the SIM is how they decide, not sure what else they could go by other than IP to detect the carrier.
bvsbutthd101 said:
Yeah I got mine the day it came out from amazon, using on Verizon.
Click to expand...
Click to collapse
I also have XT1687 4/64G US on 25.137-33 + root & TWRP, and no OTA notification.
So, is there a way to go to -67 (flash over TWRP, restore back to -15 stock)?
I could not understand the right answer from all the thread on the subject.
Sorry for this noob question: I have just rooted a brand new phone. After the first login the OTA warning popped out so I downloaded it. When finished I got a loop on the recovery; I fastbooted boot and got my phone working again ... what do I have to do? Thanks.
Hi,
My upgraded guide: http://forum.xda-developers.com/g5-plus/how-to/guide-complex-ota-update-magisk-rooted-t3688175
I'm on the stock ROM (Build number: OPNS27.76-12-22-3), rooted via Magisk and have the latest TWRP as my recovery. Say, an OTA update arrives (hopefully) in the future, could I just sideload it from my computer via adb? I know that downloading the file and installing it using the phone won't work as I'm on TWRP (it requires stock recovery). Erfan Abdi's website allows the download of the OTA zip from Moto's servers if one wants to sideload it via adb (https://erfanoabdi.000webhostapp.com/). If not, how can I apply the OTA update?
no you can't apply the ota with a custom recovery as you made changes on partitions that ota.zip check if has some changes and i believe twrp is not ready to aply ota in any way because every manufacture has a way to make changes by ota so its almost impossible to made a generic way to apply ota to all the devices that twrp suports
jst98 said:
no you can't apply the ota with a custom recovery as you made changes on partitions that ota.zip check if has some changes and i believe twrp is not ready to aply ota in any way because every manufacture has a way to make changes by ota so its almost impossible to made a generic way to apply ota to all the devices that twrp suports
Click to expand...
Click to collapse
So I should flash the stock recovery back and then sideload the OTA?
djdelarosa25 said:
So I should flash the stock recovery back and then sideload the OTA?
Click to expand...
Click to collapse
flash stock, take the ota's via ota, and then mod system. At least that's what I do. pita but it works. I back up with TBPro and copy backup to PC (ota clears internal storage) before I do that so rebuild is pretty quick.
my last smartphone is just uninstall magisk and flash stock recovery to aply ota, but i never tried this on moto z play, so you should do a clean install of stock rom first, because i can't say with sure if it's gonna work as my last devices stops update on marshmallow , and magisk that i used on this phone is older
jst98 said:
my last smartphone is just uninstall magisk and flash stock recovery to aply ota, but i never tried this on moto z play, so you should do a clean install of stock rom first, because i can't say with sure if it's gonna work as my last devices stops update on marshmallow , and magisk that i used on this phone is older
Click to expand...
Click to collapse
I have to flash stock to take ota. ymmv. Let me know if AUG is out.
I just did an uninstall latest magisk uninstall and pogo doesn't work, so it's not clean, so will need to flash stock.
KrisM22 said:
I just did an uninstall latest magisk uninstall and pogo doesn't work, so it's not clean, so will need to flash stock.
Click to expand...
Click to collapse
there some things that have be analised here, first when you unistall magisk, the safetynet verification is gonna fail, and pogo can broke, and pogo is especially case, the pogo app checks storage to see if has some folder related magisk, that in most cases are left there to backup. and the ota check partition if you change something ota fails too.
stock ota is horrible to install if you have some changes in the device, so in almost all case, especialy if don't have advanced knowledge about all android work, the recomended is reflash system in same version that you are, and after this update.
jst98 said:
there some things that have be analised here, first when you unistall magisk, the safetynet verification is gonna fail, and pogo can broke, and pogo is especially case, the pogo app checks storage to see if has some folder related magisk, that in most cases are left there to backup. and the ota check partition if you change something ota fails too.
stock ota is horrible to install if you have some changes in the device, so in almost all case, especialy if don't have advanced knowledge about all android work, the recomended is reflash system in same version that you are, and after this update.
Click to expand...
Click to collapse
a) right. what I said. uninstall magisk is dirty - it doesn't clean everything up..
b) I could suggest TBPro to back up your system. Then be sure to copy that backup to your PC because flashing the stock will wipe internal storage. Then flash stock. Then use TBPro to restore stuff. At least that's sortof what I do.
what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk
JonasVFC said:
what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk
Click to expand...
Click to collapse
what security date are you on? Thanks.
KrisM22 said:
what security date are you on? Thanks.
Click to expand...
Click to collapse
june
JonasVFC said:
june
Click to expand...
Click to collapse
Thanks. That's what I'm on. I was wondering if Aug was out...
KrisM22 said:
Thanks. That's what I'm on. I was wondering if Aug was out...
Click to expand...
Click to collapse
Damn, Motorola's taking so long again.
djdelarosa25 said:
Damn, Motorola's taking so long again.
Click to expand...
Click to collapse
and then there's Pie... Apparently with Treble. I think a lot of new stuff coming at us soon...
I think it's about time for me to do some serious playing and looked and i see that Alberto97 is working on 9 ... hmmmmmmm.
JonasVFC said:
what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk
Click to expand...
Click to collapse
August security patch is out so I tried these steps.
It didn't work. While I sideloaded the update through adb, it showed that the system was modified and that it was mounted as R/W 40 times, also showing the most recent date and time that it happened. Keep in mind, I flashed the Magisk and Xposed uninstallers and cleared Dalvik and cache before the attempt to sideload.
I just flashed the original June build (omitting the 'fastboot erase userdata' command to save myself from a potential pain in the ass) and then did I proceed to sideload the update via adb. After that, I flashed the latest TWRP and rooted using the latest Magisk (and f2fs fix as well). My data is intact (except for the root modifications and Magisk modules) but that is miles better than starting from scratch off a factory data reset.
I guess I answered my own question, then . You can't
KrisM22 said:
and then there's Pie... Apparently with Treble. I think a lot of new stuff coming at us soon...
I think it's about time for me to do some serious playing and looked and i see that Alberto97 is working on 9 ... hmmmmmmm.
Click to expand...
Click to collapse
lol we are done. nothing new will come to us (owners of z1 play)
JonasVFC said:
lol we are done. nothing new will come to us (owners of z1 play)
Click to expand...
Click to collapse
yeah, lol, I'm playing with Pie. - Nothing new... HAH! silly rabbit.
djdelarosa25 said:
While I sideloaded the update through adb, it showed that the system was modified and that it was mounted as R/W 40 times, also showing the most recent date and time that it happened.
Click to expand...
Click to collapse
Do you have an idea how to easily display if system is modified (when, how often etc.)? I'd like to know if OTA could succeed after restoring boot partition for some Moto X Play and Moto Z Play with installed Magisk.
tag68 said:
Do you have an idea how to easily display if system is modified (when, how often etc.)? I'd like to know if OTA could succeed after restoring boot partition for some Moto X Play and Moto Z Play with installed Magisk.
Click to expand...
Click to collapse
Nope, sorry. Though, I failed to mention that I did flash the original boot.img after encountering the error and tried again. You guessed it, it still failed. Maybe try flashing both boot and oem to see if it would work?