I updated my system to 4.4.2 KitKat ota. Now I can't get my phone to root.. I have tried Odin and chainfire root method and it says pass but it won't root or install SuperSU any help would be greatly appreciated.. Thanks
To root u need to flash a recovery thru odin and then boot to recovery and flash superuser
I was told to flash philz recovery through Odin and check the root option. But I don't see that option! So do I need to flash SuperSU through Odin or recovery?? Thanks for the info..
Sent from my LG-US780 using XDA Premium 4 mobile app
I flashed it through recovery.
You need to Odin recovery of choice (I recommend philz latest) boot into recovery, and flash the SuperSU zip file, boot phone back into system, open supersu (if it force closes go into play store and update it) do necessary updating and disabling knox and viola you're rooted. Hope I helped.
Sent from my Sprint Galaxy s3 rocking Bilgerryan's Wicked X Rom, with the fluidity script, tweaked out with a bunch of Xposed modules, powered by Ktoonsez KT747 Kernel
I did the same thing suggested here and it worked just fine for me. Flashed Philz and then the chainfire root and then got myself the Wicked X rom and Im never going back to stock except for the theme look
Related
I downloaded the latest OTA ATT update and then re-rooted and I cannot get CWM to stick. I unchecked auto reboot in Odin and pulled battery and booted into CWM. Installed superuser and rebooted. Now I can't get into CWM. I keep repeating the above steps but it seems that now anytime I reboot I lose CWM???? Thoughts?? I'm still running stock ROM.
There's something that has to be deleted when you Odin flash recovery. If you don't, it resets to stock when you reboot. Just use ROM manager to flash recovery, or use twrp to get away from stock recovery.
jackryan57 said:
I downloaded the latest OTA ATT update and then re-rooted and I cannot get CWM to stick. I unchecked auto reboot in Odin and pulled battery and booted into CWM. Installed superuser and rebooted. Now I can't get into CWM. I keep repeating the above steps but it seems that now anytime I reboot I lose CWM???? Thoughts?? I'm still running stock ROM.
Click to expand...
Click to collapse
The OTA includes a script that is run every boot and that restores recovery to stock. You can remove that file by installing this zip in your custom recovery: http://forum.xda-developers.com/attachment.php?attachmentid=1366357&d=1349037073. Install your custom recovery using ROM Manager or GooManager, reboot into recovery, install the zip, then reboot.
i am using team win and i did everything in the video but i am rooted but still stock.and when i flash it say failed?
This has been the case since the LG8 update. It has code that will replace the stock recovery if the signature check fails.
You need to follow the Team Epic Root from Recovery method. You flash CWM using Odin but do not reboot. Do a battery pull and boot into CWM. From there you flash the Team Epic Root from Recovery file. This gives you root but also removes the recovery signature check that is replacing the stock recovery.
m20120 said:
This has been the case since the LG8 update. It has code that will replace the stock recovery if the signature check fails.
You need to follow the Team Epic Root from Recovery method. You flash CWM using Odin but do not reboot. Do a battery pull and boot into CWM. From there you flash the Team Epic Root from Recovery file. This gives you root but also removes the recovery signature check that is replacing the stock recovery.
Click to expand...
Click to collapse
i did that one first and it still fail. i will try it again so flash cwm? when i use cwm it starts then say installing aborted
ran into a new problem when i have lbe on my phone restarts and freeze. i have to pull the battery and restore my android back up and not use lbe for my phone to work. is that a known problem?
thanks again i fix the problem. i just us rom manager and flash cm10 from it.
New GS2. Tried GooManager and says recovery installed, but when I reboot, I get the standard recovery. Tried Odin. It said PASS for both TWRP and CW, yet when I try to boot into recovery, I just get stock. What step am I overlooking? Why does it say PASS when it hasn't changed anything?
You need to root first use auto root or exynos exploit app both by chainfire
then install recovery
Sent from my GT-N7105 using Tapatalk 2
Hello friends,
Has Chainfire been updated to root the COK1 update? I am assuming it has, but...
I've tried a fresh download from his site and installation fails every time.
What could I be missing?
Thanks in advance for the help.
UPDATE: I figured out what I did wrong. It started with not reading the updates on how to root stock COK1 after updating. My bad. How do I recover now? After attempting to root the old way with CF_AutoRoot, I am now stuck in a bootloop with no access to Recovery. The only option I have is the Download tool for using ODIN.
Anyone have any ideas?
I think it's important to consider what Chainfire is offering with the recent update to CFAR. It's systemless root and the only purposeful use that applies, IMO, is for those that don't modify system, don't flash mods in recovery and would like to possibly utilize the full un-root option to take a future OTA update.
Chainfire warns that system has to be left alone and not even mounted. You might get away with installing busybox for systemless root but no guarantee that the OTA update will be possible with full un-root.
What makes this possible is the systemless root Chainfire uses. It's not compatible with system based root as we've long used in this forum. Flashing another system based root or system based SuperSU application may actually cause a boot loop. Flashing another kernel afterwards may also cause problems if not undoing the systemless root and flashing another system based SuperSU or su application.
If you didn't flash the stock tar and then latest CFAR to root, the only other method that it's prescribed for is stock ROM with stock kernel. And the fix for issues is to flash ROM with stock kernel and root again. Being that we don't have those around, the stock tar is the only way to get back to flash CFAR. Think of it as a root stock only tool with strict use prescribed. It's not intended for flashing sound mods, unofficial Xposed framework, or custom ROMs. All those will break the OTA update capability of the ROM and Xposed framework shouldn't be used on Odex ROM unless it's the finishing touch on a ROM.
Long post but systemless root requires consideration before using it. It's not for those that frequently flash, try other ROMs and mods and Xposed but for those content to sit at mostly stock updates and wait patiently for updates from Sprint.
I'm not sure why you're having an issue. Bad download or you've tried to flash another kernel or superuser application would be my guess. And the only solution I can think of is to start over with Odin, check your md5 where available and consider if CFAR systemless root fits you or not. You could just consider flashing recovery and custom ROM if you consider CFAR systemless root is not what you want.
If you continue having problems with boot loop, consider Philz CWM recovery and wipe everything but extSdCard and flash a ROM. Or Odin stock tar for stock recovery and factory reset. If using stock tar to recover, use latest Odin 3.10.7 and uncheck the option "auto reboot". When it finishes the flash and shows success, pull USB and battery and boot to recovery and wipe, power down, and Odin stock tar with Odin defaults, letting it auto boot this time.
IIRC, the symptom you describe occurred when flashing the old CFAR on recent updates. Maybe delete all CFAR copies and download again. Then start with the paragraph above.
Sent from my SM-N920P Note 4 via Tapatalk
samep said:
I think it's important to consider what Chainfire is offering with the recent update to CFAR. It's systemless root and the only purposeful use that applies, IMO, is for those that don't modify system, don't flash mods in recovery and would like to possibly utilize the full un-root option to take a future OTA update.
Chainfire warns that system has to be left alone and not even mounted. You might get away with installing busybox for systemless root but no guarantee that the OTA update will be possible with full un-root.
What makes this possible is the systemless root Chainfire uses. It's not compatible with system based root as we've long used in this forum. Flashing another system based root or system based SuperSU application may actually cause a boot loop. Flashing another kernel afterwards may also cause problems if not undoing the systemless root and flashing another system based SuperSU or su application.
If you didn't flash the stock tar and then latest CFAR to root, the only other method that it's prescribed for is stock ROM with stock kernel. And the fix for issues is to flash ROM with stock kernel and root again. Being that we don't have those around, the stock tar is the only way to get back to flash CFAR. Think of it as a root stock only tool with strict use prescribed. It's not intended for flashing sound mods, unofficial Xposed framework, or custom ROMs. All those will break the OTA update capability of the ROM and Xposed framework shouldn't be used on Odex ROM unless it's the finishing touch on a ROM.
Long post but systemless root requires consideration before using it. It's not for those that frequently flash, try other ROMs and mods and Xposed but for those content to sit at mostly stock updates and wait patiently for updates from Sprint.
I'm not sure why you're having an issue. Bad download or you've tried to flash another kernel or superuser application would be my guess. And the only solution I can think of is to start over with Odin, check your md5 where available and consider if CFAR systemless root fits you or not. You could just consider flashing recovery and custom ROM if you consider CFAR systemless root is not what you want.
If you continue having problems with boot loop, consider Philz CWM recovery and wipe everything but extSdCard and flash a ROM. Or Odin stock tar for stock recovery and factory reset. If using stock tar to recover, use latest Odin 3.10.7 and uncheck the option "auto reboot". When it finishes the flash and shows success, pull USB and battery and boot to recovery and wipe, power down, and Odin stock tar with Odin defaults, letting it auto boot this time.
IIRC, the symptom you describe occurred when flashing the old CFAR on recent updates. Maybe delete all CFAR copies and download again. Then start with the paragraph above.
Sent from my SM-N920P Note 4 via Tapatalk
Click to expand...
Click to collapse
This was very helpful information. Thank you for taking the time to write this up
I'm up and running again.
Hello, XDA Developers. I was having some trouble with the TWRP Recovery. I have the latest version of ODIN and I have rooted my Galaxy S6 before and all. I'm running 6.0.1 on the g920p model. When I went to flash the recovery. It said it passed and was successful (I used the AP option). Then when I go to put it in recovery mode, it is the stock recovery and not the custom one. Is there anything I did wrong? I've tried other recoveries but non seemed to work. Also I've tripped my KNOX but I don't know if that affects it. Thanks for your help.
Unless you root your phone, it stock recovery will overwrite TWRP.
Flash TWRP again, but do not allow it to auto-reboot through ODIN. (Uncheck that box.) Reboot into Recovery, then flash SuperSU to gain root. Then reboot and TWRP will be there.
Follow the instructions here: http://forum.xda-developers.com/spr...ide-how-to-root-marshmallow-sm-g920p-t3338694