search

checkra1n / BugTracker

checkra1n bug tracker
730 stars 104 forks source link

Android - bad system call #1314

Open The-SamminAter opened 4 years ago

The-SamminAter commented 4 years ago

Tell us about your setup:

  1. What iDevice are you using? Any supported iDevice
  2. On what version of iOS is it? Any supported iOS
  3. What version of checkra1n are you using? 0.10.1 beta
  4. What is your host system (OS version? Hackintosh? VM? etc.)? Sony Android (TV) - arm processor, android 9 (I think, it might be 8 though)
  5. How are you connecting to the device (USB-A? USB-C? Apple/3rd party cable? Through a USB hub?)? Any supported cord What are the steps to reproduce the issue?
  6. Install Termux (I installed with the apk on F-Droid)
  7. Install wget and download checkra1n 0.10.1 beta for Linux - arm (checkra1n-armel)
  8. Chmod checkra1n-armel and run it
  9. See the credits message
  10. After a couple of seconds, checkra1n will exit with the error Bad system call

What do you expect, and what is happening instead? I expect checkra1n to run, but instead, it exits after a couple of seconds, and the error Bad system call is displayed.

Does the issue also occur if you tick "Safe Mode" in the checkra1n options? N/A

Any other info, error logs, screenshots, ...? (I'll take and upload an image here as soon as I can)

nergzd723 commented 4 years ago

That probably means that you have very old Linux kernel...

The-SamminAter commented 4 years ago

the output from running uname -a Is Linux localhost 3.10.79 #1 SMP PREEMPT (the current date and time) armv7l Android

Does this give you information on the kernel @nergzd723 ?

nergzd723 commented 4 years ago

It seems like you have decent kernel, I've been running checkra1n on 3.10 kernel just fine. Can you provide kernel logs? It should give error message in /dev/kmsg if it's bad syscall. Try to update Termux packages with pkg up, this might help too.

The-SamminAter commented 4 years ago

All packages are now up to date (coreutils is now v8.32-1 instead of 8.32), and I don’t seem to have permission to access kmsg.

Is there an easy way to root a tv running Android (so that I can access /dev/kmsg? I tried towelroot, but it didn’t work.

nergzd723 commented 4 years ago

Checkra1n probably won't work if you don't have root access. But bad system call error message probably isn't related to checkra1n, it's probably Termux bug. AFAIK Sony doesn't have very strict bootloader unlocking process, so you should try unlocking the bootloader and getting root access first.

anibal642 commented 4 years ago

Thanks, at the moment I'm using linux version. But isn't not a stable method. Apreciante your help. Ty

nergzd723 commented 4 years ago

No way Towelroot will work on modern android versions. Try to unlock the bootloader using Sony instructions, Sony is usually not so strict about unlocking bootloader.

The-SamminAter commented 4 years ago

I'm afraid that I'm not very familiar with android and rooting it.

Will unlocking the bootloader effectively root it? And would there be a way to do so while possibly retaining any data/applications?

nergzd723 commented 4 years ago

I'm afraid that I'm not very familiar with android and rooting it.

Will unlocking the bootloader effectively root it? And would there be a way to do so while possibly retaining any data/applications?

Unlocking the bootloader makes you able to flash ANYTHING to your device, so you can install Magisk to gain root access.

I'm afraid but AFAIK Sony devices factory-reset themselves when bootloader-unlocked.

The-SamminAter commented 4 years ago

Ok, I rooted an arm phone running android (8.1.0), and tried to run checkra1n-armel.

I got the same message, "bad system call", so I tried running it as su, and got the error "Error opening terminal: xterm-256color."

The-SamminAter commented 4 years ago

A moment ago, when I tried to access /dev/kmsg to see what happened, the OS crashed, so I’ll see if I can copy it out first, and then open it

nergzd723 commented 4 years ago

Ok, I rooted an arm phone running android (8.1.0), and tried to run checkra1n-armel.

I got the same message, "bad system call", so I tried running it as su, and got the error "Error opening terminal: xterm-256color."

That's because the terminal is not wide enough for GUI checkra1n, so try running in CLI mode.

A moment ago, when I tried to access /dev/kmsg to see what happened, the OS crashed, so I’ll see if I can copy it out first, and then open it

You can't copy /dev/kmsg, it's a device! Try dmesg to see kmsg log, but it seems like it's termux bug and not Linux bug.

SarKaa commented 4 years ago

I think you need a linux kernel newer than 4.0 to run checkra1n

anibal642 commented 4 years ago

Thanks, and Sory to "talk" with you vary late. I'am with medical tratment. I dont have " time to stay in the forum. All my family is with cancer. My father is 84 years old, with cancer and other's patologies...See you soo. I hope. Thanks for your support.