I have flashed Paranoid Android ROM 7.1.2. I want to root my phone. I tried to flash the latest version of SuperSU via TWRP, but when I reboot it keeps looping into TWRP no matter what I do. Then I have to flash the ROM's boot image again to get into the OS. The phone does not root. Am I doing something wrong here?
Related
I've tried asking this question on other threads but no one is replying.
I have installed the official OOS4.0 through TWRP. I was on a CM13 ROM so I flashed the full 3.5.4 zip and then the 4.0 OTA directly after. Then I flashed SuperSU but I guess it didn't work because I don't have root access.
Now I lost access to TWRP as well. So I tried to reflash TWRP through my Mac and though the process runs smoothly, whenever I boot into recovery, it's still stock.
Is there anything I can do to regain TWRP access through a MacBook?
Hey, guys, my phone is stuck on a bootloop after downgrading from LineageOS 13 to spring 4.4.2, and back to anything pass 4.4.2.
I have twrp 3.0.3 TWRP-3.0.3-0-XPerience-LPAS23.12-21.7-1-GHOST-UNOFFICIALv2.img installed. I did a clean wipe before trying to get out of 4.4.2. I also tried to restore my CM13 twrp restoration and i am still stuck in bootloop. Bootloop is will be gone when I flash the flashable 4.4.0 zip. But I want my android 6.0 back.
anyone know what I am doing wrong?
solved by manually flashing to 5.1 system and recovery, then flashing twrp and lineageos13 zip
Hi all.
i previous had TWRP installed and the latest open beta but temporarily went back to stock recovery to fix a dm-verity issue. Now, whenever i fast boot flash TWRP it doesn't stick. every time it boot into the OS it seems to revert to stock recovery.
after doing multiple flashes only 2 of them actually asked me if i wanted to change the read write permissions, the other times it just booted into TWRP without a promt.
any suggestions?
on a side note, if i was to get it to boot into TWRP then wipe and install Paranoid Android might that get it to stick?
Thankyou.
chowchillacharlie said:
Hi all.
i previous had TWRP installed and the latest open beta but temporarily went back to stock recovery to fix a dm-verity issue. Now, whenever i fast boot flash TWRP it doesn't stick. every time it boot into the OS it seems to revert to stock recovery.
after doing multiple flashes only 2 of them actually asked me if i wanted to change the read write permissions, the other times it just booted into TWRP without a promt.
any suggestions?
on a side note, if i was to get it to boot into TWRP then wipe and install Paranoid Android might that get it to stick?
Thankyou.
Click to expand...
Click to collapse
I had the same problem so I flashed it TWRP again then flashed another ROM and it stuck. I have no idea why it does that either.
chowchillacharlie said:
Hi all.
i previous had TWRP installed and the latest open beta but temporarily went back to stock recovery to fix a dm-verity issue. Now, whenever i fast boot flash TWRP it doesn't stick. every time it boot into the OS it seems to revert to stock recovery.
after doing multiple flashes only 2 of them actually asked me if i wanted to change the read write permissions, the other times it just booted into TWRP without a promt.
any suggestions?
on a side note, if i was to get it to boot into TWRP then wipe and install Paranoid Android might that get it to stick?
Thankyou.
Click to expand...
Click to collapse
Flash SuperSU or magisk before booting to system...and it Will stick...
Recently tried to install the new magisk update the two ways possible, by patching the boot.img and by installing the .zip file, both which have ended in failure, I am on Google Pixel (Google store version) Android O, running ElementalX kernel, when trying to install the .zip file I get an error about not being able to mount the system (twrp) I tired to manually mount the system and flash the .zip and still nothing. I used to clean boot.imgs and tried to patch them(this worked) but when I flashed them to the system slots and booted I still did not have Magisk.
Maybe??
Since I'm on a completely different device, I'm not sure, but what worked for me on 6p was when app(13) asked, do u want to update to 14?; I select yes, (recommended option) let it install then boot into recovery and flash my kernel again. I'm running flash kernel on superxe Oreo rom. That's what worked for me otherwise it wouldn't boot since I'm on f2fs file system. Hopefully this might help.
After successful installation i am stuck after boot screen animation, htc 10 Android 7 stock rom
Aftab_khatri said:
After successful installation i am stuck after boot screen animation, htc 10 Android 7 stock rom
Click to expand...
Click to collapse
Booting in recovery and reflashing custom kernel fixed this issue for me on Nexus 6p after successful installation of Magisk 14. Maybe this might help (hopefully).
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.