Related
So about 2 months ago I rooted my phone. I followed the method here:
http://forum.xda-developers.com/showthread.php?t=928160
Everything was ok, until my super user permissions program stopped working. The program opened but its a solid black screen and I cannot give any new program SU permission. At first the programs that already had permission could still have SU permission, but, in an attempt to fix the issue I cleared the program cache and those programs lost their SU permission(like TT and terminal).
Their is a new SU permissions program on the market that I paid for from the same company but I assume because the old one is still installed that it is not showing up for that reason and cannot be opened.
I cannot figure out how to get rid of the original Superuser Permissions program. I have tried every program I could find by surfing forums, I have factory reset the phone... but that SU permissiosn program is still there upon a clean factory reset!
I have the ADB installed on my PC, but when I try to run a remount I get an error that I am not allowed to do that. After my factory reset I tried running back through the walkthrough I listed. Visionary says its temp rooted, but in terminal the SU command says "access denied." I think this all has to do with that bad SU program being in stalled and if I can get that off and install the replacement one I paid for, then the SU could grant access to terminal and I could re-root the phone.
My theory is only speculation. Can anyone tell me how to remove this SU program. Its located in directories that are read only and all the commands I have found to remove it so far have required a rooted terminal command, or ADB remount commands that I cannot use. Please help. Thanks
Couple of things to try. First can you boot into recovery? What Rom are you using if any? Since you already did a factory reset I assume you don't have any data you want to save so I would just reflash a Rom from recovery. I don't remember off the top of my head but I think you hold vol - plus power when booting to get to recovery? Or if your current Rom has the permissions still to boot to recovery from the power menu?
Another thing to try is the "rage" method to gain root. I know there are issues with using visionary after you already have root. So give rage a search and try that. Come to think of it you might just try the rage method first. Let me know how its goin I might be able to help more
Sent from my HTC Vision using XDA App
shortlived said:
First can you boot into recovery?
Click to expand...
Click to collapse
A: Not sure I will try.
shortlived said:
What Rom are you using if any?
Click to expand...
Click to collapse
A: Stock that came on the phone
shortlived said:
I don't remember off the top of my head but I think you hold vol - plus power when booting to get to recovery? Or if your current Rom has the permissions still to boot to recovery from the power menu?
Click to expand...
Click to collapse
A: Again, I will try, but nothing has SU permissions anymore.
shortlived said:
Another thing to try is the "rage" method to gain root.
Click to expand...
Click to collapse
A: I will try this too. I will look on our forum, but since you are familiar with the process maybe you can provide me with a link to make things easier? Would you happen to have a link to the rage method for the G2?
Thanks for the reply!!
Nothing has worked. The original superuser permissions is still installed. I get errors when trying to push files to those read only directories even though ADB.
Any ideas on how I can get everything back to factory settings?
What do you mean "a new SU permissions program that I paid for"?
There's only one SU program that I know of. The only paid one that I know of is just a license file for an upcoming, yet to be released, program. You'll need to be specific in order for this to get resolved but it sounds like you may need to reinstall the SU binaries and the SU program.
To uninstall the current one you just need to go to applications>manage, click on the program and then click uninstall. Then use ROM manager to download and install SU for you.
Thanks for the reply but I am way past that. The OS will not let me uninstall the current SU program. The "paid" SU program is a separate program because it asked me to install the file rather than "update" like the free one says when I open it from the market.
I am very specific in my original post.
Somehow the SU program stopped working. New programs that require SU access were not givign the pop up that allowed me to grant SU access. When I open SU its just a black screen with no options. I cleared the cache to try to fix and this removed SU permissions from all the programs that I had already granted SU permissions to(like terminal). I cannot uninstall the program from the built in manager or any of the several file managers I have tried. I also cannot overwrite the current file by "updating" the existing installed version. I paid the 1$ for the paid version because its a different program all together. My thought process was if android sees it as a separate program, it will install it as a separate program and I can use it independantly of the original non-functioning version. That did not work. It says its installed but the icon is no where to be found and I cannot run it, even from a file manager. The old SU icon(of a ninja) still stays in the program list even after I wiped the phone and dida factory reset.
The point is its going to take some advanced procedure to remove the SU program. Its in adirectory that is read only. It takes SU permissions to make that directory read/write and I cant get SU permissions, even temporarily with visionary or Z7. I have tried ADB and it also says permission denied.
So this is NOT resolved yet.
At this point:
-I have reset the phone several times, each time SUpermissions is still installed when the phone comes back up.
-USB debugging is enabled.
-I have googled possible solutions that all have not worked(using ADB failed, updating the SU program failed, clearing the cahce failed, disabling usb debugging then hooking to cpu and reenabling it and using adb to try and use SU command failed...etc
-using 3rd party apps to uninstall failed
-using other SU apps failed
A rough rundown of my problem is:
Phone is rooted. At some point when I opened a NEW app that would require SU access, the pop up generalted by SUpermissions stopped popping up allowing me to give access. Programs I had already granted SU access to would still work(like terminal and titanium backup). Per someones request I tried to clear the cache. When I did this all the programs that DID have SU access lost SU access and I still could not add new programs to the SU list. I have tried ADB commands, file managers, factor resetting the phone. Nothing works. The SUpermissions program is there when I factory reset the phone as if it is one of the preinstalled apps. Apps tell me that I DO have my phone rooted, but that I still need to allow it SU access. I have not been able to uninstall the SU program and if I could get that program updated/re-installed then I believe that I could get the root access back.
Any real suggestions?(not the "is usb debugging enabled" Tier I troubleshooting steps that I am WAY past)
Thank in advance
Kk do you have s-off and the eng-bootloader? Do you have a custom recovery?
If you have s-off and custome recovery you can back up your rom using nandroid, then do a wipe and install a freshly new rom
Also you can boot into clockwork and try to run fix permissons
If you don't have custome recovery (clock work) you will need to have eng-bootloader to do fastboot commands to flash recovery
Also have for adb make sure debuggin is on and boot into bootloader from there try to do adb commands there
If your able to do so and get access
You can go into adb shell and remount to rw then push a new SU.apk in and reboot and su should work as well
This if you don't remember commands
Adb shell
Su
#mount -o remount,rw /dev/block/mtdblock3 /system
#
Then exit out of shell then do adb push
Adb push (where ever su user location on pc) /system/app
I installed rom manager by clockworkmod, which I believe is the program you were refering too.
I tried to "fix permissions" and it failed there.
How would I reload the stock ROM?
If I backup the current ROM, and reload it, then it will reload it as it is with SUpermissions already installed.
Where can I find a copy of the stock rom that came on the G2?
BTW
I do have S-off, but I did not install the engineering hboot.
Let me know the best way to go about getting a stock rom put back on.
Do you have clockwork recovery, not rom manager, turn off phone hold vol dwn and power.. you should boot in custome recovery all letters should be orange,
If you have that good! Jus go to dev section and download a stock rom that is rooted put in sdcard and boot in cwm recovery go to back up and restore, do a back up after back up is down do a wip/factory reset, when down click install zip from sdcard, then choose zip from sdcard and look for rom that is in sdcard and flash that.. or you want you could also get cyanogenrom too but also get gapps too
You never answered if you could get to recovery. If you really have soff then your fine. So when your phone boots it says s off correct? And what happens with you hold vol down while booting? Even if you dont have clockwork recovery you can still install the original rom which you can find in the forums.
Sent from my HTC Vision using XDA App
when chick the superuser ,it always display "force close"
but other app can be supported to get root permission by superuser.
but ,
when i get the superuser update in the google market,nightmare coming.
well ,i have the same issue like yours.
i try to fix ti anywhere ,but i flash other rom to replace.
do you have the solution?
shortlived said:
You never answered if you could get to recovery. If you really have soff then your fine. So when your phone boots it says s off correct? And what happens with you hold vol down while booting? Even if you dont have clockwork recovery you can still install the original rom which you can find in the forums.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I assume that its s-off. The link that I posted the the root method that I used said that it would root with S-off. The only thing I did not do is install the eng hboot. I assume that the root is done with S-off.
I have not had time to sit and try this yet. I will try soon and get back with my results.
ilostchild said:
Do you have clockwork recovery, not rom manager
Click to expand...
Click to collapse
I know at one point I had it, but as I said I factory reset my phone. I want to make sure that I install the correct app, so who manufacturers clockwork?
If you had the cwm recovery b4 and all you did was a factory reset then you should still have it, only time you lose recovery if you update to official rom or you flashed another recovery, clockwork recovery is made my koush, and rom manager is also made by koush
derricks2 said:
So about 2 months ago I rooted my phone. I followed the method here:
http://forum.xda-developers.com/showthread.php?t=928160
Everything was ok, until my super user permissions program stopped working. The program opened but its a solid black screen and I cannot give any new program SU permission. At first the programs that already had permission could still have SU permission, but, in an attempt to fix the issue I cleared the program cache and those programs lost their SU permission(like TT and terminal).
Their is a new SU permissions program on the market that I paid for from the same company but I assume because the old one is still installed that it is not showing up for that reason and cannot be opened.
I cannot figure out how to get rid of the original Superuser Permissions program. I have tried every program I could find by surfing forums, I have factory reset the phone... but that SU permissiosn program is still there upon a clean factory reset!
I have the ADB installed on my PC, but when I try to run a remount I get an error that I am not allowed to do that. After my factory reset I tried running back through the walkthrough I listed. Visionary says its temp rooted, but in terminal the SU command says "access denied." I think this all has to do with that bad SU program being in stalled and if I can get that off and install the replacement one I paid for, then the SU could grant access to terminal and I could re-root the phone.
My theory is only speculation. Can anyone tell me how to remove this SU program. Its located in directories that are read only and all the commands I have found to remove it so far have required a rooted terminal command, or ADB remount commands that I cannot use. Please help. Thanks
Click to expand...
Click to collapse
Try flashing another ROM or a kernel. this could be an error or corruption in the folder located in the root folder of your phone. Flash a new ROM and try it again but set a backup and see if this error continued to another ROM. Hope I helped
ilostchild said:
Do you have clockwork recovery, not rom manager, turn off phone hold vol dwn and power.. you should boot in custome recovery all letters should be orange,
If you have that good! Jus go to dev section and download a stock rom that is rooted put in sdcard and boot in cwm recovery go to back up and restore, do a back up after back up is down do a wip/factory reset, when down click install zip from sdcard, then choose zip from sdcard and look for rom that is in sdcard and flash that.. or you want you could also get cyanogenrom too but also get gapps too
Click to expand...
Click to collapse
When I hold the vol down button the text is in orange.
I will try this process. I am at work and may not have a lot of time here today. If you can point me to where I might find the stock ROM w/ root that would be wonderful.
I assume that rooted version comes with SU and clockwork etc already installed?
ilostchild said:
Do you have clockwork recovery, not rom manager, turn off phone hold vol dwn and power.. you should boot in custome recovery all letters should be orange,
If you have that good! Jus go to dev section and download a stock rom that is rooted put in sdcard and boot in cwm recovery go to back up and restore, do a back up after back up is down do a wip/factory reset, when down click install zip from sdcard, then choose zip from sdcard and look for rom that is in sdcard and flash that.. or you want you could also get cyanogenrom too but also get gapps too
Click to expand...
Click to collapse
Ok... maybe I was mistaken. When I boot into recovery, it says S-off, and the options I have to choose from are orange, but ALL the text is not orange.
When I go through ROM manager to flash a ROM(which is the stock rom i downloaded that I want to flash) it says I need to have CWR installed and to use the option at the top to install it. When I click that it says its asking for permissions to install, which means I need SU permissions, which is my problem in the first place.
I have the rom loaded on my SD. As I said, the 4 options I have in the initial recovery mode are orange(though the rest of the text is now orange) but I do not know which one to choose. Any advice? Do I have clockwork recovery installed? If not, is their any way to flash a ROM?
derricks2 said:
The only thing I did not do is install the eng hboot.
Click to expand...
Click to collapse
Did someone miss this? I thought you had to have the ENG-Hboot?
But, what do I know, I'm a newb.....
Hey folks, I just updated to .21 and reran rootkeeper. That restored su to /system/bin. I can adb in and get root just fine. However if I run the superuser app or titanium it always fails getting root.
Code:
[email protected]:/system/bin # ls -l su
ls -l su
-rwsrwsr-x root root 22228 2012-05-06 13:22 su
Anyone have any suggestions as to why this is?
Just to follow up. I tried running vipermod, that failed (both option 1 and 3), and I figured I'd boot into recovery and just wipe, but all I get is the "dead android" picture. From what I read, to restore stock recovery I need cwm. To flash cwm, I need root for recoveryinstaller. I have root through adb, is it possible to flash cwm via adb?
I'm really stuck here. All I want to do is wipe and restore this baby to stock.
Try copying the su from system/bin and paste it to system/xbin
run RecoveryInstaller after that to install CWM
Done that already too. No dice.
shadoslayer said:
Just to follow up. I tried running vipermod, that failed (both option 1 and 3), and I figured I'd boot into recovery and just wipe, but all I get is the "dead android" picture. From what I read, to restore stock recovery I need cwm. To flash cwm, I need root for recoveryinstaller. I have root through adb, is it possible to flash cwm via adb?
I'm really stuck here. All I want to do is wipe and restore this baby to stock.
Click to expand...
Click to collapse
The "dead android" is the stock recovery.
You can try Wolf's method to flash the recovery blob.
http://forum.xda-developers.com/showthread.php?t=1622628
or you can go back to .17, root with ViperMod, use OTA Rootkeeper and OTA back to .21
Really? They must have changed the recovery since the HC roms, because I remember this having some options in recovery back then...
Ok, I'll give flashing the recoveryblob a shot. thanks for the help!
Hey, thanks base. It worked perfectly. I was able to get cwm flashed, flashed su+bb, backed up everything with titanium and we're all good. You've been a great help!
Any way to install xposed via Flash fire? If so, link? ?
Yeah. Get the latest zip from arter97's post as well as XposedInstaller.apk (the lollipop version!).
It's something like xposed-v5-krait-blahlblahblah.zip
Reboot into flashfire and flash it, but don't reboot yet! Using either the file manager + "run command" facility in flashfire or a shell via adb, do this:
create a directory /system/app/XposedInstaller with the mode 0755. Then use SafeStrap's file manager to copy XposedInstaller.apk into that directory and set the mode to 0644.
You're done. Reboot and you'll be fine. I'm going to create a zip that does this at some point. I don't know why no one else has.
Just did this myself, so far so good. Heres the exact steps.
Install XposedInstaller_3.0_alpha4 (latest: http://forum.xda-developers.com/showthread.php?t=3034811)
Using Flashfire v21
Clear Cache
Backup Boot, Recovery, System, Data
Flash xposed-v65-sdk21-arm-arter97-V5-krait (latest: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463)
I wanted to try out some custom ROMs for my Nexus 4 and I decided to go through the first step and unlock the bootloader, install CWM and root. However, I could only unlock loader and flash CWM, but then I noticed I can't install the zip file from sdcard since it says "unable to mount /sdcard". Then I wanted to see if my files on the card are still there and I reboot the system but it doesn't want to boot. What did I do wrong? Only thing I flashed was the CWM recovery, so the system should remain intact.
Can I fix my phone from this situation?
Pandasticus said:
I wanted to try out some custom ROMs for my Nexus 4 and I decided to go through the first step and unlock the bootloader, install CWM and root. However, I could only unlock loader and flash CWM, but then I noticed I can't install the zip file from sdcard since it says "unable to mount /sdcard". Then I wanted to see if my files on the card are still there and I reboot the system but it doesn't want to boot. What did I do wrong? Only thing I flashed was the CWM recovery, so the system should remain intact.
Can I fix my phone from this situation?
Click to expand...
Click to collapse
Try flashing TWRP recovery instead. CWM is discontinued so TWRP should be more up to date. Don't know if it will help but it might.
I found the Nexus Root Toolkit software very useful. It also has a specific task for when the phone is bootlooping. Git it a try!
Hi,
I'm currently using the Skipsoft Android Toolkit to unlock flash TWRP onto my device. I've followed to first steps (install drivers, backup device and unlock bootloader) to the letter and everything went smooth.
Now the final part of installing TWRP is not going so well. Flashing the custom recovery works as expected and I end up in the TWRP menu. However, as soon as I reboot my phone and try to go back to the recovery via Advanced Reboot --> recovery, I end up in the default One Plus Recovery Menu. Now the tool mentioneds when this process fails, renaming the Recovery Restore Files is recommend to prevent the system from flashing the stock recovery on boot (what happens to my device). I follow this option in which I end up back in TWRP, flash a zip named 'permanent-recovery.zip' (while read only mode is turned off in TWRP) and reboot my device. Still when I use Advanced Reboot to open recovery, I end up once again in the Stock Recovery.
Is there anyone who could tell me where I am going wrong and how to solve this issue?
Thanks in advance
Rawrden said:
Hi,
I'm currently using the Skipsoft Android Toolkit to unlock flash TWRP onto my device. I've followed to first steps (install drivers, backup device and unlock bootloader) to the letter and everything went smooth.
Now the final part of installing TWRP is not going so well. Flashing the custom recovery works as expected and I end up in the TWRP menu. However, as soon as I reboot my phone and try to go back to the recovery via Advanced Reboot --> recovery, I end up in the default One Plus Recovery Menu. Now the tool mentioneds when this process fails, renaming the Recovery Restore Files is recommend to prevent the system from flashing the stock recovery on boot (what happens to my device). I follow this option in which I end up back in TWRP, flash a zip named 'permanent-recovery.zip' (while read only mode is turned off in TWRP) and reboot my device. Still when I use Advanced Reboot to open recovery, I end up once again in the Stock Recovery.
Is there anyone who could tell me where I am going wrong and how to solve this issue?
Thanks in advance
Click to expand...
Click to collapse
The basic "mechanics" of what happens seems to still be as follows:
As your phone is delivered with Stock OS, it has these two files installed:
Code:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
I know from looking at mine when I got it that it had /system/recovery-from-boot.p installed. If it's there, it is run when it runs at boot.
To stop that behavior you have to get rid of those files before you reboot the first time from recovery or else recovery will be replaced with the stock image. I'm aware that supposedly the custom recovery supposedly renames either one or the other or both of these but am not convinced it does this or whether installing root (either Magisk or SuperSU) does it. Either way, since you're stuck with the problem, either from file-manager in TWRP if that's all you can boot to, you need to rename /system/recovery-from-boot.p to something like /system/recovery-from-boot.p.orig and maybe the other one /system/etc/install-recovery.sh to /system/etc/install-recovery.sh.orig as well.
Once even the .p file is gone, it's not going to rewrite recovery. You must, of course, be rooted before you can touch those files although if you can sideboot TWRP, it seems like you are rooted while it is booted and "should" have access to system files if you can mount system rw.
I've fixed it this way on other phones. On this one, installing the "official" TWRP and Magisk did it. When I booted into /system after installing Magisk, I looked for the .p file and found it renamed to /system/recovery-from-boot.bak.
I found a link for a Samsung s8 for the same purpose. It's probably identical. http://www.teamandroid.com/2017/04/25/install-galaxy-s8-twrp-310-recovery/3/
Click to expand...
Click to collapse
I looked into those two files while in TWRP and noticed I only had the recovery-from-boot.p file. This was already in fact renamed to recovery-from-boot.p.bak. I renamed it once again (just to be sure) and after flashing the .zip I mentioned earlier, the TWRP did not last another reboot...
Can I after flashing TWRP again, immediately flash Magsik? I intended to hold off rooting because the rom I was going to install has Magisk build into it. I don't want to create a conflict when flashing later on. Is this going to be an issue?
@hachamacha I've reread your post and wondering if rooting my device is even going to make a difference right now? Since I'm already able to rename files in the system directory, would it even make a difference?
Rawrden said:
I looked into those two files while in TWRP and noticed and only had the recovery-from-boot.p file. This was already in fact renamed to record-from-boot.p.bak. I renamed it once again (just to be sure) and after flashing the .zip I mentioned earlier, the TWRP did not last another reboot...
Can I after flashing TWRP again, immediately flash Magsik? I intended to hold off rooting because the rom I was going to install has Magisk build into it. I don't want to create a conflict when flashing later on. Is this going to be an issue?
Click to expand...
Click to collapse
To me, it doesn't sound like a conflict to re-install Magisk over itself in FOS and see if that helps. The real "action" that counts is all about whether you've already booted into the OS after installing TWRP and then how you go about getting rid of the .p file without doing a regular reboot via the OS. Even installing the FOS ROM should get rid of the .p file (rename it), so something else is going on. I'll look around some more and update this if I can.
By the way: Depending upon how exactly you got from TWRP to the OS the first time, it could already have rewritten the stock recovery by the time you noticed *.p file renamed to *.bak.
OK: I recalled how I did this without a problem: I wrote instructions somewhere but have no idea where. This is what I think I did:
1) fastboot flash recovery recovery.img (custom/TWRP)
2) fastboot boot recovery.img (so force it to load recovery without a traditional reboot).
3) install ROM from that point and after done just hit the reboot button (or install Magisk from that point and hit reboot).
Click to expand...
Click to collapse
---------- Post added at 09:26 AM ---------- Previous post was at 08:59 AM ----------
Rawrden said:
@hachamacha I've reread your post and wondering if rooting my device is even going to make a difference right now? Since I'm already able to rename files in the system directory, would it even make a difference?
Click to expand...
Click to collapse
Just saw this note:
Anytime you're in TWRP, you're automatically "rooted" for the time you're there. It's integral to TWRP having permissions to do anything like install etc. If you just "loaded" TWRP (as in fastboot boot twrprecovery.img) then you'd be rooted, but when you rebooted to the system, you'd be unrooted. While you were in TWRP, in theory you could make file system changes to the /system partition (a) if TWRP lets you mount it rw which I think that first swipe does and b) if you can see the correct files in it's file manager.
So it "seems" like those file changes should be actual file changes to the correct place. Keep in mind that while booted in TWRP, TWRP may have it's own ./system/ that has nothing to do with the OS's ./system folder, so you've got to be able to mount the OS's ./system. TWRP's ./system is already fine and of no importance for this. I can boot mine into TWRP and look around to try to clear this up, but it might not be crystal clear to me either.
The output of a TWRP terminal emulator "mount" command might be of use but it will be messy. Maybe if you can do this in emulator from TWRP:
# mount | grep system, and look at that output, perhaps put it in this post, it'd be of help. The mounted rw ./system we need is going to be the same one you'd see from adb shell or terminal emulator while booted from the OS. My guess is that the one we don't want from TWRP's perspective will be mounted as /system (params...) and that the the OS's system either will not yet be mounted and you'll have to go to mounts and mount it and then look at the output of the mount cmd again to figure out what it was mounted as. Sorry about how complicated this explanation has become. Anyway: The ./system that corresponds to the OS is the only one we care about.
There's no easy way to explain it so I'll leave it hidden to spare anyone having to look at it:
I just booted into TWRP and used terminal emulator and file manager to explore:
findings: While in TWRP, using terminal emulator to do a
$ df and then a $ mount command shows no ./system mounted specifically. // maybe not a surprise.
// TWRP just mounts it's root / file system and there is a /system folder, just not a specific mount point for it.
// TWRP does not auto mount the OS's ./system partition by default. It depends what you're going to do there.
Without going into "mounts" and clicking on /system, it won't even try to mount /system for the OS.
If you can get that mount to work in read/write mode, then you should be able to see the ./system mount using terminal emulator as such.
$ mount | grep -i system (and look specifically for ./system on the right side of whatever appears).
In theory you should be able to make changes to the OS's /system partition now. When you're done, unmount it. (I'm assuming all this works from TWRP, a dodgy assumption)
At this point: I'm just trying to figure out how TWRP does things like installs OS zips to the /system & /data partitions which it is clearly successfully able to do. It could do it without mounting anything because it could use the linux dd command, which just writes to the /dev name. OR: It could mount /system and use it. I'm not sure which.
hachamacha said:
OK: I recalled how I did this without a problem: I wrote instructions somewhere but have no idea where. This is what I think I did:
Quote:
Code:
1) fastboot flash recovery recovery.img (custom/TWRP)
2) fastboot boot recovery.img (so force it to load recovery without a traditional reboot).
3) install ROM from that point and after done just hit the reboot button (or install Magisk from that point and hit reboot).
Click to expand...
Click to collapse
I followed these steps and I managed to install FreedomOS without any issues. My phone booted normally and after a few complimentary steps I booted back into recovery and... TWRP! No more stock recovery. Thanks a lot!
Just one more question: TWRP currently asks whether it is allowed to install itself as a system app. Now I assume it is already a system app, but I'm not expert at this so I can't say for sure. Would you recommend me to install TWRP as a system app?
Rawrden said:
I followed these steps and I managed to install FreedomOS without any issues. My phone booted normally and after a few complimentary steps I booted back into recovery and... TWRP! No more stock recovery. Thanks a lot!
Just one more question: TWRP currently asks whether it is allowed to install itself as a system app. Now I assume it is already a system app, but I'm not expert at this so I can't say for sure. Would you recommend me to install TWRP as a system app?
Click to expand...
Click to collapse
Great! Glad that worked. I guess it's all about how that first boot to the OS occurs.
Anyway: Your question, I'm assuming is about TWRP "Manager" the app? If so, yes, it should be a system app. The thing is that "Official TWRP Manager" doesn't really do much of use that you wouldn't just as soon do from fastboot, so it's not critical and nothing other than TWRP manager will "not work" regardless of what you designate it. All saying it's a system app does is puts a slot for it in Magisks "root table".
Cheers.
hachamacha said:
Great! Glad that worked. I guess it's all about how that first boot to the OS occurs.
Anyway: Your question, I'm assuming is about TWRP "Manager" the app? If so, yes, it should be a system app. The thing is that "Official TWRP Manager" doesn't really do much of use that you wouldn't just as soon do from fastboot, so it's not critical and nothing other than TWRP manager will "not work" regardless of what you designate it. All saying it's a system app does is puts a slot for it in Magisks "root table".
Cheers.
Click to expand...
Click to collapse
Done! Can I just say how grateful I am to you for helping me out with this? Your answers have been extremely detailed and I've learned quite a few things. Unfortunately I can only thank your posts once, because you've earned more than that. Thanks again and keep being awesome!