Cook a AOSP ROM, give it to the Official HTC Developers = way to load ROMs? - Click Android Development

chusen popped me an Private Message. It contained this:
chusen said:
I've talked to HTC and they told me that if you cook a rom for tattoo sent it to the developers of HTC to see how we can load, you can cook a rom and try it?
Click to expand...
Click to collapse
If I read that correctly, he/she said that they have contacted HTC, and if we send them a ROM, they will analyse to see how we can load the sucker onto the device.
Alas, I don't have the tools to do android ROM cooking (yet).
Anyone willing to cook us a stock AOSP ROM for us to pop over to the HTC Devs to analyse? By that, I mean, no root or anything (unless you know what you're doing ), just plain stock (with some mods to make it faster, or something like that.
If HTC doesn't backstab us and 'ally' with us, they may be kind enough to tell how to flash the ROM or boot it via Fastboot or something...
I've also tried to contact HTC Australia in regards to custom kernels not booting, but every time they say "Oh yes, we're going to call you today" they don't. Damn.

Related

New Kitchen - Pandora Variant - Problems with NBSplit...

I'm trying to port over the Pandora kitchen from the Hermes to the Herald, but I'm running into a problem with the scripts it uses to build the ROM. I just realized... I should go home and check the scripts that Hypercore uses to see if they have the answers... lol
Anyways, I'm having a problem with the splitting and merging of the nb files. I thought I finally had it figured out but I don't... I'm not home right now so I can't post the code, but I was wondering if anyone had successfully used the NBSplit, NBMerge and all the imgfsTools with the Herald?
Thanks in advance!
you dont need to do so, those tools are in hypercore, and are a part of the package.
I cant even begin to understand why you wanna start on doing that.
But if you must, then you must...
itje said:
you dont need to do so, those tools are in hypercore, and are a part of the package.
I cant even begin to understand why you wanna start on doing that.
But if you must, then you must...
Click to expand...
Click to collapse
I don't want to do anything. I was just going through all the scripts and was just updating them to work with the Herald. When I get home, I'll read through all the HyperCore scripts.
It's a BuildOS kitchen: "Choose the program you want and then click on build" type of thing.
BTW, I gotta note, not one person has been very supportive of my efforts doing this... except for the Pandora kitchen maker himself... *sigh*
Kinda discouraging. (The only thing keeping me away from HyperCore originally was the lack of a "clean" ROM to start with. When I finally got comfortable with it, I realized that it'd be nice to have a simple way of making "quick" ROMs for people who didn't have the time to figure it all out.
dude good luck to you. more people working with the herald just make it better. there aren't that many custom roms it has to speak of. i hope that you are successful and I can't wait to test it out when it's done!
Thanks.
I got past that error I was having and I'm pretty much ready, except that I still don't have a clean ROM to start out with. I'm still working on that one. And I still have to add certain packages. I won't know if it works until I can get a clean ROM to work on, though.
ivanmmj said:
Thanks.
I got past that error I was having and I'm pretty much ready, except that I still don't have a clean ROM to start out with. I'm still working on that one. And I still have to add certain packages. I won't know if it works until I can get a clean ROM to work on, though.
Click to expand...
Click to collapse
What do you mean by a "clean ROM"? Can't you use an official HTC base ROM?
edzilla said:
What do you mean by a "clean ROM"? Can't you use an official HTC base ROM?
Click to expand...
Click to collapse
I can't believe I never thought about that... LOL
Well, I still need to know what the differences are between the herald and the atlas. I was trying to use a wing rom and clean that up, but MAN, tmobile clutters up that rom... when I get home, I'll do just that. I still need to know what the differences are so that I can create different configurations to choose from in the kitchen... (Touch-IT's itje... Hear my call. lol)

is this possible ????

i wanna try installing cyanogen modded rom onto my htc tattoo. if anyone has tried it or succeeded in ti or failed in it, please share your openions here.
i wanna know why i cant install it in my tattoo /what are the advantages of installing it/ from where do i get the information/guide to install it on tattoo....
if not possible, i wanna know the reason please... i am pretty sure, atleast someone must have tried doing this adventure... guys comeon please share your knowledge about this modded rom -cyanogen mod....
it's meant for a completely different hardware platform? unless you have a way of modifying it yourself to work with the tattoo's components, good luck!
i didnt get what you mean by completely different hardware platform... ????
because i have seen many HTC users with android on it, trying to install cyanogen mod ROM and most of them have succeeded in it....
its just a curiosity that i am asking here. even i dont know for sure why cyanogen mod doesnt work on tattoo or no one has tried installing/customizing for tattoo...
any input which helps us to install coocked rom/rooting tattoo would be highly appreciated.....
I'm not that much into this whole flashing thing, but as far as i know one of the main problems is that the screen resolution on the tattoo is different that on the hero, magic, etc.
This is the problem with all the apps on the market hero/magic. Those who work with hero, and magic, doesn't work on the tattoo. Not before the developer has modified the apps resolution on the app.
There is probably also other hardware in the phone, and therefore there has to be developed drivers that fit that hardware.
Hello!!!someone has proven to tutorials for the root htc hero or magic in the tattoo?
No. Not yet. If you don't know what 'root', 'superuser', or flashing means, I wouldn't recommend risking your phone doing the said activity. More for experienced people.
I am a newbie to android and in no way a developer...but am surely adventurous....I will also help in testing as long as step by step instructions are available...thanks so much for stirring up some interest in this...
kashishd said:
I am a newbie to android and in no way a developer...but am surely adventurous....I will also help in testing as long as step by step instructions are available...thanks so much for stirring up some interest in this...
Click to expand...
Click to collapse
Exactly! As soon as step by step instructions are available, people who own the tattoo and want to flash roms will be able to. For now, we just have to wait for a breakthrough.

when can we expect custom ROM's ???

guys, i cant wait to install custom ROM on my tattoo. i hardly congratulate those who worked really hard in getting this tattoo rooted...
but whats the real use when we cant play with this little device without exploiting it fully .....
sorry if i am humiliating all those who are actively involved in the development, but i am little more curious like rest of us. hence i am asking this question here....
roughly how long it will take to produce custom ROM after rooting a device ???
Expect an average development time between two days and one year but it might differ plus/minus 20%...
I understand your impatience but asking things that are already written elsewhere because the truth is reluctantly to believe ("nobody knows how long it will take") doesn't speed up anything! We don't write "We don't know" because we think it is funny to know more then the rest...
-bm-
Could you tell us what is needed for a custom rom? I'm new in android hacking, or mobile hacking in general. All I know is that for WinMo devices you'll need a hardSPL, application unlock and a RUU.
I think there will be less questions if we know what we're waiting for. Time is, at least for me, not really a question since there are numerous wonderful developers here and we all follow progress in the other threads.
For the tattoo we now have root access and r/w access to the file system. What else is needed? A new boot loader, a flash utility, kitchen?
I tried to find it elsewhere in the forum but information is scarce and/or scattered so it's quite hard to find out what is going on. Most information I found are howto's, but what we actually want here in this stage of development are whyto's .
Please, enlighten us
manuvaidya said:
guys, i cant wait to install custom ROM on my tattoo. i hardly congratulate those who worked really hard in getting this tattoo rooted...
but whats the real use when we cant play with this little device without exploiting it fully .....
sorry if i am humiliating all those who are actively involved in the development, but i am little more curious like rest of us. hence i am asking this question here....
roughly how long it will take to produce custom ROM after rooting a device ???
Click to expand...
Click to collapse
NOT LONG....
1 month atmost... i have a good friend in ahmgsk and he just needs a buzz
and he complile what ever we needed for running the rom !
and if he do this ill maybe donate him me own tattoo donate ...naa ill post a pack for the dude with the tattoo. i guess..witch me self had for free by the way ..with the wish of me rooting it ... someone else did it .. HECK..
to late ..
THX Marsdroid
To easily flash ROMs, we'd need a S-OFF Bootloader and also a custom recovery that enables us to actually flash the ROM to the phone.
However, since HTC tried to play 'god' with our Tattoo/Click and bar off any root exploits or custom ROMs, it's tricky. We've had to play around with root, and now we've got the system partition writable, soon we can get flash_image to work.
Myself, I expect to cook a community ROM (CoburnROM 360) when we've got all the tools in place.
Online kitchen/automated tools like the Relentless Rom Roaster is a plus, but not a essential item to have on your arsenal. Real Devs use Linux and the command line!
Now, it's just a matter of playing the wait game. Dream about all the customizations in a ROM you'd like, and when the day has come (it most likely happen in the near future! ), we can plop the update.zip on the MicroSD, reboot into (custom) recovery and let the fun begin.
This is exactly the reason why I'm holding off with making root permanent on mt phone. I'll wait till everything becomes stable and more can be done with root, i.e. installing custom ROMs.
sheik_yerbouti said:
This is exactly the reason why I'm holding off with making root permanent on mt phone. I'll wait till everything becomes stable and more can be done with root, i.e. installing custom ROMs.
Click to expand...
Click to collapse
Good idea. Mine at the moment is temp root, I jsut run the exploit and do the export commands to get a shell, instead of hardwriting su in my Tattoo.
is the custom ROM ready ??? i want to test it on my tattoo simultaneously i wanna root it at that time itself... so if you succeed in preparing cooked ROM, pls post it here for testing.
i will test it for you.... cant wait for its release... keeping my fingers crossed coburn.....
manuvaidya said:
is the custom ROM ready ??? i want to test it on my tattoo simultaneously i wanna root it at that time itself... so if you succeed in preparing cooked ROM, pls post it here for testing.
i will test it for you.... cant wait for its release... keeping my fingers crossed coburn.....
Click to expand...
Click to collapse
The more you refuse to spend even 3 or 4 minutes to read through the forum, the longer you will have to wait for a custom ROM because you are stealing our time to develop one because we have to answer senseless posts. This time I won't post the link you are looking for because it will take you around 10 seconds to find Coburn64's thread - its just one view!
-bm-
@bm, there is no link for downloading a custom ROM buddy, i saw coburn's thread..... but there is no mention of when we can expect custom ROM.....
anyway, i thought you might be knowing the approximate date.... ok, i will wait till you receive.... dont waste your time.... carry on with your good work. i appreciate your contribution towards this project..... keep up the good work bro...
Seek and ye will find gold

Development resources?

I am looking to learn to develop for this phone. After so many people have left we are in desperate need.
I have experience coding on PC and light experience on WINMO 6....
I am reaching out to the community for resources on how to learn to develop for the Vivid. Any Direction will be appreciated.
I would also be willing to learn to develop for this phone. I'm a computer science student at MIT and have coding experience, but have not done anything related to Android so I'm not sure where to begin.
Kraizk said:
I am looking to learn to develop for this phone. After so many people have left we are in desperate need.
I have experience coding on PC and light experience on WINMO 6....
I am reaching out to the community for resources on how to learn to develop for the Vivid. Any Direction will be appreciated.
Click to expand...
Click to collapse
You can try this kitchen. It kind of works if you start from custom Rom as base.
At least gives you idea of what you have to do. You can than develop more depending on how good ur Unix or scripting skil are
http://forum.xda-developers.com/showthread.php?t=633246
Sent from my HTC Raider X710e using XDA App
WARNING: If your HTC device is not listed below, and it does NOT use a 'YAFFS'-based filesystem (e.g. usually the mid-range and high-end devices don't use YAFFS), do not attempt to flash a ROM that you built with this kitchen. Instead, you must do the following if your device is NOT listed:
Create a file under the kitchen's /tools/edify_defs folder, with the name being the same as the value of ro.product.device (found in your device's /system/build.prop file).
See the template file in the edify_defs folder to see how to set the mount points inside the file you created. Look at the other files in that folder for examples on how to do it.
Click to expand...
Click to collapse
Since the Vivid is not listed as one of the compatible devices, do we need to do this? I saw the Rezound on there is why I am asking
I too am going to give it a stab. I have experience working with Cyanogenmod as well as a ton of C/C++/Unix/Scripting/Driver experience. Lets see what we can make.
I used it and there is nothing device specific stuff that should matter
Sent from my HTC Raider X710e using XDA App
No dont grab some one elses...incorrect....Grab the kitchen from dsixda grab an ruu run it till it opens to first screen dont install or go any further...goto search,search your c drive for rom.zip....copy this file to somewhere else on your computer and your started....
WC
zombie.raised said:
You can try this kitchen. It kind of works if you start from custom Rom as base.
At least gives you idea of what you have to do. You can than develop more depending on how good ur Unix or scripting skil are
http://forum.xda-developers.com/showthread.php?t=633246
Sent from my HTC Raider X710e using XDA App
Click to expand...
Click to collapse
I would appreciate any suggestions for resources too. I have not programmed in many years but I figure, what the hell, might as well give it a go.
Sent from my HTC PH39100 using Tapatalk
True platform development resources are slim right now...
Read this website http://www.kandroid.org/online-pdk/guide/index.html for a decent but outdated overview of platform development and bring-up.
Check this post from Cyanogen http://forum.xda-developers.com/showthread.php?p=6243873
At the bare minimum do what WC said but I don't recommend you use someone else's custom ROM as your base for a multitude of reasons. If for no other reason, you'll inherit any flaws they may have unknowingly introduced and you won't understand the changes they implemented to make the improvements they made.
I'm a little rusty, but my team and I develop on the HTC Dream/Magic. I own about 6 devices right now and just gave away 3 others to a developer on my team. It's kind of funny, even though I've owned all these devices, I've never really developed on any of them since there's always so many other people already doing so.
But since everyone left and there's no competition right now, I think I might start developing again, I just need to know what you guys want and I'll see what I can do.
Sent from my HTC PH39100 using Tapatalk
Infinimint said:
I'm a little rusty, but my team and I develop on the HTC Dream/Magic. I own about 6 devices right now and just gave away 3 others to a developer on my team. It's kind of funny, even though I've owned all these devices, I've never really developed on any of them since there's always so many other people already doing so.
But since everyone left and there's no competition right now, I think I might start developing again, I just need to know what you guys want and I'll see what I can do.
Sent from my HTC PH39100 using Tapatalk
Click to expand...
Click to collapse
I'd love to see some new guys giving it a try. I wish I could invest the time and had the knowledge to do it myself.
I think most are just looking for a good solid ICS rom, with Tethering working... anything else would pretty much be a bonus. I think "MOST" would be appreciative of pretty much anything at this point
Wild Child said:
No dont grab some one elses...incorrect....Grab the kitchen from dsixda grab an ruu run it till it opens to first screen dont install or go any further...goto search,search your c drive for rom.zip....copy this file to somewhere else on your computer and your started....
WC
Click to expand...
Click to collapse
That was dsixda kitchen , I think that is pretty good and now quite a few people use it even now.
zombie.raised said:
That was dsixda kitchen , I think that is pretty good and now quite a few people use it even now.
Click to expand...
Click to collapse
He was making a point to not use someone's custom rom
Sent from my HTC PH39100 using xda premium
If that's the case, than from my experience it is a bit harder for someone with no knowledge to start with stock ROM. Out of the box the kitchen did not work very well with any stock ROM. It was easier to tweak a custom rom because the DEV had fixed the issues which I don't know if every one can solve. e.g some may just struggle to get system.img to work in this kitchen , again that can be trivial for some to fix and some noob's may find it hard.
zombie.raised said:
If that's the case, than from my experience it is a bit harder for someone with no knowledge to start with stock ROM. Out of the box the kitchen did not work very well with any stock ROM. It was easier to tweak a custom rom because the DEV had fixed the issues which I don't know if every one can solve. e.g some may just struggle to get system.img to work in this kitchen , again that can be trivial for some to fix and some noob's may find it hard.
Click to expand...
Click to collapse
It's all trial and error my friend. Later tonight when class is over I'll try to create a rom from the Telstra 3.5 RUU. I tried the ICS stock rom, but I wasn't able to deodex about 50 or so files. Hopefully this time around the process will go smoother.
Sent from my HTC PH39100 using xda premium
Thats not learning then,thats taking someone elses work,start as everyone else did,everything is out there to be [email protected] all have to learn somehow,but the way your saying isnt the correct way to learn...its called kanging,then tweaking something here and there and calling it your own creation....truely learn something and start from scratch,we all did,so why would you expect it should be easier for you?
zombie.raised said:
If that's the case, than from my experience it is a bit harder for someone with no knowledge to start with stock ROM. Out of the box the kitchen did not work very well with any stock ROM. It was easier to tweak a custom rom because the DEV had fixed the issues which I don't know if every one can solve. e.g some may just struggle to get system.img to work in this kitchen , again that can be trivial for some to fix and some noob's may find it hard.
Click to expand...
Click to collapse
As far as resources go, download the kitchen, and DO NOT use it, rather analyze how it works. Look over the scripts and see why it does what it does, if you don't understand something, google it.
That'll help some of the beginners here.
Sent from my HTC PH39100 using Tapatalk
We all are having issue with deodexing the ics,att has **** all over the place....this is why i suggested a lower build as per your inquiry...
doktor buknasty said:
It's all trial and error my friend. Later tonight when class is over I'll try to create a rom from the Telstra 3.5 RUU. I tried the ICS stock rom, but I wasn't able to deodex about 50 or so files. Hopefully this time around the process will go smoother.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
zombie.raised said:
If that's the case, than from my experience it is a bit harder for someone with no knowledge to start with stock ROM. Out of the box the kitchen did not work very well with any stock ROM. It was easier to tweak a custom rom because the DEV had fixed the issues which I don't know if every one can solve. e.g some may just struggle to get system.img to work in this kitchen , again that can be trivial for some to fix and some noob's may find it hard.
Click to expand...
Click to collapse
I wouldn't consider that development and the OP asked for development advice. My previous post provides ample information to "do it the right way", team that with extracting your source from RUUs and you've just become a real dev. You will possess the necessary knowledge and tools to create your own ROM.
Then after you create your ROM if you still have problems that another dev has resolved you can respectfully contact that dev for guidance on what they did to resolve it.
That's the way I would want someone to use my work anyway.
Read this website http://www.kandroid.org/online-pdk/guide/index.html for a decent but outdated overview of platform development and bring-up.
Check this post from Cyanogen http://forum.xda-developers.com/showthread.php?p=6243873
Use the aforementioned kitchen to extract "stock" carrier base ROMS if you choose not to build from source.

[Q] [Ask/Discussion] Something in my mind

Hey all sorry for this silly questions, but I very interested about this fact that most of rom developers that I have seen is forget to test their rom before publishing to us. I seen their included many futures in their rom, but in the last sentences is always say "report to me immediately if you found some bug"
I am not developer but I very interest about their job, they do the best for us without any salary. we will appreciate their job. we know they were working hard to do that. But this questions is always come and I want to know what is happened;
1. that is not possible to checking our jobs when we finish to build something or develop a Rom?
2. and about Bug, that is bug are coming with different situation perhaps different type of phone or hardware or maybe production code
I know someone there can give me explanation, please help me
generally, dev. do test their Rom before released it.but not everything,maybe concentrate on basic and new feature in their Rom.however,nothing is perfect.more features will lead to more bugs.sometime,if u add 1 new feature,its will bring bug to others.so they need our help to report it.plus they give it to us for free so we should give something back in return,I guest.
and sometime bugs happen. just because someone don't read a thread carefully
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
I am sorry admin. I think this can be made to discussion tread. I will waiting another responses for this read. likely some explanation or maybe a way or process to develop a roms
If I get you right.
1. Developers DO TEST the ROM before they release it. Thats why as you can see it took sometime to be released as they want to make sure that the ROM is stable. (I dont know If all devs do that but Im sure most of them do, some ask for testers.) The reason why they ask to report you BUGS is that they cannot test all the component and esp the apps that we install. Basically they only test the default component or features that the ROM has. Issues arise because of the user setup on there phone. We have different setups thats why we have different problems, also 1 reason is how you install the ROM on your phone we may have same phone specs but believe me bugs you might encounter will not exist on mine. So in general this is want the dev to do to address those issues that users find while using the ROM. If you want the developer to test it all then dont expect the ROM to be release frequently. Actually you know the answer and was stated on your no. 2.
likely some explanation or maybe a way or process to develop a roms
Click to expand...
Click to collapse
starts from here.
Different people = different phones = different experience/bugs...even on my GingerZaraki, I have no problems with wifi on alfs but many others complained of wifi errors...I have a team of 6 so stuff like this can be tested out so the chances of others having the same probs are less. Hope that answered your question
Well its kinda impossible to navigate through all the system to discover any possible bugs, right? And I agree with Rohin.
Sent from my X8 to your screen
Well I understood know. so our phone is make multiple problems with some rom. One more time, what is the best guys, Install a rom from original rom or can directly for another. for example, let's call my original Rom (eclair) is ROM A, old costume ROM is ROM B, and the New one of ROM is ROM C.
now I used ROM B and wanna to try new ROM C. that is good if I installed directly from ROM B or make recovery first to original ROM A, before installed ROM C. Sometimes I have problems or boot lop, and sometime is fine ?
Err.. full wipe after rom B.
Sent from my X8 using xda premium
syafwan said:
Well I understood know. so our phone is make multiple problems with some rom. One more time, what is the best guys, Install a rom from original rom or can directly for another. for example, let's call my original Rom (eclair) is ROM A, old costume ROM is ROM B, and the New one of ROM is ROM C.
now I used ROM B and wanna to try new ROM C. that is good if I installed directly from ROM B or make recovery first to original ROM A, before installed ROM C. Sometimes I have problems or boot lop, and sometime is fine ?
Click to expand...
Click to collapse
you dont have to go back to a (eclair) everytime you change rom,just full wipe at cwm while using b(old rom) and install your c(your new)
i liked the a,b,c

Categories

Resources