Database Develop

[Q] ATT Update to 5.0.1 fails, confirming a solution

It has been over a year since I last flashed a S4A phone, so refreshing my notes and hoping someone can confirm the bits below are correct.
In case another, shorter way to accomplish same exists, kindly suggest it.
Background first.
Phone is SG4 Active, running Android 4.4.2. Baseband I537UCUCNH3, model is Samsung SGH I537, Build KOT49H.I537UCUCNH3
Phone is unlocked and was flashed with Odin one year ago to 4.3 and then ATT updated automatically to current version.
Status today.
When ATT offers download and install the 900 plus MB 5.0.1 update, it fails at 27 percent, reboots phone, repeatedly.
Phone has about 8 GB free space on internal memory and about 10 GB on SD card. As far as I can determine, no special mods have been done to phone and I have uninstalled all user installed apps so it has only ATT, Samsung and Google apps.
Proposed solution.
Found the original I537UCUBML2 bundle *2gb* (Android 4.3) with BL,AP,CSC,CP and I think that since Bootloader already installed, it should be possible to run Odin again and just flash AP,CSC and CP.
Once flashed the system will be back to 4.3 and the OTA updates should work, first to 4.4 and later to 5.0.1.
Can not recall right now just how to do the Odin flash but will use search to figure it out but is my thinking correct or am I missing something important ? For example, don't remember if I have to reboot phone first or if Odin handles it all once the USB cable is connected.
Thank you.

xdafly said:
It has been over a year since I last flashed a S4A phone, so refreshing my notes and hoping someone can confirm the bits below are correct.
In case another, shorter way to accomplish same exists, kindly suggest it.
Background first.
Phone is SG4 Active, running Android 4.4.2. Baseband I537UCUCNH3, model is Samsung SGH I537, Build KOT49H.I537UCUCNH3
Phone is unlocked and was flashed with Odin one year ago to 4.3 and then ATT updated automatically to current version.
Status today.
When ATT offers download and install the 900 plus MB 5.0.1 update, it fails at 27 percent, reboots phone, repeatedly.
Phone has about 8 GB free space on internal memory and about 10 GB on SD card. As far as I can determine, no special mods have been done to phone and I have uninstalled all user installed apps so it has only ATT, Samsung and Google apps.
Proposed solution.
Found the original I537UCUBML2 bundle *2gb* (Android 4.3) with BL,AP,CSC,CP and I think that since Bootloader already installed, it should be possible to run Odin again and just flash AP,CSC and CP.
Once flashed the system will be back to 4.3 and the OTA updates should work, first to 4.4 and later to 5.0.1.
Can not recall right now just how to do the Odin flash but will use search to figure it out but is my thinking correct or am I missing something important ? For example, don't remember if I have to reboot phone first or if Odin handles it all once the USB cable is connected.
Thank you.
Click to expand...
Click to collapse
ML2 won't help you. If you give me about 5-10 minutes I'll link you to the file you need (I'm slow because I'm on mobile and it's a tiny screen for my fat fingers lol)
---------- Post added at 02:43 PM ---------- Previous post was at 02:37 PM ----------
OK here is the file you need. Download and save it to your EXTERNAL SD card (internal storage won't work) and flash the file in stock recovery. You can boot to recovery by shutting the phone off, then holding down power and vol+simultaneously
If you want to be rooted, don't do this, I can point you to a different method

Ok, downloading. Now, in case this "manual method" also fails at 27 percent and just reboots with Install failed, what then ? That was the original reason I proposed to use Odin re-flash the SG4A back to some semblance of original state. Thank you.

xdafly said:
Ok, downloading. Now, in case this "manual method" also fails at 27 percent and just reboots with Install failed, what then ? That was the original reason I proposed to use Odin re-flash the SG4A back to some semblance of original state. Thank you.
Click to expand...
Click to collapse
Use Odin to restore NE3 kit kat instead of ML2. I can link to that too if you need
NE3 kit kat
You have to extract all 4 tar files and flash all 4 with Odin simultaneously

xdafly said:
Ok, downloading. Now, in case this "manual method" also fails at 27 percent and just reboots with Install failed, what then ? That was the original reason I proposed to use Odin re-flash the SG4A back to some semblance of original state. Thank you.
Click to expand...
Click to collapse
The reason your install is failing is because you've modified the stock firmware. When you try to install an AT&T update, manually or automatically there is a script in that update that checks all the files on your phone to ensure that they are the original, unmodified files. If any single one of them is not original or modified, then the update will fail as you have experienced. So if you root your phone you are modifying system files. Even if you unroot, the system files were still modified at one point and the update will fail. I suspect you've done something like this.
The only way you can update to stock OC6 (5.0.1) is to flash your phone back to stock firmware and in your case it should be NE3. As has been explained you will need to flash the NE3 Odin package, but beware this will completely wipe your phone so backup anything you don't want to lose. There is a method for updating your phone without flashing back to stock described in this thread. Also, if you're ever looking for information on rooting and updating your phone it would be a good idea to familiarize yourself with the links in the i537 Firmware Guide.

Use Odin to restore NE3 kit kat instead of ML2.
Click to expand...
Click to collapse
Got it. Downloading (as suspected, the update.zip failed) and will hook up cable and run Odin 3.09 with all 4 files
All important data is backed up to Google so unless I lose some ATT settings, such as the IMEI code or similar, all should be well
Does the phone have to be in recovery mode before starting Odin ? Can't remember now and all Youtube videos show only AP being applied, not all 4 files simultaneously.
Edit, read http://www.samsungodindownload.com/odin-tutorial/
Thank you

BL file to bootloader (BL), CP file to phone (CP), CSC file to CSC, like below:
{
"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"
}

EXAMPLE How to install a CUSTOM ROM without tripping Knox 0x000 5.1.1 920T.

I decided to create a Thread because there were to many people asking how to Install a Custom ROM using the engineered bootloader and not tripping knox. (I Will not provide links to the Bootloader i already provided the MD5 number to compare so search on google)
I used to have Rapture 2.0 that is based on COF8(I UPDATED to Rapture 2.1 Have wificalling but didn't have time to UPLOAD pictures because i changed to XtreStolite 2.2) and i still have this method. KNOX 0x000.
I don't own any of this files, i just recompiled from the forum. All thanks to the developers and their respective work. (Aou's, g.lewarne and iB4STiD and Others). I REPEAT i don't own any of the files so don't ask for files if they get removed.
Flash it at your own Risk, I am not responsible if you damage your phone or don't follow instructions. Just tested on 920T and 925T tmobile variant and it works. YOU MUST use the engineer bootloader or you will trip knox. Fingerprint and Miracast not working.
{
"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 used this Method:
DOWNLOAD These first:
Download ODIN3 3.10.6 from Here
Download Samsung USB Drivers from HERE
IF you are on 5.0.2 AOCG you must first UPDATE to COF6 from here and not FULL COF8 so you can get back to COF6 if needed. COF8 have more benefits but you still don't know.
STEPS:
1. OPEN ODIN and select AP and choose the 5.1.1 COF6 mentioned before.(Make sure RE-Partition is not selected in options. ONLY Auto Reboot and F. Reset Time) Wait until it verify.
2. Click on START and wait until your PHONE reboot(Never turn it off before it finishes)
3. After phone reboot continue bellow.
Before you do this make sure to ENABLE OEM Unlocking ON, on the Developer Options. (To enable Developer Options, go to Settings/About Device and After tapping the build number 7+ times, you will be notified you are a developer and the option will be there Settings/Developer Options)
1. Flash sboot.bin for you model. (Odin Select BL) Search on Google
S6 920T MD5: 6F8D0372CDF94A5B95B8034B7641E132
S6 925T MD5: 528F23A8138BF6570D1BAE0857B916E4
2. Flash Latest Unikernel from here (AP Odin , To give SE permisive) (Thanks to g.lewarne) Have the In Audio call fixed.
3. Odin-flashable TWRP recovery that Aou's put together (AP Odin) (Original Thread Here) (Thanks to Aou's)
4. Make a full Backup on TWRP just in Case. (Beware Touch screen will be Inverted on TWRP)(Right is left and left is right)
5. Go to REBOOT on TWRP and select DOWNLOAD , Open ODIN Select CP and Flash the G920T_UVU2COF8_BASEBAND.tar.md5. (Original Thread here) (Thanks to iB4STiD)
6. Go into TWRP WIPE/Advance WIPE and select dalvik cache, cache, data, system r/w (DON'T Select Internal Storage) Swipe to wipe.
7. Install Rapture 2.1 from Here. (Original Thread here) (Thanks to iB4STiD)
8. WIPE, Swipe Factory Reset
9. Wait 5-10 minutes first boot.
10. MAKE SURE to ENABLE AGAIN OEM Unlocking like you did the first time before you started the process so you don't have a problem later on with FRP LOCK.
11. ENJOY !!
It is recommended to Charge your phone to 100% and use a Battery Calibration, Restart your phone wait until it boots and remove the charger. Let it discharge until it turns off. Charge it again without interruption up to 100% and remove the charger and use it normally so the battery and system adapts.
In case of any problems you can Wipe and Restore from TWRP or ODIN STOCK 5.1.1 COF8 from HERE to fix any problems.
If you are on firmware COF6 with ONLY COF8 MODEM use the COF6 Odin from here.

Thanks for the write-up! Could you add how you updated from 5.0.2 to COF6? Its too bad fingerprint scanner doesn't work.

Billyvnilly said:
Thanks for the write-up! Could you add how you updated from 5.0.2 to COF6? Its too bad fingerprint scanner doesn't work.
Click to expand...
Click to collapse
Srry for the delay, i added it today the steps. I have been very busy lately creating a Custom ROM and kernel testing it.

Am I able to flash any custom rom using this method and still retain my warranty?

I flashed the ROM in the OP but now I have no sound making phone calls or receiving them.

GeorgeNYer said:
Am I able to flash any custom rom using this method and still retain my warranty?
Click to expand...
Click to collapse
Did you read the OP?
sent from my Hyperdrive powered G Note 10.1

The Apostle said:
Did you read the OP?
sent from my Hyperdrive powered G Note 10.1
Click to expand...
Click to collapse
I'm just double checking, so can I?

Deleted

GeorgeNYer said:
I'm just double checking, so can I?
Click to expand...
Click to collapse
Did you flashed the Unikernel or Unistock latest? If not that is the audio problem.Yes it works with any released Custom rom. Currently i am using latest XtreStoLite Deo-Mod Edition 2.2 [478MB ○ BOGG](Thanks to edgarf18) and if you care for wifi calling xtrestolie doesnt have it. But you can install talkatone(example) can be any app that give you a US number and call fowarding to it when you dont have signal and have wifi and works the same.
Remember sboot or engi bootloader is for 920t or 925t.

It works now after flashing unikernel v6-0001rb. Thank you for finding a way go install custom roms without tripping Knox!!! Now there's still no way no make the fingerprint scanner to work?

GeorgeNYer said:
It works now after flashing unikernel v6-0001rb. Thank you for finding a way go install custom roms without tripping Knox!!! Now there's still no way no make the fingerprint scanner to work?
Click to expand...
Click to collapse
Nop there is no way. I am currently making a hybrid custom rom sometimes it works and sometime cratches... The problem lies in the bootloader invoking it a little diferent because its a 5.0.2 bootloader.

[MY SCREEN IS OPPOSITE] I may have installed something for the Edge variant, although I got lost in trying to get back to stock, which I currently am back at. (5.1.1)
So.... hoping this gets seen, I might xpost over to another thread, but here it goes.....
Notes: 5.1.1
920T model
Ultimately I am trying to get Alliance on my S6 (920T), and no I don't care if the know counter gets tripped (*spoiler* already done)
I started trying to get root for alliance ROM, and got the samsung splash lock after using odin to root. After re-loading the 5.1.1 firmware everything was working again, so I tried this *example* thread on how to install alliance again. After following things around and now have bizzaro phone, to where the opposite sides of the screen need to be pressed for the corresponding action, I am looking for help.....

What about aroma installer roms, can I flash them using this method without tripping the Knox counter?

So I'm all good running a custom ROM with Knox untripped, if I want to flash a different ROM I can just flash normally in twrp and it won't trip Knox?

GeorgeNYer said:
What about aroma installer roms, can I flash them using this method without tripping the Knox counter?
Click to expand...
Click to collapse
Not sure... alliance hasnt worked for me with this... Im going to try another tomorrow. I'll let you know....

If you need call audio or fingerprint scanner working just flash back to the stock F8 bootloader. You can always reflash to the engineering bootloader to flash more things down the line.
Edit: My mistake, seems this is not possible without tripping it.

Calnyx said:
If you need call audio or fingerprint scanner working just flash back to the stock F8 bootloader. You can always reflash to the engineering bootloader to flash more things down the line.
Click to expand...
Click to collapse
Just to make sure i am understanding right - after step 11, i can flash back a stock COF6/8 bootloader, and retain everything (root, custom ROM, etc) without tripping knox, so long as i dont try to flash anything further? I value my fingerprint scanner, and would love to not lose it and knox if at all possible. For future flashing, go back to the eng bootloader, flash, and then reflash the stock again?

If u flash Stock bootloader it will trip knox.
For the screen problem make sure you have unikernel v6.0001. If it doesnt work maybe you have the Aou twrp. Find the Twrp that is for 920t variant. If not fixed try *#2663# and select TSP FW UPDATE AND IT WILL get fixed.
Call audio gets fixed with unikernel... v6.0001
It will work for unified and 920/5t custom roms. I have tried them all and knox still 0x000 never flash stock bootloader with anything that is custom
... or u will trip knox.

Well, thats a bummer, but i figured as much; if it was as simple as flashing back, i figured people would have been doing it.
Still, thank you for the excellent guide. Followed it on my rooted 5.0.2, and everything worked as advertised. Have root, knox, and only fingerprint reader of course is busted (no huge loss)..

is this verified to work with COH8 without tripping KNOX?

M7 OTA : OTA_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651. 10-6.23.651.7_R_release

Just got the notification for OTA update for m7 .
File name: OTA_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.10-6.23.651.7_R_release_452237.zip
Size: 189.61 mb
{
"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"
}
Sprint Website
Download link
I rooted my phone yesterday and dont want to go back to stock for the update. Can someone please help me with a flashable zip which I can use.
cheers

tangojoker said:
Just got the notification for OTA update for m7 .
I rooted my phone yesterday and dont want to go back to stock for the update. Can someone please help me with a flashable zip which I can use.
cheers
Click to expand...
Click to collapse
From my understanding, you should be able to take the OTA, but you need to make sure everything is as stock as possible first. Follow these steps:
0. BACKUP with a nandroid backup
1. Uninstall any apps that changed the /system partition (like xposed).
2. Unroot from the SuperSU app.
3. Flash the stock recovery (easiest way is to flash the latest full firmware).
4. If you are s-on, you may have to relock the bootloader first (I'm s-off, so I'm not sure).
5. Take the OTA.
6. If you are s-on, unlock the bootloader if you locked in step 4.
7. Flash TWRP.
8. Allow TWRP to root the phone (it will ask you if you want to root when you exit the recovery).
You can get the full firmware from this thread. If you wait though, someone might release a flashable stock rooted ROM, but the phone is old, so that may not happen.

Won't this wipe everything?

jy04 said:
Won't this wipe everything?
Click to expand...
Click to collapse
I don't believe so. The OTA typically leaves the /data partition alone. Of course, as always, everything you do to your phone is at your own risk.

coal686 said:
From my understanding, you should be able to take the OTA, but you need to make sure everything is as stock as possible first. Follow these steps:
0. BACKUP with a nandroid backup
1. Uninstall any apps that changed the /system partition (like xposed).
2. Unroot from the SuperSU app.
3. Flash the stock recovery (easiest way is to flash the latest full firmware).
4. If you are s-on, you may have to relock the bootloader first (I'm s-off, so I'm not sure).
5. Take the OTA.
6. If you are s-on, unlock the bootloader if you locked in step 4.
7. Flash TWRP.
8. Allow TWRP to root the phone (it will ask you if you want to root when you exit the recovery).
You can get the full firmware from this thread. If you wait though, someone might release a flashable stock rooted ROM, but the phone is old, so that may not happen.
Click to expand...
Click to collapse
If anyone does take the OTA and wants to send me a TWRP backup, I'd be more then willing to post a stock rooted flashable Rom.
Just throwing it out there, in case there's anyone interested, willing, and able.
Sent from my HTC6535LVW using Tapatalk

This is the second Stagefright patch/update.
There is an issue with the idea of flashing the latest full firmware, as it is not posted on the forum, the latest RUU post is the firmware before the first Stagefright update, I didn't realize this so I flashed stock recovery as that's how I took the first Stagefright patch, the problem with this is in the OTA update installation it identifies your build before installing so you will receive an error: "Package expects build fingerprint of blah blah/499067.10:user" but it will show as "499067.7:user" and abort installation as that is the fingerprint of the most recent firmware available on the forum, and not the most recent as of the first stagefright update. Someone needs to upload or find updated full firmware or maybe just stock recovery before the installation is possible.

So 6.23.651. 10 is not patched for "stagefright"?

Joshlul said:
This is the second Stagefright patch/update.
There is an issue with the idea of flashing the latest full firmware, as it is not posted on the forum, the latest RUU post is the firmware before the first Stagefright update, I didn't realize this so I flashed stock recovery as that's how I took the first Stagefright patch, the problem with this is in the OTA update installation it identifies your build before installing so you will receive an error: "Package expects build fingerprint of blah blah/499067.10:user" but it will show as "499067.7:user" and abort installation as that is the fingerprint of the most recent firmware available on the forum, and not the most recent as of the first stagefright update. Someone needs to upload or find updated full firmware or maybe just stock recovery before the installation is possible.
Click to expand...
Click to collapse
Just updating the firmware to the previous version won't be enough to allow the update to work.
Most OTA updates, unless they are a full Rom update or RUU, contain patch files.
Those patch files will check the MD5 of every single system file before patching each one.
So even if your firmware is current or your build.prop is edited, to pretend like you have the last version, it will still fail when checking the system files it intends on patching.
There is no way to trick an OTA to work.
You have to have the proper system files, for them to patch at all or properly.
So don't waste your time on that...you need the previous stock Rom for the latest OTA to ever apply properly, or at all.
Good luck!!
Sent from my HTC6535LVW using Tapatalk

links broken can anyone post the OTA update zip like ,i'm rooted with twrp recovery with s-on

santod040 said:
If anyone does take the OTA and wants to send me a TWRP backup, I'd be more then willing to post a stock rooted flashable Rom.
Just throwing it out there, in case there's anyone interested, willing, and able.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
I created a TWRP backup using the following procedure:
1. Relocked my bootloader
2. Took the RUU (RUU_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.10.exe)
3. Unlocked my bootloader
4. Booted into fastboot
5. I tried to run: fastboot boot twrp-2.8.7.0-m7wls.img but that didn't work
6. fastboot flash recovery twrp-2.8.7.0-m7wls.img
7. I booted to recovery.
8. I selected read only
9. Created a backup leaving out the cache.
I'm not sure where to send it or where to post it (1.73GB)

chrishonson said:
I created a TWRP backup using the following procedure:
1. Relocked my bootloader
2. Took the RUU (RUU_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.10.exe)
3. Unlocked my bootloader
4. Booted into fastboot
5. I tried to run: fastboot boot twrp-2.8.7.0-m7wls.img but that didn't work
6. fastboot flash recovery twrp-2.8.7.0-m7wls.img
7. I booted to recovery.
8. I selected read only
9. Created a backup leaving out the cache.
I'm not sure where to send it or where to post it (1.73GB)
Click to expand...
Click to collapse
Could upload to Dropbox, Google Drive, Mega, whatever host you prefer.
Then send me a link via PM, or post it here and mention me.
If using Dropbox, a public link could cause too much traffic on your account, if posted publicly.
Feel free to shoot me a PM if you need further guidance on it.
Thanks for your effort, it should benefit a few folks.
Sent from my HTC6535LVW using Tapatalk

I can't post links yet so pm me if anyone wants the link.
The funny thing about this rom is that TWRP didn't root it like i expected it would. It installed SuperSU but "There is no SU binary installed, and SuperSU cannnot install it..."
Maybe I'm missing something.

santod040 said:
Could upload to Dropbox, Google Drive, Mega, whatever host you prefer.
Then send me a link via PM, or post it here and mention me.
If using Dropbox, a public link could cause too much traffic on your account, if posted publicly.
Feel free to shoot me a PM if you need further guidance on it.
Thanks for your effort, it should benefit a few folks.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
having a similar issue. relocked and RUU'd using last release. For some reason my OTA fails. I found some other guidance that said to extract the stock recovery from the OTA and flash it then run the OTA again, but for some reason I can't extract recovery from firmware. If anyone can post it, I'd like give that method a try. Thanks!

yeah so twrp-2.8.7 wasn't able to flash super su binary in a way that would stick. twrp-2.8.6 worked fine. I think may have seen this issue elsewhere.

Small OTA available today?

I woke up this morning to a 95mb Android system OTA update. I cant find any mention of it on the T-Mobile support site.
I am currently on H81120o the latest build according to T-Mobile.
I imagine it's probably just security updates...
Anyone have any knowledge of this update and it's contents?
TIA

What's the Software version after the Update?
Did you find anything different from 20o?

I grabbed the file.
It looks like a radio update.
https://www.androidfilehost.com/?fid=312968873555003197

mingkee said:
I grabbed the file.
It looks like a radio update.
https://www.androidfilehost.com/?fid=312968873555003197
Click to expand...
Click to collapse
I have been facing constant signal drops on 20o. So may be this update fixes it.
Thanks for sharing.
I am new to LG. Can you explain how can I flash this update?
Edit : Should I use LGUP's FOTA Upgrade option?

Flash it with Flashfire
Check the bottom two.
Root is there
It's still 20o

mingkee said:
Flash it with Flashfire
Check the bottom two.
Root is there
Click to expand...
Click to collapse
Well I used the LGUP's FOTA Upgrade option and it worked.
It's still 20o
Click to expand...
Click to collapse
That's strange. It shows 20p on my device.
But the Network issue is still there. LTE Signal drops every other minute.

arnabJ said:
Well I used the LGUP's FOTA Upgrade option and it worked.
That's strange. It shows 20p on my device.
But the Network issue is still there. LTE Signal drops every other minute.
Click to expand...
Click to collapse
Is root wiped?

mingkee said:
Is root wiped?
Click to expand...
Click to collapse
I didn't had root so I can't say but if root is present then Update won't install to the best of my knowledge.
Do you use T-Mobile connection on this device or unlocked it to use with some other carrier?
I use it here in India. 2G and 3G carriers work perfectly but LTE carrier causing issues inside home.
For some reason Band 5 (850) is failing.
Any help will be appreciated.

Flashed update with LGUP FOTA.
Android Security Patch Level
2016-09-01
Software Version
h81120p

phineous said:
Flashed update with LGUP FOTA.
Android Security Patch Level
2016-09-01
Software Version
h81120p
Click to expand...
Click to collapse
Thanks phineous!
Did you have root before flashing and do you still after?

AndroidUzer said:
Thanks phineous!
Did you have root before flashing and do you still after?
Click to expand...
Click to collapse
No, flashed over a fresh install of H81120o. I'm trying to root now.
Rooted fine flashing phh's SuperUser hidesu r266 in TWRP.
Passes SafteyNet check.

Done.
Unrooted first using 20o kdz file and flashed with LGUP, let it finished bootup and flashed again with update.zip.
You can use fastboot boot TWRP to enter TWRP and root again.

I was unable to apply the update to a rooted phone. Does anyone know how to accomplish this without unrooting the phone?

lancemoreland said:
I was unable to apply the update to a rooted phone. Does anyone know how to accomplish this without unrooting the phone?
Click to expand...
Click to collapse
Haha. I just rooted this phone for the first time yesterday. Figures. Is it recommended I take this update? Can someone explain in n00bish terms how I should go about this? Here's my very basic understanding:
Boot into TWRP. Wipe and then install 20o kdz with TWRP. Install update with TWRP (where do I get this?). Flash SuperSU with TWRP. Install ROM of my choice. Dearie me this is mildly annoying.

unrooting is very simple. its within the settings of the Supersu app. For an update to work i i believe you must be on stock recovery as well, which can be flashed in twrp.

I unrooted and used LGUP to upgrade and install the stock recovery and still could not get it to install. When I pressed the button to reboot and install it would never reboot. Looks like I would need to do a refurbish to get it to install which would wipe my phone. Maybe someone like @MicroMod777 could make a TWRP flashable zip for the update.

Got the update today. Now on H81120p. Is there a change log?
{
"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-H811 using XDA-Developers mobile app

arnabJ said:
I didn't had root so I can't say but if root is present then Update won't install to the best of my knowledge.
Do you use T-Mobile connection on this device or unlocked it to use with some other carrier?
I use it here in India. 2G and 3G carriers work perfectly but LTE carrier causing issues inside home.
For some reason Band 5 (850) is failing.
Any help will be appreciated.
Click to expand...
Click to collapse
How do you use 3G metwork.. Mine only goes 4G and 2G never seen 3G i think 3G is dosabled. Am not on tmobile either. But on my previous phone G2 i had 3G.???

raptorddd said:
How do you use 3G metwork.. Mine only goes 4G and 2G never seen 3G i think 3G is dosabled. Am not on tmobile either. But on my previous phone G2 i had 3G.???
Click to expand...
Click to collapse
My carrier is 4G only. So, I face a lot of issue. Most of the time there is no network on the ground floor. And if there is its unstable.
There is no issue when I am higher levels in buildings or outside. But my room is at ground floor and I have no network there. The phone becomes useless when I am at home.

arnabJ said:
My carrier is 4G only. So, I face a lot of issue. Most of the time there is no network on the ground floor. And if there is its unstable.
There is no issue when I am higher levels in buildings or outside. But my room is at ground floor and I have no network there. The phone becomes useless when I am at home.
Click to expand...
Click to collapse
well i have 4G but sometimes signal is gone so it doesnt go into 3G. so i read we dont have 3G on our phones h811.

Did anyone else get an Android 12 update notification...on Android 12?

This popped up today and has me completely baffled.
{
"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"
}

yeah i got the notification nearly the same time.
u already updated it?

Loisel said:
yeah i got the notification nearly the same time.
u already updated it?
Click to expand...
Click to collapse
Yeah, I updated about a week and a half ago from 12 Beta.
Firmware version on Google's page is still the same...120812.015

V0latyle said:
Yeah, I updated about a week and a half ago from 12 Beta.
Firmware version on Google's page is still the same...120812.015
Click to expand...
Click to collapse
I will update right now from android 11.

Loisel said:
I will update right now from android 11.
Click to expand...
Click to collapse
If you intend on rooting, I'd wait a second....

Yes I got it as well

Maybe they're rolling out an update for Pixel-only-features like they did with the Pixel 6 series.
Until now I didn't get it even with manual search.

Well...I did a clean factory install yesterday, and I don't see an update anymore. It's not posted on the Google firmware pages either, but then again, neither is the new Pixel 6 OTA.
Still see an update available for download but not sure I want to try it quite yet.

Bad news bears.
Installed the update. Rebooted without root, as expected. Rebooted to bootloader, booted the patched kernel. Booted with root. Performed Magisk direct install, rebooted. Boot image verification failure. Reflashed vbmeta with disable flags - got put into Rescue Party. Tried to reflash vbmeta and boot in fastboot, no dice.

V0latyle said:
Bad news bears.
Installed the update. Rebooted without root, as expected. Rebooted to bootloader, booted the patched kernel. Booted with root. Performed Magisk direct install, rebooted. Boot image verification failure. Reflashed vbmeta with disable flags - got put into Rescue Party. Tried to reflash vbmeta and boot in fastboot, no dice.
Click to expand...
Click to collapse
Just happened to me, and I did a fresh install of the A12 release too! Kept getting nagged to install the update, but couldn't find it on the factory flash images page. So thought, I'd go ahead and install it, since there appeared to be no way to make it stop nagging me...now that I type this, there was one thing I forgot to try beforehand...Oh well, looks like my night has only just begun...time to reflash EVERYTHING. If it ain't broke don't fix it...
Also I had the auto system update feature turned off, so I'm not sure how it worked it's way through that setting.
Kind of hating this right now.

ProjectAlly said:
Just happened to me, and I did a fresh install of the A12 release too! Kept getting nagged to install the update, but couldn't find it on the factory flash images page. So thought, I'd go ahead and install it, since there appeared to be no way to make it stop nagging me...now that I type this, there was one thing I forgot to try beforehand...Oh well, looks like my night has only just begun...time to reflash EVERYTHING. If it ain't broke don't fix it...
Also I had the auto system update feature turned off, so I'm not sure how it worked it's way through that setting.
Kind of hating this right now.
Click to expand...
Click to collapse
Same

So I just wiped, re flashed with the flash tool, patched my boot image and everything is running fine again.
I will advise though! For now do NOT update Magisk! Stick with v23000 for now!
The newest release will take some effort to figure out, as far as getting V4A running and other modules since the repo has been removed from the app now. Stay on the older version for now, it will save you a headache.
I updated Magisk and regret it now.

I got the update notification too. I am bone stock, and I was never part of the beta. I went from bone stock 11 to bone stock 12 but it wants me to do a full update to 12. Strange. Well, I'm gonna install it. I got nothing to lose because my P6Pro should be in the mail tomorrow.

chrizzle30 said:
I got the update notification too. I am bone stock, and I was never part of the beta. I went from bone stock 11 to bone stock 12 but it wants me to do a full update to 12. Strange. Well, I'm gonna install it. I got nothing to lose because my P6Pro should be in the mail tomorrow.
Click to expand...
Click to collapse
Same here .. went everything well for you after installing the update again?

ulxerker said:
Same here .. went everything well for you after installing the update again?
Click to expand...
Click to collapse
Installation just finished. As far as I can tell. No issues. Build number is SP1A.211105.002.A1. I wish I had noted the build number before I installed. Doh!

chrizzle30 said:
Installation just finished. As far as I can tell. No issues. Build number is SP1A.211105.002.A1. I wish I had noted the build number before I installed. Doh!
Click to expand...
Click to collapse
Same here. Before, the build number was SP1A.211105.003 but that's how it's supposed to be according to other reports.

chrizzle30 said:
Installation just finished. As far as I can tell. No issues. Build number is SP1A.211105.002.A1. I wish I had noted the build number before I installed. Doh!
Click to expand...
Click to collapse
Since I installed Android 12 the day of the Pixel 6 announcement, I will guess that I was on build number SP1A.210812.015, Oct 2021. This is very interesting because on the Android OTA site, the build that just installed says that this is the Verizon image. I am on Google Fi and I purchased my Pixel 5 from the Google Store.

Today I got an update of Google Play System Update (?) and after that, no more system update available on notification bar or system settings!