Hello, people. I'm trying to port CM11 to our beloved D-618 (aka g2mds) but I got stuck in a point. When I try to get the proprietary-blobs it just don't work. Here's the output:
Code:
[email protected]:~/cm/device/lge/g2mds$ bash ./extract.sh //Command to run extract.sh script
cat: proprietary-blobs.txt: No such file or directory
./extract.sh: line 17: ./setup-makefiles.sh: No such file or directory
The script I'm using is this one (got it from @Zaaap72 repository) --> extract.sh
You guys know how to fix this?
Hope you guys can help me. Couldn't find any solution in Google and that really, REALLY surprised me. Thanks.
Related
any one had this command from adb before????
/sbin/sh: exec: line 1: logcat: not found
I am facing the same to logcat from Recovery. Anyone can help?
most probably the system partition is not mounted, logcat doesn't included in the path or even doesn't exist
Wrong place
Sent from MARVEL
Probably you have not set the Android SDK directory in your PATH. Are you using Linux?
R u porting roms and the log came for porting?
yup, I got this same error ... Any suggestions to fix this??
Im in my first porting of a custom rom. And I'm stuck in a boot loop. Need to take a logcat now, but stuck with this error now.
Im on windows 8.1, have android sdk installed
Ive seen that the Backtrack 5 can be installed on xperia x10..
here's the link
Does it work on LGP500 too?
It would be great if this would work on our phone to give some special features..
up please answer my question.
rexon2011 said:
up please answer my question.
Click to expand...
Click to collapse
Hmmm? Well, go and try it?
I tried... at first i thought it should work. As the file system and all are similar
It worked till the 'startbt' but when i entered 'bt' it said segmentation fault
So anyone can tell me please what i have done wrong ( I know the wrong thing is its not meant for Optimus but anything other than that?? ) or tell me how to make it work
Thank you
PS --> My First post on XDA
Ohk looks like something is missing.
do following
reboot your phone do startbt as usual...
after that us
http://forum.xda-developers.com/showpost.php?p=14006091&postcount=15
this script copy script to any location and run it.
sh debug.sh
output will be in /data/local/debug_log.txt
just copy paste the whole file here.
tips you can push the debug.sh file using adb push.
and simmilarly pull the log out using adb pull.
once you are done then post the debug log that can help in diagnostics.
anantshri said:
Ohk looks like something is missing.
do following
reboot your phone do startbt as usual...
after that us
http://forum.xda-developers.com/showpost.php?p=14006091&postcount=15
this script copy script to any location and run it.
sh debug.sh
output will be in /data/local/debug_log.txt
just copy paste the whole file here.
tips you can push the debug.sh file using adb push.
and simmilarly pull the log out using adb pull.
once you are done then post the debug log that can help in diagnostics.
Click to expand...
Click to collapse
http://www.mediafire.com/?x4kuvorawo4reqr
is this the debug log u wer asking??
please do something... i am too much exited to try it on my optimus
BTW add me on FB i have sent u a friend request
cooltoad92 said:
http://www.mediafire.com/?x4kuvorawo4reqr
is this the debug log u wer asking??
please do something... i am too much exited to try it on my optimus
BTW add me on FB i have sent u a friend request
Click to expand...
Click to collapse
two things.
1) reboot your phone and do startbt and bt again.
post all output here.
2) also segmentation fault could be coz of the busybox chrooting failure.
i hve busybox version 1.15.3
anantshri said:
Ohk looks like something is missing.
do following
reboot your phone do startbt as usual...
after that us
http://forum.xda-developers.com/showpost.php?p=14006091&postcount=15
this script copy script to any location and run it.
sh debug.sh
output will be in /data/local/debug_log.txt
just copy paste the whole file here.
tips you can push the debug.sh file using adb push.
and simmilarly pull the log out using adb pull.
once you are done then post the debug log that can help in diagnostics.
Click to expand...
Click to collapse
When i try to run BackTrack 5 on my P500 Optimus One with Gingerbread 2.3 and root installed, i get this error:
mkdir failed for data/local/mnt, File exists
net.ipv4.ip_forward = 1
Ubuntu is configured with SSH and VNC servers that can be accessed from the IP:
eth0: No such device
Segmentation fault
Shutting down BackTrack ARM
losetup: /dev/loop7: Device or resource busy
Here mine debug.sh.txt: http://www.megaupload.com/?d=2SE35OPZ
Can anyone help me?
You really need a bigger screen size to get this working properly.
Hello all,
I recently put backtrack 5 on my atrix and was really enjoying having a pentesting suite on my mobile phone.
I used the method and image from this thread
http://forum.xda-developers.com/showthread.php?t=1074169&page=26
Everything worked perfectly for a while until...
I updated to 4.5.91 GB OTA and now it no longer works.
When attempting to start BT I get this
Code:
#startbt
losetup:applet not found
mount: applet not found
mount :no such file or directory
mount :no such file or directory
mount :no such file or directory
net.ipv4.ip_forward=1
Setting /etc/resolv.conf to Google open DNS 8.8.8.8 and 8.8.8.4
startbt cannot create /data/local/bt/etc/resolve.conf: directory non-existent
startbt cannot create /data/local/bt/etc/resolve.conf: directory non-existent
startby cannot create /data/local/bt/etc/hosts directory non-existent
It looks to me like the backtrack image is not getting mounted, thus the directories cannot be found.
Can someone please explain to me what in the world happened, and perhaps how I can go about fixing this?
I am rooted and do have busybox installed. Both are confirmed through the rootcheck app.
Also I apologize for not posting this in the thread in the thread I mentioned before, but post count prevents me from posting in dev forums.
If someone successfully solves my issue I would be glad to donate a a few bucks to the dev of their choice.
EDIT***
Nevermind It is fixed. Just in case others are having similar issues I will explain what was wrong...
After I updated to GB and re-rooted, I ran rootcheck to verify that I had root access. One thing I noticed is that my rootcheck claimed I didnt have busybox installed. So I reinstalled it. Like a dummy I installed it /system/xbin instead of /system/bin. Simply installing it to the correct place fixed things. I feel silly. Mods feel free to delete this.
okay so trying to build from source FFOS for the ZTE Open C and keep getting the same error even tried switching Ubuntu Distro to 14.04.1 from 14.10 tried google and didnt come up with much of anything on the subject short of many people experiance this issue it seems but nobody gets it resolved and if they do they dont post on how they did it
Pulling "trace_util"
cp: cannot stat ‘../../../backup-flame/system/bin/trace_util’: No such file or directory
Failed to pull trace_util. Giving up.
> Build failed! <
above is the error i get any help is appreciated
Franzferdinan51 said:
okay so trying to build from source FFOS for the ZTE Open C and keep getting the same error even tried switching Ubuntu Distro to 14.04.1 from 14.10 tried google and didnt come up with much of anything on the subject short of many people experiance this issue it seems but nobody gets it resolved and if they do they dont post on how they did it
Pulling "trace_util"
cp: cannot stat ‘../../../backup-flame/system/bin/trace_util’: No such file or directory
Failed to pull trace_util. Giving up.
> Build failed! <
above is the error i get any help is appreciated
Click to expand...
Click to collapse
Follow up to this ive did a little searching my self and included in the init.target.rc is a NFC area that seems to be the "Root" of the problem but unfortunatly thats all the information ive come across so please anyone that has information how to bypass this error or fix it , i whould be very greatful
fixxed but still issues
Franzferdinan51 said:
Follow up to this ive did a little searching my self and included in the init.target.rc is a NFC area that seems to be the "Root" of the problem but unfortunatly thats all the information ive come across so please anyone that has information how to bypass this error or fix it , i whould be very greatful
Click to expand...
Click to collapse
okay so for those of you who ever run into this issue this is how to bypass unforunatly after flashing i still run into errors on ./flash.sh fails to erase userdata but well start from the top and leave that for others since im almost positive that error is due to me not doing something correct
okay so basically its pretty simple go too the link and copy openc.xml at the link below and attached for easy access
https://bugzilla.mozilla.org/attachment.cgi?id=8429932
https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/ZTE_OPEN_C
then follow the directions listed but to keep it simple for those of you whom dont want to look to far
Clean up the B2G directory, removing the unneeded directories:
rm -rf objdir-gecko/ out/ backup-flame/
Now configure Firefox OS with the following command: (Note that the path cannot contain spaces, otherwise it won't work).
./config.sh flame /PATH/TO/openc.xml
You can then build the Gecko component and Flash it to your phone using the following:
./build.sh gecko
./flash.sh gecko
You should now upgrade Gaia as well, so the upgraded version of Gecko works with the version of Gaia on the device:
cd gaia
make reset-gaia
and thats how i fixxed it unfortunatly like i said when i got to ./flash.sh the whole build it fails at user data
but once again pretty sure thats only me if anyone has information on this let me know please
all credit from this goes to mozilla i just decided to post it in an easy location for everyone who runs into this
thank you mozilla developers
I've been using CM12.1 for couple of months, love it. Found some bugs and waited a few nightlies (few weeks per "nightly") and after that tried to make a bug report.... not accepted, because CM12.1 is not developed anymore. CM13 is not available for Z2, so I tried to build CM13 myself, following the guide found on cyanogenmod site. Sorry, as a new member, can't link that URL here... It fails... I have gone past that point to extract the proprietary "blobs" from my phone (running the mentioned CM12.1) and tried again the breakfast sirius command. I'm unable to paste results here, because being a new member... look the result from pastebin com with /mwBfxHEL behind the URL...
The reason seems obvious, missing that msm8974-common-vendor.mk file. Can't find it on my computer using "locate". Can't find it using google. Don't know how to fix this or get past this... Any help appreciated!
Nobody has build CM13 for Z2???
The issue you are describing likely results from the blob extraction for msm8974-common not operating correcty: Please execute (or re-execute) the extraction scrip in this folder of the device tree as well (should be device/sony/msm8974-common). Could you paste the output after running that script, please?
Diewi said:
The issue you are describing likely results from the blob extraction for msm8974-common not operating correcty: Please execute (or re-execute) the extraction scrip in this folder of the device tree as well (should be device/sony/msm8974-common). Could you paste the output after running that script, please?
Click to expand...
Click to collapse
OK, that advice helped. Tried 'breakfast sirius' again, it went longer, complained about something missing in shinano-common folder. Used your approach again and got past that one too. After that, 'breakfast sirius' succeeded. I tried 'brunch sirius' and it failed. Tried it again, it got longer before failing again... did "while [ $? -ne 0 ]; do !! done" to try building until it succeeds. After quite a while, I stopped it, ran brunch sirius command and copied the output to pastebin.
Take a look at pastebin.com/Qz4hq1aZ
Something about libta.so?
Flexy75 said:
OK, that advice helped. Tried 'breakfast sirius' again, it went longer, complained about something missing in shinano-common folder. Used your approach again and got past that one too. After that, 'breakfast sirius' succeeded. I tried 'brunch sirius' and it failed. Tried it again, it got longer before failing again... did "while [ $? -ne 0 ]; do !! done" to try building until it succeeds. After quite a while, I stopped it, ran brunch sirius command and copied the output to pastebin.
Take a look at pastebin.com/Qz4hq1aZ
Something about libta.so?
Click to expand...
Click to collapse
Should I extract the blobs from a Z2 with OEM firmware? I vaguely remember that TA refers to something to do with DRMs that you lose when you unlock the phone to be able to install other firmwares...
Sorry for the delay.
This is an issue with the vendor files. I think that th extrction scripts are somewhat outdated, or didn't the extraction script didn't find some files. There should be a repo on github which should provide you with the needed files. Another possibility would be to extract and mount the system image of a stock and let the script process these files (there is a cmdline switch for pointing the script to it: please have a look into this script for the according switch).
Hope this helps.
Diewi said:
Sorry for the delay.
This is an issue with the vendor files. I think that th extrction scripts are somewhat outdated, or didn't the extraction script didn't find some files. There should be a repo on github which should provide you with the needed files. Another possibility would be to extract and mount the system image of a stock and let the script process these files (there is a cmdline switch for pointing the script to it: please have a look into this script for the according switch).
Hope this helps.
Click to expand...
Click to collapse
OK, found the repo. Got all the files, got the build to succeed! Thank you very much! Just few more questions... There is not just one zip file in the directory... which one to install? How do I install the zip file the build created? Perhaps via booting to recovery and installing it from there? And how does it behave? Like a upgrade, or a clean install?