Hello everyone, I know this is not a new issue here but I have posted here before in order to get a solution and nothing worked.
Here is the issue:
I got a treo 750 from the us, cingular. It came with WM 6 I think and I followed a guide from here and upgraded it to 6.1. Than I saw a custom rom and installed (didnt notice it was only for htc) and than my treo got stuck on the three colour screen. I than tried palm recovery tool (not succeeded), flahshed the origininal rom and others by cable connection (not succeedded again) and now, almost a year later I am trying to flash the original rom using a mini sd card formatted with fat 32 and with the original cheeimg inside.
The problem is that I have no clue on how to start the installation. I do reset, the screen stays black, I do a hard reset and the screen asks if I want to delete everything and if I select yes or no, the screen goes back to black. I pressed reset plus media button and I get the three colour screen. Now I am trying commands using mtty, since I am using vista in my only pc, I installed windows xp mode on seven and I am using a virtual xp with active sync. I disabled usb connection on activesync and still it does not show usb option to connect with mtty.
Any tips?
Related
1st off I DID use the search button.... 2nd HELPPP ME!!!
Waaah :'( I have a most intriguing problem I was running pdaviet 4.0.0.6 Touch for almost 2 weeks now without a single glitch.. the phone fell on my carpet and went to bootloader screen and eversince then it has never recovered I tried a hard reset it didn't work when I was pressing the send button it did nothing I did some forum searches and tried putting back the nvid RUU and it said that the update was succesfull and the progress bar on the phone moved accordingly but it went back to the bootloader screen ... then I tried pdaviet temp rom that was in the package still no go I can tell it works somehow because the USB lights up in the bottom left when I plug the usb cable and the progress bar that moves, but I'm getting desperate IPL and SPL info is in my sig...
same same... but i dropped mine before flashing the new PDAVIET touch rom.. still went fine..
now, it still flashes... RUU says its successful.. but PDA just reboots back to bootloader..
i can charge my phone fine in bootloader.. i can see the USB come on when i connect it to my computer.. other than that, can't do anything...
i've tried everything the past 2 days.. looks like i'll have to send it back to dopod.. will let u guys know what happens... probably something got damaged..
struck at bootloader
I tried WM6 (4.0.0.6 touch) from WM5 AKU 2.2 but it failed in between with some write message,which was bit strange as I didn't touch any key on laptop during that time and no program was being run at that time. (I am using VISTA Home premium). I got my phone into bootloader but it does not connect to my laptop...so cant upgrade back to AKU 2.2. In Windows Mobile Device Center, I cant see my device connected. So is it particular to Vista or my phone got bricked?
I am yet to try on Windows XP, which I have to arrange.
Please advise.
i had the sam problem.i installed this : try to install the 2.20 nvid rom
just go into bootloader mode-you dont need active sync connection and start the upgrade-search for 2.20 nvid rom download it and recover your device
charliess said:
i had the sam problem.i installed this : try to install the 2.20 nvid rom
just go into bootloader mode-you dont need active sync connection and start the upgrade-search for 2.20 nvid rom download it and recover your device
Click to expand...
Click to collapse
I tried the same but when I run ROMUpdateUtility_No_VenderID, I get a message 'Update Error, 260' which tells further that PDA is not connected to laptop., although it is very much connected. However LED on PDA does not blink as well.
When I plug in this phone to Wall adaptor, LED does show up.
'USB' appears at Bottom Left corner of PDA when connected to laptop and certainly its getting recognised by Vista as it starts installing Driver as soon as this is connected to laptop.
Please suggest.
I am stuck in the same situation, although I have a G3, running 2.20 on IPL & SPL
Working now
I tried on XP (I was trying on vista before)..I had to install Active Sync as it was not installed on that PC, then run RUU update for AKU 2.2 and update was successfull. Now will try Touch 4.0.0.6 again but this time on XP.
Hope this time I wont have any problems.
hello everyone. i just bought a g3 wich remains stuck in the ipl/spl screen. i tried VIPPIE 's tutorial (many thanks man for ur work) and flash button rom 1.05 to revive the phone. it flashed without any error , but same result. phone doesnt pass the ipl/spl screen. next i tried to flash Xda_MiniS_LaunchROM_v154102, flashed ok but nothing happend. i m just stuck on the ipl/spl screen. the phone isnt bricked but i can not start it to do a soft spl and flash it. any ideas ?
because it s an o2 xda mini s , i thought an original o2 rom would do the trick (start the phone) but i couldnt find an original rom (tried the xda dev ftp page and the o2 one).
many thanks
hehh
same happend to me once. Go online and finde botton run , update utility 2.00.1
go step by step:
Disconnect your phone from the usb cable,disable any Firewall and Anti virus and reboot your Pc.
1. Make sure your phone is not Connected to the PC and remove the dummy card or SD/MMC card
2. On your Desktop PC, open Microsoft ActiveSync, then go to File >Connection Settings >Remove the Selection from “Allow USB Connection with this desktop computer”
3. Reconnect your phone to the Desktop PC using the USB Cradle and the Charger MUST be Connected to the Cradle (Don’t Bluetooth for the Upgrade)
4. When you see usb appear at the bottom of bootloader screen
5. Run the Upgrade again and it will work fine without any problems.
While upgrading, the ActiveSync program will not go on, however the upgrade is running.
After then, install origial ROM. (u can try T-Mobile MDA Software Version (2.26.10.2) )
Let me know if it's working
ty man for ur reply , i have tried every possible solution, including mtty! no luck. from ur post i didnt understand the following
Go online and find botton run , update utility 2.00.1
Click to expand...
Click to collapse
did u mean button rom . if yes , what the 'update utility 2.00.1' ?
ty
can i use mtty to revive my phone? i found some command for erasing my entire rom in the phone , but it doesnt seem to work . help me
I just tried to upgrade my XDA EXEC and it was not succesful. After this attempt my exec is dead, I can't turn it on it is still showing boot loader "Serial" on the screen without backlight (when connected to PC is showing USB instead of SERIAL). When I try to upgrade it is always unsuccesful.
I'm working under Vista, maybe this is the issue.
Used different roms and all with the same effect.
Tried to run mtty before upgrade but it is showing "can not open usb port".
Has anyone idea how to sort it???
Welcome to forums
If you already read the Wiki:
http://wiki.xda-developers.com/index.php?pagename=HTC_Universal
And still have problems, try to reflash ROM on a windows XP machine
Good luck,
flashing with vista
Hi all,
I have Universal.
I have never been able to flash any rom's with vista.
Why??After all, Vista doesn't need Activesync.
By the way, how can the LEDs under the keyboard be blue on the pic above?
(Mine is red.)
Yes you can flash in vista and to sync you use windows mobile device center instead activesync, but for new members is always more easy to flash the 1st time on XP machine.
The blue light on the keyboard can be changed (at least not that I know)
That is something related to the Universal model you have.
Check here to see all different models:
http://pdadb.net/index.php?m=pdacomparer&id1=371&id2=312&id3=313&id4=311&id5=148&id6=149
As far as I know the only blue light is the O2 Exec
dear all,
first at all: I´m completely new here, so hello.
I finished reading the Wiki twice, also the guide from 'mskip' (Flashing your First GSM Raphael Rom (For Noobs)). very good and sounds very easy.
now I downloaded this file: RaphaelHardSPL-Unsigned_190_1_3
when I´m trying to flash, it results in a "error 202: connection". could the windows mobile device manager be a reason, because here is just an explanation with activesync. as I use win7 64bit, activesync will not run.
I also checked lots of posts here, but did not get a right answer which could lead to a solution.
btw I have the "MDA Vario IV"-version.
greetings, tris
EDIT:
Update: Now I downloaded "TAEL ROM v6.28244 RC2".
Connected mobile to PC, waited until it is connected via 'windows mobile device manager'.
Proceeded with the update (my image is 1.69.111.6) until the screen turned black and a progress bar is shown (0%). now error 262 appeared. have to unplug USB cable, reinstall battery and restart. old system is still working. what am I doing wrong? btw, same error on my laptop with win7 32bit with fresh installed 'windows mobile device manager'.
EDIT2: okay, and same on my other laptop with winXP and activesync.
You need to flash hard spl before doing anything else. Try putting the phone into bootloader (hold volume down, then soft reset), then connect it to your PC once it's in the tricolor screen and run the hard spl exe.
After that, just flash roms off your sd card. Make sure it's FAT 32 format, rename the ruu_signed.nbh to RAPHIMG.nbh, put it on the sd card root, and then go into bootloader and follow the instructions.
volume down and reset done. phone switched to tricolor screen. then I started 'RaphaelHardSPL-Unsigned_190_1_3', phone switched to gey screen with progress bar. 30 seconds later after 0% progress: error 262 appeared
EDIT: also when trying to update via bootloader, my image (1.69.111.6) will be left blank, I can´t see the version number which is currently installed.
I just hope you have a GSM TP/RAPH...
RAPH300 -> "T-Mobile MDA Vario IV"
but why do you ask? do I have the wrong software?
Just hear of those bad incidents with CDMA phones and GSM ROMs is all...
What does it display on the bottom of the screen when you boot into the tricolor screen/bootloader before you connect it to your PC and then after?
first serial, later USB
oh my god! *facepalm* okay for all the noobs out there: look at your phone. if you use HardSPL for the first time, you have a short timeframe to confirm "unsigned access to bootloader" via touchscreen. if you don´t do so, you will result in connection error 202 / 262.
thank you all, it works
Hi folks,
I wanted to upgrade my HTC Universal (64) with WM5 to WM6.5 with this:
TOMAL V9 64MB WM 6.5 23004.exe
On the first try the tool recognized the current versions of the images and showed me which versions will be installed.
After starting the process my USB connection got lost (happens sometimes ) and the patching crashed.
I made a hard reset (the two Soft-Buttons + Stylus-Reset). It showed "Press 0 to restore factory default, Press X to exit", which is meant to install the system from the ROM, after the update from the new ROM. (But the ROM exchange seems to be interrupted and corrupted.)
The screen showed "Serial" and this serial number with no backlight, after reconnecting the USB it showed USB.
I made a second try with the Patch-Tool above - but now no versions were found and shown - neither as current nor as new. And the tool stuck.
The "Serial/USB /w serial number" issue is a known situation and could be fixed by using MTTY like in here:
http://forum.xda-developers.com/wiki/index.php?title=Universal_Problems
But after the fix and new hard reset the screen is empty and the light off.
It cannot connect with MTTY anymore because it won't connect via USB (active sync processes are off) - the USB port isn't available anymore.
And: I get to the recovery screen ("Press 0 to restore factory default, Press X to exit") simply by pressing the two soft buttons - without pressing the Stylus-Reset-Hole.
I never had that and I don't know what to do - and be sure that I searched the net and, of course, this forum but I didn't find a solution (because I didn't find this exact problem).
Anybody any ideas or experiences with this situation?
(Don't tell me it's bricked. It's NOT bricked! It'll never be bricked! )
momo