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

Stuck In BootLoader After Trying To Install D810 Official ROM

Hi All,
My P3600 is stuck in bootloader after trying to install the official D810 ROM. I used the CID unlock install first, which seemed to work fine, I then tried to install the D810 ROM and it looked like it was working, but stopped at 28% with some kind of communications problem. Recovery does not work... it displays the progress bar, but then goes straight back to the rainbow bootloader screen.
Any help or suggestions appreciated.
Thanks
Rael

Phew... got it working. I removed the battery and replaced, boot loader was still displayed, and then ran the old official WM5 update which seemed to progress from 0 to 100% sucessfully.
Thanks
Rael

Your phone was relocked by the update, and I'm guessing you don't have an actual D810 that's supposed to get this update. The best method to flash this is to follow my post here:
http://forum.xda-developers.com/showthread.php?t=316410

oops, you can use hard SPL in this link:
http://forum.xda-developers.com/showthread.php?t=299659
i got the problem like you when i upgrade my device to wm6 officiel.
After you flash hard SPL Olipro, you can use PC to flash again another rom you like.
(sorry for my worth english)...

People just do NOT know how to read...sigh.

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

[Q] ROM Update stays at 0% - help needed

Dear All,
this time, I have a problem and need your help, please.
I just bought a new (used, but not by me ) HTC Touch Diamond. Hard-SPL (1.37 from whoever) was installed.
First MTTY'ed the device - with success (set 14 0, task 29, task 8)
Wanted to install OliNex 1.40 first
Started ROM-Update, everything went fine, screen of Diamond changed into "bar display" - but stays there with 0%
Tried several flashes (OliNex, ROM, Radio - everything the same)
Does anybody have a hint for me what to do? Identifier seems ok, DIAM100 is shown in intial bootloader screen (three color-screen)
I appreciate any hint.
With kind regards from Switzerland - Christoph

Radio
Downgrade your radio to one below 1.02.XXX before flashing the unlocked radio
Full instructions to unlock your diamond are here
http://forum.xda-developers.com/showthread.php?t=749201
Once you have done this, you can flash any ROM you like

Dear Dave,
thank you very much for your support.
Unfortunately it didn't help but showed everytime the same picture - stuck in the bar at 0% and doesn't do anything.
I tried STEP 1, STEP 2 and downgrading to radio 1.00.25.05 (but actually I don't know which is actually installed, as the Diamond never reaches the Touch Diamond page with ROM & HW Info, it stucks in the Touch Diamond page with no information at all, if started not in Bootloader mode)
It seems to me that the bootloader itself could be corrupted or the model number (shows DIAM100 in Bootloader) is somewhat corrupted, as I know that the internal storage consists of more digits (like DIAM10000 or so) - and a way to fix it with MTTY? But I can't find a description of the MTTY tasks of the Diamond.
Any more Idea?
Thank you Dave, and all the others who read and think, in advance.

X
Can you get into Bootloader mode by holding down
Volume down button + Back button (Bottom right button) + Press reset with the pen
Then keep pressed the first two buttons and let go of reset, keep hold of the first two buttons until it reaches the bootloader mode
If you can do this, then reboot and put the radio onto the storage card (4GB one) and enter bootloader mode, then folllow instructions on that screen to flash the radio, and you can do the same for the rom
It sounds to me like maybe you have not managed to flash the HardSPL properly

Hi Dave!
Thanks for your quick reaction.
Yes, I can anter bootloader mode. But nothing more. Flash is not possible. Hard-SPL was the first thing I tried to flash but it also remained at 0%
How can I put files on the internal storage card from within bootloader mode? (Phone is not booting, ONLY bootloader mode is accessible...) I never encountered this before...
But I can reach the phone with MTTY.. can I access the storage card through this?

X
Have your tried different HardSPL versions ?
Im not sure what is wrong... if you are in Bootloader mode, and the USB drivers are installed and you have activesync running on the PC it should update no problem
I would make sure all the above is true, and attempt different HardSPLs
I think that is the issue as you wont be able to flash an unlocked radio or custom rom without HardSPL being flashed first
Here is another version you could try
http://selfmod.net/how-to-hard-spl-a-htc-diamond/
EDIT - And I dont know if there is a way to access the storage card from MTTY or bootloader, my guess is that you wont be able to
Also, this is a GSM Diamond right ? Not a CDMA ? (UK Networks are GSM)
CDMA flash is here
http://forum.ppcgeeks.com/cdma-diam...ond_c-cdma-sspl-hardspl-package-here-now.html

Hi Dave!
Yes, it's GSM. Thanks for your help and the links provided - it didn't help.
I tried various Hard-SPLs: OliNex 1.20, 1.30, 1.37, 1.40 and 1.93 (developers)
Result - all the same: standstill at 0%
I've seen in MTTY that I have an "upload" menu item - but need there the start address and command line for Diamond plus to know what it is meant for, I will try to find out... and if there is some new know-how out of this, I will post it here, in order that future GENERATIONS may find it *laugh*
Dave? THANKS!
Kindest regards from Switzerland - Christoph

X
Ok, lol Another possible !
Maybe your friend flashed a Signed HardSPL which means you can only flash Signed radios and roms until you flash another unsigned HardSPL
If the Radio you are trying to downgrade to is unsigned that could explain the issue... try and find a Signed radio below version 1.02.XXX and try to flash that, then try to flash to another Unsigned HardSPL, if the radio flash goes ok.
------------
Update stops at 0%
Short answer: You're running the normal HardSPL and you're trying to flash an unsigned (not signed by olinex) ROM. You need the developer version which fixes the 0% issue. Link is at the bottom of this post. Read on to understand the difference between Standard/Developer Edition!
Long answer: First you need to understand that there are two definitions of "signed". HTC and the mobile operators sign ROMs so that the RUU flash utility allows them to be flashed. Usually this is what the word "signed" in the filename means.
Then there is another definition of signed: The developers of HardSPL introduced their own signing process. They want to ensure that people flashing cooked ROMs can rely on a certain quality standard. The normal version of HardSPL will only allow ROMs signed by OliNex to be flashed. If the ROM you are about to flash is signed, it will say so in the thread you got it from. If it isn't signed, you will need the developer version of HardSPL. That one will allow any ROM to be flashed. Get it at the bottom of this posting.
A note on this: The signing process by olinex makes sure that the ROM you're about to flash won't brick your device. It doesn't mean all other ROMs are necessarily evil.
-----------
Some help on 0% flash hangs
http://forum.xda-developers.com/showthread.php?t=409425
I`ll have a look into uploading from MTTY as I have never tried that.. sounds a good feature if you can though for dead phones and such !
good luck.. again lol

magicdave26 said:
Ok, lol Another possible !
Maybe your friend flashed a Signed HardSPL which means you can only flash Signed radios and roms until you flash another unsigned HardSPL
If the Radio you are trying to downgrade to is unsigned that could explain the issue... try and find a Signed radio below version 1.02.XXX and try to flash that, then try to flash to another Unsigned HardSPL, if the radio flash goes ok.
------------
Update stops at 0%
Short answer: You're running the normal HardSPL and you're trying to flash an unsigned (not signed by olinex) ROM. You need the developer version which fixes the 0% issue. Link is at the bottom of this post. Read on to understand the difference between Standard/Developer Edition!
Long answer: First you need to understand that there are two definitions of "signed". HTC and the mobile operators sign ROMs so that the RUU flash utility allows them to be flashed. Usually this is what the word "signed" in the filename means.
Then there is another definition of signed: The developers of HardSPL introduced their own signing process. They want to ensure that people flashing cooked ROMs can rely on a certain quality standard. The normal version of HardSPL will only allow ROMs signed by OliNex to be flashed. If the ROM you are about to flash is signed, it will say so in the thread you got it from. If it isn't signed, you will need the developer version of HardSPL. That one will allow any ROM to be flashed. Get it at the bottom of this posting.
A note on this: The signing process by olinex makes sure that the ROM you're about to flash won't brick your device. It doesn't mean all other ROMs are necessarily evil.
-----------
Some help on 0% flash hangs
http://forum.xda-developers.com/showthread.php?t=409425
I`ll have a look into uploading from MTTY as I have never tried that.. sounds a good feature if you can though for dead phones and such !
good luck.. again lol
Click to expand...
Click to collapse
This is the answer. I used to have the same problem because when I bought my diamond I thought everything runs the same as the TyTN but ...
So to cut this story short, almost 90% of the 0% bar situations are because U R not using signed roms. However if Ya want to then use the unsigned HardSPL.

Hi Dave & Nazgul,
it seems that my case belonst to the non-90%
Of course I tried all this, but I have THREE diamonds - two were branded by the Swiss Swisscom (this is, in fact, the same image as the German Vodafone branding), one was the original HTC version
I'm flashing Diamonds since two years though.
My fault this time was, that I THOUGHT, this new one were HardSPL'ed, but it wasn't - and formatted the device using MTTY without Hard-SPL.
After that I had the above mentioned situation.
NO Hard-SPL was flashable - as written above - also noth the unsigned developer 1.93 edition - it always remained at 0%
I managed in the meantime to flash the original Vodafone/Swisscom ROM. So I have back the device in the official configuration (HTC Swisscom 1.97 package http://www.swisscom-mobile.ch/scm/d...pa=0x0x147x18x0x0x0x0x0&odg=SoftwareAndManual)
But - this uses Radio 1.08.xxx and I would like to downgrade because I think, Dave's hint above to use a radio before 1.02.xxx would be worth a try.
BUT - I STILL can't flash anything. Neither ANY Hard-SPL nor any Radio version nor any ROM.
The bar remains at 0%
I tried to find the original (first edition) of the Swisscom ROM Package, which used the Radio 1.00.25.05 - and then to try Dave's proposed steps.. but I can't find it anymore - all you can find is the "latest" package...
So I would still appreciate any help to be able to flash. Ok, now at least, I have a usable phone... but... I wanted to use it (as the other two) for ROM development testing, so who wants to have a PHONE!?!?
Kind regards from Switzerland - Christoph

Here is your radios
Sorry for the short post, I have a really bad hangover lol
http://forum.xda-developers.com/showthread.php?t=407956

Morn' Dave!
I tried them all - none of them was flashable... same 0%-bar.
I thought of having the V 1.00 complete official Swisscom-Pack and as part of it, the radio 1.00.25.05, which is included. Seems to me, that the c(complete) official ROM pack is flashable.
THEN I could re-try to flash Hard-SPL (with then installed radio below 1.02.xxx)
Hangover? What's this?

Christoph21x said:
Morn' Dave!
I tried them all - none of them was flashable... same 0%-bar.
I thought of having the V 1.00 complete official Swisscom-Pack and as part of it, the radio 1.00.25.05, which is included. Seems to me, that the c(complete) official ROM pack is flashable.
THEN I could re-try to flash Hard-SPL (with then installed radio below 1.02.xxx)
Hangover? What's this?
Click to expand...
Click to collapse
YEa that might work, it is almost certain the issue is the HARDSpl being either not flashed, or flashed with a signed version
Good luck !!
And the hangover is nearly gone... I cured yesterdays with more alcohol lol

Have you tried these UNSIGNED dev HARDspls ?
http://forum.xda-developers.com/showthread.php?t=400950

Hi Dave - GOT IT, solved
The "secret" was to flash noit from withi boot loader but from within Win Mobile with ActiveSync/Windows Device Center connected.
Then say "Yes" when "enterbootloader.exe" was asked to be installed/invoked.
Then the Device rebooted, flashed Hrd-SPL 1.40 correctly - and everything else onwards went fine.
Thanks a lot for your assitance, Dave and others.
Kind regards from Switzerland - Christoph

Ah.. I thought you were already using the Activesync and CustomRUU to flash it with !
Yes, the ROMs and Radios can be flashed from the storage card, but the Hard SPL needs to be done from Activesync / CUstomRUU
Pleased you got it working anyway