Hey,
according to the Magisk OTA tutorial (https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md) you should never RW mount the /system or /vendor partition. Otherwise a verification will be broken and OTA updates will fail.
I had to mount my /system partition in the past and now Android won't find any OTA updates.
Does anybody knows if there's a way to repair the verification so that OTA updates will be working again?
Thanks
Jas
You'll have to reflash at least the system image, or the entire factory image/firmware package/ROM. Depends on your device.
Don't update a rooted phone!
Sent from my SM-A605FN using Tapatalk
Didgeridoohan said:
You'll have to reflash at least the system image, or the entire factory image/firmware package/ROM. Depends on your device.
Click to expand...
Click to collapse
That was also my first thougt, but it seems not working.
I got my Pixel 3 in December. Right after the first boot it found and installed the December OTA without any problem. Then I rooted the phone with Magisk.
In January it didn't find any OTA. Therefore I've installed the factory image manually with fasboot. That was nearly at the end of January. I didn't RW mount the /system partition after then. But the phone is not finding the February OTA.
I've just flashed the whole January factory image again to be sure that the partitions are fine. But no luck.
When I install Magisk it mount the system partition to patch the image, I'm right? Do this break the verification too?
What else could cause that my phone won't find any OTAs anymore? According to a tcpdump the connection to the Google servers are fine.
Apologies, I did not read your post properly... That your device suddenly stopped recieving OTA has nothing to do with editing or mounting /system rw (Magisk does not alter /system at all, unless you have a ROM with addon.d and then it doesn't matter anyway). The issue with having an altered /system and OTAs will only manifest itself when you're actually trying to install the OTA (when it tries to verify the integrity of your device).
I've seen several reports of similar behaviour on Pixel devices and it might very well be related to rooting or modding your device, but I have not seen anyone presenting anything about what it could be caused by.
Good to know that I'm not alone
I've started catlog and every time I press the "Search for Updates" button I see the following errors:
Code:
02-09 14:57:03.215 813 7853 E DrmWidevineDash: tz api version = 14
02-09 14:57:03.215 813 7853 E DrmWidevineDash: OEMCrypto_APIVersion: ends! returns version 14
....
02-09 14:57:03.248 813 7853 E QSEECOMAPI: Error::Cannot open the file /vendor/firmware_mnt/image/widevine.mdt errno = 13
...
02-09 14:57:03.314 813 7853 E QSEECOMAPI: Error::Cannot open the file /vendor/firmware/hdcpsrm.mdt errno = 2
02-09 14:57:03.314 813 7853 E QSEECOMAPI: Error::Loading image failed with ret = -1
....
02-09 14:57:03.314 813 7853 E QSEECOMAPI: Error::Cannot open the file /system/etc/firmware/hdcpsrm.mdt errno = 2
02-09 14:57:03.314 813 7853 E QSEECOMAPI: Error::Loading image failed with ret = -1
I'm not sure if this is related to the issue. I've also not found any hints or something like that.
JasMan78 said:
Good to know that I'm not alone
Click to expand...
Click to collapse
I'm not getting those errors in logcat, but you're definitely not alone; I haven't received any OTA updates on my Pixel 2 since I flashed the Pie factory image in August 2018. Prior to that it all used to work fine on Oreo.
As per a previous post of mine, I found other reports of the same issue and the common factors seemed to be Pixel devices, Pie and Magisk.
I'd love to help track down the cause of the problem but I wouldn't know how, other than posting a logcat recorded during a check for updates. Anyone have any ideas?
JasMan78 said:
Good to know that I'm not alone
I've started catlog and every time I press the "Search for Updates" button I see the following errors:
I'm not sure if this is related to the issue. I've also not found any hints or something like that.
Click to expand...
Click to collapse
That is to be expected and should not prevent you from getting ota updates. The missing file is your devices L1 widevine cert. Widevine is Google's DRM software and just unlocking your bootloader causes that file to disappear. But it's done by the software on the device (I think something in trustzone does it but don't quote me on that), not by Magisk or anything you did in rooting.
That file being missing is why rooted phones can't seem HD content from Netflix
I've updated my phone to Android 10 and Magisk Canary last month. Today I got my first notification that a new OTA is available.
I've installed it successfully (restored the original boot image in Magisk, installed the OTA update and installed Magisk into the inactive slot. Reboot. Done.).
Related
0
down vote
favorite
I've been trying to install cyanogen 12.1 on my Moto X 2013.
Followed all the steps mentioned in the official Cyanogen Mod Wiki (Allowed to include the link only after 10 posts)
Flew through the steps however, the final flash of ROM fails.
Here are the logs.
Installing '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
script aborted: This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc,xt1056,ghost_sprint,xt1058,ghos
t_att,ghost_rcica,xt1060,ghost_verizon; this device is .
This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc,xt1056,ghost_sprint,xt1058,ghost_att,ghost_rcic
a,xt1060,ghost_verizon; this device is .
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'
Error flashing zip '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'
Looking at the bold face logs, my hunch is the TWRP isn't able to recognize my device's model XT1052.
Is this what's happening here? If no, what seems to be going wrong?
How do I fix this?
[email protected] said:
0
down vote
favorite
I've been trying to install cyanogen 12.1 on my Moto X 2013.
Followed all the steps mentioned in the official Cyanogen Mod Wiki (Allowed to include the link only after 10 posts)
Flew through the steps however, the final flash of ROM fails.
Here are the logs.
Installing '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
script aborted: This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc,xt1056,ghost_sprint,xt1058,ghos
t_att,ghost_rcica,xt1060,ghost_verizon; this device is .
This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc,xt1056,ghost_sprint,xt1058,ghost_att,ghost_rcic
a,xt1060,ghost_verizon; this device is .
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'
Error flashing zip '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'
Looking at the bold face logs, my hunch is the TWRP isn't able to recognize my device's model XT1052.
Is this what's happening here? If no, what seems to be going wrong?
How do I fix this?
Click to expand...
Click to collapse
Which version of TWRP are you using? Try 3.x, some of the older ones aren't working correctly.
Or alternatively, edit the "updater_script" in the ROM zip (META-INF/com/google/android), and delete the first line, starting with "assert(getprop.."
rumkugel13 said:
Which version of TWRP are you using? Try 3.x, some of the older ones aren't working correctly.
Or alternatively, edit the "updater_script" in the ROM zip (META-INF/com/google/android), and delete the first line, starting with "assert(getprop.."
Click to expand...
Click to collapse
Been using twrp-2.8.7.0-ghost
twep 3.x.x isn't released for Moto X 2013 (Ghost) yet. I tried using twrp-3.0.0.0-victaria built for Moto X 2014(Victaria), however, the phone never booted into recovery.
Also tried out removing the first line from the updater script which checks for models just as you suggested.
The flash still fails. This time with barely any logs
just says Error occurred while.. Fail
Double checked the versions(of everything) but it still isn't working.
I've had simular issue . download twrp 2.6.3.1 ... worked for me and many others
Polishpolisher said:
I've had simular issue . download twrp 2.6.3.1 ... worked for me and many others
Click to expand...
Click to collapse
Didn't work out for me. Flash just fails without any useful logs
You've probably applied compression when you've changed the updste script. It should be Store only, try again, because the error you were getting is exactly from the get prop in the first line.
[email protected] said:
0
down vote
favorite
I've been trying to install cyanogen 12.1 on my Moto X 2013.
Followed all the steps mentioned in the official Cyanogen Mod Wiki (Allowed to include the link only after 10 posts)
Flew through the steps however, the final flash of ROM fails.
Here are the logs.
Installing '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
script aborted: This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc,xt1056,ghost_sprint,xt1058,ghos
t_att,ghost_rcica,xt1060,ghost_verizon; this device is .
This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc,xt1056,ghost_sprint,xt1058,ghost_att,ghost_rcic
a,xt1060,ghost_verizon; this device is .
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'
Error flashing zip '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'
Looking at the bold face logs, my hunch is the TWRP isn't able to recognize my device's model XT1052.
Is this what's happening here? If no, what seems to be going wrong?
How do I fix this?
Click to expand...
Click to collapse
First i installed cm-12.1-20150901-SNAPSHOT-YOG4PAO237-ghost.zip then i flashed CM Recovery cm-12.1-20150901-SNAPSHOT-YOG4PAO237-ghost-recovery.img then i updated the CM by the CM Updater inside the settings and it worked great !!
Hi,
I had same issue.
My Moto X 2013 had still Android 4.4.2 as I rooded it.
Then I tried to flash CM12.1 with instuctions from wiki.cyanogenmod.org and failed with same error message as [email protected]
I tried several things mentioned here and from other forums but failed.
At least the hint from Polishpolisher was working. Many many thanks!
Found twrp-2.6.3.1-ghost-4.4.img at rootjunkysdl.com.
Herewith install of cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip was possible.
Had the same issue..
Here's what you do..
Extract the cm 12.1 file and file update script file in there ( look for it it's in there in Android or Google folder ) then delete the first line in the script " JUST THE FIRST LINE "
And voilà
Enjoy CM 12.1
I've had the same problem. The solution for me was to install the rom stock using the RSD. Then I installed the latest official version of TWRP and had no problems.
I checked my logs after a bunch of things failed and my SKU is coming up blank!
"
script aborted: Please use the right SKU for updating...
Device image SKU:
OTA image SKU: WW
Please use the right SKU for updating...
"
How can I make it WW again... this is causing me an impressive amount of problems.
Is this happening when you try to install stock from a custom ROM?
FruitlessPotato said:
Is this happening when you try to install stock from a custom ROM?
Click to expand...
Click to collapse
Happened then as well. However currently it is happening with the stock ROM that I restored after getting rid of the custom ROM
Let me also give a background. I was on CM13, went to go update got an error saying I needed to update my firmware in order to install. So I tried a crap ton to get stock roms to install, didnt work (SKU was blank). So I restored my original/stock rom which would not restore the data.
I am having the same issue. I have tried and fail many times to install UL-Z00T-WW-21.40.1220.1615-user.
Always with Error 7
Right now I am stuck in fastboot with no access to recover other than fastboot boot twrp.img
However when I try to reinstall lollipop It fails with another error
FruitlessPotato said:
I am having the same issue. I have tried and fail many times to install UL-Z00T-WW-21.40.1220.1615-user.
Always with Error 7
Right now I am stuck in fastboot with no access to recover other than fastboot boot twrp.img
However when I try to reinstall lollipop It fails with another error
Click to expand...
Click to collapse
Okay so a guy on Reddit told me that errors dont mean anything, you need to look at the logs and see what caused them which is done by the recovery log.
And if you have TWRP recovery on there try to flash CM12 for the zenfone. CM13 flashes for me but randomly/constantly reboots
Installing zip file '/sdcard1/UL-Z00T-WW-21.40.0.1692-user.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
script aborted: Can't install this M package (三 6月 15 00:54:43 CST 2016) L less than 20160426 build (Tue Apr 5 07:29:00 EDT 2016).
Can't install this M package (三 6月 15 00:54:43 CST 2016) L less than 20160426 build (Tue Apr 5 07:29:00 EDT 2016).
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '/sdcard1/UL-Z00T-WW-21.40.0.1692-user.zip'
Updating partition details...
FruitlessPotato said:
Installing zip file '/sdcard1/UL-Z00T-WW-21.40.0.1692-user.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
script aborted: Can't install this M package (三 6月 15 00:54:43 CST 2016) L less than 20160426 build (Tue Apr 5 07:29:00 EDT 2016).
Can't install this M package (三 6月 15 00:54:43 CST 2016) L less than 20160426 build (Tue Apr 5 07:29:00 EDT 2016).
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '/sdcard1/UL-Z00T-WW-21.40.0.1692-user.zip'
Updating partition details...
Click to expand...
Click to collapse
script aborted: Can't install this M package (三 6月 15 00:54:43 CST 2016) L less than 20160426 build (Tue Apr 5 07:29:00 EDT 2016).
**** that looks like you are doing CM13 and it is telling you your firmware is out of date.
So it wants you to flash the latest stock firmware.... but you and I are in the boat were our phones wont let us do that. Dude I do not know
me either, tried updating the updater-script and all but to no avail
Is your phone on Android 5.0.2?
I was trying to find ROMs that fit that version. There are definitely other custom roms then just CM
Fruitless! Download the CM13 nightly from june 14th!
Dont do the most recent.
Edit: I know this sounds sketchy and or stupid but I have a cm13 rom from june 14th that I downloaded then, it works. The CM13 from then that I downloaded today did not. I can see about uploading the one that did work if the one you download doesnt work.
This thread should be deleted.
Hello together,
as I wanted to see if I get F2FS and decryption running, I want to share my progress and exchange with others.
I got both working but there are a few issues once the system is running, at least if decrypted. When encrypted, everything seems running nice on f2fs.
Here's what I did:
ENABLE F2FS AND DISABLE ENCRYPTION (IF NEEDED)
1. Flash full fastboot rom to make sure everything is clean
2. Boot to stock recovery and wipe /data so it gets cleanly formatted as ext4 (not really needed)
3. Boot and install TWRP (blu_spark) and reformat /data as f2fs
I chose latest blu_spark recovery as I think it's more stable and I don't need recovery decryption for this matter
4. Reboot to recovery
5. Flash custom kernel with f2fs support or keep stock
blu_spark didn't work for me for some reason but Smurfkernel and ElementalX were fine, also STOCK KERNEL SUPPORTS F2FS BY NOW
6. Flash the universal dm-verity and forceencryption remover by zackptg5 found here
Only if you really need it! NOT RECOMMENDED AND NOT NEEDED FOR HAVING F2FS WORK
7. Flash Magisk v18.0
8. Reboot
9. Profit (or not)
Even if hard to believe with the already amazing speeds of the OP6/T, I think I could feel a little improvement in boot time and app opening times.
Update: I wouldn't recommend doing this as of now to anyone. Maybe results with an AOSP based rom are better (please try and report), but using OxygenOS in combination with currently available kernels, the system turns out unstable and is not usable reliably. There are different weird glitches etc. Do this on your own resposibility and please share if you make any progress making OOS and/or AOSP run stable (recovery versions, file patches, kernels, settings, etc). I'm not an Android developer myself.
ENCOUNTERED ISSUES
1. Can't use any unlock method. Deleting gatekeeper and locksetting files through TWRP works but setting a new PIN results in not being able to unlock again. The PIN is entered correctly but still it reports "wrong password". But actually it detects that the PIN is correct since it doesn't trigger a lockout time. Logcat occurences can be found below.
FIXED BY NOT DECRYPTING DATA (?)
2. On first boot there will be some app crashs and lags. They settle after a few minutes and one or two reboots.
ALSO FIXED BY NOT DECRYPTING DATA (?)
3. One time I had to reflash Magisk after the first boot
UNLOCK BUG LOGCAT OCCURENCES - HELP NEEDED!
Here are some logcat lines which I think are related to the unlock bug.
HTML:
E GatekeeperHalDevice: verify
E GatekeeperHalDevice: ret: 0
E GatekeeperHalDevice: resp->status: -24
E GatekeeperHalDevice: verify
E GatekeeperHalDevice: ret: 0
E GatekeeperHalDevice: resp->status: -30
I LockSettingsService: Device doesn't implement AuthSecret HAL
E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gatekeeper.password.key: open failed: ENOENT (No such file or directory)
E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/password.key: open failed: ENOENT (No such file or directory)
E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gatekeeper.pattern.key: open failed: ENOENT (No such file or directory)
E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gatekeeper.gesture.key: open failed: ENOENT (No such file or directory)
E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gesture.key: open failed: ENOENT (No such file or directory)
E keystore: Changing user 0's password while locked, clearing old encryption
E JavaBinder: *** Uncaught remote exception! (Exceptions are not yet supported across processes.)
E JavaBinder: java.lang.RuntimeException: android.os.RemoteException: Non-OK response verifying a credential we just set: -1
E JavaBinder: at android.os.Parcel.writeException(Parcel.java:1779)
E JavaBinder: at android.os.Binder.execTransact(Binder.java:765)
E JavaBinder: Caused by: android.os.RemoteException: Non-OK response verifying a credential we just set: -1
E JavaBinder: at com.android.server.locksettings.LockSettingsService.setUserKeyProtection(LockSettingsService.java:1602)
E JavaBinder: at com.android.server.locksettings.LockSettingsService.setLockCredentialInternal(LockSettingsService.java:1483)
E JavaBinder: at com.android.server.locksettings.LockSettingsService.setLockCredential(LockSettingsService.java:1397)
E JavaBinder: at com.android.internal.widget.ILockSettings$Stub.onTransact(ILockSettings.java:141)
E JavaBinder: at android.os.Binder.execTransact(Binder.java:752)
Nice work, I discovered these very same errors while decrypting myself. I just flashed the dm verity disabler by zackptg after a format. Yeah same exact issues. I am on the fence whether I felt any difference in speed etc. Unfortunately it seems we need encryption for this device to offer any security, unlike previous phones that didn't have a/b partitions
jacksummers said:
Nice work, I discovered these very same errors while decrypting myself. I just flashed the dm verity disabler by zackptg after a format. Yeah same exact issues. I am on the fence whether I felt any difference in speed etc. Unfortunately it seems we need encryption for this device to offer any security, unlike previous phones that didn't have a/b partitions
Click to expand...
Click to collapse
You won't notice and difference in disabling encryption as it's hardware based now instead of software like on the Nexus's and then it was a slight performance increase nothing else.
jacksummers said:
Nice work, I discovered these very same errors while decrypting myself. I just flashed the dm verity disabler by zackptg after a format. Yeah same exact issues. I am on the fence whether I felt any difference in speed etc. Unfortunately it seems we need encryption for this device to offer any security, unlike previous phones that didn't have a/b partitions
Click to expand...
Click to collapse
Yeah well I updated the thread. Without decrypting everything seems running great until now, even with stock kernel which supports f2fs by now. Also, if someone really wants it decrypted, I updated the post with your method, the disabler by zackptg5, which I didnt know of until now (way easier, thanks)
Also thanks @liam_davenport for mentioning the hardware based encryption, didnt know of that as well.
This means: I'm perfectly happy. Encryption in place, f2fs working and no issues yet.
Lartsch said:
Yeah well I updated the thread. Without decrypting everything seems running great until now, even with stock kernel which supports f2fs by now. Also, if someone really wants it decrypted, I updated the post with your method, the disabler by zackptg5, which I didnt knwo of until now.
Click to expand...
Click to collapse
Good to share ideas man, that furthers the development of Android.
nevermind!
So twice now (the first was above, but it's easy, while incredibly annoying, to fix after a reformat, so I edited the post thinking it was a one-time thing) I've rebooted my phone with data as F2FS only to boot directly into recovery. TWRP doesn't ask me to decrypt; I get the error "init_user_0 failed." I have to reformat my SDcard to get out of this error.
I don't know how to get recovery logs without decrypted data. damn TWRP saves them in /data/media/0 which is useless since it's encrypted.
Another issue i encountered which may be related: I've woken my phone up to have my unlock method reset to "swipe" as if the pattern doesn't work anymore. I can reset the pattern no problems. I think the next reboot after this error happens is when you run into the bootloop.
So, users beware: You get some tasty performance improvements when you switch to F2FS, but one day later you may reboot and be ****ed.
Maybe some smarter people can get on board and figure this out. F2FS is definitely a faster file system for flash devices such as our internal sdcard.
EXT4 for now though!
Lartsch said:
Hello together,
as I wanted to see if I get F2FS and decryption running, I want to share my progress and exchange with others.
I got both working but there are a few issues once the system is running, at least if decrypted. When encrypted, everything seems running nice on f2fs.
Here's what I did:
ENABLE F2FS AND DISABLE ENCRYPTION (IF NEEDED)
1. Flash full fastboot rom to make sure everything is clean
2. Boot to stock recovery and wipe /data so it gets cleanly formatted as ext4 (not really needed)
3. Boot and install TWRP (blu_spark) and reformat /data as f2fs
I chose latest blu_spark recovery as I think it's more stable and I don't need recovery decryption for this matter
4. Reboot to recovery
5. Flash custom kernel with f2fs support or keep stock
blu_spark didn't work for me for some reason but Smurfkernel and ElementalX were fine, also STOCK KERNEL SUPPORTS F2FS BY NOW
6. Flash the universal dm-verity and forceencryption remover by zackptg5 found here
Only if you really need it! NOT RECOMMENDED AND NOT NEEDED FOR HAVING F2FS WORK
7. Flash Magisk v18.0
8. Reboot
9. Profit (or not)
Even if hard to believe with the already amazing speeds of the OP6/T, I think I could feel a little improvement in boot time and app opening times.
Update: I wouldn't recommend doing this as of now to anyone. Maybe results with an AOSP based rom are better (please try and report), but using OxygenOS in combination with currently available kernels, the system turns out unstable and is not usable reliably. There are different weird glitches etc. Do this on your own resposibility and please share if you make any progress making OOS and/or AOSP run stable (recovery versions, file patches, kernels, settings, etc). I'm not an Android developer myself.
ENCOUNTERED ISSUES
1. Can't use any unlock method. Deleting gatekeeper and locksetting files through TWRP works but setting a new PIN results in not being able to unlock again. The PIN is entered correctly but still it reports "wrong password". But actually it detects that the PIN is correct since it doesn't trigger a lockout time. Logcat occurences can be found below.
FIXED BY NOT DECRYPTING DATA (?)
2. On first boot there will be some app crashs and lags. They settle after a few minutes and one or two reboots.
ALSO FIXED BY NOT DECRYPTING DATA (?)
3. One time I had to reflash Magisk after the first boot
UNLOCK BUG LOGCAT OCCURENCES - HELP NEEDED!
Here are some logcat lines which I think are related to the unlock bug.
E GatekeeperHalDevice: verifyE GatekeeperHalDevice: ret: 0E GatekeeperHalDevice: resp->status: -24E GatekeeperHalDevice: verifyE GatekeeperHalDevice: ret: 0E GatekeeperHalDevice: resp->status: -30I LockSettingsService: Device doesn't implement AuthSecret HALE LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gatekeeper.password.key: open failed: ENOENT (No such file or directory)E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/password.key: open failed: ENOENT (No such file or directory)E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gatekeeper.pattern.key: open failed: ENOENT (No such file or directory)E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gatekeeper.gesture.key: open failed: ENOENT (No such file or directory)E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gesture.key: open failed: ENOENT (No such file or directory)E keystore: Changing user 0's password while locked, clearing old encryptionE JavaBinder: *** Uncaught remote exception! (Exceptions are not yet supported across processes.)E JavaBinder: java.lang.RuntimeException: android.os.RemoteException: Non-OK response verifying a credential we just set: -1E JavaBinder: at android.os.Parcel.writeException(Parcel.java:1779)E JavaBinder: at android.os.Binder.execTransact(Binder.java:765)E JavaBinder: Caused by: android.os.RemoteException: Non-OK response verifying a credential we just set: -1E JavaBinder: at com.android.server.locksettings.LockSettingsService.setUserKeyProtection(LockSettingsService.java:1602)E JavaBinder: at com.android.server.locksettings.LockSettingsService.setLockCredentialInternal(LockSettingsService.java:1483)E JavaBinder: at com.android.server.locksettings.LockSettingsService.setLockCredential(LockSettingsService.java:1397)E JavaBinder: at com.android.internal.widget.ILockSettings$Stub.onTransact(ILockSettings.java:141)E JavaBinder: at android.os.Binder.execTransact(Binder.java:752)
Click to expand...
Click to collapse
Hi, I have OnePlus 6t, when I flash the system clean the data section, then format it, flash the script from encryption, then the system boots to a new state, but because of the script, when I want to create a password, it is created, but immediately will not be true when you first start the phone or lock the screen. and I can't get over it, have you figured it out?
uhh186 said:
So twice now (the first was above, but it's easy, while incredibly annoying, to fix after a reformat, so I edited the post thinking it was a one-time thing) I've rebooted my phone with data as F2FS only to boot directly into recovery. TWRP doesn't ask me to decrypt; I get the error "init_user_0 failed." I have to reformat my SDcard to get out of this error.
I don't know how to get recovery logs without decrypted data. damn TWRP saves them in /data/media/0 which is useless since it's encrypted.
Another issue i encountered which may be related: I've woken my phone up to have my unlock method reset to "swipe" as if the pattern doesn't work anymore. I can reset the pattern no problems. I think the next reboot after this error happens is when you run into the bootloop.
So, users beware: You get some tasty performance improvements when you switch to F2FS, but one day later you may reboot and be ****ed.
Maybe some smarter people can get on board and figure this out. F2FS is definitely a faster file system for flash devices such as our internal sdcard.
EXT4 for now though!
Click to expand...
Click to collapse
Use adb while booted in twrp to pull recovery.
adb pull /tmp/recovery.log
uhh186 said:
So twice now (the first was above, but it's easy, while incredibly annoying, to fix after a reformat, so I edited the post thinking it was a one-time thing) I've rebooted my phone with data as F2FS only to boot directly into recovery. TWRP doesn't ask me to decrypt; I get the error "init_user_0 failed." I have to reformat my SDcard to get out of this error.
I don't know how to get recovery logs without decrypted data. damn TWRP saves them in /data/media/0 which is useless since it's encrypted.
Another issue i encountered which may be related: I've woken my phone up to have my unlock method reset to "swipe" as if the pattern doesn't work anymore. I can reset the pattern no problems. I think the next reboot after this error happens is when you run into the bootloop.
So, users beware: You get some tasty performance improvements when you switch to F2FS, but one day later you may reboot and be ****ed.
Maybe some smarter people can get on board and figure this out. F2FS is definitely a faster file system for flash devices such as our internal sdcard.
EXT4 for now though!
Click to expand...
Click to collapse
I get init_user0_failed randomly as well wish there was a fix
edit - reflashing ROM seems to get past it
Was looking at https://source.android.com/security/encryption/file-based and came across an idea,
It says it's possible to add exceptions to prevent certain directories from being encrypted.
In this manner, if the rom Dev is able to add exclusion to /data, isn't it possible that the device would work with pin set, on a decrypted op6t?
when i follow these steps OOS wont boot, it just forces back to recovery.
Hi all, I have a Nokia 7 Plus TA-1046 and I received the update of Android 10 but it has forcibly downloaded itself (with automatic update disabled)
In TWRP I:
- disabled force encryption removing fields in /vendor/etc/fstab.qcom
- created/copied a .magisk file in /cache (this one path is when we are in TWRP while, when Android loads, the file (if created) resides in /data/cache, because for us /cache is a link of it) with inside it:
Code:
KEEPVERITY=false
KEEPFORCEENCRYPT=false
- installed Magisk v20.3
These steps worked flawlessy in Android 9 but not for Android 10; after android one logo, it reboots in loop (after a few tries, when it switchs automatically to inactive slot with Android 9, system started up normally)
Do you have any ideas or suggestions (obviously I want to find first a solution before a complete format :angel: ) on how to solve the above problem? Maybe related with the way of encryption in Android 10, different of one in Android 9, as described here and here?
death_jax said:
Hi all, I have a Nokia 7 Plus TA-1046 and I received the update of Android 10 but it has forcibly downloaded itself (with automatic update disabled)
In TWRP I:
- disabled force encryption removing fields in /vendor/etc/fstab.qcom
- created/copied a .magisk file in /cache (this one path is when we are in TWRP while, when Android loads, the file (if created) resides in /data/cache, because for us /cache is a link of it) with inside it:
Code:
KEEPVERITY=false
KEEPFORCEENCRYPT=false
- installed Magisk v20.3
These steps worked flawlessy in Android 9 but not for Android 10; after android one logo, it reboots in loop (after a few tries, when it switchs automatically to inactive slot with Android 9, system started up normally)
Do you have any ideas or suggestions (obviously I want to find first a solution before a complete format ) on how to solve the above problem? Maybe related with the way of encryption in Android 10, different of one in Android 9, as described here and here?
Click to expand...
Click to collapse
Me too
Hallo, I hope someone in this forum can help me with a problem with my SM-T819 TWRP.
I tried to install a CustomRom without making a back-up copy and apparently I removed all details on the tablet.
The installation of TWRP was succesful, however all my recent trials to install a CustomRom failed with the following comments:
Updating partition details….
…done
Full SELinux support is present
MTP enabled
Installing zip file `/sdcard1/lineage-16.0-20181203_161503-Unofficial-gts210velte.zip`
Checking for digest file...
Updater process ended with ERROR: 7
Error installing zip file `/sdcard1/lineage-16.0-20181203_161503-Unofficial-gts210velte.zip`
Updating partition details…
…done
installing zip file `/ sdcard1/lineage-16.0-20181203_161503-Unofficial-gts210velte.zip`
Checking for digest file...
Warning: No file_contexts
Comparing TZ version TZ.BF.3.0.3-00054 to TZ.BF.3.0.3-00077
Comparing TZ version TZ.BF.3.0.3-00064 to TZ.BF.3.0.3-00077
Comparing TZ version TZ.BF.3.0.3-00067 to TZ.BF.3.0.3-00077
Comparing TZ version TZ.BF.3.0.3-00071 to TZ.BF.3.0.3-00077
assert failed: samsung.verify_trustzone ("TZ.BF.3.0.3-00054", "TZ.BF.3.0.3-00044",
"TZ.BF.3.0.3-00067", "TZ.BF.3.0.3-00071") == "1"
Updater process ended with ERROR: 7
Error installing zip file `/sdcard1/lineage-16.0-20181203_161503-Unofficial-gts210velte.zip`
Updating partition details…
… done
I have done this trial with various TWRP and Lineage varieties but in vain and always with the identical error.
The only thing I could do was via TWRP the installation of “SMT819_Deodex_Debloated Custom Rom” (based on Stock-Samsung-Firmware.
I have also tried via Odin (several versions) to apply the original firmware. The installation proceeds without error, the tablet starts,
the progress is shown on the blue screen and every time it is cancelled after 25 % and 32%. Then the tab shuts down and starts again and remains in a continous loop with the splash screen.
Well, what is the reason to install a ... REALLY REALLY OLD version like this?
Try this https://lineageos.wickenberg.nu/gts210velte/ or that https://drive.google.com/drive/folders/1VsHc9-k4LA3-n19dp6Gkvqwf0GZLTRcA depending on what you want to have, LOS 16 or 17.1