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.

Enter U.S. T-Mobile Vibrant Recovery Mode Guaranteed

THIS GUIDE WORKED ON USA T-MOBILE SAMSUNG VIBRANT BUT MAY VERY WELL WORK ON ALL SAMSUNG GALAXYS PHONES
After reading many XDA-Developers Forum Posts to try and figure out how to get into the Recovery Mode / Download Mode without any success, I gave T-Mobile Support a call.
After the usual noop run-down, "did you take the battery out" questions, I simply asked them how to get the Samsung Vibrant into recovery mode.
Unline the many tutorials that claim to require the Up or Down button pressed, along with the Home button then the Power, the true process is as follows:
1. Press the Up and the Down button at the same time (yes both). I too thought that button was a Toggle which only did either Up or Down, but found that in fact it does do both.
2. At the same time, press the power button.
3. As soon as the Samsung / Vibrant logo comes up on the screen, release the power button.
4. Release the Up and Down buttons.
5. PRESTO

Download Mode from Recovery Mode: Allows File Push through ADB
UPDATE
Once in Recovery Mode, to swith to what I believe is Download Mode, due to the fact that it now allows me to push files to the phone:
Click on the MENU Button from Recovery Mode.

You do relies the people with this download mode problem have hardware locked phones, rite?
Therefore they cant access recovery because the volume buttons dont work

I had a hardware locked vibrant and got to recovery the exaxt same way he described. Ill attest its true. Don't know about download mode though. Sounds interesting.
Sent from my DROID2 using XDA App

galonet said:
1. Press the Up and the Down button at the same time (yes both). I too thought that button was a Toggle which only did either Up or Down, but found that in fact it does do both.
2. At the same time, press the power button.
3. As soon as the Samsung / Vibrant logo comes up on the screen, release the power button.
4. Release the Up and Down buttons.
5. PRESTO
Click to expand...
Click to collapse
I can't get it to work. How long do you wait before releasing both volume buttons (step 4)?

You do realize that "hardware locked" means the volume buttons don't work ... right? Otherwise what do you think it means?

tgrantjr said:
I had a hardware locked vibrant and got to recovery the exaxt same way he described. Ill attest its true. Don't know about download mode though. Sounds interesting.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Then it wasn't a hardware locked Vibrant...

How do you know if your phone is hardware locked? Is the only impact that you can't get into recovery mode?

This technique has been around for a while and it simply does not work for hardware locked phones. There is no known way to get the HL phones into recovery from a power off.

ive tried this method many times on the 2 vibrants ive had over the past 2 weeks. hasnt worked. although i can get into download mode just fine.

Never mind wrong mode I was trying to describe

He used to think people don't know they should press both volume keys...

I dont think there is such a thing as "hardware locked" vibrants. I know people think they do have one but why would some be locked and others unlocked? It doesnt make any sense, the vibrant has only been out since July.

quest4fire said:
I dont think there is such a thing as "hardware locked" vibrants. I know people think they do have one but why would some be locked and others unlocked? It doesnt make any sense, the vibrant has only been out since July.
Click to expand...
Click to collapse
Well I can get into download and recovery on my phone easy. Now a fried just bought on and the same methods I use to get into those modes do not work period... so yes, some are locked... :d

quest4fire said:
I dont think there is such a thing as "hardware locked" vibrants. I know people think they do have one but why would some be locked and others unlocked? It doesnt make any sense, the vibrant has only been out since July.
Click to expand...
Click to collapse
Whether they are defective or locked the fact of the matter is yea there is such thing, people are not imagining it.
Take me for example My first vibrant was fine...my jackass friend knocked it out of my hand and chipped very tiny piece of the fake chrome bezel. I only had for week so I returned and said it had issues.
I made sure I could access recovery with new phone before exchanging. They only had 2 left both with Sept date. Powered it up and no go, tried couple more time and still nothing...it was locked, we didn't even try 2nd one.
He ended up calling a friend at T-Mobile store in mall and had him look and see if he had any with the same date as the one i was returning "August ".
He had one and he had him test before i drove down....he did and he was able to access recovery, went down to mall and sure enough it was fine, able to get into recover first shot....so yes there is such think as "hardware locked" vibrants
Sent from my SGH-T959 using XDA App

I have flashed a vibrant with a i9000S software but the radio did not work quite well. Since the two have different keys, now i cant get it to boot mode. i was able to get into recovery mode via ADB but all i can do is use vol to go up or down and not select an option. the device wont even get out of recovery mode.
Any help will be greatly appreciated.

Yes, some phones are locked. I had to get my Vibrant replaced, and was bitten by a different bug.
I went to my mom's and my niece locked my phone out by entering the wrong pattern incorrectly while it was charging (brand new phone, had to charge it... I typically don't use a pattern lock but since my first one was stolen....).
Now, the phone does not allow you to get into it using your Google Credentials.
Called T-Mobile and the woman said I'd have to send it in for a replacement because it's a "software glitch."
I asked her to try to factory reset it. She said her "researchers told her not to try it because it can brick the phone." We tried anyways.
Hold down both volume keys and power until the Vibrant logo comes up, then release.
Doesn't work. Hung up on her and went to a T-Mobile store. They tried for over 2 hours to factory reset this phone, and spend half the time on the phone with Tech Support to do it. You cannot access recovery mode on this phone. The other Vibrant here, that we checked, also cannot go into recovery mode. It boots straight up into the phone.
So:
1. Lots of Vibrants are unable to get into Recovery Mode/Download Mode
2. There is a bug in Android that will soft brick your phone if you or anyone enters the wrong pattern lock too many times - you will NOT be able to get back into your phone with your Google Credentials - at all. The phone will be useless.
Even though your phone can download emails from Google, and your sending them to yourself using the same login/password, you will not be able to authenticate your phone and unlock it.
Two pretty catastrophic faults, IMO.
When this next phone comes in (it will be brand new, like my first/second one - they're on backorder) - I'm immediately selling it, ETFing my account, and going to go phoneless (can use Google VOIP from a laptop/desktop over WiFi/Internet) and wait for a decent Win7 phone.
I doubt they will have such issues.
BTW, the Android bug I mentioned (not being able to unlock) has existed for 2+ years (since version 1.5 or before) and despite many people bricking their devices (and some devices being unable to hardware reset - like many Vibrants), Google has turned a blind eye to it, and keeps either closing the tickets or setting the priority to "medium" (Bluetooth functionality is critical, however - if you get my point).

For a long time i was under the impression that my phone was HW locked. i was on my last legs before sending out my phone for repair (im past the exchange date) so i called my carrier (Bell Mobility in Canada). They informed me i could do a restore through recovery mode -> to which i informed them that i could not enter after i had tried for 3 days previously. So the rep that i was speaking with advised me to do the following;
Turn phone off
Hold Vol+ & Menu & Power
Once screen displays Samsung release Power while still holding Menu & Vol+
Viola -> RECOVERY MODE
So, this got me thinking because if this got me into recovery mode -> download mode should be similar
Turn phone off
Hold Vol+ & Vol- & Menu & Power
Once screen displays Samsung release Power while still holding Menu & Vol+ & Vol-
Viola -> DOWNLOAD MODE
So, i thought my vibrant was hardware locked when infact it was simply just the wrong key combination to get into each respective mode. Not sure if i just wasnt reading some of the posts correctly or what but thats what worked for me.

That doesn't work on T-Mobile Vibrants.
The phone simply shows the Vibrant screen, then goes black and goes back to the Vibrant screen...
Over and over again. It can do it until the battery runs out. It will never get to the Galaxy S Screen as long as you have that Power Button down.
The only reason yours worked is cause your phone is not defective like many of ours.
I think I'm going to make a YouTube video of me using my Google Credentials (from a computer) to send myself emails while the phone syncs them in the background, yet refuses to allow me to use these credentials to unlock my phone - as well as rebooting to the Vibrant screen over and over again when I try to get into Recovery to reset it.
Because some people on this forum really like to act like problems don't exist, and tend to think their ignorance or operator error invalidates other posters' posts.
Congratulations on not having a defective device, though!

Looked it up and its real
http://www.youtube.com/user/stevec5375

16gb wifi stuck on update 27% 2-14-12

As the title implies, I'm stuck.
Notification popped up last night informing me an update was available. I had checked for any and all other updates just last week to make sure I was up to speed on things. I'm not a newb, but the tab is for my wife, so I keep it plain jane stock to avoid potential problems that could cause her to brick it.
Anyway, this morning I decided to finally click on the notification asking me to update. Device powered down and has been stuck on the 27% sign for 2 hours now. It's plugged in the entire time. It's also getting kind of warm. I'm afraid to do anything at this point for fear of bricking it.
Any help would be appreciated. I specifically talked her into the galaxy tab over the ipad, so avoiding "I told you so" from my wife would be icing on the cake with this one.
Any ideas? I can't seem to find any other threads here or via google that mimic this situation.

27% is where it starts to gettting really slow inching forward but not for 2 hours. For me it is like 30 miuutes or so.
But with Samsung updates, you take that risk everytime.
Good luck. You need it.

So where should I begin? Hold the power button and force a reboot? Leave it sitting all day and pray that it magically continues with the update?
Update: held power button, it rebooted on its own and is now stuck at 26%. I wonder what happens if I do it 25 more times?
Is this sort of thing covered under warranty?

do you know how to use odin? if you do i will set you up with a process to get you on the latest firmware without out dealing with Samsungs utterly horrible update process.

You end up fixing this?
I have the same issue!

I stumbled into a fix:
Hold down power button until it dies. Press and hold power button and volume DOWN button until the splash screen appears. Release power button.
Shows 2 options, one is an icon of an android getting out of a box. the other has "download" in it. Choose the one on the left of the android getting out of a box. Use the VOLUME selector to choose which one, and use the power button to select it. It will load the menu, using the volume button again, select the option to reboot and hit power button again. Should reboot you back to pre-update status with an error that says update failed and to try the update using Kies.
I'm a little hazy on whether or not I released the volume down button during booting. Keep trying it until you get there. You won't hurt it any worse than it already is, that's for sure.

[Q] Nexus stuck on 'X' screen, even after full wipe

So, a few days ago, I started having some problems with my stock Nexus 7 (not unlocked, no ROMs or anything like that). Some apps just wouldn't open, they would force close within a second of opening. Anyway, I think it might have stemmed from the game "Let's Golf 3", as problems started after playing that, and when going back in to it after a day of issues, a message appeared saying "Unfortunately, launcher has stopped" - it gave me the option to report or cancel, but whatever I pressed, the message popped back up. I pressed the sleep button, which seemed to turn my Nexus off somehow.
Then, when trying to to turn my Nexus back on, it just stays on the 'X' screen. I have done a factory wipe through the fastboot menu a few times, but it still stays stuck on the 'X' screen. To turn it off, I hold down the power button, but it just starts the process again automatically. The only way to actually turn the device off is through the fastboot menu.
I have seen talk of 'factory image' and drivers etc... but I am not too comfortable with that sort of thing. I know the basics of troubleshooting devices, but not much more. I am very wary of doing anything more than what the device provides me with.
Any idea how I can get my Nexus started, or am I going to have to look for a replacement?

If all else fails, then flash stock rom. If you're reluctant to do it the fastboot way, use toolkits. But it is very easy to flash a new stock rom. Go try it.

Leonhan said:
If all else fails, then flash stock rom. If you're reluctant to do it the fastboot way, use toolkits. But it is very easy to flash a new stock rom. Go try it.
Click to expand...
Click to collapse
Is that not for rooted devices?

Flashing the factory image for my N7, how do I know which version my nexus is? i.e. 4.1.2 (JZO54K) or 4.2.1 (JOP40D)?

AW: [Q] Nexus stuck on 'X' screen, even after full wipe
Gawge said:
Flashing the factory image for my N7, how do I know which version my nexus is? i.e. 4.1.2 (JZO54K) or 4.2.1 (JOP40D)?
Click to expand...
Click to collapse
Use the one you like, just choose the right one for grouper -> nakasi (wifi only) or nakasig (with simcard)
4.2.1 is the latest Android version...
Sent from my Nexus 7 running Android 4.2.1

mihahn said:
Use the one you like, just choose the right one for grouper -> nakasi (wifi only) or nakasig (with simcard)
4.2.1 is the latest Android version...
Sent from my Nexus 7 running Android 4.2.1
Click to expand...
Click to collapse
I too had the same problem. Tried everything. Finally gave it to ASUS service centre in Nehru Place. They will replace the mother board. May take 15 more days. So sad!

Okay, now the thing won't even turn on.
Holding the power button, and other combinations, nothing happens. No image comes up when charger is put in.
Feel like the thing is dead. Probably going to have to get it fixed or find a replacement. Don't want to spend too long without my Nexus

Gawge said:
Okay, now the thing won't even turn on.
Holding the power button, and other combinations, nothing happens. No image comes up when charger is put in.
Feel like the thing is dead. Probably going to have to get it fixed or find a replacement. Don't want to spend too long without my Nexus
Click to expand...
Click to collapse
FYI,
The tablet can "play possum" when it is in APX mode. (Which is easily entered from a cold start condiition with Vol-Up+Power) By that, I mean the device is on, but absolutely nothing ever appears on the screen. The only way to detect this is to plug it into a computer and the unknown APX device (USB Hardware Id VID_0955&PID_7330 ) will show up.
The only way to exit that mode is to hold the power button down continuously for 15-18 seconds. [size=+1]IF[/size] that happens, pressing the Vol-Down button immediately after the Google logo appears will pop you into Fastboot mode.
But, given that you have prior experience with other odd happenings on the tablet, the above hypothesis is a long shot, I'm more inclined to say "It's dead, Jim".
If everything fails let it sit for 3 hours on the charger (as long as it is not overheating or something) and try a few more things one last time before you ship it out.

bftb0 said:
FYI,
The tablet can "play possum" when it is in AVX mode. (Which is easily entered from a cold start condiition with Vol-Up+Power) By that, I mean the device is on, but absolutely nothing ever appears on the screen. The only way to detect this is to plug it into a computer and the unknown AVX device (USB Hardware Id VID_0955&PID_7330 ) will show up.
The only way to exit that mode is to hold the power button down continuously for 15-18 seconds. [size=+1]IF[/size] that happens, pressing the Vol-Down button immediately after the Google logo appears will pop you into Fastboot mode.
But, given that you have prior experience with other odd happenings on the tablet, the above hypothesis is a long shot, I'm more inclined to say "It's dead, Jim".
If everything fails let it sit for 3 hours on the charger (as long as it is not overheating or something) and try a few more things one last time before you ship it out.
Click to expand...
Click to collapse
Yeah, cheers, I have it on charge now, and i'll give it one last go.
What is the best way to fix/replace it? I bought it from Argos - will they take it back (bought back in December)?

Gawge said:
Okay, now the thing won't even turn on.
Holding the power button, and other combinations, nothing happens. No image comes up when charger is put in.
Feel like the thing is dead. Probably going to have to get it fixed or find a replacement. Don't want to spend too long without my Nexus
Click to expand...
Click to collapse
Service centre seems to be the only solution. My sympathies!

Gawge said:
Yeah, cheers, I have it on charge now, and i'll give it one last go.
What is the best way to fix/replace it? I bought it from Argos - will they take it back (bought back in December)?
Click to expand...
Click to collapse
Call Asus first. Make sure to let them know it is less than 2 months old. If they want you to perform the return through the original retailer, they will tell you. But it's best to eliminate any other middlemen if that is possible, as I suppose that the tablet ultimately goes back to Asus anyway.
(Might be different through other channels, e.g. PlayStore - I dont know).

Phone Won't Boot

Hello,
So my Nexus 6P turned off randomly and then would not turn back on. It would come on and show Google and sometimes even let me enter my pin to start the phone. But it constantly would freeze during start up and just shut down. I got into the recovery and factory reset my phone and now it won't even turn on. I hold the power and it doesn't do anything. I've tried the boot loader and such but it won't turn on at all. Any ideas on what I could do? Thanks!

edlovereze said:
Hello,
So my Nexus 6P turned off randomly and then would not turn back on. It would come on and show Google and sometimes even let me enter my pin to start the phone. But it constantly would freeze during start up and just shut down. I got into the recovery and factory reset my phone and now it won't even turn on. I hold the power and it doesn't do anything. I've tried the boot loader and such but it won't turn on at all. Any ideas on what I could do? Thanks!
Click to expand...
Click to collapse
Sounds like you may have more than one problem, but many have been able to get a dead phone to start by holding the power button down for a very long time, sometimes 2 minutes or more. If it doesn't start, fully charge it and try the power button again. Assuming you are stock with a locked boot loader.... you didn't mention.

My phone is stock with a locked boot loader. I held the button for over 5 minutes and got nothing. I'm wondering if Google would be willing to help me out. Unless anyone has other ideas

It's hopeless. Don't waste your time trying to revive. Contact Huawei regardless of date of purchase.

If it won't power on it's either not charged, a bad power button, or something with pcm. Which is on Motherboard.
Most common scenario is a bad power button because it's most used breakable part. That won't allow the board to receive power or not enough power if it's shorted.

Dunno if you've poked around the interwebs some more regarding this, but I've been slammed with the N6P bootloop error (which appears might be part of your problem) and I found a stop-gap solution. If you feel like you've got nothing to lose, you can try what I've done: Make sure the phone has a little charge, hold it with a hot mitt from your kitchen, and blast the back of your N6P in the region between the camera lens and the fingerprint sensor with a hairdryer. Doing so will trip the big cluster off, which is the source of the bootloop problem. If you can get it to boot to the Google logo, applying the heat for the right amount of time (maybe not too long.. 2-4 minutes tops) may cause it to make it to the spinning color graphics and beyond.
I've been able to resurrect my phone doing this, but only to back it up and do very simple tasks. The moment I do something processor-intensive (Waze, YouTube, etc) it immediately crashes and bootloops again. The only solution beyond this is to unlock your bootloader, download EX Kernel manager and use it to completely disable the big cluster. Then your phone will likely be reliable, but extremely hobbled.
I bought from Best Buy about 16 months ago, so both Google and Huawei have been utterly useless, which is infuriating. Shenanigans like this are criminal. This is my 3rd Nexus phone and I'm considering abandoning Android altogether after this experience.