Related
And now I'm boot looping won't go past n color startup animation wth
Sent from my Cyanogen Mod EVO using Tapatalk
I had that problem on my NC when it was rooted. Luckily I had another problem that let me get out by the 8 times reset manual method. Mine would occasionally update itself back to version 1.0.0. When it did that I managed to reset it & now a new NC is on its way to replace this one.
This probably won't help solve the issue but at least it lets you know you're not alone.
Mine boot looped and I did the full 8X reboot thing and then the 3 button data reset. All of that puts you back to "out-of-the-box" stock. You can then redo the autonooter rooting procedure.
Can't get out
I am stuck in a boot loop and cant get out.
First it was stuck on the droid boot animation from the auto config. After I put the autonooter card back in it started looping the rooted boot animation.
Did the 3 button thing and that forced an update but went back to bootlooping the rooted animation.
Then did the 8X reboots manually and that also forced the down arrow update, but then it still bootloops.
I tried getting in from PuTTy (as admin) but it never connects. Do I just use port 22? (to 192.168.2.2 with Data and username as root?)
adb doesn't work... going to bed now and will try again tomorrow after work.
What i had to do to resolve my issue was that was to do the 8x reset to trigger the factory reset of the OS and then do the 3 button reset of the user data. In my case it was a self tweaked issue with an app permisson. If I remember right the key combo is Power+VolUp+"n" key. Try this and let us know.
Sent from my NookColor using XDA App
Bigger Issues.... First Brick?
Nate731 said:
What i had to do to resolve my issue was that was to do the 8x reset to trigger the factory reset of the OS and then do the 3 button reset of the user data. In my case it was a self tweaked issue with an app permisson. If I remember right the key combo is Power+VolUp+"n" key. Try this and let us know.
Sent from my NookColor using XDA App
Click to expand...
Click to collapse
So ... I left my Nook in what I thought was an "OFF" state last night, only to bring it to work and find it says "Battery too low to Power on" "Please wait 15 minutes and try again"
I think... no worries... plug it in and let 'er sit for an hour.... an hour passes and I'm still getting the same screen.
Is this better or worse? let me see...
1) if it stays like this, I can return/exchange it at B&N and they won't be able to verify that it was rooted due to non-bootiness
2) If it eventually boots, I will have to try to get it out of bootloop.
3) If it comes to life and I can't get it out of bootloop, I will drain the battery again and go back to #1.
Any thoughts besides this current train?
sort of working?
OK....
so after charging on USB port (all I have at work today as I forgot the base to the charger), it will bootloop again... yay!
problem is... the bootloops take too much juice and won't allow me to fail 8 reboots. I can't even charge it up enough since I'm on USB charging and it keeps trying to turn itself on.
2 Options i see:
1) Go home and charge it on the wall and see if that helps
2) Discharge it to death and return within my 30 days (X-mas gift)
Doubt this will work, but have you tried putting in an autonooter sdcard and then plug it into the usb? If it tries to boot maybe it will boot from that sdcard?
Boot from the Froyo SD card, then fix /rom/devconf/BootCnt from ADB.
Cal you never mentioned if you cleared the user data... Did you?
Nate731 said:
Cal you never mentioned if you cleared the user data... Did you?
Click to expand...
Click to collapse
If you mean the 3 button reset? Yes.
If not... I did not because I'm not aware of it. (couldn't through the UI of course)
cal3thousand said:
If you mean the 3 button reset? Yes.
If not... I did not because I'm not aware of it. (couldn't through the UI of course)
Click to expand...
Click to collapse
Try Geezer's tip but do this:
Do three button reset WITH the autonooter card in there.
Got it working
Finally got it working after creating a Nookie Froyo card and booting off of that.
Then I reinstalled ADB on my work computer and reset the BootCnt file to 8...
that successfully restored /system and then the 3 finger trick actually gave an option to wipe.
Now to start over.
New Question: How likely is this hardware related and should I be looking to replace it before my 30 days is up>?
I ran into the same problem, trying the same solution - any luck the second time?
JasonBunting said:
I ran into the same problem, trying the same solution - any luck the second time?
Click to expand...
Click to collapse
My Nook has been great since the fix. But I also needed to use a program to turn off Wifi when I turn the display off.
I did it all from my Nookie...
confused?!
I was wondering how you fixed this..i have read everywhere, but nothing...im stuck in the nook co screen. This happened right after i plugged my nook to charge after my battery was drained...thnks
[FIX][08.04.2011]Patch for "Screen won't come on after device wakes" (RHO_S2_00895)
Problem: Device doesn't come back from suspended mode. Pressing the power button, sliding out the keyboard or taking out the stylus does nothing.
Occurrence: Random.
Quick fix: None known.
Request: Kinda all over the Rhod forums.
Affected ROMs: HTC Stock S2 2.07, all custom roms based on 2.07 drivers. Probably 2.10 drivers are partly affected too.
Patch:
For stock roms (standard HTC patch package, .exe)
For custom roms (download this if you're unsure, works for stock roms too)
For cooks (extract and put into OEMDrivers)
Thanks!
Let's see (in time) if the SOD's are finished for us.
HRQ.SLV said:
Thanks!
Let's see (in time) if the SOD's are finished for us.
Click to expand...
Click to collapse
It must be a matter of settings or hardware, I never suffered from SoD.
Jackos said:
It must be a matter of settings or hardware, I never suffered from SoD.
Click to expand...
Click to collapse
That's because youre a great cook!
This thread should be sticky...
HRQ.SLV said:
That's because youre a great cook!
This thread should be sticky...
Click to expand...
Click to collapse
Not only this one should be sticky...
.......Done
Installed. Didn't work . I think the flex cable is crapping out. Also had the problem where if the screen was fully slid, it'd black out. Now it's been like that every postion.
Although, the power button works to turn the screen off, it won't turn it back on.
It doesn't work for me either
The only thing that I was able to install on my Tilt 2 (latest stock ROM) was this file Jackos RHO_S2_00895.cab
Nothing changed.
The screen goes on but what stays off is the backlight and the only way to get the backlight to stay on in a reboot. Then try to adjust the brightness from the settings menu and moving the slides doesn't do anything. The brightness stays to the max no matter what.
Is it the light sensor? can it be disabled or checked somehow?
Thanks anyway I hope your fix helps others,
G
Jackos said:
It must be a matter of settings or hardware, I never suffered from SoD.
Click to expand...
Click to collapse
Thanks for sharing...I have had SOD only with certain builds...its been a while since I had one...
KnightmareCS said:
Installed. Didn't work . I think the flex cable is crapping out. Also had the problem where if the screen was fully slid, it'd black out. Now it's been like that every postion.
Although, the power button works to turn the screen off, it won't turn it back on.
Click to expand...
Click to collapse
Does it sometimes don't come back or always?
SoD, Sleep Of Death, so called the hangup issue does happen only after the device is suspended for a long time. It does occur kinda often, but not always if you turn off the screen. If your device never comes back from standby it isn't a problem with SoD for sure.
That would be my [email protected] cable....
KnightmareCS said:
Installed. Didn't work . I think the flex cable is crapping out. Also had the problem where if the screen was fully slid, it'd black out. Now it's been like that every postion.
Although, the power button works to turn the screen off, it won't turn it back on.
Click to expand...
Click to collapse
bisanti said:
The only thing that I was able to install on my Tilt 2 (latest stock ROM) was this file Jackos RHO_S2_00895.cab
Nothing changed.
The screen goes on but what stays off is the backlight and the only way to get the backlight to stay on in a reboot. Then try to adjust the brightness from the settings menu and moving the slides doesn't do anything. The brightness stays to the max no matter what.
Is it the light sensor? can it be disabled or checked somehow?
Thanks anyway I hope your fix helps others,
G
Click to expand...
Click to collapse
The exe file (for stock roms) is intended to work on Europe roms. I have no knowledge of HTC releasing this patch for other regions.
It's no fix for any problem with the phone The patch doesn't even touch the backlight thing.
Jackos said:
Does it sometimes don't come back or always?
SoD, Sleep Of Death, so called the hangup issue does happen only after the device is suspended for a long time. It does occur kinda often, but not always if you turn off the screen. If your device never comes back from standby it isn't a problem with SoD for sure.
Click to expand...
Click to collapse
It happens all the time. I turn the phone on via the power button. Boots up. Let it sit till backlight goes off. Press power button, nothing happens.
I can turn the phone on, press the power button to turn the backlight off and when I press it again, nothing happens.
Wild Child said:
That would be my [email protected] cable....
Click to expand...
Click to collapse
I do not think it's a flexcable problem. If I can turn the screen off and power on the device with the 'power button', it has to be something software.
I have to check again if the device comes back on, but with really really low backlight.
It's annoying, I have to restart to see a text, missed call, etc.
Thanks for your help so far.
Won't wake up
I tried loading this patch after doing yet another hard reset to try to recover from these outages. It doesn't work. Within an hour of installing it, the problem came back. My specific problem is the system goes to sleep after a minute, and it usually comes back with the power button. But after normal usage for awhile (sometimes hours, sometimes weeks without a problem), it goes to sleep and needs a red-button-reset to turn back on. Then as soon as it goes to sleep again after powering up, it's off forever. The only real recover after reaching this "cycle of death" is a hard reset (full memory erase, back to factory settings). Then it will work normally again for awhile.
I'm not sure if this is exactly the problem the other submitters were seeing, but it is surely related.
I'm off to do yet another factory reset. WM 6.5 is not worth a tinker's damn.
(AT&T Tilt 2 with ROM 2.10.502.4)
pbarschall said:
I tried loading this patch after doing yet another hard reset to try to recover from these outages. It doesn't work. Within an hour of installing it, the problem came back. My specific problem is the system goes to sleep after a minute, and it usually comes back with the power button. But after normal usage for awhile (sometimes hours, sometimes weeks without a problem), it goes to sleep and needs a red-button-reset to turn back on. Then as soon as it goes to sleep again after powering up, it's off forever. The only real recover after reaching this "cycle of death" is a hard reset (full memory erase, back to factory settings). Then it will work normally again for awhile.
I'm not sure if this is exactly the problem the other submitters were seeing, but it is surely related.
I'm off to do yet another factory reset. WM 6.5 is not worth a tinker's damn.
(AT&T Tilt 2 with ROM 2.10.502.4)
Click to expand...
Click to collapse
It's a pity that it doesn't work for you. This is a patch for Europe branded devices, I don't even see the fix at any other region-based HTC support site.
Personally I never experienced SoD, so I cannot guarantee that it does work. All I know is that this fix is supposed to help with "constant hang". Whatever it is. It's a official fix and I didn't encounter any problems with running it on my Europe branded Rhod.
Jackos is this in your ROM? I have found several times my TP2 needs a reset as the power button does not bring it life. If I take the stylus out (when this happens) the row of keys light up, but still the display is blank. I assume it's already in your ROM (Jackos S3 1.1.2 SleekBASIC) otherwise I would have installed it.
It's going to be included from version 1.1.3 and up.
Jackos said:
It's a pity that it doesn't work for you. This is a patch for Europe branded devices, I don't even see the fix at any other region-based HTC support site.
Personally I never experienced SoD, so I cannot guarantee that it does work. All I know is that this fix is supposed to help with "constant hang". Whatever it is. It's a official fix and I didn't encounter any problems with running it on my Europe branded Rhod.
Click to expand...
Click to collapse
So...how do I uninstall it? I am on sprint in the US and have the latest official win 6.5 ROM and downloaded this update on my phone through a tech website and after installing it none of my keys works except for the power button. Apparently being for Europe it has corrupted my phone and none of the talk, end, windows, back or keyboard buttons work now. I need to revert this update, is there a way without doing a hard reset. I don't want to reconfigure all my settings that aren't backed up.
scottandmo said:
So...how do I uninstall it? I am on sprint in the US and have the latest official win 6.5 ROM and downloaded this update on my phone through a tech website and after installing it none of my keys works except for the power button. No talk, end, windows, back or keyboard buttons work now. I need to revert this update, is there a way without doing a hard reset. I don't want to reconfigure all my settings that aren't backed up.
Click to expand...
Click to collapse
If anything really fails, navigate into /Windows/ directory using your favorite file manager and "delete" those two files:
Code:
debuglog.dll
HtcPm.dll
Probably deleting the second file should fix your keyboard issues.
Jackos said:
If anything really fails, navigate into /Windows/ directory using your favorite file manager and "delete" those two files:
Code:
debuglog.dll
HtcPm.dll
Probably deleting the second file should fix your keyboard issues.
Click to expand...
Click to collapse
Deleting the HtcPm.dll and rebooting fixed it, Thanks! I'm assuming that won't have any other side effects...
Hi,
My Streak froze today as I was trying to get NOVA 2 working. I had to wait until the battery ran out, like 4 hours or something.
Was wondering if you can hard reset the streak 7 and how to?
I had a similar thing happen to me. If you open up the slot where the SD card goes, look to the left and there is a hole there to reset the device. If you use a paperclip or a safety pin you can resolve this problem. HTH
Thanks a lot for that, handy to know.
dancforfreedom said:
Hi,
My Streak froze today as I was trying to get NOVA 2 working. I had to wait until the battery ran out, like 4 hours or something.
Was wondering if you can hard reset the streak 7 and how to?
Click to expand...
Click to collapse
The paperclip is only to force the S7 to turn off. To reset, press and hold the + key while powering up. That takes you to a menu that will allow either a full or partial reset. I am speaking of the stock ROM only.
Today my 4X encountered a strange problem: It shut down itself (I thought the battery was empty and charged it), and after restarting it just shuts down immediately. It shows the lockscreen saying "no SIM" and then shuts down. Anyone know a solution to fix this? I suppose a factory reset might do it, but I don't have a backup now and would like to keep my data.
muellersmattes said:
Today my 4X encountered a strange problem: It shut down itself (I thought the battery was empty and charged it), and after restarting it just shuts down immediately. It shows the lockscreen saying "no SIM" and then shuts down. Anyone know a solution to fix this? I suppose a factory reset might do it, but I don't have a backup now and would like to keep my data.
Click to expand...
Click to collapse
If it is the SIM then try a different SIM, or put a folded piece of paper between the holder and the SIM - I always do that with phones just to make sure it keeps good contact at all times.
Other than that, no real idea mate - sorry
I think it should also work without a SIM. But as said, it just shows the lockscreen for ~2 seconds and then shuts down. I have tried without a sim, it's the same. I'll try with a different one, but I suppose that won't help much. I think i'll also try a kdz reflash, but i'll have to set up my father's PC to do so. Just thought maybe someone knows a quick solution.
Alright, i've just done a kdz reflash - same situation. Is there a way to adb pull the /data/data from any of the other modes (recovery, Emergency etc.?)
muellersmattes said:
Alright, i've just done a kdz reflash - same situation. Is there a way to adb pull the /data/data from any of the other modes (recovery, Emergency etc.?)
Click to expand...
Click to collapse
Weird... Reflash use to replace all files and stock settings unless you have some app avoiding them to run... Reflash don't delete installed apps most part of the time. If you have frozen apps they'll remain frozen. Did you factory reset before reflash?
Sent from my LG-P880 using xda app-developers app
RuedasLocas said:
Weird... Reflash use to replace all files and stock settings unless you have some app avoiding them to run... Reflash don't delete installed apps most part of the time. If you have frozen apps they'll remain frozen. Did you factory reset before reflash?
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
No, as said i wanted to try everything before doing a factory reset (don't have a recent backup because Ubuntu won't recognize the MTP mode properly). I have restarted the phone many times before without that strange behaviour and didn't freeze anything since then. I just can't tell where the problem comes from. BTW, the SIM is recognised now (after the reflash), but still shutting down.
muellersmattes said:
No, as said i wanted to try everything before doing a factory reset (don't have a recent backup because Ubuntu won't recognize the MTP mode properly). I have restarted the phone many times before without that strange behaviour and didn't freeze anything since then. I just can't tell where the problem comes from. BTW, the SIM is recognised now (after the reflash), but still shutting down.
Click to expand...
Click to collapse
You notice some over heat, you try to use it without SD card, it keeps rebooting when charger is connected?...
Cause appart of hardware malfunction, I can't see any other reason... of course we don't know if the system file is corrupted or not...
If the phone is ON time enough, you can copy the data files/ folders to your SD card, after save them all you can factory reset...
Wait for better help cause I have no idea... sorry
RuedasLocas said:
You notice some over heat, you try to use it without SD card, it keeps rebooting when charger is connected?...
Cause appart of hardware malfunction, I can't see any other reason... of course we don't know if the system file is corrupted or not...
If the phone is ON time enough, you can copy the data files/ folders to your SD card, after save them all you can factory reset...
Wait for better help cause I have no idea... sorry
Click to expand...
Click to collapse
It's not because of heat, the phone is really cool. It just stays on for a second or so, just enough to see the lockscreen or the "Enter PIN" screen and then it shuts down. It's like the battery was empty, but it's charged. It even shows the charged battery symbol. Guess I'll have to do a factory reset and lose my data. As root is gone, I also can't boot to the bootstrap recovery (with this method) to backup there. Should have done that before doing a reflash...
muellersmattes said:
It's not because of heat, the phone is really cool. It just stays on for a second or so, just enough to see the lockscreen or the "Enter PIN" screen and then it shuts down. It's like the battery was empty, but it's charged. It even shows the charged battery symbol. Guess I'll have to do a factory reset and lose my data. As root is gone, I also can't boot to the bootstrap recovery (with this method) to backup there. Should have done that before doing a reflash...
Click to expand...
Click to collapse
You can try to downgrade before factory reset... some apps won't work but, maybe the phone just don't turn OFF and you'll be able to save your data.
So downgrading didn't work either. I'll use the LG Support Tool to upgrade and factory reset now (with data loss). That should hopefully fix it.
Well, the LG Support tool also didn't fix it. Data is lost now, so I can freely do whatever I want
I've tried to get into the "low-level mode" (http://forum.xda-developers.com/showpost.php?p=35524491&postcount=11), but no success. Can someone point me into the right direction and on how to press those buttons? I've tried several combinations, but they all didn't work out - either the battery symbol appeared or the phone booted to recovery or to the "do not touch cable notice" mode.
As far as I understand I should do the following steps:
1) Remove the battery and USB cable
2) Insert the battery and plug in the cable. The phone vibrates once, then shows the LG logo, then shows a battery symbol and then turns off the screen.
3) Press Vol+ and power and hold it. The battery logo shows again. There is a sound indicating that some device is connected to Windows. The screen turns off and there is a sound indicating that the device is disconnected from Windows. Let go off the buttons.
4) Press the buttons again until there is a sound indicating that a device is connected to Windows. Let go off the buttons. The screen should remain off.
Is this correct? What am I doing wrong? Do I have to wait at some point for some action? As said, all I ever got was the "battery symbol" again (for a few seconds).
muellersmattes said:
Well, the LG Support tool also didn't fix it. Data is lost now, so I can freely do whatever I want
I've tried to get into the "low-level mode" (http://forum.xda-developers.com/showpost.php?p=35524491&postcount=11), but no success. Can someone point me into the right direction and on how to press those buttons? I've tried several combinations, but they all didn't work out - either the battery symbol appeared or the phone booted to recovery or to the "do not touch cable notice" mode.
As far as I understand I should do the following steps:
1) Remove the battery and USB cable
2) Insert the battery and plug in the cable. The phone vibrates once, then shows the LG logo, then shows a battery symbol and then turns off the screen.
3) Press Vol+ and power and hold it. The battery logo shows again. There is a sound indicating that some device is connected to Windows. The screen turns off and there is a sound indicating that the device is disconnected from Windows. Let go off the buttons.
4) Press the buttons again until there is a sound indicating that a device is connected to Windows. Let go off the buttons. The screen should remain off.
Is this correct? What am I doing wrong? Do I have to wait at some point for some action? As said, all I ever got was the "battery symbol" again (for a few seconds).
Click to expand...
Click to collapse
Once that data is gone, just reflash the phone.
My advice, like always is, downgrade, factory reset, upgrade , root, factory reset.
hope you don't tell me that you have problems with flash method...
I have tried that. Flashed v10a, wiped data in recovery, upgraded to v10h via LG Support Tool. Still shutting down. I thought the emergency recovery might fix it but I cant get the emergency mode to work. I'll call the LG support tomorrow and hope they'll bring me a new phone.
Gesendet von meinem ASUS Transformer Pad TF300TG mit Tapatalk 2
muellersmattes said:
I have tried that. Flashed v10a, wiped data in recovery, upgraded to v10h via LG Support Tool. Still shutting down. I thought the emergency recovery might fix it but I cant get the emergency mode to work. I'll call the LG support tomorrow and hope they'll bring me a new phone.
Gesendet von meinem ASUS Transformer Pad TF300TG mit Tapatalk 2
Click to expand...
Click to collapse
If when you're flashing, you use "web upgrade" instead of normal upgrade, it will upgrade with LG Tool, official firmware, what it means that is the same than the emergency recovery that you're trying to use.
The difference is that you don't need to use IMEI. The detection is automatic.
RuedasLocas said:
If when you're flashing, you use "web upgrade" instead of normal upgrade, it will upgrade with LG Tool, official firmware, what it means that is the same than the emergency recovery that you're trying to use.
The difference is that you don't need to use IMEI. The detection is automatic.
Click to expand...
Click to collapse
Thanks, I thought the Emergency Recovery was still different. So no chance to fix this now. LG's support won't work on Christmas, so three more days stuck with it.
I got the phone back today. Put the battery in, started, and... it shut down. AGAIN. They were supposed to fix that! Anyone near me who has a spare battery for testing? After all that might be faulty.
muellersmattes said:
I got the phone back today. Put the battery in, started, and... it shut down. AGAIN. They were supposed to fix that! Anyone near me who has a spare battery for testing? After all that might be faulty.
Click to expand...
Click to collapse
It goes down when charger is connected?
Yes, it does. And it recognises the battery as full, that's why I don't suppose it's because of that. But one never knows.
mines done it a couple times recently too! just living with it till the update!
Problem solved. A new battery did the trick. But I still don't know why it would shut down with the old one.
Hi everyone, I'm sure this question has been answered before but being a complete noob, I honestly don't understand ANY of the technical terms such as "rooting", "flashing", "ROMS", etc etc. So most of the answers I have read make zero sense to me.
My phone started bootlooping when it was in my bag and I have no idea why it started doing so. The battery ended up draining enough to get it out of the bootloop and it was working fine for a day or so, until I put it back in my bag to go out and when I took it out, it was bootlooping again.
What I am trying to ask is what might be the cause of this and is there anyone who can explain how to fix this issue (in simple terms) so that I'd understand?
Cheers.
mine is doing same!
lostpigeon said:
Hi everyone, I'm sure this question has been answered before but being a complete noob, I honestly don't understand ANY of the technical terms such as "rooting", "flashing", "ROMS", etc etc. So most of the answers I have read make zero sense to me.
My phone started bootlooping when it was in my bag and I have no idea why it started doing so. The battery ended up draining enough to get it out of the bootloop and it was working fine for a day or so, until I put it back in my bag to go out and when I took it out, it was bootlooping again.
What I am trying to ask is what might be the cause of this and is there anyone who can explain how to fix this issue (in simple terms) so that I'd understand?
Cheers.
Click to expand...
Click to collapse
mine is exactly the same reboots every few seconds , cant do anything about it
Have you done anything to your phone? attempt to root or install any new mods or apps or is this an out of the blue occurance?
Sent from my Nexus 7 using xda app-developers app
Ajxx16 said:
Have you done anything to your phone? attempt to root or install any new mods or apps or is this an out of the blue occurance?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Well I don't know what rooting or mods are, so I doubt it is anything like that. The only things I've really done with my phone are install apps from the play store, torrent music using utorrent and save images/pictures. I thought that maybe it was due to my phone overheating in my bag as it has been rather hot the past few days. Could that be a possible reason?
Just do a factory reset
Sent from my Nexus 5 using xda app-developers app
dia_naji said:
Just do a factory reset
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Well the thing is, I can't do a factory reset because whenever I try to access that menu that has all the options, it starts looping before I can choose anything, and for some reason the buttons dont always work
lostpigeon said:
Well the thing is, I can't do a factory reset because whenever I try to access that menu that has all the options, it starts looping before I can choose anything, and for some reason the buttons dont always work
Click to expand...
Click to collapse
since it seems you haven't done anything to your phone (ie unlocking, custom ROMs, etc), this could likely be a hardware problem.
how's the power button working? damaged?
you can also do a factory reset in bootloader, power off your phone, then hold VOLDOWN, press POWER, keep holding VOLDOWN until the bootloader appears (the white screen, with a few options), you use VOLUP and VOLDOWN to move the "cursor" and POWER to select the option you want.
nkk71 said:
since it seems you haven't done anything to your phone (ie unlocking, custom ROMs, etc), this could likely be a hardware problem.
how's the power button working? damaged?
you can also do a factory reset in bootloader, power off your phone, then hold VOLDOWN, press POWER, keep holding VOLDOWN until the bootloader appears (the white screen, with a few options), you use VOLUP and VOLDOWN to move the "cursor" and POWER to select the option you want.
Click to expand...
Click to collapse
cant do that because as lostpigeon said it loops again before we get a chance to select anything! mine has been doing it out of the blue since this morning , cant turn off or anything . . .loops and loops over and over every 13 seconds.
johntychwith said:
cant do that because as lostpigeon said it loops again before we get a chance to select anything! mine has been doing it out of the blue since this morning , cant turn off or anything . . .loops and loops over and over every 13 seconds.
Click to expand...
Click to collapse
if it's rebooting in bootloader, then it's very likely the power button that's the problem, for example: http://forum.xda-developers.com/showthread.php?t=2563572
what can you do to fix the power button? tried drying the phone although it hasnt got wet.
johntychwith said:
what can you do to fix the power button? tried drying the phone although it hasnt got wet.
Click to expand...
Click to collapse
off to warranty...
hardware problems are very hard to fix; and i'm not saying it's the power button for sure, it's just highly likely it is, if it's rebooting bootloader.
asi have no orange insurance what would you do next?
johntychwith said:
asi have no orange insurance what would you do next?
Click to expand...
Click to collapse
How long have you had the phone, defects like that should be automatically covered regardless.
Sent from my HTC One using xda app-developers app
Ajxx16 said:
How long have you had the phone, defects like that should be automatically covered regardless.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
The problem with my phone is that I found it. Turned it in and no one claimed it for a substantial amount of time so I gained ownership of it. I don't have the warranty or anything that came with the phone except for the phone itself and the charger. If I took it to a phone repair shop would they possibly be able to fix it? Or am I screwed...
Okay so I let my phone run out of battery over night and just plugged it in to charge then and it's seemed to have gotten out of the bootloop and it working normally now, so would this still possibly be a hardware issue? And is there anything I can do to prevent it from bootlooping again?
i phoned up orange and they said to ring htc as ive only had the phone for 5 months . will ring them 2moro. pain in the ass.
lostpigeon said:
Okay so I let my phone run out of battery over night and just plugged it in to charge then and it's seemed to have gotten out of the bootloop and it working normally now, so would this still possibly be a hardware issue? And is there anything I can do to prevent it from bootlooping again?
Click to expand...
Click to collapse
Im not sure this is hardware related, there are a few things you can try though to prevent this from happening again. first off, if you ever do encounter another bootloop... pressing and holding in the power button for around 20 seconds or so forces a reboot, the capacitive button on the bottom will start to blink. Second would be to boot into thee bootloader by powering down the phone, holding the volume down button and powering back on while holding voldown. this will bring you to a menu described above eariler, then do a factory reset.
Sent from my Nexus 7 using xda app-developers app