Faria 3.2 Htc Wizard Rom Real Issues-report Here - 8125, K-JAM, P4300, MDA Vario Software Upgrading

DUE to the first thread been turned into another unlocking one I had no choice but, to close the project.
But I feel that it is unfair to the people that respect my work an appreciate it.
The response to the rom has been overwhelming!!!! I never see this kind of response to a rom since the blue angel days
once again this thread been trashed with crap.rom is no longer available.next realease is pending.got better things to do with my time.plus time job is takeing most of mine time now and with x-mas coming,gonna get worst. when im ready i will contact the testers.no more tester are neede at the moment.
if you experience power-ups with push email folow.this;
now for users that have the device powering up when push email activated,i have been doing some testing;
i setup my push email [web2mail]
now i have setup the device security with a password,so when it comes from stand-by,will ask for it,
then a setup devicee lock in batterie status to also lock the device [see pictures]
what can i say i works fine.
when i receive an email from my server ,it notefys-me with the email sound ,but the device does not power up as reported.
now when the device lock time out is up,the device wakes up to lock itself
and the powers down in 1-2 seconds -this is normal in this rom atleast.
how to the date in the top right corner ?
use registry wizard[included in the rom] to remove the date or time
to use default clic sound download the file below
remove the .zip from the file name as it's just a cab...thanks dr.p
whats is in my rom?

unlcoking problem
people don't get it and it is really easy to unlock CID if they really follow the threads that there are. This thread says it clearly what u do and it is really easy to do it. Most of the people have update tool problem they can solve that with wizard_ROM update utility_noID file on the FTP site of the XDA. They can just put it to the unpcaked faria RC1 file and run it after unlocking CID. Two steps simple and cristle clear !!
http://forum.xda-developers.com/showthread.php?t=263116&highlight=CID+UNLOCK

/APPLAUDE
Just wanted to thank you for everything so far. Loving the ROM and will continue to provide Beta feedback as much as possible.

hey faria, awsome job i wish i had half your skills. your latest rom has been exeptional, the only issue i had was when i overclocked it the screen would intemitently turn on, oh and the battery meter never went below 57%. any help or sugestions would me much appreciated.

bigdooky said:
hey faria, awsome job i wish i had half your skills. your latest rom has been exeptional, the only issue i had was when i overclocked it the screen would intemitently turn on, oh and the battery meter never went below 57%. any help or sugestions would me much appreciated.
Click to expand...
Click to collapse
how much did you overclocked?

LOL!!!
faria said:
You my requested the rom from me but I will select you according to your posts.
Click to expand...
Click to collapse
LOL! So you will select us according to whether or not we have something intelligent to say. Well, I am about to put your 8mb rom on my MDA (right now using the RISIDRO rom loaded on top of the t-mobile official 2.26 rom) and will let you know what I think. I will be sure to say something smart. I will just blow you away with my intelligence and technical prowess.
I would like to see some articles on the page-pool size thing though. That's a new one to me. Check my post in the original thread (#419). Anyone wanna point me in the right direction? I can only find how-to's and not any reasons as to why one would do this...
So uh ... how do I unlock my phone? I did not get any keys. Are they on the stylus somewhere? I gotta go download a computer.

Portuguese Support
I faria since i`m new in this all new stuff of cooked rooms and extended roms etc; all that i can do is asking how can i help you on your journey, just tell me how i can donate you something for you to continue the great job that i have the oportunity to see in this forum i will be pleased to help with anythig to honor your Portuguese contribute to the XDA, continua o bom trabalho e ficarei a aguardar pelo "lançamento" da tua nova room EXCELENTE TRABALHO.

well I told you I would let you all know if there was a difference that I noticed between the 8mb and 12 mb with the voicemail issues and in-call issues.
with the 12, sometimes in a call, buttons would become usless and had to soft reset to hang up. same thing with the 8.
with the 12, voicemail icon would not go away after voice mail deleted. havnt seen that with the 8 yet.
other than that, speed is good in both, and everything works like a charm.
Jeb

I hope your donations will provide you with at least the ability to take a night off and go to dinner or maybe get a massage to help you forget the newbie questions. I will be sending a donation as well. You have provided an outstanding ROM that has rivaled (and beaten) multi-m(b)illion dollar companies core and "upgrade" roms.
To all those that wish to ask newbie questions, leave faria's threads dedicated to the enhancement and ultimate release of one of the best ROMS for a PPC phone alone.
The least you could do is create your own thread and post your questions there.
I hope I may be considered for future testing granted my moderately new questions have not been classified as non rom related. If so, I will go study some more and apply to faria U at a later time

G4s and the ROMs
Faria, I think I am onto something here. From what I am reading in the posts, and from what you and I discussed the other day about my extended rom not loading correctly, I think and G4 with IPL/SPL ABOVE 2.17.0001 have a greater degree of security. Again, reading the posts in your other thread, it seems a handful of G4 owners could indeed install your rom fully, while the other half would only get the OS. Correct me if I am wrong, but I am starting to see a pattern.

First and foremost I would like to thank Jose for all the time and effort that he put into making this great rom. If and when you come to NYC I am taking you out and getting you twisted VIP style! But enough ass kissing and lets get to bussiness.
I have had very minor issues.
The mms did not work for me with the settings that I had from tmobile USA. I did get them to work when I got some of the settings cabs from the 2.26 custom extended rom. I did run the auto config that was included to set the network settings.
After installing all the software extras that was included to check how they worked, I have not been able to keep the phone off. When I say off I mean the backlight staying off when nothing is running. I have tried using the XP feature to turn the light off but it doesnt keep it off either. This could be something that I did so I may just reflash and install everything one by one to see where the problem comes from.
I also have noticed some signal problems but I think that was more of me installing those cabs from the 2.26 rom
Any help is appreciated.

one issue i have noticed is right before the device wakes up it white screens for 2-3 seconds then loads the today screen.. i dont know if this is a issue as i have not seen it really affect anything but i figured id let u know.

peraltah said:
The mms did not work for me with the settings that I had from tmobile USA. I did get them to work when I got some of the settings cabs from the 2.26 custom extended rom. I did run the auto config that was included to set the network settings.
Any help is appreciated.
Click to expand...
Click to collapse
i also experienced this problem with MMS settings, what i did was delete the settings faria provided and ran a cab file once, soft reset then ran the cab file again and now my settings are there.

Quote:
Originally Posted by dreamteam3x
Dear Faria and users,
Thank you Faria very much for your work on the new ROM, we all
highly appreciate that.I'm really confused about the
result on my Cingular 8125 after it's upgraded to your new ROM,
i mean your AKU 3.2 RC1.
Let me tell you the whole process that i followed to have a
better understanding:
1. ROM before upgrading:
-IPL 2.25
-SPL 2.25
-Radio 02.47...
-OS 2.26 (Shogun_A_La_Card's ROM)
2.What i see after upgrading to your new ROM:
-IPL 2.25
-SPL 2.25
-Radio 02.25.11
-OS 2.26.10.2
3.The proplem that i encountered:
when ROM upgrade finished, the device automatically
restarted and asked me if i wanna run the autorun files
(the installation of Ext_ROM, i know that) and i certainly choosed Yes.
The installation process went smoothly to its nearly end then a
error dialog box poped up with :"/Windows/autoconfig.exe doesnt exist"
,the only thing i could do is to choose "ok".The device restarted and
what i find after that is a new OS 2.26.10.2 without the EXt_ROM.
I downloaded both 8MB and 12MB pool versions but it gives me
the same result for both.
Please help me me on :
1.How to correct those problems.
2.How to upgrade my SPL and IPL to the newest versions?I stay the same(2.25) even when i upgraded the device to 2.26.
Thank you very much for any help.
Was your phone CID unlocked prior to the install? It seems that you have a G3 so the other thread on unlocking should have been done first. (You may have done this prior to another ROM but I am to tired to think about that...) Good luck!
--M
=============
Urgent helps needed!
So i bricked my Cingular 8125!
I just wanted to upgrade my ROM to the newest AKU 3.2 from Faria.
I did ungrade and errors arised as i described above.
I was told that the fone hadn't been CID unlocked.
I did as what described in lowikiz
-downgrade the rom,
-run enablerapi.cab on my device
-run lowikiz 0.2b
-choose CID unlock
Restarted the fone, what i saw was:
IPL 1.01
SPL 2.25
GSM 2.47.11
OS 3.0.0
There're only two things fulfill me,that's GSM and the OS.I wanted the
IPL and SPL should be 2.26 or later version.
What i did then :
-Downgrade again (hoping that i forgot to SIM unlock)
-run enablerapi on my device
-run lowikiz 0.2b
-choose unlock
And when the fone restart.
What i saw was:
IPL 1.01
SPL 1.01
GSM 1.x.x
OS 1.05.x
when the installation completed, i upgraded the ROM again to AKU3.2
everything went smoothly until it finished.The fone restarted and what i saw was:
IPL 1.01
SPL 1.01
<blank, no GSM version, couldnt believe that>
OS 3.0.0.0
the device kept running until the installation completed.
It restarted again and stopped running.What i can see now is just
nice background and blinking (waited for nearly 15 mins but no futher responses)
IPL 1.01
SPL 1.01
OS 3.0.0.0
It couldn't get further.
I think i bricked my Cingular 8125.
So could you helpers, experienced users help me with that?
Can i fix it?Or can HTC fix it?
Thank you very much!

Hello faria. I said eariler that this was a great rom. I think i have found a minor annoyance, i wouldn't call it a bug. It is related to spb time at least I'm pretty sure it is. I get the calnot.exe error every now and again and the cannot locate the spbtime.exe on reset. Its strange everything still works as it should. I think someone else had this problem in the other thread. I thought is was because spb time was loaded on the mem card and the fact that windows is sometimes late in loading it. So my next step was to move it to the sys mem. Same problem, I guessing it is on spb to fix this. I was probably not designed to work well with aku 3.2. Other than I that i could not find any real problems, except one time i uninstalled spb time and i oculd no longer sync. easliy fixed by hard reset no prob. I'm using 12mb pool. I also used your registry tweak program and set all the cache to the highest settings. Do you think that is a bad idea for this pool size. Have noticed some slow down in performance i don't know if the two are related.
thanks for the great rom again man!!
appreciated

jacob-mda said:
i also experienced this problem with MMS settings, what i did was delete the settings faria provided and ran a cab file once, soft reset then ran the cab file again and now my settings are there.
Click to expand...
Click to collapse
I didnt delte it I just ran the other cabs from 2.26 and soft rest it. I think thats where my signal problem came from. I have to reboot to get my signal back.

monadzback said:
well I told you I would let you all know if there was a difference that I noticed between the 8mb and 12 mb with the voicemail issues and in-call issues.
with the 12, sometimes in a call, buttons would become usless and had to soft reset to hang up. same thing with the 8.
with the 12, voicemail icon would not go away after voice mail deleted. havnt seen that with the 8 yet.
other than that, speed is good in both, and everything works like a charm.
Jeb
Click to expand...
Click to collapse
i see a patern emeging here the voice mail/phone buttons seems to be an american thing.now i tryng to find out if its a carrier specific thing.
cptcafne
Faria, I think I am onto something here. From what I am reading in the posts, and from what you and I discussed the other day about my extended rom not loading correctly, I think and G4 with IPL/SPL ABOVE 2.17.0001 have a greater degree of security. Again, reading the posts in your other thread, it seems a handful of G4 owners could indeed install your rom fully, while the other half would only get the OS. Correct me if I am wrong, but I am starting to see a pattern.
Click to expand...
Click to collapse
please contact-me privite go somethig for you .
Timbo_fdw
Hello faria. I said eariler that this was a great rom. I think i have found a minor annoyance, i wouldn't call it a bug. It is related to spb time at least I'm pretty sure it is. I get the calnot.exe error every now and again and the cannot locate the spbtime.exe on reset. Its strange everything still works as it should. I think someone else had this problem in the other thread. I thought is was because spb time was loaded on the mem card and the fact that windows is sometimes late in loading it. So my next step was to move it to the sys mem. Same problem, I guessing it is on spb to fix this. I was probably not designed to work well with aku 3.2. Other than I that i could not find any real problems, except one time i uninstalled spb time and i oculd no longer sync. easliy fixed by hard reset no prob. I'm using 12mb pool. I also used your registry tweak program and set all the cache to the highest settings. Do you think that is a bad idea for this pool size. Have noticed some slow down in performance i don't know if the two are related.
thanks for the great rom again man!!
Click to expand...
Click to collapse
that app has problems in 3.2 roms.
Originally Posted by peraltah
The mms did not work for me with the settings that I had from tmobile USA. I did get them to work when I got some of the settings cabs from the 2.26 custom extended rom. I did run the auto config that was included to set the network settings.
Any help is appreciated.
i also experienced this problem with MMS settings, what i did was delete the settings faria provided and ran a cab file once, soft reset then ran the cab file again and now my settings are there.
Click to expand...
Click to collapse
please provide the rigth cab files for the next update.

dreamteam3x said:
Quote:
Originally Posted by dreamteam3x
Dear Faria and users,
Thank you Faria very much for your work on the new ROM, we all
highly appreciate that.I'm really confused about the
result on my Cingular 8125 after it's upgraded to your new ROM,
i mean your AKU 3.2 RC1.
Let me tell you the whole process that i followed to have a
better understanding:
1. ROM before upgrading:
-IPL 2.25
-SPL 2.25
-Radio 02.47...
-OS 2.26 (Shogun_A_La_Card's ROM)
2.What i see after upgrading to your new ROM:
-IPL 2.25
-SPL 2.25
-Radio 02.25.11
-OS 2.26.10.2
3.The proplem that i encountered:
when ROM upgrade finished, the device automatically
restarted and asked me if i wanna run the autorun files
(the installation of Ext_ROM, i know that) and i certainly choosed Yes.
The installation process went smoothly to its nearly end then a
error dialog box poped up with :"/Windows/autoconfig.exe doesnt exist"
,the only thing i could do is to choose "ok".The device restarted and
what i find after that is a new OS 2.26.10.2 without the EXt_ROM.
I downloaded both 8MB and 12MB pool versions but it gives me
the same result for both.
Please help me me on :
1.How to correct those problems.
2.How to upgrade my SPL and IPL to the newest versions?I stay the same(2.25) even when i upgraded the device to 2.26.
Thank you very much for any help.
Was your phone CID unlocked prior to the install? It seems that you have a G3 so the other thread on unlocking should have been done first. (You may have done this prior to another ROM but I am to tired to think about that...) Good luck!
--M
=============
Urgent helps needed!
So i bricked my Cingular 8125!
I just wanted to upgrade my ROM to the newest AKU 3.2 from Faria.
I did ungrade and errors arised as i described above.
I was told that the fone hadn't been CID unlocked.
I did as what described in lowikiz
-downgrade the rom,
-run enablerapi.cab on my device
-run lowikiz 0.2b
-choose CID unlock
Restarted the fone, what i saw was:
IPL 1.01
SPL 2.25
GSM 2.47.11
OS 3.0.0
There're only two things fulfill me,that's GSM and the OS.I wanted the
IPL and SPL should be 2.26 or later version.
What i did then :
-Downgrade again (hoping that i forgot to SIM unlock)
-run enablerapi on my device
-run lowikiz 0.2b
-choose unlock
And when the fone restart.
What i saw was:
IPL 1.01
SPL 1.01
GSM 1.x.x
OS 1.05.x
when the installation completed, i upgraded the ROM again to AKU3.2
everything went smoothly until it finished.The fone restarted and what i saw was:
IPL 1.01
SPL 1.01
<blank, no GSM version, couldnt believe that>
OS 3.0.0.0
the device kept running until the installation completed.
It restarted again and stopped running.What i can see now is just
nice background and blinking (waited for nearly 15 mins but no futher responses)
IPL 1.01
SPL 1.01
OS 3.0.0.0
It couldn't get further.
I think i bricked my Cingular 8125.
So could you helpers, experienced users help me with that?
Can i fix it?Or can HTC fix it?
Thank you very much!
Click to expand...
Click to collapse
im afraid you phone still locked
now put it int bootloader mode and run the latest rom from your provider.

dreamteam3x said:
Quote:
Originally Posted by dreamteam3x
Dear Faria and users,
Thank you Faria very much for your work on the new ROM, we all
highly appreciate that.I'm really confused about the
result on my Cingular 8125 after it's upgraded to your new ROM,
i mean your AKU 3.2 RC1.
Let me tell you the whole process that i followed to have a
better understanding:
1. ROM before upgrading:
-IPL 2.25
-SPL 2.25
-Radio 02.47...
-OS 2.26 (Shogun_A_La_Card's ROM)
2.What i see after upgrading to your new ROM:
-IPL 2.25
-SPL 2.25
-Radio 02.25.11
-OS 2.26.10.2
3.The proplem that i encountered:
when ROM upgrade finished, the device automatically
restarted and asked me if i wanna run the autorun files
(the installation of Ext_ROM, i know that) and i certainly choosed Yes.
The installation process went smoothly to its nearly end then a
error dialog box poped up with :"/Windows/autoconfig.exe doesnt exist"
,the only thing i could do is to choose "ok".The device restarted and
what i find after that is a new OS 2.26.10.2 without the EXt_ROM.
I downloaded both 8MB and 12MB pool versions but it gives me
the same result for both.
Please help me me on :
1.How to correct those problems.
2.How to upgrade my SPL and IPL to the newest versions?I stay the same(2.25) even when i upgraded the device to 2.26.
Thank you very much for any help.
Was your phone CID unlocked prior to the install? It seems that you have a G3 so the other thread on unlocking should have been done first. (You may have done this prior to another ROM but I am to tired to think about that...) Good luck!
--M
=============
Urgent helps needed!
So i bricked my Cingular 8125!
I just wanted to upgrade my ROM to the newest AKU 3.2 from Faria.
I did ungrade and errors arised as i described above.
I was told that the fone hadn't been CID unlocked.
I did as what described in lowikiz
-downgrade the rom,
-run enablerapi.cab on my device
-run lowikiz 0.2b
-choose CID unlock
Restarted the fone, what i saw was:
IPL 1.01
SPL 2.25
GSM 2.47.11
OS 3.0.0
There're only two things fulfill me,that's GSM and the OS.I wanted the
IPL and SPL should be 2.26 or later version.
What i did then :
-Downgrade again (hoping that i forgot to SIM unlock)
-run enablerapi on my device
-run lowikiz 0.2b
-choose unlock
And when the fone restart.
What i saw was:
IPL 1.01
SPL 1.01
GSM 1.x.x
OS 1.05.x
when the installation completed, i upgraded the ROM again to AKU3.2
everything went smoothly until it finished.The fone restarted and what i saw was:
IPL 1.01
SPL 1.01
<blank, no GSM version, couldnt believe that>
OS 3.0.0.0
the device kept running until the installation completed.
It restarted again and stopped running.What i can see now is just
nice background and blinking (waited for nearly 15 mins but no futher responses)
IPL 1.01
SPL 1.01
OS 3.0.0.0
It couldn't get further.
I think i bricked my Cingular 8125.
So could you helpers, experienced users help me with that?
Can i fix it?Or can HTC fix it?
Thank you very much!
Click to expand...
Click to collapse
when u downgrade then upgrade with a 2.26 ROM (IPL , SPL) like moliskis and then upgrade to farias and it will show u
IPL=2.26
SPL=2.26
OS=3.000

jacob-mda said:
one issue i have noticed is right before the device wakes up it white screens for 2-3 seconds then loads the today screen.. i dont know if this is a issue as i have not seen it really affect anything but i figured id let u know.
Click to expand...
Click to collapse
there is a fix for that in page 7-8 in the old thread
LOL! So you will select us according to whether or not we have something intelligent to say. Well, I am about to put your 8mb rom on my MDA (right now using the RISIDRO rom loaded on top of the t-mobile official 2.26 rom) and will let you know what I think. I will be sure to say something smart. I will just blow you away with my intelligence and technical prowess.
I would like to see some articles on the page-pool size thing though. That's a new one to me. Check my post in the original thread (#419). Anyone wanna point me in the right direction? I can only find how-to's and not any reasons as to why one would do this...
So uh ... how do I unlock my phone? I did not get any keys. Are they on the stylus somewhere? I gotta go download a computer.
Last edited by appye : Today at 10:45 PM. Reason: I am cool like that.
Click to expand...
Click to collapse
nice try.but no dice

Related

Problems with WiFi (QTEK 9100)

Hi,
Ever since upgrading to 2.17 (official QTEK version) I can no longer get a stable WiFi connection - I get poor signal displayed even though I am next to the AP and it can take anything from 5 to 20 attempts to get connected.
The 9100 came with 1.6.7 installed which not perfect more or less connected first time, but I hoped the later ROMs would fix some other stability problems.
I have tried AKU 2.3 and I still get the same issues (plus I miss the battery indicator in the top bar).
Also, I cannot get back to 1.6.7 (I managed to get the OS back to it but the other 2 were stuck at 2.4) as every time I try I get vendor ID is wrong.
Any ideas?
Cheers,
Taomyn
I have the same problem, but even worse. I see the network after connecting it says it is connected but I cannot browse or do anything on the "socalled Internet" DHCP says that it found an adress in my case at home 192.168.1.33.
I am not sure if an upgrade would help.
My wifi version is 01.04.10
I am looking for any idea too.
Just an update, though the problem remains.
I have downgraded the OS to 2.17 as it seems better than the later ones posted and is at least a QTEK one.
Still hit and miss with the WiFi
Does anyone know if there are any later QTEK ROMS available?
search this forum to find a solution to downgrade the rom version to 1.x then do CID unlock using aWizard.
or you should try upgrade to cingular 2.25WWE rom to see if there is any improvement.
huangyz said:
search this forum to find a solution to downgrade the rom version to 1.x then do CID unlock using aWizard.
or you should try upgrade to cingular 2.25WWE rom to see if there is any improvement.
Click to expand...
Click to collapse
I did try various of the downgrade tips but none seemed to work even though I've got a G3, so hopefully the LokiWiz will be updated soon to work on v2 ROMS.
The Cingular 2.25 ROM didn't work very well either and I hated the extra rubbish it comes with. The radio ROM I happen to be using was from that same one.
I suppose I could go for the 2.25 OS but not the Extension - would that leave behind the Cingular crap?
Taomyn said:
I did try various of the downgrade tips but none seemed to work even though I've got a G3, so hopefully the LokiWiz will be updated soon to work on v2 ROMS.
The Cingular 2.25 ROM didn't work very well either and I hated the extra rubbish it comes with. The radio ROM I happen to be using was from that same one.
I suppose I could go for the 2.25 OS but not the Extension - would that leave behind the Cingular crap?
Click to expand...
Click to collapse
I now run 2.25rom without its original Extrom. It works perfect for me.
huangyz said:
I now run 2.25rom without its original Extrom. It works perfect for me.
Click to expand...
Click to collapse
Thanks. I have now loaded the following but with the QTEK 2.17 Extension ROM:
IPL: 2.24
SPL: 2.24
GSM: 02.25.11
OS: 2.25.11.1
I will have to wait until tonight to try the wireless at home.
One thing I've noticed is that I don't have a battery indicator at all now, neither in the Today window or the bar at the top. I'll dig around more to see why this has happened.
Taomyn said:
huangyz said:
I now run 2.25rom without its original Extrom. It works perfect for me.
Click to expand...
Click to collapse
Thanks. I have now loaded the following but with the QTEK 2.17 Extension ROM:
IPL: 2.24
SPL: 2.24
GSM: 02.25.11
OS: 2.25.11.1
I will have to wait until tonight to try the wireless at home.
One thing I've noticed is that I don't have a battery indicator at all now, neither in the Today window or the bar at the top. I'll dig around more to see why this has happened.
Click to expand...
Click to collapse
it looks a little strange that you have a 2.25OS with 2.24IPL/SPL. :?
you could put a bat. icon on task bar by running Windows\Init_Tray.exe
Ok so I still can't get WiFi working :-( but at least I've sorted the the battery indicator out (thanks to a reg tweak for AKU2.2)
Which leads me to this AKU stuff. I keep reading about 2.3 but I'm not sure if this is an official release or something that someone has put together. I'm willing to give it a try but not if it's just 2.2 with some tweaks or something like that.
Can anyone shed some light on the AKU releases? Mine definitely says 2.2 at the moment.
Oh and can I simply create an upgrade file with just the 2.3 OS file in it?
TIA
Ok, my WiFi is still borked, it sees AP's all over the place but the ones I know it should connect to the phone just will not lock on to - it tries for a few seconds then simply says "Unavailable".
Currently I have on the phone a combination of:
IPL: 2.24
SPL: 2.24
GSM: 02.25.11
OS:2.24.10.1 WWE
Protocol: 4.1.13.12
ExtROM: 2.17.7.102
WM5 5.1.95 (14955.2.3.0)
I've actually tried what should have been a later OS, 2.25, but the AKU was 2.2 and the copyright message shows 2005 where as this one is AKU 2.3 with 2006 displayed.
I'm thinking now that perhaps the Extended ROM which is from the latest QTEK build I could find. Can anyone suggest a good replacement for it that doesn't have a load of baggage and only useful customisations?
As a last resort I'd like to try downgrading back to full 1.x ROM (QTEK 1.6.7 I think) but as I understand it this may not be possible. If it can be done, can anyone point me in the right direction i.e. which downgrade ROM to try? Yes, I have gone through this forum but it's almost "information overload" and very confusing,
TIA
if you update to shipped Cingular 2.25WWE rom, you can bypass all the extrom and see if wifi works normal (before you install other apps.)
Mine is ok.
the AKU2.3 one is a custom test rom which may cause slightly unstable.
while this still doesn't work, i think there's no means except sending your device back for checkup and repair.
Thanks, but how do I "bypass all the extrom"? Is there a clean extrom I can use with it?
Ok, I'm making progress.
I followed the instructions for downgrading, which although says it won't work for 2.21 or above, sort of does.
I downgraded to the custom 1.5.4 which succeeded but left SPL still at 2.24 but everything else had changed. I then ran the LokiWiz v0.2b and that seemed to succeed too at least there were no errors.
I then tested WiFi and it locked and connected first time - yay!!
Next I have taken the 1.6.7 QTEK ROM (which the phone originally had) and when that finished both IPL/SPL were downgraded to v1.x - WiFi still working.
At least now I know that WiFi is not borked but it's some strange ROM issue.
I'm going to try QTEK's 2.17 ROM and see what happens - at least I know I can get back to 1.x if it still doesn't work.
This is fun - not!!
Taomyn said:
Thanks, but how do I "bypass all the extrom"? Is there a clean extrom I can use with it?
Click to expand...
Click to collapse
after the RUU completed and restart automatically, after those init setting you must follow(eg. align screen, select time zone, etc.), at the moment when u see "customize within 3 seconds", poke the reset hole as quick as you can. Then you Bypass the extrom installation.
Thanks - you are being a great help, it's much appreciated.
I went back to 1.6.7 then added the Cingular 2.25 OS ROM but with the QTEK 2.17 extended ROM. What a mixture that is! WiFi would not work. I then hard reset and used your bypass technique - WiFi now works.
It seems that an extended ROM application is screwing up WiFi so I need to get everything up to the latest and greatest, bypass the extended ROM then one by one run them to see which is the culprit.
The plot thickens......
Well it looks like *any* v2 ROM screws up the WiFi on my phone and I have no idea why :x I have tried various combinations of ROM parts (proving the phone is most definitely CID unlocked :wink: ) and I either have no WiFi or some which progressively gets worse as time goes on to the point it stops connecting again.
I'm back to the original 1.6.7 QTEK WWE shipped ROM and WiFi works flawlessly but I'm now missing all the nice tweaks of v2 and I'm sure my BT headset doesn't work as well as before.
Maybe the next release will be better :?
Just to conclude this thread. The 2.26 ROM recently released seems to have cured my WiFi woes and it has made my phone run so much better than before.
I recommend it to anyone
Taomyn said:
Just to conclude this thread. The 2.26 ROM recently released seems to have cured my WiFi woes and it has made my phone run so much better than before.
I recommend it to anyone
Click to expand...
Click to collapse
Cheers!
wifi probs with 2.26
i just upgraded my MDA USA to this ROM. My wifi now doesnt connect. It was working fine with ROM 1.08. Any suggestions? I havent tried bypassing the ext ROM, will this work? thanks
Same problem here as above
I got same wifi problem when upgrading from 2.25 to 2.26 .
i am going to revert back to 2.25 which is from the imate website. and hope it sorts it.
will get back to you when done.

Downgrading Upgrading LokiUnlock Overwhelmed and Confused Plz help

Ok I purchased a new Cingular 8125. It is a G3 Version. It was purchased with these settings
Original
Ipl 1.08
Spl 1.08
GSM 01.09.11
OS 1.8.11.1
New
Currently I Upgraded it to the HTC Release ROM from
HTC's website Settings now are
Ipl 2.25
Spl 2.25
GSM 02.25.11
OS 2.25.11.1
I want to use Risi's new 2.26 Rom but I can't CID/UNLOCK my phone. I noticed that there are MANY others here with the SAME problem.
I'm Begging for some assistance.
We need
1. Instructions on how to Downgrade to 1.8.11.1 so that we can use LOKIWIZ to unlock it. Thereby enabling us to use cooked up roms.
Been looking all over for the programs that are needed to do this. And I'm just as lost as ever. I definately do not want to brick my 8125 but I'm out of options.
http://forum.xda-developers.com/showthread.php?t=263116
Forget the warning at the top, I just used this method and on my new 8125 with the same firmware you are running and it worked fine. Take your time and follow directions. If you are not absolutly sure after reading the instructions stop and forget it. Download all the tools you need and do a dry run in your head.
Oh, I just found all this information a couple days ago by searching and spending time on the forum reading.
thanks man. im doing it right now the downgrading process hopefull it works. pray for me. if it does work ill have your children, build a shrine in our honor, and send 5 strippers to your house. if it fails i shall smite thee to hell on earth and take your first born.
well ive tried everything man. I went BACK to that old rom. Did the CIDunlock deal it apparently worked. But Nothing else does. It goes back to the old 1.xx rom then i made the mistake of upgrading to risis rom immediately. that didnt work. kept everything the same but installed the EXT rom. so i went BACK to the 1.xx rom unlocked again and then installed the 2.17 shipping rom. It instaleld but the OS stayed stuck at 1.xx. I ran risi and it only installed the ext rom again. I'm beginning to think my device can never support any cooked up roms and have given up. I'm installing the HTC shipped 2.25 rom now and hope that everythings all good and gravy again and all my numbers match up again. Hopefull this will be the case.

Did I kill the Wizard? :-(

[SOLVED! See page 4]
I have a Cingular 8125, which I hadn't used for a while (got a Trinity
I am trying to set it up for my wife, so I attempted to unlock it and upgrade to WM6. It is a G3 (it had 2.26). I had upgraded it several times before. but was never able to bring it down to 1.xx in order to unlock it.
So, I started trying to downgrade it, but basically, every time it entered bootloader, it seemed to lose connection and it just timed out on the PC, without ever going to the update bar on the bootloader screen.
I ran IPL_SPL_3.08, and it upgraded fine. But still no go on downgrading.
Finally, I ran Shelltool (bug fixed) and managed to flash to OS 1.5.4.2. But, after the hard reset, it just stays on the blue Cingular screen (showing IPL 3.08; SPL 3.08; GSM 02.47.11; OS 1.5.4.2.)
I have tried flashing again with an original Cingular WWE ROM (RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship_1.exe), with the 1.5.4.2 ROM, even with a WM6 ROM (again, through Shelltool.) I have placed it in a powered cradle, have tried both Shelltool and RUU flashes, both while in the blue Cingular screen, and while in Bootloader mode. I have disconnected and reconnected each time, and rebooted many times (both the Wizard and the PC.) I have hard-reset. I have also tried both with USB selected and unselected in Activesync.
The Shelltool seems to freeze. The official RUU gives "ERROR [296]: UPGRADE ONLY. The NBF file cannot be used for your PDA Phone. Please get another NBF file." Or, alternately, it gives "ERROR [264]: CONNECTION."
Any ideas if this is repairable?
(Or should I cry (or take a hammer to the Wizard:-((
Mine is a 2.25 and it's a G4.. Isnt 2.26 a G4?
I think it was 2.26 (it may have been something like 2.27....), but it definitely didn't have the .000 at the end. I thought that the Wizards without the .000 were G3. Did I screw up?
Madcap180 said:
Mine is a 2.25 and it's a G4.. Isnt 2.26 a G4?
Click to expand...
Click to collapse
2.25.0001 or 2.26.0001 would be a G4
2.25 or 2.26 would be a G3
MacGuy2006 said:
I have a Cingular 8125, which I hadn't used for a while (got a Trinity
I am trying to set it up for my wife, so I attempted to unlock it and upgrade to WM6. It is a G3 (it had 2.26). I had upgraded it several times before. but was never able to bring it down to 1.xx in order to unlock it.
So, I started trying to downgrade it, but basically, every time it entered bootloader, it seemed to lose connection and it just timed out on the PC, without ever going to the update bar on the bootloader screen.
I ran IPL_SPL_3.08, and it upgraded fine. But still no go on downgrading.
Finally, I ran Shelltool (bug fixed) and managed to flash to OS 1.5.4.2. But, after the hard reset, it just stays on the blue Cingular screen (showing IPL 3.08; SPL 3.08; GSM 02.47.11; OS 1.5.4.2.)
I have tried flashing again with an original Cingular WWE ROM (RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship_1.exe), with the 1.5.4.2 ROM, even with a WM6 ROM (again, through Shelltool.) I have placed it in a powered cradle, have tried both Shelltool and RUU flashes, both while in the blue Cingular screen, and while in Bootloader mode. I have disconnected and reconnected each time, and rebooted many times (both the Wizard and the PC.) I have hard-reset. I have also tried both with USB selected and unselected in Activesync.
The Shelltool seems to freeze. The official RUU gives "ERROR [296]: UPGRADE ONLY. The NBF file cannot be used for your PDA Phone. Please get another NBF file." Or, alternately, it gives "ERROR [264]: CONNECTION."
Any ideas if this is repairable?
(Or should I cry (or take a hammer to the Wizard:-((
Click to expand...
Click to collapse
I thought I read somewhere that IPL/SPL 3.08 was a bad convert from a Charmer? If this is true and the Charmer bootloaders are different than the Wizard bootloaders then you may have put yourself in a bind.
The fact that you can still get past bootloader is promising even though the phone doesn't finish booting.
Try flashing from the bootloader (tricolor IPL/SPL screen with USB in the corner)
Thanks. I've been trying to flash in both bootloader or "blue" screen, but no go so far. I just tried the official Cingular .nbf through shelltool: it spent about 30 minutes (in bootloader,) then it stopped responding. It's been doing this forever now.
Any other options left?
MacGuy2006 said:
Thanks. I've been trying to flash in both bootloader or "blue" screen, but no go so far. I just tried the official Cingular .nbf through shelltool: it spent about 30 minutes (in bootloader,) then it stopped responding. It's been doing this forever now.
Any other options left?
Click to expand...
Click to collapse
You CAN'T use shelltool in boot loader mode! it needs the OS and the TRUFFS to read and write to the phone.
Any phone that doesn't go past the boot loader must be fixed with mtty, RUU or SD card...
Thanks for the info. I've been reading about mmty and just downloaded it. But I only have a 4GB card handy (from my Trinity.) I might be able to find my old 2GB one at home.
Edit: Well, this is what I just found: http://forum.xda-developers.com/showthread.php?t=308772&highlight=mtty+wizard
It seems that the IPL_SPL 3.08 might be a real problem. I'll try the card flash, but based on the above thread, I am not holding my breath.
If anyone has a suggestion or a solution, please let me know.
Thanks!
BTW, if the problem is indeed with the IPL_SPL 3.08, then perhaps the suggestion that we upgrade to it (in red) here http://forum.xda-developers.com/showthread.php?t=285435 should be removed, so that we don't get more expensive bricks.
Just to clear up the question about 3.08 IPL/SPL, it isn't an issue at all. It's been tested thoroughly to work well, better than 2.26.
TaurusBullba said:
Just to clear up the question about 3.08 IPL/SPL, it isn't an issue at all. It's been tested thoroughly to work well, better than 2.26.
Click to expand...
Click to collapse
After I unlocked my wizard and before I try any new ROM, I always burn the latest German wizard ROM with 3.08 IPL/SPL "ruu_vario_aku3.3_3822_382120_026911_tmo_de_ger_ship". Then I downgrade the Radio ROM to Cingular 2.25.11. Then I burn my ROM of choice. I've found it works best for me. I've never had a problem with 3.08.
TaurusBullba said:
Just to clear up the question about 3.08 IPL/SPL, it isn't an issue at all. It's been tested thoroughly to work well, better than 2.26.
Click to expand...
Click to collapse
What are the grounds for such a comparison? How to tell that an SPL works better than another? As far as i know the SPL is there to initialise the hardware and to apply security restrictions.
What i'd like to know is if anyone has been successful in downgrading IPL/SPL from 3.xx to 2.xx as itsme once said that there was a security in newer SPL's preventing downgrading (i must look for it...)
cheers
O.K., so maybe it's not 3.08, but something has sure gone bad.
I am trying to use mtty 1.1.42.538, but see only Port 1, Port 2 and USB. When I type in \\.\WSCUSBSH001 I get a message that it cannot open the \\.\WSCUSBSH001 port.
I tried resetting as described in message #7 here http://forum.xda-developers.com/showthread.php?t=264652&highlight=mtty1.42, but nothing happened.
I also tried choosing USB, then typed in r2sd all and again, nothing happened - I just get CMD> again....
So, can anyone think of anything else I can do, or should I just drop it from the 4th floor?
What IPL/SPL values you have at this moment?
mestrini said:
What IPL/SPL values you have at this moment?
Click to expand...
Click to collapse
Both ar 3.08, and I have the feeling that this is why I cannot flash the official Cingular ROM over what I have now. Which makes me wonder: is there an official Wizard ROM file combined with the IPL/SPL 3.08? This may at leas allow me to flash.
MacGuy2006 said:
Both ar 3.08, and I have the feeling that this is why I cannot flash the official Cingular ROM over what I have now. Which makes me wonder: is there an official Wizard ROM file combined with the IPL/SPL 3.08? This may at leas allow me to flash.
Click to expand...
Click to collapse
I had also upgraded my IPL/SPL to 3.08 -- up from the 2.25 on the newest Cingular ROM.
Anytime I've flashed to a WM6 ROM, I've been able to downgrade to the T-Mobile 2.26 ROM -- which changes the IPL/SPL to 2.26 -- with no problems before upgrading to a WM6 ROM. After flashing the WM6, I then go back in and upgrade the IPL/SPL once again to 3.08. It's not failed me yet.
O.K., I've spent the weekend screwing around with this:
If I run any of the original 2.xx ROMs, I get "you need an updated utility" message and then the utility goes to the "Exit" screen. (I am assuming this is because of the 3.08 IPL/SPL.)
mtty tells me I don't have permissions when I tried to load the ROM on a SD card (remember, the 8125 is not SuperCD-ed.). It also does nothing when I type "set 14 0" or "task 28."
But, I found that I can run the XDA Mobile 6 ROM (http://forum.xda-developers.com/showthread.php?t=310954) and it actually starts updating, but when it gets to 99%, the bar on the 8125 turns red and after a while the Update Utility tells me that the Wizard is not connected anymore.
Got very excited when I tried mattk_r's InGeNeTiCs' ROM(http://forum.xda-developers.com/showthread.php?t=311144): it started updating, went all the way to 100%, at which point the bar on the 8125 did turn red, however after a period of time the utility gave me the "Congratulations" message and told me I've successfully upgraded. But then, the 8125 reboots, and unfortunately, it still hangs on the boot screen, and it still gives the OS as 1.5.4.2. Have tried a number of times, always the same:-(
Oh, I tried upgrading the Radio only, and it worked: I was able to upgrade to 02.61.11.
So, does it seem like there is hope, and can anyone think of what else I can do?
MacGuy2006 said:
O.K., I've spent the weekend screwing around with this:
If I run any of the original 2.xx ROMs, I get "you need an updated utility" message and then the utility goes to the "Exit" screen. (I am assuming this is because of the 3.08 IPL/SPL.)
mtty tells me I don't have permissions when I tried to load the ROM on a SD card (remember, the 8125 is not SuperCD-ed.). It also does nothing when I type "set 14 0" or "task 28."
But, I found that I can run the XDA Mobile 6 ROM (http://forum.xda-developers.com/showthread.php?t=310954) and it actually starts updating, but when it gets to 99%, the bar on the 8125 turns red and after a while the Update Utility tells me that the Wizard is not connected anymore.
Got very excited when I tried mattk_r's InGeNeTiCs' ROM(http://forum.xda-developers.com/showthread.php?t=311144): it started updating, went all the way to 100%, at which point the bar on the 8125 did turn red, however after a period of time the utility gave me the "Congratulations" message and told me I've successfully upgraded. But then, the 8125 reboots, and unfortunately, it still hangs on the boot screen, and it still gives the OS as 1.5.4.2. Have tried a number of times, always the same:-(
Oh, I tried upgrading the Radio only, and it worked: I was able to upgrade to 02.61.11.
So, does it seem like there is hope, and can anyone think of what else I can do?
Click to expand...
Click to collapse
If I were you I might be talking to IMEI unlockers. Their process works from bootloader and might be able to get you CID unlocked and fix your corrupted CID area, which seems to be your major problem atm. In any case I would contact them and explain your situation and see if they think their software will unlock your phone. If so then you should be good to go once you CID is "uncorrupted" and unlocked.
one question: can You HARD RESET your device?
Do you have "format failed" message?
if so, you have 50/50 per cent for resurrection.
3.08 is not direct problem here anyway..., version is not exactly matter of problem...
(imei? now? lol)...
Thanks!
Yes, I can hard-reset fine and it claims to reformat fine.
Tx for the suggestion - I will contact IMEI (they unlocked my Trinity before the free unlockers were available

IPL doesnt change anymore! (1.01)

I have a CID unlocked wizard which has seen many roms, without any problems.
Lately I upgraded to IPL/SPL 3.08 and tried the touchflo rom.
Since it didnt work as expected, i presumed i needed to go back to the button rom before burning yet another rom.
Guess that was a mistake. I am now stuck on IPL 1.01 ! Whatever I do, cant get it to go to anything higher. Tried 2.26 IPL/SPL only, the full t-mobile version, the 3.08 again (which gives me spl 3.08 only this time), the german rom etc.
All that changes is the SPL. Tried installing enablerapi again, no result.
I can always get back to 1.01 IPL/SPL but THAT's IT ! NO other ROM works anymore!
What to do, what have i done....
You mean you can flash and work with Button ROM?
If so why not try to go from there to Qtek WWE 1.06, then 2.17 or 2.26?
tried flashing to 1.06 .. and got at 96% that the NBF was no good for my device.
However it changed the spl to 1.01.0000 instead of 1.01.
you should flash the buttom or love rom over and over again til you get both spl and ipl to 1.xx. people in the the threads have commented that sometimes it could take up to 8 flashes or more to eventually get it to work...dunno what causes it, but afterwards, flashing to a carrier rom should be fine...
good luck
Please read my first post.
I can get both IPL and SPL the same without a problem.
Both are 1.01 at that point.
I have been burning ROMs for a year now, so I know about this stuff already.
It must have something to do with going back from 3.08.
I have been on 3.08 both IPL and SPL dont forget!
At 1.01/1.01 IPL/SPL I still can not burn any ROM without error.
It wasnt like this before, have been on high numbers already.
after trying yet another operator ROM, gone back to IPL/SPL 1.01/Button ROM.
(shouldnt it say 1.05 btw?)
Button doesnt fully install anymore.. it gets stuck at about 98% after discobuttons.cab on the extended rom installation.
maybe that is a hint?
should i reinstall enableRAPI and cert_spcs before upgrading? my phone is cid unlocked for sure, and the service tool also says it is.
UPDATE: * installing xda mini..
* it got me 1.01 / 1.05
* reinstalling mini
* install also stops on signed discobuttons.sa.cab
d-lite said:
after trying yet another operator ROM, gone back to IPL/SPL 1.01/Button ROM.
(shouldnt it say 1.05 btw?)
Button doesnt fully install anymore.. it gets stuck at about 98% after discobuttons.cab on the extended rom installation.
maybe that is a hint?
should i reinstall enableRAPI and cert_spcs before upgrading? my phone is cid unlocked for sure, and the service tool also says it is.
UPDATE: * installing xda mini..
* it got me 1.01 / 1.05
* reinstalling mini
* install also stops on signed discobuttons.sa.cab
Click to expand...
Click to collapse
It means you can take it as far as installing extended_rom? Why don't you soft-reset the phone when the message of the 3 seconds appear?
if you're just installing button rom as a step to higher roms why the extended_rom? Simply forget about it and install 2.xx
No roms worked anymore, so tried ipl/spl 2.26 together with the installer from button.. it gave me 2.26 on spl again. NO change still on IPL.
IPL seems pretty stuck on 1.01.
in case it helps, are you flashing on windows xp or windows vista?
Here, try this. It's IPL/SPL 1.05 only. I'm not sure if it will work but it's worth a try.
It gives me 1.01 / 1.05 ....
trying multiple times .. hold on
tried 10 times.. ipl 1.01 spl 1.05
giving it few more tries on button
oh windows xp professional 32bit ..
trying love, buttong all in a row again.. still on IPL 1.01 SPL 1.01.
I think i found a new way to brick a wizard, goto 3.08 and back to 1.01
However, I think the phone not fully installing the extended rom must be a hint, since it usually had no problems with this.
Now on love and button, it stops at discobuttons.
Hate to tell you this, but I'm out of ideas at the moment. If I think of something, I'll let you know though.
Just a quick thought though, did you try removing the battery for about a half hour or so and then trying it again?
will leave battery out all night and try again tomorrow.
apart from the 'not being able to fully install extended rom' another thing that is remarkable is that the wizard service tool says I don't have a Wizard, after that however the info is correct (wiza200, cid unlocked etc).
further most ROM installers now crash at about 95% with error 320 saying the NBF is not made for my device.
is there anyone that has succesfully been on ipl/spl 3.08, down to button and up to 3.08again?
something else, the bootscreen doesnt show a GSM ROM version anymore, is that normal on ipl 1.01, could it be that i need to downgrade to certain gsm version ?
^$%#$ i dont think i can get the t-mobile service department to fall for my bricked mda excuses for a second time.
was pretty proud i got them to fix it for free first time i bricked it.. but this is different hehe....
(in case you wonder: 24volts made them not discover the cid lock, just created a bigger problem for the phone so they gave me whole new pcb.. i said the powersuply caused it )
The person that I was helping on that other thread successfully got his from 3.08 down to 1.01 and then back again. It wasn't easy, but getting theirs back up was a walk in the park compared to yours. I seriously hope that leaving the battery out over night does the trick because I'm pretty much at a loss as to what else to do.
It not showing a gsm version shouldn't be a big deal. You said that your rom installers are shutting down at 95% so it just may not be installing the radio, but your wizard should still operate without it. You just wouldn't be able to do any phone related things like make calls etc. but everything else should still work.
Don't worry about the wizard service tool saying that it isn't a wizard, it says that when I run it on mine too.
Just a thought, and definitely not a suggestion since you mentioned the 24v thing, do you have insurance on it? Accidentally dropping it in the bathtub might help solve your problem, not that I would ever condone insurance fraud or anything like that. All you would be out would be whatever your deductible is, although if your deductible is like mine it still wouldn't be cheap. I'd still give a little more time before doing anything rash anyway.
xeno1 said:
Just a thought, and definitely not a suggestion since you mentioned the 24v thing, do you have insurance on it? Accidentally dropping it in the bathtub might help solve your problem
Click to expand...
Click to collapse
good idea, but on the limit for this kind of thing for this phone as you can understand from the 24v issue
now at work, phone doing without battery all night... told him it is final warning, maybe taking his juice away will make him realise it is time to get to life
LOL Good idea. Tell it that if it doesn't decide to straighten up and start working you're going to run it over with your car. That ought to make it decide to work again'
So did it fix it?
oh man it got really angry with me.
on the wizardlove rom i had no radio @ all. but no charging or power info either!
you guessed it, been playing with wires and a 1.5v-12v powersupply set on 4.5v. Since it was doing it's paperweight imitation on me.
Got power back on 39%, going for a uuh 41% walk of my labrador.
Keep you posted.
Btw, extended rom in wst is unknown... is that any hint?
could protocol version be a hint?
next thing i try is flash another radio first, turn around the sequence.
Hmm, with the things that are hapening right now, no radio and the extended rom being unknown, I'm starting to think maybe the rom you're flashing has somehow become corrupted. You don't really need to worry about the ROM or the radio too much anyway, that shouldn't really have any bearing on whether you can get your IPL up or not. Try just flashing the 1.05 IPL/SPL update or the 2.26 update again and see if leaving the battery out for a while finally lets you upgrade it.

IPL locked on 1.01

Hello all,
I am somewhat of a newby here, but I have successfully unlocked my Cingular 8125 and installed a couple of WM6 ROMs. I followed the procedure of downgrading to Button 1.05 ROM, then running Lociwiz, then installing T-Mobile 2.26, then WM6 ROM. Worked great...until now.
I was going to try another ROM, and I followed above procedures (didn't know if I needed to after initial unlocking, but I did anyway). At the "install T-Mobile 2.26" step, after 1 %, I got an error 326?, nb file not for this device. I can still install cooked WM6 ROMs, and the SPL changes, but IPL always remains at 1.01. If I try to install IPL/SPL 3.08 CAB, SPL changes to 3.08, IPL stays at 1.01. I have re-installed Button Rom 1.05 and run Lociwiz a dozen times to no effect. Even the Cingular WM5 OS meant for this device gives me the same error code as the T-Mobile.
I'm hoping this is a simple newby error. Anybody have any suggestions.
Thanks for any help.
By the way, after loading Button ROM, my Wizard hangs during the customization routine at Signed_DiscoButton8.sa. I must soft reset.
I got exactly the same problem.
I am now on IPL 1.01 , SPL 3.08, radio 2.69, using rom NBD 8.3
doesnt seem a problem however...
d-lite said:
I got exactly the same problem.
I am now on IPL 1.01 , SPL 3.08, radio 2.69, using rom NBD 8.3
doesnt seem a problem however...
Click to expand...
Click to collapse
Hey m8,
have you forgotten this thread (http://forum.xda-developers.com/showthread.php?t=319582) ? (see last post)
mestrini said:
hahaha nice to see good spirit after all this
Here goes:
Make backup of the CID block (VERY VERY important!!!)
Make backup of the GSM calibration block (VERY VERY important!!!)
Kill wcescomm.exe process
Start mtty, enter bootloader mode in Wizard and connect
type doctest (this will write test patterns in DOC chip and clear all data!)
Flash button ROM (1.01_IPL/1.01_SPL/1.05_OS)
Flash CID block backup (don't miss this)
Flash GSM calibration backup (important)
If all ok then remember to upgrade to 2.xx before installing WM6!!
Post results
EDIT:
Use WST for steps 1, 7 & 8
Click to expand...
Click to collapse
are you willing to prove me wrong?
mestrini said:
are you willing to prove me wrong?
Click to expand...
Click to collapse
yes.. missed your last post to be honest, sorry..
(btw phone is happy till now .. but we go for solving it, killing seems impossible)
step 2, gsm callibration block.. how do i copy?
D-Lite
use the "Read ROM" button and select the appropriate section from the list.
status:
Code:
DOC ImgFS partition read/write test PASS
Ext ROM partition read/write test, offset=0x0, length=0xA00000
Test pattern =0xAA
Flash Ext ROM failed.
DOC Ext ROM partition read/write test FAILED
--Flashing button rom @ 100%
--DATA CRASHES PLEASE CONTACT SERVICE CENTRE
--WST Says I am still on SPL 3.08 and rom is write protected.. screen of wizard says SPL 1.01 ...
--Installing Button ROM, ... SIM Lock SUDDENLY
--Screen goes funny flashing between simlock and customise
--Few soft-resets, WST now convinced on SPL 1.01 and flashed CID block
--Soft-reset
--Imei gone, flashed back GSM callib. data, softreset
--doesnt boot passed the pint of beer... going for RUU of T-Mobile 2.x
--bootloader, flashing RUU_Prodigy_2210205_22102108_021911_TMO_NL_DUT_Ship.exe
--The NBF can not be used for your phone @95%, followed by congratiolations (stupid software)
--trying UK version...
--all give error 326
--another button flash
--*PLING IDEA* on 3.08 i couldnt doctest properly... so doing it again
-- bad idea.. same result...
damn... i thought it would work
anyway, there was point where the phone had same values for IPL/SPL (not too bad ). What is strange is why phone didn't boot anymore after flashing the GSM calibration and saying the flashes weren't suited for the phone.
What state is it on now? Wanna go again? This time, instead of flashing the 'GSM calibration data' do a simple IMEI writing and try to unlock CID before upgrading to official ROMs
sorry for this...
IPL locked on 2.26
I am having the same issue. I have tried numberous times to load my original rom and get the 326 error @ 1%. My ipl remains locked on 2.26. Is there any way to fix this? Please help.
it is now on 1.01, got my own imei back, spl 3.08, nbd 8.x rom...
everything fine again.. pretty sure it has something to do with ext.rom and/or write protection of it.. will give it another shot but not this month.. getting busy
@acmickey, not sure if you got same issue... is your IPL 1.01? else you might just have a locked phone..
Hey d-lite,
I followed your example and loaded BSD8.3 ROM and IPL/SPL 3.08 and radio 2.69. Everything seems to be fine. No missed calls. All programs work (touchflo is pretty cool). IPL is still locked on 1.01, even though SPL is 3.08.
I tend to agree with you that something is suspicious concerning the extended ROM. The first symptom I had that something was wrong was after loading Button's ROM, during the customization routine, Signed_DiscoButton8 would not install. Phone locked up and had to soft reset.
Oh, well, at least the phone works. The downside, of course, is that you can't load an original ROM, even though you can load a cooked one. Weird, huh?
Hopefully someone a lot more knowledgeable than I will figure this one out soon. Will keep checking the boards. At least we don't have bricks.
I am having the exact same problem as the 1st post but my ipl is stuck on 2.26. I am using an unlocked device and I have no problem downgrading/upgrading the spl. I also get the 326 error when I try to flash back to the original rom. (I used to be able to do this without a problem - I can't figure out what happened.)
It's really weird and I have search and searched and can't seem to figure out a solution.
which SPL you have now?
sorry.... my spl is 1.01
Right. Assuming your device is working 'normally' are you willing to try something new? If so contact me PM
what have you cooked up this time mestrini? lol
my wiz (at 1.01 still..) is doing a-ok, but always willing to go for something new so we can fix this for the communities sake...
d-lite said:
what have you cooked up this time mestrini? lol
my wiz (at 1.01 still..) is doing a-ok, but always willing to go for something new so we can fix this for the communities sake...
Click to expand...
Click to collapse
sorry to mislead you buddy but acmickey got it all wrong and, instead of IPL stuck at 2.26 and SPL 1.01, he has same as you IPL 'locked' at 1.01
So my theory could not be verified.
cheers

Categories

Resources