HELP!!! - SuperSU

I was rooting a device for the first time, a new tablet SM-T385i. I got twrp and installed it using Odin(AP). From there I could boot into twrp recovery. I put the Supersu file into my downloads folder and booted fro the first time into twrp. I couldnt find any of the file folders in the install section so I went to mount and checked system. Still nothing. I tried to check data but didnt work. i panikced and went to reboot system. It got stuck on the boot screen over and over, showing the samsung logo. then i booted into twrp and wiped the data. Then i reinstalled twrp and i could see my tab on my pc now. Put supersu again and flashed with twrp. iT SAID MIGHT TAKE SOME TIME BUT then it just switched off. i TRIED TO BOOT INTO TWRP BUT FAILED. i went to the downloader again and installed twrp again. still shows the boot logo and switches off again. at this point i can go to the downlader and i can see the logo thats all. HELP!!!!!!!!!!!!!!!!

Search your rom/other one (custom OS) and install it via TWRP. After that (when your rom booted normally) - try to install Magisk.
https://forum.xda-developers.com/showthread.php?t=3747480
Sent from Redemi 4X (Resurrection Remix based on OS 7.1.2)

Related

s3 mini with a twrp 2.8 that hangs

I had cm12.1 on it and only wanted to clear settings in android.
It had to reboot and stuck at twrp begin screen that keeps flashing.
Only odin works now and tried installing another twrp and cwm too, all succesfull but still that twrp boot logo flashing even when cwm installed.
Normally i can manage but have no idea now. If recovery worked it was fine but just thru odin seems that twrp is write potected almost.
Any clues someone
rebooted manually also, uncheckedauto reboot box after flashing twrp new rom
nothing, still stuck

Help with Magisk root Pixel 2 factory Android 9.0.0 installed

Hello,
I have been struggling to root my device. I have not wiped and rooted it in some time and now coming back to it again magisk keeps breaking my device.
I have clean flashed the latest android 9.0.0 build. I have flashed TWRP custom recovery 3.3.0 successfully. I have tried to flash magisk 3 times now and afterwards my phone wont boot. I originally used magisk manager to get the latest zip and patch my boot image. I then rebooted to to bootloader and ran fast boot flash boot patched_Magisk.img. This wiped out my twrp recovery and my phone wouldn't boot, i couldn't get back into twrp recovery. I reflashed latest 9.0 build and wiped everything. I flashed twrp again and tried to flash Magisk 20.0 from recovery. It was successful but again i couldn't boot into my phone and it eventually restarted back into recovery which i still had twrp this time. I then tried it again with 19.3 and the same thing happened. can anyone tell me what is going on here? What am I missing? I have been having reflash factory 9.0 build each time just to get it to remove the patched boot image and boot up again.
Was either the TWRP version or the two check boxes it has now to install twrp app as system. Installed 3.2.3-1 and didnt install the twrp app through the recovery check boxes and it worked.

After booting to TWRP when i reboot back to system, it is stuck in boot menu

Hello !
I recently installed Pixel experience rom (android 10) in my redmi 4x. I used TWRP as my custom recovery. Everything was fine. Rom installed successfully and everything was working. The problem is : now that I have this rom installed I boot to TWRP( no problem till now) but when I exit TWRP (i am not installing or wiping anything, just booting to TWRP and then exiting TWRP) by going to reboot and then to system it shows the Google icon and then it keeps on loading forever.
Anyone please help out
Try lastest firmware and clean reflash

S10 stuck in bootloader loading screen after trying to flash Magisk to boot partition from the App

So basicly, I updated the magisk app and it said I have an update available.
I was on a custom rom named Blastui rom: https://forum.xda-developers.com/t/...-1-1-odex-v3-45-aroma-like-a-ferrari.4200153/
at the same time, i had twrp installed on recovery.
So i didn't want to earrase that.
Bec. of that i didnt check the "Install to recovery" option in the magisk app and flashed it.
After the flash, i tried rebooting, which failed on the bootloader loading screen.
Then I tried booting into recovery. didn't work.
Then I tried booting into download mode. didn't work either.
it just keeps rebooting in a period of like 5 minutes and then gets stuck on bootloader.
Pls help its my main phone

Stuck in boot loop

Hi, I got a situation here. I had to reinstall the rom in my Note 7 Pro after nearly 2 years from teh last time I had to do it.
Unfortunately, I had no idea that the new Magisk version can't be flashed by custom recoveries anymore. I simply flashed my rom using Orange Fox, restarted to the system, used the cell for 2 days, installed everything I needed, and yesterday I downloaded the latest 24310 Magisk version, flashed it using my custom recovery, and restarted in the system again.
Magisk greeted me with a message that it needed extra setup to be fully functional. I restarted in recovery, nothing happened, restarted to system, Maghisk still stuck in the need extra setup to be functional. I resolved to uninstall it using the app, got an error message in the console, tried restoring images, another error. Tried to reboot to recovery to try to reflash magisk, no more recovey, gone. Used adb to reflash recovery, rebooted to it, now I have a message that says Error opening: 'data/adb/magisk' (operation not permitted). Tried to use the Orange Fox option to remove Magisk, got some error messages Error opening: 'data/adb/magisk' (operation not permitted), but it said it was done. Tried to reboot, stuck in boot loop, back in recovery, dirty flashed my actual ROM, still stuck in boot load.
Any way to delete this locked magisk folder to try to completely remove magisk and try to reinstall it the correct way now? Or the only solution is a complete reinstallation of the ROM formatting all partitions? I haven't tried it yet because after 2 years of doing this procedure I barely remember how to do a clean install correctly.
Blackdragonbird said:
Hi, I got a situation here. I had to reinstall the rom in my Note 7 Pro after nearly 2 years from teh last time I had to do it.
Unfortunately, I had no idea that the new Magisk version can't be flashed by custom recoveries anymore. I simply flashed my rom using Orange Fox, restarted to the system, used the cell for 2 days, installed everything I needed, and yesterday I downloaded the latest 24310 Magisk version, flashed it using my custom recovery, and restarted in the system again.
Magisk greeted me with a message that it needed extra setup to be fully functional. I restarted in recovery, nothing happened, restarted to system, Maghisk still stuck in the need extra setup to be functional. I resolved to uninstall it using the app, got an error message in the console, tried restoring images, another error. Tried to reboot to recovery to try to reflash magisk, no more recovey, gone. Used adb to reflash recovery, rebooted to it, now I have a message that says Error opening: 'data/adb/magisk' (operation not permitted). Tried to use the Orange Fox option to remove Magisk, got some error messages Error opening: 'data/adb/magisk' (operation not permitted), but it said it was done. Tried to reboot, stuck in boot loop, back in recovery, dirty flashed my actual ROM, still stuck in boot load.
Any way to delete this locked magisk folder to try to completely remove magisk and try to reinstall it the correct way now? Or the only solution is a complete reinstallation of the ROM formatting all partitions? I haven't tried it yet because after 2 years of doing this procedure I barely remember how to do a clean install correctly.
Click to expand...
Click to collapse
Reflash the stock unrooted boot.img of your room in bootloader. Use adb
Fastboot flash boot boot.img
Similar problem here...
I tried reflashing stock recovery and stock boot.img - now whenever I reboot it just boots into recovery! I don't seem to be able to boot into system any more...
Any ideas?
I'm running AOSIP on a Xiami Mix Mi 3 - I hadn't updated to the latest Magisk in quite some time (since before the app could do it automatically). I have to use the recovery method.
Steps I took are:
Get recovery.zip from my ROM, patched it through the app, then flashed through fastboot. I rebooted while holding down the up arrow to reboot into recovery, then released for the phone to boot.
I got an error after booting that said "there's an internal error with your device" - and it was super buggy, couldn't tap the screen, super slow to load stuff, etc.... I figured it was a magisk issue, so tried to reflash recovery and boot... Not I'm stuck booting into recovery!
Help.
Edit: so - I think it turns out I have one of those RARE xiaomi devices that DOES have ramdisk even though the app doesn't detect it... Go figure. A clean install of the ROM, followed by patching the BOOT image rather than the recovery image - and we're up and running.

Categories

Resources