Hello everybody,
i guess i fryed the g-sensor of my raphael.
noticed it the first time when i instaled a 6.5 rom a few weeks ago and saw that the album app in this rom did not rotate my pictures.
was not to worried about it but recently i tryed a few other progs but non of them respond at all to the movement.
when i open the calibration prog the "bubbles" just stay in the middle, and when i try to calibrate it it does nothing beside telling me to hold the phone still and a after a while "calibration aborted".
i tryed a hard reset, flashing another 6.5 rom, a 6.1 rom, and now even the latest original htc rom, none of this did any help.
did someone had allready the same problem and even knows a fix for that?
or is the only possible fix to return it for repairs?
if i do that and just flashed the official htc rom will also be my slp and radio the correct one or do i need to take some action to get that to warranty compliance?
thanks allread in advance
that is really odd. did u hard reset after flashing the stock rom?
For warranty repairs it is suggested that you flash a stock rom and return the original SPL, not hardspl.
Now i've returned two devices with hardSPL, one the usb port was broken and couldn't flash it back, but i did revert it to the shipped rom. The other, the screen just went completely white on the device and couldn't see anything so just turned it in how it was and never had any issues with warranty attempting to charge me claiming that the cooked rom and hard spl have voided my warranty.
BUT better be safe then sorry and not take any chances right?
yes also think that is really odd, i suspect that the phone fell down one time too much and somehow that sensor is "stuck" or someting like that.
sorry for the stupid question but how can i actually see if i have a stock spl or hardspl? and what spl should be on an original german touch pro?
to check your spl go into bootloader. Do this by holding down the volume key and pressing the stylus in the reset hole. Hold both of them until you get a multicored screen (Red, green, blue, white).
Your spl will be the second line. "SPL-xxxxx" if its just numbers, pretty sure its not hard spl, if it is, you'll get something like "SPL-1.90.OliNex" which is OliNex's 1.90 hard spl.
refer to the wiki for more info, or the sticky threads under the Rom Development section.
when you go into the g-sensor calibration setting, what happens? does the spirit level graphic move??
patlabor said:
yes also think that is really odd, i suspect that the phone fell down one time too much and somehow that sensor is "stuck" or someting like that.
sorry for the stupid question but how can i actually see if i have a stock spl or hardspl? and what spl should be on an original german touch pro?
Click to expand...
Click to collapse
Wait.... if you don't know if you have stock spl or hard spl, does that mean you've never flashed hard spl? Because you need to flash hard spl in order to flash cooked roms
yes sure i have hardspl but the last rom i flashed is the original from htc. so now i dont know if i still have hardspl or if the original spl from htc came with the rom.
the tree color boot screen says SPL-1.90.OliNex.
i guess that is still the hardspl but i am not 100% sure.
so if its not original, where can i get the original one that came with the german touch pro?
The point of the hardSPL is that so it doesn't change when flashing between roms reducing the chance of bricking your device among other things.
go to this wiki page and it has instructions on how to return your device to stock spl. after you do that, flash a shipped rom for your device and you'll be grand
fone_fanatic said:
The point of the hardSPL is that so it doesn't change when flashing between roms reducing the chance of bricking your device among other things.
go to this wiki page and it has instructions on how to return your device to stock spl. after you do that, flash a shipped rom for your device and you'll be grand
Click to expand...
Click to collapse
flashed once my thrusty old prophed with an stock rom and afterwards the hardspl was gone and i could not flash any other roms before hardspl again.
was giving that wiki page a try but i cant follow it.
to where do i have to copy the original spl file?
dont know where the hardspl file extract the stuff before flashing.
any help`?
Related
Hi everyone,
I think I may have bricked my Kaiser. I've been following some similar threads but nothing seems to be working to fix the problem.
I was going through the process to flash a new Rom, starting with installing HardSPL following this thread I was. I was having problems, I think because I have the 1.82 ROM version.
Finally, I thought I had HardSPL installed, so I continued to run KaiserCustomRUU.exe. This completed (jumped from 0% to 100%) very quickly. However, I reset my phone and it is now stuck in the tri-color bootloader screen
The screen has the says:
KAIS130
SPL-1.82.0000
CPLD-8
and has the letters RUUNBH in the top right corner.
I've tried removing the battery and resetting, but the phone always goes back to this screen. I've also tried running mtty, but without success. The command 'readconfig' returned a result 'Command error !!!'.
does anyone know of anything else I can try?
Small bit of good news: if I issue the command 'boot' using mtty, my phone boots into my original ROM successfully, with the mtty output:
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
It takes a long time to boot (like a couple of minutes), but it does eventually boots up fine. When I reset, I'm back at the tri-color screen though
If your at the tri-color screen, just reflash a new rom
Im not an expert but when its at the tri colour screen, try to flash Hard SPL again, it should pick it up and flash i believe.
If that goes through ok, then do the same to flash another ROM.
Again no expert at unbricking but its definately worth a try
japher said:
Small bit of good news: if I issue the command 'boot' using mtty, my phone boots into my original ROM successfully, with the mtty output:
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
It takes a long time to boot (like a couple of minutes), but it does eventually boots up fine. When I reset, I'm back at the tri-color screen though
Click to expand...
Click to collapse
Try this.
1.) Open ActiveSync and navigate to File > Connection Settings - Uncheck Allow USB connections.
2.) Download this ROM http://rapidshare.com/files/5781641...dio_sign_22.45.88.07_1.27.12.11_Ship.rar.html and flash it to your device.
That should work for you.
hi alltheway. thanks for the advice!
I don't want to sound ungrateful, but are you sure the above is safe? I just don't want to make a wrong step now and totally screw up the device (now that I can successfully do a manual boot using mtty).
I know you can't guarantee it but is this what others who are stuck in the bootloader have done?
japher said:
hi alltheway. thanks for the advice!
I don't want to sound ungrateful, but are you sure the above is safe? I just don't want to make a wrong step now and totally screw up the device (now that I can successfully do a manual boot using mtty).
I know you can't guarantee it but is this what others who are stuck in the bootloader have done?
Click to expand...
Click to collapse
I had this problem about 2 weeks ago.
I was flashing one of Dutty's Great ROMs and I lost power at the house and shut down my computer when I was 46% done.
I had the same RUUNBH in the top right hand corner. All I did to fix this was flash a factory shipped ROM like the one I provided to you and it worked great. No issue thus far.
Honestly I can't gurantee 100% if this will totally fix your problem but I am 95% sure.
Unless some other users have an answer for you I think this will be your best solution. Regardless of what you do you will have to flash to a new ROM anyways.
Also, I'm a bit dubious on whether i will be able to flash to that ROM. I don't think I have the right HardSPL installed to flash roms (see what my boot-loader screen says in the first post).
I'm no expert though.... obviously
Thanks for all the info alltheway. I'm too tired now (will probably f*ck the thing up even further! ), so I'll try flashing this tomorrow.
Here's some more info I've collected using mtty (my phone is an O2 XDA Stellar):
Code:
Cmd>info 2
HTCSO2___001¯JG±HTCE
Cmd>getdevinfo
GetDevInfo: Get CID OK
HTCSKAIS1300O__0HTCE
New Thread
Read this:
http://forum.xda-developers.com/showthread.php?t=355910
Hi tqm. I've been following that post but as far as I can tell there is no solution there yet.
From what I can tell from that thread (and others), the only way stop the phone booting to the tri-color screen (in RUUNBH mode) is to flash with a ROM that matches the vendor. I think because I haven't been able to install HardSPL properly, my phone's version of SSPL will only load O2 ROMs (could be wrong here, but that's the picture I'm building ). Unfortunately no-one seems to have extracted the ROM from an XDA Stellar :\
I believe alltheway's solution above worked for him because he had HardSPL installed properly. He could load the stock ROM to fix the phone, because his SSPL version allowed different ROMs to be loaded. I'm not certain of this, and I'll probably try his suggested solution when I get home today... but I'm not too confident.
If only there was an mtty command to just get the phone out of 'RUUNBH' mode. I've seen the command 'task 8' mentioned on here, but it doesn't work when I try it. Does anyone know of a list of mtty commands for the Kaiser anywhere?
Definitely flash the original ROM, it will get your device to the default HTC shipped state.
Then sync phone with ActiveSync, install HardSPL again and then flash custom ROM.
I remember i had the same issue but the original rom is a lifesaver
You mean the original HTC ROM? or the original O2 ROM? (what my phone originally came with)
If I don't have one of the HardSPL versions posted on the forums (I believe they never installed properly, which is what caused all my problems I think), will I still be able to flash the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
Basically my questions is: is this stock HTC ROM flash-able to ALL kaisers? (even without downloading/installing HardSPL from the forums)
If not (i.e. I can't flash even the stock HTC ROM), is it expected that if I can't successfully install HardSPL, my Kaiser will only accept O2 ROMS?
japher said:
You mean the original HTC ROM? or the original O2 ROM? (what my phone originally came with)
If I don't have one of the HardSPL versions posted on the forums (I believe they never installed properly, which is what caused all my problems I think), will I still be able to flash the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
Basically my questions is: is this stock HTC ROM flash-able to ALL kaisers? (even without downloading/installing HardSPL from the forums)
If not (i.e. I can't flash even the stock HTC ROM), is it expected that if I can't successfully install HardSPL, my Kaiser will only accept O2 ROMS?
Click to expand...
Click to collapse
IMHO the HTC stock ROM should work even without HardSPL, at least for me it worked fine... but just for sure have your O2 stock ROM by hand.
jaso2005 said:
Im not an expert but when its at the tri colour screen, try to flash Hard SPL again, it should pick it up and flash i believe.
Click to expand...
Click to collapse
I don't thinks there's a way to flash HardSPL on tri-color scrren so far, coz activesync cannot connected to computer
the best way is trying to find the phone's offcial ship rom to flash
No luck trying to flash with the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
After getting to 1%, it reports an error:
Error [294] : Invalid Vender Id
As suspected, looks like this will only accept an O2 ROM Will have to wait until one is available.
Did you try installing HardSPL and then reflashing?
the stock HTC rom will not load onto your kaiser simply because it is still CID locked to O2's CID code. You HAVE to find the O2 rom that your device came with or any O2 ROM and reflash that and you will be good to go. You may also try and flash HardSPL but I dont think its going to work. But remember have a friend or someone on the forum dump and rebuild the O2 rom for you and just reflash the OS.nb or ROM only no radio!
It is very simple to dump and rebuild a rom so if you have a friend that has a kaiser have him over for an hour and dump his
thats your only shot at this point.
URPREY said:
Did you try installing HardSPL and then reflashing?
Click to expand...
Click to collapse
My current ROM version is 1.82. I don't think installing HardSPL has been solved for this ROM version, which I think is where all my problems started. I have tried, but no version of HardSPL (that I've found) will install correctly.
austinsnyc said:
You HAVE to find the O2 rom that your device came with or any O2 ROM... just reflash the OS.nb or ROM only no radio!
Click to expand...
Click to collapse
Thanks for the reply austinsnyc, this is what I'm hoping to do now, I'm watching this thread 'Has anyone dumped the o2 Stellar rom yet ?' closely Maybe I should reconstruct the ROM myself, I'm just a bit worried about arsing that up as well I'd rather someone experienced reconstructed and verified the ROM (on a phone that isn't already messed up).
Out of interest, would you be able to give me a succinct explanation of what is actually wrong with my phone at present? As far as I can tell, the only problem is that the boot-loader is stuck in RUUNBH mode. Has part of the ROM on the phone actually been destroyed?
I'm assuming right now that the point of flashing the O2 ROM is just to make the phone 'finish' a flash and get out of RUUNBH mode. Or is it actually to re-instate something that has been lost?
If it is to reinstate something that's at present lost, is this data definitely part of the os.nb?
If it's just to get the boot-loader out of RUUNBH mode, I'm REALLY gutted that there isn't just a mtty command to do this
Oh yeah, and perceptivepixel.com Ace!
i was thinking the other day and came to wonder about hard SPL. we always stress to the n00bs that it is very VERY VERY important, but then i noticed that the htc rom tool in the kaiser kitchen has a place to build an spl into the rom. can't we just put the spl from hard spl into the rom tool on all of our cooked roms and save everyone a step later? i wasn't sure who to ask and i don't have a kaiser without hard spl with which to test this so i am asking anyone who can answer sorry if i'm not seeing why this can't be done
I think you've forgotten something.
HardSPL is needed to be able to flash your device. So even if HardSPL is baked into a custom ROM, it wouldn't matter. HardSPL has to be installed first, no matter what. Not having HardSPL installed would prevent you from flashing a ROM.
Luckily installing HardSPL ins't really that hard.
meschle's Artemis ROM's have two batch files.
#1 for HardSPL
And
#2 for the CustomRRU.
So First time flashers can't really go wrong.
Ta
Dave
Yeah but hard SPL does not always work the same way. Some get white screen. I got 3 devieces. All 3 original TyTN II's. First one (my first deviece) flashed spl easly. But the other 2 deviece were getting white screen. Finaly I managed to Hard SPl it but in a other way.
xmoo said:
Yeah but hard SPL does not always work the same way. Some get white screen. I got 3 devieces. All 3 original TyTN II's. First one (my first deviece) flashed spl easly. But the other 2 deviece were getting white screen. Finaly I managed to Hard SPl it but in a other way.
Click to expand...
Click to collapse
Good point, I forgot that.
Dave
Hi, I use to flash cooked roms and go back and forth with official ones together with my spl. Now that i wanted to flash hard spl again so i can use newly cooked roms i cant flash hard spl using sspl or jump spl. it doesnt show usb anymore as how it use to be..anybody pls help? is there a way to flash hard spl without the sspl or jump spl?
thanks guys.
skipperbien said:
is there a way to flash hard spl without the sspl or jump spl?
thanks guys.
Click to expand...
Click to collapse
no .. atleast not that i know of. Secondly do you currently have hardspl?? also did you try this
http://forum.xda-developers.com/showthread.php?t=396922
it has options if you don't see usb on bottom.
thesire said:
no .. atleast not that i know of. Secondly do you currently have hardspl?? also did you try this
http://forum.xda-developers.com/showthread.php?t=396922
it has options if you don't see usb on bottom.
Click to expand...
Click to collapse
i use to have hard spl sir,and went back to normal official spl,just like going back to official roms.never had a problem..all went smoothly. been running official wm6.1 htc wwe for 2 weeks now with the original spl (not hard spl). Now that i wanted to try again to hard spl and flash cooked roms safely i cant see the usb on the bottom when i do sspl or jump uspl. am i missing something sir??
check for my reply under the sticky at the top of the forum
hard spl flashing...
hello skipper, thesire, and all others,
i wanted to reiterate that you should really read the forum linked above because it has a special "force usb" version of the hard spl installation that mau very well help you.
also, we could all maybe help you a bit more if you could post your firmware/spl versions (the numbers listed at top left on bootloader, but you probably knew that already, lol) Just so we can get a better idea of your situation- the more info the better!
i do a lot of kaiser and athena rom building, I posted a few decent roms at the beginning of the year but i havent released one since... (workin on one now though) but i am not exactly the caliber of rom builder that some of these guys are ... anyways, my point is that i have been in A LOT of hairy situations like this, but persistance is the key, so if i can help in any way i will....
THEQUARTZGUY said:
hello thesire, and all others,
i wanted to reiterate that you should really read the forum linked above because it has a special "force usb" version of the hard spl installation that mau very well help you.
also, we could all maybe help you a bit more if you could post your firmware/spl versions (the numbers listed at top left on bootloader, but you probably knew that already, lol) Just so we can get a better idea of your situation- the more info the better!
i do a lot of kaiser and athena rom building, I posted a few decent roms at the beginning of the year but i havent released one since... (workin on one now though) but i am not exactly the caliber of rom builder that some of these guys are ... anyways, my point is that i have been in A LOT of hairy situations like this, but persistance is the key, so if i can help in any way i will....
Click to expand...
Click to collapse
hey genius you are replying to the wrong guy. I DID NOT make the post. The guy who did i already suggested the solution you provided (even before you did) under jockyw's hardspl thread where he posted the same exact problem ....
i have managed to get in to the bootloader to flash the hard spl,using the 1.56 ver of sspl..however,neither of all the hard spl works after that.i cant flash any of the hard spl packages. im really suprise this is happening as i have done a lot of flashing back and forth for my tytnII. oh yah,my spl is 3.29 from the official HTC WWE wm6.1
thanks for all the help..
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
Heya,
I have an ATT Tilt (8925), and was using one of Dutty's custom roms. The phone was working great for quite a while, until yesterday. Now it just boots and goes to the ATT splash screen (or HTC splash screen if I flash an HTC rom).
I have tried flashing the original ATT shipped rom, HTC shipped rom, and Dutty's again to no avail. When it looked lost, I called ATT and they offered to exchange it under warranty.
The kicker is, I don't know if they will accept it with Hard SPL 3.56 still on it. I have reloaded the original shipped ROM, but have no way to restore the SPL from what I've read, because I cannot get fully booted. Is there a way to restore the shipped SPL without having to copy the SPL to the phone? (maybe through MTTY or frankenkaiser?)
Any help is greatly appreciated.
Thanks!
I don't think they care what spl is on the phone. I have returned a few of them...just make sure the stock rom is on it.
i did just see something about spl being on the phone when trying to use warinty... its on the wiki.... saw it like 2 min ago... can u run any rom on the phone? origional or home brew?
I hope they don't care
Yeah, I'm really hoping that they don't mind it. I was able to flash the shipped rom, but I still can't seem to find anything saying how to restore the SPL without being able to transfer files to the phone.
Thx Cmonex
I did a lot of searching, but not enough I guess.
Thx Cmonex for your post and utilites "in Kaiser intermittently stuck in SPL? - Possible solution and prevention!"
Using this, I was able to flash SPL to 1.93.0000, which I assume came with the phone as I bought it only a few months ago. If anyone thinks I should go back to 1.56.0000, please let me know, as I now know how.
Thanks again for your help.