Related
EDIT: The task 2a brick issue has been solved. This does not mean you can do anything via MTTY & be safe. There are still other ways to brick your device with MTTY, so still always be smart & be careful!
All you Noobies thata are stuck in bootloader or playing with MTTY or [email protected] commands PAY ATTENTION!!!!
This is not a big deal for me because I have a never ending supply of HTC Devices. However, for the noobie & the person that pays full retail for their device this is VERY IMPORTANT INFORMATION!
Understand that MTTY is not a toy & neither is your device. Some very low level flushing & programing can be done with MTTY. If you enter the incorrect information, you may very well end up with an $800.00 paper weight on your desk.
Many of you came from the Hermes Device. Many will remember that with the Hermes & MFG SPL if you had bad blocks of memory you could erase those bad blocks using the MTTY command cmd>task 2a.
However, with HardSPL (all versions including w/ [email protected] command) the command task 2a doesn't just erase the bad blocks, It will COMPLETELY reformat your device, the ROM, RAM & NAND storage, totally wiping out the Windows CE.
In other terms, if you play around with [email protected] commands or MTTY task commands, there is a very high risk of wiping your device completely & restoring CE without having an amazing amount of software & knowledge is next to immposible.
DO NOT PLAY AROUND WITH MTTY IF YOUR DEVICE IS STUCK IN BOOT LOADER! Also, know that every SPL version CAN have different commands. If you are stuck in BL, stick to the known instructions, or ask somebody for guidance.
MTTY is a very powerful & often misunderstood tool. Use it wisely.
I just want to confirm that as it's exactly how I bricked my kaiser.
what does mtty stands for?
Hey MODS????
Lets get this into a stickie or something. With all the stuck in boot loader issues, with all the noobies & with all of them asking for or downloading MTTY the board will be an explosion of my device is bricked comments.
Can someone cross post this to the wiki as well?
Thanx Bro for the info.
I've added it to the wiki under the MTTY thread by Laurentis with some strong verbiage...
Can't add it to the sticky because there are 10,000 characters in the first post already, plus, most folks don't even know what MTTY is (nor is Laurentis' thread stickied), so it shouldn't be too much of a issue...
Hope this helps!
Please explain
I 've got stucked in 3 color screen with any new FlashingROM in my Kaiser. Than i install HardSPL and the problem persists.
I'm in tri-color screen with SPL OliPof on the upper left corner.
KAIS130
SPL-1.0.OliPof
CPLD-8
I'm with the original factory ROM.
I can't sync my pda
If I use the MTTY i will brick my phone?
I should install another RadioROM and WM6.1 ROM?
How could I stablish comunication with PC?
Please help
Thanks
GSLEON3 said:
Lets get this into a stickie or something. With all the stuck in boot loader issues, with all the noobies & with all of them asking for or downloading MTTY the board will be an explosion of my device is bricked comments.
Can someone cross post this to the wiki as well?
Click to expand...
Click to collapse
What a great idea!!
I believe ALex already crossed this to the wiki.
I've made great progress understanding SPL & MTTY commands. The problem lies in doing things out of fear. Task 2a is not a command that should be generally used unless you have an unlocked device. Using it however, can be an important step in some cases, but you need to be precise in the execution of steps immediately after a task 2a command.
I am documenting all the current SPL versions & commands that are not only posisble, but also the ones that are helpful in recovery. I you do not know what you are doing, I suggest you contact me as I am documenting various issue, spl versions, & solutions for an upcomming post.
Thx!
Thanks
GSLEON3 said:
I believe ALex already crossed this to the wiki.
I've made great progress understanding SPL & MTTY commands. The problem lies in doing things out of fear. Task 2a is not a command that should be generally used unless you have an unlocked device. Using it however, can be an important step in some cases, but you need to be precise in the execution of steps immediately after a task 2a command.
I am documenting all the current SPL versions & commands that are not only posisble, but also the ones that are helpful in recovery. I you do not know what you are doing, I suggest you contact me as I am documenting various issue, spl versions, & solutions for an upcomming post.
Thx!
Click to expand...
Click to collapse
I'm sorry to be a nobie without practice. I've been searching wiki and xda about one week and no solution to my specific problem. I understand the procedure with MTTY but there is so many details and i don't want brick my phone.
I'm trying to contact you just like i'm going nuts with my pda.
I send you MSN contact and waiting your reply.
I have a kaiser bought in miami, factory unlocked, running windows mobile original ROM with HardSPL installed.
Stuck in bootloader tri-color screen as described above.No PC sync!
Solution=reward
I'm wondering, after erasing everything. isn't it possible to still flash ROM , etc.?
unless u're saying the command erase BL too.
GSLEON3 said:
I am documenting all the current SPL versions & commands that are not only posisble, but also the ones that are helpful in recovery. I you do not know what you are doing, I suggest you contact me as I am documenting various issue, spl versions, & solutions for an upcomming post.
Click to expand...
Click to collapse
Looking forward to that post, it should make for some interesting reading.
omega_ said:
I'm wondering, after erasing everything. isn't it possible to still flash ROM , etc.?
unless u're saying the command erase BL too.
Click to expand...
Click to collapse
YES & NOOOO!!! The task 2a completely formats NAND storage where SPL resides. So if you have an issues or reset BEFORE flashing a new SPL, you are done for (toast) unless your device is security unlocked.
GSLEON3 said:
YES & NOOOO!!! The task 2a completely formats NAND storage where SPL resides. So if you have an issues or reset BEFORE flashing a new SPL, you are done for (toast) unless your device is security unlocked.
Click to expand...
Click to collapse
Ok lets go with the fact that I bricked my device with the task 2a command (ok, I bought myself a new TyTN II the next day but still have the bricked one).
If HTC ever comes out with a ROM upgrade with the right CID, would it flash?
Tnx for the answer!
@ GSLEON3
I just wanted to say thank you for everything you do in recovering peoples bricks. Your worth is incalculable. Nice work. Nice work indeed.
yea, i think what you do is pretty amazing, the fact that you havent killed a newbie who bricked his phone is just unbelievable
and that's one badass tilt you have there.......a truly battle tested tilt
GSLEON3 said:
...I have a never ending supply of HTC Devices...
Click to expand...
Click to collapse
Care to share the wealth?
XtreMe_G said:
yea, i think what you do is pretty amazing, the fact that you havent killed a newbie who bricked his phone is just unbelievable
and that's one badass tilt you have there.......a truly battle tested tilt
Click to expand...
Click to collapse
Never killed one, but I've said "Go pound sand" to one once. He was a complete ARSE though & was annoying as hell.
Now if I was only smart enough to build a package around the way I've found to change the page pool I'd be good. So far you can only do it with Platform Builder though.
Lukstra said:
Ok lets go with the fact that I bricked my device with the task 2a command (ok, I bought myself a new TyTN II the next day but still have the bricked one).
If HTC ever comes out with a ROM upgrade with the right CID, would it flash?
Tnx for the answer!
Click to expand...
Click to collapse
did you get an answer on this?
YES!!!
Task 2a Bricks can now be fixed. However the CID has nothing to do with it. Task 2a completely formats everything except parts of the radio. This leave OEMSBL & depending on the radio you last had, it can now be fixed.
so, I had some people contact me about the above problem. apparently some kaisers have this for some reason: they for no reason enter bootloader screen and won't boot OS.
the usual mtty commands ("set 16 0", "set 14 0") do not seem to help, and the whole thing is intermittent, sometimes you can still get the OS to boot. (NickCollision mentioned shorting the battery terminals after removing the battery helps for a while)
I patched the 3.29.Hard HardSPL (and the 3.56 too) to remove all enterbootloader reasons other than the usual stuff, keyboard combination and ruunbh tag.
both 3.29 and 3.56 will now say .Hard2 where the 2 means it is patched version =) so it will be less confusing to users.
UPDATE: you can try using force-usb SPL versions now, see new attachments!
UPDATE2: you can try 1.0.olipof-nostuckinspl-force-usb version and 3.31 hardspl (new hardspl, asked for by some users, of course with all these features)
3.29 is still very strongly recommended over 3.56, unless you have OS freezing issues with 3.29.
download from attachment and flash with SSPL to fix problem if you can get the OS booting at least once. also strongly recommended to flash this for prevention even if you have no problems yet!
what to do if you are still stuck in SPL - in that case, the spl overwrite protection will not let you flash. you should try to get the OS booting at least once. try with USB in, or after battery removal-reinsertion, those help increase chances.
if that doesn't work out, then see below what to do in that case:
the kaisdiagtest1.zip or the kaisdiagSD.zip in attachments may help solving the problem of reflashing the SPL to the patched version, if you absolutely can't get the OS to boot at least once.
the one of these allows you to reflash SPL via USB connection, the other one allows you to reflash from microSD card. this SD one is strongly recommended especially if you have problems with USB connection in SPL. it is also much more automatic.
usage STEP BY STEP (only if you cannot get the OS to boot not even one time!).
for diag and flash via microSD:
1. format a microSD to fat32 (use a card reader on a PC), copy the image to it from the KAISDIAGSD.zip in attachment (extracted filename KAISDIAG.NBH). this is basically an SSPL patched to load from SD without booting OS and then it will autoflash my hardspl again from SD.
2. put one of my hardspl's on the card too (in attachment, 3.29.Hard2 or 3.56.Hard2, 3.29 recommended). name this file as KAISIMG.NBH!!!
3. insert the microSD in the kaiser, then reset kaiser.
4. it should say Loading / Update in progress then reboot to a screen saying SPL 1.00.OliNex.
5. it should now flash in the KAISIMG.NBH. and will reset.
6. at this point it should boot to the OS, if it doesn't, then flash an OS. (of course delete the previous KAISDIAG.NBH and KAISIMG.NBH from the sd card and remove sd unless you opt to flash the OS from sd too)
for diag and flash via USB:
1. format a microSD to fat32 (use a card reader on a PC), copy the image to it from the kaisdiagtest1.zip (extracted filename KAISDIAG.NBH). this is basically an SSPL patched to load from SD without booting OS.
2. insert the microSD in the kaiser, then reset kaiser.
3. it should say Loading / Update in progress then reboot to a screen saying SPL 1.00.OliNex.
4. it should then work with RUU over USB (has USB force patch). but test with mtty first, make sure to disable usb connection in Activesync/WMDC! if PC doesn't see the device, try a USB replug. also, the USB should be plugged in all the time (except for when you replug)!
5. if it seems to have a good connection, then please now flash one of the SPL's posted in this post. after that you will be able to boot OS (of course reflash OS if you need to but the *first* flash *must be* SPL).
6. if this doesn't work (i.e. USB connection won't go), then go and check the SD version of the diag image, if you haven't already.
Wow Great work.
Thank you very much for your hard work! Going to sticky this for the time being.
Damnn,m nice work.
Thanks for this.
I have added it to my Wiki page on what to do if you get stuck at the bootloader. (Kaiser_Stuck_at_bootloader).
Anything you spot wrong with it feel free to modify (I asked GSLEON to take a look, but I don't know if he's had time).
Thanks
Dave
I can tell you that it does work and it did fix my kaiser!
Great work!
Nice!
I don't use the SPL, other than the one that came with my phone.
(Warranty....don't want to take a chance). Come October, when the warranty expires, I'll probably start flashing some of the cooked ones, plus, the Raphael
will probably be around by then.
I love you cmonex, let me know if you broke up with olipro
whats your thoughts on using the different SPL's to fix the random freezing issues that seem to hit the kaiser? I know my phone seems to work best with the newest SPL thats out right now from Jocky but it all could be in my head!
----Thank you cmonex, once again you show that your one of the amazing forces behind Xda! I hope there are little girls out there that want to be just like you when they grow up! That would be so cool a bunch of mini cmonex's running around we would have no issues with are WM devices then!
sakajati said:
I love you cmonex, let me know if you broke up with olipro
Click to expand...
Click to collapse
lol, sorry, no chance
austinsnyc said:
whats your thoughts on using the different SPL's to fix the random freezing issues that seem to hit the kaiser? I know my phone seems to work best with the newest SPL thats out right now from Jocky but it all could be in my head!
Click to expand...
Click to collapse
most probably that was because the older SPL's formatted nand too aggressively, so the end of the OS might get erased, which is no good. wasn't a problem before but the new OS's are bigger, so it affects them more likely.
as for the SPL versions, I don't really recommend 3.56 SPL, 3.29 seems much better in terms of available commands (though neither has task 2a for frankenkaiser fun ). did someone have any good experience with the 3.56 over 3.29? - I wonder why it is an option.
cmonex can u post the patch for the 3.56 it would be greatly appreciated, thanx
Get a new battery. The reason for this problem is the power manager keeps reseting the watchdog timer. Depending on when that happens the unit will either constantly reboot or enter bootload.
For some reason the BatSense line goes high and stays high. I haven't dissected the battery yet, but replacing it solved the problem.
htcfan2008 said:
For some reason the BatSense line goes high and stays high. I haven't dissected the battery yet, but replacing it solved the problem.
Click to expand...
Click to collapse
Not discounting the theory, just wanted to say that I had swapped out battery's during my testing with cmonex. So two diff battery's, same problem? Unlikely. As cmonex indicated shorting the terminals did have a positive effect, so you may be on to somthing re: the batsense line. Just that swapping batteries had no effect in my experience.
oOoOo my batsense is tingling hehe
Where the two batteries...
Nick Collision said:
Not discounting the theory, just wanted to say that I had swapped out battery's during my testing with cmonex. So two diff battery's, same problem? Unlikely.
Click to expand...
Click to collapse
...Samsung brand made in China, and both more than six month old? Then quite possibly they're both bad. (I forgot to mention in my other post that I replaced the battery with a non-HTC brand.) One way to tell is look at the battery edge on: if it has a bulge in the middle or looks "swollen" all around then it surely is bad.
I have found that using a non-HTC car or wall charger almost always and rather quickly kills the battery. It's not the charger voltage but the charging current profile that's the problem.
Anyway, good luck.
the bootloader can enter tricolour screen for a couple reasons other than the usual key combination or nbhload / enterbootloader tags in flash:
- if CPLD function returns 0xF
- or if debugboard is detected for whatever reason
- other configdata in flash tells it to do so
the last one can be excluded, because the problem is intermittent, and flash contents should be permanent.
then, I had Nick Collision run info 7 (which calls the same function), and it doesn't return 0xF, so maybe the second one.
I don't know what would cause that though, this battsense line sounds interesting.
to ofcourseimnaked: OK, i will do that soon.
Don't have a Kaiser SPL handy, but it must be using the same boot tags as Trin/Herm.
ClrRUUTagGoToOS
ClearGotoULTag
DeviceWarmBoot
CELoadComplete
NbhLoadSuccess
EnterBootloader
GoUpdateLoader
DeviceColdBoot
SetRuuNbhUpdate
These tags are programmed into flash to force boot in required mode.
Is this the config data you are referring to?
One other thing...
SPL and OS kernel debug log is stored in flash too, the reason for soft reset may be found in the log? It should be possible to dump the log with procdump once device boots to OS.
Don't know the offset for Kaiser Should be in the next block after the block with CID and boot tags though.
stepw said:
Don't have a Kaiser SPL handy, but it must be using the same boot tags as Trin/Herm.
ClrRUUTagGoToOS
ClearGotoULTag
DeviceWarmBoot
CELoadComplete
NbhLoadSuccess
EnterBootloader
GoUpdateLoader
DeviceColdBoot
SetRuuNbhUpdate
These tags are programmed into flash to force boot in required mode.
Is this the config data you are referring to?
Click to expand...
Click to collapse
yes, those mainly, and some flags.
but the issue is not them.
stepw said:
One other thing...
SPL and OS kernel debug log is stored in flash too, the reason for soft reset may be found in the log? It should be possible to dump the log with procdump once device boots to OS.
Don't know the offset for Kaiser Should be in the next block after the block with CID and boot tags though.
Click to expand...
Click to collapse
you mean task 37? btw, reset wasn't an issue here, but if someone shows up with a device constantly rebooting, we can look into that too..
note, CID is not really accessible directly from SPL anymore, MSM7xxx. (though right now I'm having fun finally dumping the protected radio nand)
Please explain me what it exacly is.
Is it better, most recent and fixed for Bootloader mode stuck version of HardSPL 3.29 which we can found on 'jockyw2001' thread?
Is it still HardSPL which let me flash any ROM for HTC Kaiser?
Thanks for all explains. Best regards.
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
Hi All,
I have been searching and not able to find a solution that works with the problem i am having upgrading my rom.
I was trying to upgrade to either or L26_KaiserTouch_V1M2D.rar or L26KDV12_Full.rar
roms, and after unpacking, running the utilities i keep hitting the same wall.
I have two pcs i have tried on, a laptop and a desktop both running xp.
Uninstalled active sync reinstalled etc etc
even tried the hard spl after using MTTY to try and solve the problem.
I still get error 262, even with hard spl which runs a different rom update.
tried different usb ports, unplugged most devices to the basics, restarts etc make no change to it.
Then i tried a fat32 micro sd card with the rom named as KAISIMG.nbh
and after using MTTY as listed by Laurentius26, it will show loading but not just sits there for more than 10 mins!
Hopefully someone can come up with a solution or has had the same probs.
As you could probably imagine i have a moderate grasp of this kinda stuff but i think its now beggining to drive me crazy!
Cheers,
Nathan
Narf_911
narf said:
Hi All,
I have been searching and not able to find a solution that works with the problem i am having upgrading my rom.
I was trying to upgrade to either or L26_KaiserTouch_V1M2D.rar or L26KDV12_Full.rar
roms, and after unpacking, running the utilities i keep hitting the same wall.
I have two pcs i have tried on, a laptop and a desktop both running xp.
Uninstalled active sync reinstalled etc etc
even tried the hard spl after using MTTY to try and solve the problem.
I still get error 262, even with hard spl which runs a different rom update.
tried different usb ports, unplugged most devices to the basics, restarts etc make no change to it.
Then i tried a fat32 micro sd card with the rom named as KAISIMG.nbh
and after using MTTY as listed by Laurentius26, it will show loading but not just sits there for more than 10 mins!
Hopefully someone can come up with a solution or has had the same probs.
As you could probably imagine i have a moderate grasp of this kinda stuff but i think its now beggining to drive me crazy!
Cheers,
Nathan
Narf_911
Click to expand...
Click to collapse
you have already Hspl 3.29 from here:
http://forum.xda-developers.com/showthread.php?t=396922
also if you don't have WWE phone.. (English language)
you must unlock your phone with this steps:
http://forum.xda-developers.com/showthread.php?t=361236
and on activesync settings you must check usb connecting..
try the usb from your mouse to see if working...
good luck
also try AthineOS Manila Edition Rom hehehehe
http://forum.xda-developers.com/showthread.php?t=435345
Had a go at putting on Hardspl 3.56 also 3.29. even the forced Usb versions.
I can update to any standard Kaiser/Tytn2 Rom but any of these other cooked roms seem to give me grief.
I even thought perhaps i could run the other original rom update, so i did that and copied the different Nbh files in and renamed to what the original rom was but it still wouldn't allow me to get to where i wanted to get.
Is there any special way i can get Hardspl onto my device?
Can i copy it to the sd card and load it thru a bootloader?
This error 262 is driving me nuts!
I spent well over 4 hours of constant messing about and testing any possible solutions.
plus a further 2 today!
This is my last resort!
I'll be more than happy to donate to these rom developers once i get one working.
Even attempted the manilla AthineOS without luck.
I keep reading about the JumpSPL and SSPL, is anyone able to explain or link to where i can get it for the Kaiser ?
OR is it the same thru the whole series ?
Any assistance is greatly appreciated.
There is SOOO much to learn!
The more you know the more you realise you dont know!!
Use jump spl first, I reccomend 1.56, then install your spl of choice, I personally use 3.56
Place jump spl on your phone and run it from the phone, keeping your usb cord attached, you will get a tri colored screen. Now in active sync comm settings uncheck allow usb commections. unplug the usb cord wait 30 seconds and plug it back in. then from your pc open the folder hard spl and run kaiserRUU and after its done go back to active sync allow usb connections and flash your ass off.
Woo Hoo!!
Finally i got it working, I was beggining to think perhaps there was something stupidly wrong with my pc or the Tytn!
Thank you very much for your reply KD8DNS, Also thanks to b16b After so many hours of mucking round i've finally got it sorted!
Now running Kaiser Diamond V12, it works very well.
Will be looking to change to many other roms in the near future!
Cheers,
Nathan
"Narf!"
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.