Hi at all,
i've a big problem with my XA2:
- I unlocked the bootloader for flashing TWRP and LinageOs 18.1 - which worked
- After flashing the LinageOS, my Imei was "deleted" - meaning if I doing *#06# the phone shows: MEID 0000000
- If I go in the system settings, the Imei is correct.
- The phone not able to connect to the mobile network.
I can't flash the Stock-Rom with "Emma" or Flashtool, cause the bootloader is open.
I tried to relock the bootloader with Flashtool, but it eds up with a error: "Cannot invoke "String.split(String)" because the return value of "java.util.Properties.getProperty(String)" is null."
I really need any help what I can get.
thanks
knofi
Did you get it fixed?
Not yet :-(
With my XA2 H3123, I went from stock 9, to LOS 18.1 and all seemed great. To experiment further, I used Emma to go to stock 8. After a week or two I went to LOS 18.1 again but now video problems. I was told my firmware was too old from stock 8 and to upgrade to stock 9 to get newer video drivers, and then return to LOS 18.1. When I returned to Emma, Sony had removed stock 9 for the H3123. The only successful way I found was by using Xperifirm to get CustomUS version 50.2.A.3.77 for H3123 and then had to flash it with NewFlasher thanks to advice from @LuK1337. I failed on first couple attempts because I answered the questions from NewFlasher incorrectly upon launch. I got the quesitons right and it worked. I think I was saying yes to a dump for recovery or something and should have said no, and I may have at first answered wrong on whether to use Gordon Gate. I don't recall which way I went on Gordon Gate. So finally phone seems to work great. The problem remains, through the whole procedure of changing ROMs I kept noticing my phone Settings always said my phone remained encrypted. So the wipes and erase from fastboot weren't doing it right, as the instructions from LOS say wipes should obviously remove encryption. During these changes, I also tried TWRP wipe and erase, and Factory Data Reset through LOS Settings. Now I'm trying to find time to learn how to get "Parted" or "Busybox with Fdisk" to use on phone and cleanly overwrite my partitions on phone with 1s or 0s and really start over with clean phone. Lacking time.
The reason I posted all that is it amazed me my phone could stay encrypted through all that, telling me the phone is not a clean install. So figure maybe your phone is not a clean install also, and maybe a clean overwrite will get your IMEI reported correctly again. Somwhere I was reading about changing a phone's IMEI so maybe those articles will tell you which partition hold the IMEI data, other than your SIM card. Or maybe if you use TWRP rather than LOS Recovery img, you can wipe or erase and install LOS again and you're good.
By the way, my understanding is once bootloader is unlocked you won't be able to use Sony Companion to flash phone, so you have to use Emma. I use Emma with unlocked bootloader, so not sure about that statement in your opener.
Related
Dear everone!
I just sim unlocked my S5.
Because i couldnt find very much information about it, i wrote a short tutorial.
I hope it's of use for you guys
Well it seems i can't post a link, so i will copy it.
Warning: If you flash a custom rom on your device you will most likely lose your warranty!
Greetings concerned reader!
After troubles finding usefull information concerning unlocking a Galaxy S5 with a custom ROM (in my case LineageOS 14.1) i started my own research.
One thing hast to be said at the beginning: You CANNOT unlock the simlock with a custom ROM.
So what was my start situation:
I had a simlocked phone (locked by my provider) with a custom rom and custom recovery allready installed, but i wanted to use a simcard from another provider. After some time i found a forum post that it isn’t possible to unlock the phone with the custom rom.
So what do you need for proceeding:
The network unlock code (for example from your provider)
a version of your original rom
Backup your data ( for example via your google account)
Odin Flash Programm
A LineageOS rom (if you want to flash lineage again)
A custom recovery (if you want to flash lineage again, for example TWRP )
At first backup all your data! (external SD card and internal storage)
Normally the SD card won’t get deleted, but to be certain backup it.
The first time i tried to unlock the phone i made a full backup of Lineage via the TWRP recovery, flashed the original rom with ODIN and unlocked the simlock with the code. It worked on the stock rom, but when i restored the LineageOS backup it asked again for the network unlock code. Important to say that you can type in the code in LineageOS but the unlock process doesn’t work properly.
After hours of research and thinking i came to a solution which worked for me.
From LineageOS i went back to the stock rom and unlocked the simlock with the network code (the unlock was sucessfull as in the first try). Then i flashed the custom recovery (TWRP) via ODIN. After that i made a full backup from the stock rom via TWRP (just in case the unlock won’t work and i have to go back to stock).
I decided to flash a new LineageOS rom, because the restore didn’t work in the first approach. Because the phone forgot the unlock code after the restore i thought the unlock process was saved in a part of the memory i deleted while i restored the old data. My first guess was that it’s save in the Cache Partition of the phone.
So if you were useing a stock rom before and not LineageOS i would suggest to at least do a factory reset or a reinstall of the stock rom, in order to get the cache deleted BEFORE you type in the network unlock code.
What we will do now is to wipe the System and Data partition of the phone via TWRP. (DO not wipe cache).
Reinstall LineageOS and if you need them google apps (as described in the tutorial). Reboot and your device should recognize the new simcard.
Comments:
I am still not sure why the unlock worked on the stock rom but later not on the custom rom. There are two possibilities that came in my mind:
The custom rom has to be reinstalled after the simunlock because it doesn’t recognize the unlock in the restored state.
The unlock process is really stored in the cache.
It didn’t continue my research on this topic, because it worked for me and i was happy that i got it working.
If you want the link or have questions please contact me
Best regards
A bit later in history, but I just finished doing this exact thing.
The data related to unlocking is NOT in the cache, my S7 required a complete wipe due to Samsung's encryption, and the lock returned when restoring only a few sections excluding the cache.
If you are willing to go through the process, the data section (with most things that the user would care about) can be restored without reinstating the lock.
I haven't tested with other sections, however when I restored only System, Data and EFS a relock occurred, which leads me to believe it's likely something in the EFS.
Hi guys,
I'm having trouble with my A2 Lite. Right after unboxing the phone I installed Magisk as described in the guide (https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-device-t3825626), which worked like a charm. Today, I wanted to install a OTA security update. After the update was downloaded I got an error and I remembered that I had to "uninstall" Magisk, as described in "step a" of the guide. So I did exactly as described in the guide. After Magisk was "uninstalled" I closed the app and tried again to install the OTA security ("step b") update. Unfortunately I got the same error message again ("Can't install update"). So I thought f*** it - I skipped "step b" and proceeded to "step c" and installed Magisk into an empty slot. After that I hit "reboot" and now my phone's in a bootloop :-/
bootloader is unlocked, oem unlock and debug usb are activated. I'm able to enter fastboot, but no recovery, whatsoever.
Is there any way to fix this?
just letting you guys know that "fastboot set_active b" did the trick. I don't know what the hell went wrong though. I did everything according to the guide, except for trying to update the ota update (and failing) before uninstalling Magisk.
Now, the phone is booting correctly, but I still can't install the ota update. it says "Couldn't update" and "Installation problem". What the heck...
lunatikk said:
just letting you guys know that "fastboot set_active b" did the trick. I don't know what the hell went wrong though. I did everything according to the guide, except for trying to update the ota update (and failing) before uninstalling Magisk.
Now, the phone is booting correctly, but I still can't install the ota update. it says "Couldn't update" and "Installation problem". What the heck...
Click to expand...
Click to collapse
This is probably due to the root as it modified the system partition. Check the thread regarding on how to update without losing root.
fake__knv said:
This is probably due to the root as it modified the system partition. Check the thread regarding on how to update without losing root.
Click to expand...
Click to collapse
Could you explain further? Will flashing the stock boot.img fix the issue and will I lose all data on the phone after flashing the boot.img?
thanks
lunatikk said:
Could you explain further? Will flashing the stock boot.img fix the issue and will I lose all data on the phone after flashing the boot.img?
thanks
Click to expand...
Click to collapse
Please go see my guide, I just added a troubleshooting section that you should check:
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
Your feedback could improve it further.
No, flashing boot.img will not erase any data on the phone. But you must remove any PIN, password or screenlock before proceeding, or you could not access your data anymore (because of encryption).
BubuXP said:
Please go see my guide, I just added a troubleshooting section that you should check:
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
Your feedback could improve it further.
No, flashing boot.img will not erase any data on the phone. But you must remove any PIN, password or screenlock before proceeding, or you could not access your data anymore (because of encryption).
Click to expand...
Click to collapse
Hi BubuXP
I followed your troubleshooting guide and flashed the boot.img as instructed. Flashing the boot.img didn't do the trick so I continued with flashing the system.img. I checked for the correct build no. of course and for both boot.img and system.img the active slot "b" was chosen. After flashing the system.img I got stuck at a bootloop. I tried to set the active slot to "a", but that didn't help either: Now it wasn't in a bootloop anymore, but it was stuck at the boot animation (horizontal beam) loading forever. After 10 minutes I tried to restart - still the same problem.
What's going on here??
edit:
I flashed daisy_global_images_V9.6.4.0.ODLMIFF_20180724.0000.00_8.1_4afd3431a2 using MiFlash and the "Save user data" option. It was flashed successfully. However, when I start the phone it askes for a password and won't boot up into android if not entered. What the hell...? I deactivated my screenlock pin before I started all this. Is there a default password or what's the problem here?
regards
lunatikk said:
Hi BubuXP
I followed your troubleshooting guide and flashed the boot.img as instructed. Flashing the boot.img didn't do the trick so I continued with flashing the system.img. I checked for the correct build no. of course and for both boot.img and system.img the active slot "b" was chosen. After flashing the system.img I got stuck at a bootloop. I tried to set the active slot to "a", but that didn't help either: Now it wasn't in a bootloop anymore, but it was stuck at the boot animation (horizontal beam) loading forever. After 10 minutes I tried to restart - still the same problem.
What's going on here??
edit:
I flashed daisy_global_images_V9.6.4.0.ODLMIFF_20180724.0000.00_8.1_4afd3431a2 using MiFlash and the "Save user data" option. It was flashed successfully. However, when I start the phone it askes for a password and won't boot up into android if not entered. What the hell...? I deactivated my screenlock pin before I started all this. Is there a default password or what's the problem here?
regards
Click to expand...
Click to collapse
Sorry, but I don't know anything about that. It's an encryption problem, and that's why I hate data encryption on the phone: my data is not so important to be protected when some hackers physically stole my phone, it's only a nuisance when things like this happens.
I can only suggest to change the active slot, maybe with this you can resolve.
I will also update my troubleshooting section of the rooting guide to make the data backup as the first option to be safe.
If you can sacrifice the data, you can simply format the data partition via fastboot or reflash using the flash_all.bat script.
BubuXP said:
Sorry, but I don't know anything about that. It's an encryption problem, and that's why I hate data encryption on the phone: my data is not so important to be protected when some hackers physically stole my phone, it's only a nuisance when things like this happens.
I can only suggest to change the active slot, maybe with this you can resolve.
I will also update my troubleshooting section of the rooting guide to make the data backup as the first option to be safe.
If you can sacrifice the data, you can simply format the data partition via fastboot or reflash using the flash_all.bat script.
Click to expand...
Click to collapse
I also thought that it had something to do with encryption. In the security menu, where I turned off the display lock, it said that the phone is encrypted. However neither pin nor fingerprint could unlock the phone.
I had to go for ultima ratio and flash my device with the newest fastboot image and miflash (save user data option didn't work either, btw.).
I lost all data on the device, but now everything works fine and the OTA update also ran through without any issues.
Now, I'm not sure if I will fiddle with magisk again. I really don't have no clue about what went wrong at all...
Thanks
lunatikk said:
I also thought that it had something to do with encryption. In the security menu, where I turned off the display lock, it said that the phone is encrypted. However neither pin nor fingerprint could unlock the phone.
I had to go for ultima ratio and flash my device with the newest fastboot image and miflash (save user data option didn't work either, btw.).
I lost all data on the device, but now everything works fine and the OTA update also ran through without any issues.
Now, I'm not sure if I will fiddle with magisk again. I really don't have no clue about what went wrong at all...
Thanks
Click to expand...
Click to collapse
Thanks for sharing.
Maybe something to try for next time to restore data, I don't know.
I haven't tested yet but I did make a backup using the method explained here
https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/
I have yet to try (or need) the restore function but running that backup created a 6gb file. My understanding is this is the majority of your apps, data, messages, etc
Without twrp I was hesitant to root but with the bit of knowledge and files shared here so far I have moved forward and glad I did. I haven't had to flash the stock image yet but hopefully this backup helps ease the pain. It is nice to be able to modify at will
BubuXP said:
Please go see my guide, I just added a troubleshooting section that you should check:
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
Your feedback could improve it further.
No, flashing boot.img will not erase any data on the phone. But you must remove any PIN, password or screenlock before proceeding, or you could not access your data anymore (because of encryption).
Click to expand...
Click to collapse
Had the same problem. I tried to install the OTA of March, followed the guide to install OTA with Magisk, but after unistalling Magisk, i tried to install the OTA but it gave me this message "installazione riprenderà automaticamente quanto il dispositivo non sarà attivo";
I looked for some help online, but didn't find anything, so skipped to the point c, and i got this bootloop now.
I tried the "set_active b" command, but I'm still in bootloop. I tried to flash the stock rom but apparentrly it's impossible to do it without recovery (which I'm unable to open), so... Help?
EDIT: By using miFlash and using the flash_all command I flashed the most updated ROM I found on MIUI.en, which is the january's one. It worked, even if the build version (10.0.3) is different from the one I had previously (10.0.4). The system says that there's an available update, but i'm too afraid to try it. Suggestion are accepted!
Hello,
It all began that i just wanted to restart my Oneplus3 unlocked with lineage 15.
But then back in Lineage15 i wasnt able to use my pin anymore + it restarted after few seconds...
Afterwards i ended up in a lineage bootloop.
Ok, then i thought then i do a fresh flash with new lineage 16.
I tried to flash but it said i need to install new modem firmware for Lineage16.
I downdloaded the new 9.0.5 modem + firmware and flashed it from here : https://forum.xda-developers.com/oneplus-3/how-to/op3-flashable-firmware-modem-zips-t3816066
Then i tried to flash LOS16 again but it failed due to some errors on unable to mount some partitions (cache , system, etc).
So i thought i need to wipe or reformat them, as some people suggested to switch from ext4 to fat and back to reinit the partition.
I did this for at least system and internal storage. ( i learned that it was a dumb idea )
Afterwards i was not able to push anything anymore through MTP in TWRP, but i was still able to sideload or push images via adb.
Afterwards i tried to flash LOS16 or LOS15 via TWRP again but it always ends up to a "unable to mount /system (invalid argument" error at some point of the installation.
I thought: Okey maybe i go back to stock as i messed up the internal file system somehow, and go back to LOS afterwards.
So i flashed the stock recovery for nougat which i got from here: https://www.****************/2017/0...th-latest-oxygen-os-firmware-complete-unroot/
Then i tried to flash various stock Oxygen roms with the stock recovery, by using wipe + system reset + adb sideload:
4.02, 4.51, 5.08, 9.0.5
4.02 and 9.0.5 didnt run until the end.
Flashing 5.08 works but ends up in a black screen when starting it.
Flashing 4.51 works but when i start it i run into a bootloop ( 2 Dots circuling forever )
I also tried to use the 4.51 version to flash LOS again but it did not work out
I just tried again to flash 4.51 but it also didnt work out anymore. :\
So, what do you think i could do to get a working OS on my system again?
Did i do something on the installation of LOS or Oxygen ?
Can i use a backup from a friends Oneplus3_T to get a working system partition / full OS again?
Should i unbrick the phone by using one of various guides to go back to fully stock? I am kind of afraid of this, as some people describe some final brick in the threads which may be caused by modem firmware problems (Sahara issue). https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/ or https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Thank you so much, i kind of getting mad about it
@julledd
Backup from 3T seems like a bad idea.
You may have a hardware issue.
Your best bet is to use one of the tools available in the various unbrick guides. If one doesn't work, try another.
Best of luck!
Hi thx for your help!
i tried different unbrick tools (9.0.5 / 3.1.2 / 4.0.5) and after several attempts i get it flashed to the phone. But in the end it still ends up in a bootloop, either at the android logo or the circuling dots. Via Sideload i am also not able to flash a new OS. It always breaks somewhen >50%.
In very rare cases i am then able to go to the OS, but when i go to "About Phone" to unlock it for TWRP, it freezes before showing anything. I guess there is internally something broken which forbids it to show the internal state of the phone. Every boot is different, and i cannot see any system in this failure of my phone.
Do you have any more hint?
I am already at a point where i want to exchange the main PCB.. Is this possible for the Oneplus3? Can i also exchange it with a Oneplus3T PCB?
.
rodagola said:
Hello everyone on xda, please bare with me. Here's my story
I own a Redmi Note 8 pro, chinese rom model. It was running miui 11.0.3 over android 9 If I recall correctly.
Ok so... I was tired of some of the china apps pushing their notifications over and over and auto installing stuff, so I looked up how to apply adb commands to remove such bloatware, which was a fairly simple process. I copied and pasted a list of safe stuff to delete I found around some forums.
then... there were some other packages I checked out using an app called "app inspector", which directly tells you which app is under which package (totally useful for this purpose).
I tried to be careful not go overboard since I don't have any root access, or custom recovery, and wasn't really planning to have these, just wanted to keep this as my simple daily driver cellphone, but also perform this little maneuver to get rid of some bloatware.
little did I know, I was about to somehow softbrick it. More info: I did not use a screen lock method other than the "swipe up".
Ok, so I uninstalled some packages I cannot remember exactly how they went, but they had the terms "xman" and "yman" on them I think, I wasn't so sure about them because I looked them up on the web yet they didn't appear anywhere. I think they went something among the lines of "com.android.miui.xman". I also uninstalled 2 or 3 more, but after googling, they seemed unsuspecting.
Anyways, I'm aware there's a command to reinstall the packages because they're still on the phone's ROM image. That is in case I had to restore anything back to normal. Turns out I later rebooted the phone and when it launches the lock screen, I keep swiping up but it won't take me over to the actual MIUI launcher. The screen is frozen on the lock screen.
I'm not freaking out at this time because I still tried to connect the device to the pc, and it still shows as connected, I then go to the adb console and type "adb devices", it is still recognized, however, it says next to it that it is unauthorized... damn it. So now I might not be able to run the commands that allow me to reinstall the exact packages that are rendering the phone softbricked (I guess), plus I'm not really sure which package caused this.
After about a minute or two on the lock screen, the phone takes me to the "redmi-recovery 3.0",
which displays 3 options:
Reboot to system: which basically forms a loop
Wipe date: godforbid... really don't want to do it since I likely had many files not backedup
Contact miassistant: not sure what to do with this, says "pcsuite.mi.com" at the bottom
on the miassistant option you can apparently sideload stuff, idk how to go about this, maybe it allows me to install a slightly upgraded ROM, which in turn will work the same as if it was an OTA update (so it will keep my data as it was instead of wipe)? Because the point is not to erase my user data!!
I'm not sure how to feel or what to do without losing my pictures, notes and documents
I have hopes this situation can be turned around back to normal, and like the title implies... I'm WILLING to PAY you through paypal or something to WHOEVER offers to guide me through in the best way possible. Please if you have the knowledge/experience don't hesitate I'll also be grateful timelessly.
I'm not an expert at these scenarios so I might as well ask on xda where most are really skilled! Thanks in advance to those amazing souls
Click to expand...
Click to collapse
tldr;
If you can boot into fastboot mode you can just flash a official MIUI fastboot ROM:
Xiaomi Firmware Updater (where you can download official MIUI ROMS): https://xiaomifirmwareupdater.com/
This is the current hard unbrick method: https://telegra.ph/Installing-Redmi-Note-8-Pro-firmware-via-SP-Flash-Tool-01-21
It should also work in your case and there's even a video guide.
This is another video guide for fixing a hard brick:
Both methods above will format your phone though (afaik all data will be lost).
Compass.
.
rodagola said:
are these the kind of roms that you unzip and have the BL, AP, CP, CSC files? I could try that, but I've heard installing home_csc will not override/wipe my personal data. If this is what you meant, can you confirm? Or do you reckon these linked video tutorials would not wipe the data?
Click to expand...
Click to collapse
Nope, it doesn't.
If you can boot into Fastboot, flash the ROM using Mi Flash, otherwise, use this tutorial:
.
Compass Linux and juliusjr have told you the method, so I will just add supplemential infos.
In your case, I think simple upgrade will do the trick, dirty flash is applicable both via fastboot flash (mi flash) and recovery flash (the mi assistant method). If you want to stop the ads, I will recommend you to unlock your bootloader, move to global, root, and use an adblocker (a bare minimum config, in trade of some bangking apps being blocked).
I don't know the corresponding version for miui china rom, but in global rom, prior 12.0.0.7 (the one with the early 2021 security update), you can dirty flash back and forth while keeping your data.
.
rodagola said:
Hi, thanks for your info, I would like to try the mi flash tool as I've been told before the stock recovery thing has less chances of working. However, I had dev options turned on before but didn't manage to turn on the "OEM unlock" option, will flashing original ROMs work this way? or did I need that option toogled on? That's my last doubt, and thanks a lot. Btw, the China ROM this Redmi N8P had never ever showed me any ads, but thanks a lot as well for such input
Click to expand...
Click to collapse
You still have a locked bootloader? (How do I know? You will see "Unloked" on the bottom of the screen everytime your device reboots and showing mi logo if your device is unlocked)
Hmm, mechanically it work like normal ota update. Full recovery update will ony erase nessesary partitions (system, boot, and some other things) while keeping your data intact. So doing this to your phone technically safe. You can do this with MiFlashPro, do a recovery update using a recovery rom (the 2 gigs one) greater than your current MIUI version. But please bear in mind that I have never done this before to a locked phone. A same distribution version IS A MUST (i.e. global with global).
Oh and it will need you to log in to your xiaomi account. My guess is you need the flash permission open for your account (if you have unlocked your phone you shouldn't have a problem). I have never flashed with an account that never have been used to unlock a bootloader, so I might be wrong.
If your phone is bootloader unlocked, Mi Flash is the least demanding and it can retain your data with "save user data" in the bottom right corner option on, regardless your miui version (but I think there will be some problem with installed apps if you downgrade from A10 to A9).
Hope this help.
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