Related
Anyone has the latest(released Feb 16th) oreo OTA full stock firmware from T-Mobile?
I tried pulling it from a logcat. Was going to fastboot flash it since I can't install it while rooted. Every url I found in the logcat gave me a 405 error though.
I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.
droidgreg said:
I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.
Click to expand...
Click to collapse
Pulling the log through ADB will yield the OTA download link. That's how @joemossjr and I grabbed the Oreo update from nougat for TMO and Sprint.
Uzephi said:
Pulling the log through ADB will yield the OTA download link. That's how @joemossjr and I grabbed the Oreo update from nougat for TMO and Sprint.
Click to expand...
Click to collapse
Step by step instructions would be appreciated.
droidgreg said:
Step by step instructions would be appreciated.
Click to expand...
Click to collapse
It's hard to explain. You have to capture the moment the phone grabs the OTA file from Motorola's update website.
Enable developer options
Enable ADB
Plug phone up to a PC that has updated ADB binaries
Open terminal/command prompt
Adb shell
Logcat
After you do that your terminal of choice will start spitting out the log.
Run the system updater.
Download the OTA. At that moment, one of the logs should give you a VERY long URL. That's the download link you're looking for.
Copy and paste into your browser. You should be auto downloading it.
Done
Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!
joesee said:
Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!
Click to expand...
Click to collapse
I used titanium backup to freeze the update service as it's named in the notification.
charlatan01 said:
I used titanium backup to freeze the update service as it's named in the notification.
Click to expand...
Click to collapse
Thank you. I looked under U for update. I should have searched... It's actually called Motorola Update Services.
joesee said:
Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!
Click to expand...
Click to collapse
You won't be able to update through OTA if you're rooted
https://we.tl/B4j816Z2n8
Here's the link to the TMO OCX27.1 OTA firmware if anyone needs it.
Hi, I am wondering, if I am on ocx 27 do you guys think the 27.1 ota will install in adb sideload as it won't install in ota and I am not rooted. Also, is there a way to extract the bin in the ota?
droidgreg said:
I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.
Click to expand...
Click to collapse
Did you get your second Z2 rooted and if so did you use magisk v16? I just got a Z2 today that is on the December 1, 2017 security patch, OCX27.1, Android 8.00 and I'd like to root but hesitant. I have already unlocked the bootloader, placed magisk and twrp-3.2.1-1-nash zip(s) in internal storage, and know how to fastboot boot into recovery, I just don't want to brick my new phone. Any help with step by step instructions once I'm in TWRP to flash magisk is greatly appreciated! Do I need to do any of the following: Keep system read only or allow modifications before flashing magisk? wipe data/factory reset, mount storage, wipe cache and dalvik after flashing? Thanks in advance!
climbhigh77 said:
Did you get your second Z2 rooted and if so did you use magisk v16? I just got a Z2 today that is on the December 1, 2017 security patch, OCX27.1, Android 8.00 and I'd like to root but hesitant. I have already unlocked the bootloader, placed magisk and twrp-3.2.1-1-nash zip(s) in internal storage, and know how to fastboot boot into recovery, I just don't want to brick my new phone. Any help with step by step instructions once I'm in TWRP to flash magisk is greatly appreciated! Do I need to do any of the following: Keep system read only or allow modifications before flashing magisk? wipe data/factory reset, mount storage, wipe cache and dalvik after flashing? Thanks in advance!
Click to expand...
Click to collapse
All you need to do is grab the latest twrp img and zip file from twrp. Should be version 3.2.1-1
Then fastboot boot the img file, then once in twrp you want to flash the zip file, then when that is done reboot back into recovery
Then simply flash Magisk and reboot. Done.
How should I properly Flash Stock Firmware?
New to Moto phones and wondering what the correct method is for reverting to stock? I downloaded the 27.1 Oreo zip from this thread, do I flash it in twrp or should I flash it in adb from the bootloader? I get the following error message in twrp whenever I wipe dalvik/cache, try to install a zip, or do a backup which always says fail. I need a fresh install and re root, etc. Thank you!!
climbhigh77 said:
New to Moto phones and wondering what the correct method is for reverting to stock? I downloaded the 27.1 Oreo zip from this thread, do I flash it in twrp or should I flash it in adb from the bootloader? I get the following error message in twrp whenever I wipe dalvik/cache, try to install a zip, or do a backup which always says fail. I need a fresh install and re root, etc. Thank you!!
Click to expand...
Click to collapse
you can not flash with twrp. open the zip and see if there is a "flash-all.bat" file as well as adb and fastboot files. if not then pull them from one of the other flashall zips and add them to 27.1 zip. boot your phone to the bootloader, connect usb cable to your device and pc, then run the .bat file.
mattlowry said:
you can not flash with twrp. open the zip and see if there is a "flash-all.bat" file as well as adb and fastboot files. if not then pull them from one of the other flashall zips and add them to 27.1 zip. boot your phone to the bootloader, connect usb cable to your device and pc, then run the .bat file.
Click to expand...
Click to collapse
Factory reset gets the same error message shown in the attached photo. Thanks for the info, unfortunately I'm still a bit confused. Is this the only method to return to stock? I've searched but I'm not finding much and this method is completely new to me. In the past I've used Odin and LG up with my other devices, this is my first motorola. If I wipe internal storage in twrp will that erase the OS and need a new install? I am thinking that may clear up my issues but nervous that the phone won't boot up after that. Thanks and my apologies for my noob questions.
climbhigh77 said:
Factory reset gets the same error message shown in the attached photo. Thanks for the info, unfortunately I'm still a bit confused. Is this the only method to return to stock? I've searched but I'm not finding much and this method is completely new to me. In the past I've used Odin and LG up with my other devices, this is my first motorola. If I wipe internal storage in twrp will that erase the OS and need a new install? I am thinking that may clear up my issues but nervous that the phone won't boot up after that. Thanks and my apologies for my noob questions.
Click to expand...
Click to collapse
unfortunately other than manually fastbooting each img file to your phone this is the only way. check out this https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859
BROKEN
droidgreg said:
https://we.tl/B4j816Z2n8
Here's the link to the TMO OCX27.1 OTA firmware if anyone needs it.
Click to expand...
Click to collapse
Please upload again. Thx
sd_N said:
Please upload again. Thx
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=673956719939833411
Here's the official 27.1 firmware. The flashfile.xml has the correct order and commands to flash in fastboot, or search xda for the converter to a flashall.bat.
Sent from my Moto Z (2) using XDA Labs
I got update from oero to pie via OTA today,
I tried many patched boot.img and root maunally by patching stock img but its stuck on boot screen.. Any idea??
Download the OTA, extract the images from the payload, flash the stock boot.img in both slots. After your phone boots you can download the latest magisk manager, use it to patch the stock boot.img that you already downloaded and use it to root your device.
Hakkinan said:
Download the OTA, extract the images from the payload, flash the stock boot.img in both slots. After your phone boots you can download the latest magisk manager, use it to patch the stock boot.img that you already downloaded and use it to root your device.
Click to expand...
Click to collapse
What's mean " in both slots " ?
I tried to patch boot.img maunally but my device stuck on boot animations, So I flashed back stock boot.img into fastboot without root agian..
This is an A/B device which means that it has two slots for every partition (A and B). You need to flash the stock boot in the same partirion that it currently being used, flashing It in both is just to be safe in future updates.
Oh hey try this one: https://drive.google.com/file/d/1dBX2dZV_wWgSip8d9lk0lrO_JHfxGdKU/view?usp=sharing
Sorry if this has been asked before, but I didn't find it anywhere on this forum. I am also stuck on a bootloop after installing Pie update. I had Magisk installed and I've uninstalled it - didn't reboot. After, I've applied the Pie update. Didn't reboot. Went back to Magisk app and then did install - install to inactive slot. After that have a "nice" bootloop. How can I get the unpatched boot.img? Thanks in advance.
FRibeiro1400 said:
Sorry if this has been asked before, but I didn't find it anywhere on this forum. I am also stuck on a bootloop after installing Pie update. I had Magisk installed and I've uninstalled it - didn't reboot. After, I've applied the Pie update. Didn't reboot. Went back to Magisk app and then did install - install to inactive slot. After that have a "nice" bootloop. How can I get the unpatched boot.img? Thanks in advance.
Click to expand...
Click to collapse
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Hakkinan said:
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Click to expand...
Click to collapse
Thank you so much! I am going to try it later, hopefully I can get my phone back fully working. If it's not asking too much, what are the commands I have to type to install it on both slots?
FRibeiro1400 said:
Thank you so much! I am going to try it later, hopefully I can get my phone back fully working. If it's not asking too much, what are the commands I have to type to install it on both slots?
Click to expand...
Click to collapse
"fastboot flash boot_a boot.img" and "fastboot flash boot_b boot.img"
Hakkinan said:
"fastboot flash boot_a boot.img" and "fastboot flash boot_b boot.img"
Click to expand...
Click to collapse
Stuck on boot agian..
I tried flash OTA manual by fastboot & flash patched stuck too!
I think I need reset to root?
*NOTICE: I installed Xposed framwork on oreo, May that's problem?
HaN5aR said:
Stuck on boot agian..
I tried flash OTA manual by fastboot & flash patched stuck too!
I think I need reset to root?
*NOTICE: I installed Xposed framwork on oreo, May that's problem?
Click to expand...
Click to collapse
Wait, did you try to flash the whole OTA?
Hakkinan said:
Wait, did you try to flash the whole OTA?
Click to expand...
Click to collapse
At first I updated from oreo to pie via OTA without any VPN
I failed to root it so, I tried flash it again from HERE but facing the same problem with root it stuck on bootanimations
Hakkinan said:
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Click to expand...
Click to collapse
Unfortunatelly, it seems the link for the OTA zip was removed, so, phone will stay bricked thanks to the lack of instructions of how to update to Pie when Magisk is installed. Why do they remove the links?
HaN5aR said:
At first I updated from oreo to pie via OTA without any VPN
I failed to root it so, I tried flash it again from HERE but facing the same problem with root it stuck on bootanimations
Click to expand...
Click to collapse
Ok, now i understand what is happening. It bootloops as soon as you reboot after installing magisk right? If so, then i need to know what you are doing to install magisk.
FRibeiro1400 said:
Unfortunatelly, it seems the link for the OTA zip was removed, so, phone will stay bricked thanks to the lack of instructions of how to update to Pie when Magisk is installed. Why do they remove the links?
Click to expand...
Click to collapse
First the server is down, nobody removed the file, you just need to wait for it to go up again. Second, you can easily revert your phone back to 10.0.1.0 and stay there, your phone isn't bricked and it doesn't have to stay in this current state.
Hakkinan said:
Ok, now i understand what is happening. It bootloops as soon as you reboot after installing magisk right? If so, then i need to know what you are doing to install magisk.
First the server is down, nobody removed the file, you just need to wait for it to go up again. Second, you can easily revert your phone back to 10.0.1.0 and stay there, your phone isn't bricked and it doesn't have to stay in this current state.
Click to expand...
Click to collapse
I never had 10.01.0 installed. I was on Oreo and got the update this morning. I've followed the rule for OTA with Magisk and it was the wrong thing to do. If, at least, there was a warning to NOT follow the instructions, all would be sorted. Maybe I can find a link somewhere with this update, as I don't want to lose my data. On Xiaomi official site, the last rom available is version V9.6.11.0.ODLMIFF. Unless I install this one back.
FRibeiro1400 said:
I never had 10.01.0 installed. I was on Oreo and got the update this morning. I've followed the rule for OTA with Magisk and it was the wrong thing to do. If, at least, there was a warning to NOT follow the instructions, all would be sorted. Maybe I can find a link somewhere with this update, as I don't want to lose my data. On Xiaomi official site, the last rom available is version V9.6.11.0.ODLMIFF. Unless I install this one back.
Click to expand...
Click to collapse
Doesn't matter if you had 10.0.1.0 previously or not. You can download it and install it without losing data.
so i updated to OOS 10.0.9 Global on HD1900(China), but there is no patched boot or fastboot rom yet, so i patched it with his guide: guide by @gpz110
Boot.img patched with MAGISK 20.4 on OOS 10.0.9 HD65AA (GLOBAL)
Only for OOS 10.0.9 Global!!!!
Enjoy!
Instructions:
reboot to fastboot
Code:
adb reboot bootloader
Code:
fastboot boot magisk_patched_10_0_9.img
let it boot and check if u have root
if u got root then reboot to fastboot again
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched_10_0_9.img
patched boot.img download: https://drive.google.com/file/d/1mHbDV0t_TKrhV2XqT7YySoHsl8623Bc4/view?usp=sharing
stock boot.img download: https://drive.google.com/file/d/1RzUHNfp0Zns2FrfOHA9mwoDW9BKKeZVH/view?usp=sharing
My model is an HD 1905 but my current build number is 10.0.9 HD65AA... I bought it directly from OnePlus it's a 7T. Is this the boot image I need? I spent hours looking all over in different boot images patched with magisk. I haven't even unlocked my bootloader yet because I'm not sure what my options are... Lol also I noticed you have the patched boot image and a stock boot image I said just in case something goes wrong?
Sent from my OnePlus7T using XDA Labs
groovemetal81 said:
My model is an HD 1905 but my current build number is 10.0.9 HD65AA... I bought it directly from OnePlus it's a 7T. Is this the boot image I need? I spent hours looking all over in different boot images patched with magisk. I haven't even unlocked my bootloader yet because I'm not sure what my options are... Lol also I noticed you have the patched boot image and a stock boot image I said just in case something goes wrong?
Sent from my OnePlus7T using XDA Labs
Click to expand...
Click to collapse
it should work, but first u need an unlocked bootloader...
u can test it as described with the first and second step("fastboot boot" command only boot once, if u get bootloop, just restart and your device will boot as usual) , if it boot and u got root with no problems, then u can finish the process with the third and fourth step
boot image patched for EU version is possible 10.0.9.HD65BA ?
Yeah I just upgraded from a 6t and that was capable of a custom recovery but I'd run into trouble all the time because of the dual partition.. so that patched boot image with magisk all's I need is the APK file 7.51 correct I shouldn't need the magisk 24 .0zip
Sent from my OnePlus7T using XDA Labs
EmiRap said:
boot image patched for EU version is possible 10.0.9.HD65BA ?
Click to expand...
Click to collapse
check my tool here
Thx Thx Thx it worked properly
Thanks. Worked like a charm. The only thing is that I cannot find Advanced option and SafetyNet check is missing in Magisk Manager like I had previously in my OP6T. Also, with this root Google Pay and the likes work, as I also do not see Magisk Hide, but did enalbe in Settings. Thumbs up.
Update: Seems like WiFi is not working now! Any tips?
EazyVG said:
Thanks. Worked like a charm. The only thing is that I cannot find Advanced option and SafetyNet check is missing in Magisk Manager like I had previously in my OP6T. Also, with this root Google Pay and the likes work, as I also do not see Magisk Hide, but did enalbe in Settings. Thumbs up.
Update: Seems like WiFi is not working now! Any tips?
Click to expand...
Click to collapse
Are you sure, that you are on OOS 10.0.9 Global?
To revert back to stock boot image, grab the boot image from a fastboot rom here
be sure to grab the right one!
Definitely it is 10.0.9 HD65AA (GLOBAL) which I got over OTA. But I'll download the one from link again and update locally and then again re-run the steps for root.
Update: Reinstalled 10.0.0.9 and the steps ... all working, no above mentioned issues now. Thanks!
I did the whole steps but the phone application continues to stop and then the data network does not work What is the problem I have updated wirelessly to 1009
AboNaya said:
I did the whole steps but the phone application continues to stop and then the data network does not work What is the problem I have updated wirelessly to 1009
Click to expand...
Click to collapse
Did you already flashed or just booted the image?
HD1905BA Europe Patched boot
10.0.9 HD1905BA (Europe)
Stock boot : drive.google.com /file/d/1yyfzh6HbjrdZG3WDeyTv1d04fBgX3yzl/view?usp=sharing[/url]
Patched boot: drive.google.com /file/d/1ZCX7CWpRX-sZrb_ICOg64q2Abdumynmf/view?usp=sharing
guys!
Just a quick question: does this method pass the safetyNet check?
KyoshiDev said:
Did you already flashed or just booted the image?
Click to expand...
Click to collapse
I think I'll second his problem. I did first couple steps, confirmed root, everything seemed ok. Reboot and performed remaining steps. Now I have major stability problems. System UI eventually FCs then phone restarts. I'm able to get to settings and check version, still shows OOS 10.0.8 HD65AA. The signal bars showed no bars but LTE+ logo. Running another app called Signal Check Pro I confirmed that I had data. It seemed to get more stable the more it booted. The updater still wants to do a full update and wipe, it detects root and says that doing the full upgrade will lose root. I'm probably going to let mine do the full update and then reroot.
How did you patch the image? I get a non working patched boot.img when using the latest version of Magisk Manager.
AboNaya said:
I did the whole steps but the phone application continues to stop and then the data network does not work What is the problem I have updated wirelessly to 1009
Click to expand...
Click to collapse
im having a similar problem, after full ota update (2.6gb) from rooted 10.0.8 im losing mobile network (two SIM icon, greyed out, with a slash sign over it and no baseband infromation) after booting/flashing this boot, even creating mine. Mobile network restores after returning to stock. any clue? Im on 10.0.9.HD65AA
Sacob said:
guys!
Just a quick question: does this method pass the safetyNet check?
Click to expand...
Click to collapse
Yes
Nice Work with that .bat file
It works on Oneplus 7t 10.0.9Hd65BA. EU
Thanks for that super cool tool
To others that need to root a Oneplus 7t 10.0.9Hd65BA. EU i share my magisk boot file whit you all
#drive.google.com/open?id=1vGlNWrw2JAXmtb2ibst2BEQhKCM5ceMl #
Download the file an follow the guide in #1
Hi, I've just received my OP7t Global HD1900.
I installed OTA 10.0.9 and already unlocked the bootloader.
Please, does TWRP recovery work on this phone with 10.0.9? If not, which recovery should I use?
Do I have to flash a patched boot.img to get the phone rooted?
I used the boot image and it rooted my phone..great and many thanks!
Now...which recovery should I flash?
Thanks..
Hi,
I use a RMX2063 since last month, rooted with the TWRP method I found in this forum since day 0. I tried to install the lastest OTA update, that was released last week (RMX2063 _11_A.22), but I have issues to keep magisk working.
Either I do a clean install or a dirty flash, I enter into a bootloop every time I flash lastest magisk version (20.4). Otherwise, the phone works OK if I reflash the OTA and use it without rooting.
Any solutions to that, so I don´t have to downgrade the phone?
Jpigas said:
Hi,
I use a RMX2063 since last month, rooted with the TWRP method I found in this forum since day 0. I tried to install the lastest OTA update, that was released last week (RMX2063 _11_A.22), but I have issues to keep magisk working.
Either I do a clean install or a dirty flash, I enter into a bootloop every time I flash lastest magisk version (20.4). Otherwise, the phone works OK if I reflash the OTA and use it without rooting.
Any solutions to that, so I don´t have to downgrade the phone?
Click to expand...
Click to collapse
It doesn't work. In order for me to get root afterwards is to flash the latest for rmx2061, extract the boot.img, modify it with magisk and flash the modified boot.img afterwards
mepadiernos said:
It doesn't work. In order for me to get root afterwards is to flash the latest for rmx2061, extract the boot.img, modify it with magisk and flash the modified boot.img afterwards
Click to expand...
Click to collapse
First of all, thx for the quick response.
I think I already tried that, you mean flashing the modified boot.img via TWRP? (install -> install image -> "boot")?
After that I had another bootloop ("system image is destroyed" realme message)
Jpigas said:
First of all, thx for the quick response.
I think I already tried that, you mean flashing the modified boot.img via TWRP? (install -> install image -> "boot")?
After that I had another bootloop ("system image is destroyed" realme message)
Click to expand...
Click to collapse
I was actually referring to flashing via fastboot.
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
mepadiernos said:
I was actually referring to flashing via fastboot.
Click to expand...
Click to collapse
The phone enters bootloop anyway (system destroyed), but thank you anyway @mepadiernos. Any other idea?
Jpigas said:
The phone enters bootloop anyway (system destroyed), but thank you anyway @mepadiernos. Any other idea?
Click to expand...
Click to collapse
Hmmm, I do remember that the twrp provided here for the Realme 6 Pro breaks encryption after I upgraded to .27 so I had to flash the .20 for rmx2061 via stock recovery. I had to put the ozip in the microsd. I believe that will factory reset the phone. When it does I went through the process of setting up my phone sans root. I installed magisk manager and proceeded to patch the extracted boot image from the ozip, the update for the rmx2061, and flashing via fastboot. So, I have root but no twrp.
mepadiernos said:
Hmmm, I do remember that the twrp provided here for the Realme 6 Pro breaks encryption after I upgraded to .27 so I had to flash the .20 for rmx2061 via stock recovery. I had to put the ozip in the microsd. I believe that will factory reset the phone. When it does I went through the process of setting up my phone sans root. I installed magisk manager and proceeded to patch the extracted boot image from the ozip, the update for the rmx2061, and flashing via fastboot. So, I have root but no twrp.
Click to expand...
Click to collapse
It doesn´t worked for me, buy, anyway, I´m planning to downgrade due to the very high power consumption. Nowadays the phone struggles to reach 3-4h screen on, versus the 6h I managed to reach on previous version. What do you guys think about it?
I have been digging through these forums, but can't find an straight step-by-step guide explaining how you go about manually updating the firmware on this device when you have the bootloader unlocked, TWRP installed, and rooted with Magisk.
I know that having the bootloader unlocked means that the device can no longer get updates automatically and that the updates have to be manually downloaded installed from the ASUS website. But what I don't understand is how to install the firmware from the ASUS website and still keep TWRP recovery and Magisk root.
This is my first time updating the device after I first set it up in January, so I would very much appreciate it if some one knowledgeable could explain this process to me
(In case you need to know, I'm currently on WW-32.2810.2212.241 firmware, with TWRP 3.70_12-0 and Magisk 25.2 installed.)
jmaeshawn said:
I have been digging through these forums, but can't find an straight step-by-step guide explaining how you go about manually updating the firmware on this device when you have the bootloader unlocked, TWRP installed, and rooted with Magisk.
I know that having the bootloader unlocked means that the device can no longer get updates automatically and that the updates have to be manually downloaded installed from the ASUS website. But what I don't understand is how to install the firmware from the ASUS website and still keep TWRP recovery and Magisk root.
This is my first time updating the device after I first set it up in January, so I would very much appreciate it if some one knowledgeable could explain this process to me
(In case you need to know, I'm currently on WW-32.2810.2212.241 firmware, with TWRP 3.70_12-0 and Magisk 25.2 installed.)
Click to expand...
Click to collapse
Hi Bro.
Your ROG Phone was CN and did you flash the RAW WW firmware?.
Regards!.
jmaeshawn said:
I have been digging through these forums, but can't find an straight step-by-step guide explaining how you go about manually updating the firmware on this device when you have the bootloader unlocked, TWRP installed, and rooted with Magisk.
I know that having the bootloader unlocked means that the device can no longer get updates automatically and that the updates have to be manually downloaded installed from the ASUS website. But what I don't understand is how to install the firmware from the ASUS website and still keep TWRP recovery and Magisk root.
This is my first time updating the device after I first set it up in January, so I would very much appreciate it if some one knowledgeable could explain this process to me
(In case you need to know, I'm currently on WW-32.2810.2212.241 firmware, with TWRP 3.70_12-0 and Magisk 25.2 installed.)
Click to expand...
Click to collapse
I think twrp will not work properly with android 13 because twrp is made for android 12
Dumper UL full upgrade and you will get Boot.img and recovery.img (keep both files at safe place).
Use magisk manager to patch the boot file.
Keep recovery.img (original A13) and TWRP.img safe in ADB root folder (dont mix them up).
1. Update FOTA to Android 13 by copy UL full upgrade into root folder of your phone. If copy from PC/laptop with cable then unplug the cable, your phone will recognize the package, (if you already change COUNTRY CODE and currently use WW 241 rom that will be success update). Otherwise, reboot your device and pop up will appear. Wait the phone is fully reboot and set up everything.
2. Reboot your phone into download mode/fastboot mode (it's better that you should enable USB debug/Developer mode before doing anything). Using CMD command to flash patched boot from Magisk Manager. And reboot, now your phone could gain back root.
3. Check again if the recovery is gone or not. If it's gone, then use termux or any terminal emulator for the "dd command".
You will gain back the TWRP, if any failed, flash back original recovery.img that you have lately in ADB folder on your PC.
PS: backup everything, since going back from Android 13 to Android 12 need to full factory reset.
Br,
ChrisFeiveel84 said:
I think twrp will not work properly with android 13 because twrp is made for android 12
Click to expand...
Click to collapse
I'm on WW-33.0610.2810.81, and TWRP seems to be working OK so far