Issues with new (used) phone - X Style (Pure) Q&A, Help & Troubleshooting

I just got this phone on Swappa, I've been having a series of issues with it.
At first my home button stopped working. I tried booting in safe mode, it still wouldn't work. So I did a factory reset, but then my apps were crashing constantly.
Now... My wifi isn't working. Any advice? Has anyone had this happen before?

Magnik said:
I just got this phone on Swappa, I've been having a series of issues with it.
At first my home button stopped working. I tried booting in safe mode, it still wouldn't work. So I did a factory reset, but then my apps were crashing constantly.
Now... My wifi isn't working. Any advice? Has anyone had this happen before?
Click to expand...
Click to collapse
You need to post more information. Moto X Style or Pure? Which Android version? Which ROM are you running? Is the bootloader unlocked? Rooted? My initial thought is that the phone is rooted - in which case you don't want to factory reset from within Settings. You can check this from the bootloader (volume down+power). And if you look under Settings > About Phone, you should see details regarding Android version, ROM build, etc.
If the phone is unlocked, I would restore stock firmware and start from scratch. Here's the thread with firmware for the Pure Edition (XT1575). One note, before you do anything, remove any type of security you're using (e.g., pin, password, etc.). This will keep you from getting locked out of the device through Google's Device Protection.

Yeah you should flash stock images and start clean.

Related

No notification sounds on Froyo, can I revert to 2.1 on an unrooted Tmo N1?

So I updated to Froyo today, but was noticing some issues (phone wouldn't lock, home and search buttons don't work). So I tried reapplying the update, and now notification sounds do not work, in addition to the issues above. Sounds will play when I select them from a list, but not when I get a message or other notification event. How do I go about going back to 2.1? This is an unrooted phone. I haven't been able to find any clear instructions on doing this for unrooted phones. Any help would be appreciated.
Tad2much said:
So I updated to Froyo today, but was noticing some issues (phone wouldn't lock, home and search buttons don't work). So I tried reapplying the update, and now notification sounds do not work, in addition to the issues above. Sounds will play when I select them from a list, but not when I get a message or other notification event. How do I go about going back to 2.1? This is an unrooted phone. I haven't been able to find any clear instructions on doing this for unrooted phones. Any help would be appreciated.
Click to expand...
Click to collapse
Unfortunately as far as I know, you cannot revert without unlocking the bootloader and re-flashing to stock, thus voiding your warranty. You don't need to "root" to get back, but you do need an unlocked bootloader, and as I just stated it will void your warranty.
If I restore factory settings will I have to mess with unlocking the bootloader or anything? Probably won't fix it, but it's worth a shot. I just don't want to get stuck without a phone by doing the wrong thing here.
Tad2much said:
If I restore factory settings will I have to mess with unlocking the bootloader or anything? Probably won't fix it, but it's worth a shot. I just don't want to get stuck without a phone by doing the wrong thing here.
Click to expand...
Click to collapse
You can do a factory reset and maintain FroYo by going into stock recovery, pressing volume up+power at the same time and initiating whatever reset commands they give you (forget the proper terminology)
Thanks for the help.
What I ended up doing is going into Settings -> Privacy -> Reset to Factory defaults.
My phone wiped itself, rebooted with the stock Froyo rom and now everything is working. It then proceeded to re-download and install all of my apps! All said and done I had it back up and working perfectly in <10 minutes.

Massive softbrick (haven't found a solution yet)

Hello everyone,
So here's my story: I got a 6P short after release and it's been amazing. After switching from a S6 I couldn't be happier until 3 days ago.
I was playing around with my phone (checking for updates on the play store if I recall correctly) and I was going to switch from 4g to wifi. I went ahead and pulled down my notification shade and went to press WiFi but misclicked and hit Hotspot which was below it. My phone suddenly froze big time and this is for the first time ever since purchase.
At first I thought I'd wait it out since the device was completely unresponsive, home button didn't work and neither did anything on screen. Buttons didn't make a difference either. 10 minutes went by and I ended up force restarting by holding down power + volume up. First part of my bootup went fine but when it got to the android boot animation after I put in my pin to allow the device to start it dropped from the smooth usual framerate down to 1 frame every 10-15 seconds and it slowed down further until it came to a complete halt around the time the android letters appear.
My first thought was corrupt rom so I went ahead and wiped data from the stock recovery. I was running completely stock with no modifications whatsoever. That didn't do anything. Phone still froze in the same boot phase. Desperate I unlocked bootloader to flash a clean fresh image to try to fix it and to my surprise that didn't change a thing.
As I was getting pretty desperate already I had one more idea and that was to flash up to the Dev preview. To my huge surprise it booted and I jumped from excitement. So I started setting up my phone again. I got past the prompt to insert sim card and I was now at the screen to choose a wifi network. As soon as I clicked into that the phone froze up again and at that point I lost all hope.
I wiped data in stock recovery and shut the phone down for the night. On day 3, today I woke up and tried starting the phone and it worked as if nothing had happened. I went through the setup and set up my phone on the N preview. At a certain point I was planning to go back to the latest official build but for now I was happy my phone was back from the dead. Later today I tried to restart my phone to clear all running apps etc and it froze up on boot.
I'm losing all hope that I'll be resolving this myself so I'm reaching out to the community to see if anyone's had this happen to them before and hopefuly for a solution. It's still under warranty so I can eventually send it back to the retailer but I'd rather not have a phone for 3 weeks.
Any and all help is appreciated.
Thank you for reading through my long and probably pretty boring story!
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
To the OP, is there any reason you did not flash to release version 6 instead of Dev preview ?
Also, any reason you can not simply do the "unenroll" from https://www.google.com/android/beta ?
It will require you to setup certain settings again as you will be back to a "factory reset".
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
DJBhardwaj, i haven't specifically erased those partitions. I was under the impression wipe userdata along with reflashing did that. I will try that tonight when I get home!
Xdafly, I only updated up to N as a last resort because at first I had a locked BL. I was planning to unenrol but that would've been too late as it self bricked after a restart.
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
Well I just did the erase thingy and my phone booted but wifi won't turn on. Enabling hotspot doesn't brick anymore but I now suspect WiFi might've been the issue. Any tips on how to find out what it could be and possibly fix it?
Edit: 2 restarts and a factory reset later I'm back to bricked same way as before.
try safe mode
mr.dj26 said:
try safe mode
Click to expand...
Click to collapse
That was my first thought, that was the restart that bricked it again. Safe mode shouldn't have made a difference since I hadn't even logged into Google account for apps.
After reading the very first post; sounds like bad WiFi hardware.
All the hanging has been related to WiFi or Hotspot.
I think you should get a replacement
Sent from my Purified NexusixP
If Someone Helped You Then Dont Just say Thanks...Hit The Thanks Button!
Is your phone rooted and did you install Xposed?
Over the weekend I shutdown my 6p (stock rooted with April security patch, Xposed v80) and charged it. When it turned it back up I kept getting "Unfortunately, nfc service has stopped". Long story short: I ended up factory reset my phone and reinstalled EVERYTHING and I still got into bootloop. Then I came across
https://github.com/rovo89/Xposed/issues/113
https://github.com/rovo89/android_art/issues/28
At the end of the second post rovo89 (developer of Xposed) fixed the bug in V83. I wiped my 6p once more and installed everything with v83. Problem solved.
Good luck!

Android N OTA from 6.0.1 stock - Services crash and phone reboots every few minutes

Hey Guys, I updated OTA to Android N from 6.0.1 (Marshmallow). After the upgrade all services crash (all google services including Messenger SMS) and the phone reboots every few minutes.
-Boot-loader is locked.
-No Custom Recovery Image.
-Oddly, entering stock recovery from boot-loader results in "No Command" error message.
Ideas??
Probably something went wrong in the update process and conflicted with something else.
Anyway: hard reset.
The "no command" screen is just a security screen and it's normal, you need to bypass it to enter to the recovery with a button combination (that now I don't remember, but I never remembered it even though I used to enter in recovery after pressing random buttons combinations lol).
Thanks dude. No worries.
Hard reset didn't work. Also tried to flash OTA from Recovery..
I was really hoping to avoid the stock ROM.
For now, I unlocked the bootloader, installed Recovery, and then loaded Stock ROM. All is well under Stock ROM.
Will try again tomorrow.
cybrdude said:
Thanks dude. No worries.
Hard reset didn't work. Also tried to flash OTA from Recovery..
I was really hoping to avoid the stock ROM.
For now, I unlocked the bootloader, installed Recovery, and then loaded Stock ROM. All is well under Stock ROM.
Will try again tomorrow.
Click to expand...
Click to collapse
I've included full instructions on how to safely update in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
(section 14)
cybrdude said:
Hey Guys, I updated OTA to Android N from 6.0.1 (Marshmallow). After the upgrade all services crash (all google services including Messenger SMS) and the phone reboots every few minutes.
-Boot-loader is locked.
-No Custom Recovery Image.
-Oddly, entering stock recovery from boot-loader results in "No Command" error message.
Ideas??
Click to expand...
Click to collapse
Press power + volume up to get recovery menu.
Was having a similar issue. I'm all stock, unlocked bootloader. Signed for N preview and instantly got the OTA download. It installed and pretty much within a few minutes the bootloops started. couldn't even power down without it rebooting on its own. I got it to power down without turning itself back on through recovery/power down. I let it sit and cool down. Upon reboot.....was doing well, and started to boot loop again. I REALLY did not want to factory reset.
Heisenberg said:
I've included full instructions on how to safely update in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
(section 14)
Click to expand...
Click to collapse
Thanks dude, but not a newb. Not using my old account, which I should recover.
I had no issue restoring to stock after unlocking bootloader and flashing Recovery. Strange that the OTA via beta is unstable for some and not for others. Even after a reset of OTA, the services and reboot issues continued.
So for me, a factory reset and setting up a brand new phone (no backups of any kind....even from Google) have seem to do the trick. Unfortunate that I lose my wifi password backups. Asking some people for their wifi passwords again is a PIA. Especially the ones who don't know them, and it's a 27 key password from their cable company. Anyone know how to pull just the wifi backups from google?
My thought is one app or setting was causing my problem so I'm slowing adding everything one at a time. PIA really. I don't miss the Froyo days that's for sure.
cybrdude said:
Thanks dude, but not a newb. Not using my old account, which I should recover.
I had no issue restoring to stock after unlocking bootloader and flashing Recovery. Strange that the OTA via beta is unstable for some and not for others. Even after a reset of OTA, the services and reboot issues continued.
Click to expand...
Click to collapse
What happened to your old account?

I337 extreme lag, random reboots, no recovery

Recently bought a new out-of-the box Galaxy S4 I337 from Amazon. Had i known how much trouble it would give me, i would have picked something else. When i first turned the device on, it was almost totally unusable due to lag and random reboots. Software version was 4.4.2. I used Odin to flash a rootable NB1 onto the device. Still had lag and random reboots. Upgraded to lollipop using this guide: https://forum.xda-developers.com/galaxy-s4-att/help/guide-att-samsung-galaxy-s4-sgh-i337-t3383078 and still have lag and random reboots. Also, the first time i upgraded to lollipop, i installed safestrap not knowing it wouldn't work on lollipop. Obviously, my recovery disappeared. When i figured out what was going on, i did a fresh install of lollipop. I got recovery back, but today when i tried to boot into recovery to wipe the cache, i discovered it had mysteriously stopped working again. If i attempt to boot into recovery, it just skips to the Samsung logo. I didn't install safestrap or any other custom recovery this time.
When i turn the phone on, either it hangs at the AT&T white splash logo and refuses to load at all, or advances to the lock screen. I have disabled animations and every widget i could on the lock screen and yet when i attempt to unlock the phone, it usually freezes. If i repeatedly swipe the phone for thirty seconds or so, it unlocks but it is still frozen and i have to continue swiping to prevent it from locking again. Eventually i'm able to navigate the phone normally, until it randomly reboots or freezes. Sometimes i see an error message that Touchwiz home, Process System, or SystemUI has stopped working or is not responding. This is always accompanied by a freeze. Also, choosing an option in the dialogue that comes up when i press the power button (shut down, reboot, etc) invariably causes the device to soft reboot. Other times a soft reboot happens totally at random, even if i'm not doing anything. Anybody have any idea what's going on or did Amazon just sell me a dud? All of these issues have been happening since before i rooted the device or upgraded it, except for the disappearing recovery mode.
Thanks in advance for your help.
Sounds like a data factory reset is in order. First you need recovery back so I would odin the latest firmware for the phone that can be flashed in odin. If it's still messing up then get Amazon to replace it.
Since you have safe strap though, try booting a TW based rom like Thor ROM or Golden eye ROM. That may fix some things.
StoneyJSG said:
Sounds like a data factory reset is in order. First you need recovery back so I would odin the latest firmware for the phone that can be flashed in odin. If it's still messing up then get Amazon to replace it.
Since you have safe strap though, try booting a TW based rom like Thor ROM or Golden eye ROM. That may fix some things.
Click to expand...
Click to collapse
Just wanted to bump this to thank you for your reply. Never got the phone to work but i was able to get it back to stock and return it. I got a refurbished S5 instead.

Help bootloader error 01 reset device

Hello,
I bought the Android yoga book a week ago and was really happy with it. I unlocked the bootloader and rooted it.
The last few days I have been getting a lot of issues with the holo keyboard and the speakers and want to return/replace the yoga book.
I unrooted the tablet, re locked the bootloader, turned off the option under developer settings and reset the device.
However evegytime I boot, I am getting the bootloader error 01 device integrity cannot be verified.
How can I fix this issue?
Is there a stock firmware I can flash that will reset the device?
Thanks
Karthik
Why are intrusive ads - such as have begun to appear here on XDA - always so stupid and irrelevant? Always micky mouse oufits pushing micky mouse products? Really lowers the tone of the XDA website, yes?
zamzenos said:
Why are intrusive ads - such as have begun to appear here on XDA - always so stupid and irrelevant? Always micky mouse oufits pushing micky mouse products? Really lowers the tone of the XDA website, yes?
Click to expand...
Click to collapse
How about giving uBlock a try?
Before anybody starts to bark. I know Newspapers, Magazines or this kind of sites live from Advertising. But one thing is adding some Ad's, another having almost more Ad's than content... IMHO
Hey guys,
There are other threads where you can talk about ads, can anyone help with my issue?
Currently stuck with an unusable tablet.
karthikc24 said:
Hello,
I bought the Android yoga book a week ago and was really happy with it. I unlocked the bootloader and rooted it.
The last few days I have been getting a lot of issues with the holo keyboard and the speakers and want to return/replace the yoga book.
I unrooted the tablet, re locked the bootloader, turned off the option under developer settings and reset the device.
However evegytime I boot, I am getting the bootloader error 01 device integrity cannot be verified.
How can I fix this issue?
Is there a stock firmware I can flash that will reset the device?
Thanks
Karthik
Click to expand...
Click to collapse
for clarification...does it boot after the message or does it stop with that bootloader error?
danjac said:
for clarification...does it boot after the message or does it stop with that bootloader error?
Click to expand...
Click to collapse
It boots up, but my holo keyboard has a hardware defect. I can only use it in tablet mode with the keyboard disabled.
As soon as I switch it to laptop mode and the keyboard is enabled it starts acting wierd. Even without touching it random key presses occur, it keeps opening Google app closes my other windows etc
I have already done a factory reset but same problem.
When I return it, because of that bootloader error they will say that they won't exchange it
I want to restore the device to factory state so I need help how to get the bootloader back to stock.
Thanks
karthikc24 said:
It boots up, but my holo keyboard has a hardware defect. I can only use it in tablet mode with the keyboard disabled.
As soon as I switch it to laptop mode and the keyboard is enabled it starts acting wierd. Even without touching it random key presses occur, it keeps opening Google app closes my other windows etc
I have already done a factory reset but same problem.
When I return it, because of that bootloader error they will say that they won't exchange it
I want to restore the device to factory state so I need help how to get the bootloader back to stock.
Thanks
Click to expand...
Click to collapse
see here: https://source.android.com/security/verifiedboot/verified-boot
maybe unlock it again, flash a complete stock rom (with all its seperate partitions) which wasn't touched by root at all (did you make a backup using twrp). relock.
you could also download a stock rom from a website called 'easy-firmware.com', but you probably need to purchase it. still then i don't know whether just unlocking and locking the bootloader has already been enough to trigger the warning
if it doesn't work, well, then that's exactly what 'verified boot' is for...
hope it works.

Categories

Resources