Database Users

Can you install Custom ROM without Root?

Since I lost my Magisk root because everytime I installed it the home screen would be black and various thing stops working (Media storage, TouchWiz, Contact Storage apps, etc.)
However I still have TWRP Recovery on my phone (I installed it before switching to Magisk and Magisk wouldn't work later) The question is... Can you still install a custom rom without a root?

Northgical said:
Since I lost my Magisk root because everytime I installed it the home screen would be black and various thing stops working (Media storage, TouchWiz, Contact Storage apps, etc.)
However I still have TWRP Recovery on my phone (I installed it before switching to Magisk and Magisk wouldn't work later) The question is... Can you still install a custom rom without a root?
Click to expand...
Click to collapse
You don't nedd root to install a rom, just do a simple wipe from twrp, seems like you made dirty flash without wiping.

Mohamedkam000 said:
You don't nedd root to install a rom, just do a simple wipe from twrp, seems like you made dirty flash without wiping.
Click to expand...
Click to collapse
Thank you! Now I installed Resurrection Remix and for some reason Magisk somehow worked again

Can't install Magisk - Phone boot only if TWRP is flashed

Hi all
I experience kinda weird behaviour with my OP6T.
I wiped and upgraded to Android 10 a few days ago (10.3.1). I installed TWRP and immediatyl flashed Magisk using @mauronofrio all-in-one tool. I boot up, installed what I needed and all was going good.
By using the phone I noticed that in drawer there was 2 file manager app: one I think was from Google. So I downloaded an uninstaller and deleted it. After that I discovered that, without "File" (app name) I was unable to give folder access to Poweramp scan function (it was just saying the File app keep crashing).
I tried to install it again but nothing.
Now, the good stuff. Keep in mind root was working good. I also successfuly rebooted phone multiple time with no issues.
After I tried to install File app, I restarted my phone and, surprise, it keep stuck on bootloader warning screen for like 30 seconds and after it goes into recovery (TWRP).
I tried to flash recovery again together with Magisk but nothing. Same result (sometimes it wasn't even boot in TWRP but standard fastboot screen). In the end, I tried just flashing TWRP without Magisk and surprise: it booted. Without root of course.
I did some other tests, tried again (including trying to boot from slot B but that doesn't work and no decrypt message appear).
I don't understand what is going on.
What can I do further ? On Android 9 I experienced something like that but with a normal TWRP/Magisk flash it was returning all normal. It's strange because the advice from AIO says to flash TWRP and Magisk otherwise I brick the phone.
Recap:
Only TWRP installed on partiton A/B -> Phone boot with no root
TWRP (partion A/B) + Magisk (only partition A ?) -> Phone doesn't boot and go in recovery
Thanks

Maybe some modules? It's not a problem related to the tool, to the TWRP or Magisk, maybe you added some module that made the device crash at the start

mauronofrio said:
Maybe some modules? It's not a problem related to the tool, to the TWRP or Magisk, maybe you added some module that made the device crash at the start
Click to expand...
Click to collapse
Any way to see the installed modules from TWRP ? I also used Magisk Uninstaller but still nothing.
BTW, going to /data/adb/ I don't have any modules folder so I think nothing is installed.

rootgen said:
Any way to see the installed modules from TWRP ? I also used Magisk Uninstaller but still nothing.
BTW, going to /data/adb/ I don't have any modules folder so I think nothing is installed.
Click to expand...
Click to collapse
So maybe is something else

mauronofrio said:
So maybe is something else
Click to expand...
Click to collapse
Something or not, I think I will stick back to previous android version.
Just a question: why while flashing TWRP it says partion A/B are being patched while only A (or current boot) seems to correctly work (where by correctly work I mean asking for decrypt message is shown) ?
Any help is appreciated.
Thanks

rootgen said:
Something or not, I think I will stick back to previous android version.
Just a question: why while flashing TWRP it says partion A/B are being patched while only A (or current boot) seems to correctly work (where by correctly work I mean asking for decrypt message is shown) ?
Any help is appreciated.
Thanks
Click to expand...
Click to collapse
The installer patch both slots regardless of everything

Hmm, I might have missed it but after you flashed trwp to your phone did you reboot back to recovery then install root.. just asking..

My device is stuck at fastboot after rooting it and updating Magisk

I'm a total noob at rooting. I tried rooting my Xiaomi Redmi Note 7 today and everything was going surprisingly well until I decided to reboot my device.
My device is now stuck at fastboot, this may have been caused because I updated Magisk.
I can access TWRP but don't know what to do with it. I don't care about my data, I just want my device to work again.
Could anyone suggest any solutions? Thank you in advance!

Did you try rebooting it fron twrp?. twrp >reboot>reboot into system.

Anon-cross said:
Did you try rebooting it fron twrp?. twrp >reboot>reboot into system.
Click to expand...
Click to collapse
Yeap, didn't work.
I just flashed the stock ROM using MiFlash and it worked fine.
Half a hour later, I messed up again and stuck at fastboot for a second time, so I flashed the stock ROM once again and it works like a charm now.
My second failure made me realize what the problem was (well, kind of).
So, the first time I got a bootloop, I thought that it was due to the fact that I had updated Magisk (I read some similar issues online, that's why I thought so).
But that's not the case because the second time, I installed the latest version of Magisk and the same thing happened.
So, the only action that could have caused the bootloop, which was performed both the first and the second time, is the removal of a system app using System App Remover.
I clearly removed something that I wasn't supposed to. It was one of those system apps but don't know exactly which one cause I removed all of them in bulk and then tried to reboot:
GetApps (com.xiaomi.mipicks)
Games (com.xiaomi.glgm)
Mi Credit (com.xiaomi.payment)
Thanks for helping, I hope my answer helps someone else.
My only problem now, is that I'm unable to install updates to the stock MIUI ROM, but that's fine, rooting the device was worth it anyway.

I faced the same problem today
Install twrp ,root and install system app remover
delete some apps i did not need it
when i reboot the phone stuck at fastboot
I reboot to twrp and do a factory reset, format data didnt help
Return again to recovery and unroot
The phone boot to system
I dont understand why this happened because i
remove the same apps before with xiaomi adb fasboot tools didnt face any problem

Aures Batna said:
I faced the same problem today
Install twrp ,root and install system app remover
delete some apps i did not need it
when i reboot the phone stuck at fastboot
I reboot to twrp and do a factory reset, format data didnt help
Return again to recovery and unroot
The phone boot to system
I dont understand why this happened because i
remove the same apps before with xiaomi adb fasboot tools didnt face any problem
Click to expand...
Click to collapse
Sounds strange.
I thought it was the removal of specific apps, but could it be the System Apps Remover that causes the issue?
I wonder if using Titanium would make any difference but I'm not willing to risk it for a third time, I'm good now.

Test orangefox, maybe the older magisk 19.4 and the magisk module debloater.

[FIX] Flashlight and Camera not working after updating rooted 5T to OOS 10.0.0

After updating my 5t from OOS 9.0.10, it was rooted with magisk (20.4) plus some magisk modules and EdXposed framework then i did a dirty update like this:
- installed the OOS 10.0.0 firmware zip through TWRP (without first uninstalling magisk with magisk uninstaller zip)
- then i flashed magisk zip
- wiped cache/delvik and restarted, after what seems like eternity (long boot), the phone booted with Android 10 but flash and camera stopped working.
After looking for some solution online i didn't find anything helpful so i did this:
- Reboot to TWRP recovery and uninstall magisk with magisk uninstaller zip then i wipe cache/delvik and reboot to system (you loose twrp on this one cuz uninstalling magisk restores stock boot image which replaces TWRP with stock recovery)
- When the phone boots up normally everything (flash, camera) should start to work fine
- Now reboot to fastboot and flash TWRP recovery (you need pc)
- After it finishes flashing don't start the phone instead do this press volume key until the above title says recovery and press power button to boot to recovery
- When you are on TWRP install magisk zip and clear cache/delvik then reboot to system
- Now flash and camera will work and you can reinstall your previous magisk modules
- Reboot so your modules get activated
- Done! That's all
Sent from my ONEPLUS A5010 using Tapatalk

nadiration said:
After updating my 5t from OOS 9.0.10, it was rooted with magisk (20.4) plus some magisk modules and EdXposed framework then i did a dirty update like this:
- installed the OOS 10.0.0 firmware zip through TWRP (without first uninstalling magisk with magisk uninstaller zip)
- then i flashed magisk zip
- wiped cache/delvik and restarted, after what seems like eternity (long boot), the phone booted with Android 10 but flash and camera stopped working.
After looking for some solution online i didn't find anything helpful so i did this:
- Reboot to TWRP recovery and uninstall magisk with magisk uninstaller zip then i wipe cache/delvik and reboot to system (you loose twrp on this one cuz uninstalling magisk restores stock boot image which replaces TWRP with stock recovery)
- When the phone boots up normally everything (flash, camera) should start to work fine
- Now reboot to fastboot and flash TWRP recovery (you need pc)
- After it finishes flashing don't start the phone instead do this press volume key until the above title says recovery and press power button to boot to recovery
- When you are on TWRP install magisk zip and clear cache/delvik then reboot to system
- Now flash and camera will work and you can reinstall your previous magisk modules
- Reboot so your modules get activated
- Done! That's all
Click to expand...
Click to collapse
Can I give link for the ROM you flash?

zhukry said:
Can I give link for the ROM you flash?
Click to expand...
Click to collapse
[emoji1428] https://otafsg1.h2os.com/patch/amaz...ygen_43_OTA_067_all_2005130057_6b923fb89f.zip
Sent from my ONEPLUS A5010 using Tapatalk

Thanks for this! The same thing happened to me. You saved me hours of troubleshooting!

Thanks VoltaGe86 - been driving me mad for a week now and your advice has solved all my camera & flashlight problems AND YouTube and Tasker not connecting.
Appreciate your post!

i know i am late but
if anyone else is facing this problem then try installing open camera and try going to stock rom(old one) do rom update with stock recovery

I've been experiencing the same loss of camera and torch/flashlight after upgraded my Oneplus 5T to the latest firmware (10.0.0/10.0.1).
It was not solved by using magisk uninstaller and downgrading.
Additionally, the phone will not auto upgrade to new releases, whatever rom I install it always insists 'Your system is up to date'.
After wasting far too many hours I've found that the camera works on stock roms up to Oxygen 5.1.7 (Android 8 Oreo), but stops working when flashing the next update: Oxygen 9.0.0 (Android 9 Pie).
I've addtionally tried unbricking the phone using dumpling_43_O.36_180613_unlocked.7z and have attempted to upgrade with OEM Unlocking turned off.
Any ideas as to what might be the cause would be super welcome!
I'm wondering if the underlying paritioning could be damaged in some way?

Phone stuck in bootloop after updating Magisk

I'm running Android 10 with EvoX rom and after last update of Magisk to 21.4 the phone is stuck on bootloop. After going to recovery and uninstalling Magisk I have the same problem, it's still in bootloop. What can I do to fix the problem?

Dirty flash ROM or if 1st step doesn't work factory reset and install everything

Same here. I don't want to do a factory reset.
I tried to:
- uninstall Magisk from twrp
- flash the boot.img of the rom
- flash the previous version 21.2 of magisk
but none of this worked!

I have the same Issue. Havoc 3.9., Magisk 21.4.
I tried to dirty flash the rom, uninstall magisk 21.4 via twrp, and flashing 21.2.
Didn't help. Occassionally I got into the system, but the screen is a bit more white than usually, I can type in my lock password, but after this, System UI fails.
Yesterday I flashed the fix for safetynet passing after the latest update, which made it work again, and I remember that at the relevant magisk forum, somebody mentioned that would affect System UI somehow. Now I am trying to repair the System UI to see if it works as a solution.

[email protected] said:
Yesterday I flashed the fix for safetynet passing after the latest update, which made it work again, and I remember that at the relevant magisk forum, somebody mentioned that would affect System UI somehow. Now I am trying to repair the System UI to see if it works as a solution.
Click to expand...
Click to collapse
What fix are you talking about? Where can I acquire it?
EDIT: In my case the bootloop was caused by the Systemless Xposed Framework module v90-beta2 by rovo89 (packaged by topjohnwu). Disabling that module allowed me to boot normally.

en_ha87 said:
I'm running Android 10 with EvoX rom and after last update of Magisk to 21.4 the phone is stuck on bootloop. After going to recovery and uninstalling Magisk I have the same problem, it's still in bootloop. What can I do to fix the problem?
Click to expand...
Click to collapse
Same problem occur with me ,i just unistall 21.4 and indtal 20.4 veraion but nothing happens then i just wait for 5-10 min on bootloop screen and it starts processing it's updating my new boot image ... This thing happens when i update my miui after completing the process i finally see my homescreen

Lars0n89 said:
What fix are you talking about? Where can I acquire it?
EDIT: In my case the bootloop was caused by the Systemless Xposed Framework module v90-beta2 by rovo89 (packaged by topjohnwu). Disabling that module allowed me to boot normally.
Click to expand...
Click to collapse
How can you install that Module from TWRP?
That i remember i never installed it, it's automatically loaded with magisk?
To solve this problem i had to format the phone, installing the OS again and also magisk v21.2. But Today i got the same problem... so maybe is not the versione of magisk. But I don't know of to solve it.
I tried also the sotck boot.img, but it stays some seconds on the boot screen of lineage OS and then reboot again stucking on Mi logo.

i also had to install stock rom, lost all the data on the phone. today i have to install custom rom, and will probably pass on the magisk, i don't need sh**t like this happening again.

I had to reinstall the rom from scratch, and needed to format data partition too. After flashing my ROM back, I installed magisk 21.2 and it works great.

I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system

flavioggl said:
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
Click to expand...
Click to collapse
Could you help me i got into a bootloop after doing the magisk direct update from the app. My discord is : SneezeOnYou2#8507
I believe that i have a backup in twrp just dont know how to flash or uninstall or what ever to do i dont want to lose my data. I can record my screen if you add me on discord.

flavioggl said:
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
Click to expand...
Click to collapse
Thank you, brother. It was a simple solution but I forget to do that. After wasting 2 hours finally able to solve the problem. Thanks again.