yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] lightdown:
OK. Sorry.

The link bit.do/logat is not working but I have make an export with adb logcat > logcat.txt, so I think is the log you need.

Link: logcat

Also I have tryed to make the lockscreen settings change with adb with this commands:

g4:/ $ locksettings clear

Lock credential cleared

g4:/ $ locksettings set-pin 1111

Error while executing command: set-pin

java.lang.IllegalStateException: Fail to enroll user password when creating SP for user 0

at com.android.server.locksettings.SyntheticPasswordManager.createPasswordBasedSyntheticPassword(SyntheticPasswordManager.java:779)

at com.android.server.locksettings.LockSettingsService.initializeSyntheticPasswordLocked(LockSettingsService.java:2688)

at com.android.server.locksettings.LockSettingsService.setLockCredentialInternal(LockSettingsService.java:1741)

at com.android.server.locksettings.LockSettingsService.setLockCredential(LockSettingsService.java:1663)

at com.android.internal.widget.LockPatternUtils.setLockCredential(LockPatternUtils.java:660)

at com.android.server.locksettings.LockSettingsShellCommand.runSetPin(LockSettingsShellCommand.java:258)

at com.android.server.locksettings.LockSettingsShellCommand.onCommand(LockSettingsShellCommand.java:101)

at android.os.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:98)

at android.os.ShellCommand.exec(ShellCommand.java:44)

at com.android.server.locksettings.LockSettingsService.onShellCommand(LockSettingsService.java:2426)

at android.os.Binder.shellCommand(Binder.java:929)

at android.os.Binder.onTransact(Binder.java:813)

at com.android.internal.widget.ILockSettings$Stub.onTransact(ILockSettings.java:1031)

at android.os.Binder.execTransactInternal(Binder.java:1154)

at android.os.Binder.execTransact(Binder.java:1123)

But Doesn't work.

Thanks
[G4 Android Development] steadfasterX:
unfortunately no that's not enough.

I have updated the FAQ with the corrected link. pls follow that briefly and also do not forget to use a paste service (that google drive thing you've used is fine too) as noted.
[G4 Android Development] lightdown:
Great! Thanks for your answer.

Mi log is here:

logcat

Mi model is H810, unlocked with USU.

Thanks!
[G4 Android Development] steadfasterX:
well I see ongoing (camera) crashes not related to your issue..

that reminds me that this LOS version is deprecated and not very well implemented and tested. I might still make a new build one day but no further development will happen here.

Atm I would recommend either my /e/ OS pie build or one of @aoleary 's builds if you really need more recent Android versions. I plan to release AXP.OS based on (likely) A12 in the near future though but for the moment it seems LOS 18.1 is not a good choice - at least not for you.

Only one thing might be left: the boot logs. so pls follow FAQ 7 to provide them. maybe that shed some light on it. btw: do you ever had flashed the UsU baseband package? If so you have to flash your original modem partition back.

EDIT:

and last but not least: the main error here is:

> E QSEECOMAPI: : Error::send command ioctl failed. ret = -1, errno = 22

This is usually an indicator that the keystorage is not in a clean state. to fix that (if this is the reason, there is no guarantee) a factory reset WITHIN my(!) latest TWRP version is required. If you swipe to factory reset there internally the related partition gets wiped too. this does not happen if you just format data or chosen factory reset from within android or any other recovery.

so the process would be:

1. format data in TWRP

2. from TWRP reboot to recovery!

3. factory reset in TWRP

4. boot android

5. setup the device without a pin first, then reboot, then set a screen lock protection

EDIT2:

when providing logs, ensure you choose the longest time frame possible. just a few days is way too short. several months are a minimum here..
[G4 Android Development] aoleary:
@lightdown I have just released crDroid for A11 with a load of tweaks I backported from my work on A12/A13, and the 4 or 5 testers that have tested it say its really fast, like faser than current A9 builds.

crDroid is a customisation based ROM, that is based on LOS, with the security patches up to date (I havent built September Patch build yet). I'd recommend you give that a try.

If you would like to try, just ping me, as I dont have an h810 build available, but it is not a problem for me to build if you want to try it..
[G4 Android Development] lightdown:
Really thanks for your time!

I have done this with twrp 3.7.0. Is that the right version or I need another?

I'll try the steps you say in that order.

Thanks!
[G4 Android Development] lightdown:
@aoleary Thanks for your response. I'd like to try your rom if it were possible ;-)
[G4 Android Development] aoleary:
I will ping you here once I have uploaded it
[G4 Android Development] aoleary:
H810 build will be uploaded in about 10 minutes. Check the thread related to crDroid 11 (v7. 34)
[G4 Android Development] jcornell:
Hi, I'm choosing a ROM for my H812 (UsU) and auto-rotate isn't working for me on SteadfasterX's latest LOS 18.1 build (20230321). Not a dealbreaker but kind of annoying. @aoleary maybe crDroid Android 11 is for me?

I don't care much about cutting edge Android though, so if there's a rock solid build of an older version I'm open to that too.
[G4 Android Development] steadfasterX:
rock stable is pie. The eOS build integrates the latest android security patches so its still a good choice imho.
[G4 Android Development] jcornell:
@steadfasterX Thanks for getting back to me on this. eOS looks good to me so I want to switch to it. In Requirements bullet point 2 you say:

I've seen you refer to seemingly the same thing as "device firmware" in a different post and I'm not sure what it is or how to query my device's current version. If it's determined by the installed ROM I certainly don't have a Marshmallow version since I'm running Android 11. Do I need to check this (and if so how can I), or can this be ensured by just flashing a package?
[G4 Android Development] steadfasterX:
the bootloader stack is a set of important files containing also the device firmware and is provided by the phone vendor. This is not part of your running OS though. so you can run A14 while the bootloader stack is on A9. You cannot easily check which bootloader stack is installed but that is not a big deal as you simply flash the latest recommended one for your model and you are safe. the thread lists TWRP flashable files for that purpose. also this thread here is the wrong one to discuss eOS based stuff so pls use the corresponding thread, thx ;)

PS: and for sure your bootloader stack is not an Android 11 one, as LG never released A11 for this device. the latest one was Nougat and that one is BETA and while you can find those files on XDA they have NEVER been released in public.
[G4 Android Development] wraqs:
I unlocked my H815 (ARB 0 according to SALT) and after flashing LOS device does not detect any sim card.

I used mentioned files:

twrp-3.6.2_9-0-g4

lineage-18.1-20230321-UNOFFICIAL-h815_usu

Magisk-v25.2

open_gapps-arm64-11.0-nano-20220215

I supposed "usu" ROM do not need baseband flash. Was I wrong or just my device is unusual in some way?

Thanks for all your work!
[G4 Android Development] steadfasterX:
first of all: do not use the official TWRP. it is very old and contains outdated stuff if you are using a recent OS like this one. the official one is meant for PIE only. Use the latest PREVIEW build instead (see TWRP support thread).

there is no need to flash the baseband package anymore when you use the above mentioned UsU zip thats right. The only thing is that if you had ever flashed the baseband package before you have to re-flash your modem partition to avoid situations like that. also you have to know that SIM detection can take 1-5 min after a (re)boot.
[G4 Android Development] st.patryk:
Hello

Is there possibility to use physical mac address instead of random generated? There is no "privacy" button on WiFi settings. I Have two LG G4 and both have the same generated MAC address, and they can't connect to one AP.
[Samsung Galaxy S22 Ultra] gav83collins:
View attachment 5611779
[Samsung Galaxy S22 Ultra] gav83collins:
View attachment 5611787
[Samsung Galaxy S22 Ultra] Nmc_alves®:
Not new... its on OTA from the 9

https://xdaforums.com/t/2avdb-1st-m...-general-discussion-firmware-updates.4405747/
[Samsung Galaxy S22 Ultra] gav83collins:
yeah i noticed that after i installed it, but i had au turned on and it only showed today so i assumed it was new
[FYT Android Head Units] mariodantas:
# FYT-Firmware-Workbench

PLEASE DO NOT USE WITH T'EYES CC3 FIRMWARE

Scripts intended to mount the FYT UIS7862 firmware, make modifications and reassemble it back

They can retrieve the firmware from specified location and after modification, they can put the packed and signed firmware into another specified location

Files:

1-) config.ini = A file to setup parameters, paths for the original firmware and patched firmware, temp directory to work with firmware files and mount point to edit the firmware

2-) import_original.sh = Retrieves the ZIP file from the location specified in config.ini

3-) import_patched.sh = Retrieves the same files that 'import_original.sh' but from the patched location specified in the config.ini (normally a firmware that you've already patched before)

4-) unpack.sh = (autorun after import*) Unpack the imported firmware and create the mount moints (as specified in the config.ini file) to work with the firmware

5-) tweaker.sh = Allows change Locale, Language, Country and allows enabling ADB and OTG (if hardware supports it)

6-) inject_mods = Copies all contents of "_mods" folder into system partition, like gps.conf or even bootanimation, up to you to creat the same folder structure with your own files to inject

7-) repack.sh = Unmount the modified firmware from the mount points, delete the mount points, assembly the new ZIP file, sign it and move it to the patched directory as specified in config.ini

:cool: clean_local.sh = This script will unmount the firmware and delete it, it will also delete temporary files. as its name says, it cleans the local workbench !

N'joy it !

[CHANGELOG]

2.0 Introduces a different ZIP signature method

1.0 Initial release
[FYT Android Head Units] surfer63:
Did you already try to flash it? I seed that you sign with the test keys but does that now work on the 7862?

On the previous architectures the recovery did not allow self signed zips.
[FYT Android Head Units] mariodantas:
Yes it works well, of course I flashed a modified 6315_1 befor make this post. You can trust the scripts, take a look at the tweaker.sh who allow you to modify some settings, Locale,Region, Coutry, and more to come !
[FYT Android Head Units] surfer63:
Hi,

I tried your tools. Nice work.

I first did the "import_original.sh" and then the "unpack.sh". I did use this on a RPi4 running Debian Linux. All my Linux machines are currently RPi boxes and I use my headless server RPi4 for most stuff I do myself on images. (Next to that I have a Chromebook running Linux as well, but that one doesn't allow me to mount images in the linux sandbox.)

In the unpack.sh I get errors after brotli on the resizing of all the images:

**********************************************

Processing 'system' image ...

BROTLI -- Handling system.new.dat.br...
Converting system.new.dat file into system.img file

When tring the "Converting .." is where it goes wrong without error message. The sdat2img is using "#!/usr/bin/env python" which, on an python3 only system gives "/usr/bin/env: ‘python’: No such file or directory"

When I change the call to "python3 sdat2img.py <etcetera>" it works. It might be better to use something like

if [ `which python` ]; then
./tools/sdat2img.py
elif [ `which python3`]; then
python3 ./tools/sdat2img.py
else
printf "\n\nNo python found!!\n\n"
exit 1
fi

Otherwise your created dat file is 0 bytes (simply an echo of 0 bytes to a new file), then giving corrupt empty images of 128 MB when trying to resize them.

And about the resizing/shrinking of the images: Why do you do that?

Simply leave the img as is and mount it read-write, not read-only.

Please use

mount -t ext4 -o loop,rw $unzippedPath$i.img $MOUNTPOINT/$i

and then simply copy (as root) your stuff in or make the modifications directly (as root). After unmounting you can immediately repack and brotli-compress it again. No extra intermediate steps necessary.

****

And some other remarks (actually a bit of nit-picking, please don't feel offended. I think you did a great job):

You use and pack a 64bit jdk with it, which is of course very convenient in most cases but doesn't work on my ARM raspberry pi.

I would put something in the shell script like

echo "Singning '${FIRMWAREZIPFILENAME}' file..."
if [ -n `which java` ]; then
# Not found. Use packed version and hope it is a 64bit system
tools/jdk64/bin/java -jar tools/SignApkv2.jar <etcetera>
else
# Use system version
java -jar <etcetera>
fi

You also use

echo " "
echo "READY !!!."
echo " "

Why not use

printf "\n\nREADY !!!\n\n"
[FYT Android Head Units] mariodantas:
Don't feel offended at all fellow, that's normal you're improving the scripts so suit your needs, that's normal, and your code (above) seems much more adapted than mine, I packed a 64bit java 8 cause java 11 does not sign the ZIP, (or at least I didn't reach the sign correctly)

Y have a giltab at home with that projects (FYT, TS10 etc....) y you want to participate and pull-request your changes, os help me improving that scripts, you're welcome and I'll send you the link via PM
[FYT Android Head Units] surfer63:
Yes, you are right. the signapkv2 is already very old. I forgot that. I just tested and java V11 comes without the sun packages.
[FYT Android Head Units] mariodantas:
Will add and arm64 java 8 and detect the proc architecture by scripts to select the right java
[FYT Android Head Units] mariodantas:
@surfer63 I forgot to tell you that I released FYT Firmware Workbench 2.0 which includes another 6315_1 signature method (no more signapkV2), (as required with lsec6315update after Jul/2/22) thos signs well the new 6315_1 files, so we can still modify their contents and repack again and flash without the message: "Please use legal system"
[FYT Android Head Units] j-5:
I finally got my images to mount. (had to sudo)

I used the modifications @surfer63 suggested. (python3 was the trick here)

edit: are the mountpoints supposed to be RO? I'm getting "no space.." error running the tweaker.
[FYT Android Head Units] mariodantas:
No, they shoud have 128Mb + each uhntil repack

NOTE: before running FYT Firmware Workbench do a "sudo su" (you must run as ROOT) that's why it didn't work flawlessly, I'll modify the scripts to ask for sudo su if needed !
[FYT Android Head Units] surfer63:
@mariodantas : Your FYT workbench was still in the Android head units section. I had it moved to the FYT forum.
[FYT Android Head Units] j-5:
OK, got it.

I had commented out the "expand' part, my bad .
[FYT Android Head Units] Aaaron16:
Is there a github repo for the latest scripts? I'd love to try this out.
[FYT Android Head Units] mariodantas:
No Github, I'll release some fixes soon !
[FYT Android Head Units] jp08:
this is very good, thanks for your hard work!

I am also having trouble parsing the system.new.dat.br file (I only chose to edit it in config). After changing to python3, file began to be mounted and repack. But I get an error on the device in the middle of installation related to "dynamic_partitions_op_list" even though I didn't change anything
[FYT Android Head Units] Andy826:
Where are the 2.0 tools?
[FYT Android Head Units] cryptyk:
In the OP
[FYT Android Head Units] mariodantas:
@surfer63 I do that to allow me to add content inside, if not, the free size is 0Kb after mount
[FYT Android Head Units] ahmed123:
@mariodantas The CC3 Firmware Tools don't seem to work with the January firmware. The error when using them on the January firmware is:

ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open _tmp/_firmware/elable.img

Any chance of this being fixed please?
[FYT Android Head Units] mariodantas:
Not compatible with CC3 anymore
[FYT Android Head Units] ahmed123:
Ahhh that's a real shame :(. No chance of this being solved at any point?
[FYT Android Head Units] mariodantas:
can try but not this week, need the janury firmware to make tests,
[FYT Android Head Units] ahmed123:
Here is a link containing the January Firmware that I uploaded to my Google Drive. https://drive.google.com/file/d/1b2sIIJBii5Cf8T936XtPYyXziBFIEVwz/view?usp=share_link

Would be awesome if you can get it to work. Thank you.
[FYT Android Head Units] mariodantas:
Got it, will test it ASAP and come back to you with an answer !
[FYT Android Head Units] ahmed123:
Thank you so much 🙏
[FYT Android Head Units] mariodantas:
check this one please
[FYT Android Head Units] ahmed123:
Wow, awesome that was super fast. Was expecting it next week at some point. The person doing this for me is out of town til Friday so will give this a try on Friday and report back.

Out of curiosity, did you discover what’s different in this January firmware compared to the already working October firmware that was throwing them errors on your tools?

Thank you 🙏
[FYT Android Head Units] mariodantas:
No, really didn't check for diffs, only check if unpack / repack works, please advice if you flash with new firmware, if flash fails due to signature please advice and I'll update the signature procedure (Maybe Teyes has its own signature method ?)
[FYT Android Head Units] ahmed123:
Sure, I will let you know on Friday once I can get it tested :) Thank you.
[FYT Android Head Units] NoUsrNameSry:
Were you able to get it to work? I am wanting to use this workbench to install the @seb21 modded com.syu.ms firmware on the CC3 I just got so that I can remap my steering wheel buttons. Let me know how you were able to get it to work.
[FYT Android Head Units] ahmed123:
Not tried yet, will try on Friday
[FYT Android Head Units] cryptyk:
Hey @mar

Hey @mariodantas

Trying this out, but it looks like there's a java version now included in the tools which doesn't work on my system. I have a different set of system libraries.

Can you let me know what version of the jdk is required for this to run to I can install that version on my system? Specifically looking at the line in repack.sh:

tools/jdk64/bin/java -jar tools/SignApkv2.jar -w -v tools/testkey.x509.pem tools/testkey.pk8 $TMPFOLDER/${FIRMWAREZIPFILENAME}_unsigned $TMPFOLDER/$FIRMWAREZIPFILENAME

If I use your bundled version of java, I get:

./java: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./java)

If I remove the path from that line and use my own installed verison of java, I get:

Exception in thread "main" java.lang.NoClassDefFoundError: sun/misc/BASE64Encoder

Thanks!
[FYT Android Head Units] surfer63:
The downloadable version of SignApkv2.jar is for java 8.

What is the glibc version on your system and what kind of system are you running?

However, if I now download the FYT Firmware workbench there is no "tools/jdk64/bin/java" anymore. :unsure:

Depending on your version of java you can compile it yourself but you need to do a number of steps to compile it on java versions of 9 and higher.

The java8 version uses the sun.security modules and these should not be used anymore.

Actually it is terribly complicated. I compiled it once for java 11 but I lost both my notes and the jar.

Of course you can also install one of the Android SDKs and use apksigner from the Android SDK.
[FYT Android Head Units] cryptyk:
This is helpful. I think I can use this to figure out the path forward.

The updated version has the jdk bundled (in this post):

https://xdaforums.com/t/fyt-firmware-workbench-2-0.4444267/page-2#post-88042053
[FYT Android Head Units] cryptyk:
Ok got this working with the January firmware by installing Java 8 on the box and pointing repack.sh to that version. @ahmed123 - sent you the firmware so you can try to install it.
[FYT Android Head Units] ahmed123:
Awesome. Thank you. I will try this in the morning and update you as it’s 11PM here in UK already
[FYT Android Head Units] surfer63:
Thank you. I now see it. I am used to finding updates in the first post, not by seaching through the other posts.

@mariodantas Can you please change the changelog description "2.0 Introduces a different ZIP signature method" in post #1 link to that post #26? :)
[FYT Android Head Units] mariodantas:
@surfer63 the post 26 uses the older sign methos that's supported by t'eyes, not the "2.0 introduces a different ZIP signature method" this last one is in my post #1, the FW-TEYES uses the old signature method., I'll clearify this in the Thread
[FYT Android Head Units] ahmed123:
I tried it and it started installing but then got error saying:

Check Update package signature error and not allow installing update, please use legal system.

:unsure:
[FYT Android Head Units] mariodantas:
In the post #1 the attached file is FFW v2.0, which includes new zip signature method that is compatible with all kernels after 2022-07-18.

The error "please use legal system" does not appear anymore but....... I see that the chinese released a new lsec6315update and haven't tried it already (the latest one capable of flashing FFW v2.0 signed ZIPs is 2072 Kb)

Maybe they've enforced the signature method again ?, I don't know !, have to try to put the answer here
[FYT Android Head Units] NoUsrNameSry:
So were you able to get either FWs to work in the T'eyes CC3?
[FYT Android Head Units] ahmed123:
Unfortunately not, another member on here helped and re-packaged the Jan firmware for me using the firmware tools but unfortunately it didn't work as it threw an error I mentioned about the signature. But haven't heard from him since so seems like a dead-end.
[FYT Android Head Units] mariodantas:
Give me your FW I'll try something !
[FYT Android Head Units] ahmed123:
Do you mean the repackaged FW? the one that's not working and giving the signature error?
[FYT Android Head Units] mariodantas:
Yes
[FYT Android Head Units] ahmed123:
Thanks, i will send it to you in about 5hrs or so when I get home as the file is on my home device.
[FYT Android Head Units] ahmed123:
Here is the link:

Teyes Repackaged FW Jan 23 - Google Drive

drive.google.com

Thank you.
[FYT Android Head Units] mariodantas:
You're welcome

This this one with another signature method and telle if it works or not !
[FYT Android Head Units] ahmed123:
Sure, will let you know. I'm trying it in the next 10/15mins.

Thanks
[FYT Android Head Units] ahmed123:
You're a star. It worked :cool: :)

It happily installed the fw. What's different in the zip file you sent me if you dont mind me asking? is there a specific signature file that you replaced?

On a side-note, I did a fresh clean wipe install. After it installed, for some reason the steering key programming app wasn't detecting any signals and none of the MCU canbus stuff was working. I also couldn't reboot it. Every time i pressed reboot and it asks if i'm sure i want to reboot, I press Sure but it didn't reboot. So eventually, I pressed the reset button with a pin to reboot it, then when it came back I still had same issue with the CANBUS stuff. So I went to the Teyes app and updated the 4 canbus apps which said there was a 10/01/23 update. Then I tried reboot option and this time it rebooted it and it started working as normal after it started up. I then tried rebooting a few times to make sure it continues to work. So far so good, everything seems to be working. Just not sure what the CANBUS glitch was.

Many thanks once again. Much appreciated.
[FYT Android Head Units] mariodantas:
No, just the method, is not a windows JAR that signs the ZIP but a linux one !

Not related with signature method, anyway I haven't any knowledge about T'eyes units !