Related
My N1 is on stock Froyo 2.2
I was playing RoboDefence and i got popup that battery is below 15%. I ignored the warning and completed the game. Plugged in the wall charger (N1 showed charging 11%) and slept off.
Next morning when i woke up i find that the track ball is blinking, tried to switch on the phone, nothing happens. Finally i remove the battery and replace it and still nothing happens.
Searched the web and came to know that its known problem, tried a work around and was finally able to boot it up and phone is working fine.
Next day i was on a 14 hour flight, forgot to switch off the phone. When i reached at destination i noticed that the battery is in red and immediately switched off the phone.
Reached hotel and plugged in the wall charger. Now whenever i boot my phone it goes into "FastBoot" menu. I tried clearing the cache, recovering, etc. But nothing happens.
Any suggestions are most welcome before i send my phone back to HTC.
Trackball stuck down?
Rusty! said:
Trackball stuck down?
Click to expand...
Click to collapse
Don't quite get your comment. Please help me understand if i need to do something.
Thanks.
To get into fastboot, you hold down the trackball and power on.
If the trackball had become stuck down, it would always boot into fastboot. Try cleaning it with something?
Thanks for the clarification. I will try that immediately.
I cleaned the track ball using wet towel. Powered up the phone and i get the same behavior i.e. phone comes into fastboot menu.
Shouldn't have used water, I had this same problem I got my trackball to wet when I was cleaning it with alcohol and it would only boot to fastboot you can reboot via fastboot and it will turn on into safe mode. My phone dried out in like two days I ran a logcat n it was showing I was pressing it when I wasn't hope this helps you out
Sent from my Nexus One using XDA App
Maybe your getting the screen that says fastboot. In that case...your volume down button is probably stuck.
That screen will have the options FASTBOOT - RECOVERY - CLEAR STORAGE - SIMLOCK. If that's the screen you see...your volume button is stuck.
SiNJiN76 said:
Maybe your getting the screen that says fastboot. In that case...your volume down button is probably stuck.
That screen will have the options FASTBOOT - RECOVERY - CLEAR STORAGE - SIMLOCK. If that's the screen you see...your volume button is stuck.
Click to expand...
Click to collapse
I think my volume down button is not struck, since when i go into fast boot menu i can select recovery, clear storage, etc using my volume up/ down buttons.
If it is struck then the selection should continuously move from top to down and repeat.
Called up HTC customer care. They want me to send the phone for repair. Will send it to them and keep the thread alive with updates.
I sent my phone to HTC and choose the option of repairing it. I received a phone this morning and i found that it is a different phone (Missing engraving and different IMEI number).
New one is working fine with no problems. However i didn't get any message from HTC that they are sending a new phone, etc.
Overall i am happy now that i am back on N1.
I opened this app (battery booster, can't post link because I am new) after downloading it excited to hoping it was better then a previous one I was trying that seemed to do next to nothing.
I saw the brightness button and hit it. It showed 11%. I was like oh I thought I had this all the way down...so I use the scroller to take it all the way down assuming 0% meant that it was the lowest it could possible dim the screen...well it sure is a battery saver considering I can't even see my screen as its completely BLACK...............................
1. Why would you even allow something like this in a app.
2. Please help me fix it...
I have tried for about an hour to assume where the scroll down, and mounting the phone to my computer so that I could possibly uninstall it via computer with no luck...
anyone????!
I don't want to piss you off or anything, but I had read a comment on another thread saying they could never get it to come back, even when they went back to stock.
You may need to head down to the Verizon store :/
chronster said:
I don't want to piss you off or anything, but I had read a comment on another thread saying they could never get it to come back, even when they went back to stock.
You may need to head down to the Verizon store :/
Click to expand...
Click to collapse
son of a...this is so stupid! What a bad feature to have in a app for idiots like myself apparently
if you have adb debugging you might be able to fix it...
http://forum.xda-developers.com/showthread.php?t=785603&highlight=horror
If you have usb debugging on, you can use adb to delete the app you downloaded I think. Did you have it enabled?
Florynce said:
If you have usb debugging on, you can use adb to delete the app you downloaded I think. Did you have it enabled?
Click to expand...
Click to collapse
I didn't have debugging on i checked via adb and long story short...i was still within 30 days of purchase ;-)
All may not be lost!!
If you're still in your 30 days take it back and exchange it.
If not, try booting into recovery mode and reset the phone. I don't think you need root to do that much and it should put the phone back to the way it was when you took it out of the box.
Hold down the volume button so that you are pressing both up & down volume at the same time (easiest to do with the battery cover off).
While holding the volume keys down press and hold the power button too. When the Samsung screen comes up release both buttons. A couple seconds later you will see the "Android system recovery" screen.
Press the volume down button until you have highlighted "wipe data/factory reset".
Press the "Home" button to select it.
You will then be told to press the volume up button to wipe the phone or press the volume down button to exit/cancel. Press volume up and follow any additional instructions. That's as far as I go to guide you (I want to keep my stuff as is ).
If that doesn't take care of the issue then you should take it to verizon and tell them what happened. Good luck and let me know if this worked for you!
~Johnny
Verizon HTC One
I'll tell you guys the whole story of the phone, in case you find something related to the actual problem in here.
All started when a friend of mine got me interested in ROMs and other modification his phone had.
I learned by myself all I needed to in order to Root, Unlock, and S-Off my phone, also I wrote the SuperCID to it (11111111) and installed the Custom Recovery.
It gave me a little trouble, but it was all good at the end.
Now was the time of the truth. I was about to flash my first Mod ROM, which was Android Revolution HD 71.1 .
Seconds after a successful installation (yay) I go and decide to reboot my phone, only to realize that what I just had installed was a Mod ROM for AT&T (I think, at least not supported to mine) HTC One.
Thanks to this, my phone got stuck in a bootloop, that at first made me panic a little bit, but then I saw that I could still get to the bootloader, and after some days of reading and what not, I got it to work again. Fully working, everything from a stock RUU, all nice and pretty.
"Then, where is the real problem?" you may be asking. Here it goes:
5 minutes after I finally got it fixed, I got all and exited and decided to flash a ROM properly this time.
I put the ROM inside the phone's internal memory.
I reboot phone.
It gets into bootloader.
I go and choose Recovery.
Here's where the "whoops" happen.
Since I had just installed a brand new stocked RUU, the Recovery also returned to stock, which I didn't really think that would happen by then.
Obiously, or at least it was what I thought by then, to flash a ROM I need to flash a Custom Recovery first.
So, following, even though I had already chosen the "Recovery" option, and it loaded, while it was doing a god-knows-what, I turned my phone off, which I guess and would assume that interrupted some kind of important process.
After that, my phone rebooted, and I was like "Phew, ok"
But it wouldn't get past the white screen with the HTC logo. There, after some 6 to 8 seconds, it rebooted, infinitely. It wouldn't turn off either, just reboots.
Like, at first I thought I'd need to call an exorcist, the damn thing seemed like it had the devil inside or something, acting on his own.
Then I realized it was that I had just screwed up everything, again.
So, resume:
I turned off my phone while it was on a Recovery's process.
After that, the phone wouldn't get past the white HTC's logo screen.
It would reboot, load the logo, and, after some 6 to 8 seconds, reboot, infinitely.
It wouldn't turn off either, I had to wait for the battery to die. Also, after this, when I plugged it to his charger, it turned on on his own again (the devil!) and started the same rebooting process.
So, what do you guys think?
Should I really call it a total brick? Do you think there's a way to fix it? Should I consider throwing it into Holy Water?
Notes:
-Can't get into bootloader.
-Can't flash boot
-ADB doesn't works on phone. Yes, I already had all kind of drivers since before, it just doesn't now.
-Can't get to recovery either.
Please answer, I'm lonely, I have no friends.
q.q
By the way, not an usual english speaker, please forgive any gramatical errors you may find.
Thank you for reading.
Hold down the power button and the volume down together, keep holding them, don't let go, the lights on the bottom will flash 10-15 Times, when the phone goes off, let go of the power button, but continue to hold down the volume down button, the phone should boot back to the bootloader, devil gone, I think you know what to do from there, first get a custom recovery on there, or run the ruu which you ran before to get stock Rom back on it.
KomuroXV said:
Verizon HTC One
I'll tell you guys the whole story of the phone, in case you find something related to the actual problem in here.
All started when a friend of mine got me interested in ROMs and other modification his phone had.
I learned by myself all I needed to in order to Root, Unlock, and S-Off my phone, also I wrote the SuperCID to it (11111111) and installed the Custom Recovery.
It gave me a little trouble, but it was all good at the end.
Now was the time of the truth. I was about to flash my first Mod ROM, which was Android Revolution HD 71.1 .
Seconds after a successful installation (yay) I go and decide to reboot my phone, only to realize that what I just had installed was a Mod ROM for AT&T (I think, at least not supported to mine) HTC One.
Thanks to this, my phone got stuck in a bootloop, that at first made me panic a little bit, but then I saw that I could still get to the bootloader, and after some days of reading and what not, I got it to work again. Fully working, everything from a stock RUU, all nice and pretty.
"Then, where is the real problem?" you may be asking. Here it goes:
5 minutes after I finally got it fixed, I got all and exited and decided to flash a ROM properly this time.
I put the ROM inside the phone's internal memory.
I reboot phone.
It gets into bootloader.
I go and choose Recovery.
Here's where the "whoops" happen.
Since I had just installed a brand new stocked RUU, the Recovery also returned to stock, which I didn't really think that would happen by then.
Obiously, or at least it was what I thought by then, to flash a ROM I need to flash a Custom Recovery first.
So, following, even though I had already chosen the "Recovery" option, and it loaded, while it was doing a god-knows-what, I turned my phone off, which I guess and would assume that interrupted some kind of important process.
After that, my phone rebooted, and I was like "Phew, ok"
But it wouldn't get past the white screen with the HTC logo. There, after some 6 to 8 seconds, it rebooted, infinitely. It wouldn't turn off either, just reboots.
Like, at first I thought I'd need to call an exorcist, the damn thing seemed like it had the devil inside or something, acting on his own.
Then I realized it was that I had just screwed up everything, again.
So, resume:
I turned off my phone while it was on a Recovery's process.
After that, the phone wouldn't get past the white HTC's logo screen.
It would reboot, load the logo, and, after some 6 to 8 seconds, reboot, infinitely.
It wouldn't turn off either, I had to wait for the battery to die. Also, after this, when I plugged it to his charger, it turned on on his own again (the devil!) and started the same rebooting process.
So, what do you guys think?
Should I really call it a total brick? Do you think there's a way to fix it? Should I consider throwing it into Holy Water?
Notes:
-Can't get into bootloader.
-Can't flash boot
-ADB doesn't works on phone. Yes, I already had all kind of drivers since before, it just doesn't now.
-Can't get to recovery either.
Please answer, I'm lonely, I have no friends.
q.q
By the way, not an usual english speaker, please forgive any gramatical errors you may find.
Thank you for reading.
Click to expand...
Click to collapse
Press POWER and VOLUME DOWN buttons together to get in bootloader fastboot. Try until it works.
Post a fastboot getvar all as nobody has any ideea what did u flashed...
ERASE your IMEI and SERIAL before posting the report.
Seanie280672 said:
Hold down the power button and the volume down together, keep holding them, don't let go, the lights on the bottom will flash 10-15 Times, when the phone goes off, let go of the power button, but continue to hold down the volume down button, the phone should boot back to the bootloader, devil gone, I think you know what to do from there, first get a custom recovery on there, or run the ruu which you ran before to get stock Rom back on it.
Click to expand...
Click to collapse
I kinda tried this before... it just reboots before the lights actually get o flash, but I guess it wouldn't hurt to try again. I'll let you guys know if it works.
UPDATE:
Nope, it didn't work. Devil's still inside the phone. Can't even reach bootloader yet.
Also, lights never flashed. As I said, it reboots before the lights even blink.
Fain11 said:
Press POWER and VOLUME DOWN buttons together to get in bootloader fastboot. Try until it works.
Post a fastboot getvar all as nobody has any ideea what did u flashed...
ERASE your IMEI and SERIAL before posting the report.
Click to expand...
Click to collapse
Can't post "fastboot getvar all" since I can't even get to the bootloader and fastboot.
I don't think problem is anything I flashed. Last thing was the RUU, and you can trust it was 100% functional.
Hell came down after I turned off while in stock's Recovery.
KomuroXV said:
I kinda tried this before... it just reboots before the lights actually get o flash, but I guess it wouldn't hurt to try again. I'll let you guys know if it works.
Can't post "fastboot getvar all" since I can't even get to the bootloader and fastboot.
I don't think problem is anything I flashed. Last thing was the RUU, and you can trust it was 100% functional.
Hell came down after I turned off while in stock's Recovery.
Click to expand...
Click to collapse
If the phone is getting to the white screen with HTC logo then your bootloader is ok, a brick is when the phone won't switch on at all, you just got to keep trying to get into the bootloader, once there, you can just run the ruu again
Seanie280672 said:
If the phone is getting to the white screen with HTC logo then your bootloader is ok, a brick is when the phone won't switch on at all, you just got to keep trying to get into the bootloader, once there, you can just run the ruu again
Click to expand...
Click to collapse
KomuroXV said:
UPDATE:
Nope, it didn't work. Devil's still inside the phone. Can't even reach bootloader yet.
Also, lights never flashed. As I said, it reboots before the lights even blink.
Click to expand...
Click to collapse
If only I could find a way to the bootloader mode, I would be so happy.
q.q
KomuroXV said:
If only I could find a way to the bootloader mode, I would be so happy.
q.q
Click to expand...
Click to collapse
Hold down the power button untill it shuts down.
If not, press POWER and VOLUME DOWN buttons together, don't wait for any blinking lights.
KomuroXV said:
I kinda tried this before... it just reboots before the lights actually get o flash, but I guess it wouldn't hurt to try again. I'll let you guys know if it works.
UPDATE:
Nope, it didn't work. Devil's still inside the phone. Can't even reach bootloader yet.
Also, lights never flashed. As I said, it reboots before the lights even blink.
Click to expand...
Click to collapse
@Seanie280672 you forgot the bright light
OP:
B) Force reboot
Press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)
the important part is when the phone reboots, let go of POWER but keep holding VOLDOWN
Fain11 said:
Hold down the power button untill it shuts down.
If not, press POWER and VOLUME DOWN buttons together, don't wait for any blinking lights.
Click to expand...
Click to collapse
I'm not really "waiting" for any lights. Right now it's turned off since the battery ran out a while ago.
What I do is that I:
-Plug it to the wall charger or computer.
-It turns on, on his own.
-But as soons as it tries, yes, I am pressing the Power+ Volume Down and never let it go.
-I also tried to, when the screen is the HTC's logo screen, hold Power + Volume Down until the screen went black, then I'd release the Power button leaving only the Volume Down in hold, didn't work either.
nkk71 said:
@Seanie280672 you forgot the bright light
OP:
B) Force reboot
Press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)
the important part is when the phone reboots, let go of POWER but keep holding VOLDOWN
Click to expand...
Click to collapse
Oh... yes, I've heard about the "bright light" to the sensor thing. I can tell also that it actually works.
If you hold the power button with the phone in front of a very bright light, you press power button, and no matter what the problem is it would actually turn off after some time. I did it and it worked, as in, it turned off.
But I've already tried pressing Power + Volume Down with the phone already turned off (having enough battery of course), but it didn't really work either, it just went into the same bootloop again.
I'd say it is that since I turned it off while in "stock Recovery" it was in the middle of something, as soon as the phone boots, it tries to boot in recovery, but it's giving me a some kind of error though, which causes it to reboot.
Back to trying a solution, since the phone is off but charged now, I'll try turning it on with Power + Volume Down WHILE I stuck it into a light bulb or something. Could some one please tell me too where is the "sensor" of this thing is located? I don't really know where am I supposed to be facing the phone, if back, or front, or side to the light.
KomuroXV said:
I'm not really "waiting" for any lights. Right now it's turned off since the battery ran out a while ago.
What I do is that I:
-Plug it to the wall charger or computer.
-It turns on, on his own.
-But as soons as it tries, yes, I am pressing the Power+ Volume Down and never let it go.
-I also tried to, when the screen is the HTC's logo screen, hold Power + Volume Down until the screen went black, then I'd release the Power button leaving only the Volume Down in hold, didn't work either.
Oh... yes, I've heard abot the "bright light" to the sensor thing. I can tell also that it actually works.
If you hold the power button with the phone in front of a very bright light, you press power button, and no matter what the problem is it would actually turn off after some time. I did it and it worked, as in, it turned off.
But I've already tried pressing Power + Volume Down with the phone already turned off (having enough battery of course), but it didn't really work either, it just went into the same bootloop again.
I'd say it is that since I turned it off while in "stock Recovery" it was in the middle of something, as soon as the phone boots, it tries to boot in recovery, but it's giving me a some kind of error though, which causes it to reboot.
Back to trying a solution, since the phone is off but charged now, I'll try turning it on with Power + Volume Down WHILE I stuck it into a light bulb or something. Could some one please tell me too where is the "sensor" of this thing is located? I don't really know where am I supposed to be facing the phone, if back, or front, or side to the light.
Click to expand...
Click to collapse
2 little dots on the left front top, opposite the camera, if you have another phone available to you, use the flashlight on it, that's plenty bright enough at close range.
Seanie280672 said:
2 little dots on the left front top, opposite the camera, if you have another phone available to you, use the flashlight on it, that's plenty bright enough at close range.
Click to expand...
Click to collapse
Did just that, right at those two little spots,but now the trick's not working, even though it had before, only I'm not sure if it was flashing to the two-little-spots.
Phone was charged and off. I turned it on holding Power+ Volume Down, with the phone's two spots facing straight to the flashlight.
It went straight into the bootloop still.
Are you sure it is there, and not right in the front or back camera?
Is it bricked?
So I decided to go running with my phone today in the morning. I used an old nike armband for iPhone, so nearly half of the phone was exposed to my arm. When I took it off, the exposed part of the phone, was sweaty, so I dried it off with my t shirt. The phone had a black screen. I tried to press and hold the power button until the phone rebooted, but all I got was a static screen for about one second. Afterwards, neither the screen nor button lights or LED indicator worked. I tried connecting the phone to the PC but nothing happened. It's an unlocked at&t HTC One m7 bought factory refurbished on ebay, running ViperOne custom ROM.
hugof99 said:
So I decided to go running with my phone today in the morning. I used an old nike armband for iPhone, so nearly half of the phone was exposed to my arm. When I took it off, the exposed part of the phone, was sweaty, so I dried it off with my t shirt. The phone had a black screen. I tried to press and hold the power button until the phone rebooted, but all I got was a static screen for about one second. Afterwards, neither the screen nor button lights or LED indicator worked. I tried connecting the phone to the PC but nothing happened. It's an unlocked at&t HTC One m7 bought factory refurbished on ebay, running ViperOne custom ROM.
Click to expand...
Click to collapse
Well, unlike your case, my phone was actually 99.9% clean since I fixed it with the RUU. I don't think there's a ROM related issue with these reboots my phone has now.
Problem: Turned phone off while it was doing something inside stock's Recovery. Now got caught in an infinite reboot because of that,
It is actually something like this.
http://www.youtube.com/watch?v=85HtJYcVAos
http://www.youtube.com/watch?v=rai4nCciKBg
http://www.youtube.com/watch?v=W5PCJYKaCrE
Just that mine is HTC One, and, well, besides from that screen it's also rebooting on his own every 8-10 seconds.
When you say you "turned it off" after selecting recovery, how did you do it?
I don't think that interrupting recovery when it's starting up ought to do anything.
Were you able to boot properly and use the phone after running the RUU?
My gut feeling is that there is some vestige of non-Verizon software on it gumming things up somehow.
You don't actually need to hold vol-down while pressing power. It will work just as well holding power until it stops blinking and then pressing vol-down as soon as the screen goes black. But you're saying that holding power down does nothing at all? It's just stuck in a continuous bootloop?
Have you tried seeing if it shows up in ADB?
iElvis said:
When you say you "turned it off" after selecting recovery, how did you do it?
I don't think that interrupting recovery when it's starting up ought to do anything.
Were you able to boot properly and use the phone after running the RUU?
My gut feeling is that there is some vestige of non-Verizon software on it gumming things up somehow.
You don't actually need to hold vol-down while pressing power. It will work just as well holding power until it stops blinking and then pressing vol-down as soon as the screen goes black. But you're saying that holding power down does nothing at all? It's just stuck in a continuous bootloop?
Have you tried seeing if it shows up in ADB?
Click to expand...
Click to collapse
Just as it sounds. I pressed down the power button to turn it off while Recovery was starting, and soon after that, the infinite bootloop started.
The RUU was 100% good, and I tested everything I could before trying to flash a ROM again.
But, just in case, it was this one:
http://www.htc1guru.com/2013/11/verizon-ruu-zip-1-10-605-10-posted/
Anyway, as I said, after I checked everything around the phone, I went to bootloader, clicked recovery by accident, and on reflex turned it off pressing down the power button.
Since then, there's been an infinite bootloop, rebooting every 8 to 10 seconds.
Sadly, and I guess it's because it was freshly flashed from a RUU, I can't access through ADB either.
q-q
Since it's powering on, your phone should be fixable, but that doesn't mean it's going to be easy.
I think the reason you're getting this bootloop is that it's trying to get into recovery--trying to complete the command you started--but something is preventing recovery from starting up. You likely did corrupt something by hard-rebooting in the middle of the process.
Fixing it will likely require some advanced methods in Linux. There is an unbricking thread in General--I would check in there for help.
Edit: It's in the Orginal Dev forum: http://forum.xda-developers.com/showthread.php?t=2770684
iElvis said:
Since it's powering on, your phone should be fixable, but that doesn't mean it's going to be easy.
I think the reason you're getting this bootloop is that it's trying to get into recovery--trying to complete the command you started--but something is preventing recovery from starting up. You likely did corrupt something by hard-rebooting in the middle of the process.
Fixing it will likely require some advanced methods in Linux. There is an unbricking thread in General--I would check in there for help.
Edit: It's in the Orginal Dev forum: http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
I've been trying to do this for days on my own (couldn't get help) but I finally managed to install a Unbuntu and run the sudo ./revive.sh
[email protected]:~$
[email protected]:~$ cd Downloads
[email protected]:~/Downloads$ chmod +x revive.sh
[email protected]:~/Downloads$ sudo ./revive.sh
HTC Unbricking Project M7_UL 0.6beta
Detecting bricked device..
Device can't be found, check connections. Aborting
The phone is actually connected to an USB 2.0 port, rebooting on his own still, but connected.
It's not detecting it though.
:/
This morning I noticed that my watch was restarting itself a few times while on charging dock, so I thought that there might be a new OTA. Then, when I'm about to leave, it just stay dead (it says disconnected on the phone too).
I tried long press (5, 8, almost a minute), nothing happens. When I placed it back onto the dock, it just show full battery icon and then nothing. I tried long-pressing the button while on the dock too, nothing...
I'm at loss here, if possible I'd like to avoid return (problematic, coz it is imported).
inscythe said:
This morning I noticed that my watch was restarting itself a few times while on charging dock, so I thought that there might be a new OTA. Then, when I'm about to leave, it just stay dead (it says disconnected on the phone too).
I tried long press (5, 8, almost a minute), nothing happens. When I placed it back onto the dock, it just show full battery icon and then nothing. I tried long-pressing the button while on the dock too, nothing...
I'm at loss here, if possible I'd like to avoid return (problematic, coz it is imported).
Click to expand...
Click to collapse
1. Hold the button until it starts vibrating, then keep holding until it turns off.
2. Press the button to turn it back on and then QUICKLY (as SOON as the LG logo shows), swipe from 11 o-clock to 5 o'clock (diagonally) on the screen to enter the bootloader.
3. Once you see the bootloader, tap > until the red text says RECOVERY MODE, then tap O to boot into recovery.
4. Once you see the green droid robot, tap the screen to bring up the recovery menu.
5. Swipe down until the factory reset option is highlighted, then press the button.
6. Swipe down until Yes is highlighted, then press the button.
7. Wait for the factory reset to complete.
8. Swipe up to highlight "reboot system now" in the recovery menu if it's not already highlighted and press the button to reboot.
9. Wait until the watch boots into the setup screen - this will take about 3x-5x longer than a normal boot, so be patient.
10. Set up the watch with your phone.
siraltus said:
1. Hold the button until it starts vibrating, then keep holding until it turns off.
2. Press the button to turn it back on and then QUICKLY (as SOON as the LG logo shows), swipe from 11 o-clock to 5 o'clock (diagonally) on the screen to enter the bootloader.
3. Once you see the bootloader, tap > until the red text says RECOVERY MODE, then tap O to boot into recovery.
4. Once you see the green droid robot, tap the screen to bring up the recovery menu.
5. Swipe down until the factory reset option is highlighted, then press the button.
6. Swipe down until Yes is highlighted, then press the button.
7. Wait for the factory reset to complete.
8. Swipe up to highlight "reboot system now" in the recovery menu if it's not already highlighted and press the button to reboot.
9. Wait until the watch boots into the setup screen - this will take about 3x-5x longer than a normal boot, so be patient.
10. Set up the watch with your phone.
Click to expand...
Click to collapse
I would have done the following if the thing actually can boot in any way. It seemed that it was stuck at some point in the booting process and somehow went into a 'limbo' state?
Thanks for the complete description, but here's how it ended up to me: it seemed that the watch was in an ON state all the while this thing was happening. I waited about 12 hours, until it is seemingly out of juice completely. Then, putting it back to the charger turned it back on and boots properly. Hopefully it won't happen again to me, or I have to send it back to the seller, really...
LG R watch "not turning on"
inscythe said:
This morning I noticed that my watch was restarting itself a few times while on charging dock, so I thought that there might be a new OTA. Then, when I'm about to leave, it just stay dead (it says disconnected on the phone too).
I tried long press (5, 8, almost a minute), nothing happens. When I placed it back onto the dock, it just show full battery icon and then nothing. I tried long-pressing the button while on the dock too, nothing...
I'm at loss here, if possible I'd like to avoid return (problematic, coz it is imported).
Click to expand...
Click to collapse
I'm in the same situation let see if once my watch gets fully charge I will try to do the process, you are not the only one with this problem
---------- Post added at 12:37 PM ---------- Previous post was at 12:29 PM ----------
inscythe said:
This morning I noticed that my watch was restarting itself a few times while on charging dock, so I thought that there might be a new OTA. Then, when I'm about to leave, it just stay dead (it says disconnected on the phone too).
I tried long press (5, 8, almost a minute), nothing happens. When I placed it back onto the dock, it just show full battery icon and then nothing. I tried long-pressing the button while on the dock too, nothing...
I'm at loss here, if possible I'd like to avoid return (problematic, coz it is imported).
Click to expand...
Click to collapse
alextabata said:
I'm in the same situation let see if once my watch gets fully charge I will try to do the process, you are not the only one with this problem
Click to expand...
Click to collapse
The last thing I remember was that I update my watch to the new lollipop android update.
Does it create the problem of in watch????
This process it's no working !!!!!!!
siraltus said:
1. Hold the button until it starts vibrating, then keep holding until it turns off.
2. Press the button to turn it back on and then QUICKLY (as SOON as the LG logo shows), swipe from 11 o-clock to 5 o'clock (diagonally) on the screen to enter the bootloader.
3. Once you see the bootloader, tap > until the red text says RECOVERY MODE, then tap O to boot into recovery.
4. Once you see the green droid robot, tap the screen to bring up the recovery menu.
5. Swipe down until the factory reset option is highlighted, then press the button.
6. Swipe down until Yes is highlighted, then press the button.
7. Wait for the factory reset to complete.
8. Swipe up to highlight "reboot system now" in the recovery menu if it's not already highlighted and press the button to reboot.
9. Wait until the watch boots into the setup screen - this will take about 3x-5x longer than a normal boot, so be patient.
10. Set up the watch with your phone.
Click to expand...
Click to collapse
How can I do the 2 step if the screen don't show any lg logo or any light at all?
By the way my phone says the watch is connected.
Please help
I have the same problem with my LG G Watch, it doesn't show LG logo, just showing charging and blinking with big battery logo while connected with charging cradle.
I keep it for 2 week to wait for battery drain, and again when I connect charging cradle it shows the same thing.
I guess there's something problem with hardware.
Anyone can guide me, how can i fix this.
Need help.
I just experienced the same issue. Leaving the watch to drain the battery does not help. Is there any other solution?
You're the man! Thanks for the step by step instructions! One thing I would add to your instructions would be to do all this while the watch is sitting on the charger. Seems like my watch didn't charge at all and when I tried to hold down on the button nothing happened until I did so with it sitting on the charger during the whole process. I just started to setup my watch and it's at 5% so that was definitely the case!
---------- Post added at 08:57 AM ---------- Previous post was at 08:55 AM ----------
Do the whole process with the watch sitting on the charger. This worked for me like a charm. The reason it's not doing anything is because the watch can't charge until you reset to factory settings.
---------- Post added at 08:57 AM ---------- Previous post was at 08:57 AM ----------
Do the whole process with the watch sitting on the charger. This worked for me like a charm. The reason it's not doing anything is because the watch can't charge until you reset to factory settings.
This happen to me once too. What is did was to just put the watch in the charger n long press the function button for about a min n it started up. For some reason the watch got stuck in a loop while it was charging over night. I have been experiencing a few strange bugs happen during the past few weeks. Such as watch zooming n not responding to touch control n watch not responding to turn wrist light up display.
My g watch also no stay "on" anymore, two days ago [battery was 57%] shuts down suddenly and since then I can not start this watch .
Tried everything, this anoying loop is killing me, if I put it for some time in the charger dock starts for a couple of seconds and shuts down [ sometimes shows starting 36 apps and after finish shuts down again]. Also for a couple of time I entered in recovery mode and reset and wipe, but from today I can not enter in bootloader anymore.
If stays on the charger not showing anything [ only if I kep the buton pressed for 30 sec start to blink the battery icon until I keep the button pressed.
Run out of methods, is something that I am not tried ? Keep all night on the charger , but the same litlle loop [ the watch is very hot on charger but I think is not charging].
Please some one can help me ?
Same issue
mobiemi said:
My g watch also no stay "on" anymore, two days ago [battery was 57%] shuts down suddenly and since then I can not start this watch .
Tried everything, this anoying loop is killing me, if I put it for some time in the charger dock starts for a couple of seconds and shuts down [ sometimes shows starting 36 apps and after finish shuts down again]. Also for a couple of time I entered in recovery mode and reset and wipe, but from today I can not enter in bootloader anymore.
If stays on the charger not showing anything [ only if I kep the buton pressed for 30 sec start to blink the battery icon until I keep the button pressed.
Run out of methods, is something that I am not tried ? Keep all night on the charger , but the same litlle loop [ the watch is very hot on charger but I think is not charging].
Please some one can help me ?
Click to expand...
Click to collapse
____________________________________________________________________________________________________
It started after the 5.1.1 update and we are not the only ones having this issue. I am trying to charge it while in bootloader mode using a higher voltage charger. I will report back if it works
tristarwolf said:
____________________________________________________________________________________________________
It started after the 5.1.1 update and we are not the only ones having this issue. I am trying to charge it while in bootloader mode using a higher voltage charger. I will report back if it works
Click to expand...
Click to collapse
OK,
Charging the LGR in bootloader mode worked but I am still having issues so now I am going to try to re-flash it.
If I leave the watch alone for a couple of hours and I put it in the charger, starts first time showing 36 apps and after it's shuts down. After that it starts for 2 or 3 times but only until those colored balls, then is dead again [ even if I leave it on the charger for all night ]. Also tried with 2.0 A and 1.0 A charger.
The worst is that I can not enter in bootloader mode anymore, when it starts on the LG icon I try in vain with my finger from 10.00 clock to 17.00 , the watch is not responding anymore to this command. Only when I put it on the charger and keep pressed the button for more then 30 seconds the battery icon is flashing, when I relese the button the battery icon disapears.
Very disapointed, I have to throw it in the garbage and I never will buy LG.
LG R watch fixed
mobiemi,
I got my watch back to working. First, delete all android wear apps from your phone do the same for the Android wear app. Next, clean the screen off (since you are having issues) then let it charge for a few minutes to an hour (even if it looks like its not charging it is). Once charge it might come back on all on its own (let it do so). After it tries twice it will not do it power on again (still let it sit for awhile longer). Next, take it off the charger and power the watch on and try to access the bootloader by swiping downward from 11 to 5 and perform a factory reset, put the watch back on the charger. Once done do a reboot and it will attempt to reset but might power off, don't panic mine did the samething. Finally let it sit on the charger awhile later it will come back on in factory reset mode, ready to connect to your phone. Let the watch sit to recharge before downloading the android wear app and connecting it back to your phone. FYI I did three times heres why- once I added an app it went back to having the same issue as before with restarting and dying. So word of advice do not install any apps. Google is working on a new update to fix the issue so be patient. I hope this helps!
Thank you for your detailed explanations, tried your method but dosen't work because I can not enter bootloader mode [ I think my watch has not enough power to start the bootloader ].
The screen is very clean and the watch not react at my command. I remember last week I was able to resurect once the watch with similar method like you, but now has not enough juice to start proper. When I put it in the charger show 1 second the battery icon, then starts with LG icon [ in vain try to enter bootloader ], once from 10 times starts, goes until starting 36 apps and shuts down [ when I left it for a period of time and is not that warm like when is lifted from charger ], but mainly not goes far then colored balls.
I have not another explanation for not entering the bootloader and why not going further than a few seconds. Left it 1 minute, half hour and also all night on the charger [ the watch get warmer ], with multiple charger and also from laptop usb.
My watch is slowly dying, only when I put it in the charger start for maximum 5 seconds and shuts down, after that I try again to start without charger [on the charger not starts at all ] and again after 4 seconds is dead. When starts the screen with LG icon did not react at all to finger touch , could not enter bootloader anymore[ lack of power ? ] I think in a couple of days is dead . Courious when is in the charger for longer period it gets very warm but in vain. Unfortunatelly I have no warranty.
I've had the same issue so I sent it in and I am patiently waiting to get it fixed. In the meantime they sent me a list of items they'll replace...
PCB assembly
Rechargeable battery
Cover assembly
LG2 (no idea what that's going to be)
Sent from my HTC One using Tapatalk
tristarwolf said:
mobiemi,
I got my watch back to working. First, delete all android wear apps from your phone do the same for the Android wear app. Next, clean the screen off (since you are having issues) then let it charge for a few minutes to an hour (even if it looks like its not charging it is). Once charge it might come back on all on its own (let it do so). After it tries twice it will not do it power on again (still let it sit for awhile longer). Next, take it off the charger and power the watch on and try to access the bootloader by swiping downward from 11 to 5 and perform a factory reset, put the watch back on the charger. Once done do a reboot and it will attempt to reset but might power off, don't panic mine did the samething. Finally let it sit on the charger awhile later it will come back on in factory reset mode, ready to connect to your phone. Let the watch sit to recharge before downloading the android wear app and connecting it back to your phone. FYI I did three times heres why- once I added an app it went back to having the same issue as before with restarting and dying. So word of advice do not install any apps. Google is working on a new update to fix the issue so be patient. I hope this helps!
Click to expand...
Click to collapse
I'm having the same problem like mobiemi. I'm trying your method without deleting all android apps in my phone since I wiped data and cache from my watch's recovery mode. Since it cannot connect to my phone due to not being able to boot properly, I don't think it's necessary to uninstall the apps from my phone. But I've been resetting and wiping data&cache from my watch but it's still doing the same thing. It shuts down on its own after "starting apps xx of xx". Sometimes it will boot till the colored dots and after that it will go blank and shuts down.
Yeah, I thought the same thing at first until I got it back up and running the first time and as soon as the old apps were sent back to the watch it started looping all over again. I was able to reinstall my apps after the latest android wear update. My LGR is currently working with apps and holding a charge longer than a day.
kevzz01 said:
I'm having the same problem like mobiemi. I'm trying your method without deleting all android apps in my phone since I wiped data and cache from my watch's recovery mode. Since it cannot connect to my phone due to not being able to boot properly, I don't think it's necessary to uninstall the apps from my phone. But I've been resetting and wiping data&cache from my watch but it's still doing the same thing. It shuts down on its own after "starting apps xx of xx". Sometimes it will boot till the colored dots and after that it will go blank and shuts down.
Click to expand...
Click to collapse
Hope is not true, unfortunately you are after me, after a while you can not enter either the bootloader . For two weeks I do nothing but I try to turn it on.
*If the button does not turn, I put in charger: starts 10 seconds goes out and turns back for another 30-40 seconds [colored balls], sometimes flashing until the 36 apps loaded, then goes off . I tried hundreds of times, placed in charger, power on from button, put back on charger, left and so on until going crazy.
**Because not enter bootloader I thought the touch it not works anymore, but by a miracle last week lit one minutes [came in white screen apps Starting 36] and went out, I powered by button and the screen shows the welcome screen, language, [responding to commands], unfortunately I was in another room and appeared on the screen put me in charge, until I got to the charger it faded again. From then I do not manage to get out of this deadly circle.
If someone manage to escape from this loop please help me with detailed steps.
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!???!!!!!!