Database Users

[Q] Help! Wildfire crashed, tried hard reset and it won't restore!

Hi all,
I had a terrible catastrophic failure today with my 1-month old HTC Wildfire. I bought my device new, unlocked, in Singapore.
Here's what happened:
Today I received an ordinary SMS (like I have hundreds of times before in the past few weeks) and when I picked up the phone off of the desk, flipped on the screen, and slid my finger to unlock it, I saw a brief error message in a dialog on top of the Messages app. It was something like "com.something .... ", I didn't get a good look at the error but it didn't really mean anything to me at the time. The SMS that I received was then lost (I knew who it was from, but the message was not showing up). A few minutes later, I heard another SMS notification. No error message this time, but again the message did not show up in my Messages app.
So, I pressed the power button to power cycle the phone. After I shut it down, I turned it back on, saw the white screen with HTC logo, then black. It was dead. No amount of pressing buttons did anything.
After a few minutes, I removed the battery and it turned on again. Again, white splash screen and then darkness. Repeated this several times and same result.
Finally, I googled how to do a hard reset. I followed the instructions, held the volume down button while pressing power, cleared the memory, after it restarted it went right back to the white bootloader screen, flashed some error messages, and now I'm stuck in the bootloader. When I select the RECOVERY option, I get a quick screen with something like:
SD Checking ...
Loading [SOMEFILE.zip] ...
No Image!
Loading [SOMEFILE.zip] ...
No Image!
....
....
No Image or Wrong Image!
Can anybody help??! I don't know what to do now. I've searched for this "No Image or Wrong Image" message on these forums, but all the results are about rooting and loading different ROMs. I've never rooted or anything out of the ordinary, I just want the stock OS back and operational.
Btw ... I'm an Android noob, but an experienced Linux/Mac user and 10-year software developer.
Any help is greatly appreciated.
Thanks,
Nate

Recovery mode is something else.
To do a hardreset try the following:
Performing a factory reset using phone buttons
If you cannot turn on your phone or access the phone settings, you can still perform a factory reset by using the buttons on the phone.
1. With the phone turned off, press and hold the VOLUME DOWN button, and then briefly press the POWER button.
Note: If you are not sure whether your phone's power is turned off, remove and then reinsert the battery.
2. Wait for the screen with the three Android images to appear, and then release the VOLUME DOWN button.
3. Press VOLUME DOWN to select CLEAR STORAGE, and then press POWER.
4. Press VOLUME UP to start the factory reset.
Click to expand...
Click to collapse
Source : http://www.htc.com/www/howto.aspx?id=3567&type=1&p_id=316

Call HTC support. I had a problem with my previous HTC phone, and they took me through diagnositcs over the phone, and when they diagnosed a hardware fault, sent a courier to pick it up from me the next day. This was when the phone was 18 months old. No receipt was necessary, they used the serial number/manufacture date.
Downside: the phone was gone a week, and came back still broken. It was sent away again, and came back fixed. So painfully without it for two weeks, but not a bad experience.
(edit: it was a similar problem: I upgraded to windows 6.1, and my phone wouldn't get past the initial hardware/boot screen)

I tried the hard reset procedure several times. Every time it's the same thing. After it clears the memory, it says "Reboot in 5 seconds..." and then when it reboots, it goes back to the bootloader screens.
I've contacted HTC support via email, and I'm bringing it in to their support center in Singapore tomorrow. I really hope it doesn't take a week ... I'll keep you updated.

Fixed.
I just got my Wildfire back today after a full week in the repair center. Apparently they replaced the main system board. No other explanation for the problem was given.
The repair process itself was hassle free, although I was frustrated by not having my phone for a week. Ended up having to buy a cheap basic phone for $55 to get by on SMS and voice.

Restarting Sense,

Sorry for jumping in here. I've got one of those winmo HD2 jobbies.
But a non computer literate friend of mine has a problem with his legend.
The notification swipe from the top keeps randomly obscuring the screen when he's using the phone. Mid text. half way through dialling. Just when you don't want it the notification pane will swoop down and obscure everything.
Is this a known problem?
Is there a widget to restart just the sense part of the phone without doing a full soft reset? (I have such a button on mine)
He has updated the software with the latest release from Vodaphone and it still does it.
Any tips?
Thanks loads
Al

You can restart Sense by closing it in the running Applications list, or by using any application management app.
However, from the description of the problem I'd say there is something wrong with the screen. I had similar symptoms on my 2nd legend when the lefthand 8mm of the screen went wonky. There are multitouch test apps in the Market which you can use to check the functionality of the screen, they helped me pinpoint what was going on.

Had it before. The way I do it is to swipe it down again and you can swipe it back up. The other way is to flash another ROM. That did the trick permanently for me.

restarting sense
Ace Melon said:
Sorry for jumping in here. I've got one of those winmo HD2 jobbies.
But a non computer literate friend of mine has a problem with his legend.
The notification swipe from the top keeps randomly obscuring the screen when he's using the phone. Mid text. half way through dialling. Just when you don't want it the notification pane will swoop down and obscure everything.
Is this a known problem?
Is there a widget to restart just the sense part of the phone without doing a full soft reset? (I have such a button on mine)
He has updated the software with the latest release from Vodaphone and it still does it.
Any tips?
Thanks loads
Al
Click to expand...
Click to collapse
Hi,
I have the same issue on my Legend, seems total random.
I have to restart my phone in order to get it back to "normal"
As this seems to be a software bug , I really hope they will fix it in 2.2
(if we ever get it

Thanks for the replies. He's taken it back to the shop and told them to fix it.
Now he's worried he's going to get a reconditioned/refurbished one instead of the shiny new one he took in.
No pleasing some people

[Q] Beware - N7 screen crash while updating to 4.1.1

Hi Guys,
My N7 just arrived and it worked great out of the box - wifi connected, Google account connected. JB 4.1 pre-installed... then...
After about an hour of the tablet being on it came-up with a update request to take it from 4.1 to 4.1.1 - i accepted with the power lead in and power on.
The software lost control on the screen leaving it black with various shades of grey streaks across it. These change when the screen is touched - indicating the software is probably good underneath but the screen visual interface has crashed. Probably the display driver chip needs power cycling, else a feature of 4.1.1 is faulty in hardware?
Does anyone know how to recover from this - as there is no external hardware reset, the battery can't be removed, etc ?
I called Google (Call us at 0800 328 6081) and the guy told me to hold the power button in for 10 seconds which I did but the N7 just went off and came back on the same.
He then told me to hold in vol-up and vol-dwn buttons before holding in the power button. Again the device went off but came back on the same.
I include a picture of the N7 display after the unsuccessful 4.1.1 update.
Image https://docs.google.com/open?id=0B3oSwFvF1cmebXE4S2lvZlNlU0E
Cab

Also beware that lack of pirates is the the cause of global warming...
http://www.forbes.com/sites/erikaan...he-lack-of-pirates-is-causing-global-warming/

Looks like a defective unit. Not sure what pirates have to do with it.
Via my HTC Rezound

CrazyPeter said:
Also beware that lack of pirates is the the cause of global warming...
http://www.forbes.com/sites/erikaan...he-lack-of-pirates-is-causing-global-warming/
Click to expand...
Click to collapse
Thank you for being a productive member of this community, xda would not survive without you.
Sent from the matrix. (or my phone)

Not a good sign that it's doing it in fastboot mode. You can try leaving it in fastboot mode to drain the battery then plug it in and try again. Or, search for the instructions to reapply the stock 4.1 image. If those don't work then RMA it.

That looks very familiar.
A few minutes after the update (which I installed about 10 minutes in to receiving my new Nexus 7) I immediately had a total screen lockup/crash with lovely multicolours.
After that, any subsequent reboot/factory reset, the lockups continued and became more an more frequent until after just a day the device was completely unuseable.
I don't think the update caused it. I think it's factory defective and probably related to a messed-up Tegra 3.

Thanks for the feedback guys - I'm gonna RTM it as advised. A good unit shouldn't go wrong at all when just out of the box with no 'normal' or 'strange' apps added. It just had pure google stock on it.

cabello123 said:
Hi Guys,
My N7 just arrived and it worked great out of the box - wifi connected, Google account connected. JB 4.1 pre-installed... then...
After about an hour of the tablet being on it came-up with a update request to take it from 4.1 to 4.1.1 - i accepted with the power lead in and power on.
The software lost control on the screen leaving it black with various shades of grey streaks across it. These change when the screen is touched - indicating the software is probably good underneath but the screen visual interface has crashed. Probably the display driver chip needs power cycling, else a feature of 4.1.1 is faulty in hardware?
Does anyone know how to recover from this - as there is no external hardware reset, the battery can't be removed, etc ?
I called Google and the guy told me to hold the power button in for 10 seconds which I did but the N7 just went off and came back on the same.
He then told me to hold in vol-up and vol-dwn buttons before holding in the power button. Again the device went off but came back on the same.
Cab
Click to expand...
Click to collapse
Ok, I was about to post this very thing. Mine went red. Bright red. Nothing worked. Took it back to the store and it turned on fine and looked good...until the manager took it and flexed it a bit. Then, bam. Everything flickered and turned red.
So now I have new one (N7 16gig) and its working great. But the alert comes on telling me to upgrade to the 4.1.1. No way in Hell!! It's an hour drive back to the store to get another.
So what's the solution. Anyone else have this happening?

That is a very strange thing to happen. Although I dont think you should tell people to beware of upgrading the tablet because it makes it sound like it will happen to all tablets when upgrading. When I did mine it happened with no issues whatsoever.

jonnyg1097 said:
That is a very strange thing to happen. Although I dont think you should tell people to beware of upgrading the tablet because it makes it sound like it will happen to all tablets when upgrading. When I did mine it happened with no issues whatsoever.
Click to expand...
Click to collapse
I was not telling people to beware of upgrading. I was asking if others had experienced this.

cr2crf said:
I was not telling people to beware of upgrading. I was asking if others had experienced this.
Click to expand...
Click to collapse
So I finally updated the os to 4.1.1 Success. Hoping this little tab keeps going. The more I play with it the more I am glad I got it and not a 10 incher

Were these affected units stock unrooted? As a general rule you always want to revert back to stock unrooted before applying any OTA updates.

Touch Screen Unresponsive - RMA?

Hi,
Was just browsing my gallery when the touch screen would respond, along with the back and window change button. However the home / finger print button did work as I was able to get to the home screen.
However I restarted the phone and I couldn't pattern unlock due to the the screen being unresponsive still. Booting into TWRP has the same issue and I cannot use the screen to decrypt.
Anything to try before RMA?

Have you tried applying some pressure to the screen?
Other than that, the best option is to RMA. Sounds like some loose connections

Rhoban said:
Have you tried applying some pressure to the screen?
Other than that, the best option is to RMA. Sounds like some loose connections
Click to expand...
Click to collapse
Cheers. Managed to flash the stock kernel via fastboot (was on Franco) and it's now back to working. Very odd...

Just to update, my note above was coincidental. Basically the screen would stop responding and I would need to restart or leave it off for a few minutes before it would start working.
A few weekend's ago it happened again and wouldn't work, regardless of how many restarts.
I contacted Oneplus support on the Sunday and arranged an RMA. Phone was collected Tuesday, repaired on Friday (new motherboard) and returned to my door the following Tuesday. Very happy with the one week turnaround and very smooth and painless from Arvato (repair centre based in the Czech Republic).
Phone is now back up and running!

Amos91 said:
Just to update, my note above was coincidental. Basically the screen would stop responding and I would need to restart or leave it off for a few minutes before it would start working.
A few weekend's ago it happened again and wouldn't work, regardless of how many restarts.
I contacted Oneplus support on the Sunday and arranged an RMA. Phone was collected Tuesday, repaired on Friday (new motherboard) and returned to my door the following Tuesday. Very happy with the one week turnaround and very smooth and painless from Arvato (repair centre based in the Czech Republic).
Phone is now back up and running!
Click to expand...
Click to collapse
Can i ask where you live? Sounds like a great service you've received from op :good: maybe it's not in every country...

strongst said:
Can i ask where you live? Sounds like a great service you've received from op :good: maybe it's not in every country...
Click to expand...
Click to collapse
United Kingdom. Next day delivery to and from the Czech Republic via DHL.

Amos91 said:
Hi,
Was just browsing my gallery when the touch screen would respond, along with the back and window change button. However the home / finger print button did work as I was able to get to the home screen.
However I restarted the phone and I couldn't pattern unlock due to the the screen being unresponsive still. Booting into TWRP has the same issue and I cannot use the screen to decrypt.
Anything to try before RMA?
Click to expand...
Click to collapse
I'm having the same problem as you. I took a picture and then tried to view the photo when the touchscreen stopped working completely with only the fingerprint button that works. I restarted and got stuck on the lockscreen. I fixed the touchscreen problem after deleting the lockscreen keys in trwp... so I don't know if it is a hardware (motherboard) issue for me or just a software bug. I still have 2 more months left in warranty,
The other problem I'm having now is that trwp is asking me for a password that I never set. And when I boot into the phone, I have a blank screen and cannot set a new pin/password or anything. So essentially, my device is encrypted and I can't access my data. I think doing a complete format in twrp will fix it, but it will also erase my internal drive. Just wondering if you have come across this issue with your phone and if you have a solution?

Samsung A40 not responding after official update

Hey everyone,
Today my Samsung A40 was due a software update, so I downloaded the update and left it to install. However, since it has installed my phone is completely unresponsive. I have tried doing a soft and hard reset, and followed every Youtube video suggestions like tapping the phone screen and rubbing the back cover (?). But still nothing.
The phone looks like it's on - there's a very very faint light, but it remains black soon after the Samsung A40 logo goes, and when I try to call it from another phone it goes straight to voicemail.
This problem already happened once after a system update and a phone repair shop was able to fix it for 20$ but of course he did not tell me what was wrong and I cannot get a hold of him now.
Unfortunately the phone is outside of its warranty period so sending it back to Samsung isn't an option.
If anyone has any further suggestions I'd appreciate it

that's what i mean for reset, it is just a restart really.