Related
So I was forced by my employer to enabled Device Encryption on my Gnex. Not a huge problem, as we already had to enter a PIN/Password to access company email. Fine.
So then I decide to switch ROMs from CNS 1.5.1 to AOSP r7, and lo and behold, when I flash, everything on my sdcard has been devoured. I did not select any options to do a full wipe, and as I would come to find out later, I couldn't have if I wanted to, since even the latest version of TWRP doesn't know how to correctly decrypt using the supplied PIN.
So here I am with my thumb up my ass wondering how to prevent this from happening again. I'm also considering decrypting my device, leaving it decrypted, and just using the web interface for my work mail.
Is this expected?? I'm reading in other threads for other devices that TWRP and CWM both don't know how to decrypt Samsung phones.
Say it ain't so....
maxawesome said:
So I was forced by my employer to enabled Device Encryption on my Gnex. Not a huge problem, as we already had to enter a PIN/Password to access company email. Fine.
So then I decide to switch ROMs from CNS 1.5.1 to AOSP r7, and lo and behold, when I flash, everything on my sdcard has been devoured. I did not select any options to do a full wipe, and as I would come to find out later, I couldn't have if I wanted to, since even the latest version of TWRP doesn't know how to correctly decrypt using the supplied PIN.
So here I am with my thumb up my ass wondering how to prevent this from happening again. I'm also considering decrypting my device, leaving it decrypted, and just using the web interface for my work mail.
Is this expected?? I'm reading in other threads for other devices that TWRP and CWM both don't know how to decrypt Samsung phones.
Say it ain't so....
Click to expand...
Click to collapse
what version of twrp are you using? the newest version supposedly fixed decrypting.
simms22 said:
what version of twrp are you using? the newest version supposedly fixed decrypting.
Click to expand...
Click to collapse
The very latest version that can be downloaded via GooManager. I always update it before flashing any new ROMs. This was done last night, so the very latest version GooManager installs as of around 9PM PST yesterday. 2.3.2.1 I suppose?
Hell guys. I switched from OOS 3.4.2 to CM13 last week. The Phone ist still encrypted. Now my question.
Is it worth to decrypt the phone via TWRP or ADB command ? I mean, i disabled PIN at boot. So i think im able to flash updated CM13 zip's and TWRP updates. I hope i'm right but i think it's possible.
What do you guys think ? Is my phone much faster after decrypting ?
Nvm. I decrypted it with TWRP and installed all new. Now it's not encrypted with CM13.
Well i did some research and i don't believe decrypting would be much of a boost in performance. What are your findings right now? noticed any boost in performance? and what exactly did you do in TWRP to decrypt it?
what re the benefits of decrypt. I believe im still encrypted as I have never wiped my data...
i think its a bit faster now. but its not really noticeable
Probably the only reason you would unencrypt is to install MultiROM I guess.
rirozizo said:
Probably the only reason you would unencrypt is to install MultiROM I guess.
Click to expand...
Click to collapse
yeah I mean I haven't found the need to decrypt and don't see a need neither. I don't even know how to use multiroom. I rather just back up two roms and restore between the two I feel like multi rom is a bit too complex to set up two roms. my understanding is that everything has to be flashed in a certain way or it wont work.
egren58 said:
yeah I mean I haven't found the need to decrypt and don't see a need neither. I don't even know how to use multiroom. I rather just back up two roms and restore between the two I feel like multi rom is a bit too complex to set up two roms. my understanding is that everything has to be flashed in a certain way or it wont work.
Click to expand...
Click to collapse
It's really not that hard.. you will get used to it after your first time using it. And its so much worth it instead of doing the backup-restore method :good:
Misanful said:
It's really not that hard.. you will get used to it after your first time using it. And its so much worth it instead of doing the backup-restore method :good:
Click to expand...
Click to collapse
I might give it a try if I decrypt my device. Also just the thought of being able to switch to OOS for the camera in a snap is not suvh a bad idea..
i'm running sultan's CM and still have encryption on - OTA updates via CM still work fine, it just requests I enter the same password/PIN I do every time the device boots (As well as whenever I go into recovery).
it's annoying during flashing and updating but I'm glad to see it work since if someone stole my device they woudln't get any of my data nor would they be able to flash anything malicious onto my device without my knowing, and i don't notice any lag in day to day use.
Hello all!
So I've been rooting and installing custom ROMs on my Android phones since getting started on my Galaxy S2 back in the day, and as it stands I've never encountered such an annoying roadblock as I've been forced to deal with over the past few days.
I just got a new HTC 10, and quickly went ahead and rooted my phone to get a custom ROM on there. The ROM seemed to boot fine, but the home button wasn't working and I had forgotten to download and install GApps. The other problem was, upon flashing the new LineageOS, TWRP would not recognize any files whatsoever on my device--including the backup I had made. So, I went ahead and flashed the latest RUU and returned to stock. After realizing the RUU is Nougat firmware, I got the latest TWRP and went ahead to try and reinstall Lineage again.
This time, however, the phone decided to stop on a screen asking for a password before it fully boots. I've tried this with every ROM I've installed and every time it will ask for a password. Boot into Recovery, and it will ask for a password there and have all my files hidden, keeping me from doing anything short of a re-flashing my RUU to return to stock. I know these ROMs evidently encrypt your phone during first boot, but I'm at a loss for info on what I'm apparently doing wrong to cause this issue.
Is this an Android N issue? On M, I was able to boot into Lineage, though TWRP still had the file issue. Anyways, whatever help would be fully appreciated. Since I'm a new user I wasn't able to inquire directly on the LineageOS thread, and so deferred to Q&A.
EDIT:
I've solved the issue. After re-flashing the RUU, flashing TWRP, and re-rooting over and over, I figured out what seemed to be going on.
In case anyone else has the same problem as me, here was my solution:
Starting from stock, I went ahead and flashed my phone with the latest TWRP compatible with N (3.0.3.0 at this current time). Afterwards I flashed LineageOS and GApps. As usual, upon reboot, the phone needed a password to get in. So, I rebooted to Recovery, which also required a password. I hit cancel, wiped the phone with a factory reset, formatted all data, and restarted. This did the trick, and I've been running LineageOS 7.1 with no problems whatsoever!
Which version of TWRP are you using at the moment. If you're on N firmware I'd recommend to use 3.0.3-0, that is to be found on the download tab of the TWRP thread.
Sent from my htc_pmeuhl using XDA Labs
dreDREb13 said:
Hello all!
So I've been rooting and installing custom ROMs on my Android phones since getting started on my Galaxy S2 back in the day, and as it stands I've never encountered such an annoying roadblock as I've been forced to deal with over the past few days.
I just got a new HTC 10, and quickly went ahead and rooted my phone to get a custom ROM on there. The ROM seemed to boot fine, but the home button wasn't working and I had forgotten to download and install GApps. The other problem was, upon flashing the new LineageOS, TWRP would not recognize any files whatsoever on my device--including the backup I had made. So, I went ahead and flashed the latest RUU and returned to stock. After realizing the RUU is Nougat firmware, I got the latest TWRP and went ahead to try and reinstall Lineage again.
This time, however, the phone decided to stop on a screen asking for a password before it fully boots. I've tried this with every ROM I've installed and every time it will ask for a password. Boot into Recovery, and it will ask for a password there and have all my files hidden, keeping me from doing anything short of a re-flashing my RUU to return to stock. I know these ROMs evidently encrypt your phone during first boot, but I'm at a loss for info on what I'm apparently doing wrong to cause this issue.
Is this an Android N issue? On M, I was able to boot into Lineage, though TWRP still had the file issue. Anyways, whatever help would be fully appreciated. Since I'm a new user I wasn't able to inquire directly on the LineageOS thread, and so deferred to Q&A.
Click to expand...
Click to collapse
Installing cm will encrypt your device, was you encrypted previously? Then you would have created a password to access your device.
In my case, I formatted data and then flashed my sense rom (venom) I chose not to encrypt, cm doesn't give this option when you flash it so you have no choice at the time. So if you don't have the password and the device has been encrypted you'd have to format data, don't jump into that just yet though.
Unless someone else knows a way around that, personally I couldn't. However I did have a rom installed so I could boot the rom and back up my data once in the OS. Then format (not wipe) and then reinstall the rom.
Sounds confusing, to be sure we need more info from you.
Do you have an operating system at the moment? If you do then back up your data so that's safe.
Do you know the password to decrypt your phone??
5m4r7ph0n36uru said:
Which version of TWRP are you using at the moment. If you're on N firmware I'd recommend to use 3.0.3-0, that is to be found on the download tab of the TWRP thread.
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
I'm running 3.0.3.0. I had a problem after re-flashing my RUU where TWRP wouldn't boot, but I quickly realized this was due to using an M compatible TWRP with the new firmware.
dladz said:
Installing cm will encrypt your device, was you encrypted previously? Then you would have created a password to access your device.
In my case, I formatted data and then flashed my sense rom (venom) I chose not to encrypt, cm doesn't give this option when you flash it so you have no choice at the time. So if you don't have the password and the device has been encrypted you'd have to format data, don't jump into that just yet though.
Unless someone else knows a way around that, personally I couldn't. However I did have a rom installed so I could boot the rom and back up my data once in the OS. Then format (not wipe) and then reinstall the rom.
Sounds confusing, to be sure we need more info from you.
Do you have an operating system at the moment? If you do then back up your data so that's safe.
Do you know the password to decrypt your phone??
Click to expand...
Click to collapse
Turns out formatting the data was the solution. Thankfully this phone is brand new, so there was no data to lose.
As for why Cyanogen and Lineage automatically encrypt without giving some sort of default password, I have no idea...
Thanks for the help, though!
dreDREb13 said:
Turns out formatting the data was the solution. Thankfully this phone is brand new, so there was no data to lose.
As for why Cyanogen and Lineage automatically encrypt without giving some sort of default password, I have no idea...
Thanks for the help, though!
Click to expand...
Click to collapse
Could have thought of that myself. Encryption used by Cyanogen/Lineage is different to HTCs encryption used on Sense based ROMs. Thanks for your feedback.
Sent from my htc_pmeuhl using XDA Labs
dreDREb13 said:
I'm running 3.0.3.0. I had a problem after re-flashing my RUU where TWRP wouldn't boot, but I quickly realized this was due to using an M compatible TWRP with the new firmware.
Turns out formatting the data was the solution. Thankfully this phone is brand new, so there was no data to lose.
As for why Cyanogen and Lineage automatically encrypt without giving some sort of default password, I have no idea...
Thanks for the help, though!
Click to expand...
Click to collapse
There is no password and I've had it out in the cm thread, apparently it's common knowledge, which we've both found out its not, there is no password either so you did what was required.
Also, click thanks instead of saying mate [emoji6]
Glad you're back up and running.
thanks had same issue when installing Lineage 14.1 nightly on my HTC 10 today, which already had twrp on it and the stock rom - your solution worked.
i.e.
turn off device
hold volume down while pressing power for few seconds
choose reboot to bootloader from menu
choose boot to recovery mode
hit cancel when prompted for password
choose wipe from twrp, use default options
reboot
no more password prompt.
Hi all,
I'm currently not encrypted and prefer to keep it that way, I don't like entering passwords everytime I go to TWRP and I prefer the old school android system where encryption was a choice, not a mandatory decision made for you.
So when I install a ROM I run a few commands prior to installation to avoid forced encryption, unless it has an option within aroma to disable force encryption which most don't
Thanks to @j to the 4n for help with this, legend
Anyway if you'd like to install a ROM like lineage or aosp or resurrection remix etc and remain not encrypted? Keep reading.
*Note: if you're encrypted prior to doing this then stop, this is for people who've chosen to disable force encryption already but would like to retain it after installing aosp / lineage ROMs.
However if you'd like to remove encryption you'll need to format data via TWRP, not a wipe! Format.
Make sure you back up prior to doing this as it will format data, best to have the ROM on your SD card too so you don't end up with no OS.
If you've done the above or you already have a ROM installed without encryption, then you should be good to go.
------------------------------------------------------------------------------------------------
Just before youre about to install a ROM, let's say resurrection remix ( tested )
Make sure your phone is in TWRP and you're connected to your PC then just before you're about to click install, open up a command prompt on your PC then from ADB shell send the following commands to the device from your PC..
For Magisk:
echo "KEEPFORCEENCRYPT=false" >> /cache/.magisk
If the rom uses SuperSU, send the following commands.
echo "KEEPFORCEENCRYPT=false" >> /data/.supersu
echo "KEEPFORCEENCRYPT=false" >> /cache/.supersu
Then install your rom as normal.
Obviously for ROMs like viper your don't need to do this as there is an option within aroma, but for the likes of RR or lineage this will mean your phone will not encrypt on boot.
Should work for all ROMs but I've not tested this on all of them so if it goes wrong then it's not on me, this worked perfectly for me on RR coming from viper whilst not encrypted.
*Note: if you're not sure what root method your ROM uses then simply send all three commands and you should be good to go.
By using these you're not going to find yourself in TWRP being asked for a password you don't have as your device has been encrypted, I've lost data myself this way and it's extremely annoying.
:good:
If I can ask if anyone tries this and it works, would you mind replying with what it worked on so I can update the OP.
Cheers.
PS: if you're not sure what this is or have any questions, please ask away
Anyway to do this from the device for when your not near a PC?
JohnFawkes said:
Anyway to do this from the device for when your not near a PC?
Click to expand...
Click to collapse
Yes i believe it is, would need to write up a script which is ran prior to installing the rom, i've not got around to doing it yet.
Strictly speaking this should be an option with all roms, it's not exactly a lot of work is it?
Deleted
Works pretty well on Stock ROM.
Just RUU'd, and before rebooting went into download mode, flashed Recovery, flashed SuperSU, used this Command. and boom.
Multirom works.
I used to have a one plus 3 and for some time before everyone used forced decryption the good ol friends from kali net hunter made a forced decryption zip, I will put a link down below, but listen when I say this, every time you flash a new boot .Img, or rom on the htc 10 you need to flash this if you want to stay decrypted. Its ok if you flash multiple times.
The file you want is, "no verity force encrypt".
I've used it on almost every aosp and stock based rom I've flashed also used on many custom kernels to, it still stayed decrypted.
https://build.nethunter.com/android-tools/
Dlind said:
I used to have a one plus 3 and for some time before everyone used forced decryption the good ol friends from kali net hunter made a forced decryption zip, I will put a link down below, but listen when I say this, every time you flash a new boot .Img, or rom on the htc 10 you need to flash this if you want to stay decrypted. Its ok if you flash multiple times.
The file you want is, "no verity force encrypt".
I've used it on almost every aosp and stock based rom I've flashed also used on many custom kernels to, it still stayed decrypted.
https://build.nethunter.com/android-tools/
Click to expand...
Click to collapse
Yea it's used on the OnePlus 5 too. I wrote this prior to knowing of its existence and because the likes of lineage and other ROMs just assume you know, no warning.
Losing data is not fun.
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app
dladz said:
Yea it's used on the OnePlus 5 too. I wrote this prior to knowing of its existence and because the likes of lineage and other ROMs just assume you know, no warning.
Losing data is not fun.
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yeah it pisses me off. But at least with this handy zip you can flash it anyway and have some mental relief that you stay decrypted.
Dlind said:
I used to have a one plus 3 and for some time before everyone used forced decryption the good ol friends from kali net hunter made a forced decryption zip, I will put a link down below, but listen when I say this, every time you flash a new boot .Img, or rom on the htc 10 you need to flash this if you want to stay decrypted. Its ok if you flash multiple times.
The file you want is, "no verity force encrypt".
I've used it on almost every aosp and stock based rom I've flashed also used on many custom kernels to, it still stayed decrypted.
https://build.nethunter.com/android-tools/
Click to expand...
Click to collapse
i've flashed the v 5.1 got greeted by a "Encrypting" Wait while your phone is being encrypted. Time remaining 01:50 Screen.
Guess that does not work on PureFusion OS ROM / HTC 10
Edit: Okay... this does NOT work when swapping Internal with Secondaries ROM in Multirom, but for a new install it does...
Haldi4803 said:
i've flashed the v 5.1 got greeted by a "Encrypting" Wait while your phone is being encrypted. Time remaining 01:50 Screen.
Guess that does not work on PureFusion OS ROM / HTC 10
Edit: Okay... this does NOT work when swapping Internal with Secondaries ROM in Multirom, but for a new install it does...
Click to expand...
Click to collapse
Sorry I hadn't tested with all ROMs, not even sure Pure Fusion was even available when I had my HTC 10.
Stick to the script, it's quick, easy and works, you can try a zip but unless someone has gone before you you're potentially walking into a bad time.
Jep.... the zip doesn't seem to work no matter what. Not even on Stock ROM. Prolly not compatible with HTC10.
These 2 Command lines though do work perfectly fine on PureFusion OS... simply install ROM, install SU, enter 2 lines. Done.
Haldi4803 said:
Jep.... the zip doesn't seem to work no matter what. Not even on Stock ROM. Prolly not compatible with HTC10.
These 2 Command lines though do work perfectly fine on PureFusion OS... simply install ROM, install SU, enter 2 lines. Done.
Click to expand...
Click to collapse
That's absolutely fine. Because this thread isn't about the zip..I have nothing to do with that, so in regards to the zip you flash it at your own risk.
Deleted
Though i do agree with him that having a .zip and not needing a Computer every time would be pretty usefull.
Does anyone know how to create TWRP flashable zips that includes only this 2 commands?
Hello I tied this for RR rom but I got this message in the cmd, am i doing something wrong?
edit i found my fault I had to adb shell
I know it's been about a year, since somebody posted, but: if anbyone else like me stumbles across this thread, have a look at: https://www.didgeridoohan.com/magisk/MagiskInstallationIssues
It gives you even more information how to enable or disable encryption or dm-verity while usinf magisk.
Btw. you can use the terminal in twrp also, see link.
Can I use the built-in twrp terminal for echo-ing rather than using adb shell ?
Subh4sh said:
Can I use the built-in twrp terminal for echo-ing rather than using adb shell ?
Click to expand...
Click to collapse
Ofcourse,cause echo command is available everywhere.just make sure you install the magisk/supersu first before running the command
hi,
If I format /data, then the encryption is gone and LOS can be installed where backup with TWRP work?
I have U11, but i think it is the same...
Hi,
I flashed TWRP on my unlocked Redmi Note 8T with MIUI Global 12.5.5. Everything was great until I rebooted it and saw Bluetooth error which pops every time I try to turn Bluetooth on or just randomly during usage of the device. I also tried to re-flas TWRP with Orange fox but it unfortunatelly did not help. Now I have no idea what to do but there are also some other people with this problem (for example:
https://www.reddit.com/r/Xiaomi/comments/y9zsak
).
Does anybody know any solution? Thanks!
Btw Orange fox is for ginko devices, I did not find version for willow
I had the exact same problem when I tried to root my stock rom in ginkgo. I was getting a lot of "app keeps stopping" pop ups, and that also included bt. My bt was completely broken until I changed rom. Also I'm guessing this had happened when I had rooted my phone with magisk, not by flashing recovery itself. Perhaps you could try to uninstall magsik, and see it it resolves the issue for you. If that would be the case, then you would have found your problem, and maybe you can flash a custom rom to safely root your phone.
Thanks for reply, but i did not have magisk flashed on my phone. I only had installed the app, prepared apk file and did nothing in TWRP (Orange fox) , just flashed a recovery with my PC, checked that it is working and rebooted device. Anyway I tried to do it only because of acces to NFC and Gpay which is now blocked.
As you also said, I would like to try custom rom (like LineageOS) because it seems like bad idea to have a stock room on an unlocked phone. Only the problem is how to backup data like data from apps, games etc.
So now it tried one of my ideas, which was to install Magisk (root) and uninstall it but it also did not help (I expected that)
vasik006 said:
Thanks for reply, but i did not have magisk flashed on my phone. I only had installed the app, prepared apk file and did nothing in TWRP (Orange fox) , just flashed a recovery with my PC, checked that it is working and rebooted device. Anyway I tried to do it only because of acces to NFC and Gpay which is now blocked.
As you also said, I would like to try custom rom (like LineageOS) because it seems like bad idea to have a stock room on an unlocked phone. Only the problem is how to backup data like data from apps, games etc.
Click to expand...
Click to collapse
To backup data simply copy your personal files in pc or sdcard. And to backup data in apps, take back-up of only those apps and where you need to backup. Don't take a complete backup using some app. That consumes a lot of space and make the newly rom feel "not so new". Most apps don't require you to take back-up offline these days. I usually backup only my personal files before flashing rom.
Yeah, that's true. But don't you know how to backup data from these "offline" apps? I was trying to solve this also before unpocking bootloader like a year ago but unsuccessfuly.
Also, which rom should I choose? I'm deciding between LineageOS and Pixel experience.
So I have LOS installed but I can´t install other zip files (like Google apps). Im only getting error: signature verification failed while. Im using LOS recovery so where is the problem?
Solved it!
Hey @vasik006 ! I know this is very late and you might have found the solution yourself, but I found the solution to this problem. Since yesterday I was trying to root my ginkgo with twrp, using magisk delta and had exact same issue. Joyose and bluetooth keeps stopping, and don't work. Simply factory reset ( I also formatted data) in twrp, and in next boot bluetooth should work. Then you can simply install the magisk apk and let it do its thing. No need to flash again since it has already made changes to boot file that can't be overriden by resetting phone.
Thanks, this might help someone else with this problem. I have already formatted my phone, installed Lineage OS and everything is ok
For me, the problem with BT and Joyose occurs only with TWRP v3.7.x. I went back to TWRP v3.6.1_9-0 but now backups are not working.
Jatin Verma x821 said:
Hey @vasik006 ! I know this is very late and you might have found the solution yourself, but I found the solution to this problem. Since yesterday I was trying to root my ginkgo with twrp, using magisk delta and had exact same issue. Joyose and bluetooth keeps stopping, and don't work. Simply factory reset ( I also formatted data) in twrp, and in next boot bluetooth should work. Then you can simply install the magisk apk and let it do its thing. No need to flash again since it has already made changes to boot file that can't be overriden by resetting phone.
Click to expand...
Click to collapse
I have the same problem with the Redmi note 8. Did you unroot first or did the factory reset directly? Tks
ennev said:
I have the same problem with the Redmi note 8. Did you unroot first or did the factory reset directly?
Click to expand...
Click to collapse
no need to unroot. simple factory reset the device and you're done.
Jatin Verma x821 said:
To backup data simply copy your personal files in pc or sdcard. And to backup data in apps, take back-up of only those apps and where you need to backup. Don't take a complete backup using some app. That consumes a lot of space and make the newly rom feel "not so new". Most apps don't require you to take back-up offline these days. I usually backup only my personal files before flashing rom.
Click to expand...
Click to collapse
TWRP is invaluable for backing up the system before making changes like theming etc. and I can take a TWRP backup to any of my (all the same) devices and restore the whole thing in just a few minutes. So convenient! I really couldn't imagine life without TWRP. TWRP enables me to clone my device in case of hardware failure. All my settings and all my apps and all my custom configurations which would otherwise take hours/days to setup - BAM! Presto! on the new device and running perfectly.
TWRP + NeoBackup are essential. TWRP as described, and NeoBackup to roll back breaking updates to apps when devs butcher them, break them, and/or just remove really useful features. I also disconnect apps that get ruined by an update from the Play Store so they don't keep coming up when I check for updates.
Alpha_Geek1 said:
TWRP is invaluable for backing up the system before making changes like theming etc. and I can take a TWRP backup to any of my (all the same) devices and restore the whole thing in just a few minutes. So convenient! I really couldn't imagine life without TWRP. TWRP enables me to clone my device in case of hardware failure. All my settings and all my apps and all my custom configurations which would otherwise take hours/days to setup - BAM! Presto! on the new device and running perfectly.
TWRP + NeoBackup are essential. TWRP as described, and NeoBackup to roll back breaking updates to apps when devs butcher them, break them, and/or just remove really useful features. I also disconnect apps that get ruined by an update from the Play Store so they don't keep coming up when I check for updates.
Click to expand...
Click to collapse
I would advise you to read the posts again. They were asking about how to take backup of "personal apps" which twrp can't do, and if they are changing ROM then twrp backup won't be of any use to them. Therefore, whatever you're trying to tell here doesn't really help the discussion.
Jatin Verma x821 said:
I would advise you to read the posts again. They were asking about how to take backup of "personal apps" which twrp can't do, and if they are changing ROM then twrp backup won't be of any use to them. Therefore, whatever you're trying to tell here doesn't really help the discussion.
Click to expand...
Click to collapse
TWRP does backup personal apps and their settings. Once you restore a TWRP backup, you have everything back except media files - images, videos, documents, etc. The launcher icons, the apps, the system settings - everything is a perfect clone which you can restore on a new device (same model, of course).
I actually came across this thread searching to see if others had a problem where merely flashing TWRP caused Bluetooth to crash (and Atmos).
Use OrangeFox
is there anyone use BT-fix-for-PE-20190618.zip to fix this problem ?
I'm on an ROG Phone II with the same issue.
The "fix" is to wipe in TWRP and install Magisk BEFORE you leave for your first boot and NEVER come back to TWRP as the issue will return the second recovery is booted.
s3rv said:
For me, the problem with BT and Joyose occurs only with TWRP v3.7.x. I went back to TWRP v3.6.1_9-0 but now backups are not working.
Click to expand...
Click to collapse
From what I can tell, this is correct. 3.6_XX-X allows me to come and go from TWRP as much as I please without incurring the bug, however, I haven't tested backup though I can't see a reason why they wouldn't work.
Are these existing backups that aren't working or the whole backup function in general?
starkshadow said:
is there anyone use BT-fix-for-PE-20190618.zip to fix this problem ?
Click to expand...
Click to collapse
It looks like this guy didn't have any luck with it either. It may be divice specific
Dredead said:
I'm on an ROG Phone II with the same issue.
The "fix" is to wipe in TWRP and install Magisk BEFORE you leave for your first boot and NEVER come back to TWRP as the issue will return the second recovery is booted.
From what I can tell, this is correct. 3.6_XX-X allows me to come and go from TWRP as much as I please without incurring the bug, however, I haven't tested backup though I can't see a reason why they wouldn't work.
Are these existing backups that aren't working or the whole backup function in general?
It looks like this guy didn't have any luck with it either. It may be divice specific
Click to expand...
Click to collapse
amazing, I have do nothing, just reboot my device, and yesterday the bluetooth also has problem, but today I open bluetooth, it is no problem. I'm still confused about that.
starkshadow said:
amazing, I have do nothing, just reboot my device, and yesterday the bluetooth also has problem, but today I open bluetooth, it is no problem. I'm still confused about that.
Click to expand...
Click to collapse
It seems to be a twrp issue. What version do you have? And what version of magisk do you have?
I have recently flashed miui 12 (android 10) after bricking the phone using qtel. I noticed the Bluetooth problem last week and didn't find a fix. I have twrp 3.6.2 and magisk 25.1. I had twrp 3.7.1 but if failed to decrypt data using pattern so I rolled back to 3.6.2. And I thought that magisk had to do with the Bluetooth problem so I rolled back to 25.1 from 26.
I still can't use the Bluetooth, and I don't have time to reset the phone, I just finished restoring everything
I CAN CONFIRM
go back to the previous twrp 3.6.2 version + wipe factory reset or simply format data solve sucesfuly solve installation issue of Magisk 26.1 or Magisk Delta 25210
Olfason said:
I CAN CONFIRM
go back to the previous twrp 3.6.2 version + wipe factory reset or simply format data solve sucesfuly solve installation issue of Magisk 26.1 or Magisk Delta 25210
Click to expand...
Click to collapse
I can't afford resetting my phone right now , don't have enough time. I'll let it like that for some months.
Edit : I have miui 12.0.6 installed (android 10) and I'm not planning to upgrade since I have much better battery life (even better than every mod I tried). I wander if I flash miui rom from recovery can fix it?
Edit 2: flashing the rom from recovery didn't fix it