Database Develop

Stuck at padlock screen then reboots into recovery

i have a note 3 that is boots up to the unlocked padlock screen gets stuck there then boots into recovery mode. it even gets stuck in like a bsod mode where i cant see nothing or get it to respond to buttons. the only way I can is if i open it up and disconnect all ribbons(havent tried pinning pointing one yet) after i do that and reconnect them i can get the phone in download mode or recovery mode. i tried the restore with title wifi fix. to no avail. the only thing i know about this phone is supposedly it was working then they guy tried to do the update since then stuck. he said he sent it to samsung and they wouldnt fix it because it supposedly had a custom rom flashed. which im sure it had something done because of the unlock padlock/bootloader sign. any help would be greatly appreciated.

prelude91sit said:
i have a note 3 that is boots up to the unlocked padlock screen gets stuck there then boots into recovery mode. it even gets stuck in like a bsod mode where i cant see nothing or get it to respond to buttons. the only way I can is if i open it up and disconnect all ribbons(havent tried pinning pointing one yet) after i do that and reconnect them i can get the phone in download mode or recovery mode. i tried the restore with title wifi fix. to no avail. the only thing i know about this phone is supposedly it was working then they guy tried to do the update since then stuck. he said he sent it to samsung and they wouldnt fix it because it supposedly had a custom rom flashed. which im sure it had something done because of the unlock padlock/bootloader sign. any help would be greatly appreciated.
Click to expand...
Click to collapse
Dear Brother !!
This same thing happened to me!!
I looked everywhere for an easy solution BUT THERE IS NONE !! Yet.
The reason why is because there are no easy "Odin back to stock files" yet is because at&t is a fn a-hole and locked the bootloader !!
I brikt my shıt about 4 days after I brought it home from costco.
I combed through the interwebs for the 48 hrs straight like a mad tweaker!! because of course this is our 800 dollar babies we're talking about !!
I kept getting the same error message as you are mentioning about the kies update connect your pc blah and so I tool it back to costco and played dumb and said that I got a notification to update and clicked ok and it did some stuff and "now its stuck on this screen with some error??" .. the lady at the kiosk looked it up and down and said someone else had come in last week with the same error message . LoL !!
I walked out of there with a brand new baby !!
Maybe you can do the same thing? Just hoping you are within your return timeframe.
your last but definitely not last worst case scenerio option is to stick your sim card in another phone and wait till someone from our awesome family here finds away around/through that damn bootloader and drops the beautiful Odin+files to give new birth to your 5.7 beast of an angel !!
Hope this helped in any sort of way. Good luck dear Brother!!
Please let us know how it goes. I think there are many brothers on here in the same predicament.

[Q] AT&T Random Reboot - Solution?

I was unfortunate enough to get one of the first batch of preorder Nexus 6's on AT&T with the random reboot issue. Has anyone found a solution for this yet? Flashing the stock factory image from Google does not work. Exchanging is not an option as of now because no AT&T store in my area has any in stock. Any help would be appreciated.

Mine was rebooting at least once a day. I noticed that it happened a couple times as I was lifting the phone, when ambient display would normally turn on, so I turned ambient display off. It's been almost two days now with no restarts. Give it a try and let me know if it works for you.

Noticed my Motorola.com unit doing this over the past few days. Really strange, but haven't found a solution to it either.

Motorola.com order
SuperTongue said:
Noticed my Motorola.com unit doing this over the past few days. Really strange, but haven't found a solution to it either.
Click to expand...
Click to collapse
I am having the exact same issue and i purchased from Motorola.com as well. Check my phone and the screen is blank and i have to power off my phone to get it to come back to life. Not sure what the issue is but it is frustrating.

Haven't had a reboot at all, using T-Mobile N6.
Upload a last_kmsg after your "random reboot" in /proc/

OP,
Are you saying you flashed the factory image and it didn't fix the issue or you were unable to flash the factory image successfully?

At&t recalling Nexus 6
jpurv said:
I was unfortunate enough to get one of the first batch of preorder Nexus 6's on AT&T with the random reboot issue. Has anyone found a solution for this yet? Flashing the stock factory image from Google does not work. Exchanging is not an option as of now because no AT&T store in my area has any in stock. Any help would be appreciated.
Click to expand...
Click to collapse
You might have already seen this article.
http://androidcommunity.com/software-bug-forces-att-to-recall-send-back-nexus-6-inventory-20141123/
Im getting the same thing with my phone but I received it direct from Motorola. Not sure what is going on here. Hoping for a software fix.

bsteiner36 said:
You might have already seen this article.
http://androidcommunity.com/software-bug-forces-att-to-recall-send-back-nexus-6-inventory-20141123/
Im getting the same thing with my phone but I received it direct from Motorola. Not sure what is going on here. Hoping for a software fix.
Click to expand...
Click to collapse
Same here. Motorola direct device. AT&T SIM, freeze up on a black screen once every 24-hours only when NOT on WiFI for extended periods.

jwiskowski said:
Same here. Motorola direct device. AT&T SIM, freeze up on a black screen once every 24-hours only when NOT on WiFI for extended periods.
Click to expand...
Click to collapse
I am not sure if the WIFI has anything to do with it but i will keep track of when my phone reboots. Most of the time it was in my pocket and i went to check it and the screen was off and had to hold down the power button to turn it off and back on. If it happens again in going to try to call/text myself or use android device manager to see if it actually is ON but the screen is blank or if it is actually turned off completely.

Is this issue present also in the playstore's devices?

Just got home from my second trip to the AT&T store today. They told me they wanted me to return the phone and that they have no ETA on when they will be receiving the fixed batch. If I wait until after the 14 day return period the phone they will exchange me for will be refurbished.
My options are:
1. Keep the phone
2. Return the phone and go back to my old one
3. Exchange it when they have the "fixed" batch for a refurb
Great...

jwiskowski said:
Same here. Motorola direct device. AT&T SIM, freeze up on a black screen once every 24-hours only when NOT on WiFI for extended periods.
Click to expand...
Click to collapse
I just noticed yesterday by phone rebooted after leaving work and driving home. It was off wifi the whole time and when i got home the screen was blank. Couldn't turn it on without holding down the power button. I have a form in the Motorola forms about the same issue. I'll post if i get a resolve.

Shoot. Got a fully paid for AT&T Nexus 6 delivered last Friday (tried every Wed on Play Store and gave up). The ringtones, startup sound and subtle branding dont really bother me. The tether restrictions dont affect me on a shared data plan. But, it's randomly rebooted two consecutive nights while sitting next to me on couch. I suspect ambient display because it was right at time for medicine reminder app notification. Unacceptable. I guess if it continues I'll take it back after Thanksgiving and use Nexus 5 until AT&T can get some stock to replace it. Assuming it's an AT&T only hardware problem, which doesnt actually seem likely. Otherwise, maybe AT&T / Motorola can push Google to do a software fix.

I have this problem too. I have an unrooted ATT nexus 6. Last night i did a factory reset and turned off ambient display. I have a feeling ambient display may be to blame for these random reboots but who knows

Mine plays the ATT jingle when it freezes up. The screen goes black and have to hold the power button down to get it back up. Happened once at work (no wifi) and once at home (on wifi).
I hope they push an update soon.

Don't hold your breath for the update. If flashing a stock image doesn't fix it the problem is probably deeper than that. You have 14 days from the day you received it to get a new replacement.

RandomHandle said:
Don't hold your breath for the update. If flashing a stock image doesn't fix it the problem is probably deeper than that. You have 14 days from the day you received it to get a new replacement.
Click to expand...
Click to collapse
or 14 days from ship date if you ordered it online/over the phone

joelthebassplayer said:
Mine plays the ATT jingle when it freezes up. The screen goes black and have to hold the power button down to get it back up. Happened once at work (no wifi) and once at home (on wifi).
I hope they push an update soon.
Click to expand...
Click to collapse
This is EXACTLY what happens to me.

No if you ordered it its 14 days from the day you received the phone.

mouse100 said:
Is this issue present also in the playstore's devices?
Click to expand...
Click to collapse
In my experience, yes. I purchased a 32gb Blue model from the play store, running it with a brand new AT&T sim and in the week I've had it its randomly rebooted three times that I've noticed. Hopefully its an issue with a single batch, I'm RMAing this device for other reasons (uneven display color) and hopefully the new one won't have these issues.

[Q] Hard brick after 5.01 OTA just out of the box

i just got my Nexus 6 today. Ran through the setup without restoring anything from my M8 (used Setup as New device option). Got to the home screen, looked up my WiFi MAC address and added it to my router. In the meantime over LTE I received my Gmail mail and a notice to update to 5.01. Downloaded the OTA, hit the "Reboot & Install" button, watched it reboot and start the install. Didn't bother watching the process and when I looked back it was a black screen. Thought it timed out after a (possible) reboot so went to wake it and nothing. Will not power on or boot into fastboot and plugging it into the charger produces nothing on the screen.
Ordered it direct from Google Play so called their support, explained all I had done and after an hour of being put on and off hold I got disconnected. Tried calling back and after the prompts, the line drops. Guessing it was quitting time. The tech (if you can call him that) said he's got the 5.02 notice sitting on his N6 but from what he's heard, he's sticking with 5.01 for now as he has no issues.
I wanted to give you the full convo even though most of it's useless.
Oh, as far as the tech goes, he wanted to resolve it in one call and tried talking to Motorola but said his call was dropped and after trying to call back he got an After Hours message. Before that he wanted to send me a shipping label for me to send it back but wouldn't send a replacement until they got it back. He was going to talk to his supervisor about sending one out overnight... That's when the call dropped. I was very polite but after waiting since October and checking everyday, now I'm pissed.
Thoughts?
TIA

These phones dont get shipped out fully charged.
What was your battery level? If it was upgrading and it loss power due to lack of it, congratulations for bricking yourself.
You should always charge up a device like a cell phone before flashing.
Can you charge it up now? Give it some juice and see if you can at least get into the bootloader.

It was at 51%. No activity when plugged into the charger as I said in my OP.

xwera43 said:
It was at 51%. No activity when plugged into the charger as I said in my OP.
Click to expand...
Click to collapse
Man sorry to hear. I didnt even take the update. the day I recieved my device I unlocked the bootloader, flashed custom recovery and then cm12 nightly

I have a new replacement coming. Thanks for the input.
X

Yes, if you got it through Play ONLY deal with Play, Motorola is the WORST. I really never want to deal with their support again.

Nexus 6 (rooted, stock rom) won't turn on anymore. Please help

Hello everyone,
I'm experiencing a pretty tough issue mith my beloved (and, so far, flawless) Nexus 6. It had root and a stock rom on it, 6.0.1 (MMB29V). I had unlocked the bootloader and rooted the phone right after buying it more than a year ago and I've been flashing new factory images a couple times (specifically when 6.0.0 and 6.0.1 were released). I usually do everything via Wugfresh's NRT, not because I can't use adb and fastboot, just because it works fine and I'm lazy.
Yesterday, while I was working, I used "Tiny Scanner Pro" to scan a document (legit copy bought on the store, as any other premium app in my phone) and it got stuck for a while, then a popup about Google Play Services came up. I dismissed it and another appeared, and it kept going like that. I was at a client's and I was in a hurry, so I took the pic with my tablet and forced the phone off. Later I turned it on, it seemed to boot regularly, but when the SIM unlock screen appeared and I entered the (right!) PIN, it said that no SIM was found, then the home screen appeared but after a while the screen went black and it started rebooting. Recovery (TWRP) and fastboot were working, so I decided to take it home and re-flash the stock rom: it had been a while since the last time anyway, a new version was out and the OTA update notification was getting annoying. I connected to my PC in recovery mode and transfered my pics and data via adb while I downloaded the latest stock rom (6.0.1 MOB30D). Then I user NRT to flash it (selecting "Soft-bricked/Bootloop" as current status). It appeared to work fine as it went through the usual copying and unpacking. Then, when the phone was supposed to reboot, it just blacked out. I waited a long time, in fact I went out and came back a few hours later, and it was still that way. Now it doesn't power up, no matter how long or hard I press any combination of the three buttons, adb and fastboot do not detect it in any way, of course, and it doesn't seem to charge either (i.e. I left it plugged to its original charger overnight and it still feels dead cold). By the way, the phone warranty shouldn't have expired, but I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
I've taken a look at similar threads but none of them describes the very same situation. Is there something, anything I can try to do before giving up? I hope somebody can help me. I thank you all very much in advance.
lupus

lupusyon said:
.... I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
Click to expand...
Click to collapse
Bricked!. When the phone is still under warranty send it for repair. Do not use arguments.
Just: phone will not switch on and does not charge.

Because this is a Nexus device, the custom recovery shouldn't affect your warranty. It is however, a moot point. The device is totally dead, and a call to Motorola is in order.

lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...

dahawthorne said:
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
Click to expand...
Click to collapse
I bought it on Amazon Italy Marketplace, I'm not sure if they're supposed to handle the thing or if I should contact Motorola. I'll just check with them first. Thank you everybody for the kind advice, I'll let you know how this turns out. :good:

I confirm what dahawthorne wrote above: it took them about a month but Motorola repaired my Nexus under warranty, no questions asked. It seems they replaced the Mainboard PCB.
Thanks everybody!

Eight days in, and a replacement phone.

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.