Related
I got the update for the January Security Update today. I grabbed the .zip's location and the link on Google's servers is:
https://android.googleapis.com/pack...51c56752.signed-angler-MMB29P-from-MMB29M.zip
Hope it helps others!
PSA: this is not flashable over custom ROMs, and cannot be used to install the factory OS from nothing. That's what the factory images are for . This .zip is solely to incrementally update from the December security update to the January one.
Is there an easy way to flash this update.zip without the need of a computer?
tinker_tf said:
Is there an easy way to flash this update.zip without the need of a computer?
Click to expand...
Click to collapse
Unless you have a custom recovery, no. Sorry about that
Updated. Thanks for the link!
I have a rooted, stock ROM and TWRP and with several Xposed Modules, can I flash this?
Also, I don't have the December update, where do I find that?
And lastly, I'm on MDB08L Build, will that work?
For those wanting to use this update and have completely stock system based on MMB29M. Boot into recovery and do an ADB sideload update.zip (rename zip first). Mine updated with no issues.
CipherSec said:
I have a rooted, stock ROM and TWRP and with several Xposed Modules, can I flash this?
Click to expand...
Click to collapse
If you've got all that set up, why not just update using the full factory image (without the wipe)
LeoRex said:
If you've got all that set up, why not just update using the full factory image (without the wipe)
Click to expand...
Click to collapse
I assumed I'll lose all my system modifications (i.e. Xposed Modules and their settings) as well as losing root and TWRP and having to reroot again.
pmedwards25 said:
Unless you have a custom recovery, no. Sorry about that
Click to expand...
Click to collapse
This is exactly the file you need if you don't have custom recovery, don't have root, and have not unlocked bootloader. It is the same file that would eventually come to you OTA. You do however need access to adb and a computer. I don't think this is flashable with a custom recovery.
Thanks..
Thanks for this file bro. dont need to wait.
Alright, feeling like a complete noob, here. I'm on systemless root 2.61 with TWRP. I fastboot flashed the stock boot.img and stock recovery, then tried to sideload the OTA zip. I got a "system contains unexpected contents" error, then installation aborted. Now, with systemless root, I had the understanding that flashing the stock system.img would not be necessary. I was not using systemless root before when I flashed the previous OTA zip. Can anyone spot where I might have gone wrong?
Casyis said:
Alright, feeling like a complete noob, here. I'm on systemless root 2.61 with TWRP. I fastboot flashed the stock boot.img and stock recovery, then tried to sideload the OTA zip. I got a "system contains unexpected contents" error, then installation aborted. Now, with systemless root, I had the understanding that flashing the stock system.img would not be necessary. I was not using systemless root before when I flashed the previous OTA zip. Can anyone spot where I might have gone wrong?
Click to expand...
Click to collapse
Try flash stock system image
Does this update fix the LTE issue?
HRodMusic said:
Does this update fix the LTE issue?
Click to expand...
Click to collapse
No it does not
I got it:
For systemless root, fastboot flash: 1) boot.img; 2) recovery.img; 3) vendor.img; 4) system.img
Boot to recovery and enter sideloade mode. adb sideload [update].zip
Reboot to bootloader. Re-flash TWRP, then in TWRP re-flash kernel (if custom) & superSU.
I used a toolkit to root my 6P. I'm using rooted stock rom. I got an OTA update but it seems I can't update it that way as per all others. So how do I go about installing this on my mobile? Do I need to unroot, flash stock recovery & then flash the new image? Then again I have to root?
fyi: i'm rooted with systemless root and twrp
I tried to take this update per usual as i would if i were unrooted, of course that didn't work totally. i assumed i would just find the update.zip file (i did: /data/data/com.google.android.gms/app.download/update.zip, icywtk) but when i tried to flash that it said the zip was corrupted. i deleted the zip and now it still says my december build is up to date. can't we just flash the update.zip with twrp? i did allow for the system to be modified this time when i booted twrp.
asj0422 said:
fyi: i'm rooted with systemless root and twrp
I tried to take this update per usual as i would if i were unrooted, of course that didn't work totally. i assumed i would just find the update.zip file (i did: /data/data/com.google.android.gms/app.download/update.zip, icywtk) but when i tried to flash that it said the zip was corrupted. i deleted the zip and now it still says my december build is up to date. can't we just flash the update.zip with twrp? i did allow for the system to be modified this time when i booted twrp.
Click to expand...
Click to collapse
I am rooted with twrp. Same deal, twrp reports and error 7 when trying to flash the Jan security update.
kmp14 said:
I am rooted with twrp. Same deal, twrp reports and error 7 when trying to flash the Jan security update.
Click to expand...
Click to collapse
i just tried this again with the same results. it says that the installer is expecting a different build (the one that my settings app shows i'm on) but that i have a build called huawei/mmasomething/ dee_stroyer somethingsomething. (i would post exactly what it says but i've already rebooted into system). I do remember something with "dee_stroyer" when i was rooting but it's not the system...
anyone else have any ideas? i'd like to just update normally and keep my data... and the stock android with root.
EDIT: also, the update won't update my recovery will it? i don't want to have to reflash that. i should be able to update even when i'm away from a computer haha.
Rooted with TWRP. I just tried an ADB sideload and get the same error.
It seems it is impossible to get root with magisk on latest Oreo stock. Maybe someone found solution?
I asked and I answer =)
To get the root it is required to
- install latest TWRP (current version twrp-3.2.1-0)
- reboot to TWRP
- install 16.2 or higher magisk, link for 16.2
- install f2fs bug workaround
- reboot system
- install magisk Manager
- enjoy your root =)
dolar4ik said:
I asked and I answer =)
To get the root it is required to
- install latest TWRP (current version twrp-3.2.1-0)
- reboot to TWRP
- install 16.2 or higher magisk, link for 16.2
- install f2fs bug workaround
- reboot system
- install magisk Manager
- enjoy your root =)
Click to expand...
Click to collapse
its not work for me:crying:
Try to follow this guide then: https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
But use latest magisk beta instead of suggested 15.3.
And keep in mind that it is possible to easily restore working state with magisk uninstaller.
Do you have any errors during magisk or workaround installation in twrp console?
dolar4ik said:
Try to follow this guide then: https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
But use latest magisk beta instead of suggested 15.3.
And keep in mind that it is possible to easily restore working state with magisk uninstaller.
Do you have any errors during magisk or workaround installation in twrp console?
Click to expand...
Click to collapse
now its working for me.:highfive::highfive:
dolar4ik said:
I asked and I answer =)
To get the root it is required to
- install latest TWRP (current version twrp-3.2.1-0)
- reboot to TWRP
- install 16.2 or higher magisk, link for 16.2
- install f2fs bug workaround
- reboot system
- install magisk Manager
- enjoy your root =)
Click to expand...
Click to collapse
Hi, does not work for me, stuck at bootloader logo, tried Magisk, followed the steps many times but nothing, can you help please ?
evnimaster said:
Hi, does not work for me, stuck at bootloader logo, tried Magisk, followed the steps many times but nothing, can you help please ?
Click to expand...
Click to collapse
follow this: https://forum.xda-developers.com/mot...reo-8-t3743273
Code:
echo keepverity=true>>/data/.magisk
echo keepforceencrypt=true>>/data/.magisk
Is there a way to remove encryption already?
Remove root?
Is it possible to remove root and the TWRP without hard reset? Does anyone already have the original recovery of Oreo?
DavidKalil10 said:
Is it possible to remove root and the TWRP without hard reset? Does anyone already have the original recovery of Oreo?
Click to expand...
Click to collapse
There is magisk uninstaller provided in official thread.
To remove twrp you just need to flush original recovery via fastboot
Hello guys, can I have some advice on whether I should install this latest Oreo update on my moto z, how is the battery doing on this update? And overall experience?
@dolar4ik
i reflash the stock oreo ROM,then flash TWRP,flash magisk,flash f2fs bug workaround, stuck at bootloader logo,how can i do it??
Flash the Magisk uninstaller, reboot to recovery (you have this option in TWRP) and flash again only the Magisk 16.3 (without the f2fs bug workaround). This worked for me two days ago.
Today I updated to the latest Magisk 16.4 without any problems.
lesbianu said:
Flash the Magisk uninstaller, reboot to recovery (you have this option in TWRP) and flash again only the Magisk 16.3 (without the f2fs bug workaround). This worked for me two days ago.
Today I updated to the latest Magisk 16.4 without any problems.
Click to expand...
Click to collapse
still not work for me.:crying::crying:
---------- Post added at 03:12 AM ---------- Previous post was at 02:58 AM ----------
This is strange. It works on Oreo OTA but it does not work in full flash Oreo ROM.
have anyone help me??
rakee said:
It works on Oreo OTA but it does not work in full flash Oreo ROM.
Click to expand...
Click to collapse
This is right.
I re-flashed my phone using the OPL27.76-51 firmware. Now, no way to install Magisk (old, new, any version).
The solution, I restored a TWRP backup made at the first bootloader unlock (when the ROM was updated only using OTAs, not flashed). Immediately I was able to install Magisk 16.4 - without any F2FS workaround.
HERE is my TWRP backup containing the partitions: Boot, Data & System. Hope it helps!
rakee said:
@dolar4ik
i reflash the stock oreo ROM,then flash TWRP,flash magisk,flash f2fs bug workaround, stuck at bootloader logo,how can i do it??
Click to expand...
Click to collapse
Uninstall magisk with it's own uninstaller.
I installed Magisk on the full Oreo release and everything is working.
I did make a "less bloat, less bs" zip version but I doubt it would make a change.
If you guys want, I can upload it when I get home.
The Marionette said:
I installed Magisk on the full Oreo release and everything is working.
I did make a "less bloat, less bs" zip version but I doubt it would make a change.
If you guys want, I can upload it when I get home.
Click to expand...
Click to collapse
Could you provide your twrp ZIP Version? That would be great.
lesbianu said:
This is right.
I re-flashed my phone using the OPL27.76-51 firmware. Now, no way to install Magisk (old, new, any version).
The solution, I restored a TWRP backup made at the first bootloader unlock (when the ROM was updated only using OTAs, not flashed). Immediately I was able to install Magisk 16.4 - without any F2FS workaround.
HERE is my TWRP backup containing the partitions: Boot, Data & System. Hope it helps!
Click to expand...
Click to collapse
Just got myself a hand me down Moto z.
My friend who gave it to me hasn't touch the phone for a year.
So i started with 6.0 and after multiple updates, now i am on Oreo.
Since i have done ota from Marshmallow, would this method work?
Bootloader was never unlocked.
thanks for any input
Hi everyone,
i have a rooted pixel 3. I rooted it without twrp, i used adb to flash the patched boot.img so i have stock recovery. The January update arrived yesterday and i need to update to fix the video camera bug. How can i update? Thanks
Get factory image. Extract. Open "flash-all.bat" and remove -w before the update part (if you want to keep data). Disable any magisk mods you might have and reboot to system. Reboot to bootloader and run flash-all.bat . If you want root again, use magisk manager to patch the new boot.img
There is a guide for it:
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
For 3xl, but the same procedure
Thank you so much!
tekno281 said:
Hi everyone,
i have a rooted pixel 3. I rooted it without twrp, i used adb to flash the patched boot.img so i have stock recovery. The January update arrived yesterday and i need to update to fix the video camera bug. How can i update? Thanks
Click to expand...
Click to collapse
A simpler way is to follow this procedure to install the OTA update.
https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
Hello, I updated to Q and can't get it rooted.
It bootlooped.
How can I root Android Q?
visit: h t t p s : / / twrp.me/site/update/2019/10/23/twrp-and-android-10.html
As, if now you cannot. For Android Q, it's still in research.
------------------------------------------------------------------------
Never tried but: ClockworkMod Recovery – a past alternative to TWRP custom recovery.
h t t p s : / / en.wikipedia.org/wiki/ClockworkMod#ClockworkMod_Recovery
Research over it & let me know if anything worked for you-!
I successfully roote Q with this ?
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
I just flash TWRP, format and flash custom rom. Rooted.
First of all. What device do you have and what exactly have you tried? Include references.
Remember first step is to search before asking.
Guys need to re root my device on android 10 cuz i had it root under android 9 and cannot use s health
Need to root to chanfe the build prop command to use s health
Also missing the heart monitor pressure
Please help me
G965f
StonebridgeGr said:
Guys need to re root my device on android 10 cuz i had it root under android 9 and cannot use s health
Need to root to chanfe the build prop command to use s health
Also missing the heart monitor pressure
Please help me
G965f
Click to expand...
Click to collapse
I would recommend you flashing custom firmware, like the one in my signature. Everything is working, including Security Folder.
Rooting S9 +
sarjarim said:
I just flash TWRP, format and flash custom rom. Rooted.
Click to expand...
Click to collapse
Which TWRP version you used and how did you install TWRP on a non-rooted phone? Do you not have to use Magisk to root the phone first?
xectis said:
Which TWRP version you used and how did you install TWRP on a non-rooted phone? Do you not have to use Magisk to root the phone first?
Click to expand...
Click to collapse
I just used the 3.3.1.1 from the TWRP site.
Flash TWRP is to root, so I did it b4 root.
1. OEM unlock
2. Flash TWRP with odin then boot to TWRP, samsung will restore if u normal boot.
3. Backup EFS
4. Format data wipe all
5. Dm verity, search newest from dr ketan
6. Flash custom ROM.
Magisk usually comes with the custom ROM.
sarjarim said:
I just used the 3.3.1.1 from the TWRP site.
Flash TWRP is to root, so I did it b4 root.
1. OEM unlock
2. Flash TWRP with odin then boot to TWRP, samsung will restore if u normal boot.
3. Backup EFS
4. Format data wipe all
5. Dm verity, search newest from dr ketan
6. Flash custom ROM.
Magisk usually comes with the custom ROM.
Click to expand...
Click to collapse
Magic! Thanks bro.
For Android 10 U9 bootloader, is not more possible flash custom binaries... even twrp!
G965FXXU9ETF5
hi im new to this but what do you mean by Q??
i have sprint s9+ sm-g965u1, can i root my phone now ?
Devilix said:
For Android 10 U9 bootloader, is not more possible flash custom binaries... even twrp!
G965FXXU9ETF5
Click to expand...
Click to collapse
This isn't true I flashed Twrp 3.5.091 via Odin, S9+ exynos android 10, then flashed Magisk 21.4.
When I got phone it was android 10 June 2020 security update. It then updated again to 21/02/2021 ota.. I was able to flash recovery twrp and root/debloat. Only problem I did find is that I cannot flash lineage 18.1 or any custom roms.
Regards
JeyKul said:
Hello, I updated to Q and can't get it rooted.
It bootlooped.
How can I root Android Q? No root method root android Q.
Click to expand...
Click to collapse
hey ,
1.install magisk manager on your phone
2.download the firmware from samfirmware for your model of phone to pc
3.download 7zip with lz4
4. use 7zip lz4 to extract boot img from AP(firmware)
5. send the xtracted boot.img to phone sdcard and use magisk manager to patch said image .
6. send the patched img to pc and use 7zip to create archive as boot.tar file
7. one you install the firmware as normal via odin (disable auto reboot ) go back and disconnect/reconnect usb from phone so it appears as added in odin once more.
8. add the boot.tar file to AP in odin and flash the phone , reboot system and install magisk manager again , go into magisk and it will reboot again to fix the root.
there is a video somwhere on youtube showing you better than ive tried to here.
this is by far he best way as you can still take ota updates because stock recovery is still present .
regards
Hi there,
i'm rooted and i installed the latest OTA (oxygen os 10.3.7.hd01AA - india rom maybe because i used a patched boot.img in the first time months ago) right now and just like all the times before i made the usual steps:
1) Restored Original Image via Magisk Manager
2) Downloaded and installed OTA
3) Didn't reboot and tried to Install Magisk to inactive slot
Unfortunately 3 didn't work. More than that - Magisk Manager doesn't even recognized Magisk was uninstalled. So there is no Installation option.
Tried to Uninstall it again (Restore Original Image) but that didn't change anything.
a) Was the 2nd "Restore Original Image" after installing the OTA a bad idea?
b) How can i install Magisk now?
I don't reboot the phone as i think it could be bricked after that.
Dacoco said:
Hi there,
i'm rooted and i installed the latest OTA (oxygen os 10.3.7.hd01AA - india rom maybe because i used a patched boot.img in the first time months ago) right now and just like all the times before i made the usual steps:
1) Restored Original Image via Magisk Manager
2) Downloaded and installed OTA
3) Didn't reboot and tried to Install Magisk to inactive slot
Unfortunately 3 didn't work. More than that - Magisk Manager doesn't even recognized Magisk was uninstalled. So there is no Installation option.
Tried to Uninstall it again (Restore Original Image) but that didn't change anything.
a) Was the 2nd "Restore Original Image" after installing the OTA a bad idea?
b) How can i install Magisk now?
I don't reboot the phone as i think it could be bricked after that.
Click to expand...
Click to collapse
Well the procedure is disable all magisk modules. Reboot. Take the update don't reboot when the updater says to. Go to magisk select patch to inactive slot let it do it's thing then reboot
for now make a new patched one based on your current is to obtain root like you did initially
Ex pull your current non root boot img patch it in magisk then flash in fastboot
If you need I can grab the India ROM from Updater and make you a patched boot image?
I've already done it for HD01AA EU and HD01BA
Hey, i could manage to install Magisk into inactive slot after updating Magisk manager to the latest version. I would try to reboot now?
If I would like to patch my current boot.img - how can I do so?
digidude512 said:
If you need I can grab the India ROM from Updater and make you a patched boot image?
I've already done it for HD01AA EU and HD01BA
Click to expand...
Click to collapse
Thanks. I think I'll try to reboot and then - if it doesn't Boot - I will come back to you.
Dacoco said:
Thanks. I think I'll try to reboot and then - if it doesn't Boot - I will come back to you.
Click to expand...
Click to collapse
Any luck?
digidude512 said:
Any luck?
Click to expand...
Click to collapse
Booted up and root is working! Thanks a ton!
Dacoco said:
Booted up and root is working! Thanks a ton!
Click to expand...
Click to collapse
Well the ROM is already downloading, Might as well do the boot and recovery images anyway lol
When I'm done I'll update this thread to include HD01AA India
https://forum.xda-developers.com/7t-pro/how-to/oos-10-0-13-hd01aa-t4195159