My phone just received the January security update. See screenshot.
{
"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 LG-H910 using Tapatalk
haris163 said:
My phone just received the January security update. See screenshot.
Click to expand...
Click to collapse
Still 7.0......sigh...
Is it still ARB 0?
It's been giving me a real headache. I'm on stock rooted and don't want it. Downloaded automatically and resets my phone to recovery. Does some of the reset phone in 10 seconds thing. Anyone know where the ota is stored in root so I can delete it?
runningnak3d said:
Is it still ARB 0?
Click to expand...
Click to collapse
Yep. Already reset and dumped it.
Yeah it hosed my phone this morning and I had to do the dance to get to where I was.
Rooted and flashed LOS to my h910 right as I got the 10t software update notification. Got out of it. Until @runningnak3d gets ahold of 10t then.
texascbx said:
Yeah it hosed my phone this morning and I had to do the dance to get to where I was.
Click to expand...
Click to collapse
What exactly did you do? Still having to tiptoe around or it resets my phone. Even with auto update turned off.
Ryuk359 said:
What exactly did you do? Still having to tiptoe around or it resets my phone. Even with auto update turned off.
Click to expand...
Click to collapse
Use ti backup to disable the fota app and the software updater app. Should keep the notification from popping up. As for the file location it's under /cache and is the dlpkgfile. Should be about 70mb. Delete that and the stuff in the /cache/fota folder. For twrp loops manually rebooting to twrp from power off should fix it
toastyp said:
Use ti backup to disable the fota app and the software updater app. Should keep the notification from popping up. As for the file location it's under /cache and is the dlpkgfile. Should be about 70mb. Delete that and the stuff in the /cache/fota folder. For twrp loops manually rebooting to twrp from power off should fix it
Click to expand...
Click to collapse
Gotcha. I figured out the disabling in titanium. Had that done. And I wiped cache on twrp before hearing from you. There's no dlpkg in there or anything in the fota folder so that must've taken care of it. Thanks for the help sir.
If someone could get me the files from the cache and fota dirs before they wipe them, it would be appreciated. If the phone can decrypt them, then so can I -- or at least that is what I want to try.
For H910 users that are rooted, this is VERY important. When they finally release Oreo, they WILL increment ARB, and if we don't have a way to decrypt them, then no Oreo for us (and keep root).
-- Brian
Ryuk359 said:
What exactly did you do? Still having to tiptoe around or it resets my phone. Even with auto update turned off.
Click to expand...
Click to collapse
I had 10r no root but TWRP still working. So I went in and reflashed the 10r in the thread about rooting up to 10r. Then I downloaded the 10m firmware and Megarom along with the restock 1.3 kernel.
https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500
runningnak3d said:
If someone could get me the files from the cache and fota dirs before they wipe them, it would be appreciated. If the phone can decrypt them, then so can I -- or at least that is what I want to try.
For H910 users that are rooted, this is VERY important. When they finally release Oreo, they WILL increment ARB, and if we don't have a way to decrypt them, then no Oreo for us (and keep root).
-- Brian
Click to expand...
Click to collapse
Alright grabbed the entire fota folder and zipped it up. Hopefully has everything you need.
https://drive.google.com/open?id=1V8ArFzFzg6hwbeE88K5Xdw39aAjqi7Gv
Also if anyone has a link to the dumped 10t files that would be awesome to share. Looking to create a flashable zip to update myself.
If no one has posted a link to the 10t files, I will reset my H910 when I get my H918 back and dump them.
-- Brian
I use a python script to talk directly to lafd (the daemon that runs in download mode).
It is no different than using the patched LG UP, but I hate Windows
hawkeye29 said:
Rooted and flashed LOS to my h910 right as I got the 10t software update notification. Got out of it. Until @runningnak3d gets ahold of 10t then.
Click to expand...
Click to collapse
How is LOS running?
hawkeye29 said:
Rooted and flashed LOS to my h910 right as I got the 10t software update notification. Got out of it. Until @runningnak3d gets ahold of 10t then.
Click to expand...
Click to collapse
You don't have to worry about taking updates if you freeze the 2 update apps. FOTA and System Update I believe. I have the 2 frozen and haven't gotten an Ota notification for 10t.
My question is does this upgrade degrade performance? I assume this addresses spectre and meltdown vulnerabilities?
Sent from my [device_name] using XDA-Developers Legacy app
@runningnak3d I attempted to go back to full stock to update and grab us those 10t files. Don't know what happened but the full_stock 10q zip installation failed. Said reverted. tried multiple flashes and redownloads but no dice. Upon reboot I got thrown into the bootloop of corruption. Figured it was something with my custom twrp not flashing correctly so I rerooted, redownloaded and tried to flash it with twrp 3.1.1. Same thing. Zip failed and my phone got into a bootloop with the stock locked bootloader with no fastboot/recovery. Have no idea what is going on. Anyways rerooting for the second time and will not attempt that again. The whole return to stock method and dump for att updates is such a pain in the ass. Are there any reports of that full stock 10q zip failing or am I just doing something stupid?
Did you check the SHA hash?
Related
I am downloading an update that is 568.3 mb. GO GRAB IT!
{
"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"
}
Me too!
Manually went to update...
Update finally
AT LAST
Got it!!
5.1.1?
Pump your brakes
If this is the 5.1.1 update and you are rooted and enjoy a custom device. Please understand what this update means before flashing it.
http://forum.xda-developers.com/sprint-galaxy-s6-edge/help/dont-odin-5-1-1-t3136671
wildjeep said:
Pump your brakes
If this is the 5.1.1 update and you are rooted and enjoy a custom device. Please understand what this update means before flashing it.
http://forum.xda-developers.com/sprint-galaxy-s6-edge/help/dont-odin-5-1-1-t3136671
Click to expand...
Click to collapse
You are 100% correct my friend... I hate when people hurry up and jump on the update, then complain non stop they lost root and can't get it back....
Sent from my SM-G925V using Xparent Green Tapatalk 2
Soooperstar said:
5.1.1?
Click to expand...
Click to collapse
+1
If you upgrade to 5.1.1, you will not be able to root at this time
DO NOT ATTEMPT TO ROOT
I have been unsuccessful to go back to OE2 via odin, does someone have the recovery image for 5.1.1
If anyone has taken the update, please report back on whether TWRP and/or Cf autoroot works
Sent from my SM-G925P using Tapatalk
dhonzik said:
If you upgrade to 5.1.1, you will not be able to root at this time
DO NOT ATTEMPT TO ROOT
I have been unsuccessful to go back to OE2 via odin, does someone have the recovery image for 5.1.1
Click to expand...
Click to collapse
This is one of the compilations that has been warned for a few weeks now. It will take some time to achieve a stable Root/Recovery.
So if anyone is satisfied with stock. Unroot and flash away.
Or sit tight and wait for the custom development to catch up to the current stock software :highfive:
I will say, however, the device seems to run much smoother and early signs show battery improvement as well. Obviously it's early but it seems promising. Just wanted to share my stock experience as I chose to not root for the future payment platform
I updated but I am not root
no ram management .
If you take this update, you cannot root for the time being and certainly cannot Safe root (not tripping knox) with PingPoint root. In addition, you cant downgrade kernel, etc.
So the question becomes, what is the best course of action here. Can we PingPong root prior build, then update to OF7 kernel and rom once someone repacks them? Flash with FlashFire and maintain root? Then again, I guess we could accept the OTA and stay stock until CF-Auto Root is updated to work with it.
Either way, I'm holding for a bit here to see what shakes out...
UPDATE: thought about this a second. Sprint doesnt typically lock boot loader like AT&T, verizon. So this locked boot loader is whats preventing people from downgrading kernel once they update right? So this should not be an issue with Sprint if the boot loader is not locked?
Alpine- said:
If you take this update, you cannot root for the time being and certainly cannot Safe root (not tripping knox) with PingPoint root. In addition, you cant downgrade kernel, etc.
So the question becomes, what is the best course of action here. Can we PingPong root prior build, then update to OF7 kernel and rom once someone repacks them? Flash with FlashFire and maintain root? Then again, I guess we could accept the OTA and stay stock until CF-Auto Root is updated to work with it.
Either way, I'm holding for a bit here to see what shakes out...
UPDATE: thought about this a second. Sprint doesnt typically lock boot loader like AT&T, verizon. So this locked boot loader is whats preventing people from downgrading kernel once they update right? So this should not be an issue with Sprint if the boot loader is not locked?
Click to expand...
Click to collapse
Take a look at this thread: http://forum.xda-developers.com/sprint-galaxy-s6-edge/help/dont-odin-5-1-1-t3136671
It is not a looked boot loader that is the problem. T-Mobile solved it so I am sure it will be solved for us very soon.
wildjeep said:
This is one of the compilations that has been warned for a few weeks now. It will take some time to achieve a stable Root/Recovery.
So if anyone is satisfied with stock. Unroot and flash away.
Or sit tight and wait for the custom development to catch up to the current stock software :highfive:
Click to expand...
Click to collapse
Heads up the t-mobile TWRP recovery does get my bricked phone to the recovery, but the buttons do not work. If it did I had a backup I would have tried. Heading to the Sprint Store Tech Center to hopefully get a working phone or a replacement.
dhonzik said:
Heads up the t-mobile TWRP recovery does get my bricked phone to the recovery, but the buttons do not work. If it did I had a backup I would have tried. Heading to the Sprint Store Tech Center to hopefully get a working phone or a replacement.
Click to expand...
Click to collapse
So did the Sprint recovery not work?
How did you brick?
Sprint may not mess with it once the see the wrong recovery
Soooperstar said:
So did the Sprint recovery not work?
How did you brick?
Sprint may not mess with it once the see the wrong recovery
Click to expand...
Click to collapse
It was attempt to see if the CF Auto-Root would work after the update. I went back to other recovery that doesn't open up, if the tech center has the complete firmware maybe it will be to flash it back on. I opened a thread to see if someone can pull the stock recovery from the update. Trying to reflash back to OE2 fails.
dhonzik said:
It was attempt to see if the CF Auto-Root would work after the update. I went back to other recovery that doesn't open up, if the tech center has the complete firmware maybe it will be to flash it back on. I opened a thread to see if someone can pull the stock recovery from the update. Trying to reflash back to OE2 fails.
Click to expand...
Click to collapse
Did you try to Odin our twrp?
Soooperstar said:
Did you try to Odin our twrp?
Click to expand...
Click to collapse
Yes, it was a no go, $75 later I'll have a new phone in a week
I just got a prompt for a new OTA update, but being rooted and running a ROM I couldn't install it. It gave no new information about the update such as size or fixes. Anyone else get this? I'm on an OC3 based ROM by the way.
yea i got it
Seanbest said:
I just got a prompt for a new OTA update, but being rooted and running a ROM I couldn't install it. It gave no new information about the update such as size or fixes. Anyone else get this? I'm on an OC3 based ROM by the way.
Click to expand...
Click to collapse
It is the stage fright update
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Will we be able to flash it some other way?
ClearD said:
Will we be able to flash it some other way?
Click to expand...
Click to collapse
I'm sure there will be soon
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Well, on second thought, I just went ahead and let the update run. It completed. Everything appears normal.
I confirm, it is a fix for Stagefright. Baseband version went from I337UCUFNJ4 to I337UCUFNJ5
+ SuperSU is working properly.
Below: Before & After the update
{
"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"
}
New Update Came ..
https://www.att.com/esupport/softwareUpdateArticle.jsp?sid=KB419415&cv=820
ClearD said:
Well, on second thought, I just went ahead and let the update run. It completed. Everything appears normal.
Click to expand...
Click to collapse
Were you rooted with the Flashfire method?
Anytime AT&T or Samsung offer a "security" update FOTA, I cringe. I'm on rooted Lollipop and absolutely have to remain rooted to use Total Recall call recorder (you can't imagine how many times it's saved my ass with baseless promises from AT&T and other utility vendors), so I'm always hesitant to upgrade to any FOTA's that may make it more difficult to either flash a better ROM, or other utilities that it might block. Call me paranoid, but I'm going to hold off and try to find a better solution to threats to my OS. Belarc Security Advisor (Free) is highly respected, and a non-conventional system scan that identifies real threats. Running it yesterday and just now; show no threats. I realize that Stagefright is a threat, but I'm running antivirus software that I trust and keep my phone backed up locally on a regular basis.
billbillw said:
Were you rooted with the Flashfire method?
Click to expand...
Click to collapse
Well, I also let it run. Figured worst case, it would be rejected due to root. It ran, no errors, still on root (using Flashfire method). Stagefright detector now shows my device is safe.
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
nukesnooper said:
Anytime AT&T or Samsung offer a "security" update FOTA, I cringe. I'm on rooted Lollipop and absolutely have to remain rooted to use Total Recall call recorder (you can't imagine how many times it's saved my ass with baseless promises from AT&T and other utility vendors), so I'm always hesitant to upgrade to any FOTA's that may make it more difficult to either flash a better ROM, or other utilities that it might block. Call me paranoid, but I'm going to hold off and try to find a better solution to threats to my OS. Belarc Security Advisor (Free) is highly respected, and a non-conventional system scan that identifies real threats. Running it yesterday and just now; show no threats. I realize that Stagefright is a threat, but I'm running antivirus software that I trust and keep my phone backed up locally on a regular basis.
Click to expand...
Click to collapse
If you're using the Stock AT&T Lolipop, and Flashfire method for rooting, you will be OK to let the update run. It ran with no issues for me and it kept root.
billbillw said:
Well, I also let it run. Figured worst case, it would be rejected due to root. It ran, no errors, still on root (using Flashfire method). Stagefright detector now shows my device is safe.
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
If you're using the Stock AT&T Lolipop, and Flashfire method for rooting, you will be OK to let the update run. It ran with no issues for me and it kept root.
Click to expand...
Click to collapse
That's exactly how I did it. My only concern is that it may install patches that could further restrict future modifications.
I also just completed running Lookout and it found no threats or vulnerabilities. I'm staying where I am until I hear more feedback.
Thanks for your advice. I'll be keeping an eye on it.
It's coming in as a 280mb download, I'm going to see what happens with root (previously used Flashfire)
sim_pl said:
It's coming in as a 280mb download, I'm going to see what happens with root (previously used Flashfire)
Click to expand...
Click to collapse
Please Upload .cfg File For Update My Device .. That OTA File /cache .. Check It And Upload It Please And Check fota Folder
UPDATED POST:
I upgraded with the install stock but "keep root" method, using flashfire...
The update failed at 29%.
I did a factory reset, and it still failed at 29%...
What are my options now?
Update:
I used Flashfire to install the tethering addon... I wonder if that is the culprit.
Installing without thethering... will update with results.
And It's a pain to download that ATT update each time. --- Their servers are SLOW!
Same story here. Update stops and phone reboots about a third of the way through. Defrosted all Samsung/AT&T bloat and tried again. Same story. Bummer.
I rooted my wife's 0C3 with Kingroot and tried to take the update. It failed.
Maybe I should try again since I just used triangle away to get rid of the "custom" nag at boot.
Rockin' a l337 with Goldeneye v49.1 + Wanam Xposed and loving life on AT&T's 4G LTE network
billbillw said:
Were you rooted with the Flashfire method?
Click to expand...
Click to collapse
Yes. Rooted with flashfire, on oc3 bootloader. I ran the update through the normal OTA method, not trying to install it through flashfire. It worked fine and root stayed normal. Verified when titanium backup ran last night on its normal schedule.
Well, it updated fine, using just the straight rooted rom, no additional flashes. No more fails at 29%...
It appears that adding in anything extra, de-bloat, hotspot enable, etc. will cause the update to fail.
/sk
Reinstalled the rooted stock ROM and the update worked fine. Still have root. All is groovy.
Today I had a software update and come to figure out it was 6.0!!!
{
"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"
}
nice man.
are you using at&t sim and currently in america? because i am in asia and i unlocked my phone!
so i barely get any update thing. they say to use at&t sim if i have to update. alas! do tell please
---------- Post added at 09:02 PM ---------- Previous post was at 08:56 PM ----------
plus if some one has zip for MM for lg d850 i will thankful
issues after mm upgrade
Here's what I experienced after update...
Once you upgrade you can't flash back to stock. LG flash tool fails because it couldn't detect the model. After setting up McAfee it disables root and usb debugging. You have to go into McAfee and turn those options off. So it seems like once you go to mm you can't get back to lollipop. I'm also having proximity sensor issues also with the screen going black during a call. I guess once we can get root I'll be able to install another rom.
Hi, I got the notification and I was not in WiFi network so decided to cancel it and check it again once I got to wifi zone. But when I checked next time, I just get a message, your phone is uptodate. I tried rolling date forward to circumvent the 24 hour check, but no luck. Any ideas to get the update notification back ?
no luck updating
tried the update today, it just sends me to twrp recovery screen every time
You can't install a factory update while rooted. Come on guys you should know this.
Sent from my LG-D850 using XDA-Developers mobile app
Update
vishnugs said:
Hi, I got the notification and I was not in WiFi network so decided to cancel it and check it again once I got to wifi zone. But when I checked next time, I just get a message, your phone is uptodate. I tried rolling date forward to circumvent the 24 hour check, but no luck. Any ideas to get the update notification back ?
Click to expand...
Click to collapse
I had the same thing happen to me so what I did to make the phone think I haven't checked for an update and avoid the 24 hour wait I did a hard reset. I want to point out that I didn't care much about all my apps being deleted and you might want to back them up. Note: I was on stock lollipop
Anyone do an adb pull and extract the modem yet? Want to flash it on Fulmics 5.0.
Sent from my LG-D850 using Tapatalk
DARKCHYLDX101 said:
Anyone do an adb pull and extract the modem yet? Want to flash it on Fulmics 5.0.
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
Please let us know if you get it accomplished.
louvass said:
Here's what I experienced after update...
Once you upgrade you can't flash back to stock. LG flash tool fails because it couldn't detect the model. After setting up McAfee it disables root and usb debugging. You have to go into McAfee and turn those options off. So it seems like once you go to mm you can't get back to lollipop. I'm also having proximity sensor issues also with the screen going black during a call. I guess once we can get root I'll be able to install another rom.
Click to expand...
Click to collapse
Not sure if there is an "anti roll back" But You cannot use flashtools once updating to Lollipop you must use LGUP.
hyelton said:
Not sure if there is an "anti roll back" But You cannot use flashtools once updating to Lollipop you must use LGUP.
Click to expand...
Click to collapse
Where do I get a KDS for the 850 along with the LGUP, seems everything points to the 855? thanks. I can't seem to root after the upgrade to 6.
louvass said:
Where do I get a KDS for the 850 along with the LGUP, seems everything points to the 855? thanks. I can't seem to root after the upgrade to 6.
Click to expand...
Click to collapse
Its KDZ. the D850 is TOT method only.
My Guide:
http://forum.xda-developers.com/showthread.php?t=2785089
But remember its your own risk, not sure if downgrading will brick or not yet from MM on the AT&T Model.
FWIW, if you're experiencing DND issues after the 6.0 update check settings > dnd > advanced > schedule. kept noticing on my moto360 it was switching to dnd for no reason. turns out some scheduling magically appeared. been running 6.0 without a hitch since last night. had to manually disable at&t video calling and a few other things but im happy with it thus far.
cjoeone said:
I had the same thing happen to me so what I did to make the phone think I haven't checked for an update and avoid the 24 hour wait I did a hard reset. I want to point out that I didn't care much about all my apps being deleted and you might want to back them up. Note: I was on stock lollipop
Click to expand...
Click to collapse
I tried doing a factory reset after spending a lot of time to back up data. But after fresh restore, I'm getting the message that your phone is uptodate. I m cursing myself why I dismissed the prompt yesterday. Any other solutions to force update ?
hyelton said:
Its KDZ. the D850 is TOT method only.
My Guide:
http://forum.xda-developers.com/showthread.php?t=2785089
But remember its your own risk, not sure if downgrading will brick or not yet from MM on the AT&T Model.
Click to expand...
Click to collapse
Thanks yes I know how to use the flash tool...my problem is it fails every timeI try going back to stock lollipop.
vishnugs said:
I tried doing a factory reset after spending a lot of time to back up data. But after fresh restore, I'm getting the message that your phone is uptodate. I m cursing myself why I dismissed the prompt yesterday. Any other solutions to force update ?
Click to expand...
Click to collapse
You have to do a hard reset through stock recovery. Don't do it if you are using a custom rom. If you are not experienced I recommend you wait to see if you get another update notification
louvass said:
Thanks yes I know how to use the flash tool...my problem is it fails every timeI try going back to stock lollipop.
Click to expand...
Click to collapse
That is because flashtool you cannot use if your on MM you use LGUP with the TOT file.
hyelton said:
That is because flashtool you cannot use if your on MM you use LGUP with the TOT file.
Click to expand...
Click to collapse
Can you send me a link for it thanks man..i got it thanks
louvass said:
Can you send me a link for it thanks man..i got it thanks
Click to expand...
Click to collapse
It's in the 2nd post of my guide in the link I posted earlier ^^ but just remember at your own risk as I haven't seen anyone try yet. Example like the G4 after a certain point people bricked there AT&T model from downgrading. But if you do risk it and everything went smoothly let us all know!
cjoeone said:
You have to do a hard reset through stock recovery. Don't do it if you are using a custom rom. If you are not experienced I recommend you wait to see if you get another update notification
Click to expand...
Click to collapse
No luck, tried hard reset through recovery twice and before that general reset several times. I'm not getting the notification for the second time
Any other ways to force update ?
Hi, i got samsung tab s7 and it auto downloaded the update to android 12 and now it says that I can postpone it 9nly 3 times. Is there a way to get rid of it? I wouldn't be able to use the color calibrator app once it will get the update, which makes the tablet pretty useless for me. Thanks
Clear the system cache... I never tried it but was told that would clear it.
blackhawk said:
Clear the system cache... I never tried it but was told that would clear it.
Click to expand...
Click to collapse
blackhawk said:
Clear the system cache... I never tried it but was told that would clear it.
Click to expand...
Click to collapse
Thanks, I'll give it a try. How do I do a system cache clean?
sltwtr said:
Thanks, I'll give it a try. How do I do a system cache clean?
Click to expand...
Click to collapse
It's on the boot menu. Not sure for that device.
It can be a little tricky if you don't get the timing and button sequence right.
It would have been better to force power off the phone before it completed the download. Perhaps using ADB editing you could kill it. Not sure if disabling OTA updates now would stop it but that be worth a shot.
If it updates you may be able to flash it back to 11 if it doesn't upgrade the boot loader too.
You may want to see if someone has a better, more detailed plan. I always keep OTA updates package blocked. Package Disabler can be used to kill updates, that might be the easiest way.
OTA updates...
{
"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"
}
blackhawk said:
It's on the boot menu. Not sure for that device.
It can be a little tricky if you don't get the timing and button sequence right.
It would have been better to force power off the phone before it completed the download. Perhaps using ADB editing you could kill it. Not sure if disabling OTA updates now would stop it but that be worth a shot.
If it updates you may be able to flash it back to 11 if it doesn't upgrade the boot loader too.
You may want to see if someone has a better, more detailed plan. I always keep OTA updates package blocked. Package Disabler can be used to kill updates, that might be the easiest way.
OTA updates...
View attachment 5567769
Click to expand...
Click to collapse
Thank you vm. Ckearing cache didnt work, theres still a scheduled update. I thought to try and reset the tablet (its still running android 11) and not to connect it to the wifi before ill disable the auto software updates in the settings. You think it might work or is it possible that after ill reset it, it will upgrade itself?
Btw, are there any drawbacks if ill flash it back to android 11? (security-wise, warranty-wise etc')
sltwtr said:
Thank you vm. Ckearing cache didnt work, theres still a scheduled update. I thought to try and reset the tablet (its still running android 11) and not to connect it to the wifi before ill disable the auto software updates in the settings. You think it might work or is it possible that after ill reset it, it will upgrade itself?
Btw, are there any drawbacks if ill flash it back to android 11? (security-wise, warranty-wise etc')
Click to expand...
Click to collapse
Sorry that didn't work.
Try disabling the update app itself.
You can roll back to 11 as long as it doesn't update the bootloader to a new version.
No warranty implications unless you root it.
Security isn't an issue. I'm running on Pie.
blackhawk said:
Sorry that didn't work.
Try disabling the update app itself.
You can roll back to 11 as long as it doesn't update the bootloader to a new version.
No warranty implications unless you root it.
Security isn't an issue. I'm running on Pie.
Click to expand...
Click to collapse
What do you mean by disabling the app itself? What app?
How can i tell if it uploaded the bootloader?
Will i still have all the samsung features and apps?
Can you refer me to a reliable guide for downgrading?
Sorry for all the questions, thank you
sltwtr said:
What do you mean by disabling the app itself? What app?
How can i tell if it uploaded the bootloader?
Will i still have all the samsung features and apps?
Can you refer me to a reliable guide for downgrading?
Sorry for all the questions, thank you
Click to expand...
Click to collapse
My previous post shows the app in it com.wys... whatever. Install package disabler and see if that can kill the install. It probably can.
If you end up on 12... deal with that then.
I recommend you do everything you can to keep it from installing... tick-tock Mr. Wick, no time to dilly dally.
blackhawk said:
My previous post shows the app in it com.wys... whatever. Install package disabler and see if that can kill the install. It probably can.
If you end up on 12... deal with that then.
I recommend you do everything you can to keep it from installing... tick-tock Mr. Wick, no time to dilly dally.
Click to expand...
Click to collapse
I ended up doing a factory reset. I didn't connect it to wifi at first and disabled auto update in the setting. So far it seems to work. Thank you
sltwtr said:
I ended up doing a factory reset. I didn't connect it to wifi at first and disabled auto update in the setting. So far it seems to work. Thank you
Click to expand...
Click to collapse
You're welcome.
Yay. Glad you were about to kill it.
Thank you for that information about the cache fix being invalid.
Just got an alert from Oxygen Updater (I was checking it earlier to see if the update was available yet and it wasn't but I guess it is now lol)
{
"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"
}
I am not sure I really want to try it since that would involve flashing away from StagOS but I may try it later. Have a date I'm getting ready for at the moment so not a good time to mess with it lol.
I have a global op9 and rolled back to A11. Guessing I probably need to be on at least C-48 to get new C-61 build. Only 48 available ota or oxygen updater ?
mattie_49 said:
I have a global op9 and rolled back to A11. Guessing I probably need to be on at least C-48 to get new C-61 build. Only 48 available ota or oxygen updater ?
Click to expand...
Click to collapse
Since it's an incremental build you would have to be on C.48. Also, Oxygen Updater won't show it if you are rooted and don't deny it root access.
EtherealRemnant said:
Since it's an incremental build you would have to be on C.48. Also, Oxygen Updater won't show it if you are rooted and don't deny it root access.
Click to expand...
Click to collapse
It's a really nice build. Many small things I couldn't hardly deal with are getting fixed. Ability to deny privilges or disable main system apps is available now. Clear all recents works properly. Misaligned home screen clock. It's nice bud. Outta try it out.
mattie_49 said:
It's a really nice build. Many small things I couldn't hardly deal with are getting fixed. Ability to deny privilges or disable main system apps is available now. Clear all recents works properly. Misaligned home screen clock. It's nice bud. Outta try it out.
Click to expand...
Click to collapse
Until I can disable their SoC throttling without performance mode draining my battery, I'll never be happy with stock unfortunately. It's literally the biggest complaint I have with OOS12.
Glad that they are finally improving it though.
EtherealRemnant said:
Until I can disable their SoC throttling without performance mode draining my battery, I'll never be happy with stock unfortunately. It's literally the biggest complaint I have with OOS12.
Glad that they are finally improving it though.
Click to expand...
Click to collapse
Did they fix SoC throttling issue in C.61? How is performance and smoothness compare to C.48.
break.cold said:
Did they fix SoC throttling issue in C.61? How is performance and smoothness compare to C.48.
Click to expand...
Click to collapse
I highly doubt they fixed it because their official stance is that it's not broken and to use performance mode.
EtherealRemnant said:
I highly doubt they fixed it because their official stance is that it's not broken and to use performance mode.
Click to expand...
Click to collapse
I have no idea what Oneplus is doing with their software, it has become so crumbled that doubt have raised in user mind before using it. I really enjoyed OOS11 alot but since OOS12 released with bugs here and there, I really don't to stay on OOS12, however, I only used because of camera
I'm rooted on LE2115_11_C.48
When I try to install (with the plan of retaining root via step 4 of the OP here: https://forum.xda-developers.com/t/...apply-root-to-the-phone.4263811/post-84858863) I just get an error "Couldn't Update Installation Problem".
The "try again" button does the same thing.
Thoughts? Anyone else rooted able to update?
arebelspy said:
I'm rooted on LE2115_11_C.48
When I try to install (with the plan of retaining root via step 4 of the OP here: https://forum.xda-developers.com/t/...apply-root-to-the-phone.4263811/post-84858863) I just get an error "Couldn't Update Installation Problem".
The "try again" button does the same thing.
Thoughts? Anyone else rooted able to update?
Click to expand...
Click to collapse
arebelspy said:
I'm rooted on LE2115_11_C.48
When I try to install (with the plan of retaining root via step 4 of the OP here: https://forum.xda-developers.com/t/...apply-root-to-the-phone.4263811/post-84858863) I just get an error "Couldn't Update Installation Problem".
The "try again" button does the same thing.
Thoughts? Anyone else rooted able to update?
Click to expand...
Click to collapse
You need to restore original boot.img through magisk app and then do OTA update or use local update method by download the OTA zip file (check ot method 2 on how to root in xda oneplus 9 form) and then updating it through Oneplus 12 local update app.
break.cold said:
I have no idea what Oneplus is doing with their software, it has become so crumbled that doubt have raised in user mind before using it. I really enjoyed OOS11 alot but since OOS12 released with bugs here and there, I really don't to stay on OOS12, however, I only used because of camera
Click to expand...
Click to collapse
Yeah this was my first OnePlus and it may well be my last because of the throttling. It really irks me. Like they go so far as to make it impossible to actually disable in OOS12.
arebelspy said:
I'm rooted on LE2115_11_C.48
When I try to install (with the plan of retaining root via step 4 of the OP here: https://forum.xda-developers.com/t/...apply-root-to-the-phone.4263811/post-84858863) I just get an error "Couldn't Update Installation Problem".
The "try again" button does the same thing.
Thoughts? Anyone else rooted able to update?
Click to expand...
Click to collapse
Open Magisk, hit uninstall, hit restore images. Install the OTA and before rebooting, install to inactive slot.
arebelspy said:
I'm rooted on LE2115_11_C.48
When I try to install (with the plan of retaining root via step 4 of the OP here: https://forum.xda-developers.com/t/...apply-root-to-the-phone.4263811/post-84858863) I just get an error "Couldn't Update Installation Problem".
The "try again" button does the same thing.
Thoughts? Anyone else rooted able to update?
Click to expand...
Click to collapse
First off it's a Google ota. If any partitions are modified the intended update will fail. Go into magisk . In red uninstall magisk. Then restore images. Let that finish and don't reboot. Go into system updates and start ota. Will now work stock boot image there. Allow update to completely install. Don't reboot. Then go into magisk again like second photo. Install to inactive. Now reboot after this process . Reboot into new oos with root . Gl
Haha, thanks for the replies all! So quick
I'll reread them all a few times to wrap my head around.
Am I going to have any data loss?
arebelspy said:
Haha, thanks for the replies all! So quick
I'll reread them all a few times to wrap my head around.
Am I going to have any data loss?
Click to expand...
Click to collapse
No
EtherealRemnant said:
Open Magisk, hit uninstall, hit restore images.
Click to expand...
Click to collapse
mattie_49 said:
Go into magisk . In red uninstall magisk. Then restore images.
Click to expand...
Click to collapse
"Stock backup does not exist."
Have I already f'd up?
arebelspy said:
"Stock backup does not exist."
Have I already f'd up?
Click to expand...
Click to collapse
If you don't have a stock backup, it's not that big of a deal. Uninstall Magisk and install the OTA.Take the clean C.61 boot image and copy to the phone, open Magisk, patch, copy to PC, fastboot boot patched image, open Magisk again, direct install.
mattie_49 said:
First off it's a Google ota. If any partitions are modified the intended update will fail. Go into magisk . In red uninstall magisk. Then restore images. Let that finish and don't reboot. Go into system updates and start ota. Will now work stock boot image there. Allow update to completely install. Don't reboot. Then go into magisk again like second photo. Install to inactive. Now reboot after this process . Reboot into new oos with root . Gl
Click to expand...
Click to collapse
for me it says that backup was not found when hitting restore images. so i suppose u need to have a backup for this to work
Vladgabriel3 said:
for me it says that backup was not found when hitting restore images. so i suppose u need to have a backup for this to work
Click to expand...
Click to collapse
EtherealRemnant said:
If you don't have a stock backup, it's not that big of a deal. Uninstall Magisk and install the OTA.Take the clean C.61 boot image and copy to the phone, open Magisk, patch, copy to PC, fastboot boot patched image, open Magisk again, direct install.
Click to expand...
Click to collapse
even if u fully uninstall magisk when u press install ota it will say failed or something like that.