Just wondering if anyone is working on/willing to start working on an AOSP Nougat or Oreo ROM for this device? I would go for it myself, however, my internet won't even let me sync repo. Thanks in advance for any responses
Toby.
Device: J327U
Recovery: TWRP 3.1.1-1 Ashyx
Root: Yes, SuperSU
waiting bro....:good:
At this point, we know the bootloader is unlocked. We have been able to successfully root it. Is it just that the market share is so low that no one is developing for this device yet?
TMet said:
At this point, we know the bootloader is unlocked. We have been able to successfully root it. Is it just that the market share is so low that no one is developing for this device yet?
Click to expand...
Click to collapse
I do believe that is the case (not worth a custom ROM). Have the phone myself, it's a solid, cheap, fast unit. More reliable that Moto's, etc., but not worthy of a custom ROM, sadly.
Related
I have successfully unlocked and am using the G930VL and installed the official verizon version rom to get rid of anything straighttalk related and it has been working great!
But....i want to install custom roms in order to do that i need CWM or TWRP. I cannot seem to get either one to install because of a "Secure check fail: recovery" message. Any suggestions?
also does anyone have a good link here on XDA for G930V/G930VL rom's?
I am rooted so this should be possible somehow what am i missing?
You can gain root but not twrp http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039
peachpuff said:
You can gain root but not twrp http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039
Click to expand...
Click to collapse
Is there any roms that will work? I have found things like King rom but that's for the edge. Even so...how would i install it without TWRP? Would i have functionality issues with G930VL? I haven't had to install from ADB in a long time but if someone guides me i'd still be willing. The reason why this is an issue is i can't get out of the security messages that happen in the OS. Every time i boot it keeps saying i have to reboot because it finds a problem (due to it being rooted)....1 time my phone wouldn't even boot up which is when i installed the official verizon OS and wipped everything straighttalk except the bootloader(for obvious reasons i'm not touching that!).
Ziron999 said:
Is there any roms that will work? I have found things like King rom but that's for the edge. Even so...how would i install it without TWRP? Would i have functionality issues with G930VL? I haven't had to install from ADB in a long time but if someone guides me i'd still be willing. The reason why this is an issue is i can't get out of the security messages that happen in the OS. Every time i boot it keeps saying i have to reboot because it finds a problem (due to it being rooted)....1 time my phone wouldn't even boot up which is when i installed the official verizon OS and wipped everything straighttalk except the bootloader(for obvious reasons i'm not touching that!).
Click to expand...
Click to collapse
You'll have to ask the folks in that thread, i don't have any answers for you except that thread that i looked over before.
With Qualcomm Snapdragon's security feature DM-Verify, it is extremely unlikely. Even if you took the stock image from Verizon and did nothing more than deodex it, dm-verify will not allow the ROM to boot (from what I've read). There are other security features that prevent the Bootloader form being messed with.
Root was a dream come true. An unlockable bootloader (while a developer version does exist) is a more unachievable dream.
Ziron999 said:
I have successfully unlocked and am using the G930VL and installed the official verizon version rom to get rid of anything straighttalk related and it has been working great!
But....i want to install custom roms in order to do that i need CWM or TWRP. I cannot seem to get either one to install because of a "Secure check fail: recovery" message. Any suggestions?
also does anyone have a good link here on XDA for G930V/G930VL rom's?
I am rooted so this should be possible somehow what am i missing?
Click to expand...
Click to collapse
"I have successfully unlocked" what type of unlock are you speaking of?
Okay so I'm still using a OnePlus One and after the whole debacle with CM getting shut down I decided to switch away from my CM ROM to a 7.1.1 rom and after testing roms for an entire day I found the perfect one and I just love 7.1.1 in general.
HERE'S the problem. Every single Rom i tried comes Rooted. And I can't have that because a lot of apps and games are starting to be very picky with that. So I was wondering if there's a way to make the ROM I want to use completely Root free. Because here's the thing, even if I remove the Root with SuperSU or something afterwards, some apps still show the device as rooted, and for some reason Developer Options don't want to turn themselves off.
To give some of you a example between the two roms.
The ROM i want to use: https://forum.xda-developers.com/oneplus-one/development/nitrogen-os-7-1-0-nde63p-t3491386
The ROM i was using: https://forum.xda-developers.com/on...m-kernel-unofficial-cyanogenmod-13-0-t3242700
The ROM i was using (SultanOS) comes completelly un-rooted out of the box and Android Pay and the game I play (Fate/Grand Order) work just fine.
The ROM i want to use is NitrogenOS and while it works amazingly on my phone and would totally use it as a daily driver, it comes pre-rooted, and even after getting rid of the "superuser" folder in the .zip and editing the "updater-script" file with Notepad++ and removing everything with "superuser" in it (like I was told in the discussion) it seemed like the root wasn't installed, but the apps still seemed to detect some sort of root and i can't seem to turn off developer options (with and without root). Also tried the unSU method by @osm0sis but again...it only seems to get rid of the root but dev options don't allow me to turn them off and apps still see the phone as rooted.
So can anyone help me here? What I basically want is the NitrogenOS ROM, but completely Root free on install like SultanOS.
If I could possibly get input from @amardeep434 and @Sultanxda that would be amazing. Because both of your builds are amazing, but as far as i know Sultan is switching to the OP3T so I'm not expecting a 7.1 ROM anymore.
Root is good for a lot of people, but I personally think with how easy flashing SuperSU is nowadays, ROMs could easily come without it and save some of us a ton of headaches.
Hopefully I can get some help on this. I'd greatly appreciate it.
lsk91 said:
Okay so I'm still using a OnePlus One and after the whole debacle with CM getting shut down I decided to switch away from my CM ROM to a 7.1.1 rom and after testing roms for an entire day I found the perfect one and I just love 7.1.1 in general.
HERE'S the problem. Every single Rom i tried comes Rooted. And I can't have that because a lot of apps and games are starting to be very picky with that. So I was wondering if there's a way to make the ROM I want to use completely Root free. Because here's the thing, even if I remove the Root with SuperSU or something afterwards, some apps still show the device as rooted, and for some reason Developer Options don't want to turn themselves off.
To give some of you a example between the two roms.
The ROM i want to use: https://forum.xda-developers.com/oneplus-one/development/nitrogen-os-7-1-0-nde63p-t3491386
The ROM i was using: https://forum.xda-developers.com/on...m-kernel-unofficial-cyanogenmod-13-0-t3242700
The ROM i was using (SultanOS) comes completelly un-rooted out of the box and Android Pay and the game I play (Fate/Grand Order) work just fine.
The ROM i want to use is NitrogenOS and while it works amazingly on my phone and would totally use it as a daily driver, it comes pre-rooted, and even after getting rid of the "superuser" folder in the .zip and editing the "updater-script" file with Notepad++ and removing everything with "superuser" in it (like I was told in the discussion) it seemed like the root wasn't installed, but the apps still seemed to detect some sort of root and i can't seem to turn off developer options (with and without root). Also tried the unSU method by @osm0sis but again...it only seems to get rid of the root but dev options don't allow me to turn them off and apps still see the phone as rooted.
So can anyone help me here? What I basically want is the NitrogenOS ROM, but completely Root free on install like SultanOS.
If I could possibly get input from @amardeep434 and @Sultanxda that would be amazing. Because both of your builds are amazing, but as far as i know Sultan is switching to the OP3T so I'm not expecting a 7.1 ROM anymore.
Root is good for a lot of people, but I personally think with how easy flashing SuperSU is nowadays, ROMs could easily come without it and save some of us a ton of headaches.
Hopefully I can get some help on this. I'd greatly appreciate it.
Click to expand...
Click to collapse
Hello,
Well you can try magisk and systemless root, something similar to this Magisk development thread.
Here's a support and discussion thread, click here.
If you still run into issues, please post in support and discussion thread. The experts might be able to assist you.
Regards
Vatsal,
Forum Moderator.
I can pass SafetyNet but my banking app still sees my device as rooted. I think some apps just see anything but stock ROM (or at least see the ROMs with built-in root settings) as "rooted" even if all the binaries and files are stripped away.
suhide was the only thing that worked to hide things from my banking app but unfortunately it doesn't work after recent Android security updates. Haven't tried the recent Magiskhide, but I have heard it may work currently as well.
Vatsal said:
Hello,
Well you can try magisk and systemless root, something similar to this Magisk development thread.
Here's a support and discussion thread, click here.
If you still run into issues, please post in support and discussion thread. The experts might be able to assist you.
Regards
Vatsal,
Forum Moderator.
Click to expand...
Click to collapse
Thank you! I'll give that a look and if it doesn't work I'll make this post in the Support threads
osm0sis said:
I can pass SafetyNet but my banking app still sees my device as rooted. I think some apps just see anything but stock ROM (or at least sees the ROMs with built-in root settings) as "rooted" even if all the binaries and files are stripped away.
suhide was the only thing that worked to hide things from my banking app but unfortunately it doesn't work after recent Android security updates. Haven't tried the recent Magiskhide, but it may work currently as well.
Click to expand...
Click to collapse
Yea sultans OS wasn't detected because it comes un-rooted and it's not a stock rom. So I'd assume it's roms with built in root settings? Which....is there a way to get rid of that?
lsk91 said:
Yea sultans OS wasn't detected because it comes un-rooted and it's not a stock rom. So I'd assume it's roms with built in root settings? Which....is there a way to get rid of that?
Click to expand...
Click to collapse
Hello,
No way unless you build one yourself.
Regards
Vatsal,
Forum Moderator.
So I finally got a pixel after lurking around for a while and ended up with a Verizon version. Luckily the dePixel8 fix got the BootLoader unlocked as it wasn't updated yet. Now that I've got the bootloader unlocked, I haven't done anything with it yet. I used to root all of my android phones (Nexus 5, 6, 5x...) and do all kinds of cool things, but as of the 5X, everything I used to root to do is now baked into the Pixel, so I haven't touched anything on it. The one thing I would love to use is Android-Pay... DOH
So, I am verizon phone (on t-mobile), bone-stock OS with an unlocked bootloader and no Android Pay due to failing safety-net. The question is, if I re-lock the bootloader, will I ever be able to unlock it again? Like I want to try a ROM etc? Or is my best bet to get the Kernel that patches the Safety-Net process?
My original thought process drug me to the kernel patch, but since I really haven't had a need to mess with my pixel, the whole process seemed far more involved than the simple desire to use Android-Pay... Which led me to thinking about just re-locking the bootloader... So, please help!
TIA!
cmivxx said:
So I finally got a pixel after lurking around for a while and ended up with a Verizon version. Luckily the dePixel8 fix got the BootLoader unlocked as it wasn't updated yet. Now that I've got the bootloader unlocked, I haven't done anything with it yet. I used to root all of my android phones (Nexus 5, 6, 5x...) and do all kinds of cool things, but as of the 5X, everything I used to root to do is now baked into the Pixel, so I haven't touched anything on it. The one thing I would love to use is Android-Pay... DOH
So, I am verizon phone (on t-mobile), bone-stock OS with an unlocked bootloader and no Android Pay due to failing safety-net. The question is, if I re-lock the bootloader, will I ever be able to unlock it again? Like I want to try a ROM etc? Or is my best bet to get the Kernel that patches the Safety-Net process?
My original thought process drug me to the kernel patch, but since I really haven't had a need to mess with my pixel, the whole process seemed far more involved than the simple desire to use Android-Pay... Which led me to thinking about just re-locking the bootloader... So, please help!
TIA!
Click to expand...
Click to collapse
I believe most of kernels have that safety net patch. Really painless to flash. You can just boot TWRP and flash kernel I believe
mac796 said:
I believe most of kernels have that safety net patch. Really painless to flash. You can just boot TWRP and flash kernel I believe
Click to expand...
Click to collapse
Ok, I'll bite... Is there a "preferred" kernel at this point? Digging through some of the threads on the different kernels is about a bunch of people having problems... I just want the safety-net patch, probably won't use the other features.
cmivxx said:
Ok, I'll bite... Is there a "preferred" kernel at this point? Digging through some of the threads on the different kernels is about a bunch of people having problems... I just want the safety-net patch, probably won't use the other features.
Click to expand...
Click to collapse
I usually just use the kernel that comes with the rom im on. And I use magisk. I have used ex kernel. I really like the ex manager app. And I do believe it still passes safety net with just unlocked bootloader. At least it used to. Google updated safety net this month so I don't know if that changes things.
Alright, I did it... TWRP RC2 + Elemental X sorted out my safety-net issues... Just concerned about legit updates to the phone. Guess I'll fgure that out when the time comes.
Thanks for the help!
cmivxx said:
Alright, I did it... TWRP RC2 + Elemental X sorted out my safety-net issues... Just concerned about legit updates to the phone. Guess I'll fgure that out when the time comes.
Thanks for the help!
Click to expand...
Click to collapse
You will probably be able to take the OTA with just a unlocked Bootloader, you will just have to boot TWRP and Flash that kernel every month. There also is a stock kernel someone builds for what you're trying to do
You can flash google's factory-image.
Then you can re-lock your bootloader and you can unlock it too.
I ported twrp for the Asus Zenfone max plus m1.However I don't have experience on how to test it or if I did flash it,how to restores stock recovery so I haven't tested it yet.I would like some people to test it for me.After or if it is successful and I get confidence in porting these things I might try to port a rom or too for our device.or try to port a kernel.as our current kernel is kind of old.
Hi, i would love to test it.
But still can't root it after Oreo update, even with the tool provided by Asus .
Tried kingroot also didn't support.
I could test it. Although, I really need a method of root first.
Anyone knows a method in which you could root it without a custom recovery? And yes, I've heard of Magisk, but I'd rather avoid that until it's the last option. Thanks!
Carpeso said:
I could test it. Although, I really need a method of root first.
Anyone knows a method in which you could root it without a custom recovery? And yes, I've heard of Magisk, but I'd rather avoid that until it's the last option. Thanks!
Click to expand...
Click to collapse
Wait why do you need root to install a custom recovery in the first place? I haven't tested the twrp file I made and also I lost it, so I might have to recreate it. Sorry for not being active for awhile, I was busy with school
Carpeso said:
I could test it. Although, I really need a method of root first.
Anyone knows a method in which you could root it without a custom recovery? And yes, I've heard of Magisk, but I'd rather avoid that until it's the last option. Thanks!
Click to expand...
Click to collapse
follow this tread and site
https://forum.xda-developers.com/android/apps-games/twrpbuilder-t3744253
https://twrpbuilder.github.io/downloads/twrp/#tab=completed#724
and here
https://github.com/TwrpBuilderTests...s/tag/TWRP-3.2.3-TwrpBuilder-2019-03-21_15-58
Sorry for the long period of inactivity
I've been away from xda for awhile sorry y'all. I had to focus on studies and I didn't check xda for a bit. I can't seem to find the twrp file that I ported with a online method. I never tested it, and it's likely it wouldn't have worked as the previous post shows. Someone has built twrp for our device. Bless them. As for the root question. It's possible to unlock bootloader on our Asus Zenfone max plus m1 and then use the patch boot image method by extracting the boot IMG from the firmware and then patching it with the magisk apk/ app and flashing it with fastboot flash boot patched_boot.im.
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?