My nandroid backup screws my Nexus everytime. I backed my Nexus first with TWRP, restored the backup after installing franco kernel and supersu just to check and behold it 'failed to restore system' don't exactly remember the code. It was 25x. I flashed the factory image, installed CWM, installed SuperSu made the backup installed the same kernel and installed xposed. Xposed caused my device to be caught in a soft brick so i restored the backup again and, it again failed to restore system. What exactly am i doing wrong.:silly: Im tired of having to restore factory images.:crying:
I think I've found the problem. :good:
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. ???
Hi All,
I'm running the latest AICP 13.1 nightly on my Moto G4, rooted with SuperSU. My issue is that Titanium Backup throws an error when launching showing: "Sorry I could not acquire root privileges... This attempt was made using the "/system/bin/.ext/.su" command""
Starting a terminal and switching to root prompts SuperSU to ask to grant permissions and is successful. Same with busybox or the official TWRP app.
I've done a lot of digging and I'm at a bit of a loss. The only thing that seems somewhat odd is that busybox, SuperSU, and the Official TWRP App are all installed on the internal storage while Titanium Backup installed to the SD card. Moving Titanium Backup to the internal storage doesn't change the results though. The choice of where to install the apps wasn't made by me so I'm not sure what decides that.
TIA!
Seems like the next nightly of AICP fixed this, so I don't really know what the core issue was.
bra1niac said:
Hi All,
I'm running the latest AICP 13.1 nightly on my Moto G4, rooted with SuperSU. My issue is that Titanium Backup throws an error when launching showing: "Sorry I could not acquire root privileges... This attempt was made using the "/system/bin/.ext/.su" command""
Starting a terminal and switching to root prompts SuperSU to ask to grant permissions and is successful. Same with busybox or the official TWRP app.
I've done a lot of digging and I'm at a bit of a loss. The only thing that seems somewhat odd is that busybox, SuperSU, and the Official TWRP App are all installed on the internal storage while Titanium Backup installed to the SD card. Moving Titanium Backup to the internal storage doesn't change the results though. The choice of where to install the apps wasn't made by me so I'm not sure what decides that.
TIA!
Click to expand...
Click to collapse
I've been running rooted CRDroid 9.0 (with Magisk and No_Verity) for years and wanted to go back to Oxygen, so I downloaded OnePlus5Oxygen_23_OTA_068_all_2006012224_c7a6016 and updated my TWRP to 3.4.0.0. I followed the instructions - took a TWRP backup, flashed the Magisk uninstaller, did a full wipe (dalvik-cache, cache, system, vendor and data) and then tried to flash the ROM. I got an error due to the compatibility file. So, I tried to restore my TWRP backup and am now getting bootloops.
The instructions say I have to remove the compatibility file on my device, but I can't because of the bootloops.
Can anyone please help me to either get my TWRP backup successfully running or successfully flash Oxygen 10?
Thank you for any help!
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.