Related
Hello, I've tried to root my phone by various method available but in vain..
After I did it with CF root and Odin, I got security message on the phone when trying to open superSU (unrespond close).
Also, when verify the root access through rood checker, it says wasn't root properly..
Please help..anyone able to do it?
I've already increase my binary count to 2 and knox to 1. :/
See my phone details attached..
Thanks
Cypher_SGN2 said:
Hello, I've tried to root my phone by various method available but in vain..
After I did it with CF root and Odin, I got security message on the phone when trying to open superSU (unrespond close).
Also, when verify the root access through rood checker, it says wasn't root properly..
Please help..anyone able to do it?
I've already increase my binary count to 2 and knox to 1. :/
See my phone details attached..
Thanks
Click to expand...
Click to collapse
As far as it goes I think after rooting it with CFroot you should update the SuperSU from the Playstore.
Success
hagba said:
As far as it goes I think after rooting it with CFroot you should update the SuperSU from the Playstore.
Click to expand...
Click to collapse
nice..I finally succeeded to root my phone!
Going for DN3 rom..
Thanks!
Fail to intall DN3
hagba said:
As far as it goes I think after rooting it with CFroot you should update the SuperSU from the Playstore.
Click to expand...
Click to collapse
Hello, I was trying to update my note 2 with DN3 kitkat rom today.. But didn't work! :/
I rooted the phone. I got correct root access.
Then followed the instruction to flash the ROM.
After reboot, I could hear the welcome sound(new) and saw the samsung animated logo..then it stuck there. I waited for some 15mins, but nothing happened, only the animated samsung logo.
I saw an issue in TWRP.. saying there was a problem with permission. I don't know what was it. I tried to fix permission, but it failed.
After nothing worked, now I am in the process of recovery from kies.
Perhaps I didn't have the right step by step guide; from rooting the phone to flashing it. :/
If someone could please help, would be great!.. I really want to flash my phone for the DN3 custom rom.
Thanks.
Why do you need to root when flashing custom rom? It is already prerooted. You only need recovery.
madman_cro said:
Why do you need to root when flashing custom rom? It is already prerooted. You only need recovery.
Click to expand...
Click to collapse
As per rooting instruction, it is mentioned that the device must be rooted before flashing a custom rom from stock rom.
While installing the recovery the device is rooted or another way that I tried was to root by CFroot first, which was successfully done then I got the super user access to install a recovery like TWRP,,
Cypher_SGN2 said:
As per rooting instruction, it is mentioned that the device must be rooted before flashing a custom rom from stock rom.
While installing the recovery the device is rooted or another way that I tried was to root by CFroot first, which was successfully done then I got the super user access to install a recovery like TWRP,,
Click to expand...
Click to collapse
+1
Sent from my GT-N7100 using XDA Premium 4 mobile app
As far as i know for latest 4.4.2 stock roms,
Try to flash philz advance recovery(md5.tar) through odin & then flash su.zip from recovery.
Done.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Hi, I have a rooted nexus 7 and wanted to run multiple ROMs using Multirom and have and use root access on each of them. I cant figure out a way to do this and would like a little help. My Nexus 7 is running Android 4.4.4 and fully rooted on stock kernel and ROM at the moment. If anyone knows how to enable root on multiple ROMs please help me and let me know how. Thanks!
> Phoenex
Phoenex said:
Hi, I have a rooted nexus 7 and wanted to run multiple ROMs using Multirom and have and use root access on each of them. I cant figure out a way to do this and would like a little help. My Nexus 7 is running Android 4.4.4 and fully rooted on stock kernel and ROM at the moment. If anyone knows how to enable root on multiple ROMs please help me and let me know how. Thanks!
> Phoenex
Click to expand...
Click to collapse
1. Download MultiROM Manager From The Play Store
2. Download the files required. Install Them. (This will install The TWRP recovery)
3. Download A Rom.
4. Reboot Into Recovery Mode->Advanced->MultiROM->Add New Rom
A Delailed Guide Is Available. Just Google "Multirom Nexus 7 XDA"
aniket0317 said:
1. Download MultiROM Manager From The Play Store
2. Download the files required. Install Them. (This will install The TWRP recovery)
3. Download A Rom.
4. Reboot Into Recovery Mode->Advanced->MultiROM->Add New Rom
A Delailed Guide Is Available. Just Google "Multirom Nexus 7 XDA"
Click to expand...
Click to collapse
Thank you for your quick response, I already have MultiROM installed but want root access on the other ROMs. Whenever I boot the other ROMs now most Google applications crash instantly and I can't open them without them crashing again. When I open SuperSU it says that Android versions after 4.3 need to re-root to update binary. How would I update the binary and prevent Google Applications from crashing when opened?
Phoenex said:
Thank you for your quick response, I already have MultiROM installed but want root access on the other ROMs. Whenever I boot the other ROMs now most Google applications crash instantly and I can't open them without them crashing again. When I open SuperSU it says that Android versions after 4.3 need to re-root to update binary. How would I update the binary and prevent Google Applications from crashing when opened?
Click to expand...
Click to collapse
Need more info:
Which ROM?
Which GAPPS?
How did you install them?
Don't Say Thanks.
Press The Thanks Button.
My Devices:
Nexus 7 2013 LTE "DEB"
Stock ROM 4.4.3
Stock Kernel
Build: KUT48L
"Everything's Impossible. Until Someone Does It."
The Dark Knight
Most custom Roms are already rooted. Crashes are not normal. Are you using a patched kernel? Are you choosing to share kernel? Like previous poster said, you need to give more info. You're missing something.
My ROM is just a stock ROM. I am using MultiROM and SuperSU to manage ROMs and root access. Here is a screenshot of my main ROM which is the same one as the secondary. Also, I provided screenshots of SuperSU recognizing MultiROM which I granted access to. I don't see a reason for not having root access on both but I am new to rooting and may have overlooked something. I installed the ROMs and rooted using Nexus Root Toolkit. Let me know if you need more information I would be happy to share.
Why not flash a pre rooted ROM for secondary? And ROM management should be handled in twrp. In twrp select advanced then multirom. You can flash zips for secondary rom there.
I used TWRP to install my secondary ROM. What pre-rooted ROM's would you recommend? I'm looking for some new ROMs to run and I don't know where to start.
Phoenex said:
I used TWRP to install my secondary ROM. What pre-rooted ROM's would you recommend? I'm looking for some new ROMs to run and I don't know where to start.
Click to expand...
Click to collapse
I use PAC ROM for my secondary ROM. I keep rooted stock as my primary, but I plan to swap them soon once I get it set up right.
Cm does not work right in MultiROM for me. Paranoid Android, PAC, Slimroms, etc should be good.
Press Thanks If I Helped You!
Sent from my dead Nexus 7 2013 LTE! ???
Hello!
So, yesterday I somehow got bootloop with the stock .242 rom on which had recovery, root and xposed. Then I just re-flashed the system using flashtool. I was lazy to do the downgrade rooting method, so I rooted it using kingroot and then installed the dualrecovery from NUT. From there, I installed a .270 .zip which I made using PRF creator and also flashed the dualrecovery zip. The rom runs fine, but I don't have root! When I start SuperSU it says that there is no su binary. I can do anything, it just doesn't work. Could someone explain me what the hell is that or what did I do wrong?
Thanks in advance.
Yes, you must install SuperSU with recovery.
Me i do like this for my update :
http://forum.xda-developers.com/son.../root-xperia-z1c-14-5-0-270-unlocked-t3118960
LSI said:
Yes, you must install SuperSU with recovery.
Me i do like this for my update :
http://forum.xda-developers.com/son.../root-xperia-z1c-14-5-0-270-unlocked-t3118960
Click to expand...
Click to collapse
Yes, I found out that I was using a too old supersu.zip. Now it is working.
So I was totally stock on KitKat until yesterday.
I asked a question in the q&a section if the original jellybean root worked on KitKat and nobody seems to know. So I went ahead and rooted anyway. It seems to have worked except:
What works:
1) it boots into clockworkmod recovery
2) in ES file explorer, i was able to flip the switch for root file permission
3) in ES file explorer, after flipping the root permission switch, I was able to edit the build.prop by adding the net.tethering.noprovisioning=true line
4) when I boot into odin/download, it shows the tripped Knox counter and modified status, so I know my root did _something_
What doesn't work:
1) when I try to enable tethering after adding that line to the build.prop, it performs the tethering eligibility check anyway, and won't let me toggle the switch, even with a T-Mobile sim that has a tethering plan on it (its unlocked and works with any sim)
2) SuperSU won't open, and when I use cwm to flash the latest (2.14?) It flashes successfully, then when I reboot and try to open SuperSU it does the same thing and won't open
3) when I try to flash cm12.1, it aborts
4) when I try to flash cm10.1 , it aborts
For 3 and 4 maybe I need a newer version of cwm recovery?
Sooo... ??? Is going on?
-Peter
pcrussell50 said:
So I was totally stock on KitKat until yesterday.
I asked a question in the q&a section if the original jellybean root worked on KitKat and nobody seems to know. So I went ahead and rooted anyway. It seems to have worked except:
What works:
1) it boots into clockworkmod recovery
2) in ES file explorer, i was able to flip the switch for root file permission
3) in ES file explorer, after flipping the root permission switch, I was able to edit the build.prop by adding the net.tethering.noprovisioning=true line
4) when I boot into odin/download, it shows the tripped Knox counter and modified status, so I know my root did _something_
What doesn't work:
1) when I try to enable tethering after adding that line to the build.prop, it performs the tethering eligibility check anyway, and won't let me toggle the switch, even with a T-Mobile sim that has a tethering plan on it (its unlocked and works with any sim)
2) SuperSU won't open, and when I use cwm to flash the latest (2.14?) It flashes successfully, then when I reboot and try to open SuperSU it does the same thing and won't open
3) when I try to flash cm12.1, it aborts
4) when I try to flash cm10.1 , it aborts
For 3 and 4 maybe I need a newer version of cwm recovery?
Sooo... ??? Is going on?
-Peter
Click to expand...
Click to collapse
Well your using an older version of SuperSU, use version 2.46, it's also available in the Google Play Store..
I have i317 on 4.4.2 NE5 completely stock, I've rooted it and installed TWRP
I rooted with CF-AUTO-ROOT by chainfire
Update SuperSU to latest version. (v2.46)
Open an install binary (normal)
Disable Knox (should get stuck on first time) reboot and one rebooted disable Knox again ( this time it should disable)
Then installed TWRP Manager (ROOT) from Google play store.
click model AT&T Note 2 i317
Click on the recovery version of TWRP, which is 2.8.7.0
Install
(You can install CWM, instead by downloading ROM Manager from Google play store)
I personally like TWRP better.
Now your i317 Note 2 is stock rooted with Custom Recovery ( access by complete shutting off phone, hold, power down + home + volume up)
Once with Custom Recovery now you may install any i317 roms or custom kernels
Warning I am NOT responsible for any damage you may cause to your device
This will trip Knox counter 0x1
TouchWiz Based roms (recommend): DN4 rom and DN3 rom (difference is DN4 is Note 4 based and DN3 is Note 3 based.) Kernel (recommend): AGNi pureSTOCK v4.4.5
Non-TouchWiz Based roms (recommend): CyanideL rom and Resurrection Remix rom (both based off of AOSP, CM12.1) both roms are 5.1.1 lollipop. Kernel (recommend): For CyanideL rom- Shift 5.7, For Resurrection Remix rom- AGNi pureCM_11_12+_smdk4x12 v4.4.5
(These roms also need gapp flashed also)
Sent from my SAMSUNG-SM-N910A using Tapatalk
Thanks for the thoughtful, detailed post, mate
Between your advice and my fiddling, I got everything doing what it's supposed to now.
My primary phone now is a Nexus 6 so I had gotten rusty on all the hoops we need to jump through in the Sammy world
pcrussell50 said:
Thanks for the thoughtful, detailed post, mate
Between your advice and my fiddling, I got everything doing what it's supposed to now.
My primary phone now is a Nexus 6 so I had gotten rusty on all the hoops we need to jump through in the Sammy world
Click to expand...
Click to collapse
Your welcome, My primary device is Note 4 with AT&T and sucks only have temp root....
But I do switch from Note 2, and iPhone 4S from time to time. obviously Note 2 is rooted and iPhone 4S is jailbroken.
Sent from my SAMSUNG-SM-N910A using Tapatalk
hey...been here a while...did a quick search, but probably didnt look kard enough...ive always gotten good help here, so thanks in advance. just got a new note 4 through insurance and its on 5.1.1 and i was previously on, well not 5.1.1...so i need to root it. is it hard and could i get a good link? ...and sorry , but thanks again always gottwn good help here
There's actually 3 methods commonly used here with SuperSU superuser. Which applies to you?
1) Stock with Chainfire Auto Root for Note 4 (CFAR) has recently been updated to support Android 5.1 and possibly 6.0 It offers possibility to full un-root and take next OTA update but limits system and recovery to stock using systemless root. It's experimental, patches stock kernel and sort of fragile unless you avoid recovery flashes and mounting system. Custom recovery or mounting system may break the ability to return to OTA for update with full un-root but also, flashing custom recovery may trick you into applying system based SuperSU which would break root by loss of the stock kernel boot and root patch causing boot loop. Even flashing a SuperSU zip package may not help unless also flashing a custom kernel (kernel first). CFAR is not the method to use if wanting custom kernel, flash system mods, unofficial Xposed or custom ROM. You've rooted before so you most likely have your Samsung driver from Samsung mobile support for Note 4 SM-N910P and know to enable USB debugging in Developer mode.
Latest Odin
CFAR-follow OP in thread for instructions if this is best root method.
2) Rooting stock Odex by way of custom recovery and using modified custom kernel with SuperSU for root. It allows for some Odex modifications but not recommended Xposed due to the system .odex extensions making addition of system applications extra work. Have to remove the Wanam unofficial Xposed framework (the one required to use for stock) to install system application mods and reinstall unofficial Xposed. You could still use Odex ROM and Xposed, just use the unofficial Xposed as a finishing touch to your ROM. You could also backup before applying Xposed to restore later if you decide to make a system application change.
TWRP recovery
Beastmode patched kernel
SuperSU 2.52 beta
3) Flashing custom ROMs, usually deodexed which are more friendly with modifications, including Xposed only requires the custom recovery flashed in Odin with latest Odin with auto reboot option unchecked, USB and battery pull 30 seconds after success 0 fail message, and booting into recovery to flash the custom ROM per OP instructions. Watch these stock ROMs for systemless root (SuperSU version greater than 2.52 beta); you may have to swap kernel and SuperSU (together, in that order) if making a change to either.
Knowing what you want to use root for would help but the above may get you started or direct your next question.
Sent from my SM-N920P Note 4 via Tapatalk
i just want to get started with root, so i can get titanium back-up installed and get my apps back,... from there just install an ad blocker and from there that would probably be it
tammyjustin said:
i just want to get started with root, so i can get titanium back-up installed and get my apps back,... from there just install an ad blocker and from there that would probably be it
Click to expand...
Click to collapse
The ad blocker, depending on choice may indicate you should go with method 2 or 3.
Adguard from XDA forum would work with method 1 but only works with the browser in free mode. I know that Adaway webserver wouldn't stay enabled with method 1, systemless root.
You may also consider using FolderMount from Google Play to enable write to sdcard if you keep your titanium backup folders on extSdCard. The app patches /system/bin/sdcard and /system/etc/permissions/platform.xml That app would also suggest method 2 or 3 for root.
Mostly stock your preference? Go with method 2. Only real limitation methods 2 and 3 yield us having to update with Odin or try the return to stock for OTA. In theory, return to stock with method 1 and full un-root may actually fix OTA update if attempt to return to stock and OTA update fails for dm-verity or unauthorized modification. No guarantees though. Rooting means we accept the possibility that we may have to wait for a stock tar to update. Best to wait for confirmation that root is possible and what is required first, anyway.
Edit: the minimum links to root with are end of method 2. The instructions for TWRP flash are actually in method 3. Flash the kernel and SuperSU zip in recovery once TWRP is booted.
Sent from my SM-N920P Note 4 via Tapatalk
yea, i mostly just want toot and stock.. so u suggest method 2...thanks...i hope the instructions are clear cut cayse its been a while since ive rooted, dont want toscrrw up
i use the beast mode kernal?
tammyjustin said:
i use the beast mode kernal?
Click to expand...
Click to collapse
You can choose other kernels for root but Beastmode is closer to stock and easy on battery, IMO.
But yes, starting in Android 5.1.1 for our phone, kernel with root exploit became necessary for root. Flash the kernel then SuperSU zips in TWRP recovery together and boot. Rooted stock.
Sent from my SM-N920P Note 4 via Tapatalk
so i odin... flash twrp, kernal then SU?
tammyjustin said:
so i odin... flash twrp, kernal then SU?
Click to expand...
Click to collapse
Correct. You did mean Odin the TWRP recovery and then in TWRP, flash kernel and SuperSU zips, right?
Sent from my SM-N920P using Tapatalk
correct
samep said:
There's actually 3 methods commonly used here with SuperSU superuser. Which applies to you?
1) Stock with Chainfire Auto Root for Note 4 (CFAR) has recently been updated to support Android 5.1 and possibly 6.0 It offers possibility to full un-root and take next OTA update but limits system and recovery to stock using systemless root. It's experimental, patches stock kernel and sort of fragile unless you avoid recovery flashes and mounting system. Custom recovery or mounting system may break the ability to return to OTA for update with full un-root but also, flashing custom recovery may trick you into applying system based SuperSU which would break root by loss of the stock kernel boot and root patch causing boot loop. Even flashing a SuperSU zip package may not help unless also flashing a custom kernel (kernel first). CFAR is not the method to use if wanting custom kernel, flash system mods, unofficial Xposed or custom ROM. You've rooted before so you most likely have your Samsung driver from Samsung mobile support for Note 4 SM-N910P and know to enable USB debugging in Developer mode.
Latest Odin
CFAR-follow OP in thread for instructions if this is best root method.
2) Rooting stock Odex by way of custom recovery and using modified custom kernel with SuperSU for root. It allows for some Odex modifications but not recommended Xposed due to the system .odex extensions making addition of system applications extra work. Have to remove the Wanam unofficial Xposed framework (the one required to use for stock) to install system application mods and reinstall unofficial Xposed. You could still use Odex ROM and Xposed, just use the unofficial Xposed as a finishing touch to your ROM. You could also backup before applying Xposed to restore later if you decide to make a system application change.
TWRP recovery
Beastmode patched kernel
SuperSU 2.52 beta
3) Flashing custom ROMs, usually deodexed which are more friendly with modifications, including Xposed only requires the custom recovery flashed in Odin with latest Odin with auto reboot option unchecked, USB and battery pull 30 seconds after success 0 fail message, and booting into recovery to flash the custom ROM per OP instructions. Watch these stock ROMs for systemless root (SuperSU version greater than 2.52 beta); you may have to swap kernel and SuperSU (together, in that order) if making a change to either.
Knowing what you want to use root for would help but the above may get you started or direct your next question.
Sent from my SM-N920P Note 4 via Tapatalk
Click to expand...
Click to collapse
I am in kind of an odd position here. For some reason, I can't root my Note 4. I've tried both methods 1 and 2 you listed, but neither works. I am running 5.1.1, bone stock. I've been running the stock ROM for about a month since I got this phone used, upgrading from my old Note 3. This is really odd, considering I've been rooting/flashing ROMS since my first Android phone (HTC Hero) in 2010, and have had Samsung phones the last 4 years and never run into this issue. Currently, my phone shows that the beastmode kernel has been flashed, but SuperSU is not showing up and Root Checker is telling me I am not in fact rooted.
I really just want to root so I can WiFi tether, I don't mind running the stock Touchwiz ROM. It runs smoothly and I've had zero issues. Is my best bet just to Odin a stock .tar and start over? I'm trying to bypass having to backup a bunch of files. Normally CFAR would do the trick. Any suggestions are appreciated. Thanks!
HarrisY said:
I am in kind of an odd position here. For some reason, I can't root my Note 4. I've tried both methods 1 and 2 you listed, but neither works. I am running 5.1.1, bone stock. I've been running the stock ROM for about a month since I got this phone used, upgrading from my old Note 3. This is really odd, considering I've been rooting/flashing ROMS since my first Android phone (HTC Hero) in 2010, and have had Samsung phones the last 4 years and never run into this issue. Currently, my phone shows that the beastmode kernel has been flashed, but SuperSU is not showing up and Root Checker is telling me I am not in fact rooted.
I really just want to root so I can WiFi tether, I don't mind running the stock Touchwiz ROM. It runs smoothly and I've had zero issues. Is my best bet just to Odin a stock .tar and start over? I'm trying to bypass having to backup a bunch of files. Normally CFAR would do the trick. Any suggestions are appreciated. Thanks!
Click to expand...
Click to collapse
Basically, attempting method 2 after method 1 breaks root. If you want method 1, you'd have to start over with Odin.
There are a couple of solutions to get method 2 to work if you're not interested in method 3. Method 3 would be the easier fix though.
Are you interested in some fixes for methods 2?
Sent from my SM-N920P using Tapatalk
samep said:
Basically, attempting method 2 after method 1 breaks root. If you want method 1, you'd have to start over with Odin.
There are a couple of solutions to get method 2 to work if you're not interested in method 3. Method 3 would be the easier fix though.
Are you interested in some fixes for methods 2?
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I did it the other way around. I tried method 2 before method 1. I am definitely open to some fixes. However, if it requires a full wipe, I'd rather just backup and go with Odin/method 1 since I am already familiar with that method. Either way, I appreciate the help.
HarrisY said:
I did it the other way around. I tried method 2 before method 1. I am definitely open to some fixes. However, if it requires a full wipe, I'd rather just backup and go with Odin/method 1 since I am already familiar with that method. Either way, I appreciate the help.
Click to expand...
Click to collapse
Yeah, they're not really that interchangeable as you've discovered. That is why I tried to differentiate the methods to choose a direction and stay the course.
Starting over with method 1 will possibly restore the OTA for update with full un-root. But no guarantee from me. But that's the only way to restore it with that possibility. Using the ##3282# method to get hotspot may break that. I'm not sure but I think flashing the zip in recovery would break that option for two reasons: flashing custom recovery and modifying system. It wouldn't break root, just nullify the reasons to use systemless root when the traditional method is more stable and you have to use Odin to update anyway.
I guess I omitted the hotspot only suggestion should most likely choose method 2? And updated CFAR isn't the traditional system based root we had in KitKat. It's strictly systemless root and experimental as far as Samsung Lollipop is concerned.
Sent from my SM-N920P using Tapatalk