After saferoot, bootloader remains in "Custom" state, unable to take 4.4.2 OTA
Just as the title says, I have previously used saferoot and had followed all the instructions to remove the root binaries and busybox. The root process worked perfectly fine. I had Xposed Framework and Wanam Xposed installed, but they had been removed successfully prior to proceeding to adb with the following commands:
None of the files could be found, so I proceeded to go into SuperSU>Settings>Unroot. The unroot process seemed to succeed, as I opened Terminal Emulator and found that su was not found. Inspecting the device status (Settings>More>About Phone>Status>Device Status) reveals that the text says "Official" despite the "Custom" image displayed in the bootloader on boot. Every attempt made to update to 4.4.2 has failed, and battery pulling does not seem to be an issue.
Can anyone help me here?
EDIT: I am using a modified hosts file. That's probably what's causing a "Custom" bootloader status, isn't it?
Just as the title says, I have previously used saferoot and had followed all the instructions to remove the root binaries and busybox. The root process worked perfectly fine. I had Xposed Framework and Wanam Xposed installed, but they had been removed successfully prior to proceeding to adb with the following commands:
Code:
$ su
# mount -o remount,rw /system
# rm -f /system/etc/install-recovery-2.sh*
# rm -f /system/xbin/selinuxoff*
# find /system/xbin -type l | xargs rm
# rm /system/xbin/busybox
# mount -o remount,ro /system
# exit
$ exitNone of the files could be found, so I proceeded to go into SuperSU>Settings>Unroot. The unroot process seemed to succeed, as I opened Terminal Emulator and found that su was not found. Inspecting the device status (Settings>More>About Phone>Status>Device Status) reveals that the text says "Official" despite the "Custom" image displayed in the bootloader on boot. Every attempt made to update to 4.4.2 has failed, and battery pulling does not seem to be an issue.
Can anyone help me here?
EDIT: I am using a modified hosts file. That's probably what's causing a "Custom" bootloader status, isn't it?
Last edited:
