The 72 hour lock out thing is one of the dumbest thing's Google has ever done. So I got a Nexus 6 since launch. figured i'd try getting 6.0 on there since i'm on Verizon and and OTAs from them take forever. So after much messing around and a few failed attempts I get 6.0 to boot on my Nexus 6, happy days right? Well I get this message when signing in for the first time "This device has been reset please login". So I did and after password I get "please sign in using owners accounts of the owners of this device". So after google I fond out this is some sort of security lockout that has no way to defeat it once triggered because I reset my password. I did this Sunday at 8am. Well I got a little restless about it yesterday and following someone else advice I tired to flash to 5.0, in theory since it doesn't have the password lock out i'd be able to sign in, get the OTA update to 5.1 then install 6.0 without resetting user data and be in. Thing is 5.0 wouldn't boot on my phone. I'd get stuck at the boot animation. I figured because my phone being a Verizon phone never got 5.0. So I installed 6.0 again and stupid me flashed user data again. This was yesterday around 5PM. Figured I was done with it and let it be. Well today when I woke up I figured the lockout should be over but I'm still getting that same message when logging in. Did I trip the freaking 72hr lockout again? So I'm not gonna have my phone till Friday 5PM? ARE YOU KIDDING ME? I DO NOT HAVE MY PHONE FOR ANOTHER 72HRs?!?!?! This really makes me want to smash the phone with a hammer and get Asurion to send me a refurb replacement.
Related
Hey guys,
Thinking of rooting so naturally go to reset my google wallet. I hit the reset button and it gets to 99% and literally hangs. I let it sit for 20 minutes the first time before I hit the home button because I thought it froze, tried again and probably waited another 15 minutes and that's now. How long does this take? I tried connected to wifi and also just 3G. Any advice?
Update: Now when I try to open the app it hangs at "Initializing your Device". Awesome =D
Wallet has been down for a day.....
Sent from my EVO using xda premium
Weird, I used it at about 4pm today. No problem. Thanks for the info.
Well its been down for anyone who reset their device at least for the last 24 hrs from my understanding
Sent from my EVO using xda premium
Get_Out_and_Push said:
I hit the reset button and it gets to 99% and literally hangs. I let it sit for 20 minutes the first time before I hit the home button because I thought it froze, tried again and probably waited another 15 minutes and that's now. How long does this take? I tried connected to wifi and also just 3G. Any advice?
Update: Now when I try to open the app it hangs at "Initializing your Device". Awesome =D
Click to expand...
Click to collapse
I do believe you've bricked your nfc. I had a very similar experience. Hit reset, it counted up to 99% VERY slowly, then sat there. I let it do its thing, then came back 10-15 min later, screen was off, turned on, saw nothing, so assumed it cleared successfully. After rebooting, went back into the app to get a secure element not responding message. I'm not sure if the reboot did it in, or the it was already done for when stuck at 99%.
In either case, I exchanged the phone. On the new one, the entire reset process takes about 15 seconds to complete.
Go ahead and add me to the list. I went to clear out G Wallet before unlocking my Evo and it got hung up at 99% then crashed and said Google Wallet failed and now I am stuck with the "Initializing your device" screen which it gets hung up on.
Took it to a Sprint store and no one their had ever seen this before and didn't believe a word a was saying went ahead and factory reset the device and said "here it should work now". So I showed them it didn't fix anything and she said sorry we cannot issue a new phone for 1 malfunctioning app. Anyone have any recommendations on what to do next?
hshshawn said:
Go ahead and add me to the list. I went to clear out G Wallet before unlocking my Evo and it got hung up at 99% then crashed and said Google Wallet failed and now I am stuck with the "Initializing your device" screen which it gets hung up on.
Took it to a Sprint store and no one their had ever seen this before and didn't believe a word a was saying went ahead and factory reset the device and said "here it should work now". So I showed them it didn't fix anything and she said sorry we cannot issue a new phone for 1 malfunctioning app. Anyone have any recommendations on what to do next?
Click to expand...
Click to collapse
Check out this thread http://forum.xda-developers.com/showthread.php?t=1690840 in the general forum. There are a whole bunch of us with this exact issue. No resolve yet, but together we can trouble shoot it.
Hey! I had this same problem on my tmobile galaxy s4 where I didn't get an error message but it just took forever for google wallet to reset. I discovered a possible fix for the problem. I redid the build.prop file, changing the file to show the phone is a galaxy nexus. Like,
ro.product.device=maguro
ro.product.model=Galaxy Nexus
ro.product.name=yakju
I then restarted my phone and tried to reset wallet again and it reset in a few seconds. Maybe wallet needs the device model to match up with the one that was registered on the Google wallet account in order for it to work.
Please forgive me for the long arse post, details are sometimes a good thing. At this point Im positive I have techherpes. I got a bad Modem last week and on the same day this. Last week I got the test letting me know ICS was available for my note so I followed all directions and downloaded Kies, after 4 attempts finally got a good DL. During the ICS update I got an error and was prompted to use the recovery feature. No dice on recovery so I took the phone to the ATT service center and they set up a return. I got my new phone on Friday and call Sumsung support to get a walk through. The tech said it would be advisable to wait until today before trying the upgrade which I did. I tried it again and the end result was the same as the first. I don't consider myself a technology dullard, hell its what I do for a living but I'm obviously doing something wrong?
At this point I still have the original phone in the return box waiting to be shipped and another phone showing:
ODIN MODE
PRODUCT NAME: SGH-i717
CUSTOMER BINARY DOWNLOAD: NO
CURRENT BINARY SAMSUNG OFFICIAL
Below that is a pic of a phone, yield sign, pc
Firmware upgrade encountered and issue. Please select the recovery mode in Kies and try again.
I spoke with another Samsung tech tonight who tried to walk me through a factory reset, vol up+down+power which brings me back to the same screen above briefly flashing the Samsung logo. She went ahead and setup a RMA and told me that it would be 5-7 days plus shipping. I said hell I'm in Austin can I drive up and have you fix it I can do the vol down+power buttons which will take me to the screen letting me know a custom OS will cause critical problems bla bla blah and when I press the up vol button I go back to the ODIN MODE screen.
Should I simply take it back to the ATT service center again, not sure they will be so accommodating since I have been down this road once already. Ive only had the original phone for just over a month and I have the insurance plan through them. All data was backed up before both attempts.
Maybe you got a bad Kies download. It's my impression it's a little squirrely, from my own experience and reading of others'. Why don't you remove and reinstall it. It seems unlikely that you got 2 bad brand new phones.
That is very possible. I had to DL it 4 times before I finally got a DL that would complete. Ill go that route and see what I can do. Does the current status of the phone mean that its bricked?
Thanks,
Chris
I don't know much about that, but I think it would be pretty bad to be able to brick a phone that easily following manufacturer's directions. In Kies there is an option for something like an emergency firmware fix, in case you need to try that. But I'd go the normal route first. I had some trouble with mine when I did the download, and had to try more than once. The download took forever, and I understand the servers were swamped when AT&T put out the notice. Also had to disconnect the phone and try more than once, but in the end everything was fine. Good luck.
kat3k said:
I don't know much about that, but I think it would be pretty bad to be able to brick a phone that easily following manufacturer's directions. In Kies there is an option for something like an emergency firmware fix, in case you need to try that. But I'd go the normal route first. I had some trouble with mine when I did the download, and had to try more than once. The download took forever, and I understand the servers were swamped when AT&T put out the notice. Also had to disconnect the phone and try more than once, but in the end everything was fine. Good luck.
Click to expand...
Click to collapse
Yep, I tried the night I got the text and the first DL took 45 minutes with a 30mb connection. When I tried the installer it failed so I wiped it and tried again. After 4 similar attempts all taking the same amount of time to DL I finally got one that launched. The result was where Im at now with the first phone. Fortunately ATT had me one the next day and I was able to restore. I called Samsung support and the tech told me to wait until Sunday or Monday before I tried it again since Kies would be going down Sat night.
I wiped Kies and installed it this am, 3 minutes to DL and it launched the hotfix. It seems to have gone through several more steps this time so I think I know where the issue was, or at least I wont blame myself 100% for now. When I removed Kies it appears to have also removed my backups? I did another backup using two other software options just to be safe.
When I connected the phone after the new install Kies wont connect to it. I previously tried the emergency recovery since the phone directed me to go this route with no success. Im off to the ATT service center in a few and Ill see if they will go the extra mile again.
Kies wouldn't connect to my phone either at time of update, so I ended up going through the Emergency Firmware Recovery which worked. Then I had to restore my backup. I'd try that again if I were you.
Refs. rehistr
Took the phone into the ATT service center today and as soon as they looked at me they said ICS failed? They told me that their entire day had been spent on skyrockets and notes. They weren't able to correct mine so they are sending me another. I wont be attempting the update on this one for awhile. It would be nice if the replacements came with ICS so that I didn't have to worry about it. I tried the emergency firmware update which would get to 27% and also fail.
just root your phone, no more worries about bricking
Hello:
So, the bottom line up front is I need help solving a problem with my now third, new Verizon Samsung Galaxy S4--it keeps restarting on its own, at random times, but most often after I lock the screen.
To go in more depth, if you think you may know the solution: I purchased the S4 when it first came out, some time in 2013 (not sure specifically, but it was new) and it worked just fine for 13 months (1 month past the warranty of course); this was back in August, when I got the latest Android update pushed to my phone from Verizon (4.4.2). A couple of weeks later, I would occasionally get overheating warnings that would very quickly disappear (like within a few seconds), and then the device started restarting itself... I cannot predict when it will restart, it's random, but like I said above, it usually happens most right after I lock the screen by pressing the right side button once. I started looking around on the internet for a solution then, but only found a couple of videos from earlier in 2013 where people were having battery problems (Google search has been letting me down more and more as the years pass). One day while at work, I was listening to Pandora as I always have with the phone in my front pocket, as I always have. A few hours later when I got home, not having taken the phone out of my front pocket since those last few hours at work, I went to answer a text message I had received; when I unlocked the phone, the screen was black, except for a small bit of white showing through some cracks UNDER the LCD, UNDER the screen protector, INSIDE my Otterbox Defender... the phone appeared to be working still, but the screen and touch screen did not. At that point I was pretty damn irritated and tried to find answers for a week with no luck... I called Verizon, they sent me on a goose chase to Samsung, who sent me back to Verizon, who got me in a conference call with Samsung and then left the call, and then Samsung ultimately said I would need to pay for repairs to the phone... SO... I went back to Verizon who again said I would have to talk to Samsung, but instead I just settled to giving Asurion (my phone insurance through Verizon, whom I pay an extra $9 monthly) $99 as a deductible to get a replacement S4...
Two days later I receive a brand new S4... spend hours setting it up the way I had my prior one... wasting tons of my valueable time to do so and bandwidth from my Concast ISP and the data cap they've decided to give us... one week later, the phone starts restarting itself... and this one did it more often than my prior one... EVERYTHING is up to date, minus a good amount of useless bloatware apps I never use from Samsung, like "Watch On," which I ignore... but everything necessary, I update. So, I go back to Asurion, who quickly ships me a 3rd S4...
Two days later I receive that third, brand new S4... spend hours setting it up the way I had my prior one... and now, this one is also restarting itself randomly. Interestingly, when I visited family for Thanksgiving, it restarted itself over and over and over much more frequently than when I'm at my place... at my family's place, they have very poor reception, and my phone usually has to work more to try to get the signal... IDK what the deal is, but maybe that information can be helpful to y'all.
Other things to note:
1) When I check the "RAM manager" by holding down the home button and then choosing "Task Manager", the phone is always using at least 800MB of 1.77GB of RAM... even when I choose "Clear memory" and it tells me 30 something apps have been closed... it jumps right back up to 800-900MB of usage.
2) I've tried factory resets on all three phones; with the first one where the screen cracked inside, I hooked the phone up via HDMI... within a couple of days, the restarting begins.
3) With the first replacement I received, I could not sent text messages with the default messenger app... and shortly after trying, it would restart.
4) I have used the same SIM card with all three phones since the issue began, when I first got the 4.2.2 update... I do not suspect the SIM card is the problem, but I'm also not savy with the phone... I know my way around it, but I'm not in the know.
5) I thought maybe it started because of some apps I had been trying, so I had deleted them, and the problem still persists.
6) I constantly have a Pebble Bluetooth smart watch connected to the phone... I have since I got it last Spring (2014).
7) I have never rooted the S4, overclocked it, underclocked it, or modded it in anyway because I do not know how, and I was afraid of what could happen in the future with whatever ROM I did flash onto the device if Verizon tried to push an update to it... I just don't know anything about the whole process, and I'm assuming it requires a lot of know how and babysitting of the device... I just want it to work.
8) I've replaced the battery twice; it doesn't seem to be the problem.
9) I've cleared the cache through the boot manager thing gotten to by holding a combo of buttons on the device while it's rebooting... it did not help.
Edit: 10) Today while I was listening to Pandora in the car, the audio began to skip and scratch, and then it paused for a moment, and then the phone restarted itself.
11) I forgot to mention that the reboot process itself is very fast compared to a manual restart performed by me... the phone will go black, the Samsung color rings will show a second after that, the logo appears then, the screen flashes the red Verizon logo, and then the devices is ready to be used... it's less than 10 seconds.
I've been searching around on the internet for about two months now while dealing with the problem and I can't find anything useful. Does anyone here know what my issue is and how I can fix it? Is there a way to pull error logs / information from the S4 somehow to give to someone to diagnose, like DxDiags on PC? I don't know how to read that stuff myself, but I know it can be very useful... I just don't know how to find that info inside of these very locked down ****boxes we call smartphones...
I truly appreciate any help I can get--sorry I can't offer anything in return; if I can't find a solution, I'm just going to go to my backup phone from 2011 (Droid X), and I will definitely never purchase another Samsung device, especially after they blamed me as the cause of the problem without even seeing the phone...
Thanks.
The problem is with the NG6 software build, and "probably" not with your phone. Go to Settings>About Phone> and see what Baseband Version is on your phone. If the last 3 letters are NG6, that's probably the problem. There is a new OTA update (as of 12/1).....Baseband Version ending in NK1, which corrects the rebooting problem. Either install the new update, or go back to the NC5 baseband version and that should solve your problem. Both NK1 and NC5 can be rooted if you desire.
Hey there guys!
So I just recently downloaded and installed the OTA android 6.0 update and now my Nexus 9 does nothing but loop on the google boot animation. I have wiped the cache and have done a factory reset, but because my boot loader is still locked I can't think of any other options.
Any Ideas?
The exact same thing happened to me.
I guess I'm taking it back to the store I got it from. I hope they play nice and offer a quick solution and not an endless send-in-and-wait-for-ages one.
Good luck!
it's dead. same thing happened to my 100% stock 32gb Nexus 9 (sand).
if you didn't Enable Developer Options previously there is no way to unlock the bootloader or sideload the update. I talked to Google Support last night. They escalated my issue....whatever that means. Currently waiting 24-48 hours for them to contact me. ugh
Mine is on the way to HTC... hope this doesn't take ages.
Cheers for all the replies guys!
I spoke to HTC and they admitted pretty outright that it was a fault on their end and is definitely covered under warranty. Time to play the RMA game!
Hey everyone,
Coming here in hopes that the rooting community can offer some help and assistance. I had a close friend pass away last week and was provided his old Note 5 to see if any pictures could be recovered from the phone. This is his old phone from roughly 2 year ago. When I was given the phone the screen would not turn on and I think the phone was stuck in a boot loop as it would vibrate roughly every 10 seconds. I swapped the screen on the phone and was able to get it to boot. The phone now boots up but goes to the Google FRP saying the phone was reset and to access the phone we gotta used the previously synced account. Unfortunately we are not able to get into his Google account. We are unsure if the phone reset itself or if it was reset previously.
Its my understanding that when a phone resets it does not erase all the data but marks it for overwrite? Was wondering if anyone had any advice on how I should proceed and what would be my best bet to see if we can recover any photos that may still be on the phone.
Thank you,
Bump.