Related
so yea i have dxisda kitchen and sdk and sgs2 and of that junk but i dont even know how to open sdk tools how to start ? how to make custom rom? how to open the f***ing .img?! you know bascis.. so yea thk for help and pls help...
solain said:
so yea i have dxisda kitchen and sdk and sgs2 and of that junk but i dont even know how to open sdk tools how to start ? how to make custom rom? how to open the f***ing .img?! you know bascis.. so yea thk for help and pls help...
Click to expand...
Click to collapse
I too would love the help and for possibly someone to take me under their wing. I am very eager to learn. I'm always on my phone, and always trying to read, but sometimes the forums just contradict themselves, and let's face it, with all the drama going on in the forum, it can sometimes get a little frustrating trying to ask for help, especially when someone doesn't want to be bothered by a noob. Thanks in advance
Sent from my PG06100 using Tapatalk
solain said:
so yea i have dxisda kitchen and sdk and sgs2 and of that junk but i dont even know how to open sdk tools how to start ? how to make custom rom? how to open the f***ing .img?! you know bascis.. so yea thk for help and pls help...
Click to expand...
Click to collapse
Not sure what you are asking. For the sdk tools, do you mean the android sdk? If so, follow the instructions on the sdk page. For the images, I assume you mean the boot.img and possibly system.img. You do not open these. If you have a system.img, that means you probably have a shipped rom. Use the kitchen to create working folder from rom, and choose this. It should auto extract the system partition. As for the boot.img, you don't generally need to extract this, but there is an option in the advanced settings of the kitchen. You can change your rom's kernel in the boot.img.
cbernardo13 said:
I too would love the help and for possibly someone to take me under their wing. I am very eager to learn. I'm always on my phone, and always trying to read, but sometimes the forums just contradict themselves, and let's face it, with all the drama going on in the forum, it can sometimes get a little frustrating trying to ask for help, especially when someone doesn't want to be bothered by a noob. Thanks in advance
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Hey Guys!
First of all a bit of encouragement. The android kitchen sure as hell does not turn you into a rom developer. I decided i wanted to use the kitchen just over 2 weeks ago and run ubuntu in a virtual window. From then I decided I did not like windows anymore so installed linux as my main os and had to learn that (trust me getting the graphics card to work was a chore) I finally got the kitchen working tonight and decided to sign up to xda. Even with my limited knowledge I have been able to help someone on here tonight. Read Read Read and ask questions if you can not find the right answers on the forum. Research pays off eventually. (I now softmod nintendo wiis professionally from learning off a forum!!!!) Remember everyone has to start somewhere even if you are a noob and don't get disheartened if someone says you should have read this this and this. As long as you learn from ur mistake I'm sure people wont mind too much.
SFUK
aha... so let me understand i need ubuntu?
and i need to open system img fot the app edit
can someone pls answer yes im using android sdk and yes i use stock rom how to edit img? i need to edit system for app app folder edit i could open it at linux reader but icant edit its all written in hex
How long before bricked again...????
solain said:
can someone pls answer yes im using android sdk and yes i use stock rom how to edit img? i need to edit system for app app folder edit i could open it at linux reader but icant edit its all written in hex
Click to expand...
Click to collapse
Im about to take the dive myself, still rounding up the tools. Was about to dl virtual...unbuntu etc but read this just now and it makes sence so as much as i want to screwup my phine as fast as possible i think i will follow this advice.
You might have already seen and read but what the hell....
Originally Posted by cyanogen
I really dislike the "chef" moniker when it comes to Android, since we are more of an open-source community. I think it implies a "file pusher" mentality. But then again, I am biased against proprietary versions of Android like Sense, so feel free to disregard all of this.
Here's my advice for those looking to make their own Android ROMs.. Stop. Write an app or two first, learn how the system works from a developer standpoint. Learn some Java. Read the developer documentation. Learn how to use Git. Then learn how to build AOSP from source. Read the porting guides, and learn how the build system works (the links below have almost everything you could possibly want to know). Now try to put your new found skills to work on enhancing the platform by writing code or making theme overlays. And share! And put that **** on your resume. There is a *ton* of information out there but any kind of "step-by-step rom cooking guide" is going to be a complete fail- it's too broad of a subject.
Android Developer Guides: http://d.android.com
Working with AOSP source: http://source.android.com
Platform Developer Guide: http://pdk.android.com
Android Gitweb: http://android.git.kernel.org
Git Ready (Git tips and tricks): http://www.gitready.com/
Building CyanogenMod: http://wiki.cyanogenmod.com/index.ph...ng_from_source
How Dexopt works and what are those odex files: http://android.git.kernel.org/?p=pla...5936;hb=master
The PDK site is absolutely vital if you are going to work on custom ROMs. Read every single page. Twice. Some of the info isn't up to date, but you'll get a really good idea about what goes into actually configuring Android to work on a real device.
dmeadows013 said:
Not sure what you are asking. For the sdk tools, do you mean the android sdk? If so, follow the instructions on the sdk page. For the images, I assume you mean the boot.img and possibly system.img. You do not open these. If you have a system.img, that means you probably have a shipped rom. Use the kitchen to create working folder from rom, and choose this. It should auto extract the system partition. As for the boot.img, you don't generally need to extract this, but there is an option in the advanced settings of the kitchen. You can change your rom's kernel in the boot.img.
Click to expand...
Click to collapse
can u shoot me a couple links for the kitchen/other tools download
solain said:
so yea i have dxisda kitchen and sdk and sgs2 and of that junk but i dont even know how to open sdk tools how to start ? how to make custom rom? how to open the f***ing .img?! you know bascis.. so yea thk for help and pls help...
Click to expand...
Click to collapse
What version of Linux are you running? Are you running Ubuntu? I never had much luck using the Android Kitchen in a virtual environment for some reason. When I installed Ubuntu as my main OS, however, that made all the difference. From there you'll also need to make sure you have the Java Developers Kit (JDK) installed or at least open-jdk (Open source alternative) installed in order to run the Android Kitchen or the SDK for that matter.
There's a really good tutorial on how to set up the SDK on Ubuntu 10.10 or Ubuntu 11.04 which is what I had used to set up the SDK on linux for the first time. http://forum.xda-developers.com/showthread.php?t=921169
I prefer 10.10 just because I'm not huge on Ubuntu's newer Unity interface and my old laptop seems to run 10.10 a lot better than 11.04 or 11.10 but that's another story.
Once you have the SDK setup, you can then run the kitchen accordingly.
I use a tool called Android Utility by tommytomatoe which is essentially a collection of tools for creating custom ROMs, editing apk's, etc. It just happens to also include dsixda's kitchen which is a nice plus. You can download that here: http://rootzwiki.com/topic/3303-utility-android-utility-apktooldex2jarsmalimoremac-linuxoct09-2011/
Hope this helps. Good luck, dood!
**Edit** My bad... There's also a thread for Android Utility on XDA also....
http://forum.xda-developers.com/showthread.php?t=1167623
So I have been working on this for a while trying to get things to cross compile, and i got this to compile it is the Source and the program runs on the nook. Next we will have to write our new init.rc to mount our own os. Someone will have to help me with some research, but I just thought you should know.
Here are the files:
2nd-init.tar
To recomile with the NDK use the following command:
Code:
/home/<user>/Downloads/android-ndk-r7/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc --sysroot=/home/<user>/Downloads/android-ndk-r7/platforms/android-14/arch-arm/ 2nd-init.c
(Thanks to Indirect)
GOOD LUCK
Loglud said:
So I have been working on this for a while trying to get things to cross compile, and i got this to compile it is the Source and the program runs on the nook. Next we will have to write our new init.rc to mount our own os. Someone will have to help me with some research, but I just thought you should know.
Here are the files:
2nd-init.tar
To recomile with the NDK use the following command:
Code:
/home/<user>/Downloads/android-ndk-r7/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc --sysroot=/home/<user>/Downloads/android-ndk-r7/platforms/android-14/arch-arm/ 2nd-init.c
GOOD LUCK
Click to expand...
Click to collapse
Hmm, if only another developer told you how to cross compile. Oh wait! Haha, congrats Loglud.
Loglud said:
So I have been working on this for a while trying to get things to cross compile, and i got this to compile it is the Source and the program runs on the nook. Next we will have to write our new init.rc to mount our own os. Someone will have to help me with some research, but I just thought you should know.
Here are the files:
2nd-init.tar
To recomile with the NDK use the following command:
Code:
/home/<user>/Downloads/android-ndk-r7/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc --sysroot=/home/<user>/Downloads/android-ndk-r7/platforms/android-14/arch-arm/ 2nd-init.c
(Thanks to Indirect)
GOOD LUCK
Click to expand...
Click to collapse
Awesome! Great job Log. Big Step in the right direction.
Nice. 10char.
So, did development stop on this? how is it installed?
AdamOutler said:
So, did development stop on this? how is it installed?
Click to expand...
Click to collapse
I want know it too... >.<
Jeeze idk, i completely forgot about this thread until you guys posted on it. I never did to much testing. This was mostly done in concurrence with the Kexec-Mod since i had the toolchain up and running. If i remember correctly it did generate the second init file, don't know if it ever loaded it, but i can work on it some more if people want. I was hoping some one would point me in the direction they needed me to go with this.
Loglud said:
Jeeze idk, i completely forgot about this thread until you guys posted on it. I never did to much testing. This was mostly done in concurrence with the Kexec-Mod since i had the toolchain up and running. If i remember correctly it did generate the second init file, don't know if it ever loaded it, but i can work on it some more if people want. I was hoping some one would point me in the direction they needed me to go with this.
Click to expand...
Click to collapse
I prefer first a compatible Custom Recovery
I compiled, but I don't know how adapt the hijack...
what is 2nd-init? Is it a bootloader? kernel? recovery? where does it come in the boot sequence?
http://nookdevs.com/Dump_NookTablet_Partitions
AdamOutler said:
what is 2nd-init? Is it a bootloader? kernel? recovery? where does it come in the boot sequence?
http://nookdevs.com/Dump_NookTablet_Partitions
Click to expand...
Click to collapse
http://and-developers.com/2ndinit
AdamOutler said:
what is 2nd-init? Is it a bootloader? kernel? recovery? where does it come in the boot sequence?
http://nookdevs.com/Dump_NookTablet_Partitions
Click to expand...
Click to collapse
Pratically.. it's the method with many motorola phone (with locked bootloader) can run custom roms like cyanogemod.
However the problem is it requires kexec mod.
Sent from my ADR6425LVW using xda premium
Loglud said:
However the problem is it requires kexec mod.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Sorry, but you're wrong.
From this source use the Hijack method. This mean you can instal a custom rom, but you can't replace the kernel or bootloader.
From the source:
It's also important to remember that 2nd-init does NOT unlock the bootloader, nor does it allow you to run a custom kernel. It simply allows us to utilize the kernel that is there for our own means
Click to expand...
Click to collapse
That method is good enough to run CM9 and it's relative simple to port.
The kexec method is something different, but better: is a system call that enables you to load and boot into another kernel from the currently running kernel.
kexec performs the function of the boot loader from within the kernel.... essentially a hijack to allow us to call another kernel as a function of the stock one, allowing us to bypass the locked bootloader.
Source
Someone has had success with this method
See this twitter feed:
http://twitter.com/androidnemith
@AndroidNemith just have seen your photo with the CWM on the Nook tablet. How did you do that since the Bootloader is locked ?
@PetePetePete1 Hijacking . Same way moto defy and others are doing it. Right now i am kicking it manually looking for a better way now.
@AndroidNemith can you show your current state XDA developers, because they are still searching for a method to get a custom bootloader
@PetePetePete1 It's not quite ready and i got distracted by NookColor bits. If you want to see what i am doing look at the Moto Defy CM
Click to expand...
Click to collapse
I take no credit for finding this, as I haven't been talking with @AndroidNemith
HMG10 said:
See this twitter feed:
http://twitter.com/androidnemith
I take no credit for finding this, as I haven't been talking with @AndroidNemith
Click to expand...
Click to collapse
That would be me then I was also asking AndroidNemith if he could show his current state on XDA but he didn´t reply back yet :S Oh yeah and nice picture
http://yfrog.com/nxrztiij
hello
i am a new developer i am starting to create ROMS and android kernel's. i am using Ubuntu 12 and any advise on tools and a starting point would be greatly appreciated. i use Heimdall to get the ROM's onto my device.
starter questions
1) how do i download the original android kernel to my system (linux)
2) best tool to view the kernel code.
i would like to be a productive XDA developer so any advise or direction would be great.
Cy83rn1nj4 said:
hello
i am a new developer i am starting to create ROMS and android kernel's. i am using Ubuntu 12 and any advise on tools and a starting point would be greatly appreciated. i use Heimdall to get the ROM's onto my device.
starter questions
1) how do i download the original android kernel to my system (linux)
2) best tool to view the kernel code.
i would like to be a productive XDA developer so any advise or direction would be great.
Click to expand...
Click to collapse
Here's the replies
1. That depends of the device you currently own
2. I use gedit but most people says that gedit and Vim are the best editors for ubuntu.
Also you would need the android sdk (for adb) also you will need jdk. If you want more informations don't be affraid to ask.
EDIT: I forgot to ask which languages you have learned?
im learning Python using google.com/edu great online webinars my company want me to also learn ruby as we develop our apps using rails.
thanks for the reply i will look for a standard android image i can decompile and test with.
Cy83rn1nj4 said:
im learning Python using google.com/edu great online webinars my company want me to also learn ruby as we develop our apps using rails.
thanks for the reply i will look for a standard android image i can decompile and test with.
Click to expand...
Click to collapse
You cant decompile any compiled to machine code program, its basic.. You can only get source code or deassemble to unreadable and unusable code.
Sent from my GT-I9000 using xda app-developers app
Hi..im a quite fresh android user after having iphone for the last 4 years....i have a huawei ideos x5 pro that for me at least is a great phone for his price..but the major problem is that we don't have devs for our phone...only one chinese guy that develops roms for at least 7 phones so we aren't his major concern...so im asking if there is a complete noob guide for compiling rom..fixing rom.
i have to tell you and please don't flame that even that i have knowlage over pc's i haven't any knowlage over programming and coding!!so if any guide can't help me it will be ok...i try! but if there is a guide that can help me step by step to understand the basics and then with a bit of research can figure it out the rest it will be helpful!!
Thanks!!
Sorry for my english!
http://lmgtfy.com/?q=make+android+custom+ROM
thewadegeek said:
http://lmgtfy.com/?q=make+android+custom+ROM
Click to expand...
Click to collapse
Yeah i know that...im asking for a user's entirely noob guide...1st time user guide...google is full with guides but not so novice guides!!
There isn't a "type this, click this, A,B,C" guide. That would be called just copying somebody's work. What you need to do is start reading through ALL the guides you can find, compile a kernel, read smali, change colors, mod pictures, unpack-repack boot.imgs. I can't give you a link and say "Read this tutorial and you will be a developer", that's just not how it works.
thewadegeek said:
There isn't a "type this, click this, A,B,C" guide. That would be called just copying somebody's work. What you need to do is start reading through ALL the guides you can find, compile a kernel, read smali, change colors, mod pictures, unpack-repack boot.imgs. I can't give you a link and say "Read this tutorial and you will be a developer", that's just not how it works.
Click to expand...
Click to collapse
ill give it a try thanks!!!
After reading a lot of guides...i can say that i didnt find anything so hard but i haven't try it so far so i can say for sure...but i stuck in one thing...somewhere on all the guides it sais to find your device tree...and many guides that are from samsung or htc using some github and some cyanogen brances...i have an huawei ideos x5 pro...where i will find those trees?do i need them for making the android source work with my device or the source from google is universal meaning that when im build the rom from sources.android.com the rom will work in my device??
pikachukaki said:
After reading a lot of guides...i can say that i didnt find anything so hard but i haven't try it so far so i can say for sure...but i stuck in one thing...somewhere on all the guides it sais to find your device tree...and many guides that are from samsung or htc using some github and some cyanogen brances...i have an huawei ideos x5 pro...where i will find those trees?do i need them for making the android source work with my device or the source from google is universal meaning that when im build the rom from sources.android.com the rom will work in my device??
Click to expand...
Click to collapse
You must have a device tree... If not you have to build your own... The rom built from source.android.com will only work with google nexus devices...
adiles said:
You must have a device tree... If not you have to build your own... The rom built from source.android.com will only work with google nexus devices...
Click to expand...
Click to collapse
So my hands is tied...nice!!there is no way that i can make a tree i don't have so much knowlage!! :/ too bad!!
pikachukaki said:
So my hands is tied...nice!!there is no way that i can make a tree i don't have so much knowlage!! :/ too bad!!
Click to expand...
Click to collapse
look for a device with similar hardware and copy that device tree, then try to make adjustments to get it working and voila. and ask that one dev if he can give you his device tree
I have read all things in xda about my u8800, and xda helps me know about root, install cwm, uprom..etc. thank all of you, thank xda
-Sent from my u8800-
Me Too!
lemonade747 said:
I have read all things in xda about my u8800, and xda helps me know about root, install cwm, uprom..etc. thank all of you, thank xda
Click to expand...
Click to collapse
I'm actually reading everything about my new device, Sony Neo L. This is pretty amazing! XDA rocks!
CrisisCorE said:
look for a device with similar hardware and copy that device tree, then try to make adjustments to get it working and voila. and ask that one dev if he can give you his device tree
Click to expand...
Click to collapse
Hardware we need the same cpu gpu or everything?sensors bt wifi etc?
Sent from my U8800PRO using xda premium
How can i get source code for Vision, since huawei doesnt let you download it?
Sent from my Vision
if u r good at linux, u can try this guide >>> http://handycodeworks.com/wp-content/uploads/2011/02/linux_versus_android.pdf
I compile linux kernels for desktop, but the android kernel is not the same. Cyanogen team and GOOGLE Android developers provides a comprehensive guide on building ur own ROM. But to build ur own OS, u need to understand each component carefully. I don't know abt android, but i am making Linux OS from scratch. I have kernel compiled, tool chain set up, now i am putting apps on it. But android uses DALVIK VM for Java apps, also .... U refer the pdf it will tell u. Once i finish making this OS, i'll focus on Android ROMS. They r similar to Linux OS, but require patches in kernel, a light c lib, new fs, a different vm (dalvik) and different ways of managing i/o interrupts and much more..
this link is on porting android on nokia >> http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/Porting-Android-to-a-new-device/
this one is on linux on embedded systems >> http://www.lindusembedded.com/blog/2010/12/07/android-linux-kernel-additions/
Also, sorry to say but learn C/C++/Java . To make ROMS, atleast to make modifications and to understand the kernel u'll need C. Not very hard to learn, Good tuts on Lynda.com and other sites. And be good at Linux. Happy Learning
hello i just want to ask where are touchscreen files and drivers because i found cyanogenmod for similar hardware but only the touch screen is not working so i thought to replace with the working rom for my device
PLEASE HELP ME OUT WITH THIS ONE !
icoolguy1995 said:
hello i just want to ask where are touchscreen files and drivers because i found cyanogenmod for similar hardware but only the touch screen is not working so i thought to replace with the working rom for my device
PLEASE HELP ME OUT WITH THIS ONE !
Click to expand...
Click to collapse
please give me an answer
icoolguy1995 said:
please give me an answer
Click to expand...
Click to collapse
go to the root of your filesystem most root browsers do this anyways and dev then input and it should be the event files
hillconnor13 said:
go to the root of your filesystem most root browsers do this anyways and dev then input and it should be the event files
Click to expand...
Click to collapse
what are event files
i checked there are no files
there is no appropriate answers please i need it pls help me out guys
/sys/android_touch/vendor (open it as a text file)
That tells you the make of your touchscreen. First step to seeing if it is compatible at all.
And you can't just make CM for another device work for yours by replacing a few files. It has to be ported to your device or compiled from source with all the right drivers and binaries. This requires a lot of developer knowledge, which you don't seem to have judging by your questions. So don't go messing around changing files in ROMs and trying to make them work. If you're really interested, learn about porting and compiling from source.
Sent from my Desire HD using xda premium
sashank said:
/sys/android_touch/vendor (open it as a text file)
That tells you the make of your touchscreen. First step to seeing if it is compatible at all.
And you can't just make CM for another device work for yours by replacing a few files. It has to be ported to your device or compiled from source with all the right drivers and binaries. This requires a lot of developer knowledge, which you don't seem to have judging by your questions. So don't go messing around changing files in ROMs and trying to make them work. If you're really interested, learn about porting and compiling from source.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
i did not find android_touch in sys folder from root explorer