Database Users

system keeps flashing stock recovery?

My phone was rooted for the longest time without any problems, but some time ago (I'm assuming after the Treble update) apps would not detect root, although any app that was already using root could continue doing so.
I checked Magisk, which said root was not installed. I booted my phone into recovery, and somehow my phone had the stock recovery flashed on it. I tried flashing TWRP on it again, and it worked. Except, when I rebooted my phone into recovery later again, it went back to stock recovery.
I have no idea what's going on, and would really appreciate some help.
(PS: I do know how to update my phone without the phone reverting to stock recovery, I've done it many times before, so that can't be the problem)

update: I tried flashing TWRP again (through bootloader), and this time I jumped straight to recovery. It showed all the directories as if my phone had just been completely wiped. Internal memory 0M. No files anywhere. Didn't even have a downloads folder.
In a panic, I rebooted my phone, but my phone was actually untouched, no data wipe whatsoever. I'm even more confused about what the hell is happening now.

The stock OOS will automatically reflash the stock recovery if it detects it has changed to something else.
You have to boot into TWRP right after installing it and either let it mount /system read-write (likely to cause problems later) or install something like Magisk that will prevent overwriting the recovery.
TWRP was not able to read your data partition, which can happen depending on which kind of encryption you have. Try the BlueSpark TWRP, it supposedly supports encryption better than the official one.

It's the version. If I use 3.2.3.0 or 3.2.2.0 I get no files. But 3.2.1.1 works for some reason. You can also install pie now. There is a link in the one plus 5 forums here to hydrogen os. It's Chinese version but that doesn't matter. It is in English. You will need to uninstall a few Chinese bloatware apps and flash gapps. But besides that I don't see much difference. If anything the hydrogen os looks nicer. I'll add some screenshots . Developer options was enabled from first boot, with the advanced reboot menu I noticed.

Also, if you have root the TWRP app can flash recovery from in the OS.

Fif_ said:
The stock OOS will automatically reflash the stock recovery if it detects it has changed to something else.
You have to boot into TWRP right after installing it and either let it mount /system read-write (likely to cause problems later) or install something like Magisk that will prevent overwriting the recovery.
TWRP was not able to read your data partition, which can happen depending on which kind of encryption you have. Try the BlueSpark TWRP, it supposedly supports encryption better than the official one.
Click to expand...
Click to collapse
It's frustrating for sure. Lol

.

.

HMSS013 said:
Had my new OP5 rooted and almost everything was right in the world, but i flew too close to the sun by uninstalling a few apps I thought were expendable and eventually Google Play Services started crashing. When all troubleshooting failed I ended up flashing a fresh copy of OxygenOS (5.1.7) to my device, but every attempt to re-root the device has failed.
The first obstacle I ran into was that there was no access to Internal Storage in TWRP, I was able to fix that by Wipe > Format Data and then using Advanced Wipe to clean Dalvik/Cache/System/Data for good measure.
My next issue was that TWRP returned Error 7 when attempting to flash the stock OOS rom... after some digging I was able to clean the 'asserts' line from the updater-script file and now the rom will flash.
The headache has been getting the device re-rooted, and I feel like I've tried everything. I have to flash the SuperSU or Magisk zip (both fail to root the device) before reboot because the dm-verity encrypts on first boot and after that I can't access any storage to flash from internal memory. The three different dm-verity patches I've found don't prevent it. I also tried 'fastboot oem disable_dm_verity' to try and stop it but after talking with the device fastboot returns 'unknown command'.
My final effort to get around it was to flash a kernel that didn't force dm-verity (blu_spark kernel) but that returns Error 1: 'Unsupported Android Version' when I attempt to flash it.
I've tried dozens of variations on this, including a Lineage OS rom instead and also trying to sideload certain zips, but still no dice. Any and all help would be appreciated.
Click to expand...
Click to collapse
Which rom do you want to install?

HMSS013 said:
The first obstacle I ran into was that there was no access to Internal Storage in TWRP, I was able to fix that by Wipe > Format Data and then using Advanced Wipe to clean Dalvik/Cache/System/Data for good measure.
Click to expand...
Click to collapse
Hi, this one is because of your TWRP. Please flash Codework's TWRP and try that with it. It should solve your issue for sure. (same thing happened to me while I tried installing custom roms and every time I needed to wipe everything to see my internal storage again)
This guide can help you out with Error 7 on TWRP https://forum.xda-developers.com/showthread.php?t=2522762
I do believe your this issue you're having caused by TWRP. Also after rooting the phone, install magisk app. (you don't need to install supersu, it comes with magisk). After rebooting into system reboot your phone again once more it should show up on magisk app that you've successfully rooted your phone. Remember after flashing magisk you need to reboot twice in order for phone to realize it. Please try the steps I told you and let me know.
Also you don't need to flash dm-verity patch at all.
Try clean flash instructions with Codework's TWRP and root it with latest Magisk.

.

.

HMSS013 said:
I actually really like the Oreo version of OxygenOS, so when I had to resort to re-flashing to fix this mess I dug up one of the stock (5.1.7) roms, it served me well (assuming I can get it rooted, lol).
I'd be willing to move to Lineage if I absolutely have to, but if not, I'd really like to keep Oreo if at all possible.
Click to expand...
Click to collapse
For 5.1.7 try this twrp https://drive.google.com/file/d/1UlTftbe6wooAs4Fp0cjwXlOKmfQHgdfL/view?usp=drivesdk along with magisk 17.1.
Clean flash is recommended. If it didn't help, please list your steps again(detailed).
Don't use supersu and skip the other suggestions for now please.

.

Root lost after 9.0.13

Hey guys.
Just updated to 9.0.13 last night and today I saw that my root was gone.
I was rooted with Magisk, and did the same as usual. Uninstalled Magisk, downloaded and install the update from System, and after that I Installed Magisk on the second partition (after OTA update) just like in the tutorial..
Any solutions to regain root without wiping the phone ? I already fuc*d it up last month and lost everything .
Regards,
Switiz

In my case it installs magisk after updating and everything worked fine. Reinstall it from the TWRP and it should work.

I don't have twrp installed. is there any possibility to install it without pc ?
p.s I don't have a recovery. every time I try to go to recovery, I have a menu with 3 languages ( 2 Chinese and English ) and the only options are Wipe data and cache and reboot

Switiz said:
I don't have twrp installed. is there any possibility to install it without pc ?
p.s I don't have a recovery. every time I try to go to recovery, I have a menu with 3 languages ( 2 Chinese and English ) and the only options are Wipe data and cache and reboot
Click to expand...
Click to collapse
How did you get root without flashing magisk inside of twrp? And if you did the update that came thru your phone that's why you lost root.. from what I read it's best to always flash full stock. No partial updates

You updated incorrectly. So now you have the stock recovery. You will need a PC to fix it. It's not a big deal, you're just starting over. You will need to boot the TWRP image again, flash the TWRP installer. Then flash magisk. BEFORE you do anything, back up all your data.
Follow this guide here. <-- Use this to reinstall TWRP and Magisk.
Use this guide to update from now on. <-- Download update files here. Dirty flash them, follow the TWRP instructions. I don't even uninstall Magisk personally, but go ahead if you want, as the official instructions say to. No data loss. No losing root. Do not use the OTA update (unless you are stock), do not use Magisk to update (Magisk works, it just seems to mess people up), etc.

Thank you. I will try when I get home.
I update using the tutorial from the page you provided :/.
"Update Process for Rooted Users
1. Magisk Manager > Tap "Uninstall" > Tap "Restore Images" (DO NOT REBOOT)
2. Now Run the System update to download and install the full OTA zip (DO NOT REBOOT)
3. Close all background apps
4. Open Magisk > Tap "Install" > Tap "install" again > Tap "Install to Inactive/Second Slot (After OTA)"
5. Finally tap Reboot after Magisk installation is complete."
It's not the first time. I don't know why this time it didn't worked..

After booting in twrp and installing Magisk, after reboot, I still don't have root :|
https://imgur.com/a/hjGwQkR

Try this
https://forum.xda-developers.com/on...t-oneplus-6t-using-oneplus-6t-rooter-t3864238

OhioYJ said:
You updated incorrectly. So now you have the stock recovery. You will need a PC to fix it. It's not a big deal, you're just starting over. You will need to boot the TWRP image again, flash the TWRP installer. Then flash magisk. BEFORE you do anything, back up all your data.
Follow this guide here. <-- Use this to reinstall TWRP and Magisk.
Use this guide to update from now on. <-- Download update files here. Dirty flash them, follow the TWRP instructions. I don't even uninstall Magisk personally, but go ahead if you want, as the official instructions say to. No data loss. No losing root. Do not use the OTA update (unless you are stock), do not use Magisk to update (Magisk works, it just seems to mess people up), etc.
Click to expand...
Click to collapse
Thanks for this link.

Not sure if you've managed to fix this issue, but I've never used to the uninstaller. I boot into TWRP and flash the full system image and then reboot back into TWRP and flash Magisk onto the active partition. If you don't reboot inbetween then you end up flashing Magisk to the current (old) partition rather than the new upgraded partition.

please help. tried to flash OTA and now i cant get back to OS

hey guys, so i used twrp to flash a OTA then flashed twrp again and rebooted and when i went to flash magisk i was just shown a list of all random numbers/letters. i booted into bootloader flashed twrp img, booted into recovery and all my files were there once again but i still cant get into the OS, can anyone please help?
why is flashing so complicated these days? even the recovery works different. the last time i rooted (4 years ago maybe) you could use twrp to make a backup and it was done simple as that (i did this on the oneplus 6t about 4 weeks ago and got the issue with my storage just being a list of numbers and letters and had to find a way to fully wipe and re install OOS) and the same for flashing, i could just flash something and it was fine, no issues.

Do you have an OTG adapter and pendrive? You can copy the full OTA zip, TWRP zip and Magisk zip on to that and flash from TWRP using that. Your internal storage is encrypted and you won't be able to access it until you can reboot OOS fully. If that didn't work, you may have to do a factory reset/wipe (including internal data) to get the phone to boot again. You will obviously lose any unbacked data.

Which version of TWRP are you using? Which version of OOS are you using? Most likely you just don't have the correct version, and you updated to the latest version OOS with the new security patch and it no longer can decrypt it.
Have you tried TWRP 3.3.1-7 from here? If you boot the .img file from fastboot, can you decrypt your data?
Most likely you just need to flash Magisk, and you will be fine. For updates, it's always as you did, flash the full OTA update, TWRP installer, reboot to recovery, Magisk. It is recommended to uninstall Magisk, however I usually don't do that personally. Official Instructions here. You just have to make sure you are using the correct version of TWRP, otherwise you can run into encryption issues, as you found out when there are updates.

OhioYJ said:
Which version of TWRP are you using? Which version of OOS are you using? Most likely you just don't have the correct version, and you updated to the latest version OOS with the new security patch and it no longer can decrypt it.
Have you tried TWRP 3.3.1-7 from here? If you boot the .img file from fastboot, can you decrypt your data?
Most likely you just need to flash Magisk, and you will be fine. For updates, it's always as you did, flash the full OTA update, TWRP installer, reboot to recovery, Magisk. It is recommended to uninstall Magisk, however I usually don't do that personally. Official Instructions here. You just have to make sure you are using the correct version of TWRP, otherwise you can run into encryption issues, as you found out when there are updates.
Click to expand...
Click to collapse
Latest twrp and latest full OOS OTA. If I fastboot the twrp. Img I can see all my data again. I've fixed it now, I flashed the twrp. Img in fastboot then rebooted system and it worked

Angler- Magisk module and data encryption

I flashed stock firmware successfully.the after few days unlocked the bootloader and flashed TWRP and installed Magisk 21.4 .after installing Viper4X and after the driver installation the phone didn't boot clearly.
When it asked for password during boot in stock Android I entered it , then it said "Decryption successfully . Unable to check data integrity " and showed a button "reset phone".
If this is the scenario.
Q1: Is it unwise to install Magisk in Encrypted phone ?
Q2: Or I should not install Magisk modules in Encrypted phone.
Ways to disable forced encryption in Nexus 6p 8.1 is appreciated..
And I tried format data and flashing Magisk.it did nothing and also no encryption zip file befor first boot..

Can I install nethunter on my stock encrypted Android with latest Magisk and twrp 3.1 fde?