Develop Bugs

[Q] Lost root, won't come back

So I'm not a complete and utter n00b here, as I've been rooting and installing CM for at least three years now on several different phones. But this problem vexes me...
Patient: SIII, formerly rooted and running CM10.1 just fine. A few weeks ago, I tried to install a 10.2 stable build, and it somehow took my root away. I tried every trick I knew how - installing the root files via Odin (many versions), via ADB, via Kingo Root...nothing. Absolutely nothing I try will get this thing to give me my root back, and the ads are starting to really get on my nerves.
My ticker says 15 attempted installs, but I don't think it's blocking me from rooting...is it? All the phones I've rooted I've never had a problem like this, where absolutely nothing will allow root to "take", such as it is.
Any thoughts or suggestions?
Thanks!

Wow, nothing? I figured someone would at least sigh heavily, berate me for not reading the forums completely, then point me to a thread where this has been discussed ad nauseum
Last night, I tried rooting with TWRP, CWM, every variant and trick I could find to get this thing to root for me, and while these things all seem to load fine, none of them give me my root access back. No one has any ideas?
Thanks!

help
im using rooted 4.3 stock rom in t999..
everytime i boot into recovery it says "fixed root"
any solve for this?????

Did you dirty flash CM10.2 over CM10.1? if so, it might have failed to write the partition completely/correctly. I would suggest to backup everything that you can (adb backup or similar) and then wipe everything then reflash fresh CM10.2.0 + GApps + SuperSU or Koush's Superuser flashable zip.

[Q] Unable to select /sdcard when in recovery

I have rooted many mobile devices and flashed numerous ROMS. However I recently purchased a Galaxy Note 10.1 2014 edition and have not been able to get very far in my attempts to root, etc. I have tried Odin and CF-Auto-Root and although it appears to be successful the device is not rooted. I want to install TWRP and then the knox free stock ROM. I am able to push the necessary files to the sdcard with ADB and I can see that the files are in /sdcard using ES File explorer. However when I boot into recovery mode /sdcard is red and at the top of the list and it will not let me navigate to it to install any zip files. I though at first it might be because of the MobileIron I use for company email but I did a factory reset and still have this problem. I just need to root the device so I can use Titanium BU to remove the Samsung apps I don't want. Any help with this would be most appreciated. What do I need to do?
~metafizik

Ultimately I think the first thing I need to resolve is that even though the Odin rooting process appears to be working according to Odin(PASS). The fact is that regardless which combination of Odin 3.07/3.09 and CF-Auto-Root (tried 2 versions) even though Odin says it was successful it turns out the device is not getting rooted. This should be a no brainer but for for whatever reason this device will not root so far.

Bumping this as I have not received any replies. I am hoping that someone has run across a similar situation and can offer some guidance.
Thank you,
~metafizik

metafizik said:
Ultimately I think the first thing I need to resolve is that even though the Odin rooting process appears to be working according to Odin(PASS). The fact is that regardless which combination of Odin 3.07/3.09 and CF-Auto-Root (tried 2 versions) even though Odin says it was successful it turns out the device is not getting rooted. This should be a no brainer but for for whatever reason this device will not root so far.
Click to expand...
Click to collapse
Did you install super su?Did you try to flash twrp.If your not rooted twrp will ask to root.Have you tried to install a root app and see if the permissions pop up?
When you say recovery do you mean the stock one?Im pretty sure i had same problem.It was rooted but i thought it wasnt.

mikep2323 said:
Did you install super su?Did you try to flash twrp.If your not rooted twrp will ask to root.Have you tried to install a root app and see if the permissions pop up?
When you say recovery do you mean the stock one?Im pretty sure i had same problem.It was rooted but i thought it wasnt.
Click to expand...
Click to collapse
This is a very strange deal. As previously stated I have tried various combinations of Odin and CF-Auto-Root and the Odin process completes with PASS. However when I boot the OS and run Titanium it is never able to gain root access and Root Checker says it is not rooted. Unfortunately even after doing a factory reset the MobileIron Admin console at work says it is rooted so I can't use it for company email. I have definitely tripped the Knox bit. Also I want to install TWRP and have pushed the file to /sdcard and can see it there using a file explorer app. However when I boot into stock recovery I cannot see any of the zip files I have copied there. I also tried to flash TWRP with Odin and again it completes with PASS but TWRP never gets installed. And yes I installed SuperSU but did so from the Play Store.
I purchased this device just last week. I am wondering if maybe Samsung has changed things in the past few weeks and locked these friggin things down even more? This is the first device of many I have owned that I couldn't root or install a custom recovery or ROM. In any case this will definitely be my last Samsung device. I would however like to do whatever I so desire with it since I paid good money for it.

I have resolved all of the problems I was having. They were all due to Knox and my inexperience with it. I was fortunate to have customized my Note 2 before it received the Knox updates. All is well and there is no new unknown vodoo lurking in the latest iteration of Samsung devices.

[Q] Quick question about stock recovery

Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron

ericksonline said:
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
Click to expand...
Click to collapse
Yes you can go to software number to get the info you need. To do an OTA you need a stock sense ROM (NO CHANGES TO ANY SYSTEM APPS) you then need to flash the correct recovery for your software number and [IMPORTANT] relock the bootloader. You then can reboot into your system and take the OTA while still being able to unlock the bootloader and flash a custom recovery afterwards.

No need to relock the bootloader for an ota. People should stop spreading that info

Thanks for the replies!
Just to check my understanding, since I simply unlocked the bootloader, used the TWRP recovery, added SuperSU, installed then uninstalled Xposed framework, that means that I should still be on a stock sense ROM (with no changes to any system apps), right?
There is a lot to learn with all of this when you are first starting out. I'm reading a lot, but sometimes you do find conflicting information. I'd rather be a little cautious than do something stupid!
Thanks again!

ericksonline said:
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
Click to expand...
Click to collapse
ericksonline said:
Thanks for the replies!
Just to check my understanding, since I simply unlocked the bootloader, used the TWRP recovery, added SuperSU, installed then uninstalled Xposed framework, that means that I should still be on a stock sense ROM (with no changes to any system apps), right?
There is a lot to learn with all of this when you are first starting out. I'm reading a lot, but sometimes you do find conflicting information. I'd rather be a little cautious than do something stupid!
Thanks again!
Click to expand...
Click to collapse
Yup you're good ROM wise. Just flash the stock recovery and you should be good to go.

You can be unlock and have OTA.
You just need a stock recovery.

HTC ONE M8 fails to load up after failed software update
Hello guys, this is my first post. I really need your help as I'm at risk of loosing all my phone data. My phone internal memory had been exhausted and I bought an external SD card. I am unable to transfer data to the external SD card. I was doing a software update on my phone that failed to install, there was a warning sign on the phone screen for a few minutes then it try to power on but has failed, as it's seem to stuck on the screen that display htc powered by android. I tried the recovery holding down the power button and the column up button, the phone power off and back on but is still stuck on this screen (htc powered by android). I tried connecting the phone to my laptop to try and recover my data, but it's not mounting to the laptop. Please can someone help me. Thanks in advance.

Similar to the post above ie rooted and kept on stock. Also loaded a few Xposed modules but when I connected to my wifi I had over 30 updates so loaded all of them and once loaded the old bootloop started. I restored my nandroid backup from TWRP (this is an essential backup) and I was back in action. Phew!!!! I no longer had Xposed. So I did the updates again and the same thing happened. I am now updating one at a time which is painful when you've got so many. I also tried wiping the caches but that didn't work.
I noticed there were a lot of HTC apps eg HTC sense input, service pack, blinkfeed etc. I also notice a super SU update. ericksonlines post above said he had a problem with superSU. What kind of problem? What does he mean by reapplying? Flashing from TWRP?
So the big question. Which app(s) update did the damage???
Any apps I shouldn't update eg HTCs?
Has this happened to anyone else? What did you then do? Is the new updated superSU the problem
Apologies for cross posting on an Australian site but I'm a bit frazzled with all of this.

jbarr3 said:
Similar to the post above ie rooted and kept on stock. Also loaded a few Xposed modules but when I connected to my wifi I had over 30 updates so loaded all of them and once loaded the old bootloop started. I restored my nandroid backup from TWRP (this is an essential backup) and I was back in action. Phew!!!! I no longer had Xposed. So I did the updates again and the same thing happened. I am now updating one at a time which is painful when you've got so many. I also tried wiping the caches but that didn't work.
I noticed there were a lot of HTC apps eg HTC sense input, service pack, blinkfeed etc. I also notice a super SU update. ericksonlines post above said he had a problem with superSU. What kind of problem? What does he mean by reapplying? Flashing from TWRP?
So the big question. Which app(s) update did the damage???
Any apps I shouldn't update eg HTCs?
Has this happened to anyone else? What did you then do? Is the new updated superSU the problem
Apologies for cross posting on an Australian site but I'm a bit frazzled with all of this.
Click to expand...
Click to collapse
Hello! It is possible that an update came through that caused my phone to start into the boot loop. I'm not sure because it worked fine for a few hours before the problem started happening all of the sudden. My guess is that something updated that broke SuperSU. As soon as something would try to use SuperSU (or maybe the rights granted by SuperSU), the phone would crash and reboot. To fix the problem, I rebooted into the bootloader (TWRP) and re-installed SuperSU from there. After I re-installed, everything began working nicely again. I have not had a problem since and the problem occurred a few months ago now. I have also recently updated to the new version of SuperSU with no problems at all.
I hope this helps!
Ron

ericksonline said:
Hello! It is possible that an update came through that caused my phone to start into the boot loop. I'm not sure because it worked fine for a few hours before the problem started happening all of the sudden. My guess is that something updated that broke SuperSU. As soon as something would try to use SuperSU (or maybe the rights granted by SuperSU), the phone would crash and reboot. To fix the problem, I rebooted into the bootloader (TWRP) and re-installed SuperSU from there. After I re-installed, everything began working nicely again. I have not had a problem since and the problem occurred a few months ago now. I have also recently updated to the new version of SuperSU with no problems at all.
I hope this helps!
Ron
Click to expand...
Click to collapse
You're dead right Ron. Supersu was the culprit. Just simply updating from the playstore caused this. I restored an android backup which got me back. I went into the old SuperSu (V1.94) and clicked "clean up when updating from google play" or similar, did the update again (v 2.04 from google) and while this didn't cause rebooting, I couldn't install the binary. I chose "normal" (maybe I should have chosen TWRP) and it didn't work. So I flashed my old v1.94 from TWRP and that got me back. So some questions on updating SuperSu.
1. Is flashing the zip file through TWRP the best way to install a new version?
2. Should I delete or uninstall the old version or will flashing do that for me? Did you simply flash over the top of the other one?
3. Should I stick with 1.94, which works, or should I update to a new and improved version?
4. I think 2.16 is the latest. What version are you running, is it stable and do you recommend it ?
5. I assume I get the zip file from chainfire. They are way ahead of the google playstore for updates

jbarr3 said:
You're dead right Ron. Supersu was the culprit. Just simply updating from the playstore caused this. I restored an android backup which got me back. I went into the old SuperSu (V1.94) and clicked "clean up when updating from google play" or similar, did the update again (v 2.04 from google) and while this didn't cause rebooting, I couldn't install the binary. I chose "normal" (maybe I should have chosen TWRP) and it didn't work. So I flashed my old v1.94 from TWRP and that got me back. So some questions on updating SuperSu.
1. Is flashing the zip file through TWRP the best way to install a new version?
2. Should I delete or uninstall the old version or will flashing do that for me? Did you simply flash over the top of the other one?
3. Should I stick with 1.94, which works, or should I update to a new and improved version?
4. I think 2.16 is the latest. What version are you running, is it stable and do you recommend it ?
5. I assume I get the zip file from chainfire. They are way ahead of the google playstore for updates
Click to expand...
Click to collapse
I'm no expert, but I'm happy to share my experience. I do believe that flashing from TWRP is the best way to install. That is what I did to fix my reboot problems. I don't recall uninstalling the previous version in any way. I think the old file was still on there. I browsed to it in TWRP and installed it. I'm not sure what version I was on when I did this. Recently, a new update (2.16) was available that downloaded through the Play Store. When I went to update, it recommended that I use TWRP to install. I didn't go this route because I had already switched back to the default bootloader and didn't want to reinstall TWRP if I didn't have to. So, I just used the "normal" method. It updated successfully and I've had no problems. I am now running 2.16.

ericksonline said:
I'm no expert, but I'm happy to share my experience. I do believe that flashing from TWRP is the best way to install. That is what I did to fix my reboot problems. I don't recall uninstalling the previous version in any way. I think the old file was still on there. I browsed to it in TWRP and installed it. I'm not sure what version I was on when I did this. Recently, a new update (2.16) was available that downloaded through the Play Store. When I went to update, it recommended that I use TWRP to install. I didn't go this route because I had already switched back to the default bootloader and didn't want to reinstall TWRP if I didn't have to. So, I just used the "normal" method. It updated successfully and I've had no problems. I am now running 2.16.
Click to expand...
Click to collapse
Thanks erick but given what's happened I don't think I'll ever update from the playstore again. I'll load 2.16 using TWRP and report back. I can't stress enough how important it is to have a nandroid backup. I reckon its the best reason to load a custom recovery. Its got me out of trouble twice now and gives me piece of mind. I've actually gone overboard on this and I have two backups on my phone which I have copied to my PC..

vm54 said:
You can be unlock and have OTA.
You just need a stock recovery.
Click to expand...
Click to collapse
And stock ROM.

Updated to v 2.16. Piece of cake!!!
Loaded through TWRP, rebooted and that was it. It didn't even ask about installing the binary. Same binary I guess.
It worried me, however, when I saw over 700 pages on this version xda. Most with problems.

jbarr3 said:
Updated to v 2.16. Piece of cake!!!
Loaded through TWRP, rebooted and that was it. It didn't even ask about installing the binary. Same binary I guess.
It worried me, however, when I saw over 700 pages on this version xda. Most with problems.
Click to expand...
Click to collapse
Awesome! I'm glad to hear that it worked!

Problems booting and rebooting (not consistently) - just updated bootloader to OG5

So, my phone was problem free with the OB7 bootloader /OG5 ROM combination that is fairly common on this forum.
My unhealthy obsession with getting Android Pay to work on my phone led me to update the bootloader to OG5. I used odin and the tar file/instructions found here: "[GUIDE] Not quite newbie guide for moving to 5.1.1
http://forum.xda-developers.com/showthread.php?t=3199881 "
Since doing this i have been having consistent problems including:
1 - powering on often goes into a download mode, with an error message, including but not consistently one of the following:
- sbl1 partition doesn't exist
- Kernel panic krait
- mmc_read fail
2 - reboots fail in about half of the attempts , sometimes the phone boots into download mode with an above error, sometimes it just stays powered off
3 - infrequent rom freeze-ups that result in one of the errors above.
I have re-tried the process a couple of times to fix. After the tar, and TWRP, I i have flashed both Hybrid X & Freeza's stockish. Both are terrific when the phone boots properly (except for the freezes mentioned above, but i don't think that they are ROM related.)
I have also tried removing and reformating my SD Card.
I usually get it to boot properly after a couple of battery pulls.
I'm not sure what the problem is and hoping someone wise can help me come up with a fix. Wondering if this related to TWRP, or maybe the updated partitions or some kind of checkdisk situation?
Any ideas?
Many thanks,

Since you mentioned TWRP and the method you used, you must not intend to get Android Pay working? I haven't kept up with this topic since the forum Google employee disclosed the unofficial policy stating root is a security risk they don't want compromised for Android Pay. Seems the unofficial policy is to choose root or abandon it for Android Pay. Most likely applies to Samsung Pay as well.
That said, are you looking for a rooted solution or non-rooted solution for the random reboots and freezes. Non-root solution would only be wipe and start over or seek warranty resolution. Rooted: did you try the previous ROM you were using on a clean install?
Sent from my SM-N910P using Tapatalk

samep said:
Since you mentioned TWRP and the method you used, you must not intend to get Android Pay working? I haven't kept up with this topic since the forum Google employee disclosed the unofficial policy stating root is a security risk they don't want compromised for Android Pay. Seems the unofficial policy is to choose root or abandon it for Android Pay. Most likely applies to Samsung Pay as well.
That said, are you looking for a rooted solution or non-rooted solution for the random reboots and freezes. Non-root solution would only be wipe and start over or seek warranty resolution. Rooted: did you try the previous ROM you were using on a clean install?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Actually, android pay let me set up my credit cards when i disabled superuser via supersu , it wasn't letting me do that on the OB7 bootloader. I haven't had the chance to make a purchase, not sure if it will work.
That said, my goal would be to get the phone stable, resolve the booting issues and keep root. I don't need android pay.
As far as the ROM I had before updating the bootloader, it was one of the OG5 roms I've since installed. It was my understanding that the new partitions would not allow me to install the previous nandroid backup.
The issue seems to be at a lower level than the rom
samep said:
Since you mentioned TWRP and the method you used, you must not intend to get Android Pay working? I haven't kept up with this topic since the forum Google employee disclosed the unofficial policy stating root is a security risk they don't want compromised for Android Pay. Seems the unofficial policy is to choose root or abandon it for Android Pay. Most likely applies to Samsung Pay as well.
That said, are you looking for a rooted solution or non-rooted solution for the random reboots and freezes. Non-root solution would only be wipe and start over or seek warranty resolution. Rooted: did you try the previous ROM you were using on a clean install?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse

mrquaid said:
Actually, android pay let me set up my credit cards when i disabled superuser via supersu , it wasn't letting me do that on the OB7 bootloader. I haven't had the chance to make a purchase, not sure if it will work.
That said, my goal would be to get the phone stable, resolve the booting issues and keep root. I don't need android pay.
As far as the ROM I had before updating the bootloader, it was one of the OG5 roms I've since installed. It was my understanding that the new partitions would not allow me to install the previous nandroid backup.
The issue seems to be at a lower level than the rom
Click to expand...
Click to collapse
PM sent.
Sent from my SM-N910P using Tapatalk

Thanks to @samep for all the help.
If anyone finds this thread w/the same problem, here is what made it way better.
After flashing the tar, let the stock ROM boot and go through the setup wizard.
Then shut down, then power into download mode to odin TWRP.
I was installing TWRP right after the tar, and it must have mucked it up a bit.
The phone is not 100%, I can't seem to reboot from my ROM into recovery mode. But I can power down and start up into recovery the usual way (holding the Power, Home, and Volume Up buttons).

Clarifications on Bootloader unlocking

Hello, I own a sm-p605 LTE/WiFi and I had been trying to unlock the bootloader since some time unsuccessfully. I then succeeded eventually and accidentally. After having flashed twrp through Odin many times successfully and using different twrp versions, in the end twrp never showed up. I did a reset to factory defaults within the stock ROM (to address a different issue actually) and that (and only that!) made the twrp show at boot. Else it went straight into stock bootloader. I add that through twrp I was able to install LOS 14.1 2021 + pico open-gapps successfully.
Now, I have two questions:
1. it might sound silly but, can I now assume that my bootloader is unlocked? I'm asking this because my device did not have the OEM Unlock option in the stock rom developer settings, and I have tried all possible advices read on this forum to no avail, to make it appear. I assume that twrp took control over the boot process as it is working fine, but the fact that the OEM Unlock option was never available makes me doubt.
2. I thought that LOS would automatically allow root access, but it does not seem the case. A su checker tells me not. But an app that I have installed (a pdf reader) warns me if I'm ok to install the app in a rooted environment. I guess su checker is the one to trust, right?

That sounds interesting, can you provide me the files you used and the version of Odin. I would like to test this on my p605 to try it out. Sits in a drawer anyway.

mezam said:
Hello, I own a sm-p605 LTE/WiFi and I had been trying to unlock the bootloader since some time unsuccessfully. I then succeeded eventually and accidentally. After having flashed twrp through Odin many times successfully and using different twrp versions, in the end twrp never showed up. I did a reset to factory defaults within the stock ROM (to address a different issue actually) and that (and only that!) made the twrp show at boot. Else it went straight into stock bootloader. I add that through twrp I was able to install LOS 14.1 2021 + pico open-gapps successfully.
Now, I have two questions:
1. it might sound silly but, can I now assume that my bootloader is unlocked? I'm asking this because my device did not have the OEM Unlock option in the stock rom developer settings, and I have tried all possible advices read on this forum to no avail, to make it appear. I assume that twrp took control over the boot process as it is working fine, but the fact that the OEM Unlock option was never available makes me doubt.
2. I thought that LOS would automatically allow root access, but it does not seem the case. A su checker tells me not. But an app that I have installed (a pdf reader) warns me if I'm ok to install the app in a rooted environment. I guess su checker is the one to trust, right?
Click to expand...
Click to collapse
You're TWRP installing problem might have come up when not rebooted DIRECTLY after flashing into recovery.
This failure lets stock recovery get reanimated.
I have P605 too and can asure you that this devices never had an OEM locked bootloader. I've read that Verizon and others in the US locked them, but never did Samsung.
Mine is on LOS 17.1 which is very stable and to gain root you gotta flash Magisk and after rebooting to system set it up.
A simple pdf reader shouldn't imho care about it's envirement. So I wouldn't use it and search for a different one.
I use ebookdroid.

bmwdroid said:
You're TWRP installing problem might have come up when not rebooted DIRECTLY after flashing into recovery.
This failure lets stock recovery get reanimated.
I have P605 too and can asure you that this devices never had an OEM locked bootloader. I've read that Verizon and others in the US locked them, but never did Samsung.
Mine is on LOS 17.1 which is very stable and to gain root you gotta flash Magisk and after rebooting to system set it up.
A simple pdf reader shouldn't imho care about it's envirement. So I wouldn't use it and search for a different one.
I use ebookdroid.
Click to expand...
Click to collapse
I wish I could do the same, sadly I am a Verizon version owner and let me tell you it is terrible in 2022. If I could unlock it I would definitely use it more