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...
Related
Hi!
I recently bought a Mi Mix and want to flash it with Lineage OS.
I followed all relevant instructions - did unlock the bootloader and so on - but I am not able to install TWRP using ADB and fastboot.
The phone is connecting well in ADB - even the "fastboot flash recovery twrp.img" gets a positive response - all seems to work fine. But after rebooting, I am always confronted with the stock recovery - the flashing so seems not to work out of some reason - TWRP gets removed during the reboot process.
I also tried to first flash and then use the "fastboot boot twrp.img" command. This command starts TWRP, but only in a frozen state - TWRP then starts in a way that you are not able to interact with the interface. Also here - after rebooting the stock recovery is there again. Can someone give me a hint, how to solve this problem?
I am running ADB on a Linux Computer (Debian 9) - dont think, that this might cause issues, but maybe....
The phone runs the MIUI-Version "MIUI Global 9.1 Stable"
It would be great, if someone here could help me out. I am somehow stuck and dont know how to proceed..
Thanks for taking the time!
Best
You can find two compatible versions of TWRP here.
Thanks Gavin!
Just out of curiosity - can you explain me, why the official TWRP Versions are not working and the ones you did post are good?
Best
Heiko
H0707 said:
Thanks Gavin!
Just out of curiosity - can you explain me, why the official TWRP Versions are not working and the ones you did post are good?
Best
Heiko
Click to expand...
Click to collapse
Touch has never worked on the official versions to my knowledge. Even the latest 3.2.1.0 build still has broken touch. It is still usable if you use a USB adapter/mouse, but not via touch.
Dear Gavin! Your TWRP file worked great.
But I have no another issue that seems to be common with the Mi Mix - the media sound is not working anymore. Notification and phone works fine but music and video is gone. I just was reading that you should update the firmware. Are the other files added in the link you did send by chance the relevant firmware files?
Best
H0707 said:
Dear Gavin! Your TWRP file worked great.
But I have no another issue that seems to be common with the Mi Mix - the media sound is not working anymore. Notification and phone works fine but music and video is gone. I just was reading that you should update the firmware. Are the other files added in the link you did send by chance the relevant firmware files?
Best
Click to expand...
Click to collapse
Use 8.1.4 and wipe caches
https://redirect.viglink.com/?forma...://mega.nz/#F!zlJBQJhJ!BJuv0brw0doTafuLTXJATw
Thanks - do I have to wipe cache and dalvik in TWRP before installing?
H0707 said:
Thanks - do I have to wipe cache and dalvik in TWRP before installing?
Click to expand...
Click to collapse
After
I use thishttps://androidfilehost.com/?fid=673368273298927160 TWRP Modified by MrRaines (Highly recommended) and this how to show install twrp on mi mix
gavin19 said:
You can find two compatible versions of TWRP here.
Click to expand...
Click to collapse
I was looking for that as well! Thanks for sharing. I can confirm that this TWRP version works well with the Mi Mix.
Thanks guys - the device works fine now. You saved my day!
There is one thing left. I still cannot initiate TWRP manually - have to use ADB for this. Once TWRP is started, I cannot reach the devices harddisk anymore from my computer. Thats no issue now, but might cause issues in the future. Any idea how to solve this?
Best
H0707 said:
Thanks guys - the device works fine now. You saved my day!
There is one thing left. I still cannot initiate TWRP manually - have to use ADB for this. Once TWRP is started, I cannot reach the devices harddisk anymore from my computer. Thats no issue now, but might cause issues in the future. Any idea how to solve this?
Best
Click to expand...
Click to collapse
Are you encrypted, or maybe you missed a stage when installing,
H0707 said:
Thanks guys - the device works fine now. You saved my day!
There is one thing left. I still cannot initiate TWRP manually - have to use ADB for this. Once TWRP is started, I cannot reach the devices harddisk anymore from my computer. Thats no issue now, but might cause issues in the future. Any idea how to solve this?
Best
Click to expand...
Click to collapse
No. It happened with my device as well. You cannot mount your internal storage on your PC. I've tried many different versions of TWRP and none have allowed access. I'm not quite sure why ... I had other devices in the past and it always worked. On the Mi mix however, it does not. So just turn on your phone and transfer what you need to or adb sideload it.
james1089 said:
Are you encrypted, or maybe you missed a stage when installing,
Click to expand...
Click to collapse
No. I don't believe that he did James. Does it work for you? because it never worked for me either. I've tried all the different versions of TWRP and it didn't do a thing. Also I have no passwords or encryption. I'm sure of this. Maybe I'm also doing something wrong and that's why I can't Mount my internal storage while in TWRP recovery?
I don't use the official TWRP because for some reason the official versions of TWRP offered for the Mi Mix are broken. The touchscreen never works and I don't have an external controller or anything else to make it work other than the phones screen. So I've used the custom versions that have been fixed and re-released on XDA.
malimt said:
No. It happened with my device as well. You cannot mount your internal storage on your PC. I've tried many different versions of TWRP and none have allowed access. I'm not quite sure why ... I had other devices in the past and it always worked. On the Mi mix however, it does not. So just turn on your phone and transfer what you need to or adb sideload it.
No. I don't believe that he did James. Does it work for you? because it never worked for me either. I've tried all the different versions of TWRP and it didn't do a thing. Also I have no passwords or encryption. I'm sure of this. Maybe I'm also doing something wrong and that's why I can't Mount my internal storage while in TWRP recovery?
I don't use the official TWRP because for some reason the official versions of TWRP offered for the Mi Mix are broken. The touchscreen never works and I don't have an external controller or anything else to make it work other than the phones screen. So I've used the custom versions that have been fixed and re-released on XDA.
Click to expand...
Click to collapse
Well its strange cause there are thousands using it for over a year now. Maybe you have always been encrypted. Which ROM are you using, I mean you haven't still got the vendor fake ROM, any updates?
james1089 said:
Well its strange cause there are thousands using it for over a year now. Maybe you have always been encrypted. Which ROM are you using, I mean you haven't still got the vendor fake ROM, any updates?
Click to expand...
Click to collapse
That's very odd. I'm not quite sure what to tell you. I know for a fact though that my device is not encrypted. I'm currently running RR without any password/pattern. Before installing RR I was on stock OS and still no password/pattern. I live alone and so I don't feel the need to use a password on my phone. So ever since I've purchased this phone I've never had a password on it.
No updates as far as I'm aware on the RR.
Does it Mount for you? If so, what TWRP are you using on your device?
malimt said:
That's very odd. I'm not quite sure what to tell you. I know for a fact though that my device is not encrypted. I'm currently running RR without any password/pattern. Before installing RR I was on stock OS and still no password/pattern. I live alone and so I don't feel the need to use a password on my phone. So ever since I've purchased this phone I've never had a password on it.
No updates as far as I'm aware on the RR.
Does it Mount for you? If so, what TWRP are you using on your device?
Click to expand...
Click to collapse
I've used the same 1 from the beginning, smarty, I just followed the guide in the guide section how to remove vendor ROM. I use Linux it works fine. Everyone thought they had official ROM in the beginning only to find out it was vendor ROM. What about using mtp to send files, maybe that's what I did, can't even remember.
james1089 said:
I've used the same 1 from the beginning, smarty, I just followed the guide in the guide section how to remove vendor ROM. I use Linux it works fine. Everyone thought they had official ROM in the beginning only to find out it was vendor ROM. What about using mtp to send files, maybe that's what I did, can't even remember.
Click to expand...
Click to collapse
Wow. Well you're lucky tbh. I can't seem to figure out why mine doesn't connect. I'm not sure what the difference is between the vendor (ROM) and the "stock" (ROM) - I know I was using the global stable (ROM) that's what my phone first came with and it was running 6.0 MM.
Yes, I have tried to use MTP while in TWRP and it doesn't do anything. My computer does detect something but doesn't show the phone to be connected or anything. I have even tried to mount it in the options but nothing. I know I have all drivers installed and does not make a difference. I'm running Windows 10 not Linux.
malimt said:
Wow. Well you're lucky tbh. I can't seem to figure out why mine doesn't connect. I'm not sure what the difference is between the vendor (ROM) and the "stock" (ROM) - I know I was using the global stable (ROM) that's what my phone first came with and it was running 6.0 MM.
Yes, I have tried to use MTP while in TWRP and it doesn't do anything. My computer does detect something but doesn't show the phone to be connected or anything. I have even tried to mount it in the options but nothing. I know I have all drivers installed and does not make a difference. I'm running Windows 10 not Linux.
Click to expand...
Click to collapse
So does it show up when phone is booted?
james1089 said:
So does it show up when phone is booted?
Click to expand...
Click to collapse
Yes, when it is booted it shows up perfectly, after I switch from "charging to file transfer (MTP)" in the status bar.
malimt said:
Yes, when it is booted it shows up perfectly, after I switch from "charging to file transfer (MTP)" in the status bar.
Click to expand...
Click to collapse
I'm going to try when I get home, it's been do long since I tried something like that, have you ticked and then unticked mount in read only. Then reboot to recovery again.
Every Pie Rom I've installed with the February Update, kills my WIFI. It comes and goes, it's not stable. Check it guys, CHECK IT.
JJ5150 said:
Every Pie Rom I've installed with the February Update, kills my WIFI. It comes and goes, it's not stable. Check it guys, CHECK IT.
Click to expand...
Click to collapse
Strange, i'm running Ressurection Remix with no problems at all. Maybe you should check/reflash your radio?
Wisse said:
Strange, i'm running Ressurection Remix with no problems at all. Maybe you should check/reflash your radio?
Click to expand...
Click to collapse
Resurrection Remix is still UNOFFICIAL. Last version is 02/09. February OFFICIAL Security Update was Updated February 16-19, and all the PIE ROMS that are OFFICIALLY Updated with this update KILL THE WIFI.
Thanks tho.
I am using pixel experience and there isn't any problem I encountered
SAPTADIP MALAKAR said:
I am using pixel experience and there isn't any problem I encountered
Click to expand...
Click to collapse
May I ask what model number you have?
I'm running AEX 6.3 and my wifi is perfectly fine.
JJ5150 said:
May I ask what model number you have?
Click to expand...
Click to collapse
Hey , I am using Moto G5s plus and the model number is XT1804.
SAPTADIP MALAKAR said:
Hey , I am using Moto G5s plus and the model number is XT1804.
Click to expand...
Click to collapse
I'm on XT1806
I was presented with a workaround... Disable WIFI scanning in settings. Fixes Wifi drops. NO DICE. Totally unstable wifi.
No problem with me too.. using pixel experience on xt1804
I'm using havoc os in my XT1806 and everything is working great, also most people don't have your problem, you should restore your stock ROM backup and try to clean flash any pie ROM, this is not the devs fault.
Juancasa14 said:
I'm using havoc os in my XT1806 and everything is working great, also most people don't have your problem, you should restore your stock ROM backup and try to clean flash any pie ROM, this is not the devs fault.
Click to expand...
Click to collapse
Hi, i have a XT1806 too, I want to have the gcam, I just unlocked the bootloader, but I'm afraid to root it and flash a rom, how did you do it, thanks
prophetgamer said:
Hi, i have a XT1806 too, I want to have the gcam, I just unlocked the bootloader, but I'm afraid to root it and flash a rom, how did you do it, thanks
Click to expand...
Click to collapse
Hi ! Don't be afraid, if you follow every step correctly you shouldn't have any problems, if you already unlocked your bootloader you should flash the latest version of TWRP if you want to root your phone, you can't use gcam unless you do it because you need to enable cam2api by adding a specific line to the build.prop.
If you decide to root it, just flash the treble version of TWRP and then flash the latest version of magisk, then you'll be able to modify your build.prop !
Ask me if you need any help
Juancasa14 said:
Hi ! Don't be afraid, if you follow every step correctly you shouldn't have any problems, if you already unlocked your bootloader you should flash the latest version of TWRP if you want to root your phone, you can't use gcam unless you do it because you need to enable cam2api by adding a specific line to the build.prop.
If you decide to root it, just flash the treble version of TWRP and then flash the latest version of magisk, then you'll be able to modify your build.prop !
Ask me if you need any help
Click to expand...
Click to collapse
hello again, I tried to make a backup of the system image but it always says backup failed, I already made the wipe data to decrypt, but it did not work
prophetgamer said:
Hi, i have a XT1806 too, I want to have the gcam, I just unlocked the bootloader, but I'm afraid to root it and flash a rom, how did you do it, thanks
Click to expand...
Click to collapse
prophetgamer said:
hello again, I tried to make a backup of the system image but it always says backup failed, I already made the wipe data to decrypt, but it did not work
Click to expand...
Click to collapse
You don't need to backup the system image, just backup system, data and boot, and also persist and efs just in case you lose your IMEI. Are you using treble TRWP?
Finally they made it real!! Closed Beta is now opened for Oneplus 3/3t owners
If you want to be part of this beta testing, follow this link: https://www.xda-developers.com/oneplus-3-3t-closed-beta-oxygenos-9-android-pie/
IMPORTANT : Use leaked builds at your own risk
Download
(OP3 OnePlus3Oxygen_16_OTA_073_all_1903190037_c3d5b3a79f9b4895.zip)
(OP3T OnePlus3TOxygen_28_OTA_073_all_1903190038_308835b6760c41bd.zip)
Instructions (Read carefully)
* Flash through TWRP (by @dianlujitao) and do a Factory Reset before boot the device (source)
* Your device will became encrypted during boot (data partition may be corrupted on encrypted devices)
* magisk v18.1 is working
(source)
* Stock recovery will overlap TWRP unless you flash magisk before reboot.
Bugs:
None so far...
Thanks for initial testers:
@Chuck Bartowski
@himsin
Sounds amazing, waiting to see the final version coming out
FSadino said:
Finally they made it real!! Closed Beta is now opened for Oneplus 3/3t owners
If you want to be part of this beta testing, follow this link: https://www.xda-developers.com/oneplus-3-3t-closed-beta-oxygenos-9-android-pie/
Click to expand...
Click to collapse
How will I know of I get selected for closed beta testing?? And when will close beta be available for testing
alrd apply hope this early appril can roll out
Closed beta pie for op3/t leaked
helderfp said:
Closed beta pie for op3/t leaked
Click to expand...
Click to collapse
Where?
helderfp said:
Closed beta pie for op3/t leaked
Click to expand...
Click to collapse
and why do you think that?
abhibnl said:
and why do you think that?
Click to expand...
Click to collapse
Because i download the rom from a leaked link
helderfp said:
Because i download the rom from a leaked link
Click to expand...
Click to collapse
Can you share a link via PM?
abhibnl said:
While I won't ask you to post a leaked build, can you post some SS running that ROM and showing this thread in XDA app to show that you are not just joking around and have actually used the ROM?
Or you can download AIDA64 and post SS from that app.
Click to expand...
Click to collapse
Review from techibee
https://www.youtube.com/channel/UCAL31QQ9hsw8utl2GSgOchg
jay_snake said:
Where?
Click to expand...
Click to collapse
https://yadi.sk/d/Dj_6zddVg5-yog
Thread cleaned
Link restored
Please see rule 12
XDA has been the place to find leaked builds since there were leaked builds
Thank you for your cooperation
Does it work as a daily driver or still too buggy?
(he said, before inevitably rushing to install it)
helderfp said:
Review from techibee
https://www.youtube.com/channel/UCAL31QQ9hsw8utl2GSgOchg
Click to expand...
Click to collapse
Appreciate it. I'll find and download it to test it over weekend.
Thanks for the build!
Any way to decrypt?
I tried flashing Magisk (18.1) after flashing the ROM but it didn't work.
I also tried flashing Magisk + Universal DM-Verity ForceEncrypt disabler (https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389) but that gave me a bootloop.
To everyone who will rush to flash it - please don't just download and flash. Make sure you are ready for broken device, storage encryption and decryption errors, and data errors.
Make sure to take a complete backup of internal storage and then attempt to flash it using stock or twrp recovery.
Or you should rather wait til a developer figures out a way to make twrp compatible with its firmware for encryption/decryption errors
Just flash it and do a factory reset before booting rom. That will do the trick. My phone was decrypted and first boot took around 15 mins and encrypted phone.
BTW anyone tried if magisk is working on closed beta?
himsin said:
Just flash it and do a factory reset before booting rom. That will do the trick. My phone was decrypted and first boot took around 15 mins and encrypted phone.
BTW anyone tried if magisk is working on closed beta?
Click to expand...
Click to collapse
Magisk is working, I'm now using the closed beta with Magisk 18.1.
At first boot Magisk Manager (the application) was not installed and I had to install it manually. Also, Magisk Manager was saying that Magisk was not installed, but a reboot solved it. Now it is working perfectly.
And, if you were responding to me, I'm sorry I wasn't very clear, I wanted to keep the phone decrypted (disabling force encrypt at first boot), but I have failed and I'm using the phone encrypted at the moment.
I just installed it via stock recovery with locked bootloader... Everything is fine..
himsin said:
Just flash it and do a factory reset before booting rom. That will do the trick. My phone was decrypted and first boot took around 15 mins and encrypted phone.
BTW anyone tried if magisk is working on closed beta?
Click to expand...
Click to collapse
Did you used stock or TWRP recovery?
I just got my bootloader unlocked this morning and I am ready to get it started however all I see are Verizon and Google store bought methods
Trippyy Doee said:
I just got my bootloader unlocked this morning and I am ready to get it started however all I see are Verizon and Google store bought methods
Click to expand...
Click to collapse
Interesting wording. If you mean that you can now toggle OEM unlocking on, then unlocking the bootloader with fastboot is the same no matter what device you have.
Badger50 said:
Interesting wording. If you mean that you can now toggle OEM unlocking on, then unlocking the bootloader with fastboot is the same no matter what device you have.
Click to expand...
Click to collapse
Sorry for that lol But what I meant was just any root method using magisk because I used the latest 20.2 and it failed for me. And TWRP if any . Just a point in the right direction basically ?
Trippyy Doee said:
Sorry for that lol But what I meant was just any root method using magisk because I used the latest 20.2 and it failed for me. And TWRP if any . Just a point in the right direction basically ?
Click to expand...
Click to collapse
Magisk is the only way and there is no twrp
p70shooter said:
Magisk is the only way and there is no twrp
Click to expand...
Click to collapse
Is there a working Magisk Canary build that can patch my boot.img?
Trippyy Doee said:
Sorry for that lol But what I meant was just any root method using magisk because I used the latest 20.2 and it failed for me. And TWRP if any . Just a point in the right direction basically ?
Click to expand...
Click to collapse
p70shooter said:
Magisk is the only way and there is no twrp
Click to expand...
Click to collapse
Like @p70shooter said. There is no other way to root besides magisk, and there is no TWRP as of yet. If rooting with 20.2 didn't work, then try 20.1. You can find it here :good: https://github.com/topjohnwu/Magisk/releases
Trippyy Doee said:
Is there a working Magisk Canary build that can patch my boot.img?
Click to expand...
Click to collapse
Don't know. I just use stable, like they recommend. I know people do use Canary just fine but can't help you there
p70shooter said:
Don't know. I just use stable, like they recommend. I know people do use Canary just fine but can't help you there
Click to expand...
Click to collapse
This what I'm getting when I keep trying to patch it. And it is the correct stock image with my build number.
Edit : I'm just going to have to do this after work . I thought I had time but I'm just rushing probably just missing everything.
Thanks for the help guys
Trippyy Doee said:
This what I'm getting when I keep trying to patch it. And it is the correct stock image with my build number.
Edit : I'm just going to have to do this after work . I thought I had time but I'm just rushing probably just missing everything.
Thanks for the help guys
Click to expand...
Click to collapse
Just a little FYI for you my friend. Have you downloaded the factory image coinciding with your current build? If not, then do so, then extract the factory image, then extract the image.zip, then pull the boot.img from there, place it on your phones internal storage, then try to patch it with magisk. I just did it myself with the 20.2 stable version and it worked fine :good:
Badger50 said:
Just a little FYI for you my friend. Have you downloaded the factory image coinciding with your current build? If not, then do so, then extract the factory image, then extract the image.zip, then pull the boot.img from there, place it on your phones internal storage, then try to patch it with magisk. I just did it myself with the 20.2 stable version and it worked fine :good:
Click to expand...
Click to collapse
Yea I was certainly rushing . I used the wrong boot file. Thanks alot. Finally off work so now I get to enjoy rooting my first Pixel phone. ?
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)