The WIKI Ideas/Suggestion Thread - JAMin, XDA Neo, S200 Software Upgrading

Hi,
Next to making ROMs I want to try and work on the wiki some more to make it THE prophet information source on basic questions.
I made this thread for users to suggest stuff that they think should be covered.
This is NOT a thread for asking questions about your prophet.
Thanks

Hi Jester
Wiki forums has pros and cons. Reading 20 pages of mixed text is not by far the best way to learn anything, the main problem for me is to distingish good info from bad one.
The 'Expert Selection': For each thread I would like to see only what an expert/senior member has selected. This filter can be multiple and tematic; the same 'expert' can select only some posts an 'rename' the sub-thread; and of course the same thread could be filtered by two or more members.
This way i can have the same point of view of them, and this is important for me..

Hi Jester,
Thanks for the big support on the Prophet and releasing ROM versions!
In the Forums there are many questions about how to upgrade your (for example) Dutch ROM to a WWE, what to do, maybe this is also something to add to the Wiki.
The Wiki side sould be rich of information about how to upgrade the ROM, what are usefull programms, free or payed, where does ipl and SPL stand for, What are the latest versions.
Groet,
TheTeek

Hi Jesterz,
Thanks a ton for your ROMs and your efforts!
One of the most eagerly sought after info is ROM editing specifically for G4 roms (specially again for Prophet).
Can you help in consolidating the tools (along with usage tips) to modify ROMs to achieve the following:
1. Steps to upgrade only the OS to whichever ROM OS you want.
2. Steps to increase the pagepool to X [I understand the device runs faster on an increased pagepool], but I am not sure of the ideal size to be kept. I got some details from here: http://forum.xda-developers.com/showthread.php?t=283280&highlight=pagepool
4. Steps to remove MS Office, voice dial and other applications from the rom and add a few apps. Will also need help in adding few apps like resco explorer and some registry hacks into the ROM.
5. Steps to move some programs from programs to system (for e.g smsdeliveryfix)
Am sure others can also add to this request.
Thanks.

Hi Jesterz,
thanks for this thread, I beleve there are a lot of stupid questions because a lot of information in the wiki are too much generic and the people have fear to make some errors (IS NOT YOUR FAULT because the newbie are sometime very newbie).
My dream wiki is:
- more specific
- with new information
For example, if you check the main procedure to update the rom, there are some step not very clear:
1) ***
If it states: "Could not update itsutils.dll to the current version, maybe it is in use ?" Do the following :
Copy the cab's from the Utils folder in the Lokiwiz03a.zip file to your Prophet and execute them.
(There are two files : "Cert_SPCS.cab" and "EnableRapi.cab")
This is not clear. A lot of user wrote me in private asking if you need to do a soft reset (or no, or an hard reset) after that.
2) ***
Sometime after that the itsutils.dll error is still alive. What the people have to do?
3)***
In some rom, you don't have to unlock the cid... right? But this is not on the wiki.
4) ***
There are some question where there are not answer, like this one in the ROM DUMPT.
"if you want backup your own rom, you have to do the unlock cid procedure and update the rom with another one. But if you do that you lost your own rom!!! So, why there is a Dump rom procedure, if you can not do that with your original one?"
5) ***
I would lik see in the wiky a tread with the list of the BEST ROM and the update.
6) ***
There are some etc...

I think what would be a *very* good piece of info for newbies is what are all the tools you guys use (cert.cab, etc etc....) and what each does to some degree....
as a newb myself, I find it *very* daunting and very scary to see lots of stuff posted on the forums that say "How To: Copy fileA and fileB to device, run fileC.exe on computer, then execute fileD on device, then wait, and poof! you're done". I'd be nice to at least know that the heck each of the components are and the purpose (even if it's very technical) of each one.
Also, if it's possible, list off any interdependencies these tools have. There are too many "half-instructions" floating around and it's really difficult to determine whether the user needs to do anything before hand before following the instructions.
*lastely*, Can we get a guide that lists off all the pros and cons for each of the custom ROMs that are getting posted. It's a little tough for newbies to know what are all the pros and cons for each ROM. Yes, we know there are pros and cons and nothings perfect, but *what* are the bugs? and what are the features? At least that way we can decide for ourselves whether or not the ROM will work for us...
I'm only into day 2 of all of this so I apologize if what I'm suggesting sounds stupid.
Thanks

Hello all,
Jesterz, thanks you for your investisment in the forum.
Some suggestions about the wiki.
One of the main issues for upgrading a rom is to have a clear view of what is going on.
There are many threads discussing different roms.
It should be grateful to have one main page giving an overview of every live rom and a page for each rom where the author can put a link and also give the current status of his rom and known issues. So I join to Mr Yellow for this.
It should be something very basic, not as far as an Issue tracking page (ie http://jira.codehaus.org/browse/MPA)
By now, whenever I want to update a rom, I have to read the entire post...
One solution can be, for each cooking rom version, adding a text file that describe everything to know.
Of course, a howto for cooking rom and useful mistakes can be also interesting.
cheers
Andre

Hi Guys - and yes, thanks for all the time & investment made here.
I'm a fairly new member, and one thing I think would benefit the WIKI is an idiots guide or introduction.
I found the the wiki a bit tricky in so much that it starts at a fairly high level and misses the basics
Whats an AKU and why might I prefer a new one ?
What extra features can I get with a new rom ?
Why might I need newer radio drivers ?
Stuff like that.
Also, a glossary would go down reall well.
JJ

doublej said:
Hi Guys - and yes, thanks for all the time & investment made here.
I'm a fairly new member, and one thing I think would benefit the WIKI is an idiots guide or introduction.
I found the the wiki a bit tricky in so much that it starts at a fairly high level and misses the basics
Whats an AKU and why might I prefer a new one ?
What extra features can I get with a new rom ?
Why might I need newer radio drivers ?
Stuff like that.
Also, a glossary would go down reall well.
JJ
Click to expand...
Click to collapse
I agree with the above......more of a beginner area with more explaination
Not an idiot guide but something more for the leaner who want to be experts like most here

Get to it
I think these are all great suggestions. The Prophet wiki is looking pretty sparse at the moment. So why doesn't everyone start editing it, rather than just talking about it?
Cheers,
uayeb

Hello
read it !
agree!

Shall i make a tutorial for changing the case? I know there is one already in another forum(modaco). But i want one on xda-developers?

the more the merrier!

I think possibly the most useful thing would be 'How to recover Prophet stuck in Bootloader'. I seem to telling people how to do it most days and sometimes more than once a day...
I'll happily write a 'How To' if required.

l3v5y said:
I think possibly the most useful thing would be 'How to recover Prophet stuck in Bootloader'. I seem to telling people how to do it most days and sometimes more than once a day...
I'll happily write a 'How To' if required.
Click to expand...
Click to collapse
You know, that's what's awesome about the wiki... you *CAN* go ahead and write whatever you want. It only takes like 5-10 minutes to understand the syntax of wiki-code... create a new page, write your stuff down, and start formatting. Bam, you've created a wiki page that everyone can use. Announce to the fourm that you've done so and you're done!
Then you can start insulting newbies that complain about getting stuck in boot loader that they should search and read the wiki! It feels really good!

mr_yellow said:
You know, that's what's awesome about the wiki... you *CAN* go ahead and write whatever you want. It only takes like 5-10 minutes to understand the syntax of wiki-code... create a new page, write your stuff down, and start formatting. Bam, you've created a wiki page that everyone can use. Announce to the fourm that you've done so and you're done!
Then you can start insulting newbies that complain about getting stuck in boot loader that they should search and read the wiki! It feels really good!
Click to expand...
Click to collapse
But how can I get it uploaded?

l3v5y said:
But how can I get it uploaded?
Click to expand...
Click to collapse
You don't upload anything. You can edit each page like it was a forum post. there's special syntax for lists, bullet points, headlines, links etc... but if you want to create a page, all you need is a title and that's it. Everything is done on the serverside.
The easiest way to start is to pick a page, click the edit button at the bottom, then add a new link to a page using the syntax [new page title]. when you save it, "new page title" becomes a link to a new page where you can create a new page and add more content there.
Give it a shot. Don't be afraid to break stuff.. you can always look back on old versions of the page and reverse any changes.

Pallas said:
Shall i make a tutorial for changing the case? I know there is one already in another forum(modaco). But i want one on xda-developers?
Click to expand...
Click to collapse
I second this!!! I've been looking at the modaco 1, & feel we need to have 1 from xda dev & Pallas is the man... heheh

mr_yellow said:
You don't upload anything. You can edit each page like it was a forum post. there's special syntax for lists, bullet points, headlines, links etc... but if you want to create a page, all you need is a title and that's it. Everything is done on the serverside.
The easiest way to start is to pick a page, click the edit button at the bottom, then add a new link to a page using the syntax [new page title]. when you save it, "new page title" becomes a link to a new page where you can create a new page and add more content there.
Give it a shot. Don't be afraid to break stuff.. you can always look back on old versions of the page and reverse any changes.
Click to expand...
Click to collapse
Breaking stuff can be fun I'll give it a try now...

l3v5y said:
Breaking stuff can be fun I'll give it a try now...
Click to expand...
Click to collapse
Good Luck!

Related

Wiki redesign

hey guys,
I'm a regular on the HTC tytn part of this board and have been quite active in updating the wiki and making it functional.
I thought i'd wonder over to this board and took a look at the wiki and have to admit, was sort of shocked. it's one enormous page that's not very intuitive!
I'm going to shift around some stuff to make the wiki for your device easier to browse and navigate, would love for you guys to help out with this venture!
I've started with this:
http://wiki.xda-developers.com/index.php?pagename=wizard_WM_6
WM6 definitely deserves a page of its own, complete with download links, links to threads etc. it does not deserve to be in the middle of some enormous page where most people can't even see it! it's linked back to the main wiki page under the contents page, which is easier to follow.
suggestions welcome, and please help in overhauling the poor state of the wizard's wiki!!
cheers
I don't know about others here in this forum, but I think you're doing us all a huge favor. Good start on the Wizard WM6 material so far.
Hi!
Ofcourse great job. I've learn from this site
I need to suggest to put some information about Not Big Deal 5.1.
I think, this rom is realy good. Realy. Not many ppl use it, but almost all of my friends that tried this rom, confirmed, that it's very ok.
You should probably rename the page to reflect the device it is for. The current name implicates it is a general WM6 page - which is not in fact.
Chatty said:
You should probably rename the page to reflect the device it is for. The current name implicates it is a general WM6 page - which is not in fact.
Click to expand...
Click to collapse
awesome suggestion, silly of me. i've renamed the page to wizard_wm_6
I've updated the Wiki (Thanks for setting this up) with information and download links to my Crossbow Released rom.
Also I would like to make an observation... I disagree with the description of The Core, in that it says this is the best rom for Newbies (or thats how I read it)... Since this is a Clean / "core" rom, I don't know that I would call this a good general starting rom for someone new. Don't get me wrong, I'm not saying The Core 2.0 isn't good, I'm just saying the claim that its the best rom for newbies is maybe misleading as many newbies want more than just a base rom. XPlore 1.1 (IMO) is actually a better rom for someone just starting out as it comes with some apps in it. Then Wizard Mobile 6 Business Edition is very nice with the set of apps in it too... Its just all of the roms have strengths and weaknesses, so to me calling a single rom the best for Newbies may be misleading. Let them choose what fits for them (or setup some type of Matrix to compare the roms).
BTW: This isn't criticism of this new WiKi page at all? I just wanting to provide feedback so this can become a valuable resource for the Wizard community (and I really appreciate you starting this project for us. Now I need to get back to working on the WM6 Cooking wiki pages I was setting up)
mfrazzz - good point. there should be no "favouring" of roms, it should be up to the end user to decide.
I've removed the whole best rom bit. let the person choose themselves

How would you guys like a Bugtracker?

I'm currently working on a Bugtracker for the xda-developers (my own project - wasn't asked by anybody)
The idea behind it is to allow:
The Developers to see what bugs are outstanding
The user to submit their problems
The curious to see which ROM has less bugs
The n00bs to do research before asking questions (and have more places to spam)
I'm not planning to replace the forums, I just want to make an extra tool that can be used along side the forums - but is neater for bug reporting
Feel free to post your thoughts on if you like it (and so what should be included) or if you don't like it (and so what should replace it, if anything)
Thanks!
Hey, that's very nice.
But.. Are we talking about a new website? or just a new thread?
DaVince said:
Hey, that's very nice.
But.. Are we talking about a new website? or just a new thread?
Click to expand...
Click to collapse
Entirely new website.
It will be hosted on my http://www.vidmes.com webserver
i voted approving the bugtracker but i like the idea of all the information about universal development being centralized in one only location.
so, i think it would be interesting to keep it in this forum.
It's ok, we'll just have a sticky thread that has a link to TehPenguin's site.
I vote you go for it TehPenguin.
DaVince said:
It's ok, we'll just have a sticky thread that has a link to TehPenguin's site.
I vote you go for it TehPenguin.
Click to expand...
Click to collapse
Well, I've done some tentative work on it - and its looking good (if a little bare - I'm a software developer, not a web designer )
I'm a little busy this week, so its going to be about 2 weeks before I announce the link for the Beta
In the mean time, I'd like suggestions as to what people want in it
(Also, I notice one negative vote - I'd like to see their argument....)
Thanks!
Great Idea
I think mandatory information should be
1) Device Vendor...ie Imate, XDA etc
2) Radio stack in use
3) OS Rom in use
4) Third party software installed ( I know this list can be big, I myself have well over 100 apps as std) but is important for diagnosing bugs. Perhaps we could get an AppMgr listing from each system, not too hard to obtain.
You could also go overboard a little and have a PDA page, browseable from our Uni's so nothing graphics intensive or fancy. A simple login dialogue ( Can we port XDA-Dev user accounts?) once the user has logged in, they fill in a basic form with the bug description, click on submit and we could pull the information in points 1 to 4 above off of the device with a script.
Just my 50pence worth.
Great idea m8, hope it gets somewhere.............let me know if I can help with anything.
Cheers,
Beast
yes! would be really helpful for cooks
beast0898 said:
I think mandatory information should be
1) Device Vendor...ie Imate, XDA etc
2) Radio stack in use
3) OS Rom in use
4) Third party software installed ( I know this list can be big, I myself have well over 100 apps as std) but is important for diagnosing bugs. Perhaps we could get an AppMgr listing from each system, not too hard to obtain.
Click to expand...
Click to collapse
What I was planning to do with this is to have them describe a "Bug" in very generic terms as the Bug's description. Then they are required to add a comment (which other people may add) - this comment would have a "template" which would have things such as vendor, radio (I didn't actually think of this one), etc...
beast0898 said:
You could also go overboard a little and have a PDA page, browseable from our Uni's so nothing graphics intensive or fancy. A simple login dialogue ( Can we port XDA-Dev user accounts?) once the user has logged in, they fill in a basic form with the bug description, click on submit and we could pull the information in points 1 to 4 above off of the device with a script.
Click to expand...
Click to collapse
Some good ideas but....
I can't actually get info from the xda-developer's forums database - this may be a security risk on their behalf and would require far to much messing around to organise (as much as I would like to do it)
You will be able to view the page on your PDA's - its _very_ basic and I'll try to keep it xHTML complaint and do fanciness with CSS (though at the moment it does use some table hax)
Pulling info out of the PDA is virtually impossible (unless I build an app for the PDA's.... maybe later ) since the pda only tells me what browser version it is using
Either way - these are the things I like to see - Ideas!!!!
Keep them coming!
DaVince said:
It's ok, we'll just have a sticky thread that has a link to TehPenguin's site.
I vote you go for it TehPenguin.
Click to expand...
Click to collapse
I totally agree with DaVince, having a bug tracking website would be cool and having a link directly to the site via xda-developers is a good idea. Keeping everything centralised and available for use by everyone who uses xda-developers.
You have my vote! Would be a great tool...
gsmknight
TehPenguin said:
What I was planning to do with this is to have them describe a "Bug" in very generic terms as the Bug's description. Then they are required to add a comment (which other people may add) - this comment would have a "template" which would have things such as vendor, radio (I didn't actually think of this one), etc...
Some good ideas but....
I can't actually get info from the xda-developer's forums database - this may be a security risk on their behalf and would require far to much messing around to organise (as much as I would like to do it)
You will be able to view the page on your PDA's - its _very_ basic and I'll try to keep it xHTML complaint and do fanciness with CSS (though at the moment it does use some table hax)
Pulling info out of the PDA is virtually impossible (unless I build an app for the PDA's.... maybe later ) since the pda only tells me what browser version it is using
Either way - these are the things I like to see - Ideas!!!!
Keep them coming!
Click to expand...
Click to collapse
Hi TehPenguin,
Surely we can run a JScript or Vbs through the PPC Browser to get the required data from the Reg, only a couple of RegReads!
Just another thought............... I prefer accurate information, the reg is less likely to make mistakes than a user!! (No offence intended to anyone)
L8r,
Beast
Bugtracker
Hi,
Would be great to have this.
Looking forward
Leo
Why not use one of the many bugtrackers already out there? I prefer Flyspray (http://www.flyspray.org/) since it's as mighty as Mantis, but more Web 2.0 ... and you should be able to browse it on your PPC, although I don't think anybody really wants this ...
Cheers,
-mARKUS
P.S.: As for getting registry stuff through the PPC ... I doubt you can read out the registry by a JavaScript running on the page itself. Also there are many geeks out there who use Resco so they could easily export a .reg-file and attach it to the report.
mbirth said:
Why not use one of the many bugtrackers already out there? I prefer Flyspray (http://www.flyspray.org/) since it's as mighty as Mantis, but more Web 2.0 ... and you should be able to browse it on your PPC, although I don't think anybody really wants this ...
Cheers,
-mARKUS
Click to expand...
Click to collapse
I've had a look at at a number of bug reporting systems - the problem with them is that I'd have to end up customising it quite a bit anyway. For instance, they are typically designed for one program, possibly with options to support different parts\plug-ins for these programs. My design involves having multiple "Devices" each with multiple "ROMs", which may be deprecated, and each of these ROMs have multiple bugs - thats a couple more levels of complexity than the average bug tracker can handle.
Although they are more "Web 2.0" the Javasript\other fanciness would make it difficult to view on a PDA. Personally I prefer the old style Web 1.0 and a PHP back end
The other advantage of me making it is that you guys can have, almost, anything you want - and it should be done as soon as I have time, seeing as I know the code intimately.
And the point I really like - I love coding
mbirth said:
P.S.: As for getting registry stuff through the PPC ... I doubt you can read out the registry by a JavaScript running on the page itself. Also there are many geeks out there who use Resco so they could easily export a .reg-file and attach it to the report.
Click to expand...
Click to collapse
Exporting a reg file is the only possibility. Due to "security" problems, no script can actually see the registry of the device (or your PC for that matter), except what is in the "User Agent" key.
I'll put it on the "TODO" list to make a .NET program that automatically dumps your settings and creates a bug report
Given time, this can become quite beautiful. And time is now something that I will have - since I'm on holidays for the next few weeks!! (Yay for no more exams!!)
The alpha version is almost finished
I'll put a link up onto WM-Gurus for the final testing stage of the Alpha and see how it goes
Once the Alpha is complete (ie not too buggy) I'll put the link for the Beta here
Enjoy!
this is really a great idea.
i hope all goes well...
thanks to all!
Okay,
ALPHA VERSION IS NOW AVAILABLE!!!!
You can see it by going to: http://xdabugs.vidmes.com
Feel free to register or use the following users:
Username "test" password "testing" (Access level - registered user)
Username "dev" password "dev" (Access level - developer)
Username "admin" password "password" (Access level - administrator)
PLEASE NOTE: At the end of the Alpha stage, ALL DATA WILL BE CLEARED FROM THE DATABASE!
What I need people to do:
Look for bugs
Write the Help\FAQ sections
Ask me questions so I can write the Help\FAQ sections
See what else is needed
Enjoy!!

[long] Want to learn...

I bet most of you will think I'm another newbie who wants to do what he's not skilled to do. Well... maybe you are right. I'm sure you need expert people who can help you to improve the development. But I trust in knowledge sharing and since I found out no guide / tutorial / How-to / Step_by_step which explain how to become a "chef", I hope someone could help me to understand what I need to cook! I'm so tired to flash my devices every 4/5 days...
I'm sorry, but I've been reading lots of threads and posts that suggested me only little fragment of what it seems to me a big puzzle.
There are only a few key point in my mind and one of them is the idea that I cannot build up a ROM from the base. So, I think the best way is to take part to existing official/unofficial ROMs. For example, I've got the installer of official WM6 upgrade for HTC TyTN and HTC Advantage. How to get the ROM file only?. I suppose there is a sort of temporary folder where it is uncompressed into...
Next step is to "explode" ROM into folders... isn't it? Which software can do it?.
And now, the nicest part: how to add/remove software?
At last... how to build up and upload your ROM, to have your devices becoming a beautiful (above all expansive) ornament?
I know I'm boring... and I don't want you to write a book for me. Please suggest me links, other posts or threads that could help me to have a complete picture for my mission...
Thank you all! I love you!
P.S.: not a word on my english!!!

..................................

..................................
..................................
..................................
..................................
one more just in case...
Fantastic and thorough - your threads rock.
Thanks
Very informative and well put together.
Even though I've posting for sometime now, I am new to the Kaiser and somewhat lost in the processes of flashing a new Rom. I've read all of the tutorials and still my problem is not clear to me. I have no PC available to me at the moment and was wondering if I can use this method to first install hard spl and them fash a new rom using the sd method, found in this forum. Sorry for the dumb question but as of yet I've not found the answer.
thanks in advance.
manfly9884 said:
Very informative and well put together.
Even though I've posting for sometime now, I am new to the Kaiser and somewhat lost in the processes of flashing a new Rom. I've read all of the tutorials and still my problem is not clear to me. I have no PC available to me at the moment and was wondering if I can use this method to first install hard spl and them fash a new rom using the sd method, found in this forum. Sorry for the dumb question but as of yet I've not found the answer.
thanks in advance.
Click to expand...
Click to collapse
No, do not attempt to perform HardSPL from an SD card. In fact don't attempt to do anything without a PC around.
Creating a new page on the wiki is as easy as creating a link on existing page and then clicking on that link and editing the content for the new page.
*edit* For a better explanation, see the wiki for help: http://wiki.xda-developers.com/index.php?pagename=AddingPages
As you've seen with your other threads, this thread too will be lost. Wiki entries are easy to find and able to be edited by all.
This thread should exist as the discussion thread for the wiki page for questions & comments, not the main text.
Great guide that really explains what spl is about, like you say should be on the Wiki.
Bengalih, perhaps you could add some info on CID unlocking - this also leads to confusion when reading the threads. Like once CID unlocked do you need hardspl? will flashing the wwe spl make the device CID locked again? Is there a diference between CID and Super CID unlock? What exactly does CID do? also once SIM unlocked does it ever get locked again - etc!
bengilih, unlike i, you must have more than a high school education, i have read all you threads, they are, IMHO, the most easy to understand and read.
i now know more now today than i did yesterday., you have taken what has already been posted and putting it in one place makes it so much easier for guys like me. all the people you give credit to do an incredible job, but sometimes i do not understand. you make it easy for the everyday "Joe" like me. thank you,
happy to be using bengilih's
SASHIMI RAW AutoInstaller v.3.0
http://forum.xda-developers.com/showthread.php?t=392983
thanks again
Lupe
As usual a very through, informative, non-biased and exciting thread. Keep on the good work!
Cheers mate,
KOR!
elmoono said:
Greeat guide that really explains what spl is about, like you say should be on the Wiki.
Bengalih, perhaps you could add some info on CID unlocking - this also leads to confusion when reading the threads. Like once CID unlocked do you need hardspl? will flashing the wwe spl make the device CID locked again? Is there a diference between CID and Super CID unlock? What exactly does CID do? also once SIM unlocked does it ever get locked again - etc!
Click to expand...
Click to collapse
I updated post #4 with some info on that. I don't know if i have all the information to go fully into that. Hopefully other's will contribute and I will update the main thread.
_Alex_ said:
Creating a new page on the wiki is as easy as creating a link on existing page and then clicking on that link and editing the content for the new page.
As you've seen with your other threads, this thread too will be lost. Wiki entries are easy to find and able to be edited by all.
This thread should exist as the discussion thread for the wiki page for questions & comments, not the main text.
Click to expand...
Click to collapse
Ok thanks _Alex_ I will try to put this in the Wiki soon, along with my other threads.
To clarify, I just go to a page that I want to link ot my page, create a link to a Non-Existent page, and then click on that link and it will create the new page?
As I have explained in the past I use wikis for reference but have had an aversion to using them to post information (hey, I don't like other people messing up my hard work ). So I guess I don't know the basics there...
Also, is there a particular page that you feel I should begin the linkage to?
thx again
overhaulengines said:
bengilih, unlike i, you must have more than a high school education, i have read all you threads, they are, IMHO, the most easy to understand and read.
i now know more now today than i did yesterday., you have taken what has already been posted and putting it in one place makes it so much easier for guys like me. all the people you give credit to do an incredible job, but sometimes i do not understand. you make it easy for the everyday "Joe" like me. thank you,
happy to be using bengilih's
SASHIMI RAW AutoInstaller v.3.0
http://forum.xda-developers.com/showthread.php?t=392983
thanks again
Lupe
Click to expand...
Click to collapse
Thanks man... but, unlike yourself I'm lucky if I can change the oil in my car
bengalih said:
Ok thanks _Alex_ I will try to put this in the Wiki soon, along with my other threads.
To clarify, I just go to a page that I want to link ot my page, create a link to a Non-Existent page, and then click on that link and it will create the new page?
As I have explained in the past I use wikis for reference but have had an aversion to using them to post information (hey, I don't like other people messing up my hard work ). So I guess I don't know the basics there...
Also, is there a particular page that you feel I should begin the linkage to?
thx again
Click to expand...
Click to collapse
You got the jist of it
The style and formatting isn't always straight forward, so just view the source of another wiki page (by clicking edit) and borrow the wiki code.
Ta
Dave
bengalih said:
Ok thanks _Alex_ I will try to put this in the Wiki soon, along with my other threads.
To clarify, I just go to a page that I want to link ot my page, create a link to a Non-Existent page, and then click on that link and it will create the new page?
As I have explained in the past I use wikis for reference but have had an aversion to using them to post information (hey, I don't like other people messing up my hard work ). So I guess I don't know the basics there...
Also, is there a particular page that you feel I should begin the linkage to?
thx again
Click to expand...
Click to collapse
I utilize the wiki often. However, I do not believe n00bs or the sp00ns do. They at least use the search function, which is unfortunate because the search function does not direct searchers to the wiki.
redbandana said:
I utilize the wiki often. However, I do not believe n00bs or the sp00ns do. They at least use the search function, which is unfortunate because the search function does not direct searchers to the wiki.
Click to expand...
Click to collapse
I agree. I will keep all my posts where the are AND post them in the Wiki. Once they are in the Wiki I will update the posts to say to make sure to check the Wiki for the most up-to-date info, and provide the link.
bengalih said:
Ok thanks _Alex_ I will try to put this in the Wiki soon, along with my other threads.
To clarify, I just go to a page that I want to link ot my page, create a link to a Non-Existent page, and then click on that link and it will create the new page?
Click to expand...
Click to collapse
I didn't expect this thread to be updated so quickly. I actually edited the original post to include:
http://wiki.xda-developers.com/index.php?pagename=AddingPages
There are also links/backlinks to other wiki documentation pages should you have any formatting questions. As others have mentioned, most people find it easier to just edit an existing page and see what formatting was used there.
bengalih said:
As I have explained in the past I use wikis for reference but have had an aversion to using them to post information (hey, I don't like other people messing up my hard work ). So I guess I don't know the basics there...
Click to expand...
Click to collapse
Most of the wiki pages remain un-vandalized, but on occasion, people put all sorts of junk up. Another good thing is, the wiki stores previous revisions (up to 2+ months worth or 30+ amount of edits, whatever is greater), so anything can be recovered, even your own misedits (which occur from time to time).
bengalih said:
Also, is there a particular page that you feel I should begin the linkage to?
thx again
Click to expand...
Click to collapse
Create links on the main Kaiser page, as most things are linked there and then create Q/A links in the Kaiser FAQ, as we try to direct n00bs to search terms there first.
Hope this helps!
thank you
at least now iv an idea of what I was doing all this while

How does tools in cooking sets work?

Hello,
I have question about what is everything in NBH - I mean what is os.nb.payload, os.nb.extra, XIP and such, I tried searching but couldn't find anything to it, where someone would explain what it actually is, how does it work, what can I change in it, how do it etc.
And also I got question about how to insert pkg's into cook ROM, just copy it there?
Then also how does BuildOS.exe works (building registry, "copying" everything to dump from all folders etc).
I mean like explaining everything so anyone could learn from it the lowest basics of cooking. I'm interested in it and want to make completely new cooking kit, but I can't find anything about it.
Hope someone finds who can explain at least something of it.
Thanks a lot!
PS: Maybe it will be better Hacking & Developing section?
did you search in the dev & hack forum?
man! you don't ask those questions here. either not in hacking.
only answer you'll get is ban from moderator.
It's kind of rude to ask in forum with milions of msgs in archives basic questions. Use search. look around, you'll find nice wiki in here too! with step-by-step and lot's of stuff to put in.
ok, but as i just start another post about nothing...
you'll get nice general idea from very basic kitchen. get a "kaiser_kitchen"
or better, "KaiserCook v1 Yardie.Spike's" it's just copy of the same, but you'll have more recent utils there.
go through wiki "how to cook" in kaiser section.
http://wiki.xda-developers.com/index.php?pagename=HTC_Kaiser
you'll find everything there.
and get the last htc rom. not from at&t, get this from htc: 3.34.721.2
if you want to know everything, open batch (cmd) in text edit and watch it working.
It's really simple with all those pretty tools from nice guys here on forum.
a kdyby neco napis private only cos here EN ONLY.
I'm not sure I wrote it good what I'm really looking for, I'm feeling a bit dizzy so I will try to explain it (sorry for it):
I want to found out how does the "Building registry" or how does it work everything in BuildOS.exe and such works, but I couldn't find source (bepe doesn't want to share it I've found). That's why I'm asking, because I couldn't find it. Not because I want to know what tool what does, but HOW does the tool does it. I tried searching, believe me, but there's plenty of pages that talks only about "click on play button and when it says Done, close it", but none of them says how does it actually work, what it loads and saves, in what directory structure.
// Ooh, I got it what's it about - I've written it once, but I managed to find "what is what" things and wanted to left only "how does work", but send both of it, sorry!
papo said:
man! you don't ask those questions here. either not in hacking.
only answer you'll get is ban from moderator.
It's kind of rude to ask in forum with milions of msgs in archives basic questions. Use search. look around, you'll find nice wiki in here too! with step-by-step and lot's of stuff to put in.
ok, but as i just start another post about nothing...
you'll get nice general idea from very basic kitchen. get a "kaiser_kitchen"
or better, "KaiserCook v1 Yardie.Spike's" it's just copy of the same, but you'll have more recent utils there.
go through wiki "how to cook" in kaiser section.
http://wiki.xda-developers.com/index.php?pagename=HTC_Kaiser
you'll find everything there.
and get the last htc rom. not from at&t, get this from htc: 3.34.721.2
if you want to know everything, open batch (cmd) in text edit and watch it working.
It's really simple with all those pretty tools from nice guys here on forum.
a kdyby neco napis private only cos here EN ONLY.
Click to expand...
Click to collapse
lol he'll get banned for what? asking how something works? starting new thread? i dont think so!
OndraSter said:
I'm not sure I wrote it good what I'm really looking for, I'm feeling a bit dizzy so I will try to explain it (sorry for it):
I want to found out how does the "Building registry" or how does it work everything in BuildOS.exe and such works, but I couldn't find source (bepe doesn't want to share it I've found). That's why I'm asking, because I couldn't find it. Not because I want to know what tool what does, but HOW does the tool does it. I tried searching, believe me, but there's plenty of pages that talks only about "click on play button and when it says Done, close it", but none of them says how does it actually work, what it loads and saves, in what directory structure.
// Ooh, I got it what's it about - I've written it once, but I managed to find "what is what" things and wanted to left only "how does work", but send both of it, sorry!
Click to expand...
Click to collapse
I am not sure if I can answer all the questions you have! But try searching using the link in my sign, and you can usually find what you want. I am sure all the questions you have has been answered before. Good luck!
Perhaps looking at this thread, the general Kitchen and then TPC/Josh' Kitchen thread will bring better understanding.
Reverse Engineering is tough IMHO, and lots of the tools are developed by people with skill and having the tools and guts to try it out. The knowledge are gathered by experience.
what questions exactly would you like to know?
I was thinking about "higher" tools like BuildOS.exe how do they work, currently just only this one, but now I have some thoughts about doing reverse ingeneering, so I will try something myself first. But if anyone knows answer to BuildOS.exe working:
- processing OEM, SYS and ROM (=> just only recursively copy?)
- "Building registry" - take all .rgu and .provxml and put them in one? Or just only .rgu and .provxml save separately?
PS: Yes, I can read .bat-s from kitchen and such, I tried to do something, but it's always "run this program, click on this and then close" and didn't manage to google anything about the process in BuildOS.exe ^.
PPS: Actually I'm interested in cooking via TPC & Joshkoss kitchen - pretty awesome tho. Deleting unneeded stuff from SYS is fun. (Testing on emulator.) And you don't need to know the building process (actually when not knowing it you can still just rewrite somebody's kitchen with some tweaks). But I'm just only curious as many people is.

Categories

Resources