Related
I was running xelencin's latest custom rom. I have used his previous versions and all was good.
This one hung at 98%. I was just letting it do its thing when out of nowhere, BSOD. So now my phone is just sitting at 98%. I thought there was a forum post here about recovering but I'm not able to find it.
Thanks.
Update: After a soft reset, I am back to the multicolor screen. When I plug it in, it says USB in the bottom left hand corner. Device manager shows a PocketPC USB Sync device as well.
When I perform a hard reset (Comm Button + Voice Dial held, then press soft reset with stylus), I am taken right back to the same multicolor screen.
You're at the bootloader.
This is a Good Thing(tm).
At this point, you should be able to rerun any (assuming you are CID unlocked) any RUU ROM upgrade. Let it do its thing and you'll be good to go.
gamescan said:
You're at the bootloader.
This is a Good Thing(tm).
At this point, you should be able to rerun any (assuming you are CID unlocked) any RUU ROM upgrade. Let it do its thing and you'll be good to go.
Click to expand...
Click to collapse
For those that get stuck here in the future:
I had to extract the installer so as I could get past the CID unlock. I then ran "ROMUpdateUtility_Wizard_NoID.exe" and all went well!
rosewood said:
For those that get stuck here in the future:
I had to extract the installer so as I could get past the CID unlock. I then ran "ROMUpdateUtility_Wizard_NoID.exe" and all went well!
Click to expand...
Click to collapse
Yep, I went thru the exact same thing yesterday when trying to upgrade to 2.24. My PC decided to shutdown (not restart, a complete instant shutdown!) at 8% flashing. I decided to grab the "Mr Clean AKU2.3 ROM" which already had the ROM flash program available separately and then just put in the .nbf file I wanted and it was good to go
if your not cid unlocked, then what? xtract what? to wherehow can i transfer any thing, it seems though the device screen says usb, the avtivesync doesnt detects my phone. n?m, ive got it
What happen when your not CID unlocked? I had removed my hardspl before I tried to again flash a rom. I am stucked with the bootloader now...
Pls help
xpxj said:
What happen when your not CID unlocked? I had removed my hardspl before I tried to again flash a rom. I am stucked with the bootloader now...
Pls help
Click to expand...
Click to collapse
Only Official stock rom or the wizard_love rom will get flashed,no other wm6 rom is possible.
ok...i got the error from upgrading from 2.17 hacked rom to the 2.26 official rom. tried to read whatever i can but looks like solutions were given for cingular ipl etc...
can someone help me out? when i run the official rom, it updates to 1% and then i get the nbf error. i tried to run loki but mda not recognized by my usb connection.
stuck now...please help!!!
actually, tried to run machinagod's RAPI unlocker..but MDA not recognized as connected...this was part of xelencin's 2.24 rom updater.
please help!!!
Hi,
you must provide more information if you want someone to help you.
First and most important: what does it mean your phone is stuck? Stuck where? Does the screen come on? Can you get the bootloader screen? (for the bootloader screen: hold the two keys on the right side of the device and press shortly the reset hole; if you see the three colors screen then you have the bootloader!)
bye
i get the screen with the 3 colors, and usb at bottom left. when i run the official t-mobile 2.26 update, the screen goes gray and there is a bar with % done. when that kicks in, i get 1% done then it stops. on my computer screen, i get the nbk error, saying the nbk file that i have is not for my phone.
i looked for fixes but all the fixes require activesync connections which i am unable to connect with. just fyi, when i plug in the usb cable to my laptop, i hear the *ding* for usb noting it is connected but the activesync connection is not available.
thanks in advance for your help.
-mike
m3m3 said:
i get the screen with the 3 colors, and usb at bottom left. when i run the official t-mobile 2.26 update, the screen goes gray and there is a bar with % done. when that kicks in, i get 1% done then it stops. on my computer screen, i get the nbk error, saying the nbk file that i have is not for my phone.
i looked for fixes but all the fixes require activesync connections which i am unable to connect with. just fyi, when i plug in the usb cable to my laptop, i hear the *ding* for usb noting it is connected but the activesync connection is not available.
thanks in advance for your help.
-mike
Click to expand...
Click to collapse
Before your battery goes flat i suggest you to re-install your old rom. Don't know why 2.26 is not working, maybe you downloaded a corrupted archive. To install your old rom it is not required that activesync sees your phone. Go in bootloader mode and flash your old rom back.
i dont think i downloaded a corrupted rom file because i downloaded it from 2 different places, one from Tmobile site directly from my tmobile account.
what bootloader program should i use? please advise and location to download...
thanks,
mike
m3m3 said:
i dont think i downloaded a corrupted rom file because i downloaded it from 2 different places, one from Tmobile site directly from my tmobile account.
what bootloader program should i use? please advise and location to download...
thanks,
mike
Click to expand...
Click to collapse
bootloader program??? There's no bootloader program!
What i'm trying to tell you is:
- Your phone is stuck for unknown reasons. In this state you cannot recharge your battery!
- Before the remaining battery charge becomes too few, reinstall your old rom (the one you had before trying 2.26)
- When your phone -with the old rom- will be working again, then you'll have all the time to investigate on the causes of this failure.
- Now hurry up and install the old rom before it's too late (unless you have a second wizard that you can use to recharge the batteries)
To install the old rom you must go to the three-colors screen (the bootloader), connect to USB (but activesync won't start!) and start the rom installer.
bye
risi,
sorry...how do i get to bootloader screen? is it the tricolor screen? has anyone had the same problem that i'm having, going from 2.17 hack to 2.26 official?
what program can i use to load my original rom with?
sorry for the semi-newbie questions...desperate to revive my MDA...
again, thanks.
-mike
m3m3 said:
risi,
sorry...how do i get to bootloader screen? is it the tricolor screen? has anyone had the same problem that i'm having, going from 2.17 hack to 2.26 official?
what program can i use to load my original rom with?
sorry for the semi-newbie questions...desperate to revive my MDA...
again, thanks.
-mike
Click to expand...
Click to collapse
to go to the bootloader screen you must keep pressed the two keys on the right side of the device and, while keeping them pressed, shortly press the reset button. the bootloader screen IS the three colors screen. when you get the bootloader screen, reinstall your previous rom (2.17).
i plugged the phone in the wall charger and the battery charged up all last night so i am not worried about the battery...
i just cannot figure out how to load the old rom i had.
i didnt bring the phone with me to work...i will try to reflash with old rom...for now...i am using my old hp 6315 (yikes! - remember the probs with this phone?? lol
m3m3 said:
i plugged the phone in the wall charger and the battery charged up all last night so i am not worried about the battery...
i just cannot figure out how to load the old rom i had.
Click to expand...
Click to collapse
to load the old rom you must:
- get to the bootloader screen (the three colors one)
- download the 2.17 rom's ,exe archive (download it from the same place you took it last time)
- connect the phone to USB (don't worry if activesync doesn't see it)
- start the rom .exe file
thanks risi...
hope i can get it back man...
m3m3 said:
thanks risi...
hope i can get it back man...
Click to expand...
Click to collapse
I hope so! About the problem you had with 2.26, i don't know why it happened. Is your phone a T-mob USA MDA? If it is not then you must CID unlock it before flashing a different operator's rom.
Bye
yes, it is a tmo usa mda...or i would think so since i bought it from a factory store (not an authorized dealer). anyway man...i will keep you posted...for now, using my trusty hp 6315. lol
Hello,
I have a similar problem. I updated my QTEK 9100
with a T- Mobile 2.24 ROM. Now I need to go back to the original QTEK Rom, namely RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship.exe, but after starting the upgrade process the program refuses to downgrade the device and says get a newer nbf file.
Is there a way to force a downgrade?
Many thanks in advance
Anais said:
Hello,
I have a similar problem. I updated my QTEK 9100
with a T- Mobile 2.24 ROM. Now I need to go back to the original QTEK Rom, namely RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship.exe, but after starting the upgrade process the program refuses to downgrade the device and says get a newer nbf file.
Is there a way to force a downgrade?
Many thanks in advance
Click to expand...
Click to collapse
Is your phone CID unlocked? If so, then you must download the wizard_upgrade_noid tool from the ftp server and use it to install the 'down'grade.
In details:
- be sure your phone has been CID unlocked (and is not a G4)
- download the wizard_upgrade_noid (i don't remember the name exactly) tool
- use winrar to extract the original qtek rom .exe archive
- copy the noid tool to the folder where you extracted the qtek rom
- run it
bye
Hello Risidoro,
At first thanks for your fast answer. Since I have a QTEK I don't beleve it's CID locked. How can I verify if the phone is CID locked? Is there a tool to check this?
I proceeded exactly as you advised. I used Winrar to extract the files and used the Wizard_RomUpgradeUtility_noid I downloaded from the ftp site.
Then I copied the nk.nbf file to the respective folder but the utility after having completed the initial 2 screens says:
ERROR [238] : FILE READ
The update utility cannot open the requested file. Please check your update utility.....
any ideas
Greetings
Hello,
Just some small updates: My phone has currently the Mr Clean 2.3 firmware loaded : IPL 2.24 SPL 2.24 GSM 02.25.11 and OS 2.24.10.1.
Previously I was using RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship.exe and had no problems. After upgrading to xelencin t-mobile based US rom I had trouble when making data transfers over GPRS. Then I decided to test Mr clean. Altough I data transmission has improved a bit it's still not so good as with my original RUU 2.17 release.
Unfortunately I am unable to revert to this version. Also having tried to downgrade using Faria's Custom downngrade file only the IPL was downgraded to 1.05 and the SPL file stayed to 2.24.
I tried then to reapply RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship.exe but I recieved the error message UPGRADE only.
Since apparently this is unstable I decided to reapply Mr Clean and now I have again IPL 2.24 SPL 2.24 GSM 02.25.11 and OS 2.24.10.1.
I suspect that the data problems are due to the fact that these new radio versions are not compatible with our provider. I live in Luxembourg so we use LUXGSM.
Is there a way how I can revert to my old 2.17 software.
Any coments are highly appreciated.
Greetings
Anais said:
Hello Risidoro,
At first thanks for your fast answer. Since I have a QTEK I don't beleve it's CID locked. How can I verify if the phone is CID locked? Is there a tool to check this?
I proceeded exactly as you advised. I used Winrar to extract the files and used the Wizard_RomUpgradeUtility_noid I downloaded from the ftp site.
Then I copied the nk.nbf file to the respective folder but the utility after having completed the initial 2 screens says:
ERROR [238] : FILE READ
The update utility cannot open the requested file. Please check your update utility.....
any ideas
Greetings
Click to expand...
Click to collapse
Hi Anais,
try flashing with the RUU (Rom Upgrade Utility) tools that you find in this thread: http://forum.xda-developers.com/viewtopic.php?t=56088
Download the archive RUU.rar and extract its content somewhere in your PC. Copy in the same location the nk.nbf from the rom and run the .exe.
bye
I'm trying to fix my friend's MDA right now. The problem is, it's stuck on T-Mo splash screen. It can however go to tri-color screen. Can I save this MDA or should I bury it?
Any help would be appreciated
Hi!
At the tri-color screen you should be able to flash it with a new ROM. Just try it, that worked for me after a failed flash.
Cheers
djvw
rockmanneo said:
I'm trying to fix my friend's MDA right now. The problem is, it's stuck on T-Mo splash screen. It can however go to tri-color screen. Can I save this MDA or should I bury it?
Any help would be appreciated
Click to expand...
Click to collapse
I just had the same problem myself, talk about ****ting my pants.
I have a Dutch rom in my Vario and I cid unlocked it and tried installing
a US rom but the phone was dead after it.
In the tri-color screen I tried to load the new 2.26 US rom and then the latest UK rom but both failed with invalid Vendor id or something like that.
So I downloaded the NL rom from here and thnk god it loaded without a problem and the Vario is working again.
Sadly in Dutch but at least it works again, can anyone from Holland help me upgrade to the latest US rom ?.
Dave...
Dave...
Encountered some problem..
It would not connect to ActiveSync from tri-color screen. There is a 'USB' at the bottom screen when I plug in the USB cable, but I don't think the PC recognizes the device.
And the thing is my friend has never CID unlock the thing
He said he just took it overseas and never turned it off, when he got back here the phone went like this.
More help please
rockmanneo said:
Encountered some problem..
It would not connect to ActiveSync from tri-color screen. There is a 'USB' at the bottom screen when I plug in the USB cable, but I don't think the PC recognizes the device.
And the thing is my friend has never CID unlock the thing
He said he just took it overseas and never turned it off, when he got back here the phone went like this.
More help please
Click to expand...
Click to collapse
PC doesn't need to recgonize the device via activesync to flash the Rom.
Try and find your original rom.
Put the phone in the bootloader (canaryscreen aka tri-colored screen).
plug-in your usb plug.
And start the rom update utility.
Regardless of your activesync status it should start updating your mda.
This takes about 10 minutes, and will pause at some stage, don't be alarmed and don't pull the plug !!!
Good luck
the-equinoxe said:
Try and find your original rom.
Put the phone in the bootloader (canaryscreen aka tri-colored screen).
plug-in your usb plug.
And start the rom update utility.
Click to expand...
Click to collapse
Can I update using the latest ROM (2.26)? Why does it have to be original rom?
Regardless of your activesync status it should start updating your mda.
Click to expand...
Click to collapse
Even tho PC cannot detect the phone at all, rom update util still can go thru?
I will try again tonight, last night I tried, 2.26 rom update utility cannot detect the mda
Good luck
Click to expand...
Click to collapse
Thanks :wink:
rockmanneo said:
Can I update using the latest ROM (2.26)? Why does it have to be original rom?
Click to expand...
Click to collapse
It's recomended to go back to the original rom, so you can go back to the point before the problems began..
Even tho PC cannot detect the phone at all, rom update util still can go thru?
I will try again tonight, last night I tried, 2.26 rom update utility cannot detect the mda
Click to expand...
Click to collapse
In canary-screen mode the phone will have an active usb connection, ActiveSync won't detect it however, because the ActiveSync software on the phone is only started when windows-mobile is running (which doesn't occur in boot-loader).
The Rom Upgrade Utility, should be able to detect the phone.
But always make shure the battery has been charged (at least half-charged).
Several people on this forum have revived their semi-bricked phone this way.
Thanks :wink:
Click to expand...
Click to collapse
You're welcome
Hi,
I wanted to update my trinity in the version of S300+ (French) with the original HTC ROM.
Not only it didn't work, but I lost my phone, I cannot access anything even with Hard Reset and battery removal...
When I want to upgrade, it's going till 1% and then it stops and I'm getting a message "Error 286" Cannot connect with phone.
I cannot hard reset, I cannot do anything! When I hard reset, I'm always coming back to the bootloader (I think it's the bootloader, the screen with colors, where it says numbers and it's says USB).
Any idea? A upgrade with miniSD will help?
Thanks!
Start flash utility again and wait untill it starts again (can take sometime).
I had it to when I first flashed a rom.
Hi,
I tried it already, but it's always blocking at 1% of progress and it's telling me in the computer Error 286, and the phone resets and comes back to the bootloader...
Any idea?
I just tried now to update the ROM with the HTC_Trinity_SIM_CID_Unlock_v1, it's going till 14% but then it stops...
Any idea, please?
I cannot send back my device to warantee because updating roms is forbidden...
This will solve all your problems:
http://forum.xda-developers.com/showthread.php?t=308691
sharedworld said:
I just tried now to update the ROM with the HTC_Trinity_SIM_CID_Unlock_v1, it's going till 14% but then it stops...
Any idea, please?
I cannot send back my device to warantee because updating roms is forbidden...
Click to expand...
Click to collapse
Put the phone in BOOTLOADER, then disactive ACTIVESYNC (form menu). After then start MTTY (you found it in the forum) set it on USB and then give the command:
task 32 Enter
task 28 Enter
task 2A Enter
info 8 Enter
task 8 Enter
After the last command the PDA restart and then you make a normal flash.
I concur :
http://forum.xda-developers.com/showthread.php?t=308691
after 1/2 a day wasted on the agony of a my problem phonem I finally managed to get pof's sxpliot to work, and I promise, it does.....
qubit76 said:
I concur :
http://forum.xda-developers.com/showthread.php?t=308691
after 1/2 a day wasted on the agony of a my problem phonem I finally managed to get pof's sxpliot to work, and I promise, it does.....
Click to expand...
Click to collapse
Please give more instruction howto
Can't you just reflash it with an original SFR ROM? And then read correctly all the instructions for the wm6 flash?
biohazard said:
Can't you just reflash it with an original SFR ROM? And then read correctly all the instructions for the wm6 flash?
Click to expand...
Click to collapse
SFR dosen't give any ROM... But the problem is that I cannot get out the bootloader, but I'll use the solution given here.
Thanks!
sharedworld said:
SFR dosen't give any ROM... !
Click to expand...
Click to collapse
Looks there]...and flash again
shym said:
Looks there]...and flash again
Click to expand...
Click to collapse
It's a DUMP... And not a full one... For ex. you do not get the splash screens...
Hello,
I know you guys got some excellent walkthroughs, roms, programs and threads where you've helped a lot of people out but I could really use some personal feedback. I had hoped to fix my phone using one of the excisting threads but unfortunalty I can't get it to work with those.
My problem is one I've seen more of in here, I used the SE updater and it froze at 53%, I did what the program said, reconnected and it froze again at 12%, and again, again, etc. So I disconnected thinking it might be a bad USB port. But then the updater didn't recognise my phone at all. So I used the mtty program suggested in some of the threads and I got past the red/green/blue screen but now it's stuck at the Sony Ericson logo, as if WM6.1 is gone.
This is what the red/green/blue screen currently states:
KOV110
SPL-0.78.0000
MicroP1-787
MicroP2-707
From what I gather this means I can't flash roms, right? I tried making it a hard-spl but when I use the tool it says it can't connect.
So is there anyway to get a rom on it and bring it back to life?
Thanks inadvance!
Get an original rom from here : http://forum.xda-developers.com/showthread.php?t=475482
copy .nbh file from the package onto your sd card and rename it to : Kovsimg.nbh then bring phone into boot loader via : vol down + power.
It should flash the rom now. i the problem is still present after that you
have to deal with mTTy but first try the flash...
i think you could also bring phone into bootloader without sd card inserted then connect usb cable, display should now print 'USB',and after that start rom update utility.
regards
meska said:
Get an original rom from here : http://forum.xda-developers.com/showthread.php?t=475482
copy .nbh file from the package onto your sd card and rename it to : Kovsimg.nbh then bring phone into boot loader via : vol down + power.
It should flash the rom now. i the problem is still present after that you
have to deal with mTTy but first try the flash...
i think you could also bring phone into bootloader without sd card inserted then connect usb cable, display should now print 'USB',and after that start rom update utility.
regards
Click to expand...
Click to collapse
Thank you for your reply, I will do as you said although I've already tried something similiar to this. I believe the problem was that I couldn't flash roms from my SD since I don't have the hard SLD. But I will try it anyway as soon as I get home.
In the mean time I would love to hear more ideas about how to fix my phone.
Ronnet said:
Thank you for your reply, I will do as you said although I've already tried something similiar to this. I believe the problem was that I couldn't flash roms from my SD since I don't have the hard SLD. But I will try it anyway as soon as I get home.
In the mean time I would love to hear more ideas about how to fix my phone.
Click to expand...
Click to collapse
You really need have to flash the HardSPL first as, based in your above post, you still have not done that. It will be useless to flash cooked ROM with that. If you can still power on your phone and you have an activesynch in your computer, i suggest you download the HardSPL first and update your phone using your PC. If you are successful doing that, then you can flash all you want.
original roms will still work with original spl... but nevermind =P
laurence0609 said:
You really need have to flash the HardSPL first as, based in your above post, you still have not done that. It will be useless to flash cooked ROM with that. If you can still power on your phone and you have an activesynch in your computer, i suggest you download the HardSPL first and update your phone using your PC. If you are successful doing that, then you can flash all you want.
Click to expand...
Click to collapse
My phone can still power on in the sense that it shows the Sony Ericson logo or that I can access the three collor screen. But it won't launch WM6.1. I also have a problem with updating to hard DSL. It does recognise my phone because without it connected the program finds nothing and with the phone connected it wants to start updating. It says ''updating from image version: (emply) to image version: 1.00.X1 Ipress next and it opens a progress bar on both my X1 and the PC. But it never goes beyond 0% and then gives me an connection error. I think it has something to do with not being able to get passed the Sony Ericson logo. I mean the hard-DSL program does recognise my mobile but activeSync is never active because my PC doesn't recognise a WinMobile phone (since it wont go past the Sony Ericson screen)
meska said:
original roms will still work with original spl... but nevermind =P
Click to expand...
Click to collapse
Really? That might fix my device then. Could you suggest a rom from the long list? Perhaps one that works on all versions? Because I'm dutch but my mobile has always been in english so I'm not sure what rom version I had. Except that it was identified as an R2 Rom by the Sony updater before it killed my X1...
Go here
Find the latest stock rom for your country (and perhaps your carrier) and flash it
No need to have Hard SPL for that
Mopral said:
Go here
Find the latest stock rom for your country (and perhaps your carrier) and flash it
No need to have Hard SPL for that
Click to expand...
Click to collapse
I'm now downloading the initial dutch R1 firmwire, could that one work?
Mopral said:
Go here
Find the latest stock rom for your country (and perhaps your carrier) and flash it
No need to have Hard SPL for that
Click to expand...
Click to collapse
Alright so I got an R1 original rom (I now realize that the R3's were originals aswell) and it worked! I'm not sure if it was the different rom or the formatting with FAT32 that did but it works again. So I'd like to thank everyone who was kind enough to reply.
The device is incredibly slow now but now I can use the hard-DSL installer, right? DOes anyone have a suggestion for a good rom to use?
laurence0609 said:
You really need have to flash the HardSPL first as, based in your above post, you still have not done that. It will be useless to flash cooked ROM with that. If you can still power on your phone and you have an activesynch in your computer, i suggest you download the HardSPL first and update your phone using your PC. If you are successful doing that, then you can flash all you want.
Click to expand...
Click to collapse
DON'T hard-spl if you're going to flash a stock ROM. And especially if you're going to use SEUS.
Try flashing the R3A first. The R1s are way slow, as you've seen.