FORUMS
Post Reply Subscribe to Thread Email Thread

After saferoot, bootloader remains in "Custom" state, unable to take 4.4.2 OTA

29th April 2014, 07:19 AM |#1  
OP Member
Thanks Meter: 5
 
More
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
$ exit
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?
Last edited by fdigl; 29th April 2014 at 07:24 AM. Reason: Additional information was added.
 
 
29th April 2014, 07:40 AM |#2  
Member
Flag PORTLAND
Thanks Meter: 12
 
More
if you have the correct baseband installed, you can do what i did. i tried the exact method you did and i came from me7. it wouldn't work for me. i ended up hooking up my phone to kies and then upgrading through there. i hope that helps!
29th April 2014, 07:44 AM |#3  
OP Member
Thanks Meter: 5
 
More
Thanks, I'll give that a try. I'll post the results.
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes