After watching for months the issues that many have suffered over this problem, I finally found a solution that will fix all the woes.
A few months ago I was one of the many here that upgraded to 1.11 ROM, had the problem. It drove me crazy to the point that I went back to the 1.06 ROM that was rock solid. Well the other day I did a hard reset to have a clean slate. While looking at the Extended ROM I saw the file DefaultV_1.12 in the EXT Rom (Compared 1.11 ROM on FTP to my device). This was the same file that a XDA developer member had modified to somewhat solve the GPRS problem a few months ago.
At this point I had a hypothesis, so I pulled the same file from the older 1.06 ROM which was rock solid and did not have the “Cannot Connect” problem. In this EXT ROM it is named Default_Version_WWE_106150.sa.CAB.
Installed it first on my Blue Angel as a guinea pig, then for the next three hours I would sit there and disconnect and reconnect. I did it manually by holding the red button to disconnect, then I would reconnect to another webpage, then would have a call come in while in the middle of the GPRS session which would suspend it. After done with the phone call I would reconnect manually by clicking connect as well as by just hitting a link on the webpage.
The Results: No “Cannot Connect” problem.
So off I went to my Magician:
Upgraded to 1.11(I have 850 JAM)
Installed Default_Version_WWE_106150.sa.CAB
Put the phone through its paces, I have been disconnecting and reconnecting without a single problem. I receive phone calls that suspend the GPRS session and I am able to reconnect without a problem. Activesync is able to make OTA connections without a hitch.
During my trials I used the same programs:
Which included:
Photo Contacts(newest version)
Activesync
WEBIS Mail 2
xVbar
PocketZenPhone
Regking 2003
As the only variable throughout the trials was Default_Version_WWE_106150.sa.CAB
This is the solution folks.
At least until someone says it does not work.
Installation Steps:
1. Download CAB that I have attached.
2. Copy over to device
3. Install
4. Soft Reset.
1st of all let me say this is a great site for the HTC devices, I found it years ago when i had the first XDA (Wallaby i think) and now i own a O2 Mini.
I have just installed your patch and i'll let you know how it goes.
I wonder if this patch does the same as the "downgrading" of the caller id as detailed in this thread: http://forum.xda-developers.com/viewtopic.php?t=20428
The downgrade has been succesful for blue angel users too.
randomshots said:
Installation Steps:
1. Download CAB that I have attached.
2. Copy over to device
3. Install
4. Soft Reset.
Click to expand...
Click to collapse
Many thanks for posting this information.
For a relative newbie like me who has never manually fiddled with ROM files, can you please explain what I actually have to do to "install" the CAB file, i.e. in which directory on the device do I put it, and how do I run it?
- Peter
Once copied over to the device just place it where you can find it using the file explorer. Once located using the file explore simply click on it and it will install on its own. Do a soft reset and enjoy.
Crisscross: The Photo Contact solution that people have found only alleviates the problem a little, not entirely.
In my trials it has solved my problems completly. I wish for other members who try it out to report back as well to see whether all my trials were just a fluke, or our solution.
don't work for me
don't work for me. same problem as before, can't connect due unknown reason.
thanks anyway.
Orcas what is your ROM?
randomshots said:
Crisscross: The Photo Contact solution that people have found only alleviates the problem a little, not entirely.
In my trials it has solved my problems completly. I wish for other members who try it out to report back as well to see whether all my trials were just a fluke, or our solution.
Click to expand...
Click to collapse
The downgrade of caller-id to an earlier version has also solved the problem totally for me and several other people, both blue-angel and magician users. Thats why I was curious just what your patch did. Seems that it is something similar, you are maybe downgrading more of the rom?
Did you try downgrading of the caller-id first? Not just photo contacts but downgrade to the specified earlier build of caller-id?
randomshots said:
Once copied over to the device just place it where you can find it using the file explorer. Once located using the file explore simply click on it and it will install on its own. Do a soft reset and enjoy.
Click to expand...
Click to collapse
Hi there,
Just thought I'd report that I've just installed it. My ExtROM now reports as 1.06.150 WWE.
And... so far, so good!!! I've connected/disconnected to GPRS multiple times, interrupted GPRS with a phone call and then reconnected, have sent files to my device via BT while GPRS is on, and still no problem. It's looking very good!!!
And I'd swear it connects faster than it did previously.
Anyway, I'll keep hammering at it over the weekend and report back on Monday.
Thanks again randomshots!
Well, I'm back already, because I still have the problem. DARN IT!!!!!! :x
The thing that made it happen was that I made a phone call while GPRS was on. When I ended the call and tried to reconnect to GPRS, I got the blasted error. So it seems that receiving a phone call does not cause the error to happen, but making a call does. At least for me.
Oh well, it was worth a try. Back to the drawing board.
Same problem in Hong Kong
I upgraded to ROM v1.11 a few days ago and since then I have the GPRS connection error after 1 or 2 connections. Soft reset will solve the problem. This problem was not encountered at all before the ROM upgrade. It must be the new ROM that mess things up!
As this "default cab" from an old rom seems to solve the problem and also an older version of caller-id solves it there is probably something wrong in the communication between caller-id and some of the customisations from this cab on newer roms. Btw the problem is also in 1.12 roms.
Nice too see that we have two possible solutions here, I will stick to the downgrade of caller-id as it has solved the problem totally for me but it would be interesting to know what the real cause is...
Hi again. Just to answer the previous question to my post: my rom version is 1.12.00 WWE, radio 1.12.00, extrom now says 1.06.150. i think the only thing this cab changes is this rom number, nothing else
orcas
orcas,
I believe you are absolutely right. When the extended rom has finished installing the programs, it runs this .cab file to 'brand' the Magician with the build number. Nothing more or nothing less. But faith can move mountains, as we all know...
I guess some of you know that there is another (older) thread about GPRS problems. If you do not, there is a link below.
Anyway, I finally tried the most recent suggested fix in that thread (downgrading the device's CallerID program to an earlier version) and like a number of others I can happily report that so far, it has fixed my GPRS cannot connect problem. Looking good.
Here is the thread:
http://forum.xda-developers.com/viewtopic.php?t=20428
- Peter
Just thought I'd share that the second fix I tried (downgrading CallerID) has continued to work for me. I have no more problems with GPRS. All is well with my Magician. At last.
Related
Hi developers,
first of all I'd like thank you for your excellent work. I used a couple of roms and really appreciate your efforts.
This time I updated my device from WM 2003 (4.00.01 ENG, Radio 4.21.00) to the T-Mobile release whitout radio update, posted in this forum by Aurora13. After a backup of my data and removement of the T-Mob. stuff like suggested by Aurora13, I noticed that my backlight was turned of and I couldn't turn it on again either.
So I tried to downgrade again, because working without backlight really is a pain, by I'm unable to.
Not depending on which ROM I use, I get the message: "error getting device data" (CMD.exe) & "execute remote communication program error" (prog. a 1.09).
My active sync (WinXP) seems to work.
The device & telefone seems to work either.
How can I fix this?? Any suggestions?? I'd really like to go back to 4.00.01!!!!
Thanks in advance!!!
If you restored your applications from a former version of WME 2003 you will see this happen. I don't know what registry setting or file is getting changed but after a restore from say 4.00.01 or 4.00.05 backups (I use SPrite Backup) you will see this phenomenum occur after a soft reboot no backlight. Do a hard reset and resinstall your applications and all will work fine.
error in CMD.exe window after T-Mob 4.00.10 update
Hi developers,
I have similar problem, I’d like to go back to 4.00.005 too.
Using the ROMkitchen_4.00.05.exe, in the CMD.exe window I got an error message:
“error: GetConnectionType – An existing connection was forcibly closed by the remote host.
error getting connection”
My activesync seems to be working properly.
What has gone wrong? How do I fix it?
Thanks in advance
Experienced the same with the backlight.
So NEVER do a restore from a different ROM!!! Alway do a clean install.
error in CMD.exe window after T-Mob 4.00.10 update
Do a hard reset and resinstall your applications and all will work fine.
Click to expand...
Click to collapse
Always do a clean install.
Click to expand...
Click to collapse
So in plain words: how do I do that when this occurs during the flashing-procedure :
“error: GetConnectionType – An existing connection was forcibly closed by the remote host.
error getting connection”
Click to expand...
Click to collapse
It's not only the backlight, the problem is the "execute remote communication program error" which makes flashing the ROM impossible .
I used do update with *.exe-files which won't work out anymore :evil: . Can anybody post a step by step guide how to fix it and go back to the ROM before :? (Which would obviously be the best)?
Or does anybody know which registry key has to be changed to fix the backlight :idea: ?
Thanx!!!
Does it work OK after a hard reset?
Because you shouldn't have to go back, do a hard reset and do a clean install of your apps and 4.00.10 should work ok.
Thanx Aurora13,
it now seems to work !
I'm on 4.00.10 again with all the T-Mob. stuff and backlight working.
In my case, going back to 4.00.01 and restoring my backup seems to be less time consuming than doing a clean install (would loose adress book & calendar).
I actually can't spot a lot of differences besides the version numbers in the OS anyway :? .
:evil: But trying to do that, I still have the same problem with the cmd.exe:
“error: GetConnectionType – An existing connection was forcibly closed by the remote host.
error getting devicedata (cmd.exe)”
Click to expand...
Click to collapse
and
"execute remote communication program error" (prog. a 1.09).
Click to expand...
Click to collapse
:evil:
Seems to me like a serious bug that I can't flash my ROM with the USB-cradle anymore :x .
Anybody any suggestions how to get rid of this OS-version without SD-card-writer?? I'd really like to have evrything working again like it was before!
Thanks a lot in advance!!!
Most importantly: do not upgrade to a T-Mobile ROM 900/1900 MHz (American) ROM on anything but a 900/1900 MHz phone. The T-Mobile ROMS contain the RSU phone upgrade, which will run as soon as WinCE boots. You will ruin your 900/1800 (European/Asian) phone if you do.
Click to expand...
Click to collapse
Could that be the problem that I'm unable to fllash my ROM again?
You will ruin your 900/1800 (European/Asian) phone if you do.
Click to expand...
Click to collapse
What does that mean?
"What does that mean?"
i suspect it means that your xda will only work in US
untill you find some way to flash it back to the 900/1800 gsm mode
which is used in EU and much of the rest of the world [/quote]
untill you find some way to flash it back to the 900/1800 gsm mode which is used in EU and much of the rest of the world
Click to expand...
Click to collapse
Anybody know how to do that when unable to flash ROM due to
Quote:
“error: GetConnectionType – An existing connection was forcibly closed by the remote host.
error getting devicedata (cmd.exe)”
and
Quote:
"execute remote communication program error" (prog. a 1.09).
Click to expand...
Click to collapse
Only via XDArit?????????
if it can be flashed using the sd flash card and you have an sd flash card reader / writer for the pc it would be possible
Similar discussion going on here:
http://www.xda-developers.com/forum/viewtopic.php?t=2134
T-Mobile update 4.00.10 sucks!!!
@reiggue
4.00.10 does not suck.
The problems you are experiencing are not real problems but a lack of knowledge on your side.
If you asked how to solve them I can help you to solve EACH one. But you are not asking, but only being negative.
As with all ROMs if you don't know what you are doing, then don't do it.
If you read this forum more securely, you already got answers of a few of your problems:
- How to go back to an old ROM
- Removing the TMobile stuff
- Backup of previous version does not work
All the answers of the above and how to solve them you can find in this forum.
So use the knowledge of the people of this forum and don't be so negative.
I want to second Aurrora13's statement. Over and over in this forum it is stated that you should not attempt these ROM updates if you don't have an SD reader. Sometimes it is the only way to save your bacon (XDA)! If a user insists on ignoring sound advice, then he shouldn't complain about suffering the consequences.
In general, the more experienced users on this forum provide good advise and are more than willing to ehlp others. Personally, I think this forum is awsome!
We all know we are taking risks but being techno-junkies we jump in there trying to improve our XDA's and learn more about its capabilities and ways to improve it. I hope when the next majore WME phone becomes available (I'm hoping for the TI WANDA, though XDA II will probably be first) that we are able to do the same with it.
4.00.10 user wanted to revert back to old rom
You need to use SD card reader to revert back to older rom, Activesync doesn't work properly in windows, even you had sync with your windows.
I had the same problem before, but I found out this 4.00.10rom is more stable then others WM2003roms.
Please follow Aurora13 instruction,removing a few item under program/AIM -/Tmobile and if you have radio signal problem You might want to try to bootloader setting 900/1800 or 900/1900, it works for me.
This is my second time flashing v4.00.10 and I'm using XDA asian unit.
Good Luck.
:lol:
@Aurora13
You might be right in me being negative.
As I read through the forum, there are other people experiencing the same problems.
I think that people should be warned to use the 4.00.10 version instead of hyping it, because, you might agree on that, you loose the ability to go back to an old ROM via activesync, which is the most convenient procedure so far.
I didn't know that I lose this ability, especiallly after performing 4 successfull ROM-updates so far with ROM from this site. That in fact frustrated me.
I agree that the information provided in this forum should help restoring the old ROM.
To close this message, I'd like to thank everybody in this forum who contributes to help fools like me, obviously not knowing what they're doing! This forum is great and I don't want anybody to get the impression I'm blaming anybody else for my faults.
Thanx!
imho then buying a SD reader is a pretty good idea no matter what
they come in versions which read 6 or 7 different flash types so one can also read ones digi cams card if it's a different type
and they are only about 50$ or EUro or something like that
i'm sure getting 2->3 flash readers one of these days
@reiggue
Yep this forum rules big time.
If you check the Sticky thread:
http://xda-developers.com/forum/viewtopic.php?t=1624
There is already enough warnings for the 'beginner', that's why I didn't warn it can be dangerous.
But enough said, good luck with your downgrade and/or if you will stay with the 4.00.10 ROM I'll be glad to help solving some problems you may experience or talk you through the downgrade.
I appreciate your assistance, Aurora13!
Thanx! :lol:
For those of you in the UK - I bought an SD card reader (only reads SD and MMC cards) from PC World for only £6.99 - I've used it to change ROMS back and fourth several times on four XDA's without incident so far - I bought it after an activesync update (genuine O2 upgrade) went horribly wrong and trashed my XDA. I think that everyone "playing" with these ROMs should get one.
Hi everyone,
Thanks for all of the good work happening her in these forums. It’s really amazing how much information is here. I have the following situation and wonder if anyone can help me sort it out.
I have a running qtek with an un-working radio. I have the developers SE ROM 1.2 installed and it’s running but very slow. The system can’t detect the battery and its charge. The radio is off and will not turn on. I tried to install the O2 4.21 radio update using the SD card using the repair file downloaded from your site but no luck. It stops after it reboots and start the upgrade process with the dreadful 1% can’t flash error. From what I read so far the problem hover around the radio not being able to detect the battery power so it stops the flashing process. I tried changing the upgrade file and to do it many times but still always stops at 1%.
One way I didn’t try is copying the upgrade file to the windows root directory and tries to upgrade from there instead from the card. I don’t know where to find the 2 monitors files needed to be installed there before the upgrade. Anyone knows where to get them from?
Is there any other way to flash the radio using the SD card method (I am traveling and don’t have the cradle with me.)
Thanks again.
Have you tried fixing it with the following?
http://xda-developers.com/repair.zip
Hope it helps.
I have exactly the same problem as ahmedateeq. Runnung the repair.zip files as suggested by beeheij just results in Radio Stack Upgrade failure at 1% every time the XDA soft resets (the only way to break this loop is a hard reset). I have tried two different RSU upgrade versions, but to no avail.
What else can be done?
Geoff :?
gwhitea said:
I have exactly the same problem as ahmedateeq. Runnung the repair.zip files as suggested by beeheij just results in Radio Stack Upgrade failure at 1% every time the XDA soft resets (the only way to break this loop is a hard reset). I have tried two different RSU upgrade versions, but to no avail.
What else can be done?
Geoff :?
Click to expand...
Click to collapse
Did you try to turn on your GSM using the bootloader, by Holding power button then Soft reset the unit, then if you see the logo "Bootloader 5.15" press the calendar button, then you will see the GSM menu, try to select GSM ON then press the action button( the middle of navigation key), when it go back to the menu then soft reset again, then check if it is working or not..Please telme the version of your unit RSU and RUU... thank i hope this will help you.
:?
Did what you said - I was able to turn on GSM in Bootloader (though there was no message to confirm) - but this hasn't improved the situation. I still get the upgrade failure at 1%.
My RUU is SER1.2 (based on O2 3.17.03. RSU is (WAS!) O2 4.21
Any more ideas? Is it worth trying to copy the upgrade files to the Windows folder on teh XDA and running it from there?
Thanks for your help.
Geoff
I tried switching the radio on as suggested, but it failes.
Can we try the windows root directory install method. I need to know where to get the 2 monitors files to be installed with the rsupgrade file. Any one know where to get them.
Any other suggestions (Gurus help needed here)
RUU is SER1.2, O2 3.17.03, RSU O2 4.21
ahmedateeq said:
I tried switching the radio on as suggested, but it failes.
Can we try the windows root directory install method. I need to know where to get the 2 monitors files to be installed with the rsupgrade file. Any one know where to get them.
Click to expand...
Click to collapse
Ok here you go!
http://www.o2.co.uk/personal/xda/docs/Radio_Stack_Upgrade_v421.zip
Thanks Qman,
I have this file already and its installed, but I dont see the 2 monitor files in the programme b directory. Are they included in the rsupgrade cap file and if yes which one is which?
Thanks again and still waiting for some creative thinking how to solve this delmma that hit so many members.
ahmedateeq said:
Thanks Qman,
I have this file already and its installed, but I dont see the 2 monitor files in the programme b directory. Are they included in the rsupgrade cap file and if yes which one is which?
Thanks again and still waiting for some creative thinking how to solve this delmma that hit so many members.
Click to expand...
Click to collapse
Yeap they're included in the RSUpgrade.sa.CAB!
What I would do is copy the RSUpgrade.sa.CAB to my device and run it from there and if the upgrade fails do a search for the needed files and relocate them manually.
HTH
Hello all.
i have been searching the forum for the solution of this problem, some guys suggested solutions that involve a file that is no longer available, upgrade.zip which is aparently a radio upgrade(or downgrade) made for the SD card (a startup.exe in a startup directory).
Well, having said that, i had to solve this problem last night, and here it goes.
after trying original ROM upgrades, all versions, 3.14,3.17,3.18~4.
nothing worked.
finally, i grabbed a copy of xda-developers's 1.1 ROM
and guess what!!!
the phone started up, gave me the screen allignment and the whole menu!
sure enough, ran file commander(that version did not have file manager) copied the RSU files over to the windows directory, and the exe file to the windows\startup and rebooted the phone.
it stopped at 1% again... NOW REMEMBER, i had an EMPTY BATTERY...
the 1% ERROR is a battery issue, that turnes into this issue when the modem upgrade FAILS.
so here is what i did. and you be the judge.
i ran active sync from the phone, and it did connect(while the upgrade program is still running) and left the room/
in 10 minutes i came back and the upgrade was completed, so here is what i think
i think that the RSU will still run if it was in the background!!! even with an empty battery(connected to the charger ofcourse.
i did not have much time to do anymore testing, but i am sure that someone with the same problem will make the time. the key from my experience is that the proccess will complete if it is in the background.
there u have it.
good luck.
i forgot to add that the upgrade i used was taken from yorch's page and it was the latest Tmobile, i had to downgrade later to an older version that i have to solve the network issue, but it was done(the downgrade) like a charm, i had a full battery then.
here is the Tmobile RSU link v6.24
http://www.yorch.net/downloads/ROMS/TMOradiostackupgradeR624 .zip
a 1.26 MB file.
Hi!
Now I'm taking a try (unfortantely I've found only the special edition rom 1.2).
No success with SE ROM 1.2. Where could I download 1.1 from? Found it nowhere.
One more thing: maybe the version of active sync counts? Mine was 3.8.
plg said:
No success with SE ROM 1.2. Where could I download 1.1 from? Found it nowhere.
Click to expand...
Click to collapse
http://lumpistefan.dyndns.org/tools/special_rom_1.1.exe.zip
HTH
Stefan
LumpiStefan said:
plg said:
No success with SE ROM 1.2. Where could I download 1.1 from? Found it nowhere.
Click to expand...
Click to collapse
http://lumpistefan.dyndns.org/tools/special_rom_1.1.exe.zip
HTH
Stefan
Click to expand...
Click to collapse
Thanks, Stefan! Maybe this one will help...
Hello to all, and mr stefan,
I upgrade my qtek 1010 with SFX56 windws 2003, it also upgraded my RSU, which is not working in Middle East. Kindly advise me how to downgrade or upgrade with other RSU. Thanks
your problem is in the network selection, search the forum for the proggy that changes it from 1900 to 900 and you should be OK.
i hate telling anyone to search i know how hard it is, but i do not have a clue where the proggy is, meanwhile, if i run across it, i will point it out,
if not, go to the bootloader, select GSM and change it from there, you will loose all data so backup first,
Good Luck.
search for "bandwith switch tool"..... good luck.
here it is on wiki
http://wiki.xda-developers.com/index.php?pagename=BandSwitchTool
tell us if this fixes your problem.
if not, you will find links to radio upgrade on
[/url]http://lumpistefan.dyndns.org/tools/ thanks to LumpiStefan
for a great resource.
good luck.
never knew you can post as guest
well, again, let us know what happens.
hi all
I just picked up a XDA from a guy who screwed up the radio stack upgrade (it cosy me @$80 USD ) and im now on a mission to fix it...
using your advice I used the XDA developers rom 1.1, this got the phone to start up with the working today screen and menus etc....
I install/copy over the new RSU upgrade files over and reboot
but here is where i get a bit stuck...
I cant get into active sync fast enough before I get the 1% RSU upgrade error, so the upgrade wont run in the background, it just sits there....
how do you get into active sync before the error comes up?
cheers
MADMAX
Device: Qtek 9000 - straight from Dangaard with no operator personalisation.
Started out with the USB connection problem. Solved that according to descriptions in previous threads.
Flashing stopped due to it not being an O2 device.
Extracted files from the Xda_Exec_Upgrade_v113188.exe.
Tried to download /Uploads/Universal/MaUpgradeUt_noID.exe, but exactly that file could not be downloaded (I can download the other files - ????). Found another file called MaUpgradeUt_noID.exe linked from this forum. It is from 16/3-2005 and illustrates an S100.
Flashing seems to go OK. PC and Qtek says 100% complete after the 3 stages.
Hard reset gives the option of 0 for Factory reset or X for reset
Hard reset results (either 0 or X) in dark screen saying "Serial", "v1.00" (Bootloader?). I have now flashed 4 times with the same results :x
Can the cause of my problems be the "MaUpgradeUt_noID.exe" from March? If so, can someone give a working link for the right version of the file - please :wink:
If not - please help - I am in deep troubles
Best Regards
Steen
You have to upgrade the Radio ROM separately. Look for posts in here or Universal Upgrading for "unbricking your Universal" or something to that effect.
I have been looking and searching, but I’m unable to sort out of the abundance of information what should be done in my situation.
The installation information is blank for all the 3 groups displayed under “From version”, so I guess the device is totally blank – under these circumstances I can’t see why the radio Radio ROM should be updated separately.
Steen
IT'S ALIVE :lol:
Installed the seperate Radio ROM on top of the previous installations. It has now booted and I'm setting it up.
Thank's for the advice BeyondtheTech
... it was worth alot, all though I in my panic could not se the light at the end of the tunnel
Steen
I upgraded my Blueangel to windows mobile 6 a couple of days ago, yesterday i was reset it. when it powered on i have the windows mobile 6 screen and nothings happens thereafter, it is not connection to activesync and i m not able to ROM Upgrade.
Please help me ASAP
read the wiki carefully
try a hard reset after and do the no+yes+yes ritual in the hard reset.. it should worked...
regards
adri
baybe it is because third party software you installed, it happened to me with the touchflo which replaced the touch.dll with another one for another device, also with HTC Plus today plugin
I had it after installing VBAR... you have to reset it and press the record and camera button, then clear the registry HIVE and press the mail button... it will be hard resetted but in wm6 you don't lose any data, just some settings and cabs...
Yeah, I got this problem too a few days ago.. annoying...
When I tried to back up my data using Sunnysoft backup manager, BA had to restart, and then it stuck in the WM6 page... ended up clearing the whole thing again using the no yes yes option...BA was able to start up on safe mode though... weird
I only had this problem once though....
Hmmm, interesting few people have this problems with different circumstances, however leading to the same problem...
is it really WM6 issue or is it 3rd party apps issue?
joseph.sapri said:
is it really WM6 issue or is it 3rd party apps issue?
Click to expand...
Click to collapse
good question!
it just happened to me as well.... i had an almost fresh install of WM2006 (just downgraded, merged Extrom and upgraded again).
I installed some few cabs and eventhough it worked fine for a day, it then started to freeze while booting again and again....
i never had the problem before merging the rom though...
it happened to me also, after doing a soft reset using pbar. it ends up in the green screen with the microsoft logo without going any further. i've tried several soft resets after but it always ends up in that mode.
had to perform a hard reset and install my favorite apps again.
well maybe there are some incompatiblityes with those programs you mentioned, i have not use them my BA has the default apps (the posted cabs) Sprite Backup 6, Htc Home 1.5, Adobe Flash Lite and i have no problems at all
xplode said:
well maybe there are some incompatiblityes with those programs you mentioned, i have not use them my BA has the default apps (the posted cabs) Sprite Backup 6, Htc Home 1.5, Adobe Flash Lite and i have no problems at all
Click to expand...
Click to collapse
have you installed all cabs you posted (cabs & cabs2)?
in what order?
whats Sprite Backup?
and which one is the HTC Home 1.5? (i only see HTC Home6?!?)
sorry, but i am really getting more and more confused...
regards,krz
Sprite backup is the best backup softweare IMO, yes all cabs (cabs and cabs2) Home6 is HTC Home 1.5
thank you very much for your answer, xplode!
there are three HTC HOME6 cabs out there:
1) Helmi HomePlug_Comp.cab: found in Helmi_C's WM2006 archive FLASH.zip
2) Helmi_HtcHome6_WM5_comp_sdkcert.cab: found in Helmi_C's WM2006 archive AddOn.rar
3) HOME6: an archive with two folders (WM5 + WM6) and HTCHome.cab
are there any differences?
is one better than the others?
i never found an answer to these questions...
regards,
krz
KRZTF said:
thank you very much for your answer, xplode!
there are three HTC HOME6 cabs out there:
1) Helmi HomePlug_Comp.cab: found in Helmi_C's WM2006 archive FLASH.zip
2) Helmi_HtcHome6_WM5_comp_sdkcert.cab: found in Helmi_C's WM2006 archive AddOn.rar
3) HOME6: an archive with two folders (WM5 + WM6) and HTCHome.cab
are there any differences?
is one better than the others?
i never found an answer to these questions...
regards,
krz
Click to expand...
Click to collapse
Use Home6 if you want to be able to modify the HTC Home tabs from 6 (default) to less than 6..... this is the only one working....
With Helmi_HTCHome6.. it also works, but cannot modify the tabs......
never tried the other one....
OK OK I had this problem and it solved it without losing data. First i tried to reset the device , like 30 times with no success. Even with a hard reset it didnt work. So you just Put ur device in the booloader mode and then soft reset it and voila. i dont know if it's really the correct solution but it worked for me for 3 times when i had that dumb WM6 screen. It's because of Battery status software ( 100% sure )
BA Freezing
xplode said:
baybe it is because third party software you installed, it happened to me with the touchflo which replaced the touch.dll with another one for another device, also with HTC Plus today plugin
Click to expand...
Click to collapse
Can anyone tell us which third parties programs that cause the freezing or which are compatible whit WM6. To used or avoid them.
Hi,
same problem here. I just installed the cabs from helmi (Thanks again!), the HTC Home (Helmi_HtcHome6_WM5_comp_sdkcert.cab), Acrobat reader and powerpoint (out of this cabs in the first message in the central BA6 Thread) and no additional software. I've re-installed it two times, but that doesn't help .
@ Xeon: Maybe a good work-around, I will give him a try,
UPDATE: @ XEON: Doesn't work for me
regards
Andreas
OK im again facing the same problem it seems my solution didnt work. As far as it seems to, i had to soft/hard reset more than 20 times to solve it. i dont get it. when i reset it the problem is still bla bla bla.. but when u leave it stuck for 10 mins and then reset it , it will work. the point is that after all , u dont need to format/clear registry. All u need is to keep trying. WEIRD [email protected]#[email protected]$#$
I keep having the problem after installing a new cab with a soft reset. The only way to get out of the WM6 screen is to go into bootloader and a soft reset. Just like Xeon said. However, I don't think it is the battery issue because if I just do a normal soft reset, it starts up fine. The problem arrives only when a soft reset is required to finish an installation from cab.