[NEWS] Software System Changes with realme UI 2.0 - Realme X2 Guides, News, & Discussion

With a switch to Android 11/realme UI 2.0 a number of principal changes followed. It led to some dramatic changes on how you can operate with your unlocked device. Here are some observations regarding that.
What I have found so far.
1. All former recoveries are not working anymore.
2. Downloaded update (firmware) file location is changed.
3. Update (firmware) file type and naming are changed.
4. Realme did not provide official firmware file download for RMX1991 since Android 10.
5. Firmware file have new partion images, namely uefi_sec.img and imagefv.img

Solutions I have found so far:
1. There are couple of recoveries that can work with realme UI 2.0 system but cannot open data. If you mount system partions in rw mode, you get bootloop. Both cannot handle data encryption.
2. New download file location is /data/ota_package/OTA/.otaPackage/
3. Update file does not look like ozip file anymore For latest CN version I received (F26) it is called system_vendor_19771.2.15.202112140000074004433_all (no file extension). It is real zip-file, not ozip-file.
4. Two links for F26 update file download (found in /data/data/com.oppo.ota/databases/ota.db) are this and this.

reserved

Related

Update p9 lite nougat ota "s ​​no officials

I was given a link. cronociclope Senior Member
I tested it. 100 for 100 on :cyclops:
It is necessary to return or to be emu 4. (MM).
Have the unlock code. (Bootloader).
Have downloaded the full firmware (2 files) Full-ota-mf-pv that twrp can install.
And have downloaded the firmware update, full full-ota-mf (no pv). (3 files).
pc+ winzip+ twrp (chinois), carteSD,
regard
https://www.youtube.com/watch?v=oTBvz71l4s0&t=1s
So on the pc, with winzip. Because with winrar for me it does not want to transfer large volumes. :
_ Downloaded a firmware emui 5. Full-ota-mf-pv for your device (it's a firmware in two files, which twrp for MM can install).
_______ update.zip and datafull hw-eu.zip
Uploaded emui update 5. Full-ota-mf not written pv and that does not share ota. But we want it. : (this is a firmware in three files).
________update.zip, public file and data hw-eu.zip
_ Open the update file of the pv version and delete the update.app, then open the update of the no pv version, and transfer update.app in the pv version.
Do the same thing with the datafull file hw-eu and data hw-eu.
In the public zip, there is a data folder with the product and system files.
In the zip data hw-eu, there is a data folder with the cust and version.
We can also transfer them.
In the zip data full hw-eu to data / hw_init :cyclops:
_copy your two new .zip files onto the SD card.
_start the phone in recovery twrp MM.
_ Go to wipe, advanced wipe, check all except well-sure sd card, and wipe to wipe.
_allez to install, installed both zip, it will show you two errors ignore them.
_allez to reboot, reboot system.
Hello
in the public zip, there is a data folder with the product and system files.
In the zip data hw-eu, there is a data folder with the cust and version.
We can also transfer them.
In the zip data full hw-eu to data / hw_init
regard
2017.09.20 VNS-L21C432B382 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97161/f1/full/update.zip
filelist http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97161/f1/full/filelist.xml
B383 was released on Firmware Finder.
Install the OTA one (mb version).
Johnny TDN said:
B383 was released on Firmware Finder.
Install the OTA one (mb version).
Click to expand...
Click to collapse
yes, full-ota-mf
2017.09.21 VNS-L21C432B383 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97303/f1/full/update.zip
filelist http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97303/f1/full/filelist.xml
and
your pkg install full-ota-mf-pv vns-l21c432b371
2017.03.21 VNS-L21C432B371 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v89798/f2/full/update.zip
filelist http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v89798/f2/full/filelist.xml
got an ota update b383.
failed at 32%
gg huawei
Johnny TDN said:
got an ota update b383.
failed at 32%
gg huawei
Click to expand...
Click to collapse
strange 32%
with this method, I can even install p10 lite.
can be checked, the update.app that is the good you place in the update.zip
go to wipe before installing update.zip edit this seems important.
2017.08.30 VNS-L31C432B390 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97199/f1/full/update.zip
filelist http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97199/f1/full/update.zip
If I am rooted and I have TWRP, can I install the update?
I installed update without come back in mm and without reset phone by this steps:
1)flash Hassan twrp recovery
2)download the 3 update file
3)extract update.app from update.zip and from update_full_VNS-L11_hw_eu.zip.
4)With Huawei update extractor extract the image file (system boot vendor cust version misc) from the two update.app and flash It with recovery. The product Image is not falshable, you have to extract this with ext4imageview
5)do a wipe cache and davilk and flash magisk zip to root. Install magisk manager (with the new update b391 i have some problem with supersu)
6)copy the file extract from product Image and data file extract from update_full_VNS-L11_hw_eu.zip and data_full_pubblic.zip in /data and in /product partition with solid Explorer with root permission.
Reboot
It's ok
http://oi63.tinypic.com/29cncx4.jpg
Paolo83 said:
I installed update without come back in mm and without reset phone by this steps:
1)flash Hassan twrp recovery
2)download the 3 update file
3)extract update.app from update.zip and from update_full_VNS-L11_hw_eu.zip.
4)With Huawei update extractor extract the image file (system boot vendor cust version) from the two update.app and flash It with recovery. The product Image is not falshable, you have to extract this with ext4imageview
5)do a wipe cache and davilk and flash magisk zip to root. Install magisk manager (with the new update b391 i have some problem with supersu)
6)copy the file extract from product Image and data file extract from update_full_VNS-L11_hw_eu.zip and data_full_pubblic.zip in /data and in /product partition with solid Explorer with root permission.
It's ok
Click to expand...
Click to collapse
Hello
Hello
ALSO Product.img of update.zip?
Because, he does not want, that's why, I always go to MM.
bad reading sorry,
Chisetdel31260 said:
Hello
ALSO Product?
Click to expand...
Click to collapse
We are not able ti flash product with this recovery, we can try to ask information to Hassan. The solution is to extract product.img with Android ICS JB EXT4 imagefile unpacker and copy the folder in /product with solid Explorer and root permission. It replace the file with the correct attribute. You have to use this metod to copy data folder
Paolo83 said:
We are not able ti flash product with this recovery, we can try to ask information to Hassan. The solution is to extract product.img with Android ICS JB EXT4 imagefile unpacker and copy the folder in /product with solid Explorer and root permission. It replace the file with the correct attribute. You have to use this metod to copy data folder
Click to expand...
Click to collapse
I've already asked him to hassan and he added to install twrp product image, but its not working.
I tried to copy pasted already with a file explorer, but every time, things break. (either with force close parameters, or force close camera, or boot-animation disappears and becomes android).
there is always something wrong.
Yes, we leave from MM everything is ok, clean.
You have to use solid Explorer It works!! With this procedure In five minutes I upgrade to last version
Managed to update to b382.
Seems stable and somehow, the battery is much better o^o
go
time to download, c432b390.
And to transfer everything in the b370 zip, then to go back to c432b160, I installed it correctly.
so this version is emu 5.0.1, patch September 1, version kernel 25 aug and baseband 286.
as you can see.
Updated to b382 vns-l21.
Problem : No notifications on Hangouts. I must go to my friend's chat in order to see the notification.
I have a question for @Chisetdel31260 or @Paolo83 or for whom I can answer it.
Is it still unclear if it is necessary or not the data_full public, which contains this .zip? And how can I add it without errors? Thanks to whoever can guide me :angel:
Doble_f said:
I have a question for @Chisetdel31260 or @Paolo83 or for whom I can answer it.
Is it still unclear if it is necessary or not the data_full public, which contains this .zip? And how can I add it without errors? Thanks to whoever can guide me :angel:
Click to expand...
Click to collapse
Hello
yes, I add it.
you just have to open the folder data / hw_init /
sorry,
for my bad English.
yet I do a great deal of effort.
for that google translator, does not blow up the planet.
Hi Chisetdel, I share this video, which includes the files OEMinfo.zip, Update.zip and Update_data_full.zip modified and ready to install via TWRP directly from EMUI 4.1 for the L21 (C432B382/EMUI 5.0.1) and L23 (C605B372/EMUI 5.0.1): here
Greetings

OxygenOS 10.5.6 (Global to EU Without PC)

installed successfully and everything is working like normal
Download 10.5.6.BE83BA
Put on root storage
Go to system update
Tap the gear top right
Click update zip
Wait for the install to complete
The Intel boot will take up to a min or 2 don't panic
Download link
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
www.oneplus.com
After download within file manager delete the last 3 letter after .zip
Example update.zip.jpe
You will delete the .jpe to make it a zip file
After you have moved it to root storage proceed to install
If you oxygenos updater app you will have to change your device to OnePlus nord n100 (eu)
What's new?
System
• Optimized the experience of Quick Settings for mute and vibration
• Optimized some text of the Setting
• Improved system stability
Network
• Further improved network stability
This update has the December security patch not the reported 10.5.10
Please help me. My phone already brick. How to flash vendor or system
.i will try it fastboot flash system system.img not work ..partition not found
piashmsubd said:
Please help me. My phone already brick. How to flash vendor or system
.i will try it fastboot flash system system.img not work ..partition not found
Click to expand...
Click to collapse
look here
[OPN100][OOS 81AA/83BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com

How To Guide (Guide) Rooting, payload dumper, magisk_patched guides NE2213

Hi all,
Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself
Please read the process before committing to proceeding, so you know what's required and what you should and shouldn't use!
Stock and patched images are UK/ EU NE2213 but the guides are universal and could be used on multiple devices.
NOTE:
For these guides the versions used are:
Stable, Canary or BETA depending on firmware, simply change the channel in Magisk settings then select install / update:
NE2213_11_A.12
Magisk Manager v24.3 (24300) Stable
NE2213_11_A.13
Magisk Manager v24.3 (24300) Stable
NE2213_11_A.14
Magisk Manager v25 (25000) Stable this version retains root after a restart, more stable version over previous iterations.
NE2213_11_A.16
Magisk Manager v25.2 (25200) Stable
NE2213_11_C_20
Magisk Manager v25.2 (25200) Stable
NE2213_11_C_21
Magisk Manager v25.2 (25200) Stable
NE2213_13.1.0.520 (EX01)
Magisk Manager v26.1 (25200) Stable
Oxygen OS NE2213_13.1.0.521 (EX01)
Magisk Manager v26.1 Stable
1st
Extracting a boot.img using Fastboot Enhance
Pre-requisites
A device with a working version of magisk manager installed, simply change the channel to the version outlined in the list above relevant to your firmware then select install / update:
A Windows 10 computer / laptop
A full update downloaded firmware zip for your model (recommend oxygen updater)
Payload dumper program for Windows.
An unlocked bootloader.
The local System Update Installer : normal local system update will not allow a reboot during installation, the one I've linked will.
Process
On your computer
1. Download and copy the fastboot enhance folder to your desktop or a location of your choosing.
Download from here: https://github.com/libxzr/FastbootEnhance/releases
2. Download the firmware of your choice (always use full zips, not incremental) and open it using Winrar or a similar zip program, extract the file called payload.bin to a folder of your choosing.
3. Run the program FastbootEnhance.exe, a window will appear, click Payload Dumper, then click browse and point to the payload.bin file, the contents of that payload.bin will now be shown, bare in mind you'll need to check the box "Allow incremental" even if it's a full zip
4. One of the files will be called boot.img, this is the file we'll be patching, click extract then copy this to your phone, root of storage which is called /sdcard.
On your phone
5. Open up Magisk and click Install / Update, if you don't see update then change channel, do this by changing the channel in magisk settings, it'll then show the install/ update buttons.
6. Select "Select and Patch a file" it'll open up a file browser, navigate to the boot.img you copied earlier and select it, allow it to complete (this will output a file called "magisk_patched" which will be output into the Downloads folder)
You now have a patched boot.img ready to boot or flash to either slot with fastboot or boot via fastboot.
I would recommend booting as this is risk free, if it's a bad image for whatever reason and you choose to flash then your phone will bootloop.
NOTE** Some people have noticed that an already patched boot.img when flashed can fail and cause a boot loop when flashed, so if you have downloaded a magisk_patched img from somewhere else then you WILL need to re-patch it on your own device preferably using the afore mentioned magisk manager based on what firmware it's from.
If you intend to follow the guide below with your own patched img then you shouldn't need to patch it twice but it won't hurt if you do.
2nd
Update from XX stable to XX+ stable whilst retaining root
Guide
**NOTE- Although this may work, the system may be unstable, especially when changing bases, eg: Android 11-12 or 12-13, so if you encounter strange behaviour then a factory wipe is advised.
1. Download the relevant firmware for your device via oxygen updater
2. Open Magisk and remove all the modules you have installed, then reboot
**NOTE- At this point I tend to copy out the whole firmware to my computer, incase I need it in the future, the boot img and patched boot img are at the foot of this guide, I'll always upload the latest firmware as soon as it comes out for the UK/EU model
3. Install the OnePlus local install apk listed below in downloads. Click the cog and select "Local Upgrade" the file should be listed on screen, if not then move the file to the root of your phones storage.
4. Click install and allow it to go through the process
**NOTE- DO NOT REBOOT AT THIS POINT YOU WILL LOSE THE ABILITY TO PATCH ON THE FLY, SIMPLY BACK OUT OF THE SCREEN WHICH SAYS "INSTALLATION COMPLETED. RESTART TO EXPERIENCE NEW FEATURES"
5. Open up magisk and click install (you may see two install buttons, top one is magisk and the bottom is magisk manager, we need the top one)
6. You'll be faced with a screen that has several options, you want to select "Install to Inactive slot (After OTA)" then select "LET'S GO" once complete click reboot.
7. Once your phones booted back up your system / files should all remain as they were and you should have root access.
You can now install all your modules again so long as they're compatible with the firmware you've just updated to.
3rd
Rooting using fastboot commands
Method 1
Booting the patched image
1. Obtain a patched boot image for your device variant preferably using payload dumper or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer
**NOTE - The above suggested downloads are for the EU / UK variant- if you have another model / firmware please use that instead, If you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager to avoid a bootloop, if you still get a bootloop it's best to obtain one yourself using the guide at the top of this post.
2. Reboot your phone to fastboot
and connect to your computer.
3. Boot the magisk patched img
fastboot boot magisk_patched (or name of your patched boot img)
Your phone should now boot automatically, you should now be rooted but we need to make this permanent, if you were to reboot you would lose root.
4. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings and install the update, the buttons should then show.
5. Select Direct install (recommended) then click ok.
6. Allow magisk to permanently root your device then click reboot.
You should now boot and remain rooted.
Method 2
Flashing to both slots
1. Obtain a patched boot img for your device variant or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer
**NOTE - Again the above suggested downloads are for the EU/ UK variant- if you have another model / firmware please use that instead, if you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager, to avoid a bootloop
2. Reboot your phone to fastboot and connect to your computer.
Command: adb reboot bootloader
3. Open a command prompt on your computer and navigate to your ADB/fastboot folder.
4. Type the following.
fastboot flash boot_a magisk_patched
Press enter.
fastboot flash boot_b magisk_patched
Press enter
fastboot reboot
Press enter
6. Your phone should now boot, open magisk and verify you're rooted.
Troubleshooting
If flashing succeeds but you don't have root and you've followed all the instructions, you may have some magisk modules still active, try performing the following.
1. Connect your phone to your computer.
2. Reboot the phone, then during the boot animation enter this command via ADB.
adb wait-for-device shell magisk --remove-modules
3. Allow to boot, modules will be removed and root should then be active.
If there is no magisk install / update buttons.
1. Make sure you have granted permission to magisk in settings / apps / magisk / permissions
2. Make sure that the update channel is on canary, then force close magisk and then re-open
3. If it still doesn't work then update magisk using canary
4. Last method to check would be to change to the beta channel in magisk settings, then install it.
Or change the update channel, install the version on offer, then change back to canary, install and you should be good to go.
Window's version
Windows 7 will not work with fastboot, please use Windows 10
USB
Use USB 2.0 not 3.0 or 3.1
ADB
These are the files i use for ADB (in the below list) tested these on fresh installs of windows on several windows machines, all win 10
Place them into the root of C so it reads C:\ADB much easier to navigate to that way.
Bootloader unlock
Boot to the bootloader with adb reboot bootloader
type fastboot flashing unlock
Agree to unlock - allow to boot.
If you can't see the device using ADB
Make sure USB Debugging is turned on
Connect your cable to your phone and computer, when asked what you want your phone to do, click on transfer files, a driver will be installed.
After this reconnect your phone and it'll prompt you with a disclaimer with a check box, check the box and click ok, ADB / Fastboot should now work.
Files:
Local System update APK, this must be used as the local OnePlus 10 Pro one will not allow a reboot during the installation, so you cannot install the Magisk boot image during an upgrade, the android 13 local update apk is also required for rolling back to android 12.
Android 13 local update apk
3.27 MB folder on MEGA
mega.nz
Android 12 local update apk
3.27 MB folder on MEGA
mega.nz
ADB Files for Windows 10:
7.69 MB folder on MEGA
5 files
mega.nz
Payload dumper program for Windows-
https://mega.nz/folder/vU00FZDa#PIEfjl5w5wonyNAwHW3FBQ
Oxygen OS NE2213_11_A.12 Stock boot image
0 byte folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.12 Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.13 Stock boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.13 Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.14 Stock boot image
384 MB folder on MEGA
2 files
mega.nz
Oxygen OS NE2213_11_A.14 Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.16 Stock boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.16 Patched boot image
192 MB folder on MEGA
mega.nz
Android 13
Oxygen OS NE2213_11_C_20 Stock boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_C_20 Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_C_21 Stock boot image https://mega.nz/folder/LNVxTDYA#yly9xpjFjQhe4De_jqyzbw
Oxygen OS NE2213_11_C_21 Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_13.1.0.520 (EX01) Stock boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_13.1.0.520 (EX01) Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_13.1.0.521 (EX01) Stock boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_13.1.0.521 (EX01) Patched boot image
192 MB folder on MEGA
mega.nz
Glad to see you here bro with the 10 Pro and helpful guide's!!
Cheers
galaxys said:
Glad to see you here bro with the 10 Pro and helpful guide's!!
Cheers
Click to expand...
Click to collapse
Slowly coming around to this phone mate, we desperately need a few custom ROMs..
EvoX on this would be phenomenal.
Nudge nudge @AnierinB
UPDATE: First patched boot image is up, using the latest stable Magisk v24.3 (24300)
dladz said:
Slowly coming around to this phone mate, we desperately need a few custom ROMs..
EvoX on this would be phenomenal.
Nudge nudge @AnierinB
Click to expand...
Click to collapse
Yeh, it's early but hopefully a few Developer's will get this badboy device!
Thank you thank you THAAAANK YOOOOUUUU
meowmeowpewpew said:
Thank you thank you THAAAANK YOOOOUUUU
Click to expand...
Click to collapse
Lol welcome mate
meowmeowpewpew said:
Thank you thank you THAAAANK YOOOOUUUU
Click to expand...
Click to collapse
I honestly hope so..
I'm having a few issues isolating the correct files to make the center clock Magisk mod, but that's in the works. Will have it done soon hopefully.
OnePlus thought it would be a good idea to get rid of OPSystemUI.apk in place of systemui.apk so maybe more in line with stock android. But we'll see
@galaxys as if my prayers were answered, joined the Evo X TG group and there is now a OnePlus 10 group so it's in the works, seriously hope it's AnierinB, he did so well with the 8 pro.
Literally cannot wait
dladz said:
@galaxys as if my prayers were answered, joined the Evo X TG group and there is now a OnePlus 10 group so it's in the works, seriously hope it's AnierinB, he did so well with the 8 pro.
Literally cannot wait
Click to expand...
Click to collapse
Hey that's great news and something to definitely look forward to!
Cheers
Very happy to see guides! Nice, thank you so much !
dladz said:
@galaxys as if my prayers were answered, joined the Evo X TG group and there is now a OnePlus 10 group so it's in the works, seriously hope it's AnierinB, he did so well with the 8 pro.
Literally cannot wait
Click to expand...
Click to collapse
I cannot find that Evo X 10 Pro channel, have you got a link?
kouzelnik3 said:
I cannot find that Evo X 10 Pro channel, have you got a link?
Click to expand...
Click to collapse
If you have telegram just search for evo x up the top, you'll see the main channel.
The the other is in that, i'm just in the middle of something, i'll send it once i'm done.
kouzelnik3 said:
I cannot find that Evo X 10 Pro channel, have you got a link?
Click to expand...
Click to collapse
Evolution X - OnePlus 10 Series
Telegram: Contact @EvolutionXOnePlus10
t.me
Macke93 said:
Evolution X - OnePlus 10 Series
Telegram: Contact @EvolutionXOnePlus10
t.me
Click to expand...
Click to collapse
Oh I've found it.
Hello All,
Very many thanks for your guide. It really helped me root my OP 10 PRO
I was wondering if it is possible to flash my OP ColorOS with OxygenOS EU/UK version you have uploaded?
I copied the 02b0d1b2508744e3a41115aeb274cccf.zip to the root folder and I tried installing via Oxygen Updater using the automatic method, but it fails every time.
If I try installing it manually, I have to download the Oxygen Updater via oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk.zip and rename to .apk. - I then launch System Update , click on settings and it says 'Move installation package into root directory' (which it is).
Have I missed a step?
kouzelnik3 said:
Oh I've found it.
Click to expand...
Click to collapse
Ah was just about to post it mate.
Glad you found it, it's only new but that fact that it's here is brilliant . I'm hoping AnierinB is the dev who makes the rom for the 10.
Lynxy0 said:
Hello All,
Very many thanks for your guide. It really helped me root my OP 10 PRO
I was wondering if it is possible to flash my OP ColorOS with OxygenOS EU/UK version you have uploaded?
I copied the 02b0d1b2508744e3a41115aeb274cccf.zip to the root folder and I tried installing via Oxygen Updater using the automatic method, but it fails every time.
If I try installing it manually, I have to download the Oxygen Updater via oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk.zip and rename to .apk. - I then launch System Update , click on settings and it says 'Move installation package into root directory' (which it is).
Have I missed a step?
Click to expand...
Click to collapse
Honestly mate i'm not sure, you're essentially changing region.
Have you looked into fastboot enhanced?
You can obtain the firmware from oxygen updater (it's 4.15GB the one i uploaded is only the boot image and patched boot image)
Then copy it to your computer and allow it to flash to your phone.
This isn't without risk mate and i've not done this before myself.
dladz said:
Ah was just about to post it mate.
Glad you found it, it's only new but that fact that it's here is brilliant . I'm hoping AnierinB is the dev who makes the rom for the 10.
Click to expand...
Click to collapse
I am hoping too, because in this state oxygen os in this device is bad. Yeah, it is quite new, but hey, it is halfly baked. And not only evo x, but other ROMs I hope will come.
dladz said:
Honestly mate i'm not sure, you're essentially changing region.
Have you looked into fastboot enhanced?
You can obtain the firmware from oxygen updater (it's 4.15GB the one i uploaded is only the boot image and patched boot image)
Then copy it to your computer and allow it to flash to your phone.
This isn't without risk mate and i've not done this before myself.
Click to expand...
Click to collapse
Thanks for your swift reply. I will wait until there is a verified method. For now, I will tread lightly with the rooted version hehe

trying to update android version from 10 to 11. please help!

hello.
I'm look for a way to upgrade android version from 10 to 11.
build number: QKQ1.200419.002.WW_PHONE-17.0822.2005.11
-I can't use auto update
-I can't use manual update (transferring Raw file to internal storage and then install it from the os), it keeps giving my a fail error
thank you
blabla15rul said:
hello.
I'm look for a way to upgrade android version from 10 to 11.
build number: QKQ1.200419.002.WW_PHONE-17.0822.2005.11
-I can't use auto update
-I can't use manual update (transferring Raw file to internal storage and then install it from the os), it keeps giving my a fail error
thank you
Click to expand...
Click to collapse
You can't install RAW files from internal storage, you have to flash it from Fastboot. Auto updating should work if you update incrementally up to whatever version you're looking to end at, unless there is an issue that's not detailed in your post.
blabla15rul said:
hello.
I'm look for a way to upgrade android version from 10 to 11.
build number: QKQ1.200419.002.WW_PHONE-17.0822.2005.11
-I can't use auto update
-I can't use manual update (transferring Raw file to internal storage and then install it from the os), it keeps giving my a fail error
thank you
Click to expand...
Click to collapse
First update to WW-17.0823.2104.147 by putting the fw zip downloaded from asus site.
Then update to the A11 fw WW-18.0410.2106.138 by putting the fw zip downloaded from asus site.
Else you can use twrp latest build.
1. Just download the last A11 stable fw that is WW-18.0410.2203.201 from asus website.
2. Put the zip in Internal storage.
3. Boot to twrp recovery.
4. Click on Install > Select the zip file > Swipe to flash. (You will see in which slot the zip is flashing)
5. After flash done, (just don''t reboot). Go to Reboot Section of twrp> Change Slot to the other one via clicking on Slot name.
6. Now do same as 4.
7 After flash done. Just Reboot to system
Hello
I also recommend https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3358711/
Regards
Automatic updates
Sagar Sharma01 said:
First update to WW-17.0823.2104.147 by putting the fw zip downloaded from asus site.
Then update to the A11 fw WW-18.0410.2106.138 by putting the fw zip downloaded from asus site.
Else you can use twrp latest build.
1. Just download the last A11 stable fw that is WW-18.0410.2203.201 from asus website.
2. Put the zip in Internal storage.
3. Boot to twrp recovery.
4. Click on Install > Select the zip file > Swipe to flash. (You will see in which slot the zip is flashing)
5. After flash done, (just don''t reboot). Go to Reboot Section of twrp> Change Slot to the other one via clicking on Slot name.
6. Now do same as 4.
7 After flash done. Just Reboot to system
Click to expand...
Click to collapse
Apologies for the delayed answer
Well, the first method you suggested worked perfectly
Thank you so much!!!
iS Anyone Have A12 Flash Raw File?
lvl0rde said:
iS Anyone Have A12 Flash Raw File?
Click to expand...
Click to collapse
I already told you i have A12 raw.
But you need to message me in my telegram id.
As i don't have enough internet to upload in a cloud storage and give you the link.
Sagar Sharma01 said:
I already told you i have A12 raw.
But you need to message me in my telegram id.
As i don't have enough internet to upload in a cloud storage and give you the link.
Click to expand...
Click to collapse
What Was Ur Telegram account?

Rooting Multiple Phones Quickly

Hi all,
Thanks for the great work on Magisk.
Predicament - need to be rooting multiple S20 devices often.
Current Process - Unlock Bootloader, Setup Phone (install Magisk) -> Copy AP File -> Patch File in Magisk App ->> Copy Patched TAR to PC -> Use Odin to Flash. Rinse and Repeat...
So my question is.... is there a better way to do this and speed up the process for multiple phones?
My main queries...
1 . Does the patch process do the same thing (i.e. generate the same AP file) on all of the devices (same model)
1a. If so then can i just flash the same patched file to all phones?
2. Can the patching file from within the Magisk app be done on a PC instead to prevent needing to copy file to/from the phone and use the Magisk app - i.e. can i emulate it or extract the patching logic to run elsewhere?
3. Any other suggestions to automate/speed up this process??
Many thanks!
1. Patching can be done from any phone and not just the target device.
2. If all phones are on same firmware version and are same device without any changes (same model, same region etc...), Then you can use the same patch file used on 1 successful phone to other.
3. Patching can only be done by Android app.
Thanks for the quick response, that's good news!
Out of interest why the is patching only possible from Android? can this process not be extracted and ran on a PC to modify the boot file?

Categories

Resources