Related
I've been trying to get my old extended rom and new Qtek OS on my Wizard (Vario).
But now it gets stuck in the spash screen (ie the one giving the ROM numbers).
I've tried putting the wizard into bootloader mode and I can flash RUU's but when it resets it still gets stuck on the spash screen and won't go any further !!!????
What can I do ??
Please Help
Cheers
John
I should say that I had flashed using button's ROM RUU_Wizard_1050412_WWE_101_11210_WWE.exe.html
and this worked fine!
I then copied across my T-mobile Extended ROM and again everything seemed OK.
BUT then I tried to restore my new saved OS ROM using aWizard and this caused a freeze on my Wizard. It was after a hard reset that the wizard stopped at the splash screen.
Now of course I'm limited in my options because Activesync won't work until the Wizard has fully booted up.
I have tried setting the Wizard into bootloader mode and tried several ROM's (RUU Installer ones) but every time the correct splash screen comes up with the new ROM numbers but that is as far as it gets.
I also noticed on hard reset that you get the following message
Format FAT partition
Format failed
it then goes to the splash screen as before.
Are there any other things I can try Or will I have to send it back to T-mobile for a replacement??
(It's only 2 months old and I have re-flashed it with the orginal T-mobile ROM - but still won't go past the splash screen!!)
I live in hope
John
I have this EXACT same problem!
I can reflash any ROM but it will not go past the splash screen. Only difference was I wasn't playing with my extended ROM. I flashed the AKU2 QTEK ROM yesterday and have been fine through several soft resets, etc. This last time I was uninstalling phonealarm and after a soft reset I got a "could not find smswakeup.exe" (or something similar) and it's been stuck ever since! I also get the "Format Failed" message. Can anyone help!?
I think I'm going to have to send it back to T-mobile and hope they give me a replacement. Something is wrong, it doesn't seem to make any difference what ROM I used.
I think I'll reload the T-mobile shipped ROM grom the FTP site and send it back - and claim ignorance that it it suddenlt freezed and now won't boot up! - Bummer!!!
Right I've logged a fault and it will be sent back - let's hope T-mobile can't detect it's been unlocked and had several ROM updates - I suspect they will try a ROM update themselves then give up ???
The worrying thing though is that it IS possible to kill your phone with updates - maybe it was when I used aWizard to try and restore a ROM that did it??? I'll be more carefull next time!!
this has just happened to one of the devices im flashing at the moment.... absolulty f**king raging :evil: :evil:
i wish teher was a solution!!? anyone got any ideas?
activesync wont find it, so aWizard wont work.
i can flash between 3 roms without any problems (1.5.x 1.6.x 2.x) but always hangs on the splash screen. i have flashed back to the default rom that it came installed with it so i could just send it back to o2 (only 2 days old!)
i would rather just get it sorted by myself thoough so if anyone has ANY ideas then please let me know.
thank you!
Good luck! after about 3 days of trying different types of firmware, I gave up and sent it to expansys, for repair. And it looks like they've lost the bloody thing now. :evil:
tonym001 said:
Good luck! after about 3 days of trying different types of firmware, I gave up and sent it to expansys, for repair. And it looks like they've lost the bloody thing now. :evil:
Click to expand...
Click to collapse
yup looks like i might have to give up... ohwell, no worries i will just return it back to O2...
looks like one of our sales guys wont be getting a new phone on tuesday :lol:
same problem here.
tryed to write os with awizzard after changing extended_rom.
kills phone.
format failed..
Tryed different os's from win util - failed
upgraded with sd card methode worked.
in short :
you need a working wizzard to make a os dump on sd card.
Connect to wizzard with usbterm or romupdate.exe or simular.
do a rs2all command to dump os to sd card.
stick this card in broken phone.
hold voice comm button while resetting.
On ask press voice comm button again.
it bow restores the sd backup to phone.
saved mine.....
btw sd card backup can be read ad write by pc with util ntrw.exe .
so if you don't have a working dump i can upload one.
just mail me.
grtx , arnold
hard reset your device and hold your Camera Button prior to starting the wizard back on.
when the device turns back on, you will get the boot screen. Plug in your USB cable and load one of the known ROMS like the second to last iMate ROM.
This will allow you to get past the splash screen.
FarSeide said:
hard reset your device and hold your Camera Button prior to starting the wizard back on.
when the device turns back on, you will get the boot screen. Plug in your USB cable and load one of the known ROMS like the second to last iMate ROM.
This will allow you to get past the splash screen.
Click to expand...
Click to collapse
this didn't work for me.
couls flash rom. even splash screen changed to new roms one.
but still stuck at splash...
tried it with about 4 different orgigenal roms
grtx arnold
arnoldl said:
FarSeide said:
hard reset your device and hold your Camera Button prior to starting the wizard back on.
when the device turns back on, you will get the boot screen. Plug in your USB cable and load one of the known ROMS like the second to last iMate ROM.
This will allow you to get past the splash screen.
Click to expand...
Click to collapse
this didn't work for me.
couls flash rom. even splash screen changed to new roms one.
but still stuck at splash...
tried it with about 4 different orgigenal roms
grtx arnold
Click to expand...
Click to collapse
Don't worry, I met the same problem as you before, almost lost my hope, but finally I managed to fix it.
The solution is simple, that is to find an original SD card backup image from your wizard or others, then try to restore it in the bootloader mode. In my case, it said checksum error or sth else after begin restoring, and it gave up. Then I put my wizard into bootloader mode, picked one offical released RUU package, start reflash again. Finnally, I found the wirzrd works again for me after reboot.
I guess the principle is that the SD restore will destroy some import flash data structure before it said wrong, then the RUU package will rebuilt it wholely in the next reflash.
Hope this helpful, and sorry for my bad english.
There is hope
Last week after trying to downgrade to the original Cingular ROM on my 8125 using aWizard I ended up with a device that was close to being a paperweight. At least I thought so until I read and read and finally was able to get it to the bootloader and then plugged in the USB cable and ran the RUU for the new Qtek ROM (2.17). Guess what happened, yeah it worked. To my surprise I had a perfect device after 15 minutes.
For about 3 hours I thought I was a toast. Never will I do that again.
THIS is truly heaven for me !!
I have my O2 XDA MINI S locked on the splash screen .. and i updated some ROMS to it ....BUT IT DOESNT GET THROUGH IT .... please tell me what to do in a little detailed manner .. please so that i can get my phone to work.. there is no warranty on the phone and i stay IN INDIA . SO YOU'LL ARE MY ONLY HOPE .
my email id is - [email protected]
If you have a dump of the O2 XDA MINI S ..please mail it to me
Plese tell me what to do next ? WILL TRULY APPRECIATE HELP
PLEASE SOME ONE ATLEAST MAIL ME the dump of the os SO THAT I CAN TRY THE SD CARD UPGRADING ,.,,, O2 XDA MINI S
Re: There is hope
Dear Friend
I have problem that my xda mini s stuck on O2 screen, could you help me step by step.
Thank you so much
my mail : [email protected]
Thanks friend
hellomoto_25 said:
Last week after trying to downgrade to the original Cingular ROM on my 8125 using aWizard I ended up with a device that was close to being a paperweight. At least I thought so until I read and read and finally was able to get it to the bootloader and then plugged in the USB cable and ran the RUU for the new Qtek ROM (2.17). Guess what happened, yeah it worked. To my surprise I had a perfect device after 15 minutes.
For about 3 hours I thought I was a toast. Never will I do that again.
Click to expand...
Click to collapse
Dear Friend
I have problem that my xda mini s stuck on O2 screen, could you help me step by step.
Thank you so much
my mail : [email protected]
Thanks friend
odyseus said:
I've been trying to get my old extended rom and new Qtek OS on my Wizard (Vario).
But now it gets stuck in the spash screen (ie the one giving the ROM numbers).
I've tried putting the wizard into bootloader mode and I can flash RUU's but when it resets it still gets stuck on the spash screen and won't go any further !!!????
What can I do ??
Please Help
Cheers
John
Click to expand...
Click to collapse
stuck on o2 screen helppp
Dear Friend
I have problem that my xda mini s stuck on O2 screen, could you help me step by step.I see alot of post, so complicated
Thank you so much
my mail : [email protected]
Thanks friend
flexchen said:
arnoldl said:
FarSeide said:
hard reset your device and hold your Camera Button prior to starting the wizard back on.
when the device turns back on, you will get the boot screen. Plug in your USB cable and load one of the known ROMS like the second to last iMate ROM.
This will allow you to get past the splash screen.
Click to expand...
Click to collapse
this didn't work for me.
couls flash rom. even splash screen changed to new roms one.
but still stuck at splash...
tried it with about 4 different orgigenal roms
grtx arnold
Click to expand...
Click to collapse
Don't worry, I met the same problem as you before, almost lost my hope, but finally I managed to fix it.
The solution is simple, that is to find an original SD card backup image from your wizard or others, then try to restore it in the bootloader mode. In my case, it said checksum error or sth else after begin restoring, and it gave up. Then I put my wizard into bootloader mode, picked one offical released RUU package, start reflash again. Finnally, I found the wirzrd works again for me after reboot.
I guess the principle is that the SD restore will destroy some import flash data structure before it said wrong, then the RUU package will rebuilt it wholely in the next reflash.
Hope this helpful, and sorry for my bad english.
Click to expand...
Click to collapse
how to use bootloader
could you tell me how to use mentioned bootloader for restoring the images? where can I get the software?
Please help
Hendrick
flexchen said:
arnoldl said:
FarSeide said:
hard reset your device and hold your Camera Button prior to starting the wizard back on.
when the device turns back on, you will get the boot screen. Plug in your USB cable and load one of the known ROMS like the second to last iMate ROM.
This will allow you to get past the splash screen.
Click to expand...
Click to collapse
this didn't work for me.
couls flash rom. even splash screen changed to new roms one.
but still stuck at splash...
tried it with about 4 different orgigenal roms
grtx arnold
Click to expand...
Click to collapse
Don't worry, I met the same problem as you before, almost lost my hope, but finally I managed to fix it.
The solution is simple, that is to find an original SD card backup image from your wizard or others, then try to restore it in the bootloader mode. In my case, it said checksum error or sth else after begin restoring, and it gave up. Then I put my wizard into bootloader mode, picked one offical released RUU package, start reflash again. Finnally, I found the wirzrd works again for me after reboot.
I guess the principle is that the SD restore will destroy some import flash data structure before it said wrong, then the RUU package will rebuilt it wholely in the next reflash.
Hope this helpful, and sorry for my bad english.
Click to expand...
Click to collapse
Hi Arnold
My O2 cda mini s get stuck at splash scree, I read your post, still not so understand how to solve it, could you be so kind to write me step by step, and send me some software to solve it. Your help will be so much appreciated.
Hendrick
Email: [email protected]
arnoldl said:
same problem here.
tryed to write os with awizzard after changing extended_rom.
kills phone.
format failed..
Tryed different os's from win util - failed
upgraded with sd card methode worked.
in short :
you need a working wizzard to make a os dump on sd card.
Connect to wizzard with usbterm or romupdate.exe or simular.
do a rs2all command to dump os to sd card.
stick this card in broken phone.
hold voice comm button while resetting.
On ask press voice comm button again.
it bow restores the sd backup to phone.
saved mine.....
btw sd card backup can be read ad write by pc with util ntrw.exe .
so if you don't have a working dump i can upload one.
just mail me.
grtx , arnold
Click to expand...
Click to collapse
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 tried reflashing my IMATE KJAM to WM6
The process went till 35% and then got disconnected.
Now its stcuk on the Bootloader Screen(Three colors screen)
Tried the Hard Reset(comm mann+voice button+reset)
It doesnt do a hard reset, the same screen flashes back again.
Tried reflashing i get the Error 300
The previous ROm was crossbow underground edition.
Please help and let me know whats next that i can do.
paraozzy said:
I tried reflashing my IMATE KJAM to WM6
The process went till 35% and then got disconnected.
Now its stcuk on the Bootloader Screen(Three colors screen)
Tried the Hard Reset(comm mann+voice button+reset)
It doesnt do a hard reset, the same screen flashes back again.
Tried reflashing i get the Error 300
The previous ROm was crossbow underground edition.
Please help and let me know whats next that i can do.
Click to expand...
Click to collapse
You know what the totally histerical thing about this is? This is the exact same reason I made my first post. LOL.
Alright I'm gonna try to help you seeing as how it doesn't look like too many others are looking here.
I have several questions first before I can help you.
1. Who is your wireless service provider? IE: T-Mobile, Cingular, Etc...
2. What Is your IPL/SPL?
Answer these 2 questions for me and I will be able to better help you.
Thanks for the quick reponse
Now the irony is i am here in nepal and i use the phone as a simple mobile phone, but as far as i know i remember flashing a T-Mobile ROM while upgrading to WM6, the IPL and SPL both are 2.26, i unlocked the device while upgrading..
Thanks
Kushal
paraozzy said:
I tried reflashing my IMATE KJAM to WM6
The process went till 35% and then got disconnected.
Now its stcuk on the Bootloader Screen(Three colors screen)
Tried the Hard Reset(comm mann+voice button+reset)
It doesnt do a hard reset, the same screen flashes back again.
Tried reflashing i get the Error 300
The previous ROm was crossbow underground edition.
Please help and let me know whats next that i can do.
Click to expand...
Click to collapse
Hey!
ok lets c if I may be of some help here,if u r in bootloader screen than try to reflash again T-mobile 2.26 rom and if it goes alright than go on to flash any other wm6 cooked roms.
or
if it doesnt flash than i wud suggest u reflash back the buttons 105 rom to get back to ipl/spl 1.05,than again use lokiwiz tool to unlock cid & reflash T-Mobile to gain ipl.spl 2.26
hope it works out.it happened once with me also, I did the same & now I'am running wm6 XM6r3 Rom,Secondly u can use the WST TOOL by Mestrini to verify ur device status, u can even Cid unlock ur device with it, Goodluck
Yup man flashing the T-mobile 2.26 did the job..
Great thanks for the same..
paraozzy said:
Yup man flashing the T-mobile 2.26 did the job..
Great thanks for the same..
Click to expand...
Click to collapse
glade you got it up and running good luck and happy flashing
This morning my phone had frozen up on me, so I did a soft reset on it, when it got to the Windows Mobile screen it just stays there, so I soft reset again, and same thing, So I finally decided to do a hard reset, and nothing. It continues to keep getting stuck on the windows Mobile screen, does anybody have any idea as to what I can do, the phone is out of warranty already so it cant be replaced, can I load WM6 again? Please help out, Thanks
Have you tried to re-flash? Be sure to use the official ROM for your particular carrier. If your carrier has not released one then try one of these: http://forum.xda-developers.com/showthread.php?t=335402
Good luck!
tmknight said:
Have you tried to re-flash? Be sure to use the official ROM for your particular carrier. If your carrier has not released one then try one of these: http://forum.xda-developers.com/showthread.php?t=335402
Good luck!
Click to expand...
Click to collapse
Thank you for your help, I will give that a try when I go home tonight.
I've searched and asked for help for months and I can't find anything.
My Sprint Touch Diamond is F'd. I tried flashing an unofficial ROM to it, and on the reboot process, it won't turn back on. In fact, it constantly resets...every time I turn it on, or even placing it on the charger it will turn itself on and keep resetting.
I need to know if it's bricked or if there is anyway of getting it to work again. Someone please please please help, im pretty desperate for advice. Thanks in advance.
Did you install the HardspL? Anyways try to hold down the volume down button and the power button while you push the reset button. If it brings you to a multi-colored screen connect it to the USB and flash another Rom. Make sue it is a CDMA if your phone is CDMA.
Yeah, if you can get it into bootloader you should be able to reflash the shipped rom from your carrier. Use the exe. I would flash it at least twice.
i believe its cdma. it was brand new from sprint.
Lawler said:
I've searched and asked for help for months and I can't find anything.
My Sprint Touch Diamond is F'd. I tried flashing an unofficial ROM to it, and on the reboot process, it won't turn back on. In fact, it constantly resets...every time I turn it on, or even placing it on the charger it will turn itself on and keep resetting.
I need to know if it's bricked or if there is anyway of getting it to work again. Someone please please please help, im pretty desperate for advice. Thanks in advance.
Click to expand...
Click to collapse
Hi Lawler read this first >>> Click Here
Then Here >>> Click Here
HTC Stock Rom >>> Click Here
If you can get into bootloader mode(press vol down + power)until you see the tricolor bars then you're ok you can either flash the stock rom or unlock it then install a custom rom.
HTH
ive searched these forums for an answer for months and have found nothing, It wont go past the boot screen. Ive tried about ten different roms, which have worked before. Hard reset doesn't do anything, and MTTY is a joke. I am willing to pay anyone who can help me get this thing working, im a desperate man at the moment!
ive searched these forums for an answer for months and have found nothing, It wont go past the boot screen. Ive tried about ten different roms, which have worked before. Hard reset doesn't do anything, and MTTY is a joke. I am willing to pay anyone who can help me get this thing working, im a desperate man at the moment!
Click to expand...
Click to collapse
Can you get it into the bootloader? If you cant then your probably out of luck. If you can, flash HSPL, unlock your phone, and flash a ROM.
Sent from my XDANDROID using the XDA mobile application powered by Tapatalk
Yes, it goes into the bootloader. I've flashed a hard spl, it's unlocked. I just tried your rom that makes 12 that I've tried. The same thing happens. The phone turns on to the Touch DIAMOND screen with the red rom info on the bottom and it will not go any farther. Hard resetting does the same thing. I've tried using MTTY, I've tried stock sprint roms.
I know i can get it to work. This same thing happened before and my diamond didnt work for months. One day i decided, ill give it another try and flashed pegasus 6.1 and it worked like a champ ever since. I tried like 4 other roms too and they worked just fine.
I was using PMD's 2.5 rom when it crashed. I deleted all of my text messages, and then the phone froze and didn't turn back on. When I tried to reflash the rom is where im at now...stuck in the boot screen.
I've never been in the bootloader on my Diamond myself, it won't open
If there are diagnostics tools, try them out. Also try flashing on a different PC and OS or with a different cable. Disable antivirus software may also help.
I think I'm sol man. Still no luck.