Recently, during testing TCP experience a symptom that also confirms my past experience. The most recent one I had was one of the network I connect to (I have 3 SIMs) having issue. This issue is gone after I did an OEM flash & hard reset before flashing again custom ROM.
I'm trying to understand better, thus starting this thread for all seniors and chef to educate us 'flashers' and 'noobs'
Firstly, it was said that Kaiser has different structure that actually flashing OEM before custom ROM is not needed. On Hermes, it's needed.
Question What is the primary differences that requires this?
Secondly, based on TCP's post, it seems that there're some leftover behaviour from previous ROM and hard reset does not take it 100% away. From forensic computing, we know that some data is not totally overwritten and can be recovered using special tool.
Question
Our phone does not use the special data recover tool for sure, but why that behaviour occurs?
When it occurred (in TCP's case), was the setting correct but the behaviour went against the setting, or the setting was incorrect due to the leftover and the behaviour conforming the incorrect setting. Which one?
Flashing OEM: there're so many version of OEM, each has it's own 'flavor'.
Question
What is so different from going direct from custom ROM (which is not bloated, and should perform better) to another custom than going OEM first. And if OEM is flashed, how many times it actually being needed (flashes, hard reset) to ensure its 'clean'?
What is the criteria of 'clean'?
If I bought my Kaiser in Asia, should I go with AT&T stock OEM or it's better to use HK WWE?
Should we go through whole route (SPL, Radio, OS) or just the OS?
I hope by raising this, we can understand our phone better and have a safer flashing experience
anagarika said:
Recently, during testing TCP experience a symptom that also confirms my past experience. The most recent one I had was one of the network I connect to (I have 3 SIMs) having issue. This issue is gone after I did an OEM flash & hard reset before flashing again custom ROM.
I'm trying to understand better, thus starting this thread for all seniors and chef to educate us 'flashers' and 'noobs'
Firstly, it was said that Kaiser has different structure that actually flashing OEM before custom ROM is not needed. On Hermes, it's needed.
Question What is the primary differences that requires this?
Secondly, based on TCP's post, it seems that there're some leftover behaviour from previous ROM and hard reset does not take it 100% away. From forensic computing, we know that some data is not totally overwritten and can be recovered using special tool.
Question
Our phone does not use the special data recover tool for sure, but why that behaviour occurs?
When it occurred (in TCP's case), was the setting correct but the behaviour went against the setting, or the setting was incorrect due to the leftover and the behaviour conforming the incorrect setting. Which one?
Flashing OEM: there're so many version of OEM, each has it's own 'flavor'.
Question
What is so different from going direct from custom ROM (which is not bloated, and should perform better) to another custom than going OEM first. And if OEM is flashed, how many times it actually being needed (flashes, hard reset) to ensure its 'clean'?
What is the criteria of 'clean'?
If I bought my Kaiser in Asia, should I go with AT&T stock OEM or it's better to use HK WWE?
Should we go through whole route (SPL, Radio, OS) or just the OS?
I hope by raising this, we can understand our phone better and have a safer flashing experience
Click to expand...
Click to collapse
i don't have answers for all your questions, but i know for myself since i have a tilt, i flash the stock att rom before i flash a cooked rom, and the stock rom i've been flashing is the full .exe that has spl and radio with it. i feel that the rom your phone comes with should be your rom to flash before flashing a cooked rom and thats why i flash the att rom and not the htc rom on my tilt. Seems like i have alot less troubles when doing this. heres what i do with my tilt:
1.)flash stock att 6.1 rom
2.)tap screen when prompted
3.)hard reset
4.)tap screen/then do the screen alignment
5.)let the customization process do its thing
6.)after it's done and reboots i do another hard reset
7.)flash custom(cooked) rom
8.)tap screen when prompted
9.)do hard reset
10.)tap screen/then do the screen alignment, and i proceed from there with installing my aps and all.
this has always seemed to yield great results for me
msd24200,
That's what I do nowadays, after several times having issue and more convinced after reading TPC's experience.
However, the technicality (how the chipset is being written, what's the 'ghost effect' is being handled by hard reset) etc. intrigues me and perhaps by understanding this, a lot of newbies will 'listen' (as I didn't ) until more flashing started showing funny symptoms
Flashing the stock ROM using the Ship.exe will use the Stock RUU instead of the custom one, so this will also Hard Reset your phone as part of the Flash.
I can't see any reason why a stock ROM would help, where a Hard Reset would not.
Ta
Dave
DaveShaw said:
Flashing the stock ROM using the Ship.exe will use the Stock RUU instead of the custom one, so this will also Hard Reset your phone as part of the Flash.
I can't see any reason why a stock ROM would help, where a Hard Reset would not.
Ta
Dave
Click to expand...
Click to collapse
Dave,
Your response basically answers my last question in another way. To 'stretch' the argument further, how many cycle of hard reset it's required to make the phone 'clean' and load the latest ROM properly?
(Actually, what happen to the phone, the internal drive and the XIP chip by doing hard reset .. ?)
anagarika said:
Dave,
Your response basically answers my last question in another way. To 'stretch' the argument further, how many cycle of hard reset it's required to make the phone 'clean' and load the latest ROM properly?
(Actually, what happen to the phone, the internal drive and the XIP chip by doing hard reset .. ?)
Click to expand...
Click to collapse
Just one AFAIK. As I said, the CustomRUU's we use, don't do a Hard Reset (so your phone isn't wiped when flashing Radio's / SPL's / Splashes). So you have to perform one manually, this should clear any remaining data?
Did I post this link for you to look at before? There's a bit of discussion with stepw on this.
Dave
This is what I learned/understand, the Hermes has an extended rom. This ex. rom gets written to as you use your phone. Flashing a new rom does not over write this ex. rom because not all custom roms come with a written extended rom. So information from the previous rom is left on this extended rom. The only way to clean the extended rom is to flash the OEM rom first, and then the custom rom. Thereby cleaning the extended rom and allowing phone to write new info to the extended rom.
So on the Hermes, if the custom rom comes with an extended rom, there is no need to flash OEM first. If it doesn't, then you need to flash OEM first to avoid freezes and Spontaneous HR's.
The Kaiser does not have an extended rom so there is no discernible reason to flash OEM first. I never do (except on that rare occasion where I am flashing from a new chef and he insists, in his instructions. ) I have flashed over a hundred times, and can count on one hand how many times I have flashed OEM first.
Interesting. I have the HTC RUU, I think I'll start using that to flash ROMs, and use the Custom for radios and SPLs. I'm curious if that will make a difference in needing to flash a stock ROM...
personally, I've never had an issue with just flashing a ROM (no hard resets or stock rom or anything). If I find a ROM I like, I just download it and flash, that's it.
mbarvian said:
personally, I've never had an issue with just flashing a ROM (no hard resets or stock rom or anything). If I find a ROM I like, I just download it and flash, that's it.
Click to expand...
Click to collapse
I have had to do hard resets for other various problems but none were due to a "bad" flash. I find a rom i want to play with and flash it
Flashing stock before TPC's Elite helps me out a lot. Prior to that, I never bothered with hard resets, and never really had an issue.
DaveShaw said:
Did I post this link for you to look at before? There's a bit of discussion with stepw on this.
Dave
Click to expand...
Click to collapse
Dave, no, you didn't .. but thanks that you do .. especially this post is very enlightening. That's exactly what I'm looking for, the understanding of how the hardware being written/overwritten, that should answer the need of flashing OEM or not before custom and if hard reset is required.
Thanks for all that has responded ..
I flash at least 10 times a day, and have never flashed OEM ROM or did a HR after flash!
I never did the OEM thing before either, until I flashed TPCs ROM and had very strange issues. Hard reset (few times!) didn't clear it up either, only after I went back to OEM ROM (ATT for me) and then flashed TPC did all my weirdness clear up.
Perhaps it hasn't been needed before, but maybe going to 6.5 has some special conditions? Or something about the way TPC built his ROM?
Or maybe it's the fact that flashing the OEM includes the Radio so there's some extra stuff being overwritten that doesn't with a custom ROM.
Or perhaps it was just the phase of the moon combined with the low sunspot activity.
curwiler said:
I never did the OEM thing before either, until I flashed TPCs ROM and had very strange issues. Hard reset (few times!) didn't clear it up either, only after I went back to OEM ROM (ATT for me) and then flashed TPC did all my weirdness clear up.
Perhaps it hasn't been needed before, but maybe going to 6.5 has some special conditions? Or something about the way TPC built his ROM?
Or maybe it's the fact that flashing the OEM includes the Radio so there's some extra stuff being overwritten that doesn't with a custom ROM.
Or perhaps it was just the phase of the moon combined with the low sunspot activity.
Click to expand...
Click to collapse
I'm going to try his next ROM with the HTC RUU, to see if that makes a difference at all. I think that this will all get worked out in time. I don't really want to flash stock first, mainly because I'm too impatient to start playing with a new ROM lol. I will if necessary though, only takes a few extra minutes.
anagarika said:
Dave, no, you didn't .. but thanks that you do .. especially this post is very enlightening. That's exactly what I'm looking for, the understanding of how the hardware being written/overwritten, that should answer the need of flashing OEM or not before custom and if hard reset is required.
Thanks for all that has responded ..
Click to expand...
Click to collapse
Anagarika, you started one of the best threads I've seen since being a member. You started with very logical and good questions which are worthwhile to pursue. Your timing is perfect for me as I was trying to think of an approach that would be fruitful. I would encourage you continue to be logical and methodical to get to the answers. Real answers!
If you haven't already considered it, let me mention that it was implied that the flashing tools have limitations... no disrespect to the author is intended in my comment, but while everything he says may be true, the fact is the same tool is used to flash OEM and stock ROMs. So perhaps it was just an FYI for us all or I just didn't get the point.
This is a REAL issue. Before starting up on this board again, I used the previous kit and did my own ROMs and used other ROMs, with my tilt and blah blah. Sorry, not 10 times a day though... yikes dude! This week, when I started up again trying to revive my tilt, it hit me right away with OEM ROMs. So, I downloaded 6 OEM ROMs and the stock ROM. Because of the mood and the mode I was in, I was only looking for success and not experimentation and thus I don't have exact data. But, I can tell you that once I used the stock ROM a couple of previously "problem OEM ROMs" are working.
For me this important information should be used to find out why and how it can be improved..... That is of course if the developers want to continue to develop.
gadgetologist said:
...the fact is the same tool is used to flash OEM and stock ROMs. So perhaps it was just an FYI for us all or I just didn't get the point...
Click to expand...
Click to collapse
Yet Dave said:
Dave said:
Just one AFAIK. As I said, the CustomRUU's we use, don't do a Hard Reset (so your phone isn't wiped when flashing Radio's / SPL's / Splashes).
Click to expand...
Click to collapse
I take that to mean that the tool isn't exactly the same. There is a difference.
Now, the real question, for me (since I don't understand these things) is this:
Is there any difference, large or small, in a hard reset on the phone and the (I think) task 28 command issued by the OEM RUU? Dave? Anyone?
SoberGuy said:
Yet Dave said:
I take that to mean that the tool isn't exactly the same. There is a difference.
Now, the real question, for me (since I don't understand these things) is this:
Is there any difference, large or small, in a hard reset on the phone and the (I think) task 28 command issued by the OEM RUU? Dave? Anyone?
Click to expand...
Click to collapse
No.
Ta
Dave
SoberGuy said:
I'm going to try his next ROM with the HTC RUU, to see if that makes a difference at all. I think that this will all get worked out in time. I don't really want to flash stock first, mainly because I'm too impatient to start playing with a new ROM lol. I will if necessary though, only takes a few extra minutes.
Click to expand...
Click to collapse
I theory it shouldnt make a difference. I rarely use RUU as I know I have fried a MB cuz of that (I am sure I had something to do with it as well)! And had an expensive brick!
gadgetologist said:
For me this important information should be used to find out why and how it can be improved..... That is of course if the developers want to continue to develop.
Click to expand...
Click to collapse
Exactly my point. I didn't want to dilute TPC's thread as he's doing a wonderful job and his thread should be about his ROM
To put it another way is that:
Do we know what exactly being done on our device memory (XIP, NAND, etc.) during a ROM flash, during a Radio flash, during a HR, etc.
By knowing what's happening, we know better what approach to take. For example, most cooked ROM is sized 50-80 Mb (newer ones). Those OEM's are usually about 100Mb. I guess by flashing OEM, it overwrites a lot of the space left behind by previous ROM. However, in my view, flashing custom that has smaller size will have some parts of OEM left over (using space only as comparison). This might be useful if all chef's do the cooking based on OEM and bugs hunting also based on OEM first. This will give almost a 'standard' benchmark against which all other bugs are troubleshot.
I suggest (to myself too) to re-read the thread Dave pointed, especially the post I remarked. I've not yet understood fully what it really means, so I'll do a re-read.
As a side note, I came from UIQ/Symbian before .. and it was discussed they used NAND while WM uses XIP .. (which I don't quite fully grasp also) .. and there's such thing as format internal drive and flashing OS too.
Related
I am in dire need of some help when it comes to flashing custom ROMs. It appears that I can no longer flash custom ROMs. I can successfully flash the official 1.62 ROM from HTC website, the dumped TILT ROM, the Kaiser dumped ROM, and the WM6.1 WWE 3.03.405.0_radio_sign_25.70.40.02_1.64.06.04, but any other ROM I can’t. Let me explain my meaning of not being able to flash a ROM. Once it flashes 100% and reboots, when the “Tap the screen to begin to set up your windows-mobile device” is supposed to be displayed, all I get is a blank white screen. If I touch my stylus to the screen the text shows up, but none of the colored pictures that suppose to be in the back ground. Every section of the setup just displays the text no background images. Even my today screen won’t display any background images.
Does anyone have any information on this? I’ve abused this thread http://forum.xda-developers.com/showthread.php?t=314615 like a cheap dirty whore trying to find a solution, but no avail. Any help will be GREATLY appreciated.
kjones2k1 said:
I am in dire need of some help when it comes to flashing custom ROMs. It appears that I can no longer flash custom ROMs. I can successfully flash the official 1.62 ROM from HTC website, the dumped TILT ROM, the Kaiser dumped ROM, and the WM6.1 WWE 3.03.405.0_radio_sign_25.70.40.02_1.64.06.04, but any other ROM I can’t. Let me explain my meaning of not being able to flash a ROM. Once it flashes 100% and reboots, when the “Tap the screen to begin to set up your windows-mobile device” is supposed to be displayed, all I get is a blank white screen. If I touch my stylus to the screen the text shows up, but none of the colored pictures that suppose to be in the back ground. Every section of the setup just displays the text no background images. Even my today screen won’t display any background images.
Does anyone have any information on this? I’ve abused this thread http://forum.xda-developers.com/showthread.php?t=314615 like a cheap dirty whore trying to find a solution, but no avail. Any help will be GREATLY appreciated.
Click to expand...
Click to collapse
are you using 6.1 radios or the 6.0 radios?
P1Tater said:
are you using 6.1 radios or the 6.0 radios?
Click to expand...
Click to collapse
For each ROM, when ever I flashed, it changed my radio. For instance Alex's 1.62 rom, when I flashed his ROM, it already to changed my radio to the need radio to 1.27.14.09
kjones2k1 said:
For each ROM, when ever I flashed, it changed my radio. For instance Alex's 1.62 rom, when I flashed his ROM, it already to changed my radio to the need radio to 1.27.14.09
Click to expand...
Click to collapse
some come with radios, but most dont. You have to be sure if you need an AT$T specific radio or not.
P1Tater said:
some come with radios, but most dont. You have to be sure if you need an AT$T specific radio or not.
Click to expand...
Click to collapse
When I was running the WM6.1 3.03 ROM with radio 1.64.X.X, I flashed to Alex 1.62 ROM and my radio changed to 1.27.X.X. Didn't this flash change my radio?
kjones2k1 said:
When I was running the WM6.1 3.03 ROM with radio 1.64.X.X, I flashed to Alex 1.62 ROM and my radio changed to 1.27.X.X. Didn't this flash change my radio?
Click to expand...
Click to collapse
yes, if those are the only two flashes you have done, then it sounds like you might have had the unfortunate luck of having a bad flash. Reflash again and see what happens.
Edit:
Did you also do a hard reset at the "tap here to begin screen alingment" screen? If not, always do so.
P1Tater said:
yes, if those are the only two flashes you have done, then it sounds like you might have had the unfortunate luck of having a bad flash. Reflash again and see what happens.
Edit:
Did you also do a hard reset at the "tap here to begin screen alingment" screen? If not, always do so.
Click to expand...
Click to collapse
I always hard reset when flashing new roms (learned alot in the kasier wiki). This is what I'm trying. Flashing to ATT 1.62 (Offical from HTC website) > manually flashing to 1.27.04.09 radio > Flashing to Alex's 1.62 ROM
Anyone else have any suggestions?
I have a few ideas that I think may help. PM me when you get a moment. It may Late saturday or sunday till I can get back to you, but I need to know a coupl of things. So, if you're still stuck, let me know.
GSLEON3 said:
I have a few ideas that I think may help. PM me when you get a moment. It may Late saturday or sunday till I can get back to you, but I need to know a coupl of things. So, if you're still stuck, let me know.
Click to expand...
Click to collapse
PM sent
Check out the ROM Upgrading section of the Kaiser wiki under 'Troubleshooting' to learn how to enter bootloader mode.
Assuming that you installed HardSPL the first time you flashed, once you've booted into this mode, reconnect your device to your USB cable and flash another ROM.
For those who haven't looked at the Kaiser wiki in a while, I've completely revamped it w/TOC pages to make it alot easier to use (shameless plug)
_Alex_ said:
Check out the ROM Upgrading section of the Kaiser wiki under 'Troubleshooting' to learn how to enter bootloader mode.
Assuming that you installed HardSPL the first time you flashed, once you've booted into this mode, reconnect your device to your USB cable and flash another ROM.
For those who haven't looked at the Kaiser wiki in a while, I've completely revamped it w/TOC pages to make it alot easier to use (shameless plug)
Click to expand...
Click to collapse
?? This is not my issue. I'm not a complete beginner when it comes to flashing. Ever since I flashed the WM6.1 3.03 ROM I haven't been able to flash a custom ROM without having an image problem. I can still flash OEM type ROMS without the image issue, but not custom ROMS. I have the problem with images once a custom ROM has been flashed. If more clarification of problem is needed, I am will to give it.
This may be extreme and largely untested, but have you tried 'clear storage' on the WM6.1 ROMs and chosen 'delete NAND' (or something to that effect)?
That should wipe your ROM memory clean, although I'm not sure if that would help or hinder your cause, as I haven't heard anyone try it yet...
Hope this helps!
_Alex_ said:
This may be extreme and largely untested, but have you tried 'clear storage' on the WM6.1 ROMs and chosen 'delete NAND' (or something to that effect)?
That should wipe your ROM memory clean, although I'm not sure if that would help or hinder your cause, as I haven't heard anyone try it yet...
Hope this helps!
Click to expand...
Click to collapse
No, I haven't tried, but I guess I'll give it try when I get back in town on thursday.
Sorry I had to bug out....
Alex, his problem is a little different than a RUUBNH error that's commonly seen. I tried walking him through a CE reset using MTTY & he can't even communicate with his bootloader. MTTY wouldn't establish a USB connection. I agree that formating the Nand may help, but I think you really should also try & reflash hardspl as well. I suggest the new version with AT command support. I have seen a few funky hardspl flashes that inhibit communication, although rare.
I didn't forget you though Kjones, & I'm trying to duplicate your problem & find an answer.
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
OK. I have a noob question that I couldn't find the answer for. I googled and searched the site. I've read quite a few of the threads here as well.
I'm coming to the Fuze from the 8525/Hermes. Now with that, I had to flash a stock ROM prior to every custom ROM. Is it that way with the Fuze as well?
Also, I understand that I need the HardSPL prior to flashing a custom ROM, but if I don't need the go off ATT, I really don't need super CID do I? There's no ExtROM with the Fuze?
Is there also a danger of bricking my Fuze be flashing too many radio ROMs, experimenting like there is with the Hermes/8525?
Again, thanks for your time.
I can't wait to start flashing my new toy.
Jim
You need to HardSPL the Fuze before flashing any ROMs. I don't have any experience with the 8525 so can't relate to what you had to do. I did have the Tilt and I had to do the same thing on the Tilt - flash a HardSPL before flashing ROMs.
You also don't need to flash a stock ROM prior to flashing a cooked ROM. Just flash straight and you're fine.
ecltech said:
You need to HardSPL the Fuze before flashing any ROMs. I don't have any experience with the 8525 so can't relate to what you had to do. I did have the Tilt and I had to do the same thing on the Tilt - flash a HardSPL before flashing ROMs.
You also don't need to flash a stock ROM prior to flashing a cooked ROM. Just flash straight and you're fine.
Click to expand...
Click to collapse
Thanks.
Just wanted to make sure so I don't brick my phone.
The thing about flashing stock ROM was going from Big Storage to Non Big Storage. I even had a stripped stock ATT ROM with no radio because the Hermes board reported bricks from repeatedly flashing radios.
Thank and again, sorry for the noob question.
Jim
Correct, you needed to flash the Hermes with a stock rom when switching between a big storage and non big storage rom. You won't have that issue with the Raphael.
Its a rule of thumb to flash with the stock rom before another custom, just so you are sure nothing is left behind. Although, by the way some of us flash, theres not that much time to do this.
I believe someone on the tilt forums explained all this in a thread about how the circuitry worked and how flashing will do to it. There isn't an exact number on how many times you can flash it, but just like any other device, the more the use, it will die down sometime. I believe that number in the thousands, but who knows if someone flashes that many times.
hi,
i have an HTC touch (the 128/256 would be Elfin right?) to which i want to flash another ROM.
well i'm a total noob at this so i don't really understand where or how to start and what to do;
1-is the process reversible?in other words can i downgrade to my original ROM (downloaded it from HTC website)?
2-is it necessary that i upgrade/change the IPL,SPL,USPL,...etc?
3-when doing a CID unlocking,is it safe?or what's the worst case scenario?
4-does the ROM contain a radio by default or should i install it seperately?and is it necessary to upgrade/change it?
sorry for asking too many questions,but i wanna know how to do it right
thanks
suzaku said:
hi,
i have an HTC touch (the 128/256 would be Elfin right?) to which i want to flash another ROM.
well i'm a total noob at this so i don't really understand where or how to start and what to do;
1-is the process reversible?in other words can i downgrade to my original ROM (downloaded it from HTC website)?
2-is it necessary that i upgrade/change the IPL,SPL,USPL,...etc?
3-when doing a CID unlocking,is it safe?or what's the worst case scenario?
4-does the ROM contain a radio by default or should i install it seperately?and is it necessary to upgrade/change it?
sorry for asking too many questions,but i wanna know how to do it right
thanks
Click to expand...
Click to collapse
1.) Yes, once you Hard Spl your phone you can flash any rom, custom or OEM
2.) Yes, you must change from a stock spl/uspl to a custom one.
3.) Yes, For the most part it is safe, but like driving your car, accidents happen and the worst case is you brick your phone.
4.) some roms contain radios and some roms do not, you can always flash your favorite radio after the rom flash.
Don't worry this is the right section to ask questions. Read this thread and other threads in the upgrade section. Re read until it makes sense and then go for it.
http://forum.xda-developers.com/showthread.php?t=445666
1.) Yes, once you Hard Spl your phone you can flash any rom, custom or OEM
2.) Yes, you must change from a stock spl/uspl to a custom one.
3.) Yes, For the most part it is safe, but like driving your car, accidents happen and the worst case is you brick your phone.
4.) some roms contain radios and some roms do not, you can always flash your favorite radio after the rom flash.
Don't worry this is the right section to ask questions. Read this thread and other threads in the upgrade section. Re read until it makes sense and then go for it.
http://forum.xda-developers.com/showthread.php?t=445666
Click to expand...
Click to collapse
thanks a lot denco,your help is really appreciated .
i did some digging myself about this,and i ran through this topic:
http://forum.xda-developers.com/showthread.php?t=408637
and now things are starting to become more clear,but now i have another questions:
1-if i dump my IPL/SPL,can i restore them again over the stock ones (in case i wanna sell my phone or something like that)?
2-it seems a bit dumb ,but i thought CID unlocking and USPL changing are 2 completely different things,but now i see that they are two different descriptions for the same thing,am i right?
thanks
suzaku said:
thanks a lot denco,your help is really appreciated .
i did some digging myself about this,and i ran through this topic:
http://forum.xda-developers.com/showthread.php?t=408637
and now things are starting to become more clear,but now i have another questions:
1-if i dump my IPL/SPL,can i restore them again over the stock ones (in case i wanna sell my phone or something like that)?
2-it seems a bit dumb ,but i thought CID unlocking and USPL changing are 2 completely different things,but now i see that they are two different descriptions for the same thing,am i right?
thanks
Click to expand...
Click to collapse
Yes you can restore everything to stock for warranty return, providing it is not your usb connector that is th problem.
They used to be two different things, but now with the new Uspls/Spls it is the same thing
so from what i understood,all i have to do is upgrade my USPL and dump my stock IPL/SPL for restoring purposes (or can i do that without having to dump them?) and i'm ready to flash...right?
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.