Hello friends Im new year can you help me? My magisk wont update to 22.1 so I think I need to reinstall it and flash the latest realme ui from software update at the same time
I have been trying to uninstall magisk even if I click restore IMG it shows stock boot img doesnt exist or clicking complete uninstall will do nothing no error message or anything.
What I tried so far is
-Uninstall.zip from twrp
-Uninstall.zip from magisk module using the build v21 v22 v22.1 but it was still there.
As of now I do not have access for computer so can I also ask.
Will I be able to flash the latest android 10 from Color OS A.19 using twrp?
I know that you cannot install ota without stock recovery but I saw sometimes on some thread that they are flashing latest builds using twrp so Im a little confused now.
My phone is RMX1993 Pie Color OS A.19
Related
Hey guys, so I was running 3.2.8 firmware and modem (marshmallow) with latest AOKP stable (not nightly) nougat rom and things were working as they should...
Now the official 4.0 nougat oneplus oxygen rom comes out and I'd figure it's time for an update... So I do a clean install of oxygen 4.0, boot into system, and then flash twrp-3.0.2-1.28 recovery to flash aokp nougat rom.
After that I flash latest stable SuperSU 2.79, reboot and then boot back again to install Adaway systemless v2 zip
Problem is, my phone randomly un roots itself, busybox app would freeze (had to flash it through TWRP later) and Adaway won't merge hosts file.
I know it probably has to do with either latest root, the recovery, encryption/decryption, or firmware (or combination of some of these) from what I've read on the forums...
Can anybody tell me what is causing these problems and help me fix this?
I've tried installing twrp-3.0.2-0_blu_spark_v11 recovery, version 19 of bluspark's modified TWRP, and SuperSU 2.79 sr2 but I still can't get Adaway to work and system keeps unrooting...
Is it bc I have to keep the system read only in recovery? Update my partitions to f2fs? Do I need to encrypt/decrypt my device?
As the title says I am unable to boot after flashing Magisk (tried v16 and v15.3). It boots fine without magisk but of course no root and no custom recovery. Any help would be appreciated. Didn't have any problems on the previous stable build.
You need to first flash OOS 5.1 let it boot, then go to fastboot and flash twrp then go to twrp and flash magisk, only way to get root
hello, that's what I did and it worked well
this has happened here since 5.0.4
Try to use lastest blu-spark's TWRP, then flash 5.1 & Magisk without extra boot in the middle.
Things I noticed when upgrading:
A) The latest TWRP for dumpling appears to be broken. I get an error mounting /vendor when I use it. I switched to the previous version (20180309) and the error went away and everything seems to work.
B) You may very well have Xposed installed. If you do, there is an SDK bump between OOS 5.0.x and 5.1.x (26 -> 27). You'll need to disable this module either before you install the update (or assuming you already have) remove the module using something like Magisk Manager for Recovery to remove it (reboot to recovery, install module, run mm from terminal, follow prompts).
-Toucan
ToucanSam said:
Things I noticed when upgrading:
A) The latest TWRP for dumpling appears to be broken. I get an error mounting /vendor when I use it. I switched to the previous version (20180309) and the error went away and everything seems to work.
B) You may very well have Xposed installed. If you do, there is an SDK bump between OOS 5.0.x and 5.1.x (26 -> 27). You'll need to disable this module either before you install the update (or assuming you already have) remove the module using something like Magisk Manager for Recovery to remove it (reboot to recovery, install module, run mm from terminal, follow prompts).
-Toucan
Click to expand...
Click to collapse
It's not broken. The vendor error message is because it was recently updated to work better with Project treble, which uses a hidden partition for the vendor. You can simply ignore the error and it will work fine. Or if you flash a treble ROM, the error will then go away.
I just got the phone. Format it in recovery.
Flash latest blu spark twrp (v.8.73).
Flash the Oos ob06.
Reboot to system. Set the phone, instal apps from Play.
Reboot to Fastboot.
Reflash recovery.
Reboot to recovery.
Flash Magisk 15.3. Reboot to system. OK.
Updated Magisk with Magisk.
Hi, Can anyone help me. in my oneplus 5T after installing new rom it is working smooth but i can't upgrade to new updates. in recovery mode the files seems to be decrypted and cant find any folders where i copied the updation . instead new files are found and can't access and find any of the folders of my own. this happened after i input the security lock. i wiped the entire data and installed new roms still it seems so. somebody please help me to find a solution for this
Redmi Note 5 Pro gets stuck in Mi android logo after flashing any zip from TWRP. I didn't flash lazy flasher though. I flashed zip files like Font zip, launcher zip and all. Is there something else I should be doing ? I have used TWRP to enable camera 2 API plenty of times but this didn't happen. I use TWRP 3.2.1.
Post your problem in respective thread. From where did you downloaded Any zip
Without proper information you don't get proper solutions.
Just reboot to twrp wipe everything and reflash the ROM (previous ROM)
SunilSuni said:
Post your problem in respective thread. From where did you downloaded Any zip
Without proper information you don't get proper solutions.
Just reboot to twrp wipe everything and reflash the ROM (previous ROM)
Click to expand...
Click to collapse
Zip files like Poco Launcher.zip, Google Project Sans font.zip etc. I downloaded these zips from XDA developers site only.
I've got the same problem: using temporary TWRP (haven't used lazyflasher yet) and installing ZIPs ends in the stuck on mi logo. I use TWRP 3.2.3.0 and tried to install Magisk in several versions: 16.0, 16.3 and 16.7, even the manual way by patching the boot image within Magisk Manager. I just like to receive root but want to use Magisk instead of SuperSU. If I'm correct Xposed doesn't work yet, so that might explain why it it stuck at the logo.
MIUI version is 9.6.3.0
how to enable boot sound on note 5 pro
Tischbein said:
I've got the same problem: using temporary TWRP (haven't used lazyflasher yet) and installing ZIPs ends in the stuck on mi logo. I use TWRP 3.2.3.0 and tried to install Magisk in several versions: 16.0, 16.3 and 16.7, even the manual way by patching the boot image within Magisk Manager. I just like to receive root but want to use Magisk instead of SuperSU. If I'm correct Xposed doesn't work yet, so that might explain why it it stuck at the logo.
MIUI version is 9.6.3.0
Click to expand...
Click to collapse
Any solution to avoid it ?
[HELP] Get stuck in bootanimation &then only boot to TWRP after upgrade Magisk & TWRP
I have sucessfully rooted my phone but yesterday when i upgraded Magisk from 16.4 to 17.1 and then flashed lasted TWRP, my phone some how corrupted .
After that I tried to flash Factory Image and boot TWRP portable -> Flash ElementalX 2.05 -> Magisk 17.1 -> VerifiedBootSigner-v8 -> Reboot but my phone get stuck in bootanimation about 5 min and then reboot to recovery. Then it will always boot back to recovery when I reboot.
I have searched here but couldn't find any solution.
I tried to flash ElementalX and TWRP only and my phone booting normally. But anytime I flash Magisk it can't.
Please help me, I don't know what to do next, Thank you and sorry for my bad English. :crying:
I had the same issue as well. I think is is due to the latest TWRP update. I was running Magisk 17.1 with no issues, but once I tried installing the latest TWRP build, I was unable to boot. I even tried connecting to my computer and trying to boot using the boot.img from android. I am currently running the official release of android P. I ended up just doing basically a dirty flash of P over what was already installed to reset the bootloader, radio, etc. I'm going to just end up running the previous version of TWRP until the dev releases something that is confirmed to be stable.
Cozmikk said:
I had the same issue as well. I think is is due to the latest TWRP update. I was running Magisk 17.1 with no issues, but once I tried installing the latest TWRP build, I was unable to boot. I even tried connecting to my computer and trying to boot using the boot.img from android. I am currently running the official release of android P. I ended up just doing basically a dirty flash of P over what was already installed to reset the bootloader, radio, etc. I'm going to just end up running the previous version of TWRP until the dev releases something that is confirmed to be stable.
Click to expand...
Click to collapse
What version of TWRP did you use?
I need some help flashing the latest weekly miuimix a12. I'm experienced and all, been flashing roms before I could walk haha. But this device is really cracking me up.
I've tried flashing the weekly android 12 miuimix through twrp. Twrp vasishath gives a couldn't recognize zip file and twrp nebrassy gives a twrp crash (back to homescreen twrp) upon swiping the rom installation. I think both twrps don't allow installing android 12 rom. So I unzipped the latest weekly, went to fastboot and run the installer bat. This installed the rom for me.
But I don't think the installation was correctly done, since miuimix comes with magisk on board and magisk wasn't installed.
I also can't manually install magisk. I installed the app, patched the boot, flashed boot a and b, even installed twrp and sideloaded magisk.zip but the magisk app is showing n/a.
What did I do wrong, the miuimix a12 flashing or the patched boot flashing. Does someone know how to install an android 12 rom? This device is giving me a headache...
winesh said:
I need some help flashing the latest weekly miuimix a12. I'm experienced and all, been flashing roms before I could walk haha. But this device is really cracking me up.
I've tried flashing the weekly android 12 miuimix through twrp. Twrp vasishath gives a couldn't recognize zip file and twrp nebrassy gives a twrp crash (back to homescreen twrp) upon swiping the rom installation. I think both twrps don't allow installing android 12 rom. So I unzipped the latest weekly, went to fastboot and run the installer bat. This installed the rom for me.
But I don't think the installation was correctly done, since miuimix comes with magisk on board and magisk wasn't installed.
I also can't manually install magisk. I installed the app, patched the boot, flashed boot a and b, even installed twrp and sideloaded magisk.zip but the magisk app is showing n/a.
What did I do wrong, the miuimix a12 flashing or the patched boot flashing. Does someone know how to install an android 12 rom? This device is giving me a headache...
Click to expand...
Click to collapse
I'm not sure if magisk already support a12. The creator of magisk was working on it, with a lot of change like the no more hide feature, but idk if it already out
I was on the a12 supported canary build of magisk, but i guess maybe its to much "canary".
Or is installing miuimix a12 like i did, causing some trouble? By not being able tot flash the zip through twrp and installing with fastboot.
I'm lost on rooting my F3 on A12 as well. I can't do it through TWRP. I can't do it through adb sideload either. Will patching a boot image (not sure which to use for a global F3) and installing through magisk manager work?
Thanks.