I have a situation which I don't believe has ever happened before on Android, as I can't seem to find any info about it.
Here's the story:I rooted my phone with Kingoroot to remove the bloatware, couldn't bring myself to remove it out of fear of breaking something else, was sick of the constant "SE for android has been disabled" errors, and tried to unroot it with Titanium Backup's Unroot thing, and then it proceeded to crash the phone and send it to the Samsung splash screen. I tried to turn it off and on again, and couldn't do that, so I took out the battery and put it back in. It didn't go past the splash screen. I removed the MicroSD card after turning it off and tried to boot it again because I assumed that's where all this root stuff was stored, but that didn't change anything. I'm able to get into the debug menu [the volume up plus power plus home button one], if that's required for anything. How do I fix this?
Here's the story:I rooted my phone with Kingoroot to remove the bloatware, couldn't bring myself to remove it out of fear of breaking something else, was sick of the constant "SE for android has been disabled" errors, and tried to unroot it with Titanium Backup's Unroot thing, and then it proceeded to crash the phone and send it to the Samsung splash screen. I tried to turn it off and on again, and couldn't do that, so I took out the battery and put it back in. It didn't go past the splash screen. I removed the MicroSD card after turning it off and tried to boot it again because I assumed that's where all this root stuff was stored, but that didn't change anything. I'm able to get into the debug menu [the volume up plus power plus home button one], if that's required for anything. How do I fix this?
Facebook
Twitter
Instagram