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
Related
Hello guys anD GIRLs. semi-N00B here. tehehe. I say semi because I spent the last week learning evvvverything i could about "rootin'" my Area. phew, there's a lot to learn ... but I like to be fairly sure of how things work before I attempt nething./ I just have 1one question, before I do this to my DEVice... How do I flash a rom to my phone if the Aria doesn't support flash? Is there a guide to modifying flash lite for this? I can't find it.
Thanks in advance. Luv yas.
WTF NOOOOB!! YOU POSTED IN THE WRONG SECTION!! UGH. THIS SHOULD FREAKING BE POSTED IN DEVELOPMENT...i swear..noobs..anyways on a lighter note
welcome to the wonderful world of android!! im pretty new myself but have been trying to do this too. ive been reading various wikis and have come up with this(beware i am about to attempt this this weekend myself)
1)you need to be on froyo 2.2 (att official)
2)you need to pull out flashlite.apk using the android sdk
3)you need to decompile flashlite.apk with baksmali
4)you need to delete the flash files and replace them with romflash.txt
5)recompile with smali and rename it to romflash.apk
6)push it with adb
7)FLASH ROMS AND SCORE!!!!
good luck!! and hope to see moar of u around the forums!
YAY ROM FLASHERZ
ps. does anyone know what cm7 is? can you explain it to me? the guides arent telling me enough...
ps.s to the OP-heres a wonderful guide if smali is to complicated. this tool can help you decompile flash lite and works wonders!!
miui-au. co m/ add-ons/ apktool/(cant post links yet..sorr)
I'm not sure what Megamansrighthandman is talking about, but it isn't correct.
It sounds like both of you are confused about the use of the word "flash". Be careful with the terminology. When someone talks about "flashing a ROM", that simply means installing a ROM. It has nothing to do with Adobe Flash or HTC's Flash Lite. I understand the confusion though. I hope this clears things up.
The process for setting up your phone to be able to install custom ROMs basically breaks down to these steps:
1) "Root" the phone. This is accomplished by using the Unrevoked tool from a computer. There is more information about this in the other sections of this forum. This can only be done on phones that do NOT have the official Android 2.2 update installed. If you have 2.2, you can't root without special hardware.
2) Once "rooted", you can download ROM files and install them through the Clockwork recovery. Installing a ROM is generally referred to as "flashing" (there is a reason it is called this, but it has nothing to do with Adobe Flash).
Wait!! I need 2.1 not 2.2?? I had 2.1 but updated because megamanstightgland told me too. can I still use his methode, since i started already? i was at step 2 and didnt know how to pull out nething (im a girl so i never had to do that b4 tehehe) i didnt want too ask two many noob questions, so i ended up to googling searching his steps to figure out how to do some of them. (i think he meant abd not sdk) here's what I did after updating to 2.2....
[email protected]:~$ sudo su
[sudo] password for luvsmyBfdick:
[email protected]:/home/luvsmyBfdick# sh abd pull flashlite.apk
sh: Can't open abd
[email protected]:/home/luvsmyBfdick# dm -f pull abd out -m flashlite.apk /system/data
dm: command not found
[email protected]:/home/luvsmyBfdick# chmod -v remount adb pull* flashlite.apk /homo/user/system
chmod: invalid mode: `remount'
Try `chmod --help' for more information.
[email protected]:/home/luvsmyBfdick# --help
--help: command not found
[email protected]:/home/luvsmyBfdick# -x <85> /tools/win/usb drivers -r/w flashlite.apk
bash: syntax error near unexpected token `85'
Do you think there is a problem with my permission? I have a flash drive (not adobe) with updated permissions on it, but i canot currently find it.
ps. it's not like i wasnt prepare. i installed linux yesterday in my computer cause i read it make this easier... just trying to surprise my boyfriend with a rooted area for his birthday sunday. thanks so much for the help so far guys. your great!
now im readin that i have to be in root on my phone, not just my computer, to do meganmanswhitechesttanned's methode. i really need to help with one of you geeks. ;(
This is the most random troll thread I've ever seen.
drumist said:
This is the most random troll thread I've ever seen.
Click to expand...
Click to collapse
I couldn't agree more.
I had a so-called "wtf-moment". Apparently a girl with this PC: luvsmyBfdi[email protected] wants to be taken seriously with a question...
I'm thinking this is some weird troll thing...
Closed.
I think I'm missing cyttsp_fwloader on my phone. If anyone with an sk17i, and possibly 4.0 / cm9/10 could do a;
Code:
find / -name "cyttsp_fwloader"
for me (in terminal emulator, adb or other means), post the result here, and if the file is found; upload it here!
Background
After flashing the wrong rom for my phone my touch screen stopped working. I have tried a bunch of different things to get it back up; numerous different mods/kernels etc; to no avail. For instance, also wiping the touchscreen drivers etc, even wiping the whole system directory .
Anyway, opening the file hw_config.sh I can see a switch case being run, determining my touch screen driver based on my phone model as specified by the file
/sys/devices/platform/spi_qsd.0/spi0.0/appid
Checking it manually with cat; it seems to be correct!
The two last lines calles two different binaries
cyttsp_fwloader (some arguments, one being the path to a .hex file which I believe is the touch screen driver?)
bq275xx_fwloader
Code:
find / -name "bq275xx_fwloader"
results in hit(s) (have some symlinks due to botbrew-basil)
Code:
find / -name "cyttsp_fwloader"
- nothing!
Hence, I'm led to believe that cyttsp_fwloader is missing from my system.
Who wants a cookie!?
I'm not sure how to best get the attention of someone with an rooted sk17i running cm9 or equivalent who can help me.
I think nobody knows the answer Broo....
Sent from Hubble Telescope
I will try it later and let you know
I'm on sk17i, and I've found "bq275xx_fwloader" in /system/bin. This was on jelly bean.
On my MIUI rom, I've found "bq275xx_fwloader", "cyttsp_fwloader" and "cy8ctma300_fwloader". This is on ics.
I will zip these 3 files and you can flash it through cwm. But it's strange, why should the touchscreen drivers be in bin folder, if every rom has them in bin folder?!
You can download the zip here, but you do this on your own risk, maybe it will be completely destroyed. I don't think so, but only that you know it :good:
Many thanks man! The zip makes it easier to get the stuff over, cool. I'm not sure it matters, but I had to chmod +777 the two files to get them runnable on the device. Now, it seems I was also missing another binary, nvloader if memory serves me right.
I'm trying a few different mods, found a one that gave me back these binaries; I can run hw_config.sh fine now, but still no luck getting the touch to work. So, I have to dig somewhere else; judging from this forums and users similar problems this is not really solved.
Thanks for the help though, much appreciated!
ulph said:
Many thanks man! The zip makes it easier to get the stuff over, cool. I'm not sure it matters, but I had to chmod +777 the two files to get them runnable on the device. Now, it seems I was also missing another binary, nvloader if memory serves me right.
I'm trying a few different mods, found a one that gave me back these binaries; I can run hw_config.sh fine now, but still no luck getting the touch to work. So, I have to dig somewhere else; judging from this forums and users similar problems this is not really solved.
Thanks for the help though, much appreciated!
Click to expand...
Click to collapse
Another user reported the touch would work again after flashing an xperia active rom and the rom for your device again. But I can't promise, maybe your device would brick
any progress?
i have tried flashing the active rom and recieved the following error:
24/002/2012 02:02:05 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_STATIC="IMAGE_ADDRESS_RANGE";ERR_DYNAMIC="SIN-block eraseblock mismatch";
I have attached a screenshot of the same as well. If you come up with a guide to replace the touchscreen files via emulator then it would be of immense help. I am pretty sure it is a software problem.
Another thing i noticed when i logged into the service menu>software info
touch firmware version:
"the phone doesnt support firmware version read." <<<<<< aint this fishy? coz the touchscreen aint taking any input i guess :cyclops:
fuel gauge firmware version
0x0507 0x0507 0x0046 MANG 1
Following many of the excellent CM building guides on xda as well as CM's wiki, I was able to quite smoothly get my virtual Ubuntu to begin building ICS. However, after about 5 minutes of it happily churning out binaries, the build stops complaining about being unable to recognize out/host/linux-x86/obj/EXECUTABLES/mksnapshot_intermediates/src/builtins.o while compiling V8. I've googled around but have not been able to find this particular error; also given my limited understaning of the build system on Linux am unable to diagnose this rather cryptic situation.
I've tried removing the entire out/host/linux-x86/obj/EXECUTABLES/mksnapshot_intermediates/ folder as well as starting afresh (after make clean) but the error does not go away. From what I've grepped, the recipe for builtins.o is inside builtins.P but not sure if this is where something goes meh.
I'm attaching my current build log as well as the builtins.P file. Will be grateful for any ideas on how to troubleshoot this further.
EDIT: building for Galaxy S i9000, but to me this seems like a more general build error and hence posting here. If you think this thread belongs elsewhere, please do let me know.
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?
I'm so I'm just kind of putting this information out there I haven't got to go through it yet on the breakthrough of this knowledge I figured I should just make a post so people can get into it as quickly as possible it does look like the phone is running the same recovery set up as the sm8250 at least it has an entire file directory based on that number there's a lot of interesting files in therehow I got to them = (adb shell [then] cd ./sys/module/ [then] ls --color=auto -a [you should see all the files/dirs]) anyways I'm going to keep doing what I do and try to figure out this thing Happy hunting good luck people
AkayamiShurui said:
I'm so I'm just kind of putting this information out there I haven't got to go through it yet on the breakthrough of this knowledge I figured I should just make a post so people can get into it as quickly as possible it does look like the phone is running the same recovery set up as the sm8250 at least it has an entire file directory based on that number there's a lot of interesting files in therehow I got to them = (adb shell [then] cd ./sys/module/ [then] ls --color=auto -a [you should see all the files/dirs]) anyways I'm going to keep doing what I do and try to figure out this thing Happy hunting good luck people
Click to expand...
Click to collapse
can you do me a favor and pull the file from your that is called "oplus_locking_strategy" ... this may be to a bootloader unlock. For some reason i dont have this file on mine, but also my bootloader i unreachable... id appreciate it thx...
( a simple "adb pull ./sys/module/oplus_locking_strategy /sdcard/oplus_locking_strategy" should do it... then if you can dm me that would be spectacular! thx)
beatbreakee said:
can you do me a favor and pull the file from your that is called "oplus_locking_strategy" ... this may be to a bootloader unlock. For some reason i dont have this file on mine, but also my bootloader i unreachable... id appreciate it thx...
( a simple "adb pull ./sys/module/oplus_locking_strategy /sdcard/oplus_locking_strategy" should do it... then if you can dm me that would be spectacular! thx)
Click to expand...
Click to collapse
I can do you better I can give you the suppository to the phone models so you can just download every file from the phone it even has a link to build the phone with twerp plus it has to build tree files as well >Dumpfiles<
i think i have what you are referring to... i downloaded the original source for our phone, but it does me no good with a locked bootloader because the source does not include the android signing keys. If it did that would be VERY BAD for oneplus cuz anyone could forge updates packages. but afaik that file is not in the source build. i believe it is an after - addon offered to carriers
I can send you a copy
AkayamiShurui said:
I can send you a copy
Click to expand...
Click to collapse
dm sent