Related
Maybe some of you are already aware of this procedure, maybe not.
Anyway, it worked for me and I decided to share how to do it. Simple.
This procedure should only be used in case you really need enter into a bootloader mode and all other ways to do it has failed! Hold Camera button is one of these I am mentioning.
My Wizard was almost bricked at that time and after I speak with an I-mate technical guy, I got the following:
1. Make sure your i-mate™ K-JAM is not Connected to the PC and remove the dummy card or SD/MMC card
2. On your Desktop PC, open Microsoft ActiveSync, then go to File >Connection Settings >Remove the Selection from “Allow USB Connection with this desktop computer”
3. Reconnect your i-mate K-JAM to the Desktop PC using the USB Cradle and the Charger MUST be Connected to the Cradle (Don’t use the IrDA or Bluetooth for the Upgrade)
4. Run the Upgrade again and it will work fine without any problems.
While upgrading, the ActiveSync program will not go on, however the upgrade is running.
Hope it helps!
this realy worked for my (ex)bricked dutch tmobile mda vario !!!!
tip: REALY make shure that there is no wcescomm.exe running all the time and realy remove the sd card else is nogo
btw: my wizard is CID locked! and works like a charm
Thanks buddy!
I'm happy that worked for ya!
Take care!
I'm having a problem
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Any ideas?
Hi!
Have you already flashed your device once?
Which ipl/spl do you have?
I had problems over 1.05 ROM in the beggining.
If you stuck on bootloader mode, that's a good signal your device is not bricked.
I'd recommend you to disable activesync as you did and reflash it again! Check also if your device is CID unlocked! Search for a thread in the xda developers root.
Try to upgrade to ipl/spl 2.26 first and later to others you want.
Regarding the old file error...can be related to a missing file called enterbootloader.exe.
Hope it works for ya!
Take care
Ironman273 said:
I'm having a problem
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Any ideas?
Click to expand...
Click to collapse
My device is unlocked as I've been trying different ROMs as of late. I had gone back to the Cingular 2.25 ROM for a couple days to sort some things out and was going to flash Farias AKu 3.3 when my power problems happened. My Current IPL/SPL is 2.25
I've tried flashing the TMobile 2.26 but keep getting connection errors. In fact, I've tried flashing with every ROM I have pdviet 3 and 4, CIngular 2.25, TMobile 2.26 and Custom 1.05. Everything (except twice in the custom) gives me connection errors.
Any other trick I can try?
BTW, I used to live in Sao Paulo years ago...
Edit: OK, so I tried the 2.26 TMobile ROM after I typed this and it worked!! I'm back up but I was having trouble with that ROM beause of some incompatibilities with Cingular. I'll go back to Cingular's ROM and play it safe for now.
I believe part of my problem was I kept trying different updates one after the other. Now that I think back, the 2 times I got the update to almost work was after I turned off the device and turned it on again, which is what I did this time around also.
I had the same problems as mentioned by Ironman before. I followed the steps and with a few slight changes, I managed as well to "unbrick" my wiz. THANKS A LOT for the great step by step manual!!!
Still I wanted to know WHY i bricked my device:
I was trying to upgrade to the underground WM6 ROM. I got the same situation as ironman:
Quote:
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Unquote
I then followed the instructions by epimazzo as written above. I also tried the T-Mobile ROM 2.26 which was not working for me. PANIC!!!! Error messag was that I had the wrong Vendor ID. THerefore no upgrade to TMob 2.26 was possible. I tried it then my original qtek ROM in my language and see it worked!!! This IMHO means that I did not put the device in a proper IPL1.xx and SPL 1.xx status which is required for a clean system in irder to unlock it! So if it is bricked, try your native AKU2 ROM and make sure you unlocked it properly. Maybe you have to run the 1.05 ROM for a second time after the unlocking.
I hope this helps you guys.
Sounds great to hear that!
I had play around with pdaviet3, underground and another ROM just today without any problems at all. I don't think that this is the case. Now you get your device back to normal, try to reflash it again. Hope it works this time!
BTW,...São Paulo is a nice city. Thanks! Let me know if you decide to come here!
Take care
Ironman273 said:
My device is unlocked as I've been trying different ROMs as of late. I had gone back to the Cingular 2.25 ROM for a couple days to sort some things out and was going to flash Farias AKu 3.3 when my power problems happened. My Current IPL/SPL is 2.25
I've tried flashing the TMobile 2.26 but keep getting connection errors. In fact, I've tried flashing with every ROM I have pdviet 3 and 4, CIngular 2.25, TMobile 2.26 and Custom 1.05. Everything (except twice in the custom) gives me connection errors.
Any other trick I can try?
BTW, I used to live in Sao Paulo years ago...
Edit: OK, so I tried the 2.26 TMobile ROM after I typed this and it worked!! I'm back up but I was having trouble with that ROM beause of some incompatibilities with Cingular. I'll go back to Cingular's ROM and play it safe for now.
I believe part of my problem was I kept trying different updates one after the other. Now that I think back, the 2 times I got the update to almost work was after I turned off the device and turned it on again, which is what I did this time around also.
Click to expand...
Click to collapse
It seems you got the idea!
You did the right thing! Sometimes, use the official ROM can solve many issues out there!
Keep walking!
enlite_de said:
I had the same problems as mentioned by Ironman before. I followed the steps and with a few slight changes, I managed as well to "unbrick" my wiz. THANKS A LOT for the great step by step manual!!!
Still I wanted to know WHY i bricked my device:
I was trying to upgrade to the underground WM6 ROM. I got the same situation as ironman:
Quote:
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Unquote
I then followed the instructions by epimazzo as written above. I also tried the T-Mobile ROM 2.26 which was not working for me. PANIC!!!! Error messag was that I had the wrong Vendor ID. THerefore no upgrade to TMob 2.26 was possible. I tried it then my original qtek ROM in my language and see it worked!!! This IMHO means that I did not put the device in a proper IPL1.xx and SPL 1.xx status which is required for a clean system in irder to unlock it! So if it is bricked, try your native AKU2 ROM and make sure you unlocked it properly. Maybe you have to run the 1.05 ROM for a second time after the unlocking.
I hope this helps you guys.
Click to expand...
Click to collapse
Excellent post. I messed up with my own cooked ROM and could only get the bootloader screen. Tried the tips here - didn't work first time but I pulled the battery from the KJAM to reset it rather than using the reset button and it worked fine.
In my opinion this thread is so helpful to people who brick their device, it should go "sticky". Mods anything you can do about it?
Thanks buddy! I really appreciate!
We survive here over tips like that!
jt_armstrong said:
Excellent post. I messed up with my own cooked ROM and could only get the bootloader screen. Tried the tips here - didn't work first time but I pulled the battery from the KJAM to reset it rather than using the reset button and it worked fine.
Click to expand...
Click to collapse
Help me similar problem
I upgraded Super Rom, then my Wizard run very slow and no signal (no call out and in- no network at all). And Terible thing is PC could not dectect PPC thought Active Sync. I've soft and hard reset but no use.
So I donot know where to start to re install Rom again.
Please help me....
Hi there!
It seems that you just need to enter into the bootloader mode and reflash it again!
I had similar problems and more during my brick "false" stage!
So, just try to follow my steps here and you should be fine! Once you get into bootloader mode, just use any ROM out there to reflash.
Good [email protected]
thaiphong said:
I upgraded Super Rom, then my Wizard run very slow and no signal (no call out and in- no network at all). And Terible thing is PC could not dectect PPC thought Active Sync. I've soft and hard reset but no use.
So I donot know where to start to re install Rom again.
Please help me....
Click to expand...
Click to collapse
I was about to start a EMERGENCY HELP thread, but I *think* this is the right place instead.
The "touch" of my screen went dead today. It got progressively worse over a few hours, starting with difficulty in using the phone dialer, then random incorrect stuff getting triggered by screen taps.
So I hard reset, and got no response on the fifth alignment cross, meaning 1) "Tap on the screen...; 2) center; 3) top left; 4) bottom left; 5) bottom right. In that I could not proceed with alignment, I hard reset again, and now, at the first alignment screen, i.e. "Tap on the screen...", I have no screen response at all.
I called T-mo, and they are being great about sending a replacement ASAP (and getting me a loaner in the meantime).
BUT, I am running Faria+ AKU3.3 V2... so I clearly have to flash back to T-mo 2.26. I can;t figure out how to do it though, as no matter what I do I am stuck at the first alignment screen!!
HELP!! EMERGENCY!!!
(I have three or four days to get this done, so it's not THAT urgent)
Do a search for Broken Screen. Someone (either in Wizard Upgrading or in the Wizard forum) just had a similar issue with a cracked screen. They downloaded something that allowed them to get around the welcome page.
Actually, if you are just trying to flash a new ROM, don't even mess with it. Go straight to the Boot Loader screen (see the first post of this thread). No tapping necessary until the new rom is on (and that will be the Tmobile then so you would be good.
Thanks for the quick reply. Charging up to green now, and then will try to enter bootloader and flash T-mo 2.26. Will report back.
Worked great. Back to T-mo she goes!!!
BootLoader Mode
Excellent thread but you left out one thing.....exactly how to place your device in bootloader mode.
To clear up any misunderstanding because this is very important....this is how you do it:
Perform a soft reset, when the screen goes blank hold the camera button until a multi colored screen comes up .... That's it !!!!!!
When the unit is connected, USB is displayed at the bottom left.
I cant believe this....I had no issues all day upgrading the ROM...until my PC overheated and shut off at 57%...
now when my phone starts up I see the 3 bars and it sais USB in the bottom left...but active sync is not connecting!
help!
what 3 bars?
a Red Blue Green Bars color?..
If that so.. you are too lucky..
I read a little more on the wiki:
Type 2a: When the phone boots, it goes directly to bootloader mode (tri-color screen)
This is what I have right now...I can't seem to get active sync to connect...although at the bottom of the screen it has "USB"
I have tried using mtty and dont think its diong anything...
Just stay in the bootloader (tri-color screen) and make sure the "USB" is shown in your device screen..
The reflash.. even if its not sync/connected.. just reflash the ROM..
Everything will be fine..
wow....i think it may actually work....that was SCARY.
nice to know the good ole button flash works when all others fail
I just want to make a clarification..
You are just flashing your device and when the upgrade process is on 57% your computer suddenly shutoff? and the upgrade was cut..
What happened next? did you reset the device then went to tri-color screen? or you just force bootloader mode it?
Yeah pretty much exactly what you said. I literally got up for a second to get some water, came back and saw the telltale sign that my pc had just shut itself off (the screen was black except for the standard boot junk that shows up).
So I look at my device (8125) and it was locked at 57% and was not responsive. I figured that the flash util probably wouldn't continue after the computer started back up (and besides, the device wasn't alive anymore) so I rolled the dice and unplugged the USB and took out the battery. When I put the battery back in and hit the power button, it went straight to the bootloader (the tri color screen).
- By the way - ive got the button image on here now - workin like a champ...
tnx for the explanation..
have fun!!..
thanks for the quick reply - i thought i was completely stuck but the button flash seemed to take care of everything. Makes me almost think that bricking this thing is near impossible... >
Yup!.. that also my conclusion.. its impossible to brick.. thats why i ask for your clarification..
What is this "button flash"? I am stuck in RGB boot mode with no activesync connection. I have read til my eyes crossed, but can not fix my 8125 (G3)!
Please advise.
How about more information? On your bootloader (Rainbow screen) what does it show the IPL / SPL to be? What were you trying to do when you got into this situation? What happened when you were flashing? Is your device a G3 or G4?
Safest thing for you to do right now is to flash your carrier's rom onto the phone (an official shipped ROM). With your phone in the bootload, just run the ROM and it will install (DO NOT RUN A CUSTOM ROM AT THIS POINT SINCE YOU HAVEN"T TOLD US ANY OTHER INFORMATION).
G3 8125
ipl/spl 2.25
Was trying to use faria's latest rom...got stuck at 99% for almost one hour, so I rebooted computer and discon'd the wizard. Now it will boot to rainbow screen and will not connect via activesync (so I can't utilize any other roms to get back to square one).
ActiveSync will NOT connect when you are at the boot loader. As long as you see USB in the bottom left of your phone (above the left soft key) then you can flash your original Cingular ROM and be good to go again.
brick, brick, brick
It happend to me too with faria´s new crossbow rom:
the device freezed at 99% and I reseted it then....nothing happend- bootloader mode: red green blue + usb... but no chance to flash ANYTHING... always the same message:ERROR (260) update error, no connection to the device...???
I tried the O2-mini s update, and the faria rom, no chance just a brick
I need help....
Hunter6 said:
It happend to me too with faria´s new crossbow rom:
the device freezed at 99% and I reseted it then....nothing happend- bootloader mode: red green blue + usb... but no chance to flash ANYTHING... always the same message:ERROR (260) update error, no connection to the device...???
I tried the O2-mini s update, and the faria rom, no chance just a brick
Click to expand...
Click to collapse
Why did you reset it??? All roms freeze. The screen that is flashing the ROM even says it can take up to 10 mins. If you don't get an error onthe PC then DON'T stop the flashing process.
Go get a copy of your carrier's official ROM (not a custom one, but an official one from your carrier.). Then with the phone at the boot loader (Rainbow screen) and the USB cord plugged, in, run the official ROM. If that doesn't work, then get a copy of the Wizard Love rom and flash it (You'll need to find links around here for it, or pull it via PirateBay). You may also want to reboot the PC you are running on and remove your SD card (if you have one) just to remove variables that can play in to all of this.
Good luck
mfrazzz said:
Why did you reset it??? All roms freeze. The screen that is flashing the ROM even says it can take up to 10 mins. If you don't get an error onthe PC then DON'T stop the flashing process.
Click to expand...
Click to collapse
Ten minutes is understandable, but mine stalled for about an hour at the 99% mark. Even my PC would not respond. Is that normal for a rom upgrade?
-----
I was finally able to reset my 8125 to the Cingular ROM. Not sure why I couldn't do it on my PC, but after moving over to my wife's PC I did not have any problems.
Thanks!
brick, brick, brick
o.k. boys, now it is a nice little crossbow brick from faria.....and I can make telefon-calls with my brick.
thanks a lot for your help
entdiablo said:
Ten minutes is understandable, but mine stalled for about an hour at the 99% mark. Even my PC would not respond. Is that normal for a rom upgrade?
Click to expand...
Click to collapse
No, that sounds like your pc locked up or something (I'd blame windows on that one )
I was finally able to reset my 8125 to the Cingular ROM. Not sure why I couldn't do it on my PC, but after moving over to my wife's PC I did not have any problems.
Click to expand...
Click to collapse
Glad to hear you got it going. Good luck and be careful out there!
Hunter6 said:
o.k. boys, now it is a nice little crossbow brick from faria.....and I can make telefon-calls with my brick.
thanks a lot for your help
Click to expand...
Click to collapse
Sorry, I may be missing your humor or sarcasm... Are you saying its dead (if so, give more details about what it does or doesn't do, IPL/SPL it shows (if it turns on), etc... If its now working, then congrats!
A while ago I tried to Flash a version of WM6 from mfrazzz on my wizard. The installation seemed to go ok, but when I boot it up i coudn't get past the second splash screen. I thought the phone was a gonner until last night, when I gave it another shot putting on Button ROM. I followed these instructions and it worked. The instructions also had me unlock the phone, and that worked fine too. after that I tried updating my IPL and SPL, Right now my IPL is 1.05 and SPL is 3.08
After this I tried unsuccessfully to get WM6, I think I started off trying Faria.
(So here is the actual problem)
After I tried installing Faria unsuccessfully, I couldn't get Button ROM back up. I'm stuck on the second splash screen (picture of a mug of beer in front of the Colosseum). I've tried flashing my phone w/ everything i've got, including button ROM and Love, and nothing works. most of the WM6 Update Utilities won't even connect. Button Rom connects, stalls at 98%, finished and says it was a success, but I'm still hung up on the Splash.
(I'm running WinXP w/ SP2)
I really just want something running on this phone, don't care what it is.
Thank you for your time
Download official stock rom to recover back and download WST_4.2.2 to verify the CID lock/unlock status,most probably its still CID locked.or you can even reflash 'Button's Rom' again.
No, I've tried to reflash button rom many times. It says it works but it gets hung up on the splash. Since I can't get anything to run on it WST won't work (I think)
Yes! WST only works on a working OS,have you tried to flash the official stock rom ?
Don't activesync or establish partnership,better if you altogether disable & close activesync and end process 'WCESCOMM.EXE' in the Task Manager and try to end as many applications running at the background.Don't surf the net,disable all anti virus and firewall.
Simply get the phone into Bootloaders mode,hook up with pc via usb cable,watch small usb appear at the bottom of Bootloader screen and run the Rom,hope it'll work.
hEY ZABARDAST
zabardast_1 said:
Yes! WST only works on a working OS,have you tried to flash the official stock rom ?
Don't activesync or establish partnership,better if you altogether disable & close activesync and end process 'WCESCOMM.EXE' in the Task Manager and try to end as many applications running at the background.Don't surf the net,disable all anti virus and firewall.
Simply get the phone into Bootloaders mode,hook up with pc via usb cable,watch small usb appear at the bottom of Bootloader screen and run the Rom,hope it'll work.
Click to expand...
Click to collapse
I did this when my Wizard stucks on the splash...
Get mtty 1.04 i thin i dont remember exactly but the higher i ever saw.
kill process wcesscom in PC
conect the ppc on Bootloader
click on conection it shows USB if not... start up again the process
then a white screen appears
I type: task 28
then it works a little on some memory directions
I type: task 28 55aa [or something] (its better get the info on wiki cause it works on chip directly)
without unplug the PDA starts the RUU again...
It works for me...
This is a process for HTC Universal but it works on Blue angel and Wizard for sure!
wait a little i will confirm the steps and the exactly words to type in.
you might need clean the ROM or your flash ROM is overcooked.
I can repair your phone !
+ Que PPC said:
I did this when my Wizard stucks on the splash...
...
wait a little i will confirm the steps and the exactly words to type in.
Click to expand...
Click to collapse
Hey + Que PPC!
Have you confiirmed those values? And is your Wizard CID unlocked?
This would be great to confirm working so that all those with CID locked devices could get their phones back - without paying IMEI-check.co.suckourmoney.uk
@ twig2256
If your phone is CID unlocked try Drugstore's method of recovering Splash Screen frozen phones
cheers
YES
The values are the same for every DOC CHIP
When the MTTY conects to USB type exactly this...
task 28
(then it will work formating and cleaning the DOC
then it says succesfully clean
and now type...
task 28 55aa
it again works on the same process you can close the mtty without unplug your device... update your device with a Stock rom.
Actualy I have issues with mtty i dont know why i can acces to USB it say CMD GOD Damn can anybody helps...
This is the link that mestrini said for drug gsm store metod to unfreeze
http://forum.xda-developers.com/showthread.php?t=276963
Hey mestrini see this...
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader
even if it is universal it work for Wizard i did it once it works for me. but now it wont why????
zabardast_1 said:
Yes! WST only works on a working OS,have you tried to flash the official stock rom ?
Don't activesync or establish partnership,better if you altogether disable & close activesync and end process 'WCESCOMM.EXE' in the Task Manager and try to end as many applications running at the background.Don't surf the net,disable all anti virus and firewall.
Simply get the phone into Bootloaders mode,hook up with pc via usb cable,watch small usb appear at the bottom of Bootloader screen and run the Rom,hope it'll work.
Click to expand...
Click to collapse
can't solve my t-mobile mda
Hi,, I have used shelltool to install TNT 6.1 from wizlove all went smooth
Then i decided to try a different radio so flashed 02.71.11 from o2.37.11
all went smooth no problem,, It wasnt a day and I had to get rid of 02.71.11
so tried flashing to others and ruu loses conection on status bar and screen goes into the tri col mode,, since then I have tried to do hard spl and it gets as far as the white screen and then ruu says lost connection, so I used shelltool to flash back to wizlove but after reboot stuck on splash screen
I can get into the tri colour bootloader screen the usb shows but cant get any connection to ruu
Im G4, ipl 2.16.0001
spl 2.16.0001
gsm 02.71.11
os 2.26.10.2
help me please head is sore from reading too much
Thanks
What IPL/SPL it displays now and which windows are you doing on? If its vista it won't work.WinXP is highly recommended for HardSPL.Don't use Shelltool go for HardSPL or SoftSPL.
zabardast_1 said:
What IPL/SPL it displays now and which windows are you doing on? If its vista it won't work.WinXP is highly recommended for HardSPL.Don't use Shelltool go for HardSPL or SoftSPL.
Click to expand...
Click to collapse
ipl spl as posted,,,,,I have already used shelltool to load TNT and then I tried to run hard spl but ruu says lost conection on white screen so I used shelltool to go back to wizlove but on reboot it is stuck on splash screen, and Im on xp
Ah ! yes,its G4,ok,HardSPL won't work in Bootloaders (tricolor) it'll only work if working OS is running.
Which windows are you on vista or winxp ?
Im on xp,, but as I have posted Im now stuck on splash screen
It is almost bricked
So try to reflash an original ROM dont install wizlove (it wont be a diference but...) in RGB try to run the RUU from original EXE package id dont works is almost bricked.
Try to get a backup from another device fully functional following the steps indicated by Drug store on splash screen stucks solution DIY thread if dont works or you dont have a backup Minisd so try the MTTY...
I am CID locked G4
Download Official k-jam stock rom from the below link and flash it in Bootloaders,recover back to default status and than proceed further:-
http://www.imate.com/Support_DeviceSupport.aspx
G4 devices cannot be CID unlocked like a G3 phones,in this situation only official stock rom will get flashed,it contains IPL/SPL for both the devices,it shud flash and work.Than after recovering back ,Apply 'HardSPL' to semi-CID unlock the phone and upgrade to any wm6 rom,don't use Shelltool,it sometimes creates problem.
I don't think Backup rom through minisd with MTTY will work in this situation, but than, thats me !
OK I got the official rom, but same problem RUU says it hasnt got a connection the phone is in tricol boot load at this time, I think the issue is how to get a comunication between the RUU and the wizard in in Tricol mode surely someone has an answer on this?
OK.... it seems to be your PC...
When you plug your device via usb in the pc port the dev shows USB bottom left on screen... ? Does the PC shows you "Unknown device, please intall the drivers... or has a bad function"?
The USB cable... maybe your battery is low.... maybe the USB PORT... i dont imagine anymore problems... Try to get a full batt.. other USB cable and other PC XP of course... and retry.
OK a glimmer of hope,, I switched to another usb port windows loaded driver etc, then i ran the official rom ruu and,,,,,,,,,,,,,invalid ID cant run this utility,
does this mean I need the original software and how would I know what version that was,,,,,,,,cause I wasnt making notes
DAMN!!!!
OKJAM said:
OK a glimmer of hope,, I switched to another usb port windows loaded driver etc, then i ran the official rom ruu and,,,,,,,,,,,,,invalid ID cant run this utility,
does this mean I need the original software and how would I know what version that was,,,,,,,,cause I wasnt making notes
Click to expand...
Click to collapse
FIIIUUUUU!!! it seem that you have comm conection betwen the RUU and the device... but Wrong ID?
Download the file zabardast told you... it is from your carrier.
If this is the one u have tried...
so try another one... from Tmobile prodigy 2.26... or from qtek 9100 2.19 official Stock ROMS.
OKJAM said:
OK a glimmer of hope,, I switched to another usb port windows loaded driver etc, then i ran the official rom ruu and,,,,,,,,,,,,,invalid ID cant run this utility,
does this mean I need the original software and how would I know what version that was,,,,,,,,cause I wasnt making notes
Click to expand...
Click to collapse
hmmm,ok,download this RUU attached and extract it, replace this RUU with the RUU in the official rom and run this RUU from the Rom,hope it'll flash.
Or,download the K-jam official stock rom from here :-
ftp://ftp.clubimate.com/K-JAM_WWE_21...20710_ship.zip
I tried all that and still not getting anywhere, constantly the same problem re connection I do get the found new hardware when trying different usb ports but the ruu complains " no connection" I cant seem to get what it did before in terms of getting further to the point where it told me invalid ID I will have to try another pc with xp but dont have one handy
Might not be bricked..
check out this thread, it might be of help
HELP PLEASE!!
Ok so i think i bricked my wizard!
I have the t-mobile MDA wm5 unlocked g3.
I've flashed it to the WM6 Rom and everything had been working well, except there was no MMS feature on the phone at all which sucked! . My girlfriend thought it would be better if she did the "windows mobile update" icon feature that was on the phone to speed up the phone....She downloaded the updates & my phone shut off!! When it rebooted everything seemed normal...
1st.
T-mobile screen
IPL 2.26
SPL 2.26
GSM 02.25.11
OS 10.1.0.811
-Then i get the green windows mobile splash screen, but after i get an error message!!
*Device Authentication*
“Device authentication failure. Please contact the product manufacturer. For reference, please provide your device ID.
3563820017905901 38000050bf3f5173”
Ive tried to boot in safe mode to try & flash my phone again but for sum reason my computer wont recognize my phone is plugged in! What do i need to do?!? Please help, any help is thankful!
is not a bricked wizard men
easy men easy... but please tell to your girl dont push everything that she dont nderstands... Everybody knows that upgrade official is only for original OS like windows XP or VISTA..
Firs of all
Put your Wizard on bootloaders mode... plug in via usb the PC Active sync wont recognize your phone.. then run the original shipped Stock ROM and then your Coocked rom...
But if the PC at the same time you place your Device on Bootloaders and plug it via USB... shows a pop up message that said Windows cant recognize your device or unknown device or something... Restart your Pc... Hard reset your PDA... and replug your Device as I said it before... if not check your USB cable maybe a broken cable failure...
IF NOT?????!!!!!!!! then Use another PC with XP!!!!!
If it still on his not reconized message you are in serious problem but your girfriend Too...
Good luck
Easy..."Device Authentication failure" is caused by your ROM. Just flashing another custom ROM and the message should go away.
I'm surprised that the chef that made your WM6 rom left the Windows Update feature in there, it was bound to crash a cooked rom, since the update service never worked properly anyway.
I'm sure flashing another rom will resolve this.
yeah, flash the rom (you might want to try WizFlo 20273 v6.1.1.3 - i'm on it, and loving it). heck, you can even do a hard reset and that would probably resolve it.