-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
flashTar directory doesn't detect img #8
Comments
Maybe is because of the img.lz4 files? |
Please, help me... |
From the looks of it, my program fails to properly get the tar file entries. Not sure why it would happen - but I think it's fault of the tar lib I'm using, as I didn't have any issues. Just to make sure - are the following files at the root of the tar archive (not in a directory in the archive)? |
I don’t have the computer with me right now… but I obtained the tar files with this tool: https://github.com/SlackingVeteran/frija/releases/tag/v1.4.4
I don’t know if you can try this and tell for yourself if the tar files are ok for your program or not while I’m at work… Anyway, again thank you for the help |
while I don’t have my phone or Linux here, I have a doubt: is it ok if I flash a SM-A325F img (Galaxy A32) on a SM-A325F/DS (same but dual-sim, my actual model)? |
About this… this program is able to decompress img.lz4 for itself, but anyway I will give it a try later too… thank you |
Ok so it detects the magisk AP TAR but not the others: I'm going to try what @a7md8762 told me, and I will report... because it does not detect the lz4 files only the ones that are already .img... |
It's getting stuck on some img, I don't know why. I have, in every each attempt, reset to factory the userdata... and nothing, still same error, tried with only one tar file at a time, nothing... I'm tired now, will continue tomorrow |
In the end i successfully rooted muy device with Odín... Thabks again for your help and i hope your app will be great. ❤️ |
Nice! That's great to hear! |
I have the same issue. Basically, Thor is unable to detect, or at least present to the user, the .lz4 compressed files. So it simply displays "...". Opening the .tar AP file, extracting the .lz4 files, and then re-tarring it worked as a workaround, as suggested by @a7md8762. @TheAirBlow, do you think this issue could be fixed in a later release? |
I have no clue as to why it would happen, as I did include LZ4 support... Maybe an accidentally messed up if check? However, I do not have the time to work on Thor as I switched my interest to a different project of mine, so do not expect me to continue for a while. |
I've been working on a proper library for doing GUIs with ImGUI in C#, so who knows, maybe I'll make a GUI for Thor sometime soon xD |
Description
Whenever I try to "flashTar" a dir, it only displays three dots ... no img selection...
Reproduction
flashTar "dir"
BL_A325FXXU5DWE3_A325FXXU5DWE3_MQB65744574_REV00_user_low_ship_MULTI_CERT.tar
that contains img.lz4 files.Unable to read beyond the end of the stream.
Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'index')
Photo of the device
Full logs of the tool, in debug mode
To enable debug mode, enter
debug on
before doingconnect
for collecting as much info as possible.To get the "full logs", scroll up to the first message in Thor, select it's start, and drag to the end of the last message and copy it here:
Hardware and software
Additional context
I want to root this A32 for root access.
The text was updated successfully, but these errors were encountered: