Hi,
So I got this problem with my Z1 Compact (D5503) with stock ROM (14.6.A.1.236 - 5.1.1) where I can't encrypt my phone if device is rooted. I've tested this with SuperSU installed and KingRoot. In most cases after going into settings, setting up the code and trying to encrypt the phone restarts and enters bootloop. Sometimes it just restarts and shows the known error message "encryption unsuccessful"
I got the newest XZDualRecovery for Z1C installed (pre-3.0 version, so I presume the bug where I can't mount even the successfully encrypted /data partition is expected?), root is done via KingRoot, then replaced by SuperSU.
Does anyone know what's going on and how to avoid this issue?
Related
Hello,
I'm wondering if there's an official RUU for GPe that would let me restore the phone to factory configuration. I messed up my phone and while it works I observed few issues with it so far: when it first boots up for short time the launcher is accessible before the phone finish loading soft buttons and then lock screen. It's not a big deal but it decreases phone security. My WiFi no longer works.
Here's some background what happened:
I have HTC One (M8) purchased from Google Play. When I unlocked it I tried to do very minimal changes to it (install SuperSU and Xposed, I did not even flash recovery I was able to boot PhillZ Touch recovery using fastboot boot <image>, also it is S-ON as I never needed to change radios etc.) everything worked just fine. A 5.0.1 OTA came and after applying it the phone worked fine but naturally root and Xposed stopped working. I realized that after the 5.0.1 I no longer can boot custom recovery using fastboot boot <image> so I flashed latest TWRP on the recovery partition then from it I installed latest SuperSU, I also called Xposed script that supposed to uninstall it, since I learned that Xposed won't work on Lollipop.
After a reboot the phone got stuck in loading animation. After connecting adb logcat I noticed that the same message was repeating, there was more of the text, but what drew my attention was "DSEC_DMO_Token ERR: Key file does not authorize requested features. - /system/etc/soundimage/srsmodels.lic". Anyway at that point I decided to restore my 4.4.4 backup. Once restored I noticed that the phone no longer prompts me about 5.0.1 OTA and says that I'm running the latest version. I then adb sideloaded official 5.0.1 update and this is the place where I am currently. I tried wiping caches, but that had no effect.
Recently, whenever I use the fastboot command from my PC with my Zenfone 2 (64 gb) I am getting responses that read ”FAILED (remote permission denied)".
As an example, I flashed the new TWRP recovery with fastboot and got these messages:
Sending xxxxx
OKAY
Writing xxxxx
FAILED (remote permission denied
The odd thing is, the command appears to have worked as the new recovery has been flashed as desired. Anyone have an idea what's happening and how to eliminate the supposed error?
I should add that the phone is rooted and bootloader is unlocked.
I just noticed the same "problem". I caused a boot-loop (I believe by trying to get the root companion app for GSAM Battery Monitor installed to /system/priv-app), so went to attempt a fix somehow. My TWRP recovery was gone at first, tried reflashing and got the same message as you. But, likewise it did work.
Also a rooted ZE-551ML, bootloader unlocked and recently upgraded to 2.19.40.22 (maybe it's something in the .20 to .22 update)?
P.S. I'm considering myself lucky, managed to use TWRP to mount /system and then deleted the 'com.*' folder I copied into there. Rebooted fine after that...phew!
having the same issue.. any possible fix ?
stupid_productions said:
I just noticed the same "problem". I caused a boot-loop (I believe by trying to get the root companion app for GSAM Battery Monitor installed to /system/priv-app), so went to attempt a fix somehow. My TWRP recovery was gone at first, tried reflashing and got the same message as you. But, likewise it did work.
Also a rooted ZE-551ML, bootloader unlocked and recently upgraded to 2.19.40.22 (maybe it's something in the .20 to .22 update)?
P.S. I'm considering myself lucky, managed to use TWRP to mount /system and then deleted the 'com.*' folder I copied into there. Rebooted fine after that...phew!
Click to expand...
Click to collapse
I had the same fastboot problem, but now is worse. I did a unthetered recovery and rooted by flashing superuser.zip. Now i can´t go to bootloader or recovery, but i have root access (phone is strangely working normal, i just can´t uptade, acess bootloader and recovery)
Why did you deleted folders in your phone? I think i have some issue like that. Can i solve my problems like you did since i have root acess and can do that with root explorer?
same issue here, any known fix so far?
JulioQc said:
same issue here, any known fix so far?
Click to expand...
Click to collapse
nothing for me, but once my phone is rooted and unlocked i flashed twrp recovery and use only that.
Hi guys,
I am currently stuck in a bit of a loop.
I'm running stock v30c on my D855, rooted using KingRoot and has the latest TWRP bumped.
I tried doing a test from one of the hidden menus, and now my device is stuck on:
"Secure Booting Error! Cause: boot certification verify"
This appears every time the device tried to boot to system, though TWRP works just fine!
Something else that's weird and has been happening since then is, that I cannot mount my phone using TWRP, it gets recognized as "USB Serial Device" (tried on a few computers).
Any suggestions? I'd rather not flash my device if it's not an absolute must.
Thanks.
So... after 3 hours of absolutely 0 response, I gave up and flashed my device with stock firmware.
After that I rooted it using KingRoot again and flashed TWRP using AutoRec.
Then restored my Nandroid backup.
Not the best solution, I did lose some data, at least I can use my phone now.
NEVER EVER touch those stupid hidden menus if you don't absuolutely must! Those might brick you to a level when you're going to have to lose some data!!
Glad I had the backup from a few days ago so it wasn't that bad.
"Error occurred while updating..." Think I have bricked while attempting to downgrade
Please help.
I was attempting to root and SIM unlock the SM-G925T. It was already on Nougat 7.0 (and November 2017 security/patch).
CF Auto Root would not work. Neither did an attempt to manually flash TWRP (although attempting one of those two tripped KNOX).
I thought I'd downgrade to Marshmallow and then re-attempt root/unlock. Downloaded "G925TUVU5EQC2" from gsm-firmware and tried to execute via Odin.
I am left with a permanent blue screen with that "!" reading I need to use Smart Switch's Emergency Recovery. That, btw, does not work either (and neither does re-attempting after reinstalling device drivers from within SS).
Could someone please suggest what I should do? Pressing and holding power/home/vol- keeps taking me back to this blue screen. Unable to get to the recovery or anywhere for that matter.
Ok, so... Despite not seeing any other screen, I went ahead with reflashing the Marshmallow ROM via ODIN. Worked this time and the phone rebooted.
Interestingly, now, my unlock request was approved by the Device Unlock software (didn't need to use other means). However, I am stuck on Marshmallow and the device won't update to Nougat (get the error "phone not registered", despite it being unlocked). Hilarious. But at least the phone is functioning now.
Followed the same ODIN method and flashed the latest 7.0 image (Nov 2017 patch). Thankfully, it retained the unlock. Not sure if it can upgrade (I don't see the "not registered" error) but I won't know till there is a release.
Briefly got an annoying "com.sec.vsimservice stopped working" error - booted into Android recovery, wiped cache and did a factory reset. Working now!
Had already tried rooting this version (using both CF Auto Root and TWRP), but in vain, so not harbouring hopes now. Will get back to it later.
So, long story short, I followed this tutorial: www . htcmania. com/showthread.php?t=1024045 (remove the spaces in w.h and .com) and it didn't go very well.
I flashed TWRP and SuperSU as told, using both download links (TWRP 2.8.7 & SuperSU 2.46), and my phone got stuck in a bootloop at LG bootloader unlocked logo. I recovered my phone by using LG Bridge and after that, when i tried to enter TWRP using the phone keys, it resulted in a factory data reset (no TWRP after recovery, didn't know that). I then followed the exact same steps but using what I thought was the lastest SuperSU archive (SR5-SuperSU-v2.82), flashed the archive and when finished, TWRP asked me to flash it again (so I did), then rebooted, passed LG bootloader unlocked logo, got into LG animation and... Bootloop again, so I recovered again with LG Bridge but I din't attempted to enter TWRP because this time i knew it wouldn't work and I ended it there, reinstalling all apps and configuring my phone as I had it before my unsuccessfull attempt. I continued using my phone as usual but sometimes, when I enter Pokemon Go, it says that it couldn't log in and that my phone's OS is not supported. As I said, the app does this sometimes whenever it wants, so I researched a bit and turns out it doesn't work with rooted android devices (I didn't know that). I knew my root attempt failed so I downloaded and app called Root Checker and checked: Root status-Not rooted; SafetyNet Status-Failed. I don't know what should I do know, last time I rooted my phone was a Sony Xperia XL and it wasn't so tricky.
I asked for advice in the forum and got no answer, so here I am, hoping for a solution. What I want is to have a permanent custom recovery, a rooted device and to have SafetyNet status passed. Any ideas, hints or whatever? Please, help