Related
I have a Cingular 8125, I have flashed many ROMs and the last one is TNT 20273, IPL/SPL 3.08 and radio 2.19
Recently each time I have to soft reset it takes a very long time to reboot. It can be several hours.
I tried to downgrade to official Cingular rom but RUU doesn't work anymore, there is always a connection problem and it only makes a soft reset that takes hours to come back.
I tried also to force bootloader mode with camera button+reset, running enterbl.exe and disabling usb connection in Activesync but nothing worked.
Once it restarts it works fine until I have to reset but when it happens I have to wait hours to use it again.
I am desperate, I will appreciate any help or comment.
Thanks in advance
talvae
the bootloader couls be the problem. have you tried to downgrade to 225/226 what ever it is?
all you need to do is take the original rom and dump it using core kitchen or hypercore. you will see (should see several partitions once you break down the nbf back into it's parts (nb's)
using nb to nbf you can see which partitions are which and just recompile the new nbf with just the ipl/spl. then flash that new nbf using the upgrade utility.
one important question: G4 or G3?
do you have the Wizard Service tool made by mestrini?
you can figure out what type of device it is, as well as use it to flash nb's onto your phone perhaps... (dont quote me on that ask mestrini.
S.V.I said:
the bootloader couls be the problem. have you tried to downgrade to 225/226 what ever it is?
all you need to do is take the original rom and dump it using core kitchen or hypercore. you will see (should see several partitions once you break down the nbf back into it's parts (nb's)
using nb to nbf you can see which partitions are which and just recompile the new nbf with just the ipl/spl. then flash that new nbf using the upgrade utility.
one important question: G4 or G3?
do you have the Wizard Service tool made by mestrini?
you can figure out what type of device it is, as well as use it to flash nb's onto your phone perhaps... (dont quote me on that ask mestrini.
Click to expand...
Click to collapse
Thank you S.V.I., it s a G3.
Let me check if I understood, what you suggest is to use WST to flash a nb containing only ipl/spl 2.25?
If it is correct, do you think reflashing ipl/spl 3.08 could fix the problem?
I just reaaly dont understand why one would want to update the bootloader if it does not fix anything. if it isn't broken, why fix it? I can understand the radio might want to be changed, but why bootloder/bios? it does not change anything.
I recomend decompiling the original rom (the one that came from tmobile) and making a bootloader rom out of it. this means not using the cid block or the os block, just the ipl and spl blocks. flash that to your device, then you should not have any problems updating your roms using the manual bootloader mode.
also remember that if the update utility does not see your device when it is in bootloader, you need to exit the utility, and reset the phone back to bootloader, then plug in. wait for the computer to recognise the phone, then start the update utility. that should do the trick.
wst will only copy the blocks off of your phone. this means you need core, or hypercore to dump the factory rom to get the ipl spl blocks.
also, a good practice when flashing roms is to unplug it way after it starts up and you have gone through the setup welcome screens and already set up your activesync partnership.
when puting it into manual bootloader mode, you do not nessesarily need to deactivate activesync on the computer. I never have.
good luck.
Nicely thing
S.V.I said:
I just reaaly dont understand why one would want to update the bootloader if it does not fix anything. if it isn't broken, why fix it? I can understand the radio might want to be changed, but why bootloder/bios? it does not change anything.
I recomend decompiling the original rom (the one that came from tmobile) and making a bootloader rom out of it. this means not using the cid block or the os block, just the ipl and spl blocks. flash that to your device, then you should not have any problems updating your roms using the manual bootloader mode.
also remember that if the update utility does not see your device when it is in bootloader, you need to exit the utility, and reset the phone back to bootloader, then plug in. wait for the computer to recognise the phone, then start the update utility. that should do the trick.
wst will only copy the blocks off of your phone. this means you need core, or hypercore to dump the factory rom to get the ipl spl blocks.
also, a good practice when flashing roms is to unplug it way after it starts up and you have gone through the setup welcome screens and already set up your activesync partnership.
when puting it into manual bootloader mode, you do not nessesarily need to deactivate activesync on the computer. I never have.
good luck.
Click to expand...
Click to collapse
I think it is so much process to reflash but its interesant to try dump original roms... i never heard it... it sound very cool. just try to reflash from begining like it never was unlocked... wizard love etc etc etc.
S.V.I said:
I just reaaly dont understand why one would want to update the bootloader if it does not fix anything. if it isn't broken, why fix it? I can understand the radio might want to be changed, but why bootloder/bios? it does not change anything.
I recomend decompiling the original rom (the one that came from tmobile) and making a bootloader rom out of it. this means not using the cid block or the os block, just the ipl and spl blocks. flash that to your device, then you should not have any problems updating your roms using the manual bootloader mode.
also remember that if the update utility does not see your device when it is in bootloader, you need to exit the utility, and reset the phone back to bootloader, then plug in. wait for the computer to recognise the phone, then start the update utility. that should do the trick.
wst will only copy the blocks off of your phone. this means you need core, or hypercore to dump the factory rom to get the ipl spl blocks.
also, a good practice when flashing roms is to unplug it way after it starts up and you have gone through the setup welcome screens and already set up your activesync partnership.
when puting it into manual bootloader mode, you do not nessesarily need to deactivate activesync on the computer. I never have.
good luck.
Click to expand...
Click to collapse
Thank you S.V.I,
I have extracted the IPL and SPL from the original 2.26 cingular rom using the last version of WST, I have four .nb files.
Now I have to write them to my wizard but I would appreciate some advise.
Should I write each file using WST? or nessesarily I should make one rom with only this blocks and write that file?
talvae
I wanted to downgrade my ROM to 6.0 to SIM-unlock my phone as well as to try and troubleshoot some problems I am having. I searched the forum but I cannot find a clear answer. Apologies for duplicating a question if it exists someplace else.
Right now I am on HardSPL 3.29 on a Tilt with dutty's 6.1 and Radio 1.65.21.18. Once I find a ROM to downgrade to, is this the proper order:
1) Install HardSPL 1.x
2) Install 6.0 ROM
3) Install Radio for 6.0 (or specific radio for unlocking)
Thanks...
Kojak
Take a look at this. Makes it VERY easy to do a SIM-unlock.
http://forum.xda-developers.com/showthread.php?t=375583
I was looking at just the SIM-unlock as I do not need the CID change. I still thought that it was a requirement to downgrade to 6.0 first.
Still, even if Olipof's program doesn't require a downgrade, I still wanted to troubleshoot the issues I am having and wanted to run 6.0.
Kojak
The process you outline is fine. Just make sure to use JumpSPL to downgrade the SPL.
Good luck.
Just an update for those following the thread or who come upon it later...
I downgraded to SPL 1.x, then applied Dutty's TouchDual v4 ROM. The phone booted up, got to customization and ran through it successfully. However, after resetting, it hung on boot up. Even if I bypassed the customization the phone still hung. This prevents you from flashing the radio, which is the solution to this problem, since that ROM, and probably others, freeze when trying to access an incompatible radio.
The only way out of it was to flash the radio, but since the phone hangs on boot, you cannot do this via Activesync. The only way is with the MicroSD card. It's super easy - so long as you have a card reader and adapter.
So moral of the story - it pays to be prepared. If you are going to downgrade, make sure you have a card reader handy.
does anyone have the official TMo Dash 3g ROM upgrade (ver 1.17.531.6) that was on Tmo's site? It's been removed from their site, and I searched in the forums but can't seem to find it.
edit...never mind...found it.
It's still up on T-Mobile's site.
Try: www.t-mobileusa.com/wmupgrade
Was thee just now.....
Dash 3G Update
http://rapidshare.com/files/331920783/RUU_Captain_S_TMOUS_2.06.531.4_Radio_Signed_MAPLE_61.36t.25.29_3.47.25.48m_Ship.rar
brad1825 said:
http://rapidshare.com/files/331920783/RUU_Captain_S_TMOUS_2.06.531.4_Radio_Signed_MAPLE_61.36t.25.29_3.47.25.48m_Ship.rar
Click to expand...
Click to collapse
Any chance someone can mirror this on mediafire? DOWNLOAD SPEED ON RAPIDSHARE IS AT 38K RIGHT NOW!!!!
official tmo 6.5 locks up at 27%
anyone find a fix for this?
happens with hard spl 1.17 and 1.19
I would imagine if you "reset" the spl to 1.17 or 1.19 it will load.
I loaded it on a "virgin" Dash 3G new out of the box. During the upgrade process, it reset at 13%, and then paused for a FEW MINUTES at 27% (using XP).
Go back to this thread and reload the "Original SPL" on your Dash, and then try again. http://forum.xda-developers.com/showthread.php?t=550620
Works fine, EXCEPT for the notifications and reminders "VIB" functions as set up in my Profile settings. Looks like HTC is determined to "upgrade" the volume control at the expense of full profile functionality.........looks like the end of the road with WM (Sph) for me. I rely on the vibrate reminders in particular for meetings etc. Back to 6.1 for the moment.
Spl 1.26.0000
Good Day,
To load this without error...
First Download
Dash3G (Maple): SSPL, HardSPL and original SPL by Jock Dash3G then extract to a file and remove 1.19 hard spl.nbh and any other nbh files.
Then Extract the The new 3g rom to a file, copy the spl.nbh from there into the file you extracted Dash3G (Maple): SSPL, HardSPL and original SPL by JockyW
Run the auto exe and flash the new spl to your Maple.
after the phone is done customizing flash the new rom.
Work for me... Good luck
Spl 1.25.000
I folowed your instruction but I have an issue with with flashing the original SPL, it stop on 97%, after a while i gave up and after rebooting the phone the SPL reads 1.25.000 then flash the t-mobile 6.5ROM and it went through and my phone is happy. me too.
Still not able to flash the T-Mobile version
Tried the ideas on here but still cannot get this version flashed.
abofihmi said:
I folowed your instruction but I have an issue with with flashing the original SPL, it stop on 97%, after a while i gave up and after rebooting the phone the SPL reads 1.25.000 then flash the t-mobile 6.5ROM and it went through and my phone is happy. me too.
Click to expand...
Click to collapse
Upgrading to 6.5
Of course, T-Mobile tech support's solution is to send a new phone! I don't believe for an instant that this will have ANYTHING to do with solving the problem but, well, it is new and shiny!
When I downgraded to 6.1, that changed the spl to 1.17 from 1.19. Is
that what is being referred to? I tried the hard reset before as well.
Tried to upgrade from 6.1 to the t-mobile official version. I don't seem to have a problem going to the Windows Mobile 6.5 3VO version. I tried calling T-Mobile tech support but, surprise, their solution is to send me a new Dash! Okay, I don't mind the new phone but it really shouldn't be necessary. I guess having a new one will be easier to do the official upgrade.
Any instructions on what I should do to get the phone in a format so I
can do the upgrade would be appreciated. Is there a way to do the
upgrade from the memory stick?
abofihmi said:
I folowed your instruction but I have an issue with with flashing the original SPL, it stop on 97%, after a while i gave up and after rebooting the phone the SPL reads 1.25.000 then flash the t-mobile 6.5ROM and it went through and my phone is happy. me too.
Click to expand...
Click to collapse
I have confirmed this. You can not just run Jockys RomUpdateUtility.exe though, it will not work. You must run the auto.bat from within winmo. If you are stuck at the tri color then just reflash any spl (jocky) using the romupdateutility and it should boot. Then run the auto.bat. It will freeze at 97%, remove battery and USB, insert battery. You will see tri color with error code. Run T-mobile update and it should work.
EDIT:
Ok so to recap
1) Extract Jockeys HARD SPL and T-Mobile's 6.5 Rom into seperate folders.
2) Delete any .nbh files from Jockys directory
3) Copy the SPL.nbh from T-mobile directory into Jockeys
4) Run jockys auto.bat with your phone started up in windows mobile.
5) It will freeze at 97%, wait a minute and remove battery and usb.
6) Re-insert battery and power on. You will see tri color with error code.
7) Run the ROMUpdateUtility.exe from T-mobile 6.5 directory.
If you are stuck at tri color and cant boot into windows mobile to run auto.bat:
1) Follow steps 1 - 3 above.
2) run the ROMUpdateUtility.exe in Jockys directory. It will complete but will not change the SPL for some reason and boot into windows mobile.
3) Continue from step 4 above.
I downloaded the new ROM from t-mobile but it’s an executable. How do I extract the spl from this file?
Any help would be appreciated.
If you right click the ROM you can extract it. Just extract it to a folder. Then follow the instructions.
Finally got this to install!
I had to revert back to my original SPL by replacing the hard_SPL in the main folder and then running auto.bat (just running the RUU doesn't work).
The I ran the new T-Mobile ROM and it froze, but installed the new SPL.
Ran it again and it worked!
Hi aaronbaird1
Very thank you for the instructions to fix. 6.5 ROM update I was successful.
thanks a lot
NOTE: THIS MIGHT NOT WORK IF YOU INSTALLED THE HTC RUU USING A GOLD CARD IN THE FIRST PLACE... I'M LOOKING FOR TESTERS TO CONFIRM THIS.
I tried this when I first ended up with 1.76.0007, and it worked, but I didn't want to take a chance trying it again. I thought it was just a coincidence or my eyes were playing tricks on me. I was scared that I would brick my phone...
I finally got the guts to try it again and it worked!
Here's how...
You'll need:
- HTC 2.53.707.2 Test Build SAPPIMG.zip (Thanks Amon_RA!!)
http://rapidshare.com/files/267446145/2.53.707.2_-_sappimg.zip
- 1.76.2007 'Engineering' SPL
http://rapidshare.com/files/313034025/update-hboot-1.76.2007-signed.zip
- 6.35.07.29 32A Radio Image
http://rapidshare.com/files/313035429/radio-6.35.07.29-32A.zip
- Amon_RA Hero Recovery
http://forum.xda-developers.com/showthread.php?t=561124
- Gold Card
http://forum.xda-developers.com/showthread.php?t=572683
Caveats!!!
- Your splash screen will be changed to the HTC MAGIC screen and not your wireless provider's screen. I know of no way to change this.
- This might brick your phone... I was sweating bullets when I was running this on my phone because I wasn't sure it would work, and I'm still not 100% sure this will work for everyone. YMMV
Steps:
- Create your Gold Card! This is not just a suggestion. You need a proper gold card before starting. I used the card that came with my phone and it worked fine.
- Back up whatever you can from your existing setup. You can't go back and can't recovery anything here. Google sync should backup most of your stuff though.
- Shut off your phone and put the 2.53.707.2-sappimg.zip file on your gold card. Make sure it's named 'sappimg.zip'. Put the gold card in your phone.
- Turn on your phone using VolDown and Power. It will boot into HBOOT mode and within 10 seconds will scan your SD card. Do not press anything at this point! It will find SAPPIMG.zip only if it is named SAPPIMG.zip and not SAPPIMG.zip.zip... Get it? As it's loading SAPPIMG.zip it will show a blue progress bar on the right hand side of the screen.
- It will then check that SAPPIMG.zip is not corrupt.
- When prompted 'Do you want to start update?', press in on the trackwheel (Action key).
- The process will update the SYSTEM, USERDATA, BOOT, BOOTLOADER (SPL), RADIO_V2, RECOVERY and SPLASH.
At this point, you now have 3.22.20.17 32A Radio image and 1.33.2010 Engineering SPL. You can now flash any 32A Recovery and ROM and carry on like nothing happened and you didn't make a big mistake by flashing the HTC RUU. Next time don't be so impatient!
If you decide to stick with this Radio and SPL then I suggest flashing the Amon_RA 32A Recovery and picking a 32A ROM to run.
If you want to flash new HTC 3.03 ROMs using the 1.76.2007 Eng SPL and the new radio, then continue on. There are advantages to this, but at this point it's not for rookies.
Steps
- Download the recovery image, radio image and SPL (hboot) update into a folder of their own.
- Put the update-hboot-1.76.2007-signed.zip onto your SD card.
- Open a command prompt, navigate to the folder you saved all of the files in. This assumes that your Android SDK Tools folder is in your PATH environment variable)
- Boot your phone it fastboot by holding Back and Power.
- Once in FASTBOOT USB, type in these commands, hitting enter after each one.
Code:
fastboot flash radio radio.img
fastboot flash recovery recovery-RA-hero-v1.3.2.img
- Once it's finished, turn off your phone by pressing MENU.
- Start up your phone into recovery mode by holding Home and pressing Power.
- Apply the update-hboot-1.76.2007-signed.zip update.
- NOTE THAT THE RECOVERY REQUIRES YOU TO PRESS THE HOME KEY TO SELECT AN OPTION.
- Reboot your phone using the recovery option. Your phone will reboot back into recovery, and will format the CACHE. Don't worry about this, it's supposed to happen. If it doesn't boot back into recovery after a few minutes, pull the battery and power it on while holding the HOME key.
- Once it's booted into recovery mode, shut off your phone by pulling the battery.
- Start it back up into FASTBOOT mode by holding Back and pressing Power.
- You should now see the following on the screen:
Code:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.76.2007
CPLD-12
RADIO-6.35.07.29
Aug 21 2009,18:19:15
If your phone doesn't display exactly this information, then you might have made a mistake along the way and should consider yourself lucky that your phone boots at all. Try again from the beginning.
At this point, you can enter the recovery menu and run the CursorSense update.zip from:
http://forum.xda-developers.com/showthread.php?t=592856
This was probably the closest I came to bricking my phone, but I'm sure it works now.
Good luck and happy rooting!
That won't work because if you Flashed via RUU it'll say that your version is older.
If you only flashed SPL/radio and not rest of the ROM i guess it could work.
it can break the Perfected SPL?
When i was flashed the sense-ui by htc?
mkrle said:
That won't work because if you Flashed via RUU it'll say that your version is older.
If you only flashed SPL/radio and not rest of the ROM i guess it could work.
Click to expand...
Click to collapse
You might have a point here... I thinks that maybe I didn't think this through entirely...
Would anybody be willing to test? Just to see...
Thanks,
Quite tempting to try, as I did flash via the RUU. Will look into it.
cursordroid said:
You might have a point here... I thinks that maybe I didn't think this through entirely...
Would anybody be willing to test? Just to see...
Thanks,
Click to expand...
Click to collapse
Main Version is older....
I've tried it, didn't work, but again who knows it might work for someone. There was a guy who said he got s-off SPL from a regular RUU so you never know.
Main version is older...
Main Version is older
I tried it on HBOOT-1.76.0007 (SAPP10000)
Hong Kong Sense Update from 17/11/09
Same problem NOTHING NEW:
Main Version is older
main version is older, flashed with RUU
i know 2.53.707 sappimg.zip file saved a few people, they also flashed official ruu, but get spl info like this: 1.76.0007(SAPP*****), and s-off.
but for most of us, we get this: 1.76.0007(SAPP10000), and s-on. therefore, we trying to use 2.53.707 sappimg.zip file and get "main version is older, update failed". and, if we use fastboot, it says "remote: not allow".
the only difference is the SAPP model text following 1.76.0007. if it's *****(all "*" symbols, not means any key), security is off, no version check, and it work! if it's 10000(maybe 50000 is also the same but i'm not sure), we stucked at version check.
so, what can we do...
tigerdigi said:
i know 2.53.707 sappimg.zip file saved a few people, they also flashed official ruu, but get spl info like this: 1.76.0007(SAPP*****), and s-off.
but for most of us, we get this: 1.76.0007(SAPP10000), and s-on. therefore, we trying to use 2.53.707 sappimg.zip file and get "main version is older, update failed". and, if we use fastboot, it says "remote: not allow".
the only difference is the SAPP model text following 1.76.0007. if it's *****(all "*" symbols, not means any key), security is off, no version check, and it work! if it's 10000(maybe 50000 is also the same but i'm not sure), we stucked at version check.
so, what can we do...
Click to expand...
Click to collapse
yes, i also found some person get this: spl info like this: 1.76.0007(SAPP*****), and s-off, if in this state, they can flash any rom/spl/radio.
can anybody find how to go to this state? if we can, we can do anything.
I dont know any thing further other than I got 0007 and s-on
so, all I can do is bump...
I have SAP***** for some time, even before i flashed 1.76 SPL but it's s-on, so i think it's not directly related.
P.S. I think i got SAP**** by playing around with different radios and all i can say is *don't* change (especially downgrade) radio unless you're sure what you're doing and/or have a matching SPL.
still no luck searching for a root cure for 1.76.0007
I accidentaly posted this to another thread (http://forum.xda-developers.com/showpost.php?p=5196720&postcount=7) although it was meant to be posted here:
I was missing the Android Market wich didnt come with the Singapore RUU so just downloaded the the HK RUU, ran it with a gold card (dont know if thats really neccesary) and got Market.
The point being - if people are on the Singapore official update, would it be somehow possible to "patch" the HK RUU files from the temporary folders where it stores the files for the update? To say, replace the original HBOOT with an ENG HBOOT (possibly *.2007?)?
Since Singapore rom version is lower than the HK one..:
Singapore: ROM Version: 3.03.728.4(For Indonesia, Malaysia& Vietnam only)
HK-E: ROM Version: 3.03.990.6
..possibly it would skip the "wrong main version" or whatever it says during the update..?
Am I onto something here?
No because the (zip) files are signed and perfect SPL won't accept flashing them if they are modified.
so is there a newer spl yet?
jamesyb0i said:
so is there a newer spl yet?
Click to expand...
Click to collapse
nobody, help we. amon_ra, and all the developers.. because don't help us??? we need help!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
We need either kernel exploit to get root, or HTC signed RUU with 3.x ROM and s-off SPL. period.
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.