Database Info

*WARNING!!! HardSPL + MTTY = BRICK [+ or - Solved]

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.

Noobie Hard spl question

NOt sure if this is in the right topic, but its slightly rom related.
Can someone please help a noob
I cid unlocked my phone following the topic
http://forum.xda-developers.com/showthread.php?t=375583.
all worked well, tried a couple of roms and settled on
L26 WM 6.1 Professional WWE V6a (MMS and JAVA updated) rom, seems to be working ok, certainly all my apps work.
However like a typical noob I missed out on some important reading about hard spl and how it can protect my phone from a bad flash.
Now that I've done all of the above, is it too late to go back and protect my phone with hard spl?
SPL -1.0. Olipof
thanks in advance

I think that's done automatically when you flash hard spl.
(someone correct me if i'm wrong please)

step one in that unlocker would have flashed hardspl on your device, if u skipped it then no, its not too late, you can still do it now

XtreMe_G said:
step one in that unlocker would have flashed hardspl on your device, if u skipped it then no, its not too late, you can still do it now
Click to expand...
Click to collapse
No i didnt skip step one, so I guess I'm covered.
Guys thanks for the help, much appreciated!

Just go into bootloader mode (power button + camera button + reset). If the screen shows SPL-1.0.OliPof then you are ok. If not then just reflash hardSPL.

SPL-1.0.OliPof is there in bootloader.
thanks for the help guys.!

O2 Stellar will not flash or boot, tried everything!

Ok, so rapid short overview:
I tried to flash my O2 Stellar with the new HTC wm6.1 Kaiser ROM. The HTC website, for reasons unbeknowest to me would only give me the italian ROM, so I got the english variant off rapidshare.
Tried to flash, everything going well, until (at 0%) it turns around and says the ROM isn't compatible. I figure this requires some HardSPL goodness, but the installer for THAT jumps to 100% in seconds and doesn't seem to do much. Tried a soft SPL (SSPL-KAIS.. no white screen issue), hey-ho, presto! ROM tries to install.
...hangs at 15%, device reboots to the rainbow. Displays:
KAIS130
SPL-1.82.0000
CPLD-8
In the corner: RUUNBH
I've read ALL the other threads on this issue to try and restore the phone. I've tried ALL the O2 ROM dumps people have supplied (all two of them I could find) and every time it either had an error 262 (comms error) at 0%, or got as far as 1% or maybe 2% and then error 29-something (ROM not compatible/suitable for phone). O2 originals, cooked ROMs, HTC updated ROMs, ROMs for different vendors (those produced "wrong vendor" errors). NOTHING IS WORKING!! *tears out hair*
Apparently connecting with mtty and typing "boot" causes the device to try booting the original rom before the flash. I figure maybe I could boot it, copy the phone's OWN rom (c'mon, THAT rom would HAVE to work, right?!) and reflash it. So I fire up mtty, tell it to boot. But it doesn't. Instead, the screen sort of.. fades, between the SPL and pure white (looks almost like display is broken!) and mtty displays:
...OH. Ok, just tried again to copy mtty text and now it's booting.
This is what mtty displays as the phone boots:
Cmd>boot
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
Click to expand...
Click to collapse
Ok, focus of the thread changing, does anyone know if I could dump the ROM and flash it? I'm about to find out anyway but if someone knows this is foolish please let me know
Cheers, everyone.

Not looking good for you.
Sounds like you flashed a ROM into the SPL at a guess. You shouldn't flash anything except SPL's when you are in Soft SPL's (SSPL or JumpSPL).
Try PM'ing a guy called GSLEON3. He's a mod here and for a beer or two will probably set you right.
@GSLEON3, I really should figure some of this out someday myself. That way I can help rather than just pointing users to you.
EDIT:
You have tried the stuff in here first? http://forum.xda-developers.com/showthread.php?t=371154
Ta
Dave

DaveShaw said:
Sounds like you flashed a ROM into the SPL at a guess. You shouldn't flash anything except SPL's when you are in Soft SPL's (SSPL or JumpSPL).
Click to expand...
Click to collapse
In retrospect that's exactly what I did, yeah. Luckily the boot command worked on the fourth try (as above... guess perseverance gets results) and the phone worked enough for me to retry the HardSPL install (which worked). Then I was able to flash the O2 Stellar ROM found elsewhere in this forum which allowed the phone to boot normally again. THEN I was able to flash the english HTC Kaiser 6.1 WWE ROM.
That thread linking to MTTY techniques for formatting may have come in very useful, I will remember that one!

Go and "security unlock" your device now. It makes it almost unbrickable.
There is a app called FrankenKaiser which can re-install your SPL if you decide to format it (not that you would want to under normal circumstances)
Ta
Dave

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.

[REQ] Task 29 - In a single exe

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 )...