Develop Bugs

Device unresponsive no matter what rom?

HI all,
I'm having some fun and games with my Orbit today.
I previously had an old version of black & Blue on there. SO today decided to update to have a go with some manilla based ROMS.
First I Tried YuE_v11.3_3.15.20755_Lite_M2D_WWE
Which seemed to work ok but after a while applications were being very slow.
So then I tried to reflash oop, but that seemed to fail.
I Tried to flash love, but it wasn't ever getting to the progress indicator on flashing, so did an SD flash of YuE which worked.
So then tried to flash Love from that minimal YUE and the device is being really slow, like gets to the calibration and takes about 5 mins to swap between screens.
What's the best way to totally clear down the rom and start again on this?
Thanks

I've now flashed the Official UK O2 WM6 ROM and still having problems. Flashed succesfully, but when it boots up, it just sits on the "Windows Mobile" screen and beeps a bit

Current State after O2 flash :
IPL : 3.04.0001
SPL : 3.04.0000
GSM : 03.06.90
OS 3.4.0.0
Any help gratefully appreciated.
Thanks

Hard reset the device, and while you're in the config wizard, plug in your device and flash to new rom. That way it's completely formatted and you'll have a fresh new install... hope it works mate

I did a hard reset, still no joy, hangs on the welcome to windows screen
I can access the Bootloader, but can't find a way to flash a rom from there, all seem to want it done once you've made an activesync connetion

flash YUE back via SD card flashing

I already tried that, flashes fine, but becomes unresponsive soon after

have tried flashing O2 WM5 + WM6 from SD, but still no joy.
It just flashes, loads up WM(5/6) then hangs there, beeping sometimes. Pressing the green button brings up the calibration screen. I sometimes see bits of apps, today screen, but that's about it, it's generally unresponsive.
Any suggestions?
ta

A little update incase someone can help?
I left the battery out of the phone all night last night, and this morning the phone worked great.. for about 2 hours, then it froze. I hard reset, and it's back to freezing after OS loading now

What's up if you remove your MicroSD card ?

That makes no diff, i've tried flashing with + without the SD card (it's currently out), flashing from windows + flashing from microSD, all ends up the same way, with an unresponsive device once the OS boots.

need urgent help

I had my phone on and it locked up last night. I took out the battery and put it in and the diamond wouldn't turn on.
I plugged it into my computer and the Touch Diamond logo appears for a few seconds, then goes away, then reappears again then goes away. this continues endlessly.
i got my phone to go to the red/green/blue screen which shows my spl number and such. i tried to reinstall a rom, which seemed to work.
after it clears 100% it shows the "touch diamond" logo and redoes the loop mentioned above.
im lost and need my phone badly. any ideas?

CoreGMRConMan said:
I had my phone on and it locked up last night. I took out the battery and put it in and the diamond wouldn't turn on.
I plugged it into my computer and the Touch Diamond logo appears for a few seconds, then goes away, then reappears again then goes away. this continues endlessly.
i got my phone to go to the red/green/blue screen which shows my spl number and such. i tried to reinstall a rom, which seemed to work.
after it clears 100% it shows the "touch diamond" logo and redoes the loop mentioned above.
im lost and need my phone badly. any ideas?
Click to expand...
Click to collapse
Hi
Did you see tri colour bootloader? what are the reading on the tri colour screen?
Without more details we cannot help
Give more details about the spl version and the rom you are flashing
Good luck

diam100 mfg 64m
spl-1040olinex
microp-diam led v11
psox-diam stage_pvt 0x30
i got to here by doing the bootloader button code. it did not just go to tri-coulr
1 more thing. it only will turn on if plugged in.

Well the good news is .....It's not Bricked
Does it say USB at the bottom when plugged into PC?

yes mam!?????

I had this kind of problem with a WINGS. It was a battery fault, not having enough power to fully run the phone at startup. Worked ONLY connected, but with endless reboot. No way to start without connection.
I 've sent the device to HTC (without battery, as usual) and they send it back asking to change the battery. And worked!

sergiopi said:
I had this kind of problem with a WINGS. It was a battery fault, not having enough power to fully run the phone at startup. Worked ONLY connected, but with endless reboot. No way to start without connection.
I 've sent the device to HTC (without battery, as usual) and they send it back asking to change the battery. And worked!
Click to expand...
Click to collapse
i dont think thats the problem. i might put this on the car charger in a bit.

threw it on the dc charger. no luck. i might drive around a bit to get it charged. any other ideas?????

with it turning on hard reset im sure its possible with the device actually turn on try and enter into bootloader mode and flash it to the stock rom...
as i say im not to sure but worth a try.....

to get to tri-coloured screen, just reset and press the volume down key down flash the default stock rom should be fine!!!

I just got to bootloader and tried updating the ROM. it finishes but after install it renters the loop.

fixed!!!!!!! one of the gold prongs on the battery connector was bent. bent it back n it works now.

I told you, It was the BATTERY!

HTC Touch Diamond (Sprint) will not make it past "Touch Diamond" screen.

I am no stranger to forums, or 'modifying' electronics. However, this was my first hack at my Touch Diamond. I went through all the proper procedures to update to WM6.5 (or so it seemed) but now, after installing a ROM
(http://forum.xda-developers.com/showthread.php?t=506533)
the phone only shows the splash screen, then resets and continues to go through this continuous loop. I cannot access the phone, or get booted to the point where I can connect to the PC. Any ideas, as I am sans phone right now. TIA!

Do you flash a hard-SPL ?
Are you sure the ROM's archive isn't broken ?
The connection on the bootloader mode was good, synced with windows?
I think you didn't flash a rom before ? If yes, no problem, if you flash an other rom before, maybe use the MTTY method.

see how this guy could have saved him self time if the thread in my description was stickyed...
MTTY thread... look there. after that ur green to go again.

I do believe people are successfully using the ROM.
The connections were all fine. I had to first install a new bootloader, then updated the radio device (all worked fine). I then went to update the OS, and the process went through just fine, but when the phone booted, it just keeps cycling through the opening splash screen.
My problem is that I cannot get the phone past that screen to do anything.

reb0rn, thank you! The 'boot to flash' was what I was looking for. The 'Volume Down" with "Power On" was what did the trick (I was doing all sorts of other combinations with the 'reset' key).
I'm loading a new version onto the phone as we speak - wish me luck, and thanks again!

Is it bricked? UnSolved AGAIN!

A strange thing happened and now I can't escape the bootloader screen. I lost my phone for a two days and when I found it it wouldn't come on. I connected it to a power cable and it immediately brought up the bootloader. The charge light won't come on but now the phone will power on without the power cable. Problem is it just brings up the bottloader and tries to install the rom image on the sd card. I put a new image on the card reinserted it and then allowed it to reflash. But it still just brings up the bootloader. Any advice?

Try to flash another ROM but not from SD, remove SD and SIM and flash from your PC
Hope it helps,

orb3000 said:
Try to flash another ROM but not from SD, remove SD and SIM and flash from your PC
Hope it helps,
Click to expand...
Click to collapse
Go into bootloader. Plug in usb and flash from your pc. Try if it helps.

Flash with Task 29 first, it may be that corrupted info is still on the rom when you reflash screwing up the loading of the new rom.

orb3000 said:
Try to flash another ROM but not from SD, remove SD and SIM and flash from your PC
Hope it helps,
Click to expand...
Click to collapse
Lennyz1988 said:
Go into bootloader. Plug in usb and flash from your pc. Try if it helps.
Click to expand...
Click to collapse
Reflashed from PC, reboot to bootloader behavior does not change.
ultramag69 said:
Flash with Task 29 first, it may be that corrupted info is still on the rom when you reflash screwing up the loading of the new rom.
Click to expand...
Click to collapse
Flashed Task 29, then reflashed Energy ROM 23569 MaxManila. ROM booted and began setup procedure. Completed setup procedure and there was joy in the land. Installed the SD card and copilot loaded. Turned off phone to reinstall SIM. Turned phone on and bootloader loaded. every attempt to reboot brought bootloader up. Removed SD card and soft reset bootloader came up with error message but all I could read was "RUUUBH" at the top and "...error code" at the end of one line and "...se try again" at the end of the next, the rest was overwritten over the bootloader text.
Removing the SD card, I reflashed the stock SPL, rebooted to bootloader, then reflashed Task 29 and attempted to flash stock ROM, but the computer would not recognize the phone anymore.
Rebooted the phone and replugged into PC computer recognized, reflashed Hard-SPL and then attempted to flash Core EVO ROM (which is when all the trouble started by the way) The ROM flashed and the phone commenced the setup routine.
Was able to setup email and apps and customization and everything was good, left phone in cradle overnight and phone was fully charged this am. Rebooted the phone just as a check and bootloader returned, subsequent reboots always return into bootloader.
What now?

cyberscribe said:
Reflashed from PC, reboot to bootloader behavior does not change.
Flashed Task 29, then reflashed Energy ROM 23569 MaxManila. ROM booted and began setup procedure. Completed setup procedure and there was joy in the land. Installed the SD card and copilot loaded. Turned off phone to reinstall SIM. Turned phone on and bootloader loaded. every attempt to reboot brought bootloader up. Removed SD card and soft reset bootloader came up with error message but all I could read was "RUUUBH" at the top and "...error code" at the end of one line and "...se try again" at the end of the next, the rest was overwritten over the bootloader text.
Removing the SD card, I reflashed the stock SPL, rebooted to bootloader, then reflashed Task 29 and attempted to flash stock ROM, but the computer would not recognize the phone anymore.
Rebooted the phone and replugged into PC computer recognized, reflashed Hard-SPL and then attempted to flash Core EVO ROM (which is when all the trouble started by the way) The ROM flashed and the phone commenced the setup routine.
Was able to setup email and apps and customization and everything was good, left phone in cradle overnight and phone was fully charged this am. Rebooted the phone just as a check and bootloader returned, subsequent reboots always return into bootloader.
What now?
Click to expand...
Click to collapse
reflashed task 29, then reflashed stock ROM, still enters bootloader. note that it says serial on the bottom and that changes to USB most of the time when I plug it in. Also please note that when I remove the battery to power down and replace it and then plug it in it powers up all by itself (without me pushing the power button). This has been the method of rebooting that has been going on, this last time however, after removing the battery and plugging it in the charge light came on (seems to be a good sign). Pressing the power button caused the phone to boot to ROM image, but I'm afraid that rebooting it will result in the bootloader loop. I'll update after it finishes loading Winmo 6.1

this is certainly strange, could it be something with the SPL, i would look into that next if this doesnt help

cyberscribe said:
reflashed task 29, then reflashed stock ROM, still enters bootloader. note that it says serial on the bottom and that changes to USB most of the time when I plug it in. Also please note that when I remove the battery to power down and replace it and then plug it in it powers up all by itself (without me pushing the power button). This has been the method of rebooting that has been going on, this last time however, after removing the battery and plugging it in the charge light came on (seems to be a good sign). Pressing the power button caused the phone to boot to ROM image, but I'm afraid that rebooting it will result in the bootloader loop. I'll update after it finishes loading Winmo 6.1
Click to expand...
Click to collapse
I think you either have a bad battery or a bad TP 2. Try replacing the battery first. You can get a cheap external charger off ebay if you phone doesn't charge.

stevedebi said:
I think you either have a bad battery or a bad TP 2. Try replacing the battery first. You can get a cheap external charger off ebay if you phone doesn't charge.
Click to expand...
Click to collapse
Yeah, leaning heavily on the battery theory myself (although that could be wishful thinking), so I ordered a new OEM one this AM. OK here is the update. WinMo6.1 completed setup, activesync synced up my contacts, did not load copilot (since 4 out of 6 times the crash happened after I reinstalled copilot). Rebooted using the power button, rebooted to winmo.
Rebooted 4 times manually, each time it rebooted to winmo just fine.
Executed hard reset and aborted setup then reflashed task 29
Flashed Energy Rom MaxManila, allowed setup to complete, loaded copilot, and synced with activesync. Everything has been fine for 8 hours. No forced reboots, no lockups. Please note I have maintained battery charge above 50%.
Thanks for the suggestions and keep your fingers crossed.

cyberscribe said:
Yeah, leaning heavily on the battery theory myself (although that could be wishful thinking), so I ordered a new OEM one this AM. OK here is the update. WinMo6.1 completed setup, activesync synced up my contacts, did not load copilot (since 4 out of 6 times the crash happened after I reinstalled copilot). Rebooted using the power button, rebooted to winmo.
Rebooted 4 times manually, each time it rebooted to winmo just fine.
Executed hard reset and aborted setup then reflashed task 29
Flashed Energy Rom MaxManila, allowed setup to complete, loaded copilot, and synced with activesync. Everything has been fine for 8 hours. No forced reboots, no lockups. Please note I have maintained battery charge above 50%.
Thanks for the suggestions and keep your fingers crossed.
Click to expand...
Click to collapse
Fixed! Stable as a rock

cyberscribe said:
Fixed! Stable as a rock
Click to expand...
Click to collapse
Premature, OK I've been rocking just fine and bamm out of the blue the problem reemerged. OK I say to self no biggie MUST be the battery and the new just came in the mail today so I say self change battery, no help. Bootloader loop here again. Help someone please!

cyberscribe said:
Premature, OK I've been rocking just fine and bamm out of the blue the problem reemerged. OK I say to self no biggie MUST be the battery and the new just came in the mail today so I say self change battery, no help. Bootloader loop here again. Help someone please!
Click to expand...
Click to collapse
task 29 got me to the rom splash screen

cyberscribe said:
task 29 got me to the rom splash screen
Click to expand...
Click to collapse
reflash ROM from PC not SD. Reflashing after that from SD works. Hope I don't have to do this every time I change a battery!

I think I may be having the same or a similar issue as you cyberscribe. All of a sudden, I am getting restarted into the bootloader too.
I was using an older NRG 2.1 ROM (April-ish) and had to pull the battery after it froze up. Nothing new, it happens. The new part is that it would only restart into the bootloader screen. I thought it might be the older ROM, so I Task 29'ed and flashed NRG's newest 2.1 June 2nd ROM.
Successful boot and ROM setup while connected to USB. Unplugged USB, restarted phone, BOOTLOADER.
Plugged in USB, successful boot.
Unplugged USB, BOOTLOADER.
Plugged in wall outlet, successful boot.
Unplugged wall outlet, BOOTLOADER.
Obviously, I can conclude that there is an issue with trying to boot on battery power, or at least while not connected to a power source.
Anyone ever have this happen? Or have any ideas why this would be happening? I really don't want to have to find a power source every time I need to restart my phone, haha. I am still trying to troubleshoot further and will update if I find anything else worthwhile.

Also last night I tried restarting while plugged into car adapter, which as expected booted fine every time.
However, this morning I just restarted on battery power and it booted fine also. Nothing changed from last night to this posting. Honestly, I am completely at a loss as to why I am getting restarted into the boot loader seemingly at random. I thought I had it nailed down with the power source, but now that apparently is not the issue.
cyberscribe, are you still having issues? Anyone else ever have this problem? Any thoughts on a cause or solution? Or anything to help troubleshoot?

After the bootloader first pops up, there is a very quick screen that flashes, "Loading.... No image file", then goes back to the bootloader screen.
I have to discount my earlier theory that it will always boot when connected to any power source. Now it will only boot when connected via USB to the PC.
Looks like I am going to have to re-flash the stock ROM and then stock SPL and see if this solves the issue. Then, if not, I guess a warranty claim is in my near future.
I really wish we could have gotten some replies from smarter people than myself in this thread. haha

Finally flashed back everything to stock (SPL, radio, ROM) and still having the bootloader issue, looks like it is going to be a warranty claim after all.

Sounds more like a memory issue if it can't find the image file. If you both got your Rhodiums from the same carrier it could be a bad batch of phones...

Same issue on my tilt 2 just cropped up today. If I am reading the above correctly it sounds like 2 tilts and a t-mob rhodium having the issue, so different carriers. =/
Soft reset the handset and set it down, picked it back up and it was in bootloader. All attempts to get it out of bootloader (reflashing from sd, pc etc.) seem to complete just fine, but upon reboot dump into bootloader. May be a different problem than OP as I havent had any success in getting a boot after reflash.

Not sure if I am having the same problem, when I try to turn on it just comes up with the Touch pro 2 screen with the red text in the bottom left hand corner, I am using an energy Rom again from about April, I have tried re flashing but pc wont recognise/find phone, Wha acn be done?

Another M9 bootloop

Hi everyone, had the phone for few years, one day it died and never booted again. Nothing was flashed at the time, my son was using it and I read that some phones, if they got hot enough playing games, the nand will get erased and the phone is borked.
All I get is the white HTC screen.
If I hold the volume + and - I will get to the screen attached.
If I select download mode, the phone will reboot and a black HTC screen will appear, but then the phone will reboot after 1-2 seconds, back to the white HTC screen.
Same with bootloader mode.
I have downloaded 0PJAIMG_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.30.617.2.zip and copied it to a 32GB sd card, and tries to get it to flash via download mode using the process above, but nothing happens and the phone reboots within 1-2 seconds.
Is there any way I can revive this phone? or just throw it in the trash?
Thanks!

shpitz461 said:
Hi everyone, had the phone for few years, one day it died and never booted again. Nothing was flashed at the time, my son was using it and I read that some phones, if they got hot enough playing games, the nand will get erased and the phone is borked.
All I get is the white HTC screen.
If I hold the volume + and - I will get to the screen attached.
If I select download mode, the phone will reboot and a black HTC screen will appear, but then the phone will reboot after 1-2 seconds, back to the white HTC screen.
Same with bootloader mode.
I have downloaded 0PJAIMG_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.30.617.2.zip and copied it to a 32GB sd card, and tries to get it to flash via download mode using the process above, but nothing happens and the phone reboots within 1-2 seconds.
Is there any way I can revive this phone? or just throw it in the trash?
Thanks!
Click to expand...
Click to collapse
Don't trash it yet!
Do you have a custom recovery?
If not you can "RAM" boot TWRP. While in the bootloader screen do this:
Code:
./fastboot.exe boot twrp-3.0.2-0-hima.img
Then with MTP enabled you should at least be able to look at your files (assuming not HOT deleted like you mentioned).
There's something called "RUU" we can try next, it's a (HTC) way to bring your phone back to stock. But try to save your files first!

Thanks, I will give it a try.
I don't care about any data on the phone, just trying to make it function again.
I let the battery drain over-night, I'll see if I can do anything with it.
Thanks for your input!

Note it doesn't look like the RUU files are hosted on HTC anymore.
Here's the full filenames I have downloaded and used in the past.
- RUU_HIMA_UL_M60_SENSE70_TMUS_MR_TMOUS_3.39.531.7.exe
- RUU_HIMA_UL_N70_SENSE80_TMUS_MR_TMOUS_4.27.531.6
A quick google should let you find them but a little frustrating to not get it direct from HTC (security risk anyone?).

I was messing with it last night, after I let it completely drain it won't charge anymore. If i connect it to a charger, or to a pc, it will turn on for 1-2 seconds, then turn back off, and do the same again and again.
Thanks for your help but looks like I can't do anything to it at this point. Not sure if the battery can be charges externally.