Develop Bugs

Won't power up after installing cooked Rom

Ok, I'm new to cooking but I know my phone works as I've been running it under the Xda SE rom for a couple months and thought I would have a go at running ppc2003.
So I installed the standard upgrade from siemens to get the radio stack upgraded and make sure that it would all work fine and then got the bright idea that I need to customize it to my tastes.
I cooked up a rom at lumpi's site and it all seems to work till I turn it off or it times out and turns itself off at which point it will not turn back on unless i perform a soft reset, not for sync, phonecall or power button press, although the led for the phone still flashes.
If anyone has any suggestions as to how to fix this with out reflashing it would be great as this seems to be the only problem.
Thank you in advance for any help that anyone can provide.
Rom Version: A.30.09 Eng
Rom Date: 01/01/04
Radio Version: A.33.02
Protocol version: 1.3.3

does it come on when you put power on it by any means of charging?

no it doesn't it the led just changes to orange as it normally does when its charging. I thought about that when I posted as I saw there was another guy that was having the same problem.

Similar problem
Apo11yon
I've got similar problem, all external buttons locked after using xdaunlock have now tried 4 cooked roms,coming round to idea that it may be battery fault(see my postings?!)
Silent D :? :x

actually yes that was the posting i was referring to I have cooked two roms with the same result that being everything seems to work fine until the unit is turned off and then it wont turn back on without a softboot, i know my battery is good as I mentioned and I did switch back to the standard version on ppc2003 and it does work fine so I'm pretty sure its a software related problem, I was just hoping someone out there might be familiar with the problem and have a solution.

cook a rom with no added programs, install, and see if you have a problems after. i had thevsame prob bc i cooked kse truefax into tmo 4.1.16. Reflashed my device with thevsame rom and progs -kse, and all is well....
good luck!

thanks for the advice in both of the roms that I built I included truefax so I would be inclined to think that that would be it.

no prob.

did a rebuild less the fax app and it works great, should be a notice on the site that it may cause difficulties even better would be a listing of apps that conflict with each other or possibly the os
thanks again for the help fellow

Confused

I've been using my XDA Exec for almost a year now and have tried my hand at a few ROM upgrades - I'm not toally sure what I'm doing so I don't tend to try much. I now want to understand more about what each element of the upgrade does and I'm having problems finding out what does what. Can someone explain in easy terms what the CE ROM is and what it contains (I'm guessing its the operating system), what the Extended Image is and what it contains, and finally what the RADIO ROM is and what it does (or contains). I then want to try and mix and math the various bits to get the device I'm after.
Thanks
I'm currently showing ROM 2.01.06, RADIO 1.15.00, protocol 42.51.P8 and OS build 5.2.318 (Build 15341.0.0.0)

More confusion
Also, please, what is the difference between a standard ROM and a WWE ROM? I note that my question has not been covered in the glossary of terms, so is everyone else confused or is eveyone else too lazy to help out a n00b?

o.k very simple:
Ce ROM : (WM5 or WM6 etc) is the OS of your device, it can be compared to windowsXP in your desktop.
Extended Image=Extended ROM: is the image/ROM which has additional 3party application software on it. Those software’s can be related to your service provider settings /application or application simple as Adobe PDF; Backup software etc.
Extended image will be installed in a special area which called Extended ROM (ca. 10mg capacity) on your device. Normally this area is locked and hidden in official ROM. Application software or information stored in this area still untouched and available after a “hard reset (setting the device back to factory/provider settings)”
But in the ROM’s that are available in this form here (self cooked/made) is the extended ROM is mostly unlocked and visible. Moreover You will observe that this area has no more application on it anymore. Therefore you can make use of this area with storing some important data which you want to still available in case of hard reset.
RADIO ROM: includes only information for Phone functionality. It is a “application” to able the devices communicate with GSM, 3G etc. However you will find few available Radio versions. The most used one is currently 1.15 but it really depends on your location. Some are very happy with 1.15 but others having problems to receiving signals with it and leading the device been unstable.
WWE= World Wide English: that is related to OS (CE ROM) language version. It means it is English ROM.
I suggest you read the WIKI ,a lot of things that you can take from there

Bulldog,
Very many thanks for your help, and yes, I've read various bits of the Wiki but couldn't find the answers I was looking for. I appreciate the basic explanation.
I am currently using the extended ROM area as storage as I haven't found anything (CABs?) in there. Another question ref the OS ROM bit, do all 'cooked' OS ROMs of the same version have the same contents or can they vary from ROM to ROM (even if they say the same version number)?
Rgds, Phil

Hi Phil,
I assume you are using ROM made by one of the cooker here?
every cooker has own preference of software (additional to the OS) that includes in to ROM image. Basically they combine now the OS with extended rom.
You may hear the expression of "Vanilla" that indicates that ROM clean from any additional software and has only the OS on it.
Moreover different cooker may use different supporting application like commanager etc and build ROM which is XXX version. Moreover during the cooking different ROM builder using different registry settings which ends up as XXX version but have totally different performance.

Bulldog,
I am using one of the ROMs from this forum, from one of the 'stikkies'. I've tried a few but can't find the one I originally upgraded to when WM6 first came available (and also don't know whose it was!). I think I'm currently using Helmi's "Helmi_WM2k6_v.1.1
WM6 OS 5.2.318 (Built 15341.0.0.0)" ROM although I'd like to try the DarkForce one but can't find it (see other post). I'm also going to try the vanilla ROM posted by Graham but have yet to upload it to my XDA.
Once I get a bit more comfortable, I'm going to try and teach myself (via lots of reading here) how to cook my own ROM to provide the apps and features I want - but that might take me some time!!

try the PDAVIET ROM, very good. Stable and fast! you will not regret it.
http://forum.xda-developers.com/showthread.php?t=317823
darkforce rom hangs alot!

ROM based on 1.97 causing issues?

Yesterday I started to get problems with my HTC Touch Diamond. I flashed my device with udK Syrius HD R0 (BETA 5) and everything was going smooth, restored my contacts, my messages and tweaked WM6 a bit.
But after a soft reset to apply all changes the device welcomed me with the ordinary "You're using your device for the first time" message and I had to setup my device again. After another soft reset my device hung at the boot screen with ROM information and the "Touch Diamond" text.
All I could do now was a hard reset. But the problem didn't go away... the device kept freezing and resetting, and I had to do 2 or 3 more hard resets before I decided (actually I already had, but had to wait for the download to finish ) to flash to another ROM.
So I downloaded Vic Hybrid 2 Diamond ROM UC. Flashed and everything seem to went fine. But just as before, after a soft reset the device hung. Hard reset...
Why's this!? Is my HTC Touch Diamond broken or is there anything I'm missing? Perhaps this occur because of the ROM's is based on the firmware 1.97??
EDIT #1: sorry, wasn't meant to create this topic under "ROM Development"... Any mod, feel free to move it.
EDIT #2: Seems one more guy had this a relating problem after ROM flash (udK's ROM for that matter too): http://forum.xda-developers.com/showthread.php?t=455335
EDIT #3: "The device is unable to boot because either you have turned off the device incorrectly or tried to install an application from untrusted source. Press SEND to reset your device or press any other button to cancel. This operation will delete all your personal data and restore the device to its factory default settings."... didn't have time to press any "SEND" button either... it continued to... guess? The setup! Entering date + time + calibrating the stylus...

*sigh*... not it happend again. Just restored all my SMS and tried to thread them again (screw that either way!), soft resetted my device... and the damn WM6 setup guide for clock, calibration showed up, and now "Installing..."
*sigh - again*

hi dude i had the same problem
i have a DIAM300 and had the olinex 1.40 hard spl with mossis rom 2.5 (ger)
i flashed mossis 2.6 which is based on 1.97 and i had those problems too, after a few softresets it makes a hardreset...then i tried olinex 1.93 thought it could be the bootloader but the problems were still there...
i tried some other roms, udk Syrius too which is fast as hell, but unfortunately the same problem here and sometimes it even didn't boot...
i made about 50 softresets, 20 hardresets, flashed bout 10 times....then i had enough, flashed the original O2 rom, flashed the original bootloader, flashed the original rom again, and now everything is allright, it's runnin, no hardresets, i tried about 20 softresets, installed software blabla....
but now i'm wondering if the problem will be there again when i start to flash
and its really annoying when u flash a rom, customize everything, everyting seems to be allright and then it makes a hardreset instead of a softreset....

gizz68erz said:
then i had enough, flashed the original O2 rom, flashed the original bootloader, flashed the original rom again, and now everything is allright, it's runnin, no hardresets, i tried about 20 softresets, installed software blabla....
Click to expand...
Click to collapse
Damn, I don't want to flash to the orginal ROM! Just flashed to a ROM I've tried earlier, based on 1.93, Panosha ShineOn, so let's see if there's any more trouble...
gizz68erz said:
but now i'm wondering if the problem will be there again when i start to flash
and its really annoying when u flash a rom, customize everything, everyting seems to be allright and then it makes a hardreset instead of a softreset....
Click to expand...
Click to collapse
Yeah, I feel the pain. Getting sickin' tired of this **** now!!!

Try this one
Hi
Whenever i have this kind of bizar issues [ also with previous devices i had before my Diamond] i did the following:
1. Flash back to original official ROM including Radio [ no need to compelrte the initial setup , just flash and go back to bootloader screen right after]
2. Flash again to the targeted cooked ROM
3. Probelm disapeared
My assumption is that for some cooked ROMs the coverage of files been flashed and replaced is not 100% and therefor we face inconsistancy issues.
Try it

my view of this
my view of this:
new roms have other architecture such as new manila new drivers etc etc (1.97)
when you "tweak" them such as manila mods wich are made for older versions this kind of problems can happen. the problem is we have to many modded roms right now. we have 1.37 roms 1.93 roms 1.94 roms (ported from raphael) 1.97 roms and so on. all of this roms you cant compare with each other.
a example: HTC Diamond Manila has no LANDSCAPE files. every rom wich has landscape support had included RAPHAEL Manila parts. no one can deny this. cause its the only device right now that offered the landscape support on manila. but looking to diamond application and software section here and the date this files were made are back in the past. this is just a example where this problem result of.
just my 2 cent

alphazero said:
my view of this:
new roms have other architecture such as new manila new drivers etc etc (1.97)
when you "tweak" them such as manila mods wich are made for older versions this kind of problems can happen. the problem is we have to many modded roms right now. we have 1.37 roms 1.93 roms 1.94 roms (ported from raphael) 1.97 roms and so on. all of this roms you cant compare with each other.
a example: HTC Diamond Manila has no LANDSCAPE files. every rom wich has landscape support had included RAPHAEL Manila parts. no one can deny this. cause its the only device right now that offered the landscape support on manila. but looking to diamond application and software section here and the date this files were made are back in the past. this is just a example where this problem result of.
just my 2 cent
Click to expand...
Click to collapse
Yeah, I bet there's some issues with the new 1.97 and all the new drivers. The chefs need to get stuff straight before I'm trying any new 1.97 based ROM out again.
My issue seem to have been fixed after flashing to Shine On 2.4 Full (1.93 based!). My device now soft resets OK, and I keep all settings... well, atleast for the moment. I'll continue to soft reset every now and then to see if the problem comes back to me.

Yeah, got EXACTLY the same problem with ROMs based on Touch HD or Quartz OS built Hard SPL 1.93 And I don't use any manilla mods, prefer its original view with original tabs. All I have is some portion of software to install:
- Inesoft Cash org;
- Inesoft Address book;
- Agenda Fusion 8;
- Alreader;
- Auto keeper;
- HiCalc;
- Navitel Navigation system.
and the only "tweak-like" soft I use is Answerkeysdisabler. But having serious intentions to reach the truth I didn't install it.
When I've tried to flash syrius beta 02 AND beta 05) I got a STABLE hard reset after 3-5 reeboots. And it doesn't correspond with the quantity of soft installed, it's just resets and thats all.
When using Aztor v7 i had 99% hangup when installing my software just after HR, and it always hangs on different program installation, then, after reeboot manilla cannot start.
These are very interesting ROMs, especially I like AZTOR's pholosofy, but... couldn't manage to give it a try
Tried SwiftBL's, Dutty's, Bepe's ROMS - all smooth and fine. And the STABLEST FOR ME was the old bElite 0,99d. NO issues at all! Now i'm usind Dutty's 3,4 in general it's stable and ok, but with some minor issues. Would be really nice to have issue-free ROM based on new versions of software.

Advice needed........

Ok so i'm new to this custom rom thing but i'm kinda forced to it since I bought my Diamond in India and apparently htc doesn't offer updates on their site and I can't be bothered to go to the airtel website (wich is probably in Hindy ) and look for an update.
So I managed to update to HardSPL 1.4 using the tutorial thread (thanks btw, all worked like a charm ) and installed the radio 1.0.25.05 (according to the same thread the recommended version)
So now i'm seeing many roms out there and have absolutely no clue wich rom to choose.
Maybe some advice ?
Here is my wishlist/stuff that matters
I'm based in Holland, so i'm bound to end up with one of the major providers here and gonna go for some hsdpa contract.
I'd love my HTC to be faster
I like the msn thing, but it's not required.
I don't want to be running beta/buggy softwares, my pc runs that kind of softwares, not my phone
Also i've seen (after installing the radio rom) that in a different thread there is a lot more different radio roms, with people liking the some better than the one reccommended in the tutorial post, is there a better rom and should I use it ? (better gps, faster, less batt usage ?)

Best are 1.93 rom for the "fast" part you asked but it's getting old (like 6 or 8month i guess). After you will want to go for a 2.03 rom which provides you more functionalities.
I will advise you Hikari rom, udK Syrius Topaz or Shaks or nataly. These are the rom I try every time there is a new release, I change rom every 1 or 2week so better is you check yourself.
You must have HardSPL unsigned edition for some of these rom, it's the same procedure as 1.4 SPL.
BTW, you know you can upgrade directly from your internal storage?
just put your nbh file in your storage card with the name "diamimg.nbh" (stands for Diamond Image) then reset while pressing VOL_DOWN + BACK (the button up from the hang up button). After this, you will see a HardSPL like screen (red blue green) then a gray~light blue screen asking to press the power button to upgrade.
You can do this for radio, spl and rom. It's quicker, safer and better IMO.
'night

[Q] Is there is any possibility to fully run kernel on WM6 radios?

I have "semi-bricked" kaiser: it works well with WM6 and compatible radios but with WM6.x radios it wont boot farther loader
So is there is any possibility to fully run kernel on WM6 radios (with voice and camera)?

En1gma said:
I have "semi-bricked" kaiser: it works well with WM6 and compatible radios but with WM6.x radios it wont boot farther loader
So is there is any possibility to fully run kernel on WM6 radios (with voice and camera)?
Click to expand...
Click to collapse
Well we usually use 1.7....or 1.65... radios which were shipped with winmo 6.1 so It is hard to say whether Android will be fully functional on earliest radios. How about you try it for yourself? You can leave winmo in nand memory and try to run Android through haret from sd card.

I used to use different versions wm6 and different versions wm6.x and even different androids (on wm6.x radios) but some time ago the phone started to work with different malfunction and eventually cant boot with wm6.x radios
*nix kernels works and android loads but android works like WM6.x ROM + WM6 radios (no voice and no camera)

En1gma said:
I used to use different versions wm6 and different versions wm6.x and even different androids (on wm6.x radios) but some time ago the phone started to work with different malfunction and eventually cant boot with wm6.x radios
*nix kernels works and android loads but android works like WM6.x ROM + WM6 radios (no voice and no camera)
Click to expand...
Click to collapse
Try installing 3.3x HSPL (do not install forceusb ones) then try updating radio alone. Try 1.65.x first Then install WM6.1 (any cooked rom)
Just install 3.3x HSPL first, then radio then WM6.1 rom. SPL1.x is for WM6