Database Users

Firmware 32.2.A.5.11 is out

Got the notification on the available update on Xperia Companion, download in progress, no changelog available as of now.
Anybody knows where to get the update info?

gpdb said:
Got the notification on the available update on Xperia Companion, download in progress, no changelog available as of now.
Anybody knows where to get the update info?
Click to expand...
Click to collapse
Sony doesnt provide change logs, you just need to wait experiences

The biggest change should be the november security patch. I wouldn't expect much more improvements til nougat is out.

security patch is reason enough for me

It contains the security patch for November. Just a minor update.

iArvee said:
It contains the security patch for November. Just a minor update.
Click to expand...
Click to collapse
Anyone succeeded installing 32.2.a.5.11 with root and twrp?

It should work : http://forum.xda-developers.com/xpe...-kernel-dm-t3301605/post69869590#post69869590
If someone is able to share repack kernel here :good:

On my device torch quick switch does not works
Edit: works again after cache cleaning

i see the new version for my country in Xperiafirm,
but i dont see any OTA fw updates on my phone after refresh
i wonder if ill install sony software i ll get the updates via cable
but if isnt big different in batt\pref\security ill wait for 7 anyway
edit :nvm just now i got the OTA update lol... murphy law
charging my phone and updating

torben5247 said:
Anyone succeeded installing 32.2.a.5.11 with root and twrp?
Click to expand...
Click to collapse
Got it running for 2days now without any problems.
ric69 said:
If someone is able to share repack kernel here :good:
Click to expand...
Click to collapse
Here you go:
https://drive.google.com/open?id=0B-RIeaM9FQoMd05MU3VUeHEzRzA
It's stock kernel from E5823_32.2.A.5.11_1299-1063_R10C.ftf, repacked with http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
dm-verity and Sony RIC disabled, includes TWRP and DRM fix but no busybox, SuperSU or xposed. These you have to flash by your own through TWRP.
let me know if it worked for you too.

Gewiz said:
Got it running for 2days now without any problems.
Here you go:
https://drive.google.com/open?id=0B-RIeaM9FQoMR3lPenhvMDJfc2c
It's stock kernel from E5823_32.2.A.5.11_1299-1063_R10C.ftf, repacked with http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
dm-verity and Sony RIC disabled, includes TWRP and DRM fix but no busybox, SuperSU or xposed. These you have to flash by your own through TWRP.
let me know if it worked for you too.
Click to expand...
Click to collapse
Thank you so much, it's working great :good:

Gewiz said:
Got it running for 2days now without any problems.
Here you go:
https://drive.google.com/open?id=0B-RIeaM9FQoMR3lPenhvMDJfc2c
It's stock kernel from E5823_32.2.A.5.11_1299-1063_R10C.ftf, repacked with http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
dm-verity and Sony RIC disabled, includes TWRP and DRM fix but no busybox, SuperSU or xposed. These you have to flash by your own through TWRP.
let me know if it worked for you too.
Click to expand...
Click to collapse
Did you use rootkernel?

Next step is Nougat :fingers-crossed:
Sent from my Sony Xperia Z5 Compact using XDA Labs

ric69 said:
Thank you so much, it's working great :good:
Click to expand...
Click to collapse
You're welcome, i'm happy to hear that.
torben5247 said:
Did you use rootkernel?
Click to expand...
Click to collapse
Of course, like i mentioned
Gewiz said:
repacked with http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
Click to expand...
Click to collapse

I'm coming from stock 305 with xposed and Xpower kernel.
I flashed the 5.11 firmware via flashtool (without ticking any wipe from ftf), just after I flashed your kernel and reboot (optimisation) than I rebooted to TWRP, I flashed SR5-SuperSU-v2.78 + xposed-v87-sdk23-arm64 et voilà
All is working like a charm and I have lost nothing from 305 :good:

Same here. Used:
xperifirm downloader
created ftf with flashtool
loaded ftf with flashtool
loaded androplus (41) with fastboot
and supersu with twrp.

Did the same as ric69. worked! nothing lost from 305.

Can the NFC icon in the status bar be cleared in this newest version? From what I've seen, they taken out that option from .305..

Gewiz said:
Got it running for 2days now without any problems.
Here you go:
https://drive.google.com/open?id=0B-RIeaM9FQoMR3lPenhvMDJfc2c
It's stock kernel from E5823_32.2.A.5.11_1299-1063_R10C.ftf, repacked with http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
dm-verity and Sony RIC disabled, includes TWRP and DRM fix but no busybox, SuperSU or xposed. These you have to flash by your own through TWRP.
let me know if it worked for you too.
Click to expand...
Click to collapse
Thanks for sharing! Works fine here too :good:

daniel_loft said:
Can the NFC icon in the status bar be cleared in this newest version? From what I've seen, they taken out that option from .305..
Click to expand...
Click to collapse
All OK here, NFC was off before the upgrade and isn't there in the status bar after. Have you tried adding the setting to the status drop down bar options and turning it off there? NFC for me is still in the wireless and networks setting under the more option.
Sent from my E5823 using Tapatalk

[Link]MIUI 8.1.1.0 MHOMIDI / MM 6 Nightly (stable) Preview update

I got the link in google
Try at your own risk
http://bigota.d.miui.com/V8.1.1.0.MHOMIDI/miui_HMNote3ProGlobal_V8.1.1.0.MHOMIDI_8e5f6f8e03_6.0.zip
Source
http://en.miui.com/thread-433367-1-1.html
http://www.fonearena.com/blog/20621...allow-update-starts-rolling-out-in-india.html

Deleted

sachin.gokhale said:
Deleted
Click to expand...
Click to collapse
Not yet..

palbadi said:
I got the link in google
Try at your own risk
http://bigota.d.miui.com/V8.1.1.0.MHOMIDI/miui_HMNote3ProGlobal_V8.1.1.0.MHOMIDI_8e5f6f8e03_6.0.zip
Source
http://www.fonearena.com/blog/20621...allow-update-starts-rolling-out-in-india.html
Click to expand...
Click to collapse
what about fastboot rom

RSM10 said:
what about fastboot rom
Click to expand...
Click to collapse
Not yet released...I think

Here's the thread for this link OP, @palbadi -
http://en.miui.com/thread-433367-1-1.html

for quick review. fast battery drain and fingerprint doesn't work sometimes. takes many trys.

shanx_verma said:
Here's the thread for this link OP, @palbadi -
http://en.miui.com/thread-433367-1-1.html
Click to expand...
Click to collapse
Nice thread. However I did not install this. Many of my fnds installed and volte is working...

Will it lock the bootloader if I flash it through zcx twrp..???
And I have officially unlocked bootloader....and if it gets locked...I can unlock through miunlock tool...right..???

palbadi said:
Nice thread. However I did not install this. Many of my fnds installed and volte is working...
Click to expand...
Click to collapse
So you mean to say that if I flash this and then unlock officially, and finally flash AICP, that I will have working VoLTE on AICP??
siddlv said:
for quick review. fast battery drain and fingerprint doesn't work sometimes. takes many trys.
Click to expand...
Click to collapse
You've tried this? So, please try this -
1. Take EFS Backup from Alka TWRP while in this ROM only.
2. Flash AICP MM over it, then CM13 firmware then gapps, and without rebooting, restore your EFS from the backup you took above.
3. Please let me know if that works to enable VoLTE in MM ROM?

shanx_verma said:
So you mean to say that if I flash this and then unlock officially, and finally flash AICP, that I will have working VoLTE on AICP??
You've tried this? So, please try this -
1. Take EFS Backup from Alka TWRP while in this ROM only.
2. Flash AICP MM over it, then CM13 firmware then gapps, and without rebooting, restore your EFS from the backup you took above.
3. Please let me know if that works to enable VoLTE in MM ROM?
Click to expand...
Click to collapse
No, because AICP MM does not contain the files for volte, it has no option in SIM settings to enable volte. But you may try Sudeep's cm13 volte patch. Chance to work is rare..

palbadi said:
No, because AICP MM does not contain the files for volte, it has no option in SIM settings to enable volte. But you may try Sudeep's cm13 volte patch. Chance to work is rare..
Click to expand...
Click to collapse
Not truly, but it does have that option to enable VoLTE for SIM2. Check that out.

Nice sharing man.
Keep it up.

Can someone suggest me, if I should update or not? Some users are reporting that there is battery drain and FP issue. Is it true?

shanx_verma said:
Not truly, but it does have that option to enable VoLTE for SIM2. Check that out.
Click to expand...
Click to collapse
That's good , I did not aware of this. But I am on RR based on 7.1 with volte and don't want to revert back to 6.0.
You should try the method u mentioned.
AtomR said:
Can someone suggest me, if I should update or not? Some users are reporting that there is battery drain and FP issue. Is it true?
Click to expand...
Click to collapse
Some of my fnds has fp issues but can't say for battery.

kiran G. said:
Will it lock the bootloader if I flash it through zcx twrp..???
And I have officially unlocked bootloader....and if it gets locked...I can unlock through miunlock tool...right..???
Click to expand...
Click to collapse
Do not try to install it with twrp , it is ota package for miui recovery with unrooted system.

palbadi said:
Do not try to install it with twrp , it is ota package for miui recovery with unrooted system.
Click to expand...
Click to collapse
According to the link name it's a full recovery ROM not "incremental" update. There shouldn't be any issue if flashed via TWRP except bootloader getting locked maybe.

BlueJeans said:
According to the link name it's a full recovery ROM not "incremental" update. There shouldn't be any issue if flashed via TWRP except bootloader getting locked maybe.
Click to expand...
Click to collapse
Yes, but there is a point..
It is written full recovery rom, but at last it is said 'ota package here'
So, said this. Actually personally did not test it nor downloaded it. However by its size it is little clear that it may be full rom to be installed via zcx or lazy flasher.

Nightly..? seriously.. ? nightly builds on stable.. isnt it sounds funny..?

I have installed this update battery is good no heat and fp has little issue not major but little issue there and the rom is good and if u flash through twrp then your bootloader will get locked u have to unlock it again

Don't unlock BL if you need GPay

Since 19th, ZF2 is fully passing CTS & basicIntegrity again with unlocked Bootloader.
SafetyNet has been updated and will now tell CTS profile false on Zenfone with unlocked bootloader. previuosly open bl alone did not trigger it, as long you didnt had root. as there is no kernel source for ZF2 it will not be possible to create a patch and Magisk can't hide BL status without it. so be warned. only way is RELOCK

If Gpay doesn't want to play nice, then they don't get my money.
Sent from my ASUS_Z00AD using Tapatalk

GPay never meant to run on 'uncertified' devices, just Google didn't check bootloader state before on ZF2, as long the ROM was Stock it worked.

Tr4sHCr4fT said:
as there is no kernel source for ZF2
Click to expand...
Click to collapse
Kernel source is available for ZenFone 2, but custom kernel isn't a requirement for Magisk Hide as long as the kernel is at version 3.8 or higher.
Sent from my ASUS_X00TD using XDA Labs

Can I ask how to re-lock BL in easy way, thx

Have you tried to install BORETS ROM then? The stock based one with his custom kernel and Magisk pre-installed?

I am using Magisk 17.1 and I checked the SafetyNet via MagiskManager and it said both CTS and basicIntegrity check are true.
Am I missing something here? Or my SafetyNet isn't updated yet?

papin97 said:
Am I missing something here? Or my SafetyNet isn't updated yet?
Click to expand...
Click to collapse
Google had mercy and ZF2 again got valid CTS since 19th

141231 said:
Can I ask how to re-lock BL in easy way, thx
Click to expand...
Click to collapse
You can't. Period.

widevine l1 with unlocked bootloader??

As the question implies, what happens with widevine l1 if you unlock your bootloader?? My new redmi note 7 is global and has widevine l1 want to know to see if I unlock or not

it becomes L3 for sure

It becomes L3. I reflashed the official miui rom without relocking and it's L1 again.

KaladinSB said:
It becomes L3. I reflashed the official miui rom without relocking and it's L1 again.
Click to expand...
Click to collapse
Interesting, thx for letting me know, have you tried an .eu rom??

ginryu said:
Interesting, thx for letting me know, have you tried an .eu rom??
Click to expand...
Click to collapse
I did, it is L3.

Thx
I think I'm just going to flash the official updated miui rom, my redmi comes with carrier software and it's lagging behind in updates.

I have the global variant (the PFGMIXM one) with unlocked bootloader and I still have L1 certification. Rooted with Magisk too.

ganimomu said:
I have the global variant (the PFGMIXM one) with unlocked bootloader and I still have L1 certification. Rooted with Magisk too.
Click to expand...
Click to collapse
Stock rom right??

ginryu said:
Stock rom right??
Click to expand...
Click to collapse
Right, MIUI 10.3.5.0

PPWS29.116-11-13 update failed to install

The most recent update PPWS29.116-11-13 has OTA downloaded, but failed to install (even after factory reset). All previous updates had always installed without any problem.
I have XT1926-7 "Evert" (from Amazon) with unlocked BL, but otherwise stock un-rooted, unmodified PPWS29.116-11-11.
Could unlocked BL be a reason?

The unlocked BL can't be the reason for this. Try flash the 116-11-11 FW and just boot your device without any changes. Then you will be able to install the update.

WoKoschekk said:
flash the 116-11-11 FW
Click to expand...
Click to collapse
Why? Wha's the rationale here? It's already 116-11-11

rybshik said:
Why? Wha's the rationale here? It's already 116-11-11
Click to expand...
Click to collapse
Moto OTA update s have been failing for many model s
Seems like the only solution is to reflash the current version of firmware that phone and try OTA again
Or see is new version is posted on
https://mirrors.lolinet.com/firmware/moto
Just download the correct software channel version.
Flash with Rsd lite or fastboot.exe
Sent from my mata using XDA Labs

sd_shadow said:
reflash the current version of firmware that phone....
https://mirrors.lolinet.com/firmware/moto
Click to expand...
Click to collapse
Will EVERT_RETAIL_9.0_PPWS29.116-11-11 be good for AT&T and T-mobile frequency bands?
I do not care too much about LTE though

sd_shadow said:
Seems like the only solution is to reflash the current version of firmware that phone and try OTA again
Click to expand...
Click to collapse
I flashed "EVERT_RETAIL_9.0_PPWS29.116-11-11" with fastboot and then device OTA updated to PPWS29.116-11-13.
It works OK.
However, if go to System updates, I get the following:
System integrity is compromised
Android version: 9
Current version: PPWS29.116-11-13
Security patch: November 1, 2019
As your device system integrity is compromised is compromised, it is no longer eligible for software updates
Click to expand...
Click to collapse
So I am wondering if it might be because of (possibly) incorrect software channel? My original device software channel was and still is "retla".
Or because of the unlocked BL?
I have not made any other FW modifications nor did I root

rybshik said:
I flashed "EVERT_RETAIL_9.0_PPWS29.116-11-11" with fastboot and then device OTA updated to PPWS29.116-11-13.
It works OK.
However, if go to System updates, I get the following:
So I am wondering if it might be because of (possibly) incorrect software channel? My original device software channel was and still is "LA".
Or because of the unlocked BL?
I have not made any other FW modifications nor did I root
Click to expand...
Click to collapse
I'm not sure.
Someone else posted same warning, that had unlocked bootloader.
It's not a normal warning.
Sent from my Cosmo_Communicator using XDA Labs

sd_shadow said:
Someone else posted same warning, that had unlocked bootloader.
Click to expand...
Click to collapse
so folks need to be careful when updating to PPWS29.116-11-13

rybshik said:
I flashed "EVERT_RETAIL_9.0_PPWS29.116-11-11" with fastboot and then device OTA updated to PPWS29.116-11-13.
It works OK.
However, if go to System updates, I get the following:
So I am wondering if it might be because of (possibly) incorrect software channel? My original device software channel was and still is "retla".
Or because of the unlocked BL?
I have not made any other FW modifications nor did I root
Click to expand...
Click to collapse
Install Magisk and this message will disappear.
This a normal warning screen caused by a corrupted AVB due to your unlocked bootloader. Magisk will fix it by the AVB 2.0/dm-verity option.

WoKoschekk said:
This a normal warning screen caused by a corrupted AVB due to your unlocked bootloader..
Click to expand...
Click to collapse
Yet, there is no such warning with earlier FW versions, for example, PPWS29.116-11-11

rybshik said:
Yet, there is no such warning with earlier FW versions, for example, PPWS29.116-11-11
Click to expand...
Click to collapse
Yes, there is. Everytime I flashed a new FW and Magisk wasn't installed the system showed me this warning. As soon as Magisk is installed this error will disappear. Just try it.
Since the moto g6 plus was updated to Pie you got this error.

rybshik said:
Yet, there is no such warning with earlier FW versions, for example, PPWS29.116-11-11
Click to expand...
Click to collapse
Yes I think this is a new thing.
Sent from my mata using XDA Labs