can someone explain me some more permissions ?
like
777
677
etc? thank you
are you kidding me?
spacecaker asking about permission?
Lol I just know 777 that's what's said when transferring an app in system/app
Ru r r...
----------------
Sent from my Ace. Galaxy Ace
You have Terminal Emulator .
You can try it yourself .
Herpderp Defy AOKP.
Looks like spacecaker is trolling.
XD
TeamCooper Developer
TheMyth Developer
www.teamcooper.net
Maybe this is a troll thread,but an answer mite help another that stumbles on same question..
As far as i know (or searched in google) 777 is rwxrwxrwx which means all permission is checked. 644 is rw-r--r--
Just in case someone wants to know how they become like that:
Read = 4
Write = 2
Execute =1
First digit is for owner permission,second is group,last is for other's
Please correct me if i'm wrong XD
it's in binary..
777 means all row value is 7 or 111 in binary, so it will be
111
111
111
then 460 will be
100 equal r--
110 equal rw-
000 equal ---
the number 1 means u must tick it..
roxas13th said:
Maybe this is a troll thread,but an answer mite help another that stumbles on same question..
As far as i know (or searched in google) 777 is rwxrwxrwx which means all permission is checked. 644 is rw-r--r--
Just in case someone wants to know how they become like that:
Read = 4
Write = 2
Execute =1
First digit is for owner permission,second is group,last is for other's
Please correct me if i'm wrong XD
Click to expand...
Click to collapse
Yup, you are right.
UGO User Group Other
777 which means users rights 7 rwx, group rights 7 rwx and other rights 7 rwx
Rwx = 4+2+1
Rw = 4 + 2
644 means user/owner can change file content, group where user belong can read, other user (not in group) can read.
X right means that file can be executed like program or script.
diditdr said:
Yup, you are right.
UGO User Group Other
777 which means users rights 7 rwx, group rights 7 rwx and other rights 7 rwx
Rwx = 4+2+1
Rw = 4 + 2
644 means user/owner can change file content, group where user belong can read, other user (not in group) can read.
X right means that file can be executed like program or script.
Click to expand...
Click to collapse
Wow thanks for this. Now I know.
Lol...777=root permissions=full permissions=app that can do every **** you want
---------- Post added at 04:40 PM ---------- Previous post was at 04:39 PM ----------
musf said:
it's in binary..
777 means all row value is 7 or 111 in binary, so it will be
111
111
111
then 460 will be
100 equal r--
110 equal rw-
000 equal ---
the number 1 means u must tick it..
Click to expand...
Click to collapse
Wow..Thanks for googling that for me
Since r=4
Then w=2
And x=1
111=--x--x--x
222=-w--w--w-
444=r--r--r--
421=r---w---x
And the list goes on
Herpderp Defy.
deleted
maybe help for more deep information:
http://www.dartmouth.edu/~rc/help/faq/permissions.html
http://en.wikipedia.org/wiki/Filesystem_permissions
---------- Post added at 11:01 AM ---------- Previous post was at 10:59 AM ----------
EmoBoiix3 said:
Since r=4
Then w=2
And x=1
111=--x--x--x
222=-w--w--w-
444=r--r--r--
421=r---w---x
And the list goes on
Herpderp Defy.
Click to expand...
Click to collapse
LOL...
binary can't be explained with decimal
dianpadi said:
maybe help for more deep information:
http://www.dartmouth.edu/~rc/help/faq/permissions.html
http://en.wikipedia.org/wiki/Filesystem_permissions
---------- Post added at 11:01 AM ---------- Previous post was at 10:59 AM ----------
LOL...
binary can't be explained with decimal
Click to expand...
Click to collapse
I'm not good at this.....just making conjectures
Herpderp Defy.
EmoBoiix3 said:
I'm not good at this.....just making conjectures
Herpderp Defy.
Click to expand...
Click to collapse
I know what you means. just want to say to who post this.
Read = 4
Write = 2
Execute =1
Click to expand...
Click to collapse
Related
I whish to use this tweak...
http://forum.xda-developers.com/showthread.php?t=1010807
i can't find the init.d folder to push the script in... Someone knwo where ?
Yperion said:
The script works only with cyanogens mod roms, i cant post on the dev thread so plz write it for the other users.
Regards.
Click to expand...
Click to collapse
If you don't have CWM then you can do following:
Make a file with this content:
Version 1:
#!/system/bin/sh
if [ -e /sys/devices/virtual/bdi/179:0/read_ahead_kb ]
then
/system/xbin/echo "128" > /sys/devices/virtual/bdi/179:0/read_ahead_kb;
fi;
Version 2 (If the Version 1 is not working for your ROM - credit goes to rafpigna):
# Tweak mmc read-ahead - rafpigna -
mmcfolder="/sys/devices/platform/msm_sdcc.2/mmc_host/mmc1"
cd $mmcfolder
folderlist=`ls -1`
mmcresult=`echo $folderlist | grep -o '\bmmc1:\w*' | sed 's/mmc1://'`
echo 128 > /sys/devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:$mmcresult/block/mmcblk0/queue/read_ahead_kb
cd /
Change the red marked number from 128 to what you need (example 2048) and save it as "99sdcardreadfix", copy it with the Root explorer or push it with ADB into /system/etc/init.d and set permissions to 777. Reboot.
just flash one of the links he posted
It doesn't work with xrecovery ... allready tried.
Sent from my X10i using XDA App
then i have no idea sorry
it worked
Just pushed to /etc/init.d/ set permissions on all checked and reboot
Sd seems to be more fast to open pictures !
Testing with sdcard speed test my result is:
5Mb/s to write and 15 Mb/s to read
Tks
/system/etc/init.d
You have such a folder on x10?
Sent from my X10i using XDA App
28spawn said:
it worked
Just pushed to /etc/init.d/ set permissions on all checked and reboot
Sd seems to be more fast to open pictures !
Testing with sdcard speed test my result is:
5Mb/s to write and 15 Mb/s to read
Tks
Click to expand...
Click to collapse
Pls mate..can you upload the file??
Cuspide said:
You have such a folder on x10?
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Yes! what firmware are you running??
2.1 0435. Bitsnaker ...
I look in system/etc/
No init.d folder ... not even with a search ... :-( strange....
Maybe i bypassed the bootloader ... joking of course
Sent from my X10i using XDA App
Cuspide said:
2.1 0435. Bitsnaker ...
I look in system/etc/
No init.d folder ... not even with a search ... :-( strange....
Maybe i bypassed the bootloader ... joking of course
Sent from my X10i using XDA App
Click to expand...
Click to collapse
ahahah..So you are a rock!!! XD
I don't know why you don't have this folder...Maybe you can create yourself..i have only 1 file inside it!! Anyway i try to create the file and copy it to init.d folder but it's not working!! Any help pls??
I all ready tried to create that folder... put the script in, changed the permission... not working...
Really annoying it really boost sd card reading, noticable whan you open gallery for example...
Cuspide said:
I all ready tried to create that folder... put the script in, changed the permission... not working...
Really annoying it really boost sd card reading, noticable whan you open gallery for example...
Click to expand...
Click to collapse
I think there is an error in the text code:
#!/system/bin/sh
if [ -e /sys/devices/virtual/bdi/179:0/read_ahead_kb ]
then
/system/xbin/echo "128" > /sys/devices/virtual/bdi/179:0/read_ahead_kb;
fi;
I can't get the code to work automatically but it works!
Row Labels Average of Read Average of Write
128 18.067 13.033
2048 62.171 13.793
3072 74.785 13.505
4096 69.367 13.595
with 3072 it even hit 90MB/s sometimes!. thx u mate.
28spawn said:
it worked
Just pushed to /etc/init.d/ set permissions on all checked and reboot
Sd seems to be more fast to open pictures !
Testing with sdcard speed test my result is:
5Mb/s to write and 15 Mb/s to read
Tks
Click to expand...
Click to collapse
wanna share your file ?
"Yperion" wrote me in PM:
:The script works only with cyanogens mod roms, i cant post on the dev thread so plz write it for the other users.
Regards.[/QUOTE]
hmm. i was able to run thru recovery. but i dun feel ALOT of diff. just ABIT faster only.
SD tweeks
mrljlamon said:
wanna share your file ?
Click to expand...
Click to collapse
There is nothing to share here I guess. You are looking at wrong file. there si no system/etc there is only etc/init.d when you use root explorer.
however you can edit your values by
- Manually change read_ahead_kb from 128 to 2048, 3072 or 4096 using root explorer.
i am getting 6 mb/s read and 40 or 50 mb/s write
not bad finding
i was able to increase reading speed from ~10Mb to 18Mb with a script file
the problem with this is that after a reboot it returns to 128Kb
but HELL i had a script so everytime i reboot just need to press one button
atintan said:
There is nothing to share here I guess. You are looking at wrong file. there si no system/etc there is only etc/init.d when you use root explorer.
however you can edit your values by
- Manually change read_ahead_kb from 128 to 2048, 3072 or 4096 using root explorer.
i am getting 6 mb/s read and 40 or 50 mb/s write
Click to expand...
Click to collapse
and witch values you use to get those high values?
can someone tell me the location of build.prop and its permissions?
thnx in advance
Using root explorer navigate to system/build.prop. You can long-press on it to bring up a dialog which will allow you to view or change its permissions
thnx for the quick reply
but can you tell me the exact permisiions it should have because i edited the file and i want to change them?
thnx in advance
[x] [x] [ ]
[x] [x] [ ]
[x] [x] [ ]
Which is rw-rw-rw-
K><A said:
[x] [x] [ ]
[x] [x] [ ]
[x] [x] [ ]
Which is rw-rw-rw-
Click to expand...
Click to collapse
Yes, permissions are 774
D4rKn3sSyS said:
Yes, permissions are 774
Click to expand...
Click to collapse
why did it named 774？？ what mean are these number？？ sorry for my foolishness
Sent from my U20i using Tapatalk
Evillest said:
why did it named 774？？ what mean are these number？？ sorry for my foolishness
Sent from my U20i using Tapatalk
Click to expand...
Click to collapse
#-- --> Owner
-#- --> Goup
--# --> Others
0 --> No permissions
1 --> Execute
2 --> Write
4 --> Read
So, write + read = 6, write + read + execute = 7, and thats how its done !
And im sorry is not 774, its 770 !
D4rKn3sSyS said:
Yes, permissions are 774
Click to expand...
Click to collapse
Arn't the permissions rw- = 6, rw- = 6, rw- = 6 ?
K><A said:
Arn't the permissions rw- = 6, rw- = 6, rw- = 6 ?
Click to expand...
Click to collapse
Yeah, its diabolic number, im sorry again, i think that it was rwxrwx---!
I wrote this for those of you who were wondering how to convert numeric permissions (e.g. 0755) to written form (e.g. rwx-rx-rx) and vice-versa. The numeric form is used by the chmod command as well as in update.zip scripts etc.
I'm sure there are a million descriptions of this out there, but someone asked about this in the developer's forum, so for convenience, here's my explanation. For brevity, I will skip all of the theory behind binary and octal number systems as well as bitwise operations, and just give you the short version.
Permissons will always start with 0 followed by 3 digits, e.g. 0777, 0644 etc (that is just how octal numbers are usually represented).
These digits should be understood as follows: "0UGP". U is the User permission, G is the Group permisson and P is the Public permisson. So a permission of 0641 is User=6, Group=4, Public=1
Now for the description of the numbers (here's where you need some math). Each digit is the SUM of 3 possible permissions.
Read=4
Write=2
Execute=1
Some examples:
7 = 4+2+1 = Read+Write+Execute (ALL permissions).
6 = 4+2 = Read+Write
5 = 4+1 = Read+Execute
4 = Read Only
3 = 2+1 = Write+Execute
2 = Write Only
1 = Execute Only
You get the idea.
Now assume you want to give a file the following permissions: rw-r-r (common for system files).
This means User=Read+Write, Group=Read, and Public=Read
Numerically this would be User=4+2, Group=4, and Public=4
So all together, this would be 0644
Now how about rwx-rx-rx (common for directories).
This would be U=4+3+1, G=4+1, P=4+1.
Altogether: 0755.
Hope that helps. If it doesn't google is your friend. Your best bet is just reading about chmod, the linux command to set permissions. Here is a brief description about the octal representation of permissions used by chmod: http://www.tech-recipes.com/rx/697/unix-advanced-octal-file-permissions-with-chmod/
BTW, here is a great calculator: http://www.javascriptkit.com/script/script2/chmodcal.shtml
Thanks for this and those links. I'm gonna read up on it a little later after work.
exactly the explanation I was looking for. Actually ...better than I was expecting lol
I been wanting to learn more and this is a great start...thanks again!!
Thanks for writing out the explanation. Kudos for being able to tackle it with clarity! It can be hard to phrase correctly.
For those interested:
ricovox said:
Permissons will always start with 0 followed by 3 digits, e.g. 0777, 0644 etc (that is just how octal numbers are usually represented).
Click to expand...
Click to collapse
I'm not sure where you heard this information, but it's not quite correct. It's true that most permissions will start with a 0 (if you're wanting the first digit to be a 0, you can actually exclude the 0 and just use the last three digits to represent your permissions, so 755 works just as well as 0755 since the 0 is assumed unless otherwise specified), but there certainly is a reason for that placeholder and it operates in exactly the same way as the other bits, only it represents different values.
For the first bit (most of the times, a leading 0), the octal system is assigned these settings:
Set User ID (setuid) = 4
Set Group ID (setgid) = 2
Sticky = 1
The setuid and setgid are basically ways to get a program or script to run with the permissions of the owner or group owner, regardless of who is running the program (as long as they already have execute permissions of course) within the created process. This lets you temporary elevate privileges for a single process. This can be dangerous from a security stand-point, so don't mess around with it if you don't know exactly why you need to be changing that value.
The sticky property is a value (in Linux, it's only an applicable property for directories) that prevents anyone or anything from deleting/renaming a file or directory within unless they are the owner or root. It's usually used in areas that are world-writable to prevent users and processes from deleting data that isn't theirs.
In the -rwxrwxrwx format, the sticky bit is indicated by replacing the final "x" with a "t" (or "T" to indicated that the "others" category of permissions doesn't have execute permissions). The setuid and setgid properties are indicated by replacing the "x" in the appropriate place by an "s".
As you can tell if you read this far, you probably won't need to deal with that first digit that often, especially if you have trouble knowing when it'd be appropriate. Again, I've got to emphasize that setuid and setgid can be huge security risks if they are set on anything that runs the risk of a buffer overflow, so use them only when necessary.
While this information isn't as useful as the other digits in permissions, I thought some might be interested.
I would like to know how you add permissions for init.d folder in the aosp source so that the rom supports the init.d folder and scripts in it by default..
Sent from my Galaxy Nexus using Tapatalk 2
iceandfire said:
I would like to know how you add permissions for init.d folder in the aosp source so that the rom supports the init.d folder and scripts in it by default..
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Updater script.
Sent from my Nexus S 4G using xda premium
Well I know that. But where is the updater script built from? Where to add it in the source?
Sent from my Galaxy Nexus using Tapatalk 2
I will link you something when I get home.
Sent from my Nexus S 4G using xda premium
I found the easiest way was to look at a script that did what I want mine to do, then compare it to one that already exists for my device, and merge the two. My $0.02.
lithid-cm said:
I will link you something when I get home.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Still waiting....
chmod is the command , put it in the updater script , and then use the command on desired files ie chmod +777 /system/etc/init.d , something like that , hope it helps
I know what to add. But I want to know from where is the updater script built from the source. Where to add the permissions in the AOSP source for init.d folder.
Ok...this may seem simple, but have you tried using grep to search the code base? And I think it might be done in the releasetools scripts, do you have a releasetool folder in your device tree?
Here you go:
https://github.com/TeamHorizon/android_build/tree/master/tools/releasetools
In this file: https://github.com/TeamHorizon/android_build/blob/master/tools/releasetools/ota_from_target_files
Look at this module:
Code:
import edify_generator
When I get home from work I'll take a closer look at the API and see if I can get you the exact command.
---------- Post added at 03:20 PM ---------- Previous post was at 03:05 PM ----------
def SetPermissions(self, fn, uid, gid, mode)
You are going to want to call that function in there with your arguments. I'm guessing you can take it from here? Or do you need more help?
A little more help would be appreciated. Like what to add.
Sent from my Galaxy Nexus using Tapatalk 2
Ok I've never done this before so we are going to have to try some stuff. Let's start with this.
Find this block of code in the releasetools/ota_from_target_files file.
Code:
def WriteFullOTAPackage(input_zip, output_zip):
# TODO: how to determine this? We don't know what version it will
# be installed on top of. For now, we expect the API just won't
# change very often.
script = edify_generator.EdifyGenerator(3, OPTIONS.info_dict)
metadata = {"post-build": GetBuildProp("ro.build.fingerprint", input_zip),
"pre-device": GetBuildProp("ro.product.device", input_zip),
"post-timestamp": GetBuildProp("ro.build.date.utc", input_zip),
}
device_specific = common.DeviceSpecificParams(
input_zip=input_zip,
input_version=OPTIONS.info_dict["recovery_api_version"],
output_zip=output_zip,
script=script,
input_tmp=OPTIONS.input_tmp,
metadata=metadata,
info_dict=OPTIONS.info_dict)
if not OPTIONS.omit_prereq:
ts = GetBuildProp("ro.build.date.utc", input_zip)
script.AssertOlderBuild(ts)
AppendAssertions(script, input_zip)
device_specific.FullOTA_Assertions()
script.ShowProgress(0.5, 0)
script.Print("")
script.Print("************************************************")
script.Print("* *")
script.Print("* Team Horizon Presents *")
script.Print("* Xenon HD *")
script.Print("* Ice & Fire Adam80460 *")
script.Print("* *")
script.Print("************************************************")
script.Print("")
script.Print("Installing system files...")
if OPTIONS.wipe_user_data:
script.FormatPartition("/data")
script.FormatPartition("/system")
script.Mount("/system")
script.UnpackPackageDir("system", "/system")
(symlinks, retouch_files) = CopySystemFiles(input_zip, output_zip)
script.MakeSymlinks(symlinks)
if OPTIONS.aslr_mode:
script.RetouchBinaries(retouch_files)
else:
script.UndoRetouchBinaries(retouch_files)
boot_img = common.GetBootableImage("boot.img", "boot.img",
OPTIONS.input_tmp, "BOOT")
Item.GetMetadata(input_zip)
Item.Get("system").SetPermissions(script)
common.CheckSize(boot_img.data, "boot.img", OPTIONS.info_dict)
common.ZipWriteStr(output_zip, "boot.img", boot_img.data)
script.ShowProgress(0.2, 0)
script.ShowProgress(0.2, 10)
script.WriteRawImage("/boot", "boot.img")
script.ShowProgress(0.1, 0)
device_specific.FullOTA_InstallEnd()
if OPTIONS.extra_script is not None:
script.AppendExtra(OPTIONS.extra_script)
script.UnmountAll()
script.AddToZip(input_zip, output_zip)
WriteMetadata(metadata, output_zip)
Below the line that says Item.Get("system").SetPermissions(script) add:
Code:
script.SetPermissions("<path to your folder>", uid, gid, XXXX)
Please let me know if it works, I'm curious!
thewadegeek said:
Ok I've never done this before so we are going to have to try some stuff. Let's start with this.
Find this block of code in the releasetools/ota_from_target_files file.
Code:
def WriteFullOTAPackage(input_zip, output_zip):
# TODO: how to determine this? We don't know what version it will
# be installed on top of. For now, we expect the API just won't
# change very often.
script = edify_generator.EdifyGenerator(3, OPTIONS.info_dict)
metadata = {"post-build": GetBuildProp("ro.build.fingerprint", input_zip),
"pre-device": GetBuildProp("ro.product.device", input_zip),
"post-timestamp": GetBuildProp("ro.build.date.utc", input_zip),
}
device_specific = common.DeviceSpecificParams(
input_zip=input_zip,
input_version=OPTIONS.info_dict["recovery_api_version"],
output_zip=output_zip,
script=script,
input_tmp=OPTIONS.input_tmp,
metadata=metadata,
info_dict=OPTIONS.info_dict)
if not OPTIONS.omit_prereq:
ts = GetBuildProp("ro.build.date.utc", input_zip)
script.AssertOlderBuild(ts)
AppendAssertions(script, input_zip)
device_specific.FullOTA_Assertions()
script.ShowProgress(0.5, 0)
script.Print("")
script.Print("************************************************")
script.Print("* *")
script.Print("* Team Horizon Presents *")
script.Print("* Xenon HD *")
script.Print("* Ice & Fire Adam80460 *")
script.Print("* *")
script.Print("************************************************")
script.Print("")
script.Print("Installing system files...")
if OPTIONS.wipe_user_data:
script.FormatPartition("/data")
script.FormatPartition("/system")
script.Mount("/system")
script.UnpackPackageDir("system", "/system")
(symlinks, retouch_files) = CopySystemFiles(input_zip, output_zip)
script.MakeSymlinks(symlinks)
if OPTIONS.aslr_mode:
script.RetouchBinaries(retouch_files)
else:
script.UndoRetouchBinaries(retouch_files)
boot_img = common.GetBootableImage("boot.img", "boot.img",
OPTIONS.input_tmp, "BOOT")
Item.GetMetadata(input_zip)
Item.Get("system").SetPermissions(script)
common.CheckSize(boot_img.data, "boot.img", OPTIONS.info_dict)
common.ZipWriteStr(output_zip, "boot.img", boot_img.data)
script.ShowProgress(0.2, 0)
script.ShowProgress(0.2, 10)
script.WriteRawImage("/boot", "boot.img")
script.ShowProgress(0.1, 0)
device_specific.FullOTA_InstallEnd()
if OPTIONS.extra_script is not None:
script.AppendExtra(OPTIONS.extra_script)
script.UnmountAll()
script.AddToZip(input_zip, output_zip)
WriteMetadata(metadata, output_zip)
Below the line that says Item.Get("system").SetPermissions(script) add:
Code:
script.SetPermissions("<path to your folder>", uid, gid, XXXX)
Please let me know if it works, I'm curious!
Click to expand...
Click to collapse
This is what I got.
http://pastebin.com/SXzNtYrt
Trying something now. Will let you know.
Hahaha sorry I didn't mean literal "uid" and "gid", I meant the one's you wanted to use! I think "0" should work for both. And you don't actually put the "<>" around the brackets either. So try:
script.SetPermissions("/system/etc/init.d", 0, 0, 0755)
thewadegeek said:
Hahaha sorry I didn't mean literal "uid" and "gid", I meant the one's you wanted to use! I think "0" should work for both.
Click to expand...
Click to collapse
Hehe got that. Playing with it.
Cool glad it's going.
Added this in the file in the release tools:
script.SetPermissions("/system/etc/init.d", 0, 0555, 0755)
Got this in my updater script:
set_perm(0, 365, 0755, "/system/etc/init.d");
Will test it tomorrow.
Thanks for the help.
No problem, that's why we have a community. Besides it was nice to get a question from somebody who is actually trying to do something from source, and not all these people that just want to be "l33t" developers.
You probably want to add an entry for /system/etc/init.d in this file.
https://android.googlesource.com/pl...r/include/private/android_filesystem_config.h
So, you probably want to do this.
https://github.com/CyanogenMod/android_system_core/commit/cf47652af591a391c871d1ef8338565d6e5310ea
Hey I recently ported RootBox 4.2 to my device but the compiling process is failing to be completed due to this error -
Code:
Package OTA: /home/kayant/RootBox/out/target/product/mb526/rootbox_mb526-ota-eng.kayant.zip
./build/tools/releasetools/ota_from_target_files -v \
-p /home/kayant/RootBox/out/host/linux-x86 \
-k build/target/product/security/testkey \
--backup=false \
--override_device=auto \
/home/kayant/RootBox/out/target/product/mb526/obj/PACKAGING/target_files_intermediates/rootbox_mb526-target_files-eng.kayant.zip /home/kayant/RootBox/out/target/product/mb526/rootbox_mb526-ota-eng.kayant.zip
unzipping target target-files...
running: unzip -o -q /home/kayant/RootBox/out/target/product/mb526/obj/PACKAGING/target_files_intermediates/rootbox_mb526-target_files-eng.kayant.zip -d /tmp/targetfiles-uSXTQ7
Traceback (most recent call last):
File "./build/tools/releasetools/ota_from_target_files", line 889, in
main(sys.argv[1:])
File "./build/tools/releasetools/ota_from_target_files", line 841, in main
OPTIONS.info_dict = common.LoadInfoDict(input_zip)
File "/home/kayant/RootBox/build/tools/releasetools/common.py", line 146, in LoadInfoDict
d["build.prop"] = LoadBuildProp(zip)
File "/home/kayant/RootBox/build/tools/releasetools/common.py", line 160, in LoadBuildProp
name, value = line.split("=", 1)
ValueError: need more than 1 value to unpack
make: *** [/home/kayant/RootBox/out/target/product/mb526/rootbox_mb526-ota-eng.kayant.zip] Error 1
I have tried a number of things but they didn't work and also I have looked at other build setups like Cyanogenmod's but nothing seems to be different that would make it fail ......
My forked build repo can be found here - https://github.com/Kayant/RootBox_android_build
Thanks for the help...... ^_^
haha, I'm having a similar issue, if someopne could help us, they are really the same
http://pastebin.com/YdQ8y4cJ
I fsomone could help us thanks alot
Re: Compile error - Package OTA failing
bieltv.3 said:
haha, I'm having a similar issue, if someopne could help us, they are really the same
http://pastebin.com/YdQ8y4cJ
I fsomone could help us thanks alot
Click to expand...
Click to collapse
Ahhh we meet again my friend
Yh we hope someone can found a solution to our problem
Let's Go ^_^
Am really not sure why this error is happening now...... I have compared rootbox's build setup to CM's and they are identical now after cherry-picking some stuff but the error still accords .... really don't know what else to try :crying:
Re: Compile error - Package OTA failing
Kayant said:
Am really not sure why this error is happening now...... I have compared rootbox's build setup to CM's and they are identical now after cherry-picking some stuff but the error still accords .... really don't know what else to try :crying:
Click to expand...
Click to collapse
Dunno chamgimg release tools didnt help me either....
Sent from my Nexus 7 using Tapatalk HD
---------- Post added at 08:54 PM ---------- Previous post was at 08:09 PM ----------
FInaly solved wow 2 hours of searching, hope it wil help u
https://github.com/broadcomCM/andro...mmit/4f0bca47a14d08bdf0c3cab0d7bf16b715323257
bieltv.3 said:
Dunno chamgimg release tools didnt help me either....
Sent from my Nexus 7 using Tapatalk HD
---------- Post added at 08:54 PM ---------- Previous post was at 08:09 PM ----------
FInaly solved wow 2 hours of searching, hope it wil help u
https://github.com/broadcomCM/andro...mmit/4f0bca47a14d08bdf0c3cab0d7bf16b715323257
Click to expand...
Click to collapse
Still getting my error oh well I still have one thing I can try
Fix for error --->
https://github.com/Kayant/android_d...mmit/2fe7a5e6ece9d068986b82138f0338267b428e94
https://github.com/Kayant/android_d...mmit/7ef707b92e6a116f71110d0378574e12729990d9