I'm wondering if anyone struggling with Smartlock as hard as I do
I have deodex OC4 rooted! First time I was setting up new device I came from NG3 - ND3 down - Towelroot - OC4 deodex. Smartlock didn't work for me at all (I tried all type of combinations fingertip, pattern, code, pin and trusted devices/places/on-body didn't try trusted voice), really nothing worked! At the same time I had all these options in smartlock menu. I was suspecting that gps works too slow/bad/inaccurate and can't detect trusted location immediately as I try to unlock my S5. So Itried TopNTP app, something went wrong (apparently) and my cell stuck in a bootloop. I had to downgrade to NCA with Odin - Towelroot - OC4 deodex again. But this time I might installed/updated apps differently and trusted devices/trusted voice/trusted places work like a charm with the pattern lock! BUT I don't have "on-body detection" option at all and it's a nice one. Stupid touchwiz and locked bootloader are killing me. Please help!!!
Offtop: I got my old LG G3, loaded Cloudy 2.3 (mostly stock ROM) and all smart-lock options and any combinations work 100% without any issues at all!
Related
OK, I have searched for this, but have not found it in this context. I did a flawless OTA and install of 4.3 on my S4 Active. After install I had an image of an open padlock and the word "custom" show up on a boot screen, Used to get this in the early root days, but not for several month after following some tips elsewhere in these forums.
I also had trouble connecting WiFi unless I rebooted. Whether I needed or not, I did a complete factory restore, which seems to have cleaned up the WiFI thus far, but not the lock/custom situation.
Any ideas or suggestions?
Root, TWRP 3.0.2-3
Problem appeared on: SLICK-S427-ROW_by_SHENGE 6.0 rom
Problem:
notification icons on home screen top bar are gone
quick settings/notification pull down menu (the one with wifi, flashlight, airplane, etc.) on home screen cannot be accessed (neither by swiping down nor by using a Nova Launcher widget)
On the lock screen they both work. On a 5.0.2 rom (miui7_v6.5.26) they both work as well.
I have tried options, different launchers, TWRP factory reset, TWRP full wipe, TWRP format data and flashed several other top 6.0 roms - nothing helped. Even a full format and installing a 6.0 rom that I know worked before!
Cheers.
Same problem
I have exactly the same problem. Even the alarm wont go off because for some reason the notifications dont work. The problem happened when I tried to put in a second SIM and since then I can't get to fix it.
my solution
I probably should have posted this long ago, but forgot. Anyway, here's my issue:
it's the additional security PIN.
I have tried multiple unofficial ROMs for my phone. Some of them had the option of setting an additional security PIN (10+ characters) for situations like SIM card change (anti-theft measures built into the ROM). The problem is, when you later change the ROM to one without such an option, it will somehow "remember" (I guess the info is stored on a different partition or something) that it should ask for the security PIN upon changing SIM cards, but the current ROM lacks this functionality. This is why the phone acts so weird.
The solution for me was: flash a ROM that had this security PIN anti-theft option, enter it and disable it completely. Then you should be able to flash and enjoy whatever ROM you want.
Hope it helps.
EDIT: this could possibly also be achieved by installing an anti-theft apk that has this functionality, but I have not tried that.
Which ROM
Do you remember which ROM has the feature? Cause I cant seem to find one.
I don't quite remember, but most likely it was one of the AOSP LEMONADE family, a Lollipop.
Thank you very much sir, my problem finally got solved. For future reference, the ROM I used is this one: http://www.needrom.com/download/aosp-lemonade-v3/ although I' m sure many more will have the same anti-theft option.
Hey all,
Looking for some assistance here. I apologize in advance for not having specifics on everything, but it's been a couple years since I've needed to do anything with this phone (SM-G900A). I picked it up used a couple years ago and shortly after, I did a NOX unlock and rooted the phone for two reasons - using Titanium Backup and to unlock the WiFi hot spot. I recently noticed that something had happened and my root access wasn't working correctly- guessing from one of the OTA updates that was attempting to occur on my phone. I say attempt, because I don't believe they ever successfully installed since they always seemed to error out. I'm currently on StraightTalk, not an AT&T customer. Something weird was up with it though, because I could never uninstall the Xposed Framework or app, yet Pokémon Go was recognizing it was rooted and blocking my access. I should also mention that I had towelroot running on the phone and it's showing the custom unlocked padlock on startup.
Fast forward to last night- I wanted to return it back to the stock ROM so I did my research, found a couple different tutorials that included the correct ROMs and applied one - G900AUCU1ANCE_G900AATT1ANCE_ATT.zip. After flashing, the phone will not boot and freezes halfway through the swirls around the Samsung logo, then goes blank. The blue notification light also stays lit on the phone.
Thinking it was most likely bootloader related, I found another ROM that included separate AP, BL, CSC files. I attempted to flash the bootloader, which failed and I got the following error on the phone - SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
At any rate, it seems like my boot loader somehow got corrupted or isn't compatible with this ROM, but I was hoping some of you experts out there could provide some answers. At this point my phone is dead, so I'm hoping I can get it restored very soon.
Thanks in advance guys!
The issue identified in this thread (http://forum.xda-developers.com/galaxy-s5/help/g900a-stuck-samsung-logo-black-screen-d-t3050369) seems very similar to mine as well as what's described on this website- http://www.galaxys5update.com/fix-black-screen-with-pulsating-blue-led-on-galaxy-s5-g900a/
I'm seeing the pulsing blue light as well. How do I find the 4.4.4 OA1 Kernel identified in the first link?
Hello,
So my Moto X (1st gen, 2013, XT1058) used to work fine on KitKat but after it auto-updated to Lollipop it started messing up more and more every day. The phone is fully stock and locked. Here's a brief list of problems:
random freezes and crashes of apps and the OS itself
random screen freezes (doesn't respond to touches) or completely blank screen apart from the notification bar, often times nothing help but a reboot
random reboots, "optimizing apps" every so often on boot, especially when on charger
flaky and unreliable WiFi, not connecting when it should or disconnecting at random including when screen goes off (despite having "always on" selected)
GPS would sometimes have difficulty acquiring lock and would lose lock randomly (worked just fine before)
I'm not quite sure what to do at this point. It's the AT&T variant which means the bootloader is not unlockable. It is also updated to the latest OTA (build LPAS23.12-21.7-1) which means no rooting method works, or at least I haven't been able to find any. So I can't get even a temproot. I tried everything I could find, nothing worked and I'm running out of options. I love this phone and I'd like to get it back to working order. I'm wholeheartedly hoping someone here will have some good advice or some resource I haven't tried.
Here's what I tried so far:
multiple factory resets, both from system settings and through recovery
didn't help, works for a while but all the issues reappear soon after
rooting with KingRoot
failed, rooting method not available
rooting using this method
failed (not surprising, it does mention it doesn't work on OTA)
unlocking BL via Moto's official unlock service
device not supported
installing moforoot
failed, mofoverify just quits silently and the phone shows a message about some missing fastboot var
unlocking BL using Sunshine
says the device should be supported but then fails acquiring temproot, the phone just reboots
reflashing stock KitKat from here (file: ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF.xml.zip) via fastboot
failed, OS/BL downgrade not allowed
reflashing stock Lollipop from here (file: ATT_XT1058_5.1.0_LPAS23.12-21.7-1_cid1_CFC.xml.zip) via fastboot
partial success, managed to flash a few parts, however it fails on all relevant partitions (gpt, boot, system), reports "downgrade not allowed" just like with KitKat which is surprising, this version/build should be exactly the same as what's currently on the phone
wiping userdata and cache via fastboot
didn't help
I might have tried some other things/methods too, this is just what I could remember right now.
Again, I'd very much appreciate if someone could help me revive this phone. I enjoyed using it while it was working well and I'd like to get it back to that state. Any help is very much appreciated.
Cheers!
I'm having exactly the same issues on my wife's moto x. The only thing I've been able to do for a temporary fix is to enter stock recovery and clear cache. Is there really no root/custom rom method for this device?
When I rooted my Droid Turbo the wifi stopped working.
I try to turn the WiFi on and it immediately goes back off.
How do I get it running again?
XT1254
It is running version 5.1 with 23.21.44.quark_verizon.verizon.en.US vzw
Build number SU4TL-44
I have flashed the 44 again with no luck.
Any help would be appreciated.
Thanks
LD
Try re-flashing the radio for .44.
You can even try flashing the .49 radio.
There's both ADB and TWRP-flashable versions here:
[Droid Turbo XT1254] Bootloader & Radio Packages (+Unlocked warning removal)
http://forum.xda-developers.com/droid-turbo/development/droid-turbo-xt1254-bootloader-radio-t3259327
Still no worky
Thanks,
I re-flashed and still no worky.
Any other suggestions?
durtschi said:
Thanks,
I re-flashed and still no worky.
Any other suggestions?
Click to expand...
Click to collapse
Maybe flash the full .49 (Lollipop) firmware, maybe flash the 6.0.1 OTA update? Since your bootloader is unlocked you are safe. We have those here available in this forum. Here's the 6.0.1 OTA update:
[OTA] Official Marshmallow build MCG24.251-5
http://forum.xda-developers.com/dro...ota-official-marshmallow-build-mcg24-t3512813
(Do NOT attempt to install that if you have an encryption turned on.)
If those don't work, then it's something hardware related, I would presume. Just unlocking bootloader and "rooting" shouldn't affect anyone's wi-fi capability.
________
Is there SOMETHING ELSE you have installed that might affect Wi-Fi? Some battery save app would turn off and turn on Wi-Fi at different times? Something xPosed module like Smart Network? Some app or setting that is supposed to recognize a GPS location and do a certain action, like connect/disconnect Bluetooth? (But such apps can also control Wi-Fi.) One such app is Tasker, but there are plenty of others. Some people even have a couple of apps like that doing similar tasks and it's easy to have conflicts or just simple human error.
One time I configured my wife's volume control app to turn to "normal" volume at 8am and go silent at 8:30pm. Unfortunately, I accidentally chose 8:30am. (I swear I didn't, but there it was.) For two days, she had totally silent phone except for 30 minutes! And I'm the tech guy in the family.