Related
Hi guys i have a problem creating the bootmenu
I am following this post but when i'm going to 3rd line:
C:/> adb shell
$ su
# cp -R /sdcard/bootmenu /data/bootmenu
# cd /data/bootmenu
# chmod 755 *
# ./install.sh
# rm -R /data/bootmenu
i get the following message: cd: can't cd to /data/bootmenu
could you tell me please what i'm doing wrong???
Post the output of
# ls -l /data/bootmenu
Maybe it does not exist OR it is a file (it will be a file if /sdcard/bootmenu was one)
But in any case: It's much easier to install 2nd-init directly from the android market: The currently included version 0.45 works good enough to install the CM7 port (afterwards you'll have 0.51 anyway as the port includes it's own version)
pabx said:
Post the output of
# ls -l /data/bootmenu
Maybe it does not exist OR it is a file (it will be a file if /sdcard/bootmenu was one)
But in any case: It's much easier to install 2nd-init directly from the android market: The currently included version 0.45 works good enough to install the CM7 port (afterwards you'll have 0.51 anyway as the port includes it's own version)
Click to expand...
Click to collapse
Ok thanks! I saw today new version of this that include 0.5.1
BigRushDog aka brd found this ninja method for us. thank him when you see him!
run a radio logcat with adb logcat -b radio > radio.txt
then grep or search for
Code:
E/RIL[V] ( 118): OEM_HIDDEN_GET_MSL
about 4 lines below this entry you'll see a 12digit string
the first 6 being your MSL
To reiterate:
"adb logcat -b radio | grep sendData" and then perform *#*#DATA#*#* , my terminal put out E/RIL[V] *( *119): sendData : 1234561802130
Where 123456 would be your MSL
we may have a bash script coming for you guys soon.
4/27-BASH Script added for Linux users wishing to find MSL via ADB. (unzip file & run on linux machine)
Code:
unzip MSL_Find.sh.zip
chmod +x MSL_Find.sh
./MSL_Find.sh
*profit*
I gotta give a quick thanks to Myn for hinting at checking radio log in #gn-sprint. thanks bro, good looking out.
Great work guys! I didn't see anyone create a script yet, so I made one. Info can be found here...
http://forum.xda-developers.com/showthread.php?p=25371025
bash script added to OP for Linux users who wish to grab MSL using their PC. Credit to smwebster & brd for the idea.
Overview
The following steps will help you to setup a complete build environment for the webos-ports project.
WE DO NOT CURRENTLY SUPPORT webos-image PLEASE BUILD webos-dev-image
Setup the build environment
Code:
$ sudo apt-get install gawk
$ sudo apt-get install diffstat
$ sudo apt-get install chrpath
$ sudo apt-get install texinfo (if not on Ubuntu or Debian it will be makinfo instead of texinfo)
$ cd into-your-build-directory
$ mkdir webos-ports && cd webos-ports
$ wget https://raw.github.com/openwebos/build-webos/master/scripts/prerequisites.sh
$ sudo sh prerequisites.sh
$ wget https://raw.github.com/webOS-ports/webos-ports-setup/master/Makefile
$ make setup-webos-ports
Before you can build, you will need some tools. If you try to build without them, bitbake will fail a sanity check and tell you about what's missing, but not really how to get the missing pieces.
This has been tested on Gentoo (shr-chroot) and Ubuntu-12.04 amd64 and should work almost everywhere where valid toolchain is provided.
You need a lot of RAM to link webkit-webos, make sure you have at least 6GB (it's OK when some of that is swap, because it's used only for short part of build).
Webkit needs so much ram to link because it's linking with debug symbols (huge files) which are stripped later in do_package after creating -dbg packages.
You can add extra 2GB of swap file like this:
Code:
$ dd if=/dev/zero of=swap_2gb.img bs=1024k count=2048
$ mkswap swap_2gb.img
$ sudo swapon swap_2gb.img
If you want it permanently add it to your /etc/fstab.
Building
To configure to build for tuna (notice '.' which is actually bash 'source' command):
Code:
$ cd into-your-build-directory/webos-ports/webos-ports
$ . ./setup-env
To update metadata
Code:
$ make update
# or if it shows warning about different bblayers.conf or layers.txt
$ make update-conffiles && make update
# you can also add UPDATE_CONFFILES_ENABLED = 1 to config.mk
# if you never want to have any uncommited changes in your checkouts RESET_ENABLED = 1 in config.mk
To build the webos-image for the gnex device:
Code:
$ MACHINE=tuna bb webos-ports-image
# or for the webos development image
$ MACHINE=tuna bb webos-ports-dev-image
If you get an error about missing qmake-palm, try this:
Code:
$ MACHINE=tuna bitbake -c cleansstate -f qt4-webos
If you get an error about missing QtWebKit #261, try this:
Code:
$ MACHINE=tuna bitbake -c cleansstate -f webkit-webos
If you get an error "The BBPATH variable is not set", then you forgot to call:
Code:
$ . setup-env
After the build completes, you will find your image in <build env>/tmp-eglibc/deploy/images/tuna/
==Speeding up the build==
You can tune bitbake to use more of your processor. Edit webos-ports/conf/local.conf and uncomment the PARALLEL_MAKE and BB_NUMBER_THREADS lines. PARALLEL_MAKE should be set to the number of processor cores you have (or the number you have made available to the VM in the case of a VM) and BB_NUMBER_THREADS can be set from one to two times that, depending upon RAM, processor speed, other tasks running and Hyper-threading support. Example values:
Code:
PARALLEL_MAKE = "-j 4"
BB_NUMBER_THREADS = "4"
I'm not in charge of this port. This thread is just here to help you, and discuss about this port made by team WEBOS-PORT.
Thanks for their work.
Installing and running the image
Once you have built the image, you'll likely want to install it and run it on your Nexus. See Testing Gnex for further details on that process.
Source and updates : http://webos-ports.org/wiki/Galaxy_Nexus_Build_Setup
Videos
Pictures
More Pictures : http://webos-ports.org/wiki/Galaxy_Nexus
Thanks for this, just having a go at this now
Edit: Damn it seems it doesn't like Ubuntu 10.10
Suppose I needed an excuse to update........
It would be pretty cool to have web os as a port for the Nexus. Wish you all the best
Sent from my Galaxy Nexus using Tapatalk 2
Nice, I hope webOS will be a succes on our Galaxy Nexuses!
Good luck!
nice work there ...
Really excited about this. Can't wait for a relatively stable port of the WebOS
So awesome, can't wait to see how this progresses.
Sent from my Galaxy Nexus using Tapatalk 2
The source was specified for Gnex, wasn't it?
Sent from my Galaxy Nexus using xda app-developers app
woot woot. niceeeee
Sound good....
Sent from my Galaxy Nexus using xda app-developers app
Awesome dude! Can't wait for a release. Hopefully in the future we can get this to dual boot with android, that would be awesome!
possibly to get instructions for toro?
waiting this on my gnex
New video added to post #2
exciiting stuff
Ok, this may be very embarrassing. I was able to follow the process to build the image but I cannot find the image nor how-to flash it on my Nexus. Any help like links, keywords to search for is very appreciated.
#1 updated with Latest revision as of 23:58, 10 October 2012
sounds interesting.. cant wait for build that i can flash
Bread Pitta said:
Ok, this may be very embarrassing. I was able to follow the process to build the image but I cannot find the image nor how-to flash it on my Nexus. Any help like links, keywords to search for is very appreciated.
Click to expand...
Click to collapse
Same here. Finally got it to build without errors, but no clue what to do next. My best Google sleuthing couldn't find any hints either
Last week I got my GWA2 from Germany and I'm very disappointed. Samsung Pay is still not available and changing region with SDBstarterKidv1 does not work. SDB and CSC.Manager execute without error messages on the PC but the region selection is not displayed on the watch's screen. Did Samsung block the possibility to change a region?
Why buy a watch where the advertised features are not available maybe in the future? ECG - 2020?, Fall Detection sometime, Blood Pressure - the App My BP Lab 2.0 is easy to install but does not work with the hardware, calibration stops after 10%..
Maybe Galaxy Watch Active 3 or 4 comes close to Apple watch!
Can you give maybe more details...
Model Name... Firmware Version...
What exact not work with SDB?
As you know... nobody have Crystal Ball...
Btw. I am better in German language...
Best Regards
Galaxy Watch Active 2
adfree said:
Can you give maybe more details...
Model Name... Firmware Version... SM-R820 Galaxy Watch Active 2(E8F5) UI-Ver. 1.5 Tizen-Vers. 4.0.0.6
What exact not work with SDB? ….M.E. funktioniert SDB einwandfrei, nur erfolgen keine Ausgaben auf dem Uhr-Display.
Nach dem sdb connect erfolgt keine 'Debugging RSA Key ...' durch die Active 2.
Die App 'csc-manager.csc-pre-configuration' wird ausgeführt, aber es erscheint kein Auswahl-Menü auf der Uhr.
As you know... nobody have Crystal Ball...
Btw. I am better in German language...
Best Regards
Click to expand...
Click to collapse
Freundliche Grüsse
eboeschen
Registered on 16.09. and already mocking samsung. Apple fanboy.
Sent from my SM-G975F using Tapatalk
adfree said:
Can you give maybe more details...
Model Name... Firmware Version...
What exact not work with SDB?
As you know... nobody have Crystal Ball...
Btw. I am better in German language...
Best Regards
Click to expand...
Click to collapse
While inviting another member (especially one with only one post), it is better to tell him the rules of XDA (which, as a senior member, you should also know).
English is the language to be used on XDA. If another language is to be used, the English version should be on top with the other language version following it.
eboeschen said:
Freundliche Grüsse
eboeschen
Click to expand...
Click to collapse
Please note the above guideline and refrain from using another language only.
In addition, do not edit the post you are quoting. Post yours below the quote. This will make reading easier instead of hunting in the quoted post.
Same story with me: successfully linked my PC with the watch, did "sdb shell", but "launch_app csc-manager.csc-pre-configuration" did nothing on the watch's side, although the shell says "... successfully launched"
The watch is Galaxy Watch Active 2, bought in Germany. The goal is to change the region to SER to activate SPay.
csc-manager app is indeed there:
sh-3.2$ ls
com.samsung.alarm-mobile-alert-solis com.samsung.samsung-pay-app com.samsung.w-reminder
com.samsung.alarm-solis com.samsung.samsung-pay-guide-app com.samsung.w-taskmanager
com.samsung.app-list-backup-service com.samsung.sdbd-syspopup com.samsung.watch-utils
com.samsung.app-version-sync-popup com.samsung.setting-location com.samsung.watchface
com.samsung.app-widget com.samsung.shealth_gear com.samsung.weather
com.samsung.b2-setup-wizard com.samsung.sketch com.samsung.wemail
com.samsung.bluetooth com.samsung.skmsa com.samsung.wifi
com.samsung.bluetooth-testmode com.samsung.stopwatch-wc1 com.samsung.wifi-test
com.samsung.bt-syspopup com.samsung.supl-syspopup com.samsung.windicator
com.samsung.ciss com.samsung.testmode com.samsung.wis-backup-service
com.samsung.clocksetting com.samsung.timer-wc1 com.samsung.wnotification2
com.samsung.contacts-backup-service com.samsung.tizen.bixby com.samsung.worldclock
com.samsung.daily-briefing com.samsung.tizen.bixby-provisioning csc-app
com.samsung.dqagent com.samsung.tizen.bixby-voice csc-manager
com.samsung.emergency-message com.samsung.tizen.bixby-wakeup-service health-data-service
com.samsung.factory-clientw com.samsung.tizen.iva-service ise-engine
com.samsung.factory-nfchce com.samsung.tizen.samsung-account ise-languagepack-mgr
com.samsung.flash-light com.samsung.tizen.samsung-account.ui ise-multilingual
com.samsung.fmg com.samsung.tizenseckeystring net.stc-popup
com.samsung.fmm com.samsung.tts-setting net.wc-popup
com.samsung.fota-consumer com.samsung.tzdata-update-popup net.wc-syspopup
com.samsung.gearstore com.samsung.unit-test-device nfc-manager
com.samsung.iap-galaxyapps-consumer com.samsung.unit-test-input nfc-test
com.samsung.idle-clock-emergency com.samsung.unit-test-mm org.tizen.accessibility-setting
com.samsung.idle-clock-ups com.samsung.unit-test-network org.tizen.app-selector
com.samsung.idle-service com.samsung.unit-test-sensor org.tizen.crash-syspopup
com.samsung.ime-backup-service com.samsung.update-service org.tizen.dpm-syspopup
com.samsung.iot-resource-service com.samsung.voice-tos-app org.tizen.fido-syspopup
com.samsung.knox.license-viewer com.samsung.w-calendar2 org.tizen.heremaps-uc
com.samsung.knoxcustom-exitui com.samsung.w-call org.tizen.inputmethod-setting
com.samsung.knoxenrollmentservice-efl com.samsung.w-call-settings org.tizen.isf-kbd-mode-changer
com.samsung.logs-backup-service com.samsung.w-clock-viewer org.tizen.powerkey-syspopup
com.samsung.mapcontrol com.samsung.w-contacts2 org.tizen.privacy-setting-popup
com.samsung.mdec-consumer com.samsung.w-eas-it-policy org.tizen.screen-reader
com.samsung.message com.samsung.w-emergency-keypad org.tizen.stt-engine-default
com.samsung.message-backup-service com.samsung.w-gallery org.tizen.system-syspopup
com.samsung.nfc-setting-app com.samsung.w-home org.tizen.tts-engine-default
com.samsung.nfc-syspopup com.samsung.w-input-selector org.tizen.tzdata
com.samsung.pwlock com.samsung.w-lockscreen org.tizen.widget_viewer_sdk
com.samsung.runestone-core com.samsung.w-lockscreen-setting sem_daemon
com.samsung.runestone-gear com.samsung.w-logs2 smartcard-service
com.samsung.runestone-setting com.samsung.w-manager-service smartreply-service
com.samsung.safetyvolume-syspopup com.samsung.w-media-controller w-secure-element
com.samsung.samsung-account-front com.samsung.w-music-player xwalk-service
Click to expand...
Click to collapse
Life1ess said:
Same story with me: successfully linked my PC with the watch, did "sdb shell", but "launch_app csc-manager.csc-pre-configuration" did nothing on the watch's side, although the shell says "... successfully launched"
The watch is Galaxy Watch Active 2, bought in Germany. The goal is to change the region to SER to activate SPay.
csc-manager app is indeed there:
Click to expand...
Click to collapse
did you succeed to solve this problem? it happens the same to me with my german active 2
I will upload for SM-R820:
A
Code:
COMBINATION-FT40_R820XXU1ASI2.tar.md5
B
Code:
AP_R820XXU1ASHF_usr.tar.md5
BL_R820XXU1ASHF_usr.tar.md5
CSC_OXA_R820OXA1ASHF_usr.tar.md5
C
netOdin is here since years:
https://forum.xda-developers.com/showpost.php?p=73503787&postcount=150
UNTESTED with the new devices... OWN RISK!
Maybe the good old trick still work with Combination Firmware + CSC... and Code:
Code:
*#272*719434266344#
Need "few" minutes for upload...
Best Regards
Edit 1.
Combination Firmware for SM-R820:
https://www.file-upload.net/download-13731697/COMBINATION-FT40_R820XXU1ASI2.tar.md5.7z.html
Edit 2.
Stock Firmware for CSC...
https://www.file-upload.net/download-13731710/smR820XXU1ASHF.7z.html
Any more luck in this area???
adfree said:
I will upload for SM-R820:
A
Code:
COMBINATION-FT40_R820XXU1ASI2.tar.md5
B
Code:
AP_R820XXU1ASHF_usr.tar.md5
BL_R820XXU1ASHF_usr.tar.md5
CSC_OXA_R820OXA1ASHF_usr.tar.md5
C
netOdin is here since years:
https://forum.xda-developers.com/showpost.php?p=73503787&postcount=150
UNTESTED with the new devices... OWN RISK!
Maybe the good old trick still work with Combination Firmware + CSC... and Code:
Code:
*#272*719434266344#
Need "few" minutes for upload...
Best Regards
Click to expand...
Click to collapse
Thank for you providing the files. Is there any chance to get stock for a different CSC, preferably OXE?
Did anybody have any luck with changing CSC to get Samsung Pay on their GWA2?
adfree said:
I will upload for SM-R820:
A
Code:
COMBINATION-FT40_R820XXU1ASI2.tar.md5
B
Code:
AP_R820XXU1ASHF_usr.tar.md5
BL_R820XXU1ASHF_usr.tar.md5
CSC_OXA_R820OXA1ASHF_usr.tar.md5
C
netOdin is here since years:
https://forum.xda-developers.com/showpost.php?p=73503787&postcount=150
UNTESTED with the new devices... OWN RISK!
Maybe the good old trick still work with Combination Firmware + CSC... and Code:
Code:
*#272*719434266344#
Need "few" minutes for upload...
Best Regards
Edit 1.
Combination Firmware for SM-R820:
https://www.file-upload.net/download-13731697/COMBINATION-FT40_R820XXU1ASI2.tar.md5.7z.html
Edit 2.
Stock Firmware for CSC...
https://www.file-upload.net/download-13731710/smR820XXU1ASHF.7z.html
Click to expand...
Click to collapse
Hello, I tried it but it doesn't work. It seems like after the code insert the CSC doesn't change.
In fact after the choose and the reboot in the software information there still is the old CSC code and after the stock flash Samsung Pay does not appear.
Where did you find the firmware?
@Eziooo
Can you check please Videos from this Thread...
https://forum.xda-developers.com/showpost.php?p=75846867&postcount=469
It seems like after the code insert the CSC doesn't change.
Click to expand...
Click to collapse
After watching Videos... can you please "compare"...
Because no idea what you see... nor what you set...
Best Regards
adfree said:
@Eziooo
Can you check please Videos from this Thread...
https://forum.xda-developers.com/showpost.php?p=75846867&postcount=469
After watching Videos... can you please "compare"...
Because no idea what you see... nor what you set...
Best Regards
Click to expand...
Click to collapse
I mean, I have the DBT CSC stock in my watch, I followed the steps in the first post of this thread:
https://forum.xda-developers.com/smartwatch/gear-s3/succesfully-changed-csc-to-xar-to-t3718236
but when I insert the code *#272*719434266344# (like in the video 2 you linked) and the watch reboots, I chech the software information and there still is the "DBT" at the and of the software version, like nothing changed.
And when I flash the stock firmware at the end I don't have the Samsung Pay app..
sammysams said:
Did anybody have any luck with changing CSC to get Samsung Pay on their GWA2?
Click to expand...
Click to collapse
Nop. Same German active 2 and same problem. CSC change doesn't appears on watch screen. I'm afraid my watch is ready to go back to germany
Same problem
SynStratos said:
did you succeed to solve this problem? it happens the same to me with my german active 2
Click to expand...
Click to collapse
Same problem. German GWA2 and "succesfully launched" but nothing happens. . I fight and fight, but now I'm tired...
Thank for you providing the files. Is there any chance to get stock for a different CSC, preferably OXE?
---------- Post added at 08:36 AM ---------- Previous post was at 08:29 AM ----------
Thank for you providing the files. Is there any chance to get stock for a different CSC, preferably PHE?
https://forum.xda-developers.com/showpost.php?p=80172836&postcount=793
Code:
engineer-mode-on.sh
Maybe something like this is required... to write to CSA...
OWN RISK!
If I had such device... I would log... maybe some infos available what is blocked or disabled or what failed...
Best Regards
Is somebody able to check few things?
Example from my SM-R760...
Code:
sh-3.2$ ls
apps_rw data media share
sh-3.2$ cd ..
sh-3.2$ cd /
sh-3.2$ ls
%{TZ_USER_SHARE} boot dev home lost+found mnt proc run srv tmp var
bin [B]csa[/B] etc lib media opt root sbin sys usr
sh-3.2$ cd csa
sh-3.2$ ls
00000000.authtokcont ese nv sensor wd
TEE factory prov skpm_OTA_CSR_OCF_ECC_P256
bluetooth imei prov_data skpm_sk.dat
csc lost+found recovery skpm_supported_list
sh-3.2$ cd csc
sh-3.2$ ls
csc-active-customer.inf
sh-3.2$ [B]cat /csa/csc/csc-active-customer.inf[/B]
[B]XAR[/B]
sh-3.2$ cd ..
sh-3.2$ cd imei
sh-3.2$ ls
MSL_address.dat MSL_code.dat prodcode.dat serialno.dat
sh-3.2$ [B]cat /csa/imei/prodcode.dat[/B]
SM-R760NDAA[B]XAR[/B]
sh-3.2$
A.
Good to know if CSA is accessable without Root?
Code:
cd /csa
ls
If no... Combination Firmware with Root is usefull...
If yes...
B.
Code:
cat /csa/csc/csc-active-customer.inf
In my Example you see XAR for USA...
With open eyes you can see... Production Code also contains CSC text string...
Code:
cat /csa/imei/prodcode.dat
C.
1 method for Logging is... enter Code after your action...
Code:
*#9900#
Maybe you can see by open eyes... why this fail or is blocked...
Code:
launch_app csc-manager.csc-pre-configuration
D.
You can try this and report what happens... Watch explode... your Dog or your Cat?
Code:
launch_app csc-manager.csc-verifier
Best Regards
adfree said:
Is somebody able to check few things?
Example from my SM-R760...
Code:
sh-3.2$ ls
apps_rw data media share
sh-3.2$ cd ..
sh-3.2$ cd /
sh-3.2$ ls
%{TZ_USER_SHARE} boot dev home lost+found mnt proc run srv tmp var
bin [B]csa[/B] etc lib media opt root sbin sys usr
sh-3.2$ cd csa
sh-3.2$ ls
00000000.authtokcont ese nv sensor wd
TEE factory prov skpm_OTA_CSR_OCF_ECC_P256
bluetooth imei prov_data skpm_sk.dat
csc lost+found recovery skpm_supported_list
sh-3.2$ cd csc
sh-3.2$ ls
csc-active-customer.inf
sh-3.2$ [B]cat /csa/csc/csc-active-customer.inf[/B]
[B]XAR[/B]
sh-3.2$ cd ..
sh-3.2$ cd imei
sh-3.2$ ls
MSL_address.dat MSL_code.dat prodcode.dat serialno.dat
sh-3.2$ [B]cat /csa/imei/prodcode.dat[/B]
SM-R760NDAA[B]XAR[/B]
sh-3.2$
A.
Good to know if CSA is accessable without Root?
Code:
cd /csa
ls
If no... Combination Firmware with Root is usefull...
If yes...
B.
Code:
cat /csa/csc/csc-active-customer.inf
In my Example you see XAR for USA...
With open eyes you can see... Production Code also contains CSC text string...
Code:
cat /csa/imei/prodcode.dat
C.
1 method for Logging is... enter Code after your action...
Code:
*#9900#
Maybe you can see by open eyes... why this fail or is blocked...
Code:
launch_app csc-manager.csc-pre-configuration
D.
You can try this and report what happens... Watch explode... your Dog or your Cat?
Code:
launch_app csc-manager.csc-verifier
Best Regards
Click to expand...
Click to collapse
I tried to follow your steps on my watch and this is the result:
sh-3.2$ ls
apps_rw data media share
sh-3.2$ cd ..
sh-3.2$ cd /
sh-3.2$ ls
afpc boot dev home lost+found mnt opt root sbin sys usr
bin csa etc lib media nuget proc run srv tmp var
sh-3.2$ cd csa
sh-3.2$ ls
00000000.authtokcont bluetooth ese imei prov recovery skpm_FACTORY_OCF_ECC_P256
TEE csc factory lost+found prov_data sensor wd
sh-3.2$ cd csc
sh-3.2$ ls
csc-active-customer.inf
sh-3.2$ cat /csa/csc/csc-active-customer.inf
DBTsh-3.2$ cd ..
sh-3.2$ cd imei
sh-3.2$ ls
prodcode.dat serialno.dat smsn.dat
sh-3.2$ cat /csa/imei/prodcode.dat
SM-R820NZKADBTsh-3.2$
Hope it may help you.
launch_app csc-manager.csc-verifier does nothing, the code *#9900# opens a secret menu..
Hello,
my Linux OS have a strange Python Version or setting, so the Build failed with:
Code:
FAILED: //art/build/apex:art-check-release-apex-gen generate art-check-release-apex-gen.dummy
Outputs: out/soong/.intermediates/art/build/apex/art-check-release-apex-gen/gen/art-check-release-apex-gen.dummy
Error: exited with code: 1
Command: rm -rf out/soong/.intermediates/art/build/apex/art-check-release-apex-gen/gen && out/soong/host/linux-x86/bin/sbox --sandbox-path out/soong/.temp --output-root out/soong/.intermediates/art/build/apex/art-check-release-apex-gen/gen -c 'out/soong/host/linux-x86/bin/art-apex-tester --debugfs out/soong/host/linux-x86/bin/debugfs --tmpdir __SBOX_OUT_DIR__ out/soong/.intermediates/art/build/apex/com.android.runtime.release/android_common_com.android.runtime.release/com.android.runtime.release.apex && touch __SBOX_OUT_FILES__' __SBOX_OUT_DIR__/art-check-release-apex-gen.dummy
Output:
.path_interposer: no python-exec wrapped executable found in /usr/lib/python-exec.
sbox command (out/soong/host/linux-x86/bin/art-apex-tester --debugfs out/soong/host/linux-x86/bin/debugfs --tmpdir out/soong/.temp/sbox333717900 out/soong/.intermediates/art/build/apex/com.android.runtime.release/android_common_com.android.runtime.release/com.android.runtime.release.apex && touch out/soong/.temp/sbox333717900/art-check-release-apex-gen.dummy) failed with err "exit status 127"
Its on the Finish-Line of the building Process. ( [ 99% 11533/11603] )
I try to use
Code:
virtualenv --version
virtualenv 20.0.18 from /usr/lib64/python3.6/site-packages/virtualenv/__init__.py
With the Python in:
prebuilts/python/linux-x86/2.7.5/bin/python2.7
Some hints for me?
Building Lineage 16, works fine, sure the build process is different.
Can i just use the Command from lineageos16, which create the zip file if all parts are finnished?
I've been having the same issue on Gentoo since LineageOS 17.1.
I have Python 2.7, 3.6, 3.7 and 3.8 installed.
If nobody has a solution and you find it, please comment with the solution, I'm sure we are not the only two people affected by this issue.
Thank you Yurienu,
easy would be to juse another live-Distro with a build Tree on a mounted file System.
However i think the error is in the tools of google, like apex or how the script use and call this function. Not sure if i like to debug this.
I think it because the path.interposer try to present a list of tools to art-check-release-apex-gen, from where the program to do its job. And a wrapper might failed and put its path there. When art-check do its job, try it and failed, because its not design to handle the error message (and so because of that bug).
For this speaks the error message:
But take a look on my error code: "Error: exited with code: 1" from the command: //art/build/apex:art-check-release-apex-gen generate art-check-release-apex-gen.dummy".
I think there is the bug. Whatever art-check-release-apex-gen do, it fail here. Then check, see the wrapper and say that there is no python.
I try to use python 2.7.18 (Gentoos Python 2.7), and it did not work.
I try to use virtuelenvwrapper*** and it failed but the error was like: "no Module with python 2.7.5, named virtuelenvwrapper". However i got this misconfigured. But it sound compelling. Because a Module for python 2.7.18, is maybe not byte compatible with python 2.7.5.
Think i try to use another distro for building this.
Bye the way, there is a Google Summer of code 2020 project, that's sound very interesting. So there is hope for a proper lineage and gentoo support in the future.
However, if i find a solution i share it here!
I stay a little bit longer with lineageos 16.0, because self build security updates are more important for me, as Android 10 is.
*** I just linked the prebuild binary an path as environment to /usr/local/bin/
Hello everyone,
I too met the same issue, the exact same content in the "out/error.log" than the first post; I am sharing the research I got around this issue, because I don't have the same conclusion.
First I tried to discard the error about ".path_interposer", and seek the error from the "sbox" software output.
I dig around "out/soong/host/linux-x86/bin/art-apex-tester", and got those information:
Code:
% file out/soong/host/linux-x86/bin/art-apex-tester
out/soong/host/linux-x86/bin/art-apex-tester: Zip archive data, made by v?[0x314], extract using at least v2.0, last modified Thu Nov
4 03:39:44 1999, uncompressed size 2619, method=store
% unzip -l out/soong/host/linux-x86/bin/art-apex-tester
Archive: out/soong/host/linux-x86/bin/art-apex-tester
Length Date Time Name
--------- ---------- ----- ----
2619 01-01-2008 00:00 __main__.py
28376 01-01-2008 00:00 art_apex_test.py
--------- -------
30995 2 files
It looks like it’s a Zip archive which can execute the Python script "__main__.py".
The "__main__.py" is a wrapper, which its goal is to call the other python file, "art_apex_test.py" with the correct parameters.
By reading its content, I noticed it searchs Python 3 executable, and calls the following command:
Code:
/usr/bin/python3 -S relative_path/to/art_apex_test.py […]
When I execute this command under a temporary directory, I have this output (still under the current directory as parent of the "out" directory):
Code:
python3 -S /tmp/art_apex_test.py --debugfs out/soong/host/linux-x86/bin/debugfs --tmpdir out/soong/.temp out/soong/.intermediates/art/build/apex/com.android.runtime.release/android_common_com.android.runtime.release/com.android.runtime.release.apex
--bitness=auto, trying to autodetect. This may be incorrect!
Detected multilib
I have the same ouput by either executing the Zip archive with the same arguments.
Unfortunately, the "tmpdir" "out/soong/.temp" remains empty.
What about "path_interposer" then? No idea, I found no match in either the two Python scripts.
And then I don't think it's related to the Python 2.7 embedded program.
Oddly enough, the full command with sbox has the same output, but not error. I start to think this error is in a build system file.
Hope to have help (a little).
Best regards,
thican said:
I too met the same issue, the exact same content in the "out/error.log" than the first post; I am sharing the research I got around this issue, because I don't have the same conclusion.
Click to expand...
Click to collapse
I've been having this issue a while also, turns out it's fixable (not that Gentoo won't override it every time you upgrade python) I linked /usr/bin/python3.7 to /usr/bin/python3 instead of /usr/bin/python-exec2c.
Now the apex tester thinger works fine, I'm guessing that inside the sandbox can't find /usr/lib/python-exec.
Hope this works for you guys as well.
SOLVED LineageOS 17.1: .path_interposer: no python-exec wrapped executable found
superfes said:
I've been having this issue a while also, turns out it's fixable (not that Gentoo won't override it every time you upgrade python) I linked /usr/bin/python3.7 to /usr/bin/python3 instead of /usr/bin/python-exec2c.
Now the apex tester thinger works fine, I'm guessing that inside the sandbox can't find /usr/lib/python-exec.
Hope this works for you guys as well.
Click to expand...
Click to collapse
OH! That's the trick, it finally works!
For an easy fix without needing to touch files hold by system, I just create a bin directory at the root of the home directory of the user, put its path inside the PATH environment variable, at its beginning (PATH="${HOME}/bin:${PATH}"), and then creating the symbolic links.
It was so easy it's so frustrating, having this issue for months, even during 16.0 branch IIRC.
Just to be sure, I create those links (I picked Python 3.8 for my example):
Code:
ln -s /usr/bin/python3.8 ~/bin/python3
ln -s python3 ~/bin/python
Now let's try this new build. Thank you very much for you help! :good:
PS: in your message, the links are backward, it's currently python3 which is linked to python-exec2c, and /usr/bin/python3.7{,m} are there own executable. I advice you to avoid editing your system files
@superfes and @thican you guys deserve three internets!
I was struggling with this error as well (not for 16.0, only for 17.1 -- Gentoo here as well). This fixed it!
So again: Thanks!
thican said:
OH! That's the trick, it finally works!
For an easy fix without needing to touch files hold by system, I just create a bin directory at the root of the home directory of the user, put its path inside the PATH environment variable, at its beginning (PATH="${HOME}/bin:${PATH}"), and then creating the symbolic links.
It was so easy it's so frustrating, having this issue for months, even during 16.0 branch IIRC.
Just to be sure, I create those links (I picked Python 3.8 for my example):
Code:
ln -s /usr/bin/python3.8 ~/bin/python3
ln -s python3 ~/bin/python
Click to expand...
Click to collapse
This is the way that worked fully for me. Thanks all! Running Gentoo latest hardened with python 3.7 as default.
Thank you superfes and thican!
I had not the time do investigate since covid19 blow up my personal workingdesk. Nice to go on with Lineage 17.1!
Tnx! Worked for me too!
With dev-lang/python-exec-2.4.6-r2
/usr/bin/python3 is a symlink to python-exec2c which cause this error.
Workaround is use vanilla python version of python-exec2c
before brunch command you can use like
Code:
[[ -d ~/bin/ ]] || mkdir ~/bin
[[ -e ~/bin/python3 ]] || ln -s /usr/lib/python-exec/python-exec2 ~/bin/python3
export PATH=~/bin:$PATH
Hence, in future shebang support of python or python3 will removed also.
762406 – [TRACKER] Packages that have failures with dev-lang/python-exec[-native-symlinks]
bugs.gentoo.org