Related
Hello everyone.
I got these cell phone and I need help for the SW and the other things that are needed for this device.
Does anyone have this phone, I need help?
Canelis said:
Hello everyone.
I got these cell phone and I need help for the SW and the other things that are needed for this device.
Does anyone have this phone, I need help?
Click to expand...
Click to collapse
Not heard of this device. Perhaps a chinese copy of HD2.
OK, found something. It runs on Android, so you can only run Android apps. BTW what exactly you mean when you say things needed?
Need to se is it last SW, and need GPS for this phone.CoPilot Live- not work on this device !!
Canelis said:
Need to se is it last SW, and need GPS for this phone.CoPilot Live- not work on this device !!
Click to expand...
Click to collapse
It runs 2.2 (as mentioned on the web), I don't have any idea if it can be upgraded, as you may know 2.2 isn't the latest version.
For GPS, you can check its specs if it has GPS or not, if yes then you can install the apps from the market otherwise perhaps connect an external GPS, although I am not sure weather an external will work or not.
You can click on 'Thanks' button, if I helped.
Model number : T8585
Android version: 2.3.4
Based Version : MAUI.11AMD.W11.19.SP.V1,2011/6/23 00:50
Need "working" GPS !!!!!!!
Maybe it could help us to help you if you could post the link.
The chinese website where I saw this, mentioned Android 2.2.
Many app not work on this mobile !
Maybe this will help : - h**p://www.efox-shop.com/hd9-mtk6573-4-3-zoll-kapazitiver-touchscreen-handy-wlan-umts-android-2-2-gps-dual-kamera-dual-sim-bluetooth-p-236121
since it is running android, so the compatible android apps should run on it, but since its a Chinese clone, no guarantees.
You can trying looking at other android phones by HTC or some other brand, to be safe.
You can try this rom Update_HD2_3G.zip www.multiupload.com/XOVS2HZTHO to remove all chinese aplications and to improve everything.
forum.china-iphone.ru/viewtopic.php?f=22&t=15521
Installation Guide
http://forum.xda-developers.com/showthread.php?t=1423489
For fix GPS:
Enter *#*#3646633#*#*
Go to YGPS
Wait for the green satellites appear.
Go to NMEA Log
Click "save" wait 5 minutes and then click "stop". Repeat the process after 1 hour.
Is your cellphone the same of this?
fastcardtech.com/goods.php?u=41964&id=6655
I bought 1 of them.
Now HTC mobile phone is also very popular in China. But i am sorry i don't have it. It is a little expensive.
Is it upgradable to ICS???
.
Thread moved. Would advise you to read forum rules and post in correct section.
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.)
Hi,
Sharing these tools which were kindly shared on the Joying Forums (STT / STT-TEC) firmware for upgrading/recovering PX5 SOMs using the SDCARD create tool. On review, the zip contains additional tools to customise, create, unpack, repack firmware.
These tools may be of a breakthrough to both recovery and customising PX5 Firmware - the SDCARD create tool may be able to recover corrupt/bootlooping PX5 units without hardware mods, as the PX3 version results in a black screen when trying.
Note: change [config.ini] to Selected=2 to force english.
[Language]
Kinds=2
Selected=2
LangPath=Language\
Note Joying PX5s are STT and not HCT, the SOMs may be similar but the MCU code/comms may be different. e.g. Joying doesnt use MTC style apps, but this may be similar - unknown. Also note that the Joying MCU is different in terms of the filename/structure, but probably the very same hardware. If someone has one of these Joying PX5 units, would appreciate any info such as PX5 SOM module PICs, MCU pics/type, mainboard Pics. I havent attempted to flash a Joying MCU and Px5 update over my HCT as probably nothing to gain.
Download HERE
Note - Make your own OTG cable from a USB cable and two resistors!.
This indeed looks very promising. In fact if I understand properly it's able to create the directory structure on an SD card to recover even from completely busted ROM content.
It basically turns an update.img into sdupdate.img which can be flashed from an sdcard. I currently can only assume that the PX5 SoM respectively Rockchip boot process checks if certain files exist on any attached file system and if they do it will start recovery. Just like almost any mobile phone or ARM based hardware like routers, access points or similar I ever recovered.
Given this it will be a matter of time to figure out how to recovery-flash Android 8 on PX5 SoM. I started to have a look at what is available but the Android 8 ROM found in some file shares seems to be an OTA image and not a recovery image. Using those tools and tools like the included AFPTool (or 3rd party imgRePackerRK) it might be possible to build a recovery image. Although I am not sure if the OTA image even contains all required files. Probably not. The system image perhaps only contains updated files and might be incomplete.
Also the fact that this Android 8 image is an OTA image yields the question who is providing OTA images for PX5 units. At least I am not aware about any manufacturer distributing OTA updates.
The tools you provided also includes an interesting utility: RKOsConfig.exe
Unfortunately it's all in Chinese only but some items are obvious. It looks like a tool to pre-configure the Android ROM for specific device. Allowing to set DPI, system language, time zone, video decoder, USB and UART type and specifically also the screen type where there are 2 presets in lcdlist.ini for 1024x600 and 800x480 screens.
The toolset also contains a command-line tool (RKImageMaker.exe) and a sample batch script (mkupate.bat) which shows how update.img can be converted to sdupdate.img as well as how the update.img is packed.
Unfortunately the Android 8 OTA image seems not to include some of them like kernel.img, misc.img, recovery.img and resource.img. Likely since the OTA update does not ship them. Moreover system.img might be covered by system.new.dat but this might contain only the files which are updated via OTA and might not include some of the files.
So it needs a bit of further analysis and perhaps we also need to wait for the first update image for Android 8 units (not OTA) to appear. I have also extracted an older Android 6 update.img which contains all the required files, so I guess the Android 8 OTA update is likely insufficient but future full-image updates will provide all the data to create recovery sdupdate.img to be flashed on Android 6 units.
SkyBeam2048 said:
This indeed looks very promising. In fact if I understand properly it's able to create the directory structure on an SD card to recover even from completely busted ROM content.
It basically turns an update.img into sdupdate.img which can be flashed from an sdcard. I currently can only assume that the PX5 SoM respectively Rockchip boot process checks if certain files exist on any attached file system and if they do it will start recovery. Just like almost any mobile phone or ARM based hardware like routers, access points or similar I ever recovered.
Given this it will be a matter of time to figure out how to recovery-flash Android 8 on PX5 SoM. I started to have a look at what is available but the Android 8 ROM found in some file shares seems to be an OTA image and not a recovery image. Using those tools and tools like the included AFPTool (or 3rd party imgRePackerRK) it might be possible to build a recovery image. Although I am not sure if the OTA image even contains all required files. Probably not. The system image perhaps only contains updated files and might be incomplete.
Also the fact that this Android 8 image is an OTA image yields the question who is providing OTA images for PX5 units. At least I am not aware about any manufacturer distributing OTA updates.
The tools you provided also includes an interesting utility: RKOsConfig.exe
Unfortunately it's all in Chinese only but some items are obvious. It looks like a tool to pre-configure the Android ROM for specific device. Allowing to set DPI, system language, time zone, video decoder, USB and UART type and specifically also the screen type where there are 2 presets in lcdlist.ini for 1024x600 and 800x480 screens.
The toolset also contains a command-line tool (RKImageMaker.exe) and a sample batch script (mkupate.bat) which shows how update.img can be converted to sdupdate.img as well as how the update.img is packed.
Unfortunately the Android 8 OTA image seems not to include some of them like kernel.img, misc.img, recovery.img and resource.img. Likely since the OTA update does not ship them. Moreover system.img might be covered by system.new.dat but this might contain only the files which are updated via OTA and might not include some of the files.
So it needs a bit of further analysis and perhaps we also need to wait for the first update image for Android 8 units (not OTA) to appear. I have also extracted an older Android 6 update.img which contains all the required files, so I guess the Android 8 OTA update is likely insufficient but future full-image updates will provide all the data to create recovery sdupdate.img to be flashed on Android 6 units.
Click to expand...
Click to collapse
Hotaudio/Dasaita has a OTA update function since a few months. The update file is also from HA. I think that it is only a matter of time that a .img file from another reseller or even hotaudio will be published and then it should be possible to update
Oberbergler said:
Hotaudio/Dasaita has a OTA update function since a few months.
Click to expand...
Click to collapse
Oh, I didn't know. Are they shipping OS updates on a regular base now or announced to do? Perhaps even including Android security updates? (haha, this might be just a dream)
If they do that would be a real step ahead and a good reason to buy Dasaita/HA units in the future. Although the OTA updates are likely also shipped to 3rd party units if they run HA ROM. I wonder how HA deals with this as OTA updates will be tested on HA units only and if they break some 3rd party units via OTA update they might get support inquiries from customers which don't even have a HA unit.
But generally I regard this as a huge step ahead.
Oberbergler said:
The update file is also from HA. I think that it is only a matter of time that a .img file from another reseller or even hotaudio will be published and then it should be possible to update
Click to expand...
Click to collapse
This forum is quite active. Does anyone have any contacts to HCT?
I guess they might not want to talk to modders and developers directly...
I really like Dasaita/HA is present here and publishing regular updates. I just bought a car-specific unit with Anroid before actually knowing about MTCD or PX3/PX5 at all. Now after being in this discussions for a while my favorite seller would be Dasaita/HA. Unfortunately they don't have a car-specific model for me but for future purchases it will be my first address to check.
@marchnz - @mum1989 has an Oreo unit, he has offered to try and dump the ROM
SkyBeam2048 said:
.
This forum is quite active. Does anyone have any contacts to HCT?
Click to expand...
Click to collapse
Try their website :
http://en.hctsz.com/
SkyBeam2048 said:
Oh, I didn't know. Are they shipping OS updates on a regular base now or announced to do? Perhaps even including Android security updates? (haha, this might be just a dream)
If they do that would be a real step ahead and a good reason to buy Dasaita/HA units in the future. Although the OTA updates are likely also shipped to 3rd party units if they run HA ROM. I wonder how HA deals with this as OTA updates will be tested on HA units only and if they break some 3rd party units via OTA update they might get support inquiries from customers which don't even have a HA unit.
But generally I regard this as a huge step ahead.
This forum is quite active. Does anyone have any contacts to HCT?
I guess they might not want to talk to modders and developers directly...
I really like Dasaita/HA is present here and publishing regular updates. I just bought a car-specific unit with Anroid before actually knowing about MTCD or PX3/PX5 at all. Now after being in this discussions for a while my favorite seller would be Dasaita/HA. Unfortunately they don't have a car-specific model for me but for future purchases it will be my first address to check.
Click to expand...
Click to collapse
I have installed the HA ROM on my GS and tried once in November to update via OTA knowing that hotaudio has released here in the forum a newer ROM than the one I had installed on my unit but it didn't work. Don't know if it was because I have a GS or if they didn't release the update via OTA.
Don't expect security patches. They don't care about them :laugh:
typos1 said:
Try their website : http://en.hctsz.com/
Click to expand...
Click to collapse
OK. My question was rather towards the community if someone ever tried.
Their website leaves little hope that they are even open to a collaboration. The english page is very incomplete and only chinese page seems to ahve some Sofia and PX3 boards listed. As far as I can see they are manufacturing some standard SoM they market to resellers as we know. Not sure though about the design of MTCx main boards. As many sellers seem to have very similar designs this makes me believe they are perhaps also designed by HCT or at least there is some reference design available to all unit manufacturers. Moreover some apps on our units are developed by HCT directly. Apps which interface with the MCU. So I believe HCT either provides the design or is manufacturing the complete unit, not only the SoM.
Anyway we might actually need a translator or someone in china to get in direct contact with HCT and it's unlikely for such companies to collaborate with the community. Nevertheless I have sent them a mail asking about community involvement. Maybe I go the wrong direction here and chances to succeed are near-zero, but hey; you don't know if you don't try.
Oberbergler said:
I have installed the HA ROM on my GS and tried once in November to update via OTA knowing that hotaudio has released here in the forum a newer ROM than the one I had installed on my unit but it didn't work. Don't know if it was because I have a GS or if they didn't release the update via OTA.
Don't expect security patches. They don't care about them :laugh:
Click to expand...
Click to collapse
I wonder if the OTA does an MCU check as the Lollipop update on KLD MTCB/C units did ? You could try flashing an HA MCU and seeing if it updates via OTA after. If it does then it could be quite easy for a dev to work around it as @dsa8310 did to allow Lollipop on any MTCB/C unit.
typos1 said:
I wonder if the OTA does an MCU check as the Lollipop update on KLD MTCB/C units did ? You could try flashing an HA MCU and seeing if it updates via OTA after. If it does then it could be quite easy for a dev to work around it as @dsa8310 did to allow Lollipop on any MTCB/C unit.
Click to expand...
Click to collapse
I'm not playing anymore with MCU's since I've done exactly that what you've suggested me. The HA MCU converted my unit into a HA with many problems. When I tried to go back to GS I had the version unmatch error. Fortunately the seller exchanged my unit.
SkyBeam2048 said:
OK. My question was rather towards the community if someone ever tried.
Their website leaves little hope that they are even open to a collaboration. The english page is very incomplete and only chinese page seems to ahve some Sofia and PX3 boards listed. As far as I can see they are manufacturing some standard SoM they market to resellers as we know. Not sure though about the design of MTCx main boards. As many sellers seem to have very similar designs this makes me believe they are perhaps also designed by HCT or at least there is some reference design available to all unit manufacturers. Moreover some apps on our units are developed by HCT directly. Apps which interface with the MCU. So I believe HCT either provides the design or is manufacturing the complete unit, not only the SoM.
Anyway we might actually need a translator or someone in china to get in direct contact with HCT and it's unlikely for such companies to collaborate with the community. Nevertheless I have sent them a mail asking about community involvement. Maybe I go the wrong direction here and chances to succeed are near-zero, but hey; you don't know if you don't try.
Click to expand...
Click to collapse
Yes, the site is rubbish.
The motherboards are designed and made by each manufacturer to, as youve said, a set of standards that meet certain criteria so that ROMs and (most) MCUs are interchangeable, although each motherboard may be a different design.
Almost all sellers (HA is the only one who sells and manufacturers as far as I can remember) are entirely separate from the manufacturers and have nothing to do with the design or manufacturing.
It used to be though that "MTC" was behind the development of the SoM software, then it was thought htta HCT was behind it, in the light od @marchnz's first post I m not sure this is correct now.
Joying px5 units are not syu/fyt, FYI.
gtxaspec said:
Joying px5 units are not syu/fyt, FYI.
Click to expand...
Click to collapse
If not, do you know what they are?
marchnz said:
If not, do you know what they are?
Click to expand...
Click to collapse
Uncertain, would need access to a live unit.
gtxaspec said:
Joying px5 units are not syu/fyt, FYI.
Click to expand...
Click to collapse
There are no "joying" units - Joying are a seller, I take it you mean Shenzhen Joyous RK3368/PX5 units ?
Although I was under the impression that Joyous no longer made MTC units and had switched to making the "009" MCU (ie non MTC) Intel units.
I gather that @marchnz has seen ".syu" and "fyt" on he motherboard or SoM and thats why he suggested that in his first post.
gtxaspec said:
Uncertain, would need access to a live unit.
Click to expand...
Click to collapse
So without access to a unit what makes you say that ?
typos1 said:
There are no "joying" units - Joying are a seller, I take it you mean Shenzhen Joyous RK3368/PX5 units ?
Although I was under the impression that Joyous no longer made MTC units and had switched to making the "009" MCU (ie non MTC) Intel units.
I gather that @marchnz has seen ".syu" and "fyt" on he motherboard or SoM and thats why he suggested that in his first post.
So without access to a unit what makes you say that ?
Click to expand...
Click to collapse
Look at the kernel and file system. Fyt units are very specific. Joyous is a different reseller than joying also. Dunno what 009 unit is. FYT makes their own custom SoM with various cpu's.
gtxaspec said:
Look at the kernel and file system. Fyt units are very specific. Joyous is a different reseller than joying also. Dunno what 009 unit is. FYT makes their own custom SoM with various cpu's.
Click to expand...
Click to collapse
Joyous is NOT a seller, Joyous is the manufacturer of all "JY" units, its Joying that is a seller.
An 009 MCU unit is a non MTC Intel unit.
I dont think the kernel or software are relevant, we re talking about MTCD/E hardware not software.
I ve not seen any MTCB/C/D/E SoMs without "HCT" on them - HCT makes all MTC SoMs, at least thats what has been established over the last 3 years, but please if youve got any photographic evidence to the contrary post it here to prove otherwise.
typos1 said:
Joyous is NOT a seller, Joyous is the manufacturer of all "JY" units, its Joying that is a seller.
An 009 MCU unit is a non MTC Intel unit.
I dont think the kernel or software are relevant, we re talking about MTCD/E hardware not software.
I ve not seen any MTCB/C/D/E SoMs without "HCT" on them - HCT makes all MTC SoMs, at least thats what has been established over the last 3 years, but please if youve got any photographic evidence to the contrary post it here to prove otherwise.
Click to expand...
Click to collapse
It is relevant, because from a live system, you can tell what SoM the unit is using
Also, Shenzhen Joyous (which was a manufacturer/seller) does not currently make any PX3 or PX5, let alone any Intel units. This may have been true in the past, no longer.
Also, HCT does make a variety of SoM's, but they certainly don't make all of them.
gtxaspec said:
Joying px5 units are not syu/fyt, FYI.
Click to expand...
Click to collapse
Quite right, the JY PX5 is a STT, according to the RKOSTOOL: 深圳市齐顶电子科技有限公司 - Shenzhen Top Electronics Technology Co., Ltd. Top.
And a quick google lists the following (from the "russian forum"):
JOYING
Model: px5
Procecor: 8 core 64bit CUP Coretex- [email protected] G
Machine code: 050014390000AA55
Android 6.0.1
Assembly number: MXC89L release-reys V6.4
Kernel version: 3.10.0
stt-tec @ ubuntu1204 # 48
Tue Aug 22 17:22:39 CST 2017
APP-TP6735 0.0.51
MCU-TP6735 4.31
BT-SD / 2017: 09: 13: 17: 38: 49 fw: Jun 29 2017 23:57:52
.deleted
Please ask
https://www.facebook.com/profile.php?id=100010581348702
He is a member in this forum.
He can speak English and have contact to hct
Im sure he can help. I know that he listen to any wish and want help the community to get further...
---------- Post added at 03:42 AM ---------- Previous post was at 03:37 AM ----------
Also try to contact boyka from joying team his skype name is "mcloge"
Maybee he can help to
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...
I’m new to the android radio scene, asking for some help here. I’ve been reading in the forums here about “version unmatch” and the corresponding MCUs. I have a new QCM6125 running android 12. Things were working fine, but there were a few bugs. The seller sent me an update “6125 GS16 12.0 20220928”. I uncompressed it, put it on a usb, and updated the radio with “update.zip”. Upon reboot I got the version unmatch and beep. I mentioned this to the seller, they tried to send me another update, but it quits with an error.
Am I correct in assuming I shouldve got a CHS update, and they gave me a GS? What do I need to fix this?
Have a look through MTCD forums, there's quite a lot of information covering that.
Failing that, what does the reseller suggest, have they provided any support and does that work?
marchnz said:
Have a look through MTCD forums, there's quite a lot of information covering that.
Failing that, what does the reseller suggest, have they provided any support and does that work?
Click to expand...
Click to collapse
Thanks for getting back to me. I've been scouring the MTCD forums the past few days. Learning a lot (seeing your name a lot too), but not necessarily getting where I need to yet. Frankly it seems to be leaving me with more questions than answers.
So the seller's response to my "version unmatch" problem was to ask me to downgrade (assuming A10), and sent me another file (HCT7B_SC138_10.0_OTA(20220520).zip) which quits the install and goes into recovery mode. I made a youtube vid of it here (per seller request):
Later they sent me a third update (6125 GS16 2022.3.3.zip) which by the name looks to be similar to my first A12 update, but an earlier version? It quit and did the same thing as the A10 downgrade above.
From the forums and my recovery screen I see that I DON'T have a Rockchip, and thus downgrades might not be possible? Also, the CHS seems to be more rare. I did see the MTCH_CHS_V3.80 on 4pda (my current is v3.78), but can't seem to download it (404 error). My canbus decoder box says it’s a CHS, so I'm assuming CHS is the correct MCU? If so I'm not sure where the "version unmatch" error is coming from. Could that be something I've changed in the factory settings, like the steering wheel setting?
I've tried the first update that caused the version unmatch problem (6125 gs16 12.0 20220928.zip) a second time, and it installs and completes just fine, but doesn't get rid of the problem.
I read about the version unmatch unlock app, and read it didn't work with A12, tried it anyways, and it quit like others said.
I've been ghosted by the seller for about 2 weeks now. So on one hand I feel like I'm stuck, but from reading here, it could be as simple as updating the MCU? Any help is greatly appreciated.
What processor do you have? I think Qualcomm Snapdragon 665 and that is a different processor than in these threads, PX is being addressed here. For MTCD/E, the Red "version mismatch" is an MCU problem, not a firmware problem. Did the seller not include the MCU-dmcu.img update with the first firmware update, which was also installed when you installed the firmware? You probably installed another manufacturer, first find out what you had originally, if you don't know, write to the seller. You can try McuUnmatchUnlock app, but I don't know if it works on Qualcomm Snapdragon 665, you have to try it yourself:
MTCD - Verified Cross compatible MCUs
This thread is to document MCUs found to be cross-compatible between MTCD units, which includes PX3 and PX5 variants, which share identical mainboard hardware and MCU Chip STM32F091. The following MTCD & MTCE (as of v2.56) MCUs have been...
forum.xda-developers.com
Instructions:
Solution for 'Version unmatch' (I hope final)
I know that this topic has already been discussed many times in many threads (most in MTCD - Verified Cross compatible MCUs). I also know that there is a known solution to this problem. However, there are users who report that they still have a...
forum.xda-developers.com
Or, if you haven't done any MCU update and you're sure you have CHS, then MTCH_CHS_V3.80 is also here:
Яндекс
Найдётся всё
disk.yandex.ru
There is not much about Qualcomm Snapdragon 665 here even on 4pda, I tried the search engine:
Search results for query: Qualcomm Snapdragon 665
forum.xda-developers.com
There is one Qualcomm Snapdragon 665 thread on the 4pda with MCU: MTCH_xxx, but not much here either:
Головные устройства Qualcomm Snapdragon 665 (QCM6125) 8 ядер Android 10 - Обсуждение - 4PDA
Головные устройства Qualcomm Snapdragon 665 (QCM6125) 8 ядер Android 10 - Обсуждение, [Головное устройство][Android]
4pda.to
Pavel-71, thanks for the response. Yes it is a Qualcomm Snapdragon 6125, 4G/LTE, 6GB RAM, 128GB ROM, 8-core I bought from AVIN. You are correct that they did not give me a separate MCU *.img file. All that was located in the files they provided me was the android "update.zip" file. I have never updated the MCU, until now I had assumed it was included in the update.zip file. I read more last night that it is not so. Android is update.zip, MCU is dmcu.img. The seller's instructions to me make no mention of an MCU image.
I had requested from the seller 3 days ago, when I first started reading about this, they send me the MCU image and config file. I've heard nothing back.
So if I understand what's happening here, it sounds like my MCU (CHS) is likely the original, because I never updated it with an *.img file, and it’s possible the seller gave me a snapdragon version of A12 that was meant for a different MCU, causing the mismatch? If so, wouldn't my android version be wrong, and shouldn't I need an android version made for CHS? Is there a way to tell which MCU the android version is made for?
I also read that the Wifi version can't be installed on the 4G/LTE version, and it's possible if the first is wrong, the second and third files that wouldn't install could be wifi only versions of Android, when I have a 4G/LTE.
In my opinion, you can't downgrade to android 10 using update.zip, for that you should use some QPST tool and the update.img file, which contains the recovery of android 10. And the installation is done from a computer with a usb cable, but I'm just guessing. I noticed you didn't select wipe data and flash format before updating. Try updating again with 6125 GS16 12.0 20220928, and this time mark data wipe in the table, I think when you installed the GS update on CHS, without data wipe, it gave a mismatch error. The German company M.I.C. it has its updates on Qualcomm Snapdragon and there is also a guide where it recommends wiping the data to remove any errors:
SYSTEMUPDATES für Snapdragon 665
Passt für alle Geräte mit Prozessor Snapdragon 665 (QCM 6125): AV8V7(-Pro) AV9V2(-Pro) AU10 AU7 AVT7(-Pro) AVTO7(-Pro) AF7 AO7 AO8 AB9
www.mic-autoradio.com
Pavel-71 said:
In my opinion, you can't downgrade to android 10 using update.zip, for that you should use some QPST tool and the update.img file, which contains the recovery of android 10. And the installation is done from a computer with a usb cable, but I'm just guessing. I noticed you didn't select wipe data and flash format before updating. Try updating again with 6125 GS16 12.0 20220928, and this time mark data wipe in the table, I think when you installed the GS update on CHS, without data wipe, it gave a mismatch error. The German company M.I.C. it has its updates on Qualcomm Snapdragon and there is also a guide where it recommends wiping the data to remove any errors:
SYSTEMUPDATES für Snapdragon 665
Passt für alle Geräte mit Prozessor Snapdragon 665 (QCM 6125): AV8V7(-Pro) AV9V2(-Pro) AU10 AU7 AVT7(-Pro) AVTO7(-Pro) AF7 AO7 AO8 AB9
www.mic-autoradio.com
Click to expand...
Click to collapse
Thanks for getting back to me. I looked at that MIC page you linked to, followed the instructions, checked wipe data and did the restore with the above mentioned update.zip file. The update completed successfully, it did erase all my data, apps, and settings. It did NOT fix the version unmatch issue though.
While I'm here, my CPU says, AArch64 Processor rev 2 (aarch64) @1.8GHz (x8)
Too bad it didn't help. Hard to advise now. If the seller doesn't call and send the original GS update, I would try the McuUnmatchUnlock app. If that doesn't help, try updating MTCH_CHS_V3.80. The last option, but I don't know if it's safe, is to try an update from M.I.C. I really don't know how it is with the Qualcomm Snapdragon 665, but firmware from other vendors can be installed on PX processors without any problems, I installed HCT7, HCT4, GS16, M.I.C., CHS, Hal9k firmware on the PX5 without any problems. The problem is with the MCU update, here when using another manufacturer unmatch can occur, sometimes it helps to use the original manufacturer or the McuUnmatchUnlock application. For more serious problems, a special programmer is needed. Try to register on 4pda and ask here, maybe they can give you better advice, CS-X is excellent, it has MCU thread in the message.
Pavel-71 said:
Too bad it didn't help. Hard to advise now. If the seller doesn't call and send the original GS update, I would try the McuUnmatchUnlock app. If that doesn't help, try updating MTCH_CHS_V3.80. The last option, but I don't know if it's safe, is to try an update from M.I.C. I really don't know how it is with the Qualcomm Snapdragon 665, but firmware from other vendors can be installed on PX processors without any problems, I installed HCT7, HCT4, GS16, M.I.C., CHS, Hal9k firmware on the PX5 without any problems. The problem is with the MCU update, here when using another manufacturer unmatch can occur, sometimes it helps to use the original manufacturer or the McuUnmatchUnlock application. For more serious problems, a special programmer is needed. Try to register on 4pda and ask here, maybe they can give you better advice, CS-X is excellent, it has MCU thread in the message.
Click to expand...
Click to collapse
I initially did try the mcuunmatchunlock.apk, and the app quits and fails upon opening. It was one of the first things I tried when I found this forum. I appreciate the effort and attempt, felt a little alone and on my own here until I found this forum.
If I understand what I’ve read in the many pages here, wouldn’t getting another GS android cause the same issue? Correct me if I’m wrong, but if I have a CHS MCU, I either need an android built for CHS & 4G/LTE (from seller), OR attempt to change the MCU to GS, which could potentially brick me if not compatible.
Sorry I wrote it wrong, of course I meant the original CHS firmware. Of course you are right about MCU, you should use CHS.
Well, the seller (AVIN) finally got back to me, "Sorry for the inconvenience. You can send back the unit for a replacement." I would've rather just installed the correct update.zip file, but this is better than nothing. Thanks for the help, and at least I found a new interesting forum.