Database Develop

thought I wasn't a newb, guess I was wrong.

Alright, so I've been lurking on this forum for quite some time now. I've flashed, reflashed roms. I thought I had a handle on everything but I guess I was wrong. I've been away from a Window's computer for quite some time now. And I recently saw the new 3.3 rom from the gods of xda. Well, I downgraded, to button's 1.01. and then here's where i screwed up. i forgot to go back up to a 2.xx rom. and went straight for the gold and went for the 3.3. yes i know i screwed up. well here's where I'm at now. still stuck with Button's 1.01 ipl/spl but i have the 3.3 OS. And now I'm not getting any active sync connection, my computer isn't recognizing my wizard. also. my 8125 is slow, i mean i tap the screen and i get nothing re-tap nothing eventually nothin happens, and it's stuck on the today screen. I should also mention it's G3, and yes, i unlocked it all the way. so now I'm basically stuck on the today screen with nothing to do. I foolishly finally tried to clear the storage and start from scratch, but now I'm stuck with no extended rom i believe, all the settings are wiped. am i screwed or what? Or does anyone know a way to at least get active sync back up and running, shouldi re-install it? alright so correction, I'm seeing that all the settings from the extended are showing up (i.e. the battery settings on the today screen, the one-touch voicemail/ 411 connect.) so any suggestions.??
edit--
also when booting up, it takes for ever. litteraly 2-4 minutes. And i tried soft rest via stylus, and then it went to button's boot screen shows ipl spl 1.01 and no radio rom but os was 3.3 and then it would reset showing the same damn beer mug, and then it would do it again. then the screen almost faded away and then it showed the same damn screen again. finally it will go to the crossbow splash screen. and no the battery meter at the bottom is showin -1%

you wizard is not dead yet
I did this...hurry...hurry, hurry but there's somethin' that you can do. Try flashing again button's rom by entering your ppc into bootloader, and then attach it to the pc. It will be recognized, and then you can start flashing.
Good luck. And from mistakes we all learn

hmmm
Well I took your advice, put the 8125 into bootloader. And then connected to the laptop. Still no active sync connection, however the 8125 does recognize it I suppose, when I plug into the laptop the USB appears at the bottom left of my 8125's screen.

also
sorry... i hit the edit button in place of quote.
faria

bootloader mode?
i haven't messed up any of my roms personally yet...but i've read in the past that there is a bootloader mode that you can try to enter and reflash your rom from there. maybe it'll work to try and reflash back to the 1.01 rom you started with?
gotta do a search on here to find it...i think it had something to do with holding the comm manager button and the voice dial button and hitting the small button on the right side of the phone between the voice dial and camera button...

waaait
It is how it's supposed to act. It shouldn't charge...it's in bootloader. Just after you hear the "device connected" sound start the button's rom upgrade. that's it. easy as pie
Or you can start with any 2.xx rom. i think it's going to work with that too.

Ok man, I'm such a spaz, alrigh, there's no active sync, but I am running the no id update utility. And it's running on the ppc, so hopefully, I'm making progress.

Exactly what I said
monkey_knight said:
i haven't messed up any of my roms personally yet...but i've read in the past that there is a bootloader mode that you can try to enter and reflash your rom from there. maybe it'll work to try and reflash back to the 1.01 rom you started with?
gotta do a search on here to find it...i think it had something to do with holding the comm manager button and the voice dial button and hitting the small button on the right side of the phone between the voice dial and camera button...
Click to expand...
Click to collapse
That's what I'm trying to tell him. I went thru that. It worked perfectly for me, so it should for him.

anichillus said:
That's what I'm trying to tell him. I went thru that. It worked perfectly for me, so it should for him.
Click to expand...
Click to collapse
It worked for me too.

Boo yah, well I'm back at button.s rom, time to try again. Thanks guys, you've been a world of help.

eightysixfilms said:
Boo yah, well I'm back at button.s rom, time to try again. Thanks guys, you've been a world of help.
Click to expand...
Click to collapse
Also, it's not showing that the 8125 is charging either. On usb, or regular wall outlet. What have I gotten myself into?simply put the device in booloader mode and flash the latest aku2 rom from your provider...this will bring it to live again. due to an hardware flaw wizards cannot be charged with out a proper working OS ....if your battery has drained you need to find an alternative way of charging it and then only you can flash the rom.
ps
activesync is not needed once in bootloader ....

with pleasure
As i said...some mistakes come in handy
@ Faria ... man, I think that if you don't have active sync installed, it won't work... It installs some drivers, the first time it goes into bootloader(for an upgrade 4 example), but it's true that you don't need "active sync" ....course, it's verry possible that I'm wrong...but I had a motorola Mpx200 and it wouldn't recognize it for flash until I've installed active sync

anichillus said:
As i said...some mistakes come in handy
@ Faria ... man, I think that if you don't have active sync installed, it won't work... It installs some drivers, the first time it goes into bootloader(for an upgrade 4 example), but it's true that you don't need "active sync" ....course, it's verry possible that I'm wrong...but I had a motorola Mpx200 and it wouldn't recognize it for flash until I've installed active sync
Click to expand...
Click to collapse
yes you correct you need the driver ..... what i meant to say is you dont need activesync in runing state.......but you do need activesyc in the pc in order to flash.....

thanks guys
Hey, got everything up and running, thanks to all those that helped out, ever in chicago let me know, we'll go out for some beers. But the newrom is up and running and everything seems to be going good. And hey I wasn't torn apart buy the elite on here. So thanks for making me not look stupid. haha

faria said:
yes you correct you need the driver ..... what i meant to say is you dont need activesync in runing state.......but you do need activesyc in the pc in order to flash.....
Click to expand...
Click to collapse
Yeah I didn't know that either, I started to freak once i saw activesync wasn't picking up the 8125. But it's good to know that you don't necesarilly need it up and running.

Installed 2.23ROW - Help! ActiveSync will not connect!

I installed the 2.23ROW Eng on my Treo 750 yesterday. I shut down the computer at the point where the installer says to make sure you complete the list of tasks before hitting continue. I figured it was just an unnecessary step, as WM6 was on the phone. I know now that another part of the phone does not get updated unless this happens.
Now, I'm stuck without a way to finish the flash. ActiveSync won't connect, so I can't reflash it. The only thing I can think of is to do the SD card method, but I don't have an SD reader on me, and I can't freaking get ActiveSync to connect so I can't copy it over that way!!
Can someone help me out? Oh, and I already disabled the "Enable advanced network functionality". That didn't help. The phone works fine and all, but I cannot customize it with cabs at this point.

R U sure you can't connect at all - or is it just not finding your user?
When I upgraded my 750 (using the SDCard method), somehow it created a new/different user for me on the phone.
My "workaround" was to get the phone and my ActiveSync to both use the same user.
More details please...

No, it absolutely would not connect. I ended up just using the flash card method to get it fixed. Then, I was able to reconnect and get the full 2.23ROW installed. Everything seems to be working just fine now.
I do have a question, though. The phone is quite different than it was as an AT&T phone. For one, the power button does not make it sleep. In fact, I can find no quick way to get the screen to turn dark. If I put it down for a minute, it'll shut off. Any suggestions?
Also, what would you recommend for this phone? I used it for a while until I got my Tilt, but I pretty much left it stock. I've done just about everything there is to do to the Tilt, but so far I've only installed the HTC Home plugin for the Treo.
What are some other good upgrades?

Flapjack said:
I do have a question, though. The phone is quite different than it was as an AT&T phone. For one, the power button does not make it sleep. In fact, I can find no quick way to get the screen to turn dark. If I put it down for a minute, it'll shut off. Any suggestions?
Also, what would you recommend for this phone? I used it for a while until I got my Tilt, but I pretty much left it stock. I've done just about everything there is to do to the Tilt, but so far I've only installed the HTC Home plugin for the Treo.
Click to expand...
Click to collapse
Is there still a "Dial Lookup" option in the Today settings? That has to be checked for the power button to work correctly. The HTC Home plugin did that to mine as well... and it's fairly well known.

edmc said:
R U sure you can't connect at all - or is it just not finding your user?
When I upgraded my 750 (using the SDCard method), somehow it created a new/different user for me on the phone.
My "workaround" was to get the phone and my ActiveSync to both use the same user.
More details please...
Click to expand...
Click to collapse
Hi. Would you mind telling me what your Software Version says. I upgraded using the SD Method, and My Version still reads 1.13-ATT.
Thanks

vn1977 said:
Is there still a "Dial Lookup" option in the Today settings? That has to be checked for the power button to work correctly. The HTC Home plugin did that to mine as well... and it's fairly well known.
Click to expand...
Click to collapse
That worked, but it looks horrible. The HTC plug in leaves room for one item below it, and that "Dial lookup" thing takes two, so there is a crappy little scroll thing there.
manfly9884 said:
Hi. Would you mind telling me what your Software Version says. I upgraded using the SD Method, and My Version still reads 1.13-ATT.
Thanks
Click to expand...
Click to collapse
The SD method does not load the entire update. I had to the exe method with the payloads.xml file, then follow through where it applies the Palm tweaks to get it to work right.

I think I figured it out... is that the "hidelogo" cab I've seen floating around? I'll try that now.

Geez, it works... but now the phone is stuck in a rebooting loop. It's only up and running for a few seconds, then it soft resets.

Flapjack said:
That worked, but it looks horrible. The HTC plug in leaves room for one item below it, and that "Dial lookup" thing takes two, so there is a crappy little scroll thing there.
The SD method does not load the entire update. I had to the exe method with the payloads.xml file, then follow through where it applies the Palm tweaks to get it to work right.
Click to expand...
Click to collapse
Can you please tell exactly how you did the EXE method with the payloads.xml file.
Thanks in advance
Never mind.
Thanks.

Flapjack said:
Geez, it works... but now the phone is stuck in a rebooting loop. It's only up and running for a few seconds, then it soft resets.
Click to expand...
Click to collapse
Sorry. If I was around before I would have told you about that hidelogo thing. I think you may have to reflash your phone again to get around the rebooting. Search around the forums.
When I ran into the same thing, I removed the HTC Menu thing and went for SPB Menu instead, even though I lose the nice clock.

Crap. Now it's doing it again.... this time, on two different computers. The AS icon turns green, says connecting, sits like that for a minute, then returns an error asking if I wanna run the ActiveSync troubleshooter...

Ignito Hard SPL

Howdy, i have looked at all the guides, done loads of research into upgrading my Ignito.
I have tried to use the Olinex 1.40 and also the signed version....
But when i load it all up, go through the correct steps etc.. My phone screen looks like its just had some dodgy virus and looks like its about to die and then slowly turns off...
It then does a full reboot and its like i have a brand new phone again...
I am at a loss as to why it does this..
Anyone have any tips or tricks as to how to get around this problem ?
Any help at all will be very very welcome
Cheers
Sam

when you do the hard spl, you will only get a black screen and then it will reboot, just as you describe.
Hold the volume down key and then soft reset, if you see OLI anywhere, then it worked.

The problem is when i try the upgrade the screen seems to die aftera bout 10secs and then it says its fully done.
So there isnt enough time for the Hard SPL to be upgraded....
Anyone ?? Please....

The problem is when i try the upgrade the screen seems to die aftera bout 10secs and then it says its fully done.
So there isnt enough time for the Hard SPL to be upgraded....
Anyone ?? Please....
Click to expand...
Click to collapse
Maybe you could give more detailed information, what exactly are you doing, what does the PC end of the process say etc.
Can you take any screenshots, what SPL do you have now - the guide suggests that 1.93 could be better for you than 1.4?
Kim

It says complete after about 10seconds and then the phone reboots fully.
The current one i believe is 1.93.....
I have tried both of the Olinex versions to no avail at all.....

......

MuDvAyNeX said:
......
Click to expand...
Click to collapse
I guess no one is helping because you're not giving us enough information, procedure, XP or Vista, have you tried Hard-SPL 1.93, screenshots or better description of the problem.
Screen goes funny and then reboots just isn't enough
Kim

Well i have tried both of the Olinex versions both the 1.4 and the 1.93.
I am using windows vista and the mobile device center, its fully connected as i do a sync etc before hand.
I then load the Romloader that does the usual tick this, tick that etc.
Once that has happened i click the upgrade button, it then confirms i am going from the current SPL do the one i have chosen.
I click ok and then it goes to the progress section where it says it could take upto 10min, the screen on the phone then looks like it has got a virus and starts to look like its dying.
Meanwhile after about 10 seconds it tells me that upgrade is done, this is while the phone reboots and starts like its a brand new phone again with no changes that i can see...
In all honesty i can't see what i am doing wrong

Scrath what i just put, as i was typing that i was trying the upgrade via my mates XP laptop and it now says in the bootloader 1.93 Olinex...
I am going to guess this is upgraded... lol

MuDvAyNeX said:
it now says in the bootloader 1.93 Olinex...
I am going to guess this is upgraded... lol
Click to expand...
Click to collapse
Great, glad it's sorted, I was gonna say I don't have much experience with Vista (an' I don't want to )
I'm sure that I've read that there can be issues with the Vista device center(sic), A quick search of XDA-Dev will help.
If you want to eliminate the PC <-> Ignito pitfalls maybe try Suillers method of upgrading direct from the device Internal Storage.
Kim

Possibly a dead Kaiser, suggestions? (or purchase!)

So, I plugged my Kaiser (Tilt) into my computer the other day to charge it, and the next morning when I unplugged it, I noticed it was locked up. No biggie, I soft-reset it, and it came directly back to the bootloader (right before the bootloader shows is a white screen, that says "Loading image... No image found!", that flashes for a fraction of a second.
If I plug it into my computer at this point, Windows says the USB device has malfunctioned and it doesn't recognize it. I can't flash it ("connection error"), and it wouldn't hard reset.
Then it kinda came back to life, kinda. Suddenly it'll boot into WM. Windows still doesn't recognize it, but I used JumpSPL to get it into a bootloader, and tried to install a HardSPL on it so I could flash a new ROM (to this point it's been stock-only because it belongs to the company I work for). The HardSPL flash failed partway through, and then it was stuck in bootloader for real. At that point I tried flashing a stock ROM, and it kept failing at different points, never getting more than about halfway through.
Does anyone have any suggestions? Or, do you want to buy it? At this point it's mine (company doesn't want it back), so I'm willing to experiment freely with it. Right up until my Touch Pro 2 comes in and I lose interest
*** UPDATE ***
So after writing this, just for kicks, I decided to give re-flashing the original ROM one more shot (it's been off and untouched now for several days at this point) and the flash succeeded. We'll see where it goes from here

Good luck with your phone.. I hope all goes well.. If you find out what the problem was/is, let me know

Hey godefroi, im new to all of this, just bought a messed up tilt from my friend, and i want to know if you could givve me the link for the insturctions to refalsh my tilt

Just hit up AT&T's site (which redirects you to HTC's site) and download the ROM. The file you want is "_ATT Tilt_RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship.exe", which was the latest update for the phone.

Seems it's not fixed. After playing around with it for a couple days, it's back into bootloader and stuck there. Taking out the battery and leaving it for a few hours brings it back for a while, but it seems there's no permanant fix. Next step will be flashing HardSPL and a custom ROM. I'll update when that happens.

awww dang, that sucks. thank you for tellin me. hopin your tilt comes out ok

Did you ever get this resolved?
Hey man did you ever get this fixed? I cant find anything on it.
I can get to a boot loader screen and it shows USB and when I plug it into my computer I hear the sound that it's recognized but my active sync wont connect.
This is what I posted earlier and a moderator killed the post because I didn't spend hours hunting for a solution first before posting. I don't think one exists but if there is I would be glad to know it. I have flashed this phone and my older HTC Wizard dozens of times with no issues so Im not a "noob"
Earlier today I was taking a picture and the screen kind of stuck so I has to soft reboot it.
It didn't come back up. I was left at the rainbow bootloader screen.
I tried holding the camera button down and rebooting but it didn't change anything.
I tried several different combo's of holding keys down and rebooting and it always came back to that bootloader screen.
So the next thing I did was to format my cd card and downloaded KaisDiagTest1.zip and then coppied the KAISDIAG.NBH image file from the zip on to the root of the sd card.
That worked fine and I was left at a screen saying SPL 1.00.OliNex.
Next thing I did is were I think I screwed up. I flashed it with _ATT Tilt_RUU_Kaiser_CINGULAR_WWE_1.62.502.0_radio_sign _22.45.88.07_1.27.14.09R2_Ship.exe which is the ROM from the HTC site and I think I was only supose to use a custom ROM and now after it finished flashing the ROM it rebooted and is stuck showing loading ... on the screen.
It goes past the boot loader and is stuck at loading...
Please advise if there is anything I can do.
Cheers,
Chris
godefroi said:
So, I plugged my Kaiser (Tilt) into my computer the other day to charge it, and the next morning when I unplugged it, I noticed it was locked up. No biggie, I soft-reset it, and it came directly back to the bootloader (right before the bootloader shows is a white screen, that says "Loading image... No image found!", that flashes for a fraction of a second.
If I plug it into my computer at this point, Windows says the USB device has malfunctioned and it doesn't recognize it. I can't flash it ("connection error"), and it wouldn't hard reset.
Then it kinda came back to life, kinda. Suddenly it'll boot into WM. Windows still doesn't recognize it, but I used JumpSPL to get it into a bootloader, and tried to install a HardSPL on it so I could flash a new ROM (to this point it's been stock-only because it belongs to the company I work for). The HardSPL flash failed partway through, and then it was stuck in bootloader for real. At that point I tried flashing a stock ROM, and it kept failing at different points, never getting more than about halfway through.
Does anyone have any suggestions? Or, do you want to buy it? At this point it's mine (company doesn't want it back), so I'm willing to experiment freely with it. Right up until my Touch Pro 2 comes in and I lose interest
*** UPDATE ***
So after writing this, just for kicks, I decided to give re-flashing the original ROM one more shot (it's been off and untouched now for several days at this point) and the flash succeeded. We'll see where it goes from here
Click to expand...
Click to collapse

I never did. Every once in a while I can get it reflashed, but inevitably it stops working. Just like yours, I'll sfot reset it and it'll be stuck in bootloader.

Best bet is when it gets stuck on the bootloader or on the "white screen" as to put it. Do the following:
1) Unplug battery, memory car and simcard. Reinsert battery ONLY after 3 seconds (cards stay out!)
2) Hold BOTH softkeys down at the same time
3) Whilst holding softkeys, turn the unit on
4) You will be prompted to press "SEND" to reset all user data (you will lose everything on the internal storage. Press the Dial (green button) to reset.
5) When it's finished, you will be prompted to press "SEND" to reboot. Press send and it will boot into WM but might take slightly longer.
6) Realign your pointer and tada. It's up and running.
n.b. This often happens when the radio version of your phone isn't correct. If you notice, when you get stuck in the "white screen" the "gsm signal sight" is frashing green!
I've got to warn you again, this procedure WILL delete all of your internal user storage, hence why I recommend taking out all of the cards before proceeding.

heyadrian said:
Best bet is when it gets stuck on the bootloader or on the "white screen" as to put it. Do the following:
1) Unplug battery, memory car and simcard. Reinsert battery ONLY after 3 seconds (cards stay out!)
2) Hold BOTH softkeys down at the same time
3) Whilst holding softkeys, turn the unit on
4) You will be prompted to press "SEND" to reset all user data (you will lose everything on the internal storage. Press the Dial (green button) to reset.
Click to expand...
Click to collapse
Nope. Stuck in bootloader is stuck in bootloader. Like, stuck. No, really, it's stuck. Hard-resetting doesn't get it out.
heyadrian said:
n.b. This often happens when the radio version of your phone isn't correct. If you notice, when you get stuck in the "white screen" the "gsm signal sight" is frashing green!
Click to expand...
Click to collapse
There's no white screen, just bootloader rainbow. Also, there's no chance that I flashed the wrong radio, because this phone has never been flashed with anything but the official ROM. It's never even had a HardSPL flashed on it.

hmmm...now that you mention it has never had a hardSPL, maybe that could be the next step?
i understand that some people may want to keep a "stock" configuration in case waranty needs to be claimed or for any other valid reasons...but if the phone is out of waranty, theres little to lose.
only reason i'm suggesting it is because cmonex has a hardSPL that aims to fix EXACTLY this problem, among others (if i understand your problem and cmonex's fix correctly):
http://forum.xda-developers.com/showthread.php?t=420683
also, this thread links to a page in the wiki about your problem (or something along the same lines):
http://forum.xda-developers.com/showthread.php?t=423486
finally, a collection of hardSPL versions can be found in this "roll up" thread:
http://forum.xda-developers.com/showthread.php?t=498320
i guess you may have already gone through the above mentioned links but if not, they may open up more avenues for troubleshooting or even a permanent resolution.

RHOD210 Won't Boot.

I was running one of the ENERGY ROMs on my TP2, so it's got a different SPL and all that. I then put it in the box for about 5 weeks. I took it out two days ago to install XDANDROID. I used XDANDROID for about an hour, until the TP2 started randomly shutting itsself off. I've tried flashing NRGZ28's ULTRA LITE ROM and the official T-Mobile USA 6.5 ROM for the TP2. It won't go past the boot loader a majority of the time. When it does, it goes on to act like it's flashing the RHODIMG.nbh on my MicroSD but almost instantly after it starts, it shuts off again. It doesn't always try to flash the .nbh, but when it does, it never finishes. It's the same story with a hard reset. I can't ever get it to turn on, and the only way it does turn on is to do a battery pull. If I'm lucky, it'll stay on for about 60 seconds and then shut off again. I'm really clueless as to what to do here and I'm hoping someone can help me.
The Bootloader reads as folows:
RUUNBH
RHOD210 32M SS-BC
SPL-0.85.OilNex
MicroP(LED) 0x0A
MicroP(KEY) 0x04
TURBO HW/TURBO SW
TP MFG DATA
[unreadable]
812,19...
217.855 Calibrated
The reason 1.5 of the lines is unreadable is because of the message over it: "Upgrade ROM code error. please try again."
http[colonslashslash]farm3[/url][dot]static[dot]flickr[dot]com/2726/4386331314_8036d882a6_o.jpg

try flashing hard spl 1.01 it looks like you got an old version of the spl. read the sticky on flashing for newbies i belive it tells you how to do the hard spl if you are having difficulty by usb connection other than that i wouldnt know what to tell you i nver had that problem only bad flashes but those could be solved by reflashing another ROM

Sorry, i should have explained that better. I can't connect to the PC. It won't stay in bootloader mode so I can't flash it that way either. From what i understand, the only way i can flash anything to it right now is to get the xxxx.nbh file, rename it to RHODIMG.nbh and place it on the root of my SD. When I do that, though, it won't finish the flash. It just keeps going in a loop. about every 5 minutes it randomly turns on and tries to flash the RHODIMG.nbh if present. If it's not present, it just flashes the boot loader for >10 seconds and shuts off again.
Also, I'm not sure if this makes any difference, but I've had TWO computers recognize it as a new device, "Qualcomm CDMA Technologies MSM."

Make sure the battery has a good charge, nothing else springs to mind
PS. the qualcomm thing is what appears when it's flashing via USB
also maybe try formatting your SD card and put the stock ROM back on there, or try diff card

chasejones8 said:
Sorry, i should have explained that better. I can't connect to the PC. It won't stay in bootloader mode so I can't flash it that way either. From what i understand, the only way i can flash anything to it right now is to get the xxxx.nbh file, rename it to RHODIMG.nbh and place it on the root of my SD. When I do that, though, it won't finish the flash. It just keeps going in a loop. about every 5 minutes it randomly turns on and tries to flash the RHODIMG.nbh if present. If it's not present, it just flashes the boot loader for >10 seconds and shuts off again.
Also, I'm not sure if this makes any difference, but I've had TWO computers recognize it as a new device, "Qualcomm CDMA Technologies MSM."
Click to expand...
Click to collapse
it sounds like you dont have your sd card formatted make sure its format to FAT32 go to your computer inserd sd card & reformatted (make sure its a micro sd & that its less than 2g) then transfer the ROM to the card already renamed to RHODIMG then inserd ur card on your phone & flash it. it should work. let us know what happens

MadBeef said:
Make sure the battery has a good charge, nothing else springs to mind
Click to expand...
Click to collapse
I wish I could. I have no means of checking the battery status. I've had it plugged in pretty much constantly for about the last two days.
MadBeef said:
PS. the qualcomm thing is what appears when it's flashing via USB
Click to expand...
Click to collapse
I figured that's what that was, I was just a little shocked that it said CDMA.
And I tried wiping the card and reflashing, but it did exactly the same thing.

See at the top of your bootloader readout, where it says RUUNBH? That means the RUU flag is set, and that needs to be unset before you can do other things. What you need to do is establish a connection with your device via MTTY. Follow the instructions here about how to do that. Once you get an MTTY connection established with the device (it may take awhile since MTTY is quirky sometimes), type
Code:
Set 16 0
You may need to manually soft reset afterward, but otherwise you should be in the clear

The TMO Stock ROMs can install via PC even if your phone has a faulty USB connection. The stock ROM installer will keep restarting the phone's USB connection automatically as needed if your phone can't appropriately flash in one straight attempt. You can get the newest stock ROM here. And definitely install HardSPL again after getting the phone up and running on the stock ROM.
You might also try MTTY.exe. When connected, run the command 'set 16 0' then 'task 8' then 'task 0'. If your phone doesn't automatically soft reset, then manually soft reset with the stylus.

will MTTY.exe work via parallels on a Mac? I haven't tried it yet, but I have limited access to a PC. also, I tried doing the HardSPL and the TMO rom via PC, but the phone just does the same thing. It will connect, but then the RUU tries to check the phone settings and the phone shuts off. this is the problem i am having. i just cant get it to say on long enough to do anything. I'll try the MTTY.exe through parallels and if it won't respond, I'll have to wait to try it on a PC. I'll let you know how that goes.

MTTY is quirky enough that it probably won't work through parallels, though there's no reason you shouldn't at least try and see if it works. You'll probably have to wait until you can get access to that PC. Best of luck

DaveTheTytnIIGuy said:
MTTY is quirky enough that it probably won't work through parallels, though there's no reason you shouldn't at least try and see if it works. You'll probably have to wait until you can get access to that PC. Best of luck
Click to expand...
Click to collapse
Thanks. I'll have to wait till i get back to the phone but i will let you know how it turns out.
also, in reading your sig, i see that i was using the same SPL that you are. have you had any problems with it?
I was also using the ENERGY LEO ROM [i now see that you are using it too.], which apparently was defective because the next day, the chef posted a new one because of "sleep of death." I read through the thread and didn't see anyone with the issues that i was having.

chasejones8 said:
Thanks. I'll have to wait till i get back to the phone but i will let you know how it turns out.
also, in reading your sig, i see that i was using the same SPL that you are. have you had any problems with it?
I was also using the ENERGY LEO ROM [i now see that you are using it too.], which apparently was defective because the next day, the chef posted a new one because of "sleep of death." I read through the thread and didn't see anyone with the issues that i was having.
Click to expand...
Click to collapse
I haven't had any problems with this SPL, but then again, this is the only end-user version of HardSPL for GSM devices that's been made available. The SPL isn't even your problem, the only problem is that a bootloader flag is set which shouldn't be.
As for the EnergyROM sleep of death problem, that's not what you're suffering from. The sleep of death problem is when your device won't resume after being put into standby, meaning one must soft-reset their Rhodium and lose any unsaved data in open programs. It's a somewhat common problem among many HTC devices, from the old ones like the Kaiser to the newer ones like the Rhodium (though I don't think any Android device has this problem).

jdep1 said:
try flashing hard spl 1.01 it looks like you got an old version of the spl.
Click to expand...
Click to collapse
Eh ? Sorry, but I think you're confused. He's running 0.85 HardSPL, which is the one and only version for GSM Rhodiums.

I got to a PC and tried MTTY.exe
I can't seem to get it to connect. It just says "USB port can not open."
Any suggestions?
EDIT: I can get it to connect to a different version of MTTY.exe for a short time, but I can't type anything. All I get is a blinking cursor.

chasejones8 said:
I was running one of the ENERGY ROMs on my TP2, so it's got a different SPL and all that. I then put it in the box for about 5 weeks. I took it out two days ago to install XDANDROID. I used XDANDROID for about an hour, until the TP2 started randomly shutting itsself off. I've tried flashing NRGZ28's ULTRA LITE ROM and the official T-Mobile USA 6.5 ROM for the TP2. It won't go past the boot loader a majority of the time. When it does, it goes on to act like it's flashing the RHODIMG.nbh on my MicroSD but almost instantly after it starts, it shuts off again. It doesn't always try to flash the .nbh, but when it does, it never finishes. It's the same story with a hard reset. I can't ever get it to turn on, and the only way it does turn on is to do a battery pull. If I'm lucky, it'll stay on for about 60 seconds and then shut off again. I'm really clueless as to what to do here and I'm hoping someone can help me.
The Bootloader reads as folows:
RUUNBH
RHOD210 32M SS-BC
SPL-0.85.OilNex
MicroP(LED) 0x0A
MicroP(KEY) 0x04
TURBO HW/TURBO SW
TP MFG DATA
[unreadable]
812,19...
217.855 Calibrated
The reason 1.5 of the lines is unreadable is because of the message over it: "Upgrade ROM code error. please try again."
http[colonslashslash]farm3[/url][dot]static[dot]flickr[dot]com/2726/4386331314_8036d882a6_o.jpg
Click to expand...
Click to collapse
I had this EXACT same problem a week ago. I fell asleep in the middle of flashing, the phone died when it finished. I woke up, turned on the phone, ENERGY leo was trying to run its install but kept dying. Smart me, I tried to reflash (by holding the vol down button and turning it on- not through usb) and it kept dying in the middle of trying to flash.
The problem is the battery. It can't charge when it's flashing and it can't hold a charge long enough to get past the flash.
I swapped batteries with my friend, restarted the flash and it worked fine.
I let my battery charge in my friends Sprint Hero
and voila, everything went on happily ever after.
tl;dr find a way to use a charged battery while flashing.
your phone's not bricked.

bfgarzilla9k said:
I had this EXACT same problem a week ago. I fell asleep in the middle of flashing, the phone died when it finished. I woke up, turned on the phone, ENERGY leo was trying to run its install but kept dying. Smart me, I tried to reflash (by holding the vol down button and turning it on- not through usb) and it kept dying in the middle of trying to flash.
The problem is the battery. It can't charge when it's flashing and it can't hold a charge long enough to get past the flash.
I swapped batteries with my friend, restarted the flash and it worked fine.
I let my battery charge in my friends Sprint Hero
and voila, everything went on happily ever after.
tl;dr find a way to use a charged battery while flashing.
your phone's not bricked.
Click to expand...
Click to collapse
That's the best news i have heard so far. I don't know anyone with a TP2, but i do know someone with a Hero. I'm assuming the GSM hero uses the same battery as the CDMA Hero and the TP2. I'll look into it and let you know how it goes.

chasejones8 said:
That's the best news i have heard so far. I don't know anyone with a TP2, but i do know someone with a Hero. I'm assuming the GSM hero uses the same battery as the CDMA Hero and the TP2. I'll look into it and let you know how it goes.
Click to expand...
Click to collapse
chin up, bud
I actually had a replacement sent to me.
That took a week. I fixed my phone the DAY AFTER i requested a replacement.
ohwell.
Brand new TP2 for ten dollars (shipping) I'm not really complaining.
&yes. The GSM Hero does use the same battery. I was just looking at my friends phone, decided to take a look at the battery and shat bricks when I saw it fit in my phone.
report back after you try your friends battery if it works or not!

bfgarzilla9k said:
chin up, bud
I actually had a replacement sent to me.
That took a week. I fixed my phone the DAY AFTER i requested a replacement.
ohwell.
Brand new TP2 for ten dollars (shipping) I'm not really complaining.
&yes. The GSM Hero does use the same battery. I was just looking at my friends phone, decided to take a look at the battery and shat bricks when I saw it fit in my phone.
report back after you try your friends battery if it works or not!
Click to expand...
Click to collapse
thank you so much! that fixed everything. they weren't quite the same battery, the one from the HERO isn't quite as wide. it did work, though. I'm charging my tp2 now. not sure if the battery is shot or not. everytime i unplug it, it shuts off. i'll have to charge it for a while and see if that changes anything. again, thanks so much!