Database Develop

Sorry

I posted this for the few people that were awaiting for the Herald kitchen.
So..i know that you must probably hate me till now, but sorry again i have to delay the porting of my Core Kitchen to the Herald.
It has come to my attention that there is still no way of flashing an Terra because there is no RUU and thus no means of flashing. I will see what i can do, meanwhile i got some work and i will leave for about 5 days.
If anybody has any ideas on how to help these people, please put it into action or give me a pm.
Cheers !

you can flash using Aserg's method which is what other cooker's have resorted to!

blackout203 said:
you can flash using Aserg's method which is what other cooker's have resorted to!
Click to expand...
Click to collapse
From what i understood ...
Aserg's method only works from ActiveSync . So this means that if you cook a rom with my kitchen and make a mistake and the rom doesn't work then you have a brick. That's why i didn't focused my attention on this. I was waiting for a proper RUU so that people wouldn't brick they're devices.
Hope you understand.

Well hopefully they roll out that new RUU for WM6 before the months end. Would love to do some experimenting with it during my vacation next month.

anichillus said:
From what i understood ...
Aserg's method only works from ActiveSync . So this means that if you cook a rom with my kitchen and make a mistake and the rom doesn't work then you have a brick. That's why i didn't focused my attention on this. I was waiting for a proper RUU so that people wouldn't brick they're devices.
Hope you understand.
Click to expand...
Click to collapse
Yes that´s true. And nothing to say sorry - you had enough trouble with your PC.
But this is what I got as away for falshing from bootloader.
The problem is that the singing of the nbh file doesn´t worfk correctly - i guess.
I've been using his tool from:
http://forum.xda-developers.com/showthread.php?t=311909
He doesn't really show a method, so what I've been doing is:
1. Using NBHExtract to dump an .nbh that's on the Herald Wiki.
2. I rebuild the .nbh using Dark Simpson's little utility using the information I had luckily written down before I bricked the phone. So I plug in my ROM (4.10.531.3) in the Version, HERA110 in Device ID. The only other thing is that I'm not sure about the CID.
3. Place the new .nbh file in a folder with an updater (the ROM Update Utility that comes with the ROMs from the Herald Wiki).
4. Get the phone into Bootloader mode, start the updater.
In this way I've got rid of the Invalid Device ID error (error 243 or something?) and now it goes to 3% and tells me that the image file is corrupt.
I'm very new at this so maybe you can see a flaw in what I'm doing, or maybe with your knowledge we can figure this out. I was *almost* to the point of trying to cook using a couple links you've posted (XIP, dumps, etc) and then put it all together in a signed .nbh, but Rapidshare was holding me back... making me wait 80 minutes between downloads -_-
Anyway... I've only been trying to update the OS.nb portion since I believe I only screwed up my OS, not anything else. I can still get into the bootloader, my IPL/SPL still reads 4.xxxxxx, and by "brick" I mean that the phone just hangs on bootup at the T-Mobile splash screen. Correct? Incorrect?
Click to expand...
Click to collapse
Perhaps we can work with it.

It is not a huge problem for HTC branded devices as there is a RUU to flash with if everything goes wrong. It's just a problem for our T-Mobile Wing and O2 Terra cousins (if they brick their devices). But it's nice to see some proper chefs taking an interest, never liked the pdaviet ROMS ever since they used a whole bunch of Faria's stuff without asking.

im running pdaviet now, but im hoping to see something other soon, its not bad though, just a bit slow..lots of "lagging" on the today plugin, I used the herald dump from tupisdin earlier, and installed my fav progs on that...was pretty dam fast on my phone...only problem was that it occupied more space on the main memory when stuff was not cooked into the rom itself...
trying to learn about cooking myself, not so easy as a thought
But I guess im lucky to have a unbranded htc p4350, If i brick, I just install the official Ruu from HTC
(btw, I DO use Vista for flashing, just changed the usb driver that WMDC uses to connect via USB to the old activesync 4.5 USB driver...)

What exactly is hardSPL? USPL vs hardSPL

I apologize in advance if my questions are trivial and I am just dense.
I am pretty sure I've read through all the threads for "n00bs" but I still can't get a grasp of what exactly hardSPL does or is. I ran the search function and found that I don't NEED it per say and has claimed that it actually is "safer" to use USPL.
I own a Tmobile Wing (IPL > 4.xxx)
1. What exactly is the difference between USPL and hardSPL?
2. What are the limitations of either one.. will flashing a cooked rom without hardSPL cause problems?
3. I currently have flashed the newest Open Touch 4.0 and haven't had any problems at all (USPL), but I noticed in the thread for Touch-IT, it says that hardSPL is required. What does that mean exactly? If I flashed it w/o hardSPL.. will my wing crash/brick?
4. At some point, I'd like to sell the phone, so I don't want to do anything that is irreversible. My understanding was USPL is reversible, hardSPL is not?
5. I was on the verge of flashing the hardSPL but chickened out.
I installed the three cab files (canonyang.cab aserpolicy.cab disablesecurity.cab) but decided I wasn't ready to flash.
Will that cause any problems (installing the .cabs but not flashing)?
any help/input would be greatly appreciated. Sorry for all the n00b questions. Thanks

Essentially what you are doing is changing the Bootloader so you can install a different ROM regardless if it's signed.
USPL and HardSPL is a matter of having it done temporarely or permenantly.
USPL (temporary), is the safe route. This will allow you to Install one USPL capable ROMs per USPL. So if you're not a big flasher, and thinking about selling your phone in the near future, then you might want to stick to this method.
HardSPL (permenant), is the only TRUE way of bricking your phone. You will flash the bootloader for good so that you can constantly flash new ROMs without having to worry about flashing your bootloader of making sure it's a signed ROM. For heavy flashers, like myself, this is the ideal route.
HardSPL is reversible, there are some threads on how to do that. If I remember correctly, you have to flash back to a Stock T-Mo ROM.
Some ROMs require HardSPL because sometimes the cooks use different methods to flash ROMs onto devices other than ActiveSync (which is needed for flashing via USPL).
For example, ttran001's Open Touch V4.0 Micro ROM flashes onto your device using your SDCard, the phone is never connected to you PC so no opertunity to USPL. If it was not HardSPL'd, the ROM would be rejected. If it was, the flash would continue flawlessly.
I hope this answers your questions, and please, if I got anything wrong, correct me.
Regards,

three4seven said:
5. I was on the verge of flashing the hardSPL but chickened out.
I installed the three cab files (canonyang.cab aserpolicy.cab disablesecurity.cab) but decided I wasn't ready to flash.
Will that cause any problems (installing the .cabs but not flashing)?
any help/input would be greatly appreciated. Sorry for all the n00b questions. Thanks
Click to expand...
Click to collapse
Oh and from what I understand, installing those cabs wont hurt your device if you dont HardSPL. I believe you can uninstall them from the "remove program" which can be found under Settings/System/Remove Programs.
Everyone's allowed a Noob question every now and then I only know all this info because I read, so im sure if you read u'll be just fine.

nKiwan, thanks for quick and throrough reply
I get a little lost with this:
nKiwan said:
This will allow you to Install one USPL capable ROMs per USPL.
Click to expand...
Click to collapse
what does that mean exactly?
perhaps I should start by asking the USPL acronym stands for - I've googled it and I couldn't find the right acronym.
From my understanding.. the only real difference (besides one uspl rom per uspl vs infinite - i'm still a little hazy on that) is that hardSPL allows for flashing outside of activesync?
thanks again... I swear I tried my best using the search function and reading

Well, correct me if i'm wrong, if you do not HardSPL, then you must USPL your device everytime you wish to flash your device. This will temporarely change your bootloader so it will allow you to flash a non signed ROM, a.k.a. an "outside" ROM. USPL capable ROMs, are ROMs that you can flash using USPL, therefore, ActiveSync.
Well there are two differences I guess... HardSPL, basically, allows for flashing outside of ActiveSync; and will allow you to flash any ROM as many times as you would like, once HardSPL'd.
As far as the acronym goes, I have NO clue lol. Never bothered to find out, I guess it would be helpful to know .

nKiwan said:
Well, correct me if i'm wrong, if you do not HardSPL, then you must USPL your device everytime you wish to flash your device.
hardSPL.... will allow you to flash any ROM as many times as you would like, once HardSPL'd.
Click to expand...
Click to collapse
Technically then.. I could also flash any rom as many times as I want using USPL as long as I run USPL.exe? I read the flashing guide several times. The only difference I found was that you run USPL.exe and it goes through a loader instead of just running the RUU flaser. Is that right?
i apologize once again if I am being incredibly dense.
thanks again for putting up with my n00bness

there ya go! you got it. As you become more experienced you'll start to understand the need of HardSPL.
I was once a noob myself, so i understand where u coming from . Just glad I can help.
Regards,

nkiwan - thank you so much for answering my barrage of n00b questions.
You have been a great help. I really appreciate it.

Wow I think this is the coolest thread I have read ...it is just awesome what the WWW has done for all of us and thanks for the info

Glad I can help

I can understnad the use of USPL but I would recommend the use of hard SPL if you are planning to flash multiple roms. Either way I think it is just a matter of whether or not you actually want to run the USPL everytime you want to flash a rom... Don't quote me on that.

Just to doublecheck myself....
If I use USPL method and hard reset my phone - will I have the stock rom or the flashed one?
if I understand correctly USPL will bring back the stock one after hard reset and HSPL the new one.

very sorry to ask this now..from what i get is there are 3 ways of turning ur phone from phone to super phone:
1. install .cabs
2.soft flashing
3.hard flashing???
am i rite??

nKiwan said:
As far as the acronym goes, I have NO clue lol. Never bothered to find out, I guess it would be helpful to know .
Click to expand...
Click to collapse
I found this thread that you might find useful for the acronyms:xdasite.com/showthread.php?t=1104

Same was with me.....
three4seven said:
I apologize in advance if my questions are trivial and I am just dense.
I am pretty sure I've read through all the threads for "n00bs" but I still can't get a grasp of what exactly hardSPL does or is. I ran the search function and found that I don't NEED it per say and has claimed that it actually is "safer" to use USPL.
I own a Tmobile Wing (IPL > 4.xxx)
1. What exactly is the difference between USPL and hardSPL?
2. What are the limitations of either one.. will flashing a cooked rom without hardSPL cause problems?
3. I currently have flashed the newest Open Touch 4.0 and haven't had any problems at all (USPL), but I noticed in the thread for Touch-IT, it says that hardSPL is required. What does that mean exactly? If I flashed it w/o hardSPL.. will my wing crash/brick?
4. At some point, I'd like to sell the phone, so I don't want to do anything that is irreversible. My understanding was USPL is reversible, hardSPL is not?
5. I was on the verge of flashing the hardSPL but chickened out.
I installed the three cab files (canonyang.cab aserpolicy.cab disablesecurity.cab) but decided I wasn't ready to flash.
Will that cause any problems (installing the .cabs but not flashing)?
any help/input would be greatly appreciated. Sorry for all the n00b questions. Thanks
Click to expand...
Click to collapse
Hi Brother,
Same problem with me i have also search every where but failed... no answer about Hard spl.Every body say do hard spl and search in fourm and so on. There was no proper guide what it is and how to do. i was really puzzel. Now i have come to know that axect what it is Hard Spl.
Hard Spl mean CID unlock. If you unlock CId of the phone its mean you have done Hard SPl. Without CID unlock you can not write ROM.
Thanks
Br Raja

I have a T-Mobile Wing. I hardSPL'd it, installed a custom ROM, then I used the RUU to flash the original ROM back to it. It doesn't show the CanonYang startup screen, but the SPL version is still 4.70.Yang. Is it still HardSPL'd?

Stargazer418 said:
I have a T-Mobile Wing. I hardSPL'd it, installed a custom ROM, then I used the RUU to flash the original ROM back to it. It doesn't show the CanonYang startup screen, but the SPL version is still 4.70.Yang. Is it still HardSPL'd?
Click to expand...
Click to collapse
You can always check in the bootloader screen (the RGB screen).
Even if you have a 4.70.Yang you still need the IPL to be higher than 4 to flash custom ROMs. That is what is important.
If you ever see any of these number's change, Run the HardSPL folder again.

extract file from *.nbh ( ROM file )

Is it possible to extract mp3 files from the rom file ruu_signed.nbh?

i think what ur looking for is easy, there are plenty of software out there that could give you that. I remember using Koch nbh by dutty for Hermes but works fine for the Rhodium ONLY to extract files and not to combine.
But the real question is: how can cook an nb file back to nbh file? because I would like to go back to WWE rom, and I thought of extract the nbh file and pulling out the windows.nb then changing it back to nbh but this last piece of the puzzle is not available.
I went little crazy and used dutty's tool to convert nb to nbh and tried it on rhoidum as RHODIMG.NBH then putting it on the SD and going to bootloader. it seems to be stuck on loading all the time without going forward.

samery said:
i think what ur looking for is easy, there are plenty of software out there that could give you that. I remember using Koch nbh by dutty for Hermes but works fine for the Rhodium ONLY to extract files and not to combine.
But the real question is: how can cook an nb file back to nbh file? because I would like to go back to WWE rom, and I thought of extract the nbh file and pulling out the windows.nb then changing it back to nbh but this last piece of the puzzle is not available.
I went little crazy and used dutty's tool to convert nb to nbh and tried it on rhoidum as RHODIMG.NBH then putting it on the SD and going to bootloader. it seems to be stuck on loading all the time without going forward.
Click to expand...
Click to collapse
Use something like yang to rebuild the ROM image. You won't be able to flash it until Hard SPL is out.

I dunno if this will work on a rhodium or not, but it works great with dumping raphael roms. You can get anything you want out of them. You can also remove stuff or insert stuff and re-cook. Just read the text file for directions; there's nothing to it.

Farmer Ted said:
I dunno if this will work on a rhodium or not, but it works great with dumping raphael roms. You can get anything you want out of them. You can also remove stuff or insert stuff and re-cook. Just read the text file for directions; there's nothing to it.
Click to expand...
Click to collapse
there is a Trojan horse in first post!

It's the custom ruu, and it's not a virus. You are the millionth person to point this out.

Farmer Ted said:
You are the millionth person to point this out.
Click to expand...
Click to collapse
seems ur keep count, so he deserves a prize being exactly number millionth

Farmer Ted said:
It's the custom ruu, and it's not a virus. You are the millionth person to point this out.
Click to expand...
Click to collapse
Thanks. But anyway its not works with rhodium. It can read and make from *nbh to *.nb, but can`t excrat any files. Any ideas?
BTW. Where is my big pirze to be a millionth

Can't find my manila version!!!!!!

i really need help in finding my manila type
i have searched everywere on phone and online
no such help
can any one help
i have a mda t-mobile compact v
wm 6.1 professional
cpu:qualcomm 7200A
please help

You would definitely be on 2.1, just not sure what your build number is.
I don't recall if its in 2.1 but, can you go to your Settings Tab\About Phone\Software Info? The build is listed there.
If you don't have About Phone on your settings tab, you can install TD2 Tools which will also tell you your build#.
As I recall 2.1 was easier to theme, so most 2.1 tweaks should work, regardless of build#.
In 2.5, they constantly changed the manila file names with different builds.

it says on td2 tools that its
2.0.37905.0
so i take it that its 2.1
yeah?

I noticed it was wrong on my ROM as well.
That number is virtually useless, sorry.
You're on the stock ROM with WM6.1, you definitely have manila 2.1.
2.1 has programs tab, 2.5 has program shortcuts on home tab.

k thanks
what version of cht should i download then
because you recommended that to me to change themes

welshyboii said:
k thanks
what version of cht should i download then
because you recommended that to me to change themes
Click to expand...
Click to collapse
I'm not sure CHT supports 2.1. The main tweak is to add program shortcuts to home tab, which is 2.5, it has additional functionality to customize home tab appearance.
Since 2.1 is older and XDA is about "cutting edge" there is not a lot of ongoing support for 2.1
Here's a start
If I were you, you'll be much happier, I would look into flashing a custom ROM with 2.5 and CHT cooked in.

how the heck do i do that

welshyboii said:
how the heck do i do that
Click to expand...
Click to collapse
Start here
Then here
The first thing and hardest thing you have to do is Hard SPL.
This unlocks your OS so it can be overwritten.
It is only difficult because the developers have added a function that checks your IMEI# against their database and will likely force you to donate.
I was able to get it to work manually, but other's I have tried to help had to donate. It's always good to donate to chefs and developers, but IMO if its required, its a fee not a donation.
Just a quick education;
When you flash anything, ROM, SPL, Splash screen, etc. the base file is an .nbh file.
There are 3 ways to flash an .nbh file.
1. RUU.exe. You find this program for Topaz, unzip it to a folder, place the .nbh file into the same folder, sync to your PC and run the .exe. This is the method I use exclusively and it has always worked for me.
2. Flashing from SD Card, With this method, you place the .nbh file on the root of your FAT32 formatted SD card, put the phone into bootloader mode (when phone is off, hold power and volume up keys until tri-colored screen appears) and it will flash from SD card.
3. Auto Installer. Typically the .nbh will be packaged into an .exe and installed via active sync. You will only see this with stock ROMs and the HSPL autoinstaller.
Again, it doesn't matter what you're flashing, ROM, SPL, etc. the process is the same.
For HSPL, download the enablenewrapi.cab, RUU, 2.51.nbh and 1.83.nbh files and try to flash as I have listed above(in order of preference)
2.51 is the latest and you want to flash this one, I am just not sure if 1.83 is a prerequisite. Most including, myself already had 1.83 flashed when 2.51 was released. So try 2.51 first, if it fails, try 1.83, then 2.51
Make sure to copy and install the enablenewrapi.cab to your phone first!
Worse case scenario, your flash gets stuck at 0% or it stays on tricolored screen and you just reset to get your device back. Most common errors...
If you get progress screen and it says it completes, make sure to go back into bootloader mode and it will show what SPL you have installed. It should list 2.51.Olinex, the suffix is important.
If you have not successfully unlocked your device and attempt to flash a cooked ROM, you will brick your device.
I can't guarantee that it will work, because I haven't been able to get it to work for others (I think its rigged now). You would just need to try the autoinstaller donate the 4gbp (which is well worth it), and open a service ticket if needed as stated in the HSPL thread.
Then you go ROM shopping....

Bruce Inman said:
It is only difficult because the developers have added a function that checks your IMEI# against their database and will likely force you to donate.
I was able to get it to work manually, but other's I have tried to help had to donate. It's always good to donate to chefs and developers, but IMO if its required, its a fee not a donation.
Click to expand...
Click to collapse
LOL.. careful, Bruce, you're prejudices are showing again! <evil grinz>
Bruce Inman said:
You would just need to try the autoinstaller donate the 4gbp (which is well worth it), and open a service ticket if needed as stated in the HSPL thread.
Then you go ROM shopping....
Click to expand...
Click to collapse
It's the way I went, without the donating part. Works great..

different method of flashing custom rom's

hey guys i have been wanting to hspl my device for a while (see signature(pure). but i have seen that it actually working is very tricky... doesnt always work...
a few weeks ago i talked with a developer about this and he said if you could build your own rom that matches your spl and device perfectly than you dont neeed to modify your device's spl....
perfect for me only looking to flash once... to a 6.5.3...
i had no idea how i should go about doing this until i found this project...
http://ip208-100-42-21.static.xda-developers.com/private.php?do=newpm&u=1915902
using a program called yang...
could i extract only the rom part out of acustom rom and not the spl and fuse it with the official htc original ship rom so i do not have to hspl it????
if i have confused anyone i am sorry or am completely off ... again sorry
however if you have even the slightest of an idea of what im trying to do could you please help me .. and possibly anyone else who might need help
ps. i have flashed many roms on other device for my self and others... always stupidly easy and problem free... like lg incite (took me 10minutes to learn how to flash and to do it and boot up) that thing is a tank ... almost impossible to brick... but it always seems like we run into issues with htc devices and their spl's.... ugh

Check your link as it is invalid.
What you are saying makes sense and could possibly work.
You would just have to find your stock ROM, find a kitchen to decompile it, change some external packages and see if it flashes.
Keep an unaltered copy of your stock ROM in case you need to flash back to it.