Hi,
My Star Trek (cingular 3125), every now and then displays "Searching for SD card" message then goes to the tricolor boot loader mode. This happens randomly when,
1. Restart the phone (press the power button)
2. After complete boot, it would automatically reboot and will stay in the tricolor mode. I am sure the "Searching for SD card" message would have preceded this screen.
3. Typically occurs when I use the phone normally.
Neither the USB cable is plugged in nor a bluetooth connection is active when this happens.
Currently my device runs on Pampooh's Windows Mobile® 6.1 Standard CE OS 5.2.20282 Build 20282.1.3.6 (English Only) v1.05b ROM.
I had the same issue even when I was running earlier version of WM6.1 ROM by Erofich.
Not sure what triggered this issue. I dropped the phone lately, there is a little crack on the LCD, but the phone works just fine.
Has any one seen this before? Any idea what could be causing this?
Thank you for your comments.
JSenthil
Related
my son's wallaby is having a mid life crisis!!, will NOT turn on at all, the screen is in dimmed mode, screen taps/menus etc etc not working, it is just displaying the message:
Upgrading...
will take about 5 minutes.
Warning: do not remove the
USB/serial connection or power
adaptor from the pocket PC.
problem is that this message has been displayed constantly for the last 24-30hrs!!, have tried a soft re-set...nothing, then tried a hard re-set...nothing, its showing full charge, and have tried removing the SIM and SD cards as well as doing re-sets...nothing!
Please Help!!
Thanks guys.
The problem is that you propably removed your XDA from it's cradle during ROM flashing.
Can you acces bootloader (hold power then press soft reset button) ?
...Not tried that, will give it a go,
thanks for the info.
..OK, I managed to get the boot loader screen up, and ran thru the checks...all appears ok, but none of the tests relate to the OS?, so when all had been checked, and I came out of the loader screeen and turned it on again, it went back to the "upgrading..." as above, just cannot get the windows menu up at all, and activesync doesnt recognise what device it is, but activesync works perfectly on mine..........is there another level/setup program that can be acessed??
cheers guys.
So, after having access to your bootloader reflash your device using SD-Card and bootloader.
Process is described in the wiki of often here in the forum...
Stefan
Hello,
i have install the german WM6 from http://forum.xda-developers.com/showthread.php?t=337022 by softSPL.
My device is a G4 Wizard.
i have change inadvertently one or two dll files from OS. (i know: never touch a running system, but i has open some explorer windows on my PC. One was conectet to my Wizard \Windows. i was distracted, so that i say OK and not Cancel, as the confime-question comes.)
I have also install an other Software, thats i know it's running without problems. => softreset!
now after reset the Wizard freeze on boot by the welcome-screen.
if i reset and press the camera-button i can see the screen with the thre colors red/.../... and and bottom the white bar. if i plug the USB cable, it's shows the message USB
have i a chance to restore the os? how can i do it?
thanks for help!
greetings Frank
Wizard no longer freezed on boot
My inattention get's me a sleeples night. But in the morning i started an desperate attempt to rebuild the OS.
And? => My Wizard is not longer freezed on boot! (verry happy!)
What i has doing:
0. if i will run Setup with SoftSPL from the hanging up-point, comes the Message "no device detected"
1. put out the battery and reinstated,
2. Wizard connect to USB and waiting for what heppens => jellow and green carge-LED was signaled the charging function (yeah!)
3. again put out and reinstated the battery (by connection with USB)
4. Power- and camera-Button pressed for go into the multicolored bootloder-screen => USB was reportet in the bottom white bar
5. now i wanted install the VF-ship ROM by using softSPL => Error-Message!
6. new trial: start the original install of VF-ship Rom without softSPL => Error-Message: No connection to device
7. again the steppes 3 and 4
8. now i start the original install of this official german VF-Rom: RUU_Wizard_2210301_22103102_021911_VF-DE_Ship.exe => well, connection to deviece and it's runnig setup!
After the original ROM-install the Wizard is rescued! It work's fine and stable.
So i can reinstall the german WM6.
But now watch, and no new mistakes!
greetings Frank
Ok so heres an update of what I have managed to do so far:
1.) I ran a file called titan_SPL_2.40-olipro.exe
~This seemed to kick me into a "Rainbow" screen. So at this point the program told me it was done, but not matter how many time I reset it I came back to the rainbow screen. So at this point I
2.) Ran a file called titan_radio_3.27.00.exe
~This file was required for the DCD2.3.2-Alltell.exe file, so I ran the radio file. All went well till it tried to reboot. Now all I get to is a splash screen that says Alltel. The first screen that says HTC does recognize the radio as being 3.27.
So I search and search and I then tried to famous MicroSD bootloader trick. So I take the nbh file out of the firmware installer that I was going to install, rename it to TITAIMG.nbh, I format my SD card as Fat32, I copy the file over to the SD card. I put the SD card in, I hold the record and power button down and press reset... then nothing. Just a black screen. I would like to note that while its at this black screen and I plug in the USB cable to my computer, the computer sees it as a data connection.
I'm so lost on this. All I want to have in the end of this is a working Alltel phone with GPS, so that I can use Tomtom 6 to use this $549 PPC as a GPS device.
Thank you ahead of time.
[SOLVED]
Wow I am so stupid... I was holding the Voice Command button and the power button, when I should have been pressing the Camera and Power button. LOL
Heres where I found my solution: http://forum.ppcgeeks.com/showthread.php?t=17909&page=2
and in case it gets taken down:
Found a solution. This is needs to be done once you load the DcD rom 2.3. Your phone will freeze at the splash scree. Follow the steps below to get the boot loader screen back up. Your computer will then see your phone. DONT RUN HARD-SPL... Run the RRU radio instead. Windows mobile should start right up after the auto soft reset.
Steps For Install:
1. put phone in boot loader mode can do so by holding in power button and camera button at the same time while pressing in soft rest button
2. run the unlocker and follow the on screen instructions
3. then flash phone with rom of your choice, phone will reboot and be stuck at splash screen put phone back into boot loader mode
4. then run the radio upgrade and follow on screen instructions and you should be all set
Deleted, seen that you solved it.
HTC have advised me to flash the ROM on my neon200 (Touch Dual 850 Telstra) to fix a battery/charging problem.
I can't do this via the provided RUU program (via ActiveSync) because the program checks for at least 50% battery charge in order to proceed to upgrade the ROM. The phone fails this test on account of the power management not working correctly.
Is there a way I can do this using bootloader and the micro-sd card? I'm hoping this would let me upgrade the ROM with the phone plugged in to the AC wall charger, and bypassing the battery check.
I tried copying EnterBootLoader.exe and RUU_signed.nbh (copied from the temp directory that the RUU program creates) to a freshly formatted (FAT32) sd card, and then running EnterBootloader.exe on the phone, based on advice I read here on the Nike. It shows the rainbow coloured screen, then flashes up a message which doesn't display for long enough for me to read, before going back to the rainbow screen. I think the message may say something like "Loading - no image found".
I don't really want to use any custom boot loaders at this point, as all want to do is updrade to an approved HTC ROM.
I'd appreciate any ideas on what the location and name of the .nbh file needs to be in order for the neon200 bootloader to detect and load it. Thanks
PS. I'd send it for warranty repair, but it was an e-bay purchase and I don't have the original sales receipt. The problem is that the 'today' screen says the battery is full (and therefore won't charge it up) but the WM power settings screen says the battery is empty (and therefore turns off the phone as soon as it's unplugged from a charger). Genuine new battery makes no difference.
Hope this isn't too late for you, but the way I did it on my Neon200 was:
- Rename the custom_ruu.nbh to NEONIMG.nbh
- Copy it to the root of the SD card
- Enter bootloader on the phone itself by holding camera and power keys, and hitting the reset button
- The phone detects the new ROM, asks you to press the power button to continue
- When completed, it shows 'success' on the screen and you just hit reset again.
Major problem with 8525. Not sure this question has ever been asked before.
When I got it , I SIM and CID unlocked it. Since then I Have tried various ROMs and can continue to flash the ROM and get the phone working. But I seem to have two problems. The first may go away if I can figure out the second.
Firstly I now have the new Tai ROM on it but I can boot it up and then after a few minutes, the whole unit seems to freeze. Sometimes it doesnt freeze immediately but it NEVER recognises that my t-mobile SIM is there.
Secondly, whatever I do, the computer never sees the unit at all. The unit sees the computer (I can get into the bootloader and on plugging the cable in, the screen switches from SERIAL to USB. But the computer still doesn't see the unit. EXAMPLE: I can try to re-run the unlock software but at the first screen where the software tries to transfer its first file to the unit, the computer reports that it cant see any device.
The bootloader reports HERM100 IPL 1.04, and clearly shows that the SPL is 1.40 Olipro.
On boot, the splash screen (without a SIM in it) shows just M 05 S 04 B 06 and D.335 Swiss
At no stage does the computer report anything in the systray showing that it can see the unit, neither when I plug it in with the unit off and turn it on, nor when I boot it up completely and then plug it in. The computer just doesn't see it. With the unit booted up, it can power the screen off, I can press the power button and turn it on again, I can see th e clock continuing to run, I can move about within the OS showing that it hasn't frozen just yet but there is no communication whatsoever.
Is this something as simple as getting to some screen as (on my Wizard) where I have to put a tick in an 'allow pc to usb' connection ('cos if so, I cant find it and cant see where one could do this to enable communication while the unit is in bootloader mode!)
I cant report that the unit is bricked because it isn't but where do I go from here please?