Related
Hi,
Problem starting oneplus 3, let me explain.
1) purchased oneplus3, 4 months ago.
2) Rooted,updated oxygen 3.2.8 with TWRP recovery3021 and super SU 2.74-2
3) updated oxygen4.00 with twrp32128 and super SU 2.79SR2 everything was fine.
4) Received OTA update through VPN for oxygen 4.0.1 (30mb), installed but unable start instead it was always going into twrp mode.
5) i changed twrp recovery back to 3021 and install stock oxygen 3.2.8,was working fine.
6) Now i wanted to UNROOT the device and back to stock so that i can get OTA Oxygen 4 and 4.0.1.
7) i followed steps below,
a) downloaded oxygen 3.2.1 and stock recovery.img
a) fastbootloader, and connect device.
b) fastboot devices
c) fastboot fastboot flash recovery recovery.img
d) fastboot oem lock - when i used this command and accept YES, screen got black and no further instruction for ADBsideload.
8) i used to restart the device in recovery but black screen, fastboot loader working.
FASTBOOT MODE
PRODUCT NAME - ....
VARIANT - MTP UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - .....
SECURE BOOT - enabled
DEVICE STATE - locked
9) and if i start the device in normal it asked for screen pattern lock but my existing unlock pattern doesnt work.
10) by using all the chance for screen pattern unlock it showed DECRYPTION UNSUCCESSFULL, clicked on RESET PHONE but again screen black in recovery mode.
11) NOW if i start my device it again shows DECRYPTION UNSUCCESSFULL and asking for RESET PHONE......
What to do now.....
regards,
Zahir
use the mega unbrick guide method 2, always work
Don't panic mate!
mirko8054 said:
use the mega unbrick guide method 2, always work
Click to expand...
Click to collapse
Thanks mirko8054, I will let you know soon......
mirko8054 said:
use the mega unbrick guide method 2, always work
Click to expand...
Click to collapse
thanks a lot mirko8054, my oneplus 3 live again, using mega unbrick guide method 2.
appreciated.
at present oxygen3.1.2
how to install latest OTA since it is not showing any update by SYSTEM UPDATES.
my oem lock. I don't know if twrp installed.
how can I check if still my device is rooted.
I don't want to root it, just need OTA update directly.
kindly let me know the steps to update the device by oxygen4.
Many thanks
Zahir
samadayesha said:
thanks a lot mirko8054, my oneplus 3 live again, using mega unbrick guide method 2.
appreciated.
at present oxygen3.1.2
how to install latest OTA since it is not showing any update by SYSTEM UPDATES.
my oem lock. I don't know if twrp installed.
how can I check if still my device is rooted.
I don't want to root it, just need OTA update directly.
kindly let me know the steps to update the device by oxygen4.
Many thanks
Zahir
Click to expand...
Click to collapse
Device is back to stock, this method is used by One plus asstance for unbrick hard bricked device by remote control your PC. Then device is back to completly stock. No root no custom recovery etc. You Can now use OTA for update or using adb sideload or manually flash the entire ROM from sdcard. Thank you for appreciate :good:
mirko8054 said:
Device is back to stock, this method is used by One plus asstance for unbrick hard bricked device by remote control your PC. Then device is back to completly stock. No root no custom recovery etc. You Can now use OTA for update or using adb sideload or manually flash the entire ROM from sdcard. Thank you for appreciate :good:
Click to expand...
Click to collapse
thanks a lot, I will do accordingly.
samadayesha said:
thanks a lot mirko8054, my oneplus 3 live again, using mega unbrick guide method 2.
appreciated.
at present oxygen3.1.2
how to install latest OTA since it is not showing any update by SYSTEM UPDATES.
my oem lock. I don't know if twrp installed.
how can I check if still my device is rooted.
I don't want to root it, just need OTA update directly.
kindly let me know the steps to update the device by oxygen4.
Many thanks
Zahir
Click to expand...
Click to collapse
just wanted to highlight the things you did that caused the issue
1- flashing the stock rom through twrp, it's possible specially with the latest TWR0-11 but not advisable, you better always flash stock recovery and then sideload rom (full rom not update) and then fast boot TWRP back and reflash root... any other method always causes issues...
2- the 30mg updates do not work on a rooted device
3- unrooting without immediately sideloading rom will always cause the black screen and loop to recovery, it's not required to unroot unless you want to go back to full stock experience...
4- this the biggest problem you made, you relocked the devices bootloader, you also did it while the device has a lot of issues (some mentioned above) so the device bricked instantly, if you are planning on unlocking the device again ...NEVER NEVER relock the device again , there's no need to do that , all you need to do to go back to a full stock experience is to wipe everything in TWRP , flash stock recovery then wipe everything again from there, then sideload full rom (latest stable version) , then for good majors in the new rom recovery wipe everything agian and boot to system and from system do a factory reset. then recharge your device to 100% and re encrypt it if it's not...after that you're 100% on a full stock exerience and will receive ota and it'll work... and at that state only (without root or TWRP) you can relock the bootloader (which is gain not necessary at all, there's no benefit to it)
Hi,
I have question. All my devices (present and also all previous) I have rooted, unlock bootloader, have custom recovery and so on.... and I flash always some custom ROM. And now I have idea, that I want to used as daily driver customized Stock ROM. I know it's nothing new, but I want to keep:
- custom recovery
- unlock bootloader
- root
- busybox
I know, that it is very easy. But - and now my question (it is what I don't know) - when comes some monthly update, how can I do update to latest Stock ROM (downloaded from Google Factory Image) without lost of unlock bootloader, root without losing data and so on.....
How can I update Stock ROOTed ROM with keep all data and settings?
I can imagine, that I flash only system.img which I root after that or something like this. Maybe is this beginners question, but I want to try it and I'm not sure how to....
Can somebody describe this procedure step by step (first flash and each update).
Thank you in advance
Just extract the zip you download from Google Factory Images and flash system, vendor and boot via fastboot.
https://elementalx.org/how-to-install-android-monthly-security-updates/
....EDIT....
Everything seem to be fine. My previous problem was that I tried to flash wrong version of SuperSU....
hello
i am new to this forums and my phone
is unlocking bootloader is same after anti rollback update in V9.1.6.0
i want to root my device for titanium backup and use miui for now
i watch video relating anti roll back update but still confused as how i am gonna to install custom rom in future
and rollback to miui without bricking my device
Thanks
Regards
I know, its confusing to many. You can start by checking these threads:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/faq-questions-answered-t3816185
https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
I am on 9.5.19, unlocked, rooted, TWRP installed and have received update notice for 9.6.3.0, but do not want to update via OTA because will lose root, recovery (and maybe unlock?)
I believe after rooting, unlocking, and TWRP install, you need to download a version of the MIUI ROM you want without the included firmware. see here:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-redmi-note-5-pro-miui-roms-t3816343
They dont have 9.6.3 listed so need to ask about that. Also not sure which version of ARB your phone has so you need to ask in above threads or if you have ADB installed can enter fastboot command: fastboot getvar anti
I've updated to 9.6.3 and don't see any relevant change in daily use. The bootloader is still unlocked but I've lost the changes in build prop for gcam installation. I was unrooted with no twrp (or rwrp) recovery installed
Here is firmware-less 9.6.3 version download: https://mirror.akhilnarang.me/MIUI/Global/Stable/
Taken from this post in the fw-less ROMs thread: https://forum.xda-developers.com/showpost.php?p=77390404&postcount=266
taco9 said:
I know, its confusing to many. You can start by checking these threads:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/faq-questions-answered-t3816185
https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
I am on 9.5.19, unlocked, rooted, TWRP installed and have received update notice for 9.6.3.0, but do not want to update via OTA because will lose root, recovery (and maybe unlock?)
I believe after rooting, unlocking, and TWRP install, you need to download a version of the MIUI ROM you want without the included firmware. see here:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-redmi-note-5-pro-miui-roms-t3816343
They dont have 9.6.3 listed so need to ask about that. Also not sure which version of ARB your phone has so you need to ask in above threads or if you have ADB installed can enter fastboot command: fastboot getvar anti
Click to expand...
Click to collapse
My RN5 Pro is unlocked, with twrp, magisk (rooted), and running MIUI 9.5.19. Xiaomi gave me 9.6.3 last night, and although I wasn't able to install the delta update that they gave me (twrp didn't do anything with it), after the reboot, it downloaded the full 9.6.3 ROM. I then told it to do the update and twrp successfully installed it. At that point, I ONLY lost twrp and I assume magisk. The bootloader was unaffected by the MIUI upgrade.
Easy enough to fix - boot to fastboot, and used 'fastboot boot twrp.img' to get the phone started in twrp recovery mode. Then I was able to use twrp to install itself permanently/properly into the recovery partition, install lazyflasher, flash magisk, reboot normal. Phone's back to rooting state using magisk, but now with MIUI 9.6.3. 5 minutes and done.
taco9 said:
I know, its confusing to many. You can start by checking these threads:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/faq-questions-answered-t3816185
https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
I am on 9.5.19, unlocked, rooted, TWRP installed and have received update notice for 9.6.3.0, but do not want to update via OTA because will lose root, recovery (and maybe unlock?)
I believe after rooting, unlocking, and TWRP install, you need to download a version of the MIUI ROM you want without the included firmware. see here:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-redmi-note-5-pro-miui-roms-t3816343
They dont have 9.6.3 listed so need to ask about that. Also not sure which version of ARB your phone has so you need to ask in above threads or if you have ADB installed can enter fastboot command: fastboot getvar anti
Click to expand...
Click to collapse
ok thanks for helping
tajima69 said:
I've updated to 9.6.3 and don't see any relevant change in daily use. The bootloader is still unlocked but I've lost the changes in build prop for gcam installation. I was unrooted with no twrp (or rwrp) recovery installed
Click to expand...
Click to collapse
sorry what did you meant by build prop for gcam installation
tajima69 said:
I've updated to 9.6.3 and don't see any relevant change in daily use. The bootloader is still unlocked but I've lost the changes in build prop for gcam installation. I was unrooted with no twrp (or rwrp) recovery installed
Click to expand...
Click to collapse
No change ?? Let me listout some changes for you
1. New VoLTE icon
2. In lockscreen time and date displays in centre
3. Messaging app suggest new plan offer and etc (AI reply)
4. Updated security patch
5. Imporved Battery life
6. New Ringtone and notification sounds
Cannot boot twtp.img
After Installing update gcam was not workig so i was in fastboot and i put command fastboot boot twtp.img but it is stucked in downloading boot.img
tajima69 said:
I've updated to 9.6.3 and don't see any relevant change in daily use. The bootloader is still unlocked but I've lost the changes in build prop for gcam installation. I was unrooted with no twrp (or rwrp) recovery installed
Click to expand...
Click to collapse
Battery draining fast in this update
SunilSuni said:
No change ?? Let me listout some changes for you
1. New VoLTE icon
2. In lockscreen time and date displays in centre
3. Messaging app suggest new plan offer and etc (AI reply)
4. Updated security patch
5. Imporved Battery life
6. New Ringtone and notification sounds
Click to expand...
Click to collapse
you sayin improved battery backup??? other people complaining about battery backup getting lowers by updates ..??? sach kya hai
Sent from my Redmi Note 5 Pro using Tapatalk
I forgot how you update the phone when the new monthly security updates come out when rooted? I know when you have recovery it's easier just flash it but without that yet how do we install the latest October patch being rooted only?
Someone correct me if I'm wrong or missing something but this is my understanding:
1. Download image from Google and remove the -w from .bat file if you don't want to wipe data and run the bat to flash the update.
2. Patch new boot.img with Magisk.
3. Use fastboot to flash patched boot.img
shorto85 said:
Someone correct me if I'm wrong or missing something but this is my understanding:
1. Download image from Google and remove the -w from .bat file if you don't want to wipe data and run the bat to flash the update.
2. Patch new boot.img with Magisk.
3. Use fastboot to flash patched boot.img
Click to expand...
Click to collapse
Yep, that's about it in a nutshell :good:
shorto85 said:
Someone correct me if I'm wrong or missing something but this is my understanding:
1. Download image from Google and remove the -w from .bat file if you don't want to wipe data and run the bat to flash the update.
2. Patch new boot.img with Magisk.
3. Use fastboot to flash patched boot.img
Click to expand...
Click to collapse
You can also download the Google OTA image and then ADB sideload the zip file through Recovery. It won't wipe data either.
Will this work while rooted or do you have to uninstall magisk then use the stock recovery to side-load the OTA?
Flyer66 said:
You can also download the Google OTA image and then ADB sideload the zip file through Recovery. It won't wipe data either.
Click to expand...
Click to collapse
Just remove the - w in flash. Bat
You'd have to re root after of course.
Flyer66 said:
You can also download the Google OTA image and then ADB sideload the zip file through Recovery. It won't wipe data either.
Click to expand...
Click to collapse
can you share the steps for doing an ADB Sideload? My PC is all setup for it - but I don't know the exact commands to use...? Thannks
Geekser said:
can you share the steps for doing an ADB Sideload? My PC is all setup for it - but I don't know the exact commands to use...? Thannks
Click to expand...
Click to collapse
Download the full OTA image from Google
Boot into factory recovery
Choose Apply update from ADB
From windows
Code:
adb sideload fullOTAimage.zip
the update will take awhile
Reboot and let the update finish in android
Load magisk and patch the boot.img, copy patch_boot.img to computer
Boot into the bootloader
Flash the patched boot image with:
Code:
fastboot flash boot patch_boot.img
or
Code:
fastboot flash boot_a patch_boot.img
and
Code:
fastboot flash boot_b patch_boot.img
cursixx said:
Download the full OTA image from Google
Boot into factory recovery
Choose Apply update from ADB
From windows
Code:
adb sideload fullOTAimage.zip
the update will take awhile
Reboot and let the update finish in android
Load magisk and patch the boot.img, copy patch_boot.img to computer
Boot into the bootloader
Flash the patched boot image with:
Code:
fastboot flash boot patch_boot.img
or
Code:
fastboot flash boot_a patch_boot.img
and
Code:
fastboot flash boot_b patch_boot.img
Click to expand...
Click to collapse
Very Nice - thank you very much. Very helpful!
Archangel said:
Will this work while rooted or do you have to uninstall magisk then use the stock recovery to side-load the OTA?
Click to expand...
Click to collapse
No, it will work while you're rooted. You will lose root since the OTA sideload will rewrite your patched boot.img with the boot.img from the OTA. You'll have to reroot by first booting your phone into the new image and then using Magisk to patch the new boot.img and then fastboot flash the new patched boot.img.
Once we finally get TWRP recovery, you'll actually be able to "flash" the OTA zip via TWRP instead of having to sideload it.
---------- Post added at 01:10 PM ---------- Previous post was at 01:07 PM ----------
cursixx said:
Download the full OTA image from Google
Boot into factory recovery
Choose Apply update from ADB
From windows
Code:
adb sideload fullOTAimage.zip
the update will take awhile
Reboot and let the update finish in android
Load magisk and patch the boot.img, copy patch_boot.img to computer
Boot into the bootloader
Flash the patched boot image with:
Code:
fastboot flash boot patch_boot.img
or
Code:
fastboot flash boot_a patch_boot.img
and
Code:
fastboot flash boot_b patch_boot.img
Click to expand...
Click to collapse
Thanks! You beat me to it.
Flyer66 said:
Thanks! You beat me to it.
Click to expand...
Click to collapse
Sorry about that :good:
I did forget about extracting the updated boot.img from the matching OTA build you sideloaded. Geekser you will need to also download the updated factory image and extract the boot.img and copy it to the phone so magisk can patch it.
Wait, is everyone forgetting that Magisk has the ability to handle taking the OTA like normal and then patch the newly installed OS on the opposite A/B partition before you reboot? The process should be nearly seamless unless something changed recently.
This is what I'm referring to: Magisk OTA Updates with A/B Devices
Hopefully the link actually works now
Sent from my Pixel 3 XL using Tapatalk
WisdomWolf said:
Wait, is everyone forgetting that Magisk has the ability to handle taking the OTA like normal and then patch the newly installed OS on the opposite A/B partition before you reboot? The process should be nearly seamless unless something changed recently.
This is what I'm referring to: Magisk OTA Updates with A/B Devices
Click to expand...
Click to collapse
Link appears to be dead.
lollyjay said:
Link appears to be dead
Click to expand...
Click to collapse
See here : https://************/magisk-17-1-in...uding-ota-updates-with-a-b-partition-devices/
Interesting, it appears XDA is blocking the URL, so google: magisk introduces update
should be first link...
Also see HERE.
It looks like all of our links got mangled, but the new one I posted appears to work.
Where to find and download minor OTA updates to install them on rooted devic
[Moved to proper location, thanks for your advice].
Qui Peccavit said:
Please excuse the naive question, but how/where do you find the OTA files, i.e. the links to download them from?
Capturing the download link via the Android Debug Bridge (ADB) requires the OTA notifications to appear and the respective files to be downloaded, in order to then capture them via adb logcat > OTA.txt. Even if this did not require an unrooted device running an original manufacturer firmware (if we had this, we wouldn't need to go through all the hassle in the first place): it takes a looooong time for the logcat to create a loong file, in which searching for the download link resembles punishment for an amok shooter.
The reason why anybody would need the download links for OTA files is because they are on a custom ROM, have flashed TWRP, rooted their device or similar modifications. In that case, there are no more OTA notifications, i.e. one is not informed of what and when a bugfix or the like becomes available, and if trying to check for updates manually, the phone displays the following error message:
Failed to update software
Your phone's operating system has been modified in an unauthorised way. Try downloading ...
The first thing to note is the impertinence with which manufacturers and telephone operators seem to believe that they had any right to decide what is authorised and what not on our property. Unless somebody with deep pockets or the EU sue them over this BS, there is not much we ordinary mortals will be able to do against those oligopolists.
The burning practical question are therefore:
1.) How to get notified of minor updates, bugfixes and security patches when they become available?
2.) How and where to download them?
3.) How to install them?
The large firmware packages are no problem, those one can find at every corner of the street. The problem are the minor bugfixes, security patches and updates between major version numbers and sometimes even apps. Are there any proven methods that work reliably and that do neither require one to study electronics, programming and voodoo, nor force one to re-flash and re-root everything again from square one before every update, plus reinstalling and configuring everything thereafter?
In case the information is necessary, the phone is a SAMSUNG Galaxy Note 9 with Snapdragon SD-845 (SM-N9600), current firmware BL : N9600ZHS1CSC2, AP : N9600ZHS1CSC2, CP : N9600ZCU1CSAB, CSC : N9600OWO1CSB1
In a nutshell, are there ways to become aware of and apply all updates while keeping the device rooted, or is the procedure more convoluted and repetitive after every update than what Root is worth?
.
Click to expand...
Click to collapse
This has been covered many times. But, security patches generally drop the first Monday of every month. So if you want all the latest bug fixes, etc just wait for the first week of the month. Then download the full factory image for the month, edit out the -w in the flash all batch file you'll find in the factory image ( make sure you save the edited file). Run it. Afterwards, boot to twrp and install the magisk zip file once in twrp. That's it!
Qui Peccavit said:
In case the information is necessary, the phone is a SAMSUNG Galaxy Note 9 with Snapdragon SD-845 (SM-N9600), current firmware BL : N9600ZHS1CSC2, AP : N9600ZHS1CSC2, CP : N9600ZCU1CSAB, CSC : N9600OWO1CSB1
.
Click to expand...
Click to collapse
This is the Google Pixel forums, that's why updates and root are easy from us.
OTA's from Samsung are a whole different animal, you'll need to find your device's forum.
Doing it right once is better than doing it half-baked a hundred times
jd1639 said:
This has been covered many times. Download the full factory image for the month, edit out the -w in the flash all batch file you'll find in the factory image, save and then run it. Afterwards, boot into TWRP to install the Magisk zip file. That's it!
Click to expand...
Click to collapse
Quoting posts in their entirety is not necessary when the one you refer to is just one or two above yours, i.e. repeating the parts you are referring to is suficient.
Second, as with so many topics on this board, the question may have been covered many times, but usually in the same superficial telegram style without details or references as above ― which is the very reason why the questions are repeated in the first place. If there was a reference link to a detailed, step-by-step instruction that explains the necessary operations (where to find the tools for unpacking and later repacking, etc., etc.), people would not have to ask again, until one day somebody provides a comprehensible and complete, detailed step-by-step instruction. Such a guide does not have to be rewritten each time the question pops up, but «has already been covered» without doing so and without directing people to the relevant information is not as helpful as it could be.
It's like with rooting, patching, jailbreaking and other threads here on XDA: Some geeky nerd cannot write three structured sentences in a row or is too lazy to explain the procedure step by step, rather throwing around buzzwords and mentioning things without links so that people then have to hunt down a hundred tidbits from a hundred places, and in those threads, it's incomplete, superficial gibberish just the same. This is no exaggeration: there are threads here about doing something rather simple, but because the guy who started the thread was too lazy to invest the last three hours that were needed to patch it completely and fixing the known issues once and for all, too vain to wait with publishing until that has been done and too verbally incompetent or lazy to explain it properly, there are now 650 posts in that thread because god beware if somebody dared to tell the nerd «try to talk in proper sentences and explain it step by step». Many, many people wasting time, nerves, energy and work to figure something out over months that could be done by anybody in half an hour, if only instead of the imprecise mumbo-jumbo in the first post and three-word answers to questions, the geeks would do it right once in the beginning. This is speaking in general terms, not directed at any one person in particular.
Lastly and referring to the particular issue at hand, of course one can always go through the entire procedure from scratch, i.e. flash a stock ROM, re-root and do it all over again after the next update every month. The question was more in the spirit of «how can a rooted phone be updated without having to run through the entire obstacle course each and every month?», i.e. keeping the configuration, apps, etc., similar to the way it would be if the phone was not rooted. Flashing the new firmware is no problem, but having to do all the installing and configuring afterwards each time is something that, if it can be avoided, would be nice to avoid.
Again, this is not directed at you nor anybody else in particular, just to explain and maybe ring a bell that when questions are repeated over and over again, the previous answers cannot have been so terribly great, can they? And if they were, why not provide or link to them, instead of teasing with «has been answered already»?
Edit:
As already stated earlier above, the question has been moved to the proper location. Therefore it can/should be ignored in this thread, but taking the general considerations above into account in the future cannot hurt, can it now?
The Magisk A/B procedure does not work any more
So, I tried the procedure outlined in https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md on my Pixel 2 running stock Pie but the step of installing the OTA update failed. So it seems something changed recently. I'm no expert (I just follow instructions), so I can't say what changed.
WisdomWolf said:
Wait, is everyone forgetting that Magisk has the ability to handle taking the OTA like normal and then patch the newly installed OS on the opposite A/B partition before you reboot? The process should be nearly seamless unless something changed recently.
This is what I'm referring to: Magisk OTA Updates with A/B Devices
Hopefully the link actually works now
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
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