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
Related
Here's a Qtek 8310 latest radio ROM (2.47.01)
ftp://xdaupload:[email protected]/Tornado/8310 radio only/8310_024701_RADIO.exe
I dont know if it's vendor indipendent
It will not affect your data od other ROM parts, you can flash it to any AKU2 ROM... might fix some of your network problems (searching, signal strenght, gprs problems in roaming etc)
Here's an older version on Modaco: (2.37.01)
http://www.modaco.com/Tornado-Radio-Update-411319-023701-t244555.html
Enjoy!
Thanks for posting.
This Radio is from QTEK IU build. YOu can flash it to any vendor Tornado (Hertz) device. startup screen screen says QTEK IU build only. obviously, this one is not for production environment.
Just wondering, do you know what is new or what has been changed with this ROM? Thank you
this one has been recieved by a european dealer as a latest radio alltogether to correct issue one big vip customer had (perhaps microsoft europe itself)
if the red letters dont bother you, use the radio, it's good.. it can always be reflashed to original
about the changes, Ive been told there's no relese note with fixes, but it contains all updates after 2.09 radio, therefor, the 2.21 corrections are all there, as well as 2.37
jsp_m said:
Here's a Qtek 8310 latest radio ROM (2.47.01)
ftp://xdaupload:[email protected]/Tornado/8310 radio only/8310_024701_RADIO.exe
I dont know if it's vendor indipendent
It will not affect your data od other ROM parts, you can flash it to any AKU2 ROM... might fix some of your network problems (searching, signal strenght, gprs problems in roaming etc)
Here's an older version on Modaco: (2.37.01)
http://www.modaco.com/Tornado-Radio-Update-411319-023701-t244555.html
Enjoy!
Click to expand...
Click to collapse
Does this radio update work on the i-mate SP5?
yes, it does work. NO probs there..
jsp_m said:
......
if the red letters dont bother you, use the radio, it's good.. it can always be reflashed to original............
Click to expand...
Click to collapse
You can always change the startup screen to what ever you want - to avoid the red letters there.
beta rom aku3 for tornado?
since i noticed that you see alot of aku3 beta roms for other htc devices ,i wonder if the smae sources could help us out on beta aku3 for tornado?
Can anyone give an advice how to flash RADIO only for Qtek 8300 with Russian flash 2.0.10.0 (latest)?
When I'm trying to flash radio from the 1st post of topic, I 'm finding message "Invalid Vendor ID" (OK, I didn't apply SuperSID unlock - just do not want to do it). After editing file nk.bkf by means of TyphoonNBFTool (0.4) - I receive a message "Upgrade only" :shock:
Qteck radio upgrade helped my SDA
SecureGSM said:
yes, it does work. NO probs there..
Click to expand...
Click to collapse
I've got a T-Mobile SDA with the i-mate SP5 ROM version 2.0.8.0. I just flashed the Qtek radio upgrade 02.47.01 and it seems to have made quite an improvement. Not only does it spend less time searching, but it seems to hold on to weak signals better too. Just thought I'd put in my report. Thanks for posting the ROM.
Jeff
Wow
What a wonderful improvement in signal!!! I use cingular service for my qtek 8300, and it would always bounce between 'Suncom', and 'home service' usually with 1-2 bars indoors (with the qtek 8300 aku2.0 ROM). Now, it is locked solid on Cingular with at least 3 bars. AWESOME!!! THANKYOU!!!
I downloaded and run the file above and it mentions that my:
imate sp5m image version 2.6.331.2 will be updated to
qtek 8310 image version 2.5.322.99.
Anyway, I run it and now I have
radio: 2.47.01
operator: 2.6.331.2
rom: 2.0.8.0
Thanx!
Finally I've flashed my Qtek 8300 with this radio! 10x to TyphoonNBFTools developers
Files for update were uploaded here: http://rapidshare.de/files/36577121/Radio_8310_NoSID.rar.html - this is not premium account, so file will be deleted after 30 days of non-download!
Just download it, extract and launch ROMUpdateUtility.exe
Hope that is will be helpfull for somebody.
how about a beta rom leaked from htc for tornado something like aku2.3 or better
aku2.3 or better rom ,just like all these beta rom s for pocket pc floating around here hwy cant we get one for tornado?
this radio update may be flaky
Hey,
well, my qtek 8300 says that it has better reception (as per my previous post), but I am missing a lot of calls since installing this radio update. Something wierd going on. I reverted to the original (see previous link to Modaco forum), and hopefully that will fix things.
radio update effects
Hey,
I noticed with this new radio update that the 'free memory' on my qtek 8300 decreased about 5MB, from about 24MB to about 19MB, with no programs running. When I reverted to the old radio, this problem went away.
Anyone else notice this?
dm251z said:
I noticed with this new radio update that the 'free memory' on my qtek 8300 decreased about 5MB, from about 24MB to about 19MB, with no programs running. When I reverted to the old radio, this problem went away. Anyone else notice this?
Click to expand...
Click to collapse
Nope. I have 20.95M FREE (and there are Explorer, AlReaderLight and Messaging in RAM).
I have the Cingular 8125, will this Radio upgrade work for me?
ZlydenGL said:
Nope. I have 20.95M FREE (and there are Explorer, AlReaderLight and Messaging in RAM).
Click to expand...
Click to collapse
I had almost 23MB free (with papyrus on the startscreen)
Anyone out there still have this Radio ROM available for download? Or is there a newer one that can be used?
Trying to fix some issue on my wifes SDA.
sounds good. but i've got the latest radio version 4.1.13.28_02.61.01 running on my Dopod 577w. look here: http://www.pxdxa.com/read.php?tid=24816
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 get no sound from the loud speaker after i load not OEM ROM(like Duty's Hybrid), when i flash the original att tilt rom then the sound works, anybody has any clue what could be causing this?
thanks in advance
same for me...bye
Hummmmmmm let me guess, do have the radio rom 1.27.14.09
taiseer999 said:
Hummmmmmm let me guess, do have the radio rom 1.27.14.09
Click to expand...
Click to collapse
Right! I had the same thing after flashing the radio 1.27.14.09. The only one way to solve it is to reflash the shipped rom!
nugift said:
Right! I had the same thing after flashing the radio 1.27.14.09. The only one way to solve it is to reflash the shipped rom!
Click to expand...
Click to collapse
no need to flash the ship rom,just flashing the other version radio is need
Yeah downgrade radio rom only; found all radios here : ftp://xda:[email protected]/Uploads/Kaiser/
taiseer999 said:
Hummmmmmm let me guess, do have the radio rom 1.27.14.09
Click to expand...
Click to collapse
nope, what i got is: 1.27.12.11 the one that came with dutty's hybrid rom
Dutty's Rom doesnt come with a radio. Try a hard reset.
ok here is what i did, doesn't really make much sense to me, because i've done it before:
i installed the original att rom and then duty's hybrid and everything works now, and also i did this on different pc.
but anyway everything works now
thanks
marcini said:
ok here is what i did, doesn't really make much sense to me, because i've done it before:
i installed the original att rom and then duty's hybrid and everything works now, and also i did this on different pc.
but anyway everything works now
thanks
Click to expand...
Click to collapse
Hmmm, i tried that to when i first got the rom because i wanted the radio, but when i reflashed dutty's rom i still had no sound...
I dont think this problem is related to the ril.dll i did a quick file compare and they appear to be the same file, so something else must have changed...
As I wrote on the ATT ROM thread I had cooked a stripped version of this new rom aku 0.4.4 build 18128 and flashed with the new radio 1.27.14.09. Everything was fine with the sound and then after removing some more files I lost sound after flash. I put all the removed files back and reflashed... Still no sound
Went back and re cooked the whole thing but still no sound. Flashing another radio with this ROM doesn´t work either. I continue to look for the cause... keep you posted
christonge said:
As I wrote on the ATT ROM thread I had cooked a stripped version of this new rom aku 0.4.4 build 18128 and flashed with the new radio 1.27.14.09. Everything was fine with the sound and then after removing some more files I lost sound after flash. I put all the removed files back and reflashed... Still no sound
Went back and re cooked the whole thing but still no sound. Flashing another radio with this ROM doesn´t work either. I continue to look for the cause... keep you posted
Click to expand...
Click to collapse
thanks for the research, i would like to know as well
Some Differences in Sys portion of ATT ROMs and HTC Rom
I think I found some clues...that might be useful to those with greater knowledge then me....
I used Kaiser Kitchen V0.1 I exyrtacted Original ATT ROM, the Original HTC ROM, and the New ATT ROM. I then used Ultra Compare Professional to compare the three Roms' "SYS\PhoneRedist" &" \SYS\Phone" folders and sub folders. What I found is that:
1. the "SYS\PhoneRedist\" is the same for Original ATT Rom and the Original HTC ROM but that the New ATT ROM's following files are different ( Hex to Hex compare versus a simple size compare):
d9d7d86d-3f83-4289-bd32-aa1972a1447e.dsm
cprog.exe\imageinfo.bin
ril.dll\imageinfo.bin
cprog.exe\cprog.exe
cprog.exe\imageinfo.txt
cprog.exe\S000
cprog.exe\S001
cprog.exe\S002
ril.dll\imageinfo.txt
ril.dll\ril.dll
ril.dll\S000
2. the "\SYS\Phone \" is the same for Original ATT Rom and the Original HTC ROM but that the New ATT ROM's following files are different ( Hex to Hex compare versus a simple size compare):
2a6583ff-6047-46cc-b9be-b7deca1152c3.rgu
GAC_Microsoft.WindowsMobile.Telephony_v1_0_0_0_cneutral_1.dll
Lastly I also briefly examined the two ATT Roms' "OEM\OperatorPKG" folders. I did not do same extensive analysis but found that the AudioPara4-CWS_V6.csv has a series of audio settings that were not in the AudioPara4-CWS_V5.csv file. This file is identifeid in ATT's registry audio entry
"<HKLM\Drivers\BuiltIn\WaveDev"> <parm name="AcousticFile" datatype="string" value="\windows\AudioPara4-CWS_V6.csv"/>
AudioPara4-CWS_V5.csv file content (see attached file)
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.
My fuze is freezing after a soft reset, and the only solution I have found is to hard reset.
I recently flashed hard-spl and my first cooked ROM. A few days later this happened. It freezes just after the animation sequence. I hard reset the phone, set it all up again, couple days later - frozen again. Tried a different ROM, loaded fine, set it all up, couple days later - frozen. Tried a 3rd ROM, same thing.
I was running the stock at&t fuze ROM up until this with no issues. I have tried 2 different versions of the Energy ROM 2.0 and once with Shep's 6.5 ROM.
I'm getting pretty sick of setting this thing up. Any ideas, maybe a bad hard-spl flash?
I had the same problem before, i fixed it with flashing back stock rom, reflash hard-spl and trying a diffrent build of my favorite rom, and to be honest i have no idea what fixed it.
Ok thanks for the reply. I am going to try a reflash of the hard spl, and a new ROM. Something makes me think the hard spl is the problem, but a new ROM can't hurt at this point. I will post my results...... in a few days. Thanks again!
Having almost the same problem. Where exactly was it stopping?
I get the first splash-screen, afterward in the lower right corner the 3 red version numbers appear and nothing happens, i dont get to the second (animated) splashscreen, nor to the windows mobile one.
More info:
Stock Rom
--> flashed HardSPL
--> flashed PdaViet V11
--> months later V15
--> weeks later WM 6.5 Testrom, disappointed --> flashed ProvenRom 3.3
--> trouble began approx. 3 days later
--> reflashed ProvenRom 3.3
--> trouble started again, then i did a hard reset for the first time
i will try reflashing stock rom, then hardspl, than custom rom and report in a couple of days
same thing happened to my htc touch pro. i havent fixed it yet
Happened again. I had reflashed the hard-spl and then a new version of the energyROM. It froze up later that night. Iam getting the first splash, with the red numbers, romversion etc., then the animation plays, the it freezes at the end of it. I guess I will try to flash back to stock ROM and see what happens. Until someone has a fix, I guess it'll be trial and error. I'll keep you posted.
And again, twice.
I thought everything was fine, workin good for a couple of days, then it froze again. Any thoughts or further suggestions would be highly appreciated.
Seems like it happens while I am setting things up, phone starts to get laggy after a soft reset, after adding a cab that requires a soft reset. Then it freezes on the next reset.
Software Version
I think we should narrow this down by comparing the software versions.
I'll start:
Radio: 1.14.25.05
Rom: Proven 3.2, 5.07.831.17 build 5.2.21042.1.6.1
HardSPL by Olinex
now you go!
addition:
i also remember, this happened after a cab-install. Do you remember WHAT you actually tried to install? I think for me it was HomeScreenPlusPlus UI. Afterwards it was always Opera that stopped responding and i had to soft-reset --> total failure
I had the exact same problem...you can see it in the DaG 6.5 Kitchen thread. I tried flashing to a known custom Rom that I know worked and it still had the same issue. I fixed it with the advice of someone there, the same advice that's here. Flash a stock rom, hard reset....then flash a custom rom. I don't know why that fixed it but it did.
Hmmm, maybe this will work. I had tried that and it did seem to work. However, after a few days I got sick of the 6.5 and flashed back to the energyROM. So I will give this fix another shot.
In regards to the previous post here's what I am running:
radio: 1.12.25.19
Rom: EnergyROM 2.0 build 41609
Hard SPL - SPL-1.90.by Olinex
Its almost becoming funny now. I did a soft reset so I could see the radio version and guess what - it froze again.
It seems like if I don't set everything up, it will last a few days, but sooner or later I get fed up with not having progs installed etc. and after I set it up - poof!
So here is a list of cabs and general things i do to setup the phone.
Hard reset - reset at screen setup - ROM intitial setup - device reboots itself-
-PPCPIMBackup (installed on ROM, just restore contacts)
-ChangeScreen or Gyrator / have tried both individually, not at the same time
-DredSensor
-KforTouchPro
-HTCWeathermaster Rhodium
-Gscroll 2.0 (beta)
maybe something else I haven't installed every time
of course, set owner name, setup e-mail, the rhodium world clock bug setup, general tf3d setup (contacts, weather, tabs etc.)
Add shortcuts from my sd card for previously installed progs.
I'm not sure that any of these are the issue. I have done this at least ten times. Each time I have noticed which was the last cab installed then freeze, I try not to install that cab, then it will still freeze, eventually.
I am going to reflash the stock ROM and stock SPL, then hard SPL and a ROM flash. I'll be sure to post my results.
i tried latest mystic 6.5 rom lite beta 1.1 and it froze within a day at the second splash screen and after about 1-2 min the screen turned white. I have tried the battery removing trick, but same results. I'm not sure what apps i have installed after hard reset...
i tried latest romeos rom 6.1 randium edition: it got frozen after some time...
same with both NRGZ roms: 1 and 2 version (standard raphael manila and rhodium manila).
Now i'm using romeos wm6.5 rom 2.101... will post if it freezes...
i havent tried this: "reflash the stock ROM and stock SPL, then hard SPL and a ROM flash" yet...
at10ti0n said:
Now i'm using romeos wm6.5 rom 2.101... will post if it freezes...
i havent tried this: "reflash the stock ROM and stock SPL, then hard SPL and a ROM flash" yet...
Click to expand...
Click to collapse
I had no luck with this solution, and it is not exactly what was described.
Actually the solution posted is to just flash stock rom, hard reset, then flash custom rom.
I tried the above solution and it still froze, now I am going to try the correct solution posted and see what happens.
Frozen again... I am going to flash back to stock rom, stock spl, see if it still freezes.
This works (for me)
Running fine for a week:
- Flashed stock ROM (O2 German). This replaces the radio and the OS
- Went back to stock SPL. THIS IS TRICKY, SO READ(!):
+ Olinex HardSPL will NOT let you flash back to your StockSPL, because it is write-protected. This kept me up quite some time.
+ Flash your Stock ROM
+ Then, flash the hacked 195 SPL mentioned HERE: http://forum.xda-developers.com/showthread.php?t=502720
+ then, flash your Stock SPL. Read the Threads: http://forum.xda-developers.com/showthread.php?t=410150
+ Make sure, your SPL is neither Olinex, nor the hacked 195 in the third picture
+ I flashed the Stock ROM again just to be sure the stock SPL runs and allows your stock ROM to run.
- Flashed HardSPL
- Flashed Energy ROM 2.0 WITHOUT Manila, flashed latest Radio, installed cabbed Rilphone.dll
Installed Resco, Resco Today, MortPlayer - this is the SAME setup that got me caught the last time and now runs fine for a week.
This works for me. I presume some ppl get the stock SPL flashing wrong.
As i can read from other roms, it happens ONLY to Roms with the new rhodium manila,
so maybe, if you're tired of reflashing and hard reset, try one without the new manila interface.
Another suggestion: I have a different Opera now. Many describe they tried to start Opera, THEN it hangs and the phone gets stuck on bootscreen. I have 9.5 Build 15613 now and this one runs fine.
I encourage you to try energy ROM 2.0 without Manila. There seems to be a battery issue and someone uploaded a version with better battery life, you may try this, but i don't find the post anymore and this may have rhodium manila included. Energy ROM 3.0 is out now netherless, maybe someone can follow my instructions and try this with 3.0.
Hope i could help, this was bugging me SO LONG
Wow, thanks!
I have been running the stock at&t rom since my last post with no freezing. I will try this step for step, and I will try energyrom 3.0 just to let you know.
Wish me luck!
Well, I was able to get the stock SPL back, just as you described. Thanks again for the info.
However, I flashed EnergyROM3.0 and it froze after a few hours. Of course that rom has the rhodium manila cooked in, so I am going to try again with another rom. I will report back later.
from my last post i have been using romeos wm6.5 v2.101 with no freezing.. it has NO manila cooked in.
I think, maybe it has something to do with manila :-?
Same problems here as described. Using:
1.14.25.05 Radio
EnergyROM 3.0 WM6.5 50409a version
Started after flashing the WM6.5, reproduced easily after 1-2 hr of ROM on phone, it freezes (either by installing something, or Manila general use) then stays on information screen of versions.
Going to try stock ROM + reflash SPL then flash EnergyROM 3.0 again. If that wont work, i go back to 2.0 which worked well.
OK guys I am going to report this issue has been fixed (though not solved) for me.
I flashed ROMeOS wm6.5 v2101 and am also running the version of opera previously posted. I have been running for almost a week with no freezing, and (knock on wood) do not expect it to.
I am very happy with this rom and don't plan on flashing again for a while. However, if I do I will report any success/failure. I am curious to know if the problem is just certain roms, or something specific in them. If anyone else having these issues would care to post their results with other roms, it would be appreciated for the sake of the community.
I also wanted to note that I flashed the RRE wm6.5 non-manila version just before this and it did freeze on me. So it may not be related to the rhodium manila.
Anyways thanks again to all who posted and helped with this. I can't tell you how happy I am to have stable phone again!
Good luck and happy flashing!
same thing happened to my htc touch pro. i havent fixed it yet