No. Since the uis7862 Android 10 versions after end 2019, dynamic partitions are used. They are always read-only, apart from during flash. That's why you need to "simply" flash it.
Hmm... well, I'll look around a bit more and will report back if I find anything.No. Since the uis7862 Android 10 versions after end 2019, dynamic partitions are used. They are always read-only, apart from during flash. That's why you need to "simply" flash it.
Atoto's have always been slightly different, also before they switched to FYT. I really have no idea.
Is there any way to get a SplitScreen shortcut to be run via this method? The list only sees apps and not the created shortcuts that starts two apps in split screen
- Simply create an app that does what you want it to do without looking at the FYT unit intents. In Q19 I describe that the uis7862 FYTs allow you to specify which apps should be started coming from deep-sleep/cold boot. Simply add your app to that list and then do inside your automatically started app whatever you want to do from that app.
No, it's not. In Android 10 that has changed as a new "security improvement" (think of it what you want). It is no longer allowed by an app to change the active screen of another app. Only a user-action can do that. Otherwise "your app" could push anything aside if it wants to.
Contents of a firmware zip:
- AllAppUpdate.bin: Special file that contains all FYT apps (This can be (un)packed with any (un)zipper, but I prefer 7-zip). This file also contains special files with reseller specific configs. This one is only interchangeable between the same reseller-id, unless you change that reseller-id.
The AllAppUpdate.bin is actually a password protected zip archive. You can use any zip, but preferably 7-zip for your platform (Linux, MacOS, windows) to create, modify or extract it.
Specifications: zip format, non-compressed (store), password 048a02243bb74474b25233bda3cd02f8
Unzip is simple: you only need to specifiy the password.
When (re)creating a new AllAppUpdate.bin, make sure you follow the specifications. As far as I know "zip version standard 1 deflate" (aka "superfast" aka "Legacy compression") is used, but it does not always work depending on the implementation of parameters for the wide variety of zippers and zip-compatibles. A non-compressed archive always works and will be only 20-30% bigger as all apks and jars are already zip files and only the libraries will be compressed.
You can only flash a complete AllAppUpdate.bin. You can no longer flash a few apks.My Questions are:
1. Did my altered AppAllUpdate.bin must have contained other specific files other than config.txt and fyt.prop?
2. I only copied the newer version of APKs inside my original AllAppUpdate.bin, never touched other .txt files inside the folder App, but I also replaced ProtocolUpdate.apk and RKUpdate.apk, shouldn't I?
3. And I replaced SystemUI.apk and Setting.apk inside priv_app folder, shouldn't I?
4. Did I have to extract AllAppUpdate.bin and repack manually using the same default password?
Finally did it!
You could add a nokill syu.ms.apk to your allallpupdate.bin and flash your unit again, losing all settings, etcetera.I am very annoyed with my FYT device (Kingbeats K2 Plus). In sleep mode, all background apps are killed. But I need the Autostart option for such apps. The FYTStarter app does not help at all, as it is also killed. Furthermore, after each sleep mode, the Macrodroid app is deprived of various rights, e.g. the accessibility features. The Google app is automatically disabled again every time, etc.
Can someone please help me here? Can I also flash a firmware from another manufacturer on my device? Would root help?
Attached is my hwgetinfo as zip.
I have no User" -> "Application Settings". And the FYT Starter App is also killed.
Nobody an idea why the settings looks so strange?So I have successfully flashed on my Kingbeats K2 Plus with the instructions on page 1 the latest firmware from Joying and immediately set a few changes in the config.txt (previously created a backup of course).
Now everything works as it should, very stable and now also it displayed more options.
There is only one thing that is still a bit annoying: In the settings you can't see the options slider and keyboard anymore. They seem to be black on black background. I could set everything for me, but it was into blind typing. Someone an idea what this could be?
If I'm not mistaken, that's Mekede. You can find the latest software on the official site: http://www.mekede.com/Software Download Address1/
Thanks for the reply. However, MCU firmware is not the same thing. It is explained on the first page of this thread by @surfer63. Mekede doesn't provide latest MCU firmwares on their page. I have some issues with CAN protocol and I try to solve this by trying things such as updating MCU.If I'm not mistaken, that's Mekede. You can find the latest software on the official site: http://www.mekede.com/Software Download Address1/
Make sure to select your correct model, and do a backup before you start. For the backup and the update, the USB drive (I used a card reader with a 16GB card) is formatted to FAT32..
I have a M300S model, and just upgraded to the latest firmware on the site yesterday.
Can you specify, what kind of brand is your device ? What manufacturer ???I have a unit in the car as shown in the photos. Can I use the file (https://dumps.tadiphone.dev/dumps/s...v-user-10-QP1A.190711.020-09411-release-keys/) to upgrade?Since I don't know English can I download another file to upgrade or root?
Sorry about the annoyance, but I don't know where to address.
It's that, and I want to upgrade (https://www.korbos.gr/product/bizza...l-ac-car-pad-9-android-10-multimedia-station/) Sorry again for the annoyanceCan you specify, what kind of brand is your device ? What manufacturer ???
And what is your intention, what will you do ?
Without english knowledge, you will soon be stuck in a trap for this ....
And always first try to get the original updates from the manufacturers homepage .
This is the worst fake I have seen so far. Unbelievable. They really only update the property.Yeah, very suspicious. But the most worrying fact is, that companies like Joying scam their customers.
They simple push up the version number of Android, cheating and tricking - really unbelievable.
These are not only tricks, this is nearly or really CRIMINAL . I bet, they soon sell units with "Android 12" , containing Android 10 with pimp-ups of the Android version.
In this case, we should have a look at those practices .....
twipe_all # Wipe entire system twipe_data # Will wipe data partition (but not /sdcard, internal memory). Wiping the /data partition will wipe all config, all 3rd party apps and updates of system apps. This is the same as a "reset to factory defaults" twipe_sd # Will wipe internal memory /sdcard (but not the data partition) dellapp # Remove all 3rd party apps make_updates # Make an upgrade U-disk boot file test # test unit and firmware before flash
ro.product.locale = pt_BR ro.sf.swrotation = 90
persist.sys.zlink.mic.vol=9.9 persist.audio.mic.senstivity=1 persist.btmic.gain=10 persist.btspk.gain=7
com.zoulou.dab = -10 net.dinglisch.android.taskerm = -10
brotli -vd system.new.dat.br -o system.new.dat
sdat2img.py system.transfer.list system.new.dat system.img
mkdir system sudo mount -o loop system.img system ls -Rl system
sudo mount -o loop system.img system sudo mksquashfs system system.img.sqsh sudo umount system
sudo mount -o loop system.img.sqsh system
Apart from the /oem partition and a few others, the /system, /vendor and /product partition are read-only. In earlier FYTs, you could use the lsec script to make them read-write and then modifiy content, add/remove files/apks, etcetera from these partitions. The big disadvantage for modders with these new dynamic partitions is that you can't make them read-write anymore.Dynamic partitions are a userspace partitioning system for Android. Using this partitioning system, you can create, resize, or destroy partitions during over-the-air (OTA) updates. With dynamic partitions, vendors no longer have to worry about the individual sizes of partitions such as system, vendor, and product. Instead, the device allocates a super partition, and sub-partitions can be sized dynamically within it. Individual partition images no longer have to leave empty space for future OTAs. Instead, the remaining free space in super is available for all dynamic partitions.
lsec6315update lsec_update/7862lsec.sh "stuff that needs to be copied/moved/installed"