Related
I failed similar times to root my phone with twrp 3.2.xx and 3.1.xx. I used Odin 3 v3.13.1.
Any ideas or thread links for the young padawan?
I appreciate your advice masters :good:
Using Odin Flash TWRP latest from the note 8 TWRP thread here on XDA, one on their site is not latest.
Install magisk manager app from play store.
Download magisk from the app.
Reboot to TWRP and flash the magisk file just downloaded.
Reboot and check magisk manager for root and hide.
Should be good.
Nope. Not working and still ends in a bootloop and it's unable to mount the internal storage.
Something went wrong, so.. my phone is unable to boot the system after that!
The issue is the version of TWRP and Oreo, its not yet compatible on this device, it needs porting over
If you want MAGISK you need to do it all in one hit.
Flash TWRP
Select Read Only Option.
Format Data
Reboot Recovery
Flash the DM Verify Encrypt file
Reboot Recovery, You could be able to flash files wihtout a Data mount error.
Now flash the files you want, i..e MAGISK
Once you have booted the ROM and return back to TWRP you are unable to mount Data.
This can cause various issue when flashing files
Funny you.. How can I format if the internal storage isn't able to mount?
"Select Read Only Option.
Format Data" <-- seems like a contradiction to format a missing
partition.
I think we need to wait until someone will port the twrp for Oreo. cheerio!
Because it needs to be done when you first flash it.
Once you have flash Oreo, Then TWRP, You boot into TWRP and format. You then Flash the DM Verify.
Data is accessible, its empty but accessible, Flashing any files like MAGISK work without any errors.
I have it all working on mine without any issues, I do know if i need to flash any additional files it wont work properly due to Data no longer mountable.
There is a updated version of TWRP that fixes this, but its not been ported over.
I download Magisk and No Verity from http://www.desinerd.co.in/how-to-huawei-p20-pro-root-twrp-recovery/.
I have TWRP official installed 3.2.1 with security disabled on the EMUI. I'm trying to install the Magisk and No Verity but I can't find the zip files in the file system. Where is the Download folder located in the file system? Do I have to move the files somewhere else in order to access it from TWRP? I read that the Download folder is in /sdcard, but there are multiple folders with random letters and numbers, like maybe it's encrypted or something?
If I'm rooting wrong, can you tell me how to root?
I tried using the Patched ramdisk of Magisk, but it didn't do anything after reboot and Root Check says not rooted, hence, that's why I'm following this guide to see if this works.
Same
Did you find out how to root as I'm having the same problem
Install the unofficial TWRP. Remove fingerprint/password/pin etc then try again. TWRP doesn't decrypt when they're active.
Hi, having the same issue with TWRP (twrp-3.2.2-0-charlotte.img and twrp-3.2.1-0-charlotte.img) from dl.twrp.me/charlotte/.
How can I repair it? Cant flash Magisk.
Thanks
Hello, help would be amazing as this is my 2nd day trying to root my xPeria XZ Premium!
I've finally flashed twrp , I'm trying to install this rom:
https://forum.xda-developers.com/xz-premium/development/kernel-sony-xz-premium-5-2018-t3784669
But I'm getting stuck when trying to install magisk, OR move any zip files from my SD card to my Internal Storage.
Could anyone guide me through how to resolve this? :crying:
Have unlocked boot loader?
Need to format data first
xStatiZx said:
Hello, help would be amazing as this is my 2nd day trying to root my xPeria XZ Premium!
I've finally flashed twrp , I'm trying to install this rom:
https://forum.xda-developers.com/xz-premium/development/kernel-sony-xz-premium-5-2018-t3784669
But I'm getting stuck when trying to install magisk, OR move any zip files from my SD card to my Internal Storage.
Could anyone guide me through how to resolve this? :crying:
Click to expand...
Click to collapse
Hey my dude follow these steps, in twrp select wipe->format data (You'll lose all your files) now try flash the rom, you should find a custom kernel for your device as well and install it after the rom. If the Kernel doesnt install magisk now would be a good time to do it :highfive:
Matthewwwww1998 said:
Hey my dude follow these steps, in twrp select wipe->format data (You'll lose all your files) now try flash the rom, you should find a custom kernel for your device as well and install it after the rom. If the Kernel doesnt install magisk now would be a good time to do it :highfive:
Click to expand...
Click to collapse
This isn't necessary. Just extract boot.img from whatever rom.zip you're using, flash that in recovery, reboot to recovery again and magisk should install.
murph187 said:
This isn't necessary. Just extract boot.img from whatever rom.zip you're using, flash that in recovery, reboot to recovery again and magisk should install.
Click to expand...
Click to collapse
You're a GOD. Thank You!!!!!
updater process ended with error: 1
I was able to install magisk but after that if i try to install nethunter I get this same error. I am using redmi 4(santoni). have installed lineage OS 15.1
Can someone please help me?
logs
I had similar error shown below while installing a custom ROM:
Error applying update: 7 (ErrorCode:: kInstallDeviceOpenError )Updater process ended with ERROR: 1 Error installing zip file
Solved by using slightly older version of TWRP
i try and didnt work how to extract boot image in steps ??
magicstep said:
I had similar error shown below while installing a custom ROM:
Error applying update: 7 (ErrorCode:: kInstallDeviceOpenError )Updater process ended with ERROR: 1 Error installing zip file
Solved by using slightly older version of TWRP
Click to expand...
Click to collapse
which version you use
murph187 said:
This isn't necessary. Just extract boot.img from whatever rom.zip you're using, flash that in recovery, reboot to recovery again and magisk should install.
Click to expand...
Click to collapse
Hi, which option may i have to choose? there are 4 options
magicstep said:
I had similar error shown below while installing a custom ROM:
Error applying update: 7 (ErrorCode:: kInstallDeviceOpenError )Updater process ended with ERROR: 1 Error installing zip file
Solved by using slightly older version of TWRP
Click to expand...
Click to collapse
3.2.2 worked for me.
In my case unmounting all the partitions fixed it for me, the boot.img method didn't work.
magicstep said:
I had similar error shown below while installing a custom ROM:
Error applying update: 7 (ErrorCode:: kInstallDeviceOpenError )Updater process ended with ERROR: 1 Error installing zip file
Solved by using slightly older version of TWRP
Click to expand...
Click to collapse
I had flashed new version on firmware but forgot to update TWRP recovery that is why I was getting this error. I updated TWRP recovery. also flashed boot.img image then I was able to fix this issue.
guys please help me i have xiaomi mi a2 lite whit twrp 3.5.0_9 installed and unlocked bootloader i downloaded android 11 rom link: https://forum.xda-developers.com/t/rom-11-0-daisy-aosp-11-0.4167961/. When i go to recovery mode i flash the rom and appears this error: Updater process ended whit error: 1 to flash additional zips please reboot recovery to switch to the updated slots. Error installing zip file rom.zip. please help me.
THANKS
samyxy said:
guys please help me i have xiaomi mi a2 lite whit twrp 3.5.0_9 installed and unlocked bootloader i downloaded android 11 rom link: https://forum.xda-developers.com/t/rom-11-0-daisy-aosp-11-0.4167961/. When i go to recovery mode i flash the rom and appears this error: Updater process ended whit error: 1 to flash additional zips please reboot recovery to switch to the updated slots. Error installing zip file rom.zip. please help me.
THANKS
Click to expand...
Click to collapse
I was having the same issue... After hours of research I finely managed to fix it. Try the following:
1 - Install TWRP (I also had the 3.5.0_9 version).
2 - Format data and wipe all the advanced options possible.
3 - Download the program "payload_dumper-win64".
3.1 - Following the payload dumper instructions, I've copied the payload.bin from my custom ROM to the payload_input folder.
3.2 - Execute payload_dumper.exe and wait, a lot!
3.3 - Copy the resulted files (boot.img, system.img, vendor.img) in to the phone.
4 - In TWRP, go to install, select from images, and, one by one, install the images you've just copied.
4.1 - Note that during the install process, you will have to select the correct "slots" to flash the images. In my case, there where to options for system and vendor. I've chosen the "System Image" and "Vendor Image" option.
5 - Restart.
That's it! I didn't had to change slots nor wipe data after the installation... I don't know if this was the correct approach, but after many tries this is what worked for me
Sorry about my bad english...
Sometimes it is caused due to corrupted file. While transferring file through MTP it is likely to corrupt large files. I had the same problem. Then I tried copying file while in TWRP (sure it is also MTP) and it worked.
PendiukG said:
I was having the same issue... After hours of research I finely managed to fix it. Try the following:
1 - Install TWRP (I also had the 3.5.0_9 version).
2 - Format data and wipe all the advanced options possible.
3 - Download the program "payload_dumper-win64".
3.1 - Following the payload dumper instructions, I've copied the payload.bin from my custom ROM to the payload_input folder.
3.2 - Execute payload_dumper.exe and wait, a lot!
3.3 - Copy the resulted files (boot.img, system.img, vendor.img) in to the phone.
4 - In TWRP, go to install, select from images, and, one by one, install the images you've just copied.
4.1 - Note that during the install process, you will have to select the correct "slots" to flash the images. In my case, there where to options for system and vendor. I've chosen the "System Image" and "Vendor Image" option.
5 - Restart.
That's it! I didn't had to change slots nor wipe data after the installation... I don't know if this was the correct approach, but after many tries this is what worked for me
Sorry about my bad english...
Click to expand...
Click to collapse
It's legit procedure. Also you don't need to manage slots here, caz recovery automatically does that for you.
Hello guys, i'm from Russia, sorry for my bad English. I using Poco X3 Pro, and i have some troubles. I wanted to install custom firmware. First ROM
delivered successfully, unlike the second. After clearing all sections except sd cart and otg, I tried to install the original MIUI build, but it didn't work. I downloaded the original MIUI, but still. When installing, it says: "Update process ended with ERROR: 1" The methods from the top didn't help, please help!
Sushanthn94 said:
updater process ended with error: 1
I was able to install magisk but after that if i try to install nethunter I get this same error. I am using redmi 4(santoni). have installed lineage OS 15.1
Can someone please help me?
logs
Click to expand...
Click to collapse
Kali Nethunter on redmi 4x (santoni) is updated here:
Releases ยท Neternels/android_kernel_xiaomi_msm8937
Redmi 4X (santoni) NetHunter Kernel. Contribute to Neternels/android_kernel_xiaomi_msm8937 development by creating an account on GitHub.
github.com
Follow it and flash firmwares (if needed).
Hello everybody.
I've read that 18.1 supports 4.2+ so I've tried to install in two MTK6589T devices I've. One running 4.2, the other running 4.4
CMW/TWRP gave an error mounting system, so I mounted system manually and it started flashing. Firstly it detected old root installed and disabled the old root. But when it tried to find the boot, installation was aborted because installator claims cannot find the boot on both phones.
Then I though, okay, lets reboot back to android, I will try to install a few days later, maybe its buggy now, but both phones cannot boot.
I can easily fix them by flashing rom again I guess, but I would like to know where's the issue and also post it for more people could face the same problem.
Any idea where's the problem/how to fix without rom reflashing? I've tried magisk uninstaller but after mounting system in recovery it is also giving error.
Thanks
UPDATE: For now, if no other solution is found, bootloop can be bypassed by dirty installing the rom again. But it has to be an easier workaround...
We know now that the problem is caused because of two factors merging:
1- Using Magisk.zip installer through custom recovery
2-In the case that the custom recovery CMW/TWRP installed in the phone is very old (for instance, CMW automade for MTK6589X or TWRP 2.5.0).
While installing, Magisk tries to send commands to the custom recovery that cant be understood by it, leaving the installation incomplete after some modifications in /system (read below recovery log).
Acording to the recovery, it seems that Magisk did some modifications without running correctly survival script - Adding addon.d survival script ("Unrecognized option '-Xnodex2oat'") and .zip installer is not designed to revert actions in this case.
Also, Magisk couldn't reach the boot modification step, so boot is not damaged, therefore workarounds for restoring boot won't work.
Using Magisk Unistaller.zip is also not possible as the uninstaller is mainly designed for boot backup restoration, and again, this is not the case.
Currently needed: Find what's wrong in system due to the incomplete Magisk installation to revert it back to the original state (before faulty magisk.zip installation).
Recovery log:
************************
* Magisk v18.1 Installer
************************
- Mounting /system, /vendor
- Target image: /dev/bootimg
- Device platform: arm
- Removing system installed root
- Constructing environment
- Adding addon.d survival script
Unrecognized option '-Xnodex2oat'
up!
I' also having the same problem. My Samsung J2 Prime stuck at logo after updating to 18.1. Any tips on how to fix it without resetting my phone? Thanks.
Update: Bootloop fixed. I used TWRP to restore boot image. I then update Magisk by flashing zip file from TWRP. Everything went back to normal. Hope this help.
trol_sg said:
Hello everybody.
I've read that 18.1 supports 4.2+ so I've tried to install in two MTK6589T devices I've. One running 4.2, the other running 4.4
CMW/TWRP gave an error mounting system, so I mounted system manually and it started flashing. Firstly it detected old root installed and disabled the old root. But when it tried to find the boot, installation was aborted because installator claims cannot find the boot on both phones.
Then I though, okay, lets reboot back to android, I will try to install a few days later, maybe its buggy now, but both phones cannot boot.
I can easily fix them by flashing rom again I guess, but I would like to know where's the issue and also post it for more people could face the same problem.
Any idea where's the problem/how to fix without rom reflashing? I've tried magisk uninstaller but after mounting system in recovery it is also giving error.
Thanks
Click to expand...
Click to collapse
If you have a backup of your boot image, you can just restore it using TWRP. But in case that you have no backup of boot image, you can try to get boot image from the internet and restoring using it. In my case, this is what I did.
1. Go to TWRP and then make backup of boot image of the faulty phone*. (Folder 1)
2. I used another J2 prime to create a boot image backup. (Folder 2)
3. Once that is done, copy and replace the files inside the Folder 2 into Folder 1.
4. Reboot to TWRP again then use that to restore the boot image on my stuck J2.
Tips: make backup in SD card so you can easily swap it in between the bad and good phone.
*This is to create a folder of the backup file. I did tried to directly copy and paste the backup boot image file from another good phone but TWRP didn't detect it. So this is the workaround that I come with. And it worked for me.
Thanks for your answer but I doubt your case is mine. Your device is much newer than mine and according to your comment, you've sucesfully installed previous version of Magisk without issues. This is not a problem while updating, as Magisk v. earlier than 18.1 was not compatible with android 4.2+. I think Magisk is not compatible with MT6589T even if they run 4.2 or 4.4.
I think that it cannot be a boot problem as TWRP/CWM displayed msg 'Boot cannot be found' while installing Magisk, so that I don't think boot was replaced or modified in any ways. Moreover, the bootloop is not in the boot loading, as phone can pass boot image without any problem, but it is stuck in android loading image. I'm thinking in some script or root modification that Magisk did before trying to unpack the boot, however I'm not that deep into the Magisk install to find the proper workaround.
I can restore boot backup and also I can take boot file from the original rom and flash, because in Mediatek-based devices, boot.img is inside de zip, but I dont think it will solve the problem. Anyhow I'll get back ASAP with the answer.
Any more ideas??
Nothing, boot/uboot restoration or flashing again just the boot won't fix the problem, so it's something that Magisk installator touch in /system or /data I guess, but what?
trol_sg said:
Nothing, boot/uboot restoration or flashing again just the boot won't fix the problem, so it's something that Magisk installator touch in /system or /data I guess, but what?
Click to expand...
Click to collapse
Have you read/tried this?
didgeridoohan(dot)com/magisk/MagiskIssues
Ato09 said:
Have you read/tried this?
didgeridoohan(dot)com/magisk/MagiskIssues
Click to expand...
Click to collapse
Yes, I've read them before I made the post. I've also looked for a solution in some of the threads and using search, but couldn't find a way.
Here I attach recovery.log if someone is interested to see the detailed problem.
Also, here below I attach the lines concerning the installation. All other is uninstallation tries and so on:
************************
* Magisk v18.1 Installer
************************
- Mounting /system, /vendor
- Target image: /dev/bootimg
- Device platform: arm
- Removing system installed root
- Constructing environment
- Adding addon.d survival script
Unrecognized option '-Xnodex2oat'
dalvikvm: [options] class [argument ...]
dalvikvm: [options] -jar file.jar [argument ...]
The following standard options are recognized:
-classpath classpath
-Dproperty=value
-verbose:tag ('gc', 'jni', or 'class')
-ea[:<package name>... |:<class name>]
-da[:<package name>... |:<class name>]
(-enableassertions, -disableassertions)
-esa
-dsa
(-enablesystemassertions, -disablesystemassertions)
-showversion
-help
The following extended options are recognized:
-Xrunjdwp:<options>
-Xbootclasspath:bootclasspath
-Xcheck:tag (e.g. 'jni')
-XmsN (min heap, must be multiple of 1K, >= 1MB)
-XmxN (max heap, must be multiple of 1K, >= 2MB)
-XssN (stack size, >= 1KB, <= 256KB)
-Xverify:{none,remote,all}
-Xrs
-Xint (extended to accept 'ortable', ':fast' and ':jit')
These are unique to Dalvik:
-Xzygote
-Xdexopt:{none,verified,all,full}
-Xnoquithandler
-Xjniopts:{warnonly,forcecopy}
-Xjnitrace:substring (eg NativeClass or nativeMethod)
-Xstacktracefile:<filename>
-Xgc:[no]precise
-Xgc:[no]preverify
-Xgc:[no]postverify
-Xgc:[no]concurrent
-Xgc:[no]verifycardtable
-XX:+DisableExplicitGC
-X[no]genregmap
-Xverifyopt:[no]checkmon
-Xcheckdexsum
-Xincludeselectedop
-Xjitop:hexopvalue[-endvalue][,hexopvalue[-endvalue]]*
-Xincludeselectedmethod
-Xjitthreshold:decimalvalue
-Xjitcodecachesize:decimalvalueofkbytes
-Xjitblocking
-Xjitmethod:signature[,signature]* (eg Ljava/lang/String\;replace)
-Xjitclass:classname[,classname]*
-Xjitoffsetffset[,offset]
-Xjitconfig:filename
-Xjitcheckcg
-Xjitverbose
-Xjitprofile
-Xjitdisableopt
-Xjitsuspendpoll
Configured with: debugger profiler hprof jit(armv7-a-neon) smp show_exception=1
Failed to initialize runtime (check log for details)
- Unpacking boot image
MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/dev/bootimg]
No boot image magic found!
! Unable to unpack boot image
- Unmounting partitions
E:Error executing updater binary in zip '/sdcard/Magisk-v18.1.zip'
Error flashing zip '/sdcard/Magisk-v18.1.zip'
@trol_sg I'm gonna guess it's got to do with the absolutely ancient TWRP you're using. It just can't handle everything that the Magisk installation script is trying to do...
Your best bet (if Magisk will work at all on your device) is to patch the boot image with the Magisk Manager and then flash the patched image manually. There are new and shiny installation instructions available here: https://topjohnwu.github.io/Magisk/
Didgeridoohan said:
@trol_sg I'm gonna guess it's got to do with the absolutely ancient TWRP you're using. It just can't handle everything that the Magisk installation script is trying to do...
Your best bet (if Magisk will work at all on your device) is to patch the boot image with the Magisk Manager and then flash the patched image manually. There are new and shiny installation instructions available here: https://topjohnwu.github.io/Magisk/
Click to expand...
Click to collapse
Thank you so much for your answer. So it's the recovery, but can't find newer ones, sadly. Too old phones I know, but just curious if I could make Magisk working on them, lol.
I was going into the boot modification manually right now, but in order to patch the boot I need manager installed first, and phone couldn't boot so I did dirty flash of the rom to be able to boot into it again.
Lets see what happens then. I'll be right back.
Anyhow, this is not a solution to fix the problem of bootloop that I am requesting help in case someone could face the same and did not make a backup of the phone and didn't want to make dirty re-flash. Any idea?
Update: After I did dirty flash of the rom, and now Jiayu g3s android 4.4 booted.
UPDATE: So, after patching manually boot and installing (using restore in TWRP 2.5 as image flash is not yet implemented AFAIK), phone booted and yes Magisk is working.
Magisk installation .zip through a very old recovery is making the bootloop. So that, a thing learnt now.
But, for other people facing this bootloop, can we do a research to find what magisk.zip did to the phones to leave them in bootloop? Maybe we can revert without rom flashing easily if we knew what's the issue...
Thanks in advance!
Doing a bit more tests I found that magisk.zip did something in /system so that it is left in bootloop, but still no idea why/whats causing that...
There are delay complete boot like 4 5 second in j7 prime. I didn't love this version
any more help?? up!!
trol_sg said:
Yes, I've read them before I made the post. I've also looked for a solution in some of the threads and using search, but couldn't find a way.
Click to expand...
Click to collapse
Try this.
Quote:
Originally Posted by void74
I faced this problem too this morning.
I have a Redmi Note 5 with AOSiP ROM, I don't know if it's the right way to do it, but I solved the bootloop problem this way:
- volume up and then boot to TWRP
- copied magisk uninstall to phone memory
- installed magisk uninstall
- rebooted in fastboot/bootloader mode
- flashed original boot.img extracted from stock image zip file ("fastboot flash boot boot.img")
- rebooted to TWRP
- installed magisk 17.0 zip file
- rebooted to system, all OK!
Only problem is that I lost previous magisk configuration, but it's a snap to reconfigure it!
Quote:
Originally Posted by Mangraviti
Here is what to do, if you HAVE NOT installed the new version:
1) Do not update via Magisk Manager.
2) Do not update via TWRP using the zip you can download via Magisk Manager.
3) Uninstall Magisk using Magisk uninstaller (ZIP).
4) Boot to Android.
5) Reboot to TWRP
6) Install V17 ZIP via TWRP and boot to Android.
If you HAVE INSTALLED and got a bootloop:
1) Download the uninstaller ZIP.
2) Enter TWRP during the bootloop.
3) Uninstall using the uninstaller ZIP.
4) Boot to Android.
5) Download V17.
6) Reboot to TWRP and flash the V17.
7) Boot to Android it it should be working.
-------------
Original post. https://forum.xda-developers.com/apps/magisk/bootloop-magisk-update-t3836904
Hope it help.
Ato09 said:
Try this.
Quote:
Originally Posted by void74
I faced this problem too this morning.
I have a Redmi Note 5 with AOSiP ROM, I don't know if it's the right way to do it, but I solved the bootloop problem this way:
- volume up and then boot to TWRP
- copied magisk uninstall to phone memory
- installed magisk uninstall
- rebooted in fastboot/bootloader mode
- flashed original boot.img extracted from stock image zip file ("fastboot flash boot boot.img")
- rebooted to TWRP
- installed magisk 17.0 zip file
- rebooted to system, all OK!
Only problem is that I lost previous magisk configuration, but it's a snap to reconfigure it!
Quote:
Originally Posted by Mangraviti
Here is what to do, if you HAVE NOT installed the new version:
1) Do not update via Magisk Manager.
2) Do not update via TWRP using the zip you can download via Magisk Manager.
3) Uninstall Magisk using Magisk uninstaller (ZIP).
4) Boot to Android.
5) Reboot to TWRP
6) Install V17 ZIP via TWRP and boot to Android.
If you HAVE INSTALLED and got a bootloop:
1) Download the uninstaller ZIP.
2) Enter TWRP during the bootloop.
3) Uninstall using the uninstaller ZIP.
4) Boot to Android.
5) Download V17.
6) Reboot to TWRP and flash the V17.
7) Boot to Android it it should be working.
-------------
Original post. https://forum.xda-developers.com/apps/magisk/bootloop-magisk-update-t3836904
Hope it help.
Click to expand...
Click to collapse
Hello, thanks
This method won't work in my case as in the step:
- installed magisk uninstall = gives error
Note 5 is much newer phone with a recent recovery TWRP that allows all Magisk.zips commands, but unluckyly not this case.
Also, this method is for wrong boot installation/damaged boot. In my case what Magisk damage is /system, not boot.
I wish it could be boot, because that is very easy to fix (flashing through fastboot/SP Flash tools in the case of MTK, recovering boot twrp "backup" even if you didn't make backup...) as you mentioned.
Hope someone have a great idea to revert system to origin, then we could post the solution for those who would like to install Magisk in 4.2+ old phones, and instead of doing boot flash manually, they try to flash magisk.zip and they got bootloop.
Main post updated with all thread information. Up!
Nothing?? Up!!
trol_sg said:
Hope someone have a great idea to revert system to origin, then we could post the solution for those who would like to install Magisk in 4.2+ old phones, and instead of doing boot flash manually, they try to flash magisk.zip and they got bootloop.
Click to expand...
Click to collapse
The only part of the Magisk installation that actually touches /system is if it installs the addon.d survival script. The log you posted earlier shows that it's trying to do this, for some reason, and failiing. I'd start looking there...
hi, as i mentioned in the title: i am in that twrp recovery, I am not able to check the files of realme ui OS zip file. i am able to copy the OS zip file to internal storage but i am not able see those files in twrp recovery. currenlty no OS is installled in my X2pro. need suggestions. should i download and flash another twrp file of lower version to check the same?