[Script][A2SD]Darktremor 2.7.5.3 Beta 04 [Legend] (01/29/2011)

[tkirton]

Can you send me a logcat to [email protected]? If I can see what's going on, I may be able to fix it.

Also, make sure you are using at least PF4 (PF4a fixes an error I didn't catch when debugging PF4). I ended up rewriting it due to a mysterious low memory condition that cropped up in the Evo (may also have affected the Desire, Legend and Incredible...but it didn't show up in the Hero).

You actually had already answered, my bad, I crossposted this to the original discussion thread, sorry for that.

I tried the new version, but it got me stuck in a bootloop. Also tried using the old version again, increasing the Dalvik heap size, but it didn't help. And I always cleaned my Dalvik cache when enabling JIT.

 

[tkirton]

Your rom isn't starting Apps2sd.

You'll have to break down the boot image, modify the init.rc to add the lines of code to launch apps2sd, reassemble the boot image, then flash it to your phone.

Hi,
I have tried this application but I don't succeed in making to work it as it would owe.
My problem is that it creates badly the run where they owe the apks to be preserved, to it creates here him to me:

/ data/app

instead that to create here it:

/ system/sd/app

and if I check with adb shell (-> su -> ls -l /data) I don't find me these lines:


Is there a remedy?

I have made the test on:

- ROM rooter (poul) [r4]
- My personal ROM

For me Android is new as operating system and therefore I have little experience about it.

Thanks for the answers

 

[tkirton]

Could be that the rom is loaded with SenseUI. I believe to get the JIT working correctly, you have to switch to another launcher other than SenseUI.

But, it could also be issues with the Apps2SD. Try the latest version (PF4a) and see if that fixes anything. If not, let me know and I'll continue working with you on it.

After a clean install of the latest Indigo Bean I flashed Darktremor again, ran a2sd jit in recovery, after rebooting got a bunch of FCs (phone and gapps if I'm not mistaken) and the device became totally unusable. Is this somehow fixable?

 

[tkirton]

The rom may not have the code to actually launch apps2sd.

You can talk to the developer, or give me a few days and I'll see if I can get you a test boot image.

Hi.. I also just wanted to test this.. I have rooted Legend with r4..

Running the Modoco-Rodrigez 2.3 ROM..

When installing this zip.. my phone loops into a continues reboot..
Keeps rebooting itself..

 

[UltimoJedi]

OK! I have resolved, I had not modified the boot.img

thanks for the guide

UJ

Your rom isn't starting Apps2sd.

You'll have to break down the boot image, modify the init.rc to add the lines of code to launch apps2sd, reassemble the boot image, then flash it to your phone.

Yes.
I had understood that it was because of the boot.img
Unfortunately I don't succeed in finding the correct base adress for my Legend (as already says also in the other thread)

 

[schpinn]

Could be that the rom is loaded with SenseUI. I believe to get the JIT working correctly, you have to switch to another launcher other than SenseUI.

But, it could also be issues with the Apps2SD. Try the latest version (PF4a) and see if that fixes anything. If not, let me know and I'll continue working with you on it.

The ROM I'm using is a port of CyanogenMod, so no SenseUI on it. 4a does not seem to fix my problems, it even seems the problems got worse, since it can't even mount my ext3 partition. I've sent you an email with a logcat from my phone.

 

[tkirton]

This base address is very elusive on the Legend. I can't find any information on it.

Someone tried the Nexus One and the Hero base, but was unsuccessful. I noticed that the Magic is the same base as the Hero, so I started thinking maybe the Legend is the same base as the Tattoo (which I do have the base address for).

Try the Tattoo address and see if that works.

UPDATE: UltimoJedi was kind enough to tell me what the base address was on my Hero thread. It is now posted in the Rom Installation Guide.

Yes.
I had understood that it was because of the boot.img
Unfortunately I don't succeed in finding the correct base adress for my Legend (as already says also in the other thread)

 

[tkirton]

I was reading the logcat you sent. Thanks for sending the information regarding the /dev/block. I'm going to have to open up the boot image to see what's going on (since you mention there's a delay in most roms for the Legend).

The ROM I'm using is a port of CyanogenMod, so no SenseUI on it. 4a does not seem to fix my problems, it even seems the problems got worse, since it can't even mount my ext3 partition. I've sent you an email with a logcat from my phone.

 

[tkirton]

Bumped due to a Legend rom being included.

 

[tkirton]

Bump...new version released (2.7.5 RC2)

 

[tkirton]

Bump...new version 2.7.5 RC3

 

[maormark]

problem to include Darktremor Apps2SD in rom

I did everything listed, But no file is created named nowboot.img

0x12c00000 - HTC Legend

typed ./makeboot ../boot.img-kernel ../newramdisk.gz ../newboot.img #0x12c00000#

its say:
[ ] creating New Boot Image
./makeboot: line 4: ./scripts/mkbootimg: No such file or directory

Any idea what to do?.

 

[tkirton]

You are either missing the mkbootimg or you don't have the proper structure installed.

...or there's an error in the program.

If mkbootimg is in the same directory as makeboot, just take an editor (gvim) and edit the line that has mkbootimg. Just take out a slash and the word "scripts". Save and try again.

problem to include Darktremor Apps2SD in rom

I did everything listed, But no file is created named nowboot.img

0x12c00000 - HTC Legend

typed ./makeboot ../boot.img-kernel ../newramdisk.gz ../newboot.img #0x12c00000#

its say:
[ ] creating New Boot Image
./makeboot: line 4: ./scripts/mkbootimg: No such file or directory

Any idea what to do?.

 

[maormark]

You are either missing the mkbootimg or you don't have the proper structure installed.

...or there's an error in the program.

If mkbootimg is in the same directory as makeboot, just take an editor (gvim) and edit the line that has mkbootimg. Just take out a slash and the word "scripts". Save and try again.

That's what I did based on the terminal:
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

[email protected]:~$ cd ..
[email protected]:/home$ cd ..
[email protected]:/$ cd media
[email protected]:/media$ cd 2EF4A9CBF4A9961D
[email protected]:/media/2EF4A9CBF4A9961D$ cd workspace
[email protected]:/media/2EF4A9CBF4A9961D/workspace$ chmod 755 *
[email protected]:/media/2EF4A9CBF4A9961D/workspace$ cd scripts
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./getramdisk
[ ] Extracting Ramdisk from Boot Image
Page size: 2048 (0x00000800)
Kernel size: 2178840 (0x00213f18)
Ramdisk size: 166445 (0x00028a2d)
Second size: 0 (0x00000000)
Board name:
Command line: no_console_suspend=1 console=null
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
[ ] Uncompressing Ramdisk Image
536 blocks
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ cd ..
[email protected]:/media/2EF4A9CBF4A9961D/workspace$ cd ramdisk
[email protected]:/media/2EF4A9CBF4A9961D/workspace/ramdisk$ cd ..
[email protected]:/media/2EF4A9CBF4A9961D/workspace$ cd scripts
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./makeramdisk
rm: cannot remove `../newramdisk.gz': No such file or directory
[ ] Creating Ramdisk Image newramdisk.gz
537 blocks
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./makeboot ../boot.img-kernel ../newramdisk.gz ../newboot.img 0x12c00000
[ ] Creating New Boot Image
./makeboot: line 4: ./scripts/mkbootimg: No such file or directory
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$

after i taked out the slash and the word "scripts" from the file makeboot
and tried again it's says:
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./makeboot ../boot.img-kernel ../newramdisk.gz ../newboot.img 0x12c00000
[ ] Creating New Boot Image
./makeboot: line 4: ./mkbootimg: No such file or directory
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$

Still not working.

 

[tkirton]

Do you have a mkbootimg in scripts directory? If so, is the permissions set correctly on it (I usually do a chmod 777 mkbootimg just to be sure).

Download the tools again: http://www.darktremor.info/files/tools/buildscripts.tar.gz and uncompress them in the scripts directory.

That's what I did based on the terminal:
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

[email protected]:~$ cd ..
[email protected]:/home$ cd ..
[email protected]:/$ cd media
[email protected]:/media$ cd 2EF4A9CBF4A9961D
[email protected]:/media/2EF4A9CBF4A9961D$ cd workspace
[email protected]:/media/2EF4A9CBF4A9961D/workspace$ chmod 755 *
[email protected]:/media/2EF4A9CBF4A9961D/workspace$ cd scripts
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./getramdisk
[ ] Extracting Ramdisk from Boot Image
Page size: 2048 (0x00000800)
Kernel size: 2178840 (0x00213f18)
Ramdisk size: 166445 (0x00028a2d)
Second size: 0 (0x00000000)
Board name:
Command line: no_console_suspend=1 console=null
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
[ ] Uncompressing Ramdisk Image
536 blocks
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ cd ..
[email protected]:/media/2EF4A9CBF4A9961D/workspace$ cd ramdisk
[email protected]:/media/2EF4A9CBF4A9961D/workspace/ramdisk$ cd ..
[email protected]:/media/2EF4A9CBF4A9961D/workspace$ cd scripts
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./makeramdisk
rm: cannot remove `../newramdisk.gz': No such file or directory
[ ] Creating Ramdisk Image newramdisk.gz
537 blocks
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./makeboot ../boot.img-kernel ../newramdisk.gz ../newboot.img 0x12c00000
[ ] Creating New Boot Image
./makeboot: line 4: ./scripts/mkbootimg: No such file or directory
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$

after i taked out the slash and the word "scripts" from the file makeboot
and tried again it's says:
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./makeboot ../boot.img-kernel ../newramdisk.gz ../newboot.img 0x12c00000
[ ] Creating New Boot Image
./makeboot: line 4: ./mkbootimg: No such file or directory
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$

Still not working.

 

[maormark]

Do you have a mkbootimg in scripts directory? If so, is the permissions set correctly on it (I usually do a chmod 777 mkbootimg just to be sure).

Download the tools again: http://www.darktremor.info/files/tools/buildscripts.tar.gz and uncompress them in the scripts directory.

Same thing

To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

[email protected]:~$ cd ..
[email protected]:/home$ cd ..
[email protected]:/$ cd media
[email protected]:/media$ cd 2EF4A9CBF4A9961D
[email protected]:/media/2EF4A9CBF4A9961D$ cd workspace
[email protected]:/media/2EF4A9CBF4A9961D/workspace$ chmod 755 *
[email protected]:/media/2EF4A9CBF4A9961D/workspace$ chmod 777 *
[email protected]:/media/2EF4A9CBF4A9961D/workspace$ cd scripts
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./getramdisk
[ ] Extracting Ramdisk from Boot Image
Page size: 2048 (0x00000800)
Kernel size: 2178840 (0x00213f18)
Ramdisk size: 166445 (0x00028a2d)
Second size: 0 (0x00000000)
Board name:
Command line: no_console_suspend=1 console=null
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
[ ] Uncompressing Ramdisk Image
536 blocks
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ cd ..
[email protected]:/media/2EF4A9CBF4A9961D/workspace$ cd ramdisk
[email protected]:/media/2EF4A9CBF4A9961D/workspace/ramdisk$ cd ..
[email protected]:/media/2EF4A9CBF4A9961D/workspace$ cd scripts
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./makeramdisk
./makeramdisk: line 2: cd: /ramdisk: No such file or directory
rm: cannot remove `../newramdisk.gz': No such file or directory
[ ] Creating Ramdisk Image newramdisk.gz
114 blocks
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./makeboot ../boot.img-kernel ../newramdisk.gz ../newboot.img 0x12c00000
[ ] Kernel File: ../boot.img-kernel
[ ] Ramdisk File: ../newramdisk.gz
[ ] Output File: ../newboot.img
[ ] Base Address: 0x12c00000
[ ] Erasing File: ../newboot.img
rm: cannot remove `../newboot.img': No such file or directory
[ ] Creating new boot image.
./makeboot: line 69: ./mkbootimg: No such file or directory
[ ] Setting Permissions: ../newboot.img
chmod: cannot access `../newboot.img': No such file or directory
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$

 

[tkirton]

You must have a permissions issue on mkbootimg.

Go into the scripts directory and type the following:

chmod 777 mkbootimg

Then try again.

I just tested this script again...same script you are using. Works perfectly on my system.

Same thing

To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

[email protected]:~$ cd ..
[email protected]:/home$ cd ..
[email protected]:/$ cd media
[email protected]:/media$ cd 2EF4A9CBF4A9961D
[email protected]:/media/2EF4A9CBF4A9961D$ cd workspace
[email protected]:/media/2EF4A9CBF4A9961D/workspace$ chmod 755 *
[email protected]:/media/2EF4A9CBF4A9961D/workspace$ chmod 777 *
[email protected]:/media/2EF4A9CBF4A9961D/workspace$ cd scripts
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./getramdisk
[ ] Extracting Ramdisk from Boot Image
Page size: 2048 (0x00000800)
Kernel size: 2178840 (0x00213f18)
Ramdisk size: 166445 (0x00028a2d)
Second size: 0 (0x00000000)
Board name:
Command line: no_console_suspend=1 console=null
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
[ ] Uncompressing Ramdisk Image
536 blocks
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ cd ..
[email protected]:/media/2EF4A9CBF4A9961D/workspace$ cd ramdisk
[email protected]:/media/2EF4A9CBF4A9961D/workspace/ramdisk$ cd ..
[email protected]:/media/2EF4A9CBF4A9961D/workspace$ cd scripts
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./makeramdisk
./makeramdisk: line 2: cd: /ramdisk: No such file or directory
rm: cannot remove `../newramdisk.gz': No such file or directory
[ ] Creating Ramdisk Image newramdisk.gz
114 blocks
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./makeboot ../boot.img-kernel ../newramdisk.gz ../newboot.img 0x12c00000
[ ] Kernel File: ../boot.img-kernel
[ ] Ramdisk File: ../newramdisk.gz
[ ] Output File: ../newboot.img
[ ] Base Address: 0x12c00000
[ ] Erasing File: ../newboot.img
rm: cannot remove `../newboot.img': No such file or directory
[ ] Creating new boot image.
./makeboot: line 69: ./mkbootimg: No such file or directory
[ ] Setting Permissions: ../newboot.img
chmod: cannot access `../newboot.img': No such file or directory
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$

 

[maormark]

You must have a permissions issue on mkbootimg.

Go into the scripts directory and type the following:

chmod 777 mkbootimg

Then try again.

I just tested this script again...same script you are using. Works perfectly on my system.

Unfortunately I still could not get it works, maybe it's too much to ask from you to make the ROM, but if you can here is the link:
http://rapidshare.com/files/4120489...ISR_2.05.461.52_signed_081010_083339.zip.html

The problem by terminal:
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

[email protected]:~$ cd ..
[email protected]:/home$ cd ..
[email protected]:/$ cd media
[email protected]:/media$ cd 2EF4A9CBF4A9961D
[email protected]:/media/2EF4A9CBF4A9961D$ cd workspace
[email protected]:/media/2EF4A9CBF4A9961D/workspace$ chmod 755 *
[email protected]:/media/2EF4A9CBF4A9961D/workspace$ chmod 777 *
[email protected]:/media/2EF4A9CBF4A9961D/workspace$ cd scripts
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 755 *
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 777 *
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 777 mkbootimg
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 755 mkbootimg
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 755 mkbootfs
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 777 mkbootfs
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./getramdisk
[ ] Extracting Ramdisk from Boot Image
Page size: 2048 (0x00000800)
Kernel size: 2178840 (0x00213f18)
Ramdisk size: 166445 (0x00028a2d)
Second size: 0 (0x00000000)
Board name:
Command line: no_console_suspend=1 console=null
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
[ ] Uncompressing Ramdisk Image
536 blocks
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./makeramdisk
./makeramdisk: line 2: cd: /ramdisk: No such file or directory
rm: cannot remove `../newramdisk.gz': No such file or directory
[ ] Creating Ramdisk Image newramdisk.gz
114 blocks
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 755 makeramdisk
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 777 [email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./makeramdisk
./makeramdisk: line 2: cd: /ramdisk: No such file or directory
[ ] Creating Ramdisk Image newramdisk.gz
114 blocks
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 755 makeboot
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 777 makeboot
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./makeboot ../boot.img-kernel ../newramdisk.gz ../newboot.img 0x12c00000
[ ] Kernel File: ../boot.img-kernel
[ ] Ramdisk File: ../newramdisk.gz
[ ] Output File: ../newboot.img
[ ] Base Address: 0x12c00000
[ ] Erasing File: ../newboot.img
rm: cannot remove `../newboot.img': No such file or directory
[ ] Creating new boot image.
./makeboot: line 69: ./mkbootimg: No such file or directory
[ ] Setting Permissions: ../newboot.img
chmod: cannot access `../newboot.img': No such file or directory
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$

 

[tkirton]

I'll see what I can do.

However, I did see where you ran the chmod 777 on makeboot. Try running that same command on mkbootimg (maybe I specified the wrong file).

chmod 777 mkbootimg

Then try again.

While you are doing that, I'll see about making the modifications in the boot.img for you.

Unfortunately I still could not get it works, maybe it's too much to ask from you to make the ROM, but if you can here is the link:
http://rapidshare.com/files/4120489...ISR_2.05.461.52_signed_081010_083339.zip.html

The problem by terminal:
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

[email protected]:~$ cd ..
[email protected]:/home$ cd ..
[email protected]:/$ cd media
[email protected]:/media$ cd 2EF4A9CBF4A9961D
[email protected]:/media/2EF4A9CBF4A9961D$ cd workspace
[email protected]:/media/2EF4A9CBF4A9961D/workspace$ chmod 755 *
[email protected]:/media/2EF4A9CBF4A9961D/workspace$ chmod 777 *
[email protected]:/media/2EF4A9CBF4A9961D/workspace$ cd scripts
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 755 *
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 777 *
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 777 mkbootimg
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 755 mkbootimg
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 755 mkbootfs
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 777 mkbootfs
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./getramdisk
[ ] Extracting Ramdisk from Boot Image
Page size: 2048 (0x00000800)
Kernel size: 2178840 (0x00213f18)
Ramdisk size: 166445 (0x00028a2d)
Second size: 0 (0x00000000)
Board name:
Command line: no_console_suspend=1 console=null
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
[ ] Uncompressing Ramdisk Image
536 blocks
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./makeramdisk
./makeramdisk: line 2: cd: /ramdisk: No such file or directory
rm: cannot remove `../newramdisk.gz': No such file or directory
[ ] Creating Ramdisk Image newramdisk.gz
114 blocks
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 755 makeramdisk
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 777 [email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./makeramdisk
./makeramdisk: line 2: cd: /ramdisk: No such file or directory
[ ] Creating Ramdisk Image newramdisk.gz
114 blocks
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 755 makeboot
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 777 makeboot
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./makeboot ../boot.img-kernel ../newramdisk.gz ../newboot.img 0x12c00000
[ ] Kernel File: ../boot.img-kernel
[ ] Ramdisk File: ../newramdisk.gz
[ ] Output File: ../newboot.img
[ ] Base Address: 0x12c00000
[ ] Erasing File: ../newboot.img
rm: cannot remove `../newboot.img': No such file or directory
[ ] Creating new boot image.
./makeboot: line 69: ./mkbootimg: No such file or directory
[ ] Setting Permissions: ../newboot.img
chmod: cannot access `../newboot.img': No such file or directory
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$

 

[maormark]

I'll see what I can do.

However, I did see where you ran the chmod 777 on makeboot. Try running that same command on mkbootimg (maybe I specified the wrong file).

chmod 777 mkbootimg

Then try again.

While you are doing that, I'll see about making the modifications in the boot.img for you.

I also tried it you can see rows 11,12:
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 777 mkbootimg
[email protected]:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 755 mkbootimg