Related
I recently attempted to update the ROM in my Cingular 8125. The process stopped at 95% and I received an "Internal Error". Now, when I turn on the phone, it gets as far as the color RUU screen, and nothing else.
How can I find out if I can repair this situation myself or if I need to take it back to Cingular.
Hopefully you'll give Cingular a little more info regarding this than you gave us.
My psychic advisor is STILL on vacation so I can be of very little help to you, sorry!
What ROM were you running before and what ROM were you trying to flash it with? Did you CID unlock before you flashed?
Sorry - When I posted the 1st message, I was in a hurry...
I am not sure what ROM version was on the device before I attempted to update (I know, I should have paid attention, but I was not). The phone was new from Cingular and I had not done anything else to it besides load a couple of apps (Skype & Agile).
I attempted to run the file RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship.exe that I downloaded from the HTC site. The update go to 95% and I received the error "ERROR [326]: INVALID COMMAND" - This NBF file cannot be used for your PDA Phone. Please check your NBF file." (I have attached a screenshot of the error to this post).
I am not sure what to do at this point.
Thanks,
Chris
Some folks at the Cingular forum are having the same issue with no solution offered.
I'd suggest putting the device into bootloader mode (Holding Record and Camera buttons while soft reseting) and then reflashing. Make sure not to launch any programs while flashing. I also don't touch the device at all as I've noticed the USB connection might slightly disconnect.
Good luck and let us know what happens.
I just tried reloading from the bootloader screen - no luck. Exact same error at 95%. Would it work to try to reload an original earlier ROM? If so, how would I go about trying that?
Chris
I had this same problem.....I went to the cingular site after having the problem. Before installing I stopped all applications then soft reset.
THen after it boots up install the file from cingular. It worked from their site. Not sure what changed but I am not having any problems now with the new ROM.
I had this same problem.....I went to the cingular site after having the problem. Before installing I stopped all applications then soft reset.
THen after it boots up install the file from cingular. It worked from their site. Not sure what changed but I am not having any problems now with the new ROM.
I have re-downloaded the ROM file from the Cingular site (actually it just redirects to the HTC site). Same problem. I cannot get to the point to even shut down any programs because the phone OS does not even load at this point. When I do a soft reset, I get the following (sorry for the blurry image - as you can see my good phone with the good camera is dead...)
I had a similar problem. I posted the fix on another thread and ppl said i was wrong, this wasnt it...but heres what worked for me.
Are you using a usb port on the front of the computer? if so, try pluggin into the ports on the back of your computer. I tried flashing the official rom from cingular a few times using front port and it stopped at the exact same % each time. got the same thing as you, colored bars.
Someone had mentioned to me that front usb ports don't work as well as back ones. give it a try. good luck
from the picture, it looks you have the G4 chip(u can see 2.25 0001)
Thanks to everyone for their input. From the suggestions above, I have tried various USB ports on my laptop and I always get to the same point. I have also called HTC tech support and they are pretty sure I have bricked my phone. I talked to Cingular and they have agreed to replace it. I have also researched the G4 chip issues (looked at the post: http://forum.xda-developers.com/viewtopic.php?t=56408).
Now I have the following question - When I get my new phone (which I will assume will have the G4 chip as well), the Cingular rep told me that it will already have the latest 2.25.0001 ROM on it. What are my options at that point to SIM unlock my phone. Will I be able to? From the post I referenced above, it sounds like I may not be able to with the G4 chip.
Chris
xtreme23 said:
from the picture, it looks you have the G4 chip(u can see 2.25 0001)
Click to expand...
Click to collapse
I second this observation! :shock:
This makes a major difference on wether or not you can even upgrade.
Search for G4 issues.
The .0001 in the IPS/SPL number will tell you which one you have.
The way I understand it is:
2.25 - G3
2.25.0001 - G4
I think this is the proper way to identify it.
slapper said:
Now I have the following question - When I get my new phone (which I will assume will have the G4 chip as well), the Cingular rep told me that it will already have the latest 2.25.0001 ROM on it. What are my options at that point to SIM unlock my phone. Will I be able to? From the post I referenced above, it sounds like I may not be able to with the G4 chip.
Chris
Click to expand...
Click to collapse
Chris, LokiwizMSL ( http://forum.xda-developers.com/viewtopic.php?t=50768 ) can SIM Unlock your device. Be sure to read the instructions.
Well - Now I have a new problem. So far, Cingular is refusing to replace my phone - saying that the ROM upgrade voided the warantee. I am still fighting that, but just in case I loose, is there any way to get my phone fixed once it has been "bricked"?
slapper said:
Well - Now I have a new problem. So far, Cingular is refusing to replace my phone - saying that the ROM upgrade voided the warantee. I am still fighting that, but just in case I loose, is there any way to get my phone fixed once it has been "bricked"?
Click to expand...
Click to collapse
If you installed an unofficial ROM then they are correct. You should never admit that you used a ROM that was not provided by HTC.
There are warnings all over this site about VOIDing your warranty.
Since you used the Official Update they are wrong.
Same problem with official Cingular 8125 ROM
I tried to flash the official Cingular ROM from the HTC site here:
http://www.htcamerica.net/docs/RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship.exe
I got the same error at 95%:
"Error [326]: INVALID COMMAND This NBF file cannot be used for your PDA Phone. Please check your NBF file."
When I reset the phone I get the RGB bootloader screen and nothing else.
My phone is a G4 and was running ROM version 2.25.11.1 WWE before. The reason I tried to apply this ROM is because there was apparently no Extended ROM. None of the customization cabs executed on a hard reset. Also, in Device Information, there was no "ExtROM" listed.
This is the second phone that this has happened on. I thought the first time was just a fluke thing and I had a bad phone. But now I think there is an issue with this ROM.
Anyone have any idea what is going on here with this ROM? Does the fact that there was no Extended ROM have anything to do with this ROM not flashing properly?
Is there anything else to try or do I need to try to return the phone (AGAIN)?
how to fix the problem
read this thread carefully. The upgrade problem seems to be occuring on G4 chipped Wizards with the most current IPL/SPL.
http://forum.xda-developers.com/viewtopic.php?t=56088
take the official update. run it, when it finishes extracting look for the extracted NBF file in your
C:\Documents and Settings\yourusernamehere\Local Settings\Temp\the newest directory just made
find the NK.NBF file
extract it using the tutorial in the post above you will be flashing with the official cingular components sans IPL/SPL.
flash it and your are back up and running
I would have posted this earlier but i had to make sure it worked and was repeatable.
I think the problem with the new update is the new IPL/SPL version checking. It seems that if the patcher sees the same version already running it will give you that error at 95%. I've seen it on 3 phones already and I have been able to fix them by doing what i've told you above. You are already in bootloader mode and your phone is ready to accept a new rom anyways. My solution may not be the best for your phone and take no responsibilites but you are already desperate and need a fix. Good Luck!
Thanks for the reply, evilito. Since I hadn't gotten any replies for a few days, I decided to go ahead and try to exchange the phone at the Cingular store. They were baffled that this was the second phone I had returned for the exact same problem, but gave me a new phone anyway. I wish now that I had waited so that I could try evilito's solution to see if it works. As it is now, I am too scared to try any flashing on this new phone after my results with the first two. I would really hate to have to try to return a third phone
Can anyone else verify that there is a problem with the latest Cingular ROM when flashing a G4? Or did I really have two bad phones?
slapper said:
Now I have the following question - When I get my new phone (which I will assume will have the G4 chip as well), the Cingular rep told me that it will already have the latest 2.25.0001 ROM on it. What are my options at that point to SIM unlock my phone. Will I be able to? From the post I referenced above, it sounds like I may not be able to with the G4 chip.
Chris
Click to expand...
Click to collapse
Thats good to know, I thought that when we unlocked it and updated the ROM we lost Warentee Support. Where can you get the official Cingular 2.25 ROM. I am still on 2.17.
Firstly, let me say that I scoured the forums and the internet in general for information before starting a thread. Finally, I came to the conclusion that I needed to start a thread.
I bought a PDA2K from a friend who upgraded to a newer phone. It worked great, was MUCH better than my craptastic PPC4100 from Audiovox. Then it started crashing. Just freezing at random times. It got worse and worse.
Finally, someone suggested the ROM was corrupted and that a flash to the newest firmware, replacing the bad information, would solve the problem.
So, I downloaded the latest firmware (PDA2k_WWE_14000_176_11200), followed the instructions, and began the flash.
When analysing my device, there was a blank spot next to the extended ROM information, which confirmed the theory that the extended ROM was corrupted.
I initiated the flash, and it completed the first stage of the flash sucessfully. Then the problems began. The phone went blank. I left it alone, but nothing happened. So I killed the flash and pulled the battery. When I replaced the battery, the standard bootloader pulled up (Serial 2.07).
After reading for a bit, I decided that I wasn't SOL. So I docked it again, and got a 'USB Device not Recognized' error. I ran the flash anyways, but it never progressed past the 'analysing your device' screen. So, I disconnected it, hard reset it, and docked it again. This time, when I docked it, it switched to (USB 2.07), and windows recognized it as Microsoft USB Sync. I thought I was in luck.
Yea, right. Same thing, the flash program does not progress past 'analysing your device.'
So... am I SOL? What do I do?
I think I went to this problem before, I remember that I solved it by downloading the upgrade from wiki
http://wiki.xda-developers.com/index.php?pagename=BA_Upgrades
try downloading the rom from wiki and try upgrading again. if it doesn't work, upgrade without extended rom. once its done unlock extended rom by extended rom unlocker software and remove all contents in it and then run upgrade again.
hi
I tried to upgrade my pda2k to 2005, but I get hang
then when I tried again it show this message
http://www.600kb.com/uploads/20aac64ad6.jpg
can i get help please
sarab
Strategies for dealing with radio ROM update 114 errors
I had this problem last week and recovered from it. At first it looked pretty bad, nothing seemed to work. I looked the Internet up and down and in most forums, including this one, people agreed that nothing could be done about error 114, the mainboard of the BA needed replacement, etc.
When I finally did fully recover from this situation, it was from a combination of measures that I took and as I don't really know which one actually did the trick, I'll try to describe all of them even though not all will probably apply to others. Another problem is that I probably won't be able to remember them all, but anyway, here goes:
1) I downloaded the latest full official ROM update from site of the carrier this phone was branded for, in this case T-Mobile. It included a radio ROM, albeit version 1.13.0, not 1.15.0 which is the one I had been trying to flash. I decided it would be best to go back to that official version first.
2) I had been trying to do the radio ROM upgrade from a Macintosh (OSX) under Virtual PC. I have since done several ROM installations (without the radio part) from the Mac/VPC which worked fine, but since people had observed that radio ROM updates seem to be more sensitive than fiddling with the normal ROM, I decided to fire up my "real" PC, which runs WIndows XP, SP2, with Active Sync 4.5.
3) As others had suggested, I made sure that I had my cradle connected directly to a USB port on the computer; before I had been trying to go trough a hub. I also made sure the cradle was connected to the power adapter.
4) I had unlocked my device before to work with a non-T-mobile SIM card, but since I wasn't sure wether or not SIM/Net lock problems might still interfere with radio upgrades, I took my SIM card out of the unit, as well as the SD card -- trying to eliminate as many potential sources of screw-up as possible.
5) I think I tried to set my BA into as much of a defined state as I could by hard-resetting it and THEN invoking boot loader mode. I don't remember whether or not this was possible as the device was not reacting much to anything at the time.
6) On the Windows PC, I opened Active Sync, then went to Connection Settings and explicitly disabled the USB connection. I then quit Active Sync and invoked the Windows task manager (Ctrl-Alt-Del) to check that no other processes were running. Trying to cut out interference as much as poosible ...
7) I then proceeded to flash the official ROM version, which went flawlessly including the Radio ROM, took less than fifteen minutes in all. To be honest, I don't remember which ROM upgrade utility (BaUpgradeUt/MaUpgradeUt_noID) I used ... sorry. I know I tried whatever was included with the T-Mobile download first.
After that, I verified that everything was working again, then immediately flashed Radio ROM 1.15.0 as I had originally intended. This time it went uneventfully.
Hope some of this helps, I know how frustrated you must be at this point.
Good luck!
thanks a lot
i'm going to follow your instruction today.
regards to all
[email protected] said:
thanks a lot i'm going to follow your instruction today.
Click to expand...
Click to collapse
So did you have any luck?
Hi,
I used to upgrade roms all the time on my 8125 and never had a problem - until a couple of days ago. I tried installed the wm6 "most beautfiul" rom on my ppc and it bricked my phone. After many attempts I finally realized that I needed to install the official cingular 225 rom (available on the site) in order to get my phone to work. Since then I have tried downgrading to button and to wizard love with no success. My ultimate goal is to get to WM6. I have tried unlocking and have read all the threads and followed the directions but I cant switch roms. Can someone please help me with this. I am getting desperate.
thanks
ecomajor said:
Hi,
I used to upgrade roms all the time on my 8125 and never had a problem - until a couple of days ago. I tried installed the wm6 "most beautfiul" rom on my ppc and it bricked my phone. After many attempts I finally realized that I needed to install the official cingular 225 rom (available on the site) in order to get my phone to work. Since then I have tried downgrading to button and to wizard love with no success. My ultimate goal is to get to WM6. I have tried unlocking and have read all the threads and followed the directions but I cant switch roms. Can someone please help me with this. I am getting desperate.
thanks
Click to expand...
Click to collapse
do you have a G3 or G4?
What are your IPL/SPL?
Which other ROMs have you had installed on this wizard?
ecomajor said:
Hi,
I used to upgrade roms all the time on my 8125 and never had a problem - until a couple of days ago. I tried installed the wm6 "most beautfiul" rom on my ppc and it bricked my phone. After many attempts I finally realized that I needed to install the official cingular 225 rom (available on the site) in order to get my phone to work. Since then I have tried downgrading to button and to wizard love with no success. My ultimate goal is to get to WM6. I have tried unlocking and have read all the threads and followed the directions but I cant switch roms. Can someone please help me with this. I am getting desperate.
thanks
Click to expand...
Click to collapse
So, you start a new thread with the same problem you posted in another thread hoping to get an answer??
My answer to you is the same one I posted to you before --
READ THE STICKY ABOUT UNLOCKING AND FOLLOW IT STEP BY STEP!!
Then -- and ONLY then -- will you be able to flash to a custom ROM.
newbie2 said:
So, you start a new thread with the same problem you posted in another thread hoping to get an answer??
Click to expand...
Click to collapse
Yep, I've replied to ecomajor's various posts in various threads and have basically given up. Very little info each time and having a problem that nobody else that has followed the steps has had.
Sorry ecomajor, don't know what else to tell you that hasn't already been said numerous times.
One Last Try -- Then, I Give UP!!
Read the following post on how to flash ANY Wizard (yes, that includes the 8125) --
http://forum.xda-developers.com/showpost.php?p=1177659&postcount=1
Now, follow the directions in that post WORD FOR WORD and STEP BY STEP. The only reason it wouldn't work is that you're NOT READING and/or NOT FOLLOWING THE INSTRUCTIONS STEP BY STEP.
If you CAN'T read and follow directions, then don't be trying to flash different ROMs to your phone. If you're not willing to do what's necessary to help yourself, then noone else is willing to help you, either. . . especially when your problem has already been replied to with the same information over and over in 2 DIFFERENT THREADS now.
Let me detail you the exact steps I have taken. I have read through those posts, many times so I am certain I took those steps
1)device starts normally goto step 3.6 since unsure if unlocked.
2) read farias thread
3) download buttons rom
4)attempt to downgrade rom - failed
4a)tried 1.08 rom instead of button - failed
4b)tried wizard love- failed
5)download lokiwiz
6)followed all directions -failed - since was not able to downgrade rom.
Obviously these directions are not 100% foolproof - I know that the first time I tried installing WM6, I did not read through all the threads and after much effort I discovered that if I installed the official cingular 225 rom then I could get my ppc back working but since then I have had no luck getting flashing to work. Please tell me what I am doing wrong because noone has had my exact situation. there is no need to act all holier than thou and accuse me of not reading because since I screwed up the first time I have read through all these threads numerous times.
Ok, one more thing to try (shot in the dark, but I have no clue what is happening here)...
On your PC (its running XP, right???), do you have Firewall and/or Antivirus? If so, reboot your pc and don't start anything and then turn off your Antivirus and Firewall programs (I found a couple of threads where people were getting the error 260 when ZoneAlarm is active). Now try flashing the button rom. Don't try doing any other roms, don't try doing lokiwiz, just try to get the button rom on. If that works, then continue on with the steps here:
http://forum.xda-developers.com/showthread.php?t=285435
You might even try booting your computer into safemode and try flashing that way (I doubt activesync would be there, so put the phone in bootloader mode, and if you see USB above the left softkey then you should be able to flash it this way from safemode. Never tried it, but it pretty much eliminates anything that may be on your PC thats causing problems).
If none of that works, then get back to an official stock rom again and report back here with exactly what you did, what you saw, and all. Don't worry about the post being long, because to me, too much info is better than just short posts that don't tell us anything. Also, only update this thread. Forget all the other threads you have stuff going on about this problem.
Final question, I asked this before (and I don't remember if you answered or not)... Have you tried to flash your device from another PC?
And I've attached the ROM Update Utility Readme.doc that describes the error messages and how to fix them.
The weird thing is I never get code 260 with the cingular rom update just with the other roms. I will have to try the disabling all firewalls, antivirus etc at home bc at work there is all sorts of stuff i dont want to mess with. Problem if I do it in safemode is then the activesync driver wont be loaded and it will give me an error for that.
mfrazzz said:
Ok, one more thing to try (shot in the dark, but I have no clue what is happening here)...
On your PC (its running XP, right???), do you have Firewall and/or Antivirus? If so, reboot your pc and don't start anything and then turn off your Antivirus and Firewall programs (I found a couple of threads where people were getting the error 260 when ZoneAlarm is active). Now try flashing the button rom. Don't try doing any other roms, don't try doing lokiwiz, just try to get the button rom on. If that works, then continue on with the steps here:
http://forum.xda-developers.com/showthread.php?t=285435
You might even try booting your computer into safemode and try flashing that way (I doubt activesync would be there, so put the phone in bootloader mode, and if you see USB above the left softkey then you should be able to flash it this way from safemode. Never tried it, but it pretty much eliminates anything that may be on your PC thats causing problems).
If none of that works, then get back to an official stock rom again and report back here with exactly what you did, what you saw, and all. Don't worry about the post being long, because to me, too much info is better than just short posts that don't tell us anything. Also, only update this thread. Forget all the other threads you have stuff going on about this problem.
Final question, I asked this before (and I don't remember if you answered or not)... Have you tried to flash your device from another PC?
Click to expand...
Click to collapse
ecomajor said:
The weird thing is I never get code 260 with the cingular rom update just with the other roms. I will have to try the disabling all firewalls, antivirus etc at home bc at work there is all sorts of stuff i dont want to mess with. Problem if I do it in safemode is then the activesync driver wont be loaded and it will give me an error for that.
Click to expand...
Click to collapse
I've never tried it in safemode so I don't know if that will work or not, it was just an idea as we are grasping at straws here. But if you boot to safemode, and with the phone at the bootloader screen (hold down the camera button while you turn it on to get to the "rainbow" bootloader screen), if it shows USB above the left softkey then the computer and phone are communicating and Activesync does not matter. BTW:You can try the safemode way there at work as you will have no network connectivity in safemode so you don't have to worry about violating security policies.
You still have not answered my one question directly... Have you tried flashing the button rom to your phone on multiple computers? Or have you always done it from the same PC? And are the PC(s) that you are using running Windows XP?
What DOC chip does your device have? G3 or G4?
If you have a G4 then i guess you ruined your bootloader since G4 devices don't have and don't accept 1.xx IPL versions!!
I have tried button from multiple pcs. This time it gets up to 98% on button and then dies and it gives error 302 - update error for the button. This is a problem that I was having before.
Did you read the document I posted?? If you're getting Update Error 302, you're not going to be able to recover with anything other than the stock Cingular ROM.
Chances are that you did indeed ruin the bootloader when you tried using the ShellTool to flash a G3 phone. And I doubt seriously that you'll be able to do a warranty exchange if you can run the stock ROM successfully, so I'm afraid you're stuck now with the stock-shipped ROM.
So you are saying there is no way to fix the bootloader (like flashing it or soething) I was figuring I had screwed something up. I actually had read the document before but thanks for your help. Why is it that you can fix many other issues with the 8125 but not the bootloader?
I'm not saying it CAN'T be done. What I AM saying is that in the year I've been registered and active here, I've not seen any posts/threads about recovering from a bad bootloader. But that doesn't mean that there ISN'T a way to do it.
You might want to do a search of the Wizard section for bootloader error or recovering bootloader to see what might come up.
Good Luck!!
Hey there everyone, I am pretty new to this forum so I must apologize for throwing you all into the deep end. I recently purchased an o2 XDA mini S second hand from a guy on boards.ie here in Ireland. I got the phone and really liked it because it allowed me to get rid of my Dell Axim X3i and mp3 player and keep it all in one device.
After a little bit of more research I discovered that I could remove some of the bloatware from the o2 xda mini S by just hard resetting and choosing the basic option which I than did. Still not satisfied with the overall performance of the XDA I decided to try a rom upgrade. Not wanting to do a totall overhaul I decided to just do a radio upgrade first.
My device is sim unlocked, it was like that when I bought it. I used the latest wizard service tool to CID unlock the device before I even flashed the phone. I also used the wizard service tool to change the nk.nbf file within the o2 mini S radio update into 96000000-GSM.nb. I then used this file to write to the GSM radio code (Bdk 1) according to the wizard service tool in the hopes that it would upgrade my radio version.
Well when I restarted, nothing of the sort happened, on the boot screen I noticed I was now missing my GSM version and when the phone finally got into windows mobile, it did not pick up any signal even though beforehand it could. The phone also became super slow to the point where it was unusable.
I have gone into bootloader mode subsequently after reading on this forum and tried to reflash with a number of updates with active sync disabled and nothing else running with the phone connected via usb to the pc. None of the updates would even pick up the phone or allow me to flash it.
My phone is pretty much screwed, I have a spare so it is not that big of an issue but I would like to make this usable again if at all possible. So my question is how do I flash a rom while the phone is in bootloader mode?
P.S I forgot to include the Current boot screen details:
IPL - 1.05
SPL - 1.05
OS - 1.5.4.2
Hi,
You can use the Wizard Love Rom from here http://rapidshare.com/files/17792050/Wizard_Love_2.26.10.2_WWE_Novii_CF2.rar
Hey there, thanks for the advice, I did download that ROM but like I said before, none of the roms manage to flash my XDA because they all cannot seem to connect to it. Activesync does not even pick it up in windows mode, and even when I have it connected in bootloader mode via usb and I double click on the love rom, it goes through the motions but never managed to "verify the information with the pda"
Try a stock Tmobile ROM but not from bootloader. Also, I would check the activesync app on the device. Make sure it's set to use USB as the default connection method.
A few other steps to try...
Uninstall ActiveSync and install an older version. If still no go, try a newer version.
Try a different USB cable and/or USB port.
Try a different computer with XP, not Vista.
Try flashing it without the SIM card or any memory cards.
If all else fails, you can try the SD card flashing method. There are instructions in the Wiki on how to do it, but always a stock ROM.
Try this one... http://forum.xda-developers.com/showthread.php?t=311027
Updated IPL/SPL and radio 2.69
Hey Devis, I think I have come one step closer, I tried all the suggestions that you made. Except well now my phone will not even go into the operating system when I switch it on. It will boot and the version numbers show but then it just resets itself.
I tried a different usb cable and I am not using vista, tried a different pc and the same result. The one place I did have some marginal success was the sd card method.
Basically what happened is that It backed up the OS from my phone and then reloaded it, not exactly what I wanted since the OS and rom are both screwed on the phone so my question at this point is, is there anyway using the SD card method to load one of the stock roms onto my phone?
I searched around the net and found the opposite to the "r2sd all" function, would be the "s2d" function, would that allow me to flash the phone with a stock rom?
Thanks for your time, I am going to call it a night here in ireland and head to bed.
Ok, if the phone resets then you probbably have a dead/dying battery. Charge it for about an hour or so using the wall charger, not the USB cable. Try to restart it and see if you can get in the OS. I was looking in the SD card method thread and some guy was successful at restoring the image from the SD even though his OS had died. He then had a fully functional phone.
The other thing to do would be to get the image file from someone that has a living and breathing wizard, preferably one with a stock ROM. Since this method is the equivalent of making an image of a PC using Ghost, the restoration of such an image to your Wizard should work just fine.
Just make sure that the other Wizard is SIM and CID unlocked. Or just go buy a Wizard from the store, unlock SIM and CID, copy the image on the SD and flash your device. Or... since u've got a new Wizard in your hands, just take the freaking thing appart and swap the guts return the store bought wizard to the store saying that the thing just doesnt freaking work!
As for the AT commands... it is possible that s2d would workfor you, it doesn't work in my wizard. from what i have been reading it appears that the bootloader is password protected and that password is randomly generated. I haven't played long enough with it to figure out how to get the password.
It looks like you've got some "trial and error" processes ahead of you. There is a wealth of info on bootloader AT commands on Wiki, nothing for the Wizard though. But something may work... not sure.
I could try to get you a ROM dump from my Wizard but I already am on SPL/IPL 3.08 and running WM6. the SPL/IPL version alone wouldn't allow you to restore from my backup.
Hey Devis, thanks for your time, just woke up here, will work some more on the phone today and let you know what is going on
Hey Devis, I did not even get a chance to fiddle around with the phone today, from being able to switch on less than 24 hours ago, it does not even want to switch on now so I am going to officially declared it a brick and move on. Will see if anyone can fix it for me, spent way too much time already when I should be working on my dissertation, thanks alot anyway
Sorry to hear that...
I have bricked one phone myself in the past... my old Pana GD87 and I absolutely loved that phone. I know how you feel.
Good luck with your dissertation.