i am wanting to experiment with making a ROM for my WFS. i have ROM kitchen, but it doesnt natively support these phones. i have seen a thread or 2 from people that have made a ROM with the kitchen, so i was wondering if the ones that have done it can point me in the right direction to making the mount file needed to make it work right. any help is greatly appreciated, and i plan on sharing my creation here if i get one stable and working.
*note-i tried to ask this question in one of the mentioned threads, but it wouldnt let me post in the dev forums. not a problem, but wanted to explain why i asked here.
easy nuff
I've used it. What carrier you with? And what software number you got fron that carrier [Found in menu settings about phone software info]? What version of kitchen did you install on what kind of platform? Ok I asked three questions, shoot me the answers back and feel free to ask three of your own.
Rob
I have virgin mobile USA. I'm running 2.3.4, and i have kitchen installed on Ubuntu. Not sure what version of kitchen, it was the latest one from the original posting of it.
Sent from my Wildfire S
i was away from my computer when i read your response. my kitchen version is 0.182, the newest one on the official thread.
noted
Ok. What questions do you have about the kitchen?
Rob
just mainly wondering how to get the mount points i need to make the ROM work properly. aside from that unless you have any tips for a new guy, then i think thats all. i appreciate any info you provide, and i also appreciate you responding.
Rom Kitchen
Since you've made it through the setup (I assume). For your stock Rom, (in recovery) run a nandroid, now clear all your data (factory reset) and run another nandroid (just something I like to do to ensure no data will be pulled... Probably not necessary but it gives you your revert to (with data) and your (clean) build nandroid. Now take your build nandroid and open it up with a file manager (ie es explorer). You will want to grab two files from this nandroid... boot.img & system.img (may have called it system.yaffs2.img but just grab it and rename it to system.img). Ok now you have your ingredients for your first build. Connect the phone to your computer (USB storage) pull the two files across to the folder in your home directory that says put Rom here. You are ready to start cooking. Start the kitchen and use those 2 files to build your working folder. You can also try out the various features dsixda has built in. For example lets say you make your Rom rooted, you add apps2sd support, and just for giggles you deodex too. Now any additional changes you want to make can be done in the working folder. So, for our figurative example lets say you wanted to delete flashlite and add a full flash player, download the apk (think there are links to flash player or new market in the app & theme forum), delete flaslite.apk from the system folder in your working directory and paste your full flash player.apk in... Ok you've done all the editing to your working folder that you want to do (lots that you can change, but you want to have a working build and you don't have to make any changes to working folder if you just want to go through the options and read what the kitchen can cook in automatically; as you gain knowledge, you will edit your working folder more and more by hand, but that time will come). Ok start back up your kitchen and make sure all the options you wish have been completed (option 10 I think). Then if it all looks good, cook it (option 99); Also make sure you convert the update script back to updater. Go to the output folder and there you will have your flashable Rom. And thus concludes the lesson for today ;-)
Rob
InsaneDDay69 said:
just mainly wondering how to get the mount points i need to make the ROM work properly. aside from that unless you have any tips for a new guy, then i think thats all. i appreciate any info you provide, and i also appreciate you responding.
Click to expand...
Click to collapse
thanks insink71 for your help. but I think what he mean is kitchen template in 'edify_defs' dir.
there is no template for marvel (I'm stuck too )
example:
Code:
edify_defs # cat vivo
# HTC Incredible S
change_mnt=yes
param1=ext3
param2=MMC
param1_sdcard=vfat
param2_sdcard=MTD
sys_mnt=\/dev\/block\/mmcblk0p25
cache_mnt=\/dev\/block\/mmcblk0p27
boot_mnt=\/dev\/block\/mmcblk0p22
data_mnt=\/dev\/block\/mmcblk0p26
sdcard_mnt=\/dev\/block\/mmcblk1p1
edify_defs #
zero13th said:
thanks insink71 for your help. but I think what he mean is kitchen template in 'edify_defs' dir.
there is no template for marvel (I'm stuck too )
example:
Code:
edify_defs # cat vivo
# HTC Incredible S
change_mnt=yes
param1=ext3
param2=MMC
param1_sdcard=vfat
param2_sdcard=MTD
sys_mnt=\/dev\/block\/mmcblk0p25
cache_mnt=\/dev\/block\/mmcblk0p27
boot_mnt=\/dev\/block\/mmcblk0p22
data_mnt=\/dev\/block\/mmcblk0p26
sdcard_mnt=\/dev\/block\/mmcblk1p1
edify_defs #
Click to expand...
Click to collapse
You are correct, but the tips are invaluable to me as a beginner. I have read somewhere that there isn't a new template to make for the marvel, but I don't know if its true. That was the reason for my asking lol. I appreciate the responses.
Sent from my Wildfire S
edify defs
I didn't make one [and cooked a couple stock roms], but thanks for bringing it to my attention. I'll look into it.
Rob
It may not require one, but according to dsixda it should. Either way you have been very helpful in getting me started with developing.
Sent from my Wildfire S
It doesn't matter if gsm or cdma, what rom version you have or what os you are running to use the kitchen. Then the mount points won't matter either, as the kitchen defaults to mtd which is nand devices. In which the wilfire is one, the only time you need to worry about the mount points is on a emmc device.
Which below is why those files matter for the emmc devices:
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p26");
or
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p26", "/system");
Those are from my hero s rom's updater. Where the nand devices always use something like below:
Code:
format("MTD", "system");
or
Code:
mount("MTD", "system", "/system");
Where the above is from my leansense rom for the uscc wildfire s.
Edit: Here is the marvelc's virgin mobile and uscc mount points. The first is from my device config for cm.
Code:
#dev: size erasesize name
#mtd0: 00100000 00040000 "misc"
#mtd1: 00500000 00040000 "recovery"
#mtd2: 00340000 00040000 "boot"
#mtd3: 106c0000 00040000 "system"
#mtd4: 02300000 00040000 "cache"
#mtd5: 09600000 00040000 "userdata"
#mtd6: 00500000 00040000 "devlog"
Also off topic but just so you guys know the process you used to s-off corrupted the misc partition. Which makes fun for weird and stupid issues. Then also like on the desire and others a corrupted misc partition bricks usb and such. I have the stuff for uscc and virgin mobile, I just have to get it up in a post how to fix it.
Thanks
I figured we had cleared the memory block instead of altering it. That will be a very useful tool. Thanks so much.
Rob
Sent from my marvelc A510c using Tapatalk
2fast4u88 said:
It doesn't matter if gsm or cdma, what rom version you have or what os you are running to use the kitchen. Then the mount points won't matter either, as the kitchen defaults to mtd which is nand devices. In which the wilfire is one, the only time you need to worry about the mount points is on a emmc device.
Click to expand...
Click to collapse
So here's another marvelc wannabe chef that made it to this thread with the same questions. I thought my problem was not having a marvelc file in my edify_defs... thought the _template indicated I needed one.
2fast4u88 said:
Also off topic but just so you guys know the process you used to s-off corrupted the misc partition. Which makes fun for weird and stupid issues. Then also like on the desire and others a corrupted misc partition bricks usb and such. I have the stuff for uscc and virgin mobile, I just have to get it up in a post how to fix it.
Click to expand...
Click to collapse
Corrupted misc... wow... how is that fixable? Or how can I verify whether I have a corrupt misc?
Here is my problem, perhaps someone has ideas how to proceed. I am fairly new to this, as you may guess since I am here and am asking questions I downloaded some ROMs that simonsimons34 cooked up. When I flashed them, the phone would get stuck on boot, on the mfg logo screen. adb logcat would not capture anything when I tried. (I have captured it for a working ROM boot, so I think I know how to do it). I also inspected the recovery.log and found nothing weird there. Then I downloaded 2 versions from insink71 and they both booded, but the newer one had issues running, which for now is beside the point. Point is they BOOTED! So now I tried to cook my own. Trying to start simple I made no modifications, just sent a known working nandroid through the kitchen and recompiled and it get stuck trying to boot. Again no output to logcat, recovery.log looks good. So I came across the edify_defs in the kitchen tools and figure that's where my problem is. build.prop has ro.product.name=marvelc and _template tells me I need a marvelc file. Of course I don't know the mount points. So now I read you don't need it? And insink71 says his ROM did not use a marvelc?
Any pointers from thos that have gone down this road would be greatly appreciated! My environment:
phone HTC Wildfire S Virgin Moblie, A510c
windows 7
oracle VM VirtualBox
linux 11.10 with java6
DsiXDA kitchen 0.183
Regards,
Rich
help
rkleinhenz said:
So here's another marvelc wannabe chef that made it to this thread with the same questions. I thought my problem was not having a marvelc file in my edify_defs... thought the _template indicated I needed one.
Corrupted misc... wow... how is that fixable? Or how can I verify whether I have a corrupt misc?
Here is my problem, perhaps someone has ideas how to proceed. I am fairly new to this, as you may guess since I am here and am asking questions I downloaded some ROMs that simonsimons34 cooked up. When I flashed them, the phone would get stuck on boot, on the mfg logo screen. adb logcat would not capture anything when I tried. (I have captured it for a working ROM boot, so I think I know how to do it). I also inspected the recovery.log and found nothing weird there. Then I downloaded 2 versions from insink71 and they both booded, but the newer one had issues running, which for now is beside the point. Point is they BOOTED! So now I tried to cook my own...
And insink71 says his ROM did not use a marvelc?
Any pointers from thos that have gone down this road would be greatly appreciated! My environment:
phone HTC Wildfire S Virgin Moblie, A510c
windows 7
oracle VM VirtualBox
linux 11.10 with java6
DsiXDA kitchen 0.183
Regards,
Rich
Click to expand...
Click to collapse
Ummm all my roms have been for marvelc and all have booted and run decently [by most accounts]; you had a unactivated phone. I would guess that my first build [from shortly after root] was activated. Team marvelUSc will always release working boots; which, should work activated or not because they're using base roms from official RUUs to build with. Until yesterday, I was just working from copies; but today I have RUUs thanks to the wizardry of Football [see first stickied thread in development, contact him, donate to his work- he will probably share openly after he receives enough donations to cover his expenses gathering them] Other roms have been written for marvelc [some of which, may have failed to boot]; not my concern. Whether or not one has a marvelc device to test with [which is what I relayed to you]; potential concern for development; but not mine since I do have a marvelc and I do test my roms. Having a non-booting rom; that would be a grave concern [if it happened to me or the new team; also formed yesterday]...
The kitchen is a tool that people can try, or even [contrary to opinion] developers can use it too [and teach people how to get started; which being helpful and relaying knowledge; which, is the sect of XDA I'm from]. There are other tools as well.
Yesterday, when I got official RUUs, I tried to do the smart thing; [team build]. Simonsimon34 thought it a decent idea, I handed him the vm RUU. I went to who I believed to be a US Cellular developer [see the informative post above... though I won't mention names]; he was busy writing a post launching personal attacks at me [which have already been deleted], I withheld the USCC RUU meant for him. It was my intention to look at MetroPCS, and I did that briefly and made a rom [that boots and works] from it with dsixda's kitchen. If yesterday I sent you a message when my blood pressure was through the roof; I apologize. I will continue to help you privately via email on the version numbers etc for kichen if you wish. Just wanted to tell my perspective.
Rob
insink71 said:
Just wanted to tell my perspective.Rob
Click to expand...
Click to collapse
Thanks, Rob, I took no offense to posts or email from you, all info I got from you has been helpful. There's one more bit of info I have I forgot in the summary above: I had a PM from someone who ALSO had an unactivated phone, and he had no problem flashing and booting simonsimons34's ROM which failed to boot for me! So it's probably not the fact that mine is not activated... I really thought I was doing something fundamentally wrong until I downloaded your ROM and it booted fine. Now I am planning to look through the kitchen scripts to learn more about the process of making a ROM. I'm fairly tenacious and will get this to work some day I'll email you with something you may be able to help me with.
Regards,
Rich
so... in summary,
can someone create a template or upload a 'working' kitchen to cook custom ROM for marvel/c?
zero13th said:
so... in summary,
can someone create a template or upload a 'working' kitchen to cook custom ROM for marvel/c?
Click to expand...
Click to collapse
it works just fine for the wildfire s, as long as the base ROM was for the same phone. I'm not sure about porting yet though, it may need a template.
Sent from my ICDroid X
Related
Hey guys,
I've been trolling the forums for some time now, and I have yet to find the answer that I am looking for in regards to cooking my own ROMs - specifically for the HTC Vogue (Bell). I have looked through all sorts of stickies/readmes, but I still cannot figure out how to put it all together...
I've got a stock ROM from Bell, it has been extracted (so I have the bootloader, .nbh file and so on)...
Now HOW do I extract the .nbf, or even edit it for that matter? The only solution that I have found is the UNIX-based one, but I'll be honest, PERL and I dont get along well...is there a GUI or commandline based solution for WIN32?
I feel dumb for asking, but if someone could help me figure out the editing/compiling/flashing aspect, I'd be forever grateful
Thanks.
Most of the kitchens will take that nbh and parse it out in to the OEM and SYS folders you need.
I would suggest you search for DogGuy's command-line kitchen, and use that as a learning tool as he has batch files that automate most everything, and yet you can go through them to better understand what is happening.
Good luck!
Also some recent threads at ppcgeeks on this topic with useful info.
TGHI said:
Hey guys,
I've been trolling the forums for some time now, and I have yet to find the answer that I am looking for in regards to cooking my own ROMs - specifically for the HTC Vogue (Bell). I have looked through all sorts of stickies/readmes, but I still cannot figure out how to put it all together...
I've got a stock ROM from Bell, it has been extracted (so I have the bootloader, .nbh file and so on)...
Now HOW do I extract the .nbf, or even edit it for that matter? The only solution that I have found is the UNIX-based one, but I'll be honest, PERL and I dont get along well...is there a GUI or commandline based solution for WIN32?
I feel dumb for asking, but if someone could help me figure out the editing/compiling/flashing aspect, I'd be forever grateful
Thanks.
Click to expand...
Click to collapse
Here is the link: http://forum.ppcgeeks.com/showthread.php?t=20550
Follow JD's instructions.....Test.....Test.......Test the ROM to make sure its stable before posting for others to use
Thanks D
dawilliams660 said:
Here is the link: http://forum.ppcgeeks.com/showthread.php?t=20550
Click to expand...
Click to collapse
Yeah, I did check that post, however, it seemed that they were a step ahead of me...the tools that were provided did not (both gave application errors on launch...?).
Thanks for the replies, any one else have other tips, pointers, etc?
PPCGeeks.com is the answer...I still haven't found it yet...there's too much info on that site. Have you seen this thread:
http://forum.ppcgeeks.com/showthread.php?t=18745
By following that method its a TON of work...and that's using a 'kitchen' someone already made. What you and I want to do is create our own kitchen by stripping a stock rom...and there aren't any guides on how to do that...I'm assuming because that's even MORE work. So basically a (TON of work x MORE work) = Fu%$ that.
If you find a somewhat easy way to do this before I do, post it for us!
sean222 said:
PPCGeeks.com is the answer...I still haven't found it yet...there's too much info on that site. Have you seen this thread:
http://forum.ppcgeeks.com/showthread.php?t=18745
Click to expand...
Click to collapse
Hey, I didn't see that thread yet, looks interesting, thanks!
Now, I can't wait 'till I get home from work...
As I was trying to create a swap file on my Hero I noticed that both mkswap and swapon are missing. HTC might have removed them from the ROM.
So I was wondering. Is is possible to take these binaries out from a, let's say, Magic ROM and put them in Hero. In theory it should work because of the same architecture. So If anyone is willing to share these binaries, I would give it a try
Can you look inside your Heros and let me know if this is just on mine. (Of course you must root it, mine done without a problem).
Have fun with hero!!
Aren't swap apps always hacks? Thought you'd only get that in cooked ROM
Daisy xxx
Dayzee said:
Aren't swap apps always hacks? Thought you'd only get that in cooked ROM
Click to expand...
Click to collapse
Makes sense. However as android being linux, it could be done just by adding the binaries and the appropriate libs. In theory it should work. Someone should try it
I'm not so up-to-date, are there any cooked ROMs for Hero (I'd flash mine, but I would like to keep the senseUI)?
Nothing yet
ok...
I have decided to start editing the Htc Hero wiki page here on xda-devs, so I'd be grateful if anyone could help. For example: for cooked roms and stuff like that. I'm already adding rooting methods so other users don't need to search in the forum, just go to the wiki page. So if anyone is interested, please help me edit the wiki page. (Oh this was a little of-topic:S - I'll make new thread)
Peace!
This will give you swapon etc.:
http://www.modaco.com/index.php?showtopic=291345
I'll add it to an update.zip shortly.
P
What exactly does the hybrid method update.zip does? I have seen it does something with the boot partition... Just asking because I don't want to brick my hero.
If updates the boot.img one to one that lets you adb remount.
P
With some help from me, manelscout4life dumped his LG Expo.
Links here:
Part00 and Part01: http://rapidshare.com/files/330408837/part0.zip.html
Part02: http://rapidshare.com/files/330404062/Part02.zip.html
Enjoy!
(don't forget to vote against XDA's stance of only doing HTC! )
MIRRORS:
Part00 and Part01: http://rapidshare.com/files/334116367/part00and01.zip
Part02: http://rapidshare.com/files/334116370/part02.zip
awesome work guys! if i hadnt been at a funeral id have been on there helpin out. nonethe less... fantastic work!
i just hope to see some custom roms soon!
we'll i think we might need to focus on getting the phone's SSPL or Hard SPL so continuous flashing is possible eh?
Chainfire said:
(don't forget to vote against XDA's stance of only doing HTC! )
Click to expand...
Click to collapse
Where is the vote? Not to hijack the thread, but it's known that we're going to go 6 months without anything better than the HD2 from HTC meanwhile LG, Samsung and Acer are pumping out WM phones yet there's no XDA support so they will inevitably lack the same base support as we continue to salivate over HTC and it continues to pump out Android phones...We'd all be better off if XDA moved with the industry.
bugsykoosh said:
Where is the vote? Not to hijack the thread, but it's known that we're going to go 6 months without anything better than the HD2 from HTC meanwhile LG, Samsung and Acer are pumping out WM phones yet there's no XDA support so they will inevitably lack the same base support as we continue to salivate over HTC and it continues to pump out Android phones...We'd all be better off if XDA moved with the industry.
Click to expand...
Click to collapse
wouldn't we all be better off if we just got along?
Awesome that you were able to dump the eXpo rom, but we can't do anything with just a dump. We had this problem with the Incite. We had to wait for an official rom because the way LG makes their roms. The format is a .dz file and there are parts of this file that is needed to cook a rom which is not found with a dump.
We would need the actual dz file in order to deconstruct it, dump the contents, cook, and then reconstruct the dz file. Without the dz file we can't flash.
Dark9781 said:
Awesome that you were able to dump the eXpo rom, but we can't do anything with just a dump. We had this problem with the Incite. We had to wait for an official rom because the way LG makes their roms. The format is a .dz file and there are parts of this file that is needed to cook a rom which is not found with a dump.
We would need the actual dz file in order to deconstruct it, dump the contents, cook, and then reconstruct the dz file. Without the dz file we can't flash.
Click to expand...
Click to collapse
Right the dz file will be helpful but this is nice for just hacking up the phone we have now or porting the apps as well. With the dump there can be driver hacks made and all kinds of other fun goodies its a start...
killerskincanoe said:
we'll i think we might need to focus on getting the phone's SSPL or Hard SPL so continuous flashing is possible eh?
Click to expand...
Click to collapse
But we dont even know yet if we will need one we need an spl dump so we can check to see if it needs a signed image or not
This is def. very exciting and I very much look forward to seeing things getting ported from this phone to all of our other WM phones!! So we can have pieces of this phones apps/programs running in our phones to play with!!
GREAT JOB NOW LET THE FUN BEGIN
meh
that was faster than I expected. Great work!
Dark9781 said:
Awesome that you were able to dump the eXpo rom, but we can't do anything with just a dump. We had this problem with the Incite. We had to wait for an official rom because the way LG makes their roms. The format is a .dz file and there are parts of this file that is needed to cook a rom which is not found with a dump.
We would need the actual dz file in order to deconstruct it, dump the contents, cook, and then reconstruct the dz file. Without the dz file we can't flash.
Click to expand...
Click to collapse
Just because you can't do anything with a dump because it doesn't give you all the stuff you need, doesn't mean it isn't useful for other purposes.
Apps porting, driver research, etc. I am personally not interested in flashing the LG Expo (mainly because I don't have one) but I was in need of the dumps.
So... shortsighted much?
Wonderful News
This is great!!!
I tried to dump my LG IQ which is the Canadian version of this phone, but didnt work too long at it, and I fail because the phone said device not ready in the dumping process.
If you want to PM me with how you did it, and give me a bit of advice, I would be willing to try again.
The Telus and AT&T versions are slightly different, one difference being that the Telus phone has a slightly newer version of windows ce on it.
Telus 5.2.21868.5.0.69
AT&T 5.2.21749..don't know the rest
Awesome job......
Installing this CAB on your phone and rebooting should get rid of that pesky error:
http://www.jongma.org/tmp/MultASync_Security_Policies.cab
(Taken from MultASync project)
Aside from that, it's just pdocread / raw dump as usual ...
For an example of the commands, see:
http://forum.xda-developers.com/showthread.php?t=501871
As a fellow user of the LG Expo, would be more than happy to help out as I can.
Chainfire said:
Installing this CAB on your phone and rebooting should get rid of that pesky error:
http://www.jongma.org/tmp/MultASync_Security_Policies.cab
(Taken from MultASync project)
Click to expand...
Click to collapse
Sorry to say, it didn't work for me
tried installing the cab, and tried editing the reg manually to the values in the cab....
any other ideas?
Not really... all we did is hook up the device correctly, install that cab, excute the commands and we had a dump ...
Thank you Chainfire! Telus IQ ROM dump
OK I am now feeling like an idiot.
Yes, the disk on the IQ is called DSK1: not FLASHDR
Yes, this cost me being at least two weeks later than I needed to be.
Yes, I goter dun tonight....
rofl
Easy mistake to make: but rest assured, everyone only makes this mistake but once, and probably every dumper once made it
Sorry, I should of been a bit clearer, but when I said we can't do anything with just a dump I was referring to cooking. Someone had mentioned seeing custom roms soon so I was just pointing out that that wouldn't be possible until we get a base rom to work with. If I confused anyone it was not my intention.
First of all, I'm not a total newbie to this kind of stuff. I've already been creating firmwares for Different mobile Phones, some Linux-running routers and the Sony PSP, but this is my first try on Android.
At first I wanted to start off simply: compile the source on my Ubuntu and flash it - that's how I would start with any open-source 'from the scratch'-project. So I got repo, set it up and synced it, compiled it and created a zip with the rom kitchen to try if it even boots. Well it didn't (this is a bit more complicated than flashing a linux firmware to a router). Then I've taken a look a the update-script and modified it. The rom now installs successfully, but still doesn't boot. Wel my questions are:
1. Are there any guides on properly setting up the update-script? I didn't find anything, but maybe I didn't look in the right places.
2. I probably did everything wrong with the compiling. what are the options I get when I enter 'lunch' for? They should change settings for the compilation right? Am I good with the HTC passion option or do I need anything different?
Finally don't be angry because of my grammar/spelling, I'm from germany and don't get mad because of possibly 'noobish' questions, I promised I searched the forums and giyf.com
CrisisCorE said:
1. Are there any guides on properly setting up the update-script? I didn't find anything, but maybe I didn't look in the right places.
Click to expand...
Click to collapse
I too have searched for this with little to no success, so +1 on this...
Im also in need of a guide how to completely demolish/rebuild the update-script.
Someone who can point a finger?
Nobody? nothing?
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.