Related
Hi all.
I'm running CM12 2015-01-18 on my S4 i9505 and have TWRP 2.8.4.0 installed as well.
I have successfully encrypted the phone (or well the data partition is encrypted anyway), by just going into settings and doing it.
TWRP however cannot mount it, and I thought TWRP supports encrypted phones?
So how do I go about when I am to update the phone to a newer CM12?
Is there something I'm missing that I need to do?
When I encrypted it I let it sit there without touching it for a while and then put the PIN in the first time and then let it sit overnight (someone recommended letting it just lie there for 20 minutes because otherwise WIFI won't work - and I had that issue with the 2015-01-15 build so I let it rest for a long while this time and it's all working nicely now).
Thanx for any input.
// Stefan
After some more work I've found that TWRP doesn't seem to support the encryption of CM12. Is CM12 using something different than everybody else?
I understand HTC does something special in their Lollipop (at least?) encryption, but that's not relevant for CM12.
// Stefan
The way to undo the encryption is to have TWRP format data - which will also erase the internal SD.
Before doing this connect to a pc and copy the contents of the internal SD to the pc so you have a backup of it.
Hopefully you have a TWRP nandroid backup - this should also be backed up to the pc.
Thanx, that's how I've done it already but it feels a bit cumbersome doing that every time there's a new nightly out.
I'm surprised there's no in-place-decryption process (like there is an in-place-encryption) in CM. While I can think of a few reasons why there wouldn't be I'm still surprised.
Thanx for the answer though! Let's hope they update their support (or someone else adds it to TWRP).
// Stefan
I might be wrong, but my impression is that everyone is doing encryption differently : Google nexus stock, HTC, Samsung, cyanogenmod 11,cyanogenmod 12th, etc..
So it's very difficult or impossible for TWRP to support all the different flavors.
Cyanogenmod builds it's own CWM recovery, and it's my understanding that even cyanogenmod's recovery does not support encryption.
Encryption is a great idea, but it seems cyanogenmod does not really support it - probably because the development community considers encryption to be unimportant.
On the other hand, if one abandons the products
of the development community and uses stock android, then the stock recovery does not provide backups, and one gets over the air updates.
Similarly, the current state of development software like cyanogenmod and a custom recovery (CWM or TWRP) does not provide backup capability to an encrypted phone or tablet, and updates are probably done via USB doggle, copying update zip to unencrypted cache partition, or via a connected pc.
For me personally, the only reason I root is to be able to make and restore backups via recovery and individual apps via titanium backup. Being forced to choose between encryption or backups is unfortunate.
UPDATE: Please read the next post.
A while back, I rooted my v20 with magisk using this method and everything worked fine for a few months, except for a few issues that reflashing the system would fix. Last night, SystemUI kept crashing (the status bar and the buttons would disappear). After a while, the phone crashed, and then it completely refused to boot. It would very rarely get to the lock screen, but it usually crashes soon after I unlock it. I tried everything I know of that could fix it, such as restoring the boot partition and reflashing magisk, reflashing the system partition, and wiping the cache and dalvik/ART cache. I eventually gave up with this and just reset it through the wipe menu in TWRP. I was able to get the phone to work for about a day without any issues, and then the same thing started happening again. It would take a really long time to boot and the system would crash. I tried using that ~1 minute it gives me before crashing to enable core mode in magisk to prevent any modules from loading, but that didn't do anything. I am really confused as to why this would happen considering that I reset the boot and system partitions multiple times in this process, and eventually did a full reset. It should be like a brand new phone. I really don't know what could possibly be the issue. Any help would be greatly appreciated.
Update: It turns out that Magisk Core Only Mode did not properly apply because of yet another crash. I cleared my cache once more, which gave me enough time to properly apply it, and now my phone is staying on and not crashing. But this still is concerning to me. I was able to run Magisk modules perfectly fine in the past, including after the most recent Magisk zip update, so why is it that I can no longer run modules, and that this issue persists after a factory reset? It can't be an update, because, as I stated, I was able to run modules just fine for at least a week before these issues occurred. Please correct me if I'm wrong, but this makes absolutely no sense and I want to be able to run modules again. I even deleted the modules through TWRP but the only thing that seems to fix this issue is completely disabling all other features via Magisk Core Only Mode.
Update 2: A Magisk update came out recently and I tried updating to that to see if it would fix the issue. This only brought back the original crashes. I tried using the Magisk uninstaller zip (because I found that simply reflashing Magisk isn't enough, there are other files which magisk uses to store data.) After doing this and reflashing Magisk, it worked for a little bit, but, me being me and wanting busybox installed, I managed to bring back the crashes. After that, uninstalling and flashing magisk would work, but only until a reboot. I am at a complete loss. I am currently backing up my internal storage (manually since TWRP doesn't) and I will try a full /data format.
Ok, it has been a few days since I wrote the previous section but I decided not to post it because if the /data format worked, I didn't want to have bumped it for no reason. At first, it worked, and I decided to leave it like that without rebooting it for a few days or messing with Magisk, and my phone worked perfectly. I had to restart my phone because Google photos was acting up, and it started crashing again. I am genuinely confused. I completely formatted my phone and reflashed Magisk several times, and it is still crashing. I just reset my phone again because I attempted to just restore a stock boot backup from before I installed Magisk, which made my phone completely unbootable. I pulled the battery and found that it tried re-encrypting the phone (AFAIK, TWRP doesn't support encrypted data on the v20, which really sucks) so I had to wipe it and flash Magisk so it wouldn't re-encrypt it. I will try to do this again, but I don't want to not be able to restart my phone (which is so far the only thing that's working for me). This time, not even uninstalling and re-flashing Magisk worked this time, as it has all of my previous attempts. I had to completely reset it. Again. I really need this issue fixed. I probably already said this, but I would greatly appriciate any possible help I could get. I really want my phone back.
Ok I forgot to include some basic information about my phone.
Model number: LG-H910
Android version: 7.0
Android security patch level: April 1, 2017
Kernel version: 3.18.55
Build number: NRD90M
Software version: H91010m
According to Kernel Auditor:
Kernel: Linux version 3.18.55-Werewolf-2.0-Basilisk ([email protected]) (gcc version 6.3.1 20170430 (GCC) ) #1 SMP PREEMPT Sat Jun 24 00:56:07 CDT 2017
Bump/Update: This is a small one, but, despite not restarting my phone, Magisk is showing an error "Magisk is not installed". Root access also disappeared. I don't know how much longer I can keep it on without having to restart it due to random issues like these that usually fix themselves with a reboot. I would appreciate any help.
Seems like your phone is all sorts of wacked out. I noticed from the specs your using the werewolf kernel. I had all sorts of performance issues as well as random reboots using that kernel. Since you're losing root and the system is overall unstable I recommend wiping clean and starting over. Wipe system, data, cache, and dalvik in twrp and flash the full stock 10r zip by runningnak3d. It will put you on the latest security patch with the newest firmware available. I recommend installing askerm2000 1.4 kernel as it is very stable and works well on the h910. Flash magisk last (latest 15.3 works great for me) and reboot. Hopefully will solve your problems. The 10r zip for the h910 plus askermk2000 kernel and magisk has served me well for a while now.
toastyp said:
Seems like your phone is all sorts of wacked out. I noticed from the specs your using the werewolf kernel. I had all sorts of performance issues as well as random reboots using that kernel. Since you're losing root and the system is overall unstable I recommend wiping clean and starting over. Wipe system, data, cache, and dalvik in twrp and flash the full stock 10r zip by runningnak3d. It will put you on the latest security patch with the newest firmware available. I recommend installing askerm2000 1.4 kernel as it is very stable and works well on the h910. Flash magisk last (latest 15.3 works great for me) and reboot. Hopefully will solve your problems. The 10r zip for the h910 plus askermk2000 kernel and magisk has served me well for a while now.
Click to expand...
Click to collapse
Thank you. Before I do this, I have a few questions.
1. How do I disable force encrypt with Magisk? I remember when I flashed Magisk 14.0, that managed to disable force encrypt, but any other version of Magisk wouldn't do that when installing fresh (updates kept this setting). AFAIK TWRP is unusable on the v20 for things such as backups, file browser, etc because it isn't compatible with the encryption algorithm used by the v20. How would I turn off force encrypt with the latest Magisk zip
2. Should I do a full format data (where you have to actually type "yes" to confirm it) or just wipe those partitions using advanced wipe?
3. Will the askerm2000 kernel hide modified boot, unlocked bootloader, etc from safetynet just as Werewolf kernel did, and will it get rid of the static boot issue?
4. Will this increment ARB? If anything goes wrong, I want to be able to roll back.
5. If it was working perfectly fine before, what suddenly made everything come crashing down, even after multiple wipes? This is not as important as the other ones, I am just curious.
Sorry if these questions seem over excessive and/or obvious. Doing stuff like this tends to make me a bit nervous and I want to think of everything I can that might affect the outcome.
NullBite said:
Thank you. Before I do this, I have a few questions.
1. How do I disable force encrypt with Magisk? I remember when I flashed Magisk 14.0, that managed to disable force encrypt, but any other version of Magisk wouldn't do that when installing fresh (updates kept this setting). AFAIK TWRP is unusable on the v20 for things such as backups, file browser, etc because it isn't compatible with the encryption algorithm used by the v20. How would I turn off force encrypt with the latest Magisk zip
2. Should I do a full format data (where you have to actually type "yes" to confirm it) or just wipe those partitions using advanced wipe?
3. Will the askerm2000 kernel hide modified boot, unlocked bootloader, etc from safetynet just as Werewolf kernel did, and will it get rid of the static boot issue?
4. Will this increment ARB? If anything goes wrong, I want to be able to roll back.
5. If it was working perfectly fine before, what suddenly made everything come crashing down, even after multiple wipes? This is not as important as the other ones, I am just curious.
Sorry if these questions seem over excessive and/or obvious. Doing stuff like this tends to make me a bit nervous and I want to think of everything I can that might affect the outcome.
Click to expand...
Click to collapse
Twrp can properly decrypt the v20. Twrp backup and restore works just fine for me. Never had an issue with this. You format data and then type yes. Wipes the data partition but this is only needed once. Decrypts the device and twrp can then do it's thing. Encryption problems stem from booting into system with a stock boot image that has force encryption enabled without flashing magisk or supersu. They modify the kernel to prevent the device from rencrypting. Latest magisk 15.3 has zero issues keeping the phone decrypted. The modified boot warning has nothing to do with the kernel. This is caused by the debug bootloader used to achieve root on the US carrier v20's. Nothing can be done to change that. ARB has not been incremented on the h910 so that isn't an issue currently. Potentially in the future, but not right now. The problems you're having could stem from a multitude of issues. Could be modifications you made, bad flashes, etc. If you're having issues with encryption and stuff sounds like magisk wasn't functioning properly at the end. I've been rooted since last January and haven't experienced anything like that before so I'm not sure
toastyp said:
Twrp can properly decrypt the v20. Twrp backup and restore works just fine for me. Never had an issue with this. You format data and then type yes. Wipes the data partition but this is only needed once. Decrypts the device and twrp can then do it's thing. Encryption problems stem from booting into system with a stock boot image that has force encryption enabled without flashing magisk or supersu. They modify the kernel to prevent the device from rencrypting. Latest magisk 15.3 has zero issues keeping the phone decrypted. The modified boot warning has nothing to do with the kernel. This is caused by the debug bootloader used to achieve root on the US carrier v20's. Nothing can be done to change that. ARB has not been incremented on the h910 so that isn't an issue currently. Potentially in the future, but not right now. The problems you're having could stem from a multitude of issues. Could be modifications you made, bad flashes, etc. If you're having issues with encryption and stuff sounds like magisk wasn't functioning properly at the end. I've been rooted since last January and haven't experienced anything like that before so I'm not sure
Click to expand...
Click to collapse
Ok, I cannot possibly thank you enough for this. After this started happening, I seriously thought my phone was at the end of its life. If this were to happen, I wouldn't be able to get a new phone anytime soon. Not only did it fix the crashes (I only restarted it once, I'm not going to try to intentionally make it crash), It ALSO managed to fix my FM radio and (I think) the Google Assistant Voice Match unlock thing, both of which I never even thought I would be able to get back. Let's just hope that it stays this way. I have one last question. Would you say it's safe to download and install Magisk modules now?
NullBite said:
Ok, I cannot possibly thank you enough for this. After this started happening, I seriously thought my phone was at the end of its life. If this were to happen, I wouldn't be able to get a new phone anytime soon. Not only did it fix the crashes (I only restarted it once, I'm not going to try to intentionally make it crash), It ALSO managed to fix my FM radio and (I think) the Google Assistant Voice Match unlock thing, both of which I never even thought I would be able to get back. Let's just hope that it stays this way. I have one last question. Would you say it's safe to download and install Magisk modules now?
Click to expand...
Click to collapse
Yes. I use a few modules myself without an issue. If you're unsure of the stability of a module, you can always take a nandroid backup in twrp prior to installation. If things are stable, and then you flash something and the phone freaks out, it's most definitely the mod you have flashed causing problems. Some modules make changes to the system partition that have the potential to problems. But I haven't had a module cause my device to bootloop or reencrypt. So I think you're good to go. Glad you're phone is up and running as it should. Very strange that it was in such a bad way, but crap happens. I have had zero issues with this setup (10r + 1.4 askermk kernel + magisk 15.3).
I have the stock firmware on the H990 version, I end up on the Crash LK screen error. I can access TWRP, how can I restore access to my device without losing data? Thanks.
After installing TWRP and LOS I unknowingly locked the bootloader.
I had the idea this was the course of action to protect your phone. Only after did I noticed messages saying not to lock it.
After that the phone automatically rebooted and TWRP apparently detected the problem and did something to fix things I suspect. It was too fast and I can't recall the details.
Anyway, everything works fine. Apart from the warning message during boot, that everyone also gets.
My question is:
Will this be a problem when upgrading TWRP or LOS? Or is there anything I should be worried about?
Thanks
I'm currently running a custom ROM (AOSiP), but this started happening on a different rom (Syberia). With a recent update, I noticed that suddenly I couldn't use fingerprint authentication for apps anymore. Eventually, I wound up having to format data (and sadly lost quite a few recent photos that had not yet been backed up) and start all over because neither the lockscreen nor TWRP would accept my correct pattern to decrypt.
Several wipe and resets later I decided to switch to a different ROM (AOSiP). And now I'm having the same issues with a completely clean flash (I started off with MSMDownloadTool to bring the phone back to factory). The ROM was working fine, as well as fingerprint and pattern unlocks, until I restarted. Now, I can't get past the lockscreen OR TWRP pattern unlocks. Here is what I found in logcat:
Code:
java.lang.RuntimeException: Failed to decrypt blob
at com.android.server.locksettings.SyntheticPasswordCrypto.decryptBlob(SyntheticPasswordCrypto.java:143)
at com.android.server.locksettings.SyntheticPasswordManager.decryptSPBlob(SyntheticPasswordManager.java:1117)
at com.android.server.locksettings.SyntheticPasswordManager.unwrapSyntheticPasswordBlob(SyntheticPasswordManager.java:978)
at com.android.server.locksettings.SyntheticPasswordManager.unwrapPasswordBasedSyntheticPassword(SyntheticPasswordManager.java:907)
at com.android.server.locksettings.LockSettingsService.spBasedDoVerifyCredential(LockSettingsService.java:2426)
at com.android.server.locksettings.LockSettingsService.doVerifyCredential(LockSettingsService.java:1700)
at com.android.server.locksettings.LockSettingsService.checkCredential(LockSettingsService.java:1667)
at com.android.internal.widget.LockPatternUtils.checkCredential(LockPatternUtils.java:374)
at com.android.internal.widget.LockPatternUtils.checkPattern(LockPatternUtils.java:426)
at com.android.internal.widget.LockPatternUtils.checkPattern(LockPatternUtils.java:413)
at com.android.server.locksettings.LockSettingsShellCommand.checkCredential(LockSettingsShellCommand.java:182)
at com.android.server.locksettings.LockSettingsShellCommand.onCommand(LockSettingsShellCommand.java:59)
at android.os.ShellCommand.exec(ShellCommand.java:103)
at com.android.server.locksettings.LockSettingsService.onShellCommand(LockSettingsService.java:2074)
at android.os.Binder.shellCommand(Binder.java:634)
at android.os.Binder.onTransact(Binder.java:532)
at com.android.internal.widget.ILockSettings$Stub.onTransact(ILockSettings.java:532)
at android.os.Binder.execTransact(Binder.java:731)
Caused by: java.security.InvalidKeyException: Only SecretKey is supported
at com.android.org.conscrypt.OpenSSLCipher.checkAndSetEncodedKey(OpenSSLCipher.java:462)
at com.android.org.conscrypt.OpenSSLCipher.engineInit(OpenSSLCipher.java:296)
at javax.crypto.Cipher.tryTransformWithProvider(Cipher.java:2980)
at javax.crypto.Cipher.tryCombinations(Cipher.java:2891)
at javax.crypto.Cipher$SpiAndProviderUpdater.updateAndGetSpiAndProvider(Cipher.java:2796)
at javax.crypto.Cipher.chooseProvider(Cipher.java:773)
at javax.crypto.Cipher.init(Cipher.java:1288)
at javax.crypto.Cipher.init(Cipher.java:1223)
at com.android.server.locksettings.SyntheticPasswordCrypto.decrypt(SyntheticPasswordCrypto.java:63)
at com.android.server.locksettings.SyntheticPasswordCrypto.decryptBlob(SyntheticPasswordCrypto.java:135)
... 17 more
Obviously my device is encrypted so I my only option is to format again and start over for the 4th time in the past 2 days, only to worry that this might happen again. Can anyone help? Thanks in advance.
NOTE: Sig is outdated.
EDIT: Not sure if it is relevant, but the phone was initially encrypted via OOS, then wiped and set up via AOSiP with encryption already in place.
You didn't say what version of TWRP? Generally when going between AOSP and OOS formatting data is necessary otherwise you will have encryption problems. MSMTool is sort of a drastic measure though.
OhioYJ said:
You didn't say what version of TWRP?
Click to expand...
Click to collapse
Initially twrp-3.3.1-1 but now twrp-3.3.1-7 unofficial
MSMTool is sort of a drastic measure though.
Click to expand...
Click to collapse
I was fed up and figured a bone stock base couldn't hurt at that point since I had lost everything already anyway.
Generally when going between AOSP and OOS formatting data is necessary otherwise you will have encryption problems.
Click to expand...
Click to collapse
I may have just come to the same conclusion. I formatted and left forceencrypt enabled, then set up using AOSiP and now fingerprint auth works in apps again. Initially I never did it this way because forceencrypt would be disabled with fresh formatting, and the in-rom encryption option resulted in FDE rather than FBE for some reason.
Was this a recent development that formatting was required? I had no issues for 7 months with my OOS encrypted data until now.
Any ROM that has the May security patches will require a newer version of TWRP, so 3.3.1-7 may have originally decrypted your data, hard to say. I don't remember which version originally included that fix. It's been in there for a few versions though.
Formatting data has been a thing for a while, essentially the entire time as far as I'm aware (I've always done it that way). Even though it's a pain. It's the only way to avoid problems. This is how to do it. Some ROMs may handle not formatting this better than others, but it seems like skipping that step is when problems happen.
I don't think there is a way to get to FDE on these devices, otherwise your phone would ask for a password on boot.
OhioYJ said:
Any ROM that has the May security patches will require a newer version of TWRP, so 3.3.1-7 may have originally decrypted your data, hard to say. I don't remember which version originally included that fix. It's been in there for a few versions though.
Formatting data has been a thing for a while, essentially the entire time as far as I'm aware (I've always done it that way). Even though it's a pain. It's the only way to avoid problems. This is how to do it. Some ROMs may handle not formatting this better than others, but it seems like skipping that step is when problems happen.
I don't think there is a way to get to FDE on these devices, otherwise your phone would ask for a password on boot.
Click to expand...
Click to collapse
Actually, FDE is what I would initially get with formatted data and a clean install with forceencrypt disabled. If I tried to encrypt via settings, I would get FDE and password before boot. At least initially it was that way (circa when FP first became possible on custom roms 8.1). I had never bothered messing with it after that, as I had no issues with the OOS encrypted volume. Oh well. At least now I can be sure it has been done correctly. Thank you for the insight!
Mods please mark as solved
Hi,
I have a Oneplus 6T A6013. Yesterday my phone had this state:
bootloader u
nlocked
root installed with magisk
a couple of magisk module installed
latest stable
stock rom (10.3.0)
Then an OTA update (10.3.1) arrived to me and I installed as usual:
OTA full download and
installation, without reboot
Magisk installation o
n other partition and reboot
Here begin problems. My phone reboot and get stucked on OnePlus animation.
I can force shut down, enter stock recovery, enter bootloader.
I can not rely on
Code:
fastboot boot twrp.img
because phone reboots and stucks on fastboot logo.
I decide to do factory reset phone, with Google backup it is not a big problem, during configuration I obviously login in with the same account and obviously backup is on cloud, but phone says "no backup found".
Moreover it seems that magisk root files were still present on the phone, and even "uninstalling" them from magisk manager doesn't remove sucessfully them.
At this point I have tried to make a completely fresh install of the OS:
during configuration still no backup found, even if I have created more backup in the meanwhile, one of them jsut before fresh install and on Drive I can see all of them
Google Pay sais that my system is not right, maybe cause root
using Magisk Manager I have checked that this time root is no more installed, but I can see that "cts check" fails
Play Store -> settings also says to me that "my phone is not certified"
Maybe I am not able to recover backup cause cts check fails. I have still bootloader unlocked.
So here are my questions.
Someone knows beacuse my phone doesn't recognize its own backups?
How can I pass cts check?
In case I should relock bootloader, how can I check that everything is truly stock and avoid a possible brick?
Thank you so much for your future answers, I have searched on internet and made tries for a whole day and contacted OnePlus chat assistence twice, but without any luck.
You have to actually wait a few minutes after running "fastboot boot boot.img" command to boot the TWRP, and you MUST use the latest one (always use up-to-date tools) which in that case is TWRP 3.3.1-31 - you have to use "Q" version of bootable TWRP image for OxygenOS 10.3.1 which is obviously Android 10 Queen Cake so be sure to use the right one.
Tethered Fastboot TWRP boot works just fine for me, in fact I installed crDroid 6.2 ROM atop OxygenOS 10.3.1 on my converted T-Mobile OnePlus 6T.
As for the bootloader, once it's unlocked, I strongly recommend leaving it alone unlocked unless you really like to use MSMTools more often. Use SafetyPatch in Magisk's module manager, it will fix the CTS SafetyNet issues. Locked bootloader actually causes more problems compared to unlocked one in my experience.
Sent from my ONEPLUS A6013 using Tapatalk
First of all thank you very much for your answer.
Is this type of twrp right?
I thank you really much for your suggestion about locking bootloader. I don't want to specifically remove root, the real problem Is that I am no more able to recover my old backup. I have just supposed that bootloader and root could be tha causes.
Before I fully reflashed OS I was able to Hide robot and pass all checks using Magisk, buy as I said I was not able to recover backup, neither a fresh and new just made backup.
I worry about the future. Now I could set again all the phone, but what will happens if tomorrow I will have to reset again?
Dr. Mario said:
You have to actually wait a few minutes after running "fastboot boot boot.img" command to boot the TWRP
Click to expand...
Click to collapse
I used latest version by fajita downloaded from my previous link. I have waited for 10 minutes stacked on oneplus fastboot mode logo and nothing happens. Now I have the problem that I am no more able to flash magisk...
That doesn't sound good - MSMTools may be necessary. Did you back up all the files?
If your T-Mobile OnePlus 6T is converted, install OxygenOS 9.0.11 and unlock the bootloader once again (MSMTools usually relock the bootloader, so unlock it again), then update to OxygenOS 10.3.0 or 10.3.1 via update zip file (I don't trust OTA updates at all, they tend to cause problems), then install the TWRP once you're at it, and then reboot back into the recovery and install Magisk if you want to.
Unless... You want to install custom Android 10 operating system which then you must do that; First reinstall OxygenOS 10.3.x ROM (in all slots, it is mandatory because you will install the same custom OS on both slots so it boots properly) then boot into TWRP, and do factory reset and data wipe in the Wipe menu, then reboot back into recovery and then plug in the USB flash drive or copy the TWRP, OS installation zip and whatever else you want installed onto the phone via the computer. Then install crDroid, LineageOS or any of OS of your choosing, and TWRP, and reboot back into recovery once again and install the OS and TWRP one final time in another slot. After doing the last reboot, install Gapps and Magisk. Finally, after you are done and reboot the phone after the installation, it will reboot by itself once - that's due to Magisk doing some configuration.
Android 10 apparently have made installation of custom ROM difficult. I have managed to brick my OnePlus 6T eight - ten times before deciding to find out how to do it successfully, thus the instruction for installation of custom OS above.
As for failure to restore the backup, this is the artifact of the Android 10 UEFI bootloader encryption (which is occasionally buggy, and annoying - just installing the LineageOS 17 the normal way, the whole SSD just gets corrupted, so the trick to get it to work is to, yes, remove all SSD encryption keys via factory reset prior to installing any custom ROM). As of now, TWRP backup is broken on most phones running Android 10 which is due to how the encryption works in this OS version (to the point they are so touchy).
Sent from my ONEPLUS A6013 using Tapatalk
Dr. Mario said:
That doesn't sound good - MSMTools may be necessary. Did you back up all the files?
Click to expand...
Click to collapse
Yes, my device is actually ready to be wiped and I have already the international version.
The problem is that MSMTools' link are down.
Dr. Mario said:
As for failure to restore the backup, this is the artifact of the Android 10 UEFI bootloader encryption (which is occasionally buggy, and annoying - just installing the LineageOS 17 the normal way, the whole SSD just gets corrupted, so the trick to get it to work is to, yes, remove all SSD encryption keys via factory reset prior to installing any custom ROM). As of now, TWRP backup is broken on most phones running Android 10 which is due to how the encryption works in this OS version (to the point they are so touchy).
Click to expand...
Click to collapse
Do you mean "manual backup" such as nanodroid, or "automatic Google backup"?
I have no manual backup, only that one saved on Drive, it should be restored automatically during configuration of operating system.
Any way you can back it up. TWRP backup (and any nandroid) in general are broken for many Android 10 phones because of the SSD encryption - I suspect that by each reboots, new cipher keys may be generated every time, thus making it hard to be able to successfully reinstall the Nandroid backup at any point in time - they're like the snowflakes, each and every EXT4 ciphers are different. (All that is meant to resist the hacker attack, even on the custom ROMs - Google wanted to be sure they cover everyone in term of computing security, so all that encryption Voodoos are also in the AOSP and LineageOS repositories for that reasons.)
As for MSMTools, I really wonder. OnePlus didn't object before.
Sent from my ONEPLUS A6013 using Tapatalk
Gabriel1495 said:
Yes, my device is actually ready to be wiped and I have already the international version.
The problem is that MSMTools' link are down.
Do you mean "manual backup" such as nanodroid, or "automatic Google backup"?
I have no manual backup, only that one saved on Drive, it should be restored automatically during configuration of operating system.
Click to expand...
Click to collapse
Try this thread
https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746
Backup argumentation is now more clear, thank you
Dr. Mario said:
As for MSMTools, I really wonder. OnePlus didn't object before.
Click to expand...
Click to collapse
About MSMTools I have still some problem, fault of my really bad English...
I have not understood your answer, what does it means "OnePlus didn't object before"? Actually I am simply no able to download the tool.
Thank you again for your kindness
Striatum_bdr, that will do. The unbricking tool collection looks good.
Sent from my ONEPLUS A6013 using Tapatalk
Wonderful, I will read the "unbricking tool" thread in order to understand how to install it
Hopefully you get it to work once again.
Sent from my ONEPLUS A6013 using Tapatalk
Here I am with some good update
I have used MSMTools to truly factory reset my phone. Initially I had "sahara connection" error, but install again both Qualcomm and Oneplus drivers do the trick. After execution of MSMTools phone reboot with bootloader locked and as it was out of box.
At that point on Drive I had 3 backup (9 Feb, 10 Feb and 10 Feb) and magically last backup of 10 Feb was seen! Saddly even deleting last two backups I am not able to recover my true backup of 9 Feb (at this point it doesn't matter).
Now I have a virgin and working phone. I have no root and can use Google Pay and banking apps.
Really happy and satisfied, thank you thank you thank you very much!!!!
Dr. Mario said:
Any way you can back it up. TWRP backup (and any nandroid) in general are broken for many Android 10 phones because of the SSD encryption - I suspect that by each reboots, new cipher keys may be generated every time, thus making it hard to be able to successfully reinstall the Nandroid backup at any point in time - they're like the snowflakes, each and every EXT4 ciphers are different. (All that is meant to resist the hacker attack, even on the custom ROMs - Google wanted to be sure they cover everyone in term of computing security, so all that encryption Voodoos are also in the AOSP and LineageOS repositories for that reasons.)
As for MSMTools, I really wonder. OnePlus didn't object before.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
What is up with that? I booted into TWRP the other day, figured I would make a backup before upgrading, and everything was garbled.
That's because of the onboard encryption; all Nandroid backup being attempted on Android 10 only hold half of the overall encryption keys, others just stays on the phone, so when you attempt to put it back on, it is already invalidated because also Android 10 ROM on some phones (particularly the Pixels, and a few OnePlus phones like this one) changes keys upon reboots for security reasons.
Google do not want anyone including the US Government to have their hands on the data thereon as it could be very bad if it falls in the wrong hands so they went extra miles to make it difficult to hack.
Sent from my ONEPLUS A6013 using Tapatalk