I'm new to rooting and i rooted my phone today. But, when trying to confirm root for an app that needed it to be root it immediatly restarted and gave the security error saying the phone has been flashed with unauthorized software & is locked and i had to flash stock firmware to get out the error. During the time rooting phone nothing went wrong for me. So i'm curious. Is there something i forgot to do that made my phone do that
i have same problem. I´ll tried wit a new rmm by pass
Related
What is up…Question: My Samsung Genex is seems to be unlocked, as I unlocked it with the toolkit and the visual unlock appears during the Google boot. However, Superuser, Busybox and Rom Manager do not recognize the device as unlocked.
With no luck, I have re-rooted the device via toolkit several times.
Any help or direction would be greatly appreciated. Thanks All!
i had this problem just a few days ago, or a similar one. initially i rooted my phone. then i got the OTA update since i was still stock. i accepted the update but never checked root until later and i had lost root. but for whatever reason i could not get back root no matter how much i tried.
i used the superboot one click method, over and over and over, but it kept failing. then one time if finally just worked and rooted. i didnt do anything different. so that's all the experience i can help you with...
Solved. Thanks to the fine folks that created the Galaxy Nexus Toolkit!
how? please explain , im having the same problem
Hi! I've got a Galaxy S4 Mini from US Cellular. The model number is SCH-R890. I had rooted my phone, but my phone had accumulated junk over the year or so I had it, so I booted into (stock) recovery and restored the firmware.
I now have the official/stock firmware on my phone, but I'm unable to root it.
I tried towelroot (kernel version is 3.4 from May 20, 2014,) which is what I originally used to root my phone, but after I installed SuperSU from the Play store, it says it can't find the su binary.
I tried Framaroot, and both exploits failed.
I tried CF Auto Root, and I followed the instructions, but my phone got stuck in a bootloop. I ended up having to boot in to recovery, clearing the cache partition, and rebooting. This got me out of the boot loop, but as a result, I also do not have root.
I think I've provided all relevant information except for the build number, which is KOT49H.R890TYUBNE4. There are no available OTA updates. If there's any other information needed, feel free to ask, and I'll try to provide it.
As I had root on my phone before restoring it, it would be nice to get it back, but if I can't, I guess that's okay too. Any ideas?
I apologize in advance for any engrish/grammatical issues I may have made in this post, I'm a bit tired.
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers. Register an account on XDA for full access.
Stand by
Good luck
I'm rather new to the whole android thing and screwed my phone more than I could hope. When the new firmware version came out I thought I needed to unroot to install it. (I wanted it for the WiFi fixes). After installing it I went to reroot and of course the one click root doesn't work, so after trying to find a new method I tried this: http://forum.xda-developers.com/showpost.php?p=60913483&postcount=23 failing to realize it's for D855. My device is a D852 and is stuck in fastboot now. Attempts to continue give error "Unable to find suitable device tree for device (194/0x00010001/121/0)". Just wondering if there's a way to fix this without losing everything or a way to recover my files before resetting. I don't really care about the root at this point.
I rooted my S4 Mini a while back using Odin and it worked fine. I recently updated my phone to the latest firmware which I think is 4.4.2 and it removed my root access. I tried rooting using Odin but it would not work. My phone model number is SGH-I257M. I looked up how to root for that model and during the Odin phase, it would be stuck on RESET and it wouldn't say PASS hence when I verified for root it failed.
I was also told that rooting using the method for the I9195 would also work. For this one, Odin does say PASS but when the phone reboots, the phone did not install the S4Mini_kit which consisted the SuperU and the BusyBox hence when I verified for root it failed again. I feel as if I tried everything to my knowledge. It would be great if someone could shed some light in what I may be doing wrong.
Thank you
I searched the forums and it looks like running a bootunlocker for this AT&T phone might brick it. Has anyone successfully rooted this variant? Thanks.
scragglejaw said:
I searched the forums and it looks like running a bootunlocker for this AT&T phone might brick it. Has anyone successfully rooted this variant? Thanks.
Click to expand...
Click to collapse
I just got one of these yesterday (I had a t-mobile one before, but the screen broke a week or so ago) and thought it should be just as easy to root and put CWM or TWRP on it and then a custom rom with root, but I have been seeing conflicting information. It seems that there are only temporary ways to root it? Not sure what is different from the N910A and my old N910T, but obviously there must be something.
m374llic4 said:
I just got one of these yesterday (I had a t-mobile one before, but the screen broke a week or so ago) and thought it should be just as easy to root and put CWM or TWRP on it and then a custom rom with root, but I have been seeing conflicting information. It seems that there are only temporary ways to root it? Not sure what is different from the N910A and my old N910T, but obviously there must be something.
Click to expand...
Click to collapse
the n910a is not root able, and has a locked boot loader. the thing is locked down tight. you can get temp root on older version of android, but its buggy.
this is what I came to look for too
Kingroot isn't working at the moment either
And uhh.. since y'all are kinda talking about it.. a boot loader unlock & root are not the same thing..
Boot Loader unlock would be nice too but there are plenty of devices out there stock rooted that still have a locked Boot loader..
Retarded device
I got a developer edition N910V from Samsung so nice having unlocked bootloader but I got a N910A for stupid cheap and when in download mode says custom but doesn't have a lock on boot screen and the damn thing shuts off for no reason. Got the device it was in safe mode I flash with Odin and it has acted strange. I flashed it 3 times and the last time on boot says AT&T upgrade previously it would just show the android and wouldn't go into recovery without showing upgrading. Is there a possibility that the person I got from tried to root caused issues with the device and maybe it's kinda rooted... also can I clone my aboot from my N910V to this device possibly making it a Frankenstein?.....Noticed a thread called AT&T note 4 keeps freezing and rebooting that others are claimin to have the same issue... is this related and the reply about using wakelock has seamed have fixed the issue. Does this mean the processor is going out and can it be fixed? I can't let mu retarded friend use this device like this he will end up doing something and ***** about it continuing to reboot while writing a text. Thank you for your help.