Related
hi guys!!! is there any way to run the OS from the memory card????
maybe that way I can recover my elf from the freeze first screen????
please somebody a little help!!!!
thanks
best regards
linterna
Did you flash USPL? If you did, you can get into bootloader and flash another rom.
thanks for the answer!!! what I did was that I flashed the phone with a rom from another model!!!
so the phone power up and stays in the first screen HTC and the legend OS 4.0.0.0 and I try to use the uspl again and the computer cannot see the phone in freeze state but when the phone is in boot mode the computer can see it but in boot mode I cannot run the uspl but I can run the rom updater but I get an error all the time !!!
is there any way to re isntall the OS again from the memory card????
thanks again best regards
linterna
anybody please!!!!
thanks
linterna
linterna said:
but I get an error all the time !!!
Click to expand...
Click to collapse
What error? Did you flash USPL before you flashed the wrong rom? If so and if the rom doesn't contain IPL or SPL you should be able to just flash from bootloader (try big storage and pdaviet). USPL can't be flashed from bootloader.
vippie said:
What error? Did you flash USPL before you flashed the wrong rom? If so and if the rom doesn't contain IPL or SPL you should be able to just flash from bootloader (try big storage and pdaviet). USPL can't be flashed from bootloader.
Click to expand...
Click to collapse
I think that's the solution "try to storage and pdaviet" but I don't know what is this
can you please help
best regards
linterna
linterna said:
I think that's the solution "try to storage and pdaviet" but I don't know what is this
can you please help
best regards
linterna
Click to expand...
Click to collapse
Those are elf roms.
Big Storage: http://forum.xda-developers.com/showthread.php?t=320407
PDAVIET: http://forum.xda-developers.com/showthread.php?t=323378
If it doesn't help. Can you still answer the questions (error message and did you flash USPL already)?
the thin is in boot mode I can run the ROM updater but I have the error .....and then I put it in boot mode again but the USPL doesn't recognize the phone ?????so there is no way to unlock the cid to run the ROM because the phone only stays in boot mode
so my question is is possible maybe to run the OS from the memory card???
thanks
best regards
linterna
If you don't answer my questions I have no idea sorry! You tried flashing those two roms from bootloader? Didn't work? Well then I think it's bricked!
ok I already tryed those ROM's from boot mode ( because is the only mode that the PC recognize the phone) and I have the error (207)all the time and the USPL DOS program cannot see the phone in boot mode ....
nothing I can do with this ???? that's it????
come on!!!
thanks
best regards
linterna
Never heard of error 207, but did hear of "270 Update Error". Remove micro SD card and SIM and try again! Does it start flashing at all and then gives an error or is it at 0%? What's the error message? Be specific!
linterna said:
and the USPL DOS program cannot see the phone in boot mode
Click to expand...
Click to collapse
True, you can't flash USPL anymore (like said before), that's why I ask if you succesfully flashed in the past.... still waiting for an answer tho
sorry my mistake the error is 270 update error
and the process started untill 3% and it goes off and start in the main screen and freeze ...........and once again in boot mode the USPL canoot see the phone and when it freezes there is nothing in the usb!!!
thanks
best regards
linterna
vippie said:
Remove micro SD card and SIM and try again!
Click to expand...
Click to collapse
This is reported to solve the error 270 problem for other people.
linterna, Have you tried to flash one of these ROM's but first remove you micro SD card? It is hard to follow what you said you did to get into this problem. Perhaps you could repost with specifics of every step you made starting with the OEM ROM.
(sorry vippie, looks like we posted the same advice at nearly the same time!)
thank you guy for your answers
ok let's start from the beginning
I flashed the phone with the wrong ROM so the phone now is freezes in the first screen with OS 4.0.0.0 and then I have this problems the phone power up and freezes in the first screen and it doesn't connect thru usb .but when I put it in boot mode the usb can detect it ( there is no sim or memory card on the phone) and I can run the ROM updater but I have the 270 error all the time and then I try to run the USPL but I cannot do it because the usb doesn't detect the phone!!!!!
so it's like I'm stack!!!!!
what should I do??
any help will be appreciated
thanks
linterna
vippie said:
Never heard of error 207, but did hear of "270 Update Error". Remove micro SD card and SIM and try again! Does it start flashing at all and then gives an error or is it at 0%? What's the error message? Be specific!
True, you can't flash USPL anymore (like said before), that's why I ask if you succesfully flashed in the past.... still waiting for an answer tho
Click to expand...
Click to collapse
well I could flash the first time running the USPL but now is not detecting the phone
thanks
linterna
I'm out of options sorry.... removing cards is to me the only known solution for error 270.
literna,
Did you run the CID unlock patch prior to flashing the wrong ROM? What ROM did you try to flash and why? What were you trying to accomplish? Have you tried to hard reset you phone? If so what happened? If you did not CID patch your phone, then it may not be over written and a hard reset may recover it.
General advice: In your last post, you only stated the same things from your earlier posts which were somewhat lacking. If you are newer to this forum or to this type of phone, it will help you greatly to read everything two or three times before flashing, write or print out a step by step script of what you need to do to flash it, then re-read and compare your script against the posted instructions to make sure they agree. Then think about flashing your phone.
p.s. - The very fist post by the moderator on the Elf Upgrading page is a step by step script for flashing any (ELF) ROM to the ELF. Compare what it says and report what your did relative to that post so we can fully understand how to help you further. You may need to run the enable RAPI script to re-establsih communication, but this depends on what you may have already done.
raskell said:
literna,
Did you run the CID unlock patch prior to flashing the wrong ROM?well I didn't flash it with the wrong ROM but I flashed a couple of times before the wrong one!! What ROM did you try to flash and why?I tryed to put spanish on my ELF and I don't know what ROM I flashed it aparently a bad one!!! What were you trying to accomplish? spanish Have you tried to hard reset you phone?yes I already try (if you talking about the reset boton near to the mic on the bottom of my device) If so what happened? If you did not CID patch your phone, then it may not be over written and a hard reset may recover it.
General advice: In your last post, you only stated the same things from your earlier posts which were somewhat lacking. If you are newer to this forum or to this type of phone, it will help you greatly to read everything two or three times before flashing, write or print out a step by step script of what you need to do to flash it, then re-read and compare your script against the posted instructions to make sure they agree. Then think about flashing your phone.
Click to expand...
Click to collapse
thanks for you time to answer
linterna
Hi.
I have not posted much on this site, yet I have used it plenty of times. And first off I have to say "Thank you oh so very much" to everybody who frequent this site. Most of all I would like to thank the developers and rest of the crew that helps users on a daily basis.
I've had plenty of phones the last few years: 9090, 9100, Tytn and now Tytn II - all of which have been flashed - successfully I might add - with software and aid from you guys. (Ok, so my Tytn nearly ended up as a paperweight, but with some fancy maneuvers using the CE SDK from Microsoft I was able to use it as a PDA again)
Now, I am stuck. Really stuck. (Not saying I'm not to blame, but I am still stuck)
I've got a Tytn II (The P4550 HTC Kaiser 120 I believe). A few weeks back I flashed this with Alex's Home ROM (http://wiki.xda-developers.com/index.php?pagename=Alex's ROMs). At the time I was running Radio 1.27.12.11, and continued to use it after the Alex flash.
That worked perfectly.
But being interested in always trying new stuff I yesterday decided to flash Alex.v5.WM61.HTC.302.UltraClean.ROM.beta2. And it really went bad.
I studied up on many postings (obviously not enough) and started the process:
#1: Hooked up the pda to my computer
#2: HardSPL v1
#3: Tri-Color mode and activesync grey
#4: Started the upgrade with KaiserCustomRUU.exe
Everything went smoothly until it hit 99% - there it stuck and the program ended with a communication error. My computer runs Vista (yes, I know. I wont even consider flashing another phone using Vista), but it has worked flawlessly 25-30 times before.
Anyways, what happened when I tried to recover was that the phone went into tri-color mode. Needless to say it was unable to recover. After much back and forth I reinstalled an old laptop with XP (as mtty does not work on Vista) and was able to boot it back in to the OS using a walk trough from this site - cudos to Laurentius26 for the post)
Anyways - it came back. But since it failed the flash I tried it again to make sure it finished properly. What I did was flash back the Alex Home ROM I had in the first place - that worked. Then I flashed back the 1.27.12.11 Radio ROM - which failed - seriously.
It hung on 17% and when reset it would only boot to tri-color. And this is where I am now.
Every time the phone resets it boots to tri-color. I've done and redone the mtty (with and without the task 28), but it stops in tri-color mode. If I at that point hook it up to mtty and issue the boot command it will boot properly, but thats kinda annoying - having to carry with me a XP laptop for each time I have to reset the phone. (Ive also tried the set 14 0 when the phone is in this state, but it will still only boot to tri-color)
So - what now?
I've tried flashing the RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship, but it stops with 294 - invalid vendor id. I've tried flashing the same ROM with HardSPL installed - no vender id error but it fails at 16%.
In desperation I've tried HTC_Kaiser_NL_ROM_1.56.404.6_Radio_22.45.88.07_1.27.12.17_Ship, but this also fails at 16%.
I've studied many a post on this site, but have so far been unable to recover from this error.
Is there any hope of regain the much needed functionality of normal booting?
Hopefully there is.
Thanks in advance.
Can you try these?
http://forum.xda-developers.com/showthread.php?t=371154
New commands for MTTY.
Regards,
Leo
Laurentius26 said:
Can you try these?
http://forum.xda-developers.com/showthread.php?t=371154
New commands for MTTY.
Regards,
Leo
Click to expand...
Click to collapse
Most definetly.
These were also posted by e-men in another topic this morning so I am currently installing Windows XP on a computer at work to try this.
Will report back.
Laurentius26 said:
Can you try these?
http://forum.xda-developers.com/showthread.php?t=371154
New commands for MTTY.
Regards,
Leo
Click to expand...
Click to collapse
Woohoo!!!
XDA wins again.
The proper commands for the mtty worked like a charm.
Thank you kindly Leo, this was much appreciated.
Now for a question if you have the time: Since I started this process yesterday I have not been able to flash a Radio rom properly. It stops on 17% or 99% and quits with communication error. Any ideas?
And can I trust that my phone now works?
Cool...., thank you
Would you like to give this a try as well maybe?
http://forum.xda-developers.com/showthread.php?t=366014
I never tried to flash a seperate radio ROM, I'm a 'chief de cuisine' so I cook it in
Cheers,
ulfthomas said:
Woohoo!!!
XDA wins again.
The proper commands for the mtty worked like a charm.
Thank you kindly Leo, this was much appreciated.
Now for a question if you have the time: Since I started this process yesterday I have not been able to flash a Radio rom properly. It stops on 17% or 99% and quits with communication error. Any ideas?
And can I trust that my phone now works?
Click to expand...
Click to collapse
WM6.0 and WM6.1 radio's are different, they are not compatible!
So be carefull which radio version you are flashing
Info about radio versions:
http://forum.xda-developers.com/showthread.php?t=349375
Cheers,
Laurentius26 said:
Cool...., thank you
Would you like to give this a try as well maybe?
http://forum.xda-developers.com/showthread.php?t=366014
I never tried to flash a seperate radio ROM, I'm a 'chief de cuisine' so I cook it in
Cheers,
Click to expand...
Click to collapse
But of course - now that I know how to reset.
One comment: I absolutely love the Palm SMS program added by Alex in his rom. You know if this is manually installable?
This is threaded SMS isn't?
That's default in WM6.1.
But if it's a seperate program there must be a cab out there.
I will have a look if it's that good you say!
Cheers,
Leo
ulfthomas said:
But of course - now that I know how to reset.
One comment: I absolutely love the Palm SMS program added by Alex in his rom. You know if this is manually installable?
Click to expand...
Click to collapse
Laurentius26 said:
This is threaded SMS isn't?
That's default in WM6.1.
But if it's a seperate program there must be a cab out there.
I will have a look if it's that good you say!
Cheers,
Leo
Click to expand...
Click to collapse
Well, good is subjective ... but I love it.
As for the updating: halted on 16% - communication error.
*Looks around - "Where's my mtty"
How can I get pass these updating issues?
Which OS do you have on your desktop?
Do you have an original branded HTC device?
Try to flash a factory (shipped, not cooked) rom first!
Don't use a usb hub between your device and the pc, but use a straight connection.
See if there are applications running on your desktop.
Disable your Firewall for example...
And please take your storage card out.
Some tips....
ulfthomas said:
Well, good is subjective ... but I love it.
As for the updating: halted on 16% - communication error.
*Looks around - "Where's my mtty"
How can I get pass these updating issues?
Click to expand...
Click to collapse
Laurentius26 said:
Which OS do you have on your desktop?
Do you have an original branded HTC device?
Try to flash a factory (shipped, not cooked) rom first!
Don't use a usb hub between your device and the pc, but use a straight connection.
And please take your storage card out.
Some tips....
Click to expand...
Click to collapse
And all good tips Leo.
OS: Windows XP SP2. Freshly installed. Only Activesync 4.5 added.
HTC: Is orignial. Patched a few times using HardSPL
Original rom: As mentioned above I've tried a couple of them, but both ending in invalid vender id.
And no usb hub present.
Another comment - the flashing done today and yesterday has been done from two different xp computers - but with same result.
Laurentius26 said:
Which OS do you have on your desktop?
Do you have an original branded HTC device?
Try to flash a factory (shipped, not cooked) rom first!
Don't use a usb hub between your device and the pc, but use a straight connection.
See if there are applications running on your desktop.
Disable your Firewall for example...
And please take your storage card out.
Some tips....
Click to expand...
Click to collapse
hehe... really? Remove my beloved SD card? Of course - always do.
No need for firewall as there are no nic's. And also no applications.
I'm going to upload a shipped ROM for you, this one if you didn't try it yet?
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship
Another question... did you use Custom RUU with ROM update?
http://forum.xda-developers.com/showthread.php?t=334890
ulfthomas said:
hehe... really? Remove my beloved SD card? Of course - always do.
No need for firewall as there are no nic's. And also no applications.
Click to expand...
Click to collapse
Yup - that one has been tested - fails with invalid vender id.
Also tried flashing that rom with HardSPL - comm. error.
And no, I have not tried the Custom RUU. Will for sure try that now.
The Custom RUU is the same file that is included with your 6.1 Rom isn't it? If so I have used it with your ROM.
Do you think I should try it with another?
Yes... try with another shipped ROM please?
ulfthomas said:
The Custom RUU is the same file that is included with your 6.1 Rom isn't it? If so I have used it with your ROM.
Do you think I should try it with another?
Click to expand...
Click to collapse
Tried custom ruu with Radio 1.27.12.17.
Same results as other flashes - halts at 95%.
Seems like OS flashing hangs at 17% and Radio at 95%.
Use one more time MTTY, clear all FATS and I've send you a PM.
ulfthomas said:
Tried custom ruu with Radio 1.27.12.17.
Same results as other flashes - halts at 95%.
Seems like OS flashing hangs at 17% and Radio at 95%.
Click to expand...
Click to collapse
If you're getting an invalid vendor id it sounds like your hardspl or superCID isn't working correctly. Before going any further it's probably best to go to your bootloader screen and check that hardspl is still installed.
After that, I'd try flashing from the SD card.
Good point ach2, but when launching HardSPL and starting the update it lists the correct data on the bootscreen (Jumpspl or something equivavlent to that)
Leo: Looking around xda I found an article about dumping the ROM from another device. In the same thread I found a link to dumped original ROM. I patched that and it worked like a charm.
My PDA came back to its original state.
After arriving home just now I thought I would give your ROM another go, but same result - stuck at 16% (With HardSPL and Custom RUU)
What can cause this?
EDIT: The task 2a brick issue has been solved. This does not mean you can do anything via MTTY & be safe. There are still other ways to brick your device with MTTY, so still always be smart & be careful!
All you Noobies thata are stuck in bootloader or playing with MTTY or [email protected] commands PAY ATTENTION!!!!
This is not a big deal for me because I have a never ending supply of HTC Devices. However, for the noobie & the person that pays full retail for their device this is VERY IMPORTANT INFORMATION!
Understand that MTTY is not a toy & neither is your device. Some very low level flushing & programing can be done with MTTY. If you enter the incorrect information, you may very well end up with an $800.00 paper weight on your desk.
Many of you came from the Hermes Device. Many will remember that with the Hermes & MFG SPL if you had bad blocks of memory you could erase those bad blocks using the MTTY command cmd>task 2a.
However, with HardSPL (all versions including w/ [email protected] command) the command task 2a doesn't just erase the bad blocks, It will COMPLETELY reformat your device, the ROM, RAM & NAND storage, totally wiping out the Windows CE.
In other terms, if you play around with [email protected] commands or MTTY task commands, there is a very high risk of wiping your device completely & restoring CE without having an amazing amount of software & knowledge is next to immposible.
DO NOT PLAY AROUND WITH MTTY IF YOUR DEVICE IS STUCK IN BOOT LOADER! Also, know that every SPL version CAN have different commands. If you are stuck in BL, stick to the known instructions, or ask somebody for guidance.
MTTY is a very powerful & often misunderstood tool. Use it wisely.
I just want to confirm that as it's exactly how I bricked my kaiser.
what does mtty stands for?
Hey MODS????
Lets get this into a stickie or something. With all the stuck in boot loader issues, with all the noobies & with all of them asking for or downloading MTTY the board will be an explosion of my device is bricked comments.
Can someone cross post this to the wiki as well?
Thanx Bro for the info.
I've added it to the wiki under the MTTY thread by Laurentis with some strong verbiage...
Can't add it to the sticky because there are 10,000 characters in the first post already, plus, most folks don't even know what MTTY is (nor is Laurentis' thread stickied), so it shouldn't be too much of a issue...
Hope this helps!
Please explain
I 've got stucked in 3 color screen with any new FlashingROM in my Kaiser. Than i install HardSPL and the problem persists.
I'm in tri-color screen with SPL OliPof on the upper left corner.
KAIS130
SPL-1.0.OliPof
CPLD-8
I'm with the original factory ROM.
I can't sync my pda
If I use the MTTY i will brick my phone?
I should install another RadioROM and WM6.1 ROM?
How could I stablish comunication with PC?
Please help
Thanks
GSLEON3 said:
Lets get this into a stickie or something. With all the stuck in boot loader issues, with all the noobies & with all of them asking for or downloading MTTY the board will be an explosion of my device is bricked comments.
Can someone cross post this to the wiki as well?
Click to expand...
Click to collapse
What a great idea!!
I believe ALex already crossed this to the wiki.
I've made great progress understanding SPL & MTTY commands. The problem lies in doing things out of fear. Task 2a is not a command that should be generally used unless you have an unlocked device. Using it however, can be an important step in some cases, but you need to be precise in the execution of steps immediately after a task 2a command.
I am documenting all the current SPL versions & commands that are not only posisble, but also the ones that are helpful in recovery. I you do not know what you are doing, I suggest you contact me as I am documenting various issue, spl versions, & solutions for an upcomming post.
Thx!
Thanks
GSLEON3 said:
I believe ALex already crossed this to the wiki.
I've made great progress understanding SPL & MTTY commands. The problem lies in doing things out of fear. Task 2a is not a command that should be generally used unless you have an unlocked device. Using it however, can be an important step in some cases, but you need to be precise in the execution of steps immediately after a task 2a command.
I am documenting all the current SPL versions & commands that are not only posisble, but also the ones that are helpful in recovery. I you do not know what you are doing, I suggest you contact me as I am documenting various issue, spl versions, & solutions for an upcomming post.
Thx!
Click to expand...
Click to collapse
I'm sorry to be a nobie without practice. I've been searching wiki and xda about one week and no solution to my specific problem. I understand the procedure with MTTY but there is so many details and i don't want brick my phone.
I'm trying to contact you just like i'm going nuts with my pda.
I send you MSN contact and waiting your reply.
I have a kaiser bought in miami, factory unlocked, running windows mobile original ROM with HardSPL installed.
Stuck in bootloader tri-color screen as described above.No PC sync!
Solution=reward
I'm wondering, after erasing everything. isn't it possible to still flash ROM , etc.?
unless u're saying the command erase BL too.
GSLEON3 said:
I am documenting all the current SPL versions & commands that are not only posisble, but also the ones that are helpful in recovery. I you do not know what you are doing, I suggest you contact me as I am documenting various issue, spl versions, & solutions for an upcomming post.
Click to expand...
Click to collapse
Looking forward to that post, it should make for some interesting reading.
omega_ said:
I'm wondering, after erasing everything. isn't it possible to still flash ROM , etc.?
unless u're saying the command erase BL too.
Click to expand...
Click to collapse
YES & NOOOO!!! The task 2a completely formats NAND storage where SPL resides. So if you have an issues or reset BEFORE flashing a new SPL, you are done for (toast) unless your device is security unlocked.
GSLEON3 said:
YES & NOOOO!!! The task 2a completely formats NAND storage where SPL resides. So if you have an issues or reset BEFORE flashing a new SPL, you are done for (toast) unless your device is security unlocked.
Click to expand...
Click to collapse
Ok lets go with the fact that I bricked my device with the task 2a command (ok, I bought myself a new TyTN II the next day but still have the bricked one).
If HTC ever comes out with a ROM upgrade with the right CID, would it flash?
Tnx for the answer!
@ GSLEON3
I just wanted to say thank you for everything you do in recovering peoples bricks. Your worth is incalculable. Nice work. Nice work indeed.
yea, i think what you do is pretty amazing, the fact that you havent killed a newbie who bricked his phone is just unbelievable
and that's one badass tilt you have there.......a truly battle tested tilt
GSLEON3 said:
...I have a never ending supply of HTC Devices...
Click to expand...
Click to collapse
Care to share the wealth?
XtreMe_G said:
yea, i think what you do is pretty amazing, the fact that you havent killed a newbie who bricked his phone is just unbelievable
and that's one badass tilt you have there.......a truly battle tested tilt
Click to expand...
Click to collapse
Never killed one, but I've said "Go pound sand" to one once. He was a complete ARSE though & was annoying as hell.
Now if I was only smart enough to build a package around the way I've found to change the page pool I'd be good. So far you can only do it with Platform Builder though.
Lukstra said:
Ok lets go with the fact that I bricked my device with the task 2a command (ok, I bought myself a new TyTN II the next day but still have the bricked one).
If HTC ever comes out with a ROM upgrade with the right CID, would it flash?
Tnx for the answer!
Click to expand...
Click to collapse
did you get an answer on this?
YES!!!
Task 2a Bricks can now be fixed. However the CID has nothing to do with it. Task 2a completely formats everything except parts of the radio. This leave OEMSBL & depending on the radio you last had, it can now be fixed.
so, I had some people contact me about the above problem. apparently some kaisers have this for some reason: they for no reason enter bootloader screen and won't boot OS.
the usual mtty commands ("set 16 0", "set 14 0") do not seem to help, and the whole thing is intermittent, sometimes you can still get the OS to boot. (NickCollision mentioned shorting the battery terminals after removing the battery helps for a while)
I patched the 3.29.Hard HardSPL (and the 3.56 too) to remove all enterbootloader reasons other than the usual stuff, keyboard combination and ruunbh tag.
both 3.29 and 3.56 will now say .Hard2 where the 2 means it is patched version =) so it will be less confusing to users.
UPDATE: you can try using force-usb SPL versions now, see new attachments!
UPDATE2: you can try 1.0.olipof-nostuckinspl-force-usb version and 3.31 hardspl (new hardspl, asked for by some users, of course with all these features)
3.29 is still very strongly recommended over 3.56, unless you have OS freezing issues with 3.29.
download from attachment and flash with SSPL to fix problem if you can get the OS booting at least once. also strongly recommended to flash this for prevention even if you have no problems yet!
what to do if you are still stuck in SPL - in that case, the spl overwrite protection will not let you flash. you should try to get the OS booting at least once. try with USB in, or after battery removal-reinsertion, those help increase chances.
if that doesn't work out, then see below what to do in that case:
the kaisdiagtest1.zip or the kaisdiagSD.zip in attachments may help solving the problem of reflashing the SPL to the patched version, if you absolutely can't get the OS to boot at least once.
the one of these allows you to reflash SPL via USB connection, the other one allows you to reflash from microSD card. this SD one is strongly recommended especially if you have problems with USB connection in SPL. it is also much more automatic.
usage STEP BY STEP (only if you cannot get the OS to boot not even one time!).
for diag and flash via microSD:
1. format a microSD to fat32 (use a card reader on a PC), copy the image to it from the KAISDIAGSD.zip in attachment (extracted filename KAISDIAG.NBH). this is basically an SSPL patched to load from SD without booting OS and then it will autoflash my hardspl again from SD.
2. put one of my hardspl's on the card too (in attachment, 3.29.Hard2 or 3.56.Hard2, 3.29 recommended). name this file as KAISIMG.NBH!!!
3. insert the microSD in the kaiser, then reset kaiser.
4. it should say Loading / Update in progress then reboot to a screen saying SPL 1.00.OliNex.
5. it should now flash in the KAISIMG.NBH. and will reset.
6. at this point it should boot to the OS, if it doesn't, then flash an OS. (of course delete the previous KAISDIAG.NBH and KAISIMG.NBH from the sd card and remove sd unless you opt to flash the OS from sd too)
for diag and flash via USB:
1. format a microSD to fat32 (use a card reader on a PC), copy the image to it from the kaisdiagtest1.zip (extracted filename KAISDIAG.NBH). this is basically an SSPL patched to load from SD without booting OS.
2. insert the microSD in the kaiser, then reset kaiser.
3. it should say Loading / Update in progress then reboot to a screen saying SPL 1.00.OliNex.
4. it should then work with RUU over USB (has USB force patch). but test with mtty first, make sure to disable usb connection in Activesync/WMDC! if PC doesn't see the device, try a USB replug. also, the USB should be plugged in all the time (except for when you replug)!
5. if it seems to have a good connection, then please now flash one of the SPL's posted in this post. after that you will be able to boot OS (of course reflash OS if you need to but the *first* flash *must be* SPL).
6. if this doesn't work (i.e. USB connection won't go), then go and check the SD version of the diag image, if you haven't already.
Wow Great work.
Thank you very much for your hard work! Going to sticky this for the time being.
Damnn,m nice work.
Thanks for this.
I have added it to my Wiki page on what to do if you get stuck at the bootloader. (Kaiser_Stuck_at_bootloader).
Anything you spot wrong with it feel free to modify (I asked GSLEON to take a look, but I don't know if he's had time).
Thanks
Dave
I can tell you that it does work and it did fix my kaiser!
Great work!
Nice!
I don't use the SPL, other than the one that came with my phone.
(Warranty....don't want to take a chance). Come October, when the warranty expires, I'll probably start flashing some of the cooked ones, plus, the Raphael
will probably be around by then.
I love you cmonex, let me know if you broke up with olipro
whats your thoughts on using the different SPL's to fix the random freezing issues that seem to hit the kaiser? I know my phone seems to work best with the newest SPL thats out right now from Jocky but it all could be in my head!
----Thank you cmonex, once again you show that your one of the amazing forces behind Xda! I hope there are little girls out there that want to be just like you when they grow up! That would be so cool a bunch of mini cmonex's running around we would have no issues with are WM devices then!
sakajati said:
I love you cmonex, let me know if you broke up with olipro
Click to expand...
Click to collapse
lol, sorry, no chance
austinsnyc said:
whats your thoughts on using the different SPL's to fix the random freezing issues that seem to hit the kaiser? I know my phone seems to work best with the newest SPL thats out right now from Jocky but it all could be in my head!
Click to expand...
Click to collapse
most probably that was because the older SPL's formatted nand too aggressively, so the end of the OS might get erased, which is no good. wasn't a problem before but the new OS's are bigger, so it affects them more likely.
as for the SPL versions, I don't really recommend 3.56 SPL, 3.29 seems much better in terms of available commands (though neither has task 2a for frankenkaiser fun ). did someone have any good experience with the 3.56 over 3.29? - I wonder why it is an option.
cmonex can u post the patch for the 3.56 it would be greatly appreciated, thanx
Get a new battery. The reason for this problem is the power manager keeps reseting the watchdog timer. Depending on when that happens the unit will either constantly reboot or enter bootload.
For some reason the BatSense line goes high and stays high. I haven't dissected the battery yet, but replacing it solved the problem.
htcfan2008 said:
For some reason the BatSense line goes high and stays high. I haven't dissected the battery yet, but replacing it solved the problem.
Click to expand...
Click to collapse
Not discounting the theory, just wanted to say that I had swapped out battery's during my testing with cmonex. So two diff battery's, same problem? Unlikely. As cmonex indicated shorting the terminals did have a positive effect, so you may be on to somthing re: the batsense line. Just that swapping batteries had no effect in my experience.
oOoOo my batsense is tingling hehe
Where the two batteries...
Nick Collision said:
Not discounting the theory, just wanted to say that I had swapped out battery's during my testing with cmonex. So two diff battery's, same problem? Unlikely.
Click to expand...
Click to collapse
...Samsung brand made in China, and both more than six month old? Then quite possibly they're both bad. (I forgot to mention in my other post that I replaced the battery with a non-HTC brand.) One way to tell is look at the battery edge on: if it has a bulge in the middle or looks "swollen" all around then it surely is bad.
I have found that using a non-HTC car or wall charger almost always and rather quickly kills the battery. It's not the charger voltage but the charging current profile that's the problem.
Anyway, good luck.
the bootloader can enter tricolour screen for a couple reasons other than the usual key combination or nbhload / enterbootloader tags in flash:
- if CPLD function returns 0xF
- or if debugboard is detected for whatever reason
- other configdata in flash tells it to do so
the last one can be excluded, because the problem is intermittent, and flash contents should be permanent.
then, I had Nick Collision run info 7 (which calls the same function), and it doesn't return 0xF, so maybe the second one.
I don't know what would cause that though, this battsense line sounds interesting.
to ofcourseimnaked: OK, i will do that soon.
Don't have a Kaiser SPL handy, but it must be using the same boot tags as Trin/Herm.
ClrRUUTagGoToOS
ClearGotoULTag
DeviceWarmBoot
CELoadComplete
NbhLoadSuccess
EnterBootloader
GoUpdateLoader
DeviceColdBoot
SetRuuNbhUpdate
These tags are programmed into flash to force boot in required mode.
Is this the config data you are referring to?
One other thing...
SPL and OS kernel debug log is stored in flash too, the reason for soft reset may be found in the log? It should be possible to dump the log with procdump once device boots to OS.
Don't know the offset for Kaiser Should be in the next block after the block with CID and boot tags though.
stepw said:
Don't have a Kaiser SPL handy, but it must be using the same boot tags as Trin/Herm.
ClrRUUTagGoToOS
ClearGotoULTag
DeviceWarmBoot
CELoadComplete
NbhLoadSuccess
EnterBootloader
GoUpdateLoader
DeviceColdBoot
SetRuuNbhUpdate
These tags are programmed into flash to force boot in required mode.
Is this the config data you are referring to?
Click to expand...
Click to collapse
yes, those mainly, and some flags.
but the issue is not them.
stepw said:
One other thing...
SPL and OS kernel debug log is stored in flash too, the reason for soft reset may be found in the log? It should be possible to dump the log with procdump once device boots to OS.
Don't know the offset for Kaiser Should be in the next block after the block with CID and boot tags though.
Click to expand...
Click to collapse
you mean task 37? btw, reset wasn't an issue here, but if someone shows up with a device constantly rebooting, we can look into that too..
note, CID is not really accessible directly from SPL anymore, MSM7xxx. (though right now I'm having fun finally dumping the protected radio nand)
Please explain me what it exacly is.
Is it better, most recent and fixed for Bootloader mode stuck version of HardSPL 3.29 which we can found on 'jockyw2001' thread?
Is it still HardSPL which let me flash any ROM for HTC Kaiser?
Thanks for all explains. Best regards.
Anyone want to make this for the polaris as it would be very useful for cooks, and flashers. Also MTTY under 7 is less than can be desired.
Some info, http://forum.xda-developers.com/showthread.php?t=644781.
It says that you have to hex edit the RUU to get it to task 29 instead of 28 (i think)
So someone please take it!
chris10230 said:
Anyone want to make this for the polaris as it would be very useful for cooks, and flashers. Also MTTY under 7 is less than can be desired.
Some info, http://forum.xda-developers.com/showthread.php?t=644781.
It says that you have to hex edit the RUU to get it to task 29 instead of 28 (i think)
So someone please take it!
Click to expand...
Click to collapse
It shouldn't be that difficult!
RUU is done.
Just give me a dummy .nbh file and I will make a single exe ROM wiper for you
yep saw that, was trying to get the one off of the LEO thread, will have a go this evening, will PM you when I've got it. Didnt want to run, you could always extract it yourself i think... http://forum.xda-developers.com/showpost.php?p=5848003&postcount=19 if you get the time before i send it.
Cheers, once again for this.
I received a PM from chris10230 with a dummy .nbh file but replying here for others to be able to comment.
As I have understood a dummy .nbh file comes from the Leo (HD2). I am not too good in technical aspects of .nbh files so I have a doubt: as the dummy file is about 5 megabytes it still flashes something to the device. If this something is flashed into the ROM area - no problem, as it will be erased straight after flashing. But if it flashes something beyond the ROM area and this something is Leo-specific, is it safe to flash it?
Maybe some pro's can provide more information on this. As soon as I will be sure that this file is safe for our device I'll make a ROM wiper.
leppa said:
I received a PM from chris10230 with a dummy .nbh file but replying here for others to be able to comment.
As I have understood a dummy .nbh file comes from the Leo (HD2). I am not too good in technical aspects of .nbh files so I have a doubt: as the dummy file is about 5 megabytes it still flashes something to the device. If this something is flashed into the ROM area - no problem, as it will be erased straight after flashing. But if it flashes something beyond the ROM area and this something is Leo-specific, is it safe to flash it?
Maybe some pro's can provide more information on this. As soon as I will be sure that this file is safe for our device I'll make a ROM wiper.
Click to expand...
Click to collapse
Yeh very good point don't use it! Maybe you could ask a cook to create a blank nbh?
long days, not thinking straight. Good thing that someone else is looking at this apart from me
chris10230 said:
Yeh very good point don't use it!
Click to expand...
Click to collapse
Maybe it is still usable. We just need someone to be able to tell where it writes to
By the way, a boot/splash screen shouldn't be too big. I think I can create an .nbh with the default (smart mobility) screen to be flashed. There was a tool for it somewhere in this forums. Just need some free time to find it and make an .nbh...
Or maybe someone already has an .nbh with it?
try this for making splash screens .nbh http://forum.xda-developers.com/showthread.php?t=334907
Splash
Original "Smart Mobility" splash, tested.
I think may use it as dummy nbh, because it be written to phone < 1sec.
I run MTTY for " task 29 " and i trie leppa RUU with task 29 and all was ok...
But i got one problem, after task 29 i trie to flash last ROM of Kostas244 and also last ROM of Pcarvalho and the phone don't boot... But also trie the ROM of cruiserrr (naked version) and the phone did boot up...
I run task 29 before flash each of 3 ROM's... there some trick I missed?
For i can boot the phone with the new Kostas244 ROM i had to flash first Original ROM from HTC and then flash Kostas244... was the only way...
Some advice?
flash after task 29 from bootloader screen
sbettencourt said:
I run MTTY for " task 29 " and i trie leppa RUU with task 29 and all was ok...
But i got one problem, after task 29 i trie to flash last ROM of Kostas244 and also last ROM of Pcarvalho and the phone don't boot... But also trie the ROM of cruiserrr (naked version) and the phone did boot up...
I run task 29 before flash each of 3 ROM's... there some trick I missed?
For i can boot the phone with the new Kostas244 ROM i had to flash first Original ROM from HTC and then flash Kostas244... was the only way...
Some advice?
Click to expand...
Click to collapse
As Task 29 wipes out all from the phone it will be too thumb to boot, so you have to put polaris to bootloader mode (hold cam & power button while resetting to see tri-color boot screen) before you can flash as I understood in the above threads - unfortunately untested. this thread was few hours late. Please report
@ leppa good thing to start this thread. I tried on my own rigth after last pcar release. Maybe it is also a good move to provide the appropriate radio with this task 29 RUU. Could save the cooks a lot of maintenance posts.
So the final procedure would look like this
1. flash Task 29 RUU with appropriate radio (up to cooks recommendation)
2. Hard Reset
3. flash new ROM
in general a very usable thing to make things easier thanks
sqeeza said:
As Task 29 wipes out all from the phone it will be too thumb to boot, so you have to put polaris to bootloader mode (hold cam & power button while resetting to see tri-color boot screen) before you can flash as I understood in the above threads - unfortunately untested. this thread was few hours late. Please report
Click to expand...
Click to collapse
Thank's for the answer sqeeza, but you didn't tell anything new What i say is with the ROM from cruiserrr, the phone boot up ok... But with kostas244 and Pcarvalho ROM's the phone didn't boot... and yes of course i put first in bootloader mode and then flashed the ROM's...
I don't know why the ROM from cruiserrr boot ok and the others didn't...
Edit:
My phone don't boot anymore the kostas244 ROM... at least the last one... sh*t... Can anyone tell me why?
sbettencourt said:
Thank's for the answer sqeeza, but you didn't tell anything new What i say is with the ROM from cruiserrr, the phone boot up ok... But with kostas244 and Pcarvalho ROM's the phone didn't boot... and yes of course i put first in bootloader mode and then flashed the ROM's...
I don't know why the ROM from cruiserrr boot ok and the others didn't...
Click to expand...
Click to collapse
Sorry sbettencourt, this is then beyond my horizon.
Did not read attentively enough. I would have had an explaination for the original HTC ROM since they usually write all parts of the ROM (radio, sys, etc. ) at once. So I assume task 29 wipes something that cruiserr writes with his ROM while the other cooks don't. So it would be up to one cook to understand/ answer this part. Maybe cruiserr can help here.
Thank you for reporting
No problem sqeeza is good to have some answers... maybe someone can tell how to resolve this... the previous version of Kostas244 the phone booted but i download the new one and erase the previous... big mistake... i couldn't guess this too...
at least the Original ROM boot's fine not a cool ROM but work's... i already miss wm6.5
_____________Edit:
already flash again the cruiserrr ROM and the phone booted normal... it's strange...at least for me... the only difference i can see and i don't know if this matter, is, with the Cruiser ROM the splashcreen changes like with Original ROM, but with Kostas244 and Pcarvalho ROM's the splashscreen don't change... Can this make the difference?????
Ok... and now, my POLARIS is dead... No lights no nothing.
sorry to hear that, you say in your signature, dead by task 2a... That is mentioned many times that it will brick a polaris. Still sorry that you got caught by it.
sbettencourt said:
Thank's for the answer sqeeza, but you didn't tell anything new What i say is with the ROM from cruiserrr, the phone boot up ok... But with kostas244 and Pcarvalho ROM's the phone didn't boot... and yes of course i put first in bootloader mode and then flashed the ROM's...
I don't know why the ROM from cruiserrr boot ok and the others didn't...
Edit:
My phone don't boot anymore the kostas244 ROM... at least the last one... sh*t... Can anyone tell me why?
Click to expand...
Click to collapse
probably cause the rom only has the OS, its missing radio and splash...but this is just me guessing dont know what cruiserrr has...mine only has OS part so people can choose their own radio/splash...thats why i advice people to flash original 1st...takes longer and all but is flawless...be very careful with task commands...
hope you can revive your device
cheers
Yep...but never notice that HardSPL + Task 2a could wipe everything... Now i can´t forget that...loool... Was wrong but a god lesson!!!
Now my P3650 goes like a trojan to HTC for repair... lets see... maybe in 1 month i have him back and fine
At least, maybe my case can alert again who dangerous can be doing Task 2a...
sbettencourt said:
Yep...but never notice that HardSPL + Task 2a could wipe everything... Now i can´t forget that...loool... Was wrong but a god lesson!!!
Now my P3650 goes like a trojan to HTC for repair... lets see... maybe in 1 month i have him back and fine
At least, maybe my case can alert again who dangerous can be doing Task 2a...
Click to expand...
Click to collapse
As I have understood task 2a wipes ALL phone memory, including Splash, Radio and even Bootloader?
meknb said:
try this for making splash screens .nbh http://forum.xda-developers.com/showthread.php?t=334907
Click to expand...
Click to collapse
DmK75 said:
Original "Smart Mobility" splash, tested.
I think may use it as dummy nbh, because it be written to phone < 1sec.
Click to expand...
Click to collapse
Thanks for the links, guys.
Unfortunately, I've had electricity off several times yesterday and no Internet access. As I work from home, I have a lot of work to do now. Will make a wiper closer to the end of this week, I think.
Whenever leppa
Also yeh i think it does litterally wipe EVERYTHING off the phone... Still sorry that it happened to you sbettencourt, feel for you and a the phone (R.I.P. till repair that is )...