My phone is rooted and I have Jelly 'beans' ROM installed. Everything was going well (been running for a week) until I installed ActiveNotifications (https://play.google.com/store/apps/details?id=com.greatbytes.activenotifications). I'm not stuck on my lock screen and the touch screen does not respond to unlock it. There is also a hand icon in the status bar that I've never seen before. I can't (as far as I know) use adb to uninstall because the phone is not in USB debugging.
Any thoughts short of wiping and re-installing the ROM?
TIA
ffeingol said:
My phone is rooted and I have Jelly 'beans' ROM installed. Everything was going well (been running for a week) until I installed ActiveNotifications (https://play.google.com/store/apps/details?id=com.greatbytes.activenotifications). I'm not stuck on my lock screen and the touch screen does not respond to unlock it. There is also a hand icon in the status bar that I've never seen before. I can't (as far as I know) use adb to uninstall because the phone is not in USB debugging.
Any thoughts short of wiping and re-installing the ROM?
TIA
Click to expand...
Click to collapse
Yeah, neat app huh? I did the same thing myself. I think to use it you have to have a PIN unlock. Anyway, if you can pull down your notification shade, go into settings and uninstall it. Also if you have no security set for your lock screen, try to call your phone or send a text, something that will immediately get you into the main UI, then uninstall it.
Power it off the press at the same time power>home>vol up and boot into recovery and reflash the rom..
Sent from the future via Tapatalk 4
ffeingol said:
My phone is rooted and I have Jelly 'beans' ROM installed. Everything was going well (been running for a week) until I installed ActiveNotifications (https://play.google.com/store/apps/details?id=com.greatbytes.activenotifications). I'm not stuck on my lock screen and the touch screen does not respond to unlock it. There is also a hand icon in the status bar that I've never seen before. I can't (as far as I know) use adb to uninstall because the phone is not in USB debugging.
Any thoughts short of wiping and re-installing the ROM?
TIA
Click to expand...
Click to collapse
Maybe consider restoring from your most recent nandroid? I know that it's losing some progress, but you might be able to save yourself some time. Short of that, I think you'll need to re-flash your ROM, unfortunately.
I've been in situations like this one before, and that's the big reason why I've made it my standard operating procedure to maintain two backups: one for pre-flash and on stable post-flash for every new ROM. It's been helpful so far (in the extremely limited experience I have with custom software on my phone).
I'm going to wait just a bit to see if anyone else has some great suggestion, but I think I'll have to re-flash (after I finally got my home screen the way I want it). I do have PIN lock on. Can't pull the notifications down. With the ROM I'm using the AOSP lockscreen and I when you touch the circle to unlock none of the icons show.
Not a happy camper
ffeingol said:
I'm going to wait just a bit to see if anyone else has some great suggestion, but I think I'll have to re-flash (after I finally got my home screen the way I want it). I do have PIN lock on. Can't pull the notifications down. With the ROM I'm using the AOSP lockscreen and I when you touch the circle to unlock none of the icons show.
Not a happy camper
Click to expand...
Click to collapse
Try to hit the menu button while you're on the lockscreen, sometimes that'll bypass the lock screen.
Sent from my SCH-I535 using Tapatalk 2
After wiping and re-installing the ROM (several times) I think I may have found the culprit. My phone suddenly thinks that my 32 GB external SD card is bad and is stuck in a fsck. If I put the card out everything is happy. Time to backup the sdcard and reformat.
Related
So I was messing around with my Liquid Smooth lock screens. I came across this one (I don't remember the name of it though..) and whenever I try to unlock it it reboots and I can't do anything. So, how do I fix this? I can't unlock to change it because it just reboots.
Here's a picture. I think it's like the 4th one down in the menu. I'm assuming you grab the lock and take it up.. then it just reboots
I'm just going to factory restore it again. Just so everyone knows, don't use this lock screen if you have liquid smooth! D:
That's the new ring style (Used in the CM builds for our phones, I believe) But, I never had a problem with it. lol. You can drag it up if you want, but you just move it from its spot and it'll unlock (or go to app) but, I just suggest wiping user data then trying it again.
Chyrux said:
That's the new ring style (Used in the CM builds for our phones, I believe) But, I never had a problem with it. lol. You can drag it up if you want, but you just move it from its spot and it'll unlock (or go to app) but, I just suggest wiping user data then trying it again.
Click to expand...
Click to collapse
Well it definitely didn't work for me so I did a factory reset
OK, so tonight I decided to install the Atrix 2 Blaze mod. It installed without any issues.
After installing and verifying that everything worked, I then decided to use Titanium Backup to batch restore my apps. This appeared to work, and at the end of the process it told me to reboot. So I did.
Once it booted back up, I was greeted with the lock screen, as you'd expect -- but when I unlocked the phone, all I saw was a black screen and the notification bar on top. No wallpaper, no icons, no widgets, nothing. I could open the task drawer, I could make the soft keyboard appear, I could bring up the "open apps" window... but I can't actually do anything because the screen is freaking black.
But because the notification bar works, I can tell there are things going on. I see my phone checking for email. I see my phone battery decreasing. I see notifications when my google+ or twitter apps detect people are replying to threads I've been on. In other words, the phone appears to be working in every way except that there's nothing on the screen for me to interact with.
Has anyone seen this before? Is there a way to fix it? I hope?
Your best bet is probably just to flash the 2.3.5 Stock FXZ and start from scratch.
Sent from my MB865 using XDA
try re-flashing ?
looks like you loose your home launcher ..
I had the EXACT same problem, everything below the notifications bar was blacked out, i could bring up recent apps, but i couldn't even bring up the emergency dial pad at the unlock screen. Only difference is mine happened when i froze Go Launcher using Titanium Backup. I could tell it was still trying to run Go Launcher coz i could auto-rotate the screen.Sadly, the only option i had was to reset the phone and loose everything. I couldnt even backup my files coz i set USB mode to charge only so it never popped up on PC.
I reckon you restored an app that has a missing component/data and so it crashes at startup, maybe a home launcher, locker etc. Try making a backup then resetting your phone
Same problem here Ill try the fxy method,
any of you had solve the problem?
I don't know if this is a standard feature of the device, but when the phone is in standby, ie. the screen is off, the LED continues to flash the whole time.
Went into settings > Display, Gestures & Buttons > Notification Flash and un-ticked everything. Yet it continues to flash.
Also when the screen first turns on and I'm on the home page, it will continue to flash until I pull down on the status bar. Strangely I must do this every time whether there are messages, alerts and so on that need to be cleared or not. Leave the phone for 30 seconds, the screen turns off and the LED starts to blink again ...
Could someone please tell me how to stop the LED blinking? Its getting annoying thinking there's a message or something.
Thx
If you used moonshine to achieve S-Off then that could be the issue as it was for me as well. Even better my problem went as far as blinking when the battery would die on me and even after taking it off the charger it would still blink but would refuse to turn back on. I would have to remove the battery in order to start it up. However, I just downgraded my device from JB to ICS then back to JB while still keeping S-Off but removing moonshine. Now the phone works fine. Another issue was with those pesky busybox market apps. They don't function well especially if you try to restore or uninstall them. Thankfully, I have a stock JB backup for my future endeavors. I'm not sure what all you have done to your device but if you went about it with moonshine then my bet is on that lol. Again, I am only assuming.
Hey thx for the reply. This phone isn't S-Off or moonshined either. Its rooted, but doesn't even have a custom ROM.
I might scratch it and do a fresh everything and see if that sorts it out. Maybe try a custon ROM before that to see if it sorts it out.
Thx again
Burginthorn said:
Hey thx for the reply. This phone isn't S-Off or moonshined either. Its rooted, but doesn't even have a custom ROM.
I might scratch it and do a fresh everything and see if that sorts it out. Maybe try a custon ROM before that to see if it sorts it out.
Thx again
Click to expand...
Click to collapse
Sounds good. If you resolve the issue post back here with the info for the masses. You just never know who else might need the help
Sent from my C525c using xda app-developers app
Alright so, I haven't the slightest clue what caused this problem. I just happened to have rebooted my phone into bootloader mode as a way to ensure something I did didn't get transmitted when I re-enabled my Wifi which I happened to have disabled before rebooting and then re-enabled afterwards.
Anyways after I press reboot from the HBOOT menu, when my phone booted up the motion gestures would not work and I had an AOSP lockscreen...(take note im running ViperROM 1.8.0 on 4.4.3 firmware) oddly enough this isn't even enabled in the Viper Tweaks or any other tweaking apps I have. Soo why do I all of a sudden have these? It's as if I'm on an AOSP ROM but with Sense and a non Sense kernel? Even though NOTHING has changed today?? I haven't even been on my phone hardly at all besides that...
Why and how would I fix it?
Edit: Ok the tap to wake and swipe to wake actually work but double tap to turn screen back off is blocked because of the way the AOSP lockscreen functions. Swipe to shut screen off still works too. I just can't figure out how to remove this lockscreen
S1L3nTShaDoWz said:
Alright so, I haven't the slightest clue what caused this problem. I just happened to have rebooted my phone into bootloader mode as a way to ensure something I did didn't get transmitted when I re-enabled my Wifi which I happened to have disabled before rebooting and then re-enabled afterwards.
Anyways after I press reboot from the HBOOT menu, when my phone booted up the motion gestures would not work and I had an AOSP lockscreen...(take note im running ViperROM 1.8.0 on 4.4.3 firmware) oddly enough this isn't even enabled in the Viper Tweaks or any other tweaking apps I have. Soo why do I all of a sudden have these? It's as if I'm on an AOSP ROM but with Sense and a non Sense kernel? Even though NOTHING has changed today?? I haven't even been on my phone hardly at all besides that...
Why and how would I fix it?
Edit: Ok the tap to wake and swipe to wake actually work but double tap to turn screen back off is blocked because of the way the AOSP lockscreen functions. Swipe to shut screen off still works too. I just can't figure out how to remove this lockscreen
Click to expand...
Click to collapse
I had this same issue yesterday. I went to bed sat shut phone off with sense lock screen. Woke up Sunday powered on phone to see a aosp lock screen. I was like huh...I had to go to the play store an download HTC lock screen app they recently put in play store. Downloaded that then rebooted an sense lock screen is back. Try that out
Tigerstown said:
I had this same issue yesterday. I went to bed sat shut phone off with sense lock screen. Woke up Sunday powered on phone to see a aosp lock screen. I was like huh...I had to go to the play store an download HTC lock screen app they recently put in play store. Downloaded that then rebooted an sense lock screen is back. Try that out
Click to expand...
Click to collapse
The thing is..I already have that for some odd reason? It's right here and I never had this before either, it just randomly appeared and wanted me to update it a few days back. Strangely enough it was right after I downgraded back from 2.4.0 Viper ROM to 1.8.0 with a Nandroid. Should I just restore the Nandroid again*? it's literally exactly the same as this, I was gonna do it last night but it was far too late and I was tired.
S1L3nTShaDoWz said:
The thing is..I already have that for some odd reason? It's right here and I never had this before either, it just randomly appeared and wanted me to update it a few days back. Strangely enough it was right after I downgraded back from 2.4.0 Viper ROM to 1.8.0 with a Nandroid. Should I just restore the Nandroid again*? it's literally exactly the same as this, I was gonna do it last night but it was far too late and I was tired.
Click to expand...
Click to collapse
Try uninstalling that app via titabackup then go to play store an redownload it an reboot. If that don't work yeah I would definitely restore back up. But this solved my issue an it sounds like same as yours. Crazy tho huh?
Tigerstown said:
Try uninstalling that app via titabackup then go to play store an redownload it an reboot. If that don't work yeah I would definitely restore back up. But this solved my issue an it sounds like same as yours. Crazy tho huh?
Click to expand...
Click to collapse
"To finish updating lock screen please reboot now!"
Ohhhhh!! aaaaand...??? Waiting........................................................still booting...................dotdot....dotdotdotdotdot............still there
Firing the ion cannonz and restoring system backups, revert in process! *bzzzt---syste--msss faiiilllllinnngggg*
Seriously though it didn't work, restoring backups now LOL
S1L3nTShaDoWz said:
"To finish updating lock screen please reboot now!"
Ohhhhh!! aaaaand...??? Waiting........................................................still booting...................dotdot....dotdotdotdotdot............still there
Firing the ion cannonz and restoring system backups, revert in process! *bzzzt---syste--msss faiiilllllinnngggg*
Seriously though it didn't work, restoring backups now LOL
Click to expand...
Click to collapse
Well that's bs lol. You should have seen me when I woke up an seen this I was like wtf. So I went a removed sense toolbox an it was still there. I was totally lost. I did just what I told you to do an it came back an stayed. You would think if it worked for me it work for you u know. Hope your backup is alright. I like the fact HTC is dropping apps in play store so the don't have to wait on carrier to push ota to update a few things. But they should male sure it works rt..if you read all the reviews in playsotre bout this app. Not good at all some stock an locked users r in a bootloop from this updating an their only choice was factory reset. Not good
Tigerstown said:
Well that's bs lol. You should have seen me when I woke up an seen this I was like wtf. So I went a removed sense toolbox an it was still there. I was totally lost. I did just what I told you to do an it came back an stayed. You would think if it worked for me it work for you u know. Hope your backup is alright. I like the fact HTC is dropping apps in play store so the don't have to wait on carrier to push ota to update a few things. But they should male sure it works rt..if you read all the reviews in playsotre bout this app. Not good at all some stock an locked users r in a bootloop from this updating an their only choice was factory reset. Not good
Click to expand...
Click to collapse
Well I figured out the problem. When I restored it it was indeed solved or so I thought but I noticed the update was still available in the Play Store so I decided to back the original HTC LS in Titanium Backup and update to it. After having updated and rebooting I ended up with the AOSP lockscreen again, restoring the app in Titanium and rebooting again resulted in getting the original back.
Perhaps they intended this? Maybe it's their new lockscreen just with some faults, one being double tap to sleep doesn't work?
S1L3nTShaDoWz said:
Well I figured out the problem. When I restored it it was indeed solved or so I thought but I noticed the update was still available in the Play Store so I decided to back the original HTC LS in Titanium Backup and update to it. After having updated and rebooting I ended up with the AOSP lockscreen again, restoring the app in Titanium and rebooting again resulted in getting the original back.
Perhaps they intended this? Maybe it's their new lockscreen just with some faults, one being double tap to sleep doesn't work?
Click to expand...
Click to collapse
I use greenify to put my device to sleep. Works great just slide up from bottom of phone line you were going to use google search as I don't have that installed so greenify puts phone to sleep I like it.
Hey,
I purchased a used Nexus 5, 32GB edition (I think the model is D821) as my then current phone (a Samsung Galaxy S4) somehow had a magically broken screen after setting it down on a bed. I have since been able to access my old phone, but it isn't usable as a daily handset.
Anyways, wen I first obtained this phone, I wanted to be safe so I unlocked the bootloader, downloaded the necessary tools to use adb/fastboot, wiped the phones storage, and then flashed the latest version 5.0.1 LRX22C. After installing the normal things I had on my old phone and rooting the device, I have noticed that I get an absurdly abnormal amount of force closes. Mainly dealing with the launcher.
On a daily basis, the launcher, and it seems to mainly ONLY be the launcher (either Google Launcher or Nova, it isn't application specific) force close, freeze, or become unresponsive. I can come to this conclusion on the following basis:
1) The launcher screen shows the background, but doesn't show the dock or any of the shortcut/widgets on the launcher
2) All I can see is a black screen and the notification bar/tab. This is sometimes evaded by switching to the recent apps button and then switching back using the home button.
3) It will show the screen with all applications, but won't swipe between home screens.
There is no major physical damage to the device, there is a hairline crack from the previous owner.
I am guessing that I could go through the process of downloading the firmware and reflashing it, but I was wondering if anyone had ideas on how to solve it, besides flashing the device immediately. I don't want to go through the hassle of flashing firmwares and setting up a device again, especially during finals week. The problem is annoying enough that it would make me post this, but not annoying enough to spend an entire afternoon dealing with that and re-configuring applications and such.
Thanks for the help in advance.
slixzen said:
Hey,
I purchased a used Nexus 5, 32GB edition (I think the model is D821) as my then current phone (a Samsung Galaxy S4) somehow had a magically broken screen after setting it down on a bed. I have since been able to access my old phone, but it isn't usable as a daily handset.
Anyways, wen I first obtained this phone, I wanted to be safe so I unlocked the bootloader, downloaded the necessary tools to use adb/fastboot, wiped the phones storage, and then flashed the latest version 5.0.1 LRX22C. After installing the normal things I had on my old phone and rooting the device, I have noticed that I get an absurdly abnormal amount of force closes. Mainly dealing with the launcher.
On a daily basis, the launcher, and it seems to mainly ONLY be the launcher (either Google Launcher or Nova, it isn't application specific) force close, freeze, or become unresponsive. I can come to this conclusion on the following basis:
1) The launcher screen shows the background, but doesn't show the dock or any of the shortcut/widgets on the launcher
2) All I can see is a black screen and the notification bar/tab. This is sometimes evaded by switching to the recent apps button and then switching back using the home button.
3) It will show the screen with all applications, but won't swipe between home screens.
There is no major physical damage to the device, there is a hairline crack from the previous owner.
I am guessing that I could go through the process of downloading the firmware and reflashing it, but I was wondering if anyone had ideas on how to solve it, besides flashing the device immediately. I don't want to go through the hassle of flashing firmwares and setting up a device again, especially during finals week. The problem is annoying enough that it would make me post this, but not annoying enough to spend an entire afternoon dealing with that and re-configuring applications and such.
Thanks for the help in advance.
Click to expand...
Click to collapse
How did you install the stock firmware? Have you tried wiping cache and dalvik cache in recovery? I'd do that first, and if that doesn't work then try dirty flashing the same ROM (you won't lose anything). If you are still having issues after then flash a factory image with fastboot (do NOT use a toolkit). That should fix it.
_MetalHead_ said:
How did you install the stock firmware? Have you tried wiping cache and dalvik cache in recovery? I'd do that first, and if that doesn't work then try dirty flashing the same ROM (you won't lose anything). If you are still having issues after then flash a factory image with fastboot (do NOT use a toolkit). That should fix it.
Click to expand...
Click to collapse
I know this is a very late response.
The initial way that I installed the stock firmware was using fastboot, and installing each .img file separately.
I just re-flashed the factory image again (except for the recovery image), and am waiting for the phone to boot up (it seems like it takes ages for the phone to actually go from fresh install to fully booted), it has been over a 5 minutes now.
But once that is done, I will see what happens. Is there a way to check for bad hardware (I am specifically thinking flash storage)? Maybe that is causing the problem?