Hi guys, I really hope you can give me a hand here. I was rooted using method 3. Yesterday I unrooted the device. Today there were some OTA updates, so I downloaded them and wanted to install them. It was 58 if I'm not mistaken. The phone rebooted and started installing the updates and after few seconds a symbol of android popped up with an error message. After that the phone started and said that update wasn't installed and the origanal settings were returned. After that it said that there wen't new updates available. Factory reset didn't help either. Later a new update was available 59 I think, but the same thing happened... I really don't know what to do now.
I have ZF2 64Gb, WW version installed on it.
right now running 2.19.40.22
I'm really hoping for your help
Update: I've don't system wipe and cache wipe from the recovery menu
Update N2: I've managed to install V2.19.40.22 image from official website. But my phone doesn't show me an option to do an OTA update, it says that there aren't any update available. Is there a way to make him check again properly?
Hi , do u have any other app that uses root access ex xposed , busybox.If yes root and then uninstall these apps first.
harpreet.s said:
Hi , do u have any other app that uses root access ex xposed , busybox.If yes root and then uninstall these apps first.
Click to expand...
Click to collapse
Nope I only used root for titanium backup. It's been deleted... I can't even try to install new updates anymore...
NiKiToS-04 said:
Hi guys, I really hope you can give me a hand here. I was rooted using method 3. Yesterday I unrooted the device. Today there were some OTA updates, so I downloaded them and wanted to install them. It was 58 if I'm not mistaken. The phone rebooted and started installing the updates and after few seconds a symbol of android popped up with an error message. After that the phone started and said that update wasn't installed and the origanal settings were returned. After that it said that there wen't new updates available. Factory reset didn't help either. Later a new update was available 59 I think, but the same thing happened... I really don't know what to do now.
I have ZF2 64Gb, WW version installed on it.
right now running 2.19.40.22
I'm really hoping for your help
Update: I've don't system wipe and cache wipe from the recovery menu
Click to expand...
Click to collapse
flash the pre-rooted image of the firmware you all already have. then retry the OTA.
cmendonc2 said:
flash the pre-rooted image of the firmware you all already have. then retry the OTA.
Click to expand...
Click to collapse
Do you mean as in making the file MOFD_SDUPDATE.zit puting it on the SD card and through recovery? The update starts, then says gives an error
In recovery it says:
Veryfying current system...
"/system/build.prop" has unexpected contents
E: Error in /sdcard/MOFD_SDUPDATE.zip
(status 7)
I might have edited my build.prop file back then when I was playing with DPI. Now I can't find the line I edited... please help
NiKiToS-04 said:
Do you mean as in making the file MOFD_SDUPDATE.zit puting it on the SD card and through recovery? The update starts, then says gives an error
In recovery it says:
Veryfying current system...
"/system/build.prop" has unexpected contents
E: Error in /sdcard/MOFD_SDUPDATE.zip
(status 7)
I might have edited my build.prop file back then when I was playing with DPI. Now I can't find the line I edited... please help
Click to expand...
Click to collapse
That's why you have to flash the pre root firmware first. It restores all the system files so they can pass the check while the OTA runs.
NiKiToS-04 said:
Hi guys, I really hope you can give me a hand here. I was rooted using method 3. Yesterday I unrooted the device. Today there were some OTA updates, so I downloaded them and wanted to install them. It was 58 if I'm not mistaken. The phone rebooted and started installing the updates and after few seconds a symbol of android popped up with an error message. After that the phone started and said that update wasn't installed and the origanal settings were returned. After that it said that there wen't new updates available. Factory reset didn't help either. Later a new update was available 59 I think, but the same thing happened... I really don't know what to do now.
I have ZF2 64Gb, WW version installed on it.
right now running 2.19.40.22
I'm really hoping for your help
Update: I've don't system wipe and cache wipe from the recovery menu
Update N2: I've managed to install V2.19.40.22 image from official website. But my phone doesn't show me an option to do an OTA update, it says that there aren't any update available. Is there a way to make him check again properly?
Click to expand...
Click to collapse
OK
I have solution for you.
100% working.
Before update v 59 once do same with v 58.
I just reverted back to KitKat. In order to prevent any accidental updating, I skipped the entire setup process and immediately unchecked "Auto Update" under "About device" in the system settings. I rebooted the device for the hell of it. After connecting to wifi, the device is still downloading the Lollipop update. How do I stop it and get rid of the downloaded update?
Root it, it'll never update then.
I've already updated to the latest android 7.1.2 via adb tool. The image download from developers.google.com/android/ota.
But I still recieving android 7.1.1 ota updates notification.
If accept the update. It will process the download. After downloading finish, it says there's no need to install the update because my system is up to date, then the notification will disappear. But after a while the update notification will show again .
What's the problem with that. I haven't rooted my device.
A couple hours ago my phone with unlocked bootloader, twrp and magisk root installed an OTA update without me initiating it. This failed and the phone was stuck in twrp recovery and couldn't boot until I flashed a stock rom through fastboot and restored my backups.
Now I want to prevent this from happening again. How do I block the phone from checking for OTA updates?
I will have to install them manually anyway so the OTA checking is not helpful.
Same thing happened to me except I was dumb enough to try and install myself the update... You can install Titanium Backup and freeze the Motorola Update app. Also, you can go under dev options and disable automatic updates (this alone didn't work for me).
How to prevent OTA updates, without root, please?
I followed this guide, the method 4 worked for me when my phone was rooted.
http://www.droidviews.com/disable-ota-notifications-android-devices/
With help from the Google, I finally recalled how I'd done it in the past.
Initially, I thought rooting would stop OTA updates, but that may have been prior to Marshmallow or with SuperSU.
This time, I used Titanium Backup (must be rooted) to freeze the MOTOROLA UPDATE SERVICE app.
As soon as it was frozen, the OTA notification disappeared from the notification bar and I gave not seen it return, for a couple days.
Yay! I didn't want to go beyond the stock firmware version that is available and I really didn't want Oreo.
Another way is to use a firewall app.
Also you can just add Motorola's address to your 'host' file to block it
Im the opposite, I want the notifications, without the automatic installation.
Wonder if I changed the permissions of the folder the updates download to, would that prevent automatic install?
also, there is an option in developer options, to turn off OTA.
Global Update is there.
For those who installed it already, give us some feedback.. and one question, should factory rested be done before or after installing update? What is better, because i never did reset before, just apply update, but now would like to do reset also..
Works fine without reset. Smartphone was very hot during update. After installation I made a reboot. All Apps are working and Dark Mode is now available for most Apps.
This update broke my GooglePay, no longer passing ctsProfile in safetynet.
Seems to work fine. Before this update I was getting more and more bugs, but they seem to be gone now. Rebooting after the update took a long time, however. I was stuck on the Mix logo for 5-10 minutes.
There are some visual tweaks here and there, but that's all I can notice.
Themes available, region uk!
Latest update has caused my home launcher to crash. Am only able to use it cause of 3rd party launcher.
Does Magisk patched boot work with this? I was stuck a boot screen for over 10 mins before I had to reflash stock boot.img.
*update*
I had an out of date version of exposed installed that caused boot loop.
I can't install work email, and because my phone is CN region, of course, Google Pay not working. Not sure if boot options for the kernel changed, going to look and see if I need to update my flashable patcher zip.
blue1978 said:
Does Magisk patched boot work with this? I was stuck a boot screen for over 10 mins before I had to reflash stock boot.img.
Click to expand...
Click to collapse
Yes...work perfectly.
blue1978 said:
Does Magisk patched boot work with this? I was stuck a boot screen for over 10 mins before I had to reflash stock boot.img.
Click to expand...
Click to collapse
Not with the latest stable version. Take a look here so solve your problem: https://github.com/topjohnwu/Magisk/issues/2492#issuecomment-593149828
Any updates on anyone getting magisk to work on this? Can I use magisk patch with just the boot.img extracted from the OTA update .zip file?
I have the international not a china model.
Anybody found a solution for viper4android? I tried rootless 2.7 but driver will not install.
Quality_con_troll said:
Any updates on anyone getting magisk to work on this? Can I use magisk patch with just the boot.img extracted from the OTA update .zip file?
I have the international not a china model.
Click to expand...
Click to collapse
Magisk works.
But my ctsProfile fails on the safetynet.
Rendering GooglePay and PokemonGo unusable, which wasn't an issue for me before.
Also am international model.
After this update,
I was struggling to boot TWRP at first,
But my issue stemmed from trying to use adb / fastboot commands to boot into TWRP recovery, which only took me to stock recovery.
I got my Magisk back by doing a "fastboot flash recovery TWRP.img"
And then manually used the volume up + power button to boot TWRP (I used the unofficial mauronofrio)
And from there just install the Magisk zip.
spyke180 said:
Magisk works.
But my ctsProfile fails on the safetynet.
Rendering GooglePay and PokemonGo unusable, which wasn't an issue for me before.
Also am international model.
After this update,
I was struggling to boot TWRP at first,
But my issue stemmed from trying to use adb / fastboot commands to boot into TWRP recovery, which only took me to stock recovery.
I got my Magisk back by doing a "fastboot flash recovery TWRP.img"
And then manually used the volume up + power button to boot TWRP (I used the unofficial mauronofrio)
And from there just install the Magisk zip.
Click to expand...
Click to collapse
Just went through this process myself and came back here now to report on it.
This was my process for anyone also looking for guidance.
This will work for the new android 10 updated. I came from MIUI10 (10.0.3.2.0) using system update to go to MIUI11 and android 10 (11.0.3.0) via OTA update, which reverted to stock recovery and obviously lost root as well.
1. Saved most recent twrp 3.3.1-7-recovery.img for perseus by mauronofrio found in these XDA threads, magisk 20.3.zip found on magisk site and repository, and just to be sure disable forced encryption-treble.zip (just search for it) to my phone AND adb directory on Windows 10 computer.
ENSURE USB IS PLUGGED INTO 2.0 or 2.0 COMPATABILE HUB (Flashing recovery failed when connected to a USB3.0 port) and ADB/FASTBOOT is installed on your computer.
2. Booted into fastboot. (Power + Volume down)
3. Ran cmd.exe and entered "cd C:/(wherever you installed/platform-tools" without quotes.
4. Entered "fastboot devices" to ensure fastboot is connected. It should show device_id# and fastboot next to that.
5. Flashed TWRP3.3.1-7 for MiMix3 perseus (latest unofficial TWRP) by entering "fastboot flash recovery twrp3.3.1-7-recovery.img"
6. Entered "fastboot reboot recovery" the phone will reboot now, ENSURE YOU HOLD VOL+ ASAP or you will lose TWRP with stock recovery.
7. After booting into TWRP, entered password, wiped data and cache only.
8. In TWRP go to install and choose your disable_forced_encryption-treble.zip and flash it but do not select reboot device, it is selected by default.
(NOTE: Don't know if #8 is a necessary step especially for Global devices but did it anyways and it didn't hurt anything)
9. Go to install again and choose magisk20.3.zip, this time you can select reboot device.
10. After completing android setup download magisk manager 7.5.1 from play store and verify 20.3 is installed, if it is then congrats, you're rooted.
That's it! Like the above post said ctsProfile is reading false meaning you most likely will not be able to use Pay apps like Google Pay, etc.
Other apps that use google play services for verification may not work as well like Pokemon GO, Mario Kart, Harry Potter, or other banking/security apps. (Not sure about this one yet, try MagiskHide in the manager. Spyke180 is reporting above they do not work currently.) So if you can't live without Samsung Pay, or one of these games wait until a ctsProfile:true/SafetyNet passes solution is available.
Hopefully the next magisk update or someone in the community will be able to solve these issues in a timely manner, shouldn't be much of a wait.
Hope this made sense and can help some peeps out there perhaps.
CTSProfile is failing on my device as well. I tried using the boot cmdline patcher I made and it's still failing. I am wondering if Xiaomi released this update before getting the fingerprint in the CTS approved list. I can't think of anything else. My device is a CN device, so the BL is unlocked. I don't know if flashing Magisk with CN device and Global software still results in a boot loop but may try it.
Also, Magisk is detected through some methodology. I read all the posts made in both the release and beta threads in the last 3 days and it seems broken for everyone.
MMS stopped automatically sending and receiving on Google Messages app. But somehow works flawlessly on stock texting app. Notification tells me "Can't send MMS message. Tap to allow MMS messaging on (Carrier) when mobile data is off". Tapping the notification yields nothing. Even a factory reset does nothing.
siuyan187 said:
MMS stopped automatically sending and receiving on Google Messages app. But somehow works flawlessly on stock texting app. Notification tells me "Can't send MMS message. Tap to allow MMS messaging on (Carrier) when mobile data is off". Tapping the notification yields nothing. Even a factory reset does nothing.
Click to expand...
Click to collapse
If you go into settings, and then to "SIM cards & mobile networks", is the "Always receive MMS" toggle in the on position (blue)?
spyke180 said:
If you go into settings, and then to "SIM cards & mobile networks", is the "Always receive MMS" toggle in the on position (blue)?
Click to expand...
Click to collapse
Yep. Both in system settings and also in the app settings. Tried turning one on and the other off in different combinations, but still doesn't work.
siuyan187 said:
Yep. Both in system settings and also in the app settings. Tried turning one on and the other off in different combinations, but still doesn't work.
Click to expand...
Click to collapse
I see.
If you're rooted, you could try using the systemize module to make it a system app.
I verified my Google Messages and its notifications are working for me, even with both Wi-Fi and mobile data turned off.