Database Users

***noob guide***how to fix nougat random reboots on most roms

Code:
A couple of days ago I saw someone who claims to have a fix for random reboots in custom 5.0+ ROMs and after testing for 3 days till now not even a single auto reboot occurred
Please try it and tell me if it works
The fix is basically changing selinux mode from permissive to enforcing and there's an app for it called "selinux mode changer"
You'll find a link for it below
Note: I'm using Resurrection remix N 5.3.8 with built in selinux mode changer
I'm not a developer and don't know what it does so it's not my fault for anything damaged or any files missing
I accidentally cleared my browser's history and i tried to find the orginal forum to give credit to right people with no luck of finding it
if you know it please put the link in comments
Flashable zip link: [URL="https://drive.google.com/file/d/0B9MaJmh__z8uaUxoMGZISXlFNGs/view?usp=drivesdk"][url]https://drive.google.com/file/d/0B9MaJmh__z8uaUxoMGZISXlFNGs/view?usp=drivesdk[/url][/URL]

https://forum.xda-developers.com/galaxy-tab-2/general/fix-random-reboots-android-lollipop-t3310134
Here's the original post

Please answer this.

Seriously Needing Help
Phone Info - Mi A1
Rom - Resurrection Remix v6.XX OS-8.1.0 November Patch
Magisk v18 stable (used successfully 2 days after updating Magisk from v16 stable with no problem anywhere).
Modules - v4a, aml, dolby, selinux changer, busybox, MiA1 stock cam.
While updating "AML", screen got freezed for more than 5 min so i had to shutdown forcefully. But after restart i lost all installed apps and everything., from everything i mean both internal and external got formated. But that's not only the case. My device Mi A1 keep restarting automatically after few min of starting (it's not bootloop as device restarts to homescreen but freezes and restarts after few sec.). Sorry that i can't provide logcat as everything already formated.
i tried to reflashing using few unofficial and official MI tool (tried both oreo stock and pie latest) but still my device goes to setup screen and after few seconds it restarts automatically.
Isn't there any work around 'coz neither magisk support forum helped nor AML forum.
My only question is whether is this software issue or hardware? Can updating simple module result in hardware failure?
Please reply.

What is wrong with ADB in developers settings in any 9 ROM?

Hi to all v9 users.
I tried several ROMs version 9 from here and found that all of them have the same bug(?) - allowed ADB debug over USB in developers settings is lost after reboot. In both cases - rebooting to the system or, what more important for emergency cases, in recovery.
Also must be mentioned, that immediately after reboot, ADB debug is allowed and the device is visible from PC for several seconds. But when lockscreen will appear - ADB will be lost.
I'm always flash at once ROM+GAPS+Magisk and always have the same result. Even when Magisk is running in MagisCore mode.
What I'm doing wrong if I do? How it can be fixed? How to get constantly present ADB over USB? Wich of existing 9ROMs haven't this bug now?

This does not happens to me. I am on AEX Pie by subham.

PGKiD said:
This does not happens to me. I am on AEX Pie by subham.
Click to expand...
Click to collapse
Tried this one right now. ADB is allowed by default! And not switching off, but... till some moment or event.
So, my path: flashed ROM+GAPS+MAGISK, installed MagiskManager, installed BusyBox Magisk Module, installed LuckyPatcher, block ads and apply 3 android patched, installed Titanium - and it suddenly told me that I must turn on ADB after this moment ADB is permanently lost after reboot.
I understand that the reason may be in some of these apps or conflicts between them. But I used the latest versions and can't refuse any of them (
Looking forward for solution...

Yeah I lost adb debugging every reboot too. But it does not matter to me as I did not consider it to be always on myself.
As extra, I use DevTiles to makes it easier to turn adb debugging.

new Havoc 2.2 from 19.02.2018 correctly working with ADB in rebooting to a system and/or recovery, but, unfortunately, LED is not working. waiting for completely working rom...

Old, but working TWRP
Found old TWRP version 3.2.1-0 which is properly working with ADB in recovery mode and under regular android.
I'm not sure when and where I downloaded it, but it's working well for me.

CrDroid is working great. ADB doesn't reset for me.
And btw this is the wrong section.
Sent from my Lenovo P2 using XDA Labs

sm00th4f3 said:
working great. ADB doesn't reset for me.
Click to expand...
Click to collapse
As I found, it depends on TWRP version and ROM itself. Maybe you are lucky to have working pair )
Allowed ADB may not be lost when you reboot your system. However, there are a lot of cases, when you reboot from system to TWRP and the device becomes invisible for ADB under TWRP ((
Another case that was found - in some ROM device becomes visible via ADB only when in USB settings I chose "Charge only" and disappears when select "File transfer" (or vice versa).
In any case, it's software incompatibility, which can be fixed, bcz on AICP v8 and mentioned above TWRP everything is working fine in any mode. So, still looking forward to completely working pair OS9 and TWRP...

Working TWRP PLEASE?

Hello, it's been a while and the update doesn't fix this issue : the clock/time is TOTALLY off, for example now it shows we're in june 2018.. Is there a version that doesn't have this issue? Also backing up with encryption ALWAYS fail (unless you don't backup data partition so far)..

GoJo ^^ said:
Hello, it's been a while and the update doesn't fix this issue : the clock/time is TOTALLY off, for example now it shows we're in june 2018.. Is there a version that doesn't have this issue? Also backing up with encryption ALWAYS fail (unless you don't backup data partition so far)..
Click to expand...
Click to collapse
Format your internal storage don't set pin at lockscreen use patterns instead also download latest twrp from twrp website BTW wrong section of posting read the forum rules
...goodnight

Not having encryption or pin, that's a solution for you? Not for me!
Sent from my Redmi 3S using Tapatalk

I never had any worries with official version of TWRP. Once the clock is set, it remains .... unless you fully discharge the battery, which is not recommended at all.

You will also try the new Shrp_Land project, it seems very interesting and based on last version of TWRP.

Just tried that SkyHawk TWRP and SAME! The clock is OFF, it's still 2018.. This is not an hardware issue, i have other TWRP that displays time correctly, but sadly have some other (worse) issues so i cannot use. I downloaded my TWRP from official website, there must be a reason the clock is crazy.. Please help me find & fix the problem!

[SOLVED] Patching services.jar causes wifi profiles loss?

Got my phone rooted couple days ago with Magisk (in recovery) and so far its working fine. All green. Yayyy
But when I tried to patch services.jar myself (by having my own magisk module to replace), something weird happened. All wifi profiles reporting "Incorrect password" I have to re-enter the passwords but it always ends up being that after reboot.
I think patching services.jar triggers something that causes the saved data to be corrupted and cannot be decrypted somehow? I think other data like bluetooth paired devices could be corrupted in the same way too.
I tried using the original services.jar without any modifications (just replace the .odex). Still no luck.
Smali Patcher doesnt seems to work on 10. I tried that too.
Im currently on latest stock ROM android 10 in case you wonder.
Any help would be appreciated!

alex.do said:
Got my phone rooted couple days ago with Magisk (in recovery) and so far its working fine. All green. Yayyy
But when I tried to patch services.jar myself (by having my own magisk module to replace), something weird happened. All wifi profiles reporting "Incorrect password" I have to re-enter the passwords but it always ends up being that after reboot.
I think patching services.jar triggers something that causes the saved data to be corrupted and cannot be decrypted somehow? I think other data like bluetooth paired devices could be corrupted in the same way too.
I tried using the original services.jar without any modifications (just replace the .odex). Still no luck.
Smali Patcher doesnt seems to work on 10. I tried that too.
Im currently on latest stock ROM android 10 in case you wonder.
Any help would be appreciated!
Click to expand...
Click to collapse
I had the same issue with wifi, I haven't patched services.jar though, so it's not that. I never re-entered passwords, just rebooting again did the trick. Not 100% sure yet but I think I solved it by wiping dalvik-cache, haven't had the issue since, touch wood

hinxnz said:
I had the same issue with wifi, I haven't patched services.jar though, so it's not that. I never re-entered passwords, just rebooting again did the trick. Not 100% sure yet but I think I solved it by wiping dalvik-cache, haven't had the issue since, touch wood
Click to expand...
Click to collapse
Got it solved!
I followed you to wipe the davik-cache and cache partition also. It didn't help at first. So I went on re-entering the passwords to some recent wifi profiles and tried to reboot. Voilaaaa the wifi seems to be saved properly now. I will check if it still survives after several reboots.
I think my patched services.jar has something to do with secure storage (since I set the isTimaAvailable() to return true always - more details can be found in Smali Patcher project, which does no longer work properly on Android 10) and that causes the old data to be corrupted and you gotta re-enter. I hope I only need to do it once.
Thanks for the tips!