Cooked Security - Hero, G2 Touch Android Development

Firstly I want to stress that I am not making any accusations or (as far as I know) experienced anything like this, it's just a thought I had.
So my question is what's to stop an unscrupulous cook from adding something to a ROM that would steal account passwords? Sorry if this is a dumb question but I'm not a cook.
Thanks.

Very little, I guess.
I doubt anyone else goes to these lengths, but I always check the entire list of apps and their permissions (in Android) on install of a ROM.
But that's not foolproof, and takes ages, so often I do a diff of the file system to see if any dodgy apks are there.
Droidwall in whitelist mode will help against a malicious app, but a kernel based exploit would get through all of this
So personally I stick with modaco Rom, and tek kernel, as Paul & tek are trusted and have a good track record and history here and on modaco forums. So I guess just stick to major trusted chefs or wait for official. And be wary of new ROMs and chefs, not that we should distrust them, but just be wary till they build up a good reputation.

Thanks for your reply- you mentioned some things I had not considered doing.
I am currently using the Modaco 3.0 ROM and have been using it since 2.6 and have had no issues with it, I suppose the ultimate way forward would be to cook your own ROM but I'm from WinMo and wouldn't know where to start not to mention finding the time to learn all this stuff.

RetroFlux said:
Thanks for your reply- you mentioned some things I had not considered doing.
I am currently using the Modaco 3.0 ROM and have been using it since 2.6 and have had no issues with it, I suppose the ultimate way forward would be to cook your own ROM but I'm from WinMo and wouldn't know where to start not to mention finding the time to learn all this stuff.
Click to expand...
Click to collapse
You're in luck, we are in the same boat.. I made an easy kitchen for new Android cooks:
http://forum.xda-developers.com/showthread.php?t=633246
Regarding security, yeah I would go by reputation... but the best thing would be to cook your own ROM once you know what you want in a ROM, after trying out custom ROMs made by others.

Sweet! I'll check it out, thanks.

Yeah. Cooking your own seems the best bet.
One idea I did have. How about a thread where a trusted user or admin puts in the MD5/CRC hashes of the stock apk files, and makes an MD5 file. Then, users could check any suspect apps to see what (if anything) isn't stock. ie. a non-stock SMS app might be a bit suspect etc.
Although this would have a load of false positives for anyone who just edited a picture or icon within an apk.
Similarly, a catalogue of boot.img MD5 sums (the part that contains the kernel ramdisk) would allow users to check their boot.img looks legit before flashing.
The biggest issue here though is how to make sure that it's kept up to date, and that it's verified in some way so a malicious user couldn't add their own MD5 for their malicious app/kernel to the list, thus giving it trust.
Maybe better just learning to cook a rom... It's pretty easy once you get the hang of it. Just stay away from SPL and Radio until you know what to do.

Yeah I thought about getting cooks to hash their stuff but I don't think there would be much take up and like you say the false positives would be an issue.

anon2122 said:
Very little, I guess.
I doubt anyone else goes to these lengths, but I always check the entire list of apps and their permissions (in Android) on install of a ROM.
But that's not foolproof, and takes ages, so often I do a diff of the file system to see if any dodgy apks are there.
Droidwall in whitelist mode will help against a malicious app, but a kernel based exploit would get through all of this
So personally I stick with modaco Rom, and tek kernel, as Paul & tek are trusted and have a good track record and history here and on modaco forums. So I guess just stick to major trusted chefs or wait for official. And be wary of new ROMs and chefs, not that we should distrust them, but just be wary till they build up a good reputation.
Click to expand...
Click to collapse
You might come in for a surprise if you think checking apks is safe.
A simple keylogger (there's one which will compile and work for android - DON'T PM me about the name, I won't tell you) added to initrc, zipped log file of key catches and a simple ftp of the file once every 6h will do just fine.
For additional privacy concerns, you can always catch the entire screen (but that'll slow the system too much), or even zip and ftp the /data/data ...
Possibilities exist.
For the real adventurous, you might always add the code/function to one of the programs which are compiled while aosp'ing, for example, busybox, dropbear, whatver... Share that in a rom, and there you go.
Checking apk perms, scripts or whaever won't do you any good in this case.
This is why you try new roms from "amateur" chefs at your own risk. Believe me, bricking is the least of your concerns when trying new roms from unknown "devs"

I think this just further renforces the 'cook your own ROM' route. Don't worry I won't PM you about it as I'm not looking to steal people's passwords just looking to try and protect myself, I'm getting paranoid now and thinking about going back to a stock ROM :O

Related

Modifying the ROM

I've been reading the forum, and based on the information and the tools there I have been able to modify my extended ROM, which is great. Now of course I'd like to modify the main ROM as well, but despite the many hours I've spent searching the forum, I can't find the necessary information to do it. There's always something essential missing, something which probably is obvious to a programmer, but not to a normal user. As I've been able to modify the extended ROM, I guess I should be able to modify the main ROM too. Who can point me in the right direction?
from what i understand it's not even 100% possible with xda1 since people cant seem to make the extracted files back to a nbf file
and there are no tools that i know of that even extract the main rom from a xda2
As I understand it, when you upgrade the operating system, you're actually modifying the ROM. Some people here like to call it to "flash", I think, and there are a lot of messages about it in here. I just haven't found the information necessary to do it. I want to modify the ROM on my XDAII.
no the operating system is the rom which is in a eeprom in the device
when you flash the rom you replace the operating system with the new one
when you say modifying it mean more in the way of exchanging different files inside the rom
but if you just mean flashing the rom with a newer then here is a guide
http://wiki.xda-developers.com/wiki/HimalayaRomFlashing
What does EEP stand for? How many ROMs are there?
I've seen a ROM created here for the XDAI, containing more programs than what the devices normally come with. I would like to have a ROM on my XDAII containing the programs I use, so that I don't need to reinstall them every time the device is hard reset. Isn't this possible?
What does EEP stand for?
Click to expand...
Click to collapse
huh what does EEP have to do with this ?
suppose it could stand for
Executive Excellence Publishing
or
European Environmental Press
how many roms there are i think there are 1.5 1.6 1.66 and 1.72
about extra programs then they are not! in the rom they are in the extended rom any CAB file you copy to the extented will install after automatic after a hardreset
you should take a look at the romkitchens ( specifically for xda1, but can be made for xda2 as well ).
and mkrom, and the other romtools
EEPROM stands for "electrically erasable programmable read only memory".
this is sort of the predecessor of flash memory.
"electrically erasable programmable read only memory" sounds like a contradiction, but thanks for that, it makes more sense than EEPROM.
What about all of us users who don't have a Unix machine? I suppose we're stuck with the original ROM then, and have to install our programs over and over again for every hard reset. Of course you can put a few of them in the extended ROM, but it becomes full too quickly and you're left with installing the rest of them manually.
well you can upgrade to a newer rom as they come out
like i have 1.66 but if i wanted 1.72 i could upgrade
about contradiction heh yeah suppose so but then if it was 100% always READ ONLY then it would be random was what in it as how the transistors randomly set when it was produced
A newer ROM wouldn't contain the programs I want.
no :/ but it could contain bug fixes for ms and radiostack and such
i suspect that extented rom was made so it would be easier for the phonecompanys' and other 3th party resellers to get programs preinstalled fast without having to mess around too much in the rom
this is at the cost of memory though
but then some programs dident like to be in the rom i believe here i mean if setting files were places in the rom aswell and the program could not write to the setting file
mkrom also works on cygwin under windows.
( now I also wrote this in the wiki page )
Isn't that just for XDA I?
it works for windows ce in general.
that doesn't mean that there is no work involved in getting it to work, but it is possible to make it work for the xda2. I use it to build custom roms for the devices we sell, that is why I wrote it in the first place.
What's cygwin?
How much space is there in the ROM to add extra programs? In the ROM that this forum developed for XDA I they added quite many programs from what I could see.
http://www.google.dk/search?hl=da&ie=UTF-8&q=cygwin&btnG=Google-søgning
Thanks for that, Rudegar.
To Itsme: I don't mind the work, but it looks like its written for programmers and that if you're not a fairly skilled programmer, you wouldn't be able to do it.

NOOB's Kitchen

Hi eveyrone.
Background: I have been playing with the new Manilla from XBMod, but in doing so I have had to change my ROM. Previously was on a DUtty v4 ROM which I loved as it was a simple clean and fast ROM.
Now compared to Dutty's all other so far are Bloated and/or slugish (even before I put the manilla2 on).
Anyway I decided to see what it takes to make my own. I looked into it and found a nice simple basic tutorial with video here: http://forum.xda-developers.com/showthread.php?t=413782
Now this is really basic. I do need to learn a bit but I need some help in finding some information. Little things like how to edit the registry or how to change the boot image. Also need to find all the updated HTC apps, and a list of what HTC apps are available and/or ported.
Before someone tells me to use search or "google is your friend" I know that.
I can find out what each package does before I remove them and such. I can also find out how to do allot of these things too, but if you actually use the search also then you will find nearly everything is based on modifying an already installed ROM and not doing it in the Kitchen.
On top of all this I doubt I am the only person looking for a clean fast ROM so I will be releasing this to everyone. I would appreciate any suggestions for what to include and what registry edits to do. And would really appreciate a master chef coming by and helping a new apprentice chef.
Much appreciated for anyones help. (Remember I havn't asked for others to do it, I am asking for some help to learn it.) Lets just hope I don't burn anything...... .
Nothing?
No one wants a Simple Light Upto date ROM??
Kinda funny isn't it.
If I just waited around and asked who had what and all that, I would be flamed to a crisp and get told to read and use search. Just so you know I just used search for "OEM HTC" and got NOTHING.
I have been using the forums for about 6 months now and now I have decided to put my little bit of effort in, no one is interested in helping...
I always say that I only help those whom help themselves. I have and am currently helping myself, but I do need a little hand mainly to point me in the right direction.
Anyone?
Doesn't anyone want a simple ROM that is mearly a set of performance tweaks and updated OS and Updated Default HTC Apps?
Here's you answer - download one of teh full kitchens available (like Sulliers or Mondilv) and make it yourself.
Other way - download latest OEM rom (there's thread for that), ervius kitchen, and cut away to your liking - you will have your "latest light rom".
This is exactly what it is about. Either be ready and donate to the chefs who do such things (cook for demand for payment) or get behind the keyboard and start cooking. it's not that difficult...
This is how I started - got the kitchen, and step by step I go forward. I can't call myself a cook - I only know how to tweak a bit little things, but I'm learning. I suggest you start too
If you are searching for "clean, fast ROM" look no further than Mondilv's kitchen - probably the fastest Rom available now (if we are to trust Pietrucci's benchmarks, and I see no reason why not). Since it;s a kitchen you can do whatever you want to it. And if you are asking "how to edit registry" then maybe your searching skills aren't that good... This like the most basic thing....
Happy cooking!
Good to see people actually read.
At no point did I ask for a ROM. I do recall mentioning that I have downloaded a kitchen and am playing with it.
I did mention that I have searched and my skills in searching are perfectly fine. Considering that fact that I have found the registry information but NOT in XDA.
THe problem with XDA is that if you are to be succesfull in a search you must already know what you want to find (and therefore know the terminology to search for) which then means why search at all seeing you already know. And if you happen to find something you have to read the thread for a week to find the only single post within it that actually gives you an answer.
If you had read my first post properlly and understood it, you would realise I am after information TOO LEARN IT...... but maybe I'll take your suggestion and LEARN it instead.
It really pisses me off when people reply withou fully reading the post, and then tells me exactly what I said I am doing.
For all you know I could be a potential contributer to these threads and you have just destroyed my respect for the people on these threads. Thankyou for your lack of any real help.
Oh and one last thing, I was wrong with the last bit of my first post.
If I ask for the ROM I get flamed, If I ask for help to learn to build a ROM I get told to make a ROM or download one.
Catch 22 around here. Can't ask for help and can't get help. I wanted to build one but if this is the **** I am going to cop just cause I want to learn something and contribute, then its not worth jack ****.
And who are you to say if I have or havn't donated to other ROM Builders.
I would love to try your basic clean ROM, without all the pre installed applications. I have been looking for an up to date naked ROM, but haven't been able to find one.
Good Luck!!!
Well my intention is not a "Naked ROM" but a bare essentials one.
Just updated versions of all the apps that come with a HTC ROM and update OS Core, .NET etc.
Bare Minimum Apps.
good luck man. hope its super fast too.. and stable.
Can someone please point me to an UPDATED list of HTC OEM App Version and hopefully downloads.
I don't mind Ripped stuff, like from TouchFlo2 etc, but I want to leave out beta buggy stuff untill they are are fixed. For example I would want HTC Notifications as it seems to work well (unless I am just lucky) but I won't put in the TouchFlo3D 2 as it is still buggy and unstable.
Oh and VGA versions if possible for my Touch Diamond
Oh and were can I find a 21xxx+ version ROM that I can use?
Hmm, so I want to help, and the best you can do is smirk at my recommendations, and you just carry on:
can you point me here, can I have that or this, and oh, can it be VGA, and possibly with chocolate?
Man, I'm sorry, but there is something wrong. All the info you are looking for IS on this forum. I can't believe that you searched and didn't found. You either search the diamond forum, or use general forum search (which is google) and you just follow the links.
I don't want to belittle you nor argue with you. But just take a second and look at the way how ALL internet forums work. The first thing you do to gain credibility on any forum is to search, learn, then try to help. The last thing you do is to show up, and ask for links "on a platter" in rather demanding manner, and then criticize the answer. I just had a look on your posts and it seems that this is what you do. You repeatedly ask for ready solutions, and when people tell you to search, you are annoyed, or ask "does anybody read posts on this forum?"
I will say just this - google "netiquette" or "how to behave on internet forums".
Good luck in your search for perfect ROM for you.
And here you go not providing any form of help at all.
You say If I did search I searched the Diamond threads or used the Google search..
I have used the google one yes. And I have used the built in search searching for DIamond threads yes.
Now you imply that searching the Diamond is wrong??? I am own a Diamond so why not search the diamond threads.
This is exactly what I am talking about regarding the useless comments of "search the forums" crap I keep reading against any noob.
Instead of pointing people in the right direction you guys just simple say search.
There also seems a limit of more than 3 letter word length to search in the forum search. Cause each time I search OEM or HTC or HTC OEM then it returns No results.
Ontop of all that if and only IF I do actually find something then I have to spend hopurs upon hours readying all the Good job, well done comments before I find the one tiny little comment that actually has the answer. At that rate, for a noob trying his hand at cooking it would take 6 Months to actually find all the answers.
And now you come back and tell me to search, and worst still you tell me that searching for Diamond Rom Development info in the Diamond forums is wrong also. Were was the part that told me were to search?
it seems quite some posts are missing here... xda-developers did a restore from a backup or something after the mess last night? .
Anyway, eangulus. This is what I have so far:
- Started with a stock 2.03 WWE ROM.
- Put in a 21042 SYS + XIP (so it's now 21042 build)
- After that ripped out some stuff:
- NetCF (because it's 2.0 now I installed 3.5 from CAB, we need the OEM for it)
- Manilla
- Opera (I guess we want a newer build)
I also needed to remove it from the 'auto setup' list
- Windows Live
- MP3 Trimmer
- RSS Hub
- AdobePDF
- Cyberon VoiceSpeed dial
- Google Maps (Because we want a newer build or nothing at all)
Also needed to remove it from the 'auto setup list'
- JBedJava
- ZIP
- Office OneNote
- SampleMusic
- SQLCeMobile (Leave the SQLCE engine in)
- Transcriber
The whole thing build nicely, the final .nbh is 86.5mb.
There are a lot of things that can be stripped more ofcourse, and it doesn't have
any 'tweaks' included yet. Stuff I still gotta learn / try out.
Also converting cabs to oem/packages is on the agenda , and see what is easy from
the rhodium / topaz oems to include.
After the flashing and first boot I installed the older STock keyboard (bigger T9) because I still prefer it, installed newer google maps and installed the latest Rhodium Manilla from xboxmod. Runs fine and speedy (still can be faster by cooking it in though).
The notification enhancement works by installed a certain cab afterwards (not the one included in Rhodium Manilla), but Menu Enhancement and the 'manilla start menu' won't work.
My 21038 build that I was working with in the beginning seems just broken or something, because the 21042 XIP/SYS I used worked flawlessy. So I was doing it ok all along, just had broken files .
So, what now from here?
To get you a bit started:
In the end I used bebe's kitchen (http://www.darkforcesteam.com/showthread.php?p=3560). You need to create a user on that forum and wait till they 'approve' you to access the thread though.
In the thread there are a couple of video's posted how to get you started. I watched them, understood them and then started cooking and it worked . I don't know if bepe wants his files freely posted everywhere so I'll let you to get them yourself.
The ROM I used I actually downloaded from the HTC site (http://www.htc.com/www/SupportDownload.aspx?p_id=133&cat=2&dl_id=483). Entered my serial number and got the .exe with the ROM (the ruu_signed.nbh can be extracted by using WinRAR from the .exe).
The XIP/SYS I used are from here: http://forum.xda-developers.com/showthread.php?t=497586
Bepe's kitchen works with a OS.nb files (not .nbh files) so I used NBHUtil to extract it from the .NBH. NBHUtil was included in another kitchen, I got it from there. The kitchen it was included is actually an 'extended' bepe-kitchen, so you might want to play around with that one too: http://forum.xda-developers.com/showthread.php?t=469420.
But in the end, I only used NBHUtil.exe from it .
In his video on how to port a newer build to your kitchen, he uses a complete newer ROM as a starting point. He extracts the XIP/SYS from that. If you do it like me, you don't have a complete newer ROM but only a XIP/SYS downloaded from this forum. They give you a os.nb.payload and a SYS folder. So you skip the part that extract those from a ROM and just instead use the files downloaded.
And that's pretty much it. With those files and the (short!) video tutorial's on Bepe's thread in darkforcesteam.com I managed it make something. (video on starting a kitchen from a ROM, and a video on how to port the XIP/SYS from another ROM to your kitchen). Try it, if you get stuck I'll help you. It isn't hard at all!
..........
sorry
razkal1 said:
..........
sorry
Click to expand...
Click to collapse
or
razkal1 said:
here is .net 3.5
delete your ntcf forlder in sys and replace with this one
Click to expand...
Click to collapse
I actually have it already but thanks for helping out!
Trying out bebe's kitchen and trying an Upgraded OS build as we speak. Not as friendly as some of the other kitchens but with the vid's it is pretty straight forward thou.
Any luck in finding an updated list of HTC OEM Version Numbers and exactly what HTC OEM apps are available for us to package into it?
Im not going to do the manilla yet as I think its still a fraction too buggy. THe main one being atm is being out by 1 hour.
Once its much more stable and bug free then I'll package it. I do want the new notifications and menus thou. they seem to be workig OK.
ALso not sure if this is a HTC app or not but I have seen a new Wifi connection tool. It gives you a list of Wifi available in a Manilla Look, you then just click on one to connect. Do you know what that is called and who does that?
Also do I have to convert the .nb file to a .nbh again?

Upgrade Rom Without Data Loss...Is it remotely possible?

I recall reading a little while back a message (somewhere, sorry for not remembering) that there was a way (if i remember correctly) to make a ROM Update Utility that wouldn't harm the data on the phone (excluding MicroSD which we have to remove when updating). I don't know the truth to this, but the idea behind being able to upgrade roms and keep personal data (and maybe installed applications) is cool. I know that whenever I upgrade roms the biggest part is reinstallation of my programs (it gets very annoying!). Its not so annoying that i want to toss my Dash against the wall, I just don't like having to do it over and over again (especially with new roms and updates coming out).
Essentially, having to reinstall, and re-setup, my phone with each ROM update is really what keeps me from upgrading a big part of the time (ie: going from the Energy Rom to Ookba's new 3vo ROM). Is there any way to be able to make this process of reinstallation easier?
Have a look here:
http://forum.xda-developers.com/showthread.php?t=520009
orb3000 said:
Have a look here:
http://forum.xda-developers.com/showthread.php?t=520009
Click to expand...
Click to collapse
That was exactly the link I had looked at (and apparently not too long ago either). I read through a good part of it, but its past Midnight here, and I am drowsy beyond belief , so I didn't make much sense of any of it. Essentially I don't cook roms, and it mentioned something about the chef having to make the RUU in a specific way (correct?). Is this in our near future?
Da_G alread made a test ROM and updated the ROM sucessfully for the Raphael. I'm sure our smartphones aren't too far from getting it either. They just have to make some tools for us chefs to use it in our kitchens now Soon.
NRGZ28 said:
Da_G alread made a test ROM and updated the ROM sucessfully for the Raphael. I'm sure our smartphones aren't too far from getting it either. They just have to make some tools for us chefs to use it in our kitchens now Soon.
Click to expand...
Click to collapse
Awesome! Its great to know how active this community is (even for an old-er phone like this )
Keep up the work all you EXCELLET chefs, devs, hackers, programmers, and any other division of making this phone better

Gruessle -> Kaiser Froyo Rom

06/16/2011
The screenshots are not important. This is not a theme!
You can install a theme from here, for example if you like.
The theme it comes with is the:
Go Louncher Classical Theme (The new version of it)
The software installed is also not important, because you can remove it.
Google Market is installed, and you can install what ever you like, just like on your computer.
https://market.android.com
This is the actual Android Froyo operating system for the HTC Kaiser
So, stop asking me for screenshots and software installed, it's not relevant.
And the how to install guide is been posted here
Bug reports are welcome, other then that, I don't wont to hear from you.
Don't post a thank you either, there is a bottom for that, and you can also vote on the poll up there, but install and test it first!
Again Bug reports only, please!​
I been working on this for 3 days straight, and figure I'll share what I got.
Everything seems to be working, except the camera is blurry, but that seams to be the norm.
Included is the rom, radio and kernel
ROM: 2.2.1
Kernel: 2.6.25
Radio: KAISER 1.70.19.09
Panel: 2
Key Map: US Normal
Resolution: 240x320
Storage: Nand & Nand
Most everything is installed in userspace and can be uninstalled or upgraded.
Oh got GO Launcher EX installed (Also in user space)
Credits:
I stole ideas from, and used following tools:
Makers of atools
Makers of NBH creator
HTC Flasher
kallt_kaffe
Krazy-Killa
dzo (dzo's posts wore a big help. just wish he would answer his own questions after he found the solution)
n2rjt
and many more.
@todo
Resize NAND partitions to the smaller system size
Original post and download Links are posted on my blog:
http://press.pzzazz.net
Can you write something more about this? Is this your system and kernel(compiled yourself)? Any changes?
MaRekRM said:
Can you write something more about this? Is this your system and kernel(compiled yourself)? Any changes?
Click to expand...
Click to collapse
Yeah witch apps are include. Some yours tweaks or etc... ???
MaRekRM said:
Can you write something more about this? Is this your system and kernel(compiled yourself)? Any changes?
Click to expand...
Click to collapse
That sounds like a trick question.
Yes, at first I compiled everything my self but then to resolve bugs, I looked at other systems and basically stole stuff from them to fix my bugs. In other words, I can't take all the credit, it was a community effort.
Neo2SHYAlien said:
Yeah witch apps are include. Some yours tweaks or etc... ???
Click to expand...
Click to collapse
I removed most everything from the system and installed it in user space. So the system is very lean. You can uninstall what you don't like.
how is the rom?just waiting to see
gruessle ...!! thanks for your efforts in getting this done... I been looking from long time to install Android on my HTC TyTN II. However i was not able to get the proper build...
can you share the screenshots of the build which you provided as well some steps at high level on installing this..
Thanks in advance.
Please, I don't really understand how to go upgrade this. I find it hard to do. Is everything needed packaged in this download, or please can u list things needed to change to android. I'll appreciate your response.
tundelogic said:
Please, I don't really understand how to go upgrade this. I find it hard to do. Is everything needed packaged in this download, or please can u list things needed to change to android. I'll appreciate your response.
Click to expand...
Click to collapse
here is the howto
http://forum.xda-developers.com/showthread.php?t=680518
kkp said:
gruessle ...!! thanks for your efforts in getting this done... I been looking from long time to install Android on my HTC TyTN II. However i was not able to get the proper build...
can you share the screenshots of the build which you provided as well some steps at high level on installing this..
Thanks in advance.
Click to expand...
Click to collapse
The screenshots are not important.
This is not a theme.
You can install a theme from here, for example if you like:
http://golauncher.goforandroid.com/category/themes/
The theme it comes with is the:
Go Louncher Classical Theme (The new version of it)
The software installed is also not important, because you can remove it.
Google Market is installed, and you can install what ever you like, just like on your computer.
https://market.android.com/
This is the actual android froyo operating system.
Anyone else having trouble getting the kernel to install?
I get to 33% and the phone reboots...
Radio installed fine even though I was already using 1.70.19.09, just to be sure I installed everything in the package.
Installed HardSPL 3.34 and a WinMo 6.1 rom (custom) to see whats wrong. Installed L1q1d's kernel and goes right in like it should.
Checked .NBH with NBHCreator and only found 1 thing wrong: kernel set to Eclair instead of Froyo. Changed to Froyo and saved, attempted reflash and still won't go in...
;(Losted);
I also tried to install this kernel but I can't. Flashing in hardspl after few second give folowing error:
00018003
Os Fail
Update Terminate
UPDATE Fail.
Changing parameters in atools not helping. Every another kernel is flashing without problems so it's not phone fault
Gruessle, thanks for your efforts! I want to try your rom but being a noob waiting for more comprehensive list of known errors before flashing it to my kaiser.
Ok, quick "bug report":
After working with the kernel pack multiple times I have come to the conclusion that there might be a bug in the actual kernel file itself, throwing a code back to HardSPL and RUU (how I install).
I first noticed a problem in that the kernel was originally set up for a Polaris and had no resolution set. The size of the file should be unimportant as Scoot's newer kernel is in the order of 3.2-3.3MB in size (with the RIL patch installed it gets even larger), this one is 3,099KB, and l1q1d's is almost always 3,092KB.
The second issue I noticed is with the Froyo package itself... It's split up into many files (open the package in 7zip and you'll see what I mean). Normally, the packer has the files all listed inside the .tgz file, this one has the files inside many other files.
I have thus not installed the system on either phone because (correct me if I'm wrong), the kernel contains the basic directories for where everything is installed, and if I were to try and install this package on say, l1q1d's kernel, the phone would most likely crash because the files would not be found, including /system.
If ANYONE wants to dig deeper into this problem, feel free to message me. Personally, I think we've about finished getting all we can from the Kaiser, and much respect goes out to those who have done all the work in the past, but there's always that glimmer of hope that someone will find a way to pack this into a working rom installable through RUU or HardSPL.
I have one last thing to say:
Gruessle, please do your homework BEFORE posting things like this. There are people out there who still depend on this phone to operate as it is their only phone. I Personally cannot afford to go spend $100-200 on a replacement phone if this one goes down (thats why I have 2 of them). If you post something that does not work on the platform that you say it will, please correct it or move it to the proper forum.
BTW, I call shenannegans on one of the 5-star votes... just sayin'.
Your kernel have fake ;/ . rom works great ;D
sorry for bad english;p
PoXFreak said:
Ok, quick "bug report":
After working with the kernel pack multiple times I have come to the conclusion that there might be a bug in the actual kernel file itself, throwing a code back to HardSPL and RUU (how I install).
I first noticed a problem in that the kernel was originally set up for a Polaris and had no resolution set. The size of the file should be unimportant as Scoot's newer kernel is in the order of 3.2-3.3MB in size (with the RIL patch installed it gets even larger), this one is 3,099KB, and l1q1d's is almost always 3,092KB.
The second issue I noticed is with the Froyo package itself... It's split up into many files (open the package in 7zip and you'll see what I mean). Normally, the packer has the files all listed inside the .tgz file, this one has the files inside many other files.
I have thus not installed the system on either phone because (correct me if I'm wrong), the kernel contains the basic directories for where everything is installed, and if I were to try and install this package on say, l1q1d's kernel, the phone would most likely crash because the files would not be found, including /system.
If ANYONE wants to dig deeper into this problem, feel free to message me. Personally, I think we've about finished getting all we can from the Kaiser, and much respect goes out to those who have done all the work in the past, but there's always that glimmer of hope that someone will find a way to pack this into a working rom installable through RUU or HardSPL.
I have one last thing to say:
Gruessle, please do your homework BEFORE posting things like this. There are people out there who still depend on this phone to operate as it is their only phone. I Personally cannot afford to go spend $100-200 on a replacement phone if this one goes down (thats why I have 2 of them). If you post something that does not work on the platform that you say it will, please correct it or move it to the proper forum.
Click to expand...
Click to collapse
1) The kernel doesn't care where you place the files. Right now I use a debian system with Ferora and Gentoo in a chroot. Both work fine with the Debian kernel.
In other words, if you have a kernel that works for you then use that it should work with the rest of the installation.
2) I don't get what you mean with files are "split up into many files", I am just guessing but you must be extracting it wrong. Maybe it's a windows thing, I haven't used windows in 15 years so I wouldn't be able to help you with that.
3) I have included everything you need to duplicate what I got, which works for me, and it appears to work for others too. Now i don't use that phone much, and there might be bugs I am unaware of, but don't tell me it doesn't work at all, just because you can't get it to work.
barmalini said:
Gruessle, thanks for your efforts! I want to try your rom but being a noob waiting for more comprehensive list of known errors before flashing it to my kaiser.
Click to expand...
Click to collapse
barmalini, it appears that a few people have trouble installing the Kernel, but the ROM seams to work for everybody as far as I can tell.
According to my server records the files have been downloaded over 200 times and I have yet to hear a complain about the ROM.
So I would say try to install the Kernel, but if you can't still use the ROM with a Kernel that works for you.
If you have trouble installing from windows you can also try a live CD from debian or knoppix. I installed everything from a Debian system. (Knoppix is based on Debian)
If you don't know what a live CD is then go here for info:
http://wiki.debian.org/LiveCD
PoXFreak said:
Installed HardSPL 3.34 and a WinMo 6.1 rom (custom) to see whats wrong. Installed L1q1d's kernel and goes right in like it should.
Checked .NBH with NBHCreator and only found 1 thing wrong: kernel set to Eclair instead of Froyo. Changed to Froyo and saved, attempted reflash and still won't go in...
;(Losted);
Click to expand...
Click to collapse
PoXFreak,
you are not the only one having trouble, installing the ROM it appears.
I am wondering, are you also using Microsoft Windows to install the ROM?
If so can you try again with Linux, because it worked fine for me.
If you don't have Linux you can use a Live CD
Also if you can't get it to work, try the ROM with a Kernel that works for you.
Please report, I will check back.

[Q] Build ROM straight from Google Source (AOSP)

Greetings all,
I would like to know something that seems to be so simple it hasn't been documented here anywhere.
My question is: How do I build the source provided by Google for my Desire HD?
Yes, there are tutorials, don't point me to them. They either provide you with the AOKP way or the CM way.
I want to build my stuff from scratch.
Is there a generator that will create the necessary file structures for me (in the devices folder)?
Is there a complete list that my rom needs to include in order to make it run on my device (preferably a list of folders I need)?
I know about the vendor files, these are created by a third party. How do I know what vendor files I need to create? How do I know how to name them?
Don't get me wrong, I've used C, C++ and C# for YEARS (I think about 8 now) and I know how to code. I just don't know how to compile android!
It doesn't seem that hard though, I've seen threads where people provide ROMs for the Desire HD without even having the device!
Also, how would I test this and debug it? I don't think it's safe to just flash my rom once I get it compiled to my actual device and possibly brick it.. Can I use an emulator?
I hope you will read this post before answering something alike "Plenty tutorials" or "This can be found everywhere", because it can not. I can only find AOKP or CM ways, I want neither.
Greetings Ultimate-Tester
The only time I know of that this has been achieved for this device is aospX, an ICS ROM on the Inspire 4G forums. It is much harder than you would think. Google does not support this hardware, HTC does. So there was never AOSP source for this device.
Yes, I can imagine how hard it is. As I said I have programming experience, it's just that I don't have it with Android ROMS.
I have built mainly for Windows, also on Ring0 level (which is the lowest level you can get) so I think making drivers is a task I can handle. I am definitely not underestimating it.
Could anyone give me an answer to this line:
Code:
Is there a generator that will create the necessary file structures for me (in the devices folder)?
Is there a complete list that my rom needs to include in order to make it run on my device (preferably a list of folders I need)?
I am very interested in how other people knew what folders to create and what files to put in them. How would the Google Source (envsetup) know which device files to use and what not? Again, can I generate the file structure somehow?
Greetings,,
My suggestion is to use device trees from AOSP-based ROMs that already exist for this device. For example, look in the cfX manifest.xml for Ace-specific stuff (kernel, device, etc.). I personally haven't seriously tried this before, so that's all I can offer.
Okidoki, will do. Then for the last item: Testing.
What will be a safe way to test out my brew?
What will actually happen if I flash a ROM with missing files? I hope there's an underlying catcher that will send something I can see in logcat and fix it that way.. Is this the case, or will I immediately brick my phone once I do something wrong? Do I need to make sure something is 100% there in order to reach my recovery again?
Greetz,,
I'm nor aware of any safety nets. If you're developing, you probably have to be willing to take the risks.

Categories

Resources