Related
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.
help i9000 after flash, doing loop of at&t logo, can not enter download mode,
when plugged in screen goes black.
!! if anyone can help please do not hesitate, mostly appreciated.
Try to hold the Down+Menu+Power combination while INSERTING the battery into the device.
i try that seem to have no response and when unplugged from usb it loop at&t logo
or plugged in usb screen goes black and no response seem from pressing buttons
I had a similar problem as most phones in Canada seem to have Download/Recovery mode disabled, and here is what worked for me.
Grab something like One Click Un Root (all models), and click one click un root (obviously phone has to be on and plugged into the computer).
This should automatically reboot you into Recovery Mode!
All you have to do is "wipe data/factory default" or something like that (should be the third option).
As it states, you will loose all your data, but at least you will have a functionning phone!
did it work?
Hi. I have similar problem. Can anybody give instruction what can I do?
I have this problem too. Please help somebody
Add me to the list. Bell Galaxy S, went to unlock my phone the screen went black. Now it will not boot into the OS, the galaxy S splash screen displays then nothing. The menu and back button light up, thats all. ****[email protected]@
I have not rooted or anything.
Of course my download mode does not work.. Going to try this one click root thing if I can find it.
NOT HAPPY
This is not working. Probably because the phone is not in USB debugging mode as I can't change it... Is there any other way to get the phone into recovery mode?
**** me
i had the same thing happen to me the other day with my bell galaxy s and my phone wont do the 3 button combo trick. i left my phone plugged in to a wall charger for a while until the back of the phone became a little warm. i pulled the battery and then left the power cord plugged in and put the battery back in. i held the volume down and enter button until the battery charging indicator showed up, then i also pressed and held the power button until the boot animation started (this is the blue moving swirl and music, not the galaxy s splash scree) and then i let go of the power button. it took a few attempts at this before it actually worked, but eventually it will go into download mode at which time you can open the odin app, then plug in the usb cable and flash your phone that way. it did seem to make a difference if the back of the phone (around the camera area) was warm. if i let go of the power button while the music was playing and the phone did not enter download mode i would keep all 3 buttons pressed until it shut down again, then i would only let go of the power button while the phone initiated the charging screen, then once the battery logo was displayed i would hold the 3 buttons again and would just keep doing this until it went into download mode. i have flashed it at least 5 times today and i have been able to do this each time.
i also had an issue where odin would not recognize my phone was plugged in and windows would show a message saying the usb device was not recognized. i left the phone plugged in and while in download mode i pressed the volume up, enter button and power button until the phone went blank and when the galaxy s logo showed up i let go of the power button and the phone would go into recovery mode and then the usb drivers would be installed. i would then do the 3 button combo for download mode and odin would work fine. it took several attempts but it does work. i hope this helps you guys
If I hold all three buttons the splash screen does not come on, it just keeps looping the Galaxy S logo until I let go of the power button....
xZeDgEx said:
If I hold all three buttons the splash screen does not come on, it just keeps looping the Galaxy S logo until I let go of the power button....
Click to expand...
Click to collapse
That's what mine did too, several times in a row and then it worked. For some reason it only works after the battery is charging for a bit and the back becomes warm. then it works at will
No luck. I am probably screwed getting it exchanged now too as I am passed the 14 days from Best Buy.
the on click thing doesn't work, if your phone is already bricked.
also it is not the phone's fault for not working, the phone was working properly before you tried the hacks.
whenever you do these kind of things you know you are entering into the "not supported" "not covered by warranty" zone.
in the worse case scenario, if you can no enter download mode to recover your phone, it'll be to take the phone back to bell and claim warranty on it, and prentent you don't know what happened to it.
xZeDgEx said:
Add me to the list. Bell Galaxy S, went to unlock my phone the screen went black. Now it will not boot into the OS, the galaxy S splash screen displays then nothing. The menu and back button light up, thats all. [email protected]@
I have not rooted or anything.
Of course my download mode does not work.. Going to try this one click root thing if I can find it.
NOT HAPPY
Click to expand...
Click to collapse
AllGamer said:
the on click thing doesn't work, if your phone is already bricked.
also it is not the phone's fault for not working, the phone was working properly before you tried the hacks.
whenever you do these kind of things you know you are entering into the "not supported" "not covered by warranty" zone.
in the worse case scenario, if you can no enter download mode to recover your phone, it'll be to take the phone back to bell and claim warranty on it, and prentent you don't know what happened to it.
Click to expand...
Click to collapse
Its my fault??
I did not hack my phone. Its not rooted, I did nothing to it.
By "unlock" I meant exactly that, unlock as in swiping the screen to unlock it.
The more I search the net the more posts I find of Galaxy S phones randomly bricking...
on the original message sounded more like you went to Unlock the phone, as in SIM unlock the phone using any of the tools available out there, and there has been already several people which had the same problem.
if you go back to Bell for an exchange, you better not use the word "unlock" rather use Swipe
as the message on the phone "swipe the screen to unlock"
there are no known issue about this causing the phone to brick.
if that is what happened to you, you should have started a new topic for people to help you, instead of hijacking the topic from the OP, as your issue is different from OP, the OP actually screwed up because he/she flashed the wrong ROM to the i9000
... anyways, Does it work if you reboot the phone?
I have rebooted the phone about 100 times. The phone crashed when I unlocked it to check a text I received. (not hacked). Has not booted up properly since. I have found many others with the same issue who have also not hacked/rooted/unlocked/ their phones.
Waiting on Best Buy to call me back. I am so pissed right now, I have been bragging to my friends and co-workers how awesome this phone is, one has already picked one up, I hope his doesn't brick too. Not recommending it to anyone anymore..
did you load a lot of MP3 to the phone?
can you boot into Recovery Mode?
in the recovery mode you can wipe the Cache and wipe the data
that should make your phone work normal again
it'll be best to open a topic to help you trouble shoot your interesting issue, as it's the first i've hear that you get a black screen after Swiping out of the lock screen
I can't get into recovery mode. I have tried every button combination I have found. I had about 2 GB of music on the phone. I also installed the Android SDK to try ADB, but since the phone is not in USB debugging mode it does not see it.
xZeDgEx said:
I can't get into recovery mode. I have tried every button combination I have found. I had about 2 GB of music on the phone. I also installed the Android SDK to try ADB, but since the phone is not in USB debugging mode it does not see it.
Click to expand...
Click to collapse
on the other topics relating to the 3 button not working.
have you tried the heating up method?
or the plugging the battery in, when all 3 buttons are pressed? (of course for this one you will need help from a friend, unless you are very skilled at keeping the 3 button on hold meanwhile able to slide in the battery in with out a 3rd hand)
Just gonna throw this out there and hope that somebody will have some insight…
Right now, my Xoom won’t turn on... or atleast "all the way on".
If I hold in “Volume Up” and the power button for 3 seconds (as described on the support site), it boots, gets past the moto screen and to the honeycomb animation. The animation plays for a few minutes… yes minutes until it either goes dark/off or presents a bare-bones lock screen that doesn’t respond to touch input.
Occasionally, when it reboots, it gets to the screen that has the Motorola logo and in the upper left corner, it has the text: "Starting RSD Protocol support 0". When that happens, it just freezes there. This has only happen a couple of times and I believe it had to do with variable durations of holding down the power and volume buttons. The phrase quoted doesn’t appear in either bing or google’s indexes.
Right now, the honeycomb animation has been playing for several minutes and 2 notification sounds just played… WTF
Any help would be GREATLY appreciated.
FWIW
Whatever happen, it did so under the follwoing circumstances:
1. Sent gTalk invite
2. Changed background image
3. While it was applying the new background, gTalk popped up with an incoming call.
4. I accepted the call
5. I then saw my video image in the lower right and nothing else on the screen.
6. Approx 10-15 seconds later, the Xoom rebooted.
7. Never finished the reboot, just turned off during honeycomb animation.
8. Tried that again a few times.
9. Tried the hard reboot, where you hold in the volume and power in... no dice
Sometimes, it will play a notification sound when in the honeycomb animation.
Sometimes, it will get to a generic unlock screen that doesnt respond to touch input. When that happens, and once the screen goes to sleep, I'm back to square one.
Just got off the phone with Motorola. I explained to the lady on the phone the situation and she was confident that she could help. Unfortunately, the volume / power button combo was all she had up her sleeve. She advised me to return it to BestBuy tomorrow.
Willing to bet BestBuy wont have any tomorrow... This isnt the "experience" i was hoping to get.
Just return it and get a new one? its obviously defective...
martonikaj said:
Just return it and get a new one? its obviously defective...
Click to expand...
Click to collapse
Yeah, that's what I'll have to do. Just sucks because they probably won't have any and I'll end up having to wait for another. It's lame, but I suppose its one of those "it'll do what it do" scenarios.
Sent from my Evo using the XDA App
gigglebox said:
Yeah, that's what I'll have to do. Just sucks because they probably won't have any and I'll end up having to wait for another. It's lame, but I suppose its one of those "it'll do what it do" scenarios.
Sent from my Evo using the XDA App
Click to expand...
Click to collapse
The quicker you take it back, the better off you are. They'll get new stock in and you'll be better off.
If you see that it doesn't mean its defective, it means your stuck on the fastboot screen
do this:
"Holding vol up down & power does a force normal reboot"
I just returned the device to BestBuy, exchanged it for a new one… so I’m all set.
Here are my current thoughts as to what happened (and what may happen in the future):
It really seemed / behaved like an unhandled combination of circumstances exposed what might be a couple of holes in Honeycomb. Obviously, we’re still pretty early on in the life span of this thing and many things that fell through the software validation process will likely be corrected as they are found.
Best I can figure, while attempting to write a change to (what I imagine is) a config file somewhere (when changing the background image), the process was interrupted by an incoming connection (inbound gTalk video call). That, perhaps in conjunction with the set of apps that I had loaded and were likely still present in ram, somehow made Android lose its marbles.
Throughout the night, I tried lots of different ways to reboot, and lots of attempts with no luck. However, on 3 occasions, after 30-40 minutes of not touching the device, it would start to make noise. Each time, I found that the noise was that of an incoming gTalk call and the caller (that seemed to initiate the failure) appeared on the screen accompanied by the Accept, Deny buttons. The pressing of any of the on-screen buttons resulted in the powering off of the device. Whats puzzling is that the device maintained any awareness of a call, etc, hours after it was initiated and had been hard-rebooted several times. Something wasn’t getting flushed…
I assume that once folks get a solid handle on rooting and custom ROM procedures, there will be an iron-clad way out of the hole I found myself in.
Have the same problem
I am having the same problem. will not get past the honeycomb startup animation. Did try up/down volume + power with now luck. I can get to a screen that says Starting RSD protocol support 0 but wont get past that.
VanVlack said:
I am having the same problem. will not get past the honeycomb startup animation. Did try up/down volume + power with now luck. I can get to a screen that says Starting RSD protocol support 0 but wont get past that.
Click to expand...
Click to collapse
Thats the fastboot screen, you could try flashing it at your own risk. But if it was a software glitch that would fix it.
VanVlack said:
I am having the same problem. will not get past the honeycomb startup animation. Did try up/down volume + power with now luck. I can get to a screen that says Starting RSD protocol support 0 but wont get past that.
Click to expand...
Click to collapse
FastBoot or not, I never succeeded in getting it out of that funk (any combo of either proscribed or "creative" button pushing). I dicked with it for about 5-6 hours before I cut my losses and went to bed. In terms of flashing it, I would imagine that it would work, but I personally wouldnt be comfortable enough yet. The process will get a hell of a lot more tested and vouched for in the near future.
The day after launch, I just called around to see what BestBuys had them in stock and drove out there to exchange it.
I hope that you guys are reporting your issues to Google...
never got it fixed
I never did get it out of that loop or what ever was going on. I am too an advanced user of android, from day one and it seem like more of a hardware or software problem then anything. Took it back to costco and they had me call up verizon. Went up a few tech levels. He tryed to help me get into the factory reset menu but no go on that. Got a replacement. I had my new xoom crash and go to the startup screen. Held my breath as it started back up.
Will send out a message to google and motorola letting them know.
All you had to do is hit sound up and power button it would have shutdown and once you power back up it will go into the regular boot
broken xoom
mine is stuck at the duo core screen with failed image lnx 0x002
starting RSD mode 2
i can hold the down volume button and put it in the fastboot protocol support. but when i plug it in and try to unlock it to run the factory reboot protocol from motorola my command prompt says waiting on device. i have the correct mot driver installed. any help out there
Try this post http://forum.xda-developers.com/showthread.php?t=973355
Sent from my HTC HD2 using XDA Premium App
Hello,
I had been using my i9500 for quite a while now, with no issues.
rooted, Hassan rom , Philz Kernel, worked flawlessly until yesterday.
suddenly my phone started rebooting indefinitely, not entering recovery or download modes.
I tried mashing the buttons a little, and i got to the download mode "Warning" screen (unable to go any further) without holding my power button - meaning only by holding both home and volDown keys.
anyway, this lead me to believe my power button is malfunctioning, yet i can still normally press it (Clicking as usual, as if there is no physical damage) and I did not drop or damage my phone in any way.
all of the online threads are regarding phones stuck on boot animation, yet mine is flashing the "Samsung Galaxy S4 GT-I9500" white over black screen (before the boot animation) and doesnt reach boot animation.
i want to believe my data is still reachable as i have not made any backups lately, this is why I came here.
if anyone has encountered any similar issue, please shed some light as this is the first time i had been unable to solve a "boot loop".
thanks in advance!
(ps, phone is still stuck on the loop, i let it keep doing so overnight to let the battery die, plugged it back in to no avail)
rdordo23 said:
Hello,
I had been using my i9500 for quite a while now, with no issues.
rooted, Hassan rom , Philz Kernel, worked flawlessly until yesterday.
suddenly my phone started rebooting indefinitely, not entering recovery or download modes.
I tried mashing the buttons a little, and i got to the download mode "Warning" screen (unable to go any further) without holding my power button - meaning only by holding both home and volDown keys.
anyway, this lead me to believe my power button is malfunctioning, yet i can still normally press it (Clicking as usual, as if there is no physical damage) and I did not drop or damage my phone in any way.
all of the online threads are regarding phones stuck on boot animation, yet mine is flashing the "Samsung Galaxy S4 GT-I9500" white over black screen (before the boot animation) and doesnt reach boot animation.
i want to believe my data is still reachable as i have not made any backups lately, this is why I came here.
if anyone has encountered any similar issue, please shed some light as this is the first time i had been unable to solve a "boot loop".
thanks in advance!
(ps, phone is still stuck on the loop, i let it keep doing so overnight to let the battery die, plugged it back in to no avail)
Click to expand...
Click to collapse
Hi mate
I sounds a lot like a power button problem , symptoms are similar to other cases , even if power button clicks does not mean is working .... take it to a local service center a have it replace.
Data should be fine.
MAX 404 said:
Hi mate
I sounds a lot like a power button problem , symptoms are similar to other cases , even if power button clicks does not mean is working .... take it to a local service center a have it replace.
Data should be fine.
Click to expand...
Click to collapse
will do. ill update as soon as they return my phone
rdordo23 said:
will do. ill update as soon as they return my phone
Click to expand...
Click to collapse
Great mate.
Good luck
My GT-i9500 just started this same issue less than an hour ago.
I have taken the battery out and I am hoping this will help. Since I never turn the phone off the power button doesn't get used that much. At the most it might get used once a month.
Well I am not sure if this was the reason for it working but I put the battery back in and rocked the power button back and forth. Now its booted properly. Will keep and eye on it, just a pity it would give issues a few days before Christmas. Repair centers won't be open until early Jan.
killerbyte said:
My GT-i9500 just started this same issue less than an hour ago.
I have taken the battery out and I am hoping this will help. Since I never turn the phone off the power button doesn't get used that much. At the most it might get used once a month.
Well I am not sure if this was the reason for it working but I put the battery back in and rocked the power button back and forth. Now its booted properly. Will keep and eye on it, just a pity it would give issues a few days before Christmas. Repair centers won't be open until early Jan.
Click to expand...
Click to collapse
While waiting for the lab to open (sunday) i started flicking my phone a little more violently (upon the acceptable amount of strength), and now i made it boot (!!!).
the current status is the power button is not working, i am carefully navigating to titanium backup... hope i can get a Nand backup aswell, but that's just being greedy. thank god for Philz touch recovery (no power no love on recovery)
Hello mate...
I am using same I9500...i faced same problem wayback in august...phone ws starting indefinitely without even pressing power button. ..so i searched net..
No recovery mode ws accessible to me...couldn't flash....
So i went to Samsung care..
They told i will have to change my PBA meaning passive board assembly. .
Had no other options. .
Spent 9600 on my i9500.
... :/
Sent from my GT-I9500 using XDA Free mobile app
My screen broke 6 months ago, so it wasn't used/charged for 6 months. Now I've replaced the screen, but it won't start up anymore. First thing I saw was the warning "low battery", so I charged it for a while. Still, nothing. Charged it for several days, nothing. Checked the battery voltage, 3.80 volts, exactly what it should be I think?
The phone does do something though. When I hold the "on" button, after 5 seconds it buzzes and the screen shows the oneplus logo and android. Just for two seconds, then nothing. Same thing with "on" and volume down, the start-up screen for 2 seconds...
When I use "on" and volume up, I get the screen saying "fastboot mode". And that doesn't go away untill I press "on" for a while.
I can connect it to my laptop, but cant see it. But when I take the battery out while connected to the laptop, the phone will show the "low battery" warning. Connect the battery again, and the logo and android message come on for two seconds...nothing more.
So the screen works, the battery is charged, but no way to turn it on. Tried holding the "on" button for 15 seconds, same result. Just a 2 seconds oneplus logo visible...
I have no clue what this could be, I hope its not completely fubar...
Thanks in advance, Fred Doe
Hey Fred Doe,
I wouldn't like to hijack your post, but I seem to have run into the exact same issue here.
A friend of mine got his screen replaced, and the phone acts exactly the same as yours.
I have disassembled the phone and checked all connections, but everything seems to be correct on the inside.
The phone does seem to boot, and it does boot into recovery mode (it responds to the button presses by vibrating) but the screen just doesn't show anything.
Only when doing fastboot the screen stays on.
Hopefully someone here can point us in the right direction.
there's not much to hijack here...sure sounds like the same problem. At this moment I gave up, guess its a lost cause..
Guys, the exactly same thing here. I've tried to unbrick it but failed.... So far what I know is that bootloader is locked.
I would like to know what steps should us do in order unlock bootloader, get screen functioning while getting access back to bootloder (TWRP) so after that we can install a new ROM!
Any clue from the community of OnePlus 2? This phone is still a good phone! Thnx
Have you guys tried running the msm tool. It'll restore everything to stock if you can it to work. If either of you have magisk installed it can cause issues with charging while the phone is off I believe.
I mean honestly sounds more like hardware issue that a msm wouldn't fix, but it's weird that your screen works in fastboot.
If you do the msm tool though be aware it will wipe everything on your device, and relock the bootloader if it is unlocked.
Like I said doubt it will help, but just a thought.
Edit: Also make sure you use the correct one for your device.
Edit sorry guys wrong forum ignore everything I said. Apparently xda labs thought my OP6T was a OP2.
Sent from my ONEPLUS A6013 using XDA Labs
@TheLogicalGamer
no problem. Thnx anyway. I'm still locked with my OP2.
dajosova said:
@TheLogicalGamer
no problem. Thnx anyway. I'm still locked with my OP2.
Click to expand...
Click to collapse
But the screen does show up & stays on in fastboot?
I'm no expert but any stretch. I just jumped ship from lg my 6t is the 1st OP phone I've owned. But if the screen does work normally in fastboot then it wouldn't be illogical to entertain the idea that it was a software issue. So I mean this is a bit of a chin scratcher.
Sent from my ONEPLUS A6013 using XDA Labs
Thanks for replying.
IWhen I press Power + Vol. Up it shoes Fast Boot screen. Then I connect cable and sometimes I can use command line but can't unlock bootloader with command line. All methods found indicate to use Recovery but since my screen doesn't work on Recovery I'm stuck.
When I press Power + Vol. Down (for entering Recovery) screen it goes all black but the capacitive buttons and Volume button give back a vibration response, as if it have entered Recovery Mode but since I can't see nothing on screen I can do anything either.
My bootloader is locked because I see that info via command line.
Thanks anyway
PS: I think something is corrupted. My OP2 was unlocked much time ago. I frquently change ROM's and have also updated TWRP. The only thing I did was disassembling the phone in order to change a shattered screen glass.
I've also tried different methods and installed in my pc different Qualcomm drivers, ADB, etc.
I'm getting close to the point of testing with broken touch, buying a new touch screen but with frame or giving up completely and buy a new phone :|
The last option get me in doubt because I would like a phone wich is good and fast and decent battery but not with a premium price... and popular so I can unlock it without hassle in order to install root apk's.