Hi,
Last week, when my OnePlus 9 Pro updated OTA to OOS 11.2.8.8.LE15BA, I have had an issue.
At the end of update, when the phone has rebooted, it rebooted to bootloader.
My phone is not rooted, bootloader locked, never unlocked.
During at least 30 minutes, I've tried to reboot it, by the bootloader menu. Every time, it rebooted to the bootloader.
After 10 or 15 tries, it rebooted well, on OOS.
It's very strange (but I'm happy that it works great now)...
No problem now if I reboot my phone.
So I would like to know if someone has had that kind of issue... What could be the cause?
And now I'm afraid of future OTAs. Do you think that if it happens one time, it could happen every time?
And if it happens again, is there a method to reboot it with success, and no stress
Thanks in advance for your help
You have to be patient.
Can happen due to a messed-up upgrade, happened once to me on my OnePlus Nord. Your best bet is to go to recovery and erase data if nothing managed to work. Make sure to backup any important data before updating. I can only hope that things go well, considering how our future updates can be directly based off on Color OS, instead of AOSP.
Thank you @oddlyspaced .
2 things to do when the next OTA will be pushed : save everything and pray .
So if there's an unsolvable issue, I would erase all data and reboot
Related
Hey guys,
I need some help with my pixel. The phone has been rebooting like crazy the last few days, at least 10 times a day. I can't figure what it is. The phone is not rooted and the bootloader is locked
edwardlanti said:
Hey guys,
I need some help with my pixel. The phone has been rebooting like crazy the last few days, at least 10 times a day. I can't figure what it is. The phone is not rooted and the bootloader is locked
Click to expand...
Click to collapse
Try a factory reset. And run it with only the apps that come installed for 24 hours. If it still reboots its a hardware failure. If it doesnt reboot then some software you had on it was causing a crash.
Scott said:
Try a factory reset. And run it with only the apps that come installed for 24 hours. If it still reboots its a hardware failure. If it doesnt reboot then some software you had on it was causing a crash.
Click to expand...
Click to collapse
I had a pixel xl rebooting 2-3 times a day, did exactly this, reboots persisted... Was within 14 days and got the phone swapped out. New phone does not have any reboot issues.
Pretty much any phone that I restore my last backuo from marshmallow causes not stop reboots. When I got Nouget on my 6p somehow the restore screwed something up. When I got my pixel there were 2 dates to restore from. One from my 6p prior to Nouget, and one from Nouget that was a clean install from scratch. The pre 7 restore caused the pixel to reboot constantly just as it had the 6p.
I noticed my phone restarted and the date was set to Jan 1st 1970 while it was in my pocket. I did a adb bugreport but could not find anything. I did find this line though check_reboot_mode: restart_reason: 0x00000000. Does the phone ask for pin only when it restarts? I have fingerprint based authentication setup but it still asks for pin from time to time, now I am wondering if those were restarts.
318sugarhill said:
Pretty much any phone that I restore my last backuo from marshmallow causes not stop reboots. When I got Nouget on my 6p somehow the restore screwed something up. When I got my pixel there were 2 dates to restore from. One from my 6p prior to Nouget, and one from Nouget that was a clean install from scratch. The pre 7 restore caused the pixel to reboot constantly just as it had the 6p.
Click to expand...
Click to collapse
It's generally a good idea not to restore a backup from a previous major system iteration. Anytime a new generation is introduced, one should do a clean install, as you noted in your last sentence. There are potentially a lot of system changes that can cause conflicts.
edwardlanti said:
Hey guys,
I need some help with my pixel. The phone has been rebooting like crazy the last few days, at least 10 times a day. I can't figure what it is. The phone is not rooted and the bootloader is locked
Click to expand...
Click to collapse
Hello,
I had the same issue with the most recent Verizon update on my wife's Pixel. There seems to be a lot of people with Pixels having this issue as well. I needed to return it for a new one...Verizon is aware of the issue as they did not hesitate to replace the unit.
Cheers
Helpful tip, hopefully.
If you want to test the effect of installed apps, Pixels can boot into "safe mode," where installed apps are disabled temporarily. Press and hold power button to open a reboot menu, then press and hold "Power off" button. A menu will open to allow booting into "safe mode."
https://support.google.com/pixelphone/answer/2852139?hl=en
Do you have any apps under beta? I was using around 6-8 apps in beta, I unsubscribed out of the beta and reinstalled all the apps. My phone stopped rebooting.
P.S. My phone was rebooting even under safe mode!
I'm hoping somebody can provide this recent, stock firmware for me. It's 8.0 with I believe the February 2019 security patch (but I'm not 100% on which security patch). I have a US variant 1710-01 with the build number listed in the title. However, it's been tinkered with and had other stuff flashed. Now I'm having a few issues. The only way to boot is to boot system from bootloader. Trying from recovery or just a normal restart only boots to stock recovery every time. It will also not take security updates (of course).
I want to just return to a fully clean, stock ROM but the only stock files I can find are out of date and will not flash, or came from another variant and screw things up worse.
I'd also be completely happy with Build 27.76-12-28-20, which is the June security patch.
I did find a dump of the ROM, but I'm not savvy enough to make it flashable (at least the system and maybe some other partitions) in fastboot.
**EDIT** link to dump of current stock ROM https://github.com/AndroidDumps/motorola_albus_dump
Thanks anyone who can help.
Wouldn't you be happy with these links?
Thanks. Those were the files I needed.
However, I flashed my current version and was able to re-lock. During the flash, it did give me the "bad ID" or something message while flashing boot and recovery partitions. But I've seen that error many times while flashing a stock ROM. On first boot, I got the notification of an update available. I took the security patch update, which successfully installed. Upon restart after installing the update , my phone was hard bricked.... like done, toss it or replace it hard bricked. Not your fault, and I'm not sure what went wrong. I've heard of similar issues on Moto phones when sideloading an update, but not when doing an OTA.
Anybody have pointers on what may have gone wrong?
OK... strangest thing I've seen for a while with flashing. This is after numerous little attempts to reboot, factory reset, flash partitions, etc. I turned off the phone in the bootloader just so the battery wouldn't go to 0% in bootloader mode. When I went to power it on again to show my wife how screwed up it was, it booted up fine. It says the update completed and it's completely normal now.... EXCEPT that it always boots in to bootloader now instead of booting to system by default. I'm not sure how to fix that. It's not a huge deal, but still not quite right.
Maybe reflashing the boot/bootloader alone will help. Haven't seen this for all the years I work with android.
Hi friends,
I read lots of your posts and thought that you are so professional and can help me. :/
Firstly, I have a HTC One M8. (M8_UL PVT SHIP S-ON). And its HBOOT is 3.19.0.0000
The phone had android 6 before and i was using so normal. But the previous week, it has worked so slow suddenly. Very very slowly. Think that you want to write a mesagge to a friend, every letter takes 10 seconds after push. I wanted to turn it first settings with factory reset again and again, but it didn't work. After this I wanted to try rooting it.
And yes it was my first experience and that's why I think I made a few mistakes.
As I read all of your posts about Rooting, I turned its bootloader mode to UNLOCKED and install TWRP. And root with TWRP to lineageOS 17, lineage 16, lineage15. But nothing changed, my phone was slow again. And I tried somethings again and again for 3 days. And I don't know what to do as different but I had flashed lineage16 lastly and was trying another ways, it worked normally. It was very fast again like I bought it first. I was so happy.
On the same day, I wanted to give it to technical service to change its broken camera which was broke in the before months. I wanted to use full OK phone again with happines. But the man changed its camera and give it to me, the camera was working good but the phone was working so slow again. (
Now it's still working slow. I've tried many things for 2 days again. Reset factory, flashing Lineage16 again but nothing change.
And I realize it after flashing lineage16 before, I won't turn to android 6 again. I searched unroot issues and tried a few of them but I take fail or error messages again and again.
I wanted to use my phone normal and get rid of from that slowing. The versions of androids is not important. It can be lineage or another ROMs. Or we can make UNROOT with it. How will I solve this slowing issue I don't know. This is the only problem that I want to solve.
I think it can be about with its part of CPU as mechanically (that i want to thing it lastly) or its boot files (cause i deleted system data too with TWRP again again). I can't think any other thing.
Could you help me please?
Borneaz said:
Hi friends,
I read lots of your posts and thought that you are so professional and can help me. :/
Firstly, I have a HTC One M8. (M8_UL PVT SHIP S-ON). And its HBOOT is 3.19.0.0000
The phone had android 6 before and i was using so normal. But the previous week, it has worked so slow suddenly. Very very slowly. Think that you want to write a mesagge to a friend, every letter takes 10 seconds after push. I wanted to turn it first settings with factory reset again and again, but it didn't work. After this I wanted to try rooting it.
And yes it was my first experience and that's why I think I made a few mistakes.
As I read all of your posts about Rooting, I turned its bootloader mode to UNLOCKED and install TWRP. And root with TWRP to lineageOS 17, lineage 16, lineage15. But nothing changed, my phone was slow again. And I tried somethings again and again for 3 days. And I don't know what to do as different but I had flashed lineage16 lastly and was trying another ways, it worked normally. It was very fast again like I bought it first. I was so happy.
On the same day, I wanted to give it to technical service to change its broken camera which was broke in the before months. I wanted to use full OK phone again with happines. But the man changed its camera and give it to me, the camera was working good but the phone was working so slow again. (
Now it's still working slow. I've tried many things for 2 days again. Reset factory, flashing Lineage16 again but nothing change.
And I realize it after flashing lineage16 before, I won't turn to android 6 again. I searched unroot issues and tried a few of them but I take fail or error messages again and again.
I wanted to use my phone normal and get rid of from that slowing. The versions of androids is not important. It can be lineage or another ROMs. Or we can make UNROOT with it. How will I solve this slowing issue I don't know. This is the only problem that I want to solve.
I think it can be about with its part of CPU as mechanically (that i want to thing it lastly) or its boot files (cause i deleted system data too with TWRP again again). I can't think any other thing.
Could you help me please?
Click to expand...
Click to collapse
Yes, I unrooted it lastly. :laugh:
With the helps of @ckpv5 via this old share https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
My phone's version-main number is now : 6.12.401.4 It turned to the its first state.
So, my main problem continues too, it behaves so slow like a turtle again... :crying:
Hi everybody I am new here so I apologize for my lack of knowledge.
This past Sunday evening I attempted an OTA update on my Verizon S10+. Upon the phone restarting post-update it went into a reboot loop. I have tried everything I am capable of and cannot get it out of the loop. I can access the recovery menu (may not be correct term) and have cleared the cache partition, attempted to "fix apps". Also have attempted to launch in safe mode, also have let the phone go totally dead and restart, but still looping.
Here is the issue, I am fairly certain a factory reset would fix it, I found maybe one or two people with this exact problem after this most recent March update. They said factory reset worked. However, I have some pictures on the phone's internal storage that is not backed up anywhere. I know, very stupid of me to not have been backing up, I should know better.
Last night was my final attempt at a fix that hopefully wouldn't wipe my pictures. I attempted (and I thought I succeeded) to flash the March update to the phone using Odin. Hoping that might result in a successful install of the update and resolve the issue.
No change after flashing the phone. I don't know what to do to try to save those pictures, I was wondering what would happen if I waited for the next update and then tried to flash that to the phone using Odin.
I'm at a loss, you all seem very knowledgeable and helpful and I am already appreciative of the help I have found in past threads here. Any suggestions/thoughts would be great.
Thanks,
Sam
@hainguyenthao Just generously spent a solid hour and a half helping me. It appears I did not flash my phone correctly and/or the data on my phone was already toast after the initial OTA update failure that caused the reboot loop.
Fixed by @hainguyenthao even though I screwed up my own data. Phone is working again!
Had absolutely no issues with my Pixel 6 Pro on the January update but as soon as I installed the February update my phone reboots so much when the screen is off. When I'm using it, there are no issues. The second I turn off the screen, it reboots. Then it'll reboot 5 more times before I can even unlock my phone. Then I'll turn the screen off and it'll reboot again. It must have rebooted around 500 times last night.
Is there a fix for this? Or a step by step guide on how to install the January update over the February one?
How did you install it? I'd wipe it and reinstall with the android flashtool
Android Flash Tool
flash.android.com
fil3s said:
How did you install it? I'd wipe it and reinstall with the android flashtool
Android Flash Tool
flash.android.com
Click to expand...
Click to collapse
Directly through the phone's regular system update.
WHOneedsSOX said:
Directly through the phone's regular system update.
Click to expand...
Click to collapse
I don't think you need a unlocked bootloader to sideload just USB debugging enabled if you wanted to try a full wipe. Maybe try factory reseting from settings - I'm going on the assumption that the bootloader isn't unlocked
WHOneedsSOX said:
Had absolutely no issues with my Pixel 6 Pro on the January update but as soon as I installed the February update my phone reboots so much when the screen is off. When I'm using it, there are no issues. The second I turn off the screen, it reboots. Then it'll reboot 5 more times before I can even unlock my phone. Then I'll turn the screen off and it'll reboot again. It must have rebooted around 500 times last night.
Is there a fix for this? Or a step by step guide on how to install the January update over the February one?
Click to expand...
Click to collapse
You can't downgrade once you've upgraded. It's best if you backup your data and try starting fresh on the February build to see if it causes any issues.
Use the flash tool and make sure both partitions are formatted and try again.
Did you do any modifications to your phone that could have caused the random reboots?
fil3s said:
I don't think you need a unlocked bootloader to sideload just USB debugging enabled if you wanted to try a full wipe. Maybe try factory reseting from settings - I'm going on the assumption that the bootloader isn't unlocked
Click to expand...
Click to collapse
That's correct, it isn't unlocked.
RetroTech07 said:
You can't downgrade once you've upgraded. It's best if you backup your data and try starting fresh on the February build to see if it causes any issues.
Use the flash tool and make sure both partitions are formatted and try again.
Did you do any modifications to your phone that could have caused the random reboots?
Click to expand...
Click to collapse
I have done absolutely no modifications other than typical downloading of apps and modifying through there but even that is just theming. By "try again," just wipe and then reinstall the update?
WHOneedsSOX said:
Had absolutely no issues with my Pixel 6 Pro on the January update but as soon as I installed the February update my phone reboots so much when the screen is off. When I'm using it, there are no issues. The second I turn off the screen, it reboots. Then it'll reboot 5 more times before I can even unlock my phone. Then I'll turn the screen off and it'll reboot again. It must have rebooted around 500 times last night.
Is there a fix for this? Or a step by step guide on how to install the January update over the February one?
Click to expand...
Click to collapse
The random reboot bug seems to be a problem with Android 12. I haven't yet seen any clues as to the reason why.
Sometimes it's caused by a backup, sometimes by an update, some claim it's because of a hardware failure.
I experienced the same when I got my Pixel 6 Pro out of the box - about 2 random reboots per day, I had to get a replacement device to fix that.
My Pixel 3 also has the random reboot problem right after I updated it to Android 12, just like you said - every couple minutes, even though it reboots BOTH when in active usage AND when the screen is off. I have not yet tinkered with the device to find the reason, since I don't need that phone (anymore).
As a last resort, if you don't want to lose data on reseting the device, my advice would be to:
Download the latest OTA to your PC & sideload it in recovery mode (hold vol down before screen comes on, upon reboot). That will re-flash all important blocks & will boot you from the opposite partition (A/B) but keep your data/apps, hopefully fixing whatever the issue is in the process.
Morgrain said:
The random reboot bug seems to be a problem with Android 12. I haven't yet seen any clues as to the reason why.
Sometimes it's caused by a backup, sometimes by an update, some claim it's because of a hardware failure.
I experienced the same when I got my Pixel 6 Pro out of the box - about 2 random reboots per day, I had to get a replacement device to fix that.
My Pixel 3 also has the random reboot problem right after I updated it to Android 12, just like you said - every couple minutes, even though it reboots BOTH when in active usage AND when the screen is off. I have not yet tinkered with the device to find the reason, since I don't need that phone (anymore).
Click to expand...
Click to collapse
I'd be happy with 2 random reboots per day. Not even kidding, I must be at 100 a day. It's super random too. None from 9 am until around 1pm and then all of a sudden 10 in a row.
I'm pretty sure it's a software issue, had no random reboots before I installed the February update. Will probably try reformatting the entire phone first and see how that goes.
DanielF50 said:
As a last resort, if you don't want to lose data on reseting the device, my advice would be to:
Download the latest OTA to your PC & sideload it in recovery mode (hold vol down before screen comes on, upon reboot). That will re-flash all important blocks & will boot you from the opposite partition (A/B) but keep your data/apps, hopefully fixing whatever the issue is in the process.
Click to expand...
Click to collapse
Thanks, will try this out if a reformat doesn't work.
Try safe mode and see if it still happens.
neyes said:
Try safe mode and see if it still happens.
Click to expand...
Click to collapse
Still happened in safe mode.
I would honestly try a complete wipe and fresh install of the OS to see if it still happens. If it does you could get it RMAd since it could be hardware related.
RetroTech07 said:
I would honestly try a complete wipe and fresh install of the OS to see if it still happens. If it does you could get it RMAd since it could be hardware related.
Click to expand...
Click to collapse
By "wipe and fresh install" do you mean reformatting it normally through the phone (like if I was returning a used phone)? Or is it as Daniel suggested above?
WHOneedsSOX said:
By "wipe and fresh install" do you mean reformatting it normally through the phone (like if I was returning a used phone)? Or is it as Daniel suggested above?
Click to expand...
Click to collapse
Official Google Android Flash Tool
roirraW edor ehT said:
Official Google Android Flash Tool
Click to expand...
Click to collapse
Thanks!