Just seen that there is a new firmware out for our Xperia's. Can we have some feedback from people who have downloaded it.
Date of security patch?
Fixes restarts?
Power consuption?
Anything to report.
Got it OTA 5 minutes ago. Can only report December 1st security patch so far.
Wow they must be having serious issues with recent releases, what with the abnormally frequent revisions and pulling some offline.
Glad they included the December patch in the latest release.
Still sucks to be stuck on .374 though, with no camera distortion fix
@mhaha
Could you check if the app drawer opens if you swipe up in home screen (and you can go back to homescreen by swiping down in app drawer)? This seems to be new in this build. (I can not check if it works in an older one.)
nospherato said:
@mhaha
Could you check if the app drawer opens if you swipe up in home screen (and you can go back to homescreen by swiping down in app drawer)? This seems to be new in this build. (I can not check if it works in an older one.)
Click to expand...
Click to collapse
This was a new feature implemented on a recent update to the home launcher app (11.0.A.0.8), and since I updated it, I have this function in .374.
It's not tied to the firmware version.
EDIT: I updated the app through Google Play, they have a list of changes posted for the new launcher. Wish they'd do the same for firmware updates...
Hm, strange.. Mine xperia home version 10.2.A.3.25 says it's up to date. Also the changelog only says "bugfixes". (inside "more" only generic stuff like "full integrated google-feed etc.)
Hm, okay.. inside the home settings it says 11.0.A.0.5
Installed on my phone last night. It seems very smooth, I can't find any problems.
Bluetooth problems I had with connecting to things seems to have resolved. Previously the phone wouldn't automaically connect to a device, even though it was the only thing in range.
The camera fix is the most obvious thing, this will be new for people who didn't get the 47.1.A.5.51
Monitoring battery life now to see how it compares.
Phone just rebooted, so the new firmware didn't fix that.
I still have Bluetooth issues, i.e it wont automatically start playing music but FF/REW seems a bit better, but i still get no track names on my cars inbuilt head unit.
Seems a Little bit smoother imo. Still apps still freezes from time to time. Seems like battery is back to normal again. If u experience batterydrain anomaly, try updating play service to .51 Beta from apkmirror.
So far .49 seems good, the battery seems to be much improved ?
All,
I would note that it appears (per screenshot here) that you can't downgrade to a previous version once you've installed the 47.1.A.8.49 firmware.
I suspect they have enabled Qualcomm's bootloader versioning which prevents the system from booting when it detects the older version.
This probably means that there is a serious and potentially easy to exploit vulnerability in the previous versions of the bootloader. Note the many closed source Qualcomm vulnerabilities listed in the December ASB.
It's possible that someone will eventually discover what those vulnerabilities are and come up with a way to root without unlocking the bootloader.
Personally, I'm staying away from this update for a while.
EDIT: I was wrong. See below.
pbarrette said:
All,
I would note that it appears (per screenshot here) that you can't downgrade to a previous version once you've installed the 47.1.A.8.49 firmware.
Click to expand...
Click to collapse
The update screen has always had that disclaimer though, for each and every update I've ever received - and I've owned nearly every Xperia compact.
If you only go the official route, downgrading was never an option.
If they implemented a way of preventing one from flashing an older firmware even when using third party tools like Flashtool or newflasher, then that indeed is news, and bad news at that. But the screenshot is largely irrelevant.
unfortunately I don't receive any updates for mine it's still on "47.1.A.2.374"
When I'm conected to WLAN and search for new updates via "Settings --> System --> Softwareupdate" it tells me that I already have the newest updates installed
mhaha said:
The update screen has always had that disclaimer though, for each and every update I've ever received - and I've owned nearly every Xperia compact.
If you only go the official route, downgrading was never an option.
If they implemented a way of preventing one from flashing an older firmware even when using third party tools like Flashtool or newflasher, then that indeed is news, and bad news at that. But the screenshot is largely irrelevant.
Click to expand...
Click to collapse
You're correct and I was wrong.
A user was trying to downgrade and was getting boot-loops and another user pointed out the statement in the ROM.
I knew that there were a lot of closed source Qualcomm updates and assumed that Sony implemented version rollback prevention.
They did not.
I was wrong.
I pulled the attestation certificates from all of the firmware versions released thus far and compared them.
They are identical.
Code:
CN = Yoshino com-2 Attestation Cert
OU = 01 0000000000000001 SW_ID
OU = 02 0005E0E100010004 HW_ID
OU = 03 0000000000000000 DEBUG
OU = 04 0001 OEM_ID
OU = 05 00020000 SW_SIZE
OU = 06 0004 MODEL_ID
OU = 07 0001 SHA256
O = Sony Mobile Communications Inc.
L = Lund
S = N/A
C = SE
Note that the "SW_ID" is the bit used to implement rollback prevention and is actually supposed to be read in two parts:
0000000000000001
The red bit is the version number and the green bit is the image identifier.
Essentially, the version number hasn't changed, so we can still roll-back to a previous version.
The user with the problem likely has some other problem unrelated to bootloader versioning.
I apologize for the misinformation.
pbarrette said:
You're correct and I was wrong.
A user was trying to downgrade and was getting boot-loops and another user pointed out the statement in the ROM.
I knew that there were a lot of closed source Qualcomm updates and assumed that Sony implemented version rollback prevention.
They did not.
I was wrong.
I pulled the attestation certificates from all of the firmware versions released thus far and compared them.
They are identical.
Code:
CN = Yoshino com-2 Attestation Cert
OU = 01 0000000000000001 SW_ID
OU = 02 0005E0E100010004 HW_ID
OU = 03 0000000000000000 DEBUG
OU = 04 0001 OEM_ID
OU = 05 00020000 SW_SIZE
OU = 06 0004 MODEL_ID
OU = 07 0001 SHA256
O = Sony Mobile Communications Inc.
L = Lund
S = N/A
C = SE
Note that the "SW_ID" is the bit used to implement rollback prevention and is actually supposed to be read in two parts:
0000000000000001
The red bit is the version number and the green bit is the image identifier.
Essentially, the version number hasn't changed, so we can still roll-back to a previous version.
The user with the problem likely has some other problem unrelated to bootloader versioning.
I apologize for the misinformation.
Click to expand...
Click to collapse
Do you know how i might go about troubleshooting the problem? I'm grateful for newflasher and can follow directions pretty well, but obviously something went slightly wrong. Is it my own fault for not flashing over my user data? it worked fine when i flashed from .51 to .7.1.
billbond4 said:
I still have Bluetooth issues, i.e it wont automatically start playing music but FF/REW seems a bit better, but i still get no track names on my cars inbuilt head unit.
Click to expand...
Click to collapse
I had the issue with not getting the track names as well. Solved by changing AVRCP to version 1.4 in developer options and then re-pairing (forget the device and then pair again) with my Kenwood head unit. Media controls also work fine.
Im_A_Decoy said:
I had the issue with not getting the track names as well. Solved by changing AVRCP to version 1.4 in developer options and then re-pairing (forget the device and then pair again) with my Kenwood head unit. Media controls also work fine.
Click to expand...
Click to collapse
I have a Pioneer and I don't have any problems, regardless avrcp version
Im_A_Decoy said:
I had the issue with not getting the track names as well. Solved by changing AVRCP to version 1.4 in developer options and then re-pairing (forget the device and then pair again) with my Kenwood head unit. Media controls also work fine.
Click to expand...
Click to collapse
Thanks so much for this. This workaround fixed the title display in my Hyundai .
Does anyone of you also get worse battery run times? Mine phone is (only 30min sot) in standby for 1d14h and already at 45%... Standby showing 17% consume, Android OS12%, mobile standy 8% and (RCS) phone 7% which all together seems pretty much... Before this update I got runtimes for 4days+, not I already have to charge after 3 days.
(I did not uninstall or install any new apps.)
Related
I have a BT338 bluetooth GPS adapter it will not get a lock on and I have been looking for a flash program for it to see if I can reflash it.
I followed a link from a site to this sites ftp server that used to have it but it looks like it has been taken down.
Does anyone know if flashing is possible and if so does anyone have a program to do so?
Thanks for any help.
Packrat,
I have had a BT-338 for two years and I love it. I don't recall that I was ever able to find a method to upgrade the firmware. I will watch this thread in case some one has an answer.
On the other hand, I did have problems when I first got this unit. If I played with changing setting between WAAS/normal and/or Sirf/NMEA modes, sometimes this thing was not get a lock. To fix it I would use a laptop tool to reset the unit to factor setting. I think it was GPSInfo connecting via a BT dongle.
Let me know if this might help and I will look into the exact detail if you need it.
whbell said:
Packrat,
I have had a BT-338 for two years and I love it. I don't recall that I was ever able to find a method to upgrade the firmware. I will watch this thread in case some one has an answer.
On the other hand, I did have problems when I first got this unit. If I played with changing setting between WAAS/normal and/or Sirf/NMEA modes, sometimes this thing was not get a lock. To fix it I would use a laptop tool to reset the unit to factor setting. I think it was GPSInfo connecting via a BT dongle.
Let me know if this might help and I will look into the exact detail if you need it.
Click to expand...
Click to collapse
Thanks for the reply, I tried to reset it to factory via the SirDemo program, but that didnt help. Hopefully I can find a way.
Yes reflash is possible...
You can use SirfDemo and SirfFlash
The procedure is almost the one described here....
http://web.mac.com/tomtastic/site/log/Entries/2007/6/18_Holux_GPSlim236_boot_mode.html
You can download the needed tools here...
http://www.falcom.de/support/software-tools/sirf/
To flash
- First you have to connect your bt-338 using SirfDemo.
- In Action/ Transmit Serial Message select NMEA and send this message
'PSRF100,0,38400,8,1,0' without quotes. This will put the GPS in SIRF Mode.
- After that choose Action / Transmit Serial Message select SIRF this time and send '94' without quotes. This will put the GPS in boot Mode.
- Disconnect now SirfDemo using the button and start SirfFlash without powering down the GPS.
- Choose the correct port and 38400 Baud and - very important -select 'external boot mode'. Browse for the new firmware .bin file and select 'program flash'.
- Execute and enjoy.
Cheers!
I have now (finally!) successfully read the firmware from my two BT338 and a TomTom Mk2 BT mouse. Also important to notice is the following:
- Address Range is 0x0 to 0x7ffff (4 times an "f") resulting in a 512kB bin file.
- Any other speed than 38400 will NOT work!
Did not dare yet to flash actually... I have now:
TomTom Mk-II
GSW3.0.2TomTom1.1_3.0.00.03-C3P1.02b
BT338 (NaviLock labled in Germany)
GSW3.0.2_3.0.00.03-C16P1.02a
GSW3.1.1LowV_3.1.00.07-C23B1.00
I know there must be newer one for BT338 as you can see from the FAQ at Globalsat USA at: http://www.usglobalsat.com/gpsfacts/bt338_gps_facts.html
The mention even different versions there (QA 38):
BT-338_GSW3V3.1.1LowV_F-GPS-03-0506222 and
BT-338_GSW3.1.1TO_F-GPS-03-0510032
I noticed that reading out the SW sometimes delivers different results after 7d008 when some time has passed. I suspect that some data is stored there which may vary over time (satelite positions, routes or whatever may be stored depending on the time).
bye
tobbbie
I can report success now in upgrading my BT338 from the old (3.0.2) FW to the later one (3.1.1) I have retrieved from my other BT338.
Main gain for me is the availability of geoid correction for the height.
Anynone has a later firmware for the BT338 or the TomTom MK2?
You can PM me if you don't want to post here.
bye
tobbbie
GSW3.0.2TomTom1.1_3.0.00.03-C3P1.02b
Hi tobbie,
have you managed to get some new firmwares , I am searching if there is a new one for the tomtom ( there is still some issues between the treo and the tomtom related to the bluetooth stack ). Is there a way to use the BT-338 or a part of the BT-338 firmware in the tomtom ?
thanks
Laurent
look here: http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=27925&whichpage=11
please read all posts and follow the wohle story. My TomTom MkII currently runs the 3.2.2 of the latest BT338.
Thanks tobbie,
I have red the full thread, downloaded your dumps of the firmware, and dump my tomtom firmwarewith the sirf tools.
I have compared the dump from your tomtom and mine ( same version 302 ) and they are quite different beiginning in 6D008 :
your firmware :
6D008 : 06 3E 00 00 01 00 00 00 41 46 31 41 39 53 D8 19 ....
my dump :
6D008 : 20 C6 00 00 99 00 00 00 41 46 31 41 39 53 D8 19 ....
Is this part a variable part ( so may be a factory reset and a new dump will give a more comparable result ), or is there a real difference for two same version of the firmware ??
Can you tell me for upgrading the firmware of the tomtom have you used the full 3.11 firmware from 0 to 7FFFF or have you used a dump from 0 to 79999 ?
seeing the various problems some got after flashing their units I am a bit worried before flashing mine..
thanks
Laurent
Just do a system reset of your device and dump it again.
Depending how fast you are getting it into bootmode you have some data there (and not all default empty data). Doing the same after some time (e.g. after a fix was established) will again deliver different data there.
I think the main thing here is that the WHOLE data are dumped and then later flashed to another device. This may also be the rootcause of the failure to use the 0-79999 dump - where after 79999 data may confuse the device to get back online (very sad - it already cost 2 devices one BT338 and one TomTom MkII).
I have used my own dumps to crossupgrade from BT338 to TomTom and the 3.2.2 from antineutrino. After some back and forth I am on 3.2.2 again currently for all devices (living with the green-LED off until a fix).
BTW: I am quite sure that the bluetooth part is not touched by these updates.
The names of the devices as they are recognized on bluetooth are not changing after a FW update.
thanks tobbie ,
as I need this gps in the coming next weeks, I will not take the chance to do the upgrade just now. I will wait a quiter period of time to try it ( so if I brick it I will have time to make a replacement ).
thanks, I will come back for detailled instructions in some weeks.
Laurent
Hi Tobbbie,
I have a Globalsat BT 338, I would like to update the firmware. I downloaded your dumps from http://www.gpspassion.com/forumsen/t...5&whichpage=11, the 3.1.1 version.
Do I understand well that even exists a 3.2.2 version?
If yes where could I find it?
Thanks
patek
It's in the same forum a few post further down - it comes from another member there - just look it up.
Edit: just checked - it seems only the 3.2.4 of the BT368 is there.
I have edited my old post there with a new link that has all info - also for short here:
http://rapidshare.de/files/41287744/Firmware_Globalsat.zip.html
Please read the GPS passion forum entries very thoroughly - it MUST be complete dump that you insert - anything less than 512kB will kill your device (as a poor forum member there had to suuffer)..
Tobbbie,
Thank you for your prompt answer,
I checked my software version, Sirfdemo says: GSW3.1.1LowV_3.1.00.07-c23B1.00 - the same what yours was before upgraded.
I read your opinion about changing to 3.2.2 :
>As mentioned earlier I have yet to discover advantages of 3.2.2 or 3.2.4 over 3.1.1. I >think some trickle power options are more flexible and the DGPS could work - but so far I >could never get a DGPS fix.
So do you think is it worth enough to upgrade? (green lamp!)
Is the WAAS enabled in the 3.2.2 ? (maybe silly question)
Thanks
tobbbie said:
It's in the same forum a few post further down - it comes from another member there - just look it up.
Edit: just checked - it seems only the 3.2.4 of the BT368 is there.
I have edited my old post there with a new link that has all info - also for short here:
http://rapidshare.de/files/41287744/Firmware_Globalsat.zip.html
Please read the GPS passion forum entries very thoroughly - it MUST be complete dump that you insert - anything less than 512kB will kill your device (as a poor forum member there had to suuffer)..
Click to expand...
Click to collapse
hmm, i haven't used my trusty bt338 in quite some time, i might upgrade it just to see what happens..
Hello everyone,
I just update my Omnia 7 (unbranded) yesterday using disconnect trick, from Nodo. My phone receive two updates.
But the compass app and Allshare dont work yet and the version of firmware, compared to other here, is outdated.
Os Version: 7.10.7720.68
Firmware revision number: 2424.10.11.1
Hardware revision: 3.15.0.4
Radio Software: 2424.11.2.2
Bootloader version: 5.2.1.4
Chip SOC: 0.36.2.0
Any tip for this situation ??
regards !!
Try manually deploying this .cab.pks:
http://wp7.ondraster.cz/OEM.cab.pks.7z - unpack once, to get the .cab.pks file and then using Yuki & Xb0xmod WP7 tool send it to phone.
Can't guarantee it will work though.
gbpucci said:
Hello everyone,
I just update my Omnia 7 (unbranded) yesterday using disconnect trick, from Nodo. My phone receive two updates.
But the compass app and Allshare dont work yet and the version of firmware, compared to other here, is outdated.
Os Version: 7.10.7720.68
Firmware revision number: 2424.10.11.1
Hardware revision: 3.15.0.4
Radio Software: 2424.11.2.2
Bootloader version: 5.2.1.4
Chip SOC: 0.36.2.0
Any tip for this situation ??
regards !!
Click to expand...
Click to collapse
I have updated my OMNIA 7 from 7720 RTM and Allshare doesn´t work either...
Os Version: 7.10.7720.68
Firmware revision number: 2424.11.8.5
Hardware revision: 3.15.0.4
Radio Software: 2424.11.7.2
Bootloader version: 5.8.1.9
Chip SOC: 0.36.2.0
Which compass app did you try ?
OndraSter said:
Try manually deploying this .cab.pks:
http://wp7.ondraster.cz/OEM.cab.pks.7z - unpack once, to get the .cab.pks file and then using Yuki & Xb0xmod WP7 tool send it to phone.
Can't guarantee it will work though.
Click to expand...
Click to collapse
Ok the update works !! Now i have the lastest versions !!
Compass app works fine, but Allshare really dont works yet !!!
Maybe we need new hardware !!!
Thanks !!
OndraSter said:
Try manually deploying this .cab.pks:
http://wp7.ondraster.cz/OEM.cab.pks.7z - unpack once, to get the .cab.pks file and then using Yuki & Xb0xmod WP7 tool send it to phone.
Can't guarantee it will work though.
Click to expand...
Click to collapse
Does this in any way affect the reading of HTML 5?
30 fps on Fish Tank
27 fps on Speed Reading
At least i dont see any improvement on Fish Tank demo !!
What about hidden SSID?
Hi all,
I have the same problem as gbpucci.
To be more specific, I'm in the exact situation.
Plus, I do not have the option to access the hidden wlan. It appears the "Advanced" button under the WIFI section but no "+" to add manual a network.
Can someone please ad some information regarding the Yuki & Xb0xmod WP7 tool solution, because I really have no clue how to manually deploy this .cab.pks file...
This solution it will help obtain the hidden wlan access?
Thank you in advance!
Regards,
O.
I'm also not too sure which tool you are referring.
Is it this one?
http://forum.xda-developers.com/showthread.php?t=1250869
I haven't updated yet. Still thinking whether or not to force. Some forced with no problems, some forced but did not get firmware update. Not sure why.
After update i can see + option on Advanced wifi setting. I use updatewp.exe provided with Yuki wp7 tool to apply the update.
c:\updatewp.exe /iu OEM.cab.pks
Works fine to me !!
WiFi has to be turned on first then the + button appears in advanced settings...
Is this the cab sender?
http://xboxmod.sylvester20007.com/tools/WP7 Update Cab Sender.zip
2424.11.7.2 is my radio fw after force update... But everyone is saying it should be 2424.11.27.2 .... So what is missing features in my device bacuse of this missing version...? Is there a place where I can go to check my fps rate and post it back here? The compass seems to work fine fine for me because I can seee the middle stick thing is moving.... I don't know of its giving m right directions or not... But at least it is moving...
Sent from my OMNIA7 using XDA Windows Phone 7 App
Purple11 said:
2424.11.7.2 is my radio fw after force update... But everyone is saying it should be 2424.11.27.2 .... So what is missing features in my device bacuse of this missing version...? Is there a place where I can go to check my fps rate and post it back here? The compass seems to work fine fine for me because I can seee the middle stick thing is moving.... I don't know of its giving m right directions or not... But at least it is moving...
Sent from my OMNIA7 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
Try this:http://ie.microsoft.com/testdrive/mobile/Performance/SpeedReading/Default.html
Btw, what compass app did you use?
I used compass 7... I think it gives wrong directions but the hardwareis working if it is moving maybe...
Here is my speed result from that website:
FPS: 28
Using: Internet Explorer 9 (Windows Phone 7.5)
Total Billboard Draws: 1314
Average Draw Duration: 35ms
Sent from my OMNIA7 using XDA Windows Phone 7 App
Same old radio version
I don't know, something is messed up...
I still have the old radio software version: 2424.11.2.2
And yes, I did activate first the Wifi and the checked for the "+" box but there's no sign of it. I might be dumb regarding WP7, but no not that dumb.
Sorry, but it seems that I can't find a way to deal with WP7 Update Cab Sender... it keeps sayin' that it doesn't find the file. But I have the file OEM.cab.pks
Any other ideas for me? I really need the hidden wlan function.
Thanks to all.
O.
You might need to rename the file to .cab.pkg or just .cab to make WP7 update cab sender notice it
Well, Compass 7 is working after installing that little bit of software. Unfortunately Allshare still is not.
Also gotten the + for adding hidden wifi routers.
Previous Firmware (Firmware revision number)
2424.10.10.6
Updated Firmware
2424.11.8.5
Allshare might not work on omnia 7 at all...
OndraSter said:
You might need to rename the file to .cab.pkg or just .cab to make WP7 update cab sender notice it
Click to expand...
Click to collapse
Will this method clear out all info on phone or will just be like the Zune updates that doesn't clear the contents? Thanks.
Hey mates,
my XZ1c (unlocked) just received the new OTA in Germany, security patch level October 1st.
Anyone an idea what has changed? There is no official changelog or at least I didn't find any
Hello.
I got it too.
No change log on the notification, so i do not know too.
BlueBorne vulnerability fixed
I can confirm BlueBorne vulnerability fix too. No news on camera fix :/ BTW Can we use somehow the BlueBorne vulnerability to root XZ1C? Or to backup TA partition (DRM keys)?
Good question...
Davka said:
BlueBorne vulnerability fixed
Click to expand...
Click to collapse
Yeah, but for that only the update didn't need 300MB I guess
Camera "distortion" (mind the quotes) is unchanged.
Anybody using a VPN to get this update? Because I just tried VPN locations in Germany, Japan, and Austria with no luck on getting the new OTA.
I think that would not work, it's based on the emei and rom canal on the phone, so using a vpn will not change anything.
If you are on a USA model, and that the update is not released yet for the USA version, changing for EU country will not change anything.
And even if it's released for usa, it could be a little bit later for your phone, as sometimes they restricted to some IMEI not to push on all the phone in the same time.
Just updated. Don't feel any different compare to .324 aside from october security update.
Sent from my XZ1 Compact using XDA Labs
3 new things I notice after using this firmware for 1-2 days:
1) The login process to google account with 2-steps verification activated is hassle free now. In previous firmware I had trouble getting and entering the verification code, and thus had to manually disable the 2-step verification before I could login.
2) Maybe placebo, but I feel I get a better and more stable mobile data connection. Previously it felt like even though the mobile data was active and the icon shows connected to 3G, but occationally I couldn't do anything related to internet connection until I turn off and on again the mobile data. Maybe it was due to bad signal from provider on that day too, I don't know.
3) Very minor adjustment; when we press the volume up/down button it used to show 'ring volume', but its now 'ring and notification volume'.
Still no update for my phone Is has a china IMEI. Maybe i just have to wait.
What's different in the firmware update..
I did an extract and compare against the UK 324 and 374 versions and came up with a rough list.
The contents of these SIN files are exactly the same:
adspso_X-FLASH-ALL-C93B.sin
amss_fs_1_X-FLASH-ALL-C93B.sin
amss_fs_2_X-FLASH-ALL-C93B.sin
appslog_X-FLASH-ALL-C93B.sin
bluetooth_X-FLASH-ALL-C93B.sin
bootloader_X_BOOT_MSM8998_LA1_1_O_77_X-FLASH-ALL-C93B.sin (all boot SINs, actually, but this is the one that gets loaded)
cache_X-FLASH-ALL-C93B.sin
diag_X-FLASH-ALL-C93B.sin
fsmetadata_X-FLASH-ALL-C93B.sin
ramdump_X-FLASH-ALL-C93B.sin
ssd_X-FLASH-ALL-C93B.sin
persist_X-FLASH-ALL-C93B.sin
Qnovo_X-FLASH-ALL-C93B.sin
userdata_X-FLASH-ALL-C93B.sin
All *.ta files are the same.
Now for the differences.
amss_fsg_X-FLASH-ALL-C93B.sin:
MCC 240 was moved from the [mcc_list name="eu_b4_mccs"] config to a new [mcc_list name="swe_mccs"] config.
elabel-G8441-row-row_201709190503668.1_47.1.A.2.374_X-FLASH-LTALABEL-C93B.sin:
Added a regulatory label for Malaysia.
fotakernel_X-FLASH-ALL-C93B.sin (Ramdisk only, didn't extract the kernel):
crashtag specifies new firmware version
sepolicy bits changed
prop.default has "ro.setupwizard.rotation_locked=false" added
kernel_X-FLASH-ALL-C93B.sin (Ramdisk only, didn't extract the kernel):
crashtag specifies new firmware version
sepolicy bits changed
init.sony-platform.rc had this line removed: setprop persist.bluetooth.btsnooppath "/sdcard/btsnoop_hci.log"
modem_X-FLASH-ALL-C93B.sin:
Changed audio, modem, qdsp6m, and sensor blobs
oem_X-FLASH-ALL-C93B.sin:
"ssid=_The Cloud X" added to preset_networks.conf
APN updates
"com.amazon.avod.thirdpartyclient.apk" added
ee_ims & telefonica specific modem configs added
Overlay APK changes (I didn't check the changes)
Version & region changes (R8B->R12B)
system_X-FLASH-ALL-C93B.sin:
/app/[lots changed, haven't extracted]
/bin/dnsmasq changed
/bin/customization/modem/* changed
/etc/firmware/(I honestly can't tell if it's a real change or just recompile changes)
/etc/permissions/privapp-permissions-google.xml added: permission name="android.permission.DISPATCH_PROVISIONING_MESSAGE"
/framework/(all oat, odex, art changed, no vdex's were changed except: boot-framework.vdex, boot-ims-common.vdex, boot-telephony-common.vdex)
/framework/framework-res.apk changed
/lib/hw/bluetooth.default.so changed
/lib/modules/* (I honestly can't tell if it's a real change or just recompile changes)
/lib/libandroid_runtime.so, libaudioflinger.so, libmediaplayerservice.so, libminikin.so, libpdfium.so, libsqlite.so, libstagefright.so, libstagefright_foundation.so, libstagefright_soft_avcdec.so, libvorbisidec.so
/lib64/hw/bluetooth.default.so
/lib64/libandroid_runtime.so, libaudioflinger.so, libdeqp_somc.so, libmediaplayerservice.so, libminikin.so, libnfc-nci.so, libpdfium.so, libsqlite.so, libstagefright.so, libstagefright_foundation.so, libstagefright_soft_avcdec.so, libvorbisidec.so
/priv-app/[lots changed, haven't extracted]
build.prop -> "ro.expect.recovery_id"
vendor_X-FLASH-ALL-C93B.sin:
/app/[lots change, haven't extracted],
/bin/hw/illumination_service
/bin/sct_service, sensors.qcom, updatemiscta
/etc/permissions/handheld_core_hardware.xml added
/etc/sepolicy/[files] some changes
/lib/camera/libexcal_multiframe_nr_plugin.so, libexcal_snapshot_ctrl_plugin.so
/lib/modules/qca_cld3_wlan.ko
/lib/soundfx/libdownmix.so, libreverbwrapper.so
/lib/libcammw.so, libexcal_system.so (face and object tracking?), libmmcamera2_iface_modules.so, libmmcamera2_imglib_modules.so, libmmcamera2_mct.so, libmmcamera2_sensor_modules.so, libmmcamera2_stats_modules.so, libOmxVenc.so, libpf.so (OMX video related), libril-qc-qmi-1.so
/lib64/soundfx/libdownmix.so, libreverbwrapper.so,
/lib64/libpf.so, libril-qc-qmi-1.so
build date changed
ro.setupwizard.rotation_locked=false added to props
There might be bits that I missed in the changed SINs, but the unchanged ones are unchanged.
Bear in mind that with the split firmware bits, sometimes it's difficult to determine if, say, "tzsuntory.b01" was actually changed, or if it was just a header difference due to a recompile. So I'm just ignoring the ones that I "think" are the same. That said, if I'm ignoring it, it's because it was contained in a SIN file that has other changes as well.
EDIT: I forgot to add that userdata_X-FLASH-ALL-C93B.sin is also unchanged.
I am stuck at the latest version of android 10 (.618) on my xperia xz2 compact H8314 and I have a big problem using whatsapp and other messaging apps like messenger and telegram, basically the voice notes sounds very low, I can record audio using sony audio recorder and works fine but the other apps dont, I have been looking for this thread all over the xz2 forum but could not find it so thats why I decided to create it, I have also looked in other webpages but it seems that are very few mentions of it, I found this one and tried to follow it, but I failed in my attempt.
https:// xperiafirmware. com/downgrade/
Any help/advise is welcome and even questions of what I have already tried.
I thought about any other alternatives like fixing the problem in Android 10 but I couldnt either.
Edit: I get the next error message when I am flashing the .ftf file that I downloaded there:
"Those data are not in the FSC scrip and will be skipped:
BOOT,DSP,FSG,MODEMST1,MODEMST2,RDIMAGE.
Do you want to continue?"
then I try to turn on my phone and get the message "your phone is corrupt and it wont start" or something like that.
I have owned several xperia phones in the past, the last one was xperia X compact and I remember (I could be wrong) that I was able to make a downgrade without unlocking my bootloader.
I succesfully downgraded from 10 to 9 using sonys flashtool with bootloader unlocked. But I'm not sure if it's possible to do it without unlocking at the moment. Why not just unlock the bootloader?
Tom 23 said:
I succesfully downgraded from 10 to 9 using sonys flashtool with bootloader unlocked. But I'm not sure if it's possible to do it without unlocking at the moment. Why not just unlock the bootloader?
Click to expand...
Click to collapse
Would be helpful if:
Where to get the Sony flashtool. (link?)
You could provide a link to how to unlock the bootloader. and
You could describe the "Downside" to unlocking the bootloader. What "no longer works"? Such as, will it no longer apply factory updates? Will Digital Rights Management (DRM) no longer work?
Seriously, my XZ2 Compact H8214 keeps reminding me (several times a day) that a firmware update is available, and I am sort of "scared to death" to do it. All I read are negative comments about what Android 10 has done to ruin people's phone. Without a way to "go back", I am seriously thinking of just ignoring these messages for weeks and weeks.
Tom 23 said:
I succesfully downgraded from 10 to 9 using sonys flashtool with bootloader unlocked. But I'm not sure if it's possible to do it without unlocking at the moment. Why not just unlock the bootloader?
Click to expand...
Click to collapse
Well first of all, unlocking bootloader voids warranty, then a number of several sony technologies will for sure stop working, Basically all proprietary technologies like audio, video and most importan thing, CAMERA enhancements, how I do know this? well because I have been reading a lot lately and also since some years ago, and by experience because back in the day I had an xperia x compact and I didnt remember to backup DRM keys before unlocking bootloader.
Anyway I have found a way to downgrade from android 10 to 9 without unlocking the bootloader, I am not sure about if I should make a new post with specific instructions( a guide) or just write them in this post.
Oh, yes. Please share. The more details the better. (Assuming that people "know basic things" is often incorrect. The things I don't know is FAR too big to list.)
UncleDick said:
Oh, yes. Please share. The more details the better. (Assuming that people "know basic things" is often incorrect. The things I don't know is FAR too big to list.)
Click to expand...
Click to collapse
Alright I am creating e a guide detailing things the best I can. hopefully I will finish it today.
ferluna18 said:
Well first of all, unlocking bootloader voids warranty, then a number of several sony technologies will for sure stop working, Basically all proprietary technologies like audio, video and most importan thing, CAMERA enhancements, how I do know this? well because I have been reading a lot lately and also since some years ago, and by experience because back in the day I had an xperia x compact and I didnt remember to backup DRM keys before unlocking bootloader.
Anyway I have found a way to downgrade from android 10 to 9 without unlocking the bootloader, I am not sure about if I should make a new post with specific instructions( a guide) or just write them in this post.
Click to expand...
Click to collapse
I have downgraded from 10 to 9 using official flashtool from sony (with bootloader unlocked) and my camera, audio, video etc. still works just fine. Maybe I just got lucky, but I think that by doing it through the tool provided by sony itself it shouldn't break anything. Which in my case, it didn't. Btw, thanks for the guide ?
Tom 23 said:
I have downgraded from 10 to 9 using official flashtool from sony (with bootloader unlocked) and my camera, audio, video etc. still works just fine. Maybe I just got lucky, but I think that by doing it through the tool provided by sony itself it shouldn't break anything. Which in my case, it didn't. Btw, thanks for the guide
Click to expand...
Click to collapse
Or maybe you don't know what you do, and happy for the nothing.
If you unlock the bootloader, you loose the TA partition (DRM keys). Your camera quality is worst, and some features lost (ps4 etc).
Well first of all, unlocking bootloader voids warranty, then a number of several sony technologies will for sure stop working, Basically all proprietary technologies like audio, video and most importan thing, CAMERA enhancements, how I do know this? well because I have been reading a lot lately and also since some years ago, and by experience because back in the day I had an xperia x compact and I didnt remember to backup DRM keys before unlocking bootloader.
Anyway I have found a way to downgrade from android 10 to 9 without unlocking the bootloader, I am not sure about if I should make a new post with specific instructions( a guide) or just write them in this post.[/QUOTE]
I really like to wait your post of downgrade 10 to 9.0 without bootloader unlock Coz i also don't know how to bcak up my DRM and how to restore.After upgraded to 9.0 to 10 while i opened my Camera it was appear unknown error i just wanna fix that problem.thz
Xz3 H9493:good::good::good:
Tom 23 said:
I have downgraded from 10 to 9 using official flashtool from sony (with bootloader unlocked) and my camera, audio, video etc. still works just fine. Maybe I just got lucky, but I think that by doing it through the tool provided by sony itself it shouldn't break anything. Which in my case, it didn't. Btw, thanks for the guide
Click to expand...
Click to collapse
williamgrant said:
Or maybe you don't know what you do, and happy for the nothing.
If you unlock the bootloader, you loose the TA partition (DRM keys). Your camera quality is worst, and some features lost (ps4 etc).
Click to expand...
Click to collapse
I just picked up an H8314 for use on Verizon in the US and it has Android 10 already.
@Tom 23 can you explain more about what you did? Details? Are you using an H8314? On Verizon? I've read in the XZ2 forums supposedly now unlocking on Android 10 still breaks some stuff but now not the camera?
@williamgrant can you provide/link a list of exactly what breaks when you unlock the bootloader? Perhaps what breaks depends on what version of Android you're on when you unlock?
I'm trying to determine/weigh the pros and cons of unlocking to root are, if its worth it, what am I giving up...
Mike7143 said:
I just picked up an H8314 for use on Verizon in the US and it has Android 10 already..
Click to expand...
Click to collapse
Do you notice specific problems with the H8314 on Verizon? I have been delaying the Android 10 firmware update because I cannot seem to find many reports of "how it works on Verizon".
I've only been using it for a little over 36 hours, but so far nothing glaringly wrong. Keep in mind thought that 36 hours ago I was using a 2013 Motorola Moto X running Android 5.1... now I'm on Android 10... So there's probably stuff that is a bug that I don't recognize is a bug!
My wife's had her H8314 on Verizon for about 6 months and it's on Android 10 as well. If she's not complained to me about anything then that's good! Then again, she's likely not at the same "level" as XDA forum members are!
I too am interested in how to roll back to Android 9 if it can be accomplished reasonably easily without giving up a bunch of stuff.
I've been plagued with issues on Android 10. Even with the most recent update things have not improved. The two things most annoying to me are the drastically reduced battery life (more than halved!! it doesn't even last a full day anymore!!) and the fact that MMS do not download correctly all the time anymore. I've also noticed that camera quality has gone down somehow, even though Android 10 was supposed to improve it...
Hello folks
I successfully downgraded my XZ2 Compact (H8314) from Android 10 to 9 using that info: "https://forum.xda-developers.com/showpost.php?p=82087435"
but I had a problem, I downloaded (using XPERIAFIRM) 52.0.A.11.32 South Korea version (I'm from Italy, but Italy version is not available) , every thing work fine except LTE (4G) signal, as frequency of two country is not compatible, then I installed Android 10 again and all was ok.
So... now my question is: do you know where I can found 52.0.A.11.32 image customized for Italy?
Regards,,,Carlo
Carlo_IT said:
Hello folks
I successfully downgraded my XZ2 Compact (H8314) from Android 10 to 9 using that info: "https://forum.xda-developers.com/showpost.php?p=82087435"
but I had a problem, I downloaded (using XPERIAFIRM) 52.0.A.11.32 South Korea version (I'm from Italy, but Italy version is not available) , every thing work fine except LTE (4G) signal, as frequency of two country is not compatible, then I installed Android 10 again and all was ok.
So... now my question is: do you know where I can found 52.0.A.11.32 image customized for Italy?
Regards,,,Carlo
Click to expand...
Click to collapse
hello Carlo i'm from italy too, do you solved? i tried with the guide on xperiafirm but i got the same error message of the user that started this topic. can you help me? thank you
Lorenzo.
lollixo said:
hello Carlo i'm from italy too, do you solved? i tried with the guide on xperiafirm but i got the same error message of the user that started this topic. can you help me? thank you
Lorenzo.
Click to expand...
Click to collapse
Hello. I downloaded some month ago rom for UK via Xperifirm. I deleted already ta-files according to description, and I added newsflasher (version 20) into same folder. I zipped complete prepared folder and uploaded it now. Should be okay for Italy.
https://mega.nz/file/y7oVSRoQ#iCXPSNeeUTXFNmgtuw-w_c5Xs_9mo54kzl8jhiGS0Uc
Greetings Odiad
PS: I am not so familiar with uploading files. i hope this link works.
Carlo_IT said:
Hello folks
I successfully downgraded my XZ2 Compact (H8314) from Android 10 to 9 using that info: "https://forum.xda-developers.com/showpost.php?p=82087435"
but I had a problem, I downloaded (using XPERIAFIRM) 52.0.A.11.32 South Korea version (I'm from Italy, but Italy version is not available) , every thing work fine except LTE (4G) signal, as frequency of two country is not compatible, then I installed Android 10 again and all was ok.
So... now my question is: do you know where I can found 52.0.A.11.32 image customized for Italy?
Regards,,,Carlo
Click to expand...
Click to collapse
odiad said:
Hello. I downloaded some month ago rom for UK via Xperifirm. I deleted already ta-files according to description, and I added newsflasher (version 20) into same folder. I zipped complete prepared folder and uploaded it now. Should be okay for Italy.
https://mega.nz/file/y7oVSRoQ#iCXPSNeeUTXFNmgtuw-w_c5Xs_9mo54kzl8jhiGS0Uc
Greetings Odiad
PS: I am not so familiar with uploading files. i hope this link works.
Click to expand...
Click to collapse
hello i can't believe you made this! you are such an hero for me! i m going to try your package, can you explain something? when the suite ask me something should i type y or n? can i follow this steps?
b) turn off your phone and connect phone to PC with holding volume down button
c) start NewFlasher from unpacked folder
d) every time NewFlasher ask you, hit N
e) after few minutes all is done and your phone gets new firmware
thank you so much in advance!
odiad said:
Hello. I downloaded some month ago rom for UK via Xperifirm. I deleted already ta-files according to description, and I added newsflasher (version 20) into same folder. I zipped complete prepared folder and uploaded it now. Should be okay for Italy.
https://mega.nz/file/y7oVSRoQ#iCXPSNeeUTXFNmgtuw-w_c5Xs_9mo54kzl8jhiGS0Uc
Greetings Odiad
PS: I am not so familiar with uploading files. i hope this link works.
Click to expand...
Click to collapse
lollixo said:
hello i can't believe you made this! you are such an hero for me! i m going to try your package, can you explain something? when the suite ask me something should i type y or n? can i follow this steps?
b) turn off your phone and connect phone to PC with holding volume down button
c) start NewFlasher from unpacked folder
d) every time NewFlasher ask you, hit N
e) after few minutes all is done and your phone gets new firmware
thank you so much in advance!
Click to expand...
Click to collapse
Odidad and Lollixo, would love to know if I just follow from Step 4 of this guide if I am using this file Odidad provided? Have you had success flashing Lollixo?
odiad said:
Hello. I downloaded some month ago rom for UK via Xperifirm. I deleted already ta-files according to description, and I added newsflasher (version 20) into same folder. I zipped complete prepared folder and uploaded it now. Should be okay for Italy.
https://mega.nz/file/y7oVSRoQ#iCXPSNeeUTXFNmgtuw-w_c5Xs_9mo54kzl8jhiGS0Uc
Greetings Odiad
PS: I am not so familiar with uploading files. i hope this link works.
Click to expand...
Click to collapse
Hi! I know this is 1.5 years later - but do you happen to still have this file? Thanks in advance.
landsome said:
Hi! I know this is 1.5 years later - but do you happen to still have this file? Thanks in advance.
Click to expand...
Click to collapse
Hi landsome. Probably I still have, but I am on a trip and I can't check this now.
I can do this not before Monday. When I'll find I will upload on Monday...
Hi there,
I’m a little confused reading a lot of posts over the internet.
ragarding Technisat MIB STD2 PQ with nav.
Firmware version 0245
unit is not hardware patched as I can see by opening unit.
Al available option codes enabled, so satnav CarPlay and Bluetooth are functional.
How can I perform a update to latstest firmware without loosing FEC?
Unit is installed in Golf mk6, time synchronisation with tacho is only thing what doesn’t work.
Help would be appreciated
Philipstech
the next upgrade is 253, update it shouldt make u lose fec/sawp codes.
But, i dont know if woth it update
philipstech said:
Hi there,
I’m a little confused reading a lot of posts over the internet.
ragarding Technisat MIB STD2 PQ with nav.
Firmware version 0245
unit is not hardware patched as I can see by opening unit.
Al available option codes enabled, so satnav CarPlay and Bluetooth are functional.
How can I perform a update to latstest firmware without loosing FEC?
Unit is installed in Golf mk6, time synchronisation with tacho is only thing what doesn’t work.
Help would be appreciated
Philipstech
Click to expand...
Click to collapse
I’ve got 253 patched software
Not sure exactly what, if anything, you’ll lose function wise but I’ve got it
Nunyabeezwax said:
Not sure exactly what, if anything, you’ll lose function wise but I’ve got it
Click to expand...
Click to collapse
Nunyabeezwax,
Can you provide met firmware 0478 to update 0253?
0253 was succeed, but to upgrade to 0478 is difficult.
Failure info:
cpu\customerupdateinfos\13\default\Dir already exitsts.
Logging tab by this system is 13.
Firmware original was 0245 and i succeed to upgrade to 0253.
Also FEC and CP i have managed to be executed
Philipstech
Nunyabeezwax said:
Not sure exactly what, if anything, you’ll lose function wise but I’ve got it
Click to expand...
Click to collapse
Metainfo2 files from both firmware versions included
Strange thing is that with version 0253 updating works, with version 0478 there is a error.
It would be great if somebody can help me.
Philipstech