Database Info

5.2.1620 & + issue

ive been flashing roms for a good year now with pretty good lucky with everything. but now with the 1620 and greater(1908) i have had the problem where i will build a rom or flash one of the cooks roms(OCTAIVOI's Wizard 4.5) and it will flash fine..but upon the first boot(and every boot after) it will freeze and restart when it reaches the screen calibration... i have only been able to flash and run one 1620 ron and that is NBD 9.1
i really have no idea what this problem is, i have tried everything i can think of(flashing back to manufacture rom)
any help or just ideas would b great appreciated!
i hope im not the only one with this issue...

Perhaps it is a touch.dll related issue, the touch driver on the wizard is either one that is compatible with the Touch sfotware such as the cube etc, and the other is not (the original) perhaps you are combining the wrong driver into the ROM.

no i dont believe so, bc ive tried roms that were already built and tested by others...and i have the same issue some how...and on my rooms i dont include the cube so i dont believe i a touch.dll involved....im starting to wonder if its might b a hardware issue somehow..idk
on another note my wizard cant be overclocked past 223...idk if that could have any correlation...
thanks for the fast response!

Are you flashing from a base rom like tmobile or cingular 1st?
Try those then flash to the wm6 of your choice. NBD seems the most stable with that build.

ROCOAFZ said:
Are you flashing from a base rom like tmobile or cingular 1st?
Try those then flash to the wm6 of your choice. NBD seems the most stable with that build.
Click to expand...
Click to collapse
yes i do flash to base rom first in my case the cingular rom, doesnt seem to make a differnce

unlocked g3 suddenly won't flash TNT

i have a g3 ipl/spl 2.26 completely unlocked device that i have flashed many wm6 roms on in the past. my touchscreen went dead in landscape mode so on a hunch i flashed back to wm5 to try and fix it (which it did). but now i flash the same TNT rom i've flashed a hundred times the same way and everything changes but the OS i tried the boring rom and it changed, but even from there it seems (now) that it's TNT that for some reason won't change the os. any ideas?

which WM5 ROM did you flash back to? was it the official t-mobile ROM?
if not I'd try that first...
if that doesn't work I'd actually take it through the unlocking process again and use that CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE ROM first...the up to t-mobile's offical ROM...then flash to TNT

i flashed back to the latest tmo rom. i'll give what you're talking about a try. as a test i flashed to that one and that's the first one to change the OS. this whole thing caught me by surprise that's for sure.

hope it works for ya...let me know...

update, problem solved! i was using the touchflo rom (love it) and i gave the Professional flavor without the touchflo a try and it worked. all is well.

j3d1n4s7y said:
if that doesn't work I'd actually take it through the unlocking process again and use that CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE ROM first...the up to t-mobile's offical ROM...then flash to TNT
Click to expand...
Click to collapse
hi,
i have the same problem here
what exactly do you mean with "take it through the unlocking process again" should i unlock the wizard again with the service tool (mine is already unlocked and i had 2 different versions of wm6 roms) or just flash the CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE ROM and then the t-mobile one?
p/s before flashing the tnt touchflo i flashed the t-mobile rom, and then while flashing the TNT touchflo i got error on 99%. After that the wizard boots only in boot manager and i can only flash t-mobile rom, the other roms i have tested give back errors (i have not tested the CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE ROM)
Thanks!!!
Regards

i grabbed the latest lokiwiz and used one of the forum stickies as a guide and relocked it and then followed step by step to unlock again. i can't confirm or deny that solved the problem, but it's worth a shot.

NEW SIMLOCK? Emergency calls...

hey hey.
I tried the Simunlocker by jotach
Everything works fine. I get the code to enter, but the field for the 8 digit PIN isn´t there because I only can make Emergency calls...
I thougt it could be ROM problem and I´ve testet all HTC ROM till 1.57. and Installed the radio 1.0
No success.
I read about more people with this problem and without success. Is there another way to unlock? Or is this Phone to new?
Any comment is welcome!

Look on the vert first post under sticky. Unlock your Kaiser is o simple. I test my unlock Tilt with T-Mobile SIM I pop off my iphone. Wow, it works!!!!
Now, I can switch my Tilt with my iphone when ever I need it!!

farmer.joe said:
hey hey.
I tried the Simunlocker by jotach
Everything works fine. I get the code to enter, but the field for the 8 digit PIN isn´t there because I only can make Emergency calls...
I thougt it could be ROM problem and I´ve testet all HTC ROM till 1.57. and Installed the radio 1.0
No success.
I read about more people with this problem and without success. Is there another way to unlock? Or is this Phone to new?
Any comment is welcome!
Click to expand...
Click to collapse
Are you using a 6.1 ROM or 6.0 ROM? I had the same problem with a 6.1 ROM. I was forced to downgrade to a 6.0 ROM, Load the simunlocker, then load up the 6.1 ROM again. Hope this helps, Let me know how it goes.

Hi.
I appear to be having problems and my phone now thinks there is no sim inserted!!
#5. After you unpacked the download you see directories "step1" and "step2". Go into directory "step1" and run KaiserCustomRUU.exe.
This will flash the special patched radio rom. Follow the instructions until it is finished.
Everything was fine up to here!
Note that you can also skip step 6. and proceed with step 7.
#6. Power off your Kaiser and insert a 'strange' SIM, i.e. a SIM from another provider than the one your phone is locked to.
After changing sim as per #6, it now says “Insert SIM card”. – not proceeded to stage #7 yet.
#7. Once Windows Mobile has booted up it will (usually after you have entered the usual 4-digit PIN) show a window called "Simlock" and a textbox where you can enter a 8-digit unlockcode. Now perform a soft reset by pressing the reset button *but* at the same time keep the camera button pressed. If you did it well you will be back in bootloader mode and you see the tri-color screen. The best technique is to press and hold the camera button first and then shortly press the reset button with the stylus.
Anyone got any ideas, as my phone now does not recognise either my original sim or my spare sim.
I see there are a number of people who have experienced this problem.
My phone is the MDA Vario 3 on T-Mobile.
I didn't take a note of the correct ROM reference, only the bottom line which was "P 1.56.110.4", so I wouldn't know which ROM to flash it back to at the end.
All other functions are fine. WiFi, GPS and all my settings. I now have an american keyboard, so lost the £ (£) sign.
It will not recognise either my UK T-Mobile sim or my UK 3 sim.

MSanad said:
Are you using a 6.1 ROM or 6.0 ROM? I had the same problem with a 6.1 ROM. I was forced to downgrade to a 6.0 ROM, Load the simunlocker, then load up the 6.1 ROM again. Hope this helps, Let me know how it goes.
Click to expand...
Click to collapse
I tried with 6.0 and 6.1 !! HTC ROM, AT&T ROM dont work for me.
I downloaded them here: http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
No success and i´ve tested lots of them!

I had exactly the same problem. Caused me a right headache, follow these steps:-
You are more than likely running 6.0 or 6.1 rom, you will need to downgrade first to a rom that's 5.xx first. Then run the Simunlocker and it will work and you will notice the icon to click "OK" on the sim entry screen will appear.
You can then reflash back to the rom that you are currently using, but I would suggest flashing dutty's rom as it's the best.
So to recap:-
1) Downgrade to a rom that's 5.xx first
2) Then run Simunlocker.
3) Then reflash to your current rom or Dutty's.
4) Might be wise to make a note of the radio version you are using as well and then reflash this again.
Good luck.

techceptional said:
I had exactly the same problem. Caused me a right headache, follow these steps:-
You are more than likely running 6.0 or 6.1 rom, you will need to downgrade first to a rom that's 5.xx first. Then run the Simunlocker and it will work and you will notice the icon to click "OK" on the sim entry screen will appear.
You can then reflash back to the rom that you are currently using, but I would suggest flashing dutty's rom as it's the best.
So to recap:-
1) Downgrade to a rom that's 5.xx first
2) Then run Simunlocker.
3) Then reflash to your current rom or Dutty's.
4) Might be wise to make a note of the radio version you are using as well and then reflash this again.
Good luck.
Click to expand...
Click to collapse
HEY THX for your fast reply!
do you still have a link where i can download?
If you have it on your HD, would be nice if can upload it to me...
but... iam really happy to hear that someone had same prob

techceptional said:
So to recap:-
1) Downgrade to a rom that's 5.xx first
2) Then run Simunlocker.
3) Then reflash to your current rom or Dutty's.
4) Might be wise to make a note of the radio version you are using as well and then reflash this again.
Good luck.
Click to expand...
Click to collapse
There is no such thing as a WM5 rom for the Kaiser. Your only choice is 6.0 or 6.1.

OK, I'm wrong on the 5x version (i'm a bit of a newbie). To clarify this I flashed Alex's rom to fix the problem (6.0). Quote from Simunlocker:-
Note for WM6.1 users
================
Do not try this on 6.1! You will need to downgrade to 6.0
Farmer Joe - here's the link to the thread - http://forum.xda-developers.com/showthread.php?t=354583
You will need to search for Alex's Flash rom - ver .52 ultraclean (this worked for me). Then run simunlocker, then run Dutty's rom if you want, then flash a later radio rom for better battery life (I'm using 1.64.08.21...)
How do we setup a WIKI for Orange users then? Any ideas - new to me sorry.

techceptional said:
OK, I'm wrong on the 5x version (i'm a bit of a newbie). To clarify this I flashed Alex's rom to fix the problem (6.0). Quote from Simunlocker:-
Note for WM6.1 users
================
Do not try this on 6.1! You will need to downgrade to 6.0
Farmer Joe - here's the link to the thread - http://forum.xda-developers.com/showthread.php?t=354583
You will need to search for Alex's Flash rom - ver .52 ultraclean (this worked for me). Then run simunlocker, then run Dutty's rom if you want, then flash a later radio rom for better battery life (I'm using 1.64.08.21...)
How do we setup a WIKI for Orange users then? Any ideas - new to me sorry.
Click to expand...
Click to collapse
Everythink works fine now!
To all people with same prob... download Alex's v4 UltraClean and MultiMedia ROMs for AT&T and HTC
then flash the Radio ROM 1.0 from Step 1...
Jehaw! My Kaiser is unlocked!
Thanks everybody for your help and thanks to jotach for his great work!
keep up your good work!

Glad you got it sorted! Enjoy your unlocked Kaiser

NotATreoFan said:
There is no such thing as a WM5 rom for the Kaiser. Your only choice is 6.0 or 6.1.
Click to expand...
Click to collapse
Actually he is correct. I assume he's talking 5.0 CE Version, which indeed the standard WM6.0 Roms are. WM6.1 is CE OS 5.2.
That is the embeded CE version that WM is based upon.
CE 5.0 or 5.1 = WM6.0
< CE 5.2 = WM6.1

Not-so N00B dumb question

I've been flashing new ROMS on an 8525 for a couple of years now, but I'm new to the 8925.
I've been reading a lot, I think I understand the relation between SPL and the ROMs now, but I'm still puzzled.
I keep getting a lot of cruft left behind from prior ROMs and don't know how to get rid of it. for example about three ROMs ago, I flashed the "Mobile Vista" from ansar. Now I still get his Today theme, and there are still a lot of apps installed that read "ansar..."
I've tried removing the battery before flashing, making sure the SPL version is OK with the ROM doing hard resets - nothing seems to let this device start from a "clean slate".
I'm trying to find a ROM I can be happy with, which is why I'm trying so many, but I can't fairly evaluate aon one ROM if I don't know what I've really got installed.
TIA
Walt

I've never heard of anything like that happening Are you sure it is the today theme, or just the boot splash? That would be most likely.
As far as the programs, maybe most of them are from ansar? Which ROM are you using right now?

I just flashed the PDA Corner latest version (15) and it seems to be behaving now. Prior ROMS I tried this morning included Athine, Garmin and Phoenix.
Prior to flashing PDA Corner, I did an "Erase memory" (hard reset from software) and removed the battery for about 10 minutes. Maybe that's what did it. I agree, I've never seen anything like this before, I always thought that flashing the ROM reased everything, but then I started reading about SPL on the Kaiser somehow being more than just a bootloader so I got concerned.
And yes, it was the Today screen including clock, wallpaper, etc. The splash screen on bootup actually did change to the one corresponding to the new ROM.
Thanks.
Walt

When flashing a new ROM, when you get to the "Tap screen to begin" do you perform a Hard Reset?
If not, I suggest you start doing now.
Also, merschle (ex-moderator and Artemis cook) recommended flashing a ROM twice with a Hard Reset in between. I don't do this, but it just might help
Ta
Dave

Flash a stock HTC rom and then try a modified rom again. It always helped me when i got strange flash problems.
http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs

Billun said:
Flash a stock HTC rom and then try a modified rom again. It always helped me when i got strange flash problems.
http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
Click to expand...
Click to collapse
I hard reset three times then I flash an OEM ROM, then I hard reset three more times to be sure. I know it's anal, but it works for me.

I don't know how you're flashing try the SD Card method.
It's safer and more reliable.
The SPL & Rom have closer relationship than on your older device.
A sign of have the wrong SPL or needing to change to another SPL is freezing. If you notice your device is freezing or non-responsive, flash the recommended SPL by the chef.
Don't worry any, I was the same when I upgraded from the Wizard...gotta learn all over again.

Fuze freezes after soft reset - couple days after flash?

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