the phone does not turn on, stays in the loop motorola logo and does not turn on the device.
the power button not working.
since i got the phone (used), no longer had boot, but worked normally after having applied an update.zip by one recovery reboot apk, he started getting looped on motorola logo
android 2.1 i think
any ideia? tks!
ok, i fix it.
the problem was the power button aways pressed. because that, i cant get on boot scrren! ^^
tks!
Hello!
I recently flashed the latest nightly of cm12.1 (2015.11.16). Wiped all the partitions needed in TWRP since i wanted a clean install. Flashed the ROM latest openGapps and tangerine kernel 11.3 and when i pressed reboot it hanged on a black screen. So after a few moments i pressed the off button on the back seeing that it got stuck and now the device wont turn on. When i press the power button i get the usual vibrate that signals the phone for turning it on but the screen remains off, LED notification bar won't turn on nothing happens, and when i press the off button on the back it vibrates 3 times for turning it off and that's about it, same thing if i try again.
Any help would be much appreciated.
Flush any cm12.1 kernel with fastboot from your pc
hello there
upon updating the android on P9 the phone got stuck on optimizing system and been like this for the past hour! what to do??!
solved by restarting phone holding power and volume down buttons and so it booted up normally
same problem here
I just updated to January 2019 update, everything was fine until i pressed 'Restart now' after it finished updating. Now it froze at Androidone screen. I hold the power button, it vibrates and looks like it's starting up but instead it freezes again at Androidone screen. If I unplug my phone it seemingly shuts down after a while, but again if I try anything it's the same thing again and I remain stuck at the Androidone screen. Please help. Thanks, Vladan
Same issue. After the update..phone boots up to Androidone logo and shuts down. If the I press the power button, it vibrates and comes up to Androidone logo and screen goes blank again
I have same problem. for me it because I forgot to remove Magisk before update. I fix by flash December Rom and then update January pacth.
UnlimitedBB said:
Same issue. After the update..phone boots up to Androidone logo and shuts down. If the I press the power button, it vibrates and comes up to Androidone logo and screen goes blank again
Click to expand...
Click to collapse
So what to do??
vladankrle said:
So what to do??
Click to expand...
Click to collapse
I have no idea. I didn't try any methods until now.
vladankrle said:
I just updated to January 2019 update, everything was fine until i pressed 'Restart now' after it finished updating. Now it froze at Androidone screen. I hold the power button, it vibrates and looks like it's starting up but instead it freezes again at Androidone screen. If I unplug my phone it seemingly shuts down after a while, but again if I try anything it's the same thing again and I remain stuck at the Androidone screen. Please help. Thanks, Vladan
Click to expand...
Click to collapse
I have the same issue. I am able to use fastboot commands from my computer, but cannot (or do not know how to) sideload update .tgz file I downloaded from en.miui.com.
Also, I am unable to use adb commands and boot into recovery.
same issue with two mi a2. stuck on bootloader after update.
I can press and hold vol- + power to boot into fast boot.
Then press and hold vol+ + power to get it to boot back to the old partition for normal use.
There might be another update later on which would probably fix the issue?
I tried to update again and now I get the same issue ouch...
Mine went well but I did something wrong in Magisk and it stop booting.
In fastboot mode I've changed it from A to B and it loaded PIE with january update. So, try to change from A to B ou B to A and see if that fixes the problem.
Tried to boot this morning but no luck.
However... The phone came back to live this evening but God knows how.
Mmm... What is going on
Confirmed, unfortunately
Dammit, you guys!.. UNFORTUNATELY, this is confirmed!!
Brand new Mi A2 (Global Version), from the shop today and went through System updates - through, to Google January 2019 Security Update and the device will not boot; same problem as with everybody else here. Argh.
EDIT:
ken218 said:
However... The phone came back to live this evening but God knows how.
Click to expand...
Click to collapse
Yup, had just managed to start it: system was up. Went for a Factory Reset and now I'm back in the loop. Stuck again, just upon rebooting. This is going the be a serious issue.
Try to start it with holding both volume buttons down and power - then release after logo and, also -perhaps- volume down.
Click to expand...
Click to collapse
^^ At least, that's what I think I'd done, heh. Sorry, not 100% sure, all happened in -serious- panic! xF
EDIT: Ah, well, thank God (LOL). It looks like there isn't anything wrong with Google's "Security patch level: January 5, 2019" (Android 9)!
However, because this happened through normal operation - it seems that a LOT of people *are* going to have this problem...
How many know that you should Factory (Data) Reset after a (regular, OTA) update; and how many will be able to boot their device, out of the loop. Geez!
P.S. Btw., you owe me *beers! ;$
EDIT: Zomg., this thread is a duplicate, already @
Code:
https://forum.xda-developers.com/mi-a2/help/bootloop-recent-android-ota-update-t3892559
Had the same problem here with April's update - hanging on logo screen constantly. Issue resolved when I connected phone to pc. Then it entered into factory reboot mode and finally booted correctly.
ol3w said:
Had the same problem here with April's update - hanging on logo screen constantly. Issue resolved when I connected phone to pc. Then it entered into factory reboot mode and finally booted correctly.
Click to expand...
Click to collapse
You only connected it to the pc? @ol3w
ol3w said:
Had the same problem here with April's update - hanging on logo screen constantly. Issue resolved when I connected phone to pc. Then it entered into factory reboot mode and finally booted correctly.
Click to expand...
Click to collapse
Thanks! This worked for me!
ol3w said:
Had the same problem here with April's update - hanging on logo screen constantly. Issue resolved when I connected phone to pc. Then it entered into factory reboot mode and finally booted correctly.
Click to expand...
Click to collapse
I had similar issue with April 2019 update. But mine was switching off few seconds after the Android One logo screen. The phone can boot into fastboot mode though.
But instead of connecting to the PC like ol3w, I had mine connected to a charger to add some juice to the battery, thinking I will have to flash the firmware again. Few minutes later, I was promptted with a "The phone failed to boot previously, do you want to "Retry"/"Shutdown"" screen. (note: I can't really remember if the second option was "Shutdown" or something else). I selected "Retry" thinking it will fail again. But then, couple of minutes later, the phone booted correctly.
Xiaomi's security patch is getting quite... unreliable recently. Wondering if I should abandon ship when pixel 3a is out (if it doesnt cost premium money)
Same problem with boot after update 2019
Failed to boot
I had the same problem. My problem was solved by using USB cable. I connected USB cable to the PC and mobile and I pushed Power. Mobile booted correctly and I work from this time. Try it, I wish you good luck.
T
Stock XT1900-1 Android One started rebooting on its own last night, it shows the Android One boot screen for about 8 seconds, then goes to a black screen for abut 3 seconds, then back to the Android One boot screen.
If you hold power and volume down it will go to the fastboot screen for about 8 seconds, then restarts again.
Power button has been flakey for a while (hard to get to turn the screen on via the power button)
The Fastboot screen says:
Baseband: M660_7048.65.01.101R
Variant: payton XT1900-1 64GTB P4
Anything I can do to recover it, or is it most likely a issue with the power button causing this?
Thanks
Aaron Z