Hi there. I installed Bliss ROM in my Mi Note 10 earlier this week, and it's doing great, except that I can't run a handful of important apps, because they can tell my phone is rooted. Now, I tried many ways to get rid of this issue (used the MagiskHide, tried to uninstall root within Magisk App..., flashed an uninstall zip via TWRP...). Nothing works. I'd really like to keep using the custom ROM, because Xiaomi's stock ROM sucks, so what can I do? Is there any possibility of unrooting the phone without flashing back the stock ROM?
Maybe help to reset the apps and or flash the boot.img from bliss
You use the uninstall option from the magisk app?
Related
Hello
I have a problem with my Mate. I will try and list the things i did to get to this problem and I hope the information helps solve it.
I wanted to install xposed (first thing I did wrong) so I rooted using King Root (ver 4.8.2) successfully
then unlocked the bootloader using Huawei website
Using Flashy, I flashed TWRP recovery to install xposed (regrets).
After creating back up on TWRP, I tried to flash xposed, didnt work.
I gave up and rebooted phone to android, and i saw i had lost Nav buttons and Notification bar.
Booted back into TWRP and tried to restore my backup. It kept failing at 33% (would post logs but I lost them), I then thought a factory reset would help and it did.
I got the navigation and notification bar, but I soon realised I cannot install apps. I couldn’t install from my SD (apk’s) or from the Play Store.
I can’t install anything on it now. I’ve learnt my lesson not to mess with the inner workings of my device but now I am stuck with EMUI (no Nova or other 3rd party launcher).
Is there any way I can get it back to installing apps as usual? I saw another thread with similar problem (can’t install apps) but I wasn’t sure if I should post there (its old and unattended thread). If I should post this in another thread please point me in the right direction and thank you in advance.
:crying:
I would clear cache and Dalvik cache in recovery then flash back to a stock kitkat recovery, put the correct stock complete kitkat ROM in the dload folder in SD card and do a force update from stock recovery. Once it runs properly again, update to the right ROM you want to run, in the correct order of updates, make sure bootloader is unlocked, root the correct way (not kingroot, use ADB) then seek guidance on what mods work with what ROM. Do not try to root without unlocked bootloader! That ruined it I think.
If you want Xposed, it only partially works in Kitkat, not at all in Lollipop. What do you need with Xposed? I'm running B331 Lollipop now, no Xposed and no real need for it. I do have unlocked bootloader, root and Viper4android and it runs great. I use Smart Launcher Pro but kept Huawei Home (launcher) and theming apps installed so the system is happy but it looks how I want and is good to use.
Thanks for your quick response RobboW, will try that method and let you know if I make any improvement to my situation.
So I have to get a stock KitKat recovery and stock KitKat ROM for that recovery. Do I force an update from TWRP or what? I'll read up on recovering stock Roms and let you know if I make any progress. Thank you for the response though.
Force update with a stock ROM needs to be done from stock recovery. TWRP stops the phone from updating the stock way. The bootloader can stay unlocked if it already is.
It worked exactly like you said. I'm back on Lollipop B324. I can install apps and got the motion control settings back.
Thank you so much RobboW!
You're welcome
OS faults are not so bad if you have access to recovery. It's the ones that make using recovery and ADB difficult that cause the big dramas.
Checked out realme's website and they state that unlocking and flashing roms does not void warranty but rooting the phone does.So what are the possibilities/things one can do with the phone while unlocking it but not rooting it.
Also is there a safe rooting method which doesnt leave traces after unrooting again? So that the device can be used in warranty.
Thanks in advance for any advice.
If you have Realme 5 Pro (not q) then you can still flash custom rom, recovery or basically anything with adb. It's just you won't be able to do root stuff on your phone but you'll need pc. Still you could flash custom kernel, rom, or ota update. Magisk is called systemless root for it does root your system without touching the system files so after uninstalling it and flashing stock rom realme service shouldn't ever be able to tell that your phone was ever rooted. I live in Hungary and my previous Xiaomi phone was installed with custom rom, kernel and Magisk root. Before taking it to Xiaomi service I did a clean flash, reverted everything to stock and warranty was still good to go. That'd be just an example. Don't know Realme how is with these stuff.
greenys' said:
If you have Realme 5 Pro (not q) then you can still flash custom rom, recovery or basically anything with adb. It's just you won't be able to do root stuff on your phone but you'll need pc. Still you could flash custom kernel, rom, or ota update. Magisk is called systemless root for it does root your system without touching the system files so after uninstalling it and flashing stock rom realme service shouldn't ever be able to tell that your phone was ever rooted. I live in Hungary and my previous Xiaomi phone was installed with custom rom, kernel and Magisk root. Before taking it to Xiaomi service I did a clean flash, reverted everything to stock and warranty was still good to go. That'd be just an example. Don't know Realme how is with these stuff.
Click to expand...
Click to collapse
Thank you so much for the prompt and clear reply.Really did clear a lot of stuff for me. Yes I do have realme 5 pro and the problems was with the audio jack output .Its terrible so wanted to flash dolby and / viper . I'll give adb a go then. Thank you again.
Firebolt1994 said:
Thank you so much for the prompt and clear reply.Really did clear a lot of stuff for me. Yes I do have realme 5 pro and the problems was with the audio jack output .Its terrible so wanted to flash dolby and / viper . I'll give adb a go then. Thank you again.
Click to expand...
Click to collapse
You're welcome. If indeed only root void warranty then you're free to flash to your linking almost everything via usb adb. Except for root ofc.
thank you again for the same.
Firebolt1994 said:
thank you again for the same.
Click to expand...
Click to collapse
After installing twrp via adb you can flash stuff from your sd card. Don't forget to always have a backup zip file of your stock rom in case something goes wrong. And don't forget to use backup in twrp for data partition sometimes when you feel you're about to do something risky that might flip your system's stability. I do that all the time ?*
Yep I will.Its a new phone so more of a reason to take precautions .
Firebolt1994 said:
Yep I will.Its a new phone so more of a reason to take precautions .
Click to expand...
Click to collapse
Exactly. Have fun but take care.
bootloader unlock 7 ROOT
Does bootloader unlock will prevent running of Bank Applications?Can this Realme5Pro be rooted and installed Twrp using Kingoroot/
Waiting with thanks.
Please any one give an advice
TWRP
If TWRP is installed via ADB in my unrooted Rm5P will it become rooted and prevent bank applications?
pnsdhrn said:
If TWRP is installed via ADB in my unrooted Rm5P will it become rooted and prevent bank applications?
Click to expand...
Click to collapse
Magisk has an option to hide from those apps, I used it all the time with secure banking apps
If I unlock bootloader and flash TWRP, can this TWRP can be used as my stock recovery further for flashing zips(not custom ROMs)? Also will Bank apps work in this set up without any problems?
Yes, you can use TWRP to flash anything. Yes, bank apps will work as long as you have magisk installed.
I was trying to revert to stock ROM and re-root.
I've tried installing the latest Oxygen stock ROM via TWRP after a format. After initial setup prompts the phone has started encrypted.
I've also tried installing via the fastboot stock ROM. Same thing happens.
Obviously, this doesn't allow me to install Magisk among other things.
Is there a way to prevent the phone from encrypting after a fresh stock ROM install?
Hi there, I'm having no luck finding a solution to my problem anywhere.
I'm using a Galaxy S7 running Oreo (I know, old school), and like many phones, it came with a bunch of apps that can't be uninstalled unless you have root access. So, I installed TWRP, and then Magisk v23, and then I installed a root uninstaller in order to remove the apps in question.
However, I use Revolut and an app for the bank I'm with, and so while my device is rooted, I am locked out of both.
What I want is to have the disable-only apps gone, and my device unrooted and back to normal so I can use Revolut and said banking app.
I believe uninstalling Magisk should unroot the device, but without Magisk installed, I can't boot into the system because of TWRP and the whole dm-verity thing. So, I want to replace TWRP with the stock recovery, which, if I'm correct, should achieve the desired outcome.
I downloaded the exact firmware for my phone from sammobile, and the recovery file can be extracted from it easily, but I don't really know how to go about flashing said file, or even if I can. Odin isn't working for me.
I tried flashing the whole "AP" file via Odin (the latest version), but that restored the device back to it's factory state, disable-only apps and all.
So can anyone help me with this? Or is what I want to do here even possible? I'd really appreciate some input / advice. Thanks!
P.S. maybe you can tell, but I'm kind of a noob, so apologies if I'm overlooking something obvious.
Android's recovery where it doesn't matter whether it's Stock or Custom can't be used to unroot Android if it got rooted by TWRP and/or Magisk this because phone's boot.img got tampered by those: you'ld have to completely re-flash phone's Stock ROM to get rid off of all modifications you applied so far.
Okay then, thanks for explaining.
Just to be clear, what you're saying is that it isn't possible to unroot a device and then restore just its stock recovery (to replace TWRP). You cannot undo modifications made to boot.img and therefore must re-flash the stock firmware?
What I do with unwanted system apps on other android phones is to remove the .apk from /system by booting into recovery and using the shell/adb with u**x commands (actually move them somewhere they can't be seen by the O/S with mv command).
Also when faced with dm-verity, Magisk just modified the boot.img
and changes fstab to take out verify from system mount & patches init and removed /verity_key.
I was able to uninstall Magisk (only phone mod was unlocked boot loader allowing custom boot over usb).
Hello all,
My phone came with ColorOS OOS 12 and I hate it. As soon as I rooted it it started crashing daily, I even reflashed a fresh oos12 image using the local update tool and only granted superuser to one app (solid explorer so I could access user files) and it still crashes. Not to mention all the apps i want to use don't work on android 12 (call recorder, busy box) and no custom recovery.
I've been reading through the forum and I found a downgrade package that looks like its hosted by oneplus: https://oxygenos.oneplus.net/OnePlu...all_2107082125_downgrade_059624cc7298428b.zip
I just wanted to make sure I am doing this correctly...
Do I use the OP Local Update app to flash?
Will I be able to flash TWRP for android 11 afterwards?
Will i need to relock the bootloader?
Should i re-root using the magisk slot b method or wait until its flashed and use TWRP?
Will it try to OTA back to android 12? If so, what's the best method to get on the latest version of android 11?
Thanks for the help.
I am running COS C.62 on my OP9 with root and having no issues. Did you make sure to do all the things in this guide?
Root OnePlus ColorOS 12 OxygenOS Android 12 via Magisk
In this tutorial, we will show you detailed steps to root your OnePlus device running ColorOS 12 Android 12 via Magisk Patched Boot.img file.
www.droidwin.com
Anyway, yes, use the local upgrade APK, put the downgrade file in the root of storage, run it. Reboot. Factory reset and wipe data to clear out any leftover crap (don't restore a backup - if you want to use Clone Phone you can do that but only restore app APKs and messages). When it reboots it should offer the latest OOS11 OTA first. If not, just download it and place it in the root and use the local upgrade function in the settings menu of the OOS11 system updater.
There is no need re-lock the bootloader and if you do, you risk a brick that has to be recovered with MSM Tool.
Root by following the guide I linked. I just went through this yesterday after flashing COS broke mobile data. I have Magisk 24.3 working with denylist, Widevine L1, and SafetyNet passes so I have Google Pay.
EtherealRemnant said:
I am running COS C.62 on my OP9 with root and having no issues. Did you make sure to do all the things in this guide?
Root OnePlus ColorOS 12 OxygenOS Android 12 via Magisk
In this tutorial, we will show you detailed steps to root your OnePlus device running ColorOS 12 Android 12 via Magisk Patched Boot.img file.
www.droidwin.com
Anyway, yes, use the local upgrade APK, put the downgrade file in the root of storage, run it. Reboot. Factory reset and wipe data to clear out any leftover crap (don't restore a backup - if you want to use Clone Phone you can do that but only restore app APKs and messages). When it reboots it should offer the latest OOS11 OTA first. If not, just download it and place it in the root and use the local upgrade function in the settings menu of the OOS11 system updater.
There is no need re-lock the bootloader and if you do, you risk a brick that has to be recovered with MSM Tool.
Root by following the guide I linked. I just went through this yesterday after flashing COS broke mobile data. I have Magisk 24.3 working with denylist, Widevine L1, and SafetyNet passes so I have Google Pay.
Click to expand...
Click to collapse
Thank you, ill give it a try.
First i used the payload.bin method and it was crashing, then i reflashed the latest OTA using the local update tool and used the magisk slot b method. still crashing.
It might have less to do with the root and more with me using root to disable certain apps (youtube, chrome, OP community, google news/podcast/tv) i dont want them on my phone but they might be too tightly integrated. If its still crashing on android 11 ill re-enable them and see if that helps.
aaronbaird1 said:
Thank you, ill give it a try.
First i used the payload.bin method and it was crashing, then i reflashed the latest OTA using the local update tool and used the magisk slot b method. still crashing.
It might have less to do with the root and more with me using root to disable certain apps (youtube, chrome, OP community, google news/podcast/tv) i dont want them on my phone but they might be too tightly integrated. If its still crashing on android 11 ill re-enable them and see if that helps.
Click to expand...
Click to collapse
Okay you're on OOS, not COS. COS doesn't have Google apps by default (but has plenty more bloatware, I just don't use it).
It's certainly possible that disabling Google apps is your problem. If you don't want Google apps, you're better off with a custom ROM that doesn't have them. CalyxOS has a beta for OnePlus 9 and it's totally de-Googled. There's also Lineage.
EtherealRemnant said:
Okay you're on OOS, not COS. COS doesn't have Google apps by default (but has plenty more bloatware, I just don't use it).
It's certainly possible that disabling Google apps is your problem. If you don't want Google apps, you're better off with a custom ROM that doesn't have them. CalyxOS has a beta for OnePlus 9 and it's totally de-Googled. There's also Lineage.
Click to expand...
Click to collapse
ahhhh. i didnt realize there was a difference. I thought OP was just calling their android 12 build ColorOS.
Either way, for custom roms i would have to go back to 11 to flash TWRP right? or can you flash custom roms using fastboot?
aaronbaird1 said:
ahhhh. i didnt realize there was a difference. I thought OP was just calling their android 12 build ColorOS.
Either way, for custom roms i would have to go back to 11 to flash TWRP right? or can you flash custom roms using fastboot?
Click to expand...
Click to collapse
You would need to back to 11 because OnePlus hasn't released working sources for 12. Just use the downgrade package, factory reset, then upgrade to 11.2.10.10 and you'll be good to go for custom ROMs. TWRP isn't used for flashing them, they all generally post their own recovery. StagOS was the best one I used (plus the dev is really responsive when there are issues) and people seem to really be enjoying Nameless but that came out after I went back to stock so I haven't tried it yet.
Before you mess with custom ROMs, make sure that you download the global MSM Tool and make sure you can connect it. Honestly since you have to go back anyway, might as well download and use the MSM Tool to get the device back to 11 anyway.
GLOBAL OnePlus 9 MSM TOOL UPDATED
Frist off Im not responsible for anything that happens to your phone!!! VERY SIMPLE IF YOU ARE BICKED,BOOTLOOPED OR JUST WANT TO GO BACK TO 100% STOCK THIS WILL WIPE ALL DATA!!! AN RELOCK BOOTLOADER OOS 11.2.4.4.LE25AA MUST HAVE QAULCOMM...
forum.xda-developers.com
Easiest way to get it into EDL is adb reboot edl but if you want to practice the key combination in case you can't get into the OS, I found if you open the MSM, check use lite firehose, and click Start before you connect the phone, it has less connection errors because it's waiting for the phone so as soon as you connect the cable, it pops up.
EtherealRemnant said:
TWRP isn't used for flashing them, they all generally post their own recovery.
Click to expand...
Click to collapse
Really??? you can tell I haven't messed with custom roms in a long time.
Thank you for all the help. I'll try it out.
aaronbaird1 said:
Really??? you can tell I haven't messed with custom roms in a long time.
Thank you for all the help. I'll try it out.
Click to expand...
Click to collapse
Yeah TWRP has issues. I soft bricked last time I tried to do anything with it and had to use MSM Tool to get back to working order.