Hi everyone. I'm using an Oppo Find X2 Lite since january and today I finally received the update to the ColorOS 11.1 based on Android 11. I put my phone in charge and started updating, but when the process finished something strange happened. When the phone re-booted it showed nothing but a black screen with the top bar with time, wi-fi and battery icons that goes on and off in a loop. I can't do anything: if I try to boot off the phone by pressing the power key, a white empty rectangle appears on the screen, but touching it does nothing. If I press the power button multiple times I can enter in a "SOS Emergency" mode by which I can use the flash light as an SOS or call my local number for an ambulance.
After buying the phone, I debloated it with adb commands following a list I found on this forum: may this be the reason for this behaviour? After debloating the phone I updated it a couple of times, but they were minor security update of ColorOS 7.
I have no idea of what to try, I'm just waiting for the battery to die and then try to access a recovery mode. Hope someone can help me, cheers
kibalcic said:
Hi everyone. I'm using an Oppo Find X2 Lite since january and today I finally received the update to the ColorOS 11.1 based on Android 11. I put my phone in charge and started updating, but when the process finished something strange happened. When the phone re-booted it showed nothing but a black screen with the top bar with time, wi-fi and battery icons that goes on and off in a loop. I can't do anything: if I try to boot off the phone by pressing the power key, a white empty rectangle appears on the screen, but touching it does nothing. If I press the power button multiple times I can enter in a "SOS Emergency" mode by which I can use the flash light as an SOS or call my local number for an ambulance.
After buying the phone, I debloated it with adb commands following a list I found on this forum: may this be the reason for this behaviour? After debloating the phone I updated it a couple of times, but they were minor security update of ColorOS 7.
I have no idea of what to try, I'm just waiting for the battery to die and then try to access a recovery mode. Hope someone can help me, cheers
Click to expand...
Click to collapse
Try holding volume up + power button for 10-15 seconds phone should power down , when it does hold voume down plus power button should take you to recovery mode.
Hi,
I answer late but I got the same problem with my Oppo Find X2 lite. After dowonloading the Color 0S11.1 update my phone restarted.
But then I couldn't unlock it. The screen was flashing on and off in a bootloop.
I managed to get in recovery mode using the method described above. Unfortunately I couldn't just remove or restart the update and I had to do a full factory reset. Then the Colors OS 11 update went smooth.
I had also debloated my phone but only a few apps and services. I was very careful. So I have another clue : to me it looked like the phone couldn't load the fingerpint id sensor on start screen.
I wonder if it shouldn't be deactivated before any major updates.
@kibalcic : did you manage to solve your problem ?
Related
So, yesterday I decided to reboot my phone since it was very sluggish for whatever reason. I think it shut down properly but when it came back on, there was a very interesting problem that had come up - it didn't boot any further than the logo screen, which didn't even play its standard animation; it just stood there with the LED on the home button changing colors (like normal). I left it on overnight hoping the problem would be gone, but to no avail. It still hadn't booted when I woke up. If it matters, the only thing I can boot to is download mode. It doesn't let me get to safe mode or however it's called (the menu you navigate with volume up/down and the power button). Needless to say, I was very puzzled. Then I went on and tried to flash the latest kdz since I thought that would fix the problem. I hoped that would easily fix the problem. But no, it decided to be funny and give me more headache. I tried using this guide: http://forum.xda-developers.com/showthread.php?t=2409308 but after step 20 the LG Mobile Support Tool crashes and I can't continue. Sure thing, I will try the Upgrade Recovery that the tool has built in. It properly detects my phone, the software download and extraction goes smoothly. Then I reach the S/W Upgrade part of the process. The few first seconds everything is fine, but then the bar reaches 5% and just stops. Just like that. Now it's been 8 hours since I began the recovery and no progress has been made.
Can anybody help me? I'm lost here...
rexsis13 said:
So, yesterday I decided to reboot my phone since it was very sluggish for whatever reason. I think it shut down properly but when it came back on, there was a very interesting problem that had come up - it didn't boot any further than the logo screen, which didn't even play its standard animation; it just stood there with the LED on the home button changing colors (like normal). I left it on overnight hoping the problem would be gone, but to no avail. It still hadn't booted when I woke up. If it matters, the only thing I can boot to is download mode. It doesn't let me get to safe mode or however it's called (the menu you navigate with volume up/down and the power button). Needless to say, I was very puzzled. Then I went on and tried to flash the latest kdz since I thought that would fix the problem. I hoped that would easily fix the problem. But no, it decided to be funny and give me more headache. I tried using this guide: http://forum.xda-developers.com/showthread.php?t=2409308 but after step 20 the LG Mobile Support Tool crashes and I can't continue. Sure thing, I will try the Upgrade Recovery that the tool has built in. It properly detects my phone, the software download and extraction goes smoothly. Then I reach the S/W Upgrade part of the process. The few first seconds everything is fine, but then the bar reaches 5% and just stops. Just like that. Now it's been 8 hours since I began the recovery and no progress has been made.
Can anybody help me? I'm lost here...
Click to expand...
Click to collapse
Hi, thanks for using XDA assist!
Please post your question here:
http://forum.xda-developers.com/showthread.php?t=2257421
The experts in that thread will be able to help.
Good luck!
Thread closed.
Bought a Nexus 5 about 6 months ago USED. It has been amazing. I got the latest OTA a week ago or so, not sure if that has anything to do with current issues.
About 2 days ago started randomly restarting. Today, it shut down and has been in continuous loop restarting. I see "Google" and maybe even the boot dots loading, then it is off. Three seconds later, starts again and repeats. Never makes it all the way into Android system. I let it sit for a while and when I pick it up, without touching any buttons, it repeats all of this. I suppose it is probably dead in general, but I don't know. Do you guys have any ideas? Again, I bought it used and from a ma/pap store who said they buy 100 in bulk, which made me skeptical, but they also had a 60 day guarantee and it was amazing the first 60 days and even after. It has been error free for 6 months, so I don't know if this is just a random issue or if the previous owner dropped it in a lake and I got lucky, or what. FWIW the damn thing has been in a case and never dropped, so it isn't anything that I have done I don't think. Thanks for any help.
edit: never rooted, never messed with, always been stock
Another user reported some instability since the last OTA update.
Flashing the full factory images did the trick.
a friend of mine gave me his nexus 5 to repair and its doing something similar. He had ir rooted and on latest 5.1.1 (i think). Either way, he said it was randomly locking up and rebooting. When i got it it had the red blinking light when plugged so i got a new battery. That got fixed but then the constant bootloop showed itself. I flashed TWRP (many versions, 2.6.3.1; 2.7.1.1; 2.8.7.1; the one that worked best was 2.7.1.1). So, once in twrp wiped, pushed cm 12 snapshot, flashed it, pushed gapps, falshed, pushe supersu flashed. Started the system. That precise order of things (ie: pushing flashing, then pushing something new and flashing it) was what gave me best results to actually boot up at least once. Once booted up and logging in and everything to cm i had some sort of stability (even rebooting and powering off) but i think that everything went wrong when i plugged the phone to the computer and it was back to bootloops and not even getting to the recovery. Flashed everything again. Didnt work. Had to leave the phone sit for a while (without the back casing) before trying again, in order, before getting any success. Im starting to think of ovrheating but it doesnt even get that hot...
Dunno if you guys have any ideas on this. Or if i can give you mor details to help us out.
Regards!
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
WaxLarry said:
In my opinion your problems seems power button's related.
Click to expand...
Click to collapse
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Paul22000 said:
This morning my Nexus 5 was turned off all of a sudden after not having used it for 20-30 minutes. I held the power button and nothing. I plugged it into power and the "Google" screen appeared. It then went into a reboot loop on and off, on and off, on and off. I held the Volume Buttons and it went into fastboot, but then boot looped out again and again. Searching on Google yielded that this was indeed a common problem. [...]
Click to expand...
Click to collapse
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Ok @jeffsf keep going on this thread. I had the same damn experience, that ended with RMA. LG said that the problem is related to some tension change in the power button. After the RMA I used the phone totally stock and never had a problem. Two months ago I switched to blu_spark kernel and some weeks after i noticed some problem. When I pressed the button to lock the screen, phone locked itself and then screen turned on, sometimes showing the shutdown option. So i understood that something was happening to the power button. I tried to overvolt with a +5mV on general offset and since then i never had problem. If you can enter recovery or bootloader i suggest you to flash some kernel with volt change support and then overvolt the general offset... and keep finger crossed
jeffsf said:
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Click to expand...
Click to collapse
I got a notification for this post since you quoted me. I'm not sure if you're having the same problem but I'll tell you what happened to me, just in case. I called T-Mobile and they referred me to the nearest 3rd party phone repair shop. I went there and after an evaluation, the repairman told me the power button on my phone was indeed broken. They replaced it for $55.
The story doesn't end there though. I took my phone home and a few hours later I tried to use bluetooth and it didn't work. I took it back and found out that unfortunately, when the guy replaced the power button, he inadvertently broke the bluetooth. There's no way to fix bluetooth without replacing the motherboard entirely, which would cost $200. I'd rather buy a new phone at that point since my Nexus 5 was getting old. He refunded me, which was nice. At least the power button worked so I could use my phone. Bluetooth isn't as valuable as being able to you know, turn on the phone, so at least it was a net gain.
After that, I purchased a Nexus 6 and rooted it so I could use double-tap-to-wake (along with the automatic screen on when you pick up the Nexus 6). I also use the following app in order to turn off the screen by swiping up from the home button (I don't care about losing the shortcut to Google Now): Screen Off and Lock
I can now literally go weeks without using the power button on my Nexus 6. (I literally only use it when tap to wake sometimes becomes unresponsive which is rare.)
Bottom line: I will never buy another phone without tap to wake functionality! :good:
A local repair shop here indicated that one sometimes does changing the power switch resolve the issue. They have seen situations where the issue appears to be one of the power-management ICs. Just something to be aware of when examining the potential cost of a repair and who you would have do the work.
I just downloaded the update for Cyanogen Mod 13 and I clicked install then my phone powers on (no matter what buttons I press; power, power and volume up and home) it has the Samsung S5 logo and the text "Recovery booting..." (as well as the other warranty text stuff). It then quickly flashes the screen with the Android and cog logo with the text "Installing system update" for the shortest time (making it almost impossible to read the text) it then flashes this screen on and off every 5-10s for the rest of the time. I thought that the screen maybe just a little glitchy but the "update has been running for almost an hour now. How can I fix this problem if my phone doesn't allow me to put it into recovery mode .
So I spent about 3 hours trying to fix this problem trying every combination of buttons to press on boot as well as trying to make my phone detectable or something like that. Let my Mum try fiddling with it (she has no idea what she doing with new tech) some how she managed to press the buttons just right. It went into download mode and I was able to flash it with an update of TWRP using ODIN and it rebooted and started up. If you haven't already try putting it into download mode, I've heard getting the timing right can be tricky when your phone is doing unusual things. Now I'm unsure whether to try updating again but I might try wiping and going back to a stable 12.1.
Mod Edit:
Thread closed as ODIN fixed it
It started a few days ago, I was testing a cardboard/gear vr unity game and the screen would turn black but the buttons were responsive and I could get it to hard reboot or make it come back again after plugging it back into the gear. I looked around but couldn't find anything that resembles my issue.
Now as soon as it boots it goes into a black screen after samsung and carrier logos show, i sometimes get a glimpse of the lock screen and respond to some input.
The phone is still on, I can feel the battery warm.
-No response to any input. Not even pwr+vol down.
-PC won't detect it when plugged.
-No lights on charging.
-I need to let it fully drain for it to shut down and try anything again.
-Did a factory reset from recovery mode, wipe cache. Still the same.
-No root.
-There was an update that may have installed overnight but can't confirm because can't access system info.
EDIT: New find! when booting to recovery, goes into "Installing Update" and then "No command".
Any thoughts??
Is there some pc software that i can use to try to reinstall firmware? Something like SEUS for sony phones back in the day?
Is odin safe or should i look into a samsung official tool? I've never used odin so i'm not sure of it's capabilities (this is my first sammy phone, I had it to get to test gear vr apps)
Sorry for the long post but wanted to get all the info out there.
Thanks!
Can you enter "Download Mode"? (By rebooting and pressing HOME + VOLUME DOWN)
If yes, I suggest that you try, as you suggested, reinstalling your firmware.
You will have to know your carrier, or specific phone model (G930X, where X represents carrier letter (Example: T for T-Mobile) )
Modified Odin (by PrinceComsy): https://androidfilehost.com/?fid=24591023225177749
Then I suggest downloading firmware from https://SamsungBay.com as all other sources restrict download speed (So it takes a minimum of 13 hours).
https://samsungbay.com/download-firmware/?device=&model=sm-G930&firmware=
Once you have Odin and Firmware, load the correct files.
(AP_G930X), (BL_G930X), (CP_G930X), and (CSC_G930X) into Odin.
Power off phone, and boot into download mode (Pressing HOME + VOLUME DOWN)
N.B/ You will lose all your phone data, sadly, but it seems you've already wiped it.
Hi , i have working with more than 100 xz2 phones , i got many problems and fix it (google and xda) , so I think I can help you to fix your problem with xz2 asap if u ask me in this post
My exp :
Flash
Unlock
Root
and some small problems...
[deleted]
sinommo said:
Hi , i have working with more than 100 xz2 phones , i got many problems and fix it (google and xda) , so I think I can help you to fix your problem with xz2 asap if u ask me in this post
My exp :
Flash
Unlock
Root
and some small problems...
Click to expand...
Click to collapse
Hello,
My wife's Sony Xperia XZ2 Compact with model number H8324 has an issue with booting or maybe the launcher getting stuck in a loop after getting to the lock screen for a split second.
The phone seems to boot like normal and gets to the lock screen, we are even able to punch in one or two digits of the 4 digit pass code. Then it goes into a loop of the notification bar and back button flickering. From then on the phone is not responding except for the power button which brings up the normal "Turn off, Reboot, and Lockdown" menu. The issue just started out of nowhere yesterday morning and we haven't been able to fix it yet. We haven't done any rooting or custom rom flashing, it's running the official Sony software but it's out of warranty.
Here's a video showing the issue. The video shows the whole boot process but the link takes you to the last part after the logos.
We would love to get some files off it so if there is a way anyone can help us with that we'd prefer it over a hard reset.
Things we've already tried
Turning the phone off and on again
Unlocking the phone in the split second the lock screen works, this is just too short to swipe up and then put in four digits.
Rebooting the phone
Booting while charging
Booting into safe mode (this has the same issue)
Connecting the phone with USB to a pc, the phone is recognized by Windows, but it doesn't share it's filesystem with Windows.
Connecting the ADB to it, alas usb debugging is not yet enabled on the phone
Trying to get into recovery mode, we haven't been able to get into the recovery menu. Googling seems to indicate it might be holding volume up + power button when the phone is off but then it doesn't seem to do anything at all.
We're currently trying to run out the battery of the phone to see if that will resolve the issue on it's own.
If anyone has any idea, we would love to hear it.
mohhom said:
Hello,
My wife's Sony Xperia XZ2 Compact with model number H8324 has an issue with booting or maybe the launcher getting stuck in a loop after getting to the lock screen for a split second.
The phone seems to boot like normal and gets to the lock screen, we are even able to punch in one or two digits of the 4 digit pass code. Then it goes into a loop of the notification bar and back button flickering. From then on the phone is not responding except for the power button which brings up the normal "Turn off, Reboot, and Lockdown" menu. The issue just started out of nowhere yesterday morning and we haven't been able to fix it yet. We haven't done any rooting or custom rom flashing, it's running the official Sony software but it's out of warranty.
Here's a video showing the issue. The video shows the whole boot process but the link takes you to the last part after the logos.
We would love to get some files off it so if there is a way anyone can help us with that we'd prefer it over a hard reset.
Things we've already tried
Turning the phone off and on again
Unlocking the phone in the split second the lock screen works, this is just too short to swipe up and then put in four digits.
Rebooting the phone
Booting while charging
Booting into safe mode (this has the same issue)
Connecting the phone with USB to a pc, the phone is recognized by Windows, but it doesn't share it's filesystem with Windows.
Connecting the ADB to it, alas usb debugging is not yet enabled on the phone
Trying to get into recovery mode, we haven't been able to get into the recovery menu. Googling seems to indicate it might be holding volume up + power button when the phone is off but then it doesn't seem to do anything at all.
We're currently trying to run out the battery of the phone to see if that will resolve the issue on it's own.
If anyone has any idea, we would love to hear it.
Click to expand...
Click to collapse
I think u just need to reinstall rom file with newflasher and stock rom , did u tried it ? with newflasher newest version , u still can keep the personal files and flash stock rom for the phone , then i think this phone will run normal again
If u dont know how to do that , reply comment here , but u should turn off the phone to keep battery well , if u can't turn off the phone , try to press and hold volume up button + power button within 5 sec , phone will vibrate 3 times and totally off
Is there a way to get a stock recovery if somehow the recovery has been deleted?