Hi there,
Yesterday I rooted my A505W (Canadian Variant) and got random reboots like almost every one else. It got so bad, I decided to go back to un rooted stock. Before flashing stock firmware I took a look in build.prop file, hoping I might find something that does not belong there after rooting. And I think I found it. At the very end there is line like this:
ro.expect.recovery_id=0xf1dee4214a6ffec6b8
2cec9a13222d4f34c7fd10000000000000000
000000000
Comment it out to lool like this:
#ro.expect.recovery_id=0xf1dee4214a6ffec6b8
#2cec9a13222d4f34c7fd10000000000000000
#000000000
Wanted to delete it, but it was enough to comment it out whit #
Since last night I don’t have any reboots, it looks like commenting it out did the trick. So try it for yourself an see if it helps.
One more thing, if you need to reboot your device do not do it from Magisk, because it will keep rebooting, just power down and boot with the key combination. As I said since last night I have no random reboots.
Hi there,
Yesterday I rooted my A505W (Canadian Variant) and got random reboots like almost every one else. It got so bad, I decided to go back to un rooted stock. Before flashing stock firmware I took a look in build.prop file, hoping I might find something that does not belong there after rooting. And I think I found it. At the very end there is line like this:
ro.expect.recovery_id=0xf1dee4214a6ffec6b8
2cec9a13222d4f34c7fd10000000000000000
000000000
Comment it out to lool like this:
#ro.expect.recovery_id=0xf1dee4214a6ffec6b8
#2cec9a13222d4f34c7fd10000000000000000
#000000000
Wanted to delete it, but it was enough to comment it out whit #
Since last night I don’t have any reboots, it looks like commenting it out did the trick. So try it for yourself an see if it helps.
One more thing, if you need to reboot your device do not do it from Magisk, because it will keep rebooting, just power down and boot with the key combination. As I said since last night I have no random reboots.
Use "buildprop editor" from play store, open it & select the pen icon on the top right, at the end of the page u will see the line "ro.expect.recovery_id=" put # before that like this "#ro.expect.recovery_id="Was waiting for this
Still running on same rooted rom since friday. Can work with it, but when it turns off its really hard to get it on again.
So i have to make the change of the buil.prop file with a program? Then flash it again? Im not so known with this. Maybe some1 wants to make a video, who wants alot of thanks. (Or more detailed steps)
There's not much of advise I can give you, if you disabled some system apps, bloat, enable them back and freeze one or two at the time and see if it reboots, some xposed modules specially older ones will cause reboot, uninstall it, for example I installed gravity box (P) my phone started rebooting, had to uninstall it and it is OK now. This is trial and error process.
I tried to disable Magisk Hide and restarted from Magisk. Got no random reboots since yesterday. To those who are experiencing random reboots, you may also try this and observe for yourself. TIA.
Hello guys
I try this method but stock on odin Recovery when tryin to flash with magisk_patched.tar and shown a red message in the top of the screen :
custom binary(vbmeta) blocked by ... lock
my bootloader was unlock i mean that toggle in developer option is active and on but still stock in that step
plz help
where is the issue?
Update: So far I am no longer experiencing random reboot. Hopefully it stays like this forever.
Edit: Btw, is there any proper way to edit the build.prop to think it is another device? for example S8 so I can install some apps from galaxy store like smart capture.. Thanks.
the same thing happened to meThanks, i thaught i have to Lock the boatloader due to the video.
I do this (unlock the boatloader)
The error was gone but at the end of the flash progress with odin, stuck in the "RECOVERY" part (shown this word at the white square in odin) and do nothin not fail not pass, stuck for ever*
Juste flashed my SM-A505FN, this is actually working.