Does anyone have a fix?
Did you flash this to Slot B? Is it an older OTA update with Magisk patched into it? Some versions I have tried fails to start WIFI.
Related
Tried to reroot with latest firmware N910TUVU2EQC1. Supersu fails to flash during the boot image patcher portion.
Method I did so far:
1. Update firmware via smart switch. I originally tried to flash via downloaded link but it didn't work so I tried the firmware officially from samsung via smart switch thinking there might have been a bad download link.
2. Odin flash twrp 3.0.2
3. Reboot
4. Try to flash supersu 2.79 va Twrp.
5. Fails during installation process, specifically during the boot image patcher. Tried wiping calche/davik, etc first. Still can't get root.
Mr Joegernaut said:
Tried to reroot with latest firmware N910TUVU2EQC1. Supersu fails to flash during the boot image patcher portion.
Method I did so far:
1. Update firmware via smart switch. I originally tried to flash via downloaded link but it didn't work so I tried the firmware officially from samsung via smart switch thinking there might have been a bad download link.
2. Odin flash twrp 3.0.2
3. Reboot
4. Try to flash supersu 2.79 va Twrp.
5. Fails during installation process, specifically during the boot image patcher. Tried wiping calche/davik, etc first. Still can't get root.
Click to expand...
Click to collapse
What about try to flash this room probably it will work https://forum.xda-developers.com/no...rom-n910t3uvu3eqc1-stock-rooted-odex-t3592242. its a stock rooted rom.
I hope you don't have a bad memory problem as many people does. good luck
I was able to flash superSU finally after doing a complete factory wipe and firmware update via smart switch. I deleted some factory installed apps on the last firmware which probably caused some kind of issues when I upgraded to the latest firmware.
On another note, I have the DRK failed to verify message, I have had it since I have had the phone. Any suggestions to fix this? I just did a factory restore via smart switch so I know that doesn't fix it.
i have the fi - android one phone. it is unlocked and rooted with magisk. last nite i was prompted for march update. it failed. i then realized i could get the update by having magisk patch back the images to default and then after the update put back magisk patched images. i no longer get the notification on the upgrade and it shows current. i tried to reset via clearing configupdater in apps and still nothing.
is there any way to force the ota updater to give me another try ? i believe i could re flash this version and not erase user data and then maybe get the update and reinstall magisk, but i'd rather not go that route as i spent some time getting my gpay to work etc. thanks if anyone knows.
glenb77 said:
i have the fi - android one phone. it is unlocked and rooted with magisk. last nite i was prompted for march update. it failed. i then realized i could get the update by having magisk patch back the images to default and then after the update put back magisk patched images. i no longer get the notification on the upgrade and it shows current. i tried to reset via clearing configupdater in apps and still nothing.
is there any way to force the ota updater to give me another try ? i believe i could re flash this version and not erase user data and then maybe get the update and reinstall magisk, but i'd rather not go that route as i spent some time getting my gpay to work etc. thanks if anyone knows.
Click to expand...
Click to collapse
I don't think there is a way around flashing the stock firmware first.
Same phone. I would suggest flashing the latest firmware (edit the flash-all to disable the userdata wipe). The phone should take the update at this point.
https://mirrors.lolinet.com/firmware/moto/payton/official/FI/
You can flash either Fi or Retail, as they are interchangable.
jhedfors said:
I don't think there is a way around flashing the stock firmware first.
Same phone. I would suggest flashing the latest firmware (edit the flash-all to disable the userdata wipe). The phone should take the update at this point.
https://mirrors.lolinet.com/firmware/moto/payton/official/FI/
You can flash either Fi or Retail, as they are interchangable.
Click to expand...
Click to collapse
yeah, that is method i was referring in my post. i am looking to do the update because fi has sort of said this update should correct this problem on x4. https://forums.lenovo.com/t5/Moto-X...to-X4-quot-Invalid-SIM-Card-quot/td-p/4308420 but i don't want to have to reset/add my credit cards in gpay because banks are calling because i have added or attempted so many times trying to get gpay and magisk to work. so i was hoping to do this method which should keep everything as is with magisk: https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md that was what i was wondering. i got this phone recently from google and have it doing everything i want except the fluid carrier switching. probably best i wait a few weeks. thanks for the reply
just a quick update, maybe it helps someone. i did get the new march update on the phone. i did get the update notice eventually. i did try the magisk a/b method but that failed. that left magisk not available as i restored the original image.
i flashed the feb image from mirror from bootloader with no erase of userdata. when that rebooted i got update notice for the same image i had just flashed (feb 2019). i am guessing that is the result of leaving the userdata intact. i let it complete that process and rebooted.
following that install and reboot, i got the notice for the march update and i got a failure which may be because i had the vpn proxy ad blocker (block this) running so i terminated that and uninstalled magisk manager. the update then completed. leaving me on PPW29.69-39-1 patch level march 1, 2019. this is a fi phone.
rebooted and reinstalled magisk manager. i had to install magisk (canary) from bootloader using twrp img. everything seems the way it was with nothing lost, my gpay cards are still there i don't know whether or not gpay will work in stores yet.
this issue where fi pops up invalid sim has gone away so i am hopeful the fi switching issue has been resolved on this phone
Where did you get magisk canary?
I went back to Feb stock to install the March update. Now when I try fastboot boot twrp image, it just sits there "sending" nothing happens.
nxt said:
Where did you get magisk canary?
I went back to Feb stock to install the March update. Now when I try fastboot boot twrp image, it just sits there "sending" nothing happens.
Click to expand...
Click to collapse
magisk canary is here https://github.com/topjohnwu/magisk_files/tree/master/canary_builds use release.zip. i had this on my external mem card because twrp can break encryption on internal storage.
i did : 1. magisk uninstall in app by replacing image 2. from fastboot/bootloader flash rom from mirror don't erase user data. 3. reboot 4. get march update (in my case i got same feb, installed and rebooted then got march update 5. reboot to bootloader boot from twrp.img, install magisk zip off of memory card. 6. reboot install magisk apk. i am sure this is a ymmv but this is what worked on mine.
normally i just update my phone and install the latest magisk, but now rooting just makes the phone bootloop, miui ver 20.6.4 and the previous weeks update did the same. dose anyone else have the issue? perhaps rooting method changed?
xdarkmario said:
normally i just update my phone and install the latest magisk, but now rooting just makes the phone bootloop, miui ver 20.6.4 and the previous weeks update did the same. dose anyone else have the issue? perhaps rooting method changed?
Click to expand...
Click to collapse
I don't think that there is some changes in rooting method because I followed :
1.Unlock bootloader
2.Flashed TWRP
3.Flashed magisk
4.Configured magisk app after normal boot
And confirmed, my device is rooted !!
Got it to work. But I had to manually patch my boot image myself and then fully uninstall magisk then flash modded boot img.
Here's what's happening:
I'm currently on stock V11.0.14 on both slots, magisk rooted and data is encrypted.
Both slots are bootable, and PBRP (recovery) successfully detect and decrypt data partition.
Not sure why, but if I try the usual process to update, uninstall magisk and apply System Update, it always fail, I've reflashed the stock ROM on both partitions and got the same result.
Then I tried to manually flash the full rom (any version greater then V11.0.14) to the inactive slot but it always fails to boot.
Something that I've noticed is that if I boot PBRP with the updated partition active, it fails to detect that the data partition is encrypted and I think that Android is facing the same problem, the updated version isn't detecting the encryption as well.
If I flash V11.0.14 back, it boot.
Any suggestions/solutions rather than full data wipe?
Cheers!
Just today I wrote comment on problems with updates to versions >= 11.0.15.0 :
December 2020 Security Update now available
Hy, December Update out now. Greets
forum.xda-developers.com
As for TWRP - I regard as working 2 versions only:
https://forum.xda-developers.com/t/recovery-unofficial-teamwin-recovery-project.4209151 by @Nebrassy
and older https://forum.xda-developers.com/t/...-mi-a2-jasmine_sprout-by-d4e8ede8f1f2.3941096 by @d4e8ede8f1f2
Just updated to 14, rooted device and my Bluetooth won't stay on. Anybody else have that problem? Thanks
hllywd said:
Just updated to 14, rooted device and my Bluetooth won't stay on. Anybody else have that problem? Thanks
Click to expand...
Click to collapse
If you rooted and used the old patched image you will have issues.
If you lost root when your updated.
You would fastboot boot boot.img(magisk patchedimg) then when phone boots go to magisk manager and do direct install(ignore magisk not installed or needs to reboot etc message) after direct install reboot. This will patch the new rims boot img instead of using say .12 s boot img that would give you issues with Bluetooth or wifi etc
So to fix your issue I would download the software update apk from a13 dp1. Download a14 rom from oxygen updater and do local update with that app.(don't reboot in software updater. Then open magisk and select patch to inactive slot and hit reboot in magisk after