Develop Bugs

How to get into Bootloader

Hi there!
What key combination gets me into the bootloader?
I've been wondering and searching for a way to upgrade my MDA pro rom. (searching for hours on xda, google and a lot of other specialized sites. Turned out to be dead ends! FRUSTRATING!
I'va had a Qtek S100 before. There was a way to get into the bootloader. And there is a way into the bootloader for the Universal to! YES!
But when i try to push the buttons
on/of
Camera
reset button
i cant get in!
button 1 and 2
reset
the same problem.
I get as far as the pres 0 or X for factory default and exit.
Who can help me? I have the no_id upgrade utility and the ROM ready.
Was there a UUL file which i had to edit before using this upgrade method?
I hope there wil be a good tutorial for this just like the one i have used to upgrade my S100 to an orange rom. (worked great!)
Can anyone help me please

Its BACKLIGHT BUTTON + POWER BUTTON + RESET HOLE
It's better to do this without the SIM and Memory Card connected. Disconnect also the USB Sync Cable.
After entering bootloader, you will see SERIAL written on the screen but the screen has no backlight so you have to look hard.
Then when you plug the Sync Cable, the SERIAL will change to USB then you can run the NoID to update.
Remember the NoID has to be run twice in a row as the first time usually solicits an ID Country error

It Works
Thanks Jorge!
Just those keystrokes helped me a lot. It works just fine and it took me only one run to Initiate the upgrading.
Thanks a lot!
I followed your advice and removed the SD and the phone card.
Yes! now i can experiment with these ROMS.
First Jasjar, later O2 and hoping for the best roms with the best programs.(hoping to find a messenger cab file in the jasjar rom)

As I am planning to do the same, Try all the variants of the ROM's, could you inform me what are the good and bad points of all the different ROM's you used and which did you decide to use finally.
Thanks

HELP !!!!
I turn on my Qtek 9000 and i see SERIAL written and the screen but the screen has no backlight.
How can I boot my Qtek 9000 again without this SERIAL mode ????
Best Regards

Hi Ecraseur,
if You did not do anything else (no upgrading), try ColdReset : Power-switch + Reset hole.
Ruud

If we can boot from Serial/USB is it possible to boot from Mini SD? I'm toying with the idea that by using a Linux Live Disk content on a Mini SD it may be possible to boot into a virtual Linux environment? I know it's going to be uber slow and may not even work but I thought it may be worth a look?
If a Mini SD boot isn't possible do you think it'd work to have one of the smaller USB bootable Linux flavours as the USB boot for the HTC Wizard etc?

My grey screen says USB v2.07 I think I killed it!

My grey screen says USB v2.07. I tryed to update the radio to 1.13... I copied the EnterBl.exe over to the Siemens SX66 and executed it. It blinked and then turned off. Then it came back on and displays USB when on the cradel and Serial when removed. I cannot get it to do anything now. Does anyone have any advice?
Thanks,
Bobby
Cingular
Siemens SX 66 ( I have no idea how that translates into blue angel)

same here
if some one has a sulotion please send me instruction or a mail [email protected]
thnx

you are stuck in bootloader mode. just run the setup for rom upgrade/restore for your device and it should work. I think a hard reset will also allow it to reboot into normal mode, but not sure.

Defiant XDA
I cannot seem to get it to reset nor be recognized by the computer when it is placed in the cradle. It will chime as it is placed in the cradle, yet the charging light no longer ignites and the hot-sync program on my WinXP pc does not indicate that they are connected any more.
Thank you for your time!
Bobby

restore the original ROM. I had this issue after I run a defrag on my "Storage" folder using Storage Tools. I could not reset it. Also, upgrade with higher ROM did not work.
You have to restore / setup using original ROM version. Good luck!

Follow this link, download the update and follow through the instructions.
http://t-mobile.iris-global.com/download_manager_mda_3.html

original rom
Does any one has the original rom for the ph20b my son messed it up
\if any one can send it via email or a link will be helpfull
thnx

Another Possible Solution...
This has happened to me numerous times when upgrading to various ROM versions and through experimentation I finally realized that it was related to my storage card. I also remember reading another post like this where this problem can occur if the storage card is on the large side (>= 1GB ).
Just take out the card and reconnect to the cradle and you should be able to flash again.
Hope this helps

XDA EXEC Upgrade problem

Hi,
I was updating my o2 xda exec with new rom upgrade when my PC crashed causing upgrade to unexpectadly stop. It is now stuck on a grey screen with the word serial on top and v1.00 down bottom. I have tried hard reset but to no avail. My pc wont recognise it at all now. Any suggestions or will i have to leave in to be fixed
Thanks for any help
Bily

This happened to me the first time I flashed my Alpine. Just put the device in the cradle, load up the flashing program on your PC and just start over, it *should* just see the device and carry on fine. It did for me, and I did nothing special except reboot and cross my fingers.

done that but it stops saying problem with country ID error. It is unlocked but is a UK model

Someone else on the forum was experiencing the same problem... To be quite honest, I haven't the foggiest idea as to why this is happening, it never happened on my Alpine but I've had nil experience with the Exec so I can't proffer any tidbits of advice. Sorry :/ (You might want to go browsing the Exec forum though, see if there's any info relating to this problem on there, if you've not already done so of course.)

Hello Billy G
Put ur exec in bootloader mode.Use MaUpgradeNoId.exe to upgrade yr device since u r getting contry id error.The above file can b searched in forum..put it in the same folder where the upgrade files are there.
u will get back yr device alive...

Done that, but get a cant find RUU.dll. No idea how to extract the ROM/Upgrade. Installshield seems to do it automatically. Not exactly a whizz on PC

First of all, you have connection between your device and PC, this is really good.
1. Get flashing program - ROMUpdateUtility-NoVendorID.zip
2. Get the correct flash for your device. I will repeat - CORRECT flash file for your device. If your will flash with incorrect version, bootloader could be overwritten, than your device is really in a bad shape. Not every service center will be able to recover.
3. Normally rom update/upgrade is .exe file it inclides binaries and flash rom itself. Get winrar. Instead of executing .exe update/upgrade, open it with winrar and extract it to temporary location.
4. In one of the folder will be file ROMUpdateUtility.exe. Replace it with ROMUpdateUtility-No.Vendor.ID
5. Start ROMUpdateUtility-No.Vendor.ID.exe
6. Perform flash.
7. Process may slow down at some stages, don't warry, just be patient.
8. Make sure you understand that downgrade process is not always possible. Other words, if you decide to go back to your previous flash or original flash, you may have problems.
9. Buy UPS.
good flashing

Cheers, managed to get it done. Was afraid i was going to have one expensive brick here :?
Thanks for all the help.
Great resource here. Keep up good work

fdp24 said:
9. Buy UPS.
Click to expand...
Click to collapse
That is a SOUND piece of advice, from one UPS owner to another

crashed/frozen. wont boot (FInixNOver) - cant reflash!

Hi guys.
I was using the installed the FInixNOver 3.0.1 ROM onto my SPV M700 and it was great. I've had it for about 2 weeks without any problems.
Last night I looked at my phone, only to realise that it was completley dead. This didnt shock me to much because the battery was running low, and i decided to let it die completley before recharging it again.
I charged my phone overnight and switched it on this morning, but the phone would freeze at the 'FInixNOver' splash screen (the numbers at the bottom of the screen would appear overlaying the splash, but the phone wouldnt go pass this point).
The only way to turn off the phone from this state is to eject the battery. I have tried removing the sim card, turning it back on in as many ways as possible but to no avail. I am able to get to the TriColor test screen (im running IPL-0.50 / SPL-1.30.Olipro) but with all the custom roms available, they all use the ROMUpdateUtility which requires the phone to have established an activesync connection initially (but this would mean my phone would have to be 'on completley' - so this is catch 22.)
For the record, my phone/battery died while my wired handsfree was attached (dunno if thats of any interest to anyone or the rom baker).
But it looks like the only way i'll be able to flash my phone is by finding a way to install the .nbh file without using the RUU method. Because I can put my phone into test mode manually.... any help or guidence would be very much appriciated.
Thanks.

Ok can you get it into bootloader? power/camera buttons and reset?
sorry didnt read fully.
right get your device into bootloader first,
then open active sync (are you using xp)
then open connection settings and disable usb connection,
put your device into bootloader mode, then run any rom upgrade, i prefer the WM6.1 pdaviets from HERE (Username: PDAVIET / Password: pdaviet)

Your pda does not need active sync with ruu's, so no catch 22. if you turn off usb connection in active sync, you can still run ruu and it will be recognised, unless you are using vista, where you need to change your HTC SYNC drivers.

Thanks for your quick response...
Yes I can get into boot loader using the power and camera buttons (or holding the power and camera buttons when resetting the phone)...
When the phone is in boot loader mode, active sync doesnt even detect the phone anyway, but nevertheless, I have followed your instructions and disabled the USB Connection. (BTW, yes i am using XP)
The phone is still in boot loader mode, so now i try and execute the ROMUpdateUtility.exe and go through the steps, at the 1st step i tick the tickbox and click next, and the 2nd step i tick the tickbox and click next. (this step says DO NOT enter the bootloader manually? - but i have havent i?) anyway, when i click next, it says... "Verifying the information on your Trinity... Please Wait..." for about 10 seconds, and then i get a message "ERROR [260] : CONNECTION"
What am i doing wrong?

Huumm.. why dont you flash your phone throw the sd card??
Read this link:
http://wiki.xda-developers.com/index.php?pagename=Trinity_SDCardFlashing

try to flash your phone with some official rom and after that flash it with any other you want!

manos_23 said:
try to flash your phone with some official rom and after that flash it with any other you want!
Click to expand...
Click to collapse
I would recommend this option above, to be safe, i usually get them error messages when the battery is below 50% or sometimes i try it again and it works. it does state do not manually enter bootloader but i always do it this way.

also make sure active sync is not still running in taskmanager under the alais: wcescomm.exe and WCESMGR.exe, end them both.

I've just tried using an official ROM, but the problem still occurs with the 'connecting'. It doesnt seem that the computer picks up a connection to the phone whatsoever.
Should i be concerned that at the bottom of the bootloader screen it says "serial", is this correct?
Im starting to get annoyed now.

Bye,
the bottom of the sreen mast say "usb" not serial.

it seems there is a problem, if it states serial. as it should say usb. try THIS

Seems like the problem was that my USB lead was loose and made a bad connection, hence why the bootloader showed 'serial' and not 'usb'... as soon as i wiggled it and heard the 'connection noise' in windows, i knew i was good to go, and so using the RUU worked fine to reupdate my phones ROM.
Thanks for your help.
My only question is that why did it happen in the first plave?

WIZZKID - I just saw your post here now. I have to tell you that I also saw "SERIAL" at the bottom of the bootloader screen and not "USB". As I said I returned it to get another phone but maybe I will try something else for now instead of a P3600i. I will monitor your thread to see how it turns out for your phone, because it seems that we have the same problem.

if you see "serial" instead "usb" your problem is in the usb cable, usb port from your computer or in the usb connector from your trinity!!!!!
I was having the same problem that you have!! my problem was from my usb from mine trinity!! see if the conector is at good conditions !!!

Well as some of you may know, I got my Trinity replaced for sticking at the WM splash screen after a few days. This second one - I have had it ONE night - and the same thing has happened with incomplete booting. This time I have been trying all night to flash the phone to an official ROM, but I cannot do it (apparently) because I can't establish a connection via ActiveSync. When I stick the data cable in while in bootloader I see SERIAL replaced by USB and when I try the flash I get a "270" error (cannot connect to phone) and the phone re-boots to the sticking plash screen. What should I do now?

ladies and gentlemen...
we've got a lot of mixed messages in this thread.. please make sure you're posting the right thing. no need to disable USB when manually going in to bootloader to flash (at least in xp).. Also, you can ignore the part of the RUU that says 'do not manually enter bootloader' (you should really read the guide on my site)
foxuniform- can you please give some details..
1) are you running xp or vista
2) have you flashed hard-spl? if so what version?
in the mean time, try a couple of things.. first, flash hard-spl (even if you already have it, but from the sound of it i think you don't have it on your device).. if that works, try to flash an official ROM. Can also try to use splxploit, then flash hard-spl, and then flash official ROM (there's a guide on my site if you're unsure)
please post your results
*edit*
here are the steps for SD card upgrade, but i HIGHLY recommend flashing Hard-spl first..
try to do it from SD card. how?
Extract the .NBH file from your prefered ROM upgrade: In windows use winrar (right click) to extract the contents of the exe file. In Linux / MacOS use cabextract (http://www.cabextract.org.uk/) .
Rename the .NBH file to TRINIMG.nbh and copy it to the root folder of your miniSD card.
With miniSD card inserted on the phone, start the bootloader (hold Power button on right side and Camera button at same time and stick with stylus in RESET on bottom).
You should see the screen pictured on the left, confirm flashing on screen by pressing the power button.
Flashing might hang after some time but this is normal. Just wait. Complete flash takes about 30 minutes, so check your battery or connect to charger before the flashing process starts.
When flashing completes soft-reset your device.
Make sure your SD has FAT32 and has no label. There have been reports that if SD has a label the bootloader can not access the TRINIMG.nbh

racerx_ I have carefully read your response and suggestions, and thanks for your expertise input on the matter. I am fairly new to this stuff so read below carefully as you may find errors in the way I tried to go about doing what I was hoping to accomplish.
First let me answer your questions. I am running Windows XP. The phone is in it's completely natural state in that I have not flashed it in any way. The ROM I was TRYING to flash to the phone while it was not starting properly (this is where I manually entered bootloader) is an official ROM from the HTC website (please note everyone that when I registered my P3600i on the HTC website it came up as the Dopod 810). Anyway, that never worked. ActiveSync never detected the phone (and I guess that's the reason I could not do anything as far as flashing goes). I HARD-RESET my P3600i and it booted normally. I re-installed all the stuff I had on it, from memory card to various .cab files, and the phone is working beautifully thus far. I will report if anything funny happens again.
I have to ask you racerx_, if I CAN flash hard-SPL on the P3600i according to the lovely guide on www.trinityguides.info. I have been of the opinion that things don't work for the P3600i as they did for the P3600, and that has been echoed by many P3600i users on this forum who are ready and waiting to try out some cooked ROMs (myself included).
For the sake of record, my phone is running rom version 3.00.707.17 and radio version 1.46.00.11. I patiently await your response.

woaaahhh..
i didn't notice the 'i' in your previous post... yeah, as far as i know, these ROMs are not flashable on your p3600i.. sorry..
**correct me if i'm wrong somebody**

Yeah I kinda thought that would be your response. By the way - do you think that this phenomenon of sticking at the Windows Mobile splash screen (both the P3600 and P3600i models apparently) has anything to do with something users do with the devices, or you figure it's an inherent software glitch of some sort? I am wondering if I should try a different model or hold on to my P3600i? Hope it's not something that'll happen again - I fly for a living and it's not gonna be good to have the thing screw up on me away from base - I really count on it for everything from casual keeping in touch on Messenger to viewing my work schedule. I love the Trinity though - it's one of my all-time favourite HTC phones.

hmm... i don't think its inherent in the Trinity.. (not a hardware issue.. in my opinion)
its been a while since i followed the posts on it, but always seems to be software related.. sometimes ROM-specific problem. Personally, i've probably flashed as many ROMs as anyone and the only time i ever encountered problems was with the official HTC WM6 ha.. go figure.. I think ppl did find that hard resets before and after flashing are helpful as well..
i love my trinity, and there's not much else on the market to make me want to trade it in (is it just me, or have pda's kind of stopped getting cooler).. i'd stick with it..

Qtek 9090 wont upgrade

Hi i am new on this forum ,i have a qtek 9090 unlocked bought on ebay
it runs windows 2003 and when i try to upgrade to wm6 ,the process starts and and it goes into USB V2.08 and pc makes a usb has been removed sound and the installer gives me a error msg
ERROR 120:COUNTRY ID: ERROR
and when i do a soft reset it comes up with a new installtion of (wm2003 which i hate)
this is getting to my head as i need to upgrade my PDA
can anyone help me
send me some links with the correct software and stuff please

you need to put the device in bootloader mode before connecting it to the pc by pressing reset+power+record and use the MAupgradeut_noID instead of the BAupgradeut to upgrade your device. if you don't have the MAupgrade tool present, you can download it from this post of mine:
http://forum.xda-developers.com/showpost.php?p=3768875&postcount=3
by doing these 2 points, you can avoid all error 101, 110 and 120

windows 6 for qtek 9090
does anyone have links to the new wm6 for qtek 9090

try this: http://forum.xda-developers.com/showthread.php?t=482997

No service
upgrade done and the phone worked for about 3 days now is says no service and wont pick a network

first make sure you didn't soft-reset the device the wrong way, meaning restarting the device by releasing the battery lock, because restarting it like that generally starts the device w/o radio, meaning no phone function. to avoid that, simply soft reset again by pressing the actual hardware reset pin.
in second thought, you might wanna post the values shown in the boot screen, maybe another radio rom might do the trick.
if neither of that worked, maybe you should try another sim card or a different location for testing network coverage just to figure out, if it might have something to do with a network failure.
if still however nothing worked, which i wouldn't hope, it still could be a bug with the particular rom and you might try another rom.
and at last, if that didn't help, you might have a broken radio receiver and as a harware fault would require you to repair or replace the device, but that is rather unlikely, so you are probably lucky and can fix it yourself.
please post back if and when you figured out, what the problem was, so we can all profit and learn off it.
with best regards,
Chef_Tony