September Update for Moto G Power (Sofiar) - Moto G Power Questions & Answers

Anyone else already recieved the September patch update?

Yes
Sent from my moto g power using Tapatalk

tnomtlaw said:
Yes
Sent from my moto g power using Tapatalk
Click to expand...
Click to collapse
Anyone happen to copy the OTA before updating?

No. Got mine from Google via Fi. Software channel is Google and not Moto.

anyone rooted with Magisk managed to get it installed? i have not been able to do it the usual A/B slot way

sinned6915 said:
anyone rooted with Magisk managed to get it installed? i have not been able to do it the usual A/B slot way
Click to expand...
Click to collapse
Easy way to update is use Lmsa, go to rescue, download the firmware. Copy the boot image from the download to the phone and patch it with magisk. Edit the flashfile.xml (remove erase user data at the bottom) and save. should be in C:\ProgramData\LMSA\Download\RomFiles, use the rescue option and after the phone reboots go back and flash the magisk patched boot as normal.

Related

[AT&T] [OTA] (unmodified) Version 139.12.54

Disclaimer:
I am not responsible for any damage what-so-ever done to your phone, as with any thing you do with/to your phone, you accept this risk.
If you want to stay rooted, do your research first.
The AT&T OTA is already rolling out to most phones. This should come in handy as a backup.
Please make sure your phone is unmodified and your using the stock recovery, before flashing this.
Otherwise the update will fail or bootloop over and over again.
Backup any important data.
Place the OTA on your phones sdcard.
Reboot into Recovery (Power off the phone. Hold Volume Down + Power. Release the Power button, navigate to recovery by pressing Volume Down then select Recovery with Volume Up).
Once in Recovery (Select apply update from sdcard / Find the downloaded OTA zip (Blur_Version.139.12.54.ghost_att.ATT.en.US.zip) file, select it and confirm to flash).
Reboot.
Done...
You that means "you" can not root or downgrade after flashing this. You've Been Warned: http://www.mediafire.com/?03ycm1atr36jiy0
Can i use this in americamovil.en.cl version with unlocked bootloader???
Enviado desde mi XT1058 usando Tapatalk
Just a friendly reminder for n00bs (like i had to search). When you see the red triangle, hold volume up and press power to get recovery menu options.
ATT Update and Americamovil
waiflih said:
Can i use this in americamovil.en.cl version with unlocked bootloader???
Enviado desde mi XT1058 usando Tapatalk
Click to expand...
Click to collapse
No it has to applied on an ATT build.:crying:
And if i flash att stock firmware first? Does it come with 2600hz band for lte?
Tnx in advance
Enviado desde mi XT1058 usando Tapatalk
can this version be rooted?
moises1204 said:
can this version be rooted?
Click to expand...
Click to collapse
Yes but, a root for it has not been released to the general public. If your rooted already use this: Tutorial: How To Protect and Restore Root for an OTA Update http://forum.xda-developers.com/showthread.php?p=46093725
touchpro247 said:
Yes but, a root for it has not been released to the general public. If your rooted already use this: Tutorial: How To Protect and Restore Root for an OTA Update http://forum.xda-developers.com/showthread.php?p=46093725
Click to expand...
Click to collapse
thanks for the reply, but too much for me to even try this, thanks anyway.
for some reason i was able to keep root doing this:
Steps to Restore Root:
1. Make sure that there are no modifications to the system files. If there are the update will fail to flash. There are two way to go about this. You can flash back to stock using the FXZ for your carrier and rsdlite or fastboot (whichever you prefer) or remove the modifications if you know what they are. If you just removed all mods then skip to step 3.
2. Now you will need to install PwnMyMoto and then run it. After 2-3 reboots you should be rooted.
3. Make sure you install SuperSU and OTA RootKeeper.
4. Shutdown your Moto X. Then hold the power and down volume keys for about 5 seconds to boot into the bootloader. Scroll down with the down volume key to recovery and press the up volume key. You will be booted into android with write protection disabled.
5. Open up SuperSU. If it asks you to update the binary update it. mine failed to update.
6. Open OTA RootKeeper. Grant it superuser rights and click Protect Root. It will save a backup of su. After that i went back to the superSu i tried to update the binary but it failed, after that i went to the motoRoot on the phone and unroot the phone,i went ahead did the OTA update to the new software from my phone itself, after that i rebooted my phone and went to the play store and uninstalled superSu and re-installed back then i went to MotoRoot and hit root and it worked for some reason i dint have to do all of the steps you have to do to preserve root! i dont know if it would work for anybody else but that is what i did and it worked for me. so what do you guys think it happen here?
What does it take to modify this so that it doesn't alter the bootloader and prevent us from downgrading later?
touchpro247 said:
Yes but, a root for it has not been released to the general public. If your rooted already use this: Tutorial: How To Protect and Restore Root for an OTA Update http://forum.xda-developers.com/showthread.php?p=46093725
Click to expand...
Click to collapse
so this version will be rootable? considering picking up a used moto x on this version but I would eventually miss root. didn't know there was something happening on this front? thought jcase said for now this was done.
mohlsen8 said:
so this version will be rootable? considering picking up a used moto x on this version but I would eventually miss root. didn't know there was something happening on this front? thought jcase said for now this was done.
Click to expand...
Click to collapse
Jcase has already stated there won't be another 4.2.2 root, 4.3 possibly
When can we get a ROM with this update like the t mobile version?
Sent from my XT1058 using XDA Premium 4 mobile app
Really, all you have to do is post this.
http://lmgtfy.com/?q=site:forum.xda-developers.com+moto+x+at&t+OTA+unmodified
Gets the point across a lot more succinctly.
ardoreal said:
Really, all you have to do is post this.
http://lmgtfy.com/?q=site:forum.xda-developers.com+moto+x+at&t+OTA+unmodified
Gets the point across a lot more succinctly.
Click to expand...
Click to collapse
Well played sir!!
Sent from my Moto X
Can this be flashed on a Rogers phone? (same model)
Could I flash this on a unmodified Rogers moto x? Just wanna know if there's a easier way to get 4.4 than just rooting
Sent from my XT1058 using Tapatalk

ZS570KL Android 7.0 OTA Firmware download&install guide(if you unlock)

Here is the ROM
all links should add"" by yourself
For 2.15:https://dlsvr04.asus.com/pub/ASUS/ZenFone/ZS570KL/UL-Z016-WW-5.14.44.1898-user.zip
UL-Z016-WW-5.14.44.1898-user.zip
For 2.40:https://dlsvr04.asus.com/pub/ASUS/ZenFone/ZS570KL/UL-Z016_1-WW-5.14.44.1898-user.zip
UL-Z016_1-WW-5.14.44.1898-user.zip
Both of them are from Chine office website
Install Guide:
1.Download both 6.0 and 7.0 Firmware (for your model)and put them into your SD card
2.flash office recovery
3.Enter recovery and choose "Apply update from SD card" and flash 6.0 first and 7.0 firmware in order
4.Wipe Cache partition (not necessary but advice to do it)
5.Have fun with your android 7.0
there is still no twrp for android 7.0 now,so no root right now but will come soon.(TWRP now is in beta)
2.flash office recovery
where do I find this?
samson1357924 said:
there is still no twrp for android 7.0 now,so no root right now but will come soon.(TWRP now is in beta)
Click to expand...
Click to collapse
I look forward to a twrp for Android 7. I already updated to Android 7 but lost my root and I would like to reinstall/flash magisk through twrp. The lasty twrp versions I tried in Android 6, showed upside down on my phone when I booted twrp, but the touchscreen was at the "regular" spot, so it was very very difficult to navigate. I hope I do not have that problem with the next twrp.
palgo47 said:
2.flash office recovery
where do I find this?
Click to expand...
Click to collapse
Here come the stock recovery from Z016-WW-4.12.40.1698
For 2.15Ghz
https://drive.google.com/file/d/0By3NdBos6w6JQ2ZTWi1pMTdYWE0/view?usp=sharing
For 2.4Ghz
https://drive.google.com/file/d/0By3NdBos6w6JWXZOanJDbmI0akU/view?usp=sharing
this article came from Taiwan Asus office Forum:
https://www.asus.com/zentalk/tw/thread-185884-1-1.html
blahforme said:
I look forward to a twrp for Android 7. I already updated to Android 7 but lost my root and I would like to reinstall/flash magisk through twrp. The lasty twrp versions I tried in Android 6, showed upside down on my phone when I booted twrp, but the touchscreen was at the "regular" spot, so it was very very difficult to navigate. I hope I do not have that problem with the next twrp.
Click to expand...
Click to collapse
Here come the ZS570KL twrp for 7.0(this file came from Taiwan Asus office Forum made by shakalaca)
https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
Forum link:https://www.asus.com/zentalk/tw/forum.php?mod=viewthread&tid=220546&extra=page=1&page=3&mobile=2
samson1357924 said:
Here come the twrp for 7.0(this file came from Taiwan Asus office Forum made by shakalaca)
https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
Click to expand...
Click to collapse
Thank you very much. The twrp still loaded upside down, but I was able to carefully navigate it to install magisk v11.1 again to regain my root and be able to use Android Pay once again. Thank you again!
You think by now that the twrp would be back to normal after all these updates. Is there something missing in there, that making it upside down?
blahforme said:
Thank you very much. The twrp still loaded upside down, but I was able to carefully navigate it to install magisk v11.1 again to regain my root and be able to use Android Pay once again. Thank you again!
Click to expand...
Click to collapse
You are welcome~
So glad to help you^^~
samson1357924 said:
Here come the ZS570KL twrp for 7.0(this file came from Taiwan Asus office Forum made by shakalaca)
https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
Forum link:https://www.asus.com/zentalk/tw/forum.php?mod=viewthread&tid=220546&extra=page=1&page=3&mobile=2
Click to expand...
Click to collapse
Thanks... doesn't reboot anymore on mine and I can interact with the screen... but it is still upside down. Makes it very difficult.
jnmacd said:
Thanks... doesn't reboot on my and I can interact with the screen... but it is still upside down. Makes it very difficult.
Click to expand...
Click to collapse
Ummm......Maybe you are S821 model?The twrp maker seem doesn't have S821 model,so this recovery mightn't work on 6G/256G
samson1357924 said:
Ummm......Maybe you are S821 model?The twrp maker seem doesn't have S821 model,so this recovery mightn't work on 6G/256G
Click to expand...
Click to collapse
I have the non-pro version.. 2.15Ghz
I am using the sd 820 64GB version and twrp shows upside down for me.
jnmacd said:
I have the non-pro version.. 2.15Ghz
Click to expand...
Click to collapse
Well,I didn't have this problem...
But there is a new version release,maybe you should try!
twrp-3.1.0-0-Z016D-20170317-N.img
In the same link!
There is no need for all these complicated steps. My phone(Z016D) was also rooted. I just downloaded the Nougat ROM, copied it over to the root of the internal drive. As soon as you disconnect the phone from PC, you will get a notification "New System Update detected". Click Update and you're good to go. After installation, I would suggest to do a factory reset.
Sent from my ASUS_Z016D using Tapatalk
rynaus said:
There is no need for all these complicated steps. My phone(Z016D) was also rooted. I just downloaded the Nougat ROM, copied it over to the root of the internal drive. As soon as you disconnect the phone from PC, you will get a notification "New System Update detected". Click Update and you're good to go. After installation, I would suggest to do a factory reset.
Sent from my ASUS_Z016D using Tapatalk
Click to expand...
Click to collapse
It's a good news!You mean that you update to 7.0 with twrp?!!!It is awesome!
However I want to know that how did you root?with superSU?system-less superSU?magisk?or another?And did you change your system?like install Exposed,viper4Android,or delete some system app?I think these actions might make you meat some problem when updating.So I think my method might be almost 100% to update success.
Whatever thanks for your advice,and enjoy your root
I think these actions might make you meat some problem when updating.
Click to expand...
Click to collapse
How exactly can they create problems. There reason you can't have OTA updates is unlocked bootloader. That however, shouldn't really prevent you from flashing rom through recovery via SD card or sideload or just dropping it into internal storage and doing what rynaus did.
_Kuroi_ said:
How exactly can they create problems. There reason you can't have OTA updates is unlocked bootloader. That however, shouldn't really prevent you from flashing rom through recovery via SD card or sideload or just dropping it into internal storage and doing what rynaus did.
Click to expand...
Click to collapse
I think that you can try rynaus first.Because it's more easier.If it isn't work ,try what I say.
How exactly can they create problems. →It may cause update fail, usually just can't update success.(from my experience from my ZF5 and ZF2)
samson1357924 said:
Well,I didn't have this problem...
But there is a new version release,maybe you should try!
twrp-3.1.0-0-Z016D-20170317-N.img
In the same link!
Click to expand...
Click to collapse
I can confirm that the twrp-3.1.0-0-Z016D-20170319-N does not show upside down for me. I hope you all have the same result.
https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
blahforme said:
I can confirm that the twrp-3.1.0-0-Z016D-20170319-N does not show upside down for me. I hope you all have the same result.
https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
Click to expand...
Click to collapse
Thanks for your reply^^~
0319-N works right for me too.. no longer upside down. Was able to root with Magisk

Root thread (US & EU) requests welcome! Oreo boot added

This is a US unlocked patched boot.img by magisk
It works on T-Mobile variant as well.
(Added EU patched boot.img)
(Added T-Mobile Oreo boot.img)
Link for Oreo T-Mobile
https://drive.google.com/file/d/17U0m0LIshFNBdNaygVqpsQ4TeLiDRUuo/view?usp=drivesdk
Link for latest T-Mobile 2.15.531.11
https://www.androidfilehost.com/?fid=890129502657596824
Install magisk manager apk from magisk thread.
Flash in fastboot
fastboot flash boot patched_boot.img in download mode.
I am not responsible for anything that happens to your device.
Credits to @Captain_Throwback for the right direction.
Credits to @topjohnwu for magisk.
And credits to anyone else that plays a part.
OS version 1.00.617.15 works for T-Mobile variant too.
Us unlocked stock boot.img link https://drive.google.com/file/d/11OFuYNePnSSCTfC4pWpxVOgKoLvByxJ0/view?usp=drivesdk
Patched boot.img link
https://drive.google.com/file/d/1XdoIln2zai1464CCTOE0LsD2SWbVZrW0/view?usp=drivesdk
ANDROID ONE FASTBOOT FLASHING IS DIFFERENT THAN US VERSIONS
because the a & b partitions.
So, now I have the patched_boot.img and the boot_signed.img for December security patch, build No. 1.09.401.2.
You have to check with "fastboot getvar all" wich partition is active so you have to boot to boot_a or boot_b. For me it was b now.
To take new update you have to flash the signed_boot first.
https://drive.google.com/open?id=1emcDV3p6Nuqgc2RVD9BnWUnU7JV-vqez
This is for os version 1.06.401.14 europe it is from
2Q3FIMG_OCEAN_LIFE_UHL_O80_SENSE90A1_HTC_Europe_1. 06.401.14_Radio_sdm630-005201-1711031628A_release_515519_signed_2_4
Patched htc_ocla1_sprout boot.img link
https://drive.google.com/open?id=1em...BnWUnU7JV-vqez
credits to @MC_Ohr
Stock boot.img
https://drive.google.com/file/d/1V69fjXKskPQ-6EpFZm2Pxe3S2yrFGIWL/view?usp=drivesdk
Awesome thanks to this I might get this device now.
EDIT: It's working, thanks.
BookCase said:
Not working for me.
Click to expand...
Click to collapse
You need to unlock your bootloader first..
I dont have tmobile version. I have normal Life (EU). How can root and unlock?
So, after installing Magisk, a lot of my apps are force closing.
Almost Evey app, and I cannot add accounts like 2nd Google or Facebook
Well just unlocked my booloader next flash me a recovery, Then it will be time to get some BadSeed up in here ,,,, Just sayin
BookCase said:
Almost Evey app, and I cannot add accounts like 2nd Google or Facebook
Click to expand...
Click to collapse
What device variant do you have?
twinnfamous said:
What device variant do you have?
Click to expand...
Click to collapse
T-Mobile HTC U11 Life
BookCase said:
T-Mobile HTC U11 Life
Click to expand...
Click to collapse
I have the same variant and no problems for me. Did u install anything else?
In case anyone has a temporary lapse of brain functioning like I did and gets confused because it seems this isn't working, it is important to remember that you'll need to install the Magisk Manager apk and Phh's Superuser (at least, those are the things I had to do after realizing I didn't pay attention to the fact that this is Magisk).
twinnfamous said:
I have the same variant and no problems for me. Did u install anything else?
Click to expand...
Click to collapse
I did install Titanium Backup and removed some bloat. Maybe I removed something I shouldn't have. I wonder if a factory reset would help or make things worse.
BookCase said:
I did install Titanium Backup and removed some bloat. Maybe I removed something I shouldn't have. I wonder if a factory reset would help or make things worse.
Click to expand...
Click to collapse
Factory reset and let google backup restore your apps
twinnfamous said:
Factory reset and let google backup restore your apps
Click to expand...
Click to collapse
Okay, so I did the factory reset and now Google Services FC's and I cannot setup the phone. I get to the "Set Up Wifi" screen and cannot progress further. I'm thinking I need a factory image to restore the phone, now. I really borked this thing.
Has anyone else had any issues with Magisk refusing to install modules after flashing this? It acts like a module is being flashed but changes nothing. I'm wondering if it has to do with not having a functional recovery at the moment. I have been able to install Xposed using the Xposed installer and Xposed is working perfectly.
BookCase said:
Okay, so I did the factory reset and now Google Services FC's and I cannot setup the phone. I get to the "Set Up Wifi" screen and cannot progress further. I'm thinking I need a factory image to restore the phone, now. I really borked this thing.
Click to expand...
Click to collapse
U should be able to get back to normal unless you modified the system. I have a system img. I can upload later if that's the case
After you install recovery, and you modify the system ( ie format the system ) are we able to flash things in recovery? I haven't yet but wondering
cbrown245 said:
After you install recovery, and you modify the system ( ie format the system ) are we able to flash things in recovery? I haven't yet but wondering
Click to expand...
Click to collapse
U can flash things in recovery now. You just can't decrypt data yet. So only you can flash from external SD card.
Yes , but is this after you format the memory ? I can't get anything to show on the SD card or the external SD card, is it required to format ?

December update is out

It's up and here https://developers.google.com/android/ota
gm007 said:
It's up and here https://developers.google.com/android/ota
Click to expand...
Click to collapse
Changelog?
Sent from my Pixel 3 using Tapatalk
nickporwal said:
Changelog?
Click to expand...
Click to collapse
https://source.android.com/security/bulletin/pixel/2018-12-01.html
One of this days the 'Check for Update' button will work damn it! Hahahaha
Hahaha right, I have been flashing the OTA manually, its no biggie for me I am used to manually flashing the ota now
AntLyoN2053 said:
One of this days the 'Check for Update' button will work damn it! Hahahaha
Click to expand...
Click to collapse
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
AntLyoN2053 said:
One of this days the 'Check for Update' button will work damn it! Hahahaha
Click to expand...
Click to collapse
I got it through ota 1 hour ago.
gm007 said:
I got it through ota 1 hour ago.
Click to expand...
Click to collapse
You know Im mashing the button, lol. Only google phone that got all the updates pretty much same day was the Nexus 6P, I used to get the update notification even before any site would announce that it was out
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
I've rooted with 17.3 without a problem. Are you just booting into twrp, not flashing it?
Sent from my [device_name] using XDA-Developers Legacy app
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
Do you have the Magisk uninstaller on your phone? Run it from the temp TWRP .img, and then it should boot OK. Go back to temp TWRP, and install Magisk again. The Edge Sense Plus module is broken again. Don not reinstall it until fixed.
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
Flash all after removing the -w, rebooted and let it finish. Boot to TWRP and installed the latest canary. Did not install TWRP.
All good.
jd1639 said:
I've rooted with 17.3 without a problem. Are you just booting into twrp, not flashing it?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Ah figured it out, edge sense broken.
edit- thanks guys~
sulpher said:
Ah figured it out, edge sense broken.
Click to expand...
Click to collapse
There's no magic. I sideload the ota in the stock recovery. Booted into the system to make sure everything worked. Powered off the device and booted into the bootloader. Then booted twrp and flashed magisk. Then booted into the system. That's it.
Sent from my [device_name] using XDA-Developers Legacy app
No OTA here... It usually comes days later with unlocked Google pixel using TMobile. -.-
Installed the full version to update it, root just after and everything's fine!
There is only the edge sense that is'nt working as already told
TWRP keeps getting error 1 when flashing the OTA, bit odd
The TWRP for this device has never been able to side-load the OTA it always errors out. I just use the full firmware and take out the -w and all good.
laill said:
TWRP keeps getting error 1 when flashing the OTA, bit odd
Click to expand...
Click to collapse
Archangel said:
The TWRP for this device has never been able to side-load the OTA it always errors out. I just use the full firmware and take out the -w and all good.
Click to expand...
Click to collapse
So then how do we flash the OTA and keep root? Pardon my ignorance on the matter but taking out the -w, do you mean through terminal on the device or flashing with adb or something? Just need a little more detail.
I am used to putting the OTA on the device and flashing through TWRP then flashing TWRP&Magisk again before a full restart.
Once again I am new to this style of flashing so sorry for asking a dumb question.
What I do is download the full updated firmware, unzip that in your platform tools folder,,,make sure you also unzip the second zip inside there as well. If you have the Pixel edge module installed uninstall it and I also uninstalled Magisk in TWRP before I updated just in case there were any problems. Then find the flash-all.bat file in your platform tools folder, right click on it, open with notepad+ and find the -w at the bottom and delete it. After this, save the flash-all.bat notepad xml file and do not just close it. You can then flash the full firmware without it deleting your user data. After this you will have to fastboot boot TWRP and flash the TWRP zip over again. I rebooted then used TWRP to flash the Magisk 17.1 zip. I am up and running and did the same thing last month for the Nov update,,,hope this helps.
Rumsfield said:
So then how do we flash the OTA and keep root? Pardon my ignorance on the matter but taking out the -w, do you mean through terminal on the device or flashing with adb or something? Just need a little more detail.
I am used to putting the OTA on the device and flashing through TWRP then flashing TWRP&Magisk again before a full restart.
Once again I am new to this style of flashing so sorry for asking a dumb question.
Click to expand...
Click to collapse

Question Magisk

Hi friends. Bought my one on *site name*. China version. How to install Magisk root? I tried to boot patched boot.img... didn't help
have you unlock your phone?
AmbazidA said:
have you unlock your phone?
Click to expand...
Click to collapse
Yea
Rezinochka said:
Yea
Click to expand...
Click to collapse
okay, was the flashing of patch boot image not successful? or what error did you find?
AmbazidA said:
okay, was the flashing of patch boot image not successful? or what error did you find?
Click to expand...
Click to collapse
In adb it wrote "OKAY". But in magisk root haven't installed.
may be you can try this; launch magisk app already installed in the phone and select direct install(recommended), wait for the process to complete and reboot. it might help
If for some reason it’s not already installed, install it.
AmbazidA said:
may be you can try this; launch magisk app already installed in the phone and select direct install(recommended), wait for the process to complete and reboot. it might help
Click to expand...
Click to collapse
Sorry, didn't understand wdym
Sirs. With your permission, we will continue tomorrow morning. I am forced to leave you for an indefinite period for the time being.
Ok. Good morning "Vietnam"
AmbazidA said:
may be you can try this; launch magisk app already installed in the phone and select direct install(recommended), wait for the process to complete and reboot. it might help
Click to expand...
Click to collapse
I didn't understand wdym
Is the magisk app currently on your device?
If so, enter it, and clcik on the install button. Then click on”direct install”
Arealhooman said:
Is the magisk app currently on your device?
Click to expand...
Click to collapse
Yes
Arealhooman said:
If so, enter it, and clcik on the install button. Then click on”direct install”
Click to expand...
Click to collapse
I patched boot.img earlier
this video will walk you through rooting the Redmi Note 12
-
Enddo said:
this video will walk you through rooting the Redmi Note 12
-
Click to expand...
Click to collapse
Thx, i will try
Enddo said:
this video will walk you through rooting the Redmi Note 12
-
Click to expand...
Click to collapse
i tried with different versions of rom and magisk. So it doesnt work. And in video he flash patched file to the boot_a. I can flash it only to boot_b
Rezinochka said:
i tried with different versions of rom and magisk. So it doesnt work. And in video he flash patched file to the boot_a. I can flash it only to boot_b
Click to expand...
Click to collapse
it will flash to whatever your current partition is set to. some will be set to the _a partition and others will be set to the _b partition. it all depends on how many OTA updates you have installed (or if you've manually switched partitions for some reason)
the video does work, my Redmi Note 12 is rooted right now
IDK if it will work or not. But at least you could try. Someone suggested to patch init_boot.img on the Redmi note 12 4g forum.
Actual Post

Categories

Resources