Skip to content
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

Symbol Lookup Error #109

Closed
varad-kadam opened this issue Nov 10, 2023 · 7 comments
Closed

Symbol Lookup Error #109

varad-kadam opened this issue Nov 10, 2023 · 7 comments

Comments

@varad-kadam
Copy link

varad-kadam commented Nov 10, 2023

Hello,
I upgraded to PixelFlasher Version 5.8.2.0 and am encountering Android Platform Tools issues.

System:
EndeavourOS Linux: Kernel 6.5.9-arch1-1-g14
Platform Tools: Tested platform-tools_r34.0.5-linux and platform-tools_r33.0.3-linux
PixelFlasher: Tested on 5.8.2.0 and 5.8.1.0

Other Info:
Device: Pixel 7
Image: panther-up1a.231105.003-factory-1f4e21fc.zip

Console (for both versions):

2023-11-10 13:44:20 Selected Platform Tools Path:
/home/user/Apps/platform-tools.

2023-11-10 13:44:20 ERROR: /bin/sh: symbol lookup error: /bin/sh: undefined symbol: rl_trim_arg_from_keyseq


2023-11-10 13:44:20 ERROR: Android Platform Tools version is not available or is too old.
                           For your protection, disabling device selection.
                           Please select valid Android SDK.

SDK Version:      None
Adb SHA256:       d58bfae1297bed30780608dde3a1ffe1be4efc7c99512edef136c7c25c34eb1e
Fastboot SHA256:  08d0f9f73405854401208e01657d10683818b0ccf8ab548d4a287135bb0b3e15

Any ideas as to what might be going wrong, or any more information that might be needed?

@varad-kadam
Copy link
Author

Yup, that fixed the problem, thanks!

@varad-kadam varad-kadam changed the title Android Platform Tools Version Invalid? Symbol Lookup Error Nov 10, 2023
@fabifont
Copy link

Yup, that fixed the problem, thanks!

I'd like to request that this issue be reopened, as it stems from an outdated version of libreadline used by pixelflasher. The current version is incompatible with all versions of bash starting from 5.2 (https://bugs.freebsd.org/bugzilla//show_bug.cgi?id=266762), leading to this problem.

A temporary solution involves downgrading bash from 5.2 to 5.1, but this is not an ideal fix.

@badabing2005

@badabing2005
Copy link
Owner

I'll reopen it, but realize that you're using an Ubuntu build on non Ubuntu OS
Pixelflasher is build using Github actions using the available / supported OSes by the runners.

Ubuntu22.04 which is the latest supported on Github, only bundles libreadline 8.1.2-1 which is older than what you need and hence why it breaks with your newer OS.

Can you please try this and tell me if it works.

  • Launch PixelFlasher, don't set the platform tools yet, ignore the error it generates
  • assuming that the app is still running, open a terminal and navigate to /tmp
  • You should find a directory that starts with _MEI*
  • cd to that directory and delete libreadline* rm libreadline*
  • Then try to select Android Platform tools in PixelFlasher.
  • If it works, I'll add an option to delete the file on every startup.

@varad-kadam
Copy link
Author

* Launch PixelFlasher, don't set the platform tools yet, ignore the error it generates

* assuming that the app is still running, open a terminal and navigate to /tmp

* You should find a directory that starts with `_MEI*`

* cd to that directory and delete libreadline* `rm libreadline*`

* Then try to select Android Platform tools in PixelFlasher.

Yes, I can confirm this works on my end.

@badabing2005
Copy link
Owner

@varad-kadam Thank you for confirming.
I'll add this to the next build.

badabing2005 added a commit that referenced this issue Nov 12, 2023
- More verbose logging and additional debug messages for troubleshooting.
- Renamed the `Verbose` label to `Debug`.
- Improve UI responsiveness when running background tasks.
- Automatically detect vbmeta state for both slots, and warn if the selection would have wipe implications (this is for verity / verification disabling).
- Removed Check Verity button, (verity / verification), replaced with vbmeta state reporting for both slots as part of device details.
- Show Bootloader version as part of device details.
- Show slot related details such as slot-retry-count, slot-unbootable, slot-successful as part of device details.
- Added `Reboot to Sideload` option.
- Graphical display of device's slot and root status.
- In most cases long background processes are automatically killed with proper timeouts (when possible) and reported to unfreeze PixelFlasher.
- Reworked device detection / update / refresh, reboots, PixelFlasher now automatically detects device state changes and waits exactly the time until the device state changes to the expected state. Less dependency on arbitrary timeouts.
- Improved support logs sanitization.
- Detect free space on the computer and block flashing if less than 5G of storage is available.
- Refactor flashing function.
- More response console widget log messages.
- Detect currently installed OS version and block flashing older OTA (Android by default allows flashing but fails to boot).
- Detect, warn and block flashing if bootloader is locked for flashes that require bootloader to be unlocked.
- Added wipe option for custom flashing to easily wipe the phone when flashing vbmeta to disable verity / verification.
- Report if the device is unlockable.
- Bug fixes, lots of changes under the hood and miscellaneous improvements.
- Added option to delete specified libraries from the PixelFlasher bundle, to let the system library be loaded instead. Needed for newer OSes that require updated libraries. See #109, #111
- Additional support for Scrcpy of non-Windows platforms.
- Updated XDA links
@badabing2005
Copy link
Owner

Issue should be addressed in PixelFlasher 6.0.0.0
Before you select the Platform tools, go to settings and add any library that you want PixelFlasher to not load.
In this case it would be libreadline.so.8 you can also use wildcards like libreadline* and specify multiple libraries (comma separated).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants