Database Info

Crossbow Underground Help Please

25 minutes looking on the forums didn't really help me with what i need help with. i flashed Crossbow from a CID unlocked ex Faria aku 3.3 XDA Mini S, and i couldn't get signal, or play any sounds, in addition...the phone was extremely slow! i read that this is due to my device being CID unlocked, when i should flash an operator rom (to reCID lock it), then continue with the upgrade. surely this contradicts what threads say about phones MUST be CID unlocked otherwise you'll brick your phone etc. how can i get Crossbow Underground to be stable, and run normally?
also, my Faria 8mb aku 3.3 has moments of being lightning fast, and long periods of being stupidly slow (i.e. 10 seconds to unlock the phone from standby), does anybody know why it does this, and what i could do to fix it. Hard reset didn't do anything, and it's only getting slower. if i just left the phone after it being really slow, normally it will sort itself out and run fast again, after half an hour or so. the processor is set to default (not that this makes a difference as 260mhz doesn't speed it up), and i only have the normal programs on there.
any help atall will be greatly appreciated,
thanks,
thepolice

thepolice said:
25 minutes looking on the forums didn't really help me with what i need help with. i flashed Crossbow from a CID unlocked ex Faria aku 3.3 XDA Mini S, and i couldn't get signal, or play any sounds, in addition...the phone was extremely slow! i read that this is due to my device being CID unlocked, when i should flash an operator rom (to reCID lock it), then continue with the upgrade. surely this contradicts what threads say about phones MUST be CID unlocked otherwise you'll brick your phone etc. how can i get Crossbow Underground to be stable, and run normally?
Click to expand...
Click to collapse
I'm running Most Beautiful Edition so can't comment on Underground specific issues, but I don't think anyone has said that you should re-CID Lock your phone (actually I don't think you can, but thats another topic ). What I have suggested (and seen others suggest) is to always go back to an official ship ROM before upgrading. I went from Faria's AKU 3.3 straight to MBE and had all sorts of weird issues (active sync problems, Outlook complaining the calendar was corrupt, and more). I was frustrated and reflashed the TMobile 2.26 rom to go back to Faria's then it hit me I didn't do this before doing WM6. So I put MBE back on, and its worked great since. So I'm a firm believer now to take the extra time to move back to a shipped official ROM before loading a new custom one..
...the processor is set to default (not that this makes a difference as 260mhz doesn't speed it up)
Click to expand...
Click to collapse
Use batterystatus (for me I'm using .04.200 and not the beta 1.x one as it caused me issues) and have that overclock your device. If you can't see a difference, then I wonder if you have some hardware issue with your Wizard. I'm now running overclocked at 260Mhz via BatteryStatus and its been very stable and there is a definite improvement.

mfrazzz said:
I'm running Most Beautiful Edition so can't comment on Underground specific issues
Click to expand...
Click to collapse
Thanks, that was really useful
I can't run Most Beautiful, when i flashed it, it wouldn't boot atall. But this may be because i didn't flash the shipped rom before, is this likely?
When i flash the shipped rom, upon boot, the spl and ipl go back to 2.26...surely this means it's relocked. Should i flash the t-mobile rom instead? or wont this work as it wasn't the shipped rom - if that makes sense.
anyway, thanks so much for you help, you've explained a lot to me

thepolice said:
I can't run Most Beautiful, when i flashed it, it wouldn't boot atall. But this may be because i didn't flash the shipped rom before, is this likely?
Click to expand...
Click to collapse
Thats possible. can't say its likely, but its possible
When i flash the shipped rom, upon boot, the spl and ipl go back to 2.26...surely this means it's relocked. Should i flash the t-mobile rom instead? or wont this work as it wasn't the shipped rom - if that makes sense.
Click to expand...
Click to collapse
Yes when you flash the shipped rom the IPL/SPL will change to what comes with that ROM (for TMobile one it will be 2.26). That does NOT relock it. Only if you go back to a 1.x ROM will you have to deal with being relocked.
Example, I'm on a Cingular 8125. If I tried (out of the box) to flash the TMobile 2.26, it wouldn't work as its CID Locked. But after doing the CID Unlock, I can now flash TMobile, QTEK, O2, or whatever because it is CID Unlocked. And as long as I stay with 2.x roms, I can switch around as much as I want (it does't get relocked).
So definetly go back to an official shipped rom (and Tmobile 2.26 is the highly recommended one by about everyone), and then flash whichever custom rom you want to try. Its extra work to reflash an official rom but I think it removes problems some people see when they go from custom to custom.

thank you very much, i got my phone sorted now, and everything is clear to me.

It's okay now...got it sorted

Just curious, but what are you running now? And what worked for you?

mfrazzz said:
Just curious, but what are you running now? And what worked for you?
Click to expand...
Click to collapse
Right now i'm running the Faria 8mb. i was running Crossbow Underground, but i didn't see the point in going to all the efforts to fix the keyboard problems (because then I'd have to fix the predictive text) as the Faria Crossbow rom is coming out soon, i'll just get that...can't wait!
All the problems i had seemed to be becuase i wasn't flashing the shipped rom before the new one.

AT&T Tilt blank screen after Kaiser Sim Unlocker!

The screen remains black, blank, and does not light up, even though activesync knows the device has booted because the icon becomes green. I can't navigate any controls, though the keys do light up when I slide it, or press buttons. Screen remains blank/black.
Here is what I did to get to this state:
1) I first hard reset my Kaiser, to reset all user preferences. This I accouplished by pressing both soft keys while pressing power (if I recall correctly), then hitting the green call button. It then installed Windows Mobile fresh.
2) I then followed the HardSPL instructions, here:
http://forum.xda-developers.com/showthread.php?t=361236
Everything went fine.
3) I then followed the Kaiser Sim Unlocker instructions here:
http://forum.xda-developers.com/showthread.php?t=361039
After completing step 5, the device rebooted, the AT&T icon displayed, then the screen goes blank and stays that way.
What should I do? Did I miss something? Is this recoverable?

It also does not have any sound. Does this mean I can't unlock?
How do I flash back to the original rom?

Ok, looks like have version 1.27.12.11 rom, during boot.... according to this page it isn't ok for my AT&T Tilt device.
http://forum.xda-developers.com/showthread.php?t=393182
So does this mean I have to pay to unlock? Or is there some way to do it still? Thanks.

NetTechie said:
Ok, looks like have version 1.27.12.11 rom, during boot.... according to this page it isn't ok for my AT&T Tilt device.
http://forum.xda-developers.com/showthread.php?t=393182
So does this mean I have to pay to unlock? Or is there some way to do it still? Thanks.
Click to expand...
Click to collapse
Try flashing this radio.
http://www.4shared.com/file/36681926/36b4832d/KAIS_Radio_Only_1271211_CustomRUU.html
I guess you didn't read step 10

I have a problem... it wont go green now, I can't get activesync to go green. I wont be able to load the rom... what can I do?
[ EDIT ]
A reboot fixed this *sigh of releif*. Goes green now.

AllTheWay said:
Try flashing this radio.
http://www.4shared.com/file/36681926/36b4832d/KAIS_Radio_Only_1271211_CustomRUU.html
I guess you didn't read step 10
Click to expand...
Click to collapse
Ok, question: Will I use the file in Step 3 to put that on the phone? It is saying there is a file open...? I can't disable USB on the device, as the screen is blank.
[EDIT] Looks like everything I needed was in the download. I put the other ROM back on. However, I'm having a problem with activesync... When I click on Connection Settings active sync freezes up. Any ideas what to do to fix ActiveSync so I can turn off USB, without crashing ActiveSync?

Okay, I got the screen with the unlock code... only it gave me this readout:
Your Unlockcode = ........
just like that, with dots.
Is there any way to unlock a phone, if the screen goes black? I can go back to the old firmware, but this special firmware is needed I think to do the unlock, and this special firmware makes the screen go black on my model.
EDIT: On page 33 of the Kaiser unlocker topic, I found what looks like my answer. I need the AT&T 1.57 ROM, as it is compatible with this patched radio so the display will work. Unfortunately, I haven't been able to find it on this forum yet. EDIT 2: Found it, loading it on now: http://www.4shared.com/file/3857459...ULAR_WWE_157_-_Originaly_Shipped_ATT_ROM.html

Unlock worked, once I had the AT&T 1.57 version of the ROM on there. ActiveSync still freezes, but I uninstalled it for the section where I was supposed to disable USB. Installed the 1.27.12.11 radio after completing the unlock, replacing the patched radio. All finished.

Mine still showsup Blank screen
Hi,
I followed the same steps as yours :
Firstly I reset my Kaiser & then followed the HardSPL instructions, here:
http://forum.xda-developers.com/showthread.php?t=361236
Everything went fine.
I then followed the Kaiser Sim Unlocker instructions here:
http://forum.xda-developers.com/showthread.php?t=361039
After completing step 5, the device rebooted, the AT&T icon displayed, then the screen goes blank and stays that way
Now I tried flashing
http://www.4shared.com/file/36681926...CustomRUU.html
But it didnot help (
Can you please tell me what I should be doing next..

vrramakanth said:
But it didnot help (
Can you please tell me what I should be doing next..
Click to expand...
Click to collapse
what do you mean when you say it "didn't help"?

I still get the blank screen..I am now downloading the AT&T 1.57 version .. I am hoping if I install this I will get the display and I can proceed to step 8a, 8b,..

Sorry to be short,
But did you even bother reading through the other threads with the exact same problem as you?
the problem you have is that you flashed an incompatible radio with the ROM that you are runing on the phone. You need to reflash the ROM with a rom that is compatible with the radio or reflash the radio rom to what came with the phone rom that you are running.
You should have upgraded to a 6.1 cooked rom prior to doing the SIM/CID unlock.
Flash your phone with a cooked 6.1 rom that INCLUDES the radio, and then try the CID/SIM unlocker.
my two bit.

I am trying with http://www.4shared.com/file/38574592...d_ATT_ROM.html, which is the ROM that comes with this phone. Do u think this helps? Do u want me to flash 6.1 ROM instead of this?

No,
Unless you know the stock ROM comes with a compatible radio, it will not work. The problem you are having is because you loaded a radio that is not compatible with the stock rom.
If you already have hardspl loaded, then load a cooked 6.1 ROM that includes a compatible radio (for example L26 v9 rom or Sleuth 3.0 rom).

ok..am a BIG novice here..may be a bad question..I have Windows 6.0 on the mobile..so the Cooked 6.1 ROM L26 that I found http://forum.ppcgeeks.com/showthread.php?t=26925 fits into this? Do I need to upgrade to 6.1 before this? sorry if its a wrong question ..

vrramakanth said:
ok..am a BIG novice here..may be a bad question..I have Windows 6.0 on the mobile..so the Cooked 6.1 ROM L26 that I found http://forum.ppcgeeks.com/showthread.php?t=26925 fits into this? Do I need to upgrade to 6.1 before this? sorry if its a wrong question ..
Click to expand...
Click to collapse
It's not a wrong question
1. Yes, that fits in
2. No, you do not need to upgrade to 6.1 before this, flashing the ROM will take care of it
hope this helps

Thanks mbarvian!!
So I am Installing the upgrade to 6.1 ROM, but do I still need to install the correct AT&T ROM that you gave me in the other thread http://forum.xda-developers.com/showthread.php?p=2452022#post2452022?
Thanks!!

Alibaba0101 said:
No,
Unless you know the stock ROM comes with a compatible radio, it will not work. The problem you are having is because you loaded a radio that is not compatible with the stock rom.
If you already have hardspl loaded, then load a cooked 6.1 ROM that includes a compatible radio (for example L26 v9 rom or Sleuth 3.0 rom).
Click to expand...
Click to collapse
I now installed a 6.1 ROM..now do I need to downgrade to be able to do SIM unlock?
From http://forum.xda-developers.com/showthread.php?t=361039 it says :
Note for WM6.1 users
================
Do not try this on 6.1! You will need to downgrade to 6.0
Click to expand...
Click to collapse

vrramakanth said:
I now installed a 6.1 ROM..now do I need to downgrade to be able to do SIM unlock?
From http://forum.xda-developers.com/showthread.php?t=361039 it says :
Click to expand...
Click to collapse
Yes, now you would want to download and flash the ROM I gave you in the other thread
here's the link:
http://rapidshare.com/files/55298724/RUU_Kaiser_CINGULAR_WWE_.exe

I am trying with http://www.4shared.com/file/38574592...d_ATT_ROM.html is this fine??

Noob help w/ATT Fuze + WM6.5

Trying to flash my AT&T Fuze with HardSPL so I can pop a ROM of WM6.5 on it. Not having any luck.
I run the HardSPL executable, it sees the phone (with the current 5.11.XX... ROM version), and then when I hit OK, and see the progress bar (at 0%), it just sits there for about 45 seconds, then gives me a communications error.
Tried this on WinXP and Win7 with the same results. What am I doing wrong?

crescent.wire said:
Trying to flash my AT&T Fuze with HardSPL so I can pop a ROM of WM6.5 on it. Not having any luck.
I run the HardSPL executable, it sees the phone (with the current 5.11.XX... ROM version), and then when I hit OK, and see the progress bar (at 0%), it just sits there for about 45 seconds, then gives me a communications error.
Tried this on WinXP and Win7 with the same results. What am I doing wrong?
Click to expand...
Click to collapse
Is the phone new. We have reports that the SPL Loader changed and prevents flashing HardSPL. Check ur SPL it should not read anything different from 1.90. If it is a higher number then.
Go to the Hardspl thread and flash the 1.90 stock spl frome there first.

Yes, the phone is brand new.
SPL-5.10.0000 is displayed when I enter the bootloader. Would you mind pointing me in the right direction with the HardSPL thread (where I can flash to 1.90)? Can't seem to find it.

crescent.wire said:
SPL-5.10.0000 is displayed when I enter the bootloader. Would you mind pointing me in the right direction with the HardSPL thread (where I can flash to 1.90)? Can't seem to find it.
Click to expand...
Click to collapse
The 1.90 u can find in the HardSPL thread. But check if its ok to get from 5.1 to 1.90
I was more thinking from 1.9XXX to 1.90, so still within the 1.9 loaders. Dunno if its ok for the 5.1 to go down. It should but not shure about that.

Great. I'll check it out. Worse comes to worst, I just may not be able to throw WM6.5 on this, correct?

crescent.wire said:
Great. I'll check it out. Worse comes to worst, I just may not be able to throw WM6.5 on this, correct?
Click to expand...
Click to collapse
well when hardspl works, everything is possible. All the GSM roms are also for fuze afak

http://forum.xda-developers.com/showpost.php?p=4209384&postcount=589
Look through the HardSPL thread, seems that 5.1 Fuze is working with the 1.9 SPL.

Okay, so I was able to boot into the bootloader, where it tells my SPL is 5.1. I can get the HardSPL exe to run and get all the way to the Progress Bar screen (and the phone also jumps to a grey screen with a progress bar), but they both sit at 0% for about 1 min, then it cancels and says "ERROR(262): Update Failed."
Any ideas?

I also had this issue. I did the CID unlock first, then HSPL. I was then able to complete the upgrade.

No joke. I'll have to try that, then.
And, in anyone's opinion, what's the best cooked ROM to be using? EnergyROM?

crescent.wire said:
Okay, so I was able to boot into the bootloader, where it tells my SPL is 5.1. I can get the HardSPL exe to run and get all the way to the Progress Bar screen (and the phone also jumps to a grey screen with a progress bar), but they both sit at 0% for about 1 min, then it cancels and says "ERROR(262): Update Failed."
Any ideas?
Click to expand...
Click to collapse
Are you doing this through activesync. I asume you are. Make sure the file is placed on your main drive of the computer and ran from there. It cannot be in folders hidden. Otherwise it won't work. I had this issue with prior devices while upgrading.

crescent.wire said:
No joke. I'll have to try that, then.
And, in anyone's opinion, what's the best cooked ROM to be using? EnergyROM?
Click to expand...
Click to collapse
That is kind of like asking which is the best baseball team, NASCAR driver, flavor of potato chip or type of candy. Some cooks go for stability. Other cooks go for the latest release. Some cooks throw in all kinds of goodies. Other cooks put an the absolute minimum in the ROM, so the users can add just what he wants. You may hate my favorite ROM and I may hate your favorite ROM. That is why there are so many ROMs to choose from and all these wonderful cooks making them. Try a several different ROMs and see which you prefer.

Mxdadevolper said:
I also had this issue. I did the CID unlock first, then HSPL. I was then able to complete the upgrade.
Click to expand...
Click to collapse
And how might one go about unlocking the CID first?

yamilrx said:
Are you doing this through activesync. I asume you are. Make sure the file is placed on your main drive of the computer and ran from there. It cannot be in folders hidden. Otherwise it won't work. I had this issue with prior devices while upgrading.
Click to expand...
Click to collapse
Yep, doing all that. Thanks, though.

dlweston said:
That is kind of like asking which is the best baseball team, NASCAR driver, flavor of potato chip or type of candy. Some cooks go for stability. Other cooks go for the latest release. Some cooks throw in all kinds of goodies. Other cooks put an the absolute minimum in the ROM, so the users can add just what he wants. You may hate my favorite ROM and I may hate your favorite ROM. That is why there are so many ROMs to choose from and all these wonderful cooks making them. Try a several different ROMs and see which you prefer.
Click to expand...
Click to collapse
A fine point, to be sure.

Sorry, all -- kind of got ahead of myself with all these replies.
So, can anyone point me in the right direction for unlocking my phone's CID?

Simple question
crescent.wire said:
Yep, doing all that. Thanks, though.
Click to expand...
Click to collapse
I have one question. Do you have the phone in "ActiveSynch" mode before running the HardSPL? I found that running it while in the "BootLoader" does not work well, when running the HardSPL.
So, activesynch --> run the hardspl --> make sure you click "Ok", when the phone prompts you, if it is okay to run the 2 executables on your phone --> then watch your phone restart into the "bootloader", then update the hardspl...
Just observation from my past experience...

cso5874 said:
I have one question. Do you have the phone in "ActiveSynch" mode before running the HardSPL? I found that running it while in the "BootLoader" does not work well, when running the HardSPL.
So, activesynch --> run the hardspl --> make sure you click "Ok", when the phone prompts you, if it is okay to run the 2 executables on your phone --> then watch your phone restart into the "bootloader", then update the hardspl...
Just observation from my past experience...
Click to expand...
Click to collapse
Hmmm... I do not have it in ActiveSync mode. I actually have an Exchange connection set up on the phone right now with work. So I should remove that connection, set it to sync ONLY with my desktop, then run HardSPL with ActiveSync 4.5 (on XP) // WMDC (on Vista/7) open?
That's good advice, if I understand you correctly. Thank you!

Did u try to go Stock 1.90 first before doing HardSPL or did u try to flash direct to the unsigned 1.9 ?
As far as I know u have to switch from 5.1 first to the 1.90 signed and then to the unsigned version. See the hardspl thread for more info. Go to this
STEP BY STEP HOW TO RETURN TO STOCK SPL
first.

schnitzelbrain said:
Did u try to go Stock 1.90 first before doing HardSPL or did u try to flash direct to the unsigned 1.9 ?
As far as I know u have to switch from 5.1 first to the 1.90 signed and then to the unsigned version. See the hardspl thread for more info. Go to this
STEP BY STEP HOW TO RETURN TO STOCK SPL
first.
Click to expand...
Click to collapse
Awesome. I'll give that a shot, too. Thanks, guys!

[Q] wrong rom update, what now?

Hello everyone.
Yesterday I saw that there was a new update of my favourite rom EnergyRom. So today I downloaded it, installed it, everything went well. Until I restarted my Raphael ( raph300 btw). It kept stucking on the bootscreen.. even after I installed the rom again it still stucked at bootscreen. So I began trying to fix it with installing my hardSPL again, that didn't work either, still no further than my bootscreen.. after a while I decided to downgrade my spl to my stock-spl. that went well but still stuck on bootscreen. So I tried to install my stock-rom from my provider: (t-mobile netherlands). But then the Rom updater stuck at 0% and I received the well-known [262] error. Suddenly I saw that I stupidly accidentally installed the cdma version of EnergyRom instead of the one I needed: GSM. That explained why it wouldn't boot in the first place. Now I tried to install the olinex hardspl, but the updater stopped everytime with the 262 error. I connected my device to another computer with windows XP, but there I saw that the computer recognized it as a CDMA device.
I know it is a stupid mistake, but is there anybody who knows what I could try? I also tried to hard-reset it, but that wouldn't help either. Any help would SO be appreciated

try to search a tool called MTTY maybe it helps

lvxincad said:
try to search a tool called MTTY maybe it helps
Click to expand...
Click to collapse
Thanx, but how can I use this in combination with my problem?

As I remember 2 years ago,HardSPL is somehow depended on RadioROM. Maybe the ROM influenced the Radio with HardSPL,so try to reflash HardSPL again and Radio. Or it works absolutely not?
http://forums.techarena.in/hardware-peripherals/1161954.htm
http://forum.xda-developers.com/showthread.php?t=371154
http://htcwiki.wetpaint.com/page/RUU+Error+List

TomasNM said:
As I remember 2 years ago,HardSPL is somehow depended on RadioROM. Maybe the ROM influenced the Radio with HardSPL,so try to reflash HardSPL again and Radio. Or it works absolutely not?
http://forums.techarena.in/hardware-peripherals/1161954.htm
http://forum.xda-developers.com/showthread.php?t=371154
http://htcwiki.wetpaint.com/page/RUU+Error+List
Click to expand...
Click to collapse
No, I can't update any ROM. So now i'm stuck with my stock SPL, therefore I wanted to Hard SPL my device, but that didn't work and since then I haven't been able to update any ROM.. would flashing on a different PC help maybe? now I am on a Win7 Pc but maybe it will work in WinXP..

It is also not a bad idea to try different PC with XP to flash. I remember apx.1 month ago I tried to update HTC Trinity with WM6.5 ROM and it keeps failed with some errormessage(nowadays I can't remember which,but the syndroms was similar). Then I considered it as "bricked",until I tried another PC and everything wents correctly and the phone is in its productivity again. Yes,tfirst PC was company notebook with lot of safety kind of software(firewall,this,that,etc...) and the second one was my private laptop at home,just equipeed with regular antivirus software,all updates disabled(instead of AV).

Btw,what about trying to flash official ROM,while you are with stockSPL? Maybe it helps you to startup again the device and then HardSPL again afterwards...

TomasNM said:
Btw,what about trying to flash official ROM,while you are with stockSPL? Maybe it helps you to startup again the device and then HardSPL again afterwards...
Click to expand...
Click to collapse
yeah, that's what I thought too. I tried that also, also tried other custom roms btw before going to the stock rom. But with the stock rom it also stuck at 0% on the update

so, today I tried to flash my rom with two different computers: one with win7 and one with winXP. didn't work either.. I read the MTTY thread and after I installed the custom driver I was able to connect trough MTTY. But what commands should I use to clear the ROM and is there any way that I can update my rom via MTTY?

search MTTY on the forums the first link has all you need to clear the rom and flash via MTTY

I think you may be screwed. You should've asked for help before you started messing with the spl. I don't understand why you thought reverting to the stock spl would be a good approach; it may well be the end of your device. What you should have done is just flashed a stock rom-that would probably have restored your device. Re-flashing hard spl is kind of pointless. The only thing that can over-write hard spl is the special 'stock spl' that olinex put together. It's not entirely stock, and I am not sure that it can be over-written by hard spl. The sole purpose of the 'return to stock spl' is so that you can flash a stock rom, then restore the spl so that you can return your device for warranty/service without being dinged for having unofficial firmware on the device. When you do this, you aren't anticipating getting the device back, so I'm not sure that hard spl can over-write it. I know there have been discussions on whether or not it can be over-written, but I'm not sure that there was ever a clear answer. Anyway, with the 'stock spl' on the device, you can't flash any cooked roms to the device. If you are very lucky, you may be able to flash a stock rom. So, my advice is to try a few stock roms.
I'm pretty sure you'll need hard spl to run mtty/task 29, so I wouldn't waste your time on that. I really doubt it works, and I'm not sure what it's going to buy you, anyway. You really need to be able to flash a rom to the device, and you can't flash a cooked rom with that spl. Maybe you can flash a stock rom, but maybe not. I'm not sure which carrier it will let you upgrade to, either.

NeoTokyo22 said:
search MTTY on the forums the first link has all you need to clear the rom and flash via MTTY
Click to expand...
Click to collapse
yes I did, but the problem is that I can't access my Internal Storage, so I can't put any ROM's on that. Tonight I tried to flash a ROM via my SD card, but when I put my device in bootloader-mode it kept saying that it was 'loading...'

If the bootloader just says 'loading', then you probably need to either reformat the card to FAT32 or rename the image to RAPHIMG.nbh. Make sure you get the extension correct (not RAPHIMG.nbh.nbh).
But you're not going to flash anything with the stock spl, anyway. You need hard spl. I'm not sure you can even flash a stock rom off of the sd card-it probably needs to do it over usb.

I updated lot of smartphones already,but it was already few years ago. However I think,that SP's are flashed with MTTY. For that I needed ROM image in nbh file and with some commands you tell the PC,that it should flash it. Don't forget to disable USB connection in Activesync on XP in case MTTY will connect.

TomasNM said:
I updated lot of smartphones already,but it was already few years ago. However I think,that SP's are flashed with MTTY. For that I needed ROM image in nbh file and with some commands you tell the PC,that it should flash it. Don't forget to disable USB connection in Activesync on XP in case MTTY will connect.
Click to expand...
Click to collapse
I already managed to connect my device with MTTY, the only thing I need to know is which commands I can use to flash the ROM through MTTY. It just sucks that I am not able to go to my Internal Storage, otherwise it would be much simpler I think.

Farmer Ted said:
I think you may be screwed. You should've asked for help before you started messing with the spl. I don't understand why you thought reverting to the stock spl would be a good approach; it may well be the end of your device. What you should have done is just flashed a stock rom-that would probably have restored your device. Re-flashing hard spl is kind of pointless. The only thing that can over-write hard spl is the special 'stock spl' that olinex put together. It's not entirely stock, and I am not sure that it can be over-written by hard spl. The sole purpose of the 'return to stock spl' is so that you can flash a stock rom, then restore the spl so that you can return your device for warranty/service without being dinged for having unofficial firmware on the device. When you do this, you aren't anticipating getting the device back, so I'm not sure that hard spl can over-write it. I know there have been discussions on whether or not it can be over-written, but I'm not sure that there was ever a clear answer. Anyway, with the 'stock spl' on the device, you can't flash any cooked roms to the device. If you are very lucky, you may be able to flash a stock rom. So, my advice is to try a few stock roms.
I'm pretty sure you'll need hard spl to run mtty/task 29, so I wouldn't waste your time on that. I really doubt it works, and I'm not sure what it's going to buy you, anyway. You really need to be able to flash a rom to the device, and you can't flash a cooked rom with that spl. Maybe you can flash a stock rom, but maybe not. I'm not sure which carrier it will let you upgrade to, either.
Click to expand...
Click to collapse
Oke, thanx for your input. I tried to reset my ROM memory with mtty/task 29, but that didn't work, just like you predicted. So my next question is: 'Is there any app that can perform the task 29 without MTTY?'. I googled it, but I could only find the task 29 app for the HTC HD2.. And further, does anybody have a recovery ROM for my RAPH300? I tried the stock ROM on the XDA thread of HTC Raphael, but still got the 262 error

There's really no point in doing Task 29. The bad rom isn't what's killing you now, it's the SPL. It's going to block task 29, no matter what you try (that's one of it's jobs). You should just try to get hard spl back on the device, or try flashing every stock rom you can find. I tend to doubt that either will work, though. The only other option would be to look up the jump spl developed by PoF. I don't remember the name (search for threads started by him), but it was a universal soft spl that would temporarily CID unlock devices so you could flash custom roms. I've never used it before, and I don't know how it loads. You may not be able to load it onto your device with its current state, and it may not even be compatible with a Raphael (it's 3 or so years old), but it's probably worth at least checking out.
Edit: here's the jump spl link. I think you may have to activate it off the device.

[Q] Trouble unlocking/flashing HTC Arrive- DFT HSPL, 7.8 Sianto Edition AL v1.6

Good day.
I have an HTC Arrive on Sprint (CDMA, of course) that I'm trying to update to WP7.8. Specifically, I'm trying to use the HTC Arrive 7.8 Sianto Edition AL ROM.
I used this guide to downgrade the SPL to v.1.25... and the MID number is correct.. I then open up the downloaded ROM folder, and click on ROMUpdateUtility. It skips most of the steps that the user guide for the DFT, but I suppose I could attribute that to it being in the ROM folder itself and selection of the ROM being unnecessary.
Whenever I execute the ROMUpdateUtility file, after I have set the phone into bootloader mode (volume down + power button), it skips right to the flashing process. However, it then sits at 0% for a few minutes and exits with error code 262, which, according to documentation:
ERROR [262, 276, 284, 302] : UPDATE ERROR
This error occurs during the CE ROM code upgrade process.
Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue.
Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode.
Click to expand...
Click to collapse
The phone itself still works; it's not a brick. What exactly is going on here? How do I flash it correctly? If this is in the wrong section, just let me know.

Hello. I just recently flashed my Arrive to Wp7.8 with no problems. I chose the LEAD rom though. May I ask why you want the Sianto Edition? I have seen in the thread for that rom that a few people are having issues installing it. I flashed the LEAD rom with no issues and it is great.
You said that you did downgrade your SPL, did you also install both RSPL and HSPL? I don't know if it makes any difference, but as soon as the HSPL installed and the phone rebooted into the boot loader, I began the installation of the new rom. When you attempt to flash it are you seeing "Cotulla" on you phones boot loader? Also be sure that the bottom portion says USB and not Serial. If it says Serial, unplug the phone and plug it back in, it should then turn to USB and you can proceed to flashing.
Hope this helps
Edit - also, are you running the RUU as Admin? You must Run As Administrator when flashing. Right click the EXE and Run As Administrator

x_orange90_x said:
Hello. I just recently flashed my Arrive to Wp7.8 with no problems. I chose the LEAD rom though. May I ask why you want the Sianto Edition? I have seen in the thread for that rom that a few people are having issues installing it. I flashed the LEAD rom with no issues and it is great.
You said that you did downgrade your SPL, did you also install both RSPL and HSPL? I don't know if it makes any difference, but as soon as the HSPL installed and the phone rebooted into the boot loader, I began the installation of the new rom. When you attempt to flash it are you seeing "Cotulla" on you phones boot loader? Also be sure that the bottom portion says USB and not Serial. If it says Serial, unplug the phone and plug it back in, it should then turn to USB and you can proceed to flashing.
Hope this helps
Edit - also, are you running the RUU as Admin? You must Run As Administrator when flashing. Right click the EXE and Run As Administrator
Click to expand...
Click to collapse
Yeah, some idiot (who shall remain nameless because my ego is fragile) didn't do HSPL after RSPL. Installed fine after that.
Sorry to bother you guys :silly:

Glad to here you got it installed!