General :: Build Kernel MT6577 - Can't Boot After Build
Feb 21, 2013
I have a phone with a MT6577. The vendor (Wiko) published the kernel source code. So, i'm trying to build it. I can get the zImage. I converted it to boot.img but i can't boot with it on my phone.build a good zImage? (if you want to try) : URL...
cp mediatek-configs .config
TARGET_PRODUCT=s9081 MTK_ROOT_CUSTOM=../mediatek/custom make
# sudo mtk-tools/repack-MT65xx.pl -boot zImage boot.img-ramdisk boot.img
MTK-Tools by Bruno MartinsMT65xx repack script (last update: 27-01-2013)
Repacking boot image...
Ramdisk size: 2046 blocs
Repacked boot image into 'boot.img'.
Here are the Warnings I got when compiling
mediatek/platform/mt6577/kernel/drivers/video/tvc_drv.c:61:5: warning: "FIXED_WVGA_PARAMS" is not defined
net/ipv4/tcp.c: In function 'tcp_nuke_addr':
include/net/ipv6.h:338: warning: 'in6' may be used uninitialized in this function
net/ipv4/tcp.c:3367: note: 'in6' was declared here
In file included from net/ipv4/netfilter/ipt_LOG.c:27:
include/net/netfilter/xt_log.h: In function 'sb_close':
I've compiled a kernel for my device most of think working exepted usb host , sdcard mount , and camera (sourcery if for my device too , nothing ported).its wiko cink peax 2 mtk 6589 device and the main camera name is ov8825-truly-MM a 8mpx camera launching but not showing the good color its dark , and in full daylight its showing in green colors.
I am looking to compile a new kernel for this device. I have pulled off the boot.img file from /dev/block/nandc and used split_bootimg.pl to pull apart the kernel and the boot ramdisk. I have used extract-ikconfig to get the kernel config and built my new 3.4 kernel (with modules). So far so good...
I have tried to build the new boot.img file with no avail. My concern is with the original kernel as the new one should be build the same (I think). It looks like it is not compressed as I run the command
So it is not a Linux kernel ARM boot executable zImage
Is this correct? Can Android boot with this or is the split_bootimg.pl tool not creating the file correctly (it does pull the ramdisk as I have uncompressed it fine! and the file does contain the kernel config)
Ok So assuming I can create a proper boot.img with my built zImage and the old ramdisk, what do I need to do with the modules? Do I update the boot.img on the tablet and copy the modules over to the existing /system/lib/modules? (this appears to not work)
I downloaded the Android 2.2 source code and try to build it. When I executed the make command, I got an error here like this build/core/java.mk:20: *** frameworks/ex/common: Invalid LOCAL_SDK_VERSION '8' Choices are: current 4 5 6 7. Stop. Then I changed the frameworks/ex/common/Android.mk to LOCAL_SDK_VERSION = 8 from LOCAL_SDK_VERSION = 7. Next place, build/core/java.mk:20: *** external/jsr305: Invalid LOCAL_SDK_VERSION '8' Choices are: current 4 5 6 7. Stop. I changed the external/jsr305/Android.mk to LOCAL_SDK_VERSION = 8 from LOCAL_SDK_VERSION = 7
Last one, build/core/java.mk:20: *** external/guava: Invalid LOCAL_SDK_VERSION '8' Choices are: current 4 5 6 7. Stop. I changed the external/guava/Android.mk to LOCAL_SDK_VERSION = 8 from LOCAL_SDK_VERSION = 7 By these changes the code started the compilation.
1. Why the error occured? 2. Changes which I did is correct or not?
Everyone probably has the exact same Build Number, but than again, maybe a couple don't. So after a search, I was not able to find a thread like this, so here it is. I just received my X10 yesterday and per Sony Support, my X10 has the current OS. So here is my info:
I'm in the process of learning to build android from source. I've got my AOKP rom booting and am working on adding superuser to it, and am running into troubles. After much googling here is what I've done
Cloned Superuser source code
Code: git clone git://github.com/ChainsDD/Superuser.git packages/apps/Superuser Copied the su binary from my current rom (/system/xbin/su) to my device tree
# copy su binary PRODUCT_COPY_FILES += device/lge/E973/su:system/xbin/su
Everything built fine and Superuser is in my app drawer when rom boots. If i try to open Superuser it force closes. Root checker shows that i am rooted, and typing 'su' in terminal emulator gets root access. Neither will give me a dialog asking to deny or grant.
If i install SuperSuperuser from the market, it will present all the normal dialogs and everything seems as it should.
Here is a logcat of the failed attempt to open superuser
I have a rooted Verizon S4 running 4.3, build number JSS15J.I545VRUEMK2. This is a phone provided to me by work, so I have no control over the billing/ tethering abilities..I have searched to no avail on how to create a hotspot with this 4.3 build.
My company has recently received some new android hardware and has requested that I create a custom operating system for the device. The manufacturer has agreed to provide us with the existing android source, but I have a few questions to get started:
On the following link: [URL] .......
It states that I need to add lines similar to the below to my "51-android.rules" file:"
How do I determine the correct information to use for this process? Should I collect this information with the device connected to a windows PC?
Once connected, I would like to scrap their existing operating system and begin from AOSP source, what information from their original source should I retain (Kernel, bootloader, etc), and what information would I be required to remove to bring in AOSP?
But most seem to be specifying nexus devices, or devices which already have a strong developer backing, neither of which apply to this hardware.
I am writing an app and for one of the features I need the firmware build number.
I know I can get the firmware version(like 4.1.1) with android.os.build but I need the build number of a rom(like "Rom version 1.0") thats stored in build.prop. I know I can parse the whole build.prop file and extract the 1 string of information but is there another way to get is faster and that it doesnt require root to use?
I was looking through my system files with root explorer and I notice in the build.prop file, I had the information for the Xperia Arc instead of the Xperia Arc S. I changed some of the info to the Arc S, like LT18i instead of LT15i. But I'm not sure if I changed everything correctly and can upload the build.prop file for the Arc S.
I have a LG P350 which development has stopped but i want to keep it updated, i have my computer ready for building, also i have kernel sources, Cyanogenmod 11 and 10.1 sources too, (I don't know exactly if 10.1 sources could work) and i know that i need to apply patches to work on Armv6 but i don't know how to apply them to the source code, also i don't know if i would just need the pure source code to build or i need to do more modifications to it and finally, i don't know if the rom would work with 2.36 kernel which it's the most stable one for this device, i'm very new in this but i know that i can keep update my little phone,
what is the most simple way to get the latest version of TextSecure installed on my Android Phone?
My solution was creating something using the sourcecode found here: [URL] But the question is, how can I get it working. I've tried multiple things, but it seems like it isn't as easy as I thought. Currently I am on Windows 8. My phone is an Xperia S without GAPPS flashed, so no Play Store. Only F-Droid with FOSS.
I'm trying to build CWM for the HP Slate 7 Plus, but both touch and non-touch builds coming from the CWM Builder and manually built builds give a black screen with a few white lines when booted into recovery. The stock recovery.img I provided to the builder is valid because people were able to reflash the same recovery.img via Flashify with no issues, which is the same method used to flash the defunct CWM. I don't have the Slate 7 Plus, so I can't test things myself
The best I can do right now is debloat, deodex, and pre-root ROMs, as well as install more system apps.