Database Develop

Twrp problem please help!

So let me explain the whole story, so a couple days ago i install OOS 4.0 on my Oneplus 3T and tried to root it, bearing in mind i was already rooted when i upgraded and I lost my root privileges. So then when i tried to re-root my phone it ahs come up with "dm-verity has not started in enforcing mode and may not work properly", so a bit weird but then i tried to install TWRP and when i booted into TWRP, it just stayed at flash screen of TWRP and wouldn't initialize. I have being trying ever since, factory resetting my phone, re-root etc. Please help me!
I CANNOT BOOT INTO TWRP, IF YOU WERE GOING TO SAY THAT!

Boot it into a boot loader and use this :
https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
Choose option 4 and make sure you are unlocked.
Choose option 7 and wait a few moments to see if that works. If not try the UnBrick tool.

How long have you been waiting on the TWRP startup screen? You do know it takes a long time to startup using F2FS and encryption on data partition, up to a minute from what I've heard.

pitrus- said:
How long have you been waiting on the TWRP startup screen? You do know it takes a long time to startup using F2FS and encryption on data partition, up to a minute from what I've heard.
Click to expand...
Click to collapse
I'd normally wait around 5 minutes
UPDATE:So i just booted into TWRP and have been waiting around one minute and it is still on the splash screen.

Look at this:
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306

DarqAnshin said:
Look at this:
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
I'll check it out.

DerpDiamonds said:
I'll check it out.
Click to expand...
Click to collapse
It didn't work

is your bootloader locked or unlocked?

This question seems to keep repeating itself due to missing information on TWRP post about the latest official version being incompatible with OOS 4 encryption method, but that is the explanation. There is a beta release of TWRP in post 550 in that thread that is supposed to fix this.

DerpDiamonds said:
I'll check it out.
Click to expand...
Click to collapse
pitrus- said:
This question seems to keep repeating itself due to missing information on TWRP post about the latest official version being incompatible with OOS 4 encryption method, but that is the explanation. There is a beta release of TWRP in post 550 in that thread that is supposed to fix this.
Click to expand...
Click to collapse
Oh i get it now, thanks i'll wait for TWRP to update. Thanks!

How to root 3T on OOS4.0 ?

Hey,
I bought my phone 2 days ago, after charging it I updated to OOS4.0 through the system updates using VPN, when I got home I unlocked the bootloader but did nothing else afterwards. I'm seeing a lot of threads with people having issues with TWRP and encryption, considering my last device was the OPO and I was running Lollipop (was too lazy to update it ) I'm kinda out of the loop.
How can I root it now that it's running Nougat ? simply flashing the twrp img using fastboot and then flashing the SuperSU zip or is there a different method ?
Any kind of help is greatly appreciated.
Also, one more question, is Xposed working on Nougat ? I had quite a few useful modules on my OPO, wanted to know if that's possible on the 3T as well.

The beta builds of the TWRP which are compatible with the OOS 4.0.0 are available. You can find them from the thread.
If you want to use the Xposed modules, you should downgrade to 3.5.4.

WeirdSoup said:
The beta builds of the TWRP which are compatible with the OOS 4.0.0 are available. You can find them from the thread.
If you want to use the Xposed modules, you should downgrade to 3.5.4.
Click to expand...
Click to collapse
And where should I download SuperSU from ? Heard the project is being taken over or smth like that

B00steed said:
And where should I download SuperSU from ? Heard the project is being taken over or smth like that
Click to expand...
Click to collapse
http://www.supersu.com/download
Actually, I'm using the Magisk instead. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

WeirdSoup said:
http://www.supersu.com/download
Actually, I'm using the Magisk instead. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Is it better to install this instead of SuperSU ?

If you are interested in using apps which detect root or a modified system/bootloader (Android Pay, Pokémon Go, some banking apps) then yes. Otherwise, no benefit of Magisk (v10.2) for you and may as well use SuperSU which is simpler to install.

B00steed said:
Is it better to install this instead of SuperSU ?
Click to expand...
Click to collapse
It's case by case, and I don't know which one is good for you. Do some research and figure out yourself.
---------- Post added at 11:30 AM ---------- Previous post was at 11:24 AM ----------
23Six said:
If you are interested in using apps which detect root or a modified system/bootloader (Android Pay, Pokémon Go, some banking apps) then yes. Otherwise, no benefit of Magisk (v10.2) for you and may as well use SuperSU which is simpler to install.
Click to expand...
Click to collapse
Magisk is open source, and it is also easy to install. You can also install the Magisk modules. It's not a simple root-hide app as many people still misunderstand.

So, with oxygen 4.0.1 the procedure will be the same?

TWRP Stuck Mount password
Greetings guys..
Yesterday I got my 3T and upgraded OTA latest OxygenOS 4.0.1. I was able to unlock bootloader and install TWRP 3.0.3 but when I access bootloader the first screen ask me to provide "Decrypt password" to mount, and if I ignore and slide to start modification I don't have access to internal card (assume its READ-ONLY), just folders are visible but unable to find or install SU package.
I check all the forums but didn't find any relevant information how to get out of TWRP "Decrypt password" issue. I don't want my phone to be encrypted, so I would appreciate if you can please help me to root my 3T.
Cheers

junostik said:
Greetings guys..
Yesterday I got my 3T and upgraded OTA latest OxygenOS 4.0.1. I was able to unlock bootloader and install TWRP 3.0.3 but when I access bootloader the first screen ask me to provide "Decrypt password" to mount, and if I ignore and slide to start modification I don't have access to internal card (assume its READ-ONLY), just folders are visible but unable to find or install SU package.
I check all the forums but didn't find any relevant information how to get out of TWRP "Decrypt password" issue. I don't want my phone to be encrypted, so I would appreciate if you can please help me to root my 3T.
Cheers
Click to expand...
Click to collapse
I think you need latest twrp beta 1, it should be in twrp tread, look in last pages or here https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074

bertozzi243 said:
I think you need latest twrp beta 1, it should be in twrp tread, look in last pages or here https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
Click to expand...
Click to collapse
Thanks for quick reply, I'll check it.

bertozzi243 said:
I think you need latest twrp beta 1, it should be in twrp tread, look in last pages or here https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
Click to expand...
Click to collapse
Installed TWRP 3.0.3.1 BETA .... How long does it really take to decrypt new phone without any apps? Just to have an idea. When I started TWRP it asked for password and I used the PIN assigned to login to screen ... now going on for 5 minutes now.
Following on the screen:
Mount
Try Decryption
Updating partition details...
....done
Unable to mount storage
Full SELinux support present
---------blue animation-----------

junostik said:
Installed TWRP 3.0.3.1 BETA .... How long does it really take to decrypt new phone without any apps? Just to have an idea. When I started TWRP it asked for password and I used the PIN assigned to login to screen ... now going on for 5 minutes now.
Following on the screen:
Mount
Try Decryption
Updating partition details...
....done
Unable to mount storage
Full SELinux support present
---------blue animation-----------
Click to expand...
Click to collapse
I read that it takes some minutes if you are f2s and encrypted but I don't know how to proceed since I haven't flashed twrp and root yet.
Sorry but you may have to wait someone who has already done it

What is the correct way to re-enable encryption?

If I have formatted and installed with encryption disabled, what is the right way to get encryption back?
Can I just go into Settings>Security & Fingerprint>Encrypt Phone and enable it there?

Yup, that should do the trick. Didn't try on T3, but used same method on one of my prev phones.

Did that work?

I did it on OOS 4.1.1 with twrp and franco kernel installed. It worked for me :good:

AndreiVolk said:
I did it on OOS 4.1.1 with twrp and franco kernel installed. It worked for me :good:
Click to expand...
Click to collapse
I wonder if it works with a non oos rom though

stonew5082 said:
I wonder if it works with a non oos rom though
Click to expand...
Click to collapse
Well all custom roms work fine with encrypted devices so i don't see why it shouldn't be possible to encrypt your device on a custom rom. If you want to be 100% sure ask in the thread of your rom

AndreiVolk said:
Well all custom roms work fine with encrypted devices so i don't see why it shouldn't be possible to encrypt your device on a custom rom. If you want to be 100% sure ask in the thread of your rom
Click to expand...
Click to collapse
It worked. I disabled root to be on the safe side and encrypted. I get errors in twrp now, but they don't seem to effect anything.

stonew5082 said:
It worked. I disabled root to be on the safe side and encrypted. I get errors in twrp now, but they don't seem to effect anything.
Click to expand...
Click to collapse
May i know what error TWRP gives after you encrypt your phone ?
I plan to do so as well...

stonew5082 said:
It worked. I disabled root to be on the safe side and encrypted. I get errors in twrp now, but they don't seem to effect anything.
Click to expand...
Click to collapse
nicknacknuke said:
May i know what error TWRP gives after you encrypt your phone ?
I plan to do so as well...
Click to expand...
Click to collapse
Root is not a problem neither. i did it with root enabled.
That twrp error is normal. When you boot in twrp it shows the error that it can't mount data because you're encrypted and you need to type in your password first.
I also suggest you to use blu_spark's twrp because it's always updated. The official twrp for the op3t hasn't a maintainer anymore and it seems abbandoned..

AndreiVolk said:
The official twrp for the op3t hasn't a maintainer anymore and it seems abbandoned..
Click to expand...
Click to collapse
How do you figure that?
https://eu.dl.twrp.me/oneplus3t/

Didgeridoohan said:
How do you figure that?
https://eu.dl.twrp.me/oneplus3t/
Click to expand...
Click to collapse
I mean here on xda. The last build on xda is the 3.0.4.1 which it never came out. There was the 3.1.0.0 which had the wipe bug for the 3t. I don't know who is making those builds and i don't neither know if they test it.

AndreiVolk said:
I mean here on xda. The last build on xda is the 3.0.4.1 which it never came out. There was the 3.1.0.0 which had the wipe bug for the 3t. I don't know who is making those builds and i don't neither know if they test it.
Click to expand...
Click to collapse
You were talking about the official builds... That's the official downloads from the official TWRP website (https://twrp.me). There's a world outside XDA as well...

[SOLVED] Phone changed the model in TWRP

Hey,
I have question about a problem I have.
So I tried to install the latest open beta version (beta 17) on my OnePlus 3T through TWRP.
This didn't worked because of ERROR: 7.
I found some solutions to fix ERROR 7 but it doesn't worked with this OS.
I tried some things like updating TWRP and installing the Oxygen recovery. I messed some things up. I deleted my OS from my device accidentally.
I solved the problem and was able to install the latest stable OS without problems.
Then I tried to install ResurrectionRemix-N for OP3T and I got the ERROR 7 again. but it said:
E3004: This package is for device: OnePlus3T, oneplus3t; this device is Oneplus3.
The thing is, it is an OnePlus 3T.
I don't know why and how it changed. The TWRP is for OP3T.
In the settings it says that the Build-Number is: ONEPLUS A3003_28_171012.
So I don't know. The default device name was OnePlus 3T.
Later I got an automatic email from Google because I logged in on an "new" device. But here they say that it is an OP3.
I would like to change it, but I don't know how.
I thought I can just change someting in the build.prop, but I didn't tried it yet.
Hopefully someone can help me.
-Fun4Jan

Okay so, I went in the build.prop and this is what I found:
ro.build.product=OnePlus3
ro.build.user=OnePlus
ro.build.flavor=OnePlus3-user
ro.build.description=OnePlus3-user 7.1.1 NMF26F 136 dev-keys
ro.common.soft=OnePlus3
ro.display.series=OnePlus 3T
ro.build.oemfingerprint=7.1.1/NMF26F/10122113:user/release-keys
[...]
ro.build.ota.versionname=OnePlus3TOxygen_28_1710122300
ro.build.version.ota=OnePlus3TOxygen_28.A.57_GLO_057_1710122300
So do you think I can just change it in the build.prop?

Yes, you can change it in the build.prop.
please try changing it and report us back.

akash.galaxy07 said:
Yes, you can change it in the build.prop.
please try changing it and report us back.
Click to expand...
Click to collapse
So I changed it and tried to install it but failed. It tells me that it is an OP3

Try the Qualcomm MSM Tool and try resetting your device completely as instructed on the Unbrick guide. Looks like you installed a corrupted Open Beta package, and something from Bootloader configuration went completely haywire. You can backup your Internal Storage since you have TWRP access.
Good Luck!

Have you tried using TWRP version 3.1.1-0?

Fun4Jan said:
So I changed it and tried to install it but failed. It tells me that it is an OP3
Click to expand...
Click to collapse
With oreo use this TWRP https://forum.xda-developers.com/devdb/project/dl/?id=27068
after flash again beta 17

przemcio510 said:
Have you tried using TWRP version 3.1.1-0?
Click to expand...
Click to collapse
I tried it with TWRP 3.1.1-2 for the OnePlus 3t

thes3usa said:
Try the Qualcomm MSM Tool and try resetting your device completely as instructed on the Unbrick guide. Looks like you installed a corrupted Open Beta package, and something from Bootloader configuration went completely haywire. You can backup your Internal Storage since you have TWRP access.
Good Luck!
Click to expand...
Click to collapse
Okay, I will try it. I hope it works

kob72 said:
With oreo use this TWRP https://forum.xda-developers.com/devdb/project/dl/?id=27068
after flash again beta 17
Click to expand...
Click to collapse
Can you Explain it to me a bit detailed please.

Fun4Jan said:
Okay, I will try it. I hope it works
Click to expand...
Click to collapse
So I tried it with this instruction: http://www.androidbrick.com/oneplus-one-two-3-3t-5-mega-unbrick-guide-twrp-flashing/
I did it like it says but some things were different and I think it was because my phone worked and wasn't bricked.
Now I have my phone and got the oldest OOS 3.5.1. My changeable Phonename is OnePlus 3T but I got a mail again where it says that I logged in with a OnePlus 3.
I will try to install TWRP and the latest OOS version.

So I finally solved it.
I was a bit confused with the TWRP version, so I thought that I can install the latest OOS with the Oxygen Recovery and I saw, that I used the wrong Recovery for my phone.
I used the right TWRP version for my phone but not the right Oxygen Recovery when I tried it with it.
I thank all you guys for the help.

Fun4Jan said:
So I finally solved it.
I was a bit confused with the TWRP version, so I thought that I can install the latest OOS with the Oxygen Recovery and I saw, that I used the wrong Recovery for my phone.
I used the right TWRP version for my phone but not the right Oxygen Recovery when I tried it with it.
I thank all you guys for the help.
Click to expand...
Click to collapse
No problem, would you mind adding [SOLVED] to the title, so other users with the same or similar problem will read this post to fix their devices too?
Thanks, and happy flashing!

Fun4Jan said:
I tried it with TWRP 3.1.1-2 for the OnePlus 3t
Click to expand...
Click to collapse
Then try with the older version, the newest one is known to cause problems with proper device detection.
Edit: nevermind, just saw it's fixed.

[STOCK] Stable realmeUI/Android 10 ROM for RMX1991

Hi folks,
What we used as beta ROM is now published as official stable release known as version RMX1991_11.C.12 for Chinese model of Realme X2.
Probably anyone can upgrade the phone now in any possible way.

The bad news is FP stops working as soon as you patch vbmeta for disabling AVB...

The good news is that there's no verification of system partition. You can leave vbmeta untouched and modify whatever you want except boot.

yakovpol said:
The good news is that there's no verification of system partition. You can leave vbmeta untouched and modify whatever you want except boot.
Click to expand...
Click to collapse
Then, you will not loose fingerprint?

AlAneed said:
Then, you will not loose fingerprint?
Click to expand...
Click to collapse
Exactly

yakovpol said:
Exactly
Click to expand...
Click to collapse
Magisk can be installed and we still have the fingerprint working?

AlAneed said:
Magisk can be installed and we still have the fingerprint working?
Click to expand...
Click to collapse
No, Magisk is patching boot, which will require you to disable verification by means of vbmeta. You can try system-based methods like one of SuperSU.

yakovpol said:
No, Magisk is patching boot, which will require you to disable verification by means of vbmeta. You can try system-based methods like one of SuperSU.
Click to expand...
Click to collapse
but in order to fix twrp replace issue vbmeta verification is needed to be disabled right??

I will try to search for it. Is it just a normal app to install from Play store? or requires other method?
One more thing, TWRP working with it or no?
Thanks
---------- Post added 10th April 2020 at 12:36 AM ---------- Previous post was 9th April 2020 at 11:38 PM ----------
I guess I am not able to understand how to do root? I searched for system base root in the web with no luck
Would you mind explaining how to do root without Magisk?

osamanazim said:
but in order to fix twrp replace issue vbmeta verification is needed to be disabled right??
Click to expand...
Click to collapse
No. At least a few last CN ROM versions are insensitive to recovery replacement. You can keep stock vbmeta and flash custom recovery. But recovery will be replaced when you boot system, i.e. you flash custom recovery for single and immediate use

yakovpol said:
No. At least a few last CN ROM versions are insensitive to recovery replacement. You can keep stock vbmeta and flash custom recovery. But recovery will be replaced when you boot system, i.e. you flash custom recovery for single and immediate use
Click to expand...
Click to collapse
Will i lose any file if i update from color os 6.1 to realme ui or i need to backup first?

Mikelsteven said:
Will i lose any file if i update from color os 6.1 to realme ui or i need to backup first?
Click to expand...
Click to collapse
Backup is a nice thing. I would always insist on creating backup.
I successfully switched onto realmeUI without losing data. As I understand, you have to do it from A.17 (for CN device). My path was A.16 -> C.02, but now many are suggested to upgrade from A.17 straight to C.12.

yakovpol said:
Backup is a nice thing. I would always insist on creating backup.
I successfully switched onto realmeUI without losing data. As I understand, you have to do it from A.17 (for CN device). My path was A.16 -> C.02, but now many are suggested to upgrade from A.17 straight to C.12.
Click to expand...
Click to collapse
Thanks man. I don't know what reliable backup method i can use on an unrooted phone. I'm on A17 so i guess it's safe to upgrade without backup. Again, have u experienced any bug so far on realme ui?

Mikelsteven said:
Thanks man. I don't know what reliable backup method i can use on an unrooted phone. I'm on A17 so i guess it's safe to upgrade without backup. Again, have u experienced any bug so far on realme ui?
Click to expand...
Click to collapse
Put some labour on searching through Internet please. So you will be sure if to update or not
To me it works just fine.

Mikelsteven said:
Thanks man. I don't know what reliable backup method i can use on an unrooted phone. I'm on A17 so i guess it's safe to upgrade without backup. Again, have u experienced any bug so far on realme ui?
Click to expand...
Click to collapse
Black Screen problems while playing COD Mobile. Iit is a common problem on sobre Android 10 upgraded devices.
But all the rest of software running and working smoothly.

can someone please confirm if the feature of Waze returning to top during voice call is working? i have the globalized version by mettis and it doesn't work there (have CN device)