Currently lineageos are releasing night lies till a stable ROM is reached. Even though lineageos is still on nightlies, still stable enough for daily...
Sorry guys been super busy to check this. I've updated the adb driver, please check it and let me know if its working fine now.
Thanks for keeping...
I'd like to apologize for not being able to reply to many comments as I've been away for a while and busy.
Thank you all for helping each...
I wouldn't recommend a dirty flash as it could bring errors from previous ROMs or cause the previous ROMs to interfere with the new one
This is probably due to drivers not installed properly.
Check @Aqma post #207
So your unable to, install a new os?
If its unlocked, you should be able to flash twrp. Check out my guide for the rest of the steps:...
Sorry guys, I'm away for a little while. I'll try responding as soon as I can. I hope other forum members can help you out while I'm gone
Coz it was out of phase :D no idea tbh. Using Viber with no problems
Just updating should be fine. No need to flash it again. Just clear dalvik and system cache after.
Are you on the latest twrp 3.1?
Try wiping dalvik cache and system cache and try again. There's a new nightly out (410). Try that instead.
Ohh ok. Well are you on lineageos now or still on CM?
If your already able to boot to twrp, you should be fine with just flashing the new nightly...
Last couple of weeks at LineageOS
WRITTEN ON APRIL 4, 2017 BY HARRYYOUD
Welcome to LineageOS’ biweekly review, where we go over changes in the last...
By default you should not have root access unless you flash the SuperSU files. This seems pretty normal
Thanks for the feedback @Aqma
Hope your work-around methods work for others facing similar issues :D
Check steps 2 & 3 on my guide:
Try clearing cache.
If that doesn't work, it might be time to change os since cynomod has shut down and won't be rolling out any new updates
Hmm... Try clearing cache and dalvic before trying to flash again. Let us know if you've managed to solve the issue
Which is are you using?
1st of all you have to disable "update recovery" in developer options so your stock recovery doesn't replace the custom recovery (TWRP).