This happened a couple of weeks ago, but I decided to post it because I want to help others and I am always open to some explanation as to why this happened. By way of background, I have had 2 HTC MDAs, a G1, and a Dash, amongst over phones. I've been flashing ROMs for probably 5 years or so, and I'd specifically flashed the Dash at least a dozen times. About two months ago I finally got off Windows as my primary OS. I am running Ubuntu 9.04 and Sun's Virtualbox on all my systems with Windows VMs. It has worked brilliantly, and by using this setup I still have access to all my apps that will only play nice with Windows including Outlook and Activesync. I've even flashed a ROM to the Dash from within Activesync before.
HOWEVER, in early July I tried to flash the 3VO 7.01 ROM to the phone using the same cable and same laptop I've used before. Battery was fully charged. I got some error about communications being interrupted or something and it walked me through recovery and restarted the flash. I got some other error and had to take out the battery and after I booted the phone again I restarted the flash and I got a similar error. When I looked at the phone, it was COMPLETELY DEAD. It would not turn on at all, even holding the center button, two soft buttons, etc. I took it to the Tmo store the next day and they plugged in a new battery and nothing. Nada.
If anyone has used Virtualbox for this, when the flash script is run and it goes through the steps and switches modes it will change the recognized USB device type at some point. To complete it in the past I had to re-enable that USB device for the VM to actually start the flash from the tricolor screen. This time when it switched modes was when it died. I didn't realize it could brick this way, but apparently it can and I have made a note to self not to flash from a VM Windows box ever again.
Just thought I'd pass it along as a warning to others.
Can u reach the bootloader by holding the camera button while powering on?
A red-blue-green screen should appear..
No, in fact it shows no sign of life at all, though it worked fine before this event. It won't even show a charge light when plugged in.
Hmm this is something that should be posted as a warning on the wiki for everyone to remember when updating their phones. I have never used a virtual machine for any type of flashing of any thing.
Yup, and I bet we all expect it is going to become a more common occurrence, even if it isn't a mainstream situation...
Related
I have an extra Excalibur with the official T Mobile WM6 rom that isn't working. When I turn the phone on, I get a screen with a white background, red text, and blue soft key buttons that reads:
Device start up failed dueto s
udden loss of power. Please c
lick "yes" to continue.
Note:
Do not remove battery be
fore device has been comple
tely shutdown (OFF).
Yes | No
If I press yes the phone does a power cycle and hangs at either the T Mobile splash screen or the WM6 splash screen. I've had no luck with a hard reset. Anybody familiar with this issue? It isn't a huge deal. Currently I'm using a Cavalier and I also have a working Excalibur and a working Wizard, both with 6.1 roms. However, it's be nice to get this phone working.
Only time I ever seen that error is when I ws messing with editing a ROM and must of removed a file that screwed WM up. Now since you say it's the official T-Mo ROM maybe it got currupted somehow. How I fixed it was the Hard Reset the USB way. Hold down the camera button while plugging in the USB with the cell off. It'll load the boat loader and you need to reflash with an official ROM. Now I know you said you Hard Reset, but I've seen people explain a few differents methods all being explained as Hard resetting. This method worked for me during my testing.
I'm flashing the original rom and everything seems to be working alright.
I really appreciate your help man.
Okay, I wish I had better news but I'm still running into problems. After I finished installing the rom from T-MO's website, I powered the phone on. It showed the T-Mo screen, then the WM6 Screen, then played the T-Mo animation/sound. The screen stuck here, and the phone would not power off so I removed the battery and put it back in. I then got the original error message and pressed yes, and the phone lagged at the same point again.
how long did you wait for fist boot?
rickwyatt said:
how long did you wait for fist boot?
Click to expand...
Click to collapse
Like Ricky said, how long did you wait? The first boot could take a while, the flash is going to perform a "Cold Boot Config". It take a bit longer that first time to load.
I actually got it to prompt me for cold boot config once, but after finishing the phone rebooted and hung once again.
I don't know, maybe you got a hardware problem. I'd try reflashing it again and when it boots the first time don't touch it and see what happens. If it hangs for more then say 10 mins. I'd say you might be having a hardware problem.
Hmm. I guess I most definitely have a hardware problem. An error of that sort would most likely be from a faulty motherboard, correct? I have a dash that was taken into the lake not too long ago. Everything recovered okay, other than the screen. The phone no longer turns on for a completely different reason, but I think the guts are mostly good.
Is it possible to change out motherboards? If so, is it unwise to try the motherboard that went swimming with me over the summer?
Well considering neither work, what do you have to loose? lol I say try swapping aprts and see what comes of it. I have seen cells "go swimming before and servive as long as the battery is removed right away and it's allowed to dry thoroughly. They don't opperate on much voltage so short curcuits due to water is not as bad as say a 12 volt or higher device.
Also, I forgot to mention the status on the phone. Okay, I can flash an official ROM and it will boot up and run Cold Boot Config. After that the phone will power cycle. It hangs a little bit at the T-Mo splash screen, but does eventually start. At that point it basically works flawlessly, except I cannot detect it through ActiveSync via USB.
Once the phone powers off, it will not turn back on. I don't get the original error message, just nothing happens. Only way to get the phone turned on again is to hold the camera button down while plugging in the USB cord, and start all over flashing an official ROM.
Yeah, I would say hardware failure. It's a complete new flash so it shouldn't be suffering from a software problem. Maybe the ROM Chip is damaged causing errors to the WM installation. Same thing as a bad hard drive in a computer that will currupt files and end up crashing the system.
drkfngthdragnlrd said:
Yeah, I would say hardware failure. It's a complete new flash so it shouldn't be suffering from a software problem. Maybe the ROM Chip is damaged causing errors to the WM installation. Same thing as a bad hard drive in a computer that will currupt files and end up crashing the system.
Click to expand...
Click to collapse
That's exactly what i'm thinking too, sounds like a hardware error as a flash wont solve it.
So what piece of hardware is the most likely culprit?
I never took mine apart, but I would say it's the ROM Chip which should be soldered to the motherboard. If it is replace the whole motherboard...
t mobile dash
so when holding down the camera key and plug the usb do i try to also turn it on what am i looking for and how long do i hold the keys down
thank you
Hey guys, i just got a new T-Mobile Dash and it's started acting up from day 2. Turned it on today and it doesn't work, it doesn't get past the Windows Mobile screen (from what i've seen this looks like a fairly common issue). After reading around i've tried to flash to numerous roms but only 2 of the official t-mobile roms have worked (others gave error 270, wrong vendor, wrong device, etc) but still the phone doesn't get past that screen. I've tried to do the hard-reset trick a bunch of times and still no go, any clues? Thank you.
hacktek said:
Hey guys, i just got a new T-Mobile Dash and it's started acting up from day 2. Turned it on today and it doesn't work, it doesn't get past the Windows Mobile screen (from what i've seen this looks like a fairly common issue). After reading around i've tried to flash to numerous roms but only 2 of the official t-mobile roms have worked (others gave error 270, wrong vendor, wrong device, etc) but still the phone doesn't get past that screen. I've tried to do the hard-reset trick a bunch of times and still no go, any clues? Thank you.
Click to expand...
Click to collapse
Take out the memory card and try to boot her up. If that does not work.. call T-Mo and get a new one
To get past the error 270, download the SDA Unlock app. That should get you past the error there. As for not getting past the Windows screen, I had that problem too. You should be able to get it working by hooking it up to the charger. I found that my Dash was not reading the battery as having a charge. I am not sure if I have solved the overall problem yet but, just in case, you might avoid using the USB as a charger and go with the wall charger. Just keep it on the USB long enough to sync and unplug.
Hope that helps
hacktek said:
Hey guys, i just got a new T-Mobile Dash and it's started acting up from day 2. Turned it on today and it doesn't work, it doesn't get past the Windows Mobile screen (from what i've seen this looks like a fairly common issue). After reading around i've tried to flash to numerous roms but only 2 of the official t-mobile roms have worked (others gave error 270, wrong vendor, wrong device, etc) but still the phone doesn't get past that screen. I've tried to do the hard-reset trick a bunch of times and still no go, any clues? Thank you.
Click to expand...
Click to collapse
do a hard reset hold da 2 soft keys and press the on button keep holdin da soft keys until u see a screen asking u do u want to do a hard reset hope dat works
Thanks for the responses guys but i've already tried all that. The only thing i haven't been able to try is do a hard reset with the wall charger plugged in, for some reason it doesn't matter how many times i do the steps it never shows me the black screen. I might be on the same boat as you because the battery i got with the phone is some cheap counterfeit chinese crap. I'll keep trying to get to the black screen with the phone plugged in but any other help would be greatly appreciated.
Btw, i can't do anything with T-Mobile because this is an unlocked phone i got somewhere else and can't return it so i'm stuck trying to make it work.
Check sticky to make sure doing correctly
Hard-Reset & Bootloader there is 2 x options there.
I was doing it right.
So after a million retries i got the phone to boot and do the cold boot thing. Then, i did the usual steps for putting a newer rom with WM6.1 on it (RUU_Excalibur_WM61_Kavana_080408_WWE). It worked, rebooted and went into the home menu, i thought i had brought it back from the dead until i inserted the sim. I got the sim failure message and when i pressed done it crashed. Now it won't go into the home menu no matter if the sim is inserted or not. Already tried to see if the sim was making good contact by putting pressure on it, no change.
This is too frustrating.
Ok so i've semi gotten it to work by booting it up without a sim, turning flight mode on, inserting the sim and then turning flight mode off. I get asked for my pin, the phone registers and i can make/receive calls. The problem is that a) it eventually loses the connection and b) i don't want to be doing this every time i turn the phone on.
Any ideas?
Hi,
Right in the middle of use, my ATT Tilt 2 went to a basic, dead screen with red, green, blue, and white bars that says Rhod300 32m SS-BC, etc.
The operating system seems have gone down--it won't respond to anything. Hard reset produces the same results.
Can I flash a cooked or official Rom back onto this? I think activesynch is needed for a normal flash and of course I can't use active synch with the phone in this condition.
I think probably what I need is an original ROM install. Is this possible with a normal Windows 7 PC and a dead phone?
I have so many Windows Mobile programs and peripherals that I am trying to avoid going to Windows Phone at all costs--at least until they have basic stuff like file systems, a way to port over notes, etc. Also need a hard keyboard.
Right now using an older Fuze, which works, but is slower, worse screen, smaller, and lacks some of the features I like.
Thanks for your help.
You sound like you're in the bootloader mode. Tri-color screen.
You can flash from USB or from SD at that screen. I'd recommend trying to flash a stock ROM - as it flashes everything. Assuming that works, hopefully you can flash back whatever ROM you were on.
The phone isn't dead if you're at the tri-color screen. It should say 'serial' at the bottom - when you plug in your USB cable, it should say 'USB' and install some drivers. Then with the RUU software that comes with every ROM, you should be able to flash it.
Phone won't reboot--stuck on tricolored boot screen
Hi,
Thanks so much for replying. I appreciate you pros helping us novices.
Just after I posted the first note, I pulled the battery and hit the power button, it rebooted, and everything was still there in the OS--working fine. But whenever the device had to be rebooted, I would have the same problem of it getting stuck in the boot screen. After that, for the last several days once in awhile, randomly, it would finally reboot from the boot screen after I pulled the battery and hit the power button. The rest of the time (about 5/1) it would just sit there in the boot screen no matter what I did. The "Serial"/"USB" thing would change when I plugged it in, but that's all.
Thought it was the OS, so at a lucky moment where the "pull battery, hit power button" strategy actually worked, I installed the latest official HTC/ATT Rom--it's the next to last one issued that ends in .4.
It was gorgeous and I got all excited--started installing stuff thinking my problem was solved.
Had to reboot to install some programs--now it is stuck again on the boot screen. Tried 30x again--no luck with the "pull battery/hit power button"
strategy. Sometime it would flash a white screen really quickly saying something like "Can't read image!" before going into permanent boot screen. The boot screen will switch from "Serial" to "USB" if you connect it to the computer. So, the problem doesn't seem to be in the OS--rather, in the ability of the device to "read" the OS from the boot screen.
I would be grateful if you or anyone else may know what's going on here, and any ideas on how to fix it. Is there any manual way to get it to read the OS from the boot screen when that's not happening?
I have two guesses (both of which may be wrong):
1. It may be something in the hardware is just worn out and is less and less able to read the Rom--any ROM. I got the phone new off Amazon for a profit of $50 ($.01 cost plus a refund for an older phone) in the summer of 2010 when it was already outdated. and WP was replacing WM. I've certainly gotten my money's worth after 18 months!
Of course we now know that a brand new ROM has the same problem as the older one--which suggests to me it's in the hardware. I'm sure the new OS and the stuff I installed is still there on the phone, but something it appears is not reading something in order to allow the boot up.
2. I have a squirrely free program called Rax Reset (from Windows Mobile Marketplace) that does a software-based hard or soft reboot from inside the OS. The very last time the device went down and didn't come back up, I had used that program to soft reset it. Might have been a big mistake. Could this program be causing the problem? If so, just one reboot would allow me to get rid of it or even hard reset to remove everything but the new OS--but can't get it to boot.
If it turns out the phone is just worn out, I've certainly gotten my money's worth.
I still love WM even with all its problems--and especially the newer Sense version. If this one is shot, I'm thinking about just buying a new Touch Pro2 on Ebay to avoid all of the sacrifices and backwards steps involved with Windows Phone.
Thanks for any help anyone can provide.
Phil Butin
Why are you crossposting? I read this EXACT same post in a thread just below this, in the same section. That's pretty low.. Crossposting across forums isn't welcome, crossposting within forums IN THE SAME SECTION is definitely not welcome.
Don't do it again.
Sorry, just trying to get help
Sorry, just trying to get help, not that familiar with the rules.
I searched on "bootloader" and found a thread (wrote a comment there too), but it's old....
Here is the thread. It doesn't really provide any solution.
HomeArrow
Legacy & Low Activity DevicesArrow
HTC Rhodium: Touch Pro2, Tilt 2Arrow
Touch Pro2, Tilt 2 GeneralArrow
issues with bootloader.
Either way, whether you know the rules or not - why would you think copying and pasting the exact same words in the exact same forum help you any more...
Anyhoo, have you tried the usual? Flash stock? Sometimes I've heard you have to flash several times, I never really understood that logic tho.
I'll try to reinstall the HTC/ATT Sense OS again. I guess you're saying active synch doesn't need to be working in order to do that. I'm at work now--have to wait until i get home. Nothing to lose at this point.
But I'm seriously wondering whether the problem is the OS install or whether there is something in the device that is supposed to read the ROM and start the bootup that is just wearing out.
Thanks.
"No Image File"
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
[email protected] said:
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
Click to expand...
Click to collapse
That error message is 'normal'. Basically the phone checks the SD card for a file labeled "RHODIMG.nbh". If said file exists, it will flash from it. If no file exists, or no SD present - it continues loading bootloader and should say "Serial" at the bottom. This indicates that it's ready to be flashed. If you plug in your USB cable, it will install some drivers and then it should change to "USB" at the bottom instead of "Serial".
Now you should be ready to flash from a normal RUU. I would recommend flashing STOCK, because this flashes everything.
It might also be good to note a lot of people have experienced something similar - the phone getting "stuck" in bootloader mode, and only occasionally making it to WinMo. I'd guess it's failing hardware in some way shape or form, as none of my RHOD's or RAPH's have ever done this.
Good News--at least for now
Good news--I hooked it up to the computer with the USB cable for awhile and the Windows 7 computer did set up some drivers. For some reason after I disconnected it I reset it, and the reboot worked. Then I immediately uninstalled the squirrely reset program and removed it.
Everything I installed yesterday is working fine--I have soft reset it about 5 times now and each time it has rebooted. So I think maybe I'm back in business. Too soon to tell--but we will pray and keep our fingers crossed.
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
[email protected] said:
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
Click to expand...
Click to collapse
You're welcome. Basically if I or someone else posts something helpful, click the "Thanks" button under that post.
15 hours later, Tilt 2 is still working fine on the newly installed Sense OS. I have rebooted freely (using the stylus button on the side) since removing the program "Rax Reset," and everything seems to be going well. I'm keeping my fingers crossed, and will end my contributions to this thread with a warning about using "Rax Reset."
Thanks to all.
I've had my Nexus 7 for a while, and I actually recently got a Nexus 10 and handed off the 7 to my fiance, who was using it to browse tumblr and read fanfiction, and that's about it as far as I can tell. I do have it rooted and unlocked and running Paranoid Android Beta 4.6 (and has been for a very long time), however since I haven't messed with it in so long I couldn't tell you anything else about it (kernel, etc.)
Since I know she wouldn't have tried to do anything like update or anything like that, my guess is that the problem is stemming from the fact that she just lets it die a lot, then charges it. She charged it all night and it would not turn on so she had me look at it. I tried everything I could think of, holding power for various amounts of time, both alone and in combination with either of the volume buttons to try to access fastboot or just anything. I should mention I even followed Google's troubleshooting steps, which involved strange charging times, having it plugged into the PC for a spell, then unplugging and replugging and trying to power on. But the battery icon does not even show up. The screen just stays black.
I plugged it into my computer to see if anything would happen, and it showed up in Device Manager as QHSUSB_DLOAD, so I googled this problem and it seems to be some sort of hardbrick where the bootloader is corrupted, and some people have found solutions for other devices, mainly HTC devices, but there doesn't seem to be anything that particularly pertains to this device. If I hold down the power button while plugged into the PC it will intermittently "disconnect" and "reconnect" (Windows plays the sounds) and disappear and reappear in Device Manager.
I'd like to try to fix it if I can, but I'm not gonna send it in for repairs/replacement or anything like that. I'd rather just buy a brand new device at that point, but if anyone somehow has a solution, I'd gladly welcome it.
Thanks so much!
I just tried to install the pie update manually by downloading the zipped update, renaming it and placing it in the root and dialing the code. The installer started and took about 10 minutes to complete and asked to reboot at the end. Now after the reboot the phone shows absolutely no signs of life anymore.
The phone soesn't turn on, doesn't respond when i connect the charger (it doesn't even get warm) and nothing happens when i try to connect it to my pc. Did i mess something up? Does anyone know a way to bring it back to life?
Faranite said:
I just tried to install the pie update manually by downloading the zipped update, renaming it and placing it in the root and dialing the code. The installer started and took about 10 minutes to complete and asked to reboot at the end. Now after the reboot the phone shows absolutely no signs of life anymore.
The phone soesn't turn on, doesn't respond when i connect the charger (it doesn't even get warm) and nothing happens when i try to connect it to my pc. Did i mess something up? Does anyone know a way to bring it back to life?
Click to expand...
Click to collapse
This happened to me after a day of updating to pie.
I noticed that my phone is charging very slowly.I used ampere app from play store to measure the current...and found that current coming through charger is too low(about 100 milli amphour) and i thought it might be my charger fault.
Then i used another charger and got same result....i was totally shocked.!!
I don't know if it is a software problem or hardware.
So today i'm giving my device to Nokia service center......and lets see what exactly the problem is..
I think this is my last Nokia device....i'm completely dissapointed by Nokia!!
BTW...i didn't do it manually i got an ota update.
Hi,
this probably will not help much, think i have the same issue.
i have had my ta-1050 get stuck on bootloader? ~3 times now over maybe 6 months of ownership, the last time was my update this weekend to Pie.
rather frustrating .
Can see the device is stuck in bootloader when i plug the handset in to my windows computer\device manager, can see and under com ports the is a QDloader 8006.
then need to wait ~2days for the battery to go completely flat, then plug into fast charger and it boots up again.
if take device to nokia, pretty sure i will get no fault found by the time they look at it.