Helmi's AKU 3.5 ROM was installing at that time and it was interupted by a 101 connection error. I disconnected the Universal from the USB and I was seeing the bootloader screen where it only shows Serial and 1.00. I tried to press the reset button. It still went back to the bootloader screen where it shows serial and 1.00. Next i tried to hard reset the device by pressing - & - & reset. I was given two options of 0 & X. First time i tried X and it still went back to Serial and 1.00 bootloader screen. Then i tried to hard reset again and this time i selected 0, it cleared the device and it went back to the bootloader screen. . Then i tried installing Helmi's ROM again. Well it wouldn't work because the USB mentioned it as an unknown device. I tried mtty but mtty wouldn't list a USB port in the dropdown list. All i saw was COM ports. Next i tried it on another computer and it still would not work. Tried to update the bootloader but same 101 device not detected problem.
reflash your bootloader
Oh nvm this thread post. I got it fixed. It was my USB cable that was faulty. All the pins in the USB cable were not hitting all the pins USB port. I used another USB cable and it works now. I guess this post helps all zombies like me.
Related
While upgrading my XDAII to the new O2 rom, I got a connection error which tiole me to disconnect the xda and do a soft reset.
I did this and it's now stuck on the O2 boot screen and wont budge, wont connect via active sync and does nothing else when I hard reset.
Have I f**ked it up ??
Please help,
Tommy
Don't panic
Just reset the device, place it back in the cradle and re-run the upgrade. It doesn't require Activesync as the upgrade process looks after its own connection.
Make sure the cradle is connected directly into a USB port on your PC and not to a hub. Also make sure the power supply is connected to the cradle.
Thanks, but that doesnt seem to help, the program just says that their is no connection.
Do you have another PC you can use? or try using a different USB port.
tried it on both and nothing, It looks like the XDAII can't start up properly and that's why it can't establish a connection. As I said it's stuck on the O2 boot screen (the one with the bubbles on it) with the version nos at the bottom and does nowt else.
I feel sick...
Tommy
OK. I misunderstood. I thought you were in the bootloader screen. So you need to see if you can put the device into bootloader mode. Press the jog button (bottom middle front of device) and power button at same time whilst pressing the reset button. This (hopefully) will put you in the bootloader - a dark screen with Serial 1.xx displayed. Then when device is put in cradle it should change to USB 1.xx. Then you can re-run the upgrade.
Whayhey
DCS you are indeed the man!
Thanks for your help.
Tommy
i flashed my touch diamond with a cooked rom every thing went well untill 1st reboot after completing the flash then black screen with diamond touch logo and nothing i have tried soft reset many times usb cable is not detectable then i tried the program ECShift.exe
when i write ECShift.exe -bl in cmd it says "could not open EC!" so i can not use mtty please help what i can do with the device is it now broken for final or it can be repaired since i can not log in to bootloader
also when i switch it off and put the usb cable it indicates that it is recharging but when i try to turn it on it doesn't start and if i unplugged the usb cable now it still gives me the indication for recharging (whispering light)
usb is not recognized even when making hard reset without formatting the internal storage i get the colored screen the the 3 choices so fast even the diamond does not detect it is connected to pc it suppose to give me a screen writing usb
hi i have the same problem with diamond! you can fixed?tanks
Help pls i have olinex 1.40 hardspl in but my phone is stuck in bootloader with "upgrade ROM code error Please try again" i cant get out...tried hard reset nothing...tried recovery mode (volume down + reset ) nothing...cant get a usb connection help!!!!!!!!!!!!!!!!
are you sure you don't have usb connection? try running an ruu with usb plugged in see if it runs. it sounds like you tried to flash a radio from another device. try flashing a new radio.
Blazeitup123 said:
are you sure you don't have usb connection? try running an ruu with usb plugged in see if it runs. it sounds like you tried to flash a radio from another device. try flashing a new radio.
Click to expand...
Click to collapse
the bootloader shows usb when i plug it in and serial when i plug it out...when hard resetting it goes through the formatting but then just jumps back to bootloader with the message...active sync recognizes nothing but i'll try that right now
edit - ok it seems to be flashing i'm crossing my fingers
edit: ok it seems to have flashed i see my rogers main screen thank you soooooooooooooooo much
glad to hear!
just so you know you can always flash from bootloader. i have seen alot of people around here saying "oh no, my device is bricked and i'm stuck in bootloader". i lol.
Blazeitup123 said:
glad to hear!
just so you know you can always flash from bootloader. i have seen alot of people around here saying "oh no, my device is bricked and i'm stuck in bootloader". i lol.
Click to expand...
Click to collapse
lmao now i know..i was coming from an elfin, not used to diamond as of yet but now i know
Bootloader bottom says "serial" but wont switch to "usb"
Perhaps this is a known issue but I could not find the solution easily and ended up discovering it myself so wanted to share it in case others face the same.
I was try to use the mtty software to "clean" my touch diamond in an effort to get rid of some bugs in macadam 1.2 rom [great rom, by the way].
I had disabled the usb connections in active sync on my laptop [mac running windows xp in bootcamp]
I could enter bootloader easily but the bottom part of the multicolor screen kept saying "serial" and would not switch to "usb" when I connected the phone to the laptop.
What finally worked was ensuring that the phone was set for "activesync" rather than use as a "disk drive" or "internet sharing". I had assumed, wrongly, that once in bootloader the last selected option [disk drive] would be irrelevant.
So I exited the bootloader by pressing the reset key; connected phone to pc via cable; selected the active sync option; disconnected the phone; entered bootloader, connected the phone via cable again and the bottom of the bootloader changed to usb and I was able to use mtty successfully.
I wonder if this has implications for people stuck with bad flashes etc. In my case I could easily exit the bootloader and go back and select 'activesync' from the working phone. One could also hard reset if a working rom was on the phone...
BUT If one is stuck with the option of only the bootloader, would it matter on what the last selected option was [active sync or use as usb disk drive or internet sharing]?
faisal said:
Perhaps this is a known issue but I could not find the solution easily and ended up discovering it myself so wanted to share it in case others face the same.
I was try to use the mtty software to "clean" my touch diamond in an effort to get rid of some bugs in macadam 1.2 rom [great rom, by the way].
I had disabled the usb connections in active sync on my laptop [mac running windows xp in bootcamp]
I could enter bootloader easily but the bottom part of the multicolor screen kept saying "serial" and would not switch to "usb" when I connected the phone to the laptop.
What finally worked was ensuring that the phone was set for "activesync" rather than use as a "disk drive" or "internet sharing". I had assumed, wrongly, that once in bootloader the last selected option [disk drive] would be irrelevant.
So I exited the bootloader by pressing the reset key; connected phone to pc via cable; selected the active sync option; disconnected the phone; entered bootloader, connected the phone via cable again and the bottom of the bootloader changed to usb and I was able to use mtty successfully.
I wonder if this has implications for people stuck with bad flashes etc. In my case I could easily exit the bootloader and go back and select 'activesync' from the working phone. One could also hard reset if a working rom was on the phone...
BUT If one is stuck with the option of only the bootloader, would it matter on what the last selected option was [active sync or use as usb disk drive or internet sharing]?
Click to expand...
Click to collapse
This doesn't make any difference. When you're stuck in bootloader just plugin your USB and the display will state "USB" as well. You can flash a rom at this point.
I've installed some ROMs before. Today's one, stucked at 20%, only possibility was to reset device. And - there is problem, after reseting I've chosen (by mistake) option by which phone memory should be erased. So now I got clean Internal memory, and no diamimg.nbh on it, so I don't know how to bring diamond to life.
Any help?
jusr make a reset with vol down pressed to enter bootloader mode, connect to computer and flash any rom with diamondcustomruu+.nbh file of the rom
Will diamondcustomruu see my phone if it can be started only in BootLoader mode? I'm connecting my phone in this mode to PC, however customRRU doesen't see it (windows does - it's recognized as qualcomm) .
EDIT: As for now, only possibility i see is connecting phone to USB host : http://wmpoweruser.com/?p=490 . Any other ideas?
EDIT2: OK. I've unchecked USB connection in ActiveSync to connect mtty. Flashing right now.
EDIT3: It did work. Diamond is alive. Problem SOLVED.
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?