[Firmware Update] Xperia XZ Premium 47.2.A.11.234 - Sony Xperia XZ Premium Guides, News, & Discussion

Sony Xperia XZ Premium 47.2.A.11.234 Firmware Update Rolling.
OTA Update Notification. Size 76 MB
Source - https://www.gizmobolt.com/2021/04/07/xperia-xz1-xz-premium-47-2-a-11-234-firmware-update-rolling/
via Reddit User QuietImpact699 ( Image via user vForVendition )
Update is also seen for Xperia XZ1.
{
"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"
}

Guys, hoping somebody can help. I got notified about an update for 47.2.A.11.239, which I think is a related update
I had bootloader unlocked, with TWRP and Magisk installed on Customised AU 47.2.A.10.137
I completely uninstalled Magisk, and ran the update, and it fails. It downloads all 441.8MB, I select Install and it reboots to the little green Android guy saying Verifying system update. But very quickly, it says "Restarting" and obviously the update hasn't happened. It doesn't to give any useful reason why, just says "Could not install", and prompts me to start downloading again.
Is it because I have TWRP? Do I have to do a full flash using Xperifirm? That's gonna wipe everything?
Thanks
PS: Funny enough, where the System Update installer says "You can install by computer. Read more at http://support.sonymobile.com/update, that has a bad certificate and then gives me Sorry this page is no longer available.

wiresquire said:
Guys, hoping somebody can help. I got notified about an update for 47.2.A.11.239, which I think is a related update
I had bootloader unlocked, with TWRP and Magisk installed on Customised AU 47.2.A.10.137
I completely uninstalled Magisk, and ran the update, and it fails. It downloads all 441.8MB, I select Install and it reboots to the little green Android guy saying Verifying system update. But very quickly, it says "Restarting" and obviously the update hasn't happened. It doesn't to give any useful reason why, just says "Could not install", and prompts me to start downloading again.
Is it because I have TWRP? Do I have to do a full flash using Xperifirm? That's gonna wipe everything?
Thanks
PS: Funny enough, where the System Update installer says "You can install by computer. Read more at http://support.sonymobile.com/update, that has a bad certificate and then gives me Sorry this page is no longer available.
Click to expand...
Click to collapse
sorry mate but if you wish to install the update then you will need to start fresh. As for the page no longer available, that is because a lot of the Sony support for Australia documentation is gone.

Related

i need help to update a problematic gt540

hello to all xda members
in the past i update a gt540 (1.6) to 2.1 and then to cyanogenmod, this come new from store with 1.6 and never have a problem with this phone.
Now i buy a gsm unlocked gt540 wich come from store with 2.1 and then i tried to update to 2.1 stock fastboot rom with kdz updater(using the same guide that i used in the first phone), the problem is that the process was stopped and the Phone was COMPLETELY bricked.
The only way to come back to life was a complex conection(jtag) with a box named "Medusa box", but the problems no stop here, when the phone turn on there is no way to grab signal until i used a lge oficial box to repair NVM and then unlockconfused: the phone was from factory unlocked) again the phone.
i need install cyanogenmod, bacause the phone is actually no fully working since enach time, this said some like this."process android was stoped," an others like this saying a process o app stop working.
i need your help to now how update, or if the phones that come from factory with 2.1 use a diferent way to update.
the photo is my actual rom(2.1 oficial rom)
{
"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"
}
Need to think this through...
you can go into download mode right? then follow this guide to install fastboot.. then the phone will bootloop. Just download cwm or twrp from android development section and flash using fastboot.. then install any ROM...
XiproX said:
you can go into download mode right? then follow this guide to install fastboot.. then the phone will bootloop. Just download cwm or twrp from android development section and flash using fastboot.. then install any ROM...
Click to expand...
Click to collapse
Thanks this finally works.
hi,
with fastboot mod, my phone d'ont won't to pass the cyanogen blue cross at the first boot.
So, i install the clockworkrecovery.img, i download the SDSL rom for recovery, and it was quickly and secure installed.

Z1s 14.5.B.0.247 Released - Stagefright Patched

Got the OTA this morning on T-Mobile USA. I haven't noticed anything else different other than all Stagefright vulnerabilities being patched.
{
"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 C6916 using XDA Free mobile app
Interesting that they only patched Stagefright. Definitely worth upgrading, though.
I haven't touched my z1s in a while. I'm assuming if I'm rooted, I can not update via the OTA?
Someone on Reddit said they couldn't update their rooted phone. The update will fail to install.
Sent from my C6916 using XDA Free mobile app
I figured as much, guess I'll have to unroot and reroot and reinstall the dual recovery again.
Mine gives an error when trying to update. I have root and a custom recovery. It says "Could not verify."
I do not want to go through unrooting and rerooting so ill wait for a root friendly update to surface. Until then I guess im stuck with the popup in the notification bar.
silentsnow31802 said:
Mine gives an error when trying to update. I have root and a custom recovery. It says "Could not verify."
I do not want to go through unrooting and rerooting so ill wait for a root friendly update to surface. Until then I guess im stuck with the popup in the notification bar.
Click to expand...
Click to collapse
same happened with me when I tried to update via the phone or PC Companion. Have you found a way to get the update yet? I haven't had any luck
I was wondering if I were to do a full backup, unroot, update, then reflash the kernel from my backup if I'd still have root. I don't want to go through the whole root with KingRoot and replace with SuperSu again if I don't have to.... I'm not sure if SuperSuMe will work correctly because I didn't have much luck with it on BlueStacks 2 since I got to remove KingRoot but lost root after switching to SuperSu
jdmst77 said:
same happened with me when I tried to update via the phone or PC Companion. Have you found a way to get the update yet? I haven't had any luck
I was wondering if I were to do a full backup, unroot, update, then reflash the kernel from my backup if I'd still have root. I don't want to go through the whole root with KingRoot and replace with SuperSu again if I don't have to.... I'm not sure if SuperSuMe will work correctly because I didn't have much luck with it on BlueStacks 2 since I got to remove KingRoot but lost root after switching to SuperSu
Click to expand...
Click to collapse
No I haven't even looked into it. I stopped getting the update notification so I forgot about it honestly.
Sent from my C6916 using Tapatalk

No Command after security patch TA-1033

Hey, hopefully someone could help me out with this one.
I have a TA-1033 which was working fine, I installed a security patch through system update and now it boots to No Command
Tried factory reset and cleared cache but still boots to No Command.
I'm hoping someone please tell me what to flash to get it up and running?
Picture attached of recovery screen
Thanks!
{
"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 MHA-L09 using Tapatalk
imediax said:
Hey, hopefully someone could help me out with this one.
I have a TA-1033 which was working fine, I installed a security patch through system update and now it boots to No Command
Tried factory reset and cleared cache but still boots to No Command.
I'm hoping someone please tell me what to flash to get it up and running?
Picture attached of recovery screen
Thanks!
Click to expand...
Click to collapse
Your phone was rooted?
Nope wasn't rooted
Sent from my MHA-L09 using Tapatalk
What was that? July security update?
Upd: seems like it's July update according to screenshot.
1. Copy Dec 2017 and June 2018 OTA zip files on your SD card
2. Boot into recovery, install Dec 2017 OTA from SD card first. It will fail but that's ok
3. Reboot into recovery again, this time it will be Nougat recovery
4. Install June 2018 OTA from SD card
if it doesn't help and you still get recovery loop and you don't wanna reset your phone you can copy Feb 2018 OTA (having full Oreo image) to SD card and install it from recovery.
Legendary thank you! I'll give it a crack when I get home from work. Appreciate your help!
From where did you get the July security update.
jaikn1985 said:
From where did you get the July security update.
Click to expand...
Click to collapse
A notification popped up there was a system update
Sent from my MHA-L09 using Tapatalk
imediax said:
A notification popped up there was a system update
Click to expand...
Click to collapse
Seems to be a common issue. You can assume that you did nothing wrong, it's just the imperfections of humans that bricked your device
(the devs @ Nokia or Google)

SuperSU says my phone is not rooted. Drivewise wont run on rooted phone???

hello,
for auto insurance reasons, i was trying to run "Drivewise"
i downloaded the app, installed it, and when i tried to run it, it says "Running Drivewise Canada on a rooted is not allowed".
so i downloaded "Root checker basic", "Sorry! Root access is not properly installed on this device"
upon more reading and googling it seemed that i should update my "SuperSU" i found this on youtube, have downloaded the latest supersu update, but trying to start in "fastboot mode" it hangs in "odin mode"
i tried running TWRP, but on the second page "This app needs root permission to do most functions in app." i touch the "SET PERMISSION" and a popup window says "App needs root access to function"
i am only trying to unroot my phone, so that Drivewise will work/ run..
requesting some help, please..
thank you
The best way is to flash new firmware, dirty update. Just flash it over your current one.
But from the other hand if your device is rooted and you want to trick some apps than there are other apps out there to hide su from particular apps. You could use xposed framework modules or magisk modules etc.
a602820922 said:
The best way is to flash new firmware, dirty update. Just flash it over your current one.
Click to expand...
Click to collapse
thank you for the suggestion, i will (try) search google for more info
I forgot to mention, I also tried xposed framework and magisk modules both had problems..
Xposed said that it wasn't comparable
Magisk, upon downloading the app, prompting you to download a zip file, it then says that everything is installed but when you go forward to the home page it says it's not installed yet.
Obviously I have missed something, just don't know what. View attachment 4743533
View attachment 4743534
For xposed you need modified framework.
{
"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"
}
a602820922 said:
For xposed you need modified framework. View attachment 4743573
Click to expand...
Click to collapse
with the corruption i have, the phone doesnt see that i am rooted, but other programs think i am, therefore i am unable to install xposed or magisk, let alone run, as they need the phone to be rooted..
just seem to be going around in circles..
have been reading how to "dirty flash". but as i cant seem to get CWM or TWRP to install i believe Odin is my last/only chance to flash a new ROM.
all my searching seems to find odin and rooting, and not flashing a stock rom, still searching
not sure why or how, but....
i basically gave up with trying to figure out what had happened and how to fix it/ rectify/ over come it. so i decided to backup using smart switch, downloaded the stock ROM. and just before i turned off my phone to hook up to Odin, i thought i would try one last time to access the app that started me off in the first place..
and didnt it work!
im sorry that i am unable to offer any suggestions as what worked for me.

Moto G6+, 1st May update error

Hi, i have a problem with a 1st may update.
When i install the update, the phone reset and appears the following black screen error
{
"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"
}
if i select try the phone restart and appears the same black screen with the error, but if i repeat this for around 5 or 6 times the phone starts.
I did a factory data reset, and the update installed again whit the same error.
I hope you can help me, and if u have a question let me know. ty
Have you tempered with unlocking the phone? If so you'll need to reinstall stock rom
mrsiri said:
Have you tempered with unlocking the phone? If so you'll need to reinstall stock rom
Click to expand...
Click to collapse
yes, i did that, i installed the latest stoc rom, but is the same.
What about factory resetting? and don't even think about locking the bootloader
---------- Post added at 07:56 PM ---------- Previous post was at 07:55 PM ----------
if you still have warranty, send it for fixing
mrsiri said:
Have you tempered with unlocking the phone? If so you'll need to reinstall stock rom
Click to expand...
Click to collapse
yes, i did that, i installed the latest stock rom, but is the same problem. The 1st may update download again with the same error
fraan_10 said:
yes, i did that, i installed the latest stock rom, but is the same problem. The 1st may update download again with the same error
Click to expand...
Click to collapse
That's very interesting! I had the same issue with that specific OTA update from 116-20-20 to -23 (RETEU channel // XT1926-3)
My bootloader is unlocked but I also installed the full stock ROM 116-20-20 from mirrors.lolinet.com before doing the update. After ROM was flashed I booted up normally without any modifications. Almost stock except the unlocked bootloader.
After the update was installed my first boot into the new 116-20-23 failed and led me to the same screen. But a factory reset solved the problem and I was able to boot up normally.
It seems to be a corrupt OTA update file...

Categories

Resources