8 days ago, I decided my s5 had had enough abuse, and got the z force. It's been an amazing phone, other than the heat, which has always seemed a little warm, but didn't do anything to slow the phone down. Up until today, it's been glitch free, and I loved it.
Until about six hours ago. I wasn't paying attention to the battery, it died in the middle of watching YouTube videos with my kids, so I let it finish powering down, plugged it in, and let it charge. Upon turning the phone back on, I got an error message saying the device failed validation and may not work properly. Five second delay and it powered on, and everything seemed to function normally. Rebooted the device, same screen. Factory reset the device, same screen. I took the phone back to Best Buy and got a replacement, and I'm hoping it doesn't happen again, I really happen to like this phone...but I'm curious. Moto's customer support's first question was if I'd unlocked the bootloader or rooted the device, but being verizon-locked, I'm well aware that isn't possible and haven't attempted it. Anyone have any ideas why my phone just randomly decided to fail the bootloader verification so I can try to avoid replicating this mess?
I'd like to know as well. I have the same message every time it boots but it doesn't seem to affect anything I've noticed so far.
Mace68 said:
I'd like to know as well. I have the same message every time it boots but it doesn't seem to affect anything I've noticed so far.
Click to expand...
Click to collapse
If you boot into the bootloader does it say if your device is locked or unlocked?
BladeRunner said:
If you boot into the bootloader does it say if your device is locked or unlocked?
Click to expand...
Click to collapse
No such luck lol. It says "oem_locked" and software status is "Official".
Sent from my XT1650 using XDA-Developers mobile app
I wanted to add that a factory reset didn't clear the message.
I also wonder if it has to do with turning on allow bootloader unlock in dev options. It seemed to have happened at about the same time I turned it on.
Mace68 said:
I wanted to add that a factory reset didn't clear the message.
I also wonder if it has to do with turning on allow bootloader unlock in dev options. It seemed to have happened at about the same time I turned it on.
Click to expand...
Click to collapse
Factory reset didn't fix mine, either. And as far as turning on the bootloader unlock option...I hadn't even enabled dev options on mine, so I'd assume that's just a coincidence on yours.
Related
Hello,
Tried to look up some answers to my problem, however I'm not sure exactly what is wrong which makes any troubleshooting rather difficult.
I bought a new ADP1 a few months ago. I haven't had much time to play around with the phone, have just been using it stock and haven't even added any applications. There has been no physical damage to this phone, no drops etc.
Yesterday the phone locked up when I was using the browser and would not function. When I would try and reboot it, it would lock up at the first android screen and would fail to start up. I ended up doing a hard reset to factory defaults and the phone finally booted. After setting everything up again the phone seemed to be working fine.
A few hours later it locked up again while using the browser. This time no reboot/safe mode/factory reset would get it to boot. I can't even get to recovery mode or even get the phone to attempt to boot up. The screen remains black and the phone will not power on. It won't even charge when I plug it into the charger.
Not sure how to proceed here and I can't seem to find any information in regards to RMA, it is still in warranty.
Any help would be greatly appreciated.
Take out the battery for hour or so put it back in and try again.. but this sounds like my issue What happen to Me is my mobo was crapping out and eventually just died on me
Sent from my Nexus One using XDA App
Yeah, the mobo going to **** was my original thought.
I already tried taking out the battery last night for about 3 hours, it still didn't work.
Guess I'm going to have to look into an RMA, I hear they are a pain in the ass. The phone is still within it's 1 year.
Yea I would get that done quick
Sent from my Nexus One
Okay, I have been having a serious issue with my D3 lately. One time, my phone just randomly rebooted, and then it would get stuck at the red "Droid Eye" screen, where it would be laggy and such after a while. Eventually the screen would time out in like 2 minutes. After it turned off, I could not get it to turn back on. Basically dead, except I could still get notifications and even a phone call. But I could not act on any of them. it's like the phone's heart is still beating, but I can't turn the screen on. I pull the battery and reboot and it does it again. SOMETIMES if I keep touching the red eye screen I can get to get to the lock screen, but the wallpaper won't load and it's basically frozen. I even tried booting into safe mode and that didn't help. I took it to Verizon, they said they've a couple other people with a similar issue on the forums. They did a factory reset, and that has been the only solution to the issue. I have had it 3 times now, and this time I'm sticking with the Blur launcher and keeping only the essential apps installed. I'm assuming this is a software issue, and I'm currently trying to figure out if it is related to a certain app that was installed. Hoping they will fix this with an update! ANYBODY ELSE HAVING THIS ISSUE? if so, any leads on another fix or what it could be?
sounds like a software issue. a factory reset doesn't do anything other than change the software.
I had a similar issue on my droid 1. it was rooted and when I installed a gingerbread from I forgot who, it got stuck at the eye, kept rebooting, and occasionally, i'd get calls and it still wouldn't work. I look forward to root.
out of curiousity, did you have to take it to the store to factory reset or is there an option for it in the bootloader(I know its locked but I have no idea to what degree)
The first time I took it to the store they did it for me, but yeah there's an option in the bootloader. Just took my back to Verizon cuz this was the 4th time it's done it, they're sending me a new one! It's okay, cuz my nice screen open 'click' sound was gone on the keyboard lol
Hi all,
I was wondering if anyone is able to help me out with my HTC one M7. My phone has been out of commission since Monday night and I'm all out of options on what to do, I've even tried doing a factory reset as a last resort but that didn't seem to work as it looked like the process just stalled.
Here's a bit of background of what happened: Monday night I charged my phone through the wall outlet and went to have dinner, I came back to check on the phone and it was off. I thought that was odd so when I tried turning it back on I would only ever be able to get to the white HTC logo screen. I'm able to get into fastboot and recovery but after googling solutions and trying the options people have mentioned, it still isn't working. I'm not very tech oriented so I wouldn't know how to flash ROMs or anything like that...soooo, I'm hoping someone is able to explain steps in I'm able to understandr. I don't even know flashing ROMs is possible at this point since whenever I plug it into my PC, the drivers aren't recognized by Windows and says 'failed to install drivers'.
Any help is very much appreciated!! (I signed up to the forum in order to write this and seek help lol)
I haven't done ANY customization to the phone everything is all stock from my service provider so I'm really baffled at how this sudden fail could have happened. There was no OTA update either.
rina__anir said:
Hi all,
I was wondering if anyone is able to help me out with my HTC one M7. My phone has been out of commission since Monday night and I'm all out of options on what to do, I've even tried doing a factory reset as a last resort but that didn't seem to work as it looked like the process just stalled.
Here's a bit of background of what happened: Monday night I charged my phone through the wall outlet and went to have dinner, I came back to check on the phone and it was off. I thought that was odd so when I tried turning it back on I would only ever be able to get to the white HTC logo screen. I'm able to get into fastboot and recovery but after googling solutions and trying the options people have mentioned, it still isn't working. I'm not very tech oriented so I wouldn't know how to flash ROMs or anything like that...soooo, I'm hoping someone is able to explain steps in I'm able to understandr. I don't even know flashing ROMs is possible at this point since whenever I plug it into my PC, the drivers aren't recognized by Windows and says 'failed to install drivers'.
Any help is very much appreciated!! (I signed up to the forum in order to write this and seek help lol)
I haven't done ANY customization to the phone everything is all stock from my service provider so I'm really baffled at how this sudden fail could have happened. There was no OTA update either.
Click to expand...
Click to collapse
If your warranty is still valid take it to service
donkeykong1 said:
If your warranty is still valid take it to service
Click to expand...
Click to collapse
Unfortunately it's not, I've had the phone for a little over 2 years now. Seriously contemplating just using a loaner phone in the meantime while I wait for the new Nexus ...
rina__anir said:
Unfortunately it's not, I've had the phone for a little over 2 years now. Seriously contemplating just using a loaner phone in the meantime while I wait for the new Nexus ...
Click to expand...
Click to collapse
Did you try factory reset from bootloader?
donkeykong1 said:
Did you try factory reset from bootloader?
Click to expand...
Click to collapse
Yes, I did. It flashed to the screen with 2 green arrows in a circle and 1 downward green arrow with a progress bar at the bottom but nothing happens during this period. I left the phone like that for about 30 mins just to see if anything would happen and nothing did.
So, I've been running the N Preview since just after finding out that there was a beta program to join, about 5 days ago, give or take. 2 days ago, my phone's wifi started acting up. I put it down to go to sleep and it was fine, and I woke up the next morning and found out it was constantly disconnecting, shutting off on it's own after I just turned it on, and the wifi hotspot list was glitching out, flickering, and connecting/disconnecting rapidly to my home network. About an hour ago, I decided that I had had enough of it disconnecting while I was streaming content (for whatever reason, my house is just out of range of the T-Mobile LTE cell tower for this area, or I'd be streaming it from that and not worrying about the wifi), and made the decision to do a factory reset to see if it would fix the glitching. It seems now that that was a mistake, as it's been stuck on the Erasing screen for about an hour. Not sure what to do at this point. Any advice and help would be greatly appreciated at this point.
[Disclaimer: I am fully aware that this software is still in beta, and that things will be broken and/or not working, and that it was not recommended to install on daily driver devices. However, what's done is done, and I'd like to have my phone working again. So please refrain from scolding/harassing me about any of this.]
What do you mean by 'stuck on the erasing screen'?
Slender Troll said:
So, I've been running the N Preview since just after finding out that there was a beta program to join, about 5 days ago, give or take. 2 days ago, my phone's wifi started acting up. I put it down to go to sleep and it was fine, and I woke up the next morning and found out it was constantly disconnecting, shutting off on it's own after I just turned it on, and the wifi hotspot list was glitching out, flickering, and connecting/disconnecting rapidly to my home network. About an hour ago, I decided that I had had enough of it disconnecting while I was streaming content (for whatever reason, my house is just out of range of the T-Mobile LTE cell tower for this area, or I'd be streaming it from that and not worrying about the wifi), and made the decision to do a factory reset to see if it would fix the glitching. It seems now that that was a mistake, as it's been stuck on the Erasing screen for about an hour. Not sure what to do at this point. Any advice and help would be greatly appreciated at this point.
[Disclaimer: I am fully aware that this software is still in beta, and that things will be broken and/or not working, and that it was not recommended to install on daily driver devices. However, what's done is done, and I'd like to have my phone working again. So please refrain from scolding/harassing me about any of this.]
Click to expand...
Click to collapse
Is your bootloader unlocked? If it is, just reflash the latest M image.
chapelfreak said:
Is your bootloader unlocked? If it is, just reflash the latest M image.
Click to expand...
Click to collapse
Or un-enroll from the android beta programm and the latest public stock firmware will be installed by OTA if the bootloader is locked.
gee2012 said:
Or un-enroll from the android beta programm and the latest public stock firmware will be installed by OTA if the bootloader is locked.
Click to expand...
Click to collapse
True, but I've read some people not getting the ota after unenrolling. I'd rather just do it myself since the first thing I did was unlock the bootloader lol either way the phone is going to get wiped. I hope the OP phone doesn't get borked because it hung up on factory erasing the phone, and his bootloader is locked
chapelfreak said:
True, but I've read some people not getting the ota after unenrolling. I'd rather just do it myself since the first thing I did was unlock the bootloader lol either way the phone is going to get wiped. I hope the OP phone doesn't get borked because it hung up on factory erasing the phone, and his bootloader is locked
Click to expand...
Click to collapse
Aah oke, got my rollback OTA last week in a minute or so
Ok, so just woke up and it seems to have shut off. Turning the device on now...
And it seems to have successfully reset. It's currently on the setup screen, and I'm going through it now.
And for the moment, the wifi seems to have been fixed, at least for now. Not sure if the device is on N or Marshmallow though, but we'll see.
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)
aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)
Click to expand...
Click to collapse
I would try flashing the latest factory image via fastboot.
[Guide] Root Pixel 4 XL with Magisk Android 13
[Guide] Root Pixel 4 XL With Magisk Android 13 Android Security Bulletin—Feburary 2023 Pixel Update Bulletin—Feburary 2023 Introduction This Guide is for Pixel 4 XL owners that want to Root their phone, and enjoy the benefits of rooting it. The...
forum.xda-developers.com
https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/ (This is for a Pixel 2 XL but the process is the same. It's basically a condensed version of the one above.)
aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Click to expand...
Click to collapse
You did not provide the most important information we need- whether your phone is bootloader unlocked. Probably not, otherwise you would have already flashed it with a full Google image, which returns the phone to "out of the box" condition. You need to determine whether you can unlock your bootloader. If you cannot unlock (allow oem unlock is off and or greyed out in Dev options) then you will not be able to fastboot flash ANYTHING. If that is your case, the next best thing is flashing a full OTA image (sometimes called a rescue OTA) from recovery mode using the OTA via ADB option. This means you need fastboot/adb installed and working on your PC. Instructions on how are on the same Google dev page for OTA's.
So, my phone's bootloader is not unlocked. But I have an update for the crowd that may one day find this. I know your frustration and I can report that my phone is once again fixed.
A day (or two) after I sent this, a set of updates came down to my phone. And WebView was updated. That restored all of my sensors and also restored most of my crashing applications. It was an incredibly odd experience.
My phone once again functions. And the nightmare of owning a Google phone and talking to Google support has ended.