Develop Bugs

Unable to boot up after upgrade ROM to WM6

I follow instruction in http://forum.xda-developers.com/showthread.php?t=313486 but after hardreset.
My p800w is stuck in T-Mobile logo and version number. It can't continue booting up to windows mobile.
Question: How to flash ROM without ActiveSync?
How to recovery my Artemis?
Welcome any advice,
Thanks in advance.

Yea me to, mine is now a brick after that upgrade? No active sync connection possible and all I get now is the blue O2 start screen after the hard reset with the red writing and numbers in the top left hand corner..
Phone is an UK XDA Orbit
IPL 1.25.0001
SPL 1.11.0000
GSM 02.67.90
OS 3.4.0.0
HELP!!!!!!!

yeah, I had the same problem and have created a thread for it already. unfortunately I got no useful replies, and it seems that I am stuck waiting for an official o2 ROM so that I can recover my Orbit.

It seems there is a way to un brick our phones I just need to get my phone bootted into bootlader mode which no one seems to say how to do??
Can anyone help how I can boot my Orbit , like what combo of keys I need to press to boot it into bootloader mode then XP will see it at a driver level apparently Active Sync still won;t but I will be able to run some German ROM update with the ROM file replaced with the other ones and it may come back to life..
Help how can I boot my phoen in bootloader mode???

motomob said:
It seems there is a way to un brick our phones I just need to get my phone bootted into bootlader mode which no one seems to say how to do??
Can anyone help how I can boot my Orbit , like what combo of keys I need to press to boot it into bootloader mode then XP will see it at a driver level apparently Active Sync still won;t but I will be able to run some German ROM update with the ROM file replaced with the other ones and it may come back to life..
Help how can I boot my phoen in bootloader mode???
Click to expand...
Click to collapse
I read in here that you hold the voice button and soft reset.

Decaf said:
I read in here that you hold the voice button and soft reset.
Click to expand...
Click to collapse
Correct and use mtty
Already see in the forum ....

Thanks guys and apologies for the spelling..I ran the Artemis_USPL before I tried upgrading to WM6 and again have been able to run it after with my new brick now with the phone in bootloader mode but still when I try and run the german ROM update a) it will only work with the german file which freezes @ 3%? This seems to be a known problem reading around and b )when I replace it with the smaller ROM file, 54MB the german one is 66MB, I originally tried to use it doesn't read the ROM file or the update utility doesn't want to read it. I reckon I might be able to get it back if I can get one of the ROM update utilities to read a good ROm file and send it to the phone.
I can;t find this MTTY program to sniff the USB port and return the code of if the USPL util wokred as I think that could be key to all of this.
Can anyone post a quick how to here for
1) install MTTY from somewhere
2) what command to run agaist the phoen to see if the USPL util worked and what values I should be looking for
3) another WM6 ROM version (that the update utils can read) download location I can download from to try and send to the phone using the German update util
Not asking for much am I but I desperately need my phone back WM5 or 6 in the next day or so so really can't send it off.
Thanks

Error message I recive at the 3% stage when using the German ROM and english update util.

use the file attach and read that :
http://forum.xda-developers.com/showthread.php?t=285112

Thanks but I'm not that cleud up on what commands I'm meant to be sending. It works in Bootloader mode I ge a response from the phone by send it a command. But even if I get a response telling me what the CID status is its not much help as I think ti shoudl have tekane BEBEs ROM by now as I've got the german ROMUpdateUtility sending that 54,272KB file to the phone but it stops after 3%. What are my options?

motomob said:
But even if I get a response telling me what the CID status is its not much help as I think
Click to expand...
Click to collapse
That's right. On older models MTTY was quite useful, but not on the Artemis. You cannot use it to read the CID status anyway. If you are not sure about the status, run the USPL tool, just to make sure.

I've already re run the USPL ROMUpdateUtility and it completes 100% okay in bootloader mode. But after I hard reset and then try and flash the WM6 BEBE ROM or any ROM German etc back onto it it either fails with the error code I posted up earlier or gets to 3% and fails.
What are my options at this stage? Does anyone have a link to another ROM I can try like the original WM5 O2 ROM or any other WM6 ROm that might work. I'm willing to give them all a try as it's just a useless phone right now and I haven;t sent it off as 1) I need it before the weekend and 2) As I can flash some ROMs with the USPL and others have done this no problem I really feel there must be a solution as I can still falsh the phone.

What can I say RTFM... I did it all right and I didn't have a brick, I missed out one small detail... loading on the ROM with the extended ROM. All now running and it does seem a little faster than WM5.
Thank you to all those that tried to help out. To the others that are still having probs.. Don't try and run the update in the middle of a busy day in the office whilst trying to manage 100 other things meaning you are probably missing out a line like me...
One question though how do I get back my O2 power and storage meters on the today screen back as I liked them and the WiFi seems to have a bug where when it is enabled and you click on the WiFi symbol up the top it only allows you to switch it on, when it is already on.. so you have to open up the COMM manager to switch it off.

So how did you fix it exactly? I have read this thread thoroughly and can't find out what you did!

ERROR[206] occurs while trying to update ROM to WM6
While tring to update ROM to WM6 on O2 XDA Orbit i encounter ERROR[206].
I wanted to attach the screen shot but dont know how to do that, but anyway what i am doing is i attached my pda to my pc via activesync using supplied usb cord. Everything goes well till i reach a screen where it says "You are now ready to update your ROM image...." and once i click next a progress bar apperas and my pda shuts and activesync exit's automatically and my pda tries to restart with RBG band and some text:RUU, IPL 1.25.0001, SPL 1.25.0000 and USB. And thats it after few seconds or a min i get the ERROR[206] and my pda hangs.
I dont know why Activesysn shutsdown ???
Just an additional in i want to tell that without installing activesync i am not able to connect/pair my pda with my pc. So do i need to install the drivers and then try or it doen't matter cause once i install Active sync i can connect the device.
Please help me with this....
Thanks

unable to load bootloader!!!!!!!!!!!!
HELP!!!!!!!!
I have HTC3300, tried to update rom, now its bricked. I tried to start bootloader by pressing the voicebutton and softreset but loads in t-mobile screen and hangs, im unable to start the bootloader.
Is this end of story or are there any other options to get the bootloader to start????
please help

Bootloader
I had a problem with my phone loaded touch flow 4 and cid unlocking, everything was fine then after a while it froze at boot up.
I look put the battery and did a hard reset, put it into bootloadeder mode, reflashed with a t-mobile rom does not need to be cid unlocked to do that.
Once origonal rom was working, cid unlock again, flashed back to touchflow 4.0 - sorted

Where did you got an tmobile rom from can you tell me. Mine is also freezing on booting almost once every day or so after I've upgraded to 4.0

Help, stuck in bootloader after bad flash

Hello, I cant follow/or understand the guides found here or in
trinityguides to recover my device.
I have successfully flashed severa cocked roms before, however this last one failed and left me in tri-color screen displaying SPL-9.99-CP
What do i need to do, my active sync want connect and give me the green OK.
It say it cant detect my device when i connecs it?
Please help, im not good at this, how can i get the device to be recognized by
active sync?
Any help very much appreciated!

allanredo said:
Hello, I cant follow/or understand the guides found here or in
trinityguides to recover my device.
I have successfully flashed severa cocked roms before, however this last one failed and left me in tri-color screen displaying SPL-9.99-CP
What do i need to do, my active sync want connect and give me the green OK.
It say it cant detect my device when i connecs it?
Please help, im not good at this, how can i get the device to be recognized by
active sync?
Any help very much appreciated!
Click to expand...
Click to collapse
In bootloader mode AS will not recognized the PDA. As I see there is DES crash proof hard-spl on your PDA. Stay in bootloader mode, and try to flash an other rom, or the original offical rom. If does not work here is a useful link:
http://forum.xda-developers.com/showthread.php?t=308691

thanks for your quick reply!
how can i flash without the active sync is connected?
i have tried but the rom update utility says it cant find device and exits
or can it be done withot connection, if so how?
thanks for all input, as i said im not an experienced "flasher".

I don't know why, but after successfull cooked rom update (Schap, Faman, etc..) the last one didn't work and stick to 3-color (I'm under olipro 1.3)
I just made a spl update without any pb (take a look if on your pda screen it shows USB instead of serial) don't care about activsync
Then a radio update (1.40 instead of 1.50).
Shap rom update didn't work anymore (cache issue), so I'd just copied RUU_signed.nbh from SChaps replacing the one into Fman folder, and just working fine...
If it can help you.

Had this kind of problem
Simplest thing is to load rom from SD card (do search on this).
In short get the ROM you want - ROM***.nb file and rename it as TRINIMG.NB put it on the SD card. Launch bootloader and follow instructions. Otherwise check thread VISTA FLASH DISASTER...
Good luck,

Solved!
I reconnected the phone ( it sad USB in the bootloader btw)
Downloaded schaps wm6pro and unzipped, enterd the ruu and flashed, even thoug active sync was inactive.
I didnt have to go any further than this.
Many thanks, now i might dare to try som more roms, done ax3ls and karmba's so far looking forward to test schaps now.

Look in the Trinity Wiki. It describe how to flash from the SD card. this will fix you up.

Stuck in bootloader

Everything was fine, I was just browsing for wireless connections and then I've done a softreset and to my surprise it went into bootloader mode, and now whatever I do (softreset, remove battery, hard reset) it goes immediately in the bootloader mode and I can't boot windows.
I am running SPL 2.10 Olipro IPL 1.04.
Not sure if this is relevant at all, but I am running Schap's 4.31.
Any ideas?
Thanks

read the wiki
since youre hard spl you can flash the rom again. jsut run the ruu and select 2.10 and select hard spl, dont auto-detect,go through the steps and it will flash

Hmmm try reinstalling 4.31 or any other ROM again to see if it works!

Tried that already. I have tried the same ROM again (schaps 4.31), and tried the t mobile official ROM (WM6). they didn't change anything, it flashed the rom to the end and then after the reboot it goes back to the bootloader and can't get off it. I have tried the phone's original ROM which was WM5 but I couldn't do that (doesn't flash it, it says the phone is not available, maybe because it's in bootloader and it doesn't connect to activesync).
The strange thing is that overnight I left the phone off and this morning it did boot into windows (this was on the official t mobile WM6 rom) and went as far as running the custom network settings, but then after the restart it went back to bootloader and now it's back, can't get out of it.
Any ideas?

oooo
im having the very same prob
official wm6 from t-mob (UK) upgrade from WM5 that came with the hermes.
now i cnt get outta boot load.
check out my fight to bash the brick back in to its senses...
http://forum.xda-developers.com/showthread.php?t=361323
If anyone can help give my phone CPR - please do.

serializable said:
Tried that already. I have tried the same ROM again (schaps 4.31), and tried the t mobile official ROM (WM6). they didn't change anything, it flashed the rom to the end and then after the reboot it goes back to the bootloader and can't get off it. I have tried the phone's original ROM which was WM5 but I couldn't do that (doesn't flash it, it says the phone is not available, maybe because it's in bootloader and it doesn't connect to activesync).
The strange thing is that overnight I left the phone off and this morning it did boot into windows (this was on the official t mobile WM6 rom) and went as far as running the custom network settings, but then after the restart it went back to bootloader and now it's back, can't get out of it.
Any ideas?
Click to expand...
Click to collapse
Run mtty and try to see if there is bad NAND blocks on the device, to do that run 'info 8' which will report if bad blocks exist. If they do (there should be 3 bad blocks on a normal device, ignore them) then run 'task 2a' which should sort out bad blocks, then flash a new ROM.
EDIT:: Always look at the Hermes Unbricking Thread aswell.

Ok, thanks mr vanx. I'll try that.
Here's a quick update: it would appear that after it is off for a while (about 30 mins, without the battery) it boots into windows, but then after any restart it goes back stuck in the bootloader. Does this mean anything to anybody?

Brilliant
mrvanx said:
Run mtty and try to see if there is bad NAND blocks on the device, to do that run 'info 8' which will report if bad blocks exist. If they do (there should be 3 bad blocks on a normal device, ignore them) then run 'task 2a' which should sort out bad blocks, then flash a new ROM.
Click to expand...
Click to collapse
Thank you ! That fixed it.
Brilliant!
Out of curiosity, what does set 14 0 do? (as stated here: http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem4)

serializable said:
Thank you ! That fixed it.
Brilliant!
Out of curiosity, what does set 14 0 do? (as stated here: http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem4)
Click to expand...
Click to collapse
Sweet stuff, glad that worked
set 14 0 i presume is a standard bad NAND command or something, thankfully in HardSPL olipro enabled checking and fixing of bad blocks.
Have fun with your Hermes again

Thank you
mrvanx said:
Sweet stuff, glad that worked
set 14 0 i presume is a standard bad NAND command or something, thankfully in HardSPL olipro enabled checking and fixing of bad blocks.
Have fun with your Hermes again
Click to expand...
Click to collapse
Cheers mate, I sure will !

This was like reading a good book with a very happy ending.
I feel all warm and fuzzy inside.

stuck in HTC splash screen ..Help!
HI guys ,
I have been following the forum from a long time ..... so before i proceed .... i would like to acknowledge all the great work the guys r doin out here !!..
was working on a friends jasjam which had schaps 4.20 running ... due to some issuses ( screen going blank white )with schaps' ROM , was trying to flash K's 1.30b .... the flashing froze midway .... after that could only see the bootloader for a couple of days .... used the mtty method to recover ... but now i am stuck with the first splashscreen and it doesn't budge from there.....
Would really like some advice here guys

Flash Issue

I have no idea.. Seriously. I went through all the steps right 100x. I read through other people having the same problem as me. And I just cant understand why this isn't working.
I originally used the sticky tutorial in this category.
The hardSPL updated succesfully. I checked through reset+vol down. (although oddly enough it went from 0% - 100% fairly quick)
I'm trying to flash this rom http://forum.xda-developers.com/showthread.php?t=549460
It gets stuck at 0% and nothing happens. Eventually it tells me it fails and i do the recovery procedure it goes back to normal. Somebody else had the same problem so I updated the bootloader to Olinex Unsigned137 that worked too.
But the same problem ,When i goto flash the rom it stays at 0 ****ing percent.
I tried different hardSPLs but still the same ****ing thing. It says nothing about hardSPL in the ROM thread.

Try to install the HardSPL 1.93 (Olinex) from the second post of this thread http://forum.xda-developers.com/showthread.php?t=400950

Nope. Still the same thing. Trying to flash atm with 1.93 Olinex installed and confirmed 1.93 installed correctly.
Tried a different ROM just in case and still stuck at 0%.

What metod of flashing you are using? Flash with the RUU or from Internal Storage?

RUU.
I will tell you my exact method and tell me if im doing anything wrong.
I use RUU 3.27.4.3. I overwrite the NBH in the RUU directory with the NBH I downloaded in the link you provided. I run RUU and tick the boxes etc. and it jumps from 0 to 100% in about 1 minute.
The phone soft resets and then I check with soft reset+vol down key. Everything seems good theres is a 4 coloured screen and the information seems fine.
I then download the ROM and replace the NBH with the one provided by the ROM. I open RUU and do everything as usual but it gets stuck at 0%. After about 5-10 minutes it says ERROR and i follow the recovery proccess and it works fine again.
What is the other Method? Maybe I should try that?

You need to rename the nbh file to diamimg.nbh and place it to the root of your "Internal Storage" then push "reset+vol down+back" and the bootloader will appear then it will prompt you to press the power button to start the flash... This metod should work for you if you have really correctly installed the HardSPL.

I successfully upgraded Radio to 1.00.25.05 which is good. I thought maybe that was compulsary to be able to flash a new ROM. But still stuck at 0%
I'm going to try your method now, Will post back soon.
Thanks for the help so far.
EDIT:
It worked! Succesfully flashed and everything! So far no hangs or problems.
Thank you very very much! I wish there was a Rep system lol.
I think somebody should write up a tutorial on this method and sticky it for anyone like me who was having troubles.

xelasha said:
I successfully upgraded Radio to 1.00.25.05 which is good. I thought maybe that was compulsary to be able to flash a new ROM. But still stuck at 0%
I'm going to try your method now, Will post back soon.
Thanks for the help so far.
EDIT:
It worked! Succesfully flashed and everything! So far no hangs or problems.
Thank you very very much! I wish there was a Rep system lol.
I think somebody should write up a tutorial on this method and sticky it for anyone like me who was having troubles.
Click to expand...
Click to collapse
Well, there is a tutorial for this made by Suiller and it`s here http://forum.xda-developers.com/showpost.php?p=2707841&postcount=4035
if you will ever need it... And the radio you mentioned 1.00.25.5 is quite old, I suggest you to upgrade to the 1.15.25.14 radio...

[Q] Need help!

Installed a rom on my tilt 2, or thought i did. phone now boots to windows and freezes. I can boot into bootloader screen and attempt to install other roms however it never gets past 0%.
When it tell me on the computer what image i have nothing appears for the phone image. its just blank. after a while the pda program with say there is a connection error and will rail installing the rom.
plz help =(

Genesis01 said:
Installed a rom on my tilt 2, or thought i did. phone now boots to windows and freezes. I can boot into bootloader screen and attempt to install other roms however it never gets past 0%.
When it tell me on the computer what image i have nothing appears for the phone image. its just blank. after a while the pda program with say there is a connection error and will rail installing the rom.
plz help =(
Click to expand...
Click to collapse
Did You HardSpl Your Phone First?

yes, however at first i thought my phone was cmda.....now i figured it is gsm. went through the process of hard-spl how can i be sure though?

Genesis01 said:
yes, however at first i thought my phone was cmda.....now i figured it is gsm. went through the process of hard-spl how can i be sure though?
Click to expand...
Click to collapse
Since You Can Boot Into Bootloader You Can Check Your SPL Version From There Check It Out & See What Is & Post What It Is Here.

just checked it again and the olinex isnt there anymore. sure that would be the problem. how do i go about fixing said problem?
spl-0.87.0000

Genesis01 said:
just checked it again and the olinex isnt there anymore. sure that would be the problem. how do i go about fixing said problem?
spl-0.87.0000
Click to expand...
Click to collapse
Follow The Instructions In This Thread ---> http://forum.xda-developers.com/showthread.php?t=550131

tried, the phone, even thought it is connected wont sync so the spl wont detect it and run the program

when i go to manual it will start but will hang at 0% until the comp says there was an error in connection =(

Genesis01 said:
tried, the phone, even thought it is connected wont sync so the spl wont detect it and run the program
Click to expand...
Click to collapse
Try Booting Phone Into Bootloader Screen Then Plug In Usb Cable Make Sure It Says Usb At The Bottom Of The Phone Screen Then Try To HardSpl Again.

Try Installing This Cab On Your Phone --> http://hpcmonex.net/roms/enablerapinew.cab Then Run HardSpl Again.

kk thank you, i will try. will post results as soon as i get them. Thanks again. kudos to you!

If your phone does not have the HardSPL on it, and it will not boot properly, you need to get it back into bootloader mode, wait for 'USB' to appear on the screen, and flash the stock ROM, then try again with the HardSPL program.
EDIT: To see what version of Rhodium you have, remove your battery and look at the sticker under there on the phone. you should see something like RHOD100, RHOD200, RHOD300, RHOD400, or RHOD500. RHOD100-300 is GSM. RHOD400 & 500 is CDMA. Make sure you flash the correct ROMs, radios, and HSPL for your device or you run the risk of bricking it.