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.
Hi guys,
The following problem has taken me litterally DAYS of reading XDA, trying everything I could, but still no solution. Googling and searching this forum didn't help either, and it's totally weird.
It's a Samsung Galaxy S GT-I9000, on which were installed, almost two years ago, the ClockWorkMod recovery, Darky's ROM, Froyo, and everything was fine for months. Then, one day, out of nowhere, it switched off, without notice. Impossible to switch it on again! I remembered having seen some strange battery behavior few days before, like falling from 80% to 30% with no reason, so I thought of a battery issue. I plugged it for a full night. In the morning, I was able to boot it, but not easily, and all apps were crashing: during boot, or when launched manually. Yes, all I tried were crashing! Then, the phone became fully not bootable: press the power button, the screen shows "Samsung GT-I9000", then switches off...
I ordered a new battery: same result.
A guy from a phone repair store told me to plug the phone, and keep the power button down for 2 minutes: after this, I could reboot the phone, and thus, wipe data (factory reset). But it didn't help.
After "playing" a bit with it, I realized that the problem is:
the phone won't boot if an external source of power is not connected (as said above, white text shows, then the phone "dies")
if started with power cord/usb, the phone will work fine, all the time
if started with power cord/usb, and the external power source removed once the phone is booted, the phone will work fine, UNTIL the screen goes black for power saving mode or by pressing pwoer button, after which, within seconds, you can't open the phone anymore. I mean: if you press the start/power button immediately after the screen goes black, the screen goes on again, and the phone is ok. If you wait for few seconds, it's over, you can't do anything, and have to reboot the phone. This said, the phone doesn't vibrate, so I suppose it's not really off. But then... what is this state??
I really tried my best: updated to GB2.3.6, bricked my phone trying to re-install the CWM and having a bootloop, installed and used Odin and Heimdall, reverted to stock kernel, etc, etc, etc.
I feel sorry to bother you guys, I was really convinced that with the incredibly huge amount of data, how-tos, explanations, etc. I would manage to get rid of this, but this problem, though I don't really think it's hardware (but maybe it is?) stayed across so many kernels, roms, etc. that it's killing me!
For the record:
Model number: GT-I9000
Micro-software (?): 2.3.6
Baseband: I9000XXJW4
Kernel: 2.6.35.7-I9000XWJW7-CL1125830 [email protected] #2 (problem was the same with [email protected] #2)
Version number: GINGERBREAD.XXJW4
Any help would be greatly appreciated, considering that a wireless phone that needs to be wired is a little bit of an issue... :laugh:
Thanks in advance !
Marc_B_ said:
Hi guys,
The following problem has taken me litterally DAYS of reading XDA, trying everything I could, but still no solution. Googling and searching this forum didn't help either, and it's totally weird.
It's a Samsung Galaxy S GT-I9000, on which were installed, almost two years ago, the ClockWorkMod recovery, Darky's ROM, Froyo, and everything was fine for months. Then, one day, out of nowhere, it switched off, without notice. Impossible to switch it on again! I remembered having seen some strange battery behavior few days before, like falling from 80% to 30% with no reason, so I thought of a battery issue. I plugged it for a full night. In the morning, I was able to boot it, but not easily, and all apps were crashing: during boot, or when launched manually. Yes, all I tried were crashing! Then, the phone became fully not bootable: press the power button, the screen shows "Samsung GT-I9000", then switches off...
I ordered a new battery: same result.
A guy from a phone repair store told me to plug the phone, and keep the power button down for 2 minutes: after this, I could reboot the phone, and thus, wipe data (factory reset). But it didn't help.
After "playing" a bit with it, I realized that the problem is:
the phone won't boot if an external source of power is not connected (as said above, white text shows, then the phone "dies")
if started with power cord/usb, the phone will work fine, all the time
if started with power cord/usb, and the external power source removed once the phone is booted, the phone will work fine, UNTIL the screen goes black for power saving mode or by pressing pwoer button, after which, within seconds, you can't open the phone anymore. I mean: if you press the start/power button immediately after the screen goes black, the screen goes on again, and the phone is ok. If you wait for few seconds, it's over, you can't do anything, and have to reboot the phone. This said, the phone doesn't vibrate, so I suppose it's not really off. But then... what is this state??
I really tried my best: updated to GB2.3.6, bricked my phone trying to re-install the CWM and having a bootloop, installed and used Odin and Heimdall, reverted to stock kernel, etc, etc, etc.
I feel sorry to bother you guys, I was really convinced that with the incredibly huge amount of data, how-tos, explanations, etc. I would manage to get rid of this, but this problem, though I don't really think it's hardware (but maybe it is?) stayed across so many kernels, roms, etc. that it's killing me!
For the record:
Model number: GT-I9000
Micro-software (?): 2.3.6
Baseband: I9000XXJW4
Kernel: 2.6.35.7-I9000XWJW7-CL1125830 [email protected] #2 (problem was the same with [email protected] #2)
Version number: GINGERBREAD.XXJW4
Any help would be greatly appreciated, considering that a wireless phone that needs to be wired is a little bit of an issue... :laugh:
Thanks in advance !
Click to expand...
Click to collapse
That's a very strange problem... let's try something, remove the battery, sim card and sd card and hold the power button for 1-2 minutes, btw when the screen is off, is really the phone off or just the screen? did you try to make a call to your phone when the screen is off?
timberman4444 said:
That's a very strange problem... let's try something, remove the battery, sim card and sd card and hold the power button for 1-2 minutes, btw when the screen is off, is really the phone off or just the screen? did you try to make a call to your phone when the screen is off?
Click to expand...
Click to collapse
Hi timberman thanks for the answer!
You're very right: I totally forgot to say that what initially allowed me to restart my phone "regularly" was this procedure of pressing the power button for 2 minutes (hint given by a man from a repair shop). Before this, I couldn't (kind of a bootloop).
It's a very good question! I don't think the phone is really off in fact, because there isn't this vibration saying the phone turned off... Let me try to call it!
F..k! I was redirected right away to the voicemail... so... phone was off
I'm starting to think it's an harware issue... I reinstalled lots of ROMs, kernel, etc. Same ****...
Any idea?
Marc_B_ said:
Hi timberman thanks for the answer!
You're very right: I totally forgot to say that what initially allowed me to restart my phone "regularly" was this procedure of pressing the power button for 2 minutes (hint given by a man from a repair shop). Before this, I couldn't (kind of a bootloop).
It's a very good question! I don't think the phone is really off in fact, because there isn't this vibration saying the phone turned off... Let me try to call it!
F..k! I was redirected right away to the voicemail... so... phone was off
I'm starting to think it's an harware issue... I reinstalled lots of ROMs, kernel, etc. Same ****...
Any idea?
Click to expand...
Click to collapse
Hi mark, i'm totally out of ideas for your problem... anyway, maybe you read mi answer wrong, in your post you say that the guy in the repair shop tell yo to press the power button with THE PHONE PLUGGED IN, but what i say is press the power button 2 minutes WITHOUT BATTERY, btw i keep thinking about this.. if any idea comes to my mind i tell you.
Hi again, try to play a song and turn the screen off to see what happens.
Sent from my GT-I9000 using xda app-developers app
timberman4444 said:
Hi mark, i'm totally out of ideas for your problem... anyway, maybe you read mi answer wrong, in your post you say that the guy in the repair shop tell yo to press the power button with THE PHONE PLUGGED IN, but what i say is press the power button 2 minutes WITHOUT BATTERY, btw i keep thinking about this.. if any idea comes to my mind i tell you.
Click to expand...
Click to collapse
Hi! Answering is already nice
I tried the button pressed for 2 minutes without battery: didn't change anything.
I tried playing a sound: MAN, YOU'RE A GENIUS!!! Launching the music, then forcing the screen off with power button lets the music play, and OF COURSE, I can reactivate the screen by pressing the home button. The screen goes off normally again after few seconds, but the music is still playing, etc. So, as long as the music goes, the bug doesn't happen!
Other hints:
For some time already, when I was removing the phone from my ear after a call, quite often, the screen was staying off, and I had to press a lot of buttons to have it on again, and be able to close the call
The moment where it crashes when booting without power is the very INSTANT where the initial white text (Samsung Galaxy S) goes brighter. So, if you unplug the power cord just after this, the boot ends normally. In summary, something happens at boot just after screen brightness changes which is the same thing happening when the screen goes off for power saving. All this, only when no external power is plugged.
Hehe, we (you) are making progress
Marc_B_ said:
Hi! Answering is already nice
I tried the button pressed for 2 minutes without battery: didn't change anything.
I tried playing a sound: MAN, YOU'RE A GENIUS!!! Launching the music, then forcing the screen off with power button lets the music play, and OF COURSE, I can reactivate the screen by pressing the home button. The screen goes off normally again after few seconds, but the music is still playing, etc. So, as long as the music goes, the bug doesn't happen!
Other hints:
For some time already, when I was removing the phone from my ear after a call, quite often, the screen was staying off, and I had to press a lot of buttons to have it on again, and be able to close the call
The moment where it crashes when booting without power is the very INSTANT where the initial white text (Samsung Galaxy S) goes brighter. So, if you unplug the power cord just after this, the boot ends normally. In summary, something happens at boot just after screen brightness changes which is the same thing happening when the screen goes off for power saving. All this, only when no external power is plugged.
Hehe, we (you) are making progress
Click to expand...
Click to collapse
Hi again, it seems like your phone is unable to exit the deep sleep mode or something like that so, let`s try another thing, in ICS or JB there´s an option in the developer option settings that unfortunately is not present in gingerbread roms, so, you can try to switch to a ICS/JB rom and go to settings-developer options and disable the "PM sleep mode" let`s see what happens then
timberman4444 said:
Hi again, it seems like your phone is unable to exit the deep sleep mode or something like that so, let`s try another thing, in ICS or JB there´s an option in the developer option settings that unfortunately is not present in gingerbread roms, so, you can try to switch to a ICS/JB rom and go to settings-developer options and disable the "PM sleep mode" let`s see what happens then
Click to expand...
Click to collapse
I tried to install ICS, with a GREAT tutorial found here: http://forum.xda-developers.com/showthread.php?t=1494493 Sadly, the phone reboots after installing the ICS kernel, and then doesn't work anymore, I had to reinstall the Gingerbread (I tried twice).
Last news: I let the phone play music (sound muted!!) for about 12 or 18h: all was fine! So I decided to pause the music, and see what happens. Boom ((c) Steve Jobs)!! The screen went black, and phone was "dead". I was expecting this, so no panick, I put back my SIM card, my SD card, and tried to reboot, with power cord plugged: it boots until the screen shows the small loader animation, then the empty battery image, but then goes black again, instead of showing the charging battery!! Download mode is still available, so I'll try to reflash the kernel, say.
It's like if each time screen was put black, phone was dying.
I can't stress enough how I appreciate your help: even if we can't save my phone, it's very pleasant to be able to TRY things. Thanks man!! :good:
Update: I reinstalled all... and it's not, even with power cord in, going further than the "Samsung Galaxy S" white text. The moment this picture disappears from screen, phone is dead. For good this time ?
Marc_B_ said:
I tried to install ICS, with a GREAT tutorial found here: http://forum.xda-developers.com/showthread.php?t=1494493 Sadly, the phone reboots after installing the ICS kernel, and then doesn't work anymore, I had to reinstall the Gingerbread (I tried twice).
Last news: I let the phone play music (sound muted!!) for about 12 or 18h: all was fine! So I decided to pause the music, and see what happens. Boom ((c) Steve Jobs)!! The screen went black, and phone was "dead". I was expecting this, so no panick, I put back my SIM card, my SD card, and tried to reboot, with power cord plugged: it boots until the screen shows the small loader animation, then the empty battery image, but then goes black again, instead of showing the charging battery!! Download mode is still available, so I'll try to reflash the kernel, say.
It's like if each time screen was put black, phone was dying.
I can't stress enough how I appreciate your help: even if we can't save my phone, it's very pleasant to be able to TRY things. Thanks man!! :good:
Update: I reinstalled all... and it's not, even with power cord in, going further than the "Samsung Galaxy S" white text. The moment this picture disappears from screen, phone is dead. For good this time ?
Click to expand...
Click to collapse
you tried to install the rom on the recovery instead of odin?
timberman4444 said:
you tried to install the rom on the recovery instead of odin?
Click to expand...
Click to collapse
Hi! No, I didn't, I used Odin. But now, I can't try anything anymore The only "results" I can get from this phone are:
- enter download mode and update from Odin (maybe from Heimdall, too, but I didn't check)
- reboot until the first moment the screen goes black, after which, the phone becomes fully unresponsive
Marc_B_ said:
Hi! No, I didn't, I used Odin. But now, I can't try anything anymore The only "results" I can get from this phone are:
- enter download mode and update from Odin (maybe from Heimdall, too, but I didn't check)
- reboot until the first moment the screen goes black, after which, the phone becomes fully unresponsive
Click to expand...
Click to collapse
so, you can`t install any rom at the moment?
timberman4444 said:
so, you can`t install any rom at the moment?
Click to expand...
Click to collapse
I can! I can install any kernel, or ROM, trhough Odin, but I can't boot at all... Except if someone has a magical trick, I would say it smells like coffin...
Marc_B_ said:
I can! I can install any kernel, or ROM, trhough Odin, but I can't boot at all... Except if someone has a magical trick, I would say it smells like coffin...
Click to expand...
Click to collapse
Pretty bad signals there.. i think you should go to a repair shop or buy another device
timberman4444 said:
Pretty bad signals there.. i think you should go to a repair shop or buy another device
Click to expand...
Click to collapse
Sadly, yes... thanks for helping however !
freeze & black screen
I got an issue with my lg g watch r. At first my watch faze just froze up. Turned it off by pressing button for 15seconds. After a while, i tried to turn it on again but the screen not display anything, just black like turned off. Tried to charge it, can feel the vibration but the screen just stays blank/black.
Can anyone help me?
This sound like a warranty issue ... you should return it.
pr0t0typ3 said:
freeze & black screen
I got an issue with my lg g watch r. At first my watch faze just froze up. Turned it off by pressing button for 15seconds. After a while, i tried to turn it on again but the screen not display anything, just black like turned off. Tried to charge it, can feel the vibration but the screen just stays blank/black.
Can anyone help me?
Click to expand...
Click to collapse
I have the same issue, did Yuo find any solution?
Same thing here. Screen froze while updating Facer then went blank. Long press on the crown to shut it down and then pressing again to restart it does not even display the startup animation. Android Wear app on phone shows it is connected though so it appears it is a screen driver issue. Haven't go the dock with me to try powrring it off then placing it on the charger to see if that wakes it up differently. Wish there was a way to perform a full reset via the app to see if it helps before returning it.
Same problem
:crying: I have the same problem do you found the solution ????? Apparently the watch is connected to my phone but the screen still black without responding.
I fixed this problem
pr0t0typ3 said:
freeze & black screen
I got an issue with my lg g watch r. At first my watch faze just froze up. Turned it off by pressing button for 15seconds. After a while, i tried to turn it on again but the screen not display anything, just black like turned off. Tried to charge it, can feel the vibration but the screen just stays blank/black.
Can anyone help me?
Click to expand...
Click to collapse
If you can feel the vibration and the watch is connected in your phone, the problem is not so bad, the solution I found was trying pressing the button at the right side until the watch stop the vibration several times, then the logo of Lg will appear in the screen, as soon as you see the logo touch the screen from 11 to 5 making a diagonal, and that's it.
Please be patient and don't give up the logo will appear and if you make the diagonal on the screen the reset menu will appear as well.
Not working any more
alextabata said:
If you can feel the vibration and the watch is connected in your phone, the problem is not so bad, the solution I found was trying pressing the button at the right side until the watch stop the vibration several times, then the logo of Lg will appear in the screen, as soon as you see the logo touch the screen from 11 to 5 making a diagonal, and that's it.
Please be patient and don't give up the logo will appear and if you make the diagonal on the screen the reset menu will appear as well.
Click to expand...
Click to collapse
After a day of use my watch my watch, return again in the same state that yesterday (black screen and refusing to turn on ) the worst thing is that it's not allowing me to go through the sistem menu as yesterday, probably is a hardware issue
i have the same problem , yesterday it went off and came back after couple of resets and today again , stuck on black screen, any idea ?
Solution
zoot600 said:
i have the same problem , yesterday it went off and came back after couple of resets and today again , stuck on black screen, any idea ?
Click to expand...
Click to collapse
You do have to delete, the android wear, the facer and the watchmaker then reinstall the android and see if the watch is ok, reinstall all but be sure that everything is for android wear 5.0 all have to be compatible.
Regards.
alextabata said:
You do have to delete, the android wear, the facer and the watchmaker then reinstall the android and see if the watch is ok, reinstall all but be sure that everything is for android wear 5.0 all have to be compatible.
Regards.
Click to expand...
Click to collapse
still nothing
any way to reset the watch (full factory reset ) ?
Two most hardcore way to reset it is this:
1) Press the crown until the watch vibrates and turns off
2) press it again until it turns on
3) swipe from top-left to the bottom-right corner, phone will boot into bootloader mode
4) select "RECOVERY" and confirm (use the symbols on the bottom of the screen)
5) it should boot into recovery
6) tap the screen, menu should display
7) using swipes (as indicated on the screen) select factory reset and confirm
8) select reboot
you watch should be brand new...
Recover first
zoot600 said:
still nothing
any way to reset the watch (full factory reset ) ?
Click to expand...
Click to collapse
Don't do it. The factory reset it must be your last choice. Because after that your watch don't going to be able pairing with your phone.
First make sure you delete all related with the wear from your phone. Try to restore your watch pressing the button until the Lg logo appear as soon as you see the logo press the screen from 11 to 5 making a diagonal, then enter to the recovery mode the watch will show it. Recover the system.
the screen is not active - no lg boot logo , and when i swipe (blindly) to get into bootloader still no screen
I've connected the watch to the computer and it connected so i know its in bootloader
I don't think there's nothing else to do but to return it
can't return it :| will give it another go later
Do you delete all applications before do the recovery mode .. The problem sometimes come because the facer or the watchmaker are not the new versions for aw 5.0. Or because you don't installed the android wear from the playstore ( use a external download ) .1 - The cure is delete all from the phone (apps ) and after reinstall all in the watch.2- If you have the screen totally off. You can try to recover the watch with adb but I down know the method for it.. 3 - the problem after the factory reset is that after it if your watch is still with the black screen the only solution is send it back for warranty but if your wife is able to start again so do you have to reinstall the android wear from the playstore and after all your apps bit taking care that all are compatible wit AW 5.0.
I hope this help you..
If he resets the watch but the LG logo isn't there, is able to get to bootloader but nothing shows on display - that's _NOT_ caused by any application. It's a hardware fault, no doubt about that.
Yes agree . In case that the watch after a factory reset still continue with the problem , the only explication is a hardware failure ,may be in the intern memory ... But in this case the only solution will be send the watch to warranty ...
alextabata said:
Yes agree . In case that the watch after a factory reset still continue with the problem , the only explication is a hardware failure ,may be in the intern memory ... But in this case the only solution will be send the watch to warranty ...
Click to expand...
Click to collapse
Hi Alex,
Did you end-up sending your watch to warranty? Currently having the same problem with mine
ssptff said:
Hi Alex,
Did you end-up sending your watch to warranty? Currently having the same problem with mine
Click to expand...
Click to collapse
i'm having the same problem.
rip
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!???!!!!!!