Related
Pretty much a redundant thread, seeing as everyone is doing it now. (But not before I ported the method from SGS II by Phil 3759 http://forum.xda-developers.com/member.php?u=4666971 )
Still makes interesting reading though.....
Thank you for your feedback and link here
But your post links are broken as you copy pasted and forum shortcuts them
So, original thread here:
http://forum.xda-developers.com/showthread.php?t=1746794
Also linked in my signature
Please, ask questions there, I will not monitor this thread for support, so cannot answer questions
Phil3759 said:
Thank you for your feedback and link here
But your post links are broken as you copy pasted and forum shortcuts them
So, original thread here:
http://forum.xda-developers.com/showthread.php?t=1746794
Also linked in my signature
Please, ask questions there, I will not monitor this thread for support, so cannot answer questions
Click to expand...
Click to collapse
Thank you - (fixed it)
shoey63 said:
Possibly the easiest method yet! (Unless you want to PC Odin custom kernel and use potentially dangerous Triangle away to reset counter and get rid of yellow triangle)
1) Download this file:- http://forum.xda-developers.com/attachment.php?attachmentid=1256643&d=1344771266 (comes from this thread - http://forum.xda-developers.com/showthread.php?t=1746794 Kudos to Phil 3759)
2) Copy to external SD card
3) Reboot into stock recovery and select "apply update from external storage"
4) Select "CWM_Root_SuperSU.0.94-Busybox.1.20.2-S2-signed.zip" and wait for Superuser and Busybox to install
5) Go back and reboot system.
Done! You now have fully rooted stock ICS (works on 4.04). Don't forget you are also on stock kernel so NO WIPING!!!
If u want custom kernel, use mobile Odin afterwards.
(BTW dont forget to open superSU after reboot to update binary)
Click to expand...
Click to collapse
That's not rooting - that's rooting AND installing busybox. Sometimes installing busybox can cause problems on a device.
To root, it's simple:
Go to Chainfire's SuperSU thread
Download the latest "CWM-flashable" version
Put on external SD
Flash from recovery
This WON'T also add busybox which can sometimes cause problems.
The reason this works: With ICS updates for I9100/N7000/I777/probably others, Samsung started permitting ZIPs signed with testkeys to be flashed from recovery.
This does not appear to work on newer devices - fails on N8000/N8013 for example.
Hello,
Does this mean if I do this to my note running N7000DDLR6 (don't if its required to mention this), I'll be able to under-clock it and remove system apps without anything more? and that It will be totally safe?
what precautions need to be taken while doing this and after that?
Regards
Sujai
sujaishukla said:
Hello,
Does this mean if I do this to my note running N7000DDLR6 (don't if its required to mention this), I'll be able to under-clock it and remove system apps without anything more? and that It will be totally safe?
what precautions need to be taken while doing this and after that?
Regards
Sujai
Click to expand...
Click to collapse
Ofcourse not, after rooting you are not safe anymore.
If you delete something vital your phone won't boot anymore.
So only root after reading and understanding what you are doing or intent to do...
Entropy512 said:
That's not rooting - that's rooting AND installing busybox. Sometimes installing busybox can cause problems on a device.
...
This WON'T also add busybox which can sometimes cause problems.
Click to expand...
Click to collapse
It can be true under some circumstances, but:
- Many good applications will not run without busybox installed in /system/xbin. Some can chose to go without them, others no. Until developers start including their busybox under their app folder (like Titanium Backup), there will be no other choice if you do need those applications
- Without busybox, you loose a lot of commands under the terminal console. End users do not care, until they need debugging...
- CWM recovery installs busybox in /sbin, it is even completely built into his recovery. So, every time you have cwm installed, you end up with busybox (Most if not all custom kernels/ROMs are concerned that way, include CF-Root kernels...)
- Installing busybox from a market installer is a real mess while installing it through a recovery script can be fully undone
Entropy512 said:
...
Click to expand...
Click to collapse
I'm sorry, but wasn't the CWM.zip the problem for fast few weeks? How come out of nowhere it's "OK" to install the flashable/temporary CMW and it is the Busybox causing the problem?
Please make it clear - is it the CMW.zip counting as "Unsafe" or it is something else?
Spo0f said:
I'm sorry, but wasn't the CWM.zip the problem for fast few weeks? How come out of nowhere it's "OK" to install the flashable/temporary CMW and it is the Busybox causing the problem?
Please make it clear - is it the CMW.zip counting as "Unsafe" or it is something else?
Click to expand...
Click to collapse
The root methods mentioned above can be done from stock recovery skipping the cwm temporary step
Busybox can cause issues with some applications that rely on a generic busybox copy under /system/xbin
This is caused by the fact that each busybox build can have different valid commands. The application cannot know if the commands it needs are supported unless it is bundled with its own busybox copy. It will rely on the compiler of busybox to implement the commands.
Until now, I never encountered such problems with last busybox, but, it doesn't mean one of your apps will never behave strangely...
This is a problem related to the application its self, not busybox specifically
So to summarize this in clear words for note users it should be:
-Note users can easily get root only by flashing supersu or superuser (CWM flashable zips) through stock rom recovery directly,no need for CWM.ZIP at all.
-Note users can also get root + busybox by flashing CWM.ZIP old safe non touch v 4.x through stock recovery first,then to flash supersu/superuser+busybox zip through the temp CWM 4.
Am i right guys? plz do confirm...
Also what about wiping now through temp CWM4 with ICS rooted stock kernel? is it safe now??
↖(^▽^)↗ Sent from Rego Galaxy Note ↖(^▽^)↗
Entropy512 said:
That's not rooting - that's rooting AND installing busybox....
Click to expand...
Click to collapse
OK thanks, forgot to mention that, I'll amend OP
Already answered
eng.rego said:
So to summarize this in clear words for note users it should be:
-Note users can easily get root only by flashing supersu or superuser (CWM flashable zips) through stock rom recovery directly,no need for CWM.ZIP at all.
-Note users can also get root + busybox by flashing CWM.ZIP old safe non touch v 4.x through stock recovery first,then to flash supersu/superuser+busybox zip through the temp CWM 4.
Am i right guys? plz do confirm...
Also what about wiping now through temp CWM4 with ICS rooted stock kernel? is it safe now??
↖(^▽^)↗ Sent from Rego Galaxy Note ↖(^▽^)↗
Click to expand...
Click to collapse
All is ok, except wipe
I cannot certify it is safe. Entropy512 which is involved in CM dev said it is safe for CWM4. I never tested, cannot confirm
Also, CWM6 is still unknown state on stock kernel, until some dev can confirm it
eng.rego said:
So to summarize this in clear words for note users it should be:
-Note users can easily get root only by flashing supersu or superuser (CWM flashable zips) through stock rom recovery directly,no need for CWM.ZIP at all.
Click to expand...
Click to collapse
Correct.
eng.rego said:
-Note users can also get root + busybox by flashing CWM.ZIP old safe non touch v 4.x through stock recovery first,then to flash supersu/superuser+busybox zip through the temp CWM 4.
Click to expand...
Click to collapse
Haven't tried it that way because it involves an extra unnecessary flash. Anyway best to steer clear of any CWM.zip. I bricked my note wiping on touch version. Why use it if u don't have too?
but ultimately we have to used odin to flash a safe kernel after this proceedure.
can we use this to 'cure' the 'partial root' phenomenon many face after flashing even recent ics custom roms ?
i admit installing busybox from market successfully can be a real pain .....
we need busybox for many things like supercharger script etc etc
some apps wont work if you dont have the upgraded version of bb
Some like to stay on stock Ics kernel because of stability. (only unsafe if wipes are performed on them) If u want custom kernel then obviously mobile odin pro/lite is the way to go. At least this way u dont raise flash counter and then have to use potentially dangerous triangle away app. As far as "partial root" goes - not sure. It will install SuperSU. Just open it to update binary and uninstall any other superuser apps that are already on phone
Sent from my GT-N7000 using xda app-developers app
Let me get this straight:
The "official" root thread for Note [02Feb12]How to Root/Unroot Samsung Galaxy Note + CWM says this:
Using CWM.zip (temporary/Touch recovery)method to root is said to be unsafe by entropy, and till safe release don't use it
Read This http://forum.xda-developers.com/show....php?t=1810954
Click to expand...
Click to collapse
Now there is new release which is CWM 6.
Is the old method safe with the new release?
No need for ANY CWM.zip (safe or not). Just flash file in OP on stock kernel recovery from external sd card. Job done .
Sent from my GT-N7000 using xda app-developers app
Yes... Can confirm this has worked for me... Followed instructions in OP, and copied the Uninstaller to my SD Card in the even that I need to return the phone... Flashed in Stock Recovery, rooted and done..
Thanks a million for this...:good:
New Procedure updating to My this thread in 1 hr ( I am working on it)
http://forum.xda-developers.com/showthread.php?t=1329360
new method based on What Entropy have guided us few post back
No need to use CWM at all
No need to flash SUperSU busybox installer (as Entropy said this can cause problem)
I have a Sprint L720 GS4 that was originally rooted and running CM 10.1 off of the official nightlies. I flashed the new CM 10.2 build for jfltespr posted here : http://forum.xda-developers.com/showthread.php?t=2383143
Aside from a few apps acting weird because of the new way Android 4.3 handles notifications, everything runs pretty smooth. Biggest issue is that I lost root after upgrading. (Focal is bada**, in case anyone was wondering lol. I love having Photosphere on a non-nexus device)
The research I have done trying to solve this says all I should need to do is flash Chainfire's newest SuperSU app (v1.43 at the time of this post) and bingo, you will have root access again because version 1.43 gets around whatever issue Android 4.3 has with root. I have flashed this via CWM recovery and get the error "There is no custom binary installed and SuperSU can't install it, this is a problem. If you just upgraded to 4.3 you must manually re-root." when opening the SuperSU app after the phone reboots, and no root apps like Root Explorer or Adaway work anymore.
I have wiped data, cache, davlik, fixed permissions, re-flashed the CM 10.2 ROM and the 4.3 Gapps, then the re-flashed SuperSU app, fixed permissions again, and still nothing, tried several variations of the above process for several hours. As per procedure from Chainfire's G+ posts on how to do this, I did select 'No' when asked if I wanted to disable stock recovery flash as CWM is rebooting the phone. What am I missing?
BTW, I have no access to computer/laptop ATM, so if there is a way to do this without having to use ODIN or some other rooting tool, that would be great.
Verilin said:
I have a Sprint L720 GS4 that was originally rooted and running CM 10.1 off of the official nightlies. I flashed the new CM 10.2 build for jfltespr posted here : http://forum.xda-developers.com/showthread.php?t=2383143
Aside from a few apps acting weird because of the new way Android 4.3 handles notifications, everything runs pretty smooth. Biggest issue is that I lost root after upgrading. (Focal is bada**, in case anyone was wondering lol. I love having Photosphere on a non-nexus device)
The research I have done trying to solve this says all I should need to do is flash Chainfire's newest SuperSU app (v1.43 at the time of this post) and bingo, you will have root access again because version 1.43 gets around whatever issue Android 4.3 has with root. I have flashed this via CWM recovery and get the error "There is no custom binary installed and SuperSU can't install it, this is a problem. If you just upgraded to 4.3 you must manually re-root." when opening the SuperSU app after the phone reboots, and no root apps like Root Explorer or Adaway work anymore.
I have wiped data, cache, davlik, fixed permissions, re-flashed the CM 10.2 ROM and the 4.3 Gapps, then the re-flashed SuperSU app, fixed permissions again, and still nothing, tried several variations of the above process for several hours. As per procedure from Chainfire's G+ posts on how to do this, I did select 'No' when asked if I wanted to disable stock recovery flash as CWM is rebooting the phone. What am I missing?
BTW, I have no access to computer/laptop ATM, so if there is a way to do this without having to use ODIN or some other rooting tool, that would be great.
Click to expand...
Click to collapse
Roit is now in the setting app under superuser make sure prompt is on then reboot and you'll be fine. It worked for me.
Sent from my SPH-L720 using xda premium
nicotheandroidguy said:
Roit is now in the setting app under superuser make sure prompt is on then reboot and you'll be fine. It worked for me.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
So did that, went to superuser in the settings app, made sure apps had access, made sure prompt was on, everything else looked OK, rebooted. Still getting the 'No custom binary installed' thing with SuperSu and have no root access. Any other ideas?
Verilin said:
So did that, went to superuser in the settings app, made sure apps had access, made sure prompt was on, everything else looked OK, rebooted. Still getting the 'No custom binary installed' thing with SuperSu and have no root access. Any other ideas?
Click to expand...
Click to collapse
Reflash the rom and Gapps you won't loose any apps make sure you don't have any trace of super su then do what I said in the last post.
Sent from my SPH-L720 using xda premium
Couldn't get the supersu app to uninstall so I did a data wipe to get rid of it, re flashed ROM and gapps, went into superuser settings and set them as above. Still no root access via root checker, other root apps also don't work. Any other ideas?
Same issue on Pac-rom 4.3.
Anyone have any more thoughs on this? I know there's a huge movement that thinks Root isn't really needed anymore, but I do it for Adaway and being able to move files I download from internal to SD Card (which file explorers won't do without root for some reason), not to mention having CM on my phone. Lol, I almost can't wrap my head around the fact that I have a custom ROM and a custom recovery but no Root access.
Verilin said:
Anyone have any more thoughs on this? I know there's a huge movement that thinks Root isn't really needed anymore, but I do it for Adaway and being able to move files I download from internal to SD Card (which file explorers won't do without root for some reason), not to mention having CM on my phone. Lol, I almost can't wrap my head around the fact that I have a custom ROM and a custom recovery but no Root access.
Click to expand...
Click to collapse
ES File Explorer will accomplish this file moving without root.
Are you using Odin?
No computer... Answers that.
Do you have goo manager?
If no DOWNLOAD IT.
You may have to flash the recovery file (again. You have to do it two different ways to achieve root) through goo manager.
Goo> Menu> Install Custom Recovery it will ask you if you have custom installed. Select yes and it will freeze up for about 10 seconds and USUALLY reboot into recovery and voila, full and proper root achieved.
Source: I dealt with this for almost 2 days and accidentally figured it out. None of my super apps would work. SuperSU, SuperSU Elite, Superuser, nada.
Sent from my SPH-L720 using Tapatalk 2
Thanks for the suggestion. Downloaded GooManager. The path you specified doesn't exist. It is GooManager>Menu>settings>install OpenRecovreyScript. I tried that path anyway in case you had just accidentially misphrased it. It downloaded a TWRP file, and then did nothing else, didn't reboot. I tried rebooting to recovery directly through the main menu in GooManager, but it gives an error because I don't have root access. I have to manually reboot to recovery. Thankfully (I prefer CWM to TWRP) it didn't install TWRP. I still have CWM and nothing else has changed, still no root access.
Using a file manager when trying to move something from the downloads folder on my internal memory to the SD Card, it says operation failed every time, and in GooManager, I cannot access my SD Card files, only internal memory. I tried to re-flash the ROM via GooManager in case that would get results, but the /extsdcard is not listed and I cannot access the root folder to get to it.
I will try just about any suggestion that anyone throws up here because I am at the end of my rope with this, but doing anything via the settings or through an app is likely not going to work because you have to have root access for these things to function to start with in most cases. I had a similar issue when I first rooted my S4. I carelessly accepted the OTA update on initial activation without thinking about it, then when I went to root it I found out that update added a SETUID RESTRICTION to the kernal, essentially changing how Superuser apps interact with the kernal. I had to track down the original kernal and flash that to remove the SETUID RESTRICTION so SuperUser would work. I have a feeling the solution to this will be along those lines, but in hours of researching the only thing I can find to do is 'Flash SuperSU, it will re-root your phone'.
Is there anyone else that has had this issue with the unofficial nightlies of CM 10.2 linked in the OP where the Chainfire SuperSU workaround for re-rooting doesn't work?
I'm not entirely sure what I did, but my Super SU is working properly now.
Last thing I did was flash a version of Super SU I knew worked pre-4.3 (https://dl.dropboxusercontent.com/s...UHFu_xV9MFXYEd9A8ZltJ8l6RjX2l2QtUcGFlWWA&dl=1). I opened it and it gave me the regular error, so I gave up and decided I'd wait a few days. However, I just checked this thread to see if any other solutions were available, and someone mentioned GooManager, so I opened it and it asked for SU permission, and it was granted. I then opened Super SU and noticed it works properly now.
Sorry if this doesn't help.
PwnCloud said:
I'm not entirely sure what I did, but my Super SU is working properly now.
Last thing I did was flash a version of Super SU I knew worked pre-4.3 (https://dl.dropboxusercontent.com/s...UHFu_xV9MFXYEd9A8ZltJ8l6RjX2l2QtUcGFlWWA&dl=1). I opened it and it gave me the regular error, so I gave up and decided I'd wait a few days. However, I just checked this thread to see if any other solutions were available, and someone mentioned GooManager, so I opened it and it asked for SU permission, and it was granted. I then opened Super SU and noticed it works properly now.
Sorry if this doesn't help.
Click to expand...
Click to collapse
I tried an earlier version of SuperSU, sadly no dice.
nicotheandroidguy said:
Roit is now in the setting app under superuser make sure prompt is on then reboot and you'll be fine. It worked for me.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
So I continued to play with this, and I FINALLY got it to work. The thing is that you actually have to turn it on in two places, in superuser and developer options as well. I had tried that before, but it hadn't worked I think because I also had the SuperSU app on there. so steps I took when I got it to work:
1) Wiped data/cache/davlik (again, uggh, must have been my 7th data wipe in 3 days)
2) Reflashed ROM and Gapps
3) Wiped cache and davlik a second time
4) Fixed permissions
5) When phone rebooted and initial setup was finished, go into settings>superuser>menu>settings>superuser access>apps and adb
6) Activate developer options (tap 7 times on build number in about phone if anyone is still in the dark about that)
7) Settings>developer options>root access>apps and adb
I verified root access after that with root checker. While in developer options, I also turned on USB Debugging, I doubt that had an effect, just noting for thoroughness.
this did it for me:
5) When phone rebooted and initial setup was finished, go into settings>superuser>menu>settings>superuser access>apps and adb
6) Activate developer options (tap 7 times on build number in about phone if anyone is still in the dark about that)
7) Settings>developer options>root access>apps and adb
zxhian said:
this did it for me:
5) When phone rebooted and initial setup was finished, go into settings>superuser>menu>settings>superuser access>apps and adb
6) Activate developer options (tap 7 times on build number in about phone if anyone is still in the dark about that)
7) Settings>developer options>root access>apps and adb
Click to expand...
Click to collapse
Ah yes, I realized I did that too, didn't think it had an effect though.
zxhian said:
this did it for me:
5) When phone rebooted and initial setup was finished, go into settings>superuser>menu>settings>superuser access>apps and adb
6) Activate developer options (tap 7 times on build number in about phone if anyone is still in the dark about that)
7) Settings>developer options>root access>apps and adb
Click to expand...
Click to collapse
Worked for me
zxhian said:
this did it for me:
7) Settings>developer options>root access>apps and adb
Click to expand...
Click to collapse
Since I did no data wipe, this was all I had to do - switching from root access "apps" to "apps & adb" Thanks for the hint :good:
Fixing root for me was just going into recovery and fix permissions then reboot and boom I got root
I'm on PACman 4.3 and I don't manage to have a working SuperSU...
I flashed it twice from TWRP (SuperSU update v1.65).
I put apps & ADB in SuperUser menu + in Developer Options
I fixed permissions via TWRP
It doesn't still work... When I open TricksterMOD a pop up shows up "Trickster Mod needs a rooted device and root access"...
I had a few wks a while back where I was computer-less. I used a friend's pc and slapped Odin and a few unzipped rom tars, cf-auto root. ..etc on a sdcard.. I did this so that if I had an issue I could quickly fix my phone from anywhere on anyone's pc.. Just a suggestion for anyone who doesn't have access to a computer...?
Sent from my SPH-L720 using Tapatalk 4
Can someone point me to a simple guide please text or YouTube
I have latest version of Android on tf300 and I have unlocked the device using apk file
Thanks
Sent from my GT-I9100 using XDA Premium 4 mobile app
wakkaday said:
Can someone point me to a simple guide please text or YouTube
I have latest version of Android on tf300 and I have unlocked the device using apk file
Thanks
Sent from my GT-I9100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not a guide, but two simple steps would be to:
1) Root your tab, if you are not already rooted. Motochopper works for this. Plenty of info on motochopper on this forum.
2) Easy way to install CWM (although I prefer TWRP) is to download the app Goomanager. From there you can download CWM and install it. You will probably need busybox installed also, which you can download from the play store and install yourself. If you prefer TWRP an easy way to install that is to download the app System Tuner. Google how to install TWRP via Terminal Emulator. There are guides on how to do this. Pretty easy. I don't have handy links but google is your friend.
3) Alternatives are to use ADB to install/flash CWM or TWRP. If you used motochopper you should know how to use ADB. I couldn't get TWRP to work via ADB for some reason on this particular tf300, so I installed TWRP via Terminal Emulator (using the terminal emulator that the app System Tuner comes with). That worked, and was fairly easy and straightforward.
Good luck.
i never get a USB icon (as your instructions state). The only icons I see are RCK, Android and Wipe Data.
i have tried motochoper but it doesnt seem to work although it says it exists.. when i ran it multiple times. i downloaded rootchecker and it says its not rooted.
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.
Hello. I have a Samsung Galaxy Tab 4 (SM-T230NU) and I am having trouble finding a way to root it. I tried using the KingRoot app and it lied and said my device was rooted and all it did was modify system and make itself system administrator. So I had to reset and flash my device to fix it. So right now I am trying to install a custom rom but I need to find a working way to root it first. Does anyone know a method that I can use that works?
Malitahj said:
Hello. I have a Samsung Galaxy Tab 4 (SM-T230NU) and I am having trouble finding a way to root it. I tried using the KingRoot app and it lied and said my device was rooted and all it did was modify system and make itself system administrator. So I had to reset and flash my device to fix it. So right now I am trying to install a custom rom but I need to find a working way to root it first. Does anyone know a method that I can use that works?
Click to expand...
Click to collapse
YES, THERE IS ROOT FOR SM-T230NU (Samsung Tab 4 7'').
Follow this link (Thanks to the bloger "FlexiSPY" https://blog.flexispy.com/how-to-root-the-samsung-galaxy-tab-4-sm-t230nu/
There's few easy steps to do it:
-Download device USB drivers
-Download Odin
-Download TWRP/SU Tar zip file (all of the above provided in original post)
Flash tar in AP/PDA mode with tablet in download mode
Reboot in Recovery (TWRP)
Select reboot in system and accept installing SU file
Once in System, update/install SU and restart.
Any questions, let me know. Just rooted mine.