Related
stock recovery, just unlocked and rooted.
superSU said binary need to update, i choose 'normal', then it keep showing the screen as i attached.
remain the same even after reboot.
pls help
Sent from my HTC6435LVW using XDA Premium 4 mobile app
minjiet said:
stock recovery, just unlocked and rooted.
superSU said binary need to update, i choose 'normal', then it keep showing the screen as i attached.
remain the same even after reboot.
pls help
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I would recommend flashing or temporarily booting a custom recovery and then flash the latest version of SuperSu which can be found here in recovery. This should give fix the binary need's to update error your encountering. Let me know if you still have questions.
shimp208 said:
I would recommend flashing or temporarily booting a custom recovery and then flash the latest version of SuperSu which can be found here in recovery. This should give fix the binary need's to update error your encountering. Let me know if you still have questions.
Click to expand...
Click to collapse
how to boot a custom recovery? any link?
minjiet said:
stock recovery, just unlocked and rooted.
superSU said binary need to update, i choose 'normal', then it keep showing the screen as i attached.
remain the same even after reboot.
pls help
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Mine did the same. Then I chose the other option not normal and it installed it automatically through recovery. Before that it might be needed to download twrp recovery from here
http://www.teamw.in/project/twrp2/128. Use Android App Install Method.
I got my nexus 10 yesterday...
did the regular stuff:
fastboot oem unlock followed by fastboot flash recovery ... then i applied SuperSU.1.65 but its not workin > pic below.. any idea folks?
http://tinypic.com/r/2ziocra/5
awyeahh1 said:
I got my nexus 10 yesterday...
did the regular stuff:
fastboot oem unlock followed by fastboot flash recovery ... then i applied SuperSU.1.65 but its not workin > pic below.. any idea folks?
http://tinypic.com/r/2ziocra/5
Click to expand...
Click to collapse
I would recommend flashing SuperSU again in recovery and if that still doesn't work take a look at CF-Auto root which will allow you to gain root access.
shimp208 said:
I would recommend flashing SuperSU again in recovery and if that still doesn't work take a look at CF-Auto root which will allow you to gain root access.
Click to expand...
Click to collapse
thanks for the answer.. I flashed 10x times.. same story... doesn't CF-Auto root flash an old version of supersu which is not compatible with android 4.3 ?
awyeahh1 said:
thanks for the answer.. I flashed 10x times.. same story... doesn't CF-Auto root flash an old version of supersu which is not compatible with android 4.3 ?
Click to expand...
Click to collapse
People have reported that CF-Auto Root works fine with Android 4.3 on the Nexus 10. You can also always update the SuperSU app and binary after successfully rooting with CF-Auto Root.
Thx my prob was solved by appying latest recovery and latest supersu 1.65
Beamed from my Htc kickass Sensation using tapatalk 4.
Same problem here
On starting SuperSU, here’s what I get:
>The SU binary needs to be updated. Continue?
[selected: Continue]
>If you have a custom recovery like TWRP or CWM, that can be used to (try to) install the SU binary. This is recommended for HTC devices. How would you like to install the SU binary? (Normal / TWRP/CWN)
[selected: Normal]
>Installing, please wait
>Installation failed!
As far as I can tell, I can’t install TRWP/CWN because the SuperSU binary is not updated, and I can’t update the the SuperSU binary unless TRWP/CWN is installed. This looks like a vicious circle, can anyone recommend a way out of it please?
Further background:
Device: Evolveo Xtraphone 4.5 Q4, rooted by SRSroot which recognised it as an HTC device.
Also attempted: updating from SD card with UPDATE-SuperSU-v1.86.zip, by running Superuser.apk from the zip folder. This takes me back to square one: “The SU binary needs to be updated. Continue?” etc.
Any recommendations enormously appreciated, thanks!
Hello everyone,
I noticed that this is a common problem and I realize just not that I shouldn't have just updated without informing myself.
Anyway, I checked and the root seems to be gone (checked with Root Checker, although the SU app is still there [but not working]).
I checked the fastbook and it says 'unlocked', which is good, I don't have to lose data.
How do I re-root properly?
I am using OS X at the moment and I have access to adb but, if needed, I can access a Windows computer again and use Nexus Root Toolkit again (that's what I used the first time I rooted).
I have CWM-SuperSU-v0.98.zip and recovery-clockwork-6.0.1.9-manta.img.
I checked the bootloader and it says 'no command' but it still has:
- reboot system now
- apply update from ADB
- wipe data...
- wipe cache...
Thanks in advance for any help
First thing - Nearly always you will lose root after applying an OTA - at least lately so that's not really a big deal.
Second - Get and always use the Latest version of root zip from chainfire: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip
Or you can also just apply SuperSU from google play and you will prompted to reboot to update binaries etc. after you apply the OTA.
His blog on latest version: https://plus.google.com/+Chainfire/posts/QhrEdeJ3nqQ
I got the same problem.
I solved it by just by downgrading and upgrading back to the latest version of Cyanogenmod.
lg Darcade
I have the same problem...
I have the same problem, I have installed the 4.4.3 OTA and now SuperSU stopped working.
Any advice?
Easily got my root back using Wugfresh toolkit.
Only the paid for version of SuperSU - "Pro" will attempt to keep root after an OTA update. It worked perfectly for me on a 5, 7 and 10.
[Lemmy] said:
I have the same problem, I have installed the 4.4.3 OTA and now SuperSU stopped working.
Any advice?
Click to expand...
Click to collapse
Don`t use toolkits, just boot into TWRP in fastboot and reflash the latest superSU.zip and you`re rooted.
gee2012 said:
Don`t use toolkits, just boot into TWRP in fastboot and reflash the latest superSU.zip and you`re rooted.
Click to expand...
Click to collapse
thats what I did by now, just with CWM instead of TWRP.
[Lemmy] said:
thats what I did by now, just with CWM instead of TWRP.
Click to expand...
Click to collapse
Well done mate , toolkits suck and you have no control over them. Flashing with adb gives you full control and you learn something
gee2012 said:
Well done mate , toolkits suck and you have no control over them. Flashing with adb gives you full control and you learn something
Click to expand...
Click to collapse
...after having to go through this over and over again with every single update I'm starting to think that having root is definitely not worth the pain.
If you switch to TWRP using its built in SuperSU install makes re-rooting a breeze.
Sent from my SM-T800 using XDA Premium HD app
Tried twrp, but always says I don't have busybox and says loading, but never does, then on install recov, it DL's, but then comes up with an error: Flashing recovery was unsuccessful.
Gives partition as: /dev/block/bootdevice/by-name/recovery
No such partition on LG Leon LTE (h345, flashed from MPCS to T-Mob h345d, only way to get a working root)
Anyone else having this issue?
SOLVED: had to set "OEM Unlock" to enabled in Developer Options..., DUH!!!
This is off-topic, but as you wrote you've flashed a kdz from other variant: is it safe to try flashing different kdz'd just to try? I have a lot of possibilities, but i have only flashed the one from my country and exact same model and v10a. But it's impossible to root. Thanks!
leandeganis said:
This is off-topic, but as you wrote you've flashed a kdz from other variant: is it safe to try flashing different kdz'd just to try? I have a lot of possibilities, but i have only flashed the one from my country and exact same model and v10a. But it's impossible to root. Thanks!
Click to expand...
Click to collapse
I had to downgrade to an h345d kdz variant in order to get a working root. That worked, but it was a MPCS phone (on Tmo network) flashed to a Tmo kdz. Worked. I'd think if you Sbrick it, you could still re-flash with stock from recov., so not that big a deal.
It's not the only way to get root, I rooted my 10e:
http://forum.xda-developers.com/android/help/android-forums-account-rehost-file-t3211801
zowpow said:
It's not the only way to get root, I rooted my 10e:
http://forum.xda-developers.com/android/help/android-forums-account-rehost-file-t3211801
Click to expand...
Click to collapse
Ive tried that also and didnt work. No root method worked on my rom for h340ar
zowpow said:
It's not the only way to get root, I rooted my 10e:
http://forum.xda-developers.com/android/help/android-forums-account-rehost-file-t3211801
Click to expand...
Click to collapse
I can confirm it works with tmobile lg leon h34510f.
To Tomj2
Can you explain how you got twrp on it? Thanks in advance:good:
Edit: figured it out downloaded the img then used flashify to flash the image. Thanks anyways
http://androidforums.com/threads/twrp-2-8-7-0-ms345-twrp-for-lg-leon-metropcs.922379/
I can confirm this works, I have it on my T-Mobile variant.
bzzybfrm313 said:
I can confirm it works with tmobile lg leon h34510f.
To Tomj2
Can you explain how you got twrp on it? Thanks in advance:good:
Edit: figured it out downloaded the img then used flashify to flash the image. Thanks anyways
Click to expand...
Click to collapse
Yeah, that's how I got it on (the latest "blue" TWRP) to be able to load CM12.1
Working twrp recovery 2.8.7.0 on ms34510f rooted using king root installed twrp with twrp manager and then in terminal emulater command reboot oem-unlock oh and check oem-unlock in developer options but cant seem to install cm12
jmarpel said:
Working twrp recovery 2.8.7.0 on ms34510f rooted using king root installed twrp with twrp manager and then in terminal emulater command reboot oem-unlock oh and check oem-unlock in developer options but cant seem to install cm12
Click to expand...
Click to collapse
Are you using the correct twrp? We've got a basic yellow guy which won't flash cm12 and then we've got a blue guy which does.
Why did you use kingroot though? There are better methods for attaining root on your phone.
ninjasinabag said:
Are you using the correct twrp? We've got a basic yellow guy which won't flash cm12 and then we've got a blue guy which does.
Why did you use kingroot though? There are better methods for attaining root on your phone.
Click to expand...
Click to collapse
I didn't have a working pc and King root worked I tried many others and still it's the only one that works. I think I have the yellow one how do I get the blue?
Rooting LG Leon H34510e
I'm a newbie when it comes to rooting however I successfully rooted my H34510e using KingRoot. I verified root and BusyBox installation using Root Checker Basic. I installed TWRP but found that my device was not supported so, I uninstalled TWRO and installed CWM Rom Manager and that's where I'm at today. I'm looking for a custom rom but am not sure CWM is the right manager for my phone.
leandeganis said:
Ive tried that also and didnt work. No root method worked on my rom for h340ar
Click to expand...
Click to collapse
Take your phone, open your internet browser and go to http://www.kingroot.net/
Download the app, open it, follow the steps and you're root!
I have the same phone H340AR v10a ROM, from Uruguay.
Try that, it worked for me.
About TWRP I tried c50 version of TWRP Team, but it doesn't work.. You install the image and when reboot it shows the android robot opened up and nothing comes up.. I installed the TWRP using the "dd if=/dev/ bla bla bla" command..
Some help it wouldn't be bad.
Thanks!
Can't find OEM unlock
I already activated developer options, but..... CANT FIND IT!
This guide covers ALL Moto G 2015 models (including the G Turbo) that can be bootloader unlocked and have TWRP available, it doesn't matter if it is the XT1540, XT1541, XT1543, etc., the method is identical. In fact, this method will work on all 2015 and 2016 series Moto phones running Marshmallow, including the Moto E, X, G3, G4, and Z.
Please read completely and make sure you understand each step and how to do it, if you don't get something search the thread or ask an open question.
tl;dr version for advanced users: Skip to "How to do it" section
I am writing this tutorial because there are still lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto G3, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover the details of rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread.
Prerequisites:
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: Performing this prerequisite will give you all the tools (fastboot) and drivers needed to continue, and wipe your device, meaning erase all your information and programs. Make sure to backup any important data first. This step will also permanently void your warranty once an unlock code has been issued by Moto, it doesn't matter if you even use it, your warranty is done.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See TWRP for the Moto G 2015 or TWRP for Moto G Turbo.
3) You need a copy of the latest STABLE SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device.
4) Reboot and start TWRP recovery, the method you use to do this doesn't matter (boot or flash).
How to do it:
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
DISCLAIMER: I am not responsible for anything that happens... Your device, your responsibility, no matter what happens... Although all the information here has been tested and is known to work with no issues except where noted, things occasionally can and do go wrong and we cannot foresee every possible scenario or circumstance.
If you need assistance, we need detailed information about what what's going on and what you have tried to do... Please provide details including:
1) Device model number and Android version
2) TWRP version
3) SuperSU version
4) Output of 'cat /data/.supersu' from TWRP terminal
And a copy of recovery.log if possible, and any other pertinent information you can think of. Without specific information there is nothing that I can do to assist you and request for help may be ignored.
Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
EDIT: I no longer own or use this device, but will keep this thread open and will check it periodically for assisting the few people left out there who haven't rooted their Moto G 2015 yet.
Alternate Method
Some users have noted that the above method doesn't seem to work, we don't know why as it seems inconsistent but we can't pin it down specifically to user error, certain model number or build, or anything else, as it works 95% of the time...
But if the above method fails, the alternative is to download and copy to SD card or internal storage SuperSU 2.62-3 ßeta version available here and flash it through TWRP like normal.
After this is complete and boot is verified, update the SuperSU app via the Play Store to the current version, then open the SuperSU app and it should prompt you to update the su binary, go ahead and do that via the "Normal" process and reboot when complete.
can confirm, a simple flash won't work, phone stays on the splash screen, had to type op's command for root to work
Sent from my Nexus 6 using Tapatalk
After successful flashing super su it is not showing in app drawer , should I flash it again
25vikasp said:
After successful flashing super su it is not showing in app drawer , should I flash it again
Click to expand...
Click to collapse
SuperSU should show up in the app drawer after a successful flash.
Make sure you enabled changes to system, did the terminal command, and when you flash the zip for SuperSU watch the recovery log, it should say something about "systemless". If not, please attach a copy of recovery.log file
acejavelin said:
SuperSU should show up in the app drawer after a successful flash.
Make sure you enabled changes to system, did the terminal command, and when you flash the zip for SuperSU watch the recovery log, it should say something about "systemless". If not, please attach a copy of recovery.log file
Click to expand...
Click to collapse
[/QUOTE]
See this.i don't know
25vikasp said:
See this.i don't know
Click to expand...
Click to collapse
Hmm... looks like it patched the boot.img successfully. Try installing the SuperSU app from the Play Store and see if it says the binary is properly installed.
I haven't tried this with the 2.77beta yet, I know it had some changes specifically for the Note 7 because Samsung tried to make it unrootable (but failed), I have been using the latest stable build of 2.76
acejavelin said:
See this.i don't know
Hmm... looks like it patched the boot.img successfully. Try installing the SuperSU app from the Play Store and see if it says the binary is properly installed.
I haven't tried this with the 2.77beta yet, I know it had some changes specifically for the Note 7 because Samsung tried to make it unrootable (but failed), I have been using the latest stable build of 2.76
Click to expand...
Click to collapse
At last solved.that latest super su has some bugs so I just tried below version and now it is showing.thanks mate
Click to expand...
Click to collapse
25vikasp said:
At last solved.that latest super su has some bugs so I just tried below version and now it is showing.thanks mate
Click to expand...
Click to collapse
Thank you... I will update the OP to show that 2.77beta is not compatible.
stuck in Boot screen after flashing SU in My MOTO g TE 6.0.1
Pls help Me
krisbeowolf said:
stuck in Boot screen after flashing SU in My MOTO g TE 6.0.1
Pls help Me
Click to expand...
Click to collapse
Stuck on boot screen is classic case of not being a systemless install. Review your SuperSU version and make sure you entering the terminal command EXACTLY as shown in OP. If entered correctly the SuperSU script will "fix" a standard flash with a systemless one.
Otherwise, please give me more information... What version of SuperSU and TWRP, and recovery.log or a snapshot/pic of the recovery terminal screen after flashing SuperSU.
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Stuck on boot screen is classic case of not being a systemless install. Review your SuperSU version and make sure you entering the terminal command EXACTLY as shown in OP. If entered correctly the SuperSU script will "fix" a standard flash with a systemless one.
Otherwise, please give me more information... What version of SuperSU and TWRP, and recovery.log or a snapshot/pic of the recovery terminal screen after flashing SuperSU.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
Latest version of twrp 3.0.0 r2 and super SuperSU version v2.62-3 recommended one...
krisbeowolf said:
Latest version of twrp 3.0.0 r2 and super SuperSU version v2.62-3 recommended one...
Click to expand...
Click to collapse
Please read the first post in this thread again and get the current stable version. No where do I recommend that version with my procedure, current stable release is 2.76
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Please read the first post in this thread again and get the current stable version. No where do I recommend that version with my procedure, current stable release is 2.76
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
can you give me the link
krisbeowolf said:
can you give me the link
Click to expand...
Click to collapse
Read the first post of this thread, completely, paying attention to prerequisite #3!!! If you are using SuperSU v2.62-3 Beta you are NOT following my instructions for rooting, are you sure you are posting in the correct thread?
acejavelin said:
3) You need a copy of the latest STABLE SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device. As of this posting UPDATE-SuperSU-v2.76-20160630161323.zip is the current stable version.
NOTE: Version 2.77 BETA is intended specifically for the Note 7 and should not be used for rooting Moto devices, in testing it doesn't brick or stop boot, it just doesn't show up or work.
Click to expand...
Click to collapse
How to make backup before unlocking bootloader?
@acejavelin,
I am not rooted, bootloader is not unlocked. I am planning to root my phone. But do you know of anything that can be used to backup my data before unlocking bootloader? If you do know, please tell me about it or maybe provide the link.
Thanks in advance.
sanchith.hegde said:
@acejavelin,
I am not rooted, bootloader is not unlocked. I am planning to root my phone. But do you know of anything that can be used to backup my data before unlocking bootloader? If you do know, please tell me about it or maybe provide the link.
Thanks in advance.
Click to expand...
Click to collapse
Backup photos and videos with Google Photo app, and SMS with SMS Backup & Restore app. All system information should be stored in your Google account along with apps you have installed. You can also use ADB with this method http://www.technipages.com/how-to-backup-your-entire-android-device
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Backup photos and videos with Google Photo app, and SMS with SMS Backup & Restore app. All system information should be stored in your Google account along with apps you have installed. You can also use ADB with this method http://www.technipages.com/how-to-backup-your-entire-android-device
Click to expand...
Click to collapse
Thanks man for your help.
By the way, will ADB work without root?
sanchith.hegde said:
Thanks man for your help.
By the way, will ADB work without root?
Click to expand...
Click to collapse
Yes, just enable it in Developer options.
I absolutely can not get Super User Root, I followed this OP to the letter, I have tried to root, in TWRP Recovery, using the linked SuperSu from both storages ie.. internal storage, and one I placed on my adaptive/portable/ExtSdcard. Went to advanced, terminal typed the "echo.....etc", then flashed, and it says while flashing the Super Su file it's installing "systemless" and looks fine, goes through the whole process tells me to reboot, and then just loads right up no wait, BUT NO Super Su file, tried downloading SuperSu apk from playstore manually, after boot up and it doesn't recognize any root[emoji30]
I have tried this on both allowing the changes at the beginning of recovery, and also not allowing the changes, at the beginning of the recovery, lucky I backed up at first boot of TWRP, which I went into immediately after flashing it via adb/fastboot
I am at a loss, and completely frustrated at this point, any assistance would be so so thankful, thanks
Sent from my MotoG3 using XDA-Developers mobile app
Dear advisors,
Iam using stock samsung note 4 SM-910G. Snapdragon 805. Android 6.0.1. Marshmallow. I need advise on to how to install magisk on my device. Can it be done? Appreciate on a step by step instruction on how do i install it.
I don' think this is the right place for this, but it't not my job to decide.
Anyways, which ROM are you using? Are you on stock TouchWiz?
No roms its just stock. Ive rooted on my note 2 previously but i wanna know how on note 4 but rooting via magisk.
So where do i need to post this question?
Firdhaus81 said:
No roms its just stock. Ive rooted on my note 2 previously but i wanna know how on note 4 but rooting via magisk.
So where do i need to post this question?
Click to expand...
Click to collapse
You should've asked in the Q&A section. Thread moderators will probably move this one as soon as they notice, don't worry, you're a relatively new user so you can't know everything yet.
By the way, you can't root with Magisk, if you're not rooted with other methods, because your bootloader is still locked and neither stock recovery or Odin would allow it. You first need to get root access by using some specific software such as ChainFire Autoroot. There are some guides available, but first you have to search for the zip file on the ChainFire website (link), pay attention to the model and check if Odin is included with the package. If it's not, just do a Google search for a fairly recent version. When you have everything you need, use this guide to root your device (link), just go to the second post for the exact procedure.
Once you're done, use some software to verify root access, then download Flashify from Play Store. Go to the TWRP website and get the latest recovery (version 3.1.1) for your device. N910G codename should be 'trlte', better verify yourself to avoid issues. You can now flash the recovery using Flashify.
You're now at a good point, your device is ready for further steps to get Magisk. I'll post the rest of the procedure as soon as you're ready, I just want to warn you that Magisk could possibly create some issues like app instability or inability to use certain services. I got rid of it after few months and flashed SuperSU instead, which is the better option in my opinion. I've never used it on TouchWiz so I can't tell you anything specific about that, you may want to backup your current ROM into an external MicroSD using TWRP, just in case.
Black Shade said:
You should've asked in the Q&A section. Thread moderators will probably move this one as soon as they notice, don't worry, you're a relatively new user so you can't know everything yet.
By the way, you can't root with Magisk, if you're not rooted with other methods, because your bootloader is still locked and neither stock recovery or Odin would allow it. You first need to get root access by using some specific software such as ChainFire Autoroot. There are some guides available, but first you have to search for the zip file on the ChainFire website (link), pay attention to the model and check if Odin is included with the package. If it's not, just do a Google search for a fairly recent version. When you have everything you need, use this guide to root your device (link), just go to the second post for the exact procedure.
Once you're done, use some software to verify root access, then download Flashify from Play Store. Go to the TWRP website and get the latest recovery (version 3.1.1) for your device. N910G codename should be 'trlte', better verify yourself to avoid issues. You can now flash the recovery using Flashify.
You're now at a good point, your device is ready for further steps to get Magisk. I'll post the rest of the procedure as soon as you're ready, I just want to warn you that Magisk could possibly create some issues like app instability or inability to use certain services. I got rid of it after few months and flashed SuperSU instead, which is the better option in my opinion. I've never used it on TouchWiz so I can't tell you anything specific about that, you may want to backup your current ROM into an external MicroSD using TWRP, just in case.
Click to expand...
Click to collapse
Thank you for the advices. I did root following all those steps u gave me. For rooting i dont have a problem but its only after which when im tryin to install magisk i get error sayin that magisk only works for lollipop. Abit confused there. From my knowledge i knew that to install magisk i need to unroot superSu which i did & kept my twrp custom recovery. But somehow i cant seem to keep the twrp recovery & thats where i cant flash the 13.3v magisk.
Firdhaus81 said:
Thank you for the advices. I did root following all those steps u gave me. For rooting i dont have a problem but its only after which when im tryin to install magisk i get error sayin that magisk only works for lollipop. Abit confused there. From my knowledge i knew that to install magisk i need to unroot superSu which i did & kept my twrp custom recovery. But somehow i cant seem to keep the twrp recovery & thats where i cant flash the 13.3v magisk.
Click to expand...
Click to collapse
As I thought, Magisk won't work with the stock ROM. The main issue here is the kernel, which doesn't allow such modification. ChainFire has found a workaround to bring SuperSU on TouchWiz, but the fact it's not open source doesn't allow Magisk developers to use the same method. The head developer, few months ago, said that he was working on it and he was making some progress, but apparently it's not ready yet. I think it's not worth trying again, it won't work at the moment. I suggest keeping an eye on the thread, in case there are some updates. At the moment, I recommend either using SuperSU (which I recommend anyways), or flashing a different ROM, since deodexed TouchWiz ROMs with H-Vitamin or RAM Kernel do actually support Magisk, I tried myself.
Thread moved to proper section
The thing is ive seen in youtube they do get to root via magisk. I need this as to get my pokemon go workin.. :laugh:
Firdhaus81 said:
The thing is ive seen in youtube they do get to root via magisk. I need this as to get my pokemon go workin.. [emoji23]
Click to expand...
Click to collapse
Black Shade is right about the kernel. Using the wrong kernel will cause the install to fail. I'm on an n910t3, using ramrom v3 kernel, and I'm using magisk 13.3 for Android pay and viper audio. There's an official magisk 13.3 thread on xda somewhere. You should try there as a start.
Sent from my SM-N935S using Tapatalk
Attached my kernel info if u can help to check?
Found working magisk root method note 4 sm-n910g
Hello, I'm unsure if it'll work for you but it did for me.
1. Downloaded latest firmware from sammobile & flashed it to phone. (You can just try and find your current boot.img and skip to step 4)
2. Opened stock ROM zip & md5 file - using 7zip
3. Extracted boot.img
4. Place onto SD-CARD
5. Install Magisk apk
6. Magisk > settings > output format > change to ".tar" file
7. Magisk > patch boot.img
8. Locate "patched boot.img" > flash in Odin AP
Done
Worked for my galaxy note 4 SM-N910G
thanks, followed your instruction and it works for me. now i am able to flash magisk on my stock Note 4 though i had to surf more inform on xda using tar-Tool_Odin3-v3.10.7
Worked for my galaxy note 4 SM-N910G[/QUOTE]
MagiskFan said:
Found working magisk root method note 4 sm-n910g
Hello, I'm unsure if it'll work for you but it did for me.
1. Downloaded latest firmware from sammobile & flashed it to phone. (You can just try and find your current boot.img and skip to step 4)
2. Opened stock ROM zip & md5 file - using 7zip
3. Extracted boot.img
4. Place onto SD-CARD
5. Install Magisk apk
6. Magisk > settings > output format > change to ".tar" file
7. Magisk > patch boot.img
8. Locate "patched boot.img" > flash in Odin AP
Done
Worked for my galaxy note 4 SM-N910G
Click to expand...
Click to collapse
Hi, I know is kind of old post here. Just wanna ask, have you try the latest version of Magisk on your note 4 SM-N910G? New version of magisk does not have the option to choose the output format to ".tar" file.
pippideniro said:
thanks, followed your instruction and it works for me. now i am able to flash magisk on my stock Note 4 though i had to surf more inform on xda using tar-Tool_Odin3-v3.10.7
Worked for my galaxy note 4 SM-N910G
Click to expand...
Click to collapse
[/QUOTE]
Hi, I know is kind of old post here. Just wanna ask, have you try the latest version of Magisk on your note 4 SM-N910G? New version of magisk does not have the option to choose the output format to ".tar" file.
@lhooipg Were you asking to help him, or do you wanna know yourself?
bmwdroid said:
@lhooipg Were you asking to help him, or do you wanna know yourself?
Click to expand...
Click to collapse
I wanna know myself, I am facing the same issue as him. Thank you.