Camera failure when booting into Magisk - Samsung Galaxy S10+ Questions & Answers

Hi
My S10+ exynos started behaving strangely: apps crashing, camera failure etc.
Android 10, Magisk 20.4
So I did a factory reset. This indeed fixed the app problem. However, the camera failure still is present. Once booted into regular system, it works flawlessly. When booted in Magisk, there is a black screen and then the message "warning: camera failure". Other camera apps don't work as well.
I did a search here and tried:
Solving safety net cts problem. This is fixed, but didn't solve the camera problem.
Fixed permissions with built prop editor to rw-r-r. Didn't work either.
Of course I deleted cache/data from camera, wiped cache/dalvik in TWRP, went to safe mode with no success
Installed Magisk modules:
Busybox for android ndk
Magisk hide props config
Systemless host
To my best knowledge, I didn't change the configuration before the camera problem appeared.
I am running out of ideas. So please help me. Thanks in advance!

SOLVE: I forgot, I updated TWRP and in my case the TWRP Kernel and system didn't match. I did a
restore of my initial backup in TWRP
flash latest firmware and booted
patched AP file in magisk and flashed this via Odin (follow the stets when installing Magisk)
patched TWRP (used the IanMcd version) and flashed (follow the guide on how to flash TWRP)
Once the system booted I I restored all apps from my TB backup.

Related

[Q] Stuck at boot animation after flashing SuperSU 2.46 in recovery (CM13)

So I completely wiped my Nexus 4 yesterday (everything but internal storage) and clean-installed the 12/29 CM13 nightly + nano Gapps. Everything was working great, installed a bunch of apps from Google Play, etc.
Then this morning I booted to recovery and installed SuperSU 2.46 via recovery zip flash (not via the app), which appeared to flash successfully/with no errors (plus I now see a supersu directory at the root level of my device).
I then rebooted and got stuck at the boot animation. Went back to recovery, wiped dalvik cache and regular cache, rebooted, and I'm still stuck at the boot animation. Reflashed the zip and then wipes dalvik/cache, still stuck.
Any ideas on (a) how to fix without rewiping-reflashing, and (b) how to get root on CM13? Thanks!
EDIT: Forgot to mention my bootloader is unlocked and I have TWRP recovery.
EDIT2: Appears to be solved. I simply deleted the "/supersu" directory in the TWRP file manager and it now boots fine. Unsure if it screwed up hidden stuff, but I didn't have to wipe my system partition, which is a win in my book.
You don't need SuperSU on CM since it has root acces integrated, you just need to enable it under developer options. Format system, cache/dalvik and reflash cm13 and gapps.
Well ****. Looks like I needed to use the newer beta versions of "systemless" SuperSU, like 2.56 or 2.61 for Android 6/CM13.
I wasn't aware that installing 2.46 would cause me to get stuck at bootup, though! That sucks. Still looking for a solution.
Ah I wasn't aware of that. Thanks!
I deleted the /supersu directory, reflashed the 12/29 nightly, wiped caches, and the phone got past the boot animation and booted normally. I'll reboot a few times and see if things are OK.
Saved me from having to format system yet again and redo everything.
Install 2.56b Beta thats working coz it uses systemless ROOT
Do not install 2.56b , because you won't be able to install 2.60+ supersu after that without reflashing system. Install 2.65 beta. It's stable and tested on cm13. I use it myself.
Thank you so much for this - I flashed 2.46 on cm13 on my motog3. I thought I'd lose all my data since I have device encryption and an external sd formatted as internal storage (which is unsupported in twrp for the moto3g, so it isn't accessible for backing up).
I just reflashed the rom and cleared cache and it's back to normal, encryption was fine, all my data is here, and the external sd card functions as well. Saved my ass.
I tried this and it didn't work. I installed supersu while on CM13 and it got stuck at the boot animation of CM. I deleted the /supersu directory reflashed the newest nighlty rom and wiped caches but still stuck at boot animation. I'm on TWRP btw
Doesn't cm13 have an option to enable root under developer settings?

Cannot install magisk v12.0[SOLVED]

So I installed magisk v12 via normal procedure; downloaded then installed from recovery, and the phone didn't boot after. Did not even get past the samsung j5 logo to the bootanimation. I've tried uninstalling SuperSu and then install magisk but didn't help. I "updated" the same rom I was using already and I can use my phone but I would like to install magisk. Anyone?
Phone:J500FN (2015)
Rom: Resurrection remix 5.8.3
Weird, never had problems installing Magisk, even on secondary roms (multirom) when all other fail.
Wipe system, and install the ROM then Magisk, in case that doesn't work make a clean install (wipe system, data, dalvik, cache) and install only the ROM and Magisk (no gapps), if everything is working then install gapps the rest (apps, restore backups etc...)
Your Magisk could be corrupted, try download again and install.
American_Jesus said:
Weird, never had problems installing Magisk, even on secondary roms (multirom) when all other fail.
Wipe system, and install the ROM then Magisk, in case that doesn't work make a clean install (wipe system, data, dalvik, cache) and install only the ROM and Magisk (no gapps), if everything is working then install gapps the rest (apps, restore backups etc...)
Your Magisk could be corrupted, try download again and install.
Click to expand...
Click to collapse
Wiping system will have no effect. Magisk nor supersu Install anything to system.
Restore the untouched boot.img then install Magisk only.
That should be all that is required.
ashyx said:
Wiping system will have no effect. Magisk nor supersu Install anything to system.
Restore the untouched boot.img then install Magisk only.
That should be all that is required.
Click to expand...
Click to collapse
I said to wipe system in case of something installed on system before causing the bootloop (BusyBox, viper4android, etc...). Wasn't referring to Magisk or SuperSu.
That's way I said to install Magisk before gapps, to leave system untouched so it can diagnose the problem.
American_Jesus said:
I said to wipe system in case of something installed on system before causing the bootloop (BusyBox, viper4android, etc...). Wasn't referring to Magisk or SuperSu.
That's way I said to install Magisk before gapps, to leave system untouched so it can diagnose the problem.
Click to expand...
Click to collapse
Well considering he stated that it wouldn't boot directly after installing Magisk, we can deduce that it was likely Magisk that caused the issue.
ashyx said:
Well considering he stated that it wouldn't boot directly after installing Magisk, we can deduce that it was likely Magisk that caused the issue.
Click to expand...
Click to collapse
I can't deduce anything, that's way I recommend to remove any modifications before install.
If you want to debug a problem start removing the variants.
Thanks guys! Problem solved. System wipe didn't do it. It was easier for me to clean install than restore the boot.img at the moment so that fixed it this time. Thank you again. ???

Oneplus 5 shutting down after the OTA

Hello guys, i updated my phone via Oxygen Updater like i always do, i have magisk installed so Oxygen Updater booting into TWRP and flashes the rom.
The thing is when it reboots into the system when screens goes to the lock screen to insert my password the phone shutting down and boots into TWRP. Via TWRP i flashed manually the rom and its boots normally after that but magisk is not installed of course, so when i boot into TWRP flash Magisk and reboot to system the phone shuts down again.
The OTA is 9.0.5 and the twrp-3.3.0-x_blu_spark
Is there a solution for that? I cant live without magisk
Dr4In said:
Hello guys, i updated my phone via Oxygen Updater like i always do, i have magisk installed so Oxygen Updater booting into TWRP and flashes the rom.
The thing is when it reboots into the system when screens goes to the lock screen to insert my password the phone shutting down and boots into TWRP. Via TWRP i flashed manually the rom and its boots normally after that but magisk is not installed of course, so when i boot into TWRP flash Magisk and reboot to system the phone shuts down again.
The OTA is 9.0.5 and the twrp-3.3.0-x_blu_spark
Is there a solution for that? I cant live without magisk
Click to expand...
Click to collapse
Which magisk version? Decrypted or encrypted storage? Did you flashed magisk uninstaller? Which magisk modules or other mods you're running? Did you tried another twrp or without the compatibility.zip of the rom file?
strongst said:
Which magisk version? Decrypted or encrypted storage? Did you flashed magisk uninstaller? Which magisk modules or other mods you're running? Did you tried another twrp or without the compatibility.zip of the rom file?
Click to expand...
Click to collapse
When i boot into TWRP i always have to insert my fingerprint password to Decrypt my data if thats what you mean, i dont really get Encrypted or Decrypted.
Ok i found the problem, i had to use Magisk Uninstaller before flashing the new rom, after i uninstalled magisk i installed the rom and immediately magisk and it booted normally.
Dr4In said:
When i boot into TWRP i always have to insert my fingerprint password to Decrypt my data if thats what you mean, i dont really get Encrypted or Decrypted.
Ok i found the problem, i had to use Magisk Uninstaller before flashing the new rom, after i uninstalled magisk i installed the rom and immediately magisk and it booted normally.
Click to expand...
Click to collapse
Your encrypted if you have to decrypt your data in twrp.
And your issue is remaining magisk/modules, that's why you should uninstall magisk before updating like described here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040 :good:
strongst said:
Your encrypted if you have to decrypt your data in twrp.
And your issue is remaining magisk/modules, that's why you should uninstall magisk before updating like described here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040 :good:
Click to expand...
Click to collapse
Can i format data to decrypt and flash the Disable DM-Verity and then restore my TWRP backup? Or its necessary to start the device from scratch for this to work?
Dr4In said:
Can i format data to decrypt and flash the Disable DM-Verity and then restore my TWRP backup? Or its necessary to start the device from scratch for this to work?
Click to expand...
Click to collapse
If you mean your encrypted twrp of your internal storage = no.
I would start from scratch with decrypted.
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
I used this and solved the problem
I was facing to the same problem today, and the problem was the Magisk version! Same problem for Pixel 3/XL users...
The way you can fix it: Install v19.1 BETA (not the stable)! It should boot up!

Magisk SafetyNet API Error

So I was going well, Install TWRP, Take a Nandroid backup, switch from SuperSU to Magisk
But then when I check SafetyNet and click yes on download propeitary code, It wouldn't work. It kept saying "SafetyNet API Error" over and over. I tried:
-Clearing Data and Cache
-Clearing Dalvik Cache.
-Reflash Magisk.
It wouldn't work, Any help?
SM-N900 5.0 Magisk Root with TWRP Recovery
Northgical said:
So I was going well, Install TWRP, Take a Nandroid backup, switch from SuperSU to Magisk
But then when I check SafetyNet and click yes on download propeitary code, It wouldn't work. It kept saying "SafetyNet API Error" over and over. I tried:
-Clearing Data and Cache
-Clearing Dalvik Cache.
-Reflash Magisk.
It wouldn't work, Any help?
SM-N900 5.0 Magisk Root with TWRP Recovery
Click to expand...
Click to collapse
If you have xposed installed, remove it. And try again.
Or just clean magisk manager app data, and open it with internet connection.
I never installed Xposed
I tried it. It didn't work

Recovery loop after TWRP Restore LineageOS 17.1

Hello there,
I had had LOS17.1 installed on my SGN3. Made a TWRP 3.4.0-1 backup, flashed a stock ROM for a few days and then went for restoring LOS17 again. But restoration wasn't successful.
First "Cannot restore Modem - mounted read only" log show up during restoration. Checking Modem in Mount did not help. So I unchecked modem, which "solved" the issue.
After restore completed, device rebooted but got stuck in what I would call a recovery loop. Black screen -> TWRP splashscreen -> black screen (repeat indefinitely). It can be broken up by entering Recovery (or Download) by appropriate hardware key combo.
But the issue is I cannot get into my system. Installing LOS17 from scratch works but I would like the data.
I tried multiple TWRP versions and fix_rootfs_label.zip I have found here on XDA with no success. Installing fresh LOS17 works and restoring only "data" lets me boot, but the system is not usable (but still trying).
Restoring more than "data" always ended up in the recovery loop.
What was interesting is that when I tried to install GApps to the restored backup, it threw an error saying that this GApps package is for Android 10, while Android 7 (SDK 25) was detected on the system.
Any help?
Thank you!
Did you flash Gapps or no? If yes try nano if no i can't help

Categories

Resources