Database Info

Marshmallow 6.0 root (WIP) released (by Chainfire, of course!)

Just thought id point it out if no one has posted yet, but in the link provided, chainfire has included root for nexus player (fugu) as well.
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
obviously its a work in progress, but apparently doesnt require a custom kernel?

Finally got home and attempted to root, over and over again. Keep getting boot loop the moment I try to install supersu via twrp. Ugh.
Anyone else have any luck?

unvaluablespace said:
Finally got home and attempted to root, over and over again. Keep getting boot loop the moment I try to install supersu via twrp. Ugh.
Anyone else have any luck?
Click to expand...
Click to collapse
Same over here.

Boot loop here as well.

well then im sorry to have jumped the gun fellas. i was at work when i found chainfires root. Can anyone contact him to let him know root on nexus player doesnt seem to be working?
has anyone had success yet?

Chainfie Is The Best On The Planet
unvaluablespace said:
well then im sorry to have jumped the gun fellas. i was at work when i found chainfires root. Can anyone contact him to let him know root on nexus player doesnt seem to be working?
has anyone had success yet?
Click to expand...
Click to collapse
I experienced the very same thing as you guys. Chainfire is the best on the planet when it comes to rooting all Android devices. He will have this issue fixed fast.
I'm just going to wait on the Chainfire Nexus TV Player M6 root version, maybe Ethernet will work with his root.

Sorry guys, it seems I broke x86-32 support on KitKat+ in v2.50.
New v2.51 BETA posted here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
New Fugu boot.img posted here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344

Chainfire said:
Sorry guys, it seems I broke x86-32 support on KitKat+ in v2.50.
New v2.51 BETA posted here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
New Fugu boot.img posted here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Click to expand...
Click to collapse
Thanks Chainfire for your fast response fixing the boot.img and giving us a new SuperUser v251 Beta.

Works Like A Charm With Ethernet Pass Through
The above new rooting files by Chainfire works like a charm with Ethernet pass through. Chainfire you are the man!
Ok guys, it's safe to go back into the water again! Again thanks a million Chainfire.

Chainfire said:
Sorry guys, it seems I broke x86-32 support on KitKat+ in v2.50.
New v2.51 BETA posted here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
New Fugu boot.img posted here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Click to expand...
Click to collapse
I will follow your suggestion and i will build a selinux enforced boot image for my next firmware full android 6 for Nexus Player.
I want know, if possible, apart security stuff, why you suggest to maintain the enforced mode.
Is just question of security, or you suggest the enforced mode also for others future problems that can happen to the firmware and apps.
In others words, in Android 6, Selinux in permissive mode can create problems to the normal execution of the android framework and Google stuff ?
p.s.
The new init of Android 6 don't permit Selinux Permissive for release firmwares ( not problem for user-debug and eng builds ) so to have a fast root i swapped the original init with TWRP init and repacked the boot.img
Just to have a simple root method, before your instruction on the selinux stuff and before a complete custom firmware.
Just a way to have root in the same moment that Google published the stock firmware. Nothing special.

For those that don't have an otg to connect a mouse or keyboard, I was able to flash the modified kernel via fastboot and the cm recovery used for cm 12.1. I saved SuperSU to my device and flashed the zip with cm recovery and gained root.
Sent from my Nexus 6 using Tapatalk

Worked perfectly for me. Thanks!
Sent from my XT1096 using Tapatalk

followed Chainfire's instruction. on his thread http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Flashed fugu-mra58k factory> load up and put beta-supersu-2.51.zip > bootloader > flash fugu-mra58k-boot.zip from CF> flash twrp > recovery > installed beta-supersu-2.51.zip > profit.
Much thanks to CF for his work.

No Binaries in SuperSu
I can't get the Binaries in SuperSU to install. Can someone point me in the right direction?

very helpful
payazo915 said:
For those that don't have an otg to connect a mouse or keyboard, I was able to flash the modified kernel via fastboot and the cm recovery used for cm 12.1. I saved SuperSU to my device and flashed the zip with cm recovery and gained root.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
thanks, after doing my research i found your post and now i have my new NP rooted and running Android M , Thanks as well to Chainfire for his Boot wich allow us to do this.

A lot of us got the 6.0 update forced on us and aren't happy with it. With root and custom recovery, we should be able to revert back to 5.1.1 and a lot of our issues would be resolved. I would love to implement this root method on my Nexus player, but the instructions are not put in a way that I can understand. Can anyone put this in easier terms and comment on a possible downgrade? I was wondering why a thread like this wasn't on the first page or sticky'd. Please help! Marshmallow on Nexus player is a pain without root and the Marshmallow update came only a few days after I got my Nexus player so I really want to get this thing back to the version it came from the store with it(when it worked perfectly and I could root it easier).

I'm having some trouble with gaining root for marshmallow ... I flashed the newest image for NP the MRA58N build and tried following chainfire method: flashed the modified boot, twrp recovery and finally latest su zip 2.56
No dice ... I then tried to flash MRA58K and follow same steps but again ... not able to get root
Any suggestion?
Sent from my 1+1 using Tapatalk

Which TWRP Ghost or Obake? Unlocked Droid mini su4-21

Unlocked with sunshine, going to install twrp.
What will twrp change? will it change the 4.4.4 that Im on? I want to keep that. I simply want root, thats it, everything else is fine. Ive read all I need to do is install twrp and than flaah superSU. Is that correct? Root junky came up on a google and his site has
twrp-2.6.3.1-Obake-4.4.img
I found this twrp here at xda
openrecovery-twrp-2.8.4.0-obake.img
Someone please educate me on the different options
Thanks

doitinthedirt said:
Unlocked with sunshine, going to install twrp.
What will twrp change? will it change the 4.4.4 that Im on? I want to keep that. I simply want root, thats it, everything else is fine. Ive read all I need to do is install twrp and than flaah superSU. Is that correct? Root junky came up on a google and his site has
twrp-2.6.3.1-Obake-4.4.img
I found this twrp here at xda
openrecovery-twrp-2.8.4.0-obake.img
Someone please educate me on the different options
Thanks
Click to expand...
Click to collapse
Either twrp should work fine personally I would go with the latest version from XDA. Second no it will not change your operating system it just changes your recovery on the phone so you can flash Roms seamlessly. But once installed and in twrp the first thing it will ask is if you want to root system just Swype the bar and it will root if that's all you want then just reboot phone after that and your done.

Thanks, one more question, regarding superSU, do I need that after installing TWRP? I'm sure it's on my moto x that I rooted a couple years ago with slap my moto, been a couple years since I used the ADB on the pc but I'm sure I won't have a problem with this, just don't understand everything yet LOL
Thanks again.

doitinthedirt said:
Thanks, one more question, regarding superSU, do I need that after installing TWRP? I'm sure it's on my moto x that I rooted a couple years ago with slap my moto, been a couple years since I used the ADB on the pc but I'm sure I won't have a problem with this, just don't understand everything yet LOL
Thanks again.
Click to expand...
Click to collapse
Yes you will if it's not there automatically after twrp then just download the app from the play store and update binaries if needed via normal method

Hi all! Been a very busy year, the mini is still new and on 4.4.4 and 4.21, screen of the system http://s8.postimg.org/xkndt6ubp/Screenshot_2016_04_04_23_57_49.png
I unlocked it last year with sunshine, just never had the chance to install TWRP, its my moms phone and it hasnt moved in a year and a half, she has been happy with her razrM, until now. So going to install a custom rom for the first time.. can someone point me to the page where I can download TWRP and anything I need to attemp my very first install, thank you!!

Im getting a dead end, this is all I get. If anyone has an idea what I am doing wrong I would appreciate help. Thanks

doitinthedirt said:
Im getting a dead end, this is all I get. If anyone has an idea what I am doing wrong I would appreciate help. Thanks
Click to expand...
Click to collapse
Answered your new thread, but if you're trying to reboot to recovery, you should try:
fastboot reboot recovery
Since you're at the bootloader, you can also use the [VOL] buttons to select "Recovery" and go from there too.

ok, thanks, my first time trying to install TWRP, I didnt know had to boot recovery, i just did what I read the thread here on how to install it. What does TWRP look like? All I get is boot up that looks normal and nothing indicating a change has even occurred. If I boot recovery will TWRP boot?

I called my mom and asked her to hold the power and down volume buttons in and see what happens... she figured it out. she snapped this picture of it and asked me what to do now... I told her I didn't know, I thought the first thing TWRP asked upon boot was if you wanted to root?

Please help

Guys, my son messed up and followed instructions off the Max "HighOnAndroid" at www.galaxynote5root.com
He flashed twrp 3.0.2-1
He followed step by step. After flashing twrp, he booted back into recovery and flashed
No-verify-opt-encrypt
And
Update-SuperSU-v2.46
When he booted it back up, its stuck on the sprint splash screen. It is specifically in the screen that says LTE Plus More spectrum better network.
After I got off from work, I came home to him crying.
Ok, I have started to download the factory ROM from Sammobile but I am wondering if maybe there isnt an easier fix. I am not to familiar with changing kernels. Ive never needed to worry about them. Could I maybe just need to flash a new kernel?
From looking on here, really all he needed to do was flash twrp then SuperSU... Does anyone know a way to fix this faster than waiting 6 hours for the Sammobile stock rom?
Please help

Edit....
Ok guys...
I got the file downloaded from sammobile. I installed it and got it installed and working. Then I tried to do the root myself. I followed the guide on this site. However I still couldn't get it working. It was still bootlooping. But not the same bootloop. This time around, it didn't get past the very 1st screen. I again flashed back the stock ROM and again everything works fine.
The files I tried to install are:
Twrp-3.0.2-1nobleltespr.tar.md5
Then I did the twrp install boot deal, booted into twrp and installed:
BeastMode-Stock-N920P-1.3-O16.tar.md5
BETA-Flashable_SuperSU-2.52
I now take it that the issue is my twrp says noble while I read not to use the noble kernel to use BeastMode. But I could be way off...
Man alive, I didn't know just how much I appreciated CF Auto Root until just now...

You probably already figured this out by now but follow the instructions and links in my thread. You should only reboot directly to twrp from download mode after flashing twrp btw in case you haven't figured it out by now.
The method you are using is from a very old thread. Follow the instructions in the thread below.
[How-to] Root your SM-N920P Device - all versions

tdunham said:
You probably already figured this out by now but follow the instructions and links in my thread. You should only reboot directly to twrp from download mode after flashing twrp btw in case you haven't figured it out by now.
The method you are using is from a very old thread. Follow the instructions in the thread below.
[How-to] Root your SM-N920P Device - all versions
Click to expand...
Click to collapse
Thank you for responding. I was able to get the factory ROM installed and working fine.
I have downloaded the MOAR for the device and plan on giving it a go.
I still haven't been able to root the phone. EVERYTHING I tried resulted in bootloop. So I just decided to stick to stock on his phone until I can actually get it figured out...
As far as the SuperSu being old, I got it directly from the website of the maker. https://download.chainfire.eu/696/supersu/
I REALLY want to get this phone rooted for him, as I am certain he is going to keep trying following random YouTube videos regardless of my instruction.
Like I said in my last post, I have never missed cf auto root so badly...
Sent from my SM-N900T using Tapatalk

auburn2eugene said:
Thank you for responding. I was able to get the factory ROM installed and working fine.
I have downloaded the MOAR for the device and plan on giving it a go.
I still haven't been able to root the phone. EVERYTHING I tried resulted in bootloop. So I just decided to stick to stock on his phone until I can actually get it figured out...
As far as the SuperSu being old, I got it directly from the website of the maker. https://download.chainfire.eu/696/supersu/
I REALLY want to get this phone rooted for him, as I am certain he is going to keep trying following random YouTube videos regardless of my instruction.
Like I said in my last post, I have never missed cf auto root so badly...
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Root on stock is relatively simple.
TWRP + SuperSU only.
But as you saw, it's still easy to get it wrong.

tdunham said:
Root on stock is relatively simple.
TWRP + SuperSU only.
But as you saw, it's still easy to get it wrong.
Click to expand...
Click to collapse
Ok, so since I have flashed TWRP and SuperSU, and all it ever does it bootloop, would I be able to install TWRP, then flash MOAR on top of it? Then I would have a rooted MOAR if I understand correctly. My issue is that ive always had root accomplished before installing a custom ROM.
If all I have to do is flash twrp then SuperSU, I dont understand what I could be doing wrong.
But I'm going to take a look at your link you provided and see if I can't get root 1st.

auburn2eugene said:
Ok, so since I have flashed TWRP and SuperSU, and all it ever does it bootloop, would I be able to install TWRP, then flash MOAR on top of it? Then I would have a rooted MOAR if I understand correctly. My issue is that ive always had root accomplished before installing a custom ROM.
If all I have to do is flash twrp then SuperSU, I dont understand what I could be doing wrong.
But I'm going to take a look at your link you provided and see if I can't get root 1st.
Click to expand...
Click to collapse
Old habits are hard to break. A properly deodexed rom that is pre-rooted only requires twrp and a proper wipe before installing.
For rooting stock, it really is fairly simple. The instructions I provided are probably a little overly detailed but I had to cover as much as possible for those that have never done it before so it 'looks' complex but once you've done it a few times you will see that its really not that hard to do.

tdunham said:
Old habits are hard to break. A properly deodexed rom that is pre-rooted only requires twrp and a proper wipe before installing.
For rooting stock, it really is fairly simple. The instructions I provided are probably a little overly detailed but I had to cover as much as possible for those that have never done it before so it 'looks' complex but once you've done it a few times you will see that its really not that hard to do.
Click to expand...
Click to collapse
Thank you for pointing me to your thread. I was able to get root on my sons phone. Hard to believe the SuperSU was the problem... But it was... I was using the one from chainfires site, but yours worked when his created bootloops.
Thanks again!

Is there a root method for pk1

[ROOT][MAGISK] For Asus ZenPad 10 3s[P027]

Just goot this device rooted! Just gonna test the script a few times so there isent any bugs and i will upload it!
EDIT: Systemless Root methods like Magisk resets after root(I Think SuperSu works if u tweak dm-verity in the kernel). But using system-root both breaks saftynet and is boring
So im gonna try to edit the boot img to work with magisk or SuperSU even if the bootloader is locked.
If none of theese things works there is a way to Re-root after each reboot but its ofc much easyer just to edit the boot.img or unlock the BL
EDIT 2: I will also try to reverse engineer the bootloader to try to find a weak point where we can unlock it, for easyer rooting and creating custom roms
EDIT 3: Also forgot to mention xposed works because you dont "need" root. If anyone want xposed just reply in the thread and il upload the script "as is" even though it resets after each reboot, but root works perfect have tested multiple apps.
And as i said before, before i release the root method publicly i want to check if its the BL who "resets" the kernel like on some HTC devices or if its a simple dm-verity problem , if it is the dm-verity thing its easy to fix.
More info:
Flashing kernel,system,recovery works because the only partitions that are protected are the BL and FRP partions but not for long
So far:
Magisk: Works
Bootloader: Locked
Saftynet: Passes
Proof:
https://i.imgur.com/8uABTSl.jpg
Download:
Code:
Comming in an hour! Just gotta check the updatescript for errors before posting :)

j wait for your script to root my Z500 m thanks to you.

Wow, finally there's a method to root. I own the device since august and I really want to get it rooted due to all bloatware I want to uninstall and to install 3rd party apps.:good:

super thanks to you me too and thanks to you I could root the tablet with all s is unnecessary thank you for your work:good::good::good:

Cant wait
Wow.... time is ticking to bring root to the P027
I can't wait for an update on this.
There must be another way to get a rooted ASUS P027. I tried much but don't have any success. I think that there is a way to push some files manually to /data/local/tmp. Setting right permissions using adb. Finally executing a root-shell-script from one of many should do the rest. Problem is not to get the files inside the system, you have to do it again after each reboot.
I'm a bit nervous to modify bootloaders and flash them on the go with no oem support. If some support for this device comes available from ASUS it should be a lot easyer to do.
I cant upload photo's till i'm no longer seem like a robot. I also got some kind of root on my P027. only for a moment. After reboot it is gone.

I can't wait for that!

Will it come out soon..... so excited ^_^

BigThanh said:
Will it come out soon..... so excited ^_^
Click to expand...
Click to collapse
here too...the hour is over

That would be great

hey, very good news!! I am waiting a long time for this. It would also be nice, if you can give us your xposed script. Thnkas!!

Is p207 the model number? I'm only finding it listed as Z500M.

joshnat said:
Is p207 the model number? I'm only finding it listed as Z500M.
Click to expand...
Click to collapse
Yes

Ok guy's where do we stand on root as of 5pm Wednesday 10.04.2017 ??
I bought the ASUS Zenpad 3S 10 [P027] off Amazon on Saturday on a flash sale for $265, knowing it didn't have root, and that's a shame because it's a beautiful & buttery smooth tablet.
Today, as I was pondering boxing it up for a return, I figured I'd look for myself once more for the hell-of-it, AND BOOM! I found this thread!
So where are we guys? I'll test it for ya or whatever! So friggin' pumped ROOT has been established! Dare I say -Vanilla Oreo ROM with onscreen softkeys??? YEAH!

Really looking forward to this! I don't mind getting my hands dirty, but just waiting for the script I'm very happy to have stumbled upon this thread, can't wait to have root on this tablet!!

Fortunately we will get to see the script. I own the P027 since auust 17. A very good hardware. But without root its only worth half. So, me too is awaiting the script but so far I guess we still have to wait. Til now, no root app works (iRoot, Kingo, e.g.) Very sad because I think that once we rooted it and get rid of all the OEM bloatware, this tab may rocks a lot more.

Prinz069 said:
Fortunately we will get to see the script. I own the P027 since auust 17. A very good hardware. But without root its only worth half. So, me too is awaiting the script but so far I guess we still have to wait. Til now, no root app works (iRoot, Kingo, e.g.) Very sad because I think that once we rooted it and get rid of all the OEM bloatware, this tab may rocks a lot more.
Click to expand...
Click to collapse
to remove bloatware, i followed this guide. I can confirm ist works.
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/

Can you go ahead and upload the script for those of us brave enough to try it? Thank you for all your hard work!

I got root and xposed. But I don't have a way to get it in that device
At my next post will I upload a photo or link of my own (semi) rooted P027. The Magic of rooting a device which is unsupported is far away from easy as flashing chainfire's zips or something possible using Odin or what. Most likely if there was a custom recovery for the P027 root would be easy because of all possibilities you have.
I've tried a lot of other ways to get in to try modify something in that locked system. It is hard to get there without losing patients! I also lose social networks I belong to. Even if days counts 48 hour instead of 24, root wasn't there with the success I had hope to. Sometimes only after manually redirecting some files with adb and manually setting right permissions to every file. It becomes possible to get accessing "su" in terminal app. Only sometimes, after each modifying something, you're device needs to reboot for applying that modification. At that point you lose everything before you can use it.
If someone can post latest boot.img I will try to patch it with Magisk. If that is possible it will get easier to activate systemless xposed. A few weeks ago on note 8 launch day... It took at least 1 hell of a day before root came available on xda. Also twrp and custom roms are available.
Hope soon to make it happening for real.

hi I would buy this tablet but wanted to understand root situation. can you run the root on this device? you can install Rom?

toineh said:
At my next post will I upload a photo or link of my own (semi) rooted P027. The Magic of rooting a device which is unsupported is far away from easy as flashing chainfire's zips or something possible using Odin or what. Most likely if there was a custom recovery for the P027 root would be easy because of all possibilities you have.
I've tried a lot of other ways to get in to try modify something in that locked system. It is hard to get there without losing patients! I also lose social networks I belong to. Even if days counts 48 hour instead of 24, root wasn't there with the success I had hope to. Sometimes only after manually redirecting some files with adb and manually setting right permissions to every file. It becomes possible to get accessing "su" in terminal app. Only sometimes, after each modifying something, you're device needs to reboot for applying that modification. At that point you lose everything before you can use it.
If someone can post latest boot.img I will try to patch it with Magisk. If that is possible it will get easier to activate systemless xposed. A few weeks ago on note 8 launch day... It took at least 1 hell of a day before root came available on xda. Also twrp and custom roms are available.
Hope soon to make it happening for real.
Click to expand...
Click to collapse
Here is the boot.img from WW_V14.0210.1709.27: https://mega.nz/#!4bQExBTB!5fyivXxvP4aYAxCDjsYRJ1X7o1wMXYGBLf1TO0ns-z4
I downloaded the WW_V14.0210.1709.27 firmware from ASUS Support then unzip the package to get this file.
Hope it will be helpful to you. I am really looking forward to root this device!
Thank you for your hard work!

Help rooting Samsung galaxy j3 (sm-J337a)

It seems everywhere I go there is no root for this phone (sm-J337a) it's an at&t phone. I used kingoroot, kingroot and basically any root out there. nothing has worked. So this seems that it has no root made for it yet? is there any possibility for someone to do this? Sorry, I'm not too good at rooting as a whole. But I've used Odin and things like that before.
there doesn't even seem to be CWM or TWRP for this phone either.
it's running Android 8.0 and was made in 2018.

Right?
I'm having the same issue. I can't figure out how to root mine either and I've got the same phone and carrier.

nickthekid said:
It seems everywhere I go there is no root for this phone (sm-J337a) it's an at&t phone. I used kingoroot, kingroot and basically any root out there. nothing has worked. So this seems that it has no root made for it yet? is there any possibility for someone to do this? Sorry, I'm not too good at rooting as a whole. But I've used Odin and things like that before.
there doesn't even seem to be CWM or TWRP for this phone either.
it's running Android 8.0 and was made in 2018.
Click to expand...
Click to collapse
Details of your current ROM Please..?
Build number etc...

Hi all.. I know this thread is a little old but thought id add this.. As of this date Ive found no ROOT solution for the SM-J337A - AT&T variant either.. I have found a lot of other software and such and as soon as I can get it all sorted, cataloged, and uploaded to the cloud I will see about placing some links here somewhere to all of them.. Not sure how long it will be..Stay tuned...
I happen to inherit a J337A with a cracked screen but was working fine until I updated it and tryed ROOTing it.. Im still Playing with it to see if I can revive it.
Having issues finding a UB compatible Firmware set that I dont have to pay for.
Am needing "J337AUCSBBTI1" or maybe "J337AUCSABTE1" to see if I can bring it back to life.. I may end up pitching it tho...
My Device:: SM-J337A
FCC-ID : A3LSMJ337A
Samsung/j3toplteuc/j3toplteatt
CURRENTLY STUCK ON COMBINATION ROM : (8.0.0/R16NW/J337AUCUBATH1/user/release-keys)
BINARY/BOOTLOADER : UB

iamoz said:
Hi all.. I know this thread is a little old but thought id add this.. As of this date Ive found no ROOT solution for the SM-J337A - AT&T variant either.. I have found a lot of other software and such and as soon as I can get it all sorted, cataloged, and uploaded to the cloud I will see about placing some links here somewhere to all of them.. Not sure how long it will be..Stay tuned...
I happen to inherit a J337A with a cracked screen but was working fine until I updated it and tryed ROOTing it.. Im still Playing with it to see if I can revive it.
Having issues finding a UB compatible Firmware set that I dont have to pay for.
Am needing "J337AUCSBBTI1" or maybe "J337AUCSABTE1" to see if I can bring it back to life.. I may end up pitching it tho...
My Device:: SM-J337A
FCC-ID : A3LSMJ337A
Samsung/j3toplteuc/j3toplteatt
CURRENTLY STUCK ON COMBINATION ROM : (8.0.0/R16NW/J337AUCUBATH1/user/release-keys)
BINARY/BOOTLOADER : UB
Click to expand...
Click to collapse
I can help you with that if you still need it. I have my j3 rooted with magisk, although there is no twrp or any custom recovery for that matter..
I can give you the exact files along with the patched magisk file and you'll have to flash it with patched odin and you should be good. Let me know.

rip21skinz said:
I can help you with that if you still need it. I have my j3 rooted with magisk, although there is no twrp or any custom recovery for that matter..
I can give you the exact files along with the patched magisk file and you'll have to flash it with patched odin and you should be good. Let me know.
Click to expand...
Click to collapse
Yes I would be interested in having those files please... Either upload them here or I can give you an email if you prefer... Let me know..

rip21skinz said:
I can help you with that if you still need it. I have my j3 rooted with magisk, although there is no twrp or any custom recovery for that matter..
I can give you the exact files along with the patched magisk file and you'll have to flash it with patched odin and you should be good. Let me know.
Click to expand...
Click to collapse
Instead of sending a patched magisk file would you mind sending over the method you used to root? If you did what I think you did I'm very confused. The phone is OEM locked although this hasn't stopped others from accessing root before. If you can confirm you have the phone we have, the SM-J337A ATT then you can pull out the boot and recovery images using a root app. Then I could develop a working TWRP for our device. But ofc this is only possible if you explain how you went about rooting the device. Thanks in advance.

NonStickAtom785 said:
Instead of sending a patched magisk file would you mind sending over the method you used to root? If you did what I think you did I'm very confused. The phone is OEM locked although this hasn't stopped others from accessing root before. If you can confirm you have the phone we have, the SM-J337A ATT then you can pull out the boot and recovery images using a root app. Then I could develop a working TWRP for our device. But ofc this is only possible if you explain how you went about rooting the device. Thanks in advance.
Click to expand...
Click to collapse
I have both SM-J337P/A and it works the same on both. I'm not sure why you wouldn't be able to be oem unlocked? You mean greyed out? Or does it not show up at all or what? If I go into developer options I have the oem unlock option, which then allows me to unlock the bootloader. If yours is greyed out I saw a solution on XDA a long time ago, maybe a year ago. I'd have to look for it in my files, I know I saved it somewhere. Let me know what you meant by that and we can go from there

rip21skinz said:
I have both SM-J337P/A and it works the same on both. I'm not sure why you wouldn't be able to be oem unlocked? You mean greyed out? Or does it not show up at all or what? If I go into developer options I have the oem unlock option, which then allows me to unlock the bootloader. If yours is greyed out I saw a solution on XDA a long time ago, maybe a year ago. I'd have to look for it in my files, I know I saved it somewhere. Let me know what you meant by that and we can go from there
Click to expand...
Click to collapse
I do not have the option to OEM Unlock the phone period. It is not in my developer options unfortunately. If you do find something of that nature please do contact me. Also if you would like a TWRP for your device I'd be up to developing it, although I wouldn't be able to maintain bugs... All I need is the kernel and I can get it done.

Any updates on this?