Database Info

Need WM6 Underground

Since morning i'm trying to find the link where i can download the WM6 undergroud version. Actually i tried installing WM6 Most beautiful, but i'm getting Update error [302] after 95% of installation. Mine is a G3 phone with IPL 2.26 and SPL 2.26
Thanks
Abhinandan

CID locked!

enggabhinandan said:
Since morning i'm trying to find the link where i can download the WM6 undergroud version. Actually i tried installing WM6 Most beautiful, but i'm getting Update error [302] after 95% of installation. Mine is a G3 phone with IPL 2.26 and SPL 2.26
Thanks
Abhinandan
Click to expand...
Click to collapse
The dreaded 95% error... He's right. Your Wizard is still CID locked.
Follow this thread to get your device CID unlocked and then try flashing WM6 again.
http://forum.xda-developers.com/showthread.php?t=285435

enggabhinandan said:
Since morning i'm trying to find the link where i can download the WM6 undergroud version. Actually i tried installing WM6 Most beautiful, but i'm getting Update error [302] after 95% of installation. Mine is a G3 phone with IPL 2.26 and SPL 2.26
Thanks
Abhinandan
Click to expand...
Click to collapse
i remember the time, when people were able to search info BEFORE stupid moves...now, my dear users, we have dying moloch named internet.
gl.

everbody is lazy now
when i first staring updating my wizard. I read for a few days because I wanted to make sure it was done right. People read one post and then try to flash there phone only to mess it up. I guess they have alot of money to buy more phones.

tomred said:
when i first staring updating my wizard. I read for a few days because I wanted to make sure it was done right. People read one post and then try to flash there phone only to mess it up. I guess they have alot of money to buy more phones.
Click to expand...
Click to collapse
If only we were all so rich... When I first started, I downloaded a WM6 Rom I found on this forum but read nothing... Tried to flash it, phone went to bootloader immediately afterwards and would do nothing else. I called T-Mobile and they sent me to the place on T-Mobile.com where I could get the official Rom download and was able to restore my MDA to life again but not until I had read about 20 different threads, did I attempt it again.
Thats the problem with some people here. They don't read and just assume that because they're a Software Dev that they automatically know everything or think that because they're pretty computer savvy that they know what they're doing or think that because they had their device for a few months that they're automatically an expert... It's annoying to tell you the truth because the only real way to learn is through a lot of reading, or trial and error and thats how everyone here has to learn.

I read this forum for a few MONTHS before I flashed my device, and I'm glad I did. Not only do you have to READ the information, but you also have give it time to SINK IN so that it is fully understood.
There are some people who automatically cry out for help without expending any effort (NOOBE needs help! give me a link, fix this, WAA WAA). And then there are the ones who make this a great forum, they READ READ and REREAD, TEST and RETEST and generally provide knowledge, information and assistance.
All of us are riding on the backs of the mostly unsung developers Like Faria, Bepe and all the others.

joemanb said:
I read this forum for a few MONTHS before I flashed my device, and I'm glad I did. Not only do you have to READ the information, but you also have give it time to SINK IN so that it is fully understood.
There are some people who automatically cry out for help without expending any effort (NOOBE needs help! give me a link, fix this, WAA WAA). And then there are the ones who make this a great forum, they READ READ and REREAD, TEST and RETEST and generally provide knowledge, information and assistance.
All of us are riding on the backs of the mostly unsung developers Like Faria, Bepe and all the others.
Click to expand...
Click to collapse
Exactly,very true cudn't have said much better than this,had sleepless nights,doubts,fears an what if this and what if that happened,read and reread the forums for weeks and posting question,only when as you say 'give it time to SINK IN so that it is fully understood' YUP! GOT IT !!! SMOOTHLY
Dharvey
Dan I'M BACK!! MY WIZARD IS FIXED THANKS TO SOME GOOD OLD FASHION SOLDERING SKILLS...
Hey buddy I'm so pleased you got it done,CONGRATS man

Why the hell do you want Underground????!!!!!!!!
It's old, unstable and has soooo many bugs that have all been resolved in recent ROMs. Have you just had the forum on pda view then jumped at the first WM6 ROM post from the early days?

I'm not interested with the Underground WM6 but when MB_WM6 did not work, i thought of trying that.
I have a question here, i tried installing MB_WM6 and it stopped at 95%, later i tried to install Faria's kitchen ROM and it was successful. I tried unlocking the CID with lokowiz03. Do u people still feel that my phone is still CID locked.

enggabhinandan said:
I'm not interested with the Underground WM6 but when MB_WM6 did not work, i thought of trying that.
I have a question here, i tried installing MB_WM6 and it stopped at 95%, later i tried to install Faria's kitchen ROM and it was successful. I tried unlocking the CID with lokowiz03. Do u people still feel that my phone is still CID locked.
Click to expand...
Click to collapse
Download WST tool and run it,it'll give all the info about your phone to determine the present status of your phone,only than it can be confirmed if it's cid locked or unlocked.
btw,faria's kitchen is for cooking the custom rom according to your own needs,it contains the Base Rom,OEM,RUU... and tools to build a rom.Did you cook your own Rom and flashed ?

joemanb said:
I read this forum for a few MONTHS before I flashed my device, and I'm glad I did. Not only do you have to READ the information, but you also have give it time to SINK IN so that it is fully understood.
There are some people who automatically cry out for help without expending any effort (NOOBE needs help! give me a link, fix this, WAA WAA). And then there are the ones who make this a great forum, they READ READ and REREAD, TEST and RETEST and generally provide knowledge, information and assistance.
All of us are riding on the backs of the mostly unsung developers Like Faria, Bepe and all the others.
Click to expand...
Click to collapse
Well said my friend... This is is how it should be. I think there should be a rule that have to be a member for so many weeks before you can even post and access download links on the forum... This should give you time to read before you make a mistake and brick your phone...

Thanks....i will surely search for WST tool. If u could post the link of the WST tool that will be of great help.
Thanks
Abhinandan

Hey........i found the link and also downloaded it.......thanks for the info

i tried flashing buttons ROM twice. The IPL version and others except SPL got changed to older one....but SPL remained the same 2.21, should itry flashing the buttons ROM again and again till SPL get changed to 1.01

now i installed the Xda_MiniS_LaunchROM_v154102 also even then the SPL version 2.21 only, how shall i change that to older one

enggabhinandan said:
now i installed the Xda_MiniS_LaunchROM_v154102 also even then the SPL version 2.21 only, how shall i change that to older one
Click to expand...
Click to collapse
do a soft reset of your phone , tap with stylus the soft reset button on the phone.the phone will reboot,see if it changes the spl,otherwise flash button's rom 1.05 a couple of more times and then do the soft reset,hope it'll change

Sorry...for posting the same info in a new thread......one more question here how to do a soft reset...is it by using ur WST tool. By keeping the power button pressed it will ask that device will be turned off....is this soft reset...or is there any other way to do

enggabhinandan said:
Sorry...for posting the same info in a new thread......one more question here how to do a soft reset...is it by using ur WST tool. By keeping the power button pressed it will ask that device will be turned off....is this soft reset...or is there any other way to do
Click to expand...
Click to collapse
To perform a soft reset,use the stylus to lightly press and hold the RESET button on the left side of your device,it's a small hole type just underneath Infrared port,you just can't miss it,ok

I simply tried unlocking CID from lokowiz even though my IPL/SPL was 1.05/2.21. I got the below results .....in the result it says CID unlocked, can any senior person have a look at the output say was CID really unlocked
Type the letter and press Enter: C
CID unlocking mobile... DO NOT DISCONNECT UNTIL THE PHONE REBOOTS!
Copying C:\lokiwiz02_173\Utils\itsutils.dll to WCE:\windows\itsutils.dll
CopyTFFSToFile(0x0, 0x10000, lock_backup.bin)
g=16: 314962fa - 121b40d192a81203
Key idx: 16
olddata: 55e9ed9a9ab801da460f100469464259621e8365aeb43277cf2858b925828379
newdata: 95ea23df0bf16432cf7be60912a5cbdedee342037c9d3bd3dee342037c9d3bd3
newsum=f6adec8d encsum=2ee6f10180a5c82d
This exe file was created with the evaluation version of Perl2Exe.
For more information visit http://www.indigostar.com
(The full version does not display this message with a 2 second delay.)
...
CopyFileToTFFS(cidunlocked.bin:0, 0, 00010000)
result=80072746
Your phone is now CID unlocked....
Store the generated 'lock_backup.bin' file in a safe place. It can help to resto
re your device if anything goes wrong.
ECHO is off.
"Standing on the shoulder of giants"
Ricardo Afonso, 2005

Tilt Was bricked..any ideas as to unbricking?

hey Guyz. I have a Tilt that a customer gave me that got bricked while trying to flash one of dutty's roms...Problem is that the genius didn't load up Hard SPL even tho he told me that he did...now He wants me to fix it...even tho he didn't follow my instructions and read the WiKi...I kno that on the Hermes it was able to be unbricked. Is the same for the Kaiser possible? I would greatly appreciate your help as my customers are loving the work you guyz do here in nyc..
Thanks in Advance!
Cristian

What is the current status of the phone?
Can you get into the bootloader at all?
If you can get to the bootloader you should be able to load the AT&T AKU v0.4.4 ROM (the unoffical upgraded AT&T ROM). Once you get that loaded you should flash HardSPL immediately.
Let me know how it goes...
Cheers.

I bricked my tilt when it was less than 24 hours old... I recovered it with a BETA of the ATT rom and THEN redoing the hardspl thingy - worked a treat.
Do a search for tolt bricked and you should find afew threads for it.
The rom is called something like RUU_Kaiser_ATT_WWE....._Internal.exe

It goes to the Tri-Color Screen but stays there..I'll go ahead and research it so I can find the original AT&T and load it up...It shows a lot..workin for at&t and being a member on xda...U guyz have no idea how ya make life easier for my tilt customers b/c at&t truly dropped the ball on the rom...and by offering alternatives..u make the user experience so much better...thanks!

HTCFAN0923 said:
It goes to the Tri-Color Screen but stays there..I'll go ahead and research it so I can find the original AT&T and load it up...It shows a lot..workin for at&t and being a member on xda...U guyz have no idea how ya make life easier for my tilt customers b/c at&t truly dropped the ball on the rom...and by offering alternatives..u make the user experience so much better...thanks!
Click to expand...
Click to collapse
If you are at the bootloader screen (Tri-Color) then the phone is not bricked. In the sticky at the top on how to revert back for warranty replacement, it has links for the various roms. Just flash an official AT&T rom on it and you should be good to go. Then do the HardSPL.
Cool that you work for AT&T and hang out here! If you have any other warranty returns, I can give you my address as I wouldn't mind having a backup or two...
BTW: The AT&T ROM for the Tilt is actually quite good in the big picture of things. At least the phone is usable (slower than it should be and less memory than it should have, but its still very usable and stable on the official rom). If you want to ***** about official roms, go back to the 8125 and its official rom. The while the device (at the time) was great, that rom made the phone almost worthless (super slow, battery problems, bad radio, dropped calls, freezing, etc). I can't tell you how many people that run custom roms on the Wizard just can't believe what that phone is actually capable of.
Ok, sorry, got off topic there...

does Hard-SPL needs to be flashed just once on a device or does it need to be installed every tome a new ROM is going to be Flashed onto it?

mfrazzz said:
If you are at the bootloader screen (Tri-Color) then the phone is not bricked. In the sticky at the top on how to revert back for warranty replacement, it has links for the various roms. Just flash an official AT&T rom on it and you should be good to go. Then do the HardSPL.
Cool that you work for AT&T and hang out here! If you have any other warranty returns, I can give you my address as I wouldn't mind having a backup or two...
Click to expand...
Click to collapse
For some reason, it's not being recognized by my Activesync. I got it to recognize it but now it sayz Error 294: Invalid Vendor ID...I'm using the RUU_Cingular_WWE Rom for the Kaiser...so I'm flabbergasted at this point...

Quick Silver said:
does Hard-SPL needs to be flashed just once on a device or does it need to be installed every tome a new ROM is going to be Flashed onto it?
Click to expand...
Click to collapse
Only once! Than you can flash as much as you like!

HTCFAN0923 said:
For some reason, it's not being recognized by my Activesync. I got it to recognize it but now it sayz Error 294: Invalid Vendor ID...I'm using the RUU_Cingular_WWE Rom for the Kaiser...so I'm flabbergasted at this point...
Click to expand...
Click to collapse
ActiveSync will not recognize your device when in BootLoader mode!
The Vendor ID error means the ROM cannot be loaded on the Tilt without HardSPL. You need an original Tilt ROM. (That's what I think about this)

HTCFAN0923 said:
It goes to the Tri-Color Screen but stays there..I'll go ahead and research it so I can find the original AT&T and load it up...It shows a lot..workin for at&t and being a member on xda...U guyz have no idea how ya make life easier for my tilt customers b/c at&t truly dropped the ball on the rom...and by offering alternatives..u make the user experience so much better...thanks!
Click to expand...
Click to collapse
Oddly enough the "Original" Tilt ROM will not install on a Tilt that does not already have HardSPL on it (to spell it out for you, the CID of the ROM does not match the Tilt's stock SPL). If you check the "reverting back" sticky you'll find all this info already, though it is deep in the thread.
The AKU v.0.4.4 ATT Beta ROM does have the correct CID and will flash on a stock Tilt. SO that is what you are forced to resort to at this point. Once you get the beta ROM installed you can (and probably should) install HardSPL.
After all that, if you decide you want to return or warranty the phone follow the "revert" thread to restore it to "stock" form.
Some additional notes on your problem...
ActiveSync will not connect in Bootloader mode (this is expected). You should see a device show up in Device Manager however, I can't recall the exact description however.
quick flash procedure:
put phone in bootloader
connect usb cable
install ROM
FYI, the problem may not be a bricked tilt... you could try Pof's fix which involves using MTTY.exe to boot the phone, depending on how your "customer" tried to flash it it may just need a kick in the pants to restore it. (search Pof's SSPL for the Kaiser thread for instructions, the thread was closed so you will have to look deep).
<climbing on my soapbox>
Lastly... your use of the word "customer" concerns me... are you charging people for the work you do to their phones? If so, do you donate to the people who make it possible? I'm probably just misunderstanding you, but if you're profiting from others work, perhaps you should contribute (especially if you're coming here to ask for help).
</climbing down>
Good Luck!
Cheers.

Customers as in I work for an AT&T corporate owned Retail location and they have bought Tilts from me. They kno my Tilt has been modded and they usually want to do the same. I don't charge them for doing mods to their Tilts. This still remains a community where we help each other and I cherish that. Greed has no place here.

as far as ur suggestions...It looks like I'm gonna be drunk @ 4am on XDA tonite...lol...

HTCFAN0923 said:
Customers as in I work for an AT&T corporate owned Retail location and they have bought Tilts from me. They kno my Tilt has been modded and they usually want to do the same. I don't charge them for doing mods to their Tilts. This still remains a community where we help each other and I cherish that. Greed has no place here.
Click to expand...
Click to collapse
That's cool... my misunderstanding then. Hopefully no hard feelings .
All in all it sounds like the guy wants a custom ROM so you should probably get the ATT Beta ROM and install that. And then install HardSPL.
Check Kyphur's second post in the thread below for the ROM you want.
http://forum.xda-developers.com/showthread.php?t=343198

Thanks for the info sycho...I'll get to it after work..

Good news! The AKU 0.33 worked! Thanks for ur help sycho!

how can i re-install the window? at tilt 8925
i have wm6.1
i want to reset it so the error message shud gone like Recover ?

@kaal,
It seems what you want to do is a HARD RESET. Please visit Kaiser Wiki and read through. You'll know your phone better that way.
@HTCFan & Sirsycho, Glad you both sort it out in the community spirit Cheers!

sirsycho said:
Oddly enough the "Original" Tilt ROM will not install on a Tilt that does not already have HardSPL on it (to spell it out for you, the CID of the ROM does not match the Tilt's stock SPL). If you check the "reverting back" sticky you'll find all this info already, though it is deep in the thread.
The AKU v.0.4.4 ATT Beta ROM does have the correct CID and will flash on a stock Tilt. SO that is what you are forced to resort to at this point. Once you get the beta ROM installed you can (and probably should) install HardSPL.
After all that, if you decide you want to return or warranty the phone follow the "revert" thread to restore it to "stock" form.
Some additional notes on your problem...
ActiveSync will not connect in Bootloader mode (this is expected). You should see a device show up in Device Manager however, I can't recall the exact description however.
quick flash procedure:
put phone in bootloader
connect usb cable
install ROM
FYI, the problem may not be a bricked tilt... you could try Pof's fix which involves using MTTY.exe to boot the phone, depending on how your "customer" tried to flash it it may just need a kick in the pants to restore it. (search Pof's SSPL for the Kaiser thread for instructions, the thread was closed so you will have to look deep).
<climbing on my soapbox>
Lastly... your use of the word "customer" concerns me... are you charging people for the work you do to their phones? If so, do you donate to the people who make it possible? I'm probably just misunderstanding you, but if you're profiting from others work, perhaps you should contribute (especially if you're coming here to ask for help).
</climbing down>
Good Luck!
Cheers.
Click to expand...
Click to collapse
Because of you folks and this thread, I have a working device as opposed to a paperweight...Thanks!!!

"task 2a" nothing happens

I want to hard brick my Kaiser, I want to try to clear the bad blocks of the memory.
Because everytime it restarts, it goes in bootloader mode.
But most of the commands I type in Mtty don't return any result.

kafediev said:
I want to hard brick my Kaiser, I want to try to clear the bad blocks of the memory.
Because everytime it restarts, it goes in bootloader mode.
But most of the commands I type in Mtty don't return any result.
Click to expand...
Click to collapse
if you have the 1.xx versions of SPL, then you can use task 2a. Version 3.xx has been patched by jocky to do nothing when called.

Thank you.
How can I remove bad blocks on HardSPL-3.56 ?
Or change the SPL back to v1 and use "task 2a" ?

kafediev said:
Thank you.
How can I remove bad blocks on HardSPL-3.56 ?
Or change the SPL back to v1 and use "task 2a" ?
Click to expand...
Click to collapse
you can revert back to SPL v1 from olipof or jockys' version, but doing task 2a would "brick" your kaiser. You will eventually do the frankenkaiser after that. I did this before to remove bad blocks from my Kaiser BUT MAKE SURE YOU HAVE THE RIGHT RADIO FIRST BEFORE DOING THIS.

dont do this!
task 2a doesnt clear the bad blocks!
task 2a is only savety, if your device is "secure unlocked"
you must know what qemsbl is and know how frankenkaiser works!
nobody need this steps!!! realy nobody!!!

NetrunnerAT said:
dont do this!
task 2a doesnt clear the bad blocks!
task 2a is only savety, if your device is "secure unlocked"
you must know what qemsbl is and know how frankenkaiser works!
nobody need this steps!!! realy nobody!!!
Click to expand...
Click to collapse
OK, then what do you suggest.
Every time my Kaiser restarts it goes into bootloader mode.
No matter of the ROM, Radio or SPL I am using.
I've tried everything, "task 2a" is my only hope now.

kafediev said:
OK, then what do you suggest.
Every time my Kaiser restarts it goes into bootloader mode.
No matter of the ROM, Radio or SPL I am using.
I've tried everything, "task 2a" is my only hope now.
Click to expand...
Click to collapse
do task 2a if and only if you know the consequences of what you're doing. Only way to revive from task 2a is Frankenkaiser that's why I've told you that you need to have the right radio for it. Read the frankenkaiser thread and do it if you're very sure about it. It's pretty safe and I've done it about 3-4 times already, but read first-- I mean really READ first

NetrunnerAT said:
dont do this!
task 2a doesnt clear the bad blocks!
-it *might* clear the bad blocks, no guarantee. I had three bad blocks and it cleared one
task 2a is only savety, if your device is "secure unlocked"
-not necessarily, it was the case before the great frankenkaiser
you must know what qemsbl is and know how frankenkaiser works!
-of course, you need to know how frankenkaiser works! no need to know qemsbl
nobody need this steps!!! realy nobody!!!
Click to expand...
Click to collapse
as I've said, read the frankenkaiser carefully, and DONT DO IT UNTIL YOU ARE SURE OF WHAT YOU ARE DOING.

Install any MFG based hardspl for the kaiser & then PM me. I will send you the coorect flashcheck command to repair blocks if it is only a data issue. If they are physically bad there is nothing you can do period.
But listen to Netrunner, & I when I tell you, that task 2a has NOTHING to do with blocks, at least not since Hermes. So you will just be killing the SPL & the OS, nothing to do with formatting the flash blocks, there are many different commands to format, repair or erase many different sections, chips or partitions within each.

I am using HardSPL-3.56 is it a MFG based SPL ?
Sorry for the noob question.

Kaiser intermittently stuck in SPL? - Possible solution and prevention!

so, I had some people contact me about the above problem. apparently some kaisers have this for some reason: they for no reason enter bootloader screen and won't boot OS.
the usual mtty commands ("set 16 0", "set 14 0") do not seem to help, and the whole thing is intermittent, sometimes you can still get the OS to boot. (NickCollision mentioned shorting the battery terminals after removing the battery helps for a while)
I patched the 3.29.Hard HardSPL (and the 3.56 too) to remove all enterbootloader reasons other than the usual stuff, keyboard combination and ruunbh tag.
both 3.29 and 3.56 will now say .Hard2 where the 2 means it is patched version =) so it will be less confusing to users.
UPDATE: you can try using force-usb SPL versions now, see new attachments!
UPDATE2: you can try 1.0.olipof-nostuckinspl-force-usb version and 3.31 hardspl (new hardspl, asked for by some users, of course with all these features)
3.29 is still very strongly recommended over 3.56, unless you have OS freezing issues with 3.29.
download from attachment and flash with SSPL to fix problem if you can get the OS booting at least once. also strongly recommended to flash this for prevention even if you have no problems yet!
what to do if you are still stuck in SPL - in that case, the spl overwrite protection will not let you flash. you should try to get the OS booting at least once. try with USB in, or after battery removal-reinsertion, those help increase chances.
if that doesn't work out, then see below what to do in that case:
the kaisdiagtest1.zip or the kaisdiagSD.zip in attachments may help solving the problem of reflashing the SPL to the patched version, if you absolutely can't get the OS to boot at least once.
the one of these allows you to reflash SPL via USB connection, the other one allows you to reflash from microSD card. this SD one is strongly recommended especially if you have problems with USB connection in SPL. it is also much more automatic.
usage STEP BY STEP (only if you cannot get the OS to boot not even one time!).
for diag and flash via microSD:
1. format a microSD to fat32 (use a card reader on a PC), copy the image to it from the KAISDIAGSD.zip in attachment (extracted filename KAISDIAG.NBH). this is basically an SSPL patched to load from SD without booting OS and then it will autoflash my hardspl again from SD.
2. put one of my hardspl's on the card too (in attachment, 3.29.Hard2 or 3.56.Hard2, 3.29 recommended). name this file as KAISIMG.NBH!!!
3. insert the microSD in the kaiser, then reset kaiser.
4. it should say Loading / Update in progress then reboot to a screen saying SPL 1.00.OliNex.
5. it should now flash in the KAISIMG.NBH. and will reset.
6. at this point it should boot to the OS, if it doesn't, then flash an OS. (of course delete the previous KAISDIAG.NBH and KAISIMG.NBH from the sd card and remove sd unless you opt to flash the OS from sd too)
for diag and flash via USB:
1. format a microSD to fat32 (use a card reader on a PC), copy the image to it from the kaisdiagtest1.zip (extracted filename KAISDIAG.NBH). this is basically an SSPL patched to load from SD without booting OS.
2. insert the microSD in the kaiser, then reset kaiser.
3. it should say Loading / Update in progress then reboot to a screen saying SPL 1.00.OliNex.
4. it should then work with RUU over USB (has USB force patch). but test with mtty first, make sure to disable usb connection in Activesync/WMDC! if PC doesn't see the device, try a USB replug. also, the USB should be plugged in all the time (except for when you replug)!
5. if it seems to have a good connection, then please now flash one of the SPL's posted in this post. after that you will be able to boot OS (of course reflash OS if you need to but the *first* flash *must be* SPL).
6. if this doesn't work (i.e. USB connection won't go), then go and check the SD version of the diag image, if you haven't already.

Wow Great work.
Thank you very much for your hard work! Going to sticky this for the time being.

Damnn,m nice work.

Thanks for this.
I have added it to my Wiki page on what to do if you get stuck at the bootloader. (Kaiser_Stuck_at_bootloader).
Anything you spot wrong with it feel free to modify (I asked GSLEON to take a look, but I don't know if he's had time).
Thanks
Dave

I can tell you that it does work and it did fix my kaiser!
Great work!

Nice!
I don't use the SPL, other than the one that came with my phone.
(Warranty....don't want to take a chance). Come October, when the warranty expires, I'll probably start flashing some of the cooked ones, plus, the Raphael
will probably be around by then.

I love you cmonex, let me know if you broke up with olipro

whats your thoughts on using the different SPL's to fix the random freezing issues that seem to hit the kaiser? I know my phone seems to work best with the newest SPL thats out right now from Jocky but it all could be in my head!
----Thank you cmonex, once again you show that your one of the amazing forces behind Xda! I hope there are little girls out there that want to be just like you when they grow up! That would be so cool a bunch of mini cmonex's running around we would have no issues with are WM devices then!

sakajati said:
I love you cmonex, let me know if you broke up with olipro
Click to expand...
Click to collapse
lol, sorry, no chance

austinsnyc said:
whats your thoughts on using the different SPL's to fix the random freezing issues that seem to hit the kaiser? I know my phone seems to work best with the newest SPL thats out right now from Jocky but it all could be in my head!
Click to expand...
Click to collapse
most probably that was because the older SPL's formatted nand too aggressively, so the end of the OS might get erased, which is no good. wasn't a problem before but the new OS's are bigger, so it affects them more likely.
as for the SPL versions, I don't really recommend 3.56 SPL, 3.29 seems much better in terms of available commands (though neither has task 2a for frankenkaiser fun ). did someone have any good experience with the 3.56 over 3.29? - I wonder why it is an option.

cmonex can u post the patch for the 3.56 it would be greatly appreciated, thanx

Get a new battery. The reason for this problem is the power manager keeps reseting the watchdog timer. Depending on when that happens the unit will either constantly reboot or enter bootload.
For some reason the BatSense line goes high and stays high. I haven't dissected the battery yet, but replacing it solved the problem.

htcfan2008 said:
For some reason the BatSense line goes high and stays high. I haven't dissected the battery yet, but replacing it solved the problem.
Click to expand...
Click to collapse
Not discounting the theory, just wanted to say that I had swapped out battery's during my testing with cmonex. So two diff battery's, same problem? Unlikely. As cmonex indicated shorting the terminals did have a positive effect, so you may be on to somthing re: the batsense line. Just that swapping batteries had no effect in my experience.
oOoOo my batsense is tingling hehe

Where the two batteries...
Nick Collision said:
Not discounting the theory, just wanted to say that I had swapped out battery's during my testing with cmonex. So two diff battery's, same problem? Unlikely.
Click to expand...
Click to collapse
...Samsung brand made in China, and both more than six month old? Then quite possibly they're both bad. (I forgot to mention in my other post that I replaced the battery with a non-HTC brand.) One way to tell is look at the battery edge on: if it has a bulge in the middle or looks "swollen" all around then it surely is bad.
I have found that using a non-HTC car or wall charger almost always and rather quickly kills the battery. It's not the charger voltage but the charging current profile that's the problem.
Anyway, good luck.

the bootloader can enter tricolour screen for a couple reasons other than the usual key combination or nbhload / enterbootloader tags in flash:
- if CPLD function returns 0xF
- or if debugboard is detected for whatever reason
- other configdata in flash tells it to do so
the last one can be excluded, because the problem is intermittent, and flash contents should be permanent.
then, I had Nick Collision run info 7 (which calls the same function), and it doesn't return 0xF, so maybe the second one.
I don't know what would cause that though, this battsense line sounds interesting.
to ofcourseimnaked: OK, i will do that soon.

Don't have a Kaiser SPL handy, but it must be using the same boot tags as Trin/Herm.
ClrRUUTagGoToOS
ClearGotoULTag
DeviceWarmBoot
CELoadComplete
NbhLoadSuccess
EnterBootloader
GoUpdateLoader
DeviceColdBoot
SetRuuNbhUpdate
These tags are programmed into flash to force boot in required mode.
Is this the config data you are referring to?

One other thing...
SPL and OS kernel debug log is stored in flash too, the reason for soft reset may be found in the log? It should be possible to dump the log with procdump once device boots to OS.
Don't know the offset for Kaiser Should be in the next block after the block with CID and boot tags though.

stepw said:
Don't have a Kaiser SPL handy, but it must be using the same boot tags as Trin/Herm.
ClrRUUTagGoToOS
ClearGotoULTag
DeviceWarmBoot
CELoadComplete
NbhLoadSuccess
EnterBootloader
GoUpdateLoader
DeviceColdBoot
SetRuuNbhUpdate
These tags are programmed into flash to force boot in required mode.
Is this the config data you are referring to?
Click to expand...
Click to collapse
yes, those mainly, and some flags.
but the issue is not them.

stepw said:
One other thing...
SPL and OS kernel debug log is stored in flash too, the reason for soft reset may be found in the log? It should be possible to dump the log with procdump once device boots to OS.
Don't know the offset for Kaiser Should be in the next block after the block with CID and boot tags though.
Click to expand...
Click to collapse
you mean task 37? btw, reset wasn't an issue here, but if someone shows up with a device constantly rebooting, we can look into that too..
note, CID is not really accessible directly from SPL anymore, MSM7xxx. (though right now I'm having fun finally dumping the protected radio nand)

Please explain me what it exacly is.
Is it better, most recent and fixed for Bootloader mode stuck version of HardSPL 3.29 which we can found on 'jockyw2001' thread?
Is it still HardSPL which let me flash any ROM for HTC Kaiser?
Thanks for all explains. Best regards.

Flash - What Went Wrong?

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