In case other people have the problem: Update to the latest version of ppckitchen!
Hello,
I was not satisfied with the current available rom's and decided to cook my own, I used the ppcgeeks kitchen to cook a 21042 wm6.1 rom and included quite some OEM packages. After building and flashing the ROM my device started, and got in the SPL (where you can see the radio/rom version). But it would not get past there. I tried flashing again (without sim and or memory card), hard resetting after flashing, and upgrading the hardspl to 3.59. All to no avail.
I thought it might be an issue with one of the OEM packages, so I started a new project in the kitchen and left everything to default and directly build the bare ROM. The problem still persists. I noticed the only carrier available as a choice in the kitchen was AT&T, I live in europe so this might cause a problem? (absolutely not sure about this, just poking around).
Some more details:
R: 1.70.19.09
G: 25.83.40.02H
D: 3.14.00.00
Luckily I can get in the bootloader and flash whatever I want and just go back to the stock ROM, but I rather want my own, so I was wondering, can anyone help me with this issue?
Thanks in advance, peterrus
Does the backlight dim or does it stay on constantly? If it dims, then you have an issue with your SYS or OEM. If It doesn't dim, then you have an issue with your XIP. Was the kitchen already ported to run on a Kaiser? Which kitchen did you use from ppcgeeks? A little more information will help figure out your issue.
It does dim indeed, so it seems I have an issue with my SYS or OEM, tell me more.
I used the latest version but I am not aware of any versionnumbers, this is the announcement post: http://www.ppckitchen.org/forums/showthread.php?t=650
I could get the versionnumber from the kitchen, but I just uninstalled to try an older version, and updating it takes about 2 hours.
The kitchen is said to be kaiser compatible
I see however that there are others experiencing the same issues. I am gonna try an older version of the kitchen and see what happens.
Test the older kitchen like you are already doing. I suggest creating a base build without any packages included, so you can verify that the base ROM is OK. This will help with the process of elimination. Now, you should also read any documentation with that kitchen to verify that the OEM folder is exclusively for the kaiser. The OEM folder contains device specific settings and drivers. So using an Elfin or Polaris OEM with you kaiser will cause lots of issues (mainly the one you're experiencing now, stuck at splash screen). Again, give the older kitchen a try and post how that goes and we'll go from there.
Using the old kitchen () I can not succesfully produce a working 21042 ROM.
Using the old kitchen I can produce a working 20931 ROM.
I have not tested the new kitchen yet. But when I find time for that I will post results.
So, using the new kitchen I also can not produce a working 21042 ROM, a 20931 ROM works fine though, so I think i'll just leave it like this.
Unzip and add
This to your sys and see if it helps.
The ppckitchen authors have pushed an update which seems to fix the issue, so josh: I haven't tried your fix yet because I prefer the official update over other solutions, but thanks anyway it seems I can now succesfully boot the rom.
Related
Two questions:
1. How do I tell what generation my Prophet is? I see a lot of references to G3 and G4 but no information on how to work this out.
2. I currently have the latest i-mate JAMin rom, which is AKU2.0. Is there is a stable AKU2.3 ROM people have been using or is this still "experimental" It's hard to work this out from the threads.
Thanks all.
spaceboy said:
Two questions:
1. How do I tell what generation my Prophet is? I see a lot of references to G3 and G4 but no information on how to work this out.
2. I currently have the latest i-mate JAMin rom, which is AKU2.0. Is there is a stable AKU2.3 ROM people have been using or is this still "experimental" It's hard to work this out from the threads.
Thanks all.
Click to expand...
Click to collapse
1: during bootup, 2nd screen find
SPL
2.xx.0001 = g4
2.xx.0000 = g3
2: aku 2.3 seems very stable. Everything works as expected. i've only installed one version, after reading this thread: http://forum.xda-developers.com/sho...ht=16Mb_AKU2.3_GSM02.30.21_Extrom-4PDA.ru.exe
it's the 16Mb_AKU2.3_GSM02.30.21_Extrom-4PDA.ru.exe from this sites' ftp. It has been much more stable and responsive (due to the larger cache) then the preinstalled AKU2.0 on my qtek s200. Boot time is shortened by about 20s.
Before you install this you HAVE to unlock the CID:
http://wiki.xda-developers.com/index.php?pagename=Prophet_Upgrades
i didn't do this first time, and had to find a valid qtek rom that would install, since my device didn't bootup anymore..
Thanks for that. A question about unlocking the CID:
On the Prophet upgrade page you link to, it has the warning (3 times, in bold!): *WARNING!!!!! DO NOT PERFORM THIS IF YOUR PROPHET HAS THIS ROM "SPL 2.xx.0001" (New G4 Version)
Don't all G4's have that ROM? Mine does (2.13.0001). So where does that leave us for unlocking?
Thanks again.
Im also running a JAMin with the latest official rom and ive seen some good things about the 2.3 updates but im new to the whole cooked roms thing but ill figure it out.
What would I loose by upgrading from my JAMin rom and what would I gain?
Can I go back to my jamin rom if I dont like it?
I have installed the latest DOPOD ROM and I run it native without any soft installed and I reboot only about 1 a month!
To partially answer my own question: The CID unlock process looks like it IS for G3s only. To upgrade G4s you use pdocwrite.exe.
I've seen the details for using pdocwrite to install the pdamobiz ROM, but has anyone used it to install the 16Mb_AKU2.3_GSM02.30.21_Extrom-4PDA.ru.exe?
Cheers
dannyoneill said:
Im also running a JAMin with the latest official rom and ive seen some good things about the 2.3 updates but im new to the whole cooked roms thing but ill figure it out.
What would I loose by upgrading from my JAMin rom and what would I gain?
Can I go back to my jamin rom if I dont like it?
Click to expand...
Click to collapse
I'm guessing you'd loose some of the vendor customisations - which really are only some useless themes and the network provider settings - which for me just means setting up GPRS. Of course, you also risk loosing your JAMin entirely if you stuff it up
What you gain is a more up-to-date OS which is faster...
what about the extended rom? all the custom stuff is in there, i can access it no probs but would that remain with the rom mentioned above?
would I still be able to run them (if I back them up)
just been researching this rom, looks like it defaults overclocks your device and installs a ton and I mean a ton of apps that most people dont want.
Be warned, its heavily customized and may not be to everyones liking.
Anyone know if I do upgrade to this and unlock my CID if I can then re-apply the official JAMin rom?
dannyoneill said:
just been researching this rom, looks like it defaults overclocks your device and installs a ton and I mean a ton of apps that most people dont want.
Be warned, its heavily customized and may not be to everyones liking.
Anyone know if I do upgrade to this and unlock my CID if I can then re-apply the official JAMin rom?
Click to expand...
Click to collapse
To anyone reading this, here is my experience as of last night.
On my G4 I tried installing 16Mb_AKU2.3_GSM02.30.21_Extrom-4PDA.ru.exe after first hard-resetting my device. The installer went ahead fine, but it would not start-up: it would not get past the boot loader screen. So I reinstalled the latest i-mate ROM, booted up, then proceeded to try: ftp://xda:[email protected]/2006-10-05_Upgrade ROM_AKU2.3_lvsw.rar.
This uses the PDAmobiz method to upgrade a G4 which is essentially running a batch file while it unlocks and writes to the ExtRom and the ROM - then doing a hard reset, but it is not the PDAmobiz ROM.
This worked fine, and I now have AKU2.3. Even better, it is not customised, so there's no extra software installed, which I'm happy about. It's been running over night and seems very stable so far. I'm not sure what the paging size is on the ROM, maybe it's smaller = more stability.
So that's my experience!
My experience:
My JAMin running IPL/SPL 2.13.0001 using that rar file that worked for you...
hung on the copy of the OS to the device.
Trying now to recover it by downloading and trying to install latest JAMin update.
I cant get activesync / network connection using USB to phone... Don't know if that will be a problem trying to recover. Its sitting at the 3 colour screen atm.
Is there a way for me to update to IPL/SPL 2.15.0001 from 2.13.0001 before trying again? (assuming my phone is not already dead).
orian said:
My experience:
My JAMin running IPL/SPL 2.13.0001 using that rar file that worked for you...
hung on the copy of the OS to the device.
Trying now to recover it by downloading and trying to install latest JAMin update.
I cant get activesync / network connection using USB to phone... Don't know if that will be a problem trying to recover. Its sitting at the 3 colour screen atm.
Is there a way for me to update to IPL/SPL 2.15.0001 from 2.13.0001 before trying again? (assuming my phone is not already dead).
Click to expand...
Click to collapse
If your phone is G4, you should be able to install the vendor ROM no problem - which is magical really. You don't need ActiveSync running; well - it won't connect as the device is dead .
When you say it hung copying the file... it took a good 15-20 minutes to copy across for me, so I hope you weren't just being impatient.
yeah the JAMin rom worked so I'm back where I began.
I did wait 30 mins and it had crashed.... activesync wasnt doing anything, buttons / screen taps weren't working on pda.
Is it because I am running 2.13.0001 is my worry? The update specifies its for 2.15.0001. Is there any way I can update to 2.15.0001 from 2.13.0001 before trying again?
Cheers.
Tried the update again, and this time it worked.
Device is running AKU2.3 now, but still says 2.13.0001 for ipl and spl on boot.
Any ideas anyone on how I can update that to 2.15.0001? and what kind of change that makes anyway?
Thanks all.
dannyoneill said:
just been researching this rom, looks like it defaults overclocks your device and installs a ton and I mean a ton of apps that most people dont want.
Be warned, its heavily customized and may not be to everyones liking.
Anyone know if I do upgrade to this and unlock my CID if I can then re-apply the official JAMin rom?
Click to expand...
Click to collapse
you have been researching a different rom. this one does certainly NOT overclock the device by default. And it's a clean install, without any overhead, but WITH the stereo bluetooth headset support. perfect for my uses.
looks like i was looking at another rom, one loaded with junk.
I took the plunge and updated my jamin to the 16mb 4pda rom and im now back on the official jamin, it was way too unstable. Today I rebooted 5 times.
The volume is too low on headset and loud speaker
and some other annoyances.
I need stability
when i'm using AKU2.3,
in Settings / Regional Settings:
there is no "Turkey" option (also Russian).
how can i do that, is there a patch for apply these regions ?
thats why i'm using latest official jamin rom now (wwe) (from clubimate.com)
Ive found the source of instability with the 4PDA rom. Its the radio rom 02.30.21
I went back to my old ROM on my jamin and all was fine, a day without crash, Then loaded on radio rom 02.30.21, hardreset for good measure and setup again,. same as always.
Then, every hour or so im resetting.
Back to official jamin rom and all is fine again.
Radio ROM 02.30.21 is just totally unstable. Ideally I would like the AKU2.3 updated rom but without this awful radio rom they seem to be putting in them all.
I got my Tilt a month back and now interested to install one of the custom made ROM. But i have some basic questions. Please ignore my innocence.
1) As far as i understand Tilt has 2/3 kind of software that can be flashed
a) The GSM Radio
b) The OS
c) Something i missed.
Can someone correct me if i am wrong above.
2) What is Hard SPL? Is that just a tool to flash or it is needed to run the OS / Radio / Other software?
3) What is splash screen? The one that splash when we restart the phone? Why someone want to change it as it is a screen saver. It appears only on reset's if i am not wrong.
4) By flashing the Tilt with new ROM, will it flash the Radio along with the OS? Or it depend on the build. I see some ROM build's with Radio and some ROM's without Radio. Is flashing Radio is different way of doing? Or Hard SPL?
5) Is the Radio software and OS are integrated? Can i use the Radio that comes with Tilt along with some good ROM like dutty's / Custel?
6) Are these custom made ROM's are having drivers for all the hardware ( GPS, Camera, WiFi receiver, 3G Data receiver, BT etc) Do i need to take care of anything? I know that a fix is available for keyboard.
7) There are lot of ROM's around. Popular Dutty's and Custel ROM has got impressive feedback. I am planning to try Custel first. Are the below steps are right?
1) Connect Kaiser to computer using USB cable
2) Make sure ActiveSync icon is GREEN
3) RUN Kaiser-HardSPL.exe on Computer (PC)
4) Follow instructions on screen
5) Once Done, run the Kaiser_RUU.exe and that's it?
I see you scream SEARCHHHHHHHHH...
I did and i am slightly confused as I am just new to this world. I am trying to conclude my assumptions/ understanding.
Thanks.
For questions 1-3 regarding what can be flashed to a Kaiser/Tilt.
HardSPL -- Bootloader. Need to flash this before you can flash anything else that's not HTC or AT&T certified, e.g., cooked ROMs.
Splash -- Only shows up on resets. People like to change it because they can
Radio
OS
Questions 4 & 5 about cooked ROMs bundled with radios and how to flash:
Some chefs choose to include a radio in their NBH file, some chefs don't. You can find links to radio roms and flash it w/o OS.
Currently, there are two radio versions out for the Kaiser and one is dependent on a specific OS version (ATT OS 1.60.502.3 + Radio 1.27.14.09).
Use KaiserCustomRUU to flash .NBH files, which may or may not be included in the ROM release.
Question 6 about drivers & such:Depends on the cooked ROM and what has been removed from the shipped ROM. The Tilt keyboard fix applies to HTC 1.5.405.5 based ROMs only.
Question 7 - how to flash:Yes, your steps look fine.
Hope this helps...
Thank you and I appriciate your help. This gives me some confidnece. I am going to start flashing my Tilt with Custel ROM. Thanks again.
I'm having trouble with my Tilt (it recently started being randomly unresponsive to commands (15-20 second lag some times). Is there going to be a new AT&T 6.1 official ROM with updated drivers? My device has the 8-25-07 ROM date, and before I decide what to do I'm checking on the status of official AT&T releases.
No, as far as I know, there isn't an official one yet. However, a lot of the cooked ROMs on this site will probably fix your problem.
If you can't wait for the official ATT WM6.1 release then you could try their latest WM6.0 release http://www.htc.com/us/FAQ_Detail.aspx?p_id=67&act=sd or as mentioned, could try a cooked ROM.
upgrade ur hardspl and the lags/freezes will be gone.
thesire said:
upgrade ur hardspl and the lags/freezes will be gone.
Click to expand...
Click to collapse
Looks like he is still using an old Stock ATT Tilt ROM (WM 6.0), so that is not likely the issue.
@ gmfeld. If you have had your Tilt for a quote some time, it is possible that you simply have some junk, or orphaned registry settings, or something slowing your system down.
I would recommend either upgrading your ROM to the latest Stock ATT Tilt ROM (as posted above), or simply doing a Hard Reset to get your current ROM back to its original state. Of course, do a BACKUP before you do anything that involves Hard Reset or Flashing!!!1
I just got my tilt and I think I have a newer official version.
It is
ROM 1.62.502.0
Date 01/17/08
Radio 1.27.14.09
I've noticed it has a bluetooth headset issue (not sure if it is exclusive to mine) where it will end the call, but won't hang up in the phone program.
gmfeld & vanisher,
I would suggest you at least run PPCPimBackup then a hard reset. If you have a little time this weekend you should read through G.W.E.N.I. then flash a nice cooked ROM. Play with your device and post educated questions in the proper threads. You WILL appreciate your device more than you ever did...guaranteed.
http://forum.xda-developers.com/showpost.php?p=2273408&postcount=2561
The above is a noob success story. I would recommend you go the same ROM route as he did as for starters.
There is no official AT&T WM6.1 ROM yet, but we're getting there.
Check the shipped ROMs section on the wiki to see how new / old your ROM is.
kwickone said:
Looks like he is still using an old Stock ATT Tilt ROM (WM 6.0), so that is not likely the issue.
@ gmfeld. If you have had your Tilt for a quote some time, it is possible that you simply have some junk, or orphaned registry settings, or something slowing your system down.
I would recommend either upgrading your ROM to the latest Stock ATT Tilt ROM (as posted above), or simply doing a Hard Reset to get your current ROM back to its original state. Of course, do a BACKUP before you do anything that involves Hard Reset or Flashing!!!1
Click to expand...
Click to collapse
Thanks to all for all the suggestions. I've been running SKTools, so I'm pretty sure I've gotten rid of all the junk and orphaned registry settings, etc.
I agree with all that I need to flash a new ROM, or reflash my original ROM, that's the only thing left to do to clean up my Tilt. Just trying to get some info on when or if a new official AT&T 6.1 ROM is to be released, so I don't go through that process twice. If I knew that its a ways off, I will probably then go with one of the cooked ROMS now.
Because I am pissed off with the newer radio ROMS...
I have a few questions about getting the old 1.58 Niki Radio ROM working on the latest WM 6.1 Official ROMS.
As you know, using this Radio ROM on the newer WM6.1 causes issues with the phone's camera and sound.
I am going to do some research into this, but I first would like to know if the following is possible?
1) If I replaced all the *gps*.* system files on the newer WM6.1 ROM with the ones from the older WM6.1 ROM, would it be possible to run the 1.58 Niki Radio without problems?
I don't think it would be this simple...So
2) What tools are available for the WM OS that allow me to monitor memory address access by the processor. Also, where can I find a good ARM disassembler?
I will use these tools to try and make my own custom radio ROM.
If anyone here has advice about where to start with this, then please post.
Thank you.
-IK- said:
Because I am pissed off with the newer radio ROMS...
I have a few questions about getting the old 1.58 Niki Radio ROM working on the latest WM 6.1 Official ROMS.
As you know, using this Radio ROM on the newer WM6.1 causes issues with the phone's camera and sound.
I am going to do some research into this, but I first would like to know if the following is possible?
1) If I replaced all the *gps*.* system files on the newer WM6.1 ROM with the ones from the older WM6.1 ROM, would it be possible to run the 1.58 Niki Radio without problems?
I don't think it would be this simple...So
2) What tools are available for the WM OS that allow me to monitor memory address access by the processor. Also, where can I find a good ARM disassembler?
I will use these tools to try and make my own custom radio ROM.
If anyone here has advice about where to start with this, then please post.
Thank you.
Click to expand...
Click to collapse
I would start by contacting Viperbjk, cmonex, JockyW2001 and the likes. However, that being said, I would think they would have done it already if it were possible. Anyways, it would be nice if someone could achieve this.
Thanks for that P1Tater...
I've just discovered that IDA is the decompiller of choice for ARM processors, so I am going to download the demo for that to start with.
My simplistic theory is to decompile the 1.58 ROM and check for code that addresses memory reserved for the GPS, camera and sound hardware.
Then using this code, integrate it into the latest radio ROM to make a hybrid.
The unknowns (to me) right now are...
1) When I extract the Radio ROM from my phone as a raw file, is this actually machine code or is this data encrypted in some way?
2) Are the problems caused by running older radios on newer WM ROMs actually to do with updated device drivers interaction with the radio ROM, the radio ROM itself, or both?
It's been years since I've done disassembling, but this is just for fun
unfortunately I don't have any smart advice to give you, but I would really like to see this looked into
Maybe you can use the 1.58.25.17 Neon radio as a source of comparison. This radio is compatible with the newest HTC builds, and I have no issues with GPS.
NotATreoFan said:
Maybe you can use the 1.58.25.17 Neon radio as a source of comparison. This radio is compatible with the newest HTC builds, and I have no issues with GPS.
Click to expand...
Click to collapse
Thanks for that...I must admit that I am mainly looking to get a radio working that gives good GPS performance here in the UK which the Niki 1.58 was very good at doing.
The problem is that all these Radios which work great in other parts of the world, are pretty crap here in the UK.
I may test the ROM you mention, but for UK users at least, the Niki 1.58 seems to be the benchmark so far.
Cheers.
replace the GPS drivers with older WM6 drivers, i did that in all my lastest roms and it fixed the intermittent GPS issue of it not getting a lock fast. with the older drivers i get a lock in 20 seconds with the new WM6.1 drivers iit takes up to 15 minutes before. also this was talked about before there is a whole thread on dumping and rebuilding radios.
austinsnyc said:
also this was talked about before there is a whole thread on dumping and rebuilding radios.
Click to expand...
Click to collapse
i suppose you wouldn't have a link to said thread?
/ OT
austinsnyc said:
replace the GPS drivers with older WM6 drivers, i did that in all my lastest roms and it fixed the intermittent GPS issue of it not getting a lock fast. with the older drivers i get a lock in 20 seconds with the new WM6.1 drivers iit takes up to 15 minutes before. also this was talked about before there is a whole thread on dumping and rebuilding radios.
Click to expand...
Click to collapse
I'd like to try it.
Can you share your kitchen files for those? or just the driver files from WM6?
I would really appreciate that.
austinsnyc said:
replace the GPS drivers with older WM6 drivers, i did that in all my lastest roms and it fixed the intermittent GPS issue of it not getting a lock fast. with the older drivers i get a lock in 20 seconds with the new WM6.1 drivers iit takes up to 15 minutes before. also this was talked about before there is a whole thread on dumping and rebuilding radios.
Click to expand...
Click to collapse
What drivers are you talking about?
The gps dlls in the system directory?
I know how to dump a radio from the phone that's why I can hack a radio in the first place. I also know how to rebuild it back into an nbh for reflashing...This isn't what I'm looking for info on.
If you've got any info, please point it out. It will be appreciated.
I've flashed several ROM's to my x7510, starting with Cmonex's 1st WWE ROM, followed by a few versions of Xacsx's ROM's, always going back to Cmonex's every so often.
After having installed one of Xacsx's ROM's, the keyboard layout changed from QWERTY to QWERTZ and I had to do a reg edit to correct it. I learnt from somebody here that QWERTZ is a german keyboard layout, which fits seeing Xacsx is german.
Now here's the strange thing - after having flashed a previous ROM with QWERTY layout, I still had the QWERTZ layout. The setting had somehow "survived" the flashing?
And it gets better. After having flashed Xstep's ROM, the phone on my device remained turned off and nothing I could do would turn it on. That is a MAJOR crisis for me! I flashed Cmonex's ROM again, to see if I could recover from that and hoping it was simply an error with the ROM.
Xstep's ROM has RealVGA built in and the default setting is 92 dpi.
After flashing Cmonex's ROM my device was running at 92 dpi, even though RealVGA is not installed! I had to install it just to change the settings back to 192 dpi.
And still the phone doesn't turn on!
Update:
The problems I experienced were down to two things:
1) I had flashed two ROMs that each contained their own extended ROM's in succession
2) Somehow I had messed up the radio on my x7510
THE SOLUTION:
1) Flash the extended ROM supplied by Cmonex, together with the matching ROM
1. customruu for x7510, grab it from attachment. use this to flash roms.
2. nbh building tool for x7510, in another attachment. just choose X7510 from device list to work with it.
3. some stock OS links (some taken from RUU some from dumped / reconstructed roms)
WWE (english) 19209: http://rapidshare.com/files/16043971...forATHE400.zip
WWE (english) 19217: http://rapidshare.com/files/16043113...forATHE400.zip
GER (german) 19217: http://www.filedropper.com/x7510gerruusignedforathe400
CHT (taiwan chinese) 19209: http://rapidshare.com/files/15981958...forATHE400.rar and a mirror http://www.megaupload.com/?d=30L24D8W
NEW: WWE (english) 3.29.707 rom: http://rapidshare.com/files/16967590...RUU_Signed.zip
+ extrom for 3.29.707: http://rapidshare.com/files/17304340...707_extrom.zip
make a mirror for others too please if you can =)
Click to expand...
Click to collapse
2) Flash the x7510 radio supplied by Xtep
I have repacked the radio for a x7510. You can download it from: http://rapidshare.com/files/191672003/x7510_Radio_1.58.rar
Click to expand...
Click to collapse
I have axcsx's WWE ROM loaded on my x7510 which I loaded after loading cmonex's 3.29 rom. To be honest I did not know that a QWERTZ keyboard existed, however, all of the keys on my keyboard keys appear to work exactly as one would expect - QWERTY fashion without any required registry fix.
I did download xtep's rom but I'm now not likely to load after your experience. I wish I had more technical knowledge to suggest a fix. cmonex posted after a long absence yesterday. Perhaps it worth a pm?
Still wonder why you had a keyboard issue and I don't?
I actually flashed ALL of Xacsx's ROM's at one stage or the other. I believe the problem started after I flashed version2 of his WWE ROM.
Time for an update:
The QWERTZ instead of QWERTY issue I believe was down to one of Xacsx's ROM's having over-written the extended ROM (he warned that it would).
I've downloaded Cmonex's HardSPL, WWE ROM and matching extended ROM, then flashed 1st the HardSPL, then the extended ROM and finally the WWE ROM.
As a result, I no longer get the 96 dpi upon startup, and the keyboard reverted back to QWERTY.
At least that's progress.
But, the phone still simply won't turn on and I get an error message about Device.exe
I'm hoping this isn't due to hardware failure and that there is a software fix for it, but time will tell.
NanoRuler said:
But, the phone still simply won't turn on and I get an error message about Device.exe
I'm hoping this isn't due to hardware failure and that there is a software fix for it, but time will tell.
Click to expand...
Click to collapse
It does not sound like a hardware problem. Have you tried searching at the Windows folder if you do have the Device.exe file? It might just be because of a missing file. I don't know the contents of the Ext ROM, but could this file be in there too. Maybe when you upgraded your Ext ROM, this file was not included. So everytime you perform a hard reset, since it is missing from the Ext ROM, it does not install to your device.
If the file is present in the Windows folder, maybe the registry is pointing to a wrong file.
Had a look and there is no DEVICE.EXE in Windows
your problems with the keyboard layout or 96DPI are dued to ExtROM. In the ExtROM of my ROMs I have added a configuration file to switch to 96 DPI, you have said before that Xacsx said something similar about QWERTZ layout.
The real problem is that Cmonex's ROM does not include ExtROM, so although you revert to his ROM, you still have the previous extROM (from Xacsx or mine). You also need to flash the official ExtROM released by Cmonex.
About the phone problem, I cannot help you. I haven't experimented that isue on my own x7510 (tested both WWE and ESN roms). Anyway, if is a ROM problem, it sould be solved by flahsing another ROM.
Device.exe is in XIP part of the ROM.
Yes, I've already re-flashed Cmonex's extended ROM, thanks Xtep.
To be honest I don't believe your ROM is to blame. I have reflashed Cmonex's extended ROM, then her matching WWE ROM, in that order and still I get the DEVICE.EXE error and still the phone won't switch on.
That pretty much tells me it isn't ROM related.
I've attached the log file (renamed to .TXT) to this post - any help is gratefully received!
It may be worth flashing the full HTC ROM, which incliudes ROM, ExtROM and Radio; once up and running again, you could then reflash your cooked ROM of choice.
Factory ROMsdo tend to fix some of these odd problems.
Hi Neil,
I was under the impression that's pretty much what Cmonex's plain vanilla WWE ROM + matching extended ROM was, which is why I flashed it.
Only thing I haven't done yet is reverting back to the stock SPL.
NanoRuler said:
Hi Neil,
I was under the impression that's pretty much what Cmonex's plain vanilla WWE ROM + matching extended ROM was, which is why I flashed it.
Only thing I haven't done yet is reverting back to the stock SPL.
Click to expand...
Click to collapse
I sugest you to flash a Radio again (I thin that version 1.58 in this thread is from x7510).
You problem is when you activate the phone and that is managed by radio.
Thanks Xtep - I think you're on the right track with your suggestion, but that radio won't flash to my x7510. It keeps failing with unsupported device error message.
Any ideas where I can get hold of a stock radio?
NanoRuler said:
Thanks Xtep - I think you're on the right track with your suggestion, but that radio won't flash to my x7510. It keeps failing with unsupported device error message.
Any ideas where I can get hold of a stock radio?
Click to expand...
Click to collapse
That is because this file is for Athena x7500.
I have repacked the radio for a x7510. You can download it from: http://rapidshare.com/files/191672003/x7510_Radio_1.58.rar
You are indeed a scholar and a true gentleman!
Xtep, I've got phone functionality back! Thanks a stack!!!
And right now I'm re-flashing your ROM!
Did that work NR?
If not, can you PM me- I may have a suggestion, but can't post in an open forum