issue installing netcf 3.5, please help - Touch Pro2, Tilt 2 Windows Mobile General

http://forum.xda-developers.com/showthread.php?t=410454
After following the above link I still cannot get this damned thing to install...or uninstall from my Rhodium.
I changed the .dll to .dll.txt as mentioned, I installed the Safe Mode trial and then ran the .cab--NOTHING seems to be working.
I am getting seriously frustrated as 2 programs I use frequently keeps telling me I need netcf 3.5
I am running Jacko's hybrid rom which is a 6.1 with a sense overlay. I have tried making the installation with both sense off and on.

Related

in-call keyboard issues, back again???

alright, it's been awhile since i've been here but the last ROM i used was vp3g's v3.62.3 ROM on my ATT 8525. well it works great but here's my prob. it was running a little slow so i decided to try some updated ROMs. Now there was a problem with the build-in keyboard being suck on numeric when trying to use the built-in keyboard while being on a call. It worked just fine with vp3g's last ROM. I tried CRC and Shadow's 6.1 roms and it didn't work so i even tried Schaps latest wm6 rom and it still doesn't work. i don't want to use the on-screen keyboard for long texts messages while in a call, that's a pain in the ass. i can't locate any patches for this issue and i researched and it seems to still be an issue w/ other wm6 roms too. does anyone care about being able to use they're built-in keyboards while on a call to surf or txt? i know i do. i hope others and the cooks read this and understand that is was fixed and it's now broke again and needs a fix again. if i'm over looking something with this issue like a patch or a fix can someone point it out to me?
-raven
Raven,
Currenty, I am running K's ROM v1.30b, and dont have that problem...I was able to use both keypads during several calls - might be an issue with the ROM. Might need to either reinstall or switch ROMs again. (I'm partial to K's and Pay's ROMs)
Pays 6.1 rom has this issue as well... The fix has to be cooked into the rom, as it is a keyboard file that has to be replaced... and supposedly you cannot replace the file via the OS...
i'll try k's rom listed above to see if i have same issue. i really hate using older ROMs but vp3g's as i said was the last one that worked for me, unfortunately. hopefully k's will do the job.
I have used that version of K's Rom and can confirm that it does work. Jumped on the 6.1 bandwagon with Pays and issue is back. I'm actually going to flash back to K's Rom until there is a version of 6.1 with the issue confirmed fixed.

Anyone else having serious crash problems with WM6.1 ROMs?

After trying six or seven WM6.1-based ROMS from three different cookers (19199 and 19209), I'm starting to wonder if there's not something 'seriously' wrong with the WM6.1 base image.
I begins to strike me as some sort of duration-based memory degradation. My experience has been that runtime lasts between 2 and 48 hours before a hard reset is necessary. In my case, I pared my installs down to adding merely my password safe as the only add-on, and still it crashed.
The most interesting pre-crash was going to "Programs" and noticing the number of icon substantially reduced (...and reducing...), and the remaining icons as default program icons.
After about five days of fighting with these and trying different methods of extending runtime, I reloaded an older copy vp3G's 3.0.0 from last summer and haven't had a problem for the past 72 hours. In fact, I had no lock-ups with WM6-based, previously.
I'd be interested in other people's experiences with WM6.1-based ROMs on the Hermes...
- Marc
i may be wrong, but i think recall reading that flashing back to your stock rom, then flashin to 6.1 may fix some hard reset problems....
as for me, ive used 4 or 5 6.1 roms and havent experienced a hard reset.....my latest and favorite so far is faria's and dr.p's 6.1 rom, been running a week no hard reset...
im usin an at&t branded 8525
i was having a few issues with this but ended up changing radio versions from my standard 1.16 to 1.48.
havent had an issue since doing that.
i had the crash problem also, but after I not install htc cube in any of the wm6.1, everything ok and stable.
problem is with cube in wm6.1 i think.
Faria's is the best so far, but they all have problems to varying extents. Have you tried running Oxios Close apps? That will help you claim back memory and maybe help prevent the need for a hard reset. you can get it here: http://www.oxios.com/memory/
lupes5 said:
i may be wrong, but i think recall reading that flashing back to your stock rom, then flashin to 6.1 may fix some hard reset problems....
as for me, ive used 4 or 5 6.1 roms and havent experienced a hard reset.....my latest and favorite so far is faria's and dr.p's 6.1 rom, been running a week no hard reset...
im usin an at&t branded 8525
Click to expand...
Click to collapse
Interesting. I did notice that on some ROM flashes that boot screen retained a previous ROM's splash. That might mean that some ROMs are not including all facets (OS, Radio...Bootloader?) of the complete image. Will give that a shot now that I'm back to a stable WM6.
st3v3 said:
i was having a few issues with this but ended up changing radio versions from my standard 1.16 to 1.48.
havent had an issue since doing that.
Click to expand...
Click to collapse
Radio is 1.45 with vp3G 3.0.0. Will check again after a Faria re-flash and upgrade to 1.48 if it isn't included.
fizzy15 said:
i had the crash problem also, but after I not install htc cube in any of the wm6.1, everything ok and stable.
problem is with cube in wm6.1 i think.
Click to expand...
Click to collapse
I had that thought too, but my last ROM didn't include any of the HTC apps, at all, so I think it's some conflict or something lower level. The cube 'is' a resource hog, however...
hamster0914 said:
Faria's is the best so far, but they all have problems to varying extents. Have you tried running Oxios Close apps? That will help you claim back memory and maybe help prevent the need for a hard reset. you can get it here: http://www.oxios.com/memory/
Click to expand...
Click to collapse
The resets are always due to hard lockups, and they can be with only Activesync running as an application. I try to keep the number of running apps at a minimum for reasons that are probably fairly obvious to all here...
you are not alone...
http://forum.xda-developers.com/showthread.php?t=376211
Im also having the same problem .. all sorts of experiments has been done to test on why WM6.1 crash when I install them .. but 1 thing i noticed that it always hang before softreset that eventually lead to hardreset .. i thought hardware accelerations problem ... so what i do is .. every WM6.1 i changed to 8mbpp .. until now my machine ok.
My2Cents.
-/Abid.
Flash to stock rom then to wm 6.1... Apparently there is a problem if you flash from big storage rom to wm 6.1(not sure why this is so) but there have been a huge number of people who say this works for them, myself included.... I tried every wm6.1 rom that came out then doing something stupid eflashe stock os. No problems with wm 6.1 since. Also I believe that 19209 is somewhat more stable than versions 19199 or 19202... I'm using PDAViets 19209 rom,just changed to black edition, and have had NO trouble EVER since installing it when it first came out, no soft resets and more importantly, no hard resets... Cheers
milleniumbug89 said:
you are not alone...
http://forum.xda-developers.com/showthread.php?t=376211
Click to expand...
Click to collapse
Yep, sounds like the same behavior I'm seeing. Soft lock, reset, soft lock, reset, hard reset...lose data... (rinse and repeat)
fix
http://forum.xda-developers.com/showthread.php?t=381959
follow those instructions and your problems will be solved.
I have the same problem! Tell schaps so in his next rom he may fix this serious problem
Shadow CE 6.1
chronosxx said:
After trying six or seven WM6.1-based ROMS from three different cookers (19199 and 19209), I'm starting to wonder if there's not something 'seriously' wrong with the WM6.1 base image.
I begins to strike me as some sort of duration-based memory degradation. My experience has been that runtime lasts between 2 and 48 hours before a hard reset is necessary. In my case, I pared my installs down to adding merely my password safe as the only add-on, and still it crashed.
The most interesting pre-crash was going to "Programs" and noticing the number of icon substantially reduced (...and reducing...), and the remaining icons as default program icons.
After about five days of fighting with these and trying different methods of extending runtime, I reloaded an older copy vp3G's 3.0.0 from last summer and haven't had a problem for the past 72 hours. In fact, I had no lock-ups with WM6-based, previously.
I'd be interested in other people's experiences with WM6.1-based ROMs on the Hermes...
- Marc
Click to expand...
Click to collapse
Use Shadow CE 6.1's rom .. I have been using it for months, and it is near flawless. Do it, you won't regret it . I've tried everything else .
Fix works...
raidzx said:
http://forum.xda-developers.com/showthread.php?t=381959
follow those instructions and your problems will be solved.
Click to expand...
Click to collapse
After trying almost everything to get more than a few hours of runtime out of WM6.1, I followed the above instructions to the letter and WM6.1 has worked for 24 hours now (yes...a new record). I will update in a few days if the Hermes/Faria 6.1 combo continues to function.
One note: I was not able to use Vista to update to Hard-SPL after the Stock AT&T 6.0 ROM re-flash. Each attempt resulted in an updater error on the PC after the handheld entered bootloader mode. Did the same procedure on XP and it worked flawlessly.
Hey. Had the same problems but i solved it with flashing a AT&T Stock Rom first.
Now my Hermes with PDAVIET B&C WM6.1 Rom running like a flash
Without any freezes.
here is the link to my problem thread:
cu
poPY
raidzx said:
http://forum.xda-developers.com/showthread.php?t=381959
follow those instructions and your problems will be solved.
Click to expand...
Click to collapse
Sorry, but following those instructions does NOT solve my problem. It does for some, but not all.
What works for ME, is to turn off the Storage Card power saving.
gregma said:
Sorry, but following those instructions does NOT solve my problem. It does for some, but not all.
What works for ME, is to turn off the Storage Card power saving.
Click to expand...
Click to collapse
I will update the thread with your information, thanks!

Alltel Touch Vogue

Hi,...New here,
I have made the leap into modifying my phone's software enough to download "RUU_Vogue_4350_ALLTEL_WWE_3.10.671.1_RS3.42.30_NV2.02_PRL30031_SHIP.exe" from Software.alltel.com. Was this update supposed to "unlock" my GPS? If not, does anyone know how I can accomplish this? Once I get that going, who knows, I might go crazy and utilized some of the fabulous ROMs you all are offering!
Thanks
Yes that rom update is the official Alltel wm 6.1/ GPS update. It also has a 30 day trial for Alltel nav.
dont forget to go to settings>phone>location settings and turn it to "on"
And if your feeling real adventurous go over to ppcgeeks and try shadow-techs "super fast lock on" AGPS fix. Then download google maps and click use gps and you should be good.
P.S ( AGPS fix not nessissary to make it work, just gives you faster locks)
Goodluck!
Thank you both for your advice! I didn't realize I had to turn it on under settings or that I received the new program (alltel navigator). I am on my way now! I haven't tried the fast lock update you mentioned, but I did install the unlocker so I can give some new looks a shot. Any recommendations for roms to try?
Has anyone had any luck with the official 6.1 ROM and getting the internal GPS to work with a 3rd party program (specifically iGO 8)???
Has anyone had any luck with the official 6.1 ROM and getting the internal GPS to work with a 3rd party program (specifically iGO 8)???[END QUOTE]
Mine works perfectly with tomtom7.
Any recommendations for roms to try?[END QUOTE]
Conflippers Alltel ROMs are the best by far, you can check em out over at ppcgeeks.com
Click to expand...
Click to collapse
Click to expand...
Click to collapse
custom ROM & update?
With this update mentioned above..........I have already flashed to a custom ROM, do I have to flash back to the official alltel ROM before running this update? I have flashed to several REV A roms and can't get my GPS to lock or anything? have tried EVERYTHING, believe me...........
thanks in advance for any help!
Mortplayer and TCPMP crash after loading WM 6.1 updates
I have just completed upgrading my OS to the latest 6.1 Pro and installed Conflippers Alltel ROM (Great ROM) however now mortplayer comes up freezes and then exits. Loaded TCPMP and it just crashes. I use NCH Pocket dictate and it had numerous errors on (Alltel) WM6.1 / LBS Update – Version 3.10.671.1 but after the Conflipper ROM, it works great. Is there an issue with WM6.1 and Mortplayer that anyone knows how to fix? Also, I did update Esmertec Jbed 20081203.2.1.cab that fixed the Java issues with the earlier version.
nfsfans rom
You should try out nfsfans roms here, imo
they are the best out there. They have all the new
touch flo features and are very stable.
He also does a very good job updating and supporting them.
nfsfan
+1 for NFSFAN's roms
Another vote for NFSFAN's rom. Only thing not working for me with alltel is mms.

ROM based on 1.97 causing issues?

Yesterday I started to get problems with my HTC Touch Diamond. I flashed my device with udK Syrius HD R0 (BETA 5) and everything was going smooth, restored my contacts, my messages and tweaked WM6 a bit.
But after a soft reset to apply all changes the device welcomed me with the ordinary "You're using your device for the first time" message and I had to setup my device again. After another soft reset my device hung at the boot screen with ROM information and the "Touch Diamond" text.
All I could do now was a hard reset. But the problem didn't go away... the device kept freezing and resetting, and I had to do 2 or 3 more hard resets before I decided (actually I already had, but had to wait for the download to finish ) to flash to another ROM.
So I downloaded Vic Hybrid 2 Diamond ROM UC. Flashed and everything seem to went fine. But just as before, after a soft reset the device hung. Hard reset...
Why's this!? Is my HTC Touch Diamond broken or is there anything I'm missing? Perhaps this occur because of the ROM's is based on the firmware 1.97??
EDIT #1: sorry, wasn't meant to create this topic under "ROM Development"... Any mod, feel free to move it.
EDIT #2: Seems one more guy had this a relating problem after ROM flash (udK's ROM for that matter too): http://forum.xda-developers.com/showthread.php?t=455335
EDIT #3: "The device is unable to boot because either you have turned off the device incorrectly or tried to install an application from untrusted source. Press SEND to reset your device or press any other button to cancel. This operation will delete all your personal data and restore the device to its factory default settings."... didn't have time to press any "SEND" button either... it continued to... guess? The setup! Entering date + time + calibrating the stylus...
*sigh*... not it happend again. Just restored all my SMS and tried to thread them again (screw that either way!), soft resetted my device... and the damn WM6 setup guide for clock, calibration showed up, and now "Installing..."
*sigh - again*
hi dude i had the same problem
i have a DIAM300 and had the olinex 1.40 hard spl with mossis rom 2.5 (ger)
i flashed mossis 2.6 which is based on 1.97 and i had those problems too, after a few softresets it makes a hardreset...then i tried olinex 1.93 thought it could be the bootloader but the problems were still there...
i tried some other roms, udk Syrius too which is fast as hell, but unfortunately the same problem here and sometimes it even didn't boot...
i made about 50 softresets, 20 hardresets, flashed bout 10 times....then i had enough, flashed the original O2 rom, flashed the original bootloader, flashed the original rom again, and now everything is allright, it's runnin, no hardresets, i tried about 20 softresets, installed software blabla....
but now i'm wondering if the problem will be there again when i start to flash
and its really annoying when u flash a rom, customize everything, everyting seems to be allright and then it makes a hardreset instead of a softreset....
gizz68erz said:
then i had enough, flashed the original O2 rom, flashed the original bootloader, flashed the original rom again, and now everything is allright, it's runnin, no hardresets, i tried about 20 softresets, installed software blabla....
Click to expand...
Click to collapse
Damn, I don't want to flash to the orginal ROM! Just flashed to a ROM I've tried earlier, based on 1.93, Panosha ShineOn, so let's see if there's any more trouble...
gizz68erz said:
but now i'm wondering if the problem will be there again when i start to flash
and its really annoying when u flash a rom, customize everything, everyting seems to be allright and then it makes a hardreset instead of a softreset....
Click to expand...
Click to collapse
Yeah, I feel the pain. Getting sickin' tired of this **** now!!!
Try this one
Hi
Whenever i have this kind of bizar issues [ also with previous devices i had before my Diamond] i did the following:
1. Flash back to original official ROM including Radio [ no need to compelrte the initial setup , just flash and go back to bootloader screen right after]
2. Flash again to the targeted cooked ROM
3. Probelm disapeared
My assumption is that for some cooked ROMs the coverage of files been flashed and replaced is not 100% and therefor we face inconsistancy issues.
Try it
my view of this
my view of this:
new roms have other architecture such as new manila new drivers etc etc (1.97)
when you "tweak" them such as manila mods wich are made for older versions this kind of problems can happen. the problem is we have to many modded roms right now. we have 1.37 roms 1.93 roms 1.94 roms (ported from raphael) 1.97 roms and so on. all of this roms you cant compare with each other.
a example: HTC Diamond Manila has no LANDSCAPE files. every rom wich has landscape support had included RAPHAEL Manila parts. no one can deny this. cause its the only device right now that offered the landscape support on manila. but looking to diamond application and software section here and the date this files were made are back in the past. this is just a example where this problem result of.
just my 2 cent
alphazero said:
my view of this:
new roms have other architecture such as new manila new drivers etc etc (1.97)
when you "tweak" them such as manila mods wich are made for older versions this kind of problems can happen. the problem is we have to many modded roms right now. we have 1.37 roms 1.93 roms 1.94 roms (ported from raphael) 1.97 roms and so on. all of this roms you cant compare with each other.
a example: HTC Diamond Manila has no LANDSCAPE files. every rom wich has landscape support had included RAPHAEL Manila parts. no one can deny this. cause its the only device right now that offered the landscape support on manila. but looking to diamond application and software section here and the date this files were made are back in the past. this is just a example where this problem result of.
just my 2 cent
Click to expand...
Click to collapse
Yeah, I bet there's some issues with the new 1.97 and all the new drivers. The chefs need to get stuff straight before I'm trying any new 1.97 based ROM out again.
My issue seem to have been fixed after flashing to Shine On 2.4 Full (1.93 based!). My device now soft resets OK, and I keep all settings... well, atleast for the moment. I'll continue to soft reset every now and then to see if the problem comes back to me.
Yeah, got EXACTLY the same problem with ROMs based on Touch HD or Quartz OS built Hard SPL 1.93 And I don't use any manilla mods, prefer its original view with original tabs. All I have is some portion of software to install:
- Inesoft Cash org;
- Inesoft Address book;
- Agenda Fusion 8;
- Alreader;
- Auto keeper;
- HiCalc;
- Navitel Navigation system.
and the only "tweak-like" soft I use is Answerkeysdisabler. But having serious intentions to reach the truth I didn't install it.
When I've tried to flash syrius beta 02 AND beta 05) I got a STABLE hard reset after 3-5 reeboots. And it doesn't correspond with the quantity of soft installed, it's just resets and thats all.
When using Aztor v7 i had 99% hangup when installing my software just after HR, and it always hangs on different program installation, then, after reeboot manilla cannot start.
These are very interesting ROMs, especially I like AZTOR's pholosofy, but... couldn't manage to give it a try
Tried SwiftBL's, Dutty's, Bepe's ROMS - all smooth and fine. And the STABLEST FOR ME was the old bElite 0,99d. NO issues at all! Now i'm usind Dutty's 3,4 in general it's stable and ok, but with some minor issues. Would be really nice to have issue-free ROM based on new versions of software.

WOW....that was wierd!!!

My Dash has been running WM6.1 080408 Final For Excalibur WWE with English - By Kavana without any issues for months. Then rather spontaneously I was unable to access some of the settings and would get a message saying the settings couldn't be opened. So I re-installed the ROM. It fixed the settings access, but only for a couple of days and it went back to not being able to access the settings. I searched the forum and found one thread that recommended deleting a registry folder, which I did without luck. Any ideas? I am presuming that this is a software issue rather than a hardware issue.
Thanks in advance.
Why don't you try switching to another ROM? Mabye this one; |ROM||WWE|| ** EnergyROM Series 1.0 21040 - HTC Snap based ROM ** || Build 50909 |
Thanks Bigmannyjr, but that ROM looks like it is still owrking out the bugs. I need something that is solid now.
you wouldnt by chabne be doing a restore using sprite backup would you? sprite backup while being a good restore program, has done things like this to me too after i switched to WM 6.1.
On a side note.... BOOMER!
sorry for the plug.
Actually was using Sprite, but did not re-install after the second ROM update so I don't think we can consider it related to Sprite.
SOONER!!

Categories

Resources