Database Users

Help! Nexus S frozen.

About 30 minutes ago I downloaded an image off google images to use as my background. I saved it, then sent it to my background and my phone randomly restarts. Upon rebooting back up again it is frozen and I cannot unlock it. After that I try to hard reset but it fails and there is the andriod with a triangle and an exclamation mark inside. What can I do now?

mike128 said:
About 30 minutes ago I downloaded an image off google images to use as my background. I saved it, then sent it to my background and my phone randomly restarts. Upon rebooting back up again it is frozen and I cannot unlock it. After that I try to hard reset but it fails and there is the andriod with a triangle and an exclamation mark inside. What can I do now?
Click to expand...
Click to collapse
Factory reset your phone and if that doesn't work...flash stock and go from there? I've yet to see someone actually brick their NS yet and I doubt a wallpaper is the first real culprit.

I'm not sure. But sadly I'm back on my Nexus one. How do I factory reset?

Wait are you completely stock? If so you might have a real phone issue. Factory east by holding volume up and then pressing the power button. It'll wipe all your data but if you're stock its really your only option aside from excercisng a warrant.
Sent from my Sublime MoDaCo Nexus S running Netarcy's amazing kernel!

settings->security->factory reset

Yeah this could be a really bad exploit in 2.3, or something of the likes... Like something Google messed up on. Or, the wallpaper was malicious.

Yes, I was running stock. I could not get the resetter to go (volume down + power) but I kept pulling the battery and tried to get any control. Eventually I was able to swipe really quick and unlocked the phone. The wallpaper was not there, it was just black. Everything was running super slow then I quickly went to the wallpaper settings and restored the factory live microbes one and everything was back. However, all my widgets disapeared. Phew. Glad it didn't brick.

Something as trivial as that will not brick your phone, what will brick your phone is a bad radio flash or of your messing with internal files. Lots of people bricked their g2's when striving to achieve s-off, these are the ways to brick your phone other than a hardware fault already inherent.
JD
Sent from my Google Nexus S Black Neolithic Piece of Wonderment.

If you have the android SDK installed. If you unlock your bootloader (fastboot oem unlock) it will do a factory reset of your phone, at that point you can just lock it again if you wish.

I had the same thing happen to me. In the future if this happens just do a factory reset. I was worried that it would wipe my internal Memory too, but all it did was reset the phone to stock and i had to redownload my apps. All my pics, photos and music were still intact.

insanemachine said:
If you have the android SDK installed. If you unlock your bootloader (fastboot oem unlock) it will do a factory reset of your phone, at that point you can just lock it again if you wish.
Click to expand...
Click to collapse
I am trying that,but every time i write fastboot oem unlcok in cmd,i gives me back message "waiting for devices",why?!?What to do now?

Issues with new (used) phone

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.

Is my XT1575 recoverable?

My XT1575 just decided to go into a bootloop a week ago on its own, literally. I was just checking traffic on Google maps when I noticed it started to lock up. Finally, I see the Motorola splash screen, and that was the beginning of it. Went into recovery mode and tried a factory reset, clear cache partition, etc. but no luck. I've tried everything under Android 6.0 here but it continues to bootloop no matter what I do.
It's not rooted and the bootloader is locked, so I don't think I can even install TWRP or any custom recovery. I have never even though of enabling USB debugging so that's out of the question. What's odd is after trying all sorts of things, sometimes, after the phone has been off for a while I would power it on and it would actually boot into the Welcome screen. Shortly after that though, it locks up and starts bootlooping again. I don't know what else I can do about this or if it's recoverable. I hope someone can help. If it's of any significance, when in recovery mode, at the top I see what I think is the firmware it's currently on -- motorola/clark_retus/clark 6.0/MPHS24.49-18-4/5. Please help!

Update - After having my XT1575 powered off overnight, I powered it on this morning and it was able boot all the way into the Welcome screen, setup, etc. Right away I went and turned on USB Debugging and Allow OEM unlock. Tried rebooting and again it fails to boot. What's weird is it randomly seems to boot when it wants, and something must be corrupt but I just don't know what it could be. Does anyone have any ideas?

Don't unlock the bootloader.
If it is locked and behaving that way you should be able to get a warranty fix out of Lenovorola. If you unlock the bootloader you void your warranty, and they might choose to not honor it even if you say the problem started before.
Painful and slow as it might be, I'd recommend working with the manufacturer on this one.

jason2678 said:
Don't unlock the bootloader.
If it is locked and behaving that way you should be able to get a warranty fix out of Lenovorola. If you unlock the bootloader you void your warranty, and they might choose to not honor it even if you say the problem started before.
Painful and slow as it might be, I'd recommend working with the manufacturer on this one.
Click to expand...
Click to collapse
Yes undo what you just did an follow this guy

jason2678 said:
Don't unlock the bootloader.
If it is locked and behaving that way you should be able to get a warranty fix out of Lenovorola. If you unlock the bootloader you void your warranty, and they might choose to not honor it even if you say the problem started before.
Painful and slow as it might be, I'd recommend working with the manufacturer on this one.
Click to expand...
Click to collapse
I'm afraid it's too late for the bootloader, since it was one of the things I was trying out of desperation. After trying fastboot flashing the stock firmwares, I still get bootloops and strangely enough I was able to use the phone the other day for several hours before it started bootlooping again Thing is, it seems to behave differently at random times. Sometimes it makes it all the way up to the "Android is upgrading" screen but then freezes and reboots.. Other times it locks up at the Motorola splash screen and reboots.. And sometimes it even boots all the way up, is usable for a little bit, then begins bootlooping on its own.
I'm just wondering if something is corrupt software-wise (boot? system? etc?) or if it's a hardware issue. How do I even tell at this point?

iflyimpilot said:
I'm afraid it's too late for the bootloader, since it was one of the things I was trying out of desperation. After trying fastboot flashing the stock firmwares, I still get bootloops and strangely enough I was able to use the phone the other day for several hours before it started bootlooping again Thing is, it seems to behave differently at random times. Sometimes it makes it all the way up to the "Android is upgrading" screen but then freezes and reboots.. Other times it locks up at the Motorola splash screen and reboots.. And sometimes it even boots all the way up, is usable for a little bit, then begins bootlooping on its own.
I'm just wondering if something is corrupt software-wise (boot? system? etc?) or if it's a hardware issue. How do I even tell at this point?
Click to expand...
Click to collapse
The random nature of what you're describing does sound like hardware. Consider a full restore where you fastboot flash everything back to stock of you haven't already.
Check logs. See if you're getting anything in last_kmsg. Use an app like syslog if you aren't used to pulling them, though you might have to use adb if you aren't getting through boot all the time.

jason2678 said:
The random nature of what you're describing does sound like hardware. Consider a full restore where you fastboot flash everything back to stock of you haven't already.
Check logs. See if you're getting anything in last_kmsg. Use an app like syslog if you aren't used to pulling them, though you might have to use adb if you aren't getting through boot all the time.
Click to expand...
Click to collapse
Thanks for replying. I've tried fastboot flashing everything and even going into recovery and clearing cache partition as well as doing a factory data reset. I'm afraid it may very well be hardware. I'll try your suggestion about the logs.
Is 'last_kmsg' a line I should be looking for in the log? If so, what would I need to see in order to determine whether or not it's a hardware problem?

iflyimpilot said:
Thanks for replying. I've tried fastboot flashing everything and even going into recovery and clearing cache partition as well as doing a factory data reset. I'm afraid it may very well be hardware. I'll try your suggestion about the logs.
Is 'last_kmsg' a line I should be looking for in the log? If so, what would I need to see in order to determine whether or not it's a hardware problem?
Click to expand...
Click to collapse
/proc/last_kmsg is a log file that should get written to if a kernel panic causes a reboot in theory. In practice I find it is often blank even after a random reboot.

iflyimpilot said:
I'm afraid it's too late for the bootloader, since it was one of the things I was trying out of desperation. After trying fastboot flashing the stock firmwares, I still get bootloops and strangely enough I was able to use the phone the other day for several hours before it started bootlooping again Thing is, it seems to behave differently at random times. Sometimes it makes it all the way up to the "Android is upgrading" screen but then freezes and reboots.. Other times it locks up at the Motorola splash screen and reboots.. And sometimes it even boots all the way up, is usable for a little bit, then begins bootlooping on its own.
I'm just wondering if something is corrupt software-wise (boot? system? etc?) or if it's a hardware issue. How do I even tell at this point?
Click to expand...
Click to collapse
going by that logic the thing that you should have done was get a factory image from moto and flash to stock using moto tools if that failed at fixing it then send into moto it might not be lost yet but the more you progress the more less likely to replace the phone moto is...
it sounds like something is going bad could be ram emmc or the soc
What i would do is get into discussions with lenovo to see if they can get you fixed up. if you unlocked the bl they know be straight with them. if you get nowhere and no rom you load can fix it sell as parts replace at your expense...

[A2017G] LineageOS 14.1 - Can not access TWRP anymore, can't get through setup either

Hey folks,
I did not find anything on this issue, seems to be rather unique. Let me describe the problem.
This is my father's Axon 7 and he wanted me to get him a different ROM on there, which I did, and it worked smoothly until today. It kept crashing, freezing and was literally unusable for unknown reasons.
So since he was going to be gone for the next few days, I had no choice but to remove the ROM and data and reflash it. HOWEVER I did not delete the internal storage since I did not think it would be necessary. Sitting in the setup, I had issues getting through it, it will not pop up the keyboard to let me type the wifi password neither does it let me pass through if I wanted to use mobile data. It simply gets stuck. Sometimes random android processes tend to crash and put me at the start of the setup and I can't get to the settings which does prevent me from enabling USB-debugging or OEM unlock.
If I try to get into the recovery (which is still on there) it will simply get stuck on the screen that says ZTE, did not work through fastboot either, same issue.
(I do personally think that some app data is corrupted and causes the issue, since I wiped everything except internal storage and I still have major issues)
So here am I, stuck. I hope someone can enlighten me, or tell me how stupid I am and point me at something completely obvious. Thanks

OmegaFighter said:
Hey folks,
I did not find anything on this issue, seems to be rather unique. Let me describe the problem.
This is my father's Axon 7 and he wanted me to get him a different ROM on there, which I did, and it worked smoothly until today. It kept crashing, freezing and was literally unusable for unknown reasons.
So since he was going to be gone for the next few days, I had no choice but to remove the ROM and data and reflash it. HOWEVER I did not delete the internal storage since I did not think it would be necessary. Sitting in the setup, I had issues getting through it, it will not pop up the keyboard to let me type the wifi password neither does it let me pass through if I wanted to use mobile data. It simply gets stuck. Sometimes random android processes tend to crash and put me at the start of the setup and I can't get to the settings which does prevent me from enabling USB-debugging or OEM unlock.
If I try to get into the recovery (which is still on there) it will simply get stuck on the screen that says ZTE, did not work through fastboot either, same issue.
(I do personally think that some app data is corrupted and causes the issue, since I wiped everything except internal storage and I still have major issues)
So here am I, stuck. I hope someone can enlighten me, or tell me how stupid I am and point me at something completely obvious. Thanks
Click to expand...
Click to collapse
well, you can use EDL maybe?
The fastest way out is downloading the A2017G_FULL_EDL file from our Russian friends and use MiFlash while in EDL mode to flash the cluster**ck of a phone that you have.
The closest thing I've seen was a friend's Galaxy Grand 2 (like 5 years old) that maybe had a part of the system corrupted or a slightly dead eMMC. a bunch of stuff just crashed for no apparent reason. I reflashed the system and it got fixed for some time, then it started doing some weird sh!t again (after booting, you have an 80% chance that it will just freeze forever, hard reboot needed). But let's hope for the best and see if you can recover it by reflashing stock totally. If it still doesn't work you might be able to relock the BL and claim the warranty

Choose an username... said:
well, you can use EDL maybe?
The fastest way out is downloading the A2017G_FULL_EDL file from our Russian friends and use MiFlash while in EDL mode to flash the cluster**ck of a phone that you have.
The closest thing I've seen was a friend's Galaxy Grand 2 (like 5 years old) that maybe had a part of the system corrupted or a slightly dead eMMC. a bunch of stuff just crashed for no apparent reason. I reflashed the system and it got fixed for some time, then it started doing some weird sh!t again (after booting, you have an 80% chance that it will just freeze forever, hard reboot needed). But let's hope for the best and see if you can recover it by reflashing stock totally. If it still doesn't work you might be able to relock the BL and claim the warranty
Click to expand...
Click to collapse
Hey,
After a long day I managed to fix it, I was able to use the adb in fastboot and could reinstall the recovery and managed to run it, deleted internal storage and reinstalled everything. Seems to have done the trick. I hope it will keep working now.

OmegaFighter said:
Hey,
After a long day I managed to fix it, I was able to use the adb in fastboot and could reinstall the recovery and managed to run it, deleted internal storage and reinstalled everything. Seems to have done the trick. I hope it will keep working now.
Click to expand...
Click to collapse
good

OnePlus 5 touch screen stop working

Could someone help me fix my OnePlus5?
Simply from one day to the other the Touch screen stopped working, I can not select any option, being possible only by physical button.
I can not enter Recovery Mode because when I first connected the device I have already entered a password, so I can not type the password because the touch does not work.
I do not know what else to do!!!
I have the OTG cable from OnePlus and even putting Mouse or Keyboard, both do not work.
Would anyone have other suggestions?

Follow the compressed video showing the recovery mode locked by password, touch does not work.
And photo from FastBoot Mode Screen.

Any updates on how you fixed this or what the problem was?

I had to RMA, motherboard was replaced.

I have the same problem
My screen stoped working and the recovery mode is protected with password like the video sent, i live in Brazil and here i dont have the RMA option, can someone help me?

_-^SORCERER^-_ said:
Could someone help me fix my OnePlus5?
Simply from one day to the other the Touch screen stopped working, I can not select any option, being possible only by physical button.
I can not enter Recovery Mode because when I first connected the device I have already entered a password, so I can not type the password because the touch does not work.
I do not know what else to do!!!
I have the OTG cable from OnePlus and even putting Mouse or Keyboard, both do not work.
Would anyone have other suggestions?
Click to expand...
Click to collapse
i was facing this and fixed it.
just use unbrick tool
after the phone boot up and touchscreens still doesn't work, just do a reboot

Tks @Apayah, Will try this procedure, and return with status.

@Apayah, theoretically OnePlus 5 returned works, I will wait a few days to see if the problem continues.
Thank you so much.

edujmjr said:
My screen stoped working and the recovery mode is protected with password like the video sent, i live in Brazil and here i dont have the RMA option, can someone help me?[/QUOTE @edujmjr I used the unbrick process and now works.
Try this process.
Enviado de meu ONEPLUS A5000 usando Tapatalk
Click to expand...
Click to collapse

_-^SORCERER^-_ said:
@Apayah, theoretically OnePlus 5 returned works, I will wait a few days to see if the problem continues.
Thank you so much.
Click to expand...
Click to collapse
Np, all good now?

Apayah said:
Np, all good now?
Click to expand...
Click to collapse
At this moments, yes, I will wait more days.
Thanks for your support in this problem.

_-^SORCERER^-_ said:
At this moments, yes, I will wait more days.
Thanks for your support in this problem.
Click to expand...
Click to collapse
no problem

Apayah said:
i was facing this and fixed it.
just use unbrick tool
after the phone boot up and touchscreens still doesn't work, just do a reboot
Click to expand...
Click to collapse
I'm facing the same issue . My phone was working perfectly fine one minute and then the next, the screen stopped responding including the two capacitive buttons. I rebooted it thinking it mgiht fix it, but now i"m stuck on the lockscreen.
Could you point me to the unbrick tool? Is it this one:
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
Does it do a factory reset or would it fix the unresponsive touchscreen issue without any loss of data?

CoCoGirl886 said:
I'm facing the same issue . My phone was working perfectly fine one minute and then the next, the screen stopped responding including the two capacitive buttons. I rebooted it thinking it mgiht fix it, but now i"m stuck on the lockscreen.
Could you point me to the unbrick tool? Is it this one:
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
Does it do a factory reset or would it fix the unresponsive touchscreen issue without any loss of data?
Click to expand...
Click to collapse
your bootloader unlocked ?, if you're on twrp, then do a back up via mtp.
yes i was use that one, well i was do factory data reset and still touchscreen was didn't work, i was still on twrp so i backing up all my data before i mess with it.

I've also had this issue already had the MB replaced but I had my new MB lost touch for about 5min today so i'll see if it gets worse like it did last time.

Apayah said:
your bootloader unlocked ?, if you're on twrp, then do a back up via mtp.
yes i was use that one, well i was do factory data reset and still touchscreen was didn't work, i was still on twrp so i backing up all my data before i mess with it.
Click to expand...
Click to collapse
I got an usb-c to OTG cable and was able to use the mouse in trwp. I followed a guide online to get past the lockscreen by deleting the lockscreen key files. After I did that, my screen just magically started working again. But now when I boot into the phone, it swipes to unlock but I can't access anything. It looks like it may be encrypted or something? I tried to set a new password to a pin/pattern but it won't save.
When I boot into trwp, it asks me to enter a password but I never had one? I tried using "default_password" and also using the numbers to represent the pattern but still doesn't work. Any idea how I can access my files or get my phone to boot up fully? I'm trying to avoid a factory reset, :crying:

CoCoGirl886 said:
I got an usb-c to OTG cable and was able to use the mouse in trwp. I followed a guide online to get past the lockscreen by deleting the lockscreen key files. After I did that, my screen just magically started working again. But now when I boot into the phone, it swipes to unlock but I can't access anything. It looks like it may be encrypted or something? I tried to set a new password to a pin/pattern but it won't save.
When I boot into trwp, it asks me to enter a password but I never had one? I tried using "default_password" and also using the numbers to represent the pattern but still doesn't work. Any idea how I can access my files or get my phone to boot up fully? I'm trying to avoid a factory reset, :crying:
Click to expand...
Click to collapse
Ahh i never facing like that, try using multirom twrp ? At least at this moment you need to backup you're data.
You mean lockscreen thingy on data/system? There's a 3 files i guess and if you delete that, yes you can pass your screen.
I have no idea if twrp asked for a password, before this happened you're decrypted or encrypted? Password on twrp only for encrypted i think

Apayah said:
Ahh i never facing like that, try using multirom twrp ? At least at this moment you need to backup you're data.
You mean lockscreen thingy on data/system? There's a 3 files i guess and if you delete that, yes you can pass your screen.
I have no idea if twrp asked for a password, before this happened you're decrypted or encrypted? Password on twrp only for encrypted i think
Click to expand...
Click to collapse
I deleted the 5 files in data/system and passed the lockscreen. But it doesn't let me see any information . I think I was probably encrypted since I don't believe I decrypted anything. I can't backup my data in twrp because without entering the password my files have a lot of folders that look like "WDAbwwoefdFZZfde." Before I deleted the keys, twrp asks me to enter my password which is a pattern, same one as when i start my phone. After I deleted the lockscreen keys, trwp asks me to type a password from letters or numbers.
Do you think if I were to dirty flash my rom again without wiping, that it will recreate the lock keys and decrypt my data? Without having to use multirom twrp?

CoCoGirl886 said:
I deleted the 5 files in data/system and passed the lockscreen. But it doesn't let me see any information . I think I was probably encrypted since I don't believe I decrypted anything. I can't backup my data in twrp because without entering the password my files have a lot of folders that look like "WDAbwwoefdFZZfde." Before I deleted the keys, twrp asks me to enter my password which is a pattern, same one as when i start my phone. After I deleted the lockscreen keys, trwp asks me to type a password from letters or numbers.
Do you think if I were to dirty flash my rom again without wiping, that it will recreate the lock keys and decrypt my data? Without having to use multirom twrp?
Click to expand...
Click to collapse
Right seems encrypted problems, did you try multirom twrp yet? Should be on GZR xda thread

My OnePlus 5 stop Work again.
Enviado do meu iPhone usando Tapatalk