My scr44 style cover stopped working after unlocking bootloader, the app for the cover crashes when i close the cover and doesn't start until l clear the app cache. It doesnt crash if i dont give the app permissions. I've tried wiping dalvik. I'm running Androplus kernel v22.
Is it possible and/or any point to locking bootloader after rooting?
I solved it.. deny the permissions when it asks and enable them after.
Related
Currently running 1.5 The Dark Side Rom on my ATRIX. I thought installing a rom would help fix the problems, it didn't... there's about a 5cm thick line on the top half of the screen that doesn't respond, as well, the fingerprint scanner is laggy and unresponsive to the point of unusability, as a less prominent problem, proximity sensing apps and certain tasker scripts stop working after a while ... what's wrong?
Thanks!
Sent from my MB860 using XDA App
Do a full wipe (dalvik, cache, data) with latest recovery, install latest radio and the ROM again.
If you need to, update your bootloader pudding.
And try using the phone without restoring any data with titanium backup.
links:
Recovery - http://forum.xda-developers.com/showthread.php?t=1204500 (ROM MANAGER recovery is good too)
Radio - http://forum.xda-developers.com/showthread.php?t=1163009
ROM - http://forum.xda-developers.com/showthread.php?t=1222108
Pudding - http://forum.xda-developers.com/showthread.php?t=1136261
*Extra FULL WIPE if you want to use: http://forum.xda-developers.com/showpost.php?p=17656035&postcount=5
** After all that make sure you update to latest kernel - http://forum.xda-developers.com/showthread.php?t=1156040
would this help even if i had the problem when i was the bootloader was still locked and i was on stock?
I don't know ... maybe you need to give it back to store for fix.
But if you already unlocked your bootloader, give it a try ...
I have asked a few times on the forum if this could be related to the baseband of my device. Basically what happens is in call, he proximity sensor seems to cause the touchscreen to go haywire. I receive what amounts to phantom button presses. Basically voiding the functionality of the proximity sensor to begin with, the calls get put on hold, muted, dropped or whatever. A new symptom has now appeared, the dreaded black screen bug. When a call gets dropped, screen goes black and nothing but a battery pull solves this. Contacts are suddenly missing and I need to resync to get them back
I have tried many different roms, every single kernel. The only solution I personally can think of, is disabling the proximity sensor altogether. Can anyone tell me which line in the build.prop would disable this?
Its my everyday phone, so this is rather urgent, any help would be appreciated
You need to add either of these 2 lines (not sure which, or if it matters):
gsm.proximity.enable=false
gsm.proximity.enable=0
Oh, and apparently MIUI ROMs have that option in the settings.
I can spend 20 min to try solving this or just give you a clue
Try this:
-install ROM Manager and install the custom recovery for your phone if you already haven't got one
-go into recovery, wipe dalvik cache and cache, and most importantly WIPE DATA...
Now flash the custom rom and wait for it to boot...
Wiping data should delete everything from the old rom, so incompatible data when sw roms will be erased...
Backup your sd apps, contacts trough google servers - do not forget...
Sent from my LG-P500, GingerSnap 2.3 using xda premium !
Left4DeadMW said:
I can spend 20 min to try solving this or just give you a clue
Try this:
-install ROM Manager and install the custom recovery for your phone if you already haven't got one
-go into recovery, wipe dalvik cache and cache, and most importantly WIPE DATA...
Now flash the custom rom and wait for it to boot...
Wiping data should delete everything from the old rom, so incompatible data when sw roms will be erased...
Backup your sd apps, contacts trough google servers - do not forget...
Sent from my LG-P500, GingerSnap 2.3 using xda premium !
Click to expand...
Click to collapse
I usually mount and format /system when i do flash a new rom. Thanks for your reply, but as I stated before, this happens on every rom I have flashed before
All the lock screen options but pin and password are grayed out. The phone won't even let me lock it with a pin or password, it automatically goes back to swipe. They have a message under them that says "disabled by administrator, encryption policy, or credential storage". I've googled and I already cleared all credentials, unchecked everything under device administrators, and made sure SD card and phone encryption was turned off. I also wiped the cache and dalvik cache just to see if it works. The sim card lock is also off. Any advice? I'm stumped
Thanks
Edit: Fixed by flashing a new ROM. This thread can be closed - thanks
Keekers said:
All the lock screen options but pin and password are grayed out. The phone won't even let me lock it with a pin or password, it automatically goes back to swipe. They have a message under them that says "disabled by administrator, encryption policy, or credential storage". I've googled and I already cleared all credentials, unchecked everything under device administrators, and made sure SD card and phone encryption was turned off. I also wiped the cache and dalvik cache just to see if it works. The sim card lock is also off. Any advice? I'm stumped
Thanks
Edit: Fixed by flashing a new ROM. This thread can be closed - thanks
Click to expand...
Click to collapse
I've got the same problem.. but have removed root by reinstalling the stock rom. I've reflashed the stock rom twice through ODIN without any luck. What ROM did you use? Any tips?
GuySmiles said:
I've got the same problem.. but have removed root by reinstalling the stock rom. I've reflashed the stock rom twice through ODIN without any luck. What ROM did you use? Any tips?
Click to expand...
Click to collapse
Is everything else back to stock and acting normal? I am using the ECHOE ROM. That would be such a bummer if you have to reroot to fix the lock options. Did you encrypt and then decrypt just to flip it on and off again?
There are threads containing the changes you have to make to your build prop. Surge1223 had a zip I think to flash.
Not 100% sure but it was like an ro.secure line you had to change.
We had this issue before towelroot using prerooted roms.
Sent from my Verizon NC5 Galaxy S4 w/ GEL and Xposed
Keekers said:
Is everything else back to stock and acting normal? I am using the ECHOE ROM. That would be such a bummer if you have to reroot to fix the lock options. Did you encrypt and then decrypt just to flip it on and off again?
Click to expand...
Click to collapse
I found a fix, as strange as it is. I installed stock ROM NC1 (4.4) first, which finally worked well on my phone and then flashed NE1 (4.4). My knox is showing nothing, so looks like all is well.
I have no idea why I had to flash the original 4.4 before the newer one. Hope this can help someone else as well.
I know there have been a lot of issues for those attempting to pull an update.zip and the entire file becoming corrupted.
I would venture a guess that this is some type of "security" attempt either from Google or Samsung to stop those from doing so.
(Lollipop brings added security features like an activation lock)
I attempted to pull this zip myself and that data was corrupted. But wait! There's more.
Not sure if anyone else has experienced this.
I cleared the cache upon updating to the new software. No issues
Used CF Auto Root to root my device and worked fine. Albiet with normal bugs.
Cleared cache in recovery and device crashed upon booting up.
Hard reset and cleared all and device works fine.
Now to test I cleared the cache after reinstalling NK4, and downloaded the update again.
Cleared cache and everything was fine.
Rooted phone via CF AutoRoot again. Phone working fine.
Cleared cache... Same exact issue again.
So... anyone else see the same issue? Or have any insight on the added security issues.
(I fix phones at said carrier. Internal memo warned us of security issue with activation lock from Google.)
supercholo said:
I know there have been a lot of issues for those attempting to pull an update.zip and the entire file becoming corrupted.
I would venture a guess that this is some type of "security" attempt either from Google or Samsung to stop those from doing so.
(Lollipop brings added security features like an activation lock)
I attempted to pull this zip myself and that data was corrupted. But wait! There's more.
Not sure if anyone else has experienced this.
I cleared the cache upon updating to the new software. No issues
Used CF Auto Root to root my device and worked fine. Albiet with normal bugs.
Cleared cache in recovery and device crashed upon booting up.
Hard reset and cleared all and device works fine.
Now to test I cleared the cache after reinstalling NK4, and downloaded the update again.
Cleared cache and everything was fine.
Rooted phone via CF AutoRoot again. Phone working fine.
Cleared cache... Same exact issue again.
So... anyone else see the same issue? Or have any insight on the added security issues.
(I fix phones at said carrier. Internal memo warned us of security issue with activation lock from Google.)
Click to expand...
Click to collapse
Instead of using cf, just odin twrp and flash supersu. No problems going that route.
Sent from my SM-N900P using XDA Free mobile app
Definitely a good way to go. I only wonder if the added security in Lollipop is causing a lot of these issues.
Sent from my SM-N900P using XDA Free mobile app
Hey guys,
I'm wondering if there is any way to disable the forced factory reset if you go to bootloader via key combo. Picture: www[dot]upload[dot]net/file/d/4686/sgyhu6up_jpg.htm
It's really annoying to reinstall and reverify all apps if I install the latest update of the resurrection remix.
So would be great if someone could give me a hint.
NG
Dr. Console
Dr. Console said:
Hey guys,
I'm wondering if there is any way to disable the forced factory reset if you go to bootloader via key combo. Picture: www[dot]upload[dot]net/file/d/4686/sgyhu6up_jpg.htm
It's really annoying to reinstall and reverify all apps if I install the latest update of the resurrection remix.
So would be great if someone could give me a hint.
NG
Dr. Console
Click to expand...
Click to collapse
First of all, can't view the picture so not 100% sure what you're referring to but I'm pretty sure I know what you're asking about. So, on all LG phones pretty much, when you use the button combo to get to recovery, it comes up factory data reset screen and ask you to select yes or no and you have to select yes two times and are brought to TWRP. If that's what you're referring to, it has nothing to do with RR and everything to do with LGs bootloader. If you have TWRP installed selecting yes does nothing except brings you to TWRP, it does not factory reset anything. Installing an update to RR doesn't reset anything either unless you manually wipe stuff within TWRP. Only thing that sometimes gets affected by installing update is it all ask for super user rights on apps again, but no way around that and it may ask you to set some programs as default again (like if you use a different messaging app instead of stock). So, again, the reset screen is not related to RR but instead the bootloader but did nothing except bring you to TWRP. Installing an update doesn't erase your data or apps unless you manually wipe them within TWRP. If you're doing a dirty flash (just updating) no reason to wipe anything except cache and davlik after it finishes flashing, and then it doesn't erase any apps or data. Only wipe system, data, etc if you're trying to do a clean install. In that case, I recommend using titanium backup to backup and restore all apps and app data.
Hey, thanks for the fast response, and yes the thing with the factory data reset was exactly what I meant.
That when TWRP is installed it doesn't wipes the data is very good to know, I sadly found nearly nothing about this.
So I think the problem is solved with your answer.
Thanks and have a nice weekend.
Dr. Console