changing the "powered by android" at startup - Asus Zenfone 5Z Questions & Answers

hi, im at evolution-x rom android 10
is there any chance that i can change the "powered by android" screen when the device booting up?

Related

Remove operator startup logo

Hi guys,
my operator has set a startup logo when you turn on the phone. How do i remove that? Thanks!

LG System Server stopped working.

Sometimes my D855 is restarting, getting blank screen and no respond or Showing "LG System Server stopped working" and after that happens same as I earlier writed (restarts, black screen). Any help? D855 16GB, Fulmics 4.2, CTT on 2.34ghz and 65 Celsius, Oversharpening on stock value. Also installed AOSP theme for Fulmics (http://forum.xda-developers.com/lg-g3/themes-apps/theme-aosp-theme-fulmics-rom-t3318985)

Restart Issue "Android is upgrading..." Everytime I reboot my device

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

black screen loop on initial configuration

hey guys, I have a problem with the mi a2 lite. After having sbricked and installed 10.0.9.0, in the initial configuration, if I select something, the screen opens and after a second the screen goes black, remains black for 5-6 seconds and then returns to the initial configuration screen (the one with the word "Hi there" where the language is selected.
What can I do?
The last time it happened to me was when I downgraded to 10.0.3.0 (same symptoms, the screen went black and left black for 5-6 sec), I tried to reinstall the 10.0.3.0 from fastboot and the phone got bricked, I had to enter edl to fix it
I made a video if it can help
https://drive.google.com/open?id=1vl6_Ak-b2TjoRUZ1OJKiAfLQ_5jHyn3w

LinOS16 & Nova Launcher: no login screen after choosing a background picture

I do run two devices (SM-P905) on LineageOS 16.0 and Nova Launcher Prime – usually without any problem.
Yesterday we choosed another photo (don't remeber the format...) from a gallery for background picture. Since that moment we are unable to use this device.
After reboot we get a blank login screen (= just black).
After deleting Dalvic/Cache we get a blank login screen (= just black).
After rebooting in safe mode we get a blank login screen (= just black).
The device does boot ROM (=Samsung logo) and LineageOS (Lineage logo) correctly. We do not get a login screen at all.
When pushing the on/off button I get the regular menu for shut down/restart/abort
Any solution for that issue without doing a factory reset?
[updating LineageOS 16 for actual November version did not do any changes]

Categories

Resources