Database Users

Trying to build the stock kernel from source [SOLVED]

edit: The stock kernel can be built following this thread.
I'm trying to build the stock kernel from source (the one from huaweidevice). I'm running Ubuntu 10.10 64-bit.
I've gotten this far:
- I've extracted config from phone /proc/config.gz and copied it to kernel/.config
- I went through this guide: source.android.com source initializing.html
- I created some symbolic links to get rid of file not found errors when compiling:
kernel-2.6.32-U8800-Froyo/kernel/net/netfilter$ ln -s xt_connmark.c xt_CONNMARK.c
kernel-2.6.32-U8800-Froyo/kernel/net/netfilter$ ln -s xt_HL.c xt_hl.c
kernel-2.6.32-U8800-Froyo/kernel/net/netfilter$ ln -s xt_MARK.c xt_mark.c
kernel-2.6.32-U8800-Froyo/kernel/net/ipv4/netfilter$ ln -s ipt_ECN.c ipt_ecn.c
kernel-2.6.32-U8800-Froyo/kernel/include/linux/netfilter$ ln -s xt_mark.h xt_MARK.h
kernel-2.6.32-U8800-Froyo/kernel/include/linux/netfilter_ipv4$ ln -s ipt_ecn.h ipt_ECN.h
kernel-2.6.32-U8800-Froyo/kernel/include/linux/netfilter$ ln -s xt_DSCP.h xt_dscp.h
kernel-2.6.32-U8800-Froyo/kernel/include/linux/netfilter_ipv4$ ln -s ipt_ttl.h ipt_TTL.h
kernel-2.6.32-U8800-Froyo/kernel/include/linux/netfilter_ipv6$ ln -s ip6t_hl.h ip6t_HL.h
Now for the cross compilation I've tried 3 different toolchains:
- The ones from developer.android.com sdk ndk index.html
- and codesourcery.com sgpp lite arm portal package8734/public/arm-none-eabi/arm-2011.03-42-arm-none-eabi-i686-pc-linux-gnu.tar.bz2
then I've tried compiling with:
make -j8 ARCH=arm CROSS_COMPILE=.../android-ndk-r5b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-
and
make -j8 ARCH=arm CROSS_COMPILE=.../android-ndk-r5b/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin/arm-eabi-
and
make -j8 ARCH=arm CROSS_COMPILE=.../arm-2011.03/bin/arm-none-eabi-
they all give me output similar to this (this is with the 4.4.0 toolchain):
Code:
CHK include/linux/version.h
SYMLINK include/asm -> include/asm-arm
make[1]: `include/asm-arm/mach-types.h' is up to date.
CHK include/linux/utsrelease.h
CALL scripts/checksyscalls.sh
CHK include/linux/compile.h
CC net/netfilter/xt_MARK.o
CC net/ipv4/netfilter/ipt_ecn.o
CC net/netfilter/xt_NFQUEUE.o
CC net/ipv4/netfilter/ipt_NETMAP.o
CC net/netfilter/xt_comment.o
CC net/netfilter/xt_connlimit.o
net/netfilter/xt_MARK.c: In function 'mark_tg':
net/netfilter/xt_MARK.c:32: error: dereferencing pointer to incomplete type
net/netfilter/xt_MARK.c:32: error: dereferencing pointer to incomplete type
net/netfilter/xt_MARK.c: At top level:
net/netfilter/xt_MARK.c:41: error: invalid application of 'sizeof' to incomplete type 'struct xt_mark_tginfo2'
make[2]: *** [net/netfilter/xt_MARK.o] Error 1
make[2]: *** Waiting for unfinished jobs....
CC net/ipv4/netfilter/ipt_REDIRECT.o
CC net/ipv4/netfilter/ipt_REJECT.o
cc1: warnings being treated as errors
net/ipv4/netfilter/ipt_ecn.c:29: error: 'struct ipt_ECN_info' declared inside parameter list
net/ipv4/netfilter/ipt_ecn.c:29: error: its scope is only this definition or declaration, which is probably not what you want
net/ipv4/netfilter/ipt_ecn.c: In function 'set_ect_ip':
net/ipv4/netfilter/ipt_ecn.c:33: error: 'XT_DSCP_MASK' undeclared (first use in this function)
net/ipv4/netfilter/ipt_ecn.c:33: error: (Each undeclared identifier is reported only once
net/ipv4/netfilter/ipt_ecn.c:33: error: for each function it appears in.)
net/ipv4/netfilter/ipt_ecn.c:33: error: dereferencing pointer to incomplete type
net/ipv4/netfilter/ipt_ecn.c:40: error: dereferencing pointer to incomplete type
net/ipv4/netfilter/ipt_ecn.c: At top level:
net/ipv4/netfilter/ipt_ecn.c:48: error: 'struct ipt_ECN_info' declared inside parameter list
net/ipv4/netfilter/ipt_ecn.c: In function 'set_ect_tcp':
net/ipv4/netfilter/ipt_ecn.c:58: error: dereferencing pointer to incomplete type
net/ipv4/netfilter/ipt_ecn.c:58: error: 'IPT_ECN_OP_SET_ECE' undeclared (first use in this function)
net/ipv4/netfilter/ipt_ecn.c:59: error: dereferencing pointer to incomplete type
net/ipv4/netfilter/ipt_ecn.c:60: error: dereferencing pointer to incomplete type
net/ipv4/netfilter/ipt_ecn.c:60: error: 'IPT_ECN_OP_SET_CWR' undeclared (first use in this function)
net/ipv4/netfilter/ipt_ecn.c:61: error: dereferencing pointer to incomplete type
net/ipv4/netfilter/ipt_ecn.c:69: error: dereferencing pointer to incomplete type
net/ipv4/netfilter/ipt_ecn.c:70: error: dereferencing pointer to incomplete type
net/ipv4/netfilter/ipt_ecn.c:71: error: dereferencing pointer to incomplete type
net/ipv4/netfilter/ipt_ecn.c:72: error: dereferencing pointer to incomplete type
net/ipv4/netfilter/ipt_ecn.c: In function 'ecn_tg':
net/ipv4/netfilter/ipt_ecn.c:84: error: dereferencing pointer to incomplete type
net/ipv4/netfilter/ipt_ecn.c:84: error: 'IPT_ECN_OP_SET_IP' undeclared (first use in this function)
net/ipv4/netfilter/ipt_ecn.c:85: error: passing argument 2 of 'set_ect_ip' from incompatible pointer type
net/ipv4/netfilter/ipt_ecn.c:29: note: expected 'const struct ipt_ECN_info *' but argument is of type 'const struct ipt_ECN_info *'
net/ipv4/netfilter/ipt_ecn.c:88: error: dereferencing pointer to incomplete type
net/ipv4/netfilter/ipt_ecn.c:88: error: 'IPT_ECN_OP_SET_ECE' undeclared (first use in this function)
net/ipv4/netfilter/ipt_ecn.c:88: error: 'IPT_ECN_OP_SET_CWR' undeclared (first use in this function)
net/ipv4/netfilter/ipt_ecn.c:90: error: passing argument 2 of 'set_ect_tcp' from incompatible pointer type
net/ipv4/netfilter/ipt_ecn.c:48: note: expected 'const struct ipt_ECN_info *' but argument is of type 'const struct ipt_ECN_info *'
net/ipv4/netfilter/ipt_ecn.c: In function 'ecn_tg_check':
net/ipv4/netfilter/ipt_ecn.c:101: error: dereferencing pointer to incomplete type
net/ipv4/netfilter/ipt_ecn.c:101: error: 'IPT_ECN_OP_MASK' undeclared (first use in this function)
net/ipv4/netfilter/ipt_ecn.c:103: error: dereferencing pointer to incomplete type
net/ipv4/netfilter/ipt_ecn.c:106: error: dereferencing pointer to incomplete type
net/ipv4/netfilter/ipt_ecn.c:106: error: 'XT_DSCP_MASK' undeclared (first use in this function)
net/ipv4/netfilter/ipt_ecn.c:108: error: dereferencing pointer to incomplete type
net/ipv4/netfilter/ipt_ecn.c:111: error: dereferencing pointer to incomplete type
net/ipv4/netfilter/ipt_ecn.c:111: error: 'IPT_ECN_OP_SET_ECE' undeclared (first use in this function)
net/ipv4/netfilter/ipt_ecn.c:111: error: 'IPT_ECN_OP_SET_CWR' undeclared (first use in this function)
net/ipv4/netfilter/ipt_ecn.c: At top level:
net/ipv4/netfilter/ipt_ecn.c:124: error: invalid application of 'sizeof' to incomplete type 'struct ipt_ECN_info'
make[3]: *** [net/ipv4/netfilter/ipt_ecn.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[1]: *** [net/netfilter] Error 2
make[1]: *** Waiting for unfinished jobs....
make[2]: *** [net/ipv4/netfilter] Error 2
make[1]: *** [net/ipv4] Error 2
make: *** [net] Error 2
sorry for the messed up links, I'm not allowed to post links (yet).
Any ideas how to get forward?
The reason I'm doing this is that I want to fix the bug that the internal mic is disabled when a stereo headphone / or a 3.5mm jack - 2xrca cable is plugged in. I think I can fix it from kernel-2.6.32-U8800-Froyo/kernel/arch/arm/mach-msm/rpc_server_handset.c, but first I have to get my build environment working

copy missing files instead of link
xt_MARK.c and xt_mark.c are not the same, at least in my source
try copy the missing file from android source
http://android.git.kernel.org/?p=kernel/msm.git;a=tree

wmi543 said:
xt_MARK.c and xt_mark.c are not the same, at least in my source
try copy the missing file from android source
Click to expand...
Click to collapse
It worked I copied all the files from the git instead of ln -s.
"Kernel: arch/arm/boot/zImage is ready"
Thanks for the quick reply.
Then I had to remove comment out CONFIG_FB_MSM_MDDI_NT35582_WVGA=y line from .config and answer no to two questions when running make.
I used the 4.4.0 toolchain
Now I have the zImage but don't know how it'll work because the CONFIG_FB_MSM_MDDI_NT35582_WVGA probably has something to do with the display type.
BTW I've taken a backup with genokolar's recovery img. When I try this new kernel and if I can't boot, I should be able to get it to boot again by doing a restore from the earlier backup?
Now I'll start looking into packing the kernel to an .img (android-dls.com wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images#Structure_of_boot_and_recovery_images)..

OK. I copied the boot.img from the phone in bootloader mode, unpacked it with unpack-bootimg.pl. Then I bsdiffed (binary diff) the resulting boot.img-kernel.gz with the Image file I built, the patch file is only 389K so looks like they are quite similar. The only differences may be because of the display thing I changed in the Makefile.
Might try tomorrow to replace the unpacked kernel with the Image file and see if it works. What is the worst case scenario? I should always be able to restore from the old backup if it doesn't boot?
Maybe I'll also try to get the display thing to build right before trying it on the phone
edit: I read somewhere the .gz extension in the unpacked kernel file is a bug with the unpacking script, so "boot.img-kernel.gz" is actually the unpacked kernel file (so it should be the same as compiled Image) ?

Looks like the unpack-bootimg.pl and repack-bootimg.pl are not working right for the U8800 boot.img. I just tried to unpack the original boot.img and repack it, I got a blue screen when trying to boot. I could restore the original just by going to bootloader mode and copying back the original.
Any ideas how to unpack and repack the boot.img of the U8800?

You can repack the boot/recovery images with the following:
Code:
./mkbootfs RAMDISK DIRECTORY | ./minigzip > ramdisk-boot.img
./mkbootimg --kernel KERNEL --ramdisk ramdisk-boot.img --base 0x00200000 --pagesize 4096 --cmdline 'console=ttyDCC0 androidboot.hardware=huawei' -o boot.img
I just modified the repack perl script accordingly and added lines so that it will mount cust_backup and transfer the image across for me. Saves heaps of time.

stockwell said:
You can repack the boot/recovery images with the following:
Code:
./mkbootfs RAMDISK DIRECTORY | ./minigzip > ramdisk-boot.img
./mkbootimg --kernel KERNEL --ramdisk ramdisk-boot.img --base 0x00200000 --pagesize 4096 --cmdline 'console=ttyDCC0 androidboot.hardware=huawei' -o boot.img
I just modified the repack perl script accordingly and added lines so that it will mount cust_backup and transfer the image across for me. Saves heaps of time.
Click to expand...
Click to collapse
I used the unpack script from http://forum.xda-developers.com/showthread.php?t=891333 then modified the line "#$bootimg = substr($bootimg,2048);" to "$bootimg = substr($bootimg,4096);". There's still a difference of 215 bytes with the repacked img, but it works.
Now I can test the kernel I built myself. Thank you for the help.
edit: Looks like the built kernel doesn't work, now I can start tackling that

CONFIG_FB_MSM_MDDI_NT35582_WVGA=y
if you see only blue screen when you boot your own kernel, refer to my experience, edit .config, change 2 lines as below instead of comment out CONFIG_FB_MSM_MDDI_NT35582_WVGA=y should fix it
CONFIG_FB_MSM_MDDI_AUTO_DETECT=y
CONFIG_FB_MSM_TRY_MDDI_CATCH_LCDC_PRISM=y
BTW, there is a tool "abootimg" which is quite handy for packing the kernel
http://gitorious.org/ac100/abootimg

wmi543 said:
if you see only blue screen when you boot your own kernel, refer to my experience, edit .config, change 2 lines as below instead of comment out CONFIG_FB_MSM_MDDI_NT35582_WVGA=y should fix it
CONFIG_FB_MSM_MDDI_AUTO_DETECT=y
CONFIG_FB_MSM_TRY_MDDI_CATCH_LCDC_PRISM=y
BTW, there is a tool "abootimg" which is quite handy for packing the kernel
http://gitorious.org/ac100/abootimg
Click to expand...
Click to collapse
Works! great! Thanks for the help. Hopefully soon I can release my fixed kernel

Sorry, I'm new to Android. What advantages are there if you get the stock kernel or whatever?

"Stock" means the kernel that comes with the phone when you buy it. I just wanted to build it so I could modify it. I created a modified kernel that allows you to use the internal mic with headphones or for example when you connect the phone to your car stereo. The modified kernel is in the other thread.
Sent from my u8800 using XDA App

So with custom kernel you can achieve more functionality just like normal linux? Good. Would be awesome.

Help on Kernel 2.6.35.10 Compilation Error

I encounter the following error when compiling the kernel 2.6.35.10.
drivers/mmc/host/msm_sdcc.c: In function 'msmsdcc_request_end':
drivers/mmc/host/msm_sdcc.c:208: error: 'struct msmsdcc_host' has no member named 'req_tout_timer'
drivers/mmc/host/msm_sdcc.c: In function 'msmsdcc_dma_complete_tlet':
drivers/mmc/host/msm_sdcc.c:350: error: 'struct msmsdcc_host' has no member named 'req_tout_timer'
drivers/mmc/host/msm_sdcc.c: In function 'msmsdcc_start_command_deferred':
drivers/mmc/host/msm_sdcc.c:560: error: 'struct msmsdcc_host' has no member named 'req_tout_timer'
drivers/mmc/host/msm_sdcc.c:561: error: 'MSM_MMC_REQ_TIMEOUT' undeclared (first use in this function)
drivers/mmc/host/msm_sdcc.c:561: error: (Each undeclared identifier is reported only once
drivers/mmc/host/msm_sdcc.c:561: error: for each function it appears in.)
drivers/mmc/host/msm_sdcc.c: In function 'msmsdcc_probe':
drivers/mmc/host/msm_sdcc.c:1897: error: 'struct msmsdcc_host' has no member named 'req_tout_timer'
drivers/mmc/host/msm_sdcc.c:1948: error: 'struct msmsdcc_host' has no member named 'req_tout_timer'
drivers/mmc/host/msm_sdcc.c: In function 'msmsdcc_remove':
drivers/mmc/host/msm_sdcc.c:2010: error: 'struct msmsdcc_host' has no member named 'req_tout_timer'
make[3]: *** [drivers/mmc/host/msm_sdcc.o] Error 1
make[2]: *** [drivers/mmc/host] Error 2
make[1]: *** [drivers/mmc] Error 2
make: *** [drivers] Error 2
My compliation steps are as follows
1. download kernel 2.6.35.10 is from microslav_mm's git webpage:
$ cd /home/username/android/
$ git clone git://github.com/mmxtrem/android_kernel_swift.git
$ cd cm-kernel after a little rename
2. pull out the /proc/config.gz from my GT540 phone (SDSL 2.1) for kernel configuration.
$ adb pull /proc/config.gz .
$ cat config.gz | gunzip > .config
$ make ARCH=arm CROSS_COMPILE=$CCOMPILER oldconfig
3. configure the cross-compiler and trigger the compilation
$ export CCOMPILER=/home/username/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
$ make ARCH=arm CROSS_COMPILE=$CCOMPILER -j`grep 'processor' /proc/cpuinfo | wc -l`
How can I fix this compilation error? Any suggestions will be appreciated.
Shawn

csqjxiao said:
I encounter the following error when compiling the kernel 2.6.35.10.
drivers/mmc/host/msm_sdcc.c: In function 'msmsdcc_request_end':
drivers/mmc/host/msm_sdcc.c:208: error: 'struct msmsdcc_host' has no member named 'req_tout_timer'
drivers/mmc/host/msm_sdcc.c: In function 'msmsdcc_dma_complete_tlet':
drivers/mmc/host/msm_sdcc.c:350: error: 'struct msmsdcc_host' has no member named 'req_tout_timer'
drivers/mmc/host/msm_sdcc.c: In function 'msmsdcc_start_command_deferred':
drivers/mmc/host/msm_sdcc.c:560: error: 'struct msmsdcc_host' has no member named 'req_tout_timer'
drivers/mmc/host/msm_sdcc.c:561: error: 'MSM_MMC_REQ_TIMEOUT' undeclared (first use in this function)
drivers/mmc/host/msm_sdcc.c:561: error: (Each undeclared identifier is reported only once
drivers/mmc/host/msm_sdcc.c:561: error: for each function it appears in.)
drivers/mmc/host/msm_sdcc.c: In function 'msmsdcc_probe':
drivers/mmc/host/msm_sdcc.c:1897: error: 'struct msmsdcc_host' has no member named 'req_tout_timer'
drivers/mmc/host/msm_sdcc.c:1948: error: 'struct msmsdcc_host' has no member named 'req_tout_timer'
drivers/mmc/host/msm_sdcc.c: In function 'msmsdcc_remove':
drivers/mmc/host/msm_sdcc.c:2010: error: 'struct msmsdcc_host' has no member named 'req_tout_timer'
make[3]: *** [drivers/mmc/host/msm_sdcc.o] Error 1
make[2]: *** [drivers/mmc/host] Error 2
make[1]: *** [drivers/mmc] Error 2
make: *** [drivers] Error 2
My compliation steps are as follows
1. download kernel 2.6.35.10 is from microslav_mm's git webpage:
$ cd /home/username/android/
$ git clone git://github.com/mmxtrem/android_kernel_swift.git
$ cd cm-kernel after a little rename
2. pull out the /proc/config.gz from my GT540 phone (SDSL 2.1) for kernel configuration.
$ adb pull /proc/config.gz .
$ cat config.gz | gunzip > .config
$ make ARCH=arm CROSS_COMPILE=$CCOMPILER oldconfig
3. configure the cross-compiler and trigger the compilation
$ export CCOMPILER=/home/username/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
$ make ARCH=arm CROSS_COMPILE=$CCOMPILER -j`grep 'processor' /proc/cpuinfo | wc -l`
How can I fix this compilation error? Any suggestions will be appreciated.
Shawn
Click to expand...
Click to collapse
Same here. Any ideas?

Can you guys put the errors in a code tag? not so messy

These errors comes with arm-eabi-linaro-4.6.2
Compiling with arm-eabi-4.4.3 also print this error but compilation of kernel continues to the end. But. Where can I find kernel image? I suppose it should be in arch/arm/boot/ but it isn't. Or where I have to looking for the Image file?
Code:
[email protected] ~/android/kernel/$ ls -l arch/arm/boot/
razem 16
drwxr-xr-x 2 smogf smogf 4096 04-01 23:27 bootp
drwxr-xr-x 2 smogf smogf 4096 04-01 23:27 compressed
-rw-r--r-- 1 smogf smogf 1274 04-01 23:27 install.sh
-rw-r--r-- 1 smogf smogf 3118 04-01 23:27 Makefile
[email protected] ~/android/kernel/mmxtrem-android_kernel_swift-6010f54
I've tried once again with make zImage and compilation fails with the same error as before. I have no idea. Any help will be useful.

smogf said:
These errors comes with arm-eabi-linaro-4.6.2
Compiling with arm-eabi-4.4.3 also print this error but compilation of kernel continues to the end. But. Where can I find kernel image? I suppose it should be in arch/arm/boot/ but it isn't. Or where I have to looking for the Image file?
Code:
[email protected] ~/android/kernel/$ ls -l arch/arm/boot/
razem 16
drwxr-xr-x 2 smogf smogf 4096 04-01 23:27 bootp
drwxr-xr-x 2 smogf smogf 4096 04-01 23:27 compressed
-rw-r--r-- 1 smogf smogf 1274 04-01 23:27 install.sh
-rw-r--r-- 1 smogf smogf 3118 04-01 23:27 Makefile
[email protected] ~/android/kernel/mmxtrem-android_kernel_swift-6010f54
I've tried once again with make zImage and compilation fails with the same error as before. I have no idea. Any help will be useful.
Click to expand...
Click to collapse
It seems bootp, Compressed, install.sh and Makefile is in the folder your looking at...
Otherwise I think the image name starts with initrd
Sent using the LG GT540 Polishblood PreRC CM9 4.0 using XDA Premium

Chromium_org gives error all the time

Hello, I'm trying to compile OmniRom but after last repo sync I'm getting this error:
Code:
In file included from external/chromium_org/content/common/android/hash_set.cc:5:0:
/home/lozohcum/OmniRom/out/target/product/jlo/obj/GYP/shared_intermediates/content/jni/HashSet_jni.h:24:20: error: expected initializer before '<' token
/home/lozohcum/OmniRom/out/target/product/jlo/obj/GYP/shared_intermediates/content/jni/HashSet_jni.h:26:17: error: expected initializer before '<' token
/home/lozohcum/OmniRom/out/target/product/jlo/obj/GYP/shared_intermediates/content/jni/HashSet_jni.h:29:22: error: expected '{' before '<' token
/home/lozohcum/OmniRom/out/target/product/jlo/obj/GYP/shared_intermediates/content/jni/HashSet_jni.h:29:22: error: expected unqualified-id before '<' token
external/chromium_org/content/common/android/hash_set.cc:30:1: error: expected '}' at end of input
cc1plus: all warnings being treated as errors
I have tried with chromium_org from CM11 (which compile without any errors) and the same thing appear.
cc1plus: all warnings being treated as errors
Click to expand...
Click to collapse
So I suppose adding a flag somewhere will fix that error but I'm not sure which flag and where.
Do you have any clue how to solve it?

Android Studio UI Issue

Hi all,
I am having following issue while building my android app... Please help how to solve it
Error:Execution failed for task ':UiTestrocessDebugResources'.
> com.android.ide.common.internal.LoggedErrorException: Failed to run command:
/opt/android-studio/sdk/build-tools/android-4.4.2/aapt package -f --no-crunch -I /opt/android-studio/sdk/platforms/android-19/android.jar -M /root/AndroidStudioProjects/UITest/UiTest/build/manifests/debug/AndroidManifest.xml -S /root/AndroidStudioProjects/UITest/UiTest/build/res/all/debug -A /root/AndroidStudioProjects/UITest/UiTest/build/assets/debug -m -J /root/AndroidStudioProjects/UITest/UiTest/build/source/r/debug -F /root/AndroidStudioProjects/UITest/UiTest/build/libs/UiTest-debug.ap_ --debug-mode --custom-package np.info.niroj.uitest.uitest
Error Code:
1
Output:
W/ResourceType( 2822): ResXMLTree_node header size (nil) is too small.
W/ResourceType( 2822): ResXMLTree_node header size (nil) is too small.
/root/AndroidStudioProjects/UITest/UiTest/build/res/all/debug/menu/global.xml:3: error: Error parsing XML: unbound prefix
/root/AndroidStudioProjects/UITest/UiTest/build/res/all/debug/menu/main.xml:5: error: No resource identifier found for attribute 'showAsAction' in package 'np.info.niroj.uitest.uitest'
/root/AndroidStudioProjects/UITest/UiTest/build/res/all/debug/menu/main.xml:8: error: No resource identifier found for attribute 'showAsAction' in package 'np.info.niroj.uitest.uitest'
Thank you

Anyone here good with C++ or compiling a .cpp file? I need help

I found a possible root tool, but the file is a .cpp and I am having an extremely difficult time compiling this. Please respond if you are able to help!

I could help with this. I'm running W7 and would probably be using Visual Studio to compile the executable. Also, I have a Sprint G5, and work in a service and repair center, so if things went south, I would be able to order myself a replacement should it get bricked.
How are you trying to compile the .cpp file?

I also am setup to compile cpp. What kind of trouble are you having compiling?

solitarywarrior1 said:
I also am setup to compile cpp. What kind of trouble are you having compiling?
Click to expand...
Click to collapse
f_scott_scrambled_eggs said:
I could help with this. I'm running W7 and would probably be using Visual Studio to compile the executable. Also, I have a Sprint G5, and work in a service and repair center, so if things went south, I would be able to order myself a replacement should it get bricked.
How are you trying to compile the .cpp file?
Click to expand...
Click to collapse
Here is the file I have been trying to compile: https://github.com/offensive-security/exploit-database/blob/master/platforms/android/local/39340.cpp
PLEASE test this out and tell me if you get anything!

Looks like it needs to be compiled on Android or Linux for this to work. I just tried to compile it using the IDE I have on my phone and it looks like there's a bug in the code with a char pointer being cast as an integer. Is that the issue you've been having with compiling too?
I could probably correct it, but I want to make sure that you're not having a different problem.

solitarywarrior1 said:
Looks like it needs to be compiled on Android or Linux for this to work. I just tried to compile it using the IDE I have on my phone and it looks like there's a bug in the code with a char pointer being cast as an integer. Is that the issue you've been having with compiling too?
I could probably correct it, but I want to make sure that you're not having a different problem.
Click to expand...
Click to collapse
Same problem I'm having...

Honestly Annoying said:
Same problem I'm having...
Click to expand...
Click to collapse
Hmm, what compiler are you using and did you write this code yourself or get it from somewhere?
Do you know if it's the location of the char the pointer points to that we need to cast as an int, or if we're trying to cast the char itself as one?

solitarywarrior1 said:
Hmm, what compiler are you using and did you write this code yourself or get it from somewhere?
Do you know if it's the location of the char the pointer points to that we need to cast as an int, or if we're trying to cast the char itself as one?
Click to expand...
Click to collapse
I did not write this code, I found it while browsing through Android exploits. This particular one was never assigned an official CVE so it might be unpatched.
And I have no idea what that second question means. This is my first time using cpp

Honestly Annoying said:
I did not write this code, I found it while browsing through Android exploits. This particular one was never assigned an official CVE so it might be unpatched.
And I have no idea what that second question means. This is my first time using cpp
Click to expand...
Click to collapse
A CHAR POINTER is a unit of data in C that stores the MEMORY ADDRESS of a variable of type CHARACTER
The code attempts to CAST (or pass the data into a function as if it were a different datatype) the CHAR POINTER as an INTEGER
Basically, I'm wondering if we want the address of the character that the pointer points to passed into the function as an integer, or the character itself.
I hope this explanation makes sense!

We're already over my head with this, but I've still got a disposable G5 to try it out on once we get it compiled, if needed.
What will this final output of this be? Is it an APK, or something that's run in the command line? Seems like it will allow us to get elevation in the shell so we can execute root commands, provided that the autorotate vulnerability is present in the ZV3/4 firmware.

solitarywarrior1 said:
A CHAR POINTER is a unit of data in C that stores the MEMORY ADDRESS of a variable of type CHARACTER
The code attempts to CAST (or pass the data into a function as if it were a different datatype) the CHAR POINTER as an INTEGER
Basically, I'm wondering if we want the address of the character that the pointer points to passed into the function as an integer, or the character itself.
I hope this explanation makes sense!
Click to expand...
Click to collapse
Thanks for that explanation, but I'm sorry I have no idea which one of those it is. Have you tried compiling it yet?

I'll have to edit the code before I can compile it (the compiler is throwing an error because the code is trying to do something either impossible or ambiguous) that's why I was asking my question above. I'll try a couple of things and report back later.

solitarywarrior1 said:
I'll have to edit the code before I can compile it (the compiler is throwing an error because the code is trying to do something either impossible or ambiguous) that's why I was asking my question above. I'll try a couple of things and report back later.
Click to expand...
Click to collapse
Thank you so much, this is all extremely helpful! Please keep us/me updated on what you are trying to do

solitarywarrior1 said:
Looks like it needs to be compiled on Android or Linux for this to work. I just tried to compile it using the IDE I have on my phone and it looks like there's a bug in the code with a char pointer being cast as an integer. Is that the issue you've been having with compiling too?
I could probably correct it, but I want to make sure that you're not having a different problem.
Click to expand...
Click to collapse
https://github.com/solitarywarrior1/G5-Root/blob/master/exploit.cpp
I've fixed the code so that it compiles.
All I did was replace a couple of casts to INT with the atoi() function that converts a character to an integer.
EDIT: We might be able to compile the code as originally posted if we compile on a non 64-bit device, as that error message is affected by the size of the memory address: 4 bytes for a 32-bit machine, 8 bytes for a 64-bit one.

solitarywarrior1 said:
https://github.com/solitarywarrior1/G5-Root/blob/master/exploit.cpp
I've fixed the code so that it compiles.
All I did was replace a couple of casts to INT with the atoi() function that converts a character to an integer.
EDIT: We might be able to compile the code as originally posted if we compile on a non 64-bit device, as that error message is affected by the size of the memory address: 4 bytes for a 32-bit machine, 8 bytes for a 64-bit one.
Click to expand...
Click to collapse
I'm still getting the same errors... I tried compiling on Ubuntu 32-bit and it gave me these errors (there are a lot)
exploit.cpp:57:10: error: ‘__le32’ does not name a type
__le32 s_clusters_per_group;
^
exploit.cpp:58:10: error: ‘__le32’ does not name a type
__le32 s_inodes_per_group;
^
exploit.cpp:59:10: error: ‘__le32’ does not name a type
__le32 s_mtime;
^
exploit.cpp:60:10: error: ‘__le32’ does not name a type
/*30*/ __le32 s_wtime;
^
exploit.cpp:61:10: error: ‘__le16’ does not name a type
__le16 s_mnt_count;
^
exploit.cpp:62:10: error: ‘__le16’ does not name a type
__le16 s_max_mnt_count;
^
exploit.cpp:63:10: error: ‘__le16’ does not name a type
__le16 s_magic;
^
exploit.cpp:64:10: error: ‘__le16’ does not name a type
__le16 s_state;
^
exploit.cpp:65:10: error: ‘__le16’ does not name a type
__le16 s_errors;
^
exploit.cpp:66:10: error: ‘__le16’ does not name a type
__le16 s_minor_rev_level;
^
exploit.cpp:67:10: error: ‘__le32’ does not name a type
/*40*/ __le32 s_lastcheck;
^
exploit.cpp:68:10: error: ‘__le32’ does not name a type
__le32 s_checkinterval;
^
exploit.cpp:69:10: error: ‘__le32’ does not name a type
__le32 s_creator_os;
^
exploit.cpp:70:10: error: ‘__le32’ does not name a type
__le32 s_rev_level;
^
exploit.cpp:71:10: error: ‘__le16’ does not name a type
/*50*/ __le16 s_def_resuid;
^
exploit.cpp:72:10: error: ‘__le16’ does not name a type
__le16 s_def_resgid;
^
exploit.cpp:73:10: error: ‘__le32’ does not name a type
__le32 s_first_ino;
^
exploit.cpp:74:10: error: ‘__le16’ does not name a type
__le16 s_inode_size;
^
exploit.cpp:75:10: error: ‘__le16’ does not name a type
__le16 s_block_group_nr;
^
exploit.cpp:76:10: error: ‘__le32’ does not name a type
__le32 s_feature_compat;
^
exploit.cpp:77:10: error: ‘__le32’ does not name a type
/*60*/ __le32 s_feature_incompat;
^
exploit.cpp:78:10: error: ‘__le32’ does not name a type
__le32 s_feature_ro_compat;
^
exploit.cpp:79:10: error: ‘__u8’ does not name a type
/*68*/ __u8 s_uuid[16];
^
exploit.cpp:82:10: error: ‘__le32’ does not name a type
/*C8*/ __le32 s_algorithm_usage_bitmap;
^
exploit.cpp:83:10: error: ‘__u8’ does not name a type
__u8 s_prealloc_blocks;
^
exploit.cpp:84:10: error: ‘__u8’ does not name a type
__u8 s_prealloc_dir_blocks;
^
exploit.cpp:85:10: error: ‘__le16’ does not name a type
__le16 s_reserved_gdt_blocks;
^
exploit.cpp:86:10: error: ‘__u8’ does not name a type
/*D0*/ __u8 s_journal_uuid[16];
^
exploit.cpp:87:10: error: ‘__le32’ does not name a type
/*E0*/ __le32 s_journal_inum;
^
exploit.cpp:88:10: error: ‘__le32’ does not name a type
__le32 s_journal_dev;
^
exploit.cpp:89:10: error: ‘__le32’ does not name a type
__le32 s_last_orphan;
^
exploit.cpp:90:10: error: ‘__le32’ does not name a type
__le32 s_hash_seed[4];
^
exploit.cpp:91:10: error: ‘__u8’ does not name a type
__u8 s_def_hash_version;
^
exploit.cpp:92:10: error: ‘__u8’ does not name a type
__u8 s_jnl_backup_type;
^
exploit.cpp:93:10: error: ‘__le16’ does not name a type
__le16 s_desc_size;
^
exploit.cpp:94:10: error: ‘__le32’ does not name a type
/*100*/ __le32 s_default_mount_opts;
^
exploit.cpp:95:10: error: ‘__le32’ does not name a type
__le32 s_first_meta_bg;
^
exploit.cpp:96:10: error: ‘__le32’ does not name a type
__le32 s_mkfs_time;
^
exploit.cpp:97:10: error: ‘__le32’ does not name a type
__le32 s_jnl_blocks[17];
^
exploit.cpp:98:10: error: ‘__le32’ does not name a type
/*150*/ __le32 s_blocks_count_hi;
^
exploit.cpp:99:10: error: ‘__le32’ does not name a type
__le32 s_r_blocks_count_hi;
^
exploit.cpp:100:10: error: ‘__le32’ does not name a type
__le32 s_free_blocks_count_hi;
^
exploit.cpp:101:10: error: ‘__le16’ does not name a type
__le16 s_min_extra_isize;
^
exploit.cpp:102:10: error: ‘__le16’ does not name a type
__le16 s_want_extra_isize;
^
exploit.cpp:103:10: error: ‘__le32’ does not name a type
__le32 s_flags;
^
exploit.cpp:104:10: error: ‘__le16’ does not name a type
__le16 s_raid_stride;
^
exploit.cpp:105:10: error: ‘__le16’ does not name a type
__le16 s_mmp_update_interval;
^
exploit.cpp:106:10: error: ‘__le64’ does not name a type
__le64 s_mmp_block;
^
exploit.cpp:107:10: error: ‘__le32’ does not name a type
__le32 s_raid_stripe_width;
^
exploit.cpp:108:10: error: ‘__u8’ does not name a type
__u8 s_log_groups_per_flex;
^
exploit.cpp:109:10: error: ‘__u8’ does not name a type
__u8 s_checksum_type;
^
exploit.cpp:110:10: error: ‘__u8’ does not name a type
__u8 s_encryption_level;
^
exploit.cpp:111:10: error: ‘__u8’ does not name a type
__u8 s_reserved_pad;
^
exploit.cpp:112:10: error: ‘__le64’ does not name a type
__le64 s_kbytes_written;
^
exploit.cpp:113:10: error: ‘__le32’ does not name a type
__le32 s_snapshot_inum;
^
exploit.cpp:114:10: error: ‘__le32’ does not name a type
__le32 s_snapshot_id;
^
exploit.cpp:115:10: error: ‘__le64’ does not name a type
__le64 s_snapshot_r_blocks_count;
^
exploit.cpp:116:10: error: ‘__le32’ does not name a type
__le32 s_snapshot_list;
^
exploit.cpp:118:10: error: ‘__le32’ does not name a type
__le32 s_error_count;
^
exploit.cpp:119:10: error: ‘__le32’ does not name a type
__le32 s_first_error_time;
^
exploit.cpp:120:10: error: ‘__le32’ does not name a type
__le32 s_first_error_ino;
^
exploit.cpp:121:10: error: ‘__le64’ does not name a type
__le64 s_first_error_block;
^
exploit.cpp:122:10: error: ‘__u8’ does not name a type
__u8 s_first_error_func[32];
^
exploit.cpp:123:10: error: ‘__le32’ does not name a type
__le32 s_first_error_line;
^
exploit.cpp:124:10: error: ‘__le32’ does not name a type
__le32 s_last_error_time;
^
exploit.cpp:125:10: error: ‘__le32’ does not name a type
__le32 s_last_error_ino;
^
exploit.cpp:126:10: error: ‘__le32’ does not name a type
__le32 s_last_error_line;
^
exploit.cpp:127:10: error: ‘__le64’ does not name a type
__le64 s_last_error_block;
^
exploit.cpp:128:10: error: ‘__u8’ does not name a type
__u8 s_last_error_func[32];
^
exploit.cpp:130:10: error: ‘__u8’ does not name a type
__u8 s_mount_opts[64];
^
exploit.cpp:131:10: error: ‘__le32’ does not name a type
__le32 s_usr_quota_inum;
^
exploit.cpp:132:10: error: ‘__le32’ does not name a type
__le32 s_grp_quota_inum;
^
exploit.cpp:133:10: error: ‘__le32’ does not name a type
__le32 s_overhead_clusters;
^
exploit.cpp:134:10: error: ‘__le32’ does not name a type
__le32 s_backup_bgs[2];
^
exploit.cpp:135:10: error: ‘__u8’ does not name a type
__u8 s_encrypt_algos[4];
^
exploit.cpp:136:10: error: ‘__u8’ does not name a type
__u8 s_encrypt_pw_salt[16];
^
exploit.cpp:137:10: error: ‘__le32’ does not name a type
__le32 s_lpf_ino;
^
exploit.cpp:138:10: error: ‘__le32’ does not name a type
__le32 s_prj_quota_inum;
^
exploit.cpp:139:10: error: ‘__le32’ does not name a type
__le32 s_checksum_seed;
^
exploit.cpp:140:10: error: ‘__le32’ does not name a type
__le32 s_reserved[98];
^
exploit.cpp:141:9: error: ‘__le32’ does not name a type
__le32 s_checksum;
^
exploit.cpp:146:10: error: ‘__le32’ does not name a type
__le32 bg_block_bitmap_lo;
^
exploit.cpp:147:10: error: ‘__le32’ does not name a type
__le32 bg_inode_bitmap_lo;
^
exploit.cpp:148:10: error: ‘__le32’ does not name a type
__le32 bg_inode_table_lo;
^
exploit.cpp:149:10: error: ‘__le16’ does not name a type
__le16 bg_free_blocks_count_lo;
^
exploit.cpp:150:10: error: ‘__le16’ does not name a type
__le16 bg_free_inodes_count_lo;
^
exploit.cpp:151:10: error: ‘__le16’ does not name a type
__le16 bg_used_dirs_count_lo;
^
exploit.cpp:152:10: error: ‘__le16’ does not name a type
__le16 bg_flags;
^
exploit.cpp:153:10: error: ‘__le32’ does not name a type
__le32 bg_exclude_bitmap_lo;
^
exploit.cpp:154:10: error: ‘__le16’ does not name a type
__le16 bg_block_bitmap_csum_lo;
^
exploit.cpp:155:10: error: ‘__le16’ does not name a type
__le16 bg_inode_bitmap_csum_lo;
^
exploit.cpp:156:10: error: ‘__le16’ does not name a type
__le16 bg_itable_unused_lo;
^
exploit.cpp:157:10: error: ‘__le16’ does not name a type
__le16 bg_checksum;
^
exploit.cpp:158:10: error: ‘__le32’ does not name a type
__le32 bg_block_bitmap_hi;
^
exploit.cpp:159:10: error: ‘__le32’ does not name a type
__le32 bg_inode_bitmap_hi;
^
exploit.cpp:160:10: error: ‘__le32’ does not name a type
__le32 bg_inode_table_hi;
^
exploit.cpp:161:10: error: ‘__le16’ does not name a type
__le16 bg_free_blocks_count_hi;
^
exploit.cpp:162:10: error: ‘__le16’ does not name a type
__le16 bg_free_inodes_count_hi;
^
exploit.cpp:163:10: error: ‘__le16’ does not name a type
__le16 bg_used_dirs_count_hi;
^
exploit.cpp:164:10: error: ‘__le16’ does not name a type
__le16 bg_itable_unused_hi;
^
exploit.cpp:165:10: error: ‘__le32’ does not name a type
__le32 bg_exclude_bitmap_hi;
^
exploit.cpp:166:10: error: ‘__le16’ does not name a type
__le16 bg_block_bitmap_csum_hi;
^
exploit.cpp:167:10: error: ‘__le16’ does not name a type
__le16 bg_inode_bitmap_csum_hi;
^
exploit.cpp:168:10: error: ‘__u32’ does not name a type
__u32 bg_reserved;
^
exploit.cpp:172:10: error: ‘__le16’ does not name a type
__le16 i_mode;
^
exploit.cpp:173:10: error: ‘__le16’ does not name a type
__le16 i_uid;
^
exploit.cpp:174:10: error: ‘__le32’ does not name a type
__le32 i_size_lo;
^
exploit.cpp:175:10: error: ‘__le32’ does not name a type
__le32 i_atime;
^
exploit.cpp:176:10: error: ‘__le32’ does not name a type
__le32 i_ctime;
^
exploit.cpp:177:10: error: ‘__le32’ does not name a type
__le32 i_mtime;
^
exploit.cpp:178:10: error: ‘__le32’ does not name a type
__le32 i_dtime;
^
exploit.cpp:179:10: error: ‘__le16’ does not name a type
__le16 i_gid;
^
exploit.cpp:180:10: error: ‘__le16’ does not name a type
__le16 i_links_count;
^
exploit.cpp:181:10: error: ‘__le32’ does not name a type
__le32 i_blocks_lo;
^
exploit.cpp:182:10: error: ‘__le32’ does not name a type
__le32 i_flags;
^
exploit.cpp:185:26: error: ‘__le32’ does not name a type
__le32 l_i_version;
^
exploit.cpp:188:26: error: ‘__u32’ does not name a type
__u32 h_i_translator;
^
exploit.cpp:191:26: error: ‘__u32’ does not name a type
__u32 m_i_reserved1;
^
exploit.cpp:194:10: error: ‘__le32’ does not name a type
__le32 i_block[15];
^
exploit.cpp:195:10: error: ‘__le32’ does not name a type
__le32 i_generation;
^
exploit.cpp:196:10: error: ‘__le32’ does not name a type
__le32 i_file_acl_lo;
^
exploit.cpp:197:10: error: ‘__le32’ does not name a type
__le32 i_size_high;
^
exploit.cpp:198:10: error: ‘__le32’ does not name a type
__le32 i_obso_faddr;
^
exploit.cpp:201:26: error: ‘__le16’ does not name a type
__le16 l_i_blocks_high;
^
exploit.cpp:202:26: error: ‘__le16’ does not name a type
__le16 l_i_file_acl_high;
^
exploit.cpp:203:26: error: ‘__le16’ does not name a type
__le16 l_i_uid_high;
^
exploit.cpp:204:26: error: ‘__le16’ does not name a type
__le16 l_i_gid_high;
^
exploit.cpp:205:26: error: ‘__le16’ does not name a type
__le16 l_i_checksum_lo;
^
exploit.cpp:206:26: error: ‘__le16’ does not name a type
__le16 l_i_reserved;
^
exploit.cpp:209:26: error: ‘__le16’ does not name a type
__le16 h_i_reserved1;
^
exploit.cpp:210:26: error: ‘__u16’ does not name a type
__u16 h_i_mode_high;
^
exploit.cpp:211:26: error: ‘__u16’ does not name a type
__u16 h_i_uid_high;
^
exploit.cpp:212:26: error: ‘__u16’ does not name a type
__u16 h_i_gid_high;
^
exploit.cpp:213:26: error: ‘__u32’ does not name a type
__u32 h_i_author;
^
exploit.cpp:216:26: error: ‘__le16’ does not name a type
__le16 h_i_reserved1;
^
exploit.cpp:217:26: error: ‘__le16’ does not name a type
__le16 m_i_file_acl_high;
^
exploit.cpp:218:26: error: ‘__u32’ does not name a type
__u32 m_i_reserved2[2];
^
exploit.cpp:221:10: error: ‘__le16’ does not name a type
__le16 i_extra_isize;
^
exploit.cpp:222:10: error: ‘__le16’ does not name a type
__le16 i_checksum_hi;
^
exploit.cpp:223:10: error: ‘__le32’ does not name a type
__le32 i_ctime_extra;
^
exploit.cpp:224:10: error: ‘__le32’ does not name a type
__le32 i_mtime_extra;
^
exploit.cpp:225:10: error: ‘__le32’ does not name a type
__le32 i_atime_extra;
^
exploit.cpp:226:10: error: ‘__le32’ does not name a type
__le32 i_crtime;
^
exploit.cpp:227:10: error: ‘__le32’ does not name a type
__le32 i_crtime_extra;
^
exploit.cpp:228:10: error: ‘__le32’ does not name a type
__le32 i_version_hi;
^
exploit.cpp: In function ‘void get_system_dev(char*, int)’:
exploit.cpp:246:33: error: ‘memset’ was not declared in this scope
memset(buff, 0, sizeof(buff));
^
exploit.cpp:252:49: error: ‘strstr’ was not declared in this scope
int sres = atoi(strstr(buff, " /system "));
^
exploit.cpp:259:51: error: ‘strncpy’ was not declared in this scope
strncpy(link, &buff[pos], tmppos - pos);
^
exploit.cpp: In function ‘void second_step()’:
exploit.cpp:302:57: warning: format ‘%llu’ expects argument of type ‘long long unsigned int’, but argument 2 has type ‘__ino_t {aka long unsigned int}’ [-Wformat=]
printf("[+] Looking for inode no.: %llu\n", s.st_ino);
^
exploit.cpp:319:40: error: ‘struct ext4_super_block’ has no member named ‘s_log_block_size’
int block_size = 1024 << super.s_log_block_size;
^
exploit.cpp:320:37: error: ‘struct ext4_super_block’ has no member named ‘s_inodes_per_group’
int bg = (inodeno-1) /super.s_inodes_per_group;
^
exploit.cpp:322:44: error: ‘struct ext4_super_block’ has no member named ‘s_desc_size’
lseek(fd, block_size + bg * (super.s_desc_size ? super.s_desc_size : sizeof(struct ext4_group_desc) ), SEEK_SET);
^
exploit.cpp:322:64: error: ‘struct ext4_super_block’ has no member named ‘s_desc_size’
lseek(fd, block_size + bg * (super.s_desc_size ? super.s_desc_size : sizeof(struct ext4_group_desc) ), SEEK_SET);
^
exploit.cpp:326:50: error: ‘struct ext4_super_block’ has no member named ‘s_inodes_per_group’
unsigned int index = (inodeno-1) % super.s_inodes_per_group;
^
exploit.cpp:327:43: error: ‘struct ext4_super_block’ has no member named ‘s_inode_size’
unsigned int off = index * super.s_inode_size;
^
exploit.cpp:328:64: error: ‘struct ext4_group_desc’ has no member named ‘bg_inode_table_lo’
unsigned long total_offset = block_size + (group_descr.bg_inode_table_lo-1) * block_size + off;
^
exploit.cpp:333:18: error: ‘struct ext4_inode’ has no member named ‘i_size_lo’
if(inode.i_size_lo == s.st_size) {
^
exploit.cpp:334:13: error: ‘__le16’ was not declared in this scope
__le16 mode = 0;
^
exploit.cpp:334:20: error: expected ‘;’ before ‘mode’
__le16 mode = 0;
^
exploit.cpp:338:19: error: ‘struct ext4_inode’ has no member named ‘i_mode’
inode.i_mode = inode.i_mode | 0x800;
^
exploit.cpp:338:34: error: ‘struct ext4_inode’ has no member named ‘i_mode’
inode.i_mode = inode.i_mode | 0x800;
^
exploit.cpp:340:41: error: ‘struct ext4_inode’ has no member named ‘i_mode’
int modesize = sizeof(inode.i_mode);
^
exploit.cpp:341:39: error: ‘struct ext4_inode’ has no member named ‘i_mode’
int wr = write(fd, &inode.i_mode, modesize);
^
exploit.cpp: In function ‘bool isSensord(char*)’:
exploit.cpp:392:46: error: ‘strstr’ was not declared in this scope
if(strstr(buff, "/system/bin/sensord") != NULL)
^
exploit.cpp: In function ‘int main(int, char**)’:
exploit.cpp:444:30: error: ‘strstr’ was not declared in this scope
if( strstr( argv[1], "1" ) != NULL) {
^

You'll need to compile it on Android, methinks.
All of those elements that are throwing errors are android specific, I'll bet.
I use c4droid to compile on android, it's excellent and had git support.

solitarywarrior1 said:
You'll need to compile it on Android, methinks.
Click to expand...
Click to collapse
Ah OK, how do I do this?
EDIT: Just saw your edit, I'm trying to compile now

solitarywarrior1 said:
You'll need to compile it on Android, methinks.
All of those elements that are throwing errors are android specific, I'll bet.
I use c4droid to compile on android, it's excellent and had git support.
Click to expand...
Click to collapse
OK, so C4droid gives me this error: "/data/user/0/com.n0n3m4.droidc/files/temp.c:48: error ',' expected (got "s_inodes_count")". How can I fix this?
And here is what I compiled with CppDroid https://drive.google.com/open?id=0B2OlLU7vg4YzRHdwM0JoLWxla00. However, when I run the a.out file it gives me these errors
./a.out[1]: ??????: not found
./a.out[2]:
: not found
./a.out[3]: syntax error: '??
It also gives me some warnings while compiling about "implicit conversion changes signedness: 'int' to 'size_t' (aka 'unsigned int)" and some "macro is not used" errors.
Can you help me fix these?

Huh, it compiled perfectly using c4droid on my phone. I DID install the gcc plugin, did you as well?

solitarywarrior1 said:
Huh, it compiled perfectly using c4droid on my phone. I DID install the gcc plugin, did you as well?
Click to expand...
Click to collapse
Yes, but it was giving me errors... can you send me the file that you compiled? It would be much appreciated!