Hi. I have a pda2k that has been working fine for months. Yesterday the phone quit. When I would tap the icon for the phone it would go nowhere as though it wasn't even there. I tried a soft reset and got nowhere. Then it just died. It comes up to a blue screen that says "i-mate" and "no gsm"
I tried everything I could find to fix it last night and now it won't even connect with my laptop. When I plug in the usb I get the sound like something was installed but it never shows up. Any ideas would be greatly appreciated. Thanks.
read wiki, try mtty for reseting the botloader defaults, try to upgrade your rom
Read and Re-read No Radio Stack
I've read everything on this site I could find about it. I even printed it and make my husband (the computer geek) read it. He understood a whole lot more than I did.
We finally got it doing "something" but it keeps getting stuck saying "installing radio stack" and will go no further. How can I get it past this point. We have tried everything we have found in the wiki and on boards. It boots as a pda just no phone. Help!
Related
My XDA2 has gone dead, it no longer responds to anything. what do i do to bring it back.
Whilst i was updating it, it had erased the system ready to install hte new update it came up with an error telling me to disconect the USB and then reconeect it. I did this but noticed that the phone had gone dead and wouldn't pick up on the laptop using active sync.
Is there anyway to bring the phone back. if anybody knows please help.
Thank you
what's showing on your screen? is it totally blank or is there something written like "usb version...something"? if yes or no; do a couple of hard resets...this brings back the unit to the bootloader mode. from there put it back on the cradle and as expected activesync will not do a thing. but what you do is double click on the upgrade file on your pc and from there it should start again. a couple of chaps in the forum ran into the same problem. what they did was continuously do resets (soft and hard) until the screen showed something.
don't fret, your unit just got stuck somewhere and simply needs a kick in the bum.
cheers
Dimmy_XDA2 said:
My XDA2 has gone dead, it no longer responds to anything. what do i do to bring it back.
Whilst i was updating it, it had erased the system ready to install hte new update it came up with an error telling me to disconect the USB and then reconeect it. I did this but noticed that the phone had gone dead and wouldn't pick up on the laptop using active sync.
Is there anyway to bring the phone back. if anybody knows please help.
Thank you
Click to expand...
Click to collapse
Maybe this can help you because it just happen to me last 2 days ago with my XDAmini.
1. Push the power and camera with the softreset pin together.
2. It will bring you to the bootloder mode. Then plug the USB sync cable to your unit.
3. Run the rom upgrade again. It will flash from there.
Hope this help.
My DOPD - bought in China was running a chinese version of WM5.0 and I wanted to install a english version.
After upgrading my DOPOD 900 with the upgrade : Universal_Upgrade_v1.30.68_radio_1.09.0.zip I have problem.
It is really DEAD. soft reset does nothing and a hard reset only gives the option of "0" and "X" which do nothing.
the USB is no longer recognised and nothing seems to want to communicate with the Dopod. It seems the USB loader program is no longer running on the Dopod.
Has anybody any idea how I can attach to the device an install a new bootloader, or something.
I had the same issue and I have a solution. But, let me tell you my process that got me where you are.
I tried performing the update using the No_ID (or whatever) method and kept getting errors. I rebooted my PC and changed the Operator ID using the HTC64 Extended ROM Tool.
After this, I was able to use the typical installer. The flash went fine and I hard reset as instructed. From that point on, I had your exact problem.
A dead screen. I was able to redo the hard reset after pulling the battery but I would just end up with the dead (blank) screen again. ONCE, I did get it into boot loader mode where I could actually read the screen. But, of course I reset and again had a dead screen.
My solution was to revert back to a true O2 ROM. Even though I couldn't see the screen (still can't), the ROM update is proceeding as I type this. I'm at 44% of the radio ROM installed.
Hope this gives you hope!
Well, good news. I just finished the ROM update and I'm looking at the O2 boot image.
Is there any indication that the QTek ROM looks for the Carrier info to be QTek or it will fail once installed? Just wondering why I had this problem.
ARG! Reflashing with QTek ROM did the same thing. :evil:
Blank screen and all.
check 2 things
uncheck usb from active sync
hardreset after upgrade has been completed
just do the upgrade again and it should come alive again
Thanks and another question
Well thanks for the hope. but I have tried this already with no luck, however after this message I will try again. My biggest problem is that I cant regain communication over the usb.
I would like to know how your system behaved when you plugged in your apparantely dead device. My system just says device un recognised and I cant begin a download with or without active sync.
So I cant get another rom image to download.
regards
Nick
dolebole said:
check 2 things
uncheck usb from active sync
hardreset after upgrade has been completed
just do the upgrade again and it should come alive again
Click to expand...
Click to collapse
This was the first thing I did.
The problem is that I cannot get any communication over the USB.
The device is unrecognised on USB and after starting any ROM download it just timesout after "checking information from device" message .
Ever seen a dead USB interface like this ?
The USB PnP mgr sees the hardware but cannot establish the device type !!
Nick
@mobinick: You and I have the same situation.
I have 2 Universal dead like this. 1 Exec and 1 Jasjar.
Both dead, blank screen, can not enter bootloader, can not connect with PC. PC can not recognize the driver usb of the device.
I opened the phone and found that logically everything is so so. There is no clue about hardware.
So I think: the address of the bootloader with device ID maybe unlucky damaged.
Who can fix this problem pls share us some experience.
Thanksss
ta_mobile said:
@mobinick: You and I have the same situation.
I have 2 Universal dead like this. 1 Exec and 1 Jasjar.
Both dead, blank screen, can not enter bootloader, can not connect with PC. PC can not recognize the driver usb of the device.
I opened the phone and found that logically everything is so so. There is no clue about hardware.
So I think: the address of the bootloader with device ID maybe unlucky damaged.
Who can fix this problem pls share us some experience.
Thanksss
Click to expand...
Click to collapse
Why don't you guys take it to your respective service centres and get it fixed?
Even if you have to pay something, it will certainly be better than these bricks occupying table space.
Have you tried going back to an original O2 ROM? I went to 1.13.139 WWE and all is fine now.
Just to share my experience with you guys here:
I posted my problem way back during the Radio Upgrade from 1.04 to 1.06. My Dopod 900 got stuck on the splashscreen. I couldn't get my device to pass the splashscreen even after upgrading/downgrading the radio ROM back and forth two times.
Finally, I just forced my device into bootloader mode (Backlight+Reset+Power). Even after doing this, the dopod screen was completely blank (no indication of serial/usb letter on the screen). I downloaded the official O2 exec ROM and plug my device (in bootloader mode) back to the USB port. It said unrecognized port on my PC. Despite that, I reflashed my Dopod back with the NoID tool the complete O2 ROM (Radio, Main ROM & The extended). Once completed, my device regained its consciousness.
I managed to flashed back the 1.06 radio after that. And has since been upgraded 4 times (two i-mate, one Orange and the latest QTek ROM) with no problem whatsoever.
I had the exact same problem as you to guys, i tried to update it, and it wouldn't budge...
It constantly, without fail timed out... I tried everything...
As my hope started to wain, i gave it one last shot...
I took out everything, sim and sd and battery, then connect the battery back and from the bootloader menu, connected it to the pc, with usb cable...
Finally it worked!! Like normal, i was able to load any and all rom and radio updates...
Wouldn't work, from the normal working screen (which was working for a while, i later tested this out, and found out ) and also wouldn't work, from the bootloader (power+backlight+reset) with sim+flash in there....
Hope you guys have some luck.. I htink you should, because i was in the exact same boots as you guys...
It worked for me
My O2 Exec did exactly the same thing, and I spent (on and off) 24 hours trying to get the damn thing to go again - wouldnt charge either....
I too finally took out everything, SIM and sd and battery, then connect the battery back and from the bootloader menu (which I only found about from this site), connected it to the pc, with usb cable...
It worked as well - bloody brilliant. I now have the latest 02Exec Upgrade (Version 1.30.162 AKU2 Release) and all is great.
Cant believe that 2 days after logging email with O2 site, they have not responded...
Would almost kiss you guys.....
Solution for getting stuck in bootloader
http://wiki.xda-developers.com/index.php?pagename=Instructions for those stuck on Boot Screen
I tried to upgrade the ROM n my trinity without putting the device in the SPL. The device went dead completely and I could not start it on. I tried to soft reset, hard reset, and tried to get the SPL but nothing is working. When I tried to upgrade it gives message 260 “no connection”. Could anybody tell me how to revive my trinity or get it working again?
Been there a few times myself.
Do you live in the US? If so, I could call you and walk you through it, or MSN chat, or??? or if you'd rather, let me know and I will try to walk you through it in here.
I am in Europe, time difference is large, appreciate if you give step by step instructions in this forum. Thanks again.
SuperSport,
Hi agin, waiting for ur instructions. I am missing my trinity.
Once agin thanks for ur help
Sorry to hear that...you can have a look here:
http://forum.xda-developers.com/showthread.php?t=299659
and here
http://trinityguides.info/index.php?option=com_frontpage&Itemid=1
hope that can help...
good luck...
jma81113 said:
I tried to upgrade the ROM n my trinity without putting the device in the SPL. The device went dead completely and I could not start it on. I tried to soft reset, hard reset, and tried to get the SPL but nothing is working. When I tried to upgrade it gives message 260 “no connection”. Could anybody tell me how to revive my trinity or get it working again?
Click to expand...
Click to collapse
I apologize jma81113. I was unexpectedly called out of town. My nephew crashed his motorcycle and is in the hospital, so I rushed over there. I'm back now.
Any time I cannot flash another rom, I am forced to flash back to an OEM rom, in my case, I use the one found here: http://www.dopodasia.com/download/RUU_Trinity_DOPODASIA_WWE_3.00.707.18_6275_1.46.30.11_108_Ship.exe
This flashes back the original SPL, Radio, OS, etc... It works best if you can do it from a Windows XP computer. If you don't have that option, there are ways to do it using Vista outlined here.
Then I always flash the Hard SPL found here. In my case, I use Des' Crash Proof. I've had the most success flashing Cooked ROMS with this one.
From there, Flashing Cooked ROMS should work just fine. If you run into trouble, you might have to flash back to the OEM ROM again. Occasionally, I have to. I keep a copy on hand at all times.
Oops! Actually, as I read back through your message, I see that you might be getting just a BLACK screen? Is this correct? And I assume by you saying you tried to get the SPL that you mean you pushed the 'power' 'camera' and 'reset' buttons and nothing? If that's the case, let me know and I'll do some more research.
Just so I know, do you get the orange LED lighting up when you plug in the USB cable showing it's charging?
SuperSport
I am sorry to hear about your nephew accident, I hope he is well and wish him well.
Yes I got a BLACK screen when I press the 'power' 'camera' and 'reset' buttons. The device is completely dead.
When i connect the device to the laptop, red LED lights up for 10 seconds and then disappears, I even changed the battery but no sucess.
Hard Reset?
Oops! Sorry, just re-read your first post. Looks like you tried this already...
The Black Screen is new to me, so I'm shooting in the dark.
You many have already done this, but, have you tried a HARD reset? Press the 'Calendar' 'Contacts' and then 'Reset' buttons all together. Hopefully this will bring up a screen that asks if you want to do a reset. Press the Green Send key and it will reset. Let me know if that works or not...
Buttons shown in attached image:
I have done it already no luck, it seems I am going to send it to the dealer in Malaysia. Thanks any way Supersport for your time and effort. Once again hope your nephew is will.
Hi,
I had the following issue recently with bootloader:
http://forum.xda-developers.com/showthread.php?t=375685
Thanks to all those of you who replyed.
Well I now have some further info but the problem is slightly different. The fix for my problem last time seemed random, I hooked up to my pc and the phone started booting fine.
So I have been using my phone fine for X number of weeks, no changes software adds updates or anything applied.
I have been using SPB Backup (A+ s/w) to do nightly scheduled backups, followed by a reboot. Two nights ago I found my phone on the bootloader screen !!
I hooked my phone up to my pc ready to re-flash it, and switched it on (the phone). Low and behold the phone booted fine. So off I trundled with a "working" phone.
This morning I woke up to a bootloader screen ! As a side niote the phone is on charge all throughout the night so as I get no issue during backups.
I hooked my phone up to my pc and switched the phone on and voila, it booted. So I set about doing the mtty.exe tasks listed in the above post. I ran "info 8" as suggested in the above thread and my output was identical (barring checksum values) to that described here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
Nothing strange that I could see and when I ran "task 2a" it appeared to do nothing.
I have re-flashed my ROM (Schaps 4.31) and the flash worked fine except when it re-booted, it went to bootloader. A quick phoen switch on with it hooked up to the pc via USB and it booted fine.
So quick summary:
Reboot of device causes bootloader screen to appear. Hooking it up to PC via USB and switching it on allows normal boot and the phone is fine then as long as it doesn't reboot.
Anyone have any ideas how I can fix this problem ??
ps Sorry it was a long post, thought I had better explain everything!
Dave
HARDSPL7 Olipro 2.10
HERM 300 - T-Mobile MDA Vario II
Schaps 4.31
Someone else has the same issue on this thread:
http://forum.xda-developers.com/showthread.php?t=381279
But, I think I have solved my problem (not sure if it is permanent) by powering the phone off and on. Not resetting, just a simple power off. I spoke to a colleague who said the way it shuts down is different to soft reset (makes sense) and I haven't powered my phone off properly for a long time.
I have tried soft reset a couple of times since doing this and it hasn't gone to the bootloader screen once.
Maybe this is the simple fix.
I will keep you posted.
My fix didn't work.
Can someone give me some idea what I should see when I run "task 2a" in mtty ? I ran it and it just gave a blank line and then went back to the prompt.
Help
might be dumb question but did you try reinstalling hard spl? might fix. also I would try to reflash to stock rom. wouldnt hurt, then flash to rom of choice. Cheers....
as for mtty it will flash up the bad blocks and tell you if its repaired or not. if there was no response then it means there were no bad blocks...
Basically, this: http://forum.xda-developers.com/showthread.php?t=1384415
No one responded to that thread because it was in the wrong forum.
I got the "Phone -- ! -- PC" screen, and was attempting to fix it before getting this black screen of death.
Galaxy Nexus GSM
Rooted, Codename ROM, don't think there is a Kernel in there
Carrier: Virgin Mobile
Edit: I won't be able to respond for a couple hours as I'm going to work. Any and all help is much appreciated.
Original post from above thread below:
Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.
Click to expand...
Click to collapse
What i with my little (almost nothing experience in android) would do its going to another computer with no drivers installed, would download the toolkit and install those drivers, then plug the phone and see what happen, im sure its not bricked since the computer recognice it.. I did lot of stuff with blackberry and there was a lot of ways to recover a phone like that... From here if the toolkit recognice it in any way.. Then you could try to do some of those steps.. As far as i tried doing all kind of stuff to my phone, toolkit its for much the Best Tool and way to do anything to your phone or at least for starters like me
Sent from my Galaxy Nexus using xda premium
But the computer doesn't actually recognize it. The "detection" sound it makes is for an unresponsive device. It won't charge, won't be recognized, and no matter what combo I use, it doesn't turn it.
I played dumb, called Samsung, and now I'm going to send it in. Thanks for the help though.
sometimes my screen goes blank and I have to pull the battery and everything comes back to normal