Develop Bugs

[Error 270] 6.1 ROM Upgrade Problem. What did i do wrong?

Hi,
I think i followed all the steps, application unlock, hardspl, and then tried to do the 6.1 upgrade... unfortunately each time i do the phone goes sucessfully into bootloader, then starts the update. At 1% is gives me Error 270 - corrupted image...
Anyone know what i might be doing wrong?
Please help. I really want to get this running.
Thanks in advance.

salmon said:
Hi,
I think i followed all the steps, application unlock, hardspl, and then tried to do the 6.1 upgrade... unfortunately each time i do the phone goes sucessfully into bootloader, then starts the update. At 1% is gives me Error 270 - corrupted image...
Anyone know what i might be doing wrong?
Please help. I really want to get this running.
Thanks in advance.
Click to expand...
Click to collapse
maybe u have to download the rom again? if still the same, then i think u can try to flash it using the sd method
1. rename ruu_signed.nbh to cavaimg.nbh
2. copy to mini sd
3. go to bootloader mode (press camera+recorder+power)
4. follow instruction on screen
regards

Hey, thanks cruzzmz, unfortunately that didn't work either...
i've downloaded the file twice now, the two different variants in fact... i'll try once more... any other suggestions...?
i'll be seriously gutted if i can't get this to work...

Disappointingly, downloading for a 3rd time (from the mirror site this time) still didn't work...
Could i have done something wrong before this step?

Try Mtty as you could have bad blocks. Check Cruzzms post on the WM6.1 rom how to do it. After you finish with Mtty try the SD method.
Cheers

ibeqa said:
Try Mtty as you could have bad blocks. Check Cruzzms post on the WM6.1 rom how to do it. After you finish with Mtty try the SD method.
Cheers
Click to expand...
Click to collapse
if this is the case, try doing THIS first then flash.

Hey guys,
First, thanks a lot for the support! Really appreciate it... i've been following the instructions for mtty and it doesn't appear to be helping (although i could be doing something wrong)
when i do CMD>task 2a it doesn't appear to be doing anything... it just immediately brings up the next CMD> again
here's the output, just in case it's useful in diagnosing the issue... please let me know your thougts, i now don't seem able to boot up, it just gets stuck at the green windows screen.
>>>
Cmd>task 32
Level = FF
Cmd>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1300
Partition[2], type=0x25, start=0x2C00, total=0x1ED00
Partition[3], type=0x4, start=0x21900, total=0x1E700
CE Total Length(with sector info) = 0x442C800
CE CheckSum Length(without sector info) = 0x4320000
Cmd>task 32
Level = FF
Cmd>task 2a
Cmd>task 28
Storage format start
Write Nand Success
dwBlockToWrite = 13
Storage start block: 537
Storage Total block: 487
Total Bad Block in CE: 0
NeedToEraseBlockStart: 550
NeedToEraseBlockEnd: 1024
Storage format success

salmon said:
Cmd>task 32
Level = FF
Click to expand...
Click to collapse
FF is not super CID ...
Type(hex) 32: Checks your security level. Unpriviledged: "Level=0xFF", SuperCID: "Level=0"
Click to expand...
Click to collapse
that is why u cant flash it, pls do the hard spl and after u have done it, mtty task 32 again if u get as below, u r set to go
CMD>task 32
Level=0 (Super CID)
Click to expand...
Click to collapse

hey,
thanks. can i do the hard spl (which i thought i'd done) from bootloader, cos i can't fully boot the device up...

salmon said:
hey,
thanks. can i do the hard spl (which i thought i'd done) from bootloader, cos i can't fully boot the device up...
Click to expand...
Click to collapse
sad to say no, cos in ur case u have to unlock ur dev 1st, then do the hard SPL ... pls see the other thread on the how to
but then ..... u can always try

An advice for all of you who want to upgrade your Cavaliers to WM6.1:
Before you start flashing check your device via Mtty if it is CID unlocked (remember it shows "level ff" that means it is locked, if it shows "level 0" that means CID unlocked.
For more info regarding Mtty and the meaning of codes that are being used, please check Hermes thread or Hermes Wiki as there is a lot of info.
Cheers

cruzzmz said:
FF is not super CID ...
that is why u cant flash it, pls do the hard spl and after u have done it, mtty task 32 again if u get as below, u r set to go
Click to expand...
Click to collapse
are you sure the device must be SuperCID for task 2a to do it's thing?

Yes, good point...
Luckily there is a very happy ending to my story. Through some magic of clicking random buttons i managed to get the device to come out from the green windows 6 screen. I was then able to do the full super cid, check with mtty and then flash the rom...
What a nice surprise it's been too. Very stable so far. Only issue has been the symbols, which i see is being addressed in the other thread.
Thanks to everyone for their help. Where would we all be without xda-developers?
(bow)(bow)(bow)

jockyw2001 said:
are you sure the device must be SuperCID for task 2a to do it's thing?
Click to expand...
Click to collapse
i am not sure bot that though ...
salmon said:
Yes, good point...
Luckily there is a very happy ending to my story. Through some magic of clicking random buttons i managed to get the device to come out from the green windows 6 screen. I was then able to do the full super cid, check with mtty and then flash the rom...
What a nice surprise it's been too. Very stable so far. Only issue has been the symbols, which i see is being addressed in the other thread.
Thanks to everyone for their help. Where would we all be without xda-developers?
(bow)(bow)(bow)
Click to expand...
Click to collapse
Good 4 u then

how about HTC touch viva..??
some1 teach me how to solve the error 270....

alchemist89 said:
how about HTC touch viva..??
some1 teach me how to solve the error 270....
Click to expand...
Click to collapse
You should post on viva forums. Anyway did you do hardspl? and try PC with XP not Vista/7.
Cheers

Don't forget ...
And if your using the SD card method remember the system only supports SD cards not SDHC cards out of the box so you will need to use a 2G card or less if you are going to flash from the SD card ... (I think)

[TUT] Unbricking your Cavalier

Everything you ever needed to know about "unbricking" your Cavalier but were afraid to ask is in this guide. I've put together this little guide for those of you who either intentionally or unintentionally bricked your Cavalier. There are three methods you can use depending of the severity of the "bricking".
But, before I even get into that, if your phone is in fact working right now, I highly recommend you flash HardSPL to avoid even having to follow these steps anytime in the future. The steps and info for HardSPL and JumpSPL can be found in this thread by jockyw2001:
http://forum.xda-developers.com/showthread.php?t=398945
HardSPL basically flashes your phone with an "unlocked" security partition so all security checks are bypassed when you try to flash a cooked ROM or a ROM designed for another variation of the Cavalier such as Dopod, HTC, or Softbank. Makes life much easier when trying different ROMS or cooking and testing your own! Thanks jockyw2001!!
Ok, so onto the fun stuff... You flashed your phone and it won't boot. What do you do??
First and easiest way to try unbricking is:
Get a hold of your Shipped ROM. If your Cavalier is a Dopod, you can find these ROMS either in Dopod's site, HTC's site (with a valid serial #), or right here at XDA (ftp://xda:[email protected]/Uploads/Smartphone/Cavalier/Shipped_Complete_Updates/Dopod/)
Remove the SD card if one is inserted in the phone
Remove the battery from your phone for a few seconds. I found this step to be essential to reset the device. Put the battery back in.
While holding the camera button on the right side, press the power button. The phone will enter "bootloader" mode and you will see a tricolor bootscreen.
While in this mode, plug in your USB cable and you will hear the "ba-bing" USB sounds as the device connects
Unpack the ROM package you just downloaded and run RomUpdateUtility.exe. Follow the steps, check the appropriate boxes, and start the flash
Assuming all goes well, your phone will flash to the factory ROM and you can then troubleshoot what went wrong the first time that bricked your phone.
What if this doesn't work?? Or what if it flashes but the phone still doesn't boot. Or what if the flash stalls or fails? Don't panic!! That's the worst thing you can do. Try this next step.
The second mothod to unbricking your phone is:
You will need to download some tools. Downlload MTTY from this post and unpack it.
Remove your SD card
Use the method above to put your phone into "bootloader" mode and connect the USB cable
Go into Activesync and under File, Connections, uncheck "Allow USB Connections" and hit ok. Activesync will now show a red X in the systray icon
Now, launch MTTY and for port, select "USB" or \\.\WCEUSBSH001 (or any variation) and hit connect. Tap enter a few times to get the Cmd> prompt. If you don't get the prompt, review the steps and try again.
Next run the following commands to check for bad blocks and format you OS partition:
Code:
Cmd>task 32
(if you get Level=0 you are good to go)
Cmd>info 8
(This will give you bad block information if any)
Cmd>task 32
Cmd>task 2a
(Let this run and check for bad blocks, may take a while)
Cmd>task 28
(This will reformat your storage partition, if you get "Storage format success" you're in business)
Now flash back your shipped Cavalier ROM and you should be good
Oh no!! That didn't work!? Or it worked but the flash failed with Error 270 or another error......... Never fear!! XDA-Developers is here! This next method creates a "goldcard" which is used to SuperCID the Cavalier so that it doesn't care about what factory ROM you flash. Please have the factory (not a cooked) ROM ready to go.
The third "goldcard" an final method is a bit more intensive so follow closely:
Get a cup of coffee or tea
You will need a working Donor HTC device with a microSD slot and a microSD card that is smaller than 1GB (will be formatted) to create "goldcard" image using QMAT tools as described below
You will need QMAT. Get it from http://revskills.de/index.html.
Go to the Download link and download the latest version and unpack QMAT
Have some coffee
Use a SD card reader in your PC to access the SD card through Windows. Format the SD card with FAT32.
* Insert the SD card into the donor HTC device and connect the USB cable. If you unchecked "Allow USB Connections" in Activesync in an earlier step, make sure you recheck it so that you can establish a full USB sync connection to the HTC device.
Open QMAT and go to the "Hardware Forecsics" menu and select "Generate HTC Goldcard"
In "Select device key:" select the Cavalier
You will need the serial number fro the SD card so click the "Get SD Card Serial from WINCE Device" button
Once the Serial number appears in the box, click the "Save Goldcard Image to WINCE SD" button below
If no errors pop up and all goes well, proceed to these next steps
If you get an error or a popup saying "Goldcard for newer devices isn't implemented in newer devices", you must buy and register the software. Believe me, it's worth the small amount of $ you will spend to bring your expensive device back to life!
Now remove the SD card with the newly written Goldcard image from the Donor HTC device
Insert the SD card back into your PC using the microSD card reader adapter. Browse to the drive letter assigned to it. You will see no files on the SD card, this is normal.
(If, for some reason your PC sees the SD card as unformatted, something went wrong. Remove it and reinsert it into the Donor HTC device. The device should see the card as unformatted and ask you to format it, say yes. Now go back to the "* Insert the SD card into the donor HTC device" step above and repeat the steps)
Unpack your Dopod or other factory ROM and copy RUU_Signed.nbh to the SD card. Once it had finished copying, rename the file to CAVAIMG.nbh. Remove the SD card from the PC.
Make sure the Cavalier is off and insert the SD card
Enter bootloader mode as mentioned earlier (hold the camera button while pressing the power button)
You will see a gray screen that says "loading". It will then find the CAVAIMG.nbh file and ask if you would like to start the update process. Follow the instructions and let the phone flash.
It will take 10-15 mins but your phone should boot fine and be back in action!
QMAT is a VERY powerful tool written by viperbjk that allows for full low level manipulation of HTC and WINCE tasks. Read all about it here http://revskills.de/index.html.
Many thanks to jockyw2001 for his amazing HTC device knowledge! Also thanks to all who contributed to this post.
Hope this tutorial helps!

Reserved for updates.

Mtty for Vista :

Very good, thanks man.
If you don't mind, ask the mods to sticky this thread as it is nice tutorial. link: http://forum.xda-developers.com/showthread.php?t=276306
Cheers

Great post! Will check out QMAT though I haven't needed it yet (thankfully.)

What is the use of this?To solve the problem of bricks

pl879 said:
What is the use of this?To solve the problem of bricks
Click to expand...
Click to collapse
Yes, if your phone doesn't boot or a flash failed. This tutorial will help revive your phone.

hi,ookba
I have a idea,cooking SP-PPC 6.5 ROM for cava,Try to solve the Homescreen layout problem....
I tried, but cooking no avail

pl879 said:
hi,ookba
I have a idea,cooking SP-PPC 6.5 ROM for cava,Try to solve the Homescreen layout problem....
I tried, but cooking no avail
Click to expand...
Click to collapse
To get a "Pro" PPC SYS to boot on a SP is a lot of work. I got it to work once but majorly buggy. You have to remove any and all touchscreen drivers and apps as well. Not easy... The more I learn, the more I realize that the homescreen issue is hardware related with the way the new 21XXX core and up accesses hardware. I think that's why HTC abondoned the Cav so early. WM 6.1 19XXX is probably the best we're gonna get on t he CAV.

Need help
I have tried 2/3 methods all thats left is the gold card method but i dont have a working dash. Is there any way someone can send me the files necessary to make it without having the working dash?

garrettggf said:
I have tried 2/3 methods all thats left is the gold card method but i dont have a working dash. Is there any way someone can send me the files necessary to make it without having the working dash?
Click to expand...
Click to collapse
You don't need a dash. Any HTC or Windows Mobile device will work.

Pls give life to my device.
My device stuck at second splash screen.some times showing unexpected error

Follow the steps in this tutorial.

still not working
still not working after following tutorials

doubt about gold card image.
can i take gold card image from htc diamond and insert into cava.

jackienk said:
My device stuck at second splash screen.some times showing unexpected error
Click to expand...
Click to collapse
i already buy Qmat n folloh the 3rd methode,but my device stuck at GSM,on screen ican see that
spalsh 1: OK
spalsh 2: OK
jogpad : OK
GSM:
OS:
i wait about one hour but nothing is happen, i tried n tried again but still stuck at GSM.
please.. tell mewhat to do...
thx b 4

revangelion said:
i already buy Qmat n folloh the 3rd methode,but my device stuck at GSM,on screen ican see that
spalsh 1: OK
spalsh 2: OK
jogpad : OK
GSM:
OS:
i wait about one hour but nothing is happen, i tried n tried again but still stuck at GSM.
please.. tell mewhat to do...
thx b 4
Click to expand...
Click to collapse
Try to do method 2 first and format the storage partition.

ookba said:
Try to do method 2 first and format the storage partition.
Click to expand...
Click to collapse
Cmd>task 32
CID: Wait interpreter timeout
Level = FF
Cmd>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0x2CC(716) is BAD block !!!
Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1300
Partition[2], type=0x25, start=0x2C00, total=0x1D100
Partition[3], type=0x4, start=0x1FD00, total=0x20300
CE Total Length(with sector info) = 0x409E800
CE CheckSum Length(without sector info) = 0x3FA0000
Cmd>task 2a
Cmd>task 28
Storage format start
Write Nand Success
dwBlockToWrite = 13
Storage start block: 509
Storage Total block: 515
Total Bad Block in CE: 0
NeedToEraseBlockStart: 522
NeedToEraseBlockEnd: 1024
Storage format success
Cmd>
----------
after that,i continued with 3rd methodn this is the result:
IPL -OK
BOOTLOADER - OK
SPLAHS1 - OK
SPLASH2 - OK
JOGBAR - OK
GSM -
OS -
update under proses
----------------
i wait for about 30minutes but prosesdoes not continue,it's stuck
any help for my problem?

used every method still not working
i can use my phone now as paper weight.

jackienk said:
still not working after following tutorials
Click to expand...
Click to collapse
Give more detail. Where does it fail? What method does it fail on?

HELP! Weird diamond / problems with Memory ?

Hi,
in the past few weeks, I tried many different ROMS mostly based on WM6.5.
The Diamond rans really smoothly without any problems of stability and reliability.
But since one week, I'm having problems.
The problems begins, that the device restarts by himself e.g while I'm playing kevtris. But this restarts happends not from the beginning. So I could playing a couple of hours without problems. And suddenly, the device restarts with the initial phase of WM with calibrating touchscreen...
I assumed problems with this ROM (EnergyROM_DIAMOND_20090629_Standard), then I tried several ROMs with WM6.5 (e.g.CleanBlackBasic31). But all of them doesn't allow me suddenly, to install all my desired cab files, I had installed sucessfully in the past.
I went back to WM6.1 ROMs, where I used sucessfully in the past. But also with this ROMs (e.g. AZTOR_V11-GER-ULTIMATE), the installation of my cab files crashing after WM complete the initialization process. This happends not with the first cab file. I'm installing 3-4 files without any problems. And then while the installation of the next cab file, the installation failes. When I'm going to "Windows - Programs", all installed packages of myself having no original Icons. When I'm trying to start one of those "blank" icons, I'm starting a neverending process. I can't abourt such a start. After I'm doing a reset, the device hangs (for >15 minutes) at the initialization screen, where the ROM version will be shown. When I'm resetting again, WM starts with the initial phace of WM with calibrating of touchscreen. But this WM is not in stable condition. I have to reset to factory settings to get a running WM back.
I tried also the reset to factory settings (VolUP+EnterButton) many times, which works, but didn't solve my problems.
The radio ROM I used since ~ 3 month 1.09.25.23.
Have anybody an idea? Could this a hardware problem of the internal memory? Is there any stronger reset posibility which avoid problems of previous installation?
Best regards
luftdieb

I've been getting similar issues, programs refusing to run complaining there's no memory even when no programs are in memory.

Its just because you have flashed many roms when you flash a rom old system settings and such get left over from previous flashes, and after abit and many flashes all this info gets mixed up and corrupt, try using mitty to format your device, this will erase the portion of the memory where these settings are held, then flash a stock rom, this will install the default htc settings, then flash a rom of your choice

I had the same problem which was solved after I flashed shaks 4.30 rom. Somehow I wasn't able to flash any of the stock roms. Anyway try a stock rom or that mtty tool and everything will be fine

@ALL: Thanks for your reply. I just used the search function of the forum and found the following page about mtty
I could also get a connection to my diamond with mtty. But up to now, I didn't have the heart to do one of the following commands:
task 28: Format NAND
task 29: Format BinFS
task 2a: Format ALL
And what means: 28 55aa will also reformat the "partition"
What happends after I'm doing such a formating? Is a operating system still on the device? Or is only the SPL Bootloader active, which I have to use to get a new .nbh file on the device?
I just did a few commands with mtty:
Code:
Cmd>checkimage
SPL CRC checksum = 0xCB7389E9
CE CRC checksum = 0x3B4697DA
ExtROM CRC checksum = 0x0
Cmd>info 7
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_k9k2g08
DEVICE ID=0xAA
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 3 (0x3) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 12 (0xC) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 28 (0x1C) is reversed block
BLOCK 29 (0x1D) is reversed block
BLOCK 30 (0x1E) is reversed block
BLOCK 31 (0x1F) is reversed block
Partition[0], type=0x20, start=0x2, total=0x3E
Partition[1], type=0x23, start=0x40, total=0x800
Partition[2], type=0x25, start=0x840, total=0xC3C0
Partition[3], type=0x4, start=0xCC00, total=0xDCC0
CE Total Length(with sector info) = 0x6666000
CE CheckSum Length(without sector info) = 0x6600000
Cmd>info 9
Storage Start Addr=0x56A20000, length:0x6ECE600
Thanks in adavnce for reply...

when you run task 29: Format BinFS, it will erase everything on you device, even the os & system partition which is most prob causing the problem, no worries tho when you switch the device on it will show the touch diamond splash, so just put it into bootloader, then connect it to your pc, you can flash a new rom using an ruu

Thanks for this good advise. Everything looks really good after using "mtty", doing "task 29", using ruu and flashing any firmware.
Best regards
luftdieb

[Q] How to Fix: Stuck on Splash Screen (Boot) Loop After Previos Successful Flashings

I have a properly HardSPL'ed TMO-TP2, in the past 2 weeks or so, I've flashed with the following ROMs via USB in chronological order, running task29 in between & HR after every flash of a ROM
simplicity_15_November_28244CHT
EnergyROM 28244 Sense 2.5 Cookie 2.0 Dec20
EnergyROM 29007 Sense 2.5 Cookie 2.0 Dec27
Energy.RHODIUM.28244.Sense2.5.MaxSense.Dec.22
Here's the problem, after MaxSense Dec22, I decided to revert back to EnergyROM 28244 Sense 2.5 Cookie 2.0 Dec20, but my TP2 now loops in the following order:
a. splash screen 1 (pink "stick together" box)
b. splash screen 2 (same pink box with BRGD & numbers below)
c. screen brightens a bit
d. shows Energy initial setup screen ("Please wait while your device is starting for the first time...")
e. screen dims
f. device restarts repeating the same sequence over & over again
What I have done so far with corresponding results:
1. Re-ran task 29 - went smoothly, no errors (also done in between flashes below)
2. Reflashed via USB (and Hard Reset afterwards) to
a. TMO-USA TP2 Official ROM - no go, same splash screen-tmo-windows splash screen loop
b. Simplicity_15_November_28244CHT - no go, tmo-simplicity splash screen loop
c. EnergyROM 28244 Sense 2.5 Cookie 2.0 Dec20 - no go, tmo-energy splash screen loop
d. EnergyROM 29007 Sense 2.5 Cookie 2.0 Dec27 - no go, tmo-energy splash screen loop
e. Energy.RHODIUM.28244.Sense2.5.MaxSense.Dec.22 - no go, tmo-energy splash screen loop
3. Left the device loop itself crazy overnight while plugged to HTC OEM AC Wall Adapter
4. Soft Reset - still no go, same tmo-energy splash screen loop
5. Re-ran task 29 - went smoothly, no errors (also done in between flashes below)
6. Now via mSD not USB: Reflashed and Hard Reset afterwards to
a. TMO-USA TP2 Official ROM - no go, same splash screen-tmo-windows splash screen loop (only done via USB, not mSD but I repeated it just in case it might work)
b.simplicity_15_November_28244CHT - no go, tmo-simplicity splash screen loop
c. EnergyROM 28244 Sense 2.5 Cookie 2.0 Dec20 - no go, tmo-energy splash screen loop
d. EnergyROM 29007 Sense 2.5 Cookie 2.0 Dec27 - no go, tmo-energy splash screen loop
e. Energy.RHODIUM.28244.Sense2.5.MaxSense.Dec.22 - no go, tmo-energy splash screen loop
f. EnergyROM 28244 Sense 2.5 Cookie 2.0 Dec21 Christmas Ed. - no go, tmo-energy splash screen loop
7. Just pulled out the battery, put it back in, plugged to HTC OEM AC Wall Adapter, left it charging for 3 hours (not looping at this stage, just showed orange LED while its off)
8. When I saw the green LED indicating a full charge, I tried the following:
a. Turned it on - no go, tmo-energy splash screen loop
b. Hard Reset - no go, tmo-energy splash screen loop
c. Reflashed to EnergyROM 28244 Sense 2.5 Cookie 2.0 Dec21 Christmas Ed. via mSD - no go, tmo-energy splash screen loop
8. Now, I just removed mSD, pulled out the battery, put it back in, plugged to HTC OEM AC Wall Adapter, will leave it charged for the rest of the day (currently shows orange charging LED)
I hope with this detailed account, someone could help me narrow this down to just a battery issue and not an internal chip-level damage, a stuck byte that hicks up the boot process or something that may lead to warranty replacement. This was an early Chrismas gift from my wife & bought all the way from Singapore so SPL'ing it back to stock SPL ROM & claiming it through warranty is not an option for me.
Thanks in advance.

nelvbautista said:
I have a properly HardSPL'ed TMO-TP2, in the past 2 weeks or so, I've flashed with the following ROMs via USB in chronological order, running task29 in between & HR after every flash of a ROM
simplicity_15_November_28244CHT
EnergyROM 28244 Sense 2.5 Cookie 2.0 Dec20
EnergyROM 29007 Sense 2.5 Cookie 2.0 Dec27
Energy.RHODIUM.28244.Sense2.5.MaxSense.Dec.22
Here's the problem, after MaxSense Dec22, I decided to revert back to EnergyROM 28244 Sense 2.5 Cookie 2.0 Dec20, but my TP2 now loops in the following order:
a. splash screen 1 (pink "stick together" box)
b. splash screen 2 (same pink box with BRGD & numbers below)
c. screen brightens a bit
d. shows Energy initial setup screen ("Please wait while your device is starting for the first time...")
e. screen dims
f. device restarts repeating the same sequence over & over again
What I have done so far with corresponding results:
1. Re-ran task 29 - went smoothly, no errors (also done in between flashes below)
2. Reflashed via USB (and Hard Reset afterwards) to
a. TMO-USA TP2 Official ROM - no go, same splash screen-tmo-windows splash screen loop
b. Simplicity_15_November_28244CHT - no go, tmo-simplicity splash screen loop
c. EnergyROM 28244 Sense 2.5 Cookie 2.0 Dec20 - no go, tmo-energy splash screen loop
d. EnergyROM 29007 Sense 2.5 Cookie 2.0 Dec27 - no go, tmo-energy splash screen loop
e. Energy.RHODIUM.28244.Sense2.5.MaxSense.Dec.22 - no go, tmo-energy splash screen loop
3. Left the device loop itself crazy overnight while plugged to HTC OEM AC Wall Adapter
4. Soft Reset - still no go, same tmo-energy splash screen loop
5. Re-ran task 29 - went smoothly, no errors (also done in between flashes below)
6. Now via mSD not USB: Reflashed and Hard Reset afterwards to
a. TMO-USA TP2 Official ROM - no go, same splash screen-tmo-windows splash screen loop (only done via USB, not mSD but I repeated it just in case it might work)
b.simplicity_15_November_28244CHT - no go, tmo-simplicity splash screen loop
c. EnergyROM 28244 Sense 2.5 Cookie 2.0 Dec20 - no go, tmo-energy splash screen loop
d. EnergyROM 29007 Sense 2.5 Cookie 2.0 Dec27 - no go, tmo-energy splash screen loop
e. Energy.RHODIUM.28244.Sense2.5.MaxSense.Dec.22 - no go, tmo-energy splash screen loop
f. EnergyROM 28244 Sense 2.5 Cookie 2.0 Dec21 Christmas Ed. - no go, tmo-energy splash screen loop
7. Just pulled out the battery, put it back in, plugged to HTC OEM AC Wall Adapter, left it charging for 3 hours (not looping at this stage, just showed orange LED while its off)
8. When I saw the green LED indicating a full charge, I tried the following:
a. Turned it on - no go, tmo-energy splash screen loop
b. Hard Reset - no go, tmo-energy splash screen loop
c. Reflashed to EnergyROM 28244 Sense 2.5 Cookie 2.0 Dec21 Christmas Ed. via mSD - no go, tmo-energy splash screen loop
8. Now, I just removed mSD, pulled out the battery, put it back in, plugged to HTC OEM AC Wall Adapter, will leave it charged for the rest of the day (currently shows orange charging LED)
I hope with this detailed account, someone could help me narrow this down to just a battery issue and not an internal chip-level damage, a stuck byte that hicks up the boot process or something that may lead to warranty replacement. This was an early Chrismas gift from my wife & bought all the way from Singapore so SPL'ing it back to stock SPL ROM & claiming it through warranty is not an option for me.
Thanks in advance.
Click to expand...
Click to collapse
Any suggestions? tips? TIA

Hardware fault? The device loads the rom, even starts the customization. Probably a mainboard change is needed.
Sorry for not being helpful at all. Sometimes **** happens and there is nothing we can do.

As a last step you could try to change the HSPL, but I doubt it will help.
MOD EDIT: The file you are describing and instructing users to search for is a Rip-Off of the OliNex Hard-SPL and not allowed to be posted without direct permission from either Cmonex or Olipro.
My edit: Sorry, I had no idea it's a rip-off.

Jackos said:
As a last step you could try to change the HSPL, but I doubt it will help.
MOD EDIT: The file you are describing and instructing users to search for is a Rip-Off of the OliNex Hard-SPL and not allowed to be posted without direct permission from either Cmonex or Olipro.
My edit: Sorry, I had no idea it's a rip-off.
Click to expand...
Click to collapse
Could MTTY help? Since I've already restored this back to stock ROM & SPL, I couldnt do HardSPL anymore to attempt MTTY, I also have the following on my bootloader screen. Hope someone could help me decipher what it means. Really hope I can still revive my TP2.
RHOD210 32M SS-BC
SPL-0.87.0000
MicroP(LED) 0x0A
MicroP(KEY) 0x04
TURBO HW/TURBO SW
NO TP MFG DATA
Thanks

It means just that the bootloader is working fine. Since you load any rom without problems I suspect a hardware fault.
I do not think that MTTY could help in any way.

nelvbautista said:
Could MTTY help? Since I've already restored this back to stock ROM & SPL, I couldnt do HardSPL anymore to attempt MTTY, I also have the following on my bootloader screen. Hope someone could help me decipher what it means. Really hope I can still revive my TP2.
RHOD210 32M SS-BC
SPL-0.87.0000
MicroP(LED) 0x0A
MicroP(KEY) 0x04
TURBO HW/TURBO SW
NO TP MFG DATA
Thanks
Click to expand...
Click to collapse
probably HW issue. but just out of curiosity what does info 8 show in mtty?
(you can use mtty with stock SPL too, just fewer commands available, info command should work ok)

cmonex said:
probably HW issue. but just out of curiosity what does info 8 show in mtty?
(you can use mtty with stock SPL too, just fewer commands available, info command should work ok)
Click to expand...
Click to collapse
I ran MTTY, I think I did task29 (I think I shouldn't have done so...) Here's what info 8 showed...
--- 2K bytes sector version ---
DEVICE NAME=samsung_kby00n00hm
DEVICE ID=0xBC
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x1000
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 3 (0x3) is reversed block
BLOCK 4 (0x4) is reversed block
BLOCK 5 (0x5) is reversed block
BLOCK 7 (0x7) is reversed block
BLOCK 9 (0x9) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 12 (0xC) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 15 (0xF) is reversed block
BLOCK 16 (0x10) is reversed block
BLOCK 17 (0x11) is reversed block
BLOCK 18 (0x12) is reversed block
BLOCK 19 (0x13) is reversed block
BLOCK 20 (0x14) is reversed block
BLOCK 21 (0x15) is reversed block
BLOCK 22 (0x16) is reversed block
BLOCK 23 (0x17) is reversed block
BLOCK 24 (0x18) is reversed block
BLOCK 25 (0x19) is reversed block
BLOCK 26 (0x1A) is reversed block
BLOCK 27 (0x1B) is reversed block
BLOCK 28 (0x1C) is reversed block
BLOCK 29 (0x1D) is reversed block
BLOCK 30 (0x1E) is reversed block
BLOCK 31 (0x1F) is reversed block
BLOCK 32 (0x20) is reversed block
BLOCK 2094 (0x82E) is bad block
BLOCK 2310 (0x906) is bad block
OS NOT FOUND !!!
Now trying to reinstall the TMOUS Rhodioum Official ROM. Crossing my fingers & toes for this to overwrite anything that went bad & restore it back to stock...

Ok, Ive managed to reinstall the TMOUS Official ROM back but I'm still having the same boot loop issue. It still wont go past the windows splash screen even after a hard reset. Here's what info 8 showed
--- 2K bytes sector version ---
DEVICE NAME=samsung_kby00n00hm
DEVICE ID=0xBC
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x1000
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 3 (0x3) is reversed block
BLOCK 4 (0x4) is reversed block
BLOCK 5 (0x5) is reversed block
BLOCK 7 (0x7) is reversed block
BLOCK 9 (0x9) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 12 (0xC) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 15 (0xF) is reversed block
BLOCK 16 (0x10) is reversed block
BLOCK 17 (0x11) is reversed block
BLOCK 18 (0x12) is reversed block
BLOCK 19 (0x13) is reversed block
BLOCK 20 (0x14) is reversed block
BLOCK 21 (0x15) is reversed block
BLOCK 22 (0x16) is reversed block
BLOCK 23 (0x17) is reversed block
BLOCK 24 (0x18) is reversed block
BLOCK 25 (0x19) is reversed block
BLOCK 26 (0x1A) is reversed block
BLOCK 27 (0x1B) is reversed block
BLOCK 32 (0x20) is reversed block
BLOCK 2094 (0x82E) is bad block
BLOCK 2310 (0x906) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x940
Partition[2], type=0x25, start=0xF80, total=0x17680
Partition[3], type=0x4, start=0x18600, total=0x229C0
CE Total Length(with sector info) = 0xC3C3000
CE CheckSum Length(without sector info) = 0xC300000
Really hoping I could still fix this without resorting to warranty exchange. This is a T-mobile branded TP2 with warranty jurisdiction in the US. As per HTC online customer care, I could ask for HTC US or EU for global warranty coverage. T-mobile's warranty (and exchange) would only apply if I'm in the US. Unfortunately this was bought from Singapore & I'm using it in the Philippines thats why I want to exhaust all means to fix this. Appreciate all inputs guys.

that output is okay. I don't have other ideas at this point. just one more question, did the problem start right after flashing back to that energy rom (which I realize did work fine earlier)? i.e. it didn't boot even once with that?

After I flashed to Energy.RHODIUM.28244.Sense2.5.MaxSense.Dec.22, it still worked fine. It didn't quite suit my preferences when it comes to the home screen so I just decided to reflash back to EnergyROM 28244 Sense 2.5 Cookie 2.0 Dec20 (which I've used longer among all the ROMs I've tried & yeah this was working before & never encountered boot loop issues with it on my TP2). This is when the boot loop issue began.
Now its reflashed to stock ROM & SPL, TP2 still boot loops from t-mo splash screen to windows mobile splash screen (sometimes going up to the initial setup screen with the progress bar but doesn't complete it), screen dims, restarts & repeats the same sequence.

One thing I've noticed was with all these steps (doing task29, flashing from one ROM to another via USB or mSD, restoring back to stock SPL & ROM, MTTY, hard resets, etc) it seems to eat up a fully charged battery relatively quickly...
Call it wishful thinking but I'm really hoping this is just a battery issue not providing enough juice for the whole boot process to finish. I'll be taking this to HTC Phils. authorized service center tomorrow to test a different battery. Keeping my finger & toes crossed.
Current status: boot loop still there, TP2 off and charging via the AC wall charger, has orange charging LED, back to my old backup phone for the meantime (Nokia 8800)

Latest Update:
I went to HTC Phils. Authorized Service Center, they couldn't help me. T-mo branded TP2s are not serviced here due to scarce parts for such model.
Though I was informed that I might be charged for a diagnosis fee to really find out what wnet wrong, they were considerate enough to lend me a TP2 battery to narrow it down to a battery issue. Battery wasnt the problem, the boot loop still persists. They mentioned something about having the board replaced which would cost more than half of the price of the phone itself. They also recommended that I go through the proper warranty channels which was the logical, most practical step. Good thing I found the receipt & still have the complete packaging intact. I'll have a friend in SG take care of the replacement for me. I'll be back once I already have the replacement TP2...
Thanks for all the help and assistance Rhodium Gurus...

having the same exact problem, changed the battery and still in a boot loop...what happened is that my rhodium ran out of battery while on XDAndroid...tried flashing some roms and did hard rest with no luck

xturbo91 said:
having the same exact problem, changed the battery and still in a boot loop...what happened is that my rhodium ran out of battery while on XDAndroid...tried flashing some roms and did hard rest with no luck
Click to expand...
Click to collapse
Hope for the best that your issue is just a battery related. Consider these questions, I've been through all of these for the nth time, to no avail.
1. Are you using a different TP2 battery other than the one that came in the box?
2. Whether yes or no to #1, have you tried charging via a TP2 cradle or any external battery charger that's compatible with the TP2 batteries?
3. With your old TP2 (and your other) TP2 batteries fully charged, do you still have the same issue?
4. Cross your fingers & toes, pray to all the powers that may be that your TP2 boot loop issue will be resolved via a fully charged battery
5. If not & you're still having the same boot loop issue, most-likely an internal chip inside the TP2 motherboard may have had a stuck byte or two, may have bad block/s, fried or something like a low-level, abyss-deep glitch has kicked in (and got stuck in there somewhere) that prevents it from booting completely to windows (honestly, I'm no hardcore winmo developer nor a kick-a** phone guru to really know or justify in a highly technical level what causes this).
6. Quoting cajunflavoredbob on this, Reflash back to stock ROM then restore your stock TP2 SPL & claim it through your TP2 warranty for a replacement (if it still has one). Having it repaired by motherboard replacement might cost you more than half of the price of a brand new TP2 (that's what HTC Phils. told me).
7. Either way, have a back up phone handy...
Good Luck Bro

[Q] Can't boot my diamond after ROM flash

Hello averybody. I am new here and I actually don't know if this is the right place... my apologies if not.
Yesterday I put the hard spl 1.40 olinex on my diamond and, after that, everything was ok. I then tried to put a new ROM (Eto.y-2.4-ITA) but I probably missed something (was my first time... ).
anyway, in the middle of this operation something gone wrong and now mi diamond is stuck on the black screen, showing "touch diamond". I tried soft reset, hard reset, I formatted the movinand from the bott menu, but it keeps not to load. I just tried with mtty: the 1.42 version couldn't find the usb port, while the 1.0.0.1 seemed to work, but at the end the mobile still doesn't work. problem is: my active sync doesn't see the diamond when it is plugged via usb......
any chance to save it?
thank you all so much
Giò

brianza78 said:
Hello averybody. I am new here and I actually don't know if this is the right place... my apologies if not.
Yesterday I put the hard spl 1.40 olinex on my diamond and, after that, everything was ok. I then tried to put a new ROM (Eto.y-2.4-ITA) but I probably missed something (was my first time... ).
anyway, in the middle of this operation something gone wrong and now mi diamond is stuck on the black screen, showing "touch diamond". I tried soft reset, hard reset, I formatted the movinand from the bott menu, but it keeps not to load. I just tried with mtty: the 1.42 version couldn't find the usb port, while the 1.0.0.1 seemed to work, but at the end the mobile still doesn't work. problem is: my active sync doesn't see the diamond when it is plugged via usb......
any chance to save it?
thank you all so much
Giò
Click to expand...
Click to collapse
Your problem is related to Eto.y roms,them are good but the flashing software included automatically does task29(Erasing everithing on the diamond's nand)so your diamond will not boot,to make it boot again,reboot the phone holding volume down,connect to the pc,the pc will find a new device and install the drivers,then flash another rom from the pc,don't use the eto.y software,If you want eto.y rom,rename the .nbh file included to DIAMIMG.NBH,paste it in the internal storage,from the phone press soft reset,then volume down and back key,then power key and follow the instructions

thank you for the reply. unfortunately, my desktop PC doesn't see the diamond and active sync doesn't estabilish a connection.

this is the last part had with mtty
"Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 3 (0x3) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 12 (0xC) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 28 (0x1C) is reversed block
BLOCK 29 (0x1D) is reversed block
BLOCK 30 (0x1E) is reversed block
BLOCK 31 (0x1F) is reversed block
OS NOT FOUND !!! "

brianza78 said:
thank you for the reply. unfortunately, my desktop PC doesn't see the diamond and active sync doesn't estabilish a connection.
Click to expand...
Click to collapse
In bootloader(after holding volume down) mode?

neither..... if I plug the USB cable in bootloader mode, the display changes from "serial" to "USB" (and that's all).

brianza78 said:
neither..... if I plug the USB cable in bootloader mode, the display changes from "serial" to "USB" (and that's all).
Click to expand...
Click to collapse
Once it changes to USB start flashing another rom from pc,but don't flash eto.y with the included software

ok thanks. any suggestion for a suitable ROM?

brianza78 said:
ok thanks. any suggestion for a suitable ROM?
Click to expand...
Click to collapse
eto.y are really good.
before flashing eto.y choose a random rom,click on a random thread and flash it

thanks, but.... maybe it's just me being idiot...... how can I flash a new rom if I cannot paste the .nbh file into the diamond?
:-(

brianza78 said:
thanks, but.... maybe it's just me being idiot...... how can I flash a new rom if I cannot paste the .nbh file into the diamond?
:-(
Click to expand...
Click to collapse
Download anoter rom, be sure that in the rom's archive there's ruu or Rom update utility and then delete the .nbh included and put the eto.y .nbh

that's it mate! thanks so so so much. I just couldn't understand, because it kept asking to establish an active sync connection before to flash a new ROM, and it just couldn't.. but it worked anyway, somehow.
brilliant!

Same problem here
Hi guys,
I suffer from the same, the diamond won't pass the "TOUCH DIAMOND" black screen.
i entered the boot loader mode (the screen with the colors) i have there 1.40.Olinex and after my windows7 finished installing the drivers "usb" appeared on the screen.
I tried to install "RUU_Diamond_HTC_WWE-ME_1.37.456.2_Radio_Signed_Diamond_52.26a.25.09_1.00.25.03_Ship" which i found in the forum but it doesn't help, the diamond will stay forever on the TOUCH diamond screen.
what am i doing wrong?
EDIT: Got it, i flashed to SPL1.90 and the phone finally finished booting into winmo,
Now i can run android on it