so i was trying to make root with magisk boot patch and a unusual error occured basically it gets stucked on start with a black screen with some codes (similar to the bad key error)
Related
Hi Guys,
I work for a company that's in the process of rolling out about 300 HTC Touch Pro2's. Unfortunately a lot of people are experiencing an annoying black screen error message. The message reads -
"The Device is unable to boot because either you have turned off the device incorrectly or tried to install and application from untrusted source. Press Volume Up to reset your device or press any other button to cancel. This operation will delete all your personal data and restore the device to it's factory default settings."
Annoyingly some of our users are hitting the volume up button and wiping the device which then has to be sent back to us to be reconfigured!
Does anyone know either what causes this message, and / or how to stop it from appearing?
Thanks,
Chris
sounds like software you're installing is corrupting some portion of windows.
The only thing we're doing at the moment is enrolling them to Microsoft MDM and connecting them up to Active Sync.
We are also making a few registry changes to add our customisations such as network connections ect. Could this be causing the issue?
What's odd though is if you then reboot the PDA without hitting Volume up button all is well and you may not see the message again.
what is in the startup folder?
In the startup dir we've got five files -
BTTrayCE
HTCStartup
MFdll
PKG
poutlook
hmm. Well i don't know. what is mfdll.
Folks,
I had encrypted my Samsung Note 3 Neo and wanted to decrypt it. Upon pressing the decrypt button, a green Android logo showed up with black background with no progress bar (no words either). Then it just hung there until it reset by itself.
After the reset, it is now stuck with error message Decrypt error and only have an option to reset the device and once I click reset, it goes into recovery mode.
Please help.
The message "Android is upgrading..." always show up every time I reboot the device.
This happens to me too but it's very strange because it seems a pattern lock I had entered persists across factory resets. So now I have to enter both my old pattern and then my new PIN to unlock my phone when I boot up.
The pattern lock comes up after the "android is upgrading" box which also flashes "starting apps" then "finishing boot" and this is after the boot animation. After I enter my pattern, it goes to boot animation again, then loads Oxygen OS 3.2.1. The reason I find this strange is because after the factory reset, I used a pin number at the setup instead of a pattern to lock the phone.
Why is my old pattern still there? I don't like the delay caused by android is upgrading and repeated boot animation.
As a note, I originally used adb sideload to upgrade from 3.1.3 to 3.2.1..
I think I figured it out. First I tried this method: http://www.androidexplained.com/oneplus-3-fix-twrp-restore-unlock-bug/
But that didn't work... I realized that this was a device encryption thing because TWRP was asking for my pattern as well; not my new pin.
So I restarted into bootloader, connected to PC and used fastboot format userdata. This actually wiped out the encryption and now when I turn on the phone it doesn't say "Android is upgrading", "Finishing boot..." Nor does it ask me to enter my pattern. This did of course reset the phone so it looked like a first-run screen where I followed through and set up a PIN. It seems fastboot format userdata is more complete than a TWRP factory reset.
However, at this time it looks like my OnePlus 3 is un-encrypted and I have the option to encrypt it now. See attached screenshots. The question is, what will happen after I encrypt the OP3? Will it have an annoying looped boot animation and a request for my PIN or pattern?
Silly22 said:
This happens to me too but it's very strange because it seems a pattern lock I had entered persists across factory resets. So now I have to enter both my old pattern and then my new PIN to unlock my phone when I boot up.
The pattern lock comes up after the "android is upgrading" box which also flashes "starting apps" then "finishing boot" and this is after the boot animation. After I enter my pattern, it goes to boot animation again, then loads Oxygen OS 3.2.1. The reason I find this strange is because after the factory reset, I used a pin number at the setup instead of a pattern to lock the phone.
Why is my old pattern still there? I don't like the delay caused by android is upgrading and repeated boot animation.
As a note, I originally used adb sideload to upgrade from 3.1.3 to 3.2.1..
Click to expand...
Click to collapse
After you boot up after encryption go in security there should be an option to require pattern to start device, if that's disabled you won't have the double boot animation. As far as "Android is upgrading" on every boot, that usually happens if you add an app to system partition. I have Google dialer and GSam root companion so I get two apps upgrading on boot.
Your pin or password will survive factory reset.
Sent from my 1+3
Stop rebooting the device then lol
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
I noticed that when I enable "PIN on boot" in security settings (when setting a PIN, it gives you the option to require the pin to boot - to my understanding it's hiding the decryption key for /data in another boot image, which then decrypts the key and hands over the boot process) I can briefly see a "Android is upgrading" message before I can enter the PIN.
It does not take long, it just does this on every boot. Note this is for the decryption only, it's not for the "regular" Android lockscreen that comes later.
I was wondering if there's anything wrong with this, or if it's just like this. It's not a major annoyance.
Maybe someone else on 3.2.7 can check and let me know.
Thanks!
I'm having the same thing here on 3.2.7 but never really wondered why tbh
I used to see that but I removed the "pin on boot" option as it is just annoying as it means the phone stops in the bootup process and you have to manually continue it. If you turn that off then the phone still requires a pin entry instead of fingerprint to unlock the first time after booting.
That's true. But it means your system is still much easier to break into. When Android has fully booted, the data partition has already been decrypted. Pin on boot (to my knowledge) unlocks the partition only after the pin has been set.
My Xperia Arc S is having random reboots, so I installed aLogCat to search for possible errors. The error "failed to open lock file iddd.pid" appears consistently every 5 seconds or so, and starts shortly after boot begins. I've searched the internet far and wide for this error but it appears to be an Xperia only thing, and some say it's related to either quick panel buttons or SystemUI.
What is the error about and is there a fix? Could it be related to reboots I experience from time to time?
I run Ultimate HD 5.0.1. with Advanced Stock kernel.