Hi !
By freeze i mean: tap the screen or press keys and nothing happens for 2-5 seconds. This would happen to me about once every 2 minutes.
This is what i did:
http://forum.xda-developers.com/showthread.php?t=335568
I used the SPL extracted from the nbh of the official wm6.1 build which reverted my SPL back to the official one. You won't be able to flash a custom ROM anymore, until you install HardSPL again.
I have been using the Kaiser for about 30 min and no freeze.
It was not my idea that it was a SPL issue, someone mentioned this in a thread about the leaked WWE 6.1 (which is identical to the official WWE one)
edit1: This only applies if you installed HardSPL
edit2: Thanks to shafez for being the first to think about this. Apparently i was trying it at the same time as him, so i didn't know he also posted the results, that's why i started the thread as soon as saw the fix worked.
did you notice any other improvements like speed?
RPG0 said:
Hi !
By freeze i mean: tap the screen or press keys and nothing happens for 2-5 seconds. This would happen to me about once every 2 minutes.
This is what i did:
http://forum.xda-developers.com/showthread.php?t=335568
I used the SPL extracted from the nbh of the official wm6.1 build which reverted my SPL back to the official one. You won't be able to flash a custom ROM anymore, until you install HardSPL again.
I have been using the Kaiser for about 30 min and no freeze.
It was not my idea that it was a SPL issue, someone mentioned this in a thread about the leaked WWE 6.1 (which is identical to the official WWE one)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=2230736&postcount=206
It seems change the pagepool to 16MB helped. I tested, it works for me.
Thats more like it ..
xwaiz said:
http://forum.xda-developers.com/showpost.php?p=2230736&postcount=206
It seems change the pagepool to 16MB helped. I tested, it works for me.
Click to expand...
Click to collapse
can some1 post in this thread how to fix the pagepool? some sort of manual?
thnx a lot
NoFatePPC said:
can some1 post in this thread how to fix the pagepool? some sort of manual?
thnx a lot
Click to expand...
Click to collapse
kyphur has a pagepool patcher program that allows u to modify pagepool of ur rom nbh very easily.
use search; its on here. use a phrase like "kyphur pagepool patcher" which should bring up promising results.
SSOO
what you did exactly?
u changed PP or flashed another SPL, if its SPL, could you post it?
xwaiz said:
http://forum.xda-developers.com/showpost.php?p=2230736&postcount=206
It seems change the pagepool to 16MB helped. I tested, it works for me.
Click to expand...
Click to collapse
I don't doubt that you are experiencing better behavior, but I would like to get some more information on this from a developer who actually understands the mechanics here.
I am certainly not that person, but as I understand it the SPL is a bootloader. As such, I'm not really sure what it has to do with operation of the OS after the OS is booted.
In addition, everything I understand about the pagepool, and changing the pagepool, I have a hard time understanding how a different SPL is going to change the size of the pool.
Again, I don't doubt your experiences, and even if we get 100 people saying this worked for them I would like to understand why this would possibly work.
Any actual developers have any input? (please, my amateurish suppositions are enough guesswork, if you don't have educated answers there isn't need to postulate).
Can you upload the 6.1 spl here and this should work on an MDa Vario III right?
Don't really know much about all of the techie stuff but I have also found that by reducing the cache sizes to "advised" and the PP to 16MB I do not experience any freezes. I have been running Dutty's test and also tried it with both L26 Roms and it works every time.
Just flashed the official new rom om my brand new phone and I´m not having any freezing issues. The phone was not hardspl as it was new out of the box.
I am certainly not that person, but as I understand it the SPL is a bootloader. As such, I'm not really sure what it has to do with operation of the OS after the OS is booted.
Click to expand...
Click to collapse
I´m not into the workings of the device and not a hacker/programmer of any kind but what comes to mind is that if there is some incompability with the bootloader and the OS and the bootloader loads the OS the wrong way it seems natural to me that you will get errors that may result in strange behaviours of the OS. It may not be a large error and therefore the OS loads but with faults resultning in "bugs".
or its simply a bad rom. I will refrain from going to hardspl and testdrive the rom for a few weeks and se if I can come up with som errors.
can someone maybe upload german fixed version? thank you!
16 mb page pool really helps!
Very easy to do just using xda page pool patcher.
Do not forget to click "Save" button and then "Analyse" again to confirm .nbh file was updated successfully.
n00b question:
What is a nbh and pagepool? Will this affect the performance? I'm trying to learn as much as I can.
I don't post a lot, and I do not know the technical ins and outs of the SPL, but here is a theory. While browsing one of the threads regarding the video acceleration drivers, someone mentioned that the SPL could have something to do with initiating video acceleration. If this official release was supposed to have any sort of graphics fix, maybe something exists in the SPL of the official release that doesn't exist in HardSPL, and that is the reason we are experiencing the freezes. Just a thought.
bengalih said:
I don't doubt that you are experiencing better behavior, but I would like to get some more information on this from a developer who actually understands the mechanics here.
I am certainly not that person, but as I understand it the SPL is a bootloader. As such, I'm not really sure what it has to do with operation of the OS after the OS is booted.
In addition, everything I understand about the pagepool, and changing the pagepool, I have a hard time understanding how a different SPL is going to change the size of the pool.
Again, I don't doubt your experiences, and even if we get 100 people saying this worked for them I would like to understand why this would possibly work.
Any actual developers have any input? (please, my amateurish suppositions are enough guesswork, if you don't have educated answers there isn't need to postulate).
Click to expand...
Click to collapse
Isaygarcia said:
SSOO
what you did exactly?
u changed PP or flashed another SPL, if its SPL, could you post it?
Click to expand...
Click to collapse
I only changed pagepool to 16MB. Did not touch SPL (I think I'm using hardSPL).
Follow up: still no hang/freeze.
To sum up:
after flashing some 6.1 cooked builds around here, i noticed the device would stop responding, i tried two of Dutty's, one Vista, the Diamond V1, maybe some other too. They all had this issue, so i just waited for the official one, hoping that the freezes would be gone. They weren't.
So here's how i fixed it:
I flashed back the original 6.0 official ROM and saw there were no hangs / freezes. So the HW was ok.
After that i flashed the official wm 6.1 from HTC. Then i followed the "Idiot steps" (http://forum.xda-developers.com/showthread.php?t=335568) without any shortcuts (first 14 steps, i skipped step 15 ) and used the 6.1 ROM, not the 6.0 ROM to obtain the nbh file. Flashed the official SPL and hard reset.
All is well now (except i have to remove HTC Home and soft reset to use iGo).
No freezes for a day.
gauntman said:
Just flashed the official new rom om my brand new phone and I´m not having any freezing issues. The phone was not hardspl as it was new out of the box.
Click to expand...
Click to collapse
This supports my theory that 6.1 needs another SPL, probably not compatible with the old HardSPL
xwaiz said:
http://forum.xda-developers.com/showpost.php?p=2230736&postcount=206
It seems change the pagepool to 16MB helped. I tested, it works for me.
Click to expand...
Click to collapse
what is the original pagepool of the WM6.1 ROM just in case I want to revert back to it?
RPG0 said:
This supports my theory that 6.1 needs another SPL, probably not compatible with the old HardSPL
Click to expand...
Click to collapse
Just one question. What Country ID I should set in htc rom tool, to make it look exactly like UK htc branded kaiser?
Related
I ran it according to farias instructions I thought. It flashed but now I cant install anything and I cannot write to the storage card or the phone, any cab i try to install is unsuccessful and I cannot save any files to the storage card or the phones memory.
And it appears that I cannot flash the rom again. Am I screwed?
What is you IPL / SPL? IS your phone a G3 or G4? Can you get to the bootloader? (turn off your phone (pull the battery if you have to) then hold the camera key down while you turn it on). You can flash directly to the bootloader (even though activesync won't connect.
BTW: If this stuff makes you nervous, you probably shouldn't be cooking... Your phone will do all sorts of weird stuff when you screw up a build. And you should really know how to recover from most things that can happen...
I have done this before, this is the first time I have ever had a problem. my IPL/SPL is 2.26. And the phone is unlocked.
beowolf said:
I have done this before, this is the first time I have ever had a problem. my IPL/SPL is 2.26. And the phone is unlocked.
Click to expand...
Click to collapse
ok, cool... wasn't sure... So can you get to the bootloader?
yes I can get to it
I am flashing back to the t-mobile 2.26 rom. Working so far, I will leave the cooking alone. Can you recommend a good wm6 rom that doesnt have any problems?
"doesn't have problems" is the catch
I'm partial to my own Crossbow Reloaded ones, but they aren't perfect. If you don't hit the keypad issue with 1.7 though, its pretty close
Core 2.0n is very good and nice and clean.
Also NBD and Wizard Mobile 6 are both supposed to work well.
The new "official" rom we are playing with is beta, but I have to say its really fast and we aren't seeing much wrong with it (but its only been 12 hours since its been released). There are a couple of issues that are fixed with cabs (CommManager for one).
As for cooking, you probably eith had something wrong in a .rgu or somesuch. Just takes a number of builds and flashes to get it right to where it boots (then you debug what you forgot in packages and start over )
I have made three Russian ROM from Damped ROM v. 1.22.411.1
The first contains:
- OS without changes
- Black mainsplash
- radio from Arabian ROM
http://rapidshare.com/files/625681...duemonocle_1.22.411.1_4.1.13.47_02.98.90.rar
The second contains:
- Completely changed the screen of loading
- Has replaced the standard calculator on CalcOne.
- Has removed unnecessary pictures, etc.
http://rapidshare.com/files/630354...lack_V_1.0_1.22.411.1_4.1.13.47_02.98.90.rar
The third same as the second, without Office and Windows Live
http://rapidshare.com/files/630382...lack_V_1.1_1.22.411.1_4.1.13.47_02.98.90.rar
To establish only after updating USPL
Congratulations!!
Finaly someone made it!!
I was trying to do my own cooked rom but I fail. I was trying to get OS.nb from Part02.raw from dump (from other rom), but during process of converting, packages are lost and when I flash device with that I get plain vanilla rom without ANY customization. Simply, none of .provxml files are procesed during cold boot. That`s not what I want.
Any idea what went wrong?
Anyway, I see that you used Htc rom tool by Dark Simpson with Excalibur option to get .nbh file, is that correct??
anyone try and flash yet?
i would like to try but i don't want to brick my Vox.
Elisha said:
anyone try and flash yet?
i would like to try but i don't want to brick my Vox.
Click to expand...
Click to collapse
I just made some tests and will risk saying, yes it`s safe to flash it.
But before flashing, run VOX_USPL <----- It`s very important, even if your device is SuperCIDed, just to be safer.
the rom is 1.22 and the USPL is 1.16?
is there any major improvements over 1.15?
is it even worth flashing?
my VOX is factory unlocked btw.
Elisha said:
the rom is 1.22 and the USPL is 1.16?
is there any major improvements over 1.15?
is it even worth flashing?
my VOX is factory unlocked btw.
Click to expand...
Click to collapse
Read this: Vox USPL
i know of that USPL.......my question is that that didn't look like it gave much of a benefit.
and since my phone is factory unlocked again.....what does this 1.22 ROM offer?
Elisha said:
i know of that USPL.......my question is that that didn't look like it gave much of a benefit.
and since my phone is factory unlocked again.....what does this 1.22 ROM offer?
Click to expand...
Click to collapse
More stable, and I think nothing more. I`m sure, your phone is sim-lock factory unlocked, but not a cid unlocked. None of providers or htc provide cid unlock phones.
is it more efficient in the sense that i will have more available free memory at startup?
i have about 23mb usable and fresh startup now!
does this rom have english language? i'm asking because i'm not russian so i don't understand cyrilic, hence i wouldn't understand anything ;P ...and one other question, because i've never flashed my vox: can i, for any reason, flash my vox with another rom, of a previous version than this rom, if i choose to??
This ROM contains two languages: Russian and English.
You can flashing any ROM after flashing VOX USPL.
ok thank you very much for elucidating me
one other question: i've flashed with your rom, but now i have an issue: my qwerty keyboard as a different layout than the one the rom has...my keyboard as the dot next to the P...this layout as the dot next to the Q...consequently the first line of the keyboard is one position shifted to the right...what can i do about it? is there some key in the registry taht i could change?
never mind i already solved my problem...but jesus what i had to do to get through it :S
to anybody that could have been through the same issue as i did:
http://www.modaco.com/content/Smart...obile-Smartphone-Internationalization-Issues/
http://www.microsoft.com/globaldev/reference/winxp/xp-lcid.mspx
also check the registry key in \HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\KEYBD
and change it acordingly with your language code (check the second link for the code)
Really QWERTY keyboards in Russian and English devices differ.
Try to replace a file T9.Libra.russian.0409.kmap.txt in \Windows, on what I apply.
I do not guarantee, that it will solve a problem.
Look also here and here.
Thank you for your rom. My orange sp e650 is really faster when accessing programs and there is more storage left on the phone I like it
And thanks goes to carrots99 too for pointing to this excellent article from Menneisyys. It really helped me putting french language back but I still had to do a lot of editing in the txt file.
Any chance of some screen shots?
Sure. What screenshots would you like ?
I have a small request also. It seems that this rom doesn't support custom animated splash screens in HKLM\Software\HTC\Startup (or \Shutdown)
Could someone please give me the values listed here ? I think a dll was registered here ...
for the animated startup and shutdown screens you have to check the registry for this:
[HKEY_LOCAL_MACHINE\System\Startup\1]
"Dll"="\Windows\oemstartup.dll"
[HKEY_LOCAL_MACHINE\System\Shutdown\1]
"Dll"="\windows\oemstartup.dll"
you need also to check if you have that dll file in windows folder
That's it ! This dll is not included in this rom. My only complaint actually. Any chance you could upload it for me ?
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
Someone please confirm what I read on another thread -- that ROMs based on the current 6.5 will expire, forcing you to reflash.
If this is true, please update the Wiki so that 6.5 flashers will be aware of this.
/as for me, I'm sticking with 6.1 untill 6.5 is officially released...
EDIT: I should say that if someone will confirm this _I_ will put this in the Wiki, unless someone beats me to it....
burtcom said:
Someone please confirm what I read on another thread -- that ROMs based on the current 6.5 will expire, forcing you to reflash.
If this is true, please update the Wiki so that 6.5 flashers will be aware of this.
/as for me, I'm sticking with 6.1 untill 6.5 is officially released...
EDIT: I should say that if someone will confirm this _I_ will put this in the Wiki, unless someone beats me to it....
Click to expand...
Click to collapse
should have asked in that thread instead of starting a new one, the time bomb early on wasn't removed, but now some kitchens remove the time bomb
msd24200 said:
should have asked in that thread instead of starting a new one, the time bomb early on wasn't removed, but now some kitchens remove the time bomb
Click to expand...
Click to collapse
But most are not. Just assume that your 6.5 beta rom is time bombed, back up everyday, and reflash when the time comes.
Or just keep upgrading your rom with new builds so that the time bomb never kicks in.
denco7 said:
But most are not. Just assume that your 6.5 beta rom is time bombed, back up everyday, and reflash when the time comes.
Or just keep upgrading your rom with new builds so that the time bomb never kicks in.
Click to expand...
Click to collapse
true don't know which kitchens are being used on what rom, but tpc has the "official" 6.5 rom dump from the topaz and just released his rom off of it so timb bomb should be gone in that one.
LOL, ROMs are kept on a phone long enough to find out that it's time bombed? I thought they all had a 1 week expiration date
LOL, ROMs are kept on a phone long enough to find out that it's time bombed? I thought they all had a 1 week expiration date
msd24200 said:
should have asked in that thread instead of starting a new one
Click to expand...
Click to collapse
Nah -- I wanted Kaiser folks to confirm since I have a Kaiser and I want to update the Kaiser Wiki.
But thanks for the info that some ROMs have defeated the timebomb.
My ROM does not boot! By reading this.. i can only supose the bomb 'exploded'
Does anyone knows how to change the date in BOOTLOADER mode.. or any other mode that does not require to load the ROM? Just wanted to boot to backup the sms and etc...
Also i can't connect the pocket to the PC via cable.. problems with my miniUSB connection!
So my only chance is really to change the date in the pocket.. before loading ROM!
Any ideas people?
Cumps,
veList
actually, most if not all should be gone. Since I'd imagine most of the chefs on here (including myself ) use ports from other chefs (like twopumpchump, joshkoss, and anryl) because it saves on time, if the build has it removed, so do the countless ROMs that are based off them.
veList said:
My ROM does not boot! By reading this.. i can only supose the bomb 'exploded'
Does anyone knows how to change the date in BOOTLOADER mode.. or any other mode that does not require to load the ROM? Just wanted to boot to backup the sms and etc...
Also i can't connect the pocket to the PC via cable.. problems with my miniUSB connection!
So my only chance is really to change the date in the pocket.. before loading ROM!
Any ideas people?
Cumps,
veList
Click to expand...
Click to collapse
what screen does it stop on? also, you built the ROM yourself?
In my experience, only old builds do that, the one i tried, first joshkoss Roms, with the line "internal use only" was timebombed, it was the 21189 build. Right now i have PDA corners X2V2 Rom, and has no issues, i have it since May i think.
Good luck with your ROMs!
mbarvian said:
what screen does it stop on? also, you built the ROM yourself?
Click to expand...
Click to collapse
TPCElite series V4 wm 6.5 21812
Also the radio i used was 1.70.19.09
But now i flashed 1.65.30.09, just in case it had something to do with it.. but of course.. it's stuck on the same..
It stucks in the screen.. wich has the SplashScreen and the 3 lines of numbers.. discribing the radio and rom, bla bla..
Even tried to wait an hour just in case it booted... but nothing..:\
Additional info: kais130 spl-3.29.Hard2
Cumps,
veList
veList said:
TPCElite series V4 wm 6.5 21812
Also the radio i used was 1.70.19.09
But now i flashed 1.65.30.09, just in case it had something to do with it.. but of course.. it's stuck on the same..
It stucks in the screen.. wich has the SplashScreen and the 3 lines of numbers.. discribing the radio and rom, bla bla..
Even tried to wait an hour just in case it booted... but nothing..:\
Additional info: kais130 spl-3.29.Hard2
Cumps,
veList
Click to expand...
Click to collapse
that's very odd. Usually something like that happens with a bad XIP . I assure you that it's not a timebomb tho
did you install any applications before this happened?
mbarvian said:
that's very odd. Usually something like that happens with a bad XIP . I assure you that it's not a timebomb tho
did you install any applications before this happened?
Click to expand...
Click to collapse
hMm.. not timebomb? but is there anyway of retrieving the lost data (sms, etc..?) or i can just flash another rom 'cause its lost?
I have flash that rom 9 days ago... i thought it was the timebomb 'cause since 3 days ago.. today was my first reboot.. (time 01-july-09 passed.. so on the first reboot.. the rom doesn't load.. this was what passed thru my mind)
Anyway.. last thing i used was Android.. booted normally.. and then shut down normally.. when trying to boot windows it got stuck!
Cumps,
veList
veList said:
TPCElite series V4 wm 6.5 21812
Also the radio i used was 1.70.19.09
But now i flashed 1.65.30.09, just in case it had something to do with it.. but of course.. it's stuck on the same..
It stucks in the screen.. wich has the SplashScreen and the 3 lines of numbers.. discribing the radio and rom, bla bla..
Even tried to wait an hour just in case it booted... but nothing..:\
Additional info: kais130 spl-3.29.Hard2
Cumps,
veList
Click to expand...
Click to collapse
I had that happen to me too... What you will need to do is flash a stock ROM, hard rest, then flash hard spl 3.34, then your radio of choice, then finally flash V6(it is awesome!)...
Some others have had this happen to them as well... not sure what causes it, seems to be something with conflicting info left over from the previous flashed ROM and has something to do the the super RAM hack... not sure, I just know the solution.
And there is no way to back up your info without being able to boot.
errmmm... forgot to tell... haven't installed any aplication on the ROM since flash besides Resco Explorer & Kaisertweak & TOMTOM (but.. no way it had something to do with it)
Cumps,
veList
pjcforpres said:
I had that happen to me too... What you will need to do is flash a stock ROM, hard rest, then flash hard spl 3.34, then your radio of choice, then finally flash V6(it is awesome!)...
Some others have had this happen to them as well... not sure what causes it, seems to be something with conflicting info left over from the previous flashed ROM and has something to do the the super RAM hack... not sure, I just know the solution.
And there is no way to back up your info without being able to boot.
Click to expand...
Click to collapse
:/ crap..:/ really had some important messages i needed to keep!:/
flash hard spl 3.34? really needed?
yes.. already had in mind.. and downloaded v6..
Cumps,
veList
veList said:
:/ crap..:/ really had some important messages i needed to keep!:/
flash hard spl 3.34? really needed?
yes.. already had in mind.. and downloaded v6..
Cumps,
veList
Click to expand...
Click to collapse
Not 100% needed, but you do need to reflash your hard spl, so might as well flash the version that works best with the ROM... FYI, your SPL should match the ROM version... TPC uses HTC ROM version 3.34, so Hard SPL is the proper one to use for best performance.
I can't believe the number of people that haven't read to flash a stock ROM first. Man!
SoberGuy said:
I can't believe the number of people that haven't read to flash a stock ROM first. Man!
Click to expand...
Click to collapse
I don't flash a stock ROM before I flash anything and I've never had problems