Youlikethis9939, posted Sun Nov 04, 2018 8:49 pm (40111)

---

Plz give me 64 bit quickbms

noob, posted Mon Nov 05, 2018 3:40 am (40119)

---

aluigi wrote:

The only other thing you can try is running again that test script using the -V option of quickbms and pasting the output here.

Same output log dump 0

Youlikethis9939, posted Mon Nov 05, 2018 4:20 am (40120)

---

Any one give me 64 but quickbms

aluigi, posted Mon Nov 05, 2018 7:26 am (40123)

---

@noob
??? quickbms -V -r -r -w 1.bms 1.bms output_folder

The output of quickbms, the messages.

noob, posted Mon Nov 05, 2018 7:53 am (40124)

---

aluigi wrote:

@noob
??? quickbms -V -r -r -w 1.bms 1.bms output_folder

The output of quickbms, the messages.

No output just 0 file reimported

aluigi, posted Mon Nov 05, 2018 8:29 am (40125)

---

Now I need another screenshot with the extraction command:
quickbms -V 1.bms 1.bms output_folder

noob, posted Mon Nov 05, 2018 9:43 am (40127)

---

aluigi wrote:

Now I need another screenshot with the extraction command:
quickbms -V 1.bms 1.bms output_folder

Can i dm the screenshot i dont want to publick it all are behind this to copy and sell



Edit here is the code without that line

aluigi, posted Mon Nov 05, 2018 1:03 pm (40133)

---

*edit*

aluigi, posted Mon Nov 05, 2018 1:05 pm (40134)

---

Eh no, you didn't execute the command I told you.
Please do it again as I said without "-r -r -w"

noob, posted Mon Nov 05, 2018 1:56 pm (40135)

---

aluigi wrote:

Eh no, you didn't execute the command I told you.
Please do it again as I said without "-r -r -w"

My bad lol im using android so abit hard for me any way there is the screen shot of the command and the dumped file

noob, posted Mon Nov 05, 2018 1:58 pm (40136)

---

This is the dump file i got in output folder

aluigi, posted Mon Nov 05, 2018 3:50 pm (40142)

---

Great, I guess I found it.
If you pay attention to the screenshot with -r -r -w you can notice the "output folder": output_folder
while in extraction it's a full absolute path: /data/data/com.termux/home/output_folder
Everything else is identical.

I know how to solve the problem since it was a doubtful instruction in quickbms.c (commented with "???") that avoided the creation of the absolute path, so consider it fixed in 0.9.1
Well done

noob, posted Mon Nov 05, 2018 4:51 pm (40143)

---

aluigi wrote:

Great, I guess I found it.
If you pay attention to the screenshot with -r -r -w you can notice the "output folder": output_folder
while in extraction it's a full absolute path: /data/data/com.termux/home/output_folder
Everything else is identical.

I know how to solve the problem since it was a doubtful instruction in quickbms.c (commented with "???") that avoided the creation of the absolute path, so consider it fixed in 0.9.1
Well done

lmao we took about 30 posts for this btw if u made 0.9.1 make it compiled for linux already in termux itisnt compileable

aluigi, posted Mon Nov 05, 2018 6:10 pm (40144)

---

quickbms 0.9.1 has not been released yet.
Currently there is no release date.

aluigi, posted Mon Nov 05, 2018 11:07 pm (40146)

---

noob, you did a huge mess there.

There is NO problem in quickbms, the problem is just the first -V screenshot you provided.
It's clearly written that no output_folder existed in reimport mode (it asked to create the folder) and obviously all the output I needed was wrong... what a waste of time, luckily I noticed it in time.

This doesn't mean that the problem you experienced doesn't exist, it simply means that we are still at the starting point with debugging and I can't replicate the problem (even Linux with qemu works perfectly).

noob, posted Tue Nov 06, 2018 4:41 am (40148)

---

aluigi wrote:

noob, you did a huge mess there.

There is NO problem in quickbms, the problem is just the first -V screenshot you provided.
It's clearly written that no output_folder existed in reimport mode (it asked to create the folder) and obviously all the output I needed was wrong... what a waste of time, luckily I noticed it in time.

This doesn't mean that the problem you experienced doesn't exist, it simply means that we are still at the starting point with debugging and I can't replicate the problem (even Linux with qemu works perfectly).

Lol u know about it already just dont say everyone plis xD

Btw the reimport works correct if i dont edit the extracted file and reimport but if i edit it wont

aluigi, posted Tue Nov 06, 2018 8:04 am (40150)

---

Do you think it may be something related to the access permissions?

Your last statement clearly excludes any problem on the quickbms side, if reimporting works if you don't touch the files it means the files are found, if you edit them and quickbms tells you 0 files reimported it means the file does not exist or it exists but can't be accessed.

noob, posted Tue Nov 06, 2018 1:18 pm (40156)

---

aluigi wrote:

Do you think it may be something related to the access permissions?

Your last statement clearly excludes any problem on the quickbms side, if reimporting works if you don't touch the files it means the files are found, if you edit them and quickbms tells you 0 files reimported it means the file does not exist or it exists but can't be accessed.

Thanks ill run as full. Root btw can you remove this full post it seems to be useless post
I mean this whole topic

noob, posted Tue Nov 06, 2018 2:26 pm (40158)

---

I tried giving same perms that was given to extracted one and tried none worked maybe someother problem

aluigi, posted Tue Nov 06, 2018 4:06 pm (40159)

---

Anyway not related to quickbms so I prefer to not spending other precious time on this.

If you will find the real cause of that problem or you will solve it, you are more than welcome to share the information.

AxelZz, posted Thu Dec 27, 2018 1:21 pm (41667)

---

Hi guys ihave installed termux and download quickbms linux but idont know what is the command to run quickbms any help ihave some experts on pc Version but its broke

aluigi, posted Thu Dec 27, 2018 2:28 pm (41674)

---

@AxelZz
I have moved your post in an existent topic dedicated to quickbms and termux.
Maybe take a look at the previous posts here if you can find some answer.

Please note that the quickbms executables are compiled for x86, therefore you need to use qemu for using it on an arm cpu.

LolHacksRule, posted Tue Apr 09, 2019 4:15 pm (46709)

---

I want to run QuickBMS on my Samsung A8 (2018) Android phone if possible but Termux, UserLAnd and Terminal Emulator apps say permission denied when trying to run the compiled Linux executable. How do I properly do this step by step for an unrooted device or do I need root access to run it?

nihinivi, posted Thu Apr 25, 2019 3:06 am (47274)

---

LolHacksRule wrote:

I want to run QuickBMS on my Samsung A8 (2018) Android phone if possible but Termux, UserLAnd and Terminal Emulator apps say permission denied when trying to run the compiled Linux executable. How do I properly do this step by step for an unrooted device or do I need root access to run it?

Give root permission brudda after compiling u need to install tsu if in termux for that type pkg install tsu then tsudo./quickbms ..... If on linux distro like userland just do sudo ./quickbms. And for terminal that same just use sudo

nihinivi, posted Thu Apr 25, 2019 4:15 am (47277)

---

LolHacksRule wrote:

I want to run QuickBMS on my Samsung A8 (2018) Android phone if possible but Termux, UserLAnd and Terminal Emulator apps say permission denied when trying to run the compiled Linux executable. How do I properly do this step by step for an unrooted device or do I need root access to run it?

Btw how was u ablw to compile it did u install cryptography sucessfully