blocked on the boot screen - 8125, K-JAM, P4300, MDA Vario Software Upgrading

Hello,
I've tried to update my phone using the shelltool method and my phone crashed during the update.
Now it can't boot. it's freezed on the splash screen.
I've tried to put the CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE rom and it does nothing.
I have a G3 device, the IPL/SPL is now 1.01
Thanks in advance for your help

Flash back to official carrier ROM.

I have already tried using the bootloader method. it tells me that the device is not compatible

Try it doing the storage card method.

I also tried and it tells me I don't have the right

Before the first update, I have made a backup of the OS ROM but the file format is NBA. Is there a solution to reuse my original ROM?

In Addition to the SD method, the bootloader is password protected

Try reflashing the ROM you were flashing in the first post using the RUU in bootloader mode. You shouldn't need to use the shelltool to flash that one. Then when you get that flashed on there do your CID unlock. After that you should be able to flash any ROM you want.

I've tried tu put Button's ROM using the RUU in bootloader mode and its still blocked

Try flashing the wizard love rom then. I'm not sure where it is at the moment, but you can find it on here somewhere.

I also tried this ROM

I have made some research.
At the beginning (when my first upgrade crashed) someone on a chat told me to do a doctest.
No the problem is that the memory is damaged.
When I try a hard reset, I have the message "format is failed"
Any idea?

You've got me on this one, I don't think I've run across anyone else ever having this problem. By the way, did you remove any miniSD card that you had in the phone before flashing? Having one in there while flashing tends to cause people problems.
Also, I just realized that you said that you used sheeltool to flash the first time when you flashed the button rom and that it changed your IPL/SPL to 1.01. Flashing using shelltool won't change your IPL/SPL, it skips those files if they are added to a rom since they are the files that will destroy a G4 device. So, if it did change them then that's where you did something wrong. Why don't you start over and explain exactly what you did on the first flash with the button rom and see if we can't figure it out from there.

OK I'll explain from the beginning
Before beginning the flash, I have made a backup of the ROMs (OS, Radio and Ext) with aWizard.
I wanted to put a french WM6 ROM. In the the tuto, it was told to use shelltool to do this. For an unknown reason, the phone crashed. So I had to reboot the phone because it was freezed and after this point it did'nt boot.
I went on a chat to get help and someone told me to start the bootloader and with mtty enter the command doctest (I think he's a joker becose today I saw this command is very dangerous).
When I saw this command doesn't work I discovered this forum and tried 2 of the 3 methods to unbrick a phone in the wiki.
I can't use the SD one because the boot loader is password protected.
I also discovered today that the IMEI number doesn't correspond to the label on the phone.
Here is my story .

http://forum.xda-developers.com/showthread.php?t=276963&page=7&highlight=wizard+bootloader+password
This post seems to have helped many. Read from beginning to end, then try to follow it. Good Luck.

raskell said:
http://forum.xda-developers.com/showthread.php?t=276963&page=7&highlight=wizard+bootloader+password
This post seems to have helped many. Read from beginning to end, then try to follow it. Good Luck.
Click to expand...
Click to collapse
I'can't use imei check because my imei is invalid

Why do you think your IMEI is invalid? If the only reason is that it shows a different one on the box than it shows in aWizard or whatever program you're using, don't worry about it because that seems to happen quite a bit. Usually it's because it got put in the wrong box. Anyway, you're in luck, I have a program that I believe I downloaded off of XDA which is a version of the IMEI-checks unlocker with the master unlocker code for all wizards.
Well, I was going to upload that tool for you but after trying 6 times to upload it and it failing each time I figured that maybe I should wait a little bit and try again later.

I think the IMEI is different because the one given from imei-checks is different from the one on the label back the battery.
Also, when I tried to order an UNL file with the IMEI given by the unlocker, they told me its a wrong number

Lets try this again.
Still failing to upload. I'm not sure why, but I'll try yet again later.

I sent you in PM the address of my ftp server

Related

8125 ROM Upgrade Problems

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.

Problem unlocking my k-jam (HTC wizard)

hi there,
on running k-jam_Lokiwiz02b ... i did all the instructions , after unlocking (step 1) , & rebooting
a message appeared : SIM Lock
"Data crashes..contact your service center"
i tried to install the old ROM ,, nothing happened & the same error
tried to unlock my device several times as mentioned ,, also the same error reappears every time ????
when i remove the SIM card , the ppc works normally (but not the phone of course) , tried another SIM & also no use
plz HELP
Do you have a G4 or G3 device? What ROM version do you have? We'll take it from there.
i've a G3 device 3.
installed this ROM lastly :
KJAM_ROM_1010903_103_10110_cdl_me_ship
on boating the following appears :
IPL 1.01
SPL 1.01
GSM 1.1.10.0
OS 1.1.9.3
up.....................
While your KJAM rom is 1.01, why don't you try using the Button ROM just to see if it makes a difference.
No clue about the SIM Lock error though. You can use lockiwiz .3 to do the SIM Unlock to see if that fixes that issue, then go back to trying the CID Unlock with .2b.
thnx for concern mfrazzz .. u mean i should try the oldest ROM available ? i tried so & no use ,,,,
i'll try .3 Lockiwz version & c ....?
i tried .3 Lockiwz version .... problem still exists
dr.moh said:
i tried .3 Lockiwz version .... problem still exists
Click to expand...
Click to collapse
Bummer... Ok, I just did a google search on your message and found this form Howard Forums:
The data crash message means that the encryption block controlling the simlock is damaged.
That should not be possible, but it apparently IS possible, because you're not the first person who's had it happen.
What I would attempt to do to recover is:
1. Take OUT the SIM card.
2. Bring up the phone in boot loader mode.
3. Reflash an official RUU that matches the phone (T-Mobile US) OR restore an SD image that matches the phone (T-Mobile US)
See if that works. If it DOES, then use the Lokiwiz again BEFORE you go screwing around with anything new. If it does NOT, then attempt the RUU to the Qtek or Imate ROM, again, with card out, and see if THAT one can be booted.
Click to expand...
Click to collapse
There was no indication in the thread if this worked or not, but its something else to try.
Hope that works for you (or lets you make progress).
FYI: Here's a link to the thread Google put me in where I found this. Just do a search on "data crash" in your browser on this thread and you can read from there down (for aways). I didn't dig real far though.
http://www.howardforums.com/archive/topic/872974-1.html
A similar problem with solution !
i searched the forum & found that post
earljg said:
Just in case everyone is wondering what I did before I decided to pay for the IMEI and wanted to try before buying a program...
Having the 2.17 ROM installed when I started to have this problem, I first decided to try the method suggested here:
http://forum.xda-developers.com/viewtopic.php?t=50768
That still came up with the "Data crashes..." error with both T-Mo and Cingular SIM cards inserted. The same as the method in the above link (Lokiwiz3a, etc...).
So then I decided to try an alternative method followed by in this thread:
http://forum.xda-developers.com/viewtopic.php?t=47848
Which involves downgrading, then unlocking, then upgrading. Also with no luck on removing the "Data crashes..." error. I tried inserting my SIM after the downgrade and running Lokiwiz02b and still same error message.
Then I finally broke down and paid for the IMEI unlock program as posted in this thread (suggested by meschle, and in many other threads):
http://forum.xda-developers.com/viewtopic.php?t=43319
If the two previous methods mentioned before the pay method do not work and you decide to pay for the IMEI unlock mentioned: PLEASE follow jt_armstrong's advice (mentioned in above post) for obtaining your phones IMEI # when ordering the program!!
Since I did it as a last resort, it was already too late for me to obtain the IMEI from my phone as the pay website suggests (dial *#06# on your phone). This is due to when I insert my SIM the "Data crashes..." message comes up and there is no way I could obtain my IMEI without looking at the label behind my battery.
All is well now after running the $38 program. I finally realized (with the help of the previous posters, and other threads in this great forum!!) I have exhausted all other options.
Unless you can wait for someone to come up with a definitive solution to this rare (from what I have read) problem, I highly recommend using IMEI unlocking program. I have been trying to find a solution for about 5 days in the forums and this was my last resort...
Click to expand...
Click to collapse
will the IMEI unlock program work with my Imate kjam ?
up......00

upgrade didn't work

i tried several times like described here http://forum.xda-developers.com/showthread.php?t=285435
but always when i want to downgrade my rom with the mentioned button 1.05 rom it went till 98% an then my wizard didnt do anything until i reboot it.
with the standard o2 rom i have the lokiwiz didnt work. but what could be the fault ? what can i try to get it work ?
peran281 said:
i tried several times like described here http://forum.xda-developers.com/showthread.php?t=285435
but always when i want to downgrade my rom with the mentioned button 1.05 rom it went till 98% an then my wizard didnt do anything until i reboot it.
with the standard o2 rom i have the lokiwiz didnt work. but what could be the fault ? what can i try to get it work ?
Click to expand...
Click to collapse
Who knows, you didn't tell anything useful about your phone or what ROMs or anything else. Try the link in my sig. Read it, do ALL the steps, if you think you can skip something--don't, if "it doesn't work"--then you didn't follow all the steps.
Best of luck,
--M
peran281 said:
it went till 98% an then my wizard didnt do anything until i reboot it.
Click to expand...
Click to collapse
I think this may be part of the problem... How long did you wait? All roms stall at some point and can stall for like 5 mins (sometimes more). Don't do ANYTHING, unless your PC gets an error. Its still working. If it sits for more than 10 mins then you probably do have a problem, but it can sit for what seems like forever sometimes. Just be patient.
If it sits for more than 10 mins then you probably do have a problem
Click to expand...
Click to collapse
i tried it several times and i always had to wait about 20 - 30 minutes and always the same result being hung up at 98%.
about your phone or what ROMs
Click to expand...
Click to collapse
here i have some data. i have
ipl/spl: 2.21(o2 ger rom)
gsm : 02.19.11 (o2 ger rom)
os:2.21.4.3 (o2 ger rom)
i hope that is all the important info u need.
i'll try the link from demontefixo and let u know if it work.
Tried flashing on anther pc yet? For most people with this kind of problem that's the solution.
Tried flashing on anther pc yet?
Click to expand...
Click to collapse
i have 2 pcs and 1 laptop and i used all of them one time.
i used now this installationhttp://forum.xda-developers.com/showthread.php?t=298613
and it stucked on step G3.4 when i want to flash the wizard_love rom with this error:
ERROR [300] : INVALID UPDATE TOOL
This error message will appear when you use the incorrect RUU version to upgrade.
what did i do wrong? i followed step by step like demontefixo said for 3 times.
peran281 said:
i used now this installationhttp://forum.xda-developers.com/showthread.php?t=298613
and it stucked on step G3.4 when i want to flash the wizard_love rom with this error:
ERROR [300] : INVALID UPDATE TOOL
This error message will appear when you use the incorrect RUU version to upgrade.
what did i do wrong? i followed step by step like demontefixo said for 3 times.
Click to expand...
Click to collapse
This is an error that you can get on G4 devices. What are you doing in step G3.4? Read G4.6!
but in the tutorial http://forum.xda-developers.com/showthread.php?t=298613
is described how to determine the wizard type and my ipl/spl is 2.21 and thats G3 device.
peran281 said:
i used now this installationhttp://forum.xda-developers.com/showthread.php?t=298613
and it stucked on step G3.4 when i want to flash the wizard_love rom with this error:
ERROR [300] : INVALID UPDATE TOOL
This error message will appear when you use the incorrect RUU version to upgrade.
what did i do wrong? i followed step by step like demontefixo said for 3 times.
Click to expand...
Click to collapse
That error indicates you aren't CID Unlocked. Is your phone booting now? or are you at the bootloader (rainbow) screen? If you are at the bootloader, then flash your official rom to get a working device. Once you have a working device, then go to step G3.6 and do the CID Unlock procedure.
ALso remove your SD card while you are doing all of this until you get it CID Unlocked and onto the TMobile 2.26 official rom (G3.8).
AND yes, you have a G3, so you don't (and shouldn't) be in the G4.x steps.
i want to downgrade my rom with the mentioned button 1.05 rom it went till 98% an then my wizard didnt do anything
Click to expand...
Click to collapse
yes but thats my problem. i tried it like described here http://forum.xda-developers.com/showthread.php?t=285435
and always the same problem. is there another way to cid unlock the device ?
peran281 said:
yes but thats my problem. i tried it like described here http://forum.xda-developers.com/showthread.php?t=285435
and always the same problem. is there another way to cid unlock the device ?
Click to expand...
Click to collapse
This is my last post for the day as I can't handle anymore of this (its not just you peran, but the other half dozen posts I've read in the last hour or so where people just aren't following the instructions they are given. These methods are tried and true, and they work. And yes, this is the way to CID Unlock your phone unless you pay to have it done)... In a previous post to you, it was stated you had to get back to an official rom first. Have you done this (your replies indicate you just continue to do other roms)? You need to get the latest rom from your carrier and get your device working again. Get it all charged up, pull out your SD card, then try flashing back to the button rom (I would also suggest you try pulling the button rom down again in case there is something wrong with your previous download of it).
Its the weekend, I'm going to go enjoy the spring weather
i did it like u suggested mfrazzz. i know that my phone isnt CID unlocked. but that is my problem. i read the mentioned article x-times and did it like described but the problem is : when i downgrade to button 1.05 rom then my pda stuck at 98% and i get the message from the update program on my pc that the downgrade was successful. but it isn't. why? till this step u cant do much wrong i think... :-(
Have you flashed back to the official rom from your carrier? Until you do that and get your device back working there is no point in trying to continue to flash the button rom (or any other rom). You have to get back to your carrier's official rom first. None of your posts indicate you have done that.
with the standard o2 rom
Click to expand...
Click to collapse
i always went back to the official rom from my provider and this always works perfectly. i tried it today again but always the same stucking at 98%.
i did it STEP BY STEP but it didnt work.
is there another rom i can use than button 1.05 ?
Is there no other rom then the one from button to downgrade my ipl/spl to 1.xx ?
please help.
I'm not aware of another one.
You might want to try this thread (I know its not the same issue, but might be worth trying to see if it makes a difference)
http://forum.xda-developers.com/showthread.php?t=294107
You might want to try this thread (I know its not the same issue, but might be worth trying to see if it makes a difference)
http://forum.xda-developers.com/showthread.php?t=294107
Click to expand...
Click to collapse
I tried it but it didnt help.
now i used Xelecin's 1.08 rom and this one worked. then i used lokiwiz and it was successful. but then i flashed the tmobile 2.26 rom and this worked but i couldnt use my sim-card any more. always when i insert my pin it said unknown sim and then crashes. i thought i sim-unlocked the wizard? another problem was when i want to flash the official o2 rom it said unknown vendor id...but i used before lokiwiz and there were no errors...and the last question, i know there are many now, where do i insert the sim-code i got from lokiwiz?
i hope someone have some answers...thx before

Bootloader question/trouble

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.

is my phone (t-mobile wing) really bricked?

My t-mobile wing will only go to t-mobile screen or bootloader screen, which reads IPL 4.10.0002 SPL 4.10.0000. My computer will not recognize it thru usb. I have read about flashing via sd. i am not very tech savy, but i tried to follow what i could find on the forums.
So far found a ruu rom which the phone will try to read but so far doesnt seem to do anything even after hours of waiting.
Also tried different kind of rom, lzx or something, which the phone also tried to read but gave me a error saying invalid certificate.
Is there anything else to do or am I sunk?
Go to Thewingster dot com. click roms, click tmobile wing, click 6.0 click download, it will take you to the tmobile website.
Enter the number located back of phone under battery. Download the StockRom. make sure you enter your phone into boot loader and install the stock rom. You don't need to be Hard SPLed. Should work because it worked for me. After your phone works just HardSPL your phone so you don't Brick it again.
also when its in bootloader it wont have any notification on your computer.
thx will try suggestion
will try. can i extract a particular file and load it via sd card? that is the only connection i have available right now.
Ya the original Tmobile RUU is in the file. I have never Flashed through Sd card so im not sure how that works.

Categories

Resources