Related
Ok I have trouble with every rom I have found...
Orbit O2 running the latest WM5.
I start the rom upgrade for B&B and as it starts to get into the strange splash screen (I assume its a bootloader type thing, multicloured), it disconnects from my pc (running vista and the new mobile device centre 6) of course, then reconnects (i hear the tone anyway) but then the rom upgrade program tells me that it cant connect.
Thus my device is stuck on the loading page.
Another attempt to use the UG program brings me further: to the loading % screen. it gets to 3% and then the device resets and loads fully.
This is where it ends. another attempt brings me back full circle...
I had a similar problem with the official o2 rom, but the second attempt didnt stop at 3% so it went all the way.
after upgrading, I cant progress from the above any better.
I want the B&B for its interface, 3d cube and touchflo. Is there a way to add these onto my existing rom?
Thanks guys.
Have you got another pc or laptop you can try this from?
If not try disabling all your firewall and anti virus whilst upgrading.
the real issue i think isthe sync disconnecting while transferring data.
either that or my phone doesnt like anything over the 3% mark on these rom builds.
no firewall, no antivirus.
i had the same problem. this is what i did.
i installed the original wm6 of htc and from there installed bb 4
thanks ill try that.
ive so far installed the o2 orbit rom and then tried the bb4 same problems.
but ill try the htc version now.
You MUST flash the USPL upgrade first. After this you can then flash to B&Bv4.
By the way. If you can get access to a Windows XP computer, use this to flash. Windows Vista as VERY picky when upgrading.
There is a problem with upgrading you're rom in combo with windows vista. I assume upgrading is only possible with active sync 4.5(XP).
USPL and vista give's a lot of problem's like the one you discribe. Try upgrading your rom from a PC with XP.
I had the same problem. I Could'nt upgrade my rom from a PC with VISTA. Xp was the sollution for me.
thanks guys.
im gonna look into upgrading the uspl, but i dont have an xp machine. only vistas and a mac
just tried the uspl....
dos counted up 0...10....20 etc up to 70, then skipped to 100 and the rom update program launched. it went into the multicoloured splash loader then stopped.
im gonna try on xp later if i can...
ok for anyone who has similar issues to me...
I just got a Hermes today (£60, tmob) and same upgrade problems.
XP machine isnt an option for me...
BUT i found this http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=23&Itemid=27 for anyone who needs advice on vista. its very simple and works a treat.
thanks
my experiences
I couldn't flash USPL on my IBM T40p(Win XP SP2). I use other PC with clean instalation of W2K(SP4) and AS4.5(nothing else instaled) and it work fine(flash USPL then B&B 3.7-to test it then B&B 4.0). I realize I'm using Kerio Firewall on my laptop, AS 4.5 don't connect to Artemis with Kerio Firewall instaled!
Advice for all:
1) try again to flash USPL
2) TRY AGAIN!!!
3) try other pc
4) try again
.....
5) once flashed UPSL(your SPL should be 1.11.0000) flash the B&B Rom(or any other you want) - do it on same pc which you use for succesfull flashing of USPL
running vista? upgrade issues?
XP machine isnt an option for me...
BUT i found this http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=23&Itemid=27 for anyone who needs advice on vista. its very simple and works a treat.
thanks
As long as you have updated to WMDC 6.1, flashing with Vista is a breeze. Just plug in the USB cable and flash like XP.
I can confirm that as well, as long as you update to Device Center version 6.1, the vista flashing guide is not needed. The RUU tools (including auto detect) will work fine when the device is plugged in and synced.
Im soooooooooooooooooooo glad I didnt "upgrade" to have vista on my pc
That is the rub...
millercentral said:
I can confirm that as well, as long as you update to Device Center version 6.1, the vista flashing guide is not needed. The RUU tools (including auto detect) will work fine when the device is plugged in and synced.
Click to expand...
Click to collapse
... I've followed MrVanx's instructions but, the issue for me is syncing. I can connect just fine but getting my 8525 to Sync is a no go.
It seems that my Vista machine consistently renames my device from *******_PC to HTCXX (Usually a number).
Weird.
I followed the instructions and successfully upgraded my ROM, but every time I installed SplashID, I could no longer Sync.
So I just downgraded WMDC to 6.0 (found here), and all my problems appear to be gone - I can sync with no problems.
--------
UPDATE
I still get the strange TCP/IP errors - bringing up Vista's task manager, killing WMDC and restarting it makes it go away. Gotta love Microsoft.
ive been running vista and flashing / cooking for 2 months now without any problems (using 6.1) however syncing is a completely different story! In fact I'm waiting for a copy of lastxp to finish downloading to reformat xp back
I have never had any problems with Vista and WMDC 6.1
No problems either, using WMDC 6.1 on 2 different Vista machines, and haven't had any problems flashing or synching.
Many thanks HunterST!
HunterST said:
I followed the instructions and successfully upgraded my ROM, but every time I installed SplashID, I could no longer Sync.
So I just downgraded WMDC to 6.0 (found here), and all my problems appear to be gone - I can sync with no problems.
--------
UPDATE
I still get the strange TCP/IP errors - bringing up Vista's task manager, killing WMDC and restarting it makes it go away. Gotta love Microsoft.
Click to expand...
Click to collapse
Thanks for the tip. I can finally sync again. It's not perfect but, I'm at least getting closer.
Peace.
ratcom said:
ive been running vista and flashing / cooking for 2 months now without any problems (using 6.1) however syncing is a completely different story!
Click to expand...
Click to collapse
I work in IT and am using my system to test Vista functionality within our company. So far it has worked like a charm, much better than the days of beta. I prefer XP still for functionality but I have enjoyed Vista and will probably continue to run it on both my work and home systems (Enterprise, Basic/Home is for the lose).
Flashing has been a cakewalk overall. Syncing isn't too bad however it does have it's hiccups. Two problems have surfaced so far, one is related to WMDC being flaky about picking up the phone (although better in 6.1 than 6.0) the other is related to wirelessly syncing to Exchange which has nothing to do with Vista at all and just my laziness to troubleshoot it. lol
Dear all,
I have been running Starbase64's S64 3.62/HTC on my HTC TyTN HERM200 for several months. Today I wanted to change the ROM to Shamanix Ultimate 2, however, every time I try to run the RUUWrapper.exe I get the message "Custom RUUhas encountered a problem and needs to close. We are sorry for the inconvenience."
I then tried Schaps 4.31 and Custel 2.5 both returning the same result. Trying to reload Starbase's ROM had the same effect.
I then thought to try an "official" ROM and loaded Hermes_Cingular 3.62.502.3_6275. This loaded with no problems
I have successfully changed the ROM on my TyTN a least 15 times previously. I am running SPL-2.10.Olipro and IPL-1.04. After the official load these settings remain in tact. I repeated the attempt to load the above ROMs and have the same error message. This message appears regardless of whether the phone is in normal mode or in bootloader mode.
I am running Windows XP SP2 and ActiveSync 4.5 (build 5096).
Does anyone have any ideas as what is causing this?
Many thanks
I have the same problem. When i want to install Schap's rom 4.31 on my htc hermes i see this message "Custom RUUhas encountered a problem and needs to close. We are sorry for the inconvenience." I use windows xp sp2 and activesync 4.5 too. Can you help ?
Try installing .NET Framework!
Correct install both the .net frameworks: 2.0 and 3.5.
A simple search usually finds this problem a few times
Sorry I have totally ré-install windows xp and I have forget some programmes. Thank you.
Thanks for your insightall of you. I already had .net framework installed on my laptop, however, the problem seems to have been that it was corrupt, and that in itself made it difficult to remove and reinstall.
I found an uninstall tool on the net which deals with all of the registry entries. Reinstalling then updating to 3.5 now seems to have done the trick. I now have the ROM of my choice on my TyTN.
I'm opening this thread to find out the answer as to why the Hermes freezes or lockups on WM6.1. It gives you no other option but to soft reset. Unfortunately, it stays on your second splash screen after a soft reset; so, you will resort only to hard reset your device.
In some cases, it even causes to hard reset your device without warning after a freeze. It's not how long you use the device... it's what you are using most frequently.
In my observation over the last two weeks, it freezes in the following occasion:
1. restoring messages using dotFred PIM Backup
2. introducing exchange server settings
3. frequent closing and opening of SMS application
4. frequent sliding in/out of keyboard
To single out the problem, I have not introduced any changes to the ROM or even installed CABs. I am merely trying to use the base ROM like I used to with WM6.
I have tried various ROMs todate: Schapps, PDA viet, TNT, No ROM maker, Faria's and they all result to sudden system fault in the two Hermes that I have in my possession. I figured, this must be a 6.1 thing, but I noticed that it has not been given attention.
So, let us hear your freeze and hard reset problems on WM6.1 guys!
the only rom that hasnt froze on me has been CRC's rom. All the others seem to suffer from this weird problem.
After so many testing, one more would not hurt thanks for the feedback. Will give it a try.
tjlabais said:
I'm opening this thread to find out the answer as to why the Hermes freezes or lockups on WM6.1. It gives you no other option but to soft reset. Unfortunately, it stays on your second splash screen after a soft reset; so, you will resort only to hard reset your device.
In some cases, it even causes to hard reset your device without warning after a freeze. It's not how long you use the device... it's what you are using most frequently.
In my observation over the last two weeks, it freezes in the following occasion:
1. restoring messages using dotFred PIM Backup
2. introducing exchange server settings
3. frequent closing and opening of SMS application
4. frequent sliding in/out of keyboard
To single out the problem, I have not introduced any changes to the ROM or even installed CABs. I am merely trying to use the base ROM like I used to with WM6.
I have tried various ROMs todate: Schapps, PDA viet, TNT, No ROM maker, Faria's and they all result to sudden system fault in the two Hermes that I have in my possession. I figured, this must be a 6.1 thing, but I noticed that it has not been given attention.
So, let us hear your freeze and hard reset problems on WM6.1 guys!
Click to expand...
Click to collapse
I have semilar issue and now the problem is solved. please click on my signature below why did I go back to official ROM for the detail threat.
same here
i even got my device changed since i thought it was a hardware problem.
it only happens on wm6.1 though, so as much as i like the added speed and threaded sms, flashing the original wm6 rom fixed it and from there im going to keep to wm6.0 - it worked quite nicely.
I suspect (a lot) of bigstorage or some bug on the write-to-internal-rom cache/buffer (if exists) associated to any app that writes to fast to the ROM.
I notice when I use anything on SD card that nothing bad occurs but if I use the internal mem (SMS, internal apps, etc) it freezes all the time.
I had these issues until I used mtty.exe to clean up some bad blocks and then flashed Faria R32, since then no more issues (though opera 9.405 sometimes will freeze my hermes).
I had the same problem until I flashed the offical AT&T WM6 rom with radio and then flashed back to wm6.1..
No freezes or hard resets since..
I don't think this is a big storage issue... if it were, wm6.1 in other similar devices like the trinity would have suffered the same fate, but it doesn't.
I really don't see the point of going back to an ATT official ROM before flashing 6.1. But a lot has said that they no longer have this issue after doing so, then it must be RUU related.
It might also mean: a full ROM flashing for 6.1 might be necessary.
Either way, I'll continue testing, but it would be nice if other guys with this issue will be willing to help test it...
I just made some digging, and just found out how some wm6.1 users get their freezes/lockups. There issue was due to radio compatibility.
hmmm... if the WM6.1 ROM was built with OEM from the AT&T Official, then the radio that best match for it is from the AT&T as well.
This might explain that flashing the AT&T official prior to flashing the wm6.1 sets the radio to AT&T.
Hope this will solve the freeze/lockup mystery.
Have any of you guys tried changing/switching RADIO ROM while in WM6.1?
I just did, trying to experiment. Prior to WM6.1, I loaded an Official Dopod WM6 ROM. Then I loaded the Faria-R32 Full version.
Although, I did not have freezes on the first day of testing... I decided to switch to Radio 1.54 since most users flashed the AT&T Official prior to flashing WM6.1. Guess what? It flashed successfully and boot successfully for the first time. However, when I make a call, the audio has a very poor quality. So, I reset it using the reset button just to clear it up; however, it hanged on first screen... then I reset one more time, it hanged on 2nd screen, then I reset again, it hanged on WM screen.
Enough of it, so, I loaded back 1.47.0.10, and I'm back in business? No. The switching of the Radio ROM has caused the ROM to be corrupted... Somehow, the RADIO has something to do with the freezing...
WM 6.1 ROMs are very unstable (Faria, TNT, etc. I tested several, including those "naked" or clean)
After I install some (useful) software like HTC Home and some other 2-3 programs and after some hours it froze (it did with Faria, TNT, etc). TNT´s WM6.1 is a little more stable (takes longer to froze) but Faria´s WM6.1 is faster.
The more we use the internal flash memory, the faster it frozes and requests a hard reset. Since Friday I hard rebooted some 20x (Faria + TNT roms).
I´ll go back to WM6.0 for now.
EDIT: I installed my radio rom after the last main rom and works very well (I update all roms from the SD card). I updated before and after the main rom (but it never got corrupted) and they frozed. In my case nothing to do with the froze.
I nearly advised my friend to send for service thinking a big hardware problem. Thanks as now I know it's not the phone itself .
Hello,
I had the same problem when 6.1 came out on all 19199.0.7.0 builds. For me the solution was to update to a ROM using build 19199.1.0.0. Since then I had no hard resets at all (I am running CRCs PHK v12 Release 9 for about 2 weeks now).
Maybe this works for you as well.
Cheers,
Uli
mmick said:
WM 6.1 ROMs are very unstable (Faria, TNT, etc. I tested several, including those "naked" or clean)
After I install some (useful) software like HTC Home and some other 2-3 programs and after some hours it froze (it did with Faria, TNT, etc). TNT´s WM6.1 is a little more stable (takes longer to froze) but Faria´s WM6.1 is faster.
The more we use the internal flash memory, the faster it frozes and requests a hard reset. Since Friday I hard rebooted some 20x (Faria + TNT roms).
I´ll go back to WM6.0 for now.
EDIT: I installed my radio rom after the last main rom and works very well (I update all roms from the SD card). I updated before and after the main rom (but it never got corrupted) and they frozed. In my case nothing to do with the froze.
Click to expand...
Click to collapse
I don't think it's the way it's accessing the memory; otherwise, other devices would have suffered the same fate. So far, only the hermes suffer the freezing syndrome which means that there is something in the hermes that is not fully compatible with the WM6.1 build.
did you try to flash the AT&T build prior to flashing the wm6.1 build?
hukoeth said:
Hello,
I had the same problem when 6.1 came out on all 19199.0.7.0 builds. For me the solution was to update to a ROM using build 19199.1.0.0. Since then I had no hard resets at all (I am running CRCs PHK v12 Release 9 for about 2 weeks now).
Maybe this works for you as well.
Cheers,
Uli
Click to expand...
Click to collapse
I was hoping someone would release the 19202.1.0.0 build since it has the updated GWES...
After 24hours with Faria-R32 Clean version. I did not have any freezing syndrome. This is after I flashed with a Dopod Official ROM. I only got the freezing syndrome by flashing 1.54 Radio ROM.
My next move is to use a different RUU for flashing.
My Faria 6.1 also hard-resets and locks up
I had just recovered from a previous hard reset and read all posts in this thread and the other one currently dealing with this topic (http://forum.xda-developers.com/showthread.php?t=370185), and had gone down to a previous ATT radio rom and switched off SD power management out of desperation, when my Hermes locked up again. This time, however, after two soft resets (stylus induced) I managed to get it running again. Everything seemed to be in the previous state (all my preferences had been preserved), but I found that all contacts, history and calendar items had gone.
I had installed no other software than the network wizard. I had recovered most information from Outlook and the rest from Pimbackup (which by the way keeps crashing when restoring speed dials in 6.1).
As this must be the 6th hard reset in 6 days, I think I'm going back to Schap's good old 6.0 and wait for a solution.
BTW Don't take me wrong: I'm extremely grateful for all the great work done by the various cooks.
Lockups
I thought I was going crazy;my 8525 would lock up an have to be soft reset and when it came back, the contacts would all be gone.
I use Yahoo!Go to sync my contacts. I use Photo Contacts Pro for my contacts manager. I was trying to figure out if it was either of those causing the problem.
I even have a thread going on Microsoft's windows mobile forum about this.
I get NO answers from anyone. I'm running Schaps 4.30 OS and Radio 1.54.07.00. I have a 2gb sd card that I run a few apps from.
You just described the same problem I have. Thank you for confirming my limited sanity!!!
tjlabais said:
I was hoping someone would release the 19202.1.0.0 build since it has the updated GWES...
After 24hours with Faria-R32 Clean version. I did not have any freezing syndrome. This is after I flashed with a Dopod Official ROM. I only got the freezing syndrome by flashing 1.54 Radio ROM.
My next move is to use a different RUU for flashing.
Click to expand...
Click to collapse
If i could get hold of the 19202 source I would probably post a clean naked version for testing....but alas no such luck. Naturally it would help had i got a source for new ROM builds lol!
mrvanx said:
If i could get hold of the 19202 source I would probably post a clean naked version for testing....but alas no such luck. Naturally it would help had i got a source for new ROM builds lol!
Click to expand...
Click to collapse
I totally agree with you... when I cooked ROMs for the XDA Atom, I didn't want to work with none official ROMs because I wouldn't know what has been altered in the adopted device.
Hi.
I have been with one Abusalza 6.1 Rom since long time ago (don't remember number even) and it was working more or less without problem. But after months of using, the system become very loaded and dialer, you all know, don't respond quickly, so I dare to change to a newest one.
The problem now is that during last week I have flashed most of then (Joshs, Tay, CRC and some other) and no one is able to sync properly with vista.
Sometime it does (with advanced network unticked in USB2PC), the most it don't.
I have try in two diferent Vista computer and the problem is the same. Also I uninstall the whole WMDC and reinstall it to nothing.
Is there something I can do about that? Is there a new rom know to sync withow problems?
Or should I back to my old, and now missed, PDACorner version, who was able to sync inmediattly and even without disabling the advanced network funcionality?
Thanks in advance
I have found the same problems.
Tai_SW sorted the problem out a few ROMs ago, but even his latest ones have reverted to having Vista sync problems.
Out of desperation, I have reverted to a WM6 ROM, which syncs seamlessly with both my Vista computers.
I tried Josh's WM6.5 ROM, and that synced perfectly! But it had other problems so I am back to my trusty old WM6 ROM.
Going Back
It was PdaCorner v16 which I was using.
And I'm going back to it rigth now. Need Sync for work...
Finally I Installed PDACorner v25, and all beging to work again like a charm.
Even with advanced Network funcionallity on, the connection is nearly inmediate and the WMDC beging syncing in the same machine that yesterday refuse any intent.
Don't know, but maybe Cookers can try to find what has change between this old roms series and newest to solve this problem, or even make a some sort of hybrid merging the old Activesync soft & drivers in new roms. Just thought....
Anyway a big thanks to all good cookers here, without then Windows Mobiles will be a kind of nothing.
same bug here. tried wmdc 6.1 - it not work. advanced network funktionaliti dont wor at all. bluetooth sync work not regulary. tried almost any 2xxx rom - and this bug present. my way (should say try ) to fix it - disable adv netw funktionality, change device name to Pocket_PC, softreset - and almost always it sync. want anather sync - do it again. by the way - win xp work whithout any problems.