Related
Hi,
I was upgrading my XDA Exec using Xda_Exec_Upgrade_v1.30.162.exe
My laptop died. It sometimes overheats but it hadn't happened in a while.
I now can't progress past the bootloader even after full clean reset.
Anyway. I have the O2 screen reading:
R 1.04.01
G 42.37.P8
D 1.13.82 WWE
My laptop detects a USB connection, although it says "USB Device Not Recognised". Activesync 4.1 won't detect it, however, I've tried changing settings etc but to no avail.
I've trawled the board here and found people recovering from similar situations with other devices. Am I gonna be able to restore my beloved exec from paperweight-status?
btw: am in Ireland where O2 don't support the exec and bought it from a guy in the UK who got it as an unwanted upgrade. have flashed it before just fine...but don't think I'll be able to return it to O2 as UK and IRL are not the same company...
Help?
Mark
p.s. ran BL10_RUU_UNI_V11.exe and got 101 connection error :-(
EDIT:
Fixed, using bootloader mode and re-running the upgrade. thanks
xda neo crash
You need to reinstall your windows mobile 5 system. If you are using orginal german neo rom, you can download rom from o2 web site, or you can download from this sites ftp server
thanks for the feedback,
I found the info on restarting in bootloader mode (i had previously misunderstood "bootloader") and was able to re-flash it by USB no probs.
I now have a happy XDA
Hello there ...I have about the same problem with my MDA Vario....could you explain how do I "restart in bootloader mode"?
My PPC just stucks before loading windows...
thanks
How to get bootloader mode
Ok, did a bit of a lookaround and got this (I thinkg the MDA Vario is the XDA Mini)
For Xda II and Xda IIi
- Press & hold the power button
- Press & hold the D pad (5 way directional button)
- Push the stylus into the soft reset hole - until you see the word 'Serial' on the screen.
You should now be able to follow the upgrade process above for a device stuck in Bootloader mode.
For Xda IIs
- Press & hold the power button
- Press & hold the Camera button
- Push the stylus into the soft reset hole - until you see the word 'Serial' on the screen.
You should now be able to follow the upgrade process above for a device stuck in Bootloader mode.
For Xda Exec
- Press & hold the power button
- Press & hold the Backlight button
- Push the stylus into the soft reset hole - until you see the word 'Serial' on the screen.
You should now be able to follow the upgrade process above for a device stuck in Bootloader mode.
For Xda Mini S
- Press & hold the voice command button
- Push the stylus into the soft reset hole (short quick press). Keep hold of the voice command button until you see the screen with multicolored horizontal stripes). The device is now in Bootloader mode and you can follow the upgrade process above for a device stuck in Bootloader mode.
EDIT:
The rest of the process (just in case you need to know) is as follows:
(and if you have problems open your connection settings in activesync and ensure that USB is unchecked...that is OFF. remember to reset the USB settings once you've successfully upgraded)
in 'Bootloader' mode
When this happens the device screen will be blank except for the words;
Serial
v 1.00a
The word 'Serial' should change to 'USB' when the cradle is plugged into the PC, and the version number below this will vary. When you get this screen, a soft or hard reset will not make any difference.
It is still possible to run the ROM upgrade file again, WITHOUT using Activesync (activesync will not restart anyway).
Firstly unplug the USB cradle and reboot the PC
Plug the cradle back into the USB port (this must plug directly into the USB port and not into a USB Hub/adaptor).
Now run the ROM upgrade file again from the PC. This should just run as per normal and correctly reflash the device.
Thanks bob_jesus!!
I am already in bootloader mode....Could you tell me where I can find the files to flash it? My device is Tmobile MDA Vario. Are there different files for flashing for every device? (O2 XDA mini s, MDA Vario, imate kjam...)??
Thanks again
Hi Ermoscow,
I'm sure if you trawl around the boards a bit you'll find it. I'm pretty new to this but yes, all these devices tend to have a different Rom, and each device itself tends to have a different Rom based on your mobile carrier.
e.g. I use an XDA exec which is the same as an HTC universal, they could theoretically use the same Rom but not the same rom as an XDA mini.
Again, this is all in my understanding and keeping it simple.
another idea would be to check the t-mobile site and download your rom directly from them, it should be available. if i find anything for you i'll post back.
Thank you everybody!
After managing to get to the bootloader mode I made a rom update which solved the problem!
Now it works great again!
thanks
Botloader Mode
I have a bricked MDA as I had a power outage while flashing the ROM. Can someone tell me how to recover. I find references to folks entering bootloader mode and then recovering, but I cannot find a post that tells me how to do it. Can anyone help? [email protected]
I'm desperate!
Regards,
Bob
Hi, which MDA is it because the instructions should be included in my post up above. You just need to find which XDA your device corresponds to and go from there. All that info's in this forum somewhere for sure.
Best of luck!
XDA Exec Dead after interrupted Rom Upgrade
XDA Exec Dead after interrupted Rom Upgrade
Hi
I was installing new ROM WM6.1 on autom exec when it rebooted it was showing black screen and just vibrating. as when I hard rebooted it after removing my phone battery and again press the power button it was again showing the black screen and vibrator continues it is not bootng up.
can any one help me please.
How can I reinstall the the old rom using usb
help required....
Please help....
It´s always good to READ the Wiki:
http://wiki.xda-developers.com/index.php?pagename=Uni_ROM_Upgrade
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader_Serial
Keys dont work
Hey i just put WM6.1 on my xda exec and it works fine apart from the keys not working so i have to type using the touch screen and the WI-FI randomly turns off and on i was wondering if anyone else had these problems and if they could help.
Thanks
It might be very simple to all you educated guys, but I am sure there are a few more like me that are a bit baffled by some of the threads on here.
What would be REALLY nice would be a 'simple' step-by-step guide to installing wm6 on our devices, and what we need to download to achieve it, eg "you need this for MDACIII, and this for O2 Orbit"
Obviously anyone trying it runs the risk of buggering up their phone, but that's their own fault.
Any volunteers?
stunno said:
It might be very simple to all you educated guys, but I am sure there are a few more like me that are a bit baffled by some of the threads on here.
What would be REALLY nice would be a 'simple' step-by-step guide to installing wm6 on our devices, and what we need to download to achieve it, eg "you need this for MDACIII, and this for O2 Orbit"
Obviously anyone trying it runs the risk of buggering up their phone, but that's their own fault.
Any volunteers?
Click to expand...
Click to collapse
having asked the same question myself here goes.
Download USPL and follow the instructions. they are very clear.
Download
extract
connect phone with minimum 50% battery
soft reset and once started up fully run the app by clicking on Rom Update utility
follow the process through once finished your device will restart.
once restarted you then can flash the rom of your choice
I used Black and Blue again ran the update utility and bingo.
dont forget that all data on your device will be lost so make sure you have back up of contacts etc in outlook on pc.
Finaly make sure you have Activesync 4.5
enjoy
AS STATED ALTHOUGH THIS WORKS YOU ALL DO IT AT YOUR OWN RISK
Id just like to know really is that how many people have done it without unlocking the device for o2 orbit uk. i have one and am not really willing to try it unless i know there are people out there that have tried it and it worked.
as there is no rom install file from o2 for this, there is no way bacj and bricked phone is the only way forward. id like not to brick my phone as i need it daily.
so, has anyone with a locked o2 device upgraded to WM6 successfully and which rom did you use if it worked.?
joey jojo said:
Id just like to know really is that how many people have done it without unlocking the device for o2 orbit uk. i have one and am not really willing to try it unless i know there are people out there that have tried it and it worked.
as there is no rom install file from o2 for this, there is no way bacj and bricked phone is the only way forward. id like not to brick my phone as i need it daily.
so, has anyone with a locked o2 device upgraded to WM6 successfully and which rom did you use if it worked.?
Click to expand...
Click to collapse
i have o2 uk orbit and all is well
pof said:
I created update package for this ROM in NBH format, so no risk of bricking when flashing it, just unzip & run RomUpgradeUtility.exe
Download here:
ARTE_WWE_WM6.zip
NOTE: Before flashing you need to have Artemis USPL on your device.
Click to expand...
Click to collapse
Taken from Bepe's thread about the modified o2 German update. Basically you need to use the Artemis USPL program and then use the first link to install which I did successfully on a CID locked phone.
Thanks guys, but, unfortunately, the uspl thing does not work on my pc
Along with a few others I get the 'black screen' on my mdac3 then activesync disconnects and the rom loader throws up an error
Luckily my mdac3 survives through a soft reset
I think the idiots guide is not quite there yet
hi..
i have O2 uk orbit.. which is still locked, i fully charged the battery, completed a hard reset of the phone used the pof Artemis Update SPL (USPL) v.01 upgrade (wow what a brain box he is!) just in case it failed, so i could you use any NBH file to get you orbit to work again if i failed. Then used Bepe's WM6 os.nb file renamed it to windows.nb downloaded ATRE.zip unzipped the ARTE.zip file placed the windows.nb into the same directory, don't forget to edit UpgradeRom.bat file 0x3900000 to 0x3500000 with in the ATRE directory and copied and installed EnableRapi.cab to the phone. Reset it the phone and then started the UpgradeRom.bat! 12 mins later upgrade complete. Hard restart the phone.. Chewing nails by now... all went well did a soft reset of the phone before the O2 ExtROM autorun starts..
sorted, and did half way though a night shift at 3 am.. not bad at all!
crushuk said:
hi..
i have O2 uk orbit.. which is still locked, i fully charged the battery, completed a hard reset of the phone used the pof Artemis Update SPL (USPL) v.01 upgrade (wow what a brain box he is!) just in case it failed, so i could you use any NBH file to get you orbit to work again if i failed. Then used Bepe's WM6 os.nb file renamed it to windows.nb downloaded ATRE.zip unzipped the ARTE.zip file placed the windows.nb into the same directory, don't forget to edit UpgradeRom.bat file 0x3900000 to 0x3500000 with in the ATRE directory and copied and installed EnableRapi.cab to the phone. Reset it the phone and then started the UpgradeRom.bat! 12 mins later upgrade complete. Hard restart the phone.. Chewing nails by now... all went well did a soft reset of the phone before the O2 ExtROM autorun starts..
sorted, and did half way though a night shift at 3 am.. not bad at all!
Click to expand...
Click to collapse
Confused... is it really necessary to take all these steps? I thought that the only thing required is to run Pof's tool USPL, and after that run Romupdateutility.exe from the package in .nbh format (the link is just a few messages above yours). Please correct me when I'm wrong.
step by step guide
stunno said:
Any volunteers?
Click to expand...
Click to collapse
OK, I volunteered... This is a detailed list of steps how I installed a new ROM on my MDA Compact III (CID locked, at least I think so). It worked without any errors or problems. I used PDAVIET Black&Blue v2.0. It was my first flash on my Artemis, so I more than understand your need for step-by-step guide
1. download the file Artemis_USPL.zip
2. unpack into the folder c:\USPL
3. download the file ARTEMIS_Black_Blue_v2.zip
4. unpack into the folder c:\ROM
5. soft reset your phone and have it charged over 50% (I have it fully charged)
6. wait until the system starts on your Artemis
7. turn on flight mode (probably not necessary, but I wanted to minimize any risks)
8. connect your Artemis to PC with a USB cable
9. wait until ActiveSync icon in your tray (lower right corner of your windows desktop) turns from gray to green. If you connect your Artemis for the first time to PC, you do not need to set up synchronization, just click "cancel" on the first screen of "Synchronization Setup Wizard"
10. while ActiveSync icon is green, run c:\USPL\start_uspl.exe
11. a DOS screen will pop up with the text "Initializing: 0.." in the bottom indicating probably seconds from the start (it stopped around 70 in my case after about 1.5 min)
12. DOS screen disappears and PDA Phone ROM update utility pops up
13. at the same time, your Artemis turns blank (orange/green LED turns off as well)
14. tick the check box next to " I understand..." and then click Next
15. tick the check box next to " I completed..." and then click Next
16. a box saying "Verifying information on your PDA..." pops up
17. on the next screen click Update button
18. next screen says "Upgrade to ... image version 9.99" - click Next
19. Next screen says "You are now ready to update..." - click Next, a window with a blue progress bar appears with a text "Updating ROM image..", it quickly runs to 100%
20. next screen says "Congratulations! ..." - click Finish
21. your phone turns on and boots into your old system, however it should be CID unlocked now
22. your Active Sync should reestablish and icon turns green again
23. do not touch anything (phone or USB cable) and run C:\ROM\ROMUpdateUtility.exe (make sure activesync icon is green)
24. PDA Phone ROM Update utility window appears, tick the check box next to " I understand..." and then click Next
25. tick the check box next to " I completed..." and then click Next
26. a box saying "Verifying information on your PDA..." pops up
27. on next screen click Update button (says "Current information...")
28. next screen says "Upgrade to ... image version BnB2.0" - click Next
29. Next screen says "You are now ready to update..." - click Next
30. a window with a blue progress bar appears with a text "Updating ROM image..", your Artemis will have light gray screen with blue progress bar showing the progress of flashing - do not touch anything and wait (it took 2-3 minutes on my 3 years old PC)
31. next screen says "Congratulations! ..." - click Finish
32. your Artemis turns on and starts booting, you can disconnect it from PC now
33. the boot screen remains the same (T-Mobile in my case), so do not panic!! it is normal
34. wait until calibrate the screen appears, calibrate, choose time zone and you are ready to use your new OS
35. let me know if this manual was clear enough, whether it helped you and please suggest potential changes for improvement
Take care,
Dzim
i've just succesfully flashed my dutch CID-LOCKED MDA Compact 3 with this method, so i'd say it's reasonably fool-proof
A couple of questions before i take the plunge - if my t-mobile cmda iii is already CID unlocked, can i just go straight to the update rom part.
Also, is there any way of dumping my standard t-mobile rom first off? I'm having trouble trying to use itsutils due to the app lock.
Cheers Dzim!
Your instructions worked perfectly.
One very happy complete idiot here!
Furbious said:
A couple of questions before i take the plunge - if my t-mobile cmda iii is already CID unlocked, can i just go straight to the update rom part.
Also, is there any way of dumping my standard t-mobile rom first off? I'm having trouble trying to use itsutils due to the app lock.
Click to expand...
Click to collapse
There is a TMobile rom on here somewhere already, I just cant find it at the moment
My Compact 3 it’s death now. After pres voice commander button MDA start only to the boot loader. Can’t run complete system.
Pleas tell me. How can I write the new rom with WM5 or WM6 ?
OOPS! Working well apart from the "cant save word documents" bug!!
Just an update - to use the v1 or v2 black and blue, even though it is unlocked, you still need to use the supercid util.
Otherwise you get the rom update getting to 3% before crashing out to say the rom is corrupted.
I've now converted 2 other tmobile compact mda IIIs successfully, wm6 is much quicker
Yes, with my Compact was exactly as You say. Now is death. What I can do now to repair it.
big thanks to Dzim, used the idiots guide and now on wm6 =D
cheers!
PS: first post
Hi! Nemesis, try to connect your HTC to your pc in bootloader mode.
Lauch start_uspl.exe in USPL folder. Follow instruction on post N°9 by DZIM.
After USPL your HTC should reboot (maybe in bootloader mode only).
Launch the ROMUpdateUtility.exe in Black&Blue ROM v2 and follow instruction.
Thanks gguyaz
Pleas tell me.
Could I doing this upgrade with Windows Vista on my PC?
I'm the newbiest of them all, I think I bricked my brand new Excalibur!!!
Sorry if I'm posting in the wrong place, but I need heeeelp!
O.K., here it is:
I just downloaded kavana's 080314 WM6.1 installer for the HTC Excalibur, I ran the exe and followed instructions, afterwards, the ROM app opened and started upgrading the phone but it got stuck at 1%, it made be go thru the recovery process several times (unplug, turn off, disconnect battery, turn on) but it always started on tricolor mode and always got stuck on 1%, after a third recovery process the ROM app just quit and left me hanging on tricolor mode!!!
Activesync won't connect now, I try to run kavana's exe again but it doesn't recognize the phone either, the phone is on, conected (windows makes the usb sound for connection) but it is not recongized, it's as if it's not plugged.
It is stuck on tricolor mode and I don't know what to do!
Please help me!!!
Try the dicussion thread "Bricked my T Mobile phone" there are plenty of answers there.
Will this work?
I saw this on said thread, but I presume it applies for a Herald phone, will it work?
The tricolor mode is "bootloader mode"?
Isn't there some sort of restart that can fix it?
Can someone elaborate on this? I'm really a super-noob!!!
"Try a SD card flash to unbrick your device
This is how:
MAKE SURE THE HERALD IS FULLY CHARGED BEFORE STARTING THE PROCES
#01 Download your original RUU
#02 Download (if not yet installed) WinRar and install
#03 Copy your full sd micro card to your harddisk and format your card with FAT 32
#04 Rightclick the downloaded exe file with your original RUU, click Unpack here
#05 In the map the will be created you will find a file (or similar) called RUU_signed.nbh. Copy this file to your formated sd microcard.
#06 Rename the file to Heraimg.nbh
#07 Get your Herald into bootloader modus by pressing the comm manager button and the camera button and pressing the reset button at the same time. Do not release both buttons until your in bootloader.
#08 Once in bootloader pop in your sd micro card.
#09 As soon as your card is popped in the screen will say something like "Reading SD card". Wait it out till it says "Push button to start" and slide the indicated volume slider down.
#10 The Herald will start the flashing proces. Wait it out till it says "Press any button" and hit the send button.
#11 Perform a hard reset
#12 Voila! Your back in business"
velascoperroni said:
I'm the newbiest of them all, I think I bricked my brand new Excalibur!!!
Sorry if I'm posting in the wrong place, but I need heeeelp!
O.K., here it is:
I just downloaded kavana's 080314 WM6.1 installer for the HTC Excalibur, I ran the exe and followed instructions, afterwards, the ROM app opened and started upgrading the phone but it got stuck at 1%, it made be go thru the recovery process several times (unplug, turn off, disconnect battery, turn on) but it always started on tricolor mode and always got stuck on 1%, after a third recovery process the ROM app just quit and left me hanging on tricolor mode!!!
Activesync won't connect now, I try to run kavana's exe again but it doesn't recognize the phone either, the phone is on, conected (windows makes the usb sound for connection) but it is not recongized, it's as if it's not plugged.
It is stuck on tricolor mode and I don't know what to do!
Please help me!!!
Click to expand...
Click to collapse
I believe you didn't application unlock it first. I had same issues. I finally got it to load. I don't think you bricked it. Remove battery wait a few seconds and restart phone
timothyjok said:
I believe you didn't application unlock it first. I had same issues. I finally got it to load. I don't think you bricked it. Remove battery wait a few seconds and restart phone
Click to expand...
Click to collapse
Already did that... still on "brick" mode...
Question: is my warranty still valid? I bought it 3 days ago.
you can solve simply to launch original upgrade to wm6 rom
glenbo said:
Try the dicussion thread "Bricked my T Mobile phone" there are plenty of answers there.
Click to expand...
Click to collapse
Do try these procedures first. I'm just throwing it out there but if you try again it is probably a better choice to flash to WM6 first. Then try flashing to the 6.1.
I'm sure you can return it but come up with a believable excuse.
Yes, You Are Correct!
pfunkside said:
Do try these procedures first. I'm just throwing it out there but if you try again it is probably a better choice to flash to WM6 first. Then try flashing to the 6.1.
I'm sure you can return it but come up with a believable excuse.
Click to expand...
Click to collapse
Yes, that is the correct path for him to take, install a 6.0 ROM first, before installing a 6.1 ROM. I suggest he install the T-Mo official wm6, just to get things started in the right direction again.
(1) If the device is still in the tri color mode (bootloader mode), that's a very good sign, it's not bricked. Connect the device to your PC via active sync in the tri color mode, you may think that the device is not connected to Your PC but it is, it may not look like it's connected, run the official T-Mo wm6 ROM RUU WWE, it will install on your device as long as your device is in the tri color mode.
(2)Once you get the wm6 ROM installed on your device, you must first SDA_ApplicationUnlock your device, next you want to Certificate AppUnlock and SurrealApplication Unlock your phone. Now, the reason you are doing all these unlocks are because you coming off the T-Mo wm6 ROM.
(3)After all this have been done, it now ok to try to install the 6.1 ROM on your device.......!
Great support!!! But now comes the obvious question from the n00b of the n00bs!!!
Got it, now the big question is: how to flash to WM6?
Is it done by the steps I posted early? (formatting SD, etc.)
Also, where do I get the T-mobile RUU?
Finally, there are a few things you should know, my phone was bought in Mexico, under the cellphone company Movistar (Spain's Telefonica and I've heard U.S. AT&T), it had WM5 before I "bricked" it (hehehe).
When I turn it now, a few miliseconds before the tricolor screen I can read in the phone a "waiting for SD card" message when the tricolor screen comes on, I get this version of RUU 1.15.000.
I appreciate all your help, as a contribution to this amazing community, when I get thru this, I hereby commit myself to write a fully understandable guide for noobs with the same problem (not too long).
T-Mo Wm6
velascoperroni said:
Got it, now the big question is: how to flash to WM6?
Is it done by the steps I posted early? (formatting SD, etc.)
Also, where do I get the T-mobile RUU?
Finally, there are a few things you should know, my phone was bought in Mexico, under the cellphone company Movistar (Spain's Telefonica and I've heard U.S. AT&T), it had WM5 before I "bricked" it (hehehe).
When I turn it now, a few miliseconds before the tricolor screen I can read in the phone a "waiting for SD card" message when the tricolor screen comes on, I get this version of RUU 1.15.000.
I appreciate all your help, as a contribution to this amazing community, when I get thru this, I hereby commit myself to write a fully understandable guide for noobs with the same problem (not too long).
Click to expand...
Click to collapse
Is your mobile device still in the tri color mode, if so just connect it back to your PC via active sync, It will accept the download! OK you can get the T-Mo wm6 at T-Mo's website, if not I will send you a link with the T-Mo wm6 RUU. Don't panic, you are still in the game.......!
Update!! Phone unbricked but still on WM5!
Ok... I used this ROM: HTC_S620_WWE_1.27.405.1_4.1.13.44_02.94.90_Ship.exe
It went thru the upgrading process but got stuck at 3%, anyway, it finished with a message like "this ROM cannot be used for your phone" or something and restored WM5.
Now I will follow instructions on the thread: "The Full Guide To Upgrading From Windows Mobile 5 to 6" and I'll be posting my acomplishments on this thread.
Question: The reasons for me not being still able to upgrade may be:
1. I haven't unlocked phone,
2. My phone is for Mexico and cellphone co. "Movistar", or
3. I'm running Windows XP as a virtual machine (via parallels) on an intel Macintosh and somehow there's a problem with the USB drivers.
I'm rooting for option 1 (but kavana's upgrade was supposed to already unlocked it). Option 3 maybe but then, why do I get Activesync to run? Option 2 would be a bummer!
T-Mobile WM6 RUU WWE ROM
Get the T-Mobile official Wm6 RUU WWE Rom here http://www.mediafire.com/?0vtw32zmuz3 ......!Oh! I throught you had a Excalibur.....!
Just can't seem to upgrade WM5 to WM6!
Iv'e tried the T-Mobile ROM and the HTC ROM and I get an: "invalid vendor id"
I tried every step on the aforementioned thread, even de CIS unlock, and still no luck... again, my vendor is movistar/telefonica/cingular.
Any thoughts?
Your Answer Is In jockyw2001 Thread
velascoperroni said:
Iv'e tried the T-Mobile ROM and the HTC ROM and I get an: "invalid vendor id"
I tried every step on the aforementioned thread, even de CIS unlock, and still no luck... again, my vendor is movistar/telefonica/cingular.
Any thoughts?
Click to expand...
Click to collapse
A easy frix, but read the instructions very carefully, jockyw2001 thread is located in the sticky section. What you are looking for will be in post #1.........!
New Instructions
Run the Excalibur Uspl-CID ByPass.zip, extraxt on your PC and open it there, you will see several file folders. Open the one that say (uspl) MS-Dos batch File, follow on screen instructions by pressing any key. This time when you see the white screen on your device do not panic! Run the HTC WM 6 ROM, this is done while the screen is still white on your device. Just follow the on screen instructions on your PC.............!
Now I definitively bricked it!
I ran the CID unbloker, screen went blank, ran the ROM, it got to 16% and made me do a recovery, after the recovery it gave me the same "invalid vendor id" message and it automatically restarted the phone, but...
The restart stopped at the HTC intro screen!! I've restarted it several times and it just stops on the first HTC logo screen... even a hard reset won't fix it!!!
HEEEEEEEEEEEEEEEEEELP!!!
Here is a visual aid.
You are not reading into detail. Use the Tmobile rom instead of the HTC Rom.
http://forum.xda-developers.com/showthread.php?t=368998&highlight=Jamerican
Still Bricked!!!
Yeah!!! superb visual aid!!!
I just wish I had seen it before I bricked it!!!!
This is the current state of my phone: I press power, I see a white screen with the HTC logo in the middle, the phone vibrates, still the same HTC logo... and it is stuck that way! I can't turn it off, I have to take out the battery!!
I've tried a hard reset, same thing happens! It stays stuck on the HTC logo screen and I'm forced to pull the battery out for the phone to shut down.
It is obviously not recognized in any way when I plug it to the PC's USB.
What made this happen? HTC Generic ROM got stuck on 16% before telling me "invalid vendor id", restarted the phone and voila: brick!!
Boy, I wish I was back in the tricolor mode!!!
IS THERE NOTHING I CAN DO?
I'm seriously thinking about going back to the vendor on monday and saying: It was like this when I woke up (I just bought it three days ago!!!)
If it gets that far, it doesnt seem totally bricked, ima PC man, so this may be off, but it seems like some kinda bootloader error on the phone itself....IE, the HTC screen is all that the bootloader tells the phone to load. Have you tried forcing the phone into bootloader mode?
I Looooooove Google!!!
OK... I found a turnaround for the problem... got it to go to bootloader mode!!!
Whenever something like these happens to you this is the hard way to put your excalibur/dash in bootloader mode:
1. Take out battery and sd card;
2. Plug your USB cable to your PC (not yet to the phone)
3. Press and keep holding the SIMB. key (the one with the camera next to the space bar)
4. Plug your USB cable to your phone (while still pressing the SIMB. key)
5. Voila: You are in bootloader mode!!
This was gotten for a 15 min. search in google!!
Now... I'll keep going with my WM5 to WM6 upgrade...
So a little background first. I have flashed a Windows mobile rom before. I have an X50V that I have taken from mobile 2003 to 6.5, 6.5 on that is meh right now, prob going to sell it. But anyway the point is im not new to flashing a rom, but it also wasn't a verizon phone. I know I need to unlock it to update it.
So this is where I need help. I have read the FAQ set up by Nfsfan but I cannot get the unlocker to work. It keeps giving me a 262 error. I get it into bootloader it says USB but just doesn't work. it starts then gives taht error. It restarts perfectly fine so I know its not even doing anything.
I have, the official verizon 6.1 update. It was on the phone when I got it two weeks ago. Rom Version 3.14.605.1 Radio 3.37.78
I have also read the PPCgeeks forum, Every where I read it says just restart the flash, but it just keeps doing the same thing.
Thanks!!
How to switch to 6.5 on HTC Touch/Vogue/xv6900 Verizon specific (~20min):
1. Install Activesync to your computer here. Not sure if it's installed by default. If not, just download. Plug in your phone and you should be able to tell because some green thing pops up.
2. Download official 6.1 Verizon update to get latest radio. Plug your phone in, run the file, and it's self explanatory. When done, try making a call. If it doesn't work, dial *228, then press 1, and it should re program your phone to work with the cell towers.
3. Download 2.31 unlocker to unlock the phone, available on the first two links. Run the file. Don't extract it like another FAQ I found said. It'll tell you to plug your phone in so plug it in and hit enter. The phone screen changes to a rainbow color now. Computer will tell you to disconnect and reconnect the phone. Do so. Then follow the instructions on computer, check the box, keep hitting next. You'll see a 0% go to 100% pretty quick on the computer and your phone, and your phone will restart. Unplug phone. It'll load into 6.1 as normal. Hold down power+camera+stylus hole button on phone, you should see a rainbow screen, and the words 2.31 unlocker which indicates you've successfully unlocked it.
4. Disable activesync by going to activesync, File>Connection Settings> uncheck the checkbox "Allow USB connections". (I forget if this step is necessary if it's even during this part, but just to be safe).
5. Download NFSFAN's 6.5 v11 rom (or others may works) and extract to a directory. Plug your phone (with rainbow and 2.31 unlocker still on screen). Bottom display should change from serial to USB. Run the RUU exe update utility file from NFSFAN's files. In the program, the picture on the left won't be the Vogue but it's ok. Then follow the instructions, check the box, keep hitting next, you'll see a 0% go to 100% on the computer and phone, but now takes about 5 minutes since it's a large file.
6. Phone will restart itself and you should a brand new htc/6.5 screen. Just be patient as it loads. Do a hard reset anytime by pressing red and green button while using your stylus to poke the hole on the bottom. Hit the center big button, then the green button. You'll see a status bar and once it's done will reset it self. Let it load and follow on screen instructions. First time loading always takes a bit of time but after that it's fairly quick on any reset. Note, when calibrating the stylus, try to tap as lightly as you can even though it says to press firm. Windows uses this to calibrate how hard you should press your screen so if you press it too hard, your fingers will have to smash to screen to pick up anything. Tap it as lightly as you can and it would be easier to navigate with your finger. You can always recalibrate in settings.
7. (Optional) Do stpe 5 and 6 again. Codybear, a very experienced user on this forum, says he's never had any bugs/problems others seems to get because he flashes the ROM 2-3 times. He'll flash it, go through the customizations, flash it, go through the customizations, flash it, go through the customizations.
8. Tweak as necessary using this FAQ.
As an FYI, you don't have to do the SMS160 tweak because it was changed in v10.
If anybody wants to copy this to a sticky/wiki/faq anywhere, please feel free to do so. I hate when go to valuable information gets lost.
endless rebooting
ok so i got it to work i can make calls send message and such.
but when i unpluged it, it started an endless cycle of restarting after 10 seconds or so, and its fully charged.
i plug it back in and it stays on with out restarting endlessly. i posted here because i used these instructions
Please help!
My HTC TP2 freezes at start up with the black screen and the Touch Pro2 Logo and some details in red at the bottom:
B 80
R 4.49.25.17
G 61.44tc.25.32U
D 1.86.67102
No USB connection can be established.
What happened:
1. Tried to update from original WM 6.1 to WM 6.5 by using the official HTC ROM update utility. Seems like USB connection broke during update and update freezed at 42%. Update utility process has stopped by itself (no process visible anymore in the Task Manager).
2. Restarted phone and multicolor screen appeared and stayed. After connecting with USB cable again "USB" appeared at the bottom. Started again the HTC ROM update utility which recognized the phone and started the update process again, but stopped at the beginning with an error message stating something like the ROM is broken.
3. Restarted again (by removing the battery and hit power button) and state reached like described above (HTC TP2 freezes at start up with the black screen and the Touch Pro2 Logo and some details in red at the bottom).
4. Performed a hard reset but did not help.
What can I do to bring the phone back to life?
So you can't or can get in the colored screen now? (the boatloader)
And it's kind of normal that their nothing happens after the tp2 + red information screen, this since their is no rom to startup.
EDIT
Is it possible to tell exactly what error you got?
EDIT
Try to hard reset your device, do you know how to do this?
If not this is how to do it:
To perform a hard reset
1. With the device turned off, press and hold the TALK/SEND, END and POWER buttons until you see this message on the screen.
"This operation will delete all your personal data, and reset all settings to manufacturer default. Press VolUp to restore manufacturer default, or press other keys to cancel."
2. Release the TALK/SEND, END and POWER buttons.
3. Press the VOLUME UP button to perform the hard reset, or press any other button to cancel the reset.
Source: http://forum.xda-developers.com/showthread.php?t=523083
This is just what worked for me..
Had the same issue on my tp...
Hope it will work for you.
Did already the hard reset - but this did not help as nothing changed!
One further info: whenever I insert the battery the device automatically starts up - until it freezes again at the start up.
Can someone please help?
It's normal that the device starts up when the battery is plugged in...
But this is just what I know out of my own experience.
So sorry I can't help you farther.
EDIT
Did some research you might want to try to flash your phone by micro sd... (not for sure if it helps but by some people it did work)
Read the tread about flashing at the top of the rhodium section and you know how to do it.
Did another trial: downloaded and copied a RHODIMG.nbh to the micro sd card, inserted it again and pressed volume up at startup -> colored screen appears shortly, then switches to a white screen telling "Loading..." in blue font color, but nothing more.
Is there anybody out there who can help?
Do I need a specific RHODIMG.nbh to make this approach working? I didn't flash this device before, so it has been still in the original manufacturer's state.
frieder01 said:
Did another trial: downloaded and copied a RHODIMG.nbh to the micro sd card, inserted it again and pressed volume up at startup -> colored screen appears shortly, then switches to a white screen telling "Loading..." in blue font color, but nothing more.
Is there anybody out there who can help?
Do I need a specific RHODIMG.nbh to make this approach working? I didn't flash this device before, so it has been still in the original manufacturer's state.
Click to expand...
Click to collapse
suppose 2 press down volume not up after soft reset
This may help,
Try entering bootloader by switching off device then switch back on holding down the Vol down key.
If you can enter bootloader this way then you wil be able to flash from SD card following the instructions from here
http://forum.xda-developers.com/showthread.php?t=550540
if you want to flash the Official update from HTC you can extract the Nbh from the Exe file you downloaded from them, just use winzip, Zzip or Win RAR to extract the contents from the Exe you are looking for RUU_signed.nbh..follow the above thread instructions to change the name of the file to RHODIMG.nbh.
I DONT KNOW IF YOU NEED TO HARD SPL FOR THIS..Probably better to do it than not. Can Anyone Confirm???
i hope this helps
Device is up and running again !
Could enter bootloader mode and tried first to install again via the official HTC installer -> worked!
Thanks a lot for your support!
great news welldone Bro and welcome to the forum!!!
osrix25 said:
This may help,
Try entering bootloader by switching off device then switch back on holding down the Vol down key.
If you can enter bootloader this way then you wil be able to flash from SD card following the instructions from here
http://forum.xda-developers.com/showthread.php?t=550540
if you want to flash the Official update from HTC you can extract the Nbh from the Exe file you downloaded from them, just use winzip, Zzip or Win RAR to extract the contents from the Exe you are looking for RUU_signed.nbh..follow the above thread instructions to change the name of the file to RHODIMG.nbh.
I DONT KNOW IF YOU NEED TO HARD SPL FOR THIS..Probably better to do it than not. Can Anyone Confirm???
i hope this helps
Click to expand...
Click to collapse
For future info, from what I have gathered you must hardSPl for all ROM flashes. If the ROM you flash is the stock ROM, you can also revert your SPL to stock. For any other ROM, you must leave your device hardSPL'd.
Hope I helped.
how were you able to connect the phone with the pc. i seem to have a similar problem but am finding it difficult to connect the phone to the pc. i have activesync installed but cannot connect to the phone
osrix said:
This may help,
Try entering bootloader by switching off device then switch back on holding down the Vol down key.
If you can enter bootloader this way then you wil be able to flash from SD card following the instructions from here
http://forum.xda-developers.com/showthread.php?t=550540
if you want to flash the Official update from HTC you can extract the Nbh from the Exe file you downloaded from them, just use winzip, Zzip or Win RAR to extract the contents from the Exe you are looking for RUU_signed.nbh..follow the above thread instructions to change the name of the file to RHODIMG.nbh.
I DONT KNOW IF YOU NEED TO HARD SPL FOR THIS..Probably better to do it than not. Can Anyone Confirm???
i hope this helps
Click to expand...
Click to collapse
is it possible to connect to active sync in bootloader, cos my phone cannot even boot, it freezes up with a white screen and htc logo.
After entering bootloader you can flash either way,either by ruu package provided by your ROM's maker or running official ruu release or if you have the renamed file on the root of your sd card....I never use sd card flashing and have never had a failed flash...If in bootloader it will not connect with activesync,but device should be recognized by ruu.exe
WC