Hey there!
I wanted to use my banking app, so I decided to get full to stock. Before I used OxygenOS Beta 20 with Magisk.
Currently:
Stock Recovery
OxygenOS Beta 20 or OxygenOS 5 (Same Problem)
Locked Bootloader
Now with a clean OS Safety Net still fails and the Google Play Store says "not certified".
Do you have any tips to get it working again?
kaisims said:
Hey there!
I wanted to use my banking app, so I decided to get full to stock. Before I used OxygenOS Beta 20 with Magisk.
Currently:
Stock Recovery
OxygenOS Beta 20 or OxygenOS 5 (Same Problem)
Locked Bootloader
Now with a clean OS Safety Net still fails and the Google Play Store says "not certified".
Do you have any tips to get it working again?
Click to expand...
Click to collapse
Did you flash all partitions (boot, recovery, cc system) including data, full wipe, before locking boot loader?
Sent from my Nexus 6 using Tapatalk
ben_pyett said:
Did you flash all partitions (boot, recovery, cc system) including data, full wipe, before locking boot loader?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
As far as I know, Yes. I know it doesnt make much sense.
I'd suggest that you unlock bootloader and then reflash, do a full wipe to be sure
Then lock again if that's the way you want to go
Sent from my Nexus 6 using Tapatalk
ben_pyett said:
I'd suggest that you unlock bootloader and then reflash, do a full wipe to be sure
Then lock again if that's the way you want to go
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Did that again now, but its still failing sadly.
kaisims said:
Did that again now, but its still failing sadly.
Click to expand...
Click to collapse
Try using unbrick guide if that is feasible for you. That way the error is reproducible if you still get it after the "unbrick" guide since all your partitions will be the same as ours.
Unlocked bootloader and Magisk by themselves shouldn't trip Safety Net, as long as you have Magisk Hide working. Now, that doesn't mean your specific banking app isn't doing other checks besides Safety Net (I think folks have seen this happen with some apps). But you mention Safety Net failing specifically, so I thought that worth mentioning.
Did you use the full update zip to get back to "full stock"? That would be the recommended approach, to make sure all partitions were returned to stock.
redpoint73 said:
Now, that doesn't mean your specific banking app isn't doing other checks besides Safety Net
Click to expand...
Click to collapse
Exactly that was the problem in the first place, why I started to lock my bootloader again. And yes I always had the full OS as a zip.
ZVNexus said:
Try using unbrick guide if that is feasible for you.
Click to expand...
Click to collapse
I used this: https://forums.oneplus.net/threads/guide-oneplus-3-3t-unbrick.531047/ unbrick guide and that worked!!
I am so happy!
kaisims said:
Exactly that was the problem in the first place, why I started to lock my bootloader again. And yes I always had the full OS as a zip.
I used this: https://forums.oneplus.net/threads/guide-oneplus-3-3t-unbrick.531047/ unbrick guide and that worked!!
I am so happy!
Click to expand...
Click to collapse
Yep, figured. Had to be some partition.
Related
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!
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...
Hi guys,
I tried a couple of years ago disabling encryption on my Nexus 6 and the performance was great, but as updates were released it turned out to be a pain to keep up always having to manually update the phone. My nexus 6 now is crawling and I'm thinking about trying to disable encryption. I could not find any sort of reports if it can be done on 7.1.1
Has anyone tried? Is there any guide? Thanks!
Mephisto_POA said:
Hi guys,
I tried a couple of years ago disabling encryption on my Nexus 6 and the performance was great, but as updates were released it turned out to be a pain to keep up always having to manually update the phone. My nexus 6 now is crawling and I'm thinking about trying to disable encryption. I could not find any sort of reports if it can be done on 7.1.1
Has anyone tried? Is there any guide? Thanks!
Click to expand...
Click to collapse
It's no different. If your bootloader is not unlocked, unlocking it will wipe the user data partition. If the bootloader is already unlocked, you'll need to wipe the user data partition.
*IN EITHER CASE YOU WILL LOSE YOUR DATA. DO A BACKUP FIRST
Then flash a ROM with an included kernel that doesn't force encrypt. Or, just flash a kernel that doesn't force encrypt.
Now that I've answered your question, IMHO, it's not worth the effort. If your phone is crawling, do a factory reset. On a stock ROM, go to Settings > Backup & Reset and make sure you have your Google backup settings enabled. Use the Factory Data Reset button to actually reset. READ through the information and confirm. This will cause your phone to reboot with a wiped system partition.
If your on a custom ROM I'm going to assume you know how to wipe through recovery.
ktmom said:
...., IMHO, it's not worth the effort. If your phone is crawling, do a factory reset.....
Click to expand...
Click to collapse
My 7.1.1 uses the lite stock rom of Danvdh.
I think you're right about the hassle. Only decrypting is not enough. But debloating and removing unused stuff and decrypting the data partition did raise performance on my N6.
Yeah, I know it is a bit of a hassle, but considering there will be no more updates after 7.1.1 it should be a once only process right? Is possible to disable encryption on 7.1.1. without rooting?
I'm happy to unlock the bootloader and wipe the phone, not a problem.
Mephisto_POA said:
Yeah, I know it is a bit of a hassle, but considering there will be no more updates....
Click to expand...
Click to collapse
Don;t forget the monthly security updates.
I am using the lite stock room of Danvdh. It's a pre-rooted stock room.
But I think updates can be dirty flashed because the system, radio and bootloader will not change anymore.
So root and install TWRP to flash the updates
the problem with rooting is that many apps will not work, I'm cool staying without root and vanilla android, I just want to get rid of the encryption
Mephisto_POA said:
the problem with rooting is that many apps will not work, I'm cool staying without root and vanilla android, I just want to get rid of the encryption
Click to expand...
Click to collapse
In that case the post of @ktmom is applicable.
I am on 7.1.1 and have used the fed patcher mentioned on this site and it has worked nicely on custom and stock ROMs. But u have to be rooted.
NLBeev said:
In that case the post of @ktmom is applicable.
Click to expand...
Click to collapse
I'm a bit illiterate in this aspect, apologies. but I could not find a vanilla android for nexus 6 with just encryption disabled and no root. I would really appreciate if you could give me some directions?
The NEXUS 6 ANDROID DEVELOPMENT and NEXUS 6 ORIGINAL ANDROID DEVELOPMENT seems both to have only modified versions. I'm a bit confused
Mephisto_POA said:
I'm a bit illiterate in this aspect, apologies. but I could not find a vanilla android for nexus 6 with just encryption disabled and no root. I would really appreciate if you could give me some directions?
The NEXUS 6 ANDROID DEVELOPMENT and NEXUS 6 ORIGINAL ANDROID DEVELOPMENT seems both to have only modified versions. I'm a bit confused
Click to expand...
Click to collapse
Plain vanilla unencrypted would be google factory image plus a non forced enforcing kernel. B14CKB1RD, Franco there are others.
Custom ROM that is close to vanilla but comes with a non forced encrypting kernel would be Pure Nexus.
Mephisto_POA said:
I would really appreciate if you could give me some directions?
Click to expand...
Click to collapse
I have only one direction for you and that's the lite stock rom of Danvdh.
The kernel is the modified part. (no forced encryption).
After flashing this rom, you can unroot by uninstalling supersu.
https://forum.xda-developers.com/showthread.php?p=59561445/
NLBeev said:
I have only one direction for you and that's the lite stock rom of Danvdh.
The kernel is the modified part. (no forced encryption).
After flashing this rom, you can unroot by uninstalling supersu.
https://forum.xda-developers.com/showthread.php?p=59561445/
Click to expand...
Click to collapse
Hi, I also want to remove encryption from my Nexus 6 Stock as it is a stuttering mess.
I have rooted and installed the stock rom of Danvdh, but to my disappointment on boot up the phone is still showing as encrypted.
Have I done something wrong?
saltyzip said:
Hi, I also want to remove encryption from my Nexus 6 Stock as it is a stuttering mess.
I have rooted and installed the stock rom of Danvdh, but to my disappointment on boot up the phone is still showing as encrypted.
Have I done something wrong?
Click to expand...
Click to collapse
That was an answer to a different question.
The ROM you installed I believe has a non-force encrypting kernel. But just installing a non-force encrypting kernel isn't enough. You need to wipe user data and install a kernel that doesn't force encrypt.
Please read back a page to two for the whole recent conversation that has more details, like the fact that you'll lose all of your data in this process.
saltyzip said:
Hi, I also want to remove encryption from my Nexus 6 Stock as it is a stuttering mess.
I have rooted and installed the stock rom of Danvdh, but to my disappointment on boot up the phone is still showing as encrypted.
Have I done something wrong?
Click to expand...
Click to collapse
Got it working, just followed this:
Just because forced encryption is disabled doesn't mean it decrypts you. You have to do that yourself by formatting data either through TWRP (TWRP > Wipe > Format Data button) or through fastboot (fastboot format userdata), which will wipe out your app data and your internal storage partition so make the appropriate backups.
saltyzip said:
Got it working, just followed this:
Click to expand...
Click to collapse
You going to take credit, you should at least use your own words ?
I've gone with your guys suggestion with stock lite, working like a charm, very snappy. The phone feels indeed light, and multitasking is way smoother now, thanks!!!
just on a side note, after you install the rom you need to wipe the data partition to get rid of the encryption
Installed twrp on bn Nexus 6 os 5.1 OTA for 7.1.1 encrypted it
No clue how to fix this I'm a noob unlocked bootloader unencrypted Android 5 then it OTA updated to 7.1.1 and now can't get to twrp to wipe encryption how can I get this going again phones working just can't use cable to computer have the SD card reader micro SD any help would be appreciated
kudabee61 said:
...just can't use cable to computer...
Click to expand...
Click to collapse
Get your phone's USB port fixed, then you can fix the ROM issue.
Ok so I've seen a lot of confusion on how to correctly flash OxygenOS on your brand new OnePlus 5, and also how to correctly and easily root your phone.. This guide aims to clear up any confusion regarding this. Ready? Let's move on.
Q: What's the difference between International and Chinese versions of the OnePlus 5?
A: Hardware-wise there is absolutely no difference between the 2 versions. In terms of software, the international version runs OxygenOS (OOS) while the Chinese version runs HydrogenOS(H2OS). H2OS has no Google services pre-installed and is generally not recommended for use outside China. Both OxygenOS and HydrogenOS are official updates by OnePlus.
Q: I bought a Chinese phone. How do I install OxygenOS then?
A: 1. Download the latest OxygenOS from here. Download the full zip and NOT the OTA update.
2. Place it in the root of your internal memory. Basically don't put the file in any folder.
3. Go to Settings > System updates, press the gear icon and select Local upgrade.
4. Choose the file, the phone will boot into recovery and everything is done.
Q: OK I want to root my phone but I don't want to lose Android Pay, Netflix, Pokemon GO etc. Is it possible?
Simple answer: Yes. Long answer: Maybe not in the long run.
Why is that so? You see, back in the old days there were little downsides to rooting. Alas, Android Pay and Pokemon GO came along, and in an effort to tighten up security, Google implemented this thing called
SafetyNet. Basically it's a measure to test your system integrity, meaning that any modification to system will trigger SafetyNet and many apps will be "locked down". Android Pay and Pokemon GO will not work,
and Netflix won't show up on Google Play anymore. Some devices even check for unlocked bootloader, but apparently not the OnePlus 5, so you don't have to switch to a custom kernel to root.
To overcome this problem, the brilliant minds at XDA came up with system-less root. Chainfire was the first to implement it in SuperSU, but right now nobody uses SuperSU anymore. Magisk is the new kid in town,
and quite frankly much better IMO.
Q: Alright enough talk, how do I root the phone?
A: Patience my young Padawan. I will get to that in a moment. But here are some things you have to know.
1. Rooting involves unlocking your bootloader, and ALL YOUR DATA WILL BE WIPED. Keep a backup and move everything in your internal memory somewhere else.
2. Magisk may beat SafetyNet now, but there is no guarantee this will always be the case. So your SafetyNet enabled apps may not work all the time.
3. OTA updates from OnePlus will work differently when you are rooted. But hey that's what this guide is for. :good:
Easy rooting guide
1. Install ADB drivers.
2. Go into settings > about phone. Press the build no. a few times to activate developer options.
3. Turn on developer options, OEM unlocking and USB debugging.
4. Connect phone to PC and allow ADB access on phone. Wait for drivers to finish installing.
5. Download and install this simple tool on your PC.
6. Download one of the 2 TWRP recoveries below.
TWRP Official
xdvs23's TWRP
7. Open the All-in-One tool and make sure your device is recognised as OnePlus 5. Click on Unlock bootloader. Your bootloader is now unlocked and all your DATA WILL BE WIPED!
8. Select the "and boot it" arrow and click flash TWRP, click manual mode and choose the TWRP.img file you downloaded earlier.
9. After everything is done, your phone should now boot into TWRP successfully. Do not reboot yet.
10. On your PC, download the latest version of Magisk. Place the zip file onto your phone using USB and flash it with TWRP. Clear cache and reboot into system.
11. You should now see a new app called Magisk Manager. Check for updates!
12. However, do keep in mind not to mess around the system. If you need something, check to see if there any Magisk Modules available. There is also a small repo in the downloads section in Magisk Manager. Also Adaway works great with Magisk. Just make sure to turn on systemless host file in Magisk manager.
14. Congrats you are now rooted!:highfive:
Q: Alright now that I'm rooted, how do I get official updates?
A: 1. Download the latest OxygenOS from here. Download the full zip and NOT the OTA update. Place it on your phone. Make sure you also have your Magisk zip.
2. Boot into TWRP. Press the volume button when the bootloader unlocked screen comes up. Use volume buttons and power button to select recovery.
3. Flash the OxygenOS zip file. DO NOT reboot yet!
4. Tap the home button and flash Magisk. Clear cache.
5. Reboot into system and you are done!
Hope this guide is simple enough for you guys to understand. It might seem daunting at first, but practice makes perfect.
Also it is not a requirement to root, most people get by fine without ever rooting. But we are not like normal people, are we? Why else would we be on XDA then?
Further questions
Q1: Why Magisk and not SuperSU?
A: Besides the fact that Magisk is being constantly updated to bypass SafetyNet, it is also open-source. Wish I could say the same for SuperSU, the app is not what it used to be. Chainfire is no longer aware of the changes made in his app and I for one am not willing to take my chances with a shady developer. I had countless bad experiences with Chinese apps, many of them created by large companies. Check out this thread for more info.
Q2: Why exactly is HydrogenOS not recommended for use outside China?
A: Besides the aforementioned lack of Google apps, HydrogenOS is also tweaked differently from OxygenOS. It is significantly more aggressive in killing apps and not letting them run in the background, as you would expect with the number of rogue apps in China, made worse by the fact that there is no Play Store in China. OxygenOS on the other hand has a limit of 32 apps in memory, which I guess is a nice compromise between performance and battery life.
Reserved just in case. Probably will never need it though.
to be fair, there are still lots of people using SuperSU..
What should I do if I still want to use SuperSU?
2 noob questions @jasonwsc or anyone who knows
How about wiping dalvik and cache?
And how about encryption? Do I need to remove my fingerprint/security pattern before flashing OR rooting?
Thanks a lot for your help, the OP5 will be the first phone I can actually root. My old Xperia Z (2013) had a locked bootloader that was not unlockable haha.
ipredatorv said:
2 noob questions @jasonwsc or anyone who knows
How about wiping dalvik and cache?
And how about encryption? Do I need to remove my fingerprint/security pattern before flashing OR rooting?
Thanks a lot for your help, the OP5 will be the first phone I can actually root. My old Xperia Z (2013) had a locked bootloader that was not unlockable haha.
Click to expand...
Click to collapse
Wiping Dalvik and cache is usually done after flashing a ROM in TWRP. Not that big of deal now that many apps use ART, but still good to do to prevent app crashes.
No need to remove fingerprint security before rooting.
iamelton said:
to be fair, there are still lots of people using SuperSU..
Click to expand...
Click to collapse
Ningyou Higeki said:
What should I do if I still want to use SuperSU?
Click to expand...
Click to collapse
Just flash SuperSU zip instead of Magisk.
I don't know why anyone still uses SuperSU though. For one, it's sold to a Chinese company and is no longer open source. Not to mention it doesn't pass SafetyNet at all.
jasonwsc said:
Wiping Dalvik and cache is usually done after flashing a ROM in TWRP. Not that big of deal now that many apps use ART, but still good to do to prevent app crashes.
No need to remove fingerprint security before rooting.
Click to expand...
Click to collapse
Thanks for the clarification!
I only asked about wiping dalvik/cache because some other people here recommended that, as it may help to fix my battery drain issue.
Sent from my ONEPLUS A5000 using Tapatalk
ipredatorv said:
Thanks for the clarification!
I only asked about wiping dalvik/cache because some other people here recommended that, as it may help to fix my battery drain issue.
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
It might help with your battery drain issue, but chances are some apps are running in the background draining your battery.
Google services not working
I have installed oxygen OS in my chinese version OP5 following above method. However, after installing oxygen OS my google play store isnt working. When I open google play store, it stucks on checking info.
Nishatian1 said:
I have installed oxygen OS in my chinese version OP5 following above method. However, after installing oxygen OS my google play store isnt working. When I open google play store, it stucks on checking info.
Click to expand...
Click to collapse
Just a wild guess, but are you still in China? Check your VPN before trying to access the Google Playstore. Otherwise, remove the Playstore and download the most recent Playstore apk from a website like apkmirror. If they offer multiple versions, go for ARM 64.
Sent from my ONEPLUS A5000 using Tapatalk
jasonwsc said:
Just flash SuperSU zip instead of Magisk.
I don't know why anyone still uses SuperSU though. For one, it's sold to a Chinese company and is no longer open source. Not to mention it doesn't pass SafetyNet at all.
Click to expand...
Click to collapse
I'm a little tired of tuning my phone now. And I don't care about SafetyNet. BTW, how's Magisk's compatibility now?
jasonwsc said:
Just flash SuperSU zip instead of Magisk.
I don't know why anyone still uses SuperSU though. For one, it's sold to a Chinese company and is no longer open source. Not to mention it doesn't pass SafetyNet at all.
Click to expand...
Click to collapse
I got my Chinese OP5 two days ago and went through the whole procedure of unlocking, rooting, and flashing OxygenOS. Now I see that somebody took the time to write a nice guide on how to do it. Thanks @jasonwsc! I really wish I had this available to me already. I am sure it's gonna be a great help to others though!
I wasn't aware that SuperSU had been sold to a Chinese company through and that it is no longer open source. Knowing what I know now I regret flashing SuperSU yesterday and would love to switch to Magisk.
My question would be: what's the "proper way" to switch from SuperSU to Magisk? Just unroot via SuperSU and flash Magisk, or is there a better, cleaner way?
Edit:
Nevermind, just searched it and there's a super nice guide here.
Ningyou Higeki said:
I'm a little tired of tuning my phone now. And I don't care about SafetyNet. BTW, how's Magisk's compatibility now?
Click to expand...
Click to collapse
Magisk works fine, have no issues so far.
Hello,
I have the opportunity to receive an OP5T (128 GB)
from China. The ROM will be Hydrogen OS and not Oxygen OS.
I would like to be sure that the procedure used to install Oxygen OS will be the same as for the OP5?
Moazamali said:
Hello,
I have the opportunity to receive an OP5T (128 GB)
from China. The ROM will be Hydrogen OS and not Oxygen OS.
I would like to be sure that the procedure used to install Oxygen OS will be the same as for the OP5?
Click to expand...
Click to collapse
Yes it's the same. Just flash the firmware file for OP5T instead of the OP5.
i have international model oneplus 5. My phone was bricked, so i unbricked the phone by flashing h2os. I have rooted my phone with supersu and unrooted it again by flashing stock recovery. i want to now flash my phone with oxygenos. i have tried but no success. Please guide me with correct method.
Thanks
nayemohd said:
i have international model oneplus 5. My phone was bricked, so i unbricked the phone by flashing h2os. I have rooted my phone with supersu and unrooted it again by flashing stock recovery. i want to now flash my phone with oxygenos. i have tried but no success. Please guide me with correct method.
Thanks
Click to expand...
Click to collapse
See here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 it might be useful to format internal storage.
strongst said:
See here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 it might be useful to format internal storage.
Click to expand...
Click to collapse
Good morning all,
I have the same problem. Installed a H2os on a international oneplus 5.
Didn't like it so much so I formatted the system and installed the open beta 26.
However if I want to use the latest recovery either to clear cache or davlik cache I get a bunch of errors.
Any idea why?
kimon60 said:
Good morning all,
I have the same problem. Installed a H2os on a international oneplus 5.
Didn't like it so much so I formatted the system and installed the open beta 26.
However if I want to use the latest recovery either to clear cache or davlik cache I get a bunch of errors.
Any idea why?
Click to expand...
Click to collapse
Which h2os version and which recovery version did you use(file names please)? What do you mean with formatting the system? What did you wipe or format exactly?
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)