yashsingh1/xdaforums huggingface dataset:
[Sony Xperia T, TL, TX, V] soncarl:
Re: Tester Needed Xperia Z Camera

No burst mode?
[Sony Xperia T, TL, TX, V] jasieq:
same here, seems like nothing changed (FW 9.1.A.0.492)
[Sony Xperia T, TL, TX, V] dryla:
Yes right
[Sony Xperia T, TL, TX, V] Noel Macwan:
Thanks Bros For testing ... hmm ... I have also ported unlimited burst mode .. but I don't know why you guys are not getting :(
[Sony Xperia T, TL, TX, V] MrTapa:
Umm seems like your mount points are wrong. Anyone have tryed mounting from recovery first?
[Sony Xperia T, TL, TX, V] AliAlsuhail:
Re: Tester Needed Xperia Z Camera

I mount system before any flash just to be sure, but still nothing changed
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] DFruit:
Here's a somewhat interesting case, I think.

I installed CyanogenMod 10.1 and now have this problem where I can't hear/talk when I make a phone call. The call does connect to the other side (after a brief freeze of the phone app), but I hear nothing. Toggling the phone volume up/down during call makes no sound.

Here's what I've tried thus far:

Flash UXUMA7 modem.

Flash UCLI3 modem (current)

Take out SIM, shutdown phone. Insert SIM, reboot, reboot.

All other functions seem to work fine (messaging, etc.)

I'm on AT&T.

I was planning to reinstall a stock ROM and then flash CM again, but one thing confused me: I could call and hear fine when I was in Europe with a European (Vodaphone) SIM card last week. However, the same problem occurred when I used this SIM card to try to call the US (from Europe). So I'm wondering, is there setting I need to change?

Thanks in advance!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ctalcant:
What ROM did you specifically install?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] DFruit:
CyanogenMod version (after recent update):

10.1-20130304-EXPERIMENTAL-skyrocket-M2
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] xcrazydx:
Full wipe and use the latest nightly
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] DFruit:
Dang. I was hoping for a different answer. I appreciate the help!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] livefree79:
Had the same problem yesterday. I ended up up flashing a stable build of cm10
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mrfeuss:
You could have stuck with 10.1-just not the experimental build. There was a commit added that fixed the no in-call audio bug. The audio is working fine now on the nightly builds. You can check out the thread and see which one has been the most stable for other users.
[Samsung Galaxy Nexus] twistedumbrella:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel [24/03]

So if I follow, this is doing the same thing the current dual boot kernels do but needs two kernels?
[Samsung Galaxy Nexus] Suxsem:
keep trying... true multi boot will be awesome ;)
[Samsung Galaxy Nexus] twistedumbrella:
In theory this is the u-boot kernel with both the first and second kernel for running two 4.2 ROMs. I haven't tested it, but it should fix the issues with the second kernel by fixing the fstab and then symlinking the directories instead of all that realdata stuff that didn't match up to anything
[Samsung Galaxy Nexus] dlhxr:
Thank you so much.

But i tested it and something was wrong.

The screen said Cannot mount filesystem on /dev/block/platform/omap/omap_hsmmc.0/by-name/system at /data/media/2nd/system.

And other stuffs...

I see in your fstab.tuna.

/dev/block/platform/omap/omap_hsmmc.0/by-name/system /data/media/2nd/system ext4 noatime,ro wait
/dev/block/platform/omap/omap_hsmmc.0/by-name/efs /factory ext4 ro wait
/dev/block/platform/omap/omap_hsmmc.0/by-name/cache /data/media/2nd/cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic,noauto_da_alloc,data=writeback wait,check
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata /data/media/2nd/data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic,noauto_da_alloc,data=writeback wait,check,encryptable=/dev/block/platform/omap/omap_hsmmc.0/by-name/metadata

The second parameter is the mount point, right?

/data/media/2nd/system seems not work.....
[Samsung Galaxy Nexus] twistedumbrella:
# Android fstab file.

#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>

It's not working because you can't really mount something to data without mounting data first and you are trying to have a second data folder inside the first. Basically, the way you are trying to do it won't work.
[Samsung Galaxy Nexus] dlhxr:
So it is the end?

/data/2nd/system is even not a mount point, but why you write it in fstab.tuna?

How did the dual-boot work deal with the first-mount stuff?
[Samsung Galaxy Nexus] twistedumbrella:
/dev/block/platform/omap/omap_hsmmc.0/by-name/system /data/media/2nd/system

ext4 noatime,ro wait

I have it that way because you said that was where you were trying to mount...

If this one doesn't work, then you need to restructure the directories to have your "fake" folder as a top-level directory like /udata
[Samsung Galaxy Nexus] dlhxr:
ah, I didn't explain myself well....

What I want is to mount /mmcblk0p12(realdata)/media/2nd/system to /system.....etc.
[Samsung Galaxy Nexus] twistedumbrella:
mmcblk0p12 mounts as /data in the first ROM correct? So in the second ROM, you are mounting a subdirectory of /data, otherwise you just overwrite the first ROMs data. Maybe it's better to leave you to it.
[Samsung Galaxy Nexus] dlhxr:
When I boot into the second rom kernel, I need to firstly mount mmcblk0p12 to /realdata and then mount its subdirectory to /data.

When I am in second rom, it would not influence the first rom because I even didn't load the first rom....
[Samsung Galaxy Nexus] dlhxr:
I made it work and updated my second post in this thread.

But in the second system there's no root access and I can't see what's in data and what's in cache in root explorer....

Don't know what's wrong.
[Samsung Galaxy Nexus] twistedumbrella:
Try this one. I know what's in it and I can explain it if it works, but I don't have a setup to test it on.
[Samsung Galaxy Nexus] dlhxr:
It doesn't work showing system not mounted (can't find /system/xxxxxx)

I unpacked your kernel and I think we should remove the check part during mounting realdata in fstab.tuna because it uses e2fsck in the system partition to check whether the partition mounted right or not, which lead to an error.

After I changed this, the system boots! But still no root access.....

Maybe my updater-script modification is not right?

At last, great work! Thanks a lot!
[Samsung Galaxy Nexus] twistedumbrella:
https://github.com/ThePlayground/uboot-tuna
[Samsung Galaxy Nexus] twistedumbrella:
Classy... but I have one better for ya:

http://xdaforums.com/showthread.php?t=2009485
[Samsung Galaxy Nexus] dlhxr:
it is very interesting...

I followed your git and made the same change (init.rc, init.tuna.rc, fstab.tuna) for leankernel 6.2 and it didn't work...

It is stuck in the u-boot bootimg 2nd kernel on the screen...
[Samsung Galaxy Nexus] wkwkwk:
Hi,

I tried with the stock CM10 kernel and it has the same issue with the brightness.

The Fix_Colour script didn't make a difference.

Maybe it's a problem with 4.1.2 kernels? I think I tried running 2nd with a 4.2.2 and looked all right but I'll give it another go and report back.

Thanks.
[Samsung Galaxy Nexus] twistedumbrella:
Are your brightness settings all normal when it happens? And is it I color tint or is the phone actually brighter as in more power to the backlight?
[Samsung Galaxy Nexus] wkwkwk:
Yes, it's on auto brightness.

I tried to take a screenshot (before and after) and but they are identical on the computer although the 'after' one is much brighter on the screen.

I can't see a colour problem, rather the contrast seems to be higher with u-boot kernel. I tried using the CM10 stock kernel and Franco R300 and both behave the same.

Thanks.
[Samsung Galaxy Nexus] wkwkwk:
I got it sorted, it seems that my panel_id was actually 162.

Everything is now working as expected, thank you.
[Samsung Galaxy Nexus] dlhxr:
Interesting. Do you have the normal gsm gn or other models? I thought we all share the same panel_id.:laugh:
[Samsung Galaxy Nexus] wkwkwk:
Yes, it's a standard (european) galaxy nexus.
[Samsung Galaxy Nexus] wkwkwk:
Hi,

I have a question about the busybox binary. Is the one attached to the first post somehow special?

I'm having the following issue. CM10.1 (a recent nightly) with .img files (all three)

stock kernel with the included busybox -> boot hung after mount_all /fstab.tuna and before busybox mount (confirmed by a mkdir after mount_all)

stock kernel with the busybox attached to the first post -> working as expected, no issues

franco kernel (4.2.2) with the included busybox -> hung as the first attempt

franco kernel (4.2.2) with the attached busybox -> also hung (doesn't like this busybox?)

Any idea what's going on? Is there anyway I can put some debugging on the screen (to see what's the error busybox throws when trying to mount the .img files?)

Thanks.
[Samsung Galaxy Nexus] icedzed:
hi everyone, i can't running ubuntu touch and 4.2 in dual boot =( i try to put ubuntu in 1st boot and cyano in 2nd, and ubuntu doesn't boot, i try to put 1st liquidsmoooth and 2nd ubuntu and nothing boot, can someone give me a working kernel? i'm using saucy-preinstalled-armel+maguro and saucy-preinstalled-phablet-armhf on galaxy nexus, i'm looking to put ubuntu on 2nd boot, now i have liquidsmooth already installed, i follow the guide to edit the file updater-script.. sorry for my bad english
[Samsung Galaxy Nexus] mbi0:
Will this work with 4.3 Kernel ??
[Samsung Galaxy Nexus] twistedumbrella:
If you remake the 4.3 with the same layout it should.
[Samsung Galaxy Nexus] twistedumbrella:
It's not for leanKernel
[Samsung Galaxy Nexus] dlhxr:
it is universal? Why only your kernel can boot?

Is it somthing related to build option to allow kernel boot into links like /system other than mount point?
[Samsung Galaxy Nexus] twistedumbrella:
Every kernel has to be modified with its own ramdisk. That is why this ends up being less efficient than the other method. You are modifying a second kernel every time along with a second ROM every time, and you have to have EVERYTHING installed on the system.
[Samsung Galaxy Nexus] dlhxr:
I know the efficiency problem. But I edit the leankernel as the same as your modification, not just copying your ramdisk. It doesn't work.

Any idea why?

And also do you know why there's no root access?
[Samsung Galaxy Nexus] twistedumbrella:
How about you upload your changes to github so I know what you are doing instead of making me guess. It's hard to fix something when you keep saying my stuff doesn't work and I have no idea what you are using.
[Samsung Galaxy Nexus] dlhxr:
Sorry... I created a git for this.

And in the folder_boot branch

https://github.com/dlhxr/2nd-kernel-for-galaxy-nexus/commit/00801e4d95bfd0ea6e7058e02423276c69daa0b4

After these changes, it is stuck in the u-boot booting second kernel image.

I used the extract.sh and pack_boot.sh to unpack and pack the original kernel downloaded in leankernel thread.

I see someone pulled my repository. Is that you?

And the problem about the image boot is that showing com.android.phone stopped working and can't go into system when booting...

Actually, I just learnt how to use github today...
[Samsung Galaxy Nexus] twistedumbrella:
I didn't pull it. I forked the original and made my changes to that. I am running the kernels from /data/boot and booting the ROM installed to /cache. There is something going wrong with the mounts if you can't get to system. It isn't picking up the cache it sounds like.
[Samsung Galaxy Nexus] dlhxr:
I see. Just make the system partition of the second rom to cache and everything is ok? I'll try later on.

When you have time, would you mind looking at my image boot modification? I can boot into the system, but the com.android.phone fc again and again....
[Samsung Galaxy Nexus] twistedumbrella:
That's what I was talking about.
[Samsung Galaxy Nexus] dlhxr:
I try to change the sysetm position to cache(p11). Showed in my repository.

https://github.com/dlhxr/2nd-kernel-for-galaxy-nexus/commits/folder_boot

But stuck at the rom boot logo...

Any ideas?
[Samsung Galaxy Nexus] dlhxr:
Haha, the folder and cache 2nd rom fully working with my way, including busybox.
[Samsung Galaxy Nexus] twistedumbrella:
If that is what you are using, the only way it is working is stuff getting bypassed. You have the system being mounted two different places in two different ways, and you mount data twice two different ways.
[Samsung Galaxy Nexus] dlhxr:
Small question.... How did you compile your kernel to make the screen show logs when booting?

Maybe it is related to the tuna.defconfig?

I don't know which lines to change to make the kernel doing like that?

Thanks.
[Samsung Galaxy Nexus] dlhxr:
Do you mean lines here?

mount yaffs2 mtd@system /system
mount yaffs2 mtd@system /system ro remount
mount yaffs2 mtd@userdata /data nosuid nodev
mount yaffs2 mtd@cache /cache nosuid nodev

Our phone doesn't have yaffs2 system. Maybe that's the reason these lines don't work.
[Samsung Galaxy Nexus] twistedumbrella:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel [27/03]

I mean the fstab then busybox.

Terminal output is all the vt and console options when you compile.
[Samsung Galaxy Nexus] dlhxr:
I commented most line of the fstab.tuna.

The fstab.tuan only mount cache to system and data to rdata.
[Samsung Galaxy Nexus] twistedumbrella:
[KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel [27/03]

http://xdaforums.com/showthread.php?p=39646088
[Samsung Galaxy Nexus] dlhxr:
I didn't get to understand the triboot...Do you mean by modifying the volume up button to boot the thrid kernel other than the recovery?

Once the scripts were left in, it worked just fine

.

And what do you mean by this?

Is it related to the commit https://github.com/ThePlayground/uboot-tuna/commit/c27da08303b5d5cd46fd53e839c47b5e66cc7d5e?

I don't know why these lines would prevent 2nd booting?

And could you tell me how you managed to make the screen shows the debug message?
[Samsung Galaxy Nexus] twistedumbrella:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel [27/03]

By having the first kernel as a dual-boot kernel

That was just cleanup for governors not in my kernel

I didn't enable debug, that is the output of the dual-boot script.
[Samsung Galaxy Nexus] dlhxr:
I successfully boot from an system image, haha.

After some tests, I'll wirte them here~:laugh:
[Samsung Galaxy Nexus] twistedumbrella:
[KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel [27/03]

Ok? Well I'm going to go do this triboot kernel.
[Samsung Galaxy Nexus] dlhxr:
My way maybe a little buggy. You can help me improve it~

This is my fstab.tuna

#/dev/block/platform/omap/omap_hsmmc.0/by-name/system /system ext4 ro wait
/dev/block/platform/omap/omap_hsmmc.0/by-name/efs /factory ext4 ro wait
#/dev/block/platform/omap/omap_hsmmc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata /rdata ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,encryptable=/dev/block/platform/omap/omap_hsmmc.0/by-name/metadata

This is the modification of the init.tuna.rc

on fs
mkdir /factory 0775 radio radio
exec /sbin/busybox mkdir /rdata
mount_all /fstab.tuna
exec /sbin/busybox mount -t ext4 -o ro /rdata/media/rom/system.img /system
mkdir /rdata/media/2nd
mkdir /rdata/media/2nd/data 0775 system system
mkdir /rdata/media/2nd/cache 0775 system cache
exec /sbin/busybox mount --bind /rdata/media/2nd/data /data
exec /sbin/busybox mount --bind /rdata/media/2nd/cache /cache
setprop ro.crypto.fuse_sdcard true

And

# virtual sdcard daemon running as media_rw (1023)
service sdcard /system/bin/sdcard /rdata/media /mnt/shell/emulated 1023 1023
class late_start

Add a busybox to the /ramdisk/sbin/busybox
[Samsung Galaxy Nexus] twistedumbrella:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel [27/03]

You said that worked.
[Samsung Galaxy Nexus] dlhxr:
Yes, it worked...Take back my words.

And I managed to boot only in images just now.

The line is like this.

mkdir /rdata 0771 system system
mount_all /fstab.tuna
exec /sbin/busybox mount -t ext4 -o ro /rdata/media/rom/system.img /system
exec /sbin/busybox mount -t ext4 -o noatime,nodiratime,nosuid,nodev,commit=19,barrier=0,nobh,nouser_xattr,errors=continue,rw /rdata/media/rom/data.img /data
exec /sbin/busybox mount -t ext4 -o noatime,nodiratime,nosuid,nodev,commit=19,barrier=0,nobh,nouser_xattr,errors=continue,rw /rdata/media/rom/cache.img /cache

However, I don't know the right parameters for mounting data and cahce...Could you help me?

The fstab.tuna says

noatime,nosuid,nodev,nomblk_io_submit,errors=panic

But is seems nomblk_io_submit is not a right parameter for busybox mount command?
[Samsung Galaxy Nexus] twistedumbrella:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel [27/03]

To boot images you need loop devices or they become read only. For that you should look into the ubuntu scripts for the old ubuntu android.
[Samsung Galaxy Nexus] dlhxr:
Never mind...I just put the options in fstab.tuna into my busybox mount lines and add a rw parameter, they worked...

I think it's time to summarize.
[Samsung Galaxy Nexus] twistedumbrella:
That is why it is better to wait until you finish something or really don't know what to do before posting your current progress instead of every single edit.
[Samsung Galaxy Nexus] dlhxr:
OK, I now made three ways (including folder boot, image boot and image folder boot) to boot another rom. And github is up-to-date.

You can check.

https://github.com/dlhxr/2nd-kernel-for-galaxy-nexus:laugh:

I have to say the network in China sucks....It is hard to connect to github...Tried four different ways..So slow...
[Samsung Galaxy Nexus] twistedumbrella:
? Isn't that what I posted earlier? Oh, that isn't a third kernel. Nevermind.
[Samsung Galaxy Nexus] dlhxr:
Sorry....
[Samsung Galaxy Nexus] twistedumbrella:
I've spent the last two days answering questions and you misunderstand one thing and threw a tantrum... It's always a pleasure to keep at something you feel is wasted effort to find out the kid on the other end doesn't even appreciate it. Good luck. I'm done here.
[Samsung Galaxy Nexus] dlhxr:
Treat it something is wrong with me before...

Sorry and I delete the post...

Actually you really helped me a lot in the last two days and you are the only who acompany me to finish the project.

I just don't like your tune...Maybe it is just a language problem...

That's it.
[Samsung Galaxy Nexus] Zittoro:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [28

Does that mean you can't get tri-boot from folder boot way?
[Samsung Galaxy Nexus] dlhxr:
No...The three ways are the same.

The triboot is related to the u-boot.

If we wamt tri-boot, we can modify the u-boot to let it boot the 3rd.img when pressing volum up button.:laugh:
[Samsung Galaxy Nexus] twistedumbrella:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [28

If you want tri-boot, set a dual-boot kernel as your first or second uboot kernel. You don't want to replace the recovery function in the case that something goes wrong to avoid a battery pull.

The app I have going will generate images for system, data, and cache from a zip then modify the kernel on the device for dynamic swapping. One of the options will eventually be using a dual-boot kernel as your primary.
[Samsung Galaxy Nexus] dlhxr:
That's great if you can make an app to do it automatically. The app can also have the boot select.function to make it true multi-boot!

I have no ability to build an app till now...
[Samsung Galaxy Nexus] antonio8297:
hi dlhxr

you can make a small guide to the first setting??

thanks for the guide and the dualboot! : D
[Samsung Galaxy Nexus] dlhxr:
It is a little messy now. I think I'll make it ordered and give a simple guide tomorrow because it is midnight in China now.
[Samsung Galaxy Nexus] antonio8297:
no problem, good night! ;)
[Samsung Galaxy Nexus] Zittoro:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [28

I know I should use a dualboot kernel, but I wonder if it is ok to have two differnet ROM system in cache partition.

Also, because dual boot kernel has huge battery drain, so it would be better if i use three different kernels by using uboot.
[Samsung Galaxy Nexus] twistedumbrella:
[KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [28/03]

What dual-boot kernel were you using? I released one yesterday with some fixes for battery drain included. I think it's the only working one that's "current"

The uBoot could handle three, but two systems in cache would likely be more work than its worth. You could do one in cache and one as images. It would be more reliable that way.
[Samsung Galaxy Nexus] Zittoro:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [28

I used to use the leankernel from Jijonhyuni and the airkernel that he also enabled later. You mean yours is good with battery? If it is, let me have the url please?

I tried to do that on my phone, but the terminal keeps saying unpackbootimg is not executable. I'm not allowed to use computer and my parents dont know I do these things, so I think I have to do it when you enable the function in the app :)

Great work btw.
[Samsung Galaxy Nexus] twistedumbrella:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [28

I'm working on that part now.

Here is the folder: http://goo.im/devs/playground/starkissed

You want the very first one on the list. It's all available on goo manager if you search "playground" also.
[Samsung Galaxy Nexus] twistedumbrella:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [28

The files are in this commit if you don't want to wait on the app:

https://github.com/NoblesseOblige/StarKissedMod/commit/754b7334d12a7fc428b2fc3155f8e41e4c55bee7

The commands are modified from the Koush AnyKernel package. The app has to wait a minute while I finish another project but it's pretty close to done.
[Samsung Galaxy Nexus] Zittoro:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [28

Thanks very much. Have you tested it?

---------- Post added at 01:32 PM ---------- Previous post was at 01:26 PM ----------

@twistedumbrella

How do I download the file? I'm almost new to github
[Samsung Galaxy Nexus] twistedumbrella:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [28

Click files you need. It should be just the unpackbootimg and mkbootimg and click the view raw. It'll download as a .txt file but all you have to do is rename it. On the phone it may download as a .bin which you can rename or even the right way. I haven't downloaded from there on the phone in a while.
[Samsung Galaxy Nexus] Zittoro:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [28

ok I think it should work, but it says segmentation fault when I mkbootimg or unpackbootimg. How do you get it work?
[Samsung Galaxy Nexus] twistedumbrella:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [28

I haven't tested them yet. Ill let you know soon.
[Samsung Galaxy Nexus] Zittoro:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [28

ok thx.
[Samsung Galaxy Nexus] dlhxr:
You can also use my pack&unpack tool with some useful script in post #3
[Samsung Galaxy Nexus] Zittoro:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [28

Yours keeps giving me

not executable: magic 7F45
[Samsung Galaxy Nexus] dlhxr:
Firstly , chmod +x to make it executable.;)

Like

chmod +x ./tools/mkbootimg ./tools/mkbootfs ./tools/unpackbootimg
[Samsung Galaxy Nexus] twistedumbrella:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [28

I had an outdated version. I found out it had to updated for the nexus. No point sending the new one. I'm almost done with the app. It can unpack and pack. Writing the editor now.