yashsingh1/xdaforums huggingface dataset:
[Moto G7 Play Themes, Apps, and Mods] chuy19312:
Here is an Magisk patched boot.img to use Magisk 26.3 on Stock QPYS30.52-22-14 firmware (needs unlocked bootloader)

After flashing, install Magisk 26.3 apk and open it, sometimes, an message will appear to configure some additional things, tap on accept, it will restart the phone and magisk will be completely installed

- Instructions

Extract Magisk v26.3 Fastboot on any folder (fastboot folder highly recommended), reboot your phone on Fastboot mode and open Flash Magisk.bat file that is included, alternatively, you can open CMD on the folder you extracted the files and put this command

fastboot flash boot magisk_patched.img

Then reboot your phone

- Extra

To make SafetyNet pass and to make banking apps work, flash Play Integrity fix and Shamiko Modules, here are links for them

Play Integrity Fix

Releases · chiteroman/PlayIntegrityFix

Fix Play Integrity (and SafetyNet) verdicts. Contribute to chiteroman/PlayIntegrityFix development by creating an account on GitHub.

github.com

Shamiko (sadly, recent version do require an beta Magisk version since the last stable Magisk version is 26000 and it does require Magisk 26302, so here is the last compatible version with this Magisk version)

Release Shamiko v0.7.3 · LSPosed/LSPosed.github.io

0.7.3 Requires Magisk 26000+ / KernelSU 10940+ Follow root profile on KernelSU

github.com

Edit: added MetroPCS variant boot.img with Magisk 26.4, so latest version of shamiko should work on it
[Moto G7 Play Themes, Apps, and Mods] ZG_DEV:
Thanks, mate 👍
[Shadow General] gamble97:
Hey everyone, I just joined. I have a tmobile shadow. Just got it a few weeks back.

Anyway I'm trying to run this java based program. It's called dsmlink and I use it to tune my car. I had this working on my dell axim x3 no problem, but can't get it to work on my phone.

I get unpexceted error has occurred.

Then under details:

not supported exception

at

microft.agl.common.misc.handleAr()

at

system.windows.forms.control.initinstane()

at

system.windows.forums.buttons()

at

dsmlinkpcocket.select.ecu..ctor()

at dsmlinkpocket.form1..ctor()

at dsmlinkpocket.form1.main()

------------

What in the world does this mean? I'm also expecting an LG VU in the mail and if I can get it to work on that phone that would be better, but for now I'll try this.

Is there any way to get this program to run or is there any program for the shadow that allows you to run windows based programs?

Thanks for the help.
[Shadow General] ashasaur:
Looks like that program only works on Pocket PC devices, not WinMo smartphones, seems to be the problem that I gather from that error dump anyways.
[Google Pixel 7 Pro] BunnyPig1:
Is there a way to configure the time for adaptive charging?

This system doesn't work at all for a person like me working nighttime. It only works between 21.00-10.00 is ridiculous. Google claim they are using "AI" to find your schedule but it's either the dumbest AI made to date, or it simply doesn't work properly.

I am willing to install a third-party application for this and I am rooted and ready, any ideas?
[Google Pixel 7 Pro] synesthete:
Just curious, but do you set a wake up alarm with the stock clock app? I know it seems to use my wakeup alarm as the target time to be charged by. I wake up in the morning, so I know that isn't your situation. Do you have any extra alarms that night be confusing it?
[Google Pixel 7 Pro] simplepinoi177:
Most other advanced users/members use Advanced Charging Controller (ACC) and with CrazyBoyFeng's ACC Settings (either using his settings or using it as a template for your own personalized) to accomplish what Adaptive Charging attempts to do....

Spoiler content hidden.

But I can also confirm what @synesthete was saying -- I always had adaptive charging on, but only when I made an alarm at 8:35AM did it consistently give me a time stating "adaptive charging to 8:35AM" or something like that....
[Google Pixel 7 Pro] synesthete:
Yeah ACC is more configurable and I have been using it in place of adaptive charging for mos of the time that I have had the device.
[Google Pixel 7 Pro] krakout:
How do those CrazyBoyFeng's settings work? I found an apk on GitHub but how does it relate to ACC itself?

[EDIT] Ohhh right it's like AccA, I thought it was a config file at first...
[Google Pixel 7 Pro] simplepinoi177:
Really??? See, I don't use ACC and have only seen other expert members reference it, so I wondered that myself and assumed as you did -- that it was a config or preference type file; that's why i used the term "template" earlier....lol😅

Thanks for illuminating & clarifying it for me!
[Google Pixel 7 Pro] NCVol:
I'll put a plug in for AccA. Works great for me.
[Google Pixel 7 Pro] BunnyPig1:
I do, but if I set an alarm at 13:30 it won't start the adaptive charging and say "charging until full". If I put the alarm to anything earlier than 10:00 it will work.

Also if I put it on the charger and the clock is later than 4:00 it will not activate adaptive charging. It just sucks for us night owls haha

I tried AccA but couldn't figure out how to set a time for it (only to limit the charge to 90% per se) but I'll try Acc and see if that's any different, thank you.

Edit: just looked at Acc and it's the same as AccA? AccA is just a version of Acc with a gui?

Then I didn't understand at all how to make it based on plugged in and adjust according to my alarm I set.
[Google Pixel 7 Pro] synesthete:
Ah okay. Well, that that does suck.

ACC is a terminal app/script packaged with a magisk module. Both AccA and CrazyBoyFeng's ACC Settings are Android apps that act as a frontend/GUI for ACC. So they control ACC and still require ACC to be installed. They aren't necessarily a direct replacement for Adaptive Charging, but accomplish some of the goals. I don't think there is any current way to specify a target time to be charged by with ACC, but it does charge your battery in a more gentle way that can help preserve it.

People often use ACC to preserve/extend the life of their battery. Keeping your charge between 20% and 80% is the recommended range. Dipping below and above tends to shorten its life. Reducing charge cycles can help too. Acc allows you to set a maximum percentage to charge to, at which point it will stop charging. You can also set a percentage at which it will begin charging again. So you could have it charge to 80, stop until it gets down to 70 and then start charging again ( or whatever percentages you choose). If you don't care about the 20-80 rule, you can have it sit between 95 and 100 or whatever.

It also allows you to set cooldown intervals, so if the device temperature gets too hot during charging it can stop charging for a minute or so. You can set cutom intervals and temperatures for this too. It can be set to charge and cool in a timed cycle.

ACC and ACCA let you use a job scheduler (DJS) to schedule/trigger different profiles. The settings I wrote about in the paragraphs above can be saved to a profile. Then you can set ACC to use different profiles at different times. In AccA they can be toggled on and off. You might be able to use this scheduler to do something sort of similar to Adaptive Charging. If you have a rough idea of how long it takes your phone to charge whne you get home, you could tell it to start charging to full at a certain time to be ready for you when you wake up.
[Google Pixel 7 Pro] BunnyPig1:
Sorry for the late reply, life got busy!

Thank you for so much for the indepth explanation, very appreciated!

It sounds like Acc is a great tool and would probably work great if it was implemented along something like Tasker, but now it feels like I'm dwelling outside my knowledge and skill.

I'm not sure I'll be able to do what adaptive charging does. It's just a very good feature in my eyes and I'm just mad at Google that we're not allowed to just set an option like "follow alarm" in settings.
[Redmi 9A Questions & Answers] ChillBR0:
Can anyone explain what (Garden), [blossom](dandelion) in rom are
[Redmi 9A Questions & Answers] ZG_DEV:
They are codenames for some xiaomi phones, you can consider them as a nickname for the phones :)
[Redmi 9A Questions & Answers] ChillBR0:
And how to know in what code currently i m plz reply🥺
[Redmi 9A Questions & Answers] ZG_DEV:
You can download cpu-z app to check your codename + other info about your phone
[General Topics] J448BLE:
After upgrading to 6.0 one UI on my Samsung Galaxy S23ultra. Doesn't respond on home up on good lock
[General Topics] V0latyle:
What device? Your question belongs in the specific Samsung device forum, not here.
[General Topics] J448BLE:
S23ultra
[FYT Android Head Units] crackotage:
I recently installed a Tesla style head unit that I got from Phoenix Automotive. Surprisingly, it does seem to actually be running Android 12. I installed and ran the HWGet_Info.apk from @surfer63 and it has some `fyt` properties. I will attach the full zipped output, but here are some highlights:

[ro.system.build.version.sdk]: [31]
[ro.system_ext.build.id]: [SP1A.210812.016]
[ro.system_ext.build.fingerprint]: [UNISOC/uis7862a_1h10_Natv/uis7862a_1h10:12/SP1A.210812.016/33312:user/release-keys]
[sys.fyt.platform]: [6315]

With it being the 6315 platform and an FYT 7862 device, I have tried the lsec6315update technique to run a script. However, using a USB FAT32 formatted USB drive with the `lsec6315update` binary file in the root, along with an `lsec_updatesh` folder with a shell script inside, nothing happens when I plug in the flash drive. I'm specifically trying to run the `getinfo` script to gather even more data. My USB device gets mounted at `/storage/USB1` so I have modified the script to account for that, but really, the problem seems to be that for whatever reason, it is not auto running.

Has anyone else had this problem?
[FYT Android Head Units] surfer63:
You have indeed a genuine Android 12 unit. FYT restricts user activities more and more. They changed thae password again for the AllAppUpdate.bin and it is currently not know yet what it is.

One question though: Did you use the lsec6315update from your own firmware?
[FYT Android Head Units] gordgelin:
this is real Android 12, so nothing from android 10 is compatible, including lsec6315update, old scripts and patches
[FYT Android Head Units] laoyang88:
Unisoc T618

Linux localhost 5.4.147 #77 SMP PREEMPT Wed Aug 16 11:37:09 CST 2023 aarch64

Kernel 5.4.147
[FYT Android Head Units] crackotage:
No. I guess that explains it. I will contact the seller and try to get the lsec update binary. Thank you.
[FYT Android Head Units] crackotage:
Update:

I got a firmware update from the seller. It included the following:

6315_2.zip
AllAppUpdateA12.bin
config.txt
lsec6315updateA12

I applied the update and also tried playing around with the `lsec6315updateA12` binary. Unfortunately, it doesn't look for an `lsec_updatesh` dir with a `7862lsec.sh` file to run scripts. I've poked around in the `lsec6315updateA12` binary at the resource strings for clues. The only interesting thing I found was a reference to `lsec_updatesh/lsecsh.bin`

Anyways, I'm bummed that my unit is running Android 12 and there are no current modding options
[FYT Android Head Units] Ejpi16:
Do you mind sharing the update?

I also got a Android 12 version and seems that my hardware info almost looks the same as yours:

[ro.bootimage.build.fingerprint]: [UNISOC/uis7862a_1h10_Natv/uis7862a_1h10:12/SP1A.210812.016/27416:user/release-keys]
[ro.bootimage.build.id]: [SP1A.210812.016]
[ro.bootimage.build.version.release]: [12]
[ro.bootimage.build.version.release_or_codename]: [12]
[ro.bootimage.build.version.sdk]: [31]
[ro.fyt.platform]: [6315]
[FYT Android Head Units] crackotage:
I PM'd you with a link
[FYT Android Head Units] wooko0:
Do you mind sharing the update?
[FYT Android Head Units] crackotage:
I PM'd you
[FYT Android Head Units] Ejpi16:
I received the latest Android 12 update for my device. Bought it as a Yeer unit but @surfer63 helped me to find out it's acutally a Mekede 500 unit (4gig ram + 64gig storage Android 12).

I contacted Mekede for the latest update and they were helpfull to send me the latest version.

Perhaps I found some interesting things that could help us further. It can never harm to share... :)

I received update instructions (trandlated from Chineese)(point 2 can be interesting):

When I was playing around with the AllAppUpdateA12.bin file I found out it's ZipCrypto encrypted. When searching for ZipCrypto I found a github with bkcrack that can help to find the key to decrypt the files. This is done by using a file where you know how the first line(s) start. Like a XML file starts with a:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

With this precedure I found the key and I am able to extract all files in the AllAppUpdateA12.bin file.

For now I decrypted:

* cryptofile

* customer_config.properties

* customs_appid.properties

* fyt.prop

* skipkillapp.prop

* pwctl_config.xml

* Ver

Also trying now to find the password of the AllAppUpdateA12.bin file but that can take a while.

I haven't unpacked payload.bin in the 6315_2 zip yet.
[FYT Android Head Units] surfer63:
First of all: nice work.

What do you mean with "With this procedure I found the key..."? What key and can you share it?

What do you mean with decrypted in this case? Are they now no longer encrypted because you were able to use a 12+ plain text string to decyfer them?

Do you mean that all apks and libs are extracted, but still as an encrypted apk or lib?

Edit:

I hope you succeed but these password crackers (there are more of those tools. I have several on my system), but they all go for 10 charcters or up to 16-18 characters and that already takes very long. The password inside the "old" AllAppUpdate.bin for the Android 10 versions is 33 characters.

You need a supercomputer to crack that.
[FYT Android Head Units] Ejpi16:
@surfer63

If you read this github md you'll know what i mean.

GitHub - kimci86/bkcrack: Crack legacy zip encryption with Biham and Kocher's known plaintext attack.

Crack legacy zip encryption with Biham and Kocher's known plaintext attack. - kimci86/bkcrack

github.com

So basicly I have the data inside the AllAppUpdateA12.bin. To give an example this is the data inside of the fyt.prop:

Thats correct. You can change the password of the AllAppUpdateA12.bin file with the obtained key in bkcrack and then extract all the files inside it.

Jep. Now we can extract the individual files if we want to. Below a screenshot fo the files and folders in the app folder:

View attachment 6047576

While updating the headunit I saw that all the files in the AllAppUpdateA12.bin/app folder are just copied to the headunit.

Haven't found a way to inject commands. But if we have a APK that we want to install we can put it in the app folder (but first we need the password).

bkcrack uses the obtained key and an algorithm to find the password, hopefully it takes less longer then just brute forcing. I thought the old password was 32 characters long :rolleyes:. I let bkcrack find a password with 32 characters with the idea that if the old one is 32 characters, perhaps the new one is also 32 characters. It's a pure guess, but if it's 32 it saves a lot of time because bkcrack starts with a length of 4 characters and continues with 5,6,7 and so on.

For my knowledge; what does the data inside the lsec6315updateA12 file do? I can read some text and commands but also a lot of data that I'm not able to read. Is there a way to decode this unreadable text? Can we just add or remove commands in this file? So far now I haven't found a script that is called inside the AllAppUpdateA12.bin to execute things like we are used to in Android 10.
[FYT Android Head Units] surfer63:
I already knew bkcrack and somer of the other ones mentioned via my link. I tried them on the old Android 10 AllAppUpdate.bin where I actually already knew the password. After days and days on my server, I simply stopped them.

Why would you change the password? the lsec6315updateA12 will only use the original one. It would mean to change the lsec6315updateA12 as well to use the new password.

32? OK, counting is getting more difficult on my age ;)
[FYT Android Head Units] Ejpi16:
You can extract the data with a single command per file or you change the password and you extract everything at once haha.

Any clues where I can search for? I edited my previous post a few times btw.
[FYT Android Head Units] surfer63:
I understand the "extract everything". That is quite obvious. But if you change the password, you can't rebuild it with the original password. This means that you also need to modify that same password into the lsec6315updateA12. Otherwise you can't flash a modified AllAppUpdate.bin.

And you can't change the password to the new one and after rezipping the AllAppUpdate.bin, use the old password again as you don't know that one.

And as long we can't use scripts, you can't unpack it it and "flash" the apps by simply copying them all with an lsec script.
[FYT Android Head Units] Ejpi16:
Yes true. I wasn't that far jet to put everything together haha. First wanted to find out what's inside the bin file and see from there.
[FYT Android Head Units] gordgelin:
no you can not, even with password

android 12 protection is more complex then what we have with android 10
[FYT Android Head Units] gordgelin:
no you can not, this is not a script file
[FYT Android Head Units] gordgelin:
also there is no one-for-all password, now it is dynamic password, different for every AllAppUpdate file
[FYT Android Head Units] Ejpi16:
How is it done? I mean, the apk's in the app folder are from fyt. Does it need some kind of whitelist?
[FYT Android Head Units] Ejpi16:
How does the update know that it needs to copy all the apps to the device?
[FYT Android Head Units] Ejpi16:
How does it work? Hoe does the update system know the password if it changes every time?

It all seem things are impossible but are there possibilities?
[FYT Android Head Units] Ejpi16:
How does it work? Hoe does the update system know the password if it changes every time?

It all seem things are impossible but are there possibilities
[FYT Android Head Units] gordgelin:
it just extracts everything from AllAppUpdate file if it is present, but first it checks if file is valid
[FYT Android Head Units] Ejpi16:
How does it know what to extract and how? Are there any clues or possibilities or are we just screwed?
[FYT Android Head Units] gordgelin:
it just extracts WHOLE ARCHIVE, not some separate files. It does not care if there is 1 file or 1000 files inside. And no, you can not just add some apk with 7zip etc 'coz file will be invalidated and extraction will fail
[FYT Android Head Units] surfer63:
Oh. Those FYT guys are so nice to us :).

Well, if it means they deliver totally bug-free software, I don't care anymore. ;)
[FYT Android Head Units] gordgelin:
i'd not count on that ))
[FYT Android Head Units] j0hn83:
I'm not a fan of having to send PM's asking for copies of free firmware. It's much easier and better for the wider modding community to just share the uploads freely.

Even after sending a PM asking for a link to download I still had to then request permission to download the file. This requires exposing my Google email address to the uploader.

Google Drive has no bandwidth restrictions so I'm not sure why that's necessary. (Not a direct criticism of the OP who I'm sure has some reason for doing it like this, just my opinion).

So here is the update in question for anyone who needs it (or anyone just curious) to save them that trouble.

Link to Google Drive download

As mentioned already these firmwares can't be modified in any way like the Android 10 firmware can so don't flash this to your unit unless you know what you are doing.
[FYT Android Head Units] Ejpi16:
That's indeed clear by now haha :p but is there a way if it would not have a password on it? I understand it's not the same as with Android 10. Just curious thats all 😇

Thanks for sharing the update.
[FYT Android Head Units] gordgelin:
no. update should be valid
[FYT Android Head Units] wooko0:
how to flash it to my Android10 unit?

@gordgelin @Ejpi16
[FYT Android Head Units] gordgelin:
not possible to use this firmware update with android 10 unit
[FYT Android Head Units] crackotage:
Apologies for the additional hoops to get the file. Having never shared a large (2 GBs) file publicly via Google drive, I wasn't sure about bandwidth restrictions or data caps, so it was done out of caution. Anyways, thanks for the clarification and posting it publicly.
[FYT Android Head Units] hulk_bulk:
can you also please share me the updates, i also own a similar one.
[FYT Android Head Units] j0hn83:
It was share on the next page

Google Drive download link
[FYT Android Head Units] Seikilos:
Hello, the password is obtained very quickly by the utility 7870pwd_extract, on this file the password is: b94d9c92ac1b1c2d57e6de80314c8898
[FYT Android Head Units] Seikilos:
did you unpack? Otherwise you can do it using this utility, but I don’t know how true it is
[FYT Android Head Units] Ejpi16:
No haven't tried it yet. Thought you did 😋
[FYT Android Head Units] surfer63:
You are mixing and matchings answers from other topics from other users. Don't do that or specify and refer to the correct posts in this forum.

It all doesn't matter. The payload dumper works and you can unpack but you still can't modify it at all.
[FYT Android Head Units] Seikilos:
I indicated everything correctly, I just wanted to help the person in his research.

If you know more than me, can you tell me what the lsecsh.bin file contains or how can I make it for Android 12?
[FYT Android Head Units] gordgelin:
as i've already explained to you at 4pda - for now you can not. it is sh-script encrypted and signed with private key
[FYT Android Head Units] Clandaries:
Is there a way to root Android 12?

Just got a head unit with UIS7870 and Android 12 :oops:

Edit, it is Android 13.
[FYT Android Head Units] giouncino80:
Is there any possibility to upgrade a FYT unit from android 10 to this new android 12? It could be very interesting....
[FYT Android Head Units] gordgelin:
it is not interesting at all when you look at new system restrictions. downgrading to android 10 looks more interesting for now
[FYT Android Head Units] marchnz:
People love bigger numbers :)
[FYT Android Head Units] surfer63:
Size doesn't matter :)
[FYT Android Head Units] Clandaries:
Could someone please help me finding this lcdconfig?

Snd is it possible to install it on UIS7862 and UIS7870?

Thank you.
[FYT Android Head Units] gordgelin:
yes, just rename 6315lcdconfig.cfg to 6318lcdconfig.cfg. should work
[FYT Android Head Units] giouncino80:
in terms of an upgraded system, with updated security it is more interesting than android 10.

Furthermore android 10 will become deprecated earlier....
[FYT Android Head Units] gordgelin:
very funny in terms of security for this chinese device with oem software which sends all sorts of your data to its servers )))

it is top 1 android version in the world (it was when i checked last time) for now and top 2 is android 11 so it is a bit to eary to talk about being obsolete

update: ok, it started declining since mid 2023 but nevertheless
[FYT Android Head Units] surfer63:
Security patches are continously rolled out to all supported systems, also Android 10. Occasionally a new firmware for our systems is released containing kernels with new patches. So that is no point whatsoever.

When you talk about security related to filesystems, then Android 12 makes it only harder. How will you use UB-sticks on real Android 12. It has many limitations (or call it security enhancements).

And the top layer of FYT systems is as leaky as a sieve. If you talk about security, you should not buy a Chinese system. Not because of the Android base layer, but because of the inherently unsafe Chinese app layer.
[FYT Android Head Units] w90ang:
I think so too.and... you mentioned that there is a way to root uis7870. Is there any news, please?