Hi there,
I got a brand new Galaxy Note 10.1 this weekend and tried to get my hands dirty on rooting it just yesterday. So I got Odin3, CWM and SuperSU, installed Samsung Kies and thought I were good to go. Unfortunately, after doing what some guides tell me to do, I'm still on official device status.
Before I go into detail: I had to manually edit the Odin3 INI file to force the device NOT to auto reboot after flashing the CWM - the checkboxes in Odin3 were disabled and greyed out. Can someone explain why and if that might be the cause of my problems?
HoPi` said:
Hi there,
I got a brand new Galaxy Note 10.1 this weekend and tried to get my hands dirty on rooting it just yesterday. So I got Odin3, CWM and SuperSU, installed Samsung Kies and thought I were good to go. Unfortunately, after doing what some guides tell me to do, I'm still on official device status.
Before I go into detail: I had to manually edit the Odin3 INI file to force the device NOT to auto reboot after flashing the CWM - the checkboxes in Odin3 were disabled and greyed out. Can someone explain why and if that might be the cause of my problems?
Click to expand...
Click to collapse
Download a clean copy of Odin and install .
Auto Reboot is normal .
Root and Recovery TWRP
http://forum.xda-developers.com/showthread.php?t=1851548
Root and Recovery CWM
http://forum.xda-developers.com/showthread.php?t=1831173
jje
Thanks, but that didn't help either. Auto-Rebooting brings me back to stock, device state official. I tried to install CWM-SuperSU-v0.99.zip manually via CWM, but a reboot later it's still "official" and apps that need root access either run forever ("checking...") or freeze the tablet. But since this is getting off topic, I might be better off asking in other threads.
Thanks anyway!
HoPi` said:
Thanks, but that didn't help either. Auto-Rebooting brings me back to stock, device state official. I tried to install CWM-SuperSU-v0.99.zip manually via CWM, but a reboot later it's still "official" and apps that need root access either run forever ("checking...") or freeze the tablet.
Click to expand...
Click to collapse
Then you are not understanding instructions .
What is your intention .
Root or flash a stock rom .
Root via either method i posted .
Stock rom direct flash tar file via Odin.
ODIN flash is a tar not a zip.
Custom rom via a rooted phone with recovery zip file from ext sd card or sd card .
jje
Come on, the instructions are pretty clear boot in Odin Mode, click a button in Odin, let it restart, finished. The SuperSU zip file is from another guide, where the tar-file didn't include it. So I tried to manually install it via CWM (I think it was 6.0.2.7 or 8), but that didn't work either. Whenever the device reboots, Root Checker Basic runs for a few minutes and says "Sorry, the device does not have proper root access". If it helps, I used this guide:
http://www.android-hilfe.de/root-cu...ly-root-fuer-anfaenger-n8000-n8010-n8020.html
Even though it's in german, the screenshots are pretty obvious.
Sorry never ever seen any method with those sort of instructions.Personally not a clue what they mean .
I have used two methods as posted to root note 4 or 5 times. Rooted standard Samsung phones with cwm and root hundreds of times without any of those instructions.
Even run one standard cwm root via Odin to allow a specific rom install followed by a reroot using TWRP this afternoon .
jje
Sent from my GT-N8010 using xda premium
Thanks to Darkman, I finally got it. The problem was the current firmware update from Samsung. I reflashed with the version from January, followed his tutorial (like I did before - wow, after doing this 3-4 times, it certainly becomes second nature), and BAM, the device is rooted. Thanks anyway JJegan
Hi,
I have a 920T with 5.0.2 android version and I'm having a hell of a time installing TWRP. I root fine verified root and the whole thing is beautiful. Every root app I try says im rooted, titanium backup works fine and super user does as well. So I know i'm rooted correctly.
Now I download TWRP from the market place and set up a recovery, I pick "twrp 2.8.6.0 zeroflte" and go through the steps. Again no problem, says it is set up correctly would you like to go into recovery mode. I say yes and then I get stuck in a boot loop forever, I can't do anything but go into download mode and redo my stock rom which I don't want. My end wish is to get http://forum.xda-developers.com/tmo...ent/rom-xtrestolite-pure-edition-1-0-t3088032 that on my phone as I'd love to bypass selinux which I can't on a stock rom.
I should note I also tried installing TWRP through odin and that boot loopd my phone as well. Am I missing something here? Wrong step? wrong app? wrong something?
bump bump
Hi,
I have a 920T with 5.1.1 android version and I'm having a hell of a time installing TWRP. I root fine verified root and the whole thing is beautiful. Every root app I try says im rooted, titanium backup works fine and super user does as well. So I know i'm rooted correctly.
Now I download TWRP from the market place and set up a recovery, I pick "twrp 2.8.6.0 zeroflte" and go through the steps. Again no problem, says it is set up correctly would you like to go into recovery mode. I say yes and then I get stuck in a boot loop forever, I can't do anything but go into download mode and redo my stock rom which I don't want. My end wish is to get http://forum.xda-developers.com/tmob...n-1-0-t3088032 that on my phone as I'd love to bypass selinux which I can't on a stock rom.
I should note I also tried installing TWRP through odin and that boot loopd my phone as well. Am I missing something here? Wrong step? wrong app? wrong something?
bump bump bump
I own a Samsung Galaxy A5(A500G) and have recently rooted it using the Kingo root app via my PC.After that,I tried to use Flashify app on Google Play store to flash a TWRP recovery.After I installed it,When i restarted my phone, it states 'xxxxxx serodroid not enforcing' or something like that.In the TWRP,I tried to reboot it but it kept pulling back to the TWRP and I could not reboot it to the Android screen.This is not quite bothering me,because I could just flash my Stock ROM(A500GXXU1BPC3_A500GOLC1BPD1_XSP)that I found it on Samobile and I have used it many times to get my soft bricked phone back to normal.The thing is, after I flashed the Stock ROM,IT DID NOT ERASE ANY DATA .Except that i get my back to the unrooted state.Everything is just normal and all my files are intact.I do not know why.Is it just a normal thing,or has it got anything to do with the Kingo Root app?
Please reply.Many thanks.
P.S. I have not installed titanium backup,or a nanodroid backup.
Problem solved,thread closed.
Hi all.
Yesterday I noticed a issue while using greenify, it says "Failed to put Facebook,Snapchat into hibernation." I've never experienced this before. So I thought that it could be about root and downloaded root checker.
I run it an it says "Root access is not properly installed on this device." But when I restart in recovery mode it says that bootloader is still unlocked.
And also some strange things happen. App permissions change randomly etc.
I tried a hard reset this morning, but everything is same.
I don't know much about this root thing. My device is second hand, and it had root when I got the phone.
Edit: I'm using stock rom 6.0.1 MOB30P, and stock recovery
Any help will be appreciated. Thanks.
Flash TWRP in fastboot and then flash the latest supersu through TWRP. Could be an issue of how the phone was rooted.
If you want to keep stock recovery, just use fastboot boot TWRP.img to use it temporarily.
An unlocked bootloader has nothing to do with root as you can have one or both.
Thanks for the replies guys.
I've read that doing a factory reset on Marshmallow can cause to lose the root, maybe this caused my problem.
Actually I don't wanna mess with these things because I don't have any experience before. I'm just using Greenify which requires root, but I've got it working by switching the "non-root" mode.
Will it cause an issue using the device at this situation as a normal user?
And just another question about these random permission changes. Could MOB30P build cause this issue? I haven't had a trouble about it before the July update.