Develop Bugs

Questions after upgrading to WM6 - Help...

Ok, I have upgraded my Hermes to WM6 using the ROM on the wiki site.
I have installed all my apps and everything was looking great. I then noticed the Extended ROM and half a dozen cab files. So I have installed all of these as assumed they were some sort of patches.
I carried on installing my apps but now after a reboot the SIM PIN Lock entry screen looks a really basic (non 3d) button version and the keypad that should be shown when pressing the green call button isn't displayed I just get a white screen.
I have installed the following apps:-
eWallet 5
Tomtom 6
PocketBreeze 5.2
Phone Alarm + VistaMedia skin
Any ideas on what has happened?
Do I need to re-flash my phone?
Help..
Thanks
Mark

mdavenport said:
Ok, I have upgraded my Hermes to WM6 using the ROM on the wiki site.
I have installed all my apps and everything was looking great. I then noticed the Extended ROM and half a dozen cab files. So I have installed all of these as assumed they were some sort of patches.
I carried on installing my apps but now after a reboot the SIM PIN Lock entry screen looks a really basic (non 3d) button version and the keypad that should be shown when pressing the green call button isn't displayed I just get a white screen.
I have installed the following apps:-
eWallet 5
Tomtom 6
PocketBreeze 5.2
Phone Alarm + VistaMedia skin
Any ideas on what has happened?
Do I need to re-flash my phone?
Help..
Thanks
Mark
Click to expand...
Click to collapse
Which version have you upgraded to?? If it is v0.20.x (thats 0.20.0 or 0.20.1) this is a known issue, seriously recommend reading the thread concerned with the ROM you are flashing before going ahead (the link for the thread is in the table aswell).

mrvanx said:
Which version have you upgraded to?? If it is v0.20.x (thats 0.20.0 or 0.20.1) this is a known issue, seriously recommend reading the thread concerned with the ROM you are flashing before going ahead (the link for the thread is in the table aswell).
Click to expand...
Click to collapse
Hi,
My ROM Version is 3.22.110.1
I installed it from the 1st option in this list:-
http://wiki.xda-developers.com/index.php?pagename=Hermes_Cooked_ROMs
I installed from Mirror 5
I am little confused, is there a way to overcome this issue. Im bit of a newbie so do appreciate your help..
Mark

mdavenport said:
Hi,
My ROM Version is 3.22.110.1
I installed it from the 1st option in this list:-
http://wiki.xda-developers.com/index.php?pagename=Hermes_Cooked_ROMs
I installed from Mirror 5
I am little confused, is there a way to overcome this issue. Im bit of a newbie so do appreciate your help..
Mark
Click to expand...
Click to collapse
So you installed the 'Vanilla' version?? (look at the names on the left side)

mrvanx said:
So you installed the 'Vanilla' version?? (look at the names on the left side)
Click to expand...
Click to collapse
Yes it was the Vanilla version. I have done the wrong one?
Can you point me in the direction of the fix if there is one?
Thanks again
Mark

mdavenport said:
Yes it was the Vanilla version. I have done the wrong one?
Can you point me in the direction of the fix if there is one?
Thanks again
Mark
Click to expand...
Click to collapse
The best thing to do is to is to perform a 'Hard Reset' which will reset your device back to the same point as when the rom was flashed, so you will need to reinstall everything. Suggest you install the same things again but dont install the skin....this might be incompatible with WM6 (since nearly all skins are designed for use in WM5).
BTW, i would take some time to read through the wiki and familiarise yourself with the various reset types and other literature on ROM upgrades, the knowledge in these pages will hold you in good stead for the future sir

mrvanx said:
The best thing to do is to is to perform a 'Hard Reset' which will reset your device back to the same point as when the rom was flashed, so you will need to reinstall everything. Suggest you install the same things again but dont install the skin....this might be incompatible with WM6 (since nearly all skins are designed for use in WM5).
BTW, i would take some time to read through the wiki and familiarise yourself with the various reset types and other literature on ROM upgrades, the knowledge in these pages will hold you in good stead for the future sir
Click to expand...
Click to collapse
Ok, thanks for your help.
Just one other question. Should I have ran all the CAB's from the Extended ROM?

mdavenport said:
Ok, thanks for your help.
Just one other question. Should I have ran all the CAB's from the Extended ROM?
Click to expand...
Click to collapse
Not really....the best thing you can do is to leave the ext_rom alone and just manually configure your MMS and WAP settings by hand. The ext_rom (again) contains cab installers that are designed for WM5.....while most should work in WM6 there are some that dont. ext_rom is something i havent used for ages in XDA-Live (v0.1 and now 0.2) and I dont miss it.
Just install the apps you were running (phonealarm and others). The ext_rom doesnt do much except run carrier based stuff (like themes and automatic settings).

Getting Whitescreens with LVSW? download this

ok, this is a re-done LVSW ROM; if you're getting whitescreens then please flash this and post back as to whether it fixes the problem or not.
http://www.megaupload.com/?d=U30NDFH1
please note: if this fixes your whitescreen, TELL US!

Olipro said:
ok, this is a re-done LVSW ROM; if you're getting whitescreens then please flash this and post back as to whether it fixes the problem or not.
http://www.megaupload.com/?d=U30NDFH1
Click to expand...
Click to collapse
Wath do you change in this ROM?
Thanks for your hard work on this

Olipro said:
ok, this is a re-done LVSW ROM; if you're getting whitescreens then please flash this and post back as to whether it fixes the problem or not.
http://www.megaupload.com/?d=U30NDFH1
Click to expand...
Click to collapse
Just downloading it now, how do I remove the current extrom?
I'd like to use either LVSW or Black2 as my base OS then cook my own extrom with all my selected apps and settings for fast and reliable hard resets, is this a relatively simple sate plan or best left well alone?

Is this still in testing or should i replace the wiki entries?

mrvanx said:
Is this still in testing or should i replace the wiki entries?
Click to expand...
Click to collapse
if it works, I'll redo the whole LVSW package.
nothing is changed in this ROM... it's been reconstructed such that those with whitescreens shouldn't experience them any more.

Olipro said:
if it works, I'll redo the whole LVSW package.
nothing is changed in this ROM... it's been reconstructed such that those with whitescreens shouldn't experience them any more.
Click to expand...
Click to collapse
cool cool. Nice work sir
was thinking a new section of the guide might need to be written LOL!!
Will update the wiki and guide once it is all sorted dude.

mrvanx said:
cool cool. Nice work sir
was thinking a new section of the guide might need to be written LOL!!
Will update the wiki and guide once it is all sorted dude.
Click to expand...
Click to collapse
yes, unfortunately, this also means the tadzios toolchain should be avoided.

surely someone can post whether this works or not.

Works as it should for me.
Although, so did the original 26/3 version, AFTER you updated 1.35/1.40 SPL.
Thanks for all your great efforts! this one is perfect and should replace the original that LVSW released

mxlaser said:
Works as it should for me.
Although, so did the original 26/3 version, AFTER you updated 1.35/1.40 SPL.
Thanks for all your great efforts! this one is perfect and should replace the original that LVSW released
Click to expand...
Click to collapse
yeah... I had a phone here with 1.40 and I was able to *cause* the whitescreen with a modification, this fixes it.
I believe it's because the extra Hermes data that goes along with the main payload has become corrupted; so what I've done is merged it into one with working Hermes data.

come on! I'm going to keep bumping this till one of you buggers with a whitescreen confirms it works

@Olipro
I had the white screen with both LVSW and Black1.2. Downloading now will test. Im running SPL-1.40 at the moment with RUU_Hermes_QTEK_WWE_2.11.255.1_102_6275_1.38.00.10_108_Ship.exe flashed on after all the WHITENESS!!!
JasJam
HERM100 IPL-1.01

stukes said:
@Olipro
I had the white screen with both LVSW and Black1.2. Downloading now will test. Im running SPL-1.40 at the moment with RUU_Hermes_QTEK_WWE_2.11.255.1_102_6275_1.38.00.10_108_Ship.exe flashed on after all the WHITENESS!!!
JasJam
HERM100 IPL-1.01
Click to expand...
Click to collapse
thanks! finally someone replies \o/

@Olipro
It works flawless!!! I extracted to a folder, ran the RUU, forced SSPL, and it updated. Upon reboot I still had the Big HTC logo. THen the windows mobile 6 screen. After that the tap on the screen showed up without the WHITENESS!!!
Oh maybe I should have cleared out the extended rom before loading this....
Anyways Cheers to U Olipro

stukes said:
@Olipro
It works flawless!!! I extracted to a folder, ran the RUU, forced SSPL, and it updated. Upon reboot I still had the Big HTC logo. THen the windows mobile 6 screen. After that the tap on the screen showed up without the WHITENESS!!!
Oh maybe I should have cleared out the extended rom before loading this....
Anyways Cheers to U Olipro
Click to expand...
Click to collapse
no, ExtROM is fine, I presume you want that on there.
anyway... looks like tadzio needs to fix his tools.

Olipro said:
no, ExtROM is fine, I presume you want that on there.
anyway... looks like tadzio needs to fix his tools.
Click to expand...
Click to collapse
Finally tadzio util is the singular origin of the problem?
can you explain detailled why the tadzio util is the problem?
wath so onlooker
thanks and regards

No white screen anymore
Thx for everything you give me the solution...
Veeery very good

Don't know about the white screen issues because I've never encountered one before, but I've tried this one besides other LVSW and Black Edition versions. Seems this one is more compatible with SPB Mobile Shell. Hope to hear news about the toolchain error soon and hope Tadzio will fix it ASAP. Ollipro, I don't really care what others complaining about you but I think you're one of the best one here. Please make your own sub-sections for all your tools. Let's say " Ollipro's Hermes Tools" etc.

It works
Thnx!! It works on my mda vario II.

jcespi2005 said:
Finally tadzio util is the singular origin of the problem?
can you explain detailled why the tadzio util is the problem?
Click to expand...
Click to collapse
I will have a look later today, but I seriously doubt that. The whitescreen problem started occuring with LVSW's March 20th ROM, and currently I know of nobody who had problems with my tools before that unfortunate LVSW ROM.
Can anyone who has the whitescreen problem with a ROM based on a version released before March 20th and flashing with an SPL also predating March 20th please let me know?
Anyway, I will make a version that can optionally preserve both the unused space (for Windows Update) and the value of the sector information bytes.
Cheers
Daniel

Hermes Touchflo: anybody willing to give a proper roundup?

Hi,
i was reading through the posts in this forum and over at 4winmobile.com regarding the porting of Touchflo and all the apps unique to Wizard.
What I still don't get is this:
Is there a "working" CAB already out now? So that I would just need to install that CAB to have Touchflo?
If there is, which would be the best ROM to go with it.
Are there any complete Roms, that have Touchflo already enabled?
How stable is the whole thing anyway?
Maybe somebody who is really into this can give us all an update/ walkthrough on this topic, since information on it is widely scattered over several posts at the moment.
Thanks for your efforts,
trial

roundup... touchFLO is currently only buttonFLO on the hermes.

and at SchapsROM it is only Buttonflo with Blackscreen...

so, there is no proper ROM avaible, that has at least touchButton installed by default?
What about the other questions I asked?
anybody?
thx

Is there a "working" CAB already out now?
Click to expand...
Click to collapse
"ButtonFLO" is known to work well with blackmajik and most latest roms.
So that I would just need to install that CAB to have Touchflo?
Click to expand...
Click to collapse
There is no need to install a cab to assign the button. Just set any button to run the app.
Are there any complete Roms, that have Touchflo already enabled?
Click to expand...
Click to collapse
Yes, there is some rom flying around. black majik + "ButtonFLO" but you have to assign the button. The steps to make it function are in there. Just follow.
How stable is the whole thing anyway?
Click to expand...
Click to collapse
TouchFLO was not meant/made for hermes but for HTC Touch therefore it doesnt run perfectly but some people at 4winmobile.com are still working on making it better.

trialbin said:
so, there is no proper ROM avaible, that has at least touchButton installed by default?
What about the other questions I asked?
anybody?
thx
Click to expand...
Click to collapse
There's a Black Majik ROM that was re-cooked with the added files in Windows over at 4winmobile. I think Slueth? cooked it but not 100% sure. I'm actually using it right now, but I didn't add the ButtonFlo CAB cause the first time I used it, it worked for a little, but as you add apps it acts weird, so, I'm using just the ROM and it's absolutely awesome! Super stable, etc!

guys, thanks for all your replies!
will continue my search with your infos now, and add to this post, as i have more info myself.
regards,
trial

FIX for lost settings (passwords, BT pairing,etc.)?

I've installed MARY 3.7.1 and some other cabs. After a soft reset it was normal that BT pairing, passwords and the GPRS settings were gone or didn't work.
By accident I tried an old CAB from mun_rus calls BT_DUN.cab, I don't install this one normally when I reflashed my device.
I thought the solution was in MARY 3.7.1, but after uninstalling BT_DUN.cab I've found out that the settings were lost again.
The CAB is here: http://forum.xda-developers.com/attachment.php?attachmentid=39883&d=1180164571
Can someone check this with a ROM with the new XIP like MARY, PDAVIET, schaps, etc.?

Stingray66 said:
By accident I tried an old CAB from mun_rus calls BT_DUN.cab, I don't install this one normally when I reflashed my device.
Click to expand...
Click to collapse
Hmm, at first glance you actually seem to be right which is good news for many among us
I had never installed that CAB before, and I learned to live with lost passwords etc. (never got around to trying the workaround), but that's all about to change with this easy fix​Some more tests have revealed that in my case the "first glance" must have been sheer luck
I mainly checked whether wifi passwords were required again, and tried uninstalling/re-installing/rebooting/resetting/... but all I can conclude is that only sometimes the settings are preserved and still most of the times the settings are lost - this regardless of the aforementioned CAB.
Well, I haven’t lost hope yet, though. Maybe someone will figure it out, but the sooner the better

MANY THANKS,
It's seems works fine...
Many thanks again...

Stingray66 said:
I've installed MARY 3.7.1 and some other cabs. After a soft reset it was normal that BT pairing, passwords and the GPRS settings were gone or didn't work.
By accident I tried an old CAB from mun_rus calls BT_DUN.cab, I don't install this one normally when I reflashed my device.
I thought the solution was in MARY 3.7.1, but after uninstalling BT_DUN.cab I've found out that the settings were lost again.
The CAB is here: http://forum.xda-developers.com/attachment.php?attachmentid=39883&d=1180164571
Can someone check this with a ROM with the new XIP like MARY, PDAVIET, schaps, etc.?
Click to expand...
Click to collapse
This would be VERY cool if it works! I hope that's all there is to it.
Thanks again Stingray66! PS: Do you drive a Corvette?

StefanoRuleZZ said:
MANY THANKS,
It's seems works fine...
Many thanks again...
Click to expand...
Click to collapse
Work here again too on the ROM FInixNOver 3.1

SuperSport said:
Thanks again Stingray66! PS: Do you drive a Corvette?
Click to expand...
Click to collapse
I did a couple of times, but I'm not in the position right now to buy one. Priority is my wife, kids and moving to another house right now, but a Corvette from 1966 is a great car ..... beautiful!

I already fixed this problem in my latest ROM (version 1.2).
I created a modified XIP and changed some buetooth drivers to verify A2DP still works.
I will create a personal ROM to verify if this solutions works too!
Would be great if this is another solution to fix the problem.

Ok, I found something!
I opened the rom the ausdim WM6.1 and Mary rom 3.7 and took the files of the *. hv ausdim and copy for the 3.7 rom Mary!
The two rom´s are the same version and don't have any trouble copy, and I noticed that once the 3.7 rom Mary no longer loses the passwords or the codes of wifi!
I think the problem is in the register!
HKEY_CLASSES_ROOT
HKEY_CURRENT_USER
HKEY_LOCAL_MACHINE
But where???
Translated by Google, sorry!

sergitec said:
Ok, I found something!
I opened the rom the ausdim WM6.1 and Mary rom 3.7 and took the files of the *. hv ausdim and copy for the 3.7 rom Mary!
The two rom´s are the same version and don't have any trouble copy, and I noticed that once the 3.7 rom Mary no longer loses the passwords or the codes of wifi!
I think the problem is in the register!
HKEY_CLASSES_ROOT
HKEY_CURRENT_USER
HKEY_LOCAL_MACHINE
But where???
Translated by Google, sorry!
Click to expand...
Click to collapse
The problem is in the XIP section, it is in the nk.exe (kernel).
Ausdim uses an older XIP version which does not lose settings.
The only problem was the broken A2DP. I managed to fix this problem and Ausdim will include my solution to fix A2DP in his ROMs.
Upcoming ROMs from me and Ausdim will no longer lose settings.
I hope other ROM-cookers decide to use the older kernel too.

adewidt said:
The problem is in the XIP section, it is in the nk.exe (kernel).
Ausdim uses an older XIP version which does not lose settings.
The only problem was the broken A2DP. I managed to fix this problem and Ausdim will include my solution to fix A2DP in his ROMs.
Upcoming ROMs from me and Ausdim will no longer lose settings.
I hope other ROM-cookers decide to use the older kernel too.
Click to expand...
Click to collapse
well actually the old xip didnt lose the settings, yet it cause unstable de system, problem include cant find the contacts, lose response when launch the programs from SD card after wake up. I've been suffering for a long time about it which doesnt happens with the new xip and i dont know why, with the same cooking only expect the new and old xip

themaskfly said:
well actually the old xip didnt lose the settings, yet it cause unstable de system, problem include cant find the contacts, lose response when launch the programs from SD card after wake up. I've been suffering for a long time about it which doesnt happens with the new xip and i dont know why, with the same cooking only expect the new and old xip
Click to expand...
Click to collapse
I did not experience any of the problems you describe.

adewidt said:
The problem is in the XIP section, it is in the nk.exe (kernel).
Ausdim uses an older XIP version which does not lose settings.
The only problem was the broken A2DP. I managed to fix this problem and Ausdim will include my solution to fix A2DP in his ROMs.
Upcoming ROMs from me and Ausdim will no longer lose settings.
I hope other ROM-cookers decide to use the older kernel too.
Click to expand...
Click to collapse
So if it is the XIP that matters we cant have a fix right ? Roms using the new XIP are doomed to have crappy A2DP

firiel said:
So if it is the XIP that matters we cant have a fix right ? Roms using the new XIP are doomed to have crappy A2DP
Click to expand...
Click to collapse
As I already said, I managed to fix A2DP using the old bootkernel (nk.exe part of XIP).
This works for wm6.1 and wm6.0.
There is no reason good reason to use the new kernel in stead of the old kernel.

As i say 4 months before here:
http://forum.xda-developers.com/showthread.php?t=342269
the old xip section (nk.exe) is working better with trinity 400mhz.
All my rom in this 4 months is builded with old nk.exe and i tell to cookers to use them to.
I dont see any reason to use the new (dopod) nk.exe with that very iportant bug.
No problems and nothing, nk.exe is the kernel from the device no nead to update that in the future.
The only problem it was in a2dp sound but after the fix from adewidt (Thanks again) the sound it is perfect!
Thank's

adewidt said:
I already fixed this problem in my latest ROM (version 1.2).
I created a modified XIP and changed some buetooth drivers to verify A2DP still works.
I will create a personal ROM to verify if this solutions works too!
Would be great if this is another solution to fix the problem.
Click to expand...
Click to collapse
Well after some resets, it does loose it's settings.
@adewidt
I'll try your 1.2 too, but I think the DEVICE ID of TomTom will change again (like it did whenm we switched from WM5 (official) to WM6 (DOPOD))

Stingray66 said:
Well after some resets, it does loose it's settings.
@adewidt
I'll try your 1.2 too, but I think the DEVICE ID of TomTom will change again (like it did whenm we switched from WM5 (official) to WM6 (DOPOD))
Click to expand...
Click to collapse
Yes it change your device ID.

New battery.dll driver with 1% battery level increments

I couldn't find any info about it here so I think it's worth to mention that no2chem created new battery driver for "Titan" (I think he mean Tytn) it's prepared for kitchen and since I'm not a cook could someone else test it? I think most of us are interested in precise battery measurement
http://www.weienterprises.com/nue/battery.html
Edit: So now this is possible! Thanx to Cmonex and CRCinAU we finally have what we should have out of the box!!! Thank you!!!

HTC TITAN
http://forum.xda-developers.com/forumdisplay.php?f=382

My mistake than pity... It would be nice to have it for Tytn.

AHhhh dam
shamus said:
My mistake than pity... It would be nice to have it for Tytn.
Click to expand...
Click to collapse
Ahhh Dam, I was soooo hoping this was true!!

Will it work?
Are we confident that it won't work on Hermes? Is anyone willing to test it out?

Should be ok, needsto be cooked into a ROM though, using the updated ROM tools these dlls should work on ANY device afaik.

FWIW, I installed this on my 8525 (running Faria's R32 6.1) using a CAB installer found on another forum and it did not work - battery meter showed 0% no matter what. Fortunately, I was able to revert simply by uninstalling.
I also tried the original instruction set, using Total Commander, which resulted in the same. Reverting to the original bat dll didn't work for me either so I had to hard reset.
Hope that helps!

iron_hide said:
FWIW, I installed this on my 8525 (running Faria's R32 6.1) using a CAB installer found on another forum and it did not work - battery meter showed 0% no matter what. Fortunately, I was able to revert simply by uninstalling.
I also tried the original instruction set, using Total Commander, which resulted in the same. Reverting to the original bat dll didn't work for me either so I had to hard reset.
Hope that helps!
Click to expand...
Click to collapse
The dll needs to be cooked in probably.

So, is any of the chiefs willing to try cooking it it any rom to test if it is working on our hermes?

mrvanx said:
The dll needs to be cooked in probably.
Click to expand...
Click to collapse
mrvanx, pardon my ignorance but I can't resist to ask if he successfully replaced the dll (and did a soft reset I presume) and the result is negative, what difference would it make to cook the dll into the rom?

KaiserVideoDriver said:
mrvanx, pardon my ignorance but I can't resist to ask if he successfully replaced the dll (and did a soft reset I presume) and the result is negative, what difference would it make to cook the dll into the rom?
Click to expand...
Click to collapse
It most likely has to reside in the rom as a physical entity rather than overwriting the file on the flashdisk, since alot of the dlls are linked to parts of the XIP on the device. Many dll replacements have this sort of behaviour (Updated ATi drivers are a good example).

mrvanx said:
Should be ok, needsto be cooked into a ROM though, using the updated ROM tools these dlls should work on ANY device afaik.
Click to expand...
Click to collapse
So there is hope I thought all drivers are hardware specific.

so who's willing to cook this in then?! mrvanx?! pretty please?!lol
if you cook it, i will be more than willing to test it out
cheers

Building a ROM now to test it with... I'm testing it with my Stable build - as it should minimise issues... Will post a URL when it's up...

CRCinAU said:
Building a ROM now to test it with... I'm testing it with my Stable build - as it should minimise issues... Will post a URL when it's up...
Click to expand...
Click to collapse
Thanks! Will keep my fingers crossed

Ok - try this test ROM.
Let me know what you see

CRCinAU said:
Ok - try this test ROM[/url].
Let me know what you see
Click to expand...
Click to collapse
Just flashed it and nothing. The battery indicator is present in the tray with "!" sign and the charge indicator in the Main Battery app. is missing.
When connecting phone to charger, the led doesn't turn amber and no sings or messages of charging.
Too bad... I liked the idea.
edit:
for those who just flashed this OS, put the phone into boot mode if flashing something else, otherwise you will be getting low batt. warning even though you had it fully charged.

Doh. I was excited about that too - it'd be nice to see

Damn, thats too bad it didnt work for hermes!

Maybe someone should contact no2chem and see if it is possible to do the same for hermes? I'm guessing it's a hexedit? something else? It may well be portable between devices with a bit of effort.