Hi all,
Would like to find out if it is possible to install android without the use of acmeinstaller, the reson for that is that i have a touchpad-go, which is basically 100% the same hardware, but uses a different name for kernel (shortloin instead of tenderloin) and probably some other naming differences. I think the acmeinstaller script refuses to continue due to not finding the right files or signatures, however I believe CM10 should work on it. Would appreciate some input on how to start
Check out the Kexec thread in the Other Development section, he's not done yet, but it sounds promising!
Sent from my slim_tenderloin using xda premium
Related
What is porting a rom? I think it is just taking a rom from different phone and making it work on another device....is that right?
If that is right I want to port a rom or roms from the Nexus One to the HTC Hero CDMA.
But can anyone list what tools and knowledge I will need? I'm running windows 7. So any programs or books I need to read can someone give links to information about the book, or links to download/buy the program that I'll need to get started on porting roms to our HTC Hero CDMA.
Also can someone tell me the pros and cons of porting roms as well?
Thanks, I can't wait to get started on this
Try using the ultimate theme injector is what I've been using
Sent from my DROIDX using XDA App
If you really want to get into it I suggest running a Linux distro. I run ubuntu 10.04. Haven't had windows on my computer since August of last year. Took a little while to get use to, but I now like it better. Also gives you the ability to get repos, compile Android and kernels, and much more.
Depending on what you are porting it might require new drivers, xml edits and resizing, the theme injector will only do so much. I think it will only replace and resize images.
Sent from my dual-booted liquidsense 2.1
spleef said:
Try using the ultimate theme injector is what I've been using
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
so i use this for resizing/replacing images.....
unCoRrUpTeD said:
If you really want to get into it I suggest running a Linux distro. I run ubuntu 10.04. Haven't had windows on my computer since August of last year. Took a little while to get use to, but I now like it better. Also gives you the ability to get repos, compile Android and kernels, and much more.
Depending on what you are porting it might require new drivers, xml edits and resizing, the theme injector will only do so much. I think it will only replace and resize images.
Sent from my dual-booted liquidsense 2.1
Click to expand...
Click to collapse
and then you say use my linux distro for everything else.....but where are the links tutorials/books i need to read/tools i'll need to get started on the rest of the stuff for porting roms?
thanks for helping btw
Have you built any roms yet? I'd suggest getting a kitchen and playing around with a known good rom - get used to what's there, what you can change, things like that. I've been playing around with dsixda's HTC Android Kitchen (on WinXP using Cygwin) lately with a few ROMs (my stock rom, liquid sense, aosp, and CM6). That's the best way to learn IMO.
TJinWV said:
Have you built any roms yet? I'd suggest getting a kitchen and playing around with a known good rom - get used to what's there, what you can change, things like that. I've been playing around with dsixda's HTC Android Kitchen (on WinXP using Cygwin) lately with a few ROMs (my stock rom, liquid sense, aosp, and CM6). That's the best way to learn IMO.
Click to expand...
Click to collapse
OOOOOOOOOH!!!!!11
that sounds like that might actually work....once i get a kitchen set up on linux mint. play around with a few different roms and see what i'm able to change, find out what it is that i'm changing and what changing it does.....AAAAHHH YOU'RE A GENIUS!
That sounds like that will work for learning to begin to develope beginner roms, and improve roms.
But now that you've got me set for like the first few months of learning. I don't want to post another thread about porting roms, so anyone know any information on porting roms? I know the user above said use a theme injector but that is for resizing and editing the images of the rom im porting. There has to be more to porting a rom than just resizing images. I'm trying to get all my information ahead of time so that i can just jump into developing with little to no questions for our device
kifno, that kitchen also has "experimental" porting tools in the Advanced Menu. I meant to say that in my original post.
TJinWV said:
kifno, that kitchen also has "experimental" porting tools in the Advanced Menu. I meant to say that in my original post.
Click to expand...
Click to collapse
Thanks for letting me know. Now once I begin porting roms I'll have at least a start. Thanks everyone
Sent from my DROIDX using XDA App
kifno said:
Thanks for letting me know. Now once I begin porting roms I'll have at least a start. Thanks everyone
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
If your open to Suggestions... Try going to theunlockr.com, and Select the "How to's" Then Look for the Rom Development section... Know what, I'll do it for you!
Hold on!!
Ok here you go:
Watch these videos, see if they Help you out a bit!
http://theunlockr.com/category/howt...-development-how-tos/rom-development-how-tos/
Sent from my Hero using XDA App
I love so much AOSP Roms for our Galaxy S I9000..I have done a nandroid back-up of Galnet MIUI v4 and Cyanogenmod 7..so if i want one of two roms i have to format system/data/cache/datadata from recovery and then restore the back-up..
My question is if is there a way to manage to do a dualboot between this two (or others) Roms..??
I think if it is possible it will be a great develoment for our Galaxy S..
Maybe i'm sayng a stupid thing but i want to read your opinions about this..
Cheers
i dont think its stupid at all, this would be a great feature! I have seen this in other android devices!
I've always wondered this too.
This was done on my previous device (HTC Hero) but it was a bit of a pain. The second Rom was installed on SDcard which was slow, and was FCing constantly, etc.
Whoever's interested can have a look at the HTC Hero forum section. It was ported by Kendon (he was part of VillainROM back then, don't know now).
Hope some developpers can do this ..
If it was possible on Htc Hero with less memory and less power it could be done also on Galaxy S I9000..
But Htc Hero is Htc and Galaxy S is Samsung so..i don't know..
I'm sure this week in dev I saw a trial program to do just this, running up to 4 roms! Will hunt down link if I can! Brb
Sent from my GT-I9000 using XDA Premium App
Where..??On I9000 Development section..??
Just checked back in dev,q & a and general, 10 pages back, so either it is buried deeper, or it was a total phone bricker and mods pulled it, will search some more
Sent from my GT-I9000 using XDA Premium App
slaphead20 said:
Just checked back in dev,q & a and general, 10 pages back, so either it is buried deeper, or it was a total phone bricker and mods pulled it, will search some more
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
saw that 2...it was for the evo if i recall ...
Cant find it anywhere, @silkydude....thanks for confirming, started to think I had lost the plot!
Sent from my GT-I9000 using XDA Premium App
Hi there,
Dual booting is kinda possible.
First one is to have very slims roms so you can install both on the nand and select one using a modded recovery.
Second one is to use redbend_ua script that will backup the current running rom, and then install another one and run it. The operation takes between 5 to 10 min depending on the rom and thats the only possibility to switch from 2.2.1 to 2.3 and vice-verca without having to flash bootloaders as redbend can flash bootloaders.
Also using redbend can be tricky as it can dump and write on partition but if it fail at flashing bootloaders you will be bricked.
Bricked phones can still be recovered using j-tag or 301k resitor.
Here is an attempt by z4ziggy:
http://z4ziggy.wordpress.com/2010/09/15/rom-flashing-using-redbend_ua/
The script in this page does not work but it can be improved.
You should check with him and some good dev like supercurio or codeworkx.
Also before applying any scripts, post it here and ask other people to see if it seems correct.
Happy flashing.
quick edit:
Be sure to dump the whole rom and restore the whole image even empty bml as it may have an importance.
We have to ask to developpers..
Not really, try to make a script that dump some bml, then try to restore them is it works then your good to go further.
Finally when you have a working script use tegrak kernel sources to include a "boot selection" as he did.
(on tegrak at phone boot you can enter recovery using the "home" button, change that to run the script so if you wait it boots normally, if you push "home" it dump the current rom and restore another one to boot on it)
Editing again:
If you use 2.2.1 bootloaders only, you can symlink an rom.img at boot and boot on it, it is easier but it is also pretty slow. (see nexus S rom port by supercurio)
Hello all. I've recently been trying to get into Android development, more specifically Kernel development. I've played around with some kitchens and looked at the GB kernel sources from Samsung and tweaked it around.
Previously I previously learned Java to a point where I can put basic lines down and also more advanced stuff but with a bit of help here and there.
I have one question though, what would be the recommended path for creating an ICS Kernel. My plan is to start of with something "stock" and build up but I'm not quite sure what to consider stock seeing as the S1 never got ICS officially. Would I have to use CM9's Kernel sources and if so where do I acquire them.
I also have a good understanding of Ubuntu and its terminal and have a functional idea of what I'm doing there.
I'm having some problems to understand or find the difference between two concepts:
difference between kernel and firmware...
I really can't find the difference. Thanks for helping me
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Fersh0o said:
I'm having some problems to understand or find the difference between two concepts:
difference between kernel and firmware...
I really can't find the difference. Thanks for helping me
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
I'm still a noob myself, but this is what I think would explain this simply. The firmware is the ROM that you place onto your phone. This encompasses the user interface and overall function as seen by you, the user. The kernel is what tells the device what to do by allowing the hardware and software (firmware) communicate with each other. They're two separate items, but must be compatible in order for the device to function (and even boot) properly. For example, a kernel not meant for captivate firmware won't boot because it can't communicate the right messages to the hardware of the device to normally go through the start-up process. Kernel is also what allows many things to work right since it is hardware-related. Many custom kernels add functions like overclocking, underclocking, and many other tweaks that stock kernels can't. In turn, some beta kernels make the phone lose some functionality such as wifi, data, and video playback because it can't communicate with the phone's internals correctly. To sum it up, kernel is always present as a silent hero behind the firmware which you see and touch on the screen of your phone. The firmware bosses it around, but without a kernel, the firmware is nothing.
Hope this helped you a bit.
From noob to noob thanks a lot! Now I know more about this two concepts, this really helps me to understand better how they works, and at the same time has helped me to clarify and answer other questions that I had.... :laugh: Now I think I´m ready to start rooting my Cappy.
Once again THANKS! Belive me this helped me a lot... :good:
actually, firmware includes both the kernel and the various device drivers (example: graphics/touchscreen driver, modem that runs communications hardware for a specific phone on a specific network).
its the part of the phone's instructions that generally do not change regardless of which applications you install or remove from your phone via google play or other sources.
the rom flashing packages that folks develop and post on xda may include just a kernel, just a modem, or a complete rom that either matches, or differs, from the stock rom by Samsung/AT&T.
here's a link that may help
en.wikipedia.org/wiki/Firmware
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
I read the touchpad shares the same exact chip set as the exhilarate. Will I be able to port say, cm9? I'm new to development and porting so any details and help would be appreciated and there is currently no dedicated form for this phone, yet
Sent from my MB860 using Tapatalk 2
It sounds like you intend to port a Touchpad ROM to this phone? I wouldn't suggest doing that, as there are many phones that have the same chipset as the Touchpad, such as the T989. However, the thing with porting is that you are always using the Kernel from YOUR device, not the one you are porting from. This limitation means that you can only port from an existing level of development. Take for example, if you are currently on 2.3.3, you will be limited to porting CM7 ROM's.
I would not suggest flashing a Kernel from another device on your phone unless you are 100% sure it will work. Even with the same chipset, I think some things in the Kernel are executed differently in different devices.
Let me use the Touchpad as an example. I consider it a great device for playing around with because you have Moboot as a protective layer to ensure you do not brick anything. You can flash whatever Kernel you like and it should not brick, but will certainly not work! I flashed a Kernel from my T989 on to it, and all you get is a black screen when trying to boot. Same chipset, different Kernel execution... see my point?
If you were to do that with your phone you would mess up your boot partition and get a hard brick!
Edit: I seen that you found the Forum in Android General about pushing CWM to the phone, that's a good stepping stone!
If you wanted to be brave, I would try pushing CWM from the Blaze 4G, and then Flash one of those ROM's with your Kernel and Radio.
Very informative thanks man!
Sent from my MB860 using Tapatalk 2