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?
Related
This evening I connected my phone to WiFi and I have been notified about an update. I have a Vodafone-locked handset.
This is my current phone version:
{
"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"
}
Has anyone else received this update today? Anyone know what is included in this update?
I shall download and install the update now and then post back my phone version page in this thread...
No replies? Huh, ok?
Anyway, this is what the update said it was:
And this is my version after the successful update (took about 10 minutes):
This is what I received this morning on my c625a (unlocked):
Yip i received this update last night too, appears to be a firmware & bootloader update, not os, so will need to see what the update has 'fixed'. Hopefully related to random reboots but that is unknown at this time.
Lets test and find out
btw, carrier unlocked 8x.
http://forum.xda-developers.com/showthread.php?t=2240186
stuck on update screen
I've tried to install this update but the it was stuck on the update screen with the two cogs rotating... If I turn off the phone it reboots itslf imediately and goes directly to this same screen... I can't turn my phone off and can't even do a hard reset!!
Any help?
Does anyone have battery problems after this update? It seems to me that after installing there is much more battery draining. Connection seems to be improved.
Edit : seems that the battery drain is gone after I disabled some background apps.
Looks like the htc update is a step forward in the good direction. Overall satisfied with my device.
Battery drain appears to be worse post-update; however it could be Kik Messenger. Not noticed anything else beneficial though.
Sent from my Windows Phone 8X by HTC using Board Express
Hey guys,
I have a big problem with my Mate 8. My build number was NXT-L29 C636 B170 and I never got any updates, because I was using this asian build with a european SIM-card. Because of these annoying notification bugs B170 has and because I was about to factory reset my phone I thought about updating it manually.
Tried to understand how all this works and started to do a small OTA update first to test if it's that easy. With the B180 from the screenshot of FF below I easily managed to update my phone.
What I tried next is to go to Android 7.0, so I used the selected blue FullOTA-MF-PV. My phone updated successfully and works really smooth, but now I see "NRD90M test-keys" as build number. I read a lot of bad things about this version because it seems to be a really early and bugged beta version and thats not what I need. I already wanted to try a factory reset but also read that you should completely avoid doing that.
I want to go back before anything unsuspected happens to my phone. My updater has gone, so I cannot install anything else. Can anyone explain for a newbie how to get back to my previous build?
Was it wrong to use the PV version?
What I want to reach then is an updated version of my phone software as a stable version.
Hope anyone can save my phone
Thanks in advance
{
"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"
}
What...
{
"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"
}
For what it's worth, I can't test the update myself because hours after posting this thread, my beloved LG Flex2 died.
Sometimes there's only a few lines on the screen, sometimes it boots in QHUSB 9008 mode, oftentimes it boots a little bit but then dies, etc.
The same here - with this update it was getting slower and slower. Finally today my LG G Flex 2 died - it didn't boot anymore.
Mine is fortunately still alive and i did the update but didn't really see much difference in performance and whatnot?!? Update didn't even include newer security level which is odd. I guess this update just improved something that is not very visible for common user like me. Well, update is update and i was glad to see this model isn't totally abandoned by LG
Carmanen said:
Mine is fortunately still alive and i did the update but didn't really see much difference in performance and whatnot?!? Update didn't even include newer security level which is odd. I guess this update just improved something that is not very visible for common user like me. Well, update is update and i was glad to see this model isn't totally abandoned by LG
Click to expand...
Click to collapse
Got the update also. I think it was just for new eu privacy law.
Nothing much changed.
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??
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.