Hello, I am new to this site and the whole BA experience. I got my sx66 about a week ago and decided to upgrade the ROM to 1.33.51. Yes, from what I've gathered from reading it is also a little out of date, but I was trying to start out small. Well, at some point things went terribly wrong, everything seemed to be well, when all of a sudden my screen went blank and I was left with a screen that just says serial at the top and v 2.07 at the bottom. I have left the battery off for about 20 hours now, waitting on the backup battery to die(from what I understand my phone may be stuck in bootloader mode and this should fix it) Well, I just got home from work and the phone still says the same thing if I put the battery on. Any help or suggestion would be appreciated or even just a "Hey, your phones gone" would be as well, just curious to know what to do. Thanks!
Yes, you're in bootloader mode. It's now ready for upgrade.
If you put it in cradle, it will change from 'Serial' to 'USB', run the upgrade and do the (Record,Camera) reset with 'no,yes,yes' and press 'Mail' button.
Most of these are in the Wiki.
Yes,
Note: I have had HardSPL, Olipro, etc for ages, and have been flashing roms in the 81, 85 and now 89 series for years.
An odd issue: I had the RyanCPPR v4 Rom in my Tilt, and the multi-color bootloader screen popped up and froze in my Kaiser, Soft, Hard and Battery Resets ensued, but nothing worked......after multiple tries, it reloaded....
I figured a corrupted Rom and tried the new Friday13thV7Diamond....voila...same problem......try, try, try again, and finally it loads....
But, I don't know what is going on. I would guess a radio issue as it stayed from Rom to Rom, but, this not being my area of expertise, wanted to get some thoughts from the big boys.
Anyone?
Thanks, G
Some more info -
Come on people, throw me a friggin' bone here...I know there are a dozen reasons this could be happening, so I'm not abut to run MTTY and start throwing in commands , no matter how much searching I do without some guidance.
On the bootloader, we have:
KAIS1*0 MFG
SPL-1.0OliPof
CPLD-8
MultiColors and at the Bottom
Serial
PPS: Problem began when Opera 9. whatever froze the Device (IN THE LAST ROM) and I softreset-ed. But this could be coincidence
Thanks again,
G
PS: Mystery Continues: Removed Sim - Booted. Let's see how long this lasts.....yup, Looks like sim is affecting it, though it has booted with the sim before.
Thoughts?
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!
Hi All,
While on a business trip last week, my Tilt 2 (at the time, running the April 14 Energy ROM), my phone--for lack of a better word--crashed on me.
Everything had been working fine, I was sitting there with my phone connected to my laptop via a USB cable, and out of the blue, for no apparent reason, my phone re-booted, and never came back up. It would get to the splash screen, start loading the OS, reboot mid-stream, and get stuck in a loop. Weirder still, if I pulled the battery, let the phone sit, then put the battery back in, hitting the power button did nothing--even with the phone plugged in to power. On top of that, even if the phone was off, after a few minutes, it would power itself back on randomly, and get stuck in the re-boot loop. Very weird.
So, when I got home, before heading to the AT&T store and asking for a replacement, I thought I'd try to restore the phone myself.
At first, I pulled the battery, then stuck it back in, and sat there holding the volume down button, waiting to put the phone into bootloader mode. That worked, but even in bootloader mode, it would randomly re-boot. So, I started the process again, and immediately plugged the phone into my computer while in bootloader mode and ran the Task 29 tool. That completed properly.
At this point, I popped in another battery I had laying around and just let the phone charge for a few hours. Then, for the heck of it, I re-ran the HardSPL tool. Re-Flashed to the .91 radio (it was already on the phone), and then flashed to the latest Energy ROM.
Since then, my phone has been better than ever. Seems faster, battery life is better (Went three days without having to charge it), no dropped calls, and no weirdness with the latest ROM (that I've found so far).
Does it pay to REALLY start fresh from time to time, and re-flash everything on the phone?
Thanks for any input.
I have no idea, but hopefully the WinMo experts will see this and have an idea, so here's a bump for you. Most of my computer expertise revolves around Unix, Linux, and a bit of Windows, not so much these phones.
I do know that task 29 is awesome, though. It seems like DBAN for your phone...
DBAN=Darik's Boot and Nuke. Look it up.
I don't know what happened with your phone, sounds like something broke in the area of booting.
I don't think you should need to re-flash HardSPL radios just for the sake of it, but I'd strongly recommend task29 every time you flash a new ROM.
bricked my TP2
My TP2 seems to have a similar problem which I haven't been able to fix it just yet. The bootloader reboot loop is too short to succesfully run task 29 and flashing it using the microSD gets stuck around 40%
during bootloader mode there's an unreadable errormessage since it's on the same line as some of the usual information.
any thoughts/suggestions would be very welcome since i can't afford to send it to the factory.
cheers.
By the way my phone is a HTC Pure, that was security and sim unlocked, at the time it went down was running the latest Energy.TOPAZ.29022.Sense2.5.Cookie.2.0.GTX.Jul.04.7z ROM. With no recent updates or installs.
Ok my phone was in my pocket for the morning and when I pulled it out it was dead and wouldn't turn back on. Plugged it in to charge and once charged it will only boot to the white screen with the little red numbers in the bottom. It takes very little time to get to this point and once here it is unresponsive to any buttons pushed. I can leave it like this and it will just get hot and wear down the battery, I have only left it like this for ten minutes, just to see if it would come out of this stage.
After searching and reading all the brick / won't boot posts I could. I tried to hard reset, which works and I can get to the bootloader screen(striped screen). Then re flashed to the newest hard spl and have flashed three different versions of Energy, currently trying MaxSense. But nothing has gotten it past the boot screen. All flashes were done with the USB through my computer and the SIM and SD cards have not been in it.
I just don't get how it bricked in my pocket, it had worked fine for a month on the same Energy ROM with no issues and I had not downloaded or installed anything new recently.
Just miss my phone now, any help would be greatly appreciated.
Did I post this in the wrong area? 3 days 50 or so views and nothing, this sucks!
I take it this is the wrong area for this post as it has gotten a few views, but no responses. I should probably move it and see if that helps.
This sucks and I am disappointed, I'm done with this post, I give up!!!
I have a paperweight for a phone and I hope no one else has this issue, because no one on here can help.