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.
Related
Hey,
My AT&T rooted nexus one is still randomly rebooting if I use 3g data. I am in Costa Rica and the 3g is on the 850 band. I also have to add the apn "kolbi3g".
So basically I can use the phone for anything and it works great, but if I add the apn and start using the 3g heavily I will get a reboot, sometimes it will reboot vibrate 7 times and I have to pull the battery. I have tried 2.1 and 2.2 rooted and not also cyanogen 6 all the same problem.
If I do *#*#4636#*#* and select the wcdma only it runs the 3g better but reboots way more, sometimes the instant I place load on the connection. However if I select wcdma "unkown" the 3g works much better I can use it sometimes 30min at a time without a problem.
So any ideas what I could try? Is there a kernel that will up the volt's a bit just help stability? Or anything else I could try? Data roaming is off, I have tried both off and on, no difference that I can tell.
Thanks a lot this is driving me crazy! Just got this phone Sunday too sick to my stomach of the thought I spend $600 on this phone if I can't get 3g to work
How about radio image???
It is currently on baseband 4.06.00.12_7. Is there a more current radio?
I came across this multiple reboot issue on a (locked) Vodafone UK Nexus.
It booted into the OS (lockscreen) and as soon as data connected it looped back to the last couple seconds of the animated Nexus logo.... and again.... and again.
I powered down the unit (battery pull), booted into bootloader (voldown+power) and selected clear storage (voldown,voldown,power) then (volup) to confirm.
This deletes the user data and you have to sign in and set up the phone again but it certainly fixed the issue. My only guess is some user data became corrupt and the kernel panicked and forced a partial reboot.
Give it a try and lemme know.
Cabarnacus said:
I came across this multiple reboot issue on a (locked) Vodafone UK Nexus.
It booted into the OS (lockscreen) and as soon as data connected it looped back to the last couple seconds of the animated Nexus logo.... and again.... and again.
I powered down the unit (battery pull), booted into bootloader (voldown+power) and selected clear storage (voldown,voldown,power) then (volup) to confirm.
This deletes the user data and you have to sign in and set up the phone again but it certainly fixed the issue. My only guess is some user data became corrupt and the kernel panicked and forced a partial reboot.
Give it a try and lemme know.
Click to expand...
Click to collapse
Just did that (had the phone plugged into wall charger), and the second I got to the home screen it rebooted then vibrated like 6 or seven times. Seems to do it worse when it is plugged in. And now it won't even boot up even after pulling the battery, it vibrates 6-7 times.
I am really worried about this, any other ideas??? I will try anything! Thanks for the help
Update! Now the phone just reboot when I do anything period with it plugged in. Just like posted in another thread on this section!
Please any ideas I am very desperate and very sick to my stomach!
Hmmm very strange.
I'm aware from what you were saying on the other thread that you've got an unlocked bootloader and you're wondering what to do on the warranty front.
If you've really tried different combinations of stock and custom firmware and having the same issue I'm tempted to say its a hardware issue.
Many people have returned their unlocked phones with no comeback from HTC some have reported that they have noticed the unlocked bootloader and have issued a motherboard repair as part of the fix because of this.
Although im unsure of the additional cost (if any) i would definitely recommend going through the warranty repair route with HTC. They won't say no and send you back the same broken phone. And who knows, if its a confirmed hardware issue they may just replace it as a goodwill gesture.
Other than that I don't have any more ideas.
A nexus support thread has a popular answer referring to the clear storage fix.
http://www.google.de/support/forum/p/android/thread?tid=40f52d29e9c4177e&hl=en
Just make sure you are definitely clearing the storage FROM THE BOOTLOADER before calling HTC. It is the first thing they will make you do before accepting a return anyway.
Cabarnacus said:
Other than that I don't have any more ideas.
A nexus support thread has a popular answer referring to the clear storage fix.
http://www.google.de/support/forum/p/android/thread?tid=40f52d29e9c4177e&hl=en
Just make sure you are definitely clearing the storage FROM THE BOOTLOADER before calling HTC. It is the first thing they will make you do before accepting a return anyway.
Click to expand...
Click to collapse
Ok thank you so much sir. I am so glad to hear that I may still have a chance at getting it replaced! It was very fullish of me to unlock it, I know, it is just that I figured it was software and could be fixed by unlocking. It is going to cost me $$$ to get this to the States, but that is life. If I still can't get it to work I will call htc and let you know what they say
Little update here. I cleared storage again and just simply disabled data, I have been using the phone for a couple of hours on work without any problems. Next thong I am going yo yty is another friends 3g similar card and see if it still reboots on that sim, if it does then I am calling HTC.
Also still open to any other ideas you guys may have.
Help!! My XT has been running fine since I got it last September however since yesterday my device just shuts down when connected to network. Not a restart I actually have to physically turn it back. My device runs fine in airplane mode but as soon as I turn airplane mode off 3 seconds later off.
I am running a locked boot loader with non rooted 141 loaded through PCC so completely stock setup.
Is this looking like a hardware issue possibly or will reloading the stock firmware fix this?
Thanks
Sent from my Transformer TF101 using xda app-developers app
A quick update:
Issue sorted its self out in the evening, Managed to get conected to a network but only with data off, by the morning all was working fine again.
BUT
Later on saturday I had exactly the same cycle of issues again.
Device was fine all day yesterday YAY
However today has seen a return to being dead.
The difference being I didnt drive anywhere yesterday along with this rareity known as "British Summer". We have had some very warm days of recent and I am assuming the shutting down is a fail safe as the device gets too warm.
I guess there is nothing I can do but ride this out. Given we only have this sort of weather for about a week or so a year(if at all).
How do you guys who live in the more consistently warm climates cope with this device which clearly has heat issues?
Issue is getting much worse.
All last night it was out of action worrying as I use it as an alarm so ran it over night in airplane mode.
This morning working fine but now turns off everytime I send a text message.
I had an issue similar to this but it was whenever i connected to a particular WiFi network. For me changing the WiFi channel worked.
ITHORA said:
I had an issue similar to this but it was whenever i connected to a particular WiFi network. For me changing the WiFi channel worked.
Click to expand...
Click to collapse
No issues linked to WiFi seen here just when connecting to network.
issues have only come up since I updated to 141. everyone says this one prevents these issues which I never saw on earlier softwares.
I have done a repair through PCC and will see how that goes now.
Ok, device is not fixed by the repair.
I am no longer having the device randomly shut down completely but the the device is restarting. It has happened 4 times in the last hour.
1- As soon as sent a text.
2- Moving some apps around in the draw
3- Sending another text
4- unlocking phone
Does anyone have any ideas at all what is wrong with my device. Running smoothly for so many months and then now phone is becoming completely unusable.
Not sure if related but issues dont seem to arise when on charge and issues today only started once batter got below 60%.
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.
Love the device, but this one is going in for an exchange. Not sure if it will resolve the issues I had, but my phone was behaving badly. I unlocked and rooted it about 10 minutes after I got it, using the Chainfire method here..
1) WiFi reception is awesome, except it drops the connection constantly! I have an entry level commercial AP (Unifi) and the thing is awesome. All kinds of devices connected to it, but this Moto can't stay connected. From the logs on the controller, it appears to be switching channels constantly. Wifi goes from all bars to bars with x to off.
2) Reboot results in bootloop. On more than one occasion, I had to reset the device multiple times to get it to boot. This morning, I could not get it to complete a boot at all. I've since reflashed the Tmo stock ROM.
3) Lookout randomly comes back! Froze it with TiBu, stop and disable in app manager... nothing kills it! Reason 1 for root!
The WiFi issue is a killer. Again, I am going to take this one in and exchange it for another and hopefully the WiFi issue is gone. I think I'll need to restrain myself from rooting until I pass the exchange date.
I had similar issues what i did was flash the stock boot img then do a factory reset and reroot and everything is good now
forty9er said:
I had similar issues what i did was flash the stock boot img then do a factory reset and reroot and everything is good now
Click to expand...
Click to collapse
Thanks! I will give that a shot before I take it in.
I've been back on stock with unlocked bootloader for a day and change, and I still get WiFi drops. It seems to happen more with BT on, but they certainly haven't gone away. I've changed a bunch of things on my AP to try and eliminate them too, but it hasn't helped much. I may try disabling the A/C radio (which fixes it for some), but that's hardly an answer. I am starting to think that this is a Nougat or a Qualcomm issue.
Seems like a hardware issue. If it was a software issue then it would affect more than just you. So far you are the only person on various forms I go to having issues.
Sent from my Moto Z (2) using Tapatalk
Tidbits said:
Seems like a hardware issue. If it was a software issue then it would affect more than just you. So far you are the only person on various forms I go to having issues.
Click to expand...
Click to collapse
Well, it seems I'm not the only one.
https://forums.lenovo.com/t5/Moto-Z...terprise-type-5Ghz-band-802-11AC/td-p/3816198
I actually have this issue with another device too , so I think it's either an Android, AP or a Qualcomm thing. Some have said turning off the A/C/N radio helps, but that's not a "solution."
Hey all! New here. I just soft bricked my phone, i woke up to it not booting. I tried various fw in Odin, but no success. This is my day to day use phone, I don't have anything else, so I'd like to make it work again ASAP, hopefully without factory reset.
Hi
what manipulation did you do to get there before flashing a lot of stuff in odin?
I've been just pressing the buttons all around, then I read about Odin, so I tried it. Now my battery died, let's see if I can get to wipe the cache...
Update: no success. Is there a way to get it into recovery? the old volume up+bixby doesn't seem to work.
Sometimes its because the recovery itself is error so that button combination is not working..
Charge your battery until full, then factory reset it with odin, let see if that works
But before you do that make sure you download correct fw that match your phone model. dont try all fw available there, make sure you download fw for SM N950F..
Well it worked and it broke again... Back to square one.
Your infos are kinda vague.
Did you modify your phone and it got triggered by user-action, or did it hit the fan by itself?
I think it was a suicide attempt, I never flashed before, only major thing was just a battery change in a samsung service last summer. It's weird, because since last time it turned on again, but seems like the wifi didn't want to communicate, plus as I look back, sometimes it restarted when I touched the wifi or some random setting. Somewhere else I read that it could be a motherboard failure.
fzoli469 said:
I think it was a suicide attempt, I never flashed before, only major thing was just a battery change in a samsung service last summer. It's weird, because since last time it turned on again, but seems like the wifi didn't want to communicate, plus as I look back, sometimes it restarted when I touched the wifi or some random setting. Somewhere else I read that it could be a motherboard failure.
Click to expand...
Click to collapse
This was happening to me too before my phone just started bootlooping to recovery
Well it's been a few months, so a little update: it still reboots sometimes all out of nowhere, but now I have a different problem: tried to log into a mcdonalds app and it says it detects a security issue. Not that i'll cry over it, but definitely interesting. Anyway, I really think this is some sort of hardware issue related to wifi, because every time it started rebooting, about one out of two times i was turning the wifi on or off. Also sometimes the wifi just wasn't available or working, strengthening my thought. As I read on other threads, this is probably some manufacturing/serial issue, that just happens to come forth after all these years. Probably the last time I bought a Samsung...
fzoli469 said:
Well it's been a few months, so a little update: it still reboots sometimes all out of nowhere, but now I have a different problem: tried to log into a mcdonalds app and it says it detects a security issue. Not that i'll cry over it, but definitely interesting. Anyway, I really think this is some sort of hardware issue related to wifi, because every time it started rebooting, about one out of two times i was turning the wifi on or off. Also sometimes the wifi just wasn't available or working, strengthening my thought. As I read on other threads, this is probably some manufacturing/serial issue, that just happens to come forth after all these years. Probably the last time I bought a Samsung...
Click to expand...
Click to collapse
Try changing build prop, ro.config.tima to 0