Develop Bugs

Restore original O2 UK ROM from Bootloader

Hi everyone,
A while ago I was stupid and tried to flash my O2 XDA Orbit without fully reading the instructions and therefore ended up "bricking" the device. It turns on but seems to hang on the "O2 Welcome Screen" which shows the following information:
IPL 1.25.0001
SPL 1.25.0000
GSM 02.67.90
OS 1.28.0.0
The device can boot up into the bootloader screen no problems and I have tried to install various ROM's from the German O2 WM6 ROM to the UK T-Mobile WM5 ROM but with no success, it just gets to 3% then reboots.
Does anyone know a way that I can restore the original O2 UK WM5 ROM from the bootloader? Or at least get it working again?

At this point there is no O2 Rom avaliable, you will have to wait till they finally release the WM6 Rom sometime this Summer.
Lordao

try this
http://forum.xda-developers.com/showthread.php?t=312495
go to this tread and test it

1234567890

No Joy
pvdhelm said:
http://forum.xda-developers.com/showthread.php?t=312495
go to this tread and test it
Click to expand...
Click to collapse
Thank you however I have tried the above instructions but my device just gets to 3% then reboots.
Does anyone know what the MTTY.EXE software is all about and is there any way that I can manually force the device to Flash using this?

Or!!!!!
Is there a way for me to clone a mates xda orbit and drop the image onto mine? Both were purchased at the same time just I thought i'd be clever and update mine which didn't quite work out.

Have you already tried to flash a rom by using your microSD card ?
http://wiki.xda-developers.com/index.php?pagename=Artemis_SD_Card_Flashing

try to flash it from sd card if your orbit is cid unlocked

not sure
I dont think my device is cid unlocked as it would have worked with the updated rom install, wouldn't it? sorry pretty new to all this.
I have tried to flash straight from the sd card but it just searches through the sd card then goes straight to the multicoloured bootloader screen.
Anyother ways or is there a better rom that i could use?

Trouble with Dopod WM6..

can't seem to get this upgrade to work. the updater stops at about 28 percent for me with an error (286? i think) and after that i'm stuck in bootloader. Every time after that, the updater wont even start.. (a different error).
i can flash successfully a cooked ROM, but can't get the official one to work. Could it be a conflict with Des' crash-proof SPL? That's the only thing i can think of at this point..

To me said invalid device id, and got stuck on the boot loader

try back to any old offical ROM
and then copy SSPL to PDA and run it on PDA
when bootloader appear, run WM6 offical updater
I got same problem too and get fix
good luck

update: since i managed to flash PDAVIET's rom, i thought i'd just try going back to Olipro's hard-spl and see what happens.. So i flashed it, entered bootloader and ran the WM6 update again, and SUCCESS!!
very strange though.. anyone have some thoughts as to why it wouldn't work under Des', or if this is just coincidence?

It installs a new bootloader that can't be hacked by the previous hacks I think.... I'm stuck in it too...
SPL-3.03.0000

racerx_ said:
update: since i managed to flash PDAVIET's rom, i thought i'd just try going back to Olipro's hard-spl and see what happens.. So i flashed it, entered bootloader and ran the WM6 update again, and SUCCESS!!
very strange though.. anyone have some thoughts as to why it wouldn't work under Des', or if this is just coincidence?
Click to expand...
Click to collapse
Hi racerx,
I've encountered the same problem as your, stuck at 28% ERROR [286] while flashing, and couldn't go over it even after recovery process following the instruction.
Could you please explain a bit more details about how to go back to Olipro's hard-spl and enter into bootloader?
Thanks, eager to flash the new ROM...

Well I was able to get out of it by running Pof's CID RUU Unlocker, however, it errors after 7%, and resets. It gets past the bootloader, however, it hardreset the phone...eh.

IT happened to me too - Update Error.
So should i go back to Official WM5 then update to WM6 (i had AX3L installed before and i just had to reflash back to AX3L coz of the error from WM6).
Kinda scared me.....LoL

well, to start with i had Des' Crash-Proof SPL on my phone... so after the updater hung at 28%, i remained in Des' bootloader. I then ran the RUU for pdaviet's ROM, which flashed successfully. After that was on and my trinity was up and running, i flashed Olipro's hard-spl. Then manually put it in bootloader again, and flashed the official ROM.
Let me say this, though. At this point, i think you should be content to get your device out of bootloader mode. This Dopod WM6 doesn't have so much to be desired in it compared to cooked ROM's on this forum, plus your bootloader will be stuck at version 3.xxxx which i don't know if anyone is sure how to deal with yet. I'm regretting flashing mine to official version. Should have waited for a chef to pack it up for me.
what does your bootloader say?

You need to actually have a device that this release is supported by. It flashes a new SPL but you can flash Olipros HARD SPL 1.20 straight over that once WM6 has flashed.
It replaces any HARD SPL before flashing, probably to ensure only official devices get this update. Those having issues are probably out of this.
The official rom is fine, not as finished or customised as some chef ones, but good none the less. Also, the new 3.0??? SPL is no issue at all and easily removed once flashed.

yeah saw your post on the other thread.. thanks for the tip! talk about a stressful morning haha..
i was waiting for this ROM cause my activesync has mysteriously stopped working for a couple of weeks. so i was going to flash and take it to the service center. The miracle of it, was after my device hung and i reflashed pdaviet's rom, my activesync mysteriously works now even though i reflashed a million times before trying to get it going haha..

new spl is needed for flashing new radio rom with cid locked device.
So that's why RUU reflashes SPL at first.
U could simply reflash HArd spl back by using sspl

mUn, when can we expect your much anticipated "Indigo" rom using this offical WM6 base??

Genius! thanks for the tip mun...
all i can say is one word....
INDIGOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO!!

I also got Invalid vendor ID when I tried to flash for the first time. But it flashed just fine after I put it into bootloader mode. Give it a try..

Flashed my mine in a breeze from LSVW version 27/05/07.

myppcsg said:
Flashed my mine in a breeze from LSVW version 27/05/07.
Click to expand...
Click to collapse
still same problem
can you post the RUU files plz

mxlaser said:
You need to actually have a device that this release is supported by. It flashes a new SPL but you can flash Olipros HARD SPL 1.20 straight over that once WM6 has flashed.
It replaces any HARD SPL before flashing, probably to ensure only official devices get this update. Those having issues are probably out of this.
The official rom is fine, not as finished or customised as some chef ones, but good none the less. Also, the new 3.0??? SPL is no issue at all and easily removed once flashed.
Click to expand...
Click to collapse
Thanks for all the helps from you guys. This is what I did after stuck at 28% with ERROR[286]:
1. Flash back to Official OZ WM5 ROM. Had no problem to flash back as it was in the bootload mode.
2. Flash Olipro's Hard-spl. No problem as well.
3. Flash Official OZ WM6 ROM again...... and stuck at 28% again!!!!!! with ERROR [262] @#[email protected]#$.
4. Now in the process flash back to Official WM5 again... @#@#@....
5. Will flash Official WM6 straightaway after that.
6. Will update result later....

geoffreyhan said:
Thanks for all the helps from you guys. This is what I did after stuck at 28% with ERROR[286]:
1. Flash back to Official OZ WM5 ROM. Had no problem to flash back as it was in the bootload mode.
2. Flash Olipro's Hard-spl. No problem as well.
3. Flash Official OZ WM6 ROM again...... and stuck at 28% again!!!!!! with ERROR [262] @#[email protected]#$.
4. Now in the process flash back to Official WM5 again... @#@#@....
5. Will flash Official WM6 straightaway after that.
6. Will update result later....
Click to expand...
Click to collapse
hehe i did that many time this day maybe hmmm 5 or 6 and im still doing that

try to use another version of RUU (the older one)
ps. plz don't post messages about indigo in other tgreads ) if u want to ask - so ask in mine thread.
I'll flash official rom today and then will make some conclusion ) but i thibk that indigo will be based on oficial release

HELP: Cooked ROMS won't flash

I have Orange branded spv m700 and have unlocked and supercid'd the device using pof's tool. I then added HardSpl (Olipro 1.20). All appear to have loaded fine - phone is unlocked and Olipro shows up when put into bootloader.
So, the problem - every time I flash a cooked ROM (Ausdim, NiAx, FiNixNover...?) it won't boot past the first screen. I can rescue the situation by putting device into bootloader and flashing the official WM6 ROM (no radio, no ipl....) and it boots up just fine.
Can anybody help or at least point me in the direction of some good advice?

hmm... odd... can you list step by step what your procedure is for flashing the ROMs

I've done lots of devices - old XDA2i, SPVM600, wifes SPV M700 (unlocked, hard spl etc and flashed away!
This particular device shows IPL 0.50 & SPL 1.20 Olipro. It is unlocked (have o2 sim working in it), and should be SuperCid (I checked the box and radio shows as 1.16.00.00 - pof's patch I believe?). I also re-run HardSpl and Pof's unlock/supercid patch just in case it hadn't flashed properly.
I generally just download ROM and flash via RUU. Occasionally I get the device not responding error so I just re-run RUU from the bootloader screen.
Have tried WM 6.1 and 6.0 cooked roms but all show initial boot screen (numbers along bottom) next screen and then frozen, have waited and waited and nothing. Also, it would not flash back to Mozzers WM5 Orange UK ROM - same symptoms. I thought it was bricked, but the Dopod WM6 flashed perfectly.
Hope that helps - thanks for looking into my problem.

anybody please? por favor........

hmm.. i remember someone having a similar problem but it was some time ago..
two things to try just in case...
1) i'd manually go to bootloader (hard-spl) before flashing
2) Have you tried to flash from SD card? this method seems to provide less problems..
let me know how it goes..

A degree of success - managed to flash WM6 AX3L. All seems to be working. As I recall this is very similar to the official ROM and I used to use it last year because it is very stable. Think I moved on because of the missing email accounts problem. Will happily keep it if I can sort the email problem out. Never really had much fun with the hard reset after loading method - is there another/better way? Just wondering.
Also, now I have a "cooked" rom loaded perhaps it will stop being so sensitive.....!!

How strange! Have just flashed Akeo's new Diamond port ROM and no problems. Not only that, the ROM is FAB!!!

touch diamond rom update

Hi i have a HTC TD device and I am traing to update rom from 1.93.401.2 to 2.03.401.2 but not sucssesifuly and at the end of update update utility shows this massage : 270 update error , the image file is corrupted, please check youre update utility.
This is frustrating because i tried all possibilities to fix a problem and still nothing, does anybody have any expirience with something like this to help me thanks a lot.

have you tried downloading the rom again?
Is your device locked by provider? If yes, you have to hardspl.

nickytheshaft said:
have you tried downloading the rom again?
Is your device locked by provider? If yes, you have to hardspl.
Click to expand...
Click to collapse
Yes I have tried all available posibilities : Hard Reset, changeing radio, and it is not locked by provider because first time i was sucssesifuly updated and then i saw olinex and i instaled that one after olinex there is no way to instal 2.03.401.2 I think that olinex is my problem but i do not have any idea to remove it because i have tried all available options and this is my 5th day that i am fighting with that and still i did not find any solution but anyway THANKS A LOT and get back to me soon if you know how to resolve this.

Diamond-HD said:
Yes I have tried all available posibilities : Hard Reset, changeing radio, and it is not locked by provider because first time i was sucssesifuly updated and then i saw olinex and i instaled that one after olinex there is no way to instal 2.03.401.2 I think that olinex is my problem but i do not have any idea to remove it because i have tried all available options and this is my 5th day that i am fighting with that and still i did not find any solution but anyway THANKS A LOT and get back to me soon if you know how to resolve this.
Click to expand...
Click to collapse
I seem to remember that error 270 means that you need to udate your bootloader, Try flashing an updated HardSpl.
And remember olinex has two spl's, one for gsm and one for cdma, they are not interchangeable.

thanks
Thank you i solved my problem i have know that olinex is for gsm and cdma i am fixed with hard spl 1.34 and now work perfect and after this long problem resolving now i know everithing about rom because i have try everything THANKS A LOT AND STAY GOOD AS WHOLE THIS SITE IS THANKS AGAIN

Error 270 when flashing to 2.03 stock firmware
I had the exact same problem. I went out on a limb and try something different and it worked! When you have just completed a fail upgrade (you see the 3 colored bars on your phones screen) quit the firmware update software, soft reset phone, re-connect to computer, and immediately flash to hard spl 1.34 signed. When finished the phone will reboot to and viola, you will have the latest firmware installed. At this point you can put back on the latest spl (1.40 I think) so that you can load custom ROM's. Just remeber if you want to get back to the latest stock ROM from HTC you have to rollback to the 1.34 SPL. Hope this helps peeps.

got stuck in bootloader screen

hi all,
i have a mda pro (htc 9000) from T-mobile, during wm5 and many bugs
i have tried to upgrade, i find some update rom overhere and followed the
instructions, direct during upgrade the device comes up in bootloader screen
en got stuck, i have tried everything even reset e.t. still i cannot get out
of the boatloader screen, i have tried an wm6 rom but i gaot the message
checking the information on your device and nothing is happend anymore
still waiting for a long time.
i have no idea
please help
thanks

Download an official Shipped ROM meant for your Universal and flash it. It should then pass through the screen.

thanks for the tip, i find the rom, but it need for upgrade active sync installed
and that's the issue now, because active sync does do nothing now when the device is in boatloader mode.
IT UPGRADING NOW pfffffffffffff
after intestalling again active sync...
oeps

Read Wiki!
Read Wiki.
Use mtty...DOC format.
Flash original WM5 ROM.
THEN
CID unlock with upgradeutility Noid.
You are free to do almost anything.
Again Read Wiki.
Read hdubli ...thread for stuck in bootloader.
Read Roms from Cotulla thread....it's helpful.
As long as you have intact bootloader , don't panic...it is not dead yet.

thanks for the advise, i find the wiki and solve the problem.
on my old xp pc and installed active sync, the device was direct upgraded
and the orginal rom is back to the latest version.
i find also the 6.5 rom but for now it works