I want to compile one of these Roms to our awesome phone.
Which should be done?
Can some one help me with this?
I have already installed my Virtual Machine and everything else that is needed, I just need to pull the neccesary files from the Rom and somehow (this i dont know how to do) integrate the CM code that is needed for our phone to function.
Related
so i have a custom build over in the vogue forums but i would love to get it working on the hero, it is basically just a heavily customized version of AOSP so i took asop mod as a base and added my custom changes to it (that part i got) i then signed it and attempted to flash it to my hero, it got about half way through the installation and said i was missing and update script so if anybody can give me advice that would be awesome i would really love to get this build running on my daily phone.
thoughtlesskyle said:
so i have a custom build over in the vogue forums but i would love to get it working on the hero, it is basically just a heavily customized version of AOSP so i took asop mod as a base and added my custom changes to it (that part i got) i then signed it and attempted to flash it to my hero, it got about half way through the installation and said i was missing and update script so if anybody can give me advice that would be awesome i would really love to get this build running on my daily phone.
Click to expand...
Click to collapse
When you unzipped the ROM you should have seen some folders and a boot.img. There are some folders in the boot.img that need to be replaced along with the kernel for our phone. So just using a boot.img from another ROM might be the easiest. Otherwise you will have to unpack it, switch out files and repack with a kernel for our phone.
The update script is found in /META-INF/com/google/android/. You should be able to pull it from another ROM.
unCoRrUpTeD said:
When you unzipped the ROM you should have seen some folders and a boot.img. There are some folders in the boot.img that need to be replaced along with the kernel for our phone. So just using a boot.img from another ROM might be the easiest. Otherwise you will have to unpack it, switch out files and repack with a kernel for our phone.
The update script is found in /META-INF/com/google/android/. You should be able to pull it from another ROM.
Click to expand...
Click to collapse
ah i deleted the meta-inf folder thats probably what cause the problem
also am i able to have a folder that keeps things in /data like i am on the vogue or does it all have to be in the system?
I was wondering if anyone would be able to code a bootloader like piece of software
in theory if we could make something that can start at the same level as revoery then we could have that select wich rom to start. I think then we could have mutiple roms on one device.
i was thinking it could be very good right now as devs and testers are using GB roms. THey could have a nice stable themed rom and then a dev rom and be able to switch between the to.
Is this possible or a pipedream(and why wont it work)
kedster said:
Is this possible or a pipedream(and why wont it work)
Click to expand...
Click to collapse
Bootloaders are closed source, and no one wants to re-write them right now.
Also, Q/A.
actually there was a script to dual boot the nexus S rom on our captivate a while back but it required data as system..
got honeystreak rc 2.1 on my dell streak 7 and i have no clue how to get clockwork recovery on it with honeystreak, so when i get rom manager and flash clockwork it works, then i reboot into the original recovery then i choose software upadate.pkg then when i click it nothing happens it just has the dell logo then it just powers up like it normally would so i cant get clockwork i need help!!!
CWM and Honeystreak are not compatible.
Same thing happened to me, the root was easy with gingerbreak, had root so I could run rom manager and flashed that to the clockwork recovery and backed up. Installed honeystreak using the nvflash and didnt like the instability of it so I wanted to go back but didnt realize the way back was another nvflash the breaks the device and then you have to recover from the cwm back up. I returned it at that point.
I've learned some more about nvflash since then, it seems its the official way they install the os's to the tegra devices. But without the official install files needed for your device, it has to be rigged. Which is why the honeystreak is unstable and the flash back to stock is broken and has to be recovered from a back up.
Windows, ubuntu are such easy installs compared to android. Everythings on a disc(that you can setup on a usb stick), there arent 14 or how ever many separate files you have to download(for the nvflash). And it just starts the install, you dont need separate program to install. They really made the process needlessly complicated for installing android.
I just find it hard to believe, non developers have to RELY on the hacker community to perform fresh(or not so fresh) installs because google/the middlemen dont provide installation media. Oh wait they provide the source code... which if your not a developer is no help to the uninitiated that just want a clean install, install newer versions.
http://forum.xda-developers.com/showthread.php?p=16257823#post16257823
http://forum.xda-developers.com/showthread.php?t=1018809&highlight=nvflash
papermate said:
Same thing happened to me, the root was easy with gingerbreak, had root so I could run rom manager and flashed that to the clockwork recovery and backed up. Installed honeystreak using the nvflash and didnt like the instability of it so I wanted to go back but didnt realize the way back was another nvflash the breaks the device and then you have to recover from the cwm back up. I returned it at that point.
I've learned some more about nvflash since then, it seems its the official way they install the os's to the tegra devices. But without the official install files needed for your device, it has to be rigged. Which is why the honeystreak is unstable and the flash back to stock is broken and has to be recovered from a back up.
Windows, ubuntu are such easy installs compared to android. Everythings on a disc(that you can setup on a usb stick), there arent 14 or how ever many separate files you have to download(for the nvflash). And it just starts the install, you dont need separate program to install. They really made the process needlessly complicated for installing android.
I just find it hard to believe, non developers have to RELY on the hacker community to perform fresh(or not so fresh) installs because google/the middlemen dont provide installation media. Oh wait they provide the source code... which if your not a developer is no help to the uninitiated that just want a clean install, install newer versions.
http://forum.xda-developers.com/showthread.php?p=16257823#post16257823
http://forum.xda-developers.com/showthread.php?t=1018809&highlight=nvflash
Click to expand...
Click to collapse
so your saying its not possible to get cwm on honeystreak
azoller1 said:
so your saying its not possible to get cwm on honeystreak
Click to expand...
Click to collapse
Its possible to get cwm(the app) ON honeystreak. What doesnt work on honeystreak is the clockwork recovery boot up menu as you have noticed yourself. Dont ask me why, I dont know. And the only current "fix" for it is to nvflash to stock where the clockwork recovery boot up menu works.
I have an open question for anyone, does clockwork rom manager work properly on honeycomb and thereby make the problem isolated to honeystreak? Or does it not work properly on honeycomb at all.
Honeystreak requires NVflash to install because it completely repartitions the nand.
nandroid depends on knowing ahead of time what the partition layout is, it's not gonna work if it'd different depending on what rom is installed.
If someone made a HC compatable clockwork it wouldnt be compatable with the stock rom either
so when the official honeycomb comes out for the dell streak 7 will clockwork mod actually boot up correctly?
azoller1 said:
so when the official honeycomb comes out for the dell streak 7 will clockwork mod actually boot up correctly?
Click to expand...
Click to collapse
When clockwork rom manager is updated to work on HC it will work... thats what I understood from his post, considering the partition layout is different on HC from previous versions.
There needs to be a partition editor and usb/sd card install-able android media like with ubuntu/windows too do away with these crippled ways of doing this. This modern os cant even perform the basics of installation that desktop os's have performed for a decade?. Maybe when Ice cream source code comes out, this is exactly what someone will do. Til then this is ridiculous. They have so hamstrung the ability to control the os on your hardware. What good is open source software if they control how it gets on the hardware. This is not a methodology I would support.
I'll have to see how windows 8 is handled on arm hardware. Might be the only os you can install and update on your own without the hassle. Or I just wont buy any arm devices and stick to flip phones and laptops for mobility.
papermate said:
When clockwork rom manager is updated to work on HC it will work... thats what I understood from his post, considering the partition layout is different on HC from previous versions.
There needs to be a partition editor and usb/sd card install-able android media like with ubuntu/windows too do away with these crippled ways of doing this. This modern os cant even perform the basics of installation that desktop os's have performed for a decade?. Maybe when Ice cream source code comes out, this is exactly what someone will do. Til then this is ridiculous. They have so hamstrung the ability to control the os on your hardware. What good is open source software if they control how it gets on the hardware. This is not a methodology I would support.
I'll have to see how windows 8 is handled on arm hardware. Might be the only os you can install and update on your own without the hassle. Or I just wont buy any arm devices and stick to flip phones and laptops for mobility.
Click to expand...
Click to collapse
The only reason the HC builds all require repartitioning is because they're based off system dumps form other devices. As the majority of the source isnt available the only way to get them to work is to make the device more closely resemble the donor rom device instead of making the rom more similar to the reciving device.
If/when HC lands it's either going to use the 2.2's partition map or require a pc to install that has a streamlined version of nvflash bundled. The only thing that would happen if users were able to manually repartition devices is seeing the rom completely break and require a un-repartitioning as android is hardcoded to take a specific partition layout, as device makers have the source they can change the hardcoded values.
Being able to repartition would be more akin to being able to shuffle around the layout of your pc's bios more then being able to repartition windows. There's no generic version of android (nexus devices might be considered generic, but nexus roms wouldnt boot on any other device anyway), it requires it to be ported to a specific device to work. you COULD play around with your bios to the point that you can shuffle stuff around but unless you had a good reason to there's no point.
Being Linux based, I would like to see Android loaded as modular as opposed to monolithic, and then the device manufacturers could simply release open source modules for their hardware. Of course, maybe this would slow things down for processing; but I'd really like a simple way to just port the OS on any device. This would be a great boon for the open source community.
could it be pssible to port over clockwork from another device to this? or is the only way to flash it
The original clockwork is a port, there would need to be 3 versions total to cover every rom:
2.2
3.1
3.2
as the HC roms are based off multiple device dumps and neither are compatable with eachother
I want to learn how to build my own android roms from the source up. So does anyone recommend any literature to read, tutorials to follow, things I need to understand.
I do have two minor preferences; I prefer to develop on Windows, is this possible? And I would like all the literature to be on the internet, so actuaally to be free available....
About me, you can say that I am a noob (I did build an android app with a group of people for school), but I am willing to learn. So does anyone know what are the first steps to take to become a succesful developer.
*Also could someone explain to me: Is there a difference between a regular/rom cooker developer and kernel developer. Do you need to be both to for example make jelly bean working on your phone singlehandedly or do you just need to be a rom cooker?
Rom cookers are the sort of people that have all the required files and they just cook it up into a ROM, Developers are the sort that make things, Add things re-write things, then cook it up.
you will need to start by getting a stock ODIN ROM, and using the tools that can open it, As for these tools im unsure, The kernel is zImage << so you need to find a tool to read / edit that.
You will need to use linux, However you can use Cygwin (linux for windows) and you could try dsixda's rom kitchen,
You will also need 7zip and Notepad ++ , These are just a few of many stuff you will need
Here are a few guides to get you started
http://forum.xda-developers.com/showthread.php?t=633246
http://www.xda-developers.com/android/learn-to-build-kernels-and-roms-for-the-galaxy-s-ii/
http://forum.xda-developers.com/showthread.php?t=1069868
Everything you need to know will be on XDA somewhere
Good luck !!
PS: Make regular backups during development, You first aim should be to get a Stock ODIN ROM converted to a CWM zip file and get it booting, Then start to make tweaks / mods / themes
Good luck, and read this as a word of caution: http://forum.xda-developers.com/showthread.php?t=1690663
A question: how do you extract the boot.img from the SGN? I have already tried this with dsixda's kitchen and CM9, but all I get is the error; "Android Magic not found in ./boot.img". So what are the exact steps to follow for the SGN to extract the boot.img?
I also have a pice of advice. Get a cheaper android phone to play with (which you don't mind breaking). Emulators are great, but there's nothing like the real thing.
PS: For some reason, the image of Guybrush Treepwood saying "I want to be a pirate" came to my mind...
Hi,
I have this weird issue where every time I flash a Cyanogen based mod, (CM itself, SlimBean etc.) my IMEI gets wiped (see here) and I have no way of recoving it unless I flash a MIUI ROM which adds a dummy IMEI and then run a tool to recover the actual one.
What ROMS are out there that are not based on CM apart from MIUI (which is simply too slow on this phone)?
Alternatively, if anyone knows a way of flashing CM or SlimBean without it deleting the phone's IMEI, I'm all ears.
edit: If I had to guess I'd say there's something messed up with the partitions although I can't imagine what. Maybe Odin has some feature to detect/fix such a thing?
Thanks
P
pickarooney said:
Hi,
I have this weird issue where every time I flash a Cyanogen based mod, (CM itself, SlimBean etc.) my IMEI gets wiped (see here) and I have no way of recoving it unless I flash a MIUI ROM which adds a dummy IMEI and then run a tool to recover the actual one.
What ROMS are out there that are not based on CM apart from MIUI (which is simply too slow on this phone)?
Alternatively, if anyone knows a way of flashing CM or SlimBean without it deleting the phone's IMEI, I'm all ears.
edit: If I had to guess I'd say there's something messed up with the partitions although I can't imagine what. Maybe Odin has some feature to detect/fix such a thing?
Thanks
P
Click to expand...
Click to collapse
Which CM do you use?
Return to stock (odin) and after flash rom.
ROM can be erased in some. Especially Miui.(Sorry bad English)