Database Info

NBD 8.x doesnt do anything!

Hy everyone. I tried installing NBD 8.1, 8.2, and 8.3 on my phone today and it goes well. It says it has finished updating my phone and then when I start my phone, it says its being customized and I see everything being installed. After it is done installing, it resets. When it resets it is just the same old thing. It looks the same way it did when I first bought the phone. Im using a Cingular 8125 if it makes any difference. Thanks.

Your phone is still CID locked.
Follow this tutorial to unlock it, and follow the steps closely.

i wouldnt follow that tutorial just yet. You still need to give us a little more information like if your wizard is a G3/G4. You can only cidunlock your wizard if it is a G3.

I wonder why newbies are always told to CID unlock...
Shelltool works perfectly for flashing new OS (I flashed my CID locked G4 at least 6 times) and there should not be any risk of bricking the phone...
Mirek

mirekluza said:
I wonder why newbies are always told to CID unlock...
Shelltool works perfectly for flashing new OS (I flashed my CID locked G4 at least 6 times) and there should not be any risk of bricking the phone...
Mirek
Click to expand...
Click to collapse
I agree! I'd been flashing my G4 phone from about 5 months ago with different ROMs (almost continuously)... ShellTool is the best tool that I tried to flash ROMs without risk.
Cheers!

mirekluza said:
I wonder why newbies are always told to CID unlock...
Shelltool works perfectly for flashing new OS (I flashed my CID locked G4 at least 6 times) and there should not be any risk of bricking the phone...
Mirek
Click to expand...
Click to collapse
nobody bothers to read anymore and dont know what the search link looks like. The just jump on the bandwagon. But its true i had a hard time following some instructions but i got through it.

Really??
I used shelltool 2 times without problem, but then i get the 1 time a message - flashing done after 8 minutes and the flash wasnt really on the phone. Since then i use RUU (which is in the love wizard rom package) and it works for me.
Today i tried flashing nbd 8.3 to faria aku 3.3 and other faria rom with aku 4. In both casec the flashing stoped at 99% and i had to reflash it with nbd rom.
The flash didnt end , cause i have cid-locked phone?? I would like to have a newer aku(i have 2.3). HELP

I used Shelltool to install the rom I had. It finished after about ten minutes, and then I hard reset my device.
Whenever I start my phone up now it just hangs on the Cingular start up screen and this is what it says.
IPL 2.25
SPL 2.25
GSM 02.25.11
OS 6.6.6.666
Any idea what went wrong or if there is any way to fix this?
Thanks

Are you using Vista?

Nope. I used Windows XP Pro.

I had the same problem with shelltool on xp pro sp2. Get the phone in bootloader mode and flash again. Maybe with RUU , which is in the wizard love rom package. Just replace the .nkb file (rom file) to one u want.

I don't like this topic name. It should be: "I don't know how to install new rom"

A few advices from long time shelltool user
(I used it to flash "faria real thing", several version of "crossbow reloaded", "xda mobile", "pandora", "wrcx3"). I am on a locked G4 phone.
a) I always start by flashing the original ROM of my provider (in my case T-Mobile CZ) in normal way. This may not be a needed, but I read that it is *recommended*to flash your provider's ROM to have some stable base. It takes about 10 minutes or so.
b) Afterwards I flash using shelltool (see shelltool documentation how it is done)
Possible problems with shelltool
a) It does not end and the flashed phone seems to be frozen (clock is not updated etc.):
No problem, flash is done. After 30 minutes from the flash start just take your phone, do the hard reset and everything will work ok.
This (shelltool not ending) happens often, but as I said - it is no problem.
b) The wrong flash
Either the shelltool is interrupted prematurely or it the phone freezes during restart afterwards.
No problem, just reflash your provider's ROM in normal way and try again shelltool.
This happens only very rarely and I never went through this more than once.
Conclusion
Since the shelltool is limited to flashing only OS, you should not ever brick your phone in this way... The most you can do is to screw up your OS - which can be quickly recovered by flashing the official ROM from your provider.
Flashing by normal way is more dangerous: if you flash a locked phone with the ROM containing more than just OS, you can easily brick your phone (if you flash ROM just with the OS you will wonder that nothing has changed - at least this is like I understand it).
Mirek

zoki said:
I don't like this topic name. It should be: "I don't know how to install new rom"
Click to expand...
Click to collapse
I have to agree with you Zoki. Has nothing to do with your ROM.

zoki said:
I don't like this topic name. It should be: "I don't know how to install new rom"
Click to expand...
Click to collapse
I'm sorry. I didn't mean to offend you or anything. I just thought I did it the right way the first time and that something went wrong but not on my part because I followed directions doing it. I'm not saying anything bad about the rom. Sorry!!
I'll try to do it with the RUU then. Thanks a lot.

Think I've bricked my Kaiser - Can anyone help?

Hi everyone,
I think I may have bricked my Kaiser. I've been following some similar threads but nothing seems to be working to fix the problem.
I was going through the process to flash a new Rom, starting with installing HardSPL following this thread I was. I was having problems, I think because I have the 1.82 ROM version.
Finally, I thought I had HardSPL installed, so I continued to run KaiserCustomRUU.exe. This completed (jumped from 0% to 100%) very quickly. However, I reset my phone and it is now stuck in the tri-color bootloader screen
The screen has the says:
KAIS130
SPL-1.82.0000
CPLD-8
and has the letters RUUNBH in the top right corner.
I've tried removing the battery and resetting, but the phone always goes back to this screen. I've also tried running mtty, but without success. The command 'readconfig' returned a result 'Command error !!!'.
does anyone know of anything else I can try?

Small bit of good news: if I issue the command 'boot' using mtty, my phone boots into my original ROM successfully, with the mtty output:
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
It takes a long time to boot (like a couple of minutes), but it does eventually boots up fine. When I reset, I'm back at the tri-color screen though

If your at the tri-color screen, just reflash a new rom

Im not an expert but when its at the tri colour screen, try to flash Hard SPL again, it should pick it up and flash i believe.
If that goes through ok, then do the same to flash another ROM.
Again no expert at unbricking but its definately worth a try

japher said:
Small bit of good news: if I issue the command 'boot' using mtty, my phone boots into my original ROM successfully, with the mtty output:
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
It takes a long time to boot (like a couple of minutes), but it does eventually boots up fine. When I reset, I'm back at the tri-color screen though
Click to expand...
Click to collapse
Try this.
1.) Open ActiveSync and navigate to File > Connection Settings - Uncheck Allow USB connections.
2.) Download this ROM http://rapidshare.com/files/5781641...dio_sign_22.45.88.07_1.27.12.11_Ship.rar.html and flash it to your device.
That should work for you.

hi alltheway. thanks for the advice!
I don't want to sound ungrateful, but are you sure the above is safe? I just don't want to make a wrong step now and totally screw up the device (now that I can successfully do a manual boot using mtty).
I know you can't guarantee it but is this what others who are stuck in the bootloader have done?

japher said:
hi alltheway. thanks for the advice!
I don't want to sound ungrateful, but are you sure the above is safe? I just don't want to make a wrong step now and totally screw up the device (now that I can successfully do a manual boot using mtty).
I know you can't guarantee it but is this what others who are stuck in the bootloader have done?
Click to expand...
Click to collapse
I had this problem about 2 weeks ago.
I was flashing one of Dutty's Great ROMs and I lost power at the house and shut down my computer when I was 46% done.
I had the same RUUNBH in the top right hand corner. All I did to fix this was flash a factory shipped ROM like the one I provided to you and it worked great. No issue thus far.
Honestly I can't gurantee 100% if this will totally fix your problem but I am 95% sure.
Unless some other users have an answer for you I think this will be your best solution. Regardless of what you do you will have to flash to a new ROM anyways.

Also, I'm a bit dubious on whether i will be able to flash to that ROM. I don't think I have the right HardSPL installed to flash roms (see what my boot-loader screen says in the first post).
I'm no expert though.... obviously

Thanks for all the info alltheway. I'm too tired now (will probably f*ck the thing up even further! ), so I'll try flashing this tomorrow.
Here's some more info I've collected using mtty (my phone is an O2 XDA Stellar):
Code:
Cmd>info 2
HTCSO2___001¯JG±HTCE
Cmd>getdevinfo
GetDevInfo: Get CID OK
HTCSKAIS1300O__0HTCE

New Thread
Read this:
http://forum.xda-developers.com/showthread.php?t=355910

Hi tqm. I've been following that post but as far as I can tell there is no solution there yet.
From what I can tell from that thread (and others), the only way stop the phone booting to the tri-color screen (in RUUNBH mode) is to flash with a ROM that matches the vendor. I think because I haven't been able to install HardSPL properly, my phone's version of SSPL will only load O2 ROMs (could be wrong here, but that's the picture I'm building ). Unfortunately no-one seems to have extracted the ROM from an XDA Stellar :\
I believe alltheway's solution above worked for him because he had HardSPL installed properly. He could load the stock ROM to fix the phone, because his SSPL version allowed different ROMs to be loaded. I'm not certain of this, and I'll probably try his suggested solution when I get home today... but I'm not too confident.
If only there was an mtty command to just get the phone out of 'RUUNBH' mode. I've seen the command 'task 8' mentioned on here, but it doesn't work when I try it. Does anyone know of a list of mtty commands for the Kaiser anywhere?

Definitely flash the original ROM, it will get your device to the default HTC shipped state.
Then sync phone with ActiveSync, install HardSPL again and then flash custom ROM.
I remember i had the same issue but the original rom is a lifesaver

You mean the original HTC ROM? or the original O2 ROM? (what my phone originally came with)
If I don't have one of the HardSPL versions posted on the forums (I believe they never installed properly, which is what caused all my problems I think), will I still be able to flash the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
Basically my questions is: is this stock HTC ROM flash-able to ALL kaisers? (even without downloading/installing HardSPL from the forums)
If not (i.e. I can't flash even the stock HTC ROM), is it expected that if I can't successfully install HardSPL, my Kaiser will only accept O2 ROMS?

japher said:
You mean the original HTC ROM? or the original O2 ROM? (what my phone originally came with)
If I don't have one of the HardSPL versions posted on the forums (I believe they never installed properly, which is what caused all my problems I think), will I still be able to flash the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
Basically my questions is: is this stock HTC ROM flash-able to ALL kaisers? (even without downloading/installing HardSPL from the forums)
If not (i.e. I can't flash even the stock HTC ROM), is it expected that if I can't successfully install HardSPL, my Kaiser will only accept O2 ROMS?
Click to expand...
Click to collapse
IMHO the HTC stock ROM should work even without HardSPL, at least for me it worked fine... but just for sure have your O2 stock ROM by hand.

jaso2005 said:
Im not an expert but when its at the tri colour screen, try to flash Hard SPL again, it should pick it up and flash i believe.
Click to expand...
Click to collapse
I don't thinks there's a way to flash HardSPL on tri-color scrren so far, coz activesync cannot connected to computer
the best way is trying to find the phone's offcial ship rom to flash

No luck trying to flash with the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
After getting to 1%, it reports an error:
Error [294] : Invalid Vender Id
As suspected, looks like this will only accept an O2 ROM Will have to wait until one is available.

Did you try installing HardSPL and then reflashing?

the stock HTC rom will not load onto your kaiser simply because it is still CID locked to O2's CID code. You HAVE to find the O2 rom that your device came with or any O2 ROM and reflash that and you will be good to go. You may also try and flash HardSPL but I dont think its going to work. But remember have a friend or someone on the forum dump and rebuild the O2 rom for you and just reflash the OS.nb or ROM only no radio!
It is very simple to dump and rebuild a rom so if you have a friend that has a kaiser have him over for an hour and dump his
thats your only shot at this point.

URPREY said:
Did you try installing HardSPL and then reflashing?
Click to expand...
Click to collapse
My current ROM version is 1.82. I don't think installing HardSPL has been solved for this ROM version, which I think is where all my problems started. I have tried, but no version of HardSPL (that I've found) will install correctly.

austinsnyc said:
You HAVE to find the O2 rom that your device came with or any O2 ROM... just reflash the OS.nb or ROM only no radio!
Click to expand...
Click to collapse
Thanks for the reply austinsnyc, this is what I'm hoping to do now, I'm watching this thread 'Has anyone dumped the o2 Stellar rom yet ?' closely Maybe I should reconstruct the ROM myself, I'm just a bit worried about arsing that up as well I'd rather someone experienced reconstructed and verified the ROM (on a phone that isn't already messed up).
Out of interest, would you be able to give me a succinct explanation of what is actually wrong with my phone at present? As far as I can tell, the only problem is that the boot-loader is stuck in RUUNBH mode. Has part of the ROM on the phone actually been destroyed?
I'm assuming right now that the point of flashing the O2 ROM is just to make the phone 'finish' a flash and get out of RUUNBH mode. Or is it actually to re-instate something that has been lost?
If it is to reinstate something that's at present lost, is this data definitely part of the os.nb?
If it's just to get the boot-loader out of RUUNBH mode, I'm REALLY gutted that there isn't just a mtty command to do this
Oh yeah, and perceptivepixel.com Ace!

I'm a newb looking for advice.

Hi, I have a T-Mobile SDA, i think it's called the HTC Tornado. Right now im running WM5, and I want to switch to WM6 (the newest release, i don't know which). I try reading the posts in this forum, but they're kinda overwhelming, I'm not sure if I understand everything. So, can someone point me in the direction to start the upgrading process in a safest way (I don't want to kill the phone). I also want to transfer the contacts I have right now onto WM6.
Thank you everybody.

Hey! Welcome to the forums.
Upgrading/flashing your phone is pretty easy. You just have to follow karhoes guide which is excellent.
This guide was meant for flashing WM6 Roms, but the flashing routine is exactly the same for WM6.1 Roms. So, just follow it step by step and you won't do anything wrong.
I can recommend GnatGoSplat's WM6.1 Rom. I use it for weeks now and didn't experience any problems so far. Try it out. It's in english and T9 languages can easily be added.
--> Guide by karhoe
--> WM6.1 by GnatGoSplat

I agree... the guide is superb and I'm using GnatGoSplats 6.1 as well. Very good, stable ROM. Not had any issues at all

hi, I successfully upgraded my phone to WM6.1, but using another ROM. if I want to change ROM, reflashing, which step do I start ?
thanks

To use another WM6 or 6.1 rom all you have to do is connect to your computer and flash. You don't have to worry about formatting BINFS, or super CIDing anymore.

if you want to flash your phone with another rom you HAVE to "format BINFS" on tera term pro before flashing it with any other WM6, WM6.1 standard,professional tornado ROM's,if you don't "format BINFS" you might be staying with a nice paper weight

I have reflashed my rom a no. of times without formatting ... may be formatting is advisable but without formatting mine is working fine...
Yes i usually use it as a paper weight at office but not a dumb paper weight it is a smart paperweight. Thanks

thacen said:
I have reflashed my rom a no. of times without formatting ... may be formatting is advisable but without formatting mine is working fine...
Yes i usually use it as a paper weight at office but not a dumb paper weight it is a smart paperweight. Thanks
Click to expand...
Click to collapse
keep on doing that and your gonna fill up you device flash,consequently making it unable to boot up do to lack of memory

Reflash without format?!
I wouldn't advise anybody to reflash their device without performing "format BINFS". This operation completely clears all reminants of the existing ROM, thus leaving the device clean and fresh ready for a new ROM. I'm surprised people haven't had conflict issues by missing this step out!

Flash - What Went Wrong?

I've always fancied flashing my Kaiser (V1615) with a new ROM, but was always nervous because I wasn't sure of the process and didn't want to risk bricking the phone as well as all the effort needed to get everything back on it I needed. Well, a few days ago my old Kaiser met the floor and an untimely end. So I decided to take the risk and put a new ROM on it and decided on the latest Dutty WM6.1 ROM.
I read all about flashing on here and made as much sense of it as I could. Thing is, I'm very technical in general, but not very familiar with Windows Mobile or flashing. I found there was lots to read, but it was all written with an assumed level of knowledge and understanding of terminology. As a result I found it quite hard to understand. I took the plunge anyway and started, but things didn't work out as expected and I didn't understand why.
I'm not trying to be critical of all the work a lot of people have put into the documentation that is available online, it's just that when I originally approached this with zero flashing experience I found it difficult and confusing to understand. What I really needed was a concise and basic introduction to flashing. I've now been through the process and after re-reading the documentation it makes a lot more sense.
I worked out you need to run something called HardSPL before you could flash a new ROM. I'm still not sure what HardSPL does apart from CID unlock the device, but what does CID unlock mean?
I ran HardSPL v1 and it started ok, but then I ended up with a white screen. At this point I already wished I hadn't started, but no going back now. Is it known why some phones white screen? Turns out it's a common problem, so followed the instructions to recover. All was well again, but still with the original ROM.
I thought I'd be brave and stuck with it and this time tried JumpSPL1.56-KAIS instead of HardSPL as recommended on one of the tutorials. This went better and I ended up with the Tri-Color screen. I plugged my USB cable in and USB showed on screen.
Next step I thought was to flash a ROM onto the device. I ran the Dutty updater on my PC and all started ok, but when the update got to 18% I received a communication error. I tried to recover using the updater, but the same thing happened. At this point the phone wouldn't boot, so I was more than a little worried and wishing I hadn't started!
Found something that described several options for recovering from this problem. I decided to try and flash the device back to the original ROM from Vodafone. When I eventually found that ROM I ran JumpSPL again, got to the Tri-Color screen and ran the updater. This time the update completed successfully and the phone rebooted and was all working again.
I decided to leave the device as it was and started customising it myself. I'd still love to put a cooked ROM on there, especially if it helps with performance, but after the experience above I'm not very confident.
Can anyone tell me where or what went wrong? I'm going to get my old Kaiser repaired and want to try again on that phone.

My flashing routene (not ideal but it works for me)
1) run the first part of the Kaiser SIM/CID Unlocker & Changer
2) after device reboots, hold camera button and restart to check SPL
3) Flash rom/radio of choice
4) Follow HardSPL v3.07, v3.28, v3.29 and v3.56 by JockyW 's second guide "If you have problems with the above process, try this:" and flash my 3.XX SPL of choice.
Sam

Wow, I need a cuppa now
I'll go through 1 at a time... (and Sam has answered some questions already)
-CID unlock means that when the phone is loading a new device into the ROM the Carrier ID check is removed, each Mobile phone carrier has a different CID in thier OS ROMs. Unlocked means you can flash a OS ROM from any carrier or a cooked OS ROM from this site.
-The Jump SPL should only be used for replacing the SPL. Do not flash anything other than SPL's when at the Jump SPL (or SSPL). OS and Radio ROMs should be flashed from either in Windows Or By Manually Entering the Bootloaders. More info on SPL's is here: http://wiki.xda-developers.com/index.php?pagename=SPL Questions?
-Have a look at flashing from SD Card to avoid communication problems, http://wiki.xda-developers.com/index.php?pagename=KaiserSDFlash
-The most clear instructions can be found here: http://wiki.xda-developers.com/index.php?pagename=HTC_Kaiser#ROMx20.Upgrading
Hope this helps.
Dave

Thanks for the advice, but this is what I normally encounter when I read something on here, which is advice which no doubt makes perfect sense to the author or others experienced in flashing, but usually raises more questions than it answers in my head.
For example;
1) run the first part of the Kaiser SIM/CID Unlocker & Changer
Click to expand...
Click to collapse
What do you mean by the "first part"? The thread you've linked to doesnt really explain what I'm downloading and doing.
2) after device reboots, hold camera button and restart to check SPL
Click to expand...
Click to collapse
Ok. I get this assuming you mean the device will reboot automatically and I restart it to check the SPL version that gets shown on the boot screen, but why do I need to do this?
3) Flash rom/radio of choice
Click to expand...
Click to collapse
So at this point I can simply plug my device into my PC and run the ROM updater I've downloaded. Working out what rom/radio version to download is a minefield in its own right.
4) Follow HardSPL v3.07, v3.28, v3.29 and v3.56 by JockyW 's second guide "If you have problems with the above process, try this:" and flash my 3.XX SPL of choice.
Click to expand...
Click to collapse
I thought HardSPL needed to be run before I flashed? Also, why the different versions? Which one do I choose?

BTW, not trying to moan about everything, just posting my experiences to find out where I went wrong, but also highlight some issues hopefully other flashing newbies can relate to and authors of tutorials can draw some useful feedback from.

Only one question, do I need to CID Unlock before using Jump and HardSpl or, the Hardspl does the Supercid ?
I'm not referring about SIM since I don't care, for now
With WM6.1 - Oficiall HTC ROM
Thanks

Thanks for that one dave, on reflection i kinda missed the whole point of the thread, and as for the majority of the stuff you posted i didnt undertand that to begin with.
Also, DaveTME, if you are wanting to flash a custom rom to youre kaiser. from my experiance and from the number of times ive seen this happen. i advise against asking for reccomendations(sp?) (not saying you will but its worth saying) try a few roms out and decide from there.
Also another thing to note. if you flash to WM6.1 remember to use a 3.xx spl otherwise you'll encounter a few problems with youre device.
Sam
What do you mean by the "first part"? The thread you've linked to doesnt really explain what I'm downloading and doing.
Click to expand...
Click to collapse
download the Kaiser unlocker and run the first stage of it, the program is in the linked thread.
Ok. I get this assuming you mean the device will reboot automatically and I restart it to check the SPL version that gets shown on the boot screen, but why do I need to do this?
Click to expand...
Click to collapse
No, after the device reboots, youre given youre Rom, Protocol and Radio. if you hold the camera button and reset you'll get youre SPL displayed, youre looking for 1.01 olinex to be shown
So at this point I can simply plug my device into my PC and run the ROM updater I've downloaded. Working out what rom/radio version to download is a minefield in its own right.
Click to expand...
Click to collapse
1) Yes, just run the RUU with youre chosen rom and thats it
2) its not a minefield, just make a decision on what rom you like and flash it. theres nothing to stop you flashing another one.
I thought HardSPL needed to be run before I flashed? Also, why the different versions? Which one do I choose?
Reply With Quote
Click to expand...
Click to collapse
The 1.01 SPL will allow you to flash a cutom rom. following that you need a 3.xx SPL as they are designed for windows mobile 6.1. as for yure decision. i use 3.29, yet other users have had better sucess with 3.56. Most rom chefs will say which SPL they reccomend anyway with their rom.

-CID unlock means that when the phone is loading a new device into the ROM the Carrier ID check is removed, each Mobile phone carrier has a different CID in thier OS ROMs. Unlocked means you can flash a OS ROM from any carrier or a cooked OS ROM from this site.
Click to expand...
Click to collapse
Great. Thanks for that. Makes perfect sense now
-The Jump SPL should only be used for replacing the SPL. Do not flash anything other than SPL's when at the Jump SPL (or SSPL). OS and Radio ROMs should be flashed from either in Windows Or By Manually Entering the Bootloaders. More info on SPL's is here: http://wiki.xda-developers.com/index.php?pagename=SPL Questions?
Click to expand...
Click to collapse
Ok. I think you mean that the SPL is a component on the device? What is the difference between HardSPL and JumpSPL?
-Have a look at flashing from SD Card to avoid communication problems, http://wiki.xda-developers.com/index.php?pagename=KaiserSDFlash
-The most clear instructions can be found here: http://wiki.xda-developers.com/index.php?pagename=HTC_Kaiser#ROMx20.Upgrading
Hope this helps.
Dave
Click to expand...
Click to collapse
Thanks, will have a read

DaveTME said:
Ok. I think you mean that the SPL is a component on the device? What is the difference between HardSPL and JumpSPL?
Click to expand...
Click to collapse
Read the "SPL Questions" Wiki Page, it is all there and fairly clear.
Ta
Dave

New to windows mobile, would appreciate help.

Hi everyone, I have recently bought a htc touch pro from polish orange provider. I have browsed dozens of topic, trying to make my windows mobile 6.1 life more satisfying, but I have few questions to ask.
1. What does Hard-Spl do ? And can I hard-spl my phone ?
2. To install advanced config, do I have to jailbreak my windows, or do anything to install it ? I don't want to end up with useless phone
3. When I try to upgrade my default opera browser to the newest build, the instlaler cannot uninstall previous version of opera, neither can I because it is not listed in add/remove programs menu. And, if I ignore the warning, I get an error in installling the newest build, but somehow I have 2 opera mobiles listed in programs menu.
Thanks in advance, r4ster.

r4ster said:
Hi everyone, I have recently bought a htc touch pro from polish orange provider. I have browsed dozens of topic, trying to make my windows mobile 6.1 life more satisfying, but I have few questions to ask.
1. What does Hard-Spl do ? And can I hard-spl my phone ?
2. To install advanced config, do I have to jailbreak my windows, or do anything to install it ? I don't want to end up with useless phone
3. When I try to upgrade my default opera browser to the newest build, the instlaler cannot uninstall previous version of opera, neither can I because it is not listed in add/remove programs menu. And, if I ignore the warning, I get an error in installling the newest build, but somehow I have 2 opera mobiles listed in programs menu.
Thanks in advance, r4ster.
Click to expand...
Click to collapse
I probably can't answer your questions like a pro, but I had a few experience that I can share with you.
1. I don't know what Hard-SPL do, but I guess it's like jailbreak for Windows Mobile device. If you want to flash to a new custom Rom, you need to Hard-SPL it first (don't need to do this if you flash back to the original ROM). And yes, Hard-SPL your device
2. Jailbreak is only a term to unlock your iphone... With a Win Device, you don't need to unlock anything to be able to download and install other software. This is the beautiful part of a Window mobile.
3. Definitively can't help you here... but I know that plenty of thread has been posted for this matter... just do a quick search. However, I strongly suggest (with no responsibility) you to "Hard-SPL" and "CID unlock" your device and flash it to a new ROM. It will make your phone faster and much cleaner. Also, you'll get your new Opera install.
The question now is, which ROM
I suggest NATF's v2.3, but he'll be releasing a v3 today or so. Don't flash to it right away... just flash to v2.3 first and see if v3 is stable or not by reading people posts.
Flashing is not as hard as people claim... just read and be very carefully before you do it. Don't skip any step. The first time is stressful, but after that it's just a daily burger.

pandaboyy said:
I probably can't answer your questions like a pro, but I had a few experience that I can share with you.
1. I don't know what Hard-SPL do, but I guess it's like jailbreak for Windows Mobile device. If you want to flash to a new custom Rom, you need to Hard-SPL it first (don't need to do this if you flash back to the original ROM). And yes, Hard-SPL your device
2. Jailbreak is only a term to unlock your iphone... With a Win Device, you don't need to unlock anything to be able to download and install other software. This is the beautiful part of a Window mobile.
3. Definitively can't help you here... but I know that plenty of thread has been posted for this matter... just do a quick search. However, I strongly suggest (with no responsibility) you to "Hard-SPL" and "CID unlock" your device and flash it to a new ROM. It will make your phone faster and much cleaner. Also, you'll get your new Opera install.
The question now is, which ROM
I suggest NATF's v2.3, but he'll be releasing a v3 today or so. Don't flash to it right away... just flash to v2.3 first and see if v3 is stable or not by reading people posts.
Flashing is not as hard as people claim... just read and be very carefully before you do it. Don't skip any step. The first time is stressful, but after that it's just a daily burger.
Click to expand...
Click to collapse
So, I can flash any rom I want, and still have a fully working phone, after hard spl ?

r4ster said:
So, I can flash any rom I want, and still have a fully working phone, after hard spl ?
Click to expand...
Click to collapse
you have to hard-spl first before Flashing any Rom. Please read those sticky carefully. I do not take any responsibility of what you're doing.
This is what I did (it works for me without any problem)
0- I backup everything I need with PPCPimbackup and outlook
1- I HARD-SPL my device
2- I CID unlock my device
3- Flash to NATF's v2.3 ROM, hard-reset my device
4- Flash new Radio (this step is optional... and to find the best one, you have to test one by one.)
5- Restore my backup
6- Re-install extra software that I need.
Like I mention earlier, these steps work for me, and there are big chance that it will work for you as well... but I do not take any responsibility. Before you Flash to any ROM, HARD-SPL your device. and after flashing your ROM, HARD-RESET it.

pandaboyy said:
you have to hard-spl first before Flashing any Rom. Please read those sticky carefully. I do not take any responsibility of what you're doing.
This is what I did (it works for me without any problem)
0- I backup everything I need with PPCPimbackup and outlook
1- I HARD-SPL my device
2- I CID unlock my device
3- Flash to NATF's v2.3 ROM, hard-reset my device
4- Flash new Radio (this step is optional... and to find the best one, you have to test one by one.)
5- Restore my backup
6- Re-install extra software that I need.
Like I mention earlier, these steps work for me, and there are big chance that it will work for you as well... but I do not take any responsibility. Before you Flash to any ROM, HARD-SPL your device. and after flashing your ROM, HARD-RESET it.
Click to expand...
Click to collapse
Ok, what if the hard spl goes wrong, is there a way to unbrick the phone ?
And thanks for all the help !

r4ster said:
Ok, what if the hard spl goes wrong, is there a way to unbrick the phone ?
And thanks for all the help !
Click to expand...
Click to collapse
Well, first I hope that it doesn't go wrong. And second, I'm pretty sure you can stand the temptation of flashing to a new ROM, so you'll probably going to do it very soon. But Third, So far I haven't seen any thread that someone can unbrick their Touch Pro after a bad flash (he/she didn't Hard-spl before flashing, that's why)... However, there is a way to do it with the Kaiser... so don't lose hope there.
Just READ everything carefully, you have a 99.5% successful rate if you do. I would say that the 0.5% is just your bad luck (example Computer stop working during the flash... but that's just pure bad luck and you can't blame anyone but God)