Hi,
Does anyone know if it possible to extract/copy an APK's signature and how?
I have noticed all CERT.RSA files in APK's signed with the same key are very similar, apart from the last few bytes, so i am thinking there must be a way.
Ne0
from my understanding it is not possible, as it would ridicule the whole process of signing the apk in the first place. then again i am everything else than an expert on this topic...
One would have to ask the question as to why you would want to do this in the first place?
Regards,
Dave
foxmeister said:
One would have to ask the question as to why you would want to do this in the first place?
Regards,
Dave
Click to expand...
Click to collapse
that's the thing. if it was possible there would be no reason to sign the app in the first place. it is signed so you can make sure who the dev is (or that the dev is the same as the one who made the previous version). if you could extract and reuse that signature, where's the meaning in signing it at all?
and there are only two obvious reasons one would want to do that: he lost his key, or he wants to fake the source of an aop...
kendong2 said:
that's the thing. if it was possible there would be no reason to sign the app in the first place. it is signed so you can make sure who the dev is (or that the dev is the same as the one who made the previous version). if you could extract and reuse that signature, where's the meaning in signing it at all?
and there are only two obvious reasons one would want to do that: he lost his key, or he wants to fake the source of an aop...
Click to expand...
Click to collapse
Personally, I would be interested if there was a way to do it, because I would like to update a system app on my phone using a modified apk (in my case I use android 12 that comes with Samsung files 13 and I would like to update it to the version 14 which is only supposed to be compatible with android 13. I changed the min SDK requirement and resigned the v14 apk but because the signature is different, the app just won’t update).
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
Hello! I currently have this version of MCU: MTCE_LM_V2.75_1
Is it important to update MCU? Are there risks? After the installation should I configure something?
From the radio I can not update MCU, it does not find any update. But in a post of this forum (Dasaita) I have seen an update is it compatible with my radio unit? MTCE_HA_V3.06.zip
I have a PX3 of 2Gb.
Thank you
I just found this MCU file: MTCE_LM_V3.01c20190111 better this update? I do not know what is the latest MCU version of MTCE_LM_V2.75_1
It's better to keep it up to date, even when you dont experience issues with the device.
The updates are normally not that hard to install and version 3 has the function of teleconference within.
I noticed with my upgrade that the device doesnt freeze anymore during boot. But i had 1.9 installed and now 3.00
d5stick said:
It's better to keep it up to date, even when you dont experience issues with the device.
The updates are normally not that hard to install and version 3 has the function of teleconference within.
I noticed with my upgrade that the device doesnt freeze anymore during boot. But i had 1.9 installed and now 3.00
Click to expand...
Click to collapse
Could you tell me what is the most updated version of this MTCE_LM_V2.75_1? PX3 2Gb. Thank you
I thought the rom for the MCU is 3.01 for LM, you can find those on the forum, only a good search is required.
I have the GS version but i do not recommend installing an MCU from another supplier.
The android PX3 2GB roms can be found anywhere. Search for PX3 ROM LM.
Can somebody help me please
Can somebody help me with a mcu update file please as it keeps shutting down when using gps applications
black_ps said:
Can somebody help me with a mcu update file please as it keeps shutting down when using gps applicstions
Click to expand...
Click to collapse
Not an MTCD.
What do you mean?
marchnz said:
Not an MTCD.
Click to expand...
Click to collapse
black_ps said:
What do you mean?
Click to expand...
Click to collapse
Your unit is not an MTCB/C/D/E, asking in the wrong forums. Read on.
This entire thread is a waste of space in that there are more appropriate places the OP could have posted in or at least searched first, but that's another matter.
I have a MTCE_XRC_V2.79k_1 which has the Intel Sofia cpu. What MCUs can I use?