Is there instructions on creating a post-flash (or hard reset) install script? I'd like to have it run the cingular WAP cab, and maybe a couple others. I think I've been all over, but haven't seen anything...
Thanks!
Also - does anyone have a package or cab for camera 3.3???
Hi Matt... there are a couple of options...
First off, you could go the route that Faria does in his kitchen - effectively an Extended ROM folder under Windows. When the ROM install has finished and you've done the screen align, it runs the Extended ROM contents - just like the customisations you get in most operator ROMs. The advantage of doing it from a subfolder under Windows is that it works for G4 users as well as G3.
The other alternative is to actually flash your Extended ROM (this is what I've done, as mine is G3).
With the right files in Windows and Windows\Startup (CheckAutoRun.exe and CheckAutoRun.lnk respectively) and the registry entries set up for the appropriate location (I can tell you what these need to be), it will run no problem.
Is this what you're looking for? Faria also has a nice couple of utils that run during customisation and let you choose which operator's settings (GPRS and MMS) you wish to install. I guess these just run the appropriate CAB file based on your choice.
I am happy to help you set this up if it would be of assistance, having spent the last couple of days trying to get all this stuff up and running.
JoelC said:
Hi Matt... there are a couple of options...
First off, you could go the route that Faria does in his kitchen - effectively an Extended ROM folder under Windows. When the ROM install has finished and you've done the screen align, it runs the Extended ROM contents - just like the customisations you get in most operator ROMs. The advantage of doing it from a subfolder under Windows is that it works for G4 users as well as G3.
The other alternative is to actually flash your Extended ROM (this is what I've done, as mine is G3).
With the right files in Windows and Windows\Startup (CheckAutoRun.exe and CheckAutoRun.lnk respectively) and the registry entries set up for the appropriate location (I can tell you what these need to be), it will run no problem.
Is this what you're looking for? Faria also has a nice couple of utils that run during customisation and let you choose which operator's settings (GPRS and MMS) you wish to install. I guess these just run the appropriate CAB file based on your choice.
I am happy to help you set this up if it would be of assistance, having spent the last couple of days trying to get all this stuff up and running.
Click to expand...
Click to collapse
It sounds like your first point is what I was looking for - but up till now I've avoided adding / manipulating the extended rom to prevent issues related to it's use. I guess I'll have to cross that bridge sooner than later!
Is there a "howto" anywhere on it? I'd like to add the option for users to select post installation packages to run, in a nice and "foolproof" way - such as themes, WAP cabs, or whatever. Kinda like "drop your post install cabs in this folder" and it'll go ahead and add them during the rom build, then execute the install after flashing.
Thanks!
mattk_r said:
It sounds like your first point is what I was looking for - but up till now I've avoided adding / manipulating the extended rom to prevent issues related to it's use. I guess I'll have to cross that bridge sooner than later!
Is there a "howto" anywhere on it? I'd like to add the option for users to select post installation packages to run, in a nice and "foolproof" way - such as themes, WAP cabs, or whatever. Kinda like "drop your post install cabs in this folder" and it'll go ahead and add them during the rom build, then execute the install after flashing.
Thanks!
Click to expand...
Click to collapse
search lol i'll try and dig it up for you since i should probably do the same thing
try this of course editing it to where you want it to point:
Code:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRunCFG"="\\Extended_ROM\\config.txt"
"AutoRun"="\\Extended_ROM\\autorun.exe"
notyourdaddy said:
search lol i'll try and dig it up for you since i should probably do the same thing
try this of course editing it to where you want it to point:
Code:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRunCFG"="\\Extended_ROM\\config.txt"
"AutoRun"="\\Extended_ROM\\autorun.exe"
Click to expand...
Click to collapse
I just found this link that has an extended rom in it. It makes a lot of sense, especially the txt file that directs the installation and then initiates a reset. Getting warmer!
http://forum.xda-developers.com/showthread.php?t=309922
So here's what I'm thinking - just initial thoughts:
Have a folder with the base applications that are used every time like AutoRun.exe.
The user places the cab(s) in the "add files to ext rom" folder.
They run an exe that reads the directory file contents, verifies file type, copies the files to the extended rom folder, and displays the list. I'd write it in VB, since I'm most comfortable with file system operations in that language...
They change the list based on the order they want them installed using up and down arrows to sort priority.
The click OK, and it creates the config.txt file, including all necessary commands such as reset and whatnot.
That way when they build, it's all good to go.
Any thoughts?
Slightly off topic but does anyone have a .CAB for TomTom6 (or know how to edit/make one) that doesn't require user input during the installation?
I am not looking for a hacked version of TomTom, just how to prevent it asking me where to install. .CABs that run from the Extended ROM can't ask for user input or it will crash the extended ROM installation as we know; I just don't know how to edit the ttn.cab to stop it asking.
Thanks
Andy
Hi Matt,
It does sound like the first option is the best - it's also the only way to get G4 compatibility. I think your idea to write a VB app is a good one - let the user choose which CABs to install to ExtRom, but I think u need to be very clear what you want to achieve. As this `ExtRom` is not actually in the proper extended Rom, but just a folder under Windows, you gain nothing really by installing programs from here, best just keeping it for operator specific settings and such.
The other issue with extended Rom installations, of any type, is that the config file must run to completion. if you put in cab files that require user input, the install will fail (at least from a proper extRom, maybe ok in this scenario, I don't know); likewise cabs that require or initiate a soft reset will cause an ExtRom install to crash. So, this sorts of limits what cabs can be used. mine puts in personal reg settings; no operator settings as I use wifi not gprs or mms.
Also - and I hope I'm not out of line here, or misunderstanding you - Faria has something that does exactly what u need in his fake ExtRom... u cld always ask him nicely for use of it, or r u looking forward to the coding?
My only other thought is the extra support burden a complex fake extrom scenario would generate, especially if ppl don't understand its purpose and stick stuff in that causes problems...
I hope this has made some sense - past my bedtime and I'm knackered LOL. Just my 2 cents, y'know?
Good work and all the best
JoelC said:
Hi Matt,
It does sound like the first option is the best - it's also the only way to get G4 compatibility. I think your idea to write a VB app is a good one - let the user choose which CABs to install to ExtRom, but I think u need to be very clear what you want to achieve. As this `ExtRom` is not actually in the proper extended Rom, but just a folder under Windows, you gain nothing really by installing programs from here, best just keeping it for operator specific settings and such.
The other issue with extended Rom installations, of any type, is that the config file must run to completion. if you put in cab files that require user input, the install will fail (at least from a proper extRom, maybe ok in this scenario, I don't know); likewise cabs that require or initiate a soft reset will cause an ExtRom install to crash. So, this sorts of limits what cabs can be used. mine puts in personal reg settings; no operator settings as I use wifi not gprs or mms.
Also - and I hope I'm not out of line here, or misunderstanding you - Faria has something that does exactly what u need in his fake ExtRom... u cld always ask him nicely for use of it, or r u looking forward to the coding?
My only other thought is the extra support burden a complex fake extrom scenario would generate, especially if ppl don't understand its purpose and stick stuff in that causes problems...
I hope this has made some sense - past my bedtime and I'm knackered LOL. Just my 2 cents, y'know?
Good work and all the best
Click to expand...
Click to collapse
That's really good info, because I'm climbing the learning curve as fast as I can here to get a good grasp on what the extended rom is, as well as how to use it. I appreciate the conditional warnings... better to know ahead of time than find out following a problem.
I'd rather use the true extended rom (as I understand it anyway), so I don't loose any additional space for the BuildOS programs. That is, assuming the extended rom is a seperate memory location than the base...
In another thread, someone is going to post that tool. I'm really interested in how it works.
If I can get all the concepts together, I hope to get a solid tool that will improve functionality in the ROM, without adding complexity or trouble... and I greatly appreciate the help!
Interesting thread...guys, you just gave me some new ideas.
Before that...there's one thing that's bothering me...
Can we use ExtendedRom on a G4 or not...lol I thought not, until me an Boto made a clean one from a G4 ExtRom and when Boto flashed it it worked , and he has a G4. Why we always say that we don't use an Extended Rom for G4 users ?
Normaly, a G4 should/would brick when flashing IPL/SPL not Extended Rom, am I right ?
We are shrinking the OS space to integrate features of the ExtendedRom in order to all people use it but is it that true ?
Ok, now back to my idea .. I want that in my next rom to include an extended rom, of course and make it that way so when you first start your PDA, it will act like when installing windows on the PC , asking you which apps or what options you want to use. I think i can manage to do that...still the question remains ...will G4 users be able to use it ?
Sorry for the delay writing back... I've been over in the G4 subforum trying to find out if they can flash Extended Rom. Some ppl have reported success using Faria's tutorial. Hopefully this is the case - what u said about IPL/SPL flashing is right, this seems to be a real problem, but if u can flash a radio-only Rom, why not Extended Rom?
What did u and Boto flash onto his G4? Blank Extrom or a cooked one?
Perhaps what we need is a guinea pig to try this out for us...!
JoelC said:
Sorry for the delay writing back... I've been over in the G4 subforum trying to find out if they can flash Extended Rom. Some ppl have reported success using Faria's tutorial. Hopefully this is the case - what u said about IPL/SPL flashing is right, this seems to be a real problem, but if u can flash a radio-only Rom, why not Extended Rom?
What did u and Boto flash onto his G4? Blank Extrom or a cooked one?
Perhaps what we need is a guinea pig to try this out for us...!
Click to expand...
Click to collapse
I took the Ext Rom from the Wizard Love Rom and i edited the config.txt and deleted cabs ...that's it
Well, if it flashed OK... sounds like it might be usable after all But tell me, is Boto's G4 CID locked or unlocked? It's all very uncertain, but some of the G4 posts lead me to believe this may make a difference
ADB100 said:
Slightly off topic but does anyone have a .CAB for TomTom6 (or know how to edit/make one) that doesn't require user input during the installation?
I am not looking for a hacked version of TomTom, just how to prevent it asking me where to install. .CABs that run from the Extended ROM can't ask for user input or it will crash the extended ROM installation as we know; I just don't know how to edit the ttn.cab to stop it asking.
Thanks
Andy
Click to expand...
Click to collapse
All I did for TomTom is install as normal and then copy the Navigator directory and My Documents\TomTomto my storage card where the maps, postcodes etc. are located. After any ROM upgrade all I need to do is create a shortcut in the start menu pointing at \Storage Card\Navigator\TomTom Navigator.exe No user input needed other than to pair the bluetooth gps and define a serial port.Hope this helps, it has worked for me after every change in ROM which has been quite a lot recently.
wizzzard said:
All I did for TomTom is install as normal and then copy the Navigator directory and My Documents\TomTomto my storage card where the maps, postcodes etc. are located. After any ROM upgrade all I need to do is create a shortcut in the start menu pointing at \Storage Card\Navigator\TomTom Navigator.exe No user input needed other than to pair the bluetooth gps and define a serial port.Hope this helps, it has worked for me after every change in ROM which has been quite a lot recently.
Click to expand...
Click to collapse
Thanks for that but it isn't what I was really after.... I am just trying to automate everything. I have flashed my ROM that many times recently and going through the install of TomTom each time is a bit of a pain. I have got a couple of .CABs in the Extended ROM OK and these work fine, I just thought it would be nice if I could get TomTom in there as well.
Andy
I didn't want this to turn into a "how-to" thread, but I'm still scratching for hard info on the extended rom, and as many questions out there, it might be a good one to clarify some details...
As I understand it now, there's two forms of "extended ROM":
1. The true extended rom "similar to the radio ROM"
There is some "trigger" that runs the contents of the extended rom, such as AutoRun.exe?
2. The 'psuedo' extended rom that is basically a post install script to run cabs.
The contents of the folder under windows are run from a trigger that resides in the startup folder - similar to a runonce in Windows on first boot?
Does this sound close?
Also, where does the 'true' extended rom reside? Does it use the portion of memory reserved for the OS, or is there another portion just for it? (so if by adding applications to the extended rom, your available storage memory will remain unchanged - less the installed application?)
I'm presuming then by the 'psuedo' extended rom, that it does consume ROM space, but simplifies post-flash cab installations - assuming you follow the rules...
From what I see, by using the 'psuedo' ER, you waste space by keeping the installation files in addition to the installed application files.
If I'm wasting space and time by asking these questions and you know of a good extended rom tutorial, please direct me to it. I have spend some time tonight searching, but a definitive guide still eludes me... Thanks!
Sorry, coming into this thread late, but you have seen this thread, right?
http://forum.xda-developers.com/showthread.php?p=968417
While it may not directly answer some of the questions, the tools and info in the tutorial may shed some light on this subject (or give you a direction to start digging further).
mfrazzz said:
Sorry, coming into this thread late, but you have seen this thread, right?
http://forum.xda-developers.com/showthread.php?p=968417
While it may not directly answer some of the questions, the tools and info in the tutorial may shed some light on this subject (or give you a direction to start digging further).
Click to expand...
Click to collapse
OMG, I'm getting senile... I came across this months ago, but at that point didn't know what I was looking at... and didn't see it just now in any stickies... thanks man.
mattk_r said:
OMG, I'm getting senile... I came across this months ago, but at that point didn't know what I was looking at... and didn't see it just now in any stickies... thanks man.
Click to expand...
Click to collapse
Yeah, never figured out why that one was never made a sticky. I just know to go look at Faria's sig and it (and a few other good links) are in there
I have a few questions about this cooking stuff. Yes I searched and watched the videos. Maybe I can't find the proper wording for the search to work for me. But if I'm in the clear in that department, then maybe I can get some help.
1. If I have a radio that is an NBH file, the BuildOs wants an NB file. How do I convert?
2. How would I get someone else'e rom, say the Hyperdragon roms, and get it to the oem, sys and rom folder. I already did the dump and I end up with the temp directory that has some stuff like what is in the oem, sys, and rom folders. Am I missing something?
3. Is there any easy way to find one of the Packages after doing a dump? Say i am looking for the registry entries in the Hyperdragon roms, where would those be and how would I get them?
I have the basic idea of how to do this stuff, just need some assistance in the stuff that I feel was not covered very well. I already made a few roms with Manilla and without and some with HTC home. They all work with some bugs here and there. I have never been much of a person on reading on how to do stuff, just tell the "simple" explanation and I experiment from there.
Any help, please!
Hi there I don't know if this thread really belongs here (mods will tell ) but here are some answers to your question:
1/ use the search function... ok, not SO funny
1 bis/ use NBH extract http://forum.xda-developers.com/showthread.php?t=289830
2/ Download a good Kaiser kitchen (Alex's or the one on PPCKitchen) and follow the first steps that will extract your OEM/SYS folders
3/ Registry entries can be found all the place, under varied forms: basically, .rgu files, initflashfile.dat, and .provxml files. You'll have to take some (like in a lot) time to figure out which modifies a given reg key
Hope this shed some light
Best regards
Ok, I was missing the Extraction tool for the NBH files.
I thought I was right on the reg files but I was thinking, maybe even hoping, for an easier route but I guess not.
I have everything I could find on the kitchen stuff and have tons of packages and cabs. Now, like you said, time to spend a lot of time experimenting.
But again, where do I get a radio*.nb file from?
whitehooptie said:
Ok, I was missing the Extraction tool for the NBH files.
I thought I was right on the reg files but I was thinking, maybe even hoping, for an easier route but I guess not.
I have everything I could find on the kitchen stuff and have tons of packages and cabs. Now, like you said, time to spend a lot of time experimenting.
But again, where do I get a radio*.nb file from?
Click to expand...
Click to collapse
You have download the radio you want, and extract it using nbh tool.
You'd better not include the radio ROM into your final .nbh package: it will be easier to later test different radio roms without having to reflash the radio in case you flash the main (OS) rom again, and will make your packaged ROM lighter. If you later want to share it, you can still zip your OS and Rasio roms together for people to flash separately...
Remember that the efficiency of a radio ROM is more or less closely tied to your phone service provider, location, Kaiser build, color of your socks and so on... People most often have a prefered radio ROM they'll tend to stick to.
When I cook roms I want to share, I get 3 .nbh ready: one for OS, one for radio, and one for splash, so people can choose to flash whatever they want.
So NBHextract works on everything. Who would've thought. I think maybe I am reading too hard in this. My biggest deal on the radio was I want to make one for myself where I can put my phone back to how it is exactly. If I try a cooked one and need to change a few things then I can load my stuff back on without spening 30 minutes doing it.
Thanks for the answers guys, I appreciate it.
Another question. Is there any other way than flashing to your phone to test these roms? I know microsoft has that "emulator" to try out WM6. Any way to change those files?
How do you use sys files that are designed for visual kitchens with the non visual buildos? I tried moving all the folders into one directory and buildos finishes but the rom doesn't boot... anyone? thanks!
I dunno, but you'll need all of the dsm's to begin with. If you don't have them, you might as well not even try. There's a folder in the visual kitchens with dependencies; maybe those are the dsm's that are removed from the original packages. It's just a guess.
Why not just use the newer kitchens? Or, wait until Da_G finishes with all of his kitchen tools. I bet he'll have everything figured out.
Edit: Or, check this post. It will probably help you out.
Thanks for the info! Perhaps I should have also asked what the differences were! I will check that post. About newer kitchens.. I guess I am old-fashioned. I will have to convert one day but it's like I am with cars, I require a standard transmission - one day I will have to give in a drive automatic ...
raidzero said:
Thanks for the info! Perhaps I should have also asked what the differences were! I will check that post. About newer kitchens.. I guess I am old-fashioned. I will have to convert one day but it's like I am with cars, I require a standard transmission - one day I will have to give in a drive automatic ...
Click to expand...
Click to collapse
Automatic sucks, don't go there, lol.
I started out with the older style kitchens and was reluctant to change, but it's really not that hard. You'll need to convert your packages, but there's a simple tool for doing it put together by Kraize. The kitchen itself works better; I used to have the older style one crash all the time. Just suck it up and do it.
more and more kitchens are showing up as visual. I have groove rom 5 kitchen but just could not figure it out, my rom would not boot. maybe I will swap my question around and learn to convert old style kitchens to new. I do kinda like the no duplicate file error... and the nbh's they produce do seem to be smaller. not sure though as I have never made a rom that will boot!
I have separated as many parts as I could figure out with TPC's OEM and EXT packages from his last kitchen (at the time of this posting), 23034.
If you cook using TPC's files, I highly recommend that you upgrade to these.
I deleted some things that were partially deleted, removed references in *.rgu and initflashfiles.dat to files that are missing. I corrected some rgu/reg files that were missing the trailing CRLF. I removed many *.provxml that did nothing. I cleaned up the *.rgu, *.reg so that they are easier to read and contain no delete entries ([-HKEY_...]).
Here is the link
BTW, I spoke with TPC about my findings and asked his permission before releasing this. He let me know that he doesn't personally use the files anymore since he uses a newer device and that he compiled these files when he was still learning to cook.
Downloading Now! Thanks selyb
Can't extract
Don't know where the problem is, but I can't extract files from your archives (tried winrar and 7zip), gets an error telling me its an "unsupported compression method". Anyone else with this problem?
Edit:
I'm stupid! Says in your post that I must use the newest 7zip BETA. Get it.
Good job! Stole some for use in my pure kitchen. Started out on TPC's kitchen and learned a lot by fixing the files as needed.
I'm just happy that someone else could get some use out of all the work I've done on them. If anyone finds anything wrong or has any advice/complaints please don't hesitate to post.
selyb said:
I'm just happy that someone else could get some use out of all the work I've done on them. If anyone finds anything wrong or has any advice/complaints please don't hesitate to post.
Click to expand...
Click to collapse
Nice one Sir. I noticed that most of the packages were incompatible with the newer builds. I have an idea for you tho:- Why dont you start your new thread like Ultimate packages- Collect Packages and fix em up and release them so that chef's dont waste time they just download and cook like users download and flash Nice eh think about it. LOL! - Nice once again I am downloading right now...
What I was really aiming for by releasing these files is to give people the same thing they had before but make it much easier to remove each element and to point out what had not been done or what had been done incompletely with these files in the first place.
I had thought about doing exactly what you suggested but tossed the idea because I believe there is no such thing as 'one size fits all' with these roms. Every use has different needs and no matter what you cook in or leave out, some users want more cooked in and others want more left out. I feel the same way about these base files.
I know very well that newer versions of many of these packages exist and one reason for this release was to make it easier for people to replace the packages with newer ones.
man, this is awesome! everything's organized just like when u dump a stock rom from the newer devices, no more apps hidden in the oemapps or oemdrivers etc...
Thank you sir
I have begun dissecting the OEM from the latest stock ATT rom and 21055 SYS/XIP. This takes all my spare time (something I don't have much of lately ) but when I release the entire kitchen I plan to update what packages I can. I will use TPC's files as a reference because people seem to like them. I am a minimalist and as such, I don't like most of the crap that people add to their public roms so I doubt it will be an Ultimate package collection. Anyway, it may take me days, maybe even weeks before I can release it.
The files I already released took me more than a month and I still am not satisfied with them. :-/
Is there anyone out there who has the knowledge on how to tweak/make ROM's willing to do a quick (I don't know if that is realistic) tutorial on just how to compare to different ROM's? For instance a video or a step-by-step process on how to take one ROM (let's say the Stock ROM of the Droid Charge Gingerbread version) and compare this to a heavily modded ROM (let's say Infinity ROM or Humble)... I'm curious just how the devs do this; many have advised to start here to see how ROM's work, what's different and where the location of different parts are.... Please help thanks..
My initial thread
Hmm good question. Sure most will point you to several links to read different threads. Each Rom depending on what they change are usually an effort by several people. Thats were credit to certain people are given. Some start with a stock ROM and do some tweaks but alot of theme work. Guess thats why you are asking. Think there is so much going on in the back round with what we dont see it would be hard to compare, such as lines of code etc... Dont know if that is the correct answer but figured I would try.
I know, the reason I'm asking is because I've been given advice to start here and the names of programs needed, but I'm not learned enough to use the programs the correct way yet... Figured I'd ask-whats the harm?
Sent from my SCH-I510 using XDA App
Programs:
Linux if you want to extract files from factoryfs.rfs files
7zip or File-roller (or other archive utility)
apktool (or smali/baksmali)
diff (win-diff or kdiff3 also works, can also use git)
Notepad++ or gEdit
andriod-sdk with platform-tools (for adb)
Any dependencies of the above
After that, it's as "simple" as de-compiling various files (with apktool/baksmali) and comparing them. Then use a text editor to add/remove things that you want/don't want from the de-compiled files, or swap out images. After the changes are made, recompile and test. It is a very time consuming process, especially if you run into issues, as problems aren't always easy to track. Logcat will definitely become your friend.
andrewjt19 said:
I know, the reason I'm asking is because I've been given advice to start here and the names of programs needed, but I'm not learned enough to use the programs the correct way yet... Figured I'd ask-whats the harm?
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
You came to the game kind of late. There're so many roms/kernels etc..and the history of them. It will take you months to catch up. I suggest that we would provide you the most current one and it's new/just release you can read up on it. When you look at a rom, alway start on the first page, this is where developer will provide details/description about what has changed for the rom. I would recommend the most current, stable, fast and it's a new release. The TweakStock Rom. This rom when you're using with Go Launcher (Go launcher set to smooth and with some animation, will give you the fluid of Iphone 4S. Start from thread one and see what dev has taken a stock rom and upgraded/tweaked up until today. Good luck. If any question you can post here and we will try our best to help out.
Thanks fellas, I appreciate the advice and I will let you know how I do. One problem I kept running into was in this procedure:
1. Opened kdiff
2.file browse rom a (stock gb in this case) both files still in .tar.md5 format
3. File browse rom b (humble or infinity)
4. Open/compare
5.force close
Second attempt removed .md5, left
.tar, same problem.
Third attempt unpacked and zipped, repeated steps 1-5. Force close.
Fourth attempt, tried to open just the .rfs files and repeated steps 1-5. this time I got a bunch of symbols... laid it to rest...........
So based upon the replies so far, I can see that I was trying to oversimplify a whole; each file must be extracted and browsed individually.
Sent from my SCH-I510 using XDA App