Related
I forgot that my phone was plugged into my PC with the sd card mounted. I checked for update and it found one and started the download. The download just sat there at 0%. I realized my usb was connected and unmounted it (thinking that the update somehow was waiting for the SD card). No change, so I clicked Cancel on the upload screen. I then tried Check for Update and again and it said "no firmware". I rebooted and tried again. Still same message. I then tried "Resume update" instead of "Check for update". It said it found an update and would reboot the phone in 5 seconds. The phone then rebooted and it started to apply the update. This seemed very wrong to me because the updated certainly didn't have time to download. The update failed and it said it was rebooting my phone. The phone went off and now I can't get it to start back up. I press the power and get nothing. I pulled the battery and sim card. Still nothing. Any ideas?
Yikes, that's a sticky situation you've got yourself into. From reading around the forums it seems that the update was bricking phones anyway; however, from what you described it seems like that isn't your case. If you can't power on your phone, then there isn't a way to head back to stock or fix the update, that I know about. You might think about calling Samsung or AT&T and saying you tried applying the update, but now your phone won't power on.
richb500 said:
I forgot that my phone was plugged into my PC with the sd card mounted. I checked for update and it found one and started the download. The download just sat there at 0%. I realized my usb was connected and unmounted it (thinking that the update somehow was waiting for the SD card). No change, so I clicked Cancel on the upload screen. I then tried Check for Update and again and it said "no firmware". I rebooted and tried again. Still same message. I then tried "Resume update" instead of "Check for update". It said it found an update and would reboot the phone in 5 seconds. The phone then rebooted and it started to apply the update. This seemed very wrong to me because the updated certainly didn't have time to download. The update failed and it said it was rebooting my phone. The phone went off and now I can't get it to start back up. I press the power and get nothing. I pulled the battery and sim card. Still nothing. Any ideas?
Click to expand...
Click to collapse
try holding both volume keys and power button until you see something then release power.
If you bought your phone from an AT&T store and you have one close to you, I would take it in and show it to them. They replaced mine on the spot, took me less than 5 minutes.
ThisWasATriumph said:
try holding both volume keys and power button until you see something then release power.
Click to expand...
Click to collapse
I already tried that. I held them for 1 min. It just doesnt turn on. The battery was about 75%, so I know it's not dead.
hollowayXDA said:
If you bought your phone from an AT&T store and you have one close to you, I would take it in and show it to them. They replaced mine on the spot, took me less than 5 minutes.
Click to expand...
Click to collapse
I bought it from Best Buy. Also, it has been more than 30 day. I'm not even sure who to bring it to.
richb500 said:
I bought it from Best Buy. Also, it has been more than 30 day. I'm not even sure who to bring it to.
Click to expand...
Click to collapse
Check and see if there's a warranty center in your area. AT&T has one on the south side of Baltimore. You walk in, they test it real quick and if they can't fix it, they give you a new phone. Much quicker than exchanging it by mail if there's one close to you.
richb500 said:
I already tried that. I held them for 1 min. It just doesnt turn on. The battery was about 75%, so I know it's not dead.
Click to expand...
Click to collapse
Have you tried holding both vol up/down while plugging in usb to get into download mode?
hold the + and - volume buttons and plug the usb back in, if you get to download mode your not quite dead yet
must type faster next time......
PRS_Player said:
Have you tried holding both vol up/down while plugging in usb to get into download mode?
Click to expand...
Click to collapse
Yup. Nothing. Screen stays black. No sign of life.
Damn I was really close to messing mine up too then from the sound of it. I noticed my phone downloading some kind of update today too, well I immediately hit cancel, not knowing what it would do and wanting to come do some research here before accepting it. When I went back, I also hit Resume Update and it gave me the same "no firmware" error, then I hit check for update and it gave me an error message that said "You have not waited 24 hours since the last time you checked for an update, please wait 23...."
Guess I wont be trying to update tomorrow afterall
I had the same problem, but my phone completely downloaded the update. Couldn't power it on at all even if I pushed the + - volume button with power button. Took it to ATT and told them that it happened when I applied the update, and since I was over my 30 day update, they called some ATT replacement hotline and they are sending me one today.
ditto on a dead phone because of OTA my wifes not mine(glad it was hers)
stock captivate update stopped at 87% then went black, no power at all, not even the volume +- way
called att 2 day air on a replacement of course its a refurb but better than no phone at all....
oven
Well i am going to sound like nutcase but have you tried putting into the oven? I am being 100% serious. Look over in the i9000 forums and i think there were some people that were bricked beyond recognition and they did some crazyness such as putting it in the oven at 350 untill it was hot to the touch but not melting and it got their phones into download......just a thought and no i am not lying it worked for them!!!!
Best of luck guys
Remove the battery and put it again, without turning the phone on, press volume up + volume down, and then plug it to the USB connected to your computer.
JorgeC said:
Remove the battery and put it again, without turning the phone on, press volume up + volume down, and then plug it to the USB connected to your computer.
Click to expand...
Click to collapse
That didn't work either. I will receive a replacement phone tomorrow. I hate getting a refurb. My phone is in perfect condition. I hope the replacement one is too.
Here's something that I did discover. I don't think the phone is actually dead. I think it's stuck in some kind of loop, making it completely unresponsive. I had it sitting in my dest drawer today for several hours. When I took it out it was pretty warm - as if was clocking some pretty serious cpu or network traffic. Either way, it's a brick, but I think it a living brick, not a dead brick. In case you're wondering, my office was like a refridgerator today, so it wasn't from the warm room.
richb500 said:
That didn't work either. I will receive a replacement phone tomorrow. I hate getting a refurb. My phone is in perfect condition. I hope the replacement one is too.
Here's something that I did discover. I don't think the phone is actually dead. I think it's stuck in some kind of loop, making it completely unresponsive. I had it sitting in my dest drawer today for several hours. When I took it out it was pretty warm - as if was clocking some pretty serious cpu or network traffic. Either way, it's a brick, but I think it a living brick, not a dead brick. In case you're wondering, my office was like a refridgerator today, so it wasn't from the warm room.
Click to expand...
Click to collapse
I have received several refurbs over the years and all the phone appear to be brand new. I already exchanged my Captivate one. Not a scratch on them. Even though they say they are refurbs the device appears to be new product. You will not have a problem.
i got mine bricked too, it was perfectly fine before the update... it stopped at 50% and then it said update failed, phone rebooted, and then it never open its eyes again, its DEAD... omg, good job att! morons giving us wrong software...
richb500 said:
Yup. Nothing. Screen stays black. No sign of life.
Click to expand...
Click to collapse
I've had the same issue but I was able to fix it. Unfortunately, I don't remember the exact steps, you will have to try for a few times until you make it work.
When your phone is "dead":
1. Take out SIM+SD cards (keep your battery in)
2. USB connect to your PC
3. Start Odin3
4. VolUp+Power and wait until a few red colored lines will show up (if not then try for a few times until they show up), you should see something like this:
RST_STAT =0x1
PMIC_IRQ =0x3c
..... and so on.
5. When you see the red lines press VolUp+VolDown+Power
6. The red lines will go off/on in a few seconds but you keep holding VolUp+VolDown+Power
7. When red lines will go off for a second time just release Power, you should get back to download mode
8. Use Odin3 to re-flash
Good luck!
ice3186 said:
Well i am going to sound like nutcase but have you tried putting into the oven? I am being 100% serious. Look over in the i9000 forums and i think there were some people that were bricked beyond recognition and they did some crazyness such as putting it in the oven at 350 untill it was hot to the touch but not melting and it got their phones into download......just a thought and no i am not lying it worked for them!!!!
Best of luck guys
Click to expand...
Click to collapse
This sounds as crazy as out gets.
After my first update the phone is dead, I have my htc inc s for one
week(I think it was android 2.3.3 and it worked fine yesterday I got
update notification I've downloaded it and then the phone shutted down
and started with the dark screen with the green arrows in circle and
one inside facing down symbol and it stayed like that forever!I took
battery out and put back press power and its the same symbol! The phone
is from china got it from ebay and if I need to send it back for fixing
it will take a lot of time to come back!
So I tried battery out back in, volume down + pover the same green
arrow symbol,like this when plugged in my pc doesnt do nothing,after I
tried battery out than in, volume up + power and I got 3 vibes, orange
light and black screen, when plugged to my pc i says "qualcom CDMA
technologies MSM" device and it searches for drivers!
I dont believe that its possible to brick my device with the first
update that I got from the mobile network and I never touched nothing
like rooting or messing with my phone...
So what can I do now to fix it without losing my waranty and having
everything like it was before stock and working???
PLEASE HELP PLEASE HELP!!!
simshtcincs said:
After my first update the phone is dead, I have my htc inc s for one
week(I think it was android 2.3.3 and it worked fine yesterday I got
update notification I've downloaded it and then the phone shutted down
and started with the dark screen with the green arrows in circle and
one inside facing down symbol and it stayed like that forever!I took
battery out and put back press power and its the same symbol! The phone
is from china got it from ebay and if I need to send it back for fixing
it will take a lot of time to come back!
So I tried battery out back in, volume down + pover the same green
arrow symbol,like this when plugged in my pc doesnt do nothing,after I
tried battery out than in, volume up + power and I got 3 vibes, orange
light and black screen, when plugged to my pc i says "qualcom CDMA
technologies MSM" device and it searches for drivers!
I dont believe that its possible to brick my device with the first
update that I got from the mobile network and I never touched nothing
like rooting or messing with my phone...
So what can I do now to fix it without losing my waranty and having
everything like it was before stock and working???
PLEASE HELP PLEASE HELP!!!
Click to expand...
Click to collapse
I have no idea what volume up+power does, nor do I understand half of what you are saying but ill try and help anyways...
download HTC Sync. Download SDK and ADB files from google. then save the files in a place ull remember. Download HTC Sync too (I forget if you actually need it but download it anyways because you need it for USB Drivers). When you are finished download of SDK, go into the folder sdk/platform-tools. Shift+right mouse click and then select "Open Command Window here." Back to your phone, boot into bootloader (Volume DOWN + Power button) and select fasboot (if u dont know how to navigate in bootlaoder, search it up). On your computer in command window type in fastboot devices and it should list your device serial number (if u dont know it dont worry, it should start with something like HT and then numbers and stuff like that). If your computer recognizes the deivce, then proceed and type "fastboot getvar all" Paste what u read here or screenshot, whatever, just see that its here IN THIS THREAD.
072665995 said:
I have no idea what volume up+power does, nor do I understand half of what you are saying but ill try and help anyways...
download HTC Sync. Download SDK and ADB files from google. then save the files in a place ull remember. Download HTC Sync too (I forget if you actually need it but download it anyways because you need it for USB Drivers). When you are finished download of SDK, go into the folder sdk/platform-tools. Shift+right mouse click and then select "Open Command Window here." Back to your phone, boot into bootloader (Volume DOWN + Power button) and select fasboot (if u dont know how to navigate in bootlaoder, search it up). On your computer in command window type in fastboot devices and it should list your device serial number (if u dont know it dont worry, it should start with something like HT and then numbers and stuff like that). If your computer recognizes the deivce, then proceed and type "fastboot getvar all" Paste what u read here or screenshot, whatever, just see that its here IN THIS THREAD.
Click to expand...
Click to collapse
I will try to explain better... My htc brand new never rooted never played with, after 4-5 days of using (everything worked great) got
the first OTA update, shutted down and then started with the green update sign on the screen, it stayed like this forever, so I took the battery out and put it back and tried to go to the boot menu (volume down + power button) it does nothing again the same green symbol on the screen. Than I took battery out and in again and pressed volume up + power button and the phone vibrates 3 times and the orange lid is on. When connected to PC does nothing! I instaled and played with sdk and adb like you instructed me but the problem is that the device is not in the device list! I start to think that its bricked or soft bricked but it makes me mad since its new and I never played with it or changed something!
Also if it matters I got it from the eBay but since I wrote to HTC also the answer was from them that its a indonesian market phone that has expired guarantee one year ago, so this makes me think that maybe its a referb and not new phone
P.S Sorry for the double post I am new here and thanks for trying to help
I.m attaching two pics of what is seen on the screen help me if you can
simshtcincs said:
I will try to explain better... My htc brand new never rooted never played with, after 4-5 days of using (everything worked great) got
the first OTA update, shutted down and then started with the green update sign on the screen, it stayed like this forever, so I took the battery out and put it back and tried to go to the boot menu (volume down + power button) it does nothing again the same green symbol on the screen. Than I took battery out and in again and pressed volume up + power button and the phone vibrates 3 times and the orange lid is on. When connected to PC does nothing! I instaled and played with sdk and adb like you instructed me but the problem is that the device is not in the device list! I start to think that its bricked or soft bricked but it makes me mad since its new and I never played with it or changed something!
Also if it matters I got it from the eBay but since I wrote to HTC also the answer was from them that its a indonesian market phone that has expired guarantee one year ago, so this makes me think that maybe its a referb and not new phone
P.S Sorry for the double post I am new here and thanks for trying to help
I.m attaching two pics of what is seen on the screen help me if you can
Click to expand...
Click to collapse
You might want to try official RUU although I dont know if it will work since you dont seem to be able to boot up properly, but its certainly worth a try. BTW, how long did u wait for the OTA update to finish installing?
Seems like you have the same problem as this guy http://forum.xda-developers.com/showthread.php?t=2298438
072665995 said:
You might want to try official RUU although I dont know if it will work since you dont seem to be able to boot up properly, but its certainly worth a try. BTW, how long did u wait for the OTA update to finish installing?
Click to expand...
Click to collapse
I waited more than one hour and then decided to take battery out since it was not responding!
Btw how to get the official RUU , my phone is for Indonesian market and I am in Greece Europe and I cant decide what to choose and download from htc.dev because I see only Kernel Source Code can be downloaded there, can you help please?
Hi. To start with I bought a phone from a friend which I knew was faulty but decided to take my chances and try to fix it. He claims he did nothing to the phone but don't know for sure. Phone is in constant bootloop, Goes until splash screen and reboots. Worst yet to come - even bootloader menu restarts on constant basis when i try to get into it. Meaning it goes into bootloader but restarts in few seconds before i can get to factory reset. Computer is not picking up this device but i also don't have any drivers installed but don't even know how to install them with a phone in this state. Is there anything i can do about it? Been with Samsung for the past few years and here is everything completely different so don't know much about adb but am a quick learner and can follow any steps! I can provide picture of bootloader if it would be any helpful.
michal_alton said:
Hi. To start with I bought a phone from a friend which I knew was faulty but decided to take my chances and try to fix it. He claims he did nothing to the phone but don't know for sure. Phone is in constant bootloop, Goes until splash screen and reboots. Worst yet to come - even bootloader menu restarts on constant basis when i try to get into it. Meaning it goes into bootloader but restarts in few seconds before i can get to factory reset. Computer is not picking up this device but i also don't have any drivers installed but don't even know how to install them with a phone in this state. Is there anything i can do about it? Been with Samsung for the past few years and here is everything completely different so don't know much about adb but am a quick learner and can follow any steps! I can provide picture of bootloader if it would be any helpful.
Click to expand...
Click to collapse
Send a picture of the bootloader while I find the drivers you need
Seems like battery is completely dead as it only reboots when there is power supply connected, but then it won't turn off (any charging light don't come on, not sure if it should though). Just now i've seen a vodafone logo for a very short second when I connected to pc from charger. But phone rebooted again just after.
HTC_Phone said:
Send a picture of the bootloader while I find the drivers you need
Click to expand...
Click to collapse
edit. downloaded drivers (4.8) but that didn't change anything and windows still doesn't pick up device.
After connecting my one to computer for past 3 hours its started more frequently boot and showing Vodafone menu but still restarts shortly after. Vodafone logo shows on and lights on soft buttons starts flashing like 3 times and than it keeps rebooting. Does it mean anything?
michal_alton said:
Seems like battery is completely dead as it only reboots when there is power supply connected, but then it won't turn off (any charging light don't come on, not sure if it should though).
Click to expand...
Click to collapse
Have you checked this: http://forum.xda-developers.com/showthread.php?t=2481211
michal_alton said:
After connecting my one to computer for past 3 hours its started more frequently boot and showing Vodafone menu but still restarts shortly after. Vodafone logo shows on and lights on soft buttons starts flashing like 3 times and than it keeps rebooting. Does it mean anything?
Click to expand...
Click to collapse
That almost sounds like your POWER button is stuck!! Are you able to completely power off, and it stays off.
I think i know what it is. Power button stuck and keeps restarting device. Although i can feel pressing it, this is what it looks like.
nkk71 said:
Have you checked this: http://forum.xda-developers.com/showthread.php?t=2481211
That almost sounds like your POWER button is stuck!! Are you able to completely power off, and it stays off.
Click to expand...
Click to collapse
Didn't see your comment but this is exactly how it looks to me. I can't switch off phone and in bootloader it acts like i was pressing power button. Although it operates normally meaning that it can be pressed down. Arranged warranty repair with HTC and they are collecting phone tomorrow.
michal_alton said:
Didn't see your comment but this is exactly how it looks to me. I can't switch off phone and in bootloader it acts like i was pressing power button. Although it operates normally meaning that it can be pressed down. Arranged warranty repair with HTC and they are collecting phone tomorrow.
Click to expand...
Click to collapse
Good luck mate, but definitely sounds like the power button is stuck
It's been fixed under warranty by HTC. They replaced motherboard on mine HTC. So all good
So I've posted this problem here before:
http://forum.xda-developers.com/htc-one/help/please-confirm-totally-bricked-t2831685
Just wondering if any of you would know how to fix it.
Probably no one will want to read that much, so here's the short version:
-Can't enter bootloader
-Can't enter recovery
-ABD doesn't work
-Fastboot doesn't work
Reasons why I think it still can get fixed:
-It stills turns on.
-Battery has ran out a couple of times, so it still charges.
-Windows 8 makes a pulg-in sound when I connect the phone to the laptop.
The phone also keeps rebooting each 6 to 10 seconds, so it is actually a plug-in, and plug-out, and a plug-in, and so on...
It doesn't list anything inside Device Manager.
Some people have tried Dexter's fix for bricked devices, but I think it only works for devices listed at least as QHSUSB_DLOAD.
Mine is not recognized that way... or at all.
That plug-in sound though.
HTC Drivers Installed:
setup_3.1.24.5_htc.exe
HTC_BMP_USB_Driver_x64_1.0.5375.msi
HTC Driver 4.10.0.001.exe
HTC Sync Manager
KomuroXV said:
So I've posted this problem here before:
http://forum.xda-developers.com/htc-one/help/please-confirm-totally-bricked-t2831685
Just wondering if any of you would know how to fix it.
Probably no one will want to read that much, so here's the short version:
-Can't enter bootloader
-Can't enter recovery
-ABD doesn't work
-Fastboot doesn't work
Reasons why I think it still can get fixed:
-It stills turns on.
-Battery has ran out a couple of times, so it still charges.
-Windows 8 makes a pulg-in sound when I connect the phone to the laptop.
The phone also keeps rebooting each 6 to 10 seconds, so it is actually a plug-in, and plug-out, and a plug-in, and so on...
It doesn't list anything inside Device Manager.
Some people have tried Dexter's fix for bricked devices, but I think it only works for devices listed at least as QHSUSB_DLOAD.
Mine is not recognized that way... or at all.
That plug-in sound though.
HTC Drivers Installed:
setup_3.1.24.5_htc.exe
HTC_BMP_USB_Driver_x64_1.0.5375.msi
HTC Driver 4.10.0.001.exe
HTC Sync Manager
Click to expand...
Click to collapse
So wait. Why can't you enter? Because it reboots too fast? Can you shut off your phone? If yes do it so and then try to reboot to bootloader. And if it reboots there too every 5 to 6 seconds, you're gonna have a big problem. Within 5-6 seconds you can't hide the rooted state of your device and this also means that you can't return it.
But if you can get to your bootloader and if you can fastboot connect it, I'd recommend using a RUU if you are S-OFF. Otherwise I'd try to reinstall another recovery and from the recovery I'd reinstall a new OS.
Anyways, just try to get to the bootloader and do what I told you to. If my instructions were too unaccurate, just mention or quote me, I'll get back to you.
LibertyMarine said:
So wait. Why can't you enter? Because it reboots too fast? Can you shut off your phone? If yes do it so and then try to reboot to bootloader. And if it reboots there too every 5 to 6 seconds, you're gonna have a big problem. Within 5-6 seconds you can't hide the rooted state of your device and this also means that you can't return it.
But if you can get to your bootloader and if you can fastboot connect it, I'd recommend using a RUU if you are S-OFF. Otherwise I'd try to reinstall another recovery and from the recovery I'd reinstall a new OS.
Anyways, just try to get to the bootloader and do what I told you to. If my instructions were too unaccurate, just mention or quote me, I'll get back to you.
Click to expand...
Click to collapse
First of all, thank you for replying.
On topic.
Phone is actually turned off right now.
Battery died again.
Only way to turn it back on is connecting it to the wall charger and sometimes to the laptop.
But as soon as I do...
1. Phone turns on.
2. Shows the white screen with only the green HTC logo.
3. If it's plugged to the laptop then I hear that "plug in" sound Windows does.
4. After a few seconds phone reboots... and reboots... and reboots... doing the same I just stated.
I also get to hear the Windows "plug-out" sound everytime it turns off to reboot.
Not sure of why I can't enter the boot loader.
This problem started after I decided to turn off my phone while it was installing a custom recovery (Process was being slow and I am OCD like that)
My paranoic guesses are that I screwed it so bad I wiped the bootloader also, but is that even possible?
KomuroXV said:
First of all, thank you for replying.
On topic.
Phone is actually turned off right now.
Battery died again.
Only way to turn it back on is connecting it to the wall charger and sometimes to the laptop.
But as soon as I do...
1. Phone turns on.
2. Shows the white screen with only the green HTC logo.
3. If it's plugged to the laptop then I hear that "plug in" sound Windows does.
4. After a few seconds phone reboots... and reboots... and reboots... doing the same I just stated.
I also get to hear the Windows "plug-out" sound everytime it turns off to reboot.
Not sure of why I can't enter the boot loader.
This problem started after I decided to turn off my phone while it was installing a custom recovery (Process was being slow and I am OCD like that)
My paranoic guesses are that I screwed it so bad I wiped the bootloader also, but is that even possible?
Click to expand...
Click to collapse
I wonder if this is a damaged partition - and it's tricky to solve
@nkk71 what do you think?
stovie_steve said:
I wonder if this is a damaged partition - and it's tricky to solve
@nkk71 what do you think?
Click to expand...
Click to collapse
I made a video, hope it helps.
https://www.youtube.com/watch?v=GMuo-kvIGIc
Suggestions: Mute it :silly:
KomuroXV said:
I made a video, hope it helps.
https://www.youtube.com/watch?v=GMuo-kvIGIc
Suggestions: Mute it :silly:
Click to expand...
Click to collapse
only thing i noticed in the video is your holding volume up not volume down. Volume up plus power will not load the bootloader
clsA said:
only thing i noticed in the video is your holding volume up not volume down. Volume up plus power will not load the bootloader
Click to expand...
Click to collapse
I've tried both.
Here's another one anyways.
https://www.youtube.com/watch?v=1zyA6XGFEpo&list=UUzlEfhRw_dyaJ7aAFpWC7-A
KomuroXV said:
First of all, thank you for replying.
On topic.
Phone is actually turned off right now.
Battery died again.
Only way to turn it back on is connecting it to the wall charger and sometimes to the laptop.
But as soon as I do...
1. Phone turns on.
2. Shows the white screen with only the green HTC logo.
3. If it's plugged to the laptop then I hear that "plug in" sound Windows does.
4. After a few seconds phone reboots... and reboots... and reboots... doing the same I just stated.
I also get to hear the Windows "plug-out" sound everytime it turns off to reboot.
Not sure of why I can't enter the boot loader.
This problem started after I decided to turn off my phone while it was installing a custom recovery (Process was being slow and I am OCD like that)
My paranoic guesses are that I screwed it so bad I wiped the bootloader also, but is that even possible?
Click to expand...
Click to collapse
Hmmm, as the others said this might be really hard to solve.
Most likely this here won't solve your problem but it's better to try it than to just let it be:
Hold your HTC One below a bright lights source and hold the power button for about 15 seconds or even longer. The charging light will light up. Then hold down the volume down button and try different key combinations!
I heard about that this here could get some devices to fully boot after they had been in such a strange loop as your phone is:
A: Hold volume down and volume up button and the power button for about 90 seconds. If this doesn't work, try holding your phone below bright light again
I couldn't watch the second video (it's private) where you pressed the volume down button. But I believe you're right.
@stovie_steve what is the indication for this damaged partition? I can't imagine which partition would lead into a such behaviour.
Anyways.. @KomuroXV just try what I've writtten if it doesn't work, just mention or quote again, I'll try to look up what it could be.
Good luck!
LibertyMarine said:
Hmmm, as the others said this might be really hard to solve.
Most likely this here won't solve your problem but it's better to try it than to just let it be:
Hold your HTC One below a bright lights source and hold the power button for about 15 seconds or even longer. The charging light will light up. Then hold down the volume down button and try different key combinations!
I heard about that this here could get some devices to fully boot after they had been in such a strange loop as your phone is:
A: Hold volume down and volume up button and the power button for about 90 seconds. If this doesn't work, try holding your phone below bright light again
I couldn't watch the second video (it's private) where you pressed the volume down button. But I believe you're right.
@stovie_steve what is the indication for this damaged partition? I can't imagine which partition would lead into a such behaviour.
Anyways.. @KomuroXV just try what I've writtten if it doesn't work, just mention or quote again, I'll try to look up what it could be.
Good luck!
Click to expand...
Click to collapse
Oh... I fixed the private video thing, sorry about that.
I've tried the bright light + power + volume down button combination before but it never managed to make the phone to boot properly.
It did have some little behaviour changes though...
Like... it was more responsive for the button combination making it turn off kind of faster, just to reboot again some seconds after anyway.
Tried it again just now, but still nothing different. :/
Same stuff as before.
I could make another video if you guys wanted to make sure, but it'd be me just pressing the volume down + power under the bright light for nothing but the loop, besides the responsiveness I've told you it seems to get to pressing the buttons.
Anyway, just tell me if making another video would help.
By the way.
Some months ago (Yeah, I have a lot of time dealing with this) I was able to turn it on with or without the charger, now it seems like it's only possible when it's "charging" or connected to the laptop, regardless of bright light or not.
Guess that was because it had charge before, now it doesn't and it's unable to actually charge the battery.
Which would explain why the orange little charging light is off now.
I'm open to any new ideas. :/
Thank you guys for all your support.
KomuroXV said:
Oh... I fixed the private video thing, sorry about that.
I've tried the bright light + power + volume down button combination before but it never managed to make the phone to boot properly.
It did have some little behaviour changes though...
Like... it was more responsive for the button combination making it turn off kind of faster, just to reboot again some seconds after anyway.
Tried it again just now, but still nothing different. :/
Same stuff as before.
I could make another video if you guys wanted to make sure, but it'd be me just pressing the volume down + power under the bright light for nothing but the loop, besides the responsiveness I've told you it seems to get to pressing the buttons.
Anyway, just tell me if making another video would help.
By the way.
Some months ago (Yeah, I have a lot of time dealing with this) I was able to turn it on with or without the charger, now it seems like it's only possible when it's "charging" or connected to the laptop, regardless of bright light or not.
Guess that was because it had charge before, now it doesn't and it's unable to actually charge the battery.
Which would explain why the orange little charging light is off now.
I'm open to any new ideas. :/
Thank you guys for all your support.
Click to expand...
Click to collapse
hey guys, sorry been/am a bit busy lately, so don't get to respond/contribute much
OP, looks like your power button is messed up? (ie it's continually "pressed") you can try to nudge a little, to see if it gets unpressed
after "nudging" a little, don't even bother pressing it, when the phone reboots, just hold voldown to get to bootloader
EDIT: be gentle :silly: :laugh:
nkk71 said:
hey guys, sorry been/am a bit busy lately, so don't get to respond/contribute much
OP, looks like your power button is messed up? (ie it's continually "pressed") you can try to nudge a little, to see if it gets unpressed
after "nudging" a little, don't even bother pressing it, when the phone reboots, just hold voldown to get to bootloader
EDIT: be gentle :silly: :laugh:
Click to expand...
Click to collapse
hey @nkk71, but in what way does that explain the fact that it only boots when the phone is connected to a power source? And he also holds down the powerbutton the first time. I can't find an explanation for this.
@KomuroXV but what nkk suggested is a good idea, but just be very very gentle. I f#cked up my powerbutton pressing it too much. Luckily HTC believed my (altered) story and I got a replacement.
What you can try is to just go with a paper edge between the power button and the Magnesium surrounding then try to much it upwards and downwards, this may help "unstucking" your powerbutton if that's even the case.
I'm gonna test the with my phone how long it takes to reboot if I hold down the power button (will post again in a few min). If it's about the same as shown in your vid, it might really be a stuck power button.
LibertyMarine said:
hey @nkk71, but in what way does that explain the fact that it only boots when the phone is connected to a power source? And he also holds down the powerbutton the first time. I can't find an explanation for this.
Click to expand...
Click to collapse
1) battery drains, he plugs it in -> boom, it turns on
2) it reboots no matter what button combo he tries
3) it's not even staying on the bootsplash long enough (from the video) to consider it a bootloop
it's just a thought, but that's what it looks like to me
(if it were even going slightly further than the bootsplash, or even bootlooping back to bootloader, then it could be something else, it just looks to me as if the power button is constantly pressed)
nkk71 said:
1) battery drains, he plugs it in -> boom, it turns on
2) it reboots no matter what button combo he tries
3) it's not even staying on the bootsplash long enough (from the video) to consider it a bootloop
it's just a thought, but that's what it looks like to me
(if it were even going slightly further than the bootsplash, or even bootlooping back to bootloader, then it could be something else, it just looks to me as if the power button is constantly pressed)
Click to expand...
Click to collapse
@KomuroXV and @nkk71 I mistreated my phone and yeah, seems to have about the same time to reboot.
And yeah, I now saw in the first video he didn't first hold down the power button. So your thesis is very probable.
So yeah only way is to try and get the button unstuck and if this doesn't work I'd return it to the manufacturer. Shouldn't be something you have to pay for. Only bad thing is that if they notice the altered motherboard...
LibertyMarine said:
@KomuroXV and @nkk71 I mistreated my phone and yeah, seems to have about the same time to reboot.
And yeah, I now saw in the first video he didn't first hold down the power button. So your thesis is very probable.
So yeah only way is to try and get the button unstuck and if this doesn't work I'd return it to the manufacturer. Shouldn't be something you have to pay for. Only bad thing is that if they notice the altered motherboard...
Click to expand...
Click to collapse
For a second there I thought it could be this, but it looks like it's not.
I nudged it.
Carefully cleaned with the edge of a paper too.
God, I basically gave a blowjob to that power button just in case there was any dust inside of it.
But it looks like there's not anything.
It was a good theory though.
But still it wouldn't explain, why did it happen just after I interrupted the custom recovery flashing?
Let explain again in case I didn't do it clearly last time.
I flashed a Custom Recovery through fastboot.
I was Unlocked, S-Off, Rooted, everything good.
All went smoothly at CMD screen.
But the process in the phone was being slow and it looked like if it was stuck to me.
Which it wasn't I guess... but I panicked and turned off the phone like at 40% of the install.
Then all this happened.
That broken power button thing would be way too much coincidence.
My theory is that since I was flashing Custom Recovery through fastboot (bootloader) and I interrupted it.
Now, every time it turns on, it tries to log into fastboot and continue the process I stopped.
Just that now.... it doesn't has the files needed to complete it, or maybe just got corrupted.
Since it can't finish that ghost recovery flashing process, it gives error and reboots.... and reboots... and reboots...
Doesn't really look like a hardware problem.
Seriously, it's the most well taken care phone I've ever had.
I bought it a tempered glass screen protector, an UAG case which for me made the phone indestructible.
Still, guess it wasn't silly-owner-proof.
*facepalms*
:silly:
KomuroXV said:
For a second there I thought it could be this, but it looks like it's not.
I nudged it.
Carefully cleaned with the edge of a paper too.
God, I basically gave a blowjob to that power button just in case there was any dust inside of it.
But it looks like there's not anything.
It was a good theory though.
But still it wouldn't explain, why did it happen just after I interrupted the custom recovery flashing?
Let explain again in case I didn't do it clearly last time.
I flashed a Custom Recovery through fastboot.
I was Unlocked, S-Off, Rooted, everything good.
All went smoothly at CMD screen.
But the process in the phone was being slow and it looked like if it was stuck to me.
Which it wasn't I guess... but I panicked and turned off the phone like at 40% of the install.
Then all this happened.
That broken power button thing would be way too much coincidence.
My theory is that since I was flashing Custom Recovery through fastboot (bootloader) and I interrupted it.
Now, every time it turns on, it tries to log into fastboot and continue the process I stopped.
Just that now.... it doesn't has the files needed to complete it, or maybe just got corrupted.
Since it can't finish that ghost recovery flashing process, it gives error and reboots.... and reboots... and reboots...
Doesn't really look like a hardware problem.
Seriously, it's the most well taken care phone I've ever had.
I bought it a tempered glass screen protector, an UAG case which for me made the phone indestructible.
Still, guess it wasn't silly-owner-proof.
*facepalms*
:silly:
Click to expand...
Click to collapse
I'm gonna sleep now, will answer tomorrow evening. I have an important meeting tomorrow.
KomuroXV said:
I flashed a Custom Recovery through fastboot.
I was Unlocked, S-Off, Rooted, everything good.
All went smoothly at CMD screen.
But the process in the phone was being slow and it looked like if it was stuck to me.
Which it wasn't I guess... but I panicked and turned off the phone like at 40% of the install.
Then all this happened.
That broken power button thing would be way too much coincidence.
Click to expand...
Click to collapse
i dont see how flashing / interrupting flashing a recovery could cause that, the recovery is in a different partition than bootloader, so even if you were unable to enter recovery (due to bad flash), you should be able to get to bootloader
but when you say it got stock at 40%, i'm seriously surprised, as flashing a recovery literally takes 2 seconds:
Code:
C:\ADB3>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
maybe try covering the light sensors completely, and hold voldown, when it reboots again.... maybe (though i doubt it), it will forego the simulated battery pull
KomuroXV said:
[...]
I flashed a Custom Recovery through fastboot.
I was Unlocked, S-Off, Rooted, everything good.
All went smoothly at CMD screen.
But the process in the phone was being slow and it looked like if it was stuck to me.
Which it wasn't I guess... but I panicked and turned off the phone like at 40% of the install.
Then all this happened.
That broken power button thing would be way too much coincidence.
My theory is that since I was flashing Custom Recovery through fastboot (bootloader) and I interrupted it.
Now, every time it turns on, it tries to log into fastboot and continue the process I stopped.
Just that now.... it doesn't has the files needed to complete it, or maybe just got corrupted.
Since it can't finish that ghost recovery flashing process, it gives error and reboots.... and reboots... and reboots...
[...]
Click to expand...
Click to collapse
How did you turn it off? Did you press the power button very hard/strong?
Did you flash the recovery with fastboot
or did you flash your recovery within rebootRUU and with an firmware.zip ?
Because the method via fastboot (fastboot flash recovery recovery.img) doesn't indicate a percentage. And btw. I had issues with this method too and interrupted the installation several times, didn't cause any problems. To the theory that your phone wants to continue flashing recovery is not true. This isn't possible since your phone should boot correctly and if it wanted to boot into recovery you could prevent that with pressing the vol. down button. That didn't work in your case so I think that this theory doesn't work out.
If you flashed it with a firmware zip, was there another hboot.img that you installed too without knowing/wanting? Because interrupting a hboot flash will brick your device. but if that happend you wouldn't be able to boot your phone. So I think this isn't true either.
i have exactly the same problem, is very strange beacause i was updating my ROM
My wife Nokia 7 Plus was found in download mode (white screen with Android One logo) and is stuck in this mode. I've never done any unlock bootloader or root or anything on it (thus I did on other phones so I'm not totally stranger to it) and I'm 100% sure she didn't tried anything strange either. The phone is completely stock and probably with the last update as it went back new from repair a few months ago (for screen brightness issue) and I did update everything possible before she used it again.
The phone start automatically and immediately I see the white screen with AndroidOne logo and after a few ms it refresh and it's the same screen with the back text "Download mode" at the top.
I've tried to force shutdown and reboot by long pressing power. I cannot keep it shutdown, it goes back to Download Mode screen.
I've tried to restart start with power + vol up or power + vol down, power + vol up + vol down. Same.
I've tried to let it die on battery, charge it, and here it's a black screen with the large battery logo and a white text at the top saying: Download mode. After a few minute I try to boot and it's back to the white screen.
What can I tried next before I send it back for repair and it will be probably wiped again...
Side story, I've almost force her to switch from iPhone to Android because of price of the devices, and so far she is not converted at all with all the trouble we got with this Nokia.
As last before send to service try wipe in recovery, if not boot to recovery via buttons, try if your download mode is recognised by fastboot and reboot to recovery using: fastboot reboot AND IMMEDIATELY HOLD BUTTONS POWER and VOLUP until show "green android icon with no command
k3dar7 said:
As last before send to service try wipe in recovery, if not boot to recovery via buttons, try if your download mode is recognised by fastboot and reboot to recovery using: fastboot reboot AND IMMEDIATELY HOLD BUTTONS POWER and VOLUP until show "green android icon with no command
Click to expand...
Click to collapse
Thanks for your help, unfortunately none of this work. I've tried adb device and nothing is seen, fastboot reboot neither. I'll send it to repair now.
Suffering the same problem.
Eluc said:
My wife Nokia 7 Plus was found in download mode (white screen with Android One logo) and is stuck in this mode. I've never done any unlock bootloader or root or anything on it (thus I did on other phones so I'm not totally stranger to it) and I'm 100% sure she didn't tried anything strange either. The phone is completely stock and probably with the last update as it went back new from repair a few months ago (for screen brightness issue) and I did update everything possible before she used it again.
The phone start automatically and immediately I see the white screen with AndroidOne logo and after a few ms it refresh and it's the same screen with the back text "Download mode" at the top.
I've tried to force shutdown and reboot by long pressing power. I cannot keep it shutdown, it goes back to Download Mode screen.
I've tried to restart start with power + vol up or power + vol down, power + vol up + vol down. Same.
I've tried to let it die on battery, charge it, and here it's a black screen with the large battery logo and a white text at the top saying: Download mode. After a few minute I try to boot and it's back to the white screen.
What can I tried next before I send it back for repair and it will be probably wiped again...
Side story, I've almost force her to switch from iPhone to Android because of price of the devices, and so far she is not converted at all with all the trouble we got with this Nokia.
Click to expand...
Click to collapse
I'm having the same problem. Exactly what you said. I didn't root my device or even attempt to do anything. I bought Nokia because they were purely stock and delivered some quality mobile phones. I've got only this phone as my daily driver. So tell me if you have got the issue fixed and how much did it cost and how long it took. It's been stuck with that 'android one' logo and a small message that reads 'Download mode' on top. I've tried everything. And what I'm worried about is, my phone's out of warranty and I'm a student. I hope you got it fixed for some reasonable cost. Please reply to me ASAP.
My wife's phone also has had this exact same problem.
I have tried all the tricks mentioned above including ADB mode (it could not find the phone).
The phone is supposed to be under warranty. So I took it back to the place of purchase.
However, the phone has a tiny crack in the corner of the screen which my wife and I were not aware of. So Nokia have indicated that unless I get the crack fixed, the warranty is voided and they will not fix the boot problem.
Because the broken crack is not covered by warranty, Nokia want $270 for a new screen before they will look at the software problem caused by the pie update.
I took it to a third party repair shop to see if there is a cheaper option. They cannot fix it either.
So the 5 month old Nokia phone is now useless.
But if anyone can comes across a solution for this, can they please post it here.
Thanks.
Same here. I told the guy on the phone about the crack. But he told me it should not be a problem. Now I got an email that I needed to pay 185 euro's to repair the screen.
Because of their FW-update, my phone became unuseful.
When I get it back (not repaired) I will try a OST on it.
I solved my issue via this procedure:
https://www.techmesto.com/possible-fix-nokia-smartphone-stuck-on-download-mode-after-ota-update/
I solved it via drivers: https://github.com/StollD/nokia-driver-installer/raw/master/out/Phone_Nokia_USB_Driver_v1.4.0.exe
WTF Finally I fix it!!!
Pibroens said:
I solved my issue via this procedure:
before, i can't got the phone connect to the pc.
So every way have failed...
After install the driver he supply,I still cant.. but!
I keep connect it,and press the power,volume up down all three button.
After it power on again pc find the phone. And i use the way he supply.
Click to expand...
Click to collapse
My Nokia 7 Plus got stuck in download mode after accidently pressing all buttons simu
Yes I know that sounds like a weird title and maybe you are wondering why did I do that? notice the word accidently.
I was just trying to fly my newly bought drone x pro for the first time and the controller has a little pull out extendable cradle to hold the phone in
if you want to view what the FPV camera is viewing while in flight and because of the bad design with all buttons on the same side of the Nokia 7 plus, unbeknownst to me all 3 buttons were being pressed at the same time and before I knew it my phone was shutting down and rebooting to this ridiculous download mode and the rest is history!
So I just thought I would mention this to anyone who happened to or happens to land in the same situation as me to be aware that you should probably put a little bit of sponge taped to the side of your phone over the volume buttons to possibly prevent it from being pressed simultaneously when flying your fpv drone.
If all else fails you could always connect the drone to your phone and then just put your phone in your pocket and fly blind by simply walking with the drone or rather running since they are pretty nippy. I am a bit bummed as this would have been a very convenient way of checking how full my guttering is of leaves without having to climb a ladder every time to check!?
Anyway I also used the fix here: https://www.techmesto.com/possible-fix-nokia-smartphone-stuck-on-download-mode-after-ota-update/
after downloading the nokia phone drivers from github.
If you are on windows 10 pro you may get a screen protector warning not to proceed further?
Ignore it and continue installing the drivers!
So far I got the Nokia Logo back and then it just hung there for several minutes without being recognised by the pc.
So I simply disconnected the phone from the pc and suddenly got the familiar nokia tone start up but then black screen again.
I realised it had been on the download mode so long it had completely drained the battery so now I am charging it.
Fingers crossed when I power up again I will at least have my phone back, sadly minus the data. (I will of course at least have all my google notes and contacts etc backed up to google servers at least they are useful for something!!)
I can't recall the last time I used it but I am pretty sure I had the SD card set as the main download so hopefully fingers crossed that data should have remained untouched, not sure how Android sets this up anymore?
Long time since gingerbread when you could still install and run apps as a completely separate partition.
All became a bit confusing after that so rooting became something I did hesitantly and as a definite last resort!
Anyway I am rambling on. If I find the fix works I will let you know.
Thanks for reading and thanks in advance if the fix works !!:good::good:
---------- Post added at 05:50 PM ---------- Previous post was at 05:23 PM ----------
leahcimewol said:
Yes I know that sounds like a weird title and maybe you are wondering why did I do that? notice the word accidently.
I was just trying to fly my newly bought drone x pro for the first time and the controller has a little pull out extendable cradle to hold the phone in
if you want to view what the FPV camera is viewing while in flight and because of the bad design with all buttons on the same side of the Nokia 7 plus, unbeknownst to me all 3 buttons were being pressed at the same time and before I knew it my phone was shutting down and rebooting to this ridiculous download mode and the rest is history!
So I just thought I would mention this to anyone who happened to or happens to land in the same situation as me to be aware that you should probably put a little bit of sponge taped to the side of your phone over the volume buttons to possibly prevent it from being pressed simultaneously when flying your fpv drone.
If all else fails you could always connect the drone to your phone and then just put your phone in your pocket and fly blind by simply walking with the drone or rather running since they are pretty nippy. I am a bit bummed as this would have been a very convenient way of checking how full my guttering is of leaves without having to climb a ladder every time to check!?
Anyway I also used the fix here: https://www.techmesto.com/possible-fix-nokia-smartphone-stuck-on-download-mode-after-ota-update/
after downloading the nokia phone drivers from github.
If you are on windows 10 pro you may get a screen protector warning not to proceed further?
Ignore it and continue installing the drivers!
So far I got the Nokia Logo back and then it just hung there for several minutes without being recognised by the pc.
So I simply disconnected the phone from the pc and suddenly got the familiar nokia tone start up but then black screen again.
I realised it had been on the download mode so long it had completely drained the battery so now I am charging it.
Fingers crossed when I power up again I will at least have my phone back, sadly minus the data. (I will of course at least have all my google notes and contacts etc backed up to google servers at least they are useful for something!!)
I can't recall the last time I used it but I am pretty sure I had the SD card set as the main download so hopefully fingers crossed that data should have remained untouched, not sure how Android sets this up anymore?
Long time since gingerbread when you could still install and run apps as a completely separate partition.
All became a bit confusing after that so rooting became something I did hesitantly and as a definite last resort!
Anyway I am rambling on. If I find the fix works I will let you know.
Thanks for reading and thanks in advance if the fix works !!:good::good:
Click to expand...
Click to collapse
So it worked, I have my phone back! Thank you so much for this solution!
Sadly my SD card was wiped too!!!!! super pissed off about this, many photos and notes and other files that I will never get back unless if I recall I may have made a manual backup of at least some of the earlier stuff I put on here a few months back on my pc?
Nokia will be hearing from me for sure!!!!! I want a 50% refund for messing with my life and my time. How can they send an update that essentially breaks a phone for a bit!???!!!!!!