Related
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.
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
I have a Tilt that has been security unlocked, currently using Hard spl 3.56.
I have been having issues flashing certain ROMs, a few of them are Garmin's DK10 Final, Anryl's 21232, and some others.
Regardless if I flash using USB or SD Card certain ROMs will error out. If I'm using windows to flash I get the error 270, which is not in the wiki. Also this happens after it shows a complete load of the rom at the point where the phone reboots. If I flash from SD Card it will get better than 80% then error out with a code of 00018003.
Now this does not happen on all roms, for instance I can flash DK8 Final and Anryls 21222 rom with success just as an example.
What I've done, today I went so far as to flash the radio from hell (even though I doubt I needed to so that I can follow the recovery guide again (I was stuck with the radio from hell for a while when I flashed the AT&T rom that included it and used the guide to recover from it and in the process Security Unlock my Tilt) so I could format my entire device.
I have tried different versions of Hard SPL, Different radios, downloaded the suspect roms several times on several computers at home and work with the same results.
MTTY shows no issue with the NAND that I could find.
Any help with this issue would be greatly appreciated.
z
error 270
Upgrade error number 270 means that the bootloader is not correct for the rom you are trying to flash, have you installed Hard SPL 1.20 (or a later version) to your device before attempting to upgrade, and could you tell me which rom you are trying to flash to your device?
thefatboy said:
Upgrade error number 270 means that the bootloader is not correct for the rom you are trying to flash, have you installed Hard SPL 1.20 (or a later version) to your device before attempting to upgrade, and could you tell me which rom you are trying to flash to your device?
Click to expand...
Click to collapse
Garmin's DK10 Final, Anryl's 21232 and as stated I've tried several versions of HardSPL, was using 3.56 I have tried 3.34 which is the one Anryl states he is using. Same issue.
I would recommend cmonex (.hard2) 3.31 Hard SPL nostuckinSPL Force USB as I have flashed all the roms you listed with this, with out any problems, have you also tried to flash a stock rom first I know this approach is old school but still worth a try
thefatboy said:
I would recommend cmonex (.hard2) 3.31 Hard SPL nostuckinSPL Force USB as I have flashed all the roms you listed with this, with out any problems, have you also tried to flash a stock rom first I know this approach is old school but still worth a try
Click to expand...
Click to collapse
Yeh, htc and at&t stock 6.1 roms install without issue
hard spl and super cid again
anryl said:
hard spl and super cid again
Click to expand...
Click to collapse
just did this and it made no difference. still failing!
What is odd is it only happens with certain roms.
zPacKRat said:
Yeh, htc and at&t stock 6.1 roms install without issue
Click to expand...
Click to collapse
I take this back, I tried the 6.1 rom for the tilt and it fails as well.
I've read the wiki article about SPLs, located here
http://wiki.xda-developers.com/index.php?pagename=SPL Questions?
What is the difference between Flashing and installing?
And I've a few clarifications to make. There was this note that says "You should never use a SoftSPL to flash a full ROM to your device. You should only use them to flash a new SPL and once the new SPL is on your device, then flash the ROM! This is why you need to extract the SPL and flash it first and then once it is "HARD" on your device you can flash the ROM."
From what I understand, a SoftSPL cannot be used immediately until the SPL is extracted first, then flash it, then flash the ROM.
Then why not provide 2 things, the extracted SPL and the ROM, rather than both in one, and thereby create the need for the warning in the article?
Sorry if I sound like a noob, cos I really am!
Thanks!
ferns_mccanus said:
I've read the wiki article about SPLs, located here
http://wiki.xda-developers.com/index.php?pagename=SPL Questions?
What is the difference between Flashing and installing?
And I've a few clarifications to make. There was this note that says "You should never use a SoftSPL to flash a full ROM to your device. You should only use them to flash a new SPL and once the new SPL is on your device, then flash the ROM! This is why you need to extract the SPL and flash it first and then once it is "HARD" on your device you can flash the ROM."
From what I understand, a SoftSPL cannot be used immediately until the SPL is extracted first, then flash it, then flash the ROM.
Then why not provide 2 things, the extracted SPL and the ROM, rather than both in one, and thereby create the need for the warning in the article?
Sorry if I sound like a noob, cos I really am!
Thanks!
Click to expand...
Click to collapse
Think of it in PC terms, installing is downloading a program Adobe Flash or
Itunes ans installing it on your hard drive. Flashing is like going from Windows XP to Vista, you are replacing your operating system.
Generally , anything installed will get erased after a hard reset, anything flashed will survive a hard reset.
Generally the spl's are extracted from the roms already and are available in the forum to flash to your phone. Once your phone is flashed with Hardspl there is no need to flash a new spl for every rom.
Stock roms come with a new spl for every version, cooked roms do not contain an spl. There fore your phone must be flashed with a hard spl prior to flashing a custom rom.
Some say that when flashing a cooked rom that you should , for performance sake, flash the patched spl (hardspl ) that came with the rom that the cooked rom is based on ie: 3.56hard for roms that are based on AT$T 3.56.xxxx 6.1 roms or 3.34hard for 3.34.xxxxxx WWE based roms. I personally have seen no " hard " evidence of this. I have always used 3.29Hard whether I was flashing stock or cooked roms.
For more info, Dave has a nice thread on this
http://forum.xda-developers.com/showthread.php?t=498320
Further clarification about ROMs
Thanks for the reply, I think I'm understanding all these a bit more.
Another thing to clarify:
Basically, my phone comes with PAPAGO, a navigation software pre-installed. In other words, after a hard reset, it's automatically installed. So if I do a ROM upgrade, does that mean I won't have this software anymore?
Thanks!
ferns_mccanus said:
Thanks for the reply, I think I'm understanding all these a bit more.
Another thing to clarify:
Basically, my phone comes with PAPAGO, a navigation software pre-installed. In other words, after a hard reset, it's automatically installed. So if I do a ROM upgrade, does that mean I won't have this software anymore?
Thanks!
Click to expand...
Click to collapse
That is correct, you will not have it anymore, unless the new rom includes it.
but im pretty sure there is a program to install from a sd card to newly flashed rom. so if the navigator software is on card then you could do this
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.