Related
nexus 5
android 4.4.2
bootloader version: HHZ11K
Secure boot: enabled
unlocked
rooted
encrypted (i have set a pattern to unlock)
TWRP 2.6.3.4
Xposed module (not sure which version or if it is relevant at all)
xprivacy (not sure which version or if it is relevant at all)
suddenly, while i was surfing twitter, the phone restarted and attempted to install an update (not sure if it was 4.4.3 or Lollipop).
The phone went into bootloop.
My concern here , for now, is not how to fix it. I just need to retrieve my data (contacts, pics, calendar,...).
I held the power button and volume down to load into bootloader. from there i started TWRP. I was greeted with "please enter your password". I entered my pattern following the below arrangement
1 2 3
4 5 6
7 8 9
after several attempts which always ended with "Password failed. Please try again" i hit "cancel". This took me to the main TWRP screen.
I was worried about my data so i tried to copy everything to my pc through "adb pull sdcard/ C:\test" through terminal but i only got two folders namely "sys" and "tmp" but none of my personal data
In TWRP i touched "mount" to find the following..
"Select Partition to Mount:"
[ ] System
[ ] Cache
[ ] Persist
[ ] firmware
[ ] USB-OTG
below them there is a line that says "Storage: Internal Storage (0 MB)"
below that it says "Decrypt Data". If i touch it, it asks to enter my password. Again, i enter my password and it says password failed.
The log has this:
Updating Partition details...
E:Unable to mount ' /cache'
E:Unable to mount ' /persist'
E:Unable to mount storage
E:Unable to mount ' /cache'
E:Unable to mount ' /cache'
E:Failed to decrypt data.
I think that i need to update TWRP to 2.8.2.0 at least in order to decrypt my data as previous versions don't support decryption and/or pattern passwords. Am i right?
if so, how can i update TWRP to the latest version ?
I tried flashing 2.8.4.0 through fastboot with no luck. I have tried the following during the flashing process:
1) flashed it and then tried starting TWRP immediately.
2) flashed it and then restarted bootloader and then tried starting TWRP
3) flashed it and then started system, which took me into bootloop, shutdown phone
and restart into bootloader then tried starting TWRP.
No matter what i do it always goes back to 2.6.3.4 :crying:
I tried to update it from within TWRP. I pushed TWRP 2.8.4.0 which was in zip format (jjd-openrecovery-twrp-2.8.4.0-hammerhead.zip which i took from this thread ) to the main directory "/". Then inside TWRP i went to install, choose the zip file, swiped right to confirm flash to only get the following:
at the top it says "Zip install complete"
then in like a feedback window this is written:
E : Mount : unable to find partition for patch '/jj
error flashing zip 'jjd-openrecovery-twrp-2.8.
updating partition details...
E:Unable to mount ' /cache'
E:Unable to mount ' /persist'
E:Unable to mount storage
finally at the bottom it says Failed (in red)
no need to say that it is still stuck on 2.6.3.4
Am i heading in the right direction ? if yes how can i update TWRP?
If not, Is there any other way to retrieve my data ?
Is it possible to fix this thing with out a wipe and keep my data intact?
Help plz
have you tried flashing only the cache partition through fastboot?
Thanks for your reply
I downloaded the factory image for nexus 5 from "developers dot google dot com/android/nexus/images#hammerhead" (version 4.4.2 (KOT49H) )
I kept extracting the zip file until I arrived at cache.img
copied it to the folder fastboot.exe is located in
run the command
Code:
fastboot flash cache cache.img
through terminal while in fastboot mode
i got the following:
erasing 'cache'...
OKAY [ 0.125s]
sending 'cache' (13348 KB)...
OKAY [ 0.671s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 0.983s
I started the phone, it passed by the bootloop but then i got a message that says:
Unfortunately, google search has stopped
Unfortunately, the process com.google.process.gapps has stopped
Unfortunately, Google play has stopped
and couple of other similar messages
then i'm greeted with android setup screen (as if I'm running the phone for the first time; choosing language, time ...etc
while I'm in the middle of the setup process, the phone restarts. and it keeps happening again and again
Is there anything else I can do ?
crobh said:
Thanks for your reply
I downloaded the factory image for nexus 5 from "developers dot google dot com/android/nexus/images#hammerhead" (version 4.4.2 (KOT49H) )
I kept extracting the zip file until I arrived at cache.img
copied it to the folder fastboot.exe is located in
run the command
Code:
fastboot flash cache cache.img
through terminal while in fastboot mode
i got the following:
erasing 'cache'...
OKAY [ 0.125s]
sending 'cache' (13348 KB)...
OKAY [ 0.671s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 0.983s
I started the phone, it passed by the bootloop but then i got a message that says:
Unfortunately, google search has stopped
Unfortunately, the process com.google.process.gapps has stopped
Unfortunately, Google play has stopped
and couple of other similar messages
then i'm greeted with android setup screen (as if I'm running the phone for the first time; choosing language, time ...etc
while I'm in the middle of the setup process, the phone restarts. and it keeps happening again and again
Is there anything else I can do ?
Click to expand...
Click to collapse
That means it's borked. You have to RMA it with Google or send it to LG repair.
BirchBarlow said:
That means it's borked. You have to RMA it with Google or send it to LG repair.
Click to expand...
Click to collapse
I have bought it from google directly but I live overseas.
Tried the local LG maintenance center, they guy there didn't seem knowledgeable on the issue. He said he can try formating it and it might work again but has no idea of recovering the pics and other personal data.
I'm starting to lose hope :crying:
new attempt
I tried wiping cache from twrp and then starting the system. this happen:
Google logo for few minutes
then the four circles merging into white circle animation
then three message pops up,one by one, saying
"Android us upgrading" at the top in blue (this stays in all three messages)
and below it, it says
starting apps
upgrading contacts database
finishing boot
and then it returns to the four circles and then the messages again and again and again
Try flashing just the system.img.
Wakamatsu said:
Try flashing just the system.img.
Click to expand...
Click to collapse
So i extracted System.img from 4.4.2 (KOT49H) and then through terminal while in fastboot i wrote
Code:
fastboot flash system system.img
and the result was..
erasing 'system'...
OKAY [ 0.140s]
sending 'system' (702500 KB)...
OKAY [ 24.866s]
writing 'system'...
FAILED (remote: flash write failure)
finished. total time: 25.178s
What could be the reason for this ?
Sounds like yet another corrupted emmc. The usual test for this is to try locking the bootloader. If nothing happens and it reverts to unlocked it's dead. You could try the lg service but I have no idea if they would accept a warranty /rma
Sent from my Nexus 5 using XDA Free mobile app
Hi.
I'm experiencing a weird problem with Moto G3, that is osprey XT1541 when trying to change encryption password.
Did tried several different combinations of ROM or kernel, searched with several engines and through this forum, but got almost nothing.
Platform is CM 12.1, because I couldn't successfully encrypt with CM13; "...Trebushet has stopped...". ADB is run with root.
Device can be encrypted inplace with GUI if PIN/password is defined; also inplace in ADB CLI
"vdc cryptfs enablecrypto inplace pin|password pin_or_password"
Different lock code && encryption password can be set only with 5.1.1 build of CM if 1st PIN or password is defined in GUI (Settings>Lock screen) then in ADB CLI
"vdc cryptfs enablecrypto inplace password password"
But, encryption password can be changed only with GUI (Settings>Lock screen), after what there is no difference between lock code and encryption password.
ADB CLI
"vdc cryptfs changepw password password"
respond with "200 0 1" error and GUI tools give display error with similar meaning.
Also, ADB CLI
"vdc cryptfs verifypw password"
respond with "200 0 0", but, after entering encryption password in bootstrap, there is infinite bootloop.
Does anybody have idea why different lock code and encryption password can't be set on this device, apart from scenario described above?
Also, why encryption is unsuccessful with CM13?
I have CM13 and encryption worked fine. Can you backup, completely wipe your phone and flash a clean version of CM on your device? Maybe that'll help.
xDantehh said:
I have CM13 and encryption worked fine. Can you backup, completely wipe your phone and flash a clean version of CM on your device? Maybe that'll help.
Click to expand...
Click to collapse
Already tried clean install of several CM13 builds, without success. Either bootloop or "...Trebushet has stopped...".
How did u do it; with what build?
Also, my primary problem isn't encrypting, cause that can be done without problem with CM12.1, but encryption pwd change with success.
pseudorng said:
Already tried clean install of several CM13 builds, without success. Either bootloop or "...Trebushet has stopped...".
How did u do it; with what build?
Also, my primary problem isn't encrypting, cause that can be done without problem with CM12.1, but encryption pwd change with success.
Click to expand...
Click to collapse
I downloaded the latest CM nightly from their repo (https://download.cyanogenmod.org/?device=osprey) then downloaded Gapps and Firekernel, flashed them and works fine with encryption.
Tried with cm-13.0-20160903-NIGHTLY-osprey and FireKernel-osprey-v5.6 without success. Got "Unfortunately, Trebushet has stopped." and "Unfortunately, Music has stopped."
Also tried with XOSP-5.4-OFFICIAL-20160512-osprey which resulted in bootloop.
I'm quite puzzled with both encryption process problems && failure of encryption pwd change.
TL;DR I need an answer to one of the four questions at the bottom.
Preferably #1 or #3.
---------------------------------------------------------------
I have a Oneplus 3T running the latest Resurrectionremix (7.1.1) and TWRP recovery (3.0.4-1).
I use a pattern lock and device encryption, but I had separate passwords for the pattern and the encryption.
I tried to change my encryption password back to my pattern combo using 'vdc cryptfs changepw password' and entering numbers that correspond to the dots of the pattern. (E.g. in a 3x3, the dots are labeled 1-9)
Let's say the password I entered was '123456789'
I didn't realize that I needed to enter the HEX values in this command, (313233343536373839) so I just entered the ASCII values (123456789). The password I entered was all numbers so it corresponded to HEX values without giving an error.
Now, when I restart my phone, or boot into TWRP, I cannot enter the password I set. I cannot access adb or a terminal when booting android, and I cannot use 'vdc cryptfs' through TWRP. (I can use adb and terminal through TWRP)
The obvious solution is to convert the HEX values I entered to ASCII values and type them in, but I have two problems:
I use an odd number of dots for my pattern lock, and I entered an odd number of numbers for the HEX password. I don't know how that would break down into ASCII, because you need 2 HEX digits per ASCII character.
No matter how I convert the HEX to ASCII (either by prepending or appending a 0) there are characters that cannot be typed on a keyboard, and cannot be pasted into an adb shell.
---------------------------------------------------------------
I can think of a number of possible solutions to this problem:
How can I input my encryption password in hexadecimal rather than ASCII?
I think this would only be possible through TWRP/adb. It only needs to be temporary; I'll move my data out and format everything.
How can I backup the encrypted '/data' partition to my PC?
This way, I can freely format my phone while I try to decrypt the encrypted blob. Additionally, are there tools to help me decrypt the partition on a PC?
How can I use 'vdc cryptfs' in TWRP?
Right now, the problem is that it cannot find 'cryptd'. If I can get this to work, I can reset the password to something typeable.
How can I use 'vdc cryptfs' in Android without entering a password on boot?
As I said, my phone doesn't turn on adb before I enter the password, and I can't access Terminal or anything... or is there a way?
Or can I solve this any other way, without losing my data?
Alternatively, is there a way to inject hex into android's clipboard, and paste it during boot or in TWRP?
Decrypt Android Pie File-Based Encryption? No success with "twrp decrypt 123"
Hi,
during update of my Xiaomi A2 to Android Pie I corrupted my /data. The phone gets Android One, so my problem should be quite widespread. Phone is up and running again but had to factory reset at the end. I tried to recover some files but I wasn't able to decrypt /data within TWRP with
Code:
twrp decrypt <NumberSequence-from Lock Patern>
The phone was protected with a pattern, that was correctly converted to the number sequence described in the TWRP FAQ. From what I saw in the TWRP source this command is for Android Disk Encryption only. Currently TWRP can't open my encryption of the fresh install:
Code:
I:File Based Encryption is present
begin failed, code -62Upgrading key: /data/unencrypted/keyupgrade_key failed, code -38e4crypt_initialize_global_de returned fail
begin failed, code -62Upgrading key: /data/unencrypted/keyupgrade_key failed, code -38e4crypt_initialize_global_de returned fail
begin failed, code -62Upgrading key: /data/unencrypted/keyupgrade_key failed, code -38e4crypt_initialize_global_de returned fail
I've got a backup of the encrypted partition so I can try anytime again but I didn't find any good clue. File encryption seems to have changed with Pie but the keystore looks accessible:
Code:
/data/unencrypted/ref
/data/unencrypted/key/version
/data/unencrypted/key/keymaster_key_blob
/data/unencrypted/key/encrypted_key
/data/unencrypted/key/stretching
/data/unencrypted/key/secdiscardable
/data/unencrypted/mode
I've had a quick lock into the TWRP source but found no easy clue how to fix the error above.
Question: Does anybody know a easy solution? Before I waste hours reinventing the wheel?
I guess either your best bet is to reflash images from the fastboot. Twrp natively support format data. By "entering yes". This removed all sort of encryption on Oreo. But I have read somewhere things have changed in pie.
ljakob said:
Hi,
during update of my Xiaomi A2 to Android Pie I corrupted my /data. The phone gets Android One, so my problem should be quite widespread. Phone is up and running again but had to factory reset at the end. I tried to recover some files but I wasn't able to decrypt /data within TWRP with
Code:
twrp decrypt <NumberSequence-from Lock Patern>
The phone was protected with a pattern, that was correctly converted to the number sequence described in the TWRP FAQ. From what I saw in the TWRP source this command is for Android Disk Encryption only. Currently TWRP can't open my encryption of the fresh install:
Code:
I:File Based Encryption is present
begin failed, code -62Upgrading key: /data/unencrypted/keyupgrade_key failed, code -38e4crypt_initialize_global_de returned fail
begin failed, code -62Upgrading key: /data/unencrypted/keyupgrade_key failed, code -38e4crypt_initialize_global_de returned fail
begin failed, code -62Upgrading key: /data/unencrypted/keyupgrade_key failed, code -38e4crypt_initialize_global_de returned fail
I've got a backup of the encrypted partition so I can try anytime again but I didn't find any good clue. File encryption seems to have changed with Pie but the keystore looks accessible:
Code:
/data/unencrypted/ref
/data/unencrypted/key/version
/data/unencrypted/key/keymaster_key_blob
/data/unencrypted/key/encrypted_key
/data/unencrypted/key/stretching
/data/unencrypted/key/secdiscardable
/data/unencrypted/mode
I've had a quick lock into the TWRP source but found no easy clue how to fix the error above.
Question: Does anybody know a easy solution? Before I waste hours reinventing the wheel?
Click to expand...
Click to collapse
Hey man... i have the same issue... well not issue... but i agree with you... for some reason in pie it is not decrypting... even without any pattern or pin ( i mean factory wipe still is encrypted)
I heard from a XDA member that the reason is that TWRP is still not based in Pie and therefore decryption fails (which doesn't explain much).
data is mounted
/dev/block/mmcblk0p69 on /data type ext4 (rw,seclabel,relatime,resgid=1065,data=ordered)
/dev/block/mmcblk0p69 on /sdcard type ext4 (rw,seclabel,relatime,resgid=1065,data=ordered)
but totally encrypted
/data/property # ls
7ie0ntZL7gIdCVBtZIRikhzXYZFI1twW
/sdcard # ls
3oZYlgteNMPvlbx7i7N5SC HHPy3vFJBv09B20I2Im2iKrJvdBiPBfc ...
Since it was factory reseted, i thought i could try something like
twrp decrypt ' '
But, no success... tried to put a password and decrypt with the password, but dmesg returns me:
<4>[ 139.534400] SELinux: security_context_str_to_sid(ubject_r:firmware_file:s0) failed for (dev mmcblk0p58, type vfat) errno=-22
<6>[ 139.547889] binder: tried to use weak ref as strong ref
<6>[ 139.547909] binder: 559:667 Release 1 refcount change on invalid ref 0 ret -22
lrwxrwxrwx 1 root root 21 Jan 12 1970 modem_a -> /dev/block/mmcblk0p58
Do you have the source page where you checked the twrp decrypt command?
After trying to root this smartphone, it ended up corrupting some system files. I reinstalled stock rom and this message showed up: TEE key not write, Google key not write:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Using Google i ended up at this thread here in xda:
https://forum.xda-developers.com/general/help/ulefone-power-3s-problem-t3794521
But this method about using adb platform tools didn't worked for me. There's no Factory Mode even when listing all the packages installed. Is there any other recommendation of what i should do? This is actually very annoying? Thanks.
Listed packages:
package:com.android.fmradio
package:com.mediatek.gba
package:com.mediatek.ims
package:com.android.cts.priv.ctsshim
package:com.google.android.youtube
package:com.android.internal.display.cutout.emulation.corner
package:com.google.android.ext.services
package:com.android.internal.display.cutout.emulation.double
package:com.android.providers.telephony
package:com.google.android.googlequicksearchbox
package:com.android.providers.calendar
package:com.android.providers.media
package:com.google.android.onetimeinitializer
package:com.google.android.ext.shared
package:com.mediatek.location.lppe.main
package:com.android.wallpapercropper
package:com.teslacoilsw.launcher
package:com.android.protips
package:com.android.documentsui
package:android.auto_generated_rro__
package:com.android.externalstorage
package:com.mediatek.ygps
package:com.mediatek.simprocessor
package:com.android.htmlviewer
package:com.mediatek.mms.appservice
package:com.android.companiondevicemanager
package:com.android.mms.service
package:com.android.providers.downloads
package:com.google.android.apps.messaging
package:com.adups.fota
package:com.mediatek.engineermode
package:com.android.partnerbrowsercustomizations.example
package:com.qiku.face.unlock
package:com.mediatek.omacp
package:com.google.android.configupdater
package:com.android.soundrecorder
package:com.mediatek.wfo.impl
package:com.android.defcontainer
package:com.android.providers.downloads.ui
package:com.android.vending
package:com.android.pacprocessor
package:com.android.simappdialog
package:com.android.internal.display.cutout.emulation.tall
package:com.android.certinstaller
package:com.android.carrierconfig
package:com.google.android.marvin.talkback
package:com.adups.privacypolicy
package:android
package:com.android.contacts
package:com.android.egg
package:com.android.mtp
package:com.android.nfc
package:com.android.stk
package:com.android.launcher3
package:com.android.backupconfirm
package:com.sprd.screencapture
package:com.android.statementservice
package:com.google.android.gm
package:com.google.android.apps.tachyon
package:com.mediatek.mdmlsample
package:com.android.settings.intelligence
package:com.mediatek.providers.drm
package:com.android.systemui.theme.dark
package:com.google.android.setupwizard
package:com.android.providers.settings
package:com.android.sharedstoragebackup
package:com.mediatek.batterywarning
package:com.google.android.music
package:com.android.printspooler
package:com.android.dreams.basic
package:com.android.se
package:com.android.inputdevices
package:com.google.android.apps.wellbeing
package:com.android.bips
package:com.mediatek
package:com.google.android.apps.nbu.files
package:com.example
package:com.mediatek.duraspeed
package:com.android.musicfx
package:com.google.android.apps.docs
package:com.google.android.apps.maps
package:com.google.android.webview
package:com.android.server.telecom
package:com.google.android.syncadapters.contacts
package:com.android.keychain
package:com.android.camera
package:com.google.android.calculator
package:com.android.chrome
package:com.android.dialer
package:com.google.android.packageinstaller
package:com.google.android.gms
package:com.google.android.gsf
package:com.google.android.ims
package:com.google.android.tts
package:com.google.android.gmsintegration
package:com.android.calllogbackup
package:com.google.android.partnersetup
package:com.google.android.videos
package:com.android.proxyhandler
package:com.google.android.feedback
package:com.google.android.printservice.recommendation
package:com.google.android.apps.photos
package:com.google.android.calendar
package:com.android.managedprovisioning
package:com.mediatek.calendarimporter
package:com.mediatek.thermalmanager
package:com.mediatek.callrecorder
package:com.android.providers.partnerbookmarks
package:com.android.smspush
package:com.mtk.telephony
package:com.android.wallpaper.livepicker
package:com.google.android.gms.policy_sidecar_aps
package:com.google.android.backuptransport
package:com.android.storagemanager
package:com.android.bookmarkprovider
package:com.android.settings
package:com.themonsterit.EngineerStarter
package:com.fineos.superscreenshot
package:com.mediatek.mdmconfig
package:com.mediatek.lbs.em2.ui
package:com.android.cts.ctsshim
package:com.android.vpndialogs
package:com.android.phone
package:com.android.shell
package:com.android.wallpaperbackup
package:com.android.providers.blockednumber
package:com.android.providers.userdictionary
package:com.android.emergency
package:com.android.location.fused
package:com.android.deskclock
package:com.android.systemui
package:com.android.bluetoothmidiservice
package:com.cryptotel.chamelephon
package:com.android.traceur
package:com.mediatek.mtklogger
package:com.mediatek.sensorhub.ui
package:com.android.bluetooth
package:com.android.wallpaperpicker
package:com.android.providers.contacts
package:com.android.captiveportallogin
package:com.google.android.inputmethod.latin
package:com.google.android.apps.restore
I have same issue on Cubot X19S. No factory mode, but still overlay. Did yo find a solution?
bululu said:
I have same issue on Cubot X19S. No factory mode, but still overlay. Did yo find a solution?
Click to expand...
Click to collapse
hey guys sorry there's probably a solution If you try one or some of the methods for other phones with trial and error
I dont let it bother me much though youll get used to ignoring it
I have the same issue!
The issue appear after formatting and flashing a non backuped ROM, because the TEE (Trusted Execution Environment) key it's not written or it's not the phone's original.
The red sentence (TEE key not write Google key not write) it is positioned in the system app: com.android.systemui
However, I read online that "maybe" could be solved with SN Write Tool (google it), I have not yet been able to try it for various reasons.
If by chance I solve it, I will tell you!
But for now nothing.
tiagao_extremo said:
After trying to root this smartphone, it ended up corrupting some system files. I reinstalled stock rom and this message showed up: TEE key not write, Google key not write:
Using Google i ended up at this thread here in xda:
https://forum.xda-developers.com/general/help/ulefone-power-3s-problem-t3794521
But this method about using adb platform tools didn't worked for me. There's no Factory Mode even when listing all the packages installed. Is there any other recommendation of what i should do? This is actually very annoying? Thanks.
Listed packages:
ecc...
Click to expand...
Click to collapse
I solved the "TEE key not write, Google key not write" issue!
Now I tell you how to solve the issue 100%:
IMPORTANT FOLLOW STEP BY STEP IF YOU DON'T WANT TO HAVE PROBLEMS! ONLY FOR DOOGEE N20!
Make a backup of System and Userdata partition first for precaution!
Requirements:
- The phone must be rooted
- TWRP Recovery (Optional)
- Root File Manager (e.g. Es File Manager)
- A PC with adb installed
- The modded APK that you will find in the attachments
Method:
- Enter the root file manager and navigate to \system\priv-app\MtkSystemUI
- Rename the apk that you will find inside the folder from "MtkSystemUI.apk" to "MtkSystemUI.apk.bck"
- Copy the modded APK and insert it in the \system\priv-app\MtkSystemUI folder
- Enter the PC and run this adb command
(Tips: when entering adb shell right click to paste, "ctrl+v" not work in adb shell. When you run the "su" command you will be asked to provide root access to the adb shell on your phone)
adb shell
su
pkill -TERM -f com.android.systemui; am startservice --user 0 -n com.android.systemui/.SystemUIService
IF you restart the phone and "TEE key not write......" reappears, follow these steps:
- IMPORTANT! Copy the modified apk to the SD card in case of encrypted userdata!
- Restart the phone in recovery mode
- Entered TWRP recovery tap on Advanced and tap on File Manager
- Once in the file manager navigate to \external_sd and look for the folder where you put it; Eg \external_sd\Download (Only if you have inserted the modified apk in the SD card).
- Tap on the modified apk and then tap on "Copy File"
- Now navigate to \system\system\priv-app\MtkSystemUI and tap on the button at the bottom right.
- Restart normally
- Enjoy!:good:
IosifMihaescu said:
I solved the "TEE key not write, Google key not write" issue!
Now I tell you how to solve the issue 100%:
IMPORTANT FOLLOW STEP BY STEP IF YOU DO NOT WANT TO HAVE PROBLEMS! ONLY FOR DOOGEE N20!
Make a backup of System and Userdata partition first for precaution!
Requirements:
- The phone must be rooted
- TWRP Recovery
- Root File Manager (e.g. Es File Manager)
- A PC with adb installed
- The modded APK that you will find in the attachments
Method:
- Enter the root file manager and navigate to \system\priv-app\MtkSystemUI
- Rename the apk that you will find inside the folder from "MtkSystemUI.apk" to "MtkSystemUI.apk.bck"
- Copy the modded APK and insert it in the \system\priv-app\MtkSystemUI folder
- Enter the PC and run this adb command
(Tips: when entering adb shell right click to paste, "ctrl+v" not work in adb shell. When you run the "su" command you will be asked to provide root access to the adb shell on your phone)
adb shell
su
pkill -TERM -f com.android.systemui; am startservice --user 0 -n com.android.systemui/.SystemUIService
- Now you will notice that the "TEE key not write......" is gone, but it is not finished yet! Because if now you will try to restart the phone normally the "TEE key not write......" will reappear!
- IMPORTANT! Copy the modified apk to the SD card in case of encrypted userdata!
- Restart the phone in recovery mode
- Entered TWRP recovery tap on Advanced and tap on File Manager
- Once in the file manager navigate to \external_sd and look for the folder where you put it; Eg \external_sd\Download (Only if you have inserted the modified apk in the SD card).
- Tap on the modified apk and then tap on "Copy File"
- Now navigate to \system\system\priv-app\MtkSystemUI and tap on the button at the bottom right.
- Restart normally
- Enjoy!:good:
Click to expand...
Click to collapse
Thanks, buddy! This message it's finally gone after two months. You helped me more than Doogee's support. I followed your steps after the adb message and it worked. But i could not enter into recovery to move the apk because it says there's encrypted data. Is it really necessary? Because i rebooted the smartphone and the message it's gone. Thanks a lot for your help!
tiagao_extremo said:
Thanks, buddy! This message it's finally gone after two months. You helped me more than Doogee's support. I followed your steps after the adb message and it worked. But i could not enter into recovery to move the apk because it says there's encrypted data. Is it really necessary? Because i rebooted the smartphone and the message it's gone. Thanks a lot for your help!
Click to expand...
Click to collapse
Let's say I tried to solve this problem because I had it too :laugh:
However in TWRP recovery if it tells you that the data is encrypted just tap on cancel, the userdata will remain encrypted but the other partitions es: \system will be uncrypted!
However it's not necessary to put the apk in the system folder with TWRP if the "TEE key......" not reappear after reboot!
IosifMihaescu said:
Let's say I tried to solve this problem because I had it too :laugh:
However in TWRP recovery if it tells you that the data is encrypted just tap on cancel, the userdata will remain encrypted but the other partitions es: \system will be uncrypted!
Click to expand...
Click to collapse
I did that, and the internal memory it's encrypted. After that i used a pen drive through the usb otg, but there was a error message when i tried to copy the file to the system partition. Do you want me to share a photo of the error message?
Since you know a lot about this device, do you know if it's possible to set the selinux policy to permissive definitely? I need to set it everytime i reboot by using the terminal command.
tiagao_extremo said:
I did that, and the internal memory it's encrypted. After that i used a pen drive through the usb otg, but there was a error message when i tried to copy the file to the system partition. Do you want me to share a photo of the error message?
Since you know a lot about this device, do you know if it's possible to set the selinux policy to permissive definitely? I need to set it everytime i reboot by using the terminal command.
Click to expand...
Click to collapse
Ok
tiagao_extremo said:
I did that, and the internal memory it's encrypted. After that i used a pen drive through the usb otg, but there was a error message when i tried to copy the file to the system partition. Do you want me to share a photo of the error message?
Since you know a lot about this device, do you know if it's possible to set the selinux policy to permissive definitely? I need to set it everytime i reboot by using the terminal command.
Click to expand...
Click to collapse
Install this app: https://drive.google.com/file/d/16MvDOlGNZ3v3yNMoeYyAGGE3WjcruHQC/view?usp=drivesdk
This app sets selinux to permissive automatically at boot.
IosifMihaescu said:
Install this app: https://drive.google.com/file/d/16MvDOlGNZ3v3yNMoeYyAGGE3WjcruHQC/view?usp=drivesdk
This app set's selinux to permissive automatically at boot.
Click to expand...
Click to collapse
Thank you again, my friend! This one it's working perfectly!
tiagao_extremo said:
Thank you again, my friend! This one it's working perfectly!
Click to expand...
Click to collapse
You're welcome!
IosifMihaescu said:
I solved the "TEE key not write, Google key not write" issue!
Now I tell you how to solve the issue 100%:
IMPORTANT FOLLOW STEP BY STEP IF YOU DON'T WANT TO HAVE PROBLEMS! ONLY FOR DOOGEE N20!
Make a backup of System and Userdata partition first for precaution!
Requirements:
- The phone must be rooted
- TWRP Recovery (Optional)
- Root File Manager (e.g. Es File Manager)
- A PC with adb installed
- The modded APK that you will find in the attachments
Method:
- Enter the root file manager and navigate to \system\priv-app\MtkSystemUI
- Rename the apk that you will find inside the folder from "MtkSystemUI.apk" to "MtkSystemUI.apk.bck"
- Copy the modded APK and insert it in the \system\priv-app\MtkSystemUI folder
- Enter the PC and run this adb command
(Tips: when entering adb shell right click to paste, "ctrl+v" not work in adb shell. When you run the "su" command you will be asked to provide root access to the adb shell on your phone)
adb shell
su
pkill -TERM -f com.android.systemui; am startservice --user 0 -n com.android.systemui/.SystemUIService
IF you restart the phone and "TEE key not write......" reappears, follow these steps:
- IMPORTANT! Copy the modified apk to the SD card in case of encrypted userdata!
- Restart the phone in recovery mode
- Entered TWRP recovery tap on Advanced and tap on File Manager
- Once in the file manager navigate to \external_sd and look for the folder where you put it; Eg \external_sd\Download (Only if you have inserted the modified apk in the SD card).
- Tap on the modified apk and then tap on "Copy File"
- Now navigate to \system\system\priv-app\MtkSystemUI and tap on the button at the bottom right.
- Restart normally
- Enjoy!:good:
Click to expand...
Click to collapse
Hello sir. I have a blackview max 1 with this red message. I assume I cannot use the same systemui apk... I have rooted it and need to get rid from this message. Could you help? I replaced the apk and the system got the navbar removed, the message was gone, but no navigation buttons and no qs tile notification pulldown panel either.
Any solution? Thanks
Morphine1 said:
Hello sir. I have a blackview max 1 with this red message. I assume I cannot use the same systemui apk... I have rooted it and need to get rid from this message. Could you help? I replaced the apk and the system got the navbar removed, the message was gone, but no navigation buttons and no qs tile notification pulldown panel either.
Any solution? Thanks
Click to expand...
Click to collapse
Yes, the SystemUI mod apk given in this thread is only for Doogee N20.
However, If you send me your phone's original SystemUI apk, I can try to mod it.
Just send me your Blackview Max 1 SystemUI.
IosifMihaescu said:
Yes, the SystemUI mod apk given in this thread is only for Doogee N20.
However, If you send me your phone's original SystemUI apk, I can try to mod it.
Just send me your Blackview Max 1 SystemUI.
Click to expand...
Click to collapse
Thank you so much. I'm uploading it right now. Attached file
I saw about using SN Write Tool , Here and Here
but to be honest that would be a bit of a headache.
Hopefully I can get rid of this text by just replacing your modded systemui for the Blackview Max 1.
Morphine1 said:
Thank you so much. I'm uploading it right now. Attached file
I saw about using SN Write Tool , Here and Here
but to be honest that would be a bit of a headache.
Hopefully I can get rid of this text by just replacing your modded systemui for the Blackview Max 1.
Click to expand...
Click to collapse
Can you try to reupload it with https://wetransfer.com/upload
Because when I try to download it from the attached files, it gives me an Error 404.
IosifMihaescu said:
Can you try to reupload it with https://wetransfer.com/upload
Because when I try to download it from the attached files, it gives me an Error 404.
Click to expand...
Click to collapse
Done: https://wetransfer.com/downloads/e1...d6d1b7704d03dfa3ff07da7820200714024051/503f37
Morphine1 said:
Done: https://wetransfer.com/downloads/e1...d6d1b7704d03dfa3ff07da7820200714024051/503f37
Click to expand...
Click to collapse
Can you give me a screenshot of the message?
IosifMihaescu said:
Can you give me a screenshot of the message?
Click to expand...
Click to collapse
Done, attached
Here it is:
https://we.tl/t-PA2IgNyqD6