General Problems updating to A13. - Google Pixel 6a

If I check for an update it shows there's an update to android 13. I've tried several times to update and it always says there was a problem installing the update. I start the installation and then says it's paused. I resume and it says the installation will continue when the device isn't being used. I again hit resume and it says there was a problem. Rooted on build SD2A.220601.003.B1. I've tried on wifi and mobile data with no change. Restarted the phone several times with no change. I'm coming from a Oneplus 7 pro, is there something Pixel related that I don't know about? I haven't tried anything related to Magisk because I've never had to in the past.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Rooted on build SD2A.220601.003.B1. I've tried on wifi and mobile data with no change. Restarted the phone several times with no change. I'm coming from a Oneplus 7 pro, is there something Pixel related that I don't know about? I haven't tried anything related to Magisk because I've never had to in the past.

Rooted is the issue. Flash back the stock kernel or just flash 13 manually

You're trying to take an OTA while rooted and asking why it doesn't work? If you want to run a rooted phone, you have some learning to do before you brick your phone.

If root is the problem, it's not a big deal. Taking the OTA and then using Magisk to flash to the inactive slot has always been the easiest solution. The Oneplus never cared about root. Pixel 2 XL was my last pixel device I used but I always had a rom installed. So this is new to me.

Be careful...if/when you DO get updated and reboot into 13, make sure u flash the new bootloader to the other partition.

Related

SM-N915V -- Downgraded from 6.0.1 to 4.4.4 with mixed results

So, this is a little bit odd.
I have long since moved from using a Samsung phone as my daily driver, but still use my Note Edge while on the go as a mobile sketchbook. Well, last night I accidentally approved the OTA update that had been pending on my phone for several years straight, which updated my device to Marshmallow. The 6.0.1 update caused my performance to tank hardcore, to the point where it's borderline unusable and my battery drains in less than an hour. Unacceptable.
I used Odin to flash back to 4.4.4. I grabbed a stock ROM for my device and Odin 3.12.7, put it into recovery mode, and started the process. Surprisingly, everything went off without a hitch and I found myself with a green PASS box and no errors in the Odin log. Sweet.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
However, something's not right. I'm still on Marshmallow, but with all of the old KitKat apps having replaced the ones that updated. All of the icons are their older versions and even the system font is back to its old thick, round self. The OTA update is back, somehow, and my phone's About page says I'm still on 6.0.1. User data was also not touched. The baseband of the phone matches the file I used, so I definitely flashed the ROM.
Obviously I missed a step. I thought this process would factory reset my device?

suddenly black screen with back-light On issue?!

I'm using android 9 with microg Rom and everything works just fine but after testing the android 10 beta release and comeback to android 9 with microg, I suddenly encountered a strange black screen with back-light & HW-navigation buttons on also network(adb) disconnected. So I have to press and hold the power button for 10 seconds to force turn the phone off.
I reflash several firmware(s) and other PIE Roms but the issue is existing :crying:
I take some pictures in the dark room to better understand the situation
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is anybody experienced the same issue to oneplus one device Is my phone dying?! :crying:
You are not alone, same **** happens to me after trying to flash android 10 on my device. The worst part of it is, it’s happening after restoring a backup of a perfecto working phone i just did before upgrading from lineage 16...
If you found anything about this, let me know please.
I have also yet to find a stable version for android 10, it keeps giving me errors. As long as you still access twrp, then at least it is not hard bricked.
I have the same problem ._.
I flashed an android 10 rom, then I restored my Android 9 backup... then those issues occured. Then i did a factory reset: it didnt help at all, then I wiped all my data, system,... and did a clean install... didnt help.
Have you guys already found a solution for this problem?

Random Restart and Finding the culprit

Hi Everyone,
From past few days, I was facing random restart of my device. Whether I am watching Netflix, facebook or simply joining a new Wifi network. Even it restarts at night when I am sleeping. It was 100% random.
So I wiped (data & System) the phone and started from scratch. It worked for a day without restarting but today I am facing same issue.
I wanted to know is there a way to know why the device is restarting. Any logs we can capture? Since it is totally random I don't think LogCat would be feasible.
Please advice.
Device: Oneplus 6/64GB
OOS 10.3.2
Hii. Did it resloved? I am facing the same issue.
Have you tried the latest oneplus 6 official beta to see if the same behavior exists on beta?
Remember, this will completely wipe your device.. [emoji2] Good luck!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ONEPLUS A6003 using Tapatalk
No, I didnt tried to flash Beta.
It was working fine since I purchased the device (~ a year). Facing this issue since 2 weeks. Nothing major changed. Installed few non-play store apps here and there. Now all of them are uninstalled and still issue persists.
Is there any Solution? I am facing the same Problem with my OP6. Yesterday i tried a restart with the MSM Tool, and the i make a fresh install with Havoc. After 5 Hours i get reboots. It mostly appears when i plugged in the Power Cable, or touch longer on the black Screen.
Edith: For me i found a Solution. I flashed the blu_spark Custom Kernel. Now the past 5 Days no random Reboot!

Sticky Recovery

Hey everyone,
I have this issue with my device hopefully you know something about it: a while ago I rooted it, got Magisk on it all that. The device was just out so updates were still coming strong--or maybe I payed more attention to them than I do now, IDK--the case is that I accepted one of them and it undid the root and updated MIUI to something-something, regardless, since then I'm unable to flash a recovery image.
I thought the partitions got messed up or something and flashed the official system with the official Xiaomi spyware/adware suite "tools" hoping it would rewrite what needed rewriting then I tried flashing the recovery (TWRP) but no luck.
I'm using the XiaomiADBFastbootTools Java applet. It seemingly flashes the thing successfuly then it boots right into the system again, not in recovery. If I use force a recovery reboot through adb or with the buttons (which I've already forgot which were) the recovery the comes up is the official one, not TWRP.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Every time finishes "successfully", then the device reboots taking just tiny bit longer then I see the MIUI logo with the sort of paint-spill animation covering it and then I'm back on stupid Mars again (the stock pseudo-interactive wallpaper). Not even my information is lost--not that I'd want to, but at least it'd be something.
Since I removed most bloat the phone became pretty much useless and I wasn't even thorough because there's stuff that just can't be removed. Rooting would allow me to get some utility back out of it. Can it be fixed at all??

Question After using MSM Tool, all updates fail. Please help

I was trying to return the phone to stock after using the CalyxOS beta, I used MSM tool and it worked fine, I booted into OxygenOS and was like "great, it worked, no issues!" yeahhh I spoke too soon
Obviously the version of OxygenOS installed by MSM tool is very old, so I went to update. It downloaded, prompted me to reboot, the phone restarts, I open it up annd "Update failed, please try again"
Nothing I do works, although interestingly when I unlocked the bootloader I was able to update fine. But relocking the bootloader bricked the phone and I had to use MSM tool again. Does anyone know how I fix this? I searched but couldn't find this issue anywhere, obviously people have had update-related issues before, but nothing to do with MSM tool
Edit: the phone is model LE2115 btw
which msm tool did you use?
Index of /list/Unbrick_Tools/OnePlus_9/Global_LE25AA/R
Following this guide https://community.oneplus.com/thread/1541327
I reflashed with MSM tool, and without connecting to internet I sideloaded updates, I am able to update to 11.2.10.10, but it's everything after that will fail. It must be a problem with ColorOS. I'm going to connect to the internet and try a regular OTA update.
Still nope...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Maybe I just need to talk to OnePlus support..? I thought it was MSM being broken because I had never used it before, but now it looks like it's just the switch to ColorOS breaking things
I talked to OnePlus support, useless. They were just telling me to wait for a new update, but it will still have the same issue

Categories

Resources