I am wondering if there is any possible way to get a custom recovery (Even if not TWRP) installed onto my pixel 3a running stock 10? I'm rooted, and am concerned about installing xposed modules without any form of recovery. If there isn't any way to get a recovery, is there a method to maybe disable exposed during boot to prevent a bootloop?
Thanks.
dev1334 said:
I am wondering if there is any possible way to get a custom recovery (Even if not TWRP) installed onto my pixel 3a running stock 10? I'm rooted, and am concerned about installing xposed modules without any form of recovery. If there isn't any way to get a recovery, is there a method to maybe disable exposed during boot to prevent a bootloop?
Thanks.
Click to expand...
Click to collapse
Simply said, no. the only working recovery is TWRP. And it only works on Android 9. Also its not installed, you can just boot it and not all features work. Accessing /system is out of the question, because Google introduced some security stuff which makes it read only.
I mean, when you want to test out some specific modules, just backup all your stuff and try out all the modules you need. In the worst case you would have to flash the factory image and restore your data...
I used xposed a lot in the past but im not missing it for a long time. Which are the modules you want to install?
bejunk said:
I mean, when you want to test out some specific modules, just backup all your stuff and try out all the modules you need. In the worst case you would have to flash the factory image and restore your data...
Click to expand...
Click to collapse
Before completely re-flashing, one can try this adb command to remove all magisk modules right?
adb wait-for-device shell magisk --remove-modules
Related
I am actually using this order to reinstall all the system each time a new security revision is out for my Nexus 6P.
Flash Factory image
Reboot
Flash TWRP
Flash SuperSU
Reboot
Flash custom kernel (ElementalX)
Reboot
Flash Xposed
Install Busybox
Click to expand...
Click to collapse
Unfortunately, the "Android is upgrading... Optimizing app x of 193" lasts a loooooong time, and it needs to be made two times: one after I install the factory image (with no data erase), and another time when Xposed is installed.
In order to get a correct setup, I heard that, after SuperSU is installed, it needs to enter the system to do some things. And if I don't recall correctly, the kernel too. Do you think it may be possible to supress some reboot in my list, without affect something, so I can avoid the two long cache creations?
Thank you very much and kind regards.
Hi I just got this hh yesterday and it's already android 8.1 oreo. How to flash costum recovery TWRP?
Flash this one first, but only the recovery, not the boot part. https://forum.xda-developers.com/ga...-j701f-core-nxt-exynos-7870/recovery-t3693009
After that, boot into TWRP, and select to use an image, flash this one choosing 'recovery' image https://forum.xda-developers.com/ga...-exynos-7870/stable-twrp-3-2-1-j701f-t3742401
Note that in order to install some things, supersu or magisk most importantly, but anything that goes on the /data partition, you must explicitly format the data partition, then flash what you want, then reboot. This will factory reset the phone with the exception of what you just flashed. Once you've rebooted, there aren't any TWRPs that can decrypt the data partition so you won't be able to flash anything else or back up /data. It will get you rooted and if you have magisk then you can get xposed from within the magisk manager app.
Good luck.
PantsDownJedi said:
Flash this one first, but only the recovery, not the boot part. https://forum.xda-developers.com/ga...-j701f-core-nxt-exynos-7870/recovery-t3693009
After that, boot into TWRP, and select to use an image, flash this one choosing 'recovery' image https://forum.xda-developers.com/ga...-exynos-7870/stable-twrp-3-2-1-j701f-t3742401
Note that in order to install some things, supersu or magisk most importantly, but anything that goes on the /data partition, you must explicitly format the data partition, then flash what you want, then reboot. This will factory reset the phone with the exception of what you just flashed. Once you've rebooted, there aren't any TWRPs that can decrypt the data partition so you won't be able to flash anything else or back up /data. It will get you rooted and if you have magisk then you can get xposed from within the magisk manager app.
Good luck.
Click to expand...
Click to collapse
So, it is just 1 time TWRP and it will factory reset my phone?
eBuzz_Recon said:
So, it is just 1 time TWRP and it will factory reset my phone?
Click to expand...
Click to collapse
Yes, pretty much.
You have to format the data partition from TWRP in order to have it in a state where TWRP can read or write to it as it isn't yet encrypted. Doing that is a factory reset. After you boot again, the ROM will encrypt the data partition, so unless someone builds a TWRP that can read the encrypted partition in this Oreo build, it will be like that.
Until there's a new build of TWRP, you need to do that format of data to install something from TWRP. You can try installing magisk and let it fail, it might patch the kernel, before failing, and then let you install the magisk manager separately but probably not. Perhaps if you go to that thread and explain, someone can clarify and there might be something you can remove from the magisk install script if it fails when data can't be mounted, so that the kernel will still be patched to accept root. As for xposed, you can install it from magisk manager and most other stuff can be done from the phone while its running.
PantsDownJedi said:
Yes, pretty much.
You have to format the data partition from TWRP in order to have it in a state where TWRP can read or write to it as it isn't yet encrypted. Doing that is a factory reset. After you boot again, the ROM will encrypt the data partition, so unless someone builds a TWRP that can read the encrypted partition in this Oreo build, it will be like that.
Until there's a new build of TWRP, you need to do that format of data to install something from TWRP. You can try installing magisk and let it fail, it might patch the kernel, before failing, and then let you install the magisk manager separately but probably not. Perhaps if you go to that thread and explain, someone can clarify and there might be something you can remove from the magisk install script if it fails when data can't be mounted, so that the kernel will still be patched to accept root. As for xposed, you can install it from magisk manager and most other stuff can be done from the phone while its running.
Click to expand...
Click to collapse
I don't understand the part of kernel patching. Why would I need to patch the kernel? Is there any chance for fail when I try flashing magisk?
Sorry for my noobinity.
eBuzz_Recon said:
I don't understand the part of kernel patching. Why would I need to patch the kernel? Is there any chance for fail when I try flashing magisk?
Sorry for my noobinity.
Click to expand...
Click to collapse
The magisk and supersu scripts do that automatically. As for why, I don't remember, but there's information on it here most likely
https://forum.xda-developers.com/an.../test-disable-defex-security-samsung-t3851487
It has to do with the implementation of security features that Samsung includes. Remember that rooting is in itself an exploit. Those features see something with elevated permissions and are programmed to believe that it isn't meant to be there.
As for failure, you can always reflash the whole ROM with Odin if it doesn't go well, and if that doesn't work, then yes you have a real problem at that point. The link I just put above is perhaps a place to ask which could have better information.
I just installed a module (Active Edge) for the pixel 3 and now my phone is stuck in a bootloop.
Specifically its stuck on a page that says: Can't load Android System. Your data may be corrupt.......
The only options are:
Try Again
Factory Data Reset
I can get it into fastboot mode, but wanted to know if there is a way to disable the modules or uninstall magisk and start over. The instructions that I have found only reference TWRP when uninstalling and I don't have that. Any help is appreciated before I wipe this thing.
Flashing stock boot img will remove magisk
Sent from my Pixel 2 using XDA Labs
I ran into this same issue and solved it, check out my post here:
https://forum.xda-developers.com/showpost.php?p=78075483&postcount=121
thanks guys. I am back into the OS. I used the Sept boot.img as I haven't updated yet. I assume I have to flash the Nov update prior to using the patche_boot.img you linked. In any case, I have a usable phone that is ready for magisk again. Thank you, much appreciated.
In fact, you can just flash Magisk Uninstaller in TWRP then flash Magisk zip again, this will remove all modules installed.
Well i have followed multiple tutorials, and idk what im doing wrong, but everytime i go to boot the patched boot image the phone just bootloops. I have tried different versions of magisk stable, beta, canary, but to no avail. I think i need some help, sorry
Thank you
I had to full wipe to stop that from happening. Then the whole Android flash-all, followed by Patched Boot (with latest Magisk) seemed to work fine. Dunno really what caused it. May be left over user data? This thread may help if there is something from a Magisk Module causing the bootloop. I didn't try it during my install attempts but it may be worth a shot?
Exokan said:
I had to full wipe to stop that from happening. Then the whole Android flash-all, followed by Patched Boot (with latest Magisk) seemed to work fine. Dunno really what caused it. May be left over user data? This thread may help if there is something from a Magisk Module causing the bootloop. I didn't try it during my install attempts but it may be worth a shot?
Click to expand...
Click to collapse
would a adb backup up cause any harm? And about how long did it take you to reflash the phone?
Flash the Magisk patched boot to both slots either with a --slot all command or by flashing to one manually changing slots and flashing to the other all before final system boot.
Dallas2346 said:
would a adb backup up cause any harm? And about how long did it take you to reflash the phone?
Click to expand...
Click to collapse
Sorry, missed this (and hopefully you've already resolved the issue). I don't think doing a back up would cause any harm, although to be fair, I've never used adb backup. I don't think it'll help on a restore though. Reflashing took all of 15 minutes... signing in and getting all my apps up and running again was a little tedious as Titanium wasn't restoring some app data correctly (or the apps themselves didn't 'take'). Overall, not the worst.
Hi guys. Really need your help. Oneplus 7pro ,european version running 10.0.4 software, latest magisk 20.4 i think? and twrp. Everything was running fine until earlier when I installed a system ui overlay (one i've used before) and now my phone is in a boot loop. I can access TWRP, I've run the substratum overlay uninstaller zip and removed all magisk modules but still i'm in a bootloop. I've never had a proper bootloop before and i'm very frustrated. I've googled for the past few hours and removed everything I can think of that could be causing issues. Does anyone have some advice that doesn't end with me losing all my data? I have a backup but its from a month ago. I've never had this issue before so i'm a little stuck. Thanks
Edit. Phone is fully accessible through my laptop I can see all my files and connect to it. I just cannot get it to boot,surely its a simple fix?
Bxperiaz3 said:
Hi guys. Really need your help. Oneplus 7pro ,european version running 10.0.4 software, latest magisk 20.4 i think? and twrp. Everything was running fine until earlier when I installed a system ui overlay (one i've used before) and now my phone is in a boot loop. I can access TWRP, I've run the substratum overlay uninstaller zip and removed all magisk modules but still i'm in a bootloop. I've never had a proper bootloop before and i'm very frustrated. I've googled for the past few hours and removed everything I can think of that could be causing issues. Does anyone have some advice that doesn't end with me losing all my data? I have a backup but its from a month ago. I've never had this issue before so i'm a little stuck. Thanks
Edit. Phone is fully accessible through my laptop I can see all my files and connect to it. I just cannot get it to boot,surely its a simple fix?
Click to expand...
Click to collapse
Can you boot in TWRP? if can try changing slot and boot from it
Mervingio said:
Can you boot in TWRP? if can try changing slot and boot from it
Click to expand...
Click to collapse
Hi,yes I can. Its loading the logo now so i'll wait and see what happens. If that works then what should be the next thing I do?
Edit: Slot B seems to be bootlooping on the logo unless its meant to take a few minutes
Is there a way to recover without wiping my data?
So slot A sits on the caution device rooted screen then defaults to the fastboot rescue mode which allows me to select reboot to recovery which is twrp. From there I have full access to the phone but still not booting to system. Slot B passes the fastboot screen and hangs on the one plus logo just circling around. This is my first rooted phone and I haven't had any problems until now so I'm hoping its something simple because I didnt do anything big to cause it. Hopefully someone has some insight.
Can I just sideload the current version of OOS i'm running using TWRP and not lose my data?
Bxperiaz3 said:
Can I just sideload the current version of OOS i'm running using TWRP and not lose my data?
Click to expand...
Click to collapse
Yes
MrSteelX said:
Yes
Click to expand...
Click to collapse
Will I lost root or relock the bootloader? I'm trying to find the least destructive way to get back to what I had which was oos 10 with twrp and magisk.
Uninstalled magisk and was able to reboot. However reflashing it as i want to retain root makes it bootloop again. Any possible fix for this that isn't a factory reset and reroot?
I can't get substratum or substratum themes to work on any rom or stock, nothing happens after reboots.....or everything turns this weird orange theme. Then one time it corrupted the whole OS and I had to wipe.
try to Dirty flash the same Oxygen version
it will not Wipe your Data or internal storage
i6rb said:
try to Dirty flash the same Oxygen version
it will not Wipe your Data or internal storage
Click to expand...
Click to collapse
Thanks, i'll try this. Will I need to install TWRP again once I do this or is it unaffected?
Tried to dirty flash the same stock rom from TWRP but I don't think it did it properly. Can I dirty flash stock rom, flash magisk then try reboot to system?
Any help greatly appreciated.