Hello!
I thought I'd contribute back to the Kaiser community by starting a wiki page with what I've discovered about packages while cooking and cleaning my own ROM.
12-07-07 Update: Major overhaul with more content! Great read for all cooks and chefs...
OEM Package Tutorial
If you have any comments or questions about this tutorial, please reply to this thread. Thanks!
Nice, thanks!
_Alex_ said:
Hello!
I thought I'd contribute back to the Kaiser community by starting a wiki page with what I've discovered about packages while cooking and cleaning my own ROM.
Most of the material I've read is outdated and scattered, so hopefully this will save time for novice chefs.
Please note that this is the first draft / rough outline. More content to follow...
Kaiser OEM Package Tutorial
Click to expand...
Click to collapse
Great
Really good contribution... I'll add a link in the KaiserKitchen second post...
Cheers.
Nice Work...
Its always nice to see some of the newer members active and contributing. The write-up is good and I think it will help a lot of Rom "Sous" Chefs as they start experimenting with their own creations.
BTW, thanks for the kudos. The best pay-off is seeing that my efforts have inspired others to strike-out on their own. I also want to say good work on adding a Wiki page instead of just leaving the info in a thread somewhere.
Great guide.
Makes me want to try it.
Just go to my signature, i have wrote it too,.
Garmin, that's a great tutorial for the manual process for converting OEM packages to cabs.
Just wanted to make sure you're aware that Ervius package creator automatically converts cabs into the following, which makes things alot easier:
initflashfiles.txt from file structure found in cab
links found in .inf and/or setup.xml
randomly generated UUID
rgu from setup.xml or .inf
option.xml
Hope this helps.
_Alex_ said:
Garmin, that's a great tutorial for the manual process for converting OEM packages to cabs.
Just wanted to make sure you're aware that Ervius package creator automatically converts cabs into the following, which makes things alot easier:
initflashfiles.txt from file structure found in cab
links found in .inf and/or setup.xml
randomly generated UUID
rgu from setup.xml or .inf
option.xml
Hope this helps.
Click to expand...
Click to collapse
hehehe,.
thanks buddy,.
but many people dont understand it like you did,.
yeah agree nice one mate, Great idea.
True, i do build upon existing works to inform folks of the most efficient way to build an OEM package...
I've added your tutorial into the wiki page as a 'primer', should anyone not understand my text.
Maybe I'll find the time to write my own primer, or someone else could take up the challenge?
Folks, all in good intention but the Tutorial is fairly steep.
I don't consider myself is all thumbs but plowing through them is going to be not just a week effort and at the end it is still in monkey see, monkey do level.
To put it in a simple way, (I will stand for correction). Most people who strode around this forum is only expected to spent "Basic" level in stead of "C++" level programing effort to get what they want or solve their problem. Most will only have the ability to play with a few different ROM's but not to cook them. I really like Palm, it is much simpler and much faster machine for given same horse power. But its founders just grabbed the money and went fishing and left it to rot and we have to entertain M$.
My intent was not to write a tutorial understandable by all, as clearly stated within the preface. The tutorial is geared towards intermediates who have already dabbled.
The tutorial that's missing is the ROM kitchen one. In the ROM Kitchen thread, jcespi2005 says he has one in the works, so I didn't want to step on his toes. When that comes out, I would hope for it to be alot easier to understand than my intermediate OEM package tutorial.
I've done a major overhaul to this tutorial, knowing that more people will be reading it with the release of the Kaiser ROM Kitchen tutorial...
It should prove to be a good read for all interested in building OEM packages.
Need help for not able to convert .cab to Package
I was trying to convert some .cab files into Packages using Ervius Package Creator. Following the instruction 1. Click on "Open CAB file" and select a cab file to convert.
Then I just pick a .cab file (tried different ones but same error message)
Before I could go to the 2nd step of "Extract CAB files with original names in a folder", I got the error message:
x Erreur d"insertion de ligne RichEdit
I can't read Italian ?!
What went wrong?
jychan28 said:
I was trying to convert some .cab files into Packages using Ervius Package Creator. Following the instruction 1. Click on "Open CAB file" and select a cab file to convert.
Then I just pick a .cab file (tried different ones but same error message)
Before I could go to the 2nd step of "Extract CAB files with original names in a folder", I got the error message:
x Erreur d"insertion de ligne RichEdit
I can't read Italian ?!
What went wrong?
Click to expand...
Click to collapse
Hi... I went to google translate and translated the french error message from MSCEINF which means 'Error of insertion line RichEdit'. This doesn't mean much to me either
If you run MSCEINF.exe, click on the first icon cab with the caption 'Choose a CE installation file', open the cab and click on the icon with the caption 'Extract CAB Files with original names in a folder', does the same thing happen? If so, you may need to ask the original author. His thread is here: http://forum.xda-developers.com/showthread.php?t=347397&highlight=msceinf
Hope this helps...
Alex, I downloaded all you files and setup all the file directories as described. I downloaded more packages.
I want to add a few more .cab and needed to convert them into packages.
It was frustrating for hours. I have re-download the MSCEinf.exe file a few times.
I Unziped it and renamed it to MSCEinfen.exe as instructed.
Then click on packages creator 5.4.exe, check the boxes as instructed.
Click on Open cab file, select a .cab file in one of the directory, then it automatically execute MSCEinfen.exe and the error message poped
I even tried to execute packages creator 5.4.exe in a DOS black box. Same problem and same result.
Click on anything else will eventually cancel the procedure and back to square zero.
What could be the problem?
I Got The Same Problem.
I'm confidence that I strictly follow the instruction of converting cab to OEM package, and got the same error message like you do.
I try to translate the message with google, looks the language is French translated to English as "Error inserting line RichEdit".
Good News, I just solved this problem in my machine.
I changed the "Language for non-Unicode Program" to "English (United State)", the error message gone, and my MSCEInfEn works well now. I not sure it works for everybody, welcome to post with your result, maybe in other language. Thanks.
Anyone getting an Unhandled exception error after clicking on "Go"? I've done the following:
1) DL and Extract kaiserkitchen
2) Extract the build/package tools (3 files) to the folder where I installed kaiserkitchen
3) DL and Extracted AT&T Ultraclean ROM folders (3 folders) to the kaiserkitchen folder
4) DL and extracted AT&T OEM packages
When I start up the program I can select the AT&T OEM Packages. I left at default and hit Go but get the unhandled exception error.
Also, it doesn't seem like the AT&T OEM Packages contains any Registry Tweaks. Is there a separate package to dl that contains the registry tweaks? A few days ago I know there was an AT&T OEM package that had the registry tweaks.
I'm attaching a capture of the error. Appreciate any feedback.
Thanks.
Update:
I tried doing this again with ROM Folders and AT&T OEM Package I downloaded on 12/8/07 and it works fine. No error when building as outlined above.
-Mike
ecltech said:
Anyone getting an Unhandled exception error after clicking on "Go"? I've done the following:
1) DL and Extract kaiserkitchen
2) Extract the build/package tools (3 files) to the folder where I installed kaiserkitchen
3) DL and Extracted AT&T Ultraclean ROM folders (3 folders) to the kaiserkitchen folder
4) DL and extracted AT&T OEM packages
When I start up the program I can select the AT&T OEM Packages. I left at default and hit Go but get the unhandled exception error.
Also, it doesn't seem like the AT&T OEM Packages contains any Registry Tweaks. Is there a separate package to dl that contains the registry tweaks? A few days ago I know there was an AT&T OEM package that had the registry tweaks.
I'm attaching a capture of the error. Appreciate any feedback.
Thanks.
Update:
I tried doing this again with ROM Folders and AT&T OEM Package I downloaded on 12/8/07 and it works fine. No error when building as outlined above.
-Mike
Click to expand...
Click to collapse
See these posts: http://forum.xda-developers.com/showpost.php?p=1745239&postcount=105, http://forum.xda-developers.com/showpost.php?p=1747265&postcount=117 & http://forum.xda-developers.com/showpost.php?p=1747298&postcount=119. Alot more info can be found in that thread, so you might want to read up there...
Hope this helps...
I was trying to convert some .cab files into Packages using Ervius Package Creator. Following the instruction 1. Click on "Open CAB file" and select a cab file to convert.
Then I just pick a .cab file (tried different ones but same error message)
Before I could go to the 2nd step of "Extract CAB files with original names in a folder", I got the error message:
x Erreur d"insertion de ligne RichEdit
I can't read Italian ?!
Could some experience cook able to tell me what I did wrong?
Many thanks!
In the future, please follow the instructions on the OEM Package Tutorial wiki more carefully, specifically the text found in the first two lines:
"If you have any questions or comments, please reply here:
http://forum.xda-developers.com/showthread.php?p=1692110#post1692110"
This way we can keep the number of threads down with ALL THE INFORMATION TOGETHER IN ONE THREAD.
I've also provided the answer to your problem by changing the installation steps. Please see step 1 of 'Setting up and running for the first time'.
If you have any other questions or comments, USE THE THREAD ABOVE!
Hello,
I need help in making a Device Lock icon for the the HTChomeplug. Believe me, I did my search and I came up with nothing. I followed the steps mentioned in the link below, however the problem was that I couldn't find the *.exe file associated with the device lock program. the best thing I found was this:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Today\Items\"Device Lock"]
I would highly appreciate if someone can assist me
The link I was trying to follow the instructions from was this one:
http://forum.xda-developers.com/showthread.php?t=308250&highlight=htc+home+today
Thank you in advance
bump
Please help
http://www.vijay555.com/?Releases:VJDeviceLock
XtreMe_G, THANK YOU VERY MUCH...
I was able to do it! if some one is interested in doing the same just download the CAB file from the website XtreMe_G mentioned. Follow the steps on the website I mentioned on my first post. When you come to writing the code for the registry use the following:
Code:
iconindex = 101
LaunchApPath = \Program Files/Vijay555/VJDeviceLock/VJDeviceLock.exe
ResPath = \Program Files/Vijay555/VJDeviceLock/VJDeviceLock.exe
Thanks again XtreMe_G
PS. I gatta mention that the icon looks really ugly. Is there a way I can use a different one; say, one from my own...
I have been working on a project to insert debug messages in low level dlls [like coredll, ws2.dll] and so on. The testing so far was done on device emulators and the .nb0 image seems to be pretty stable on it now.
Where I need help from xda community is how to take the next step - how to generate a ROM image for my kaiser. Specifically what all build options should be specified to my platform builder to get the right image for my device.
I tried to search previous postings for help but could not find one - may be I did not search thoroughly. My apologies if I did not search thoroughly - if it has been discussed in the past - would be great if someone could point me a link to it.
Thnx
TPC and myself has kitchens available for download. Pick one and replace your files, and build ROM.
To be precise - download a kitchen from here?
http://m-s-j.net/tpckitchen/kitchens/
poifgh said:
To be precise - download a kitchen from here?
http://m-s-j.net/tpckitchen/kitchens/
Click to expand...
Click to collapse
yes any one will work
Thnx for helping .. have a few hickups setting the ROM up.
1. Downloaded http://m-s-j.net/tpckitchen/kitchens/TPC_KITCHEN_6.120146.7z
2. Doing a build_rom.bat results in the following errors
Failed to set data for 'htcrt_backup'
"There is no device found to meet your project configuration. Try to update your devices file with new one."
"Access Violation - read at 000000"
Do I need to setup some config file somewhere - do we have a README for the process?
3. I dont quite understand the point "replace your files, and build ROM."
I have changes done to coredll and ws2.dll which were compiled using the 'emulator' flag in platform builder
a. What compile flags should the I use before I copy/paste my dlls into the kitchen
b. In the current kitchen - coredll is a directory containing 5 files S00 to S04 and also contains imageinfo files. Do I put in my coredll.dll file? or is there a step in between?
As you could see from my questions, I am complete newbee in building ROMs for phones - would appreciate any help from the community
thnx
I guess you're using Vista, right? It did me too. There are two (three?) solutions:
1. Disable UAC
2. Ignore it and via htc rom tool build .nbh by yourself (click right -> run as administrator on TOOLS\htcrt.exe) - OS.nb is in TMP directory
3. (not confirmed) Run the build script via cmdline manually, AFAIK TPC has got it written somewhere there.
poifgh said:
Thnx for helping .. have a few hickups setting the ROM up.
1. Downloaded http://m-s-j.net/tpckitchen/kitchens/TPC_KITCHEN_6.120146.7z
2. Doing a build_rom.bat results in the following errors
Failed to set data for 'htcrt_backup'
"There is no device found to meet your project configuration. Try to update your devices file with new one."
"Access Violation - read at 000000"
Do I need to setup some config file somewhere - do we have a README for the process?
3. I dont quite understand the point "replace your files, and build ROM."
I have changes done to coredll and ws2.dll which were compiled using the 'emulator' flag in platform builder
a. What compile flags should the I use before I copy/paste my dlls into the kitchen
b. In the current kitchen - coredll is a directory containing 5 files S00 to S04 and also contains imageinfo files. Do I put in my coredll.dll file? or is there a step in between?
As you could see from my questions, I am complete newbee in building ROMs for phones - would appreciate any help from the community
thnx
Click to expand...
Click to collapse
this is not the right place to be asking this, if you have questions about my kitchen you need to look in my kitchen thread. you will find the answers to your questions have already been posted there and if you need more help ask there and we will help you.
twopumpchump said:
this is not the right place to be asking this, if you have questions about my kitchen you need to look in my kitchen thread. you will find the answers to your questions have already been posted there and if you need more help ask there and we will help you.
Click to expand...
Click to collapse
you know how it is anymore, Have a question = START A NEW THREAD.
msd24200 said:
you know how it is anymore, Have a question = START A NEW THREAD.
Click to expand...
Click to collapse
= Flying Fishheads lol
Here you go guys. Please help each other out using this thread on the how to.
It is pretty straight forward. Just read the READ-ME folder.
I highly recommend using the Factory Flasher version A.05 !
Download Link here: https://mega.nz/#F!70hwFCTa!Kiy6R0TeL70QrLGuvOHFAA
ColorOS A.05 will allow for use of the OppoTools.
Which can be used to gain root access.
Such as seen on my guide here:
https://forum.xda-developers.com/r7...very-official-twrp-oppo-r7sf-3-0-2-0-t3358552
Look at the buttom for the PDF Guide.
Please do NOT PM me for help.
I won't reply. I already have hundreds of unread PM's. I simply don't have time for replying.
So please help each other out.
a short screenshot guide (NOT BY ME!):
just ignore the device model number shown in one of the screenshots and select the proper one.
Hey,
sorry to bug you, I know you're incredibly busy. I've gone to your provided link and downloaded the R7sfEX_11_A.05_151119 Factory Flasher file.
Only thing is - there is no readme. Not in the archive, not at your link. I need the readme to know what to do.
Am I being stupid, or is it nowhere to be found?
Cheers
zaako said:
Hey,
sorry to bug you, I know you're incredibly busy. I've gone to your provided link and downloaded the R7sfEX_11_A.05_151119 Factory Flasher file.
Only thing is - there is no readme. Not in the archive, not at your link. I need the readme to know what to do.
Am I being stupid, or is it nowhere to be found?
Cheers
Click to expand...
Click to collapse
i just noticed the DownloadTool is missing from the A.05 package.
Do this to unbrick:
download the R7sfEX_11_A.06_151210.7z package.
unpack it and install the Qualcomm Driver in the READ-ME folder.
run the "Msm8x39DownloadTool.exe" select the device model which is listed in the "Instructions.txt"
with this package your R7S is unbrickable.
if you want the A.05 version.
do the same just copy the md5sum.exe and Msm8x39DownloadTool.exe from the A.06 package to the A.05 package and follow the same procedure.
at everyone using those packages.
feel free to write a step by step instruction (maybe with screenshots) and include it in this thread!
i've uploaded one older version and the latest i could find to my archive.
older version R7sfEX_11_A.03_151105.7z (rooting works with OppoTools)
newer version R7sfEX_11_A.11_160721.7z (rooting does not work with OppoTools, downgrade to A.05!)
i also came across a possible list of factory flasher versions.
R7sfEX_11_A.03_151105.tar.bz2 (in archive)
R7sfEX_11_A.05_151119.tar.bz2 (in archive)
R7sfEX_11_A.10_160421.tar(1).bz2 (missing)
R7sfEX_11_A.11_160721.tar.bz2 (in archive)
R7sfEX_11_A.12_160809.tar.bz2 (missing)
R7sfEX_11_A.13_170311.tar.bz2 (missing)
if anyone comes across one of the missing packages. please mirror a direct download link and i will push it into my mirror.
Can this thread be updated. Had an old phone lying around and need to reflasg. Cant get into download mode.
Thanks guys x