Develop Bugs

MY XDAII is stuck in bootloader mode

Help, my device pda2k is stuck in bootlader mode
All I see is a grey screen with a serial number on top (or USB when the device is placed in the cradle) and on the bottom I see V1.06
I have tried a hard reset but nothing.

reflashed and use the "HimaUpgradeUt_noID.exe"
jojo

I am a bit of a dummy.
Where can I find HimaUpgradeUt.noID.exe???

The link is in xda2jojo's signature.
Cheers!!

XDA EXEC stuck at spalsh screen after flashing

Hai ,
I tried different flashes of WM6 , then i reverted back to wm5.
But then again i flashed it with wm6 rom.
It flashes it successfully but after hard reset , pressing 0 , it just stays at splash screen giving infos in red.
I am stuck at spalsh screen ... any ideas ?
Also tried uni_exitbootloader .. but still stucks at splash screen
Tried Refalshing it many times but same ..

babablacksheep said:
Hai ,
I tried different flashes of WM6 , then i reverted back to wm5.
But then again i flashed it with wm6 rom.
It flashes it successfully but after hard reset , pressing 0 , it just stays at splash screen giving infos in red.
I am stuck at spalsh screen ... any ideas ?
Also tried uni_exitbootloader .. but still stucks at splash screen
Tried Refalshing it many times but same ..
Click to expand...
Click to collapse
Try enter bootloader and re-flash WM6 Rom, if it still fails to boot, search the Universal forum for MTTY commands to reset partition tables. I suspect the partitions are corrupt.
Hope youre battery is not too low.
Cheers,
Beast

babablacksheep said:
Hai ,
I tried different flashes of WM6 , then i reverted back to wm5.
But then again i flashed it with wm6 rom.
It flashes it successfully but after hard reset , pressing 0 , it just stays at splash screen giving infos in red.
I am stuck at spalsh screen ... any ideas ?
Also tried uni_exitbootloader .. but still stucks at splash screen
Tried Refalshing it many times but same ..
Click to expand...
Click to collapse
Something like this happened to me when I first flashed my Universal, I tried something in the Wiki (Cannot remember?) That told me to use that usb port from now on for all flashing. After that it worked. I will search further to see if I can help...

Okie Problem Solved.
I did this to get myself sigh if relief.
100% working
1. Take out the SD and SIM cards
2. Opened ActiveSync and go to file, connection setting and Un-check "Allow USB Connections". Then press Ok and close ActiveSync
3. Put in bootloader mode (Power + Light + reset) which brings up the "un-backlit" screen with "Serial" at the top and v0.XX at the bottom
4. Plug in USB cable DIRECTLY from PC to Jasjar (MAKE SURE NOT TO USE A USB HUB). You MIGHT then see a warning window complaining that an "Unsigned" device driver is being attempted to be installed. You will be prompted to either "STOP INSTALLATION" or "CONTINUE ANYWAY" - this warning can be safely ignored and so just click on "CONTINUE ANYWAY".
5. Open mtty utility / software
6. Select USB from the "Port" drop-down on the upper left corner of the dialog box and hit OK
7. Then another screen will come up. Hit enter and that will show "USB>"
8. Type "task 28 55aa" and hit enter. {type it manually/ don`t copy and paste commands}
9. use the "Original OEM ROM" that is made for your device and update with it (CE,Extended and Radio) Flash all
10. Hard Reset
Also if your device bootloader version is lower than "v 1.01" you should update that first (before installing the OEM ROM, but NOT before "Task 28 55aa").
After this is complete you may then use your device again.
NOTe : I find you must kill the wcescomm, wcesmgr and rapimgr exe's using task manager before you get the 'usb' option in mtty (kills activesync)

Please,
what to do when there's no USB port in mtty (only COM1 and COM2) ?????

babablacksheep
must say -Thank you!

vjj said:
Please,
what to do when there's no USB port in mtty (only COM1 and COM2) ?????
Click to expand...
Click to collapse
You must disable ActiveSync before connection
and put in bootloader mode (Power + Light + reset) BEFORE run MTTY
after USB must appear in drop-down menu
one more time thanked babablacksheep

My Dash stuck on the red,green,blue screen (please help)

Yesterday, I tried to upgrade my T-mobile Dash ROM to WM6.1 ROM by kavana. I downloaded and ran both the SDA application unlock and the Excalibur USPL - Cid Bypass. After I completed all the steps, I run the upgrade ROM but it failed at 4% with error 270. After that, I turned the phone off and turned it back on; however, it now stuck on the red(ONBL1.10.0000), green(SPL1.10.0000), and blue(IU) screen every time I turned the phone on.
After I searched using the search function in this forum, I found several solutions, but none of them work for me. I tried to do hard reset (pressing soft buttons) with no success. I also tried to flash the original T-mobile WM5 ROM with no success(error 260) even though the phone is already connected to the PC. My computer cannot read the phone, but the USB indicator on the bottom right corner can detect there is a mobile device connected to the pc.
Is there anyway that I can do to repair my phone?

Same problem here.
On normal boot I get the HTC logo and nothing else.
Hard reset doesn't work.
I can enter the bootloader (Camera+power) but have attempted to flash several roms all failing.
Any suggestions please?
Thanks to all

[Q] Bootloader nightmare

I have a nordic HTC Touch Pro 2
This unit started acting up after I installed the Energy ROM from the 20th of December. It used to fail in booting occationally(fixed by attaching USB-power), but now it is thouroughly stuck in the bootloader.
This is what I see when I reboot:
RHOD100 32M SS-BC
SPL-0.85.OliNex
MicroP(LED) 0x0A
MicroLED(KEY) 0x04
TURBO HW/TURBO SW
TP MFG DATA
509,521 792,844
795,200 221,198
226,843 Calibrated
Serial (changes to USB when connected)
There is a quick flash of 2 previous screens, one tri-color and one saying something about no image to load.
I belive, but would be thrilled to be proven wrong, that I have tried all tricks.
Running Windows 7 I first disabled device driver signing and loaded the HTC USB driver. Downloaded mtty 1.42, connected to the phone via USB and ran "boot" command.
The only problem listed was one bad block in CE.
Tried reboot again with same error.
"info 8" revealed that the bad block is 370.
Ran "task 29" but it gave an error trying to delete block 370.
Rebooted and tried to flash latest 29007 Energy ROM. No errors reported during the flash, still when it rebooted after reaching 100% it stopped in bootloader again.
I have also tried this procedure and replaced the Energy ROM with the latest original nordic ROM. When I use "boot" command from mtty I get the HTC screen (white background with htc in green letters) but the phone apparantly is stuck there. A soft restart brings me bach to the bootloader again.
Is my phone bricked? I'm not sure what to do or try next and as I have seen others report my battery is draining and will not charge(no light) when plugged in to computer or charger.
Thanks in advance, I love what you all do for this community and wouldn't have still used tha TP2 if it wasn't for all the great ROMs presented here!

NVM, re-read and see you already tried my suggestion.

Additional info
I ahould add that I also can't do a hard reset. Pressing and holding send and end and then power button only result in getting the bootloader menu. I borrowed a freshly charged battery and tried loading a new ROM, but no change, it still only restarts to the bootloader after completion.

If you can get into bootloader and the usb shows when plugged in, you should be able to flash back to stock via RUU.

Try this;
Open your downloaded ROM with unzipper. You should see two files, the RUU and the RHODIMG.nbh. Copy the .nbh onto the root of your SD card. Powerup the device holding the volume down. It should boot to bootloader and immediatly look for and find the .nhb and install it.
Hope that helps.

Hi!
Thanks for your answers! Sorry about the late reply!
I tested with RHODIMG.nbh file(29007 Energy) on the SD-card. The installation started and ran as expected. When done the screen showed the following info:
"RHODIMG.nbh - OK
OS - OK
Update Complete
UPDATE SUCCESS"
There were no button to press on the screen, and pressing the power-button didn't do anything. I eventually removed the battery, reinstalled the battery and pressed the power button. Unfortunately for me I was once again presented with the bootloader screen.
Any ideas to a new approach? I really don't want to write off the phone as bricked, it should have about a year left in it before I consider replacing it.

Try this:
When powered off, attach headset to the phone. Then press power button.
My Touch Pro2 ran into the same situation recently, showing nothing but a 3-color screen with the same information as you listed. I haven't tried mtty but I found if I plug in the headset, it boots normally. No idea why...

It sounds like an error in the instruction set for the bootloader. Maybe cmonex can help you with a bootloader-friendly version of Hard SPL to re-flash.

cajunflavoredbob said:
It sounds like an error in the instruction set for the bootloader. Maybe cmonex can help you with a bootloader-friendly version of Hard SPL to re-flash.
Click to expand...
Click to collapse
he already has Hard-SPL so he could just reflash it with the Hard-SPL exe in manual mode, but as the version number is the same, the device may skip the updating of the SPL. if the OP wants to try this, I can make one with a different version number. though I seriously doubt that the issue would be fixed that way...

Headset trick
Hi,
Again, thanks to all that try to help me!
I tried the headset trick just now and look and behold, it actually worked! My limited brain can't come up with any plausible explenation but I'm happy anyway
I do remember reading about this trick at some point, but I couldn't locate a headset until today. Thanks lilei105!
Now I will reboot the unit several times to ensure this wasn't just a coincident.
Edit: Booted 4 times, still no problem. Have booted both with and without USB-cable connected to PC.

Yeah my advice would be re-flash it or install/download a different ROM.

i may be way off here, but could it be a problem with the volume down button on the unit? maybe the headset bypasses the standard volume button?

[Help] Stuck in Bootloader "serial" mode. Not sure how to flash from here.

I did some searching, but I was unable to find directions how to fix this.
So my phone is now stuck in "Serial" mode. There are a Red/Green/Blue/White horizontal bars going across the screen. It says:
Code:
RHOD300 32M SS-BC
SPL-0.88.0000
MicroP(LED) 0x0A
MicroP(Key) 0x04
Turbo HW/Turbo SW
TP MFG DATA
521,530 822,850
818,208 216,211
224, 853 Calibrated
At the bottom of the screen, it says "Serial". If I hook it up to my computer via USB before turning it on, the bottom stays blank.
So I did some searching, and I take it my phone lost it's ROM. So I need to flash it, right? I "found" a stock image, but it was in an executable. I extracted the EXE but am now faced with two different .nbh's. One is called "RUU_Signed" and the other "SPL_signed".
From here I have two questions:
1) Can I still flash via microSD?
2) Which .nbh do I use? Alternatively, if someone can point me to the proper stock .nbh that would be great. I searched but could only find it wrapped up an executable (RUU?).
Thank you for your time.

Grab an energyrom. While in bootloader and plugged into yer pc run the energy custom ruu. Should install just fine for you.

Trying that now. It doesn't seem to be working, the phone is stuck on the "loading" screen. My SPL isn't unlocked, don't I need an unlocked SPL to load a custom ROM?
Edit:
Apparently my problem with getting the phone to connect is that I didn't have WMDC installed. Did that and now I can update. Tried the stock rom. The update went through perfectly, but it didnt' take. When it boots it boots into the boat-loader.

I'm sorry I assumed you. had already unlocked the spl. Get the hard spl unlocker then flash The stock rom