Related
Alright, so as most of you know, (or not) there has been a MAJOR exploit for not just our device, but the ENTIRE android base as a whole. This is very exciting for us at this time, for as you know, Marshmallow for our phone gets near to no developer support. It goes by the name, the myth, the legend, Dirty Cow (CVE-2016-5195). How it works, is it uses a very old, 7-9 year old exploit that was overlooked a long time, but was patched on some Linux desktop systems. However, Android is running on a different kernel, and we can take advantage of CoW (Copy on Write). This is great news once again, if you want to know more, feel free to Google it. So, we don't really need to do much. Just sit back, and wait for people like J Case and Chainfire to release a tool that is verified to work.
(Or don't wait and try to make a tool of your own, each to their own)
Once we obtain root for our devices on 6.0 I will start to work on this device again and develop for it. I will port Cyanogenmod Mod 13 over, or whatever the latest is). Very excited to possibly start working on this device again, great device, just recently got wireless charging for it, +1 . Whatever you do, do NOT take any patches from AT&T if you can avoid it (reason why I say "if you can avoid it" is because AT&T has been known to automatically update your device in the past, and has happened countless times. Also, try not to download anything that isn't verified or from a source you trust, this can also be used for malicious purposes obviously.
-ZVNexus
ZVNexus said:
Alright, so as most of you know, (or not) there has been a MAJOR exploit for not just our device, but the ENTIRE android base as a whole. This is very exciting for us at this time, for as you know, Marshmallow for our phone gets near to no developer support. It goes by the name, the myth, the legend, Dirty Cow (CVE-2016-5195). How it works, is it uses a very old, 7-9 year old exploit that was overlooked a long time, but was patched on some Linux desktop systems. However, Android is running on a different kernel, and we can take advantage of CoW (Copy on Write). This is great news once again, if you want to know more, feel free to Google it. So, we don't really need to do much. Just sit back, and wait for people like J Case and Chainfire to release a tool that is verified to work.
(Or don't wait and try to make a tool of your own, each to their own)
Once we obtain root for our devices on 6.0 I will start to work on this device again and develop for it. I will port Cyanogenmod Mod 13 over, or whatever the latest is). Very excited to possibly start working on this device again, great device, just recently got wireless charging for it, +1 . Whatever you do, do NOT take any patches from AT&T if you can avoid it (reason why I say "if you can avoid it" is because AT&T has been known to automatically update your device in the past, and has happened countless times. Also, try not to download anything that isn't verified or from a source you trust, this can also be used for malicious purposes obviously.
-ZVNexus
Click to expand...
Click to collapse
Jcase doesn't work on LG devices at all anymore. (That's what he told me) Chainfire is occupied with working on a systemless root for the google Pixel! Think you could try it?
abine45 said:
Jcase doesn't work on LG devices at all anymore. (That's what he told me) Chainfire is occupied with working on a systemless root for the google Pixel! Think you could try it?
Click to expand...
Click to collapse
Nonono, the thing is this exploit will work on ALL Android devices, so even if one person creates a tool for another device that does not yet have root, that tool will instantly work on ALL devices. (at least to my knowledge) So it doesn't matter if he works on LG devices or not, any tool he makes can be used on our devices.
ZVNexus said:
Once we obtain root for our devices on 6.0 I will start to work on this device again and develop for it. I will port Cyanogenmod Mod 13 over, or whatever the latest is).
-ZVNexus
Click to expand...
Click to collapse
The root has nothing to do with custom roms. Root won't let you to unlock bootloader.
rascal0pl said:
The root has nothing to do with custom roms. Root won't let you to unlock bootloader.
Click to expand...
Click to collapse
With a certain method, we won't need one. I was thinking, once you boot /system, it will automatically trigger which will send you into CM13.
It would be very similar to Safestrap, but not.
i have unlocked bootloader on MM, meybe someday I learn how to port rom V10 is poor in unofficial soft
I dont understand ????
Excuse me can u say it in simple way ? ???
Are u wanna say with Our locked bootloader we can install root and Twrp on Our device ? On MM or Nougat or any system? Do u mean that ?!
₪HuEx₪
HuEx said:
I dont understand
Excuse me can u say it in simple way ?
Are u wanna say with Our locked bootloader we can install root and Twrp on Our device ? On MM or Nougat or any system? Do u mean that ?!
₪HuEx₪
Click to expand...
Click to collapse
Installing TWRP is IMPOSSIBLE without unlocked bootloader so no. Although, systemless root is very much possible, just we have no devs that will work on it. Although I do work on minor root applications, I myself am no where at the level of where people like Chainfire are. So yes, root possibility, bootloader nope. (Until further notice at least)
The T-Mobile varient already has root + TWRP on MM ......
ZVNexus said:
Installing TWRP is IMPOSSIBLE without unlocked bootloader so no. Although, systemless root is very much possible, just we have no devs that will work on it. Although I do work on minor root applications, I myself am no where at the level of where people like Chainfire are. So yes, root possibility, bootloader nope. (Until further notice at least)
Click to expand...
Click to collapse
But i see they could Unlock bootloader with Nougat system with Fastboot on V20 without a bin file or any thing .. So is there a hope with Nougat For us ? To get TWRP in V10? All Variants?
₪HuEx₪
This exploit is not specific to this phone. Once someone releases root via this method it should work on all phones, all firmwares.
ZVNexus said:
Installing TWRP is IMPOSSIBLE without unlocked bootloader so no. Although, systemless root is very much possible, just we have no devs that will work on it. Although I do work on minor root applications, I myself am no where at the level of where people like Chainfire are. So yes, root possibility, bootloader nope. (Until further notice at least)
Click to expand...
Click to collapse
This is both true and untrue. There is a way around this, if you can use Android itself as a bootloader, then you don't actually need the usual sort of unlocked bootloader. The idea is similar to Linux's KEXEC functionality. Alas I'd bet KEXEC won't be available on Android kernels any time soon, but if you can inject code into kernel space you can get the same effect.
beavis5706 said:
This exploit is not specific to this phone. Once someone releases root via this method it should work on all phones, all firmwares.
Click to expand...
Click to collapse
I've read there are some already out and people have been successfully experimenting.
I am SO excited. This forum has been so barren for so long I just never even imagined CM on my phone
when will we be able to unlock bootloader for v10 H960a middle east version. i had two option, go with sony z5 premium dual or LG V10, i regret choosing LG v10 over z5. i wish if i knew that you cant unlock the bootloader!!
Has there been someone that has been able to permanently root marshmallow yet (non t-mobile v10) ?
Permanent root may not be necessary. But no one has replied to my questions on the functionality of temporary root. Questions are... With temp root...
1. Can I replace mobile hotspot APK and use my hotspot after reboot (no root) unlimited data user.
2. Would ad blocking still work after reboot (no root)
3. Would viper4android still work after reboot (i could live with out this one)
4. Would I be able to use Titanium Backup while temporary rooted?
Hello
I'm new to LG V10 so I don't know in detail.
But can we use VIKIROOT??
It looks work on this device and we can get temporal root?
I'm sorry for my bad English.
I tried to use it but it says "Permission denied."
iptr9 said:
Hello
I'm new to LG V10 so I don't know in detail.
But can we use VIKIROOT??
It looks work on this device and we can get temporal root?
I'm sorry for my bad English.
I tried to use it but it says "Permission denied."
Click to expand...
Click to collapse
I just saw VIKIROOT and looks promising!
You probably did not make "exploit" executable. I pushed "exploit" through adb to /data/local/tmp, then opened an adb shell, cd to /data/local/tmp and made it executable (by chmod +x exploit). Then I ran it, and seemed to execute fine. However it stuck on "waiting for reverse connect shell". I don't know what to do now; I opened up the device, toggled Bluetooth etc as the developer suggests but nothing happens. Anybody to take it further?
ftaios said:
I just saw VIKIROOT and looks promising!
You probably did not make "exploit" executable. I pushed "exploit" through adb to /data/local/tmp, then opened an adb shell, cd to /data/local/tmp and made it executable (by chmod +x exploit). Then I ran it, and seemed to execute fine. However it stuck on "waiting for reverse connect shell". I don't know what to do now; I opened up the device, toggled Bluetooth etc as the developer suggests but nothing happens. Anybody to take it further?
Click to expand...
Click to collapse
Thank you for reply!!!
It also stuck on "Waiting for reverse connect shell"...
iptr9 said:
Thank you for reply!!!
It also stuck on "Waiting for reverse connect shell"...
Click to expand...
Click to collapse
I'm in contact with the developer, we will have to wait a bit. Let's keep fingers crossed
Mod Edit
So this is BS right? I've been out of the phone rooting game for a bit.
Sent from my SM-N920V using Tapatalk
Mod Edit
MrMike2182 said:
Why are you trying to get people to do this when it's not FULL ROOT?! You basically took the same exact console root eng kernel that is listed here https://forum.xda-developers.com/verizon-galaxy-note5/general/root-n920v-t3538192 and just renamed it..
Do not do this it's simply console root and nothing else!!
Click to expand...
Click to collapse
Lol at the if you see SuperSU you're rooted. I mean, if the CF auto works cool, but I'm gonna wait to see how many people don't read first and try to flash this.
tylerlawhon said:
Lol at the if you see SuperSU you're rooted. I mean, if the CF auto works cool, but I'm gonna wait to see how many people don't read first and try to flash this.
Click to expand...
Click to collapse
LOL there isn't even a CF auto root for the N920V!! He seriously just took the same one we already have for console root and renamed it! They're even the same exact size, haha. Besides, where does he think the SuperSU app is coming from? It sure ain't from the file he has posted because that's just the console root kernel and that doesn't install/ flash SuperSU it only flashes the boot.img..
tylerlawhon said:
..
Click to expand...
Click to collapse
There's to many inexperienced people claiming root and cluttering the hell out the forums!! Even on the easy-firmware website he posted this same exact thing and when a user asked him a question he didn't even know the answer and told the user to flash and report back with his findings.. This thread is totally not needed at all!!
Stuck in the boot interface
tylerlawhon said:
Lol at the if you see SuperSU you're rooted. I mean, if the CF auto works cool, but I'm gonna wait to see how many people don't read first and try to flash this.
Click to expand...
Click to collapse
Well there goes 1 who didn't read first lol.
please remove this threade Please .
it's worng from inexperienced someone
I know this website, easy firm ware listed above, to be a scam site. I've seen a lot of different angles they've tried INCLUDING a download manager quote unquote that is supposed to help you finish downloading. But this is a trojan app. While I never fired it up I can tell you it doesn't look like something a windows user should execute on their system. I use linux.
(mods I promise I know this site is a scam site I've watched them work over the past couple months as I researched my studies)
Regards to root. If you are patched for dirtycow good luck getting root on this phone. (see below for dirtycow patch details) The AT&T / Verizon variants of the Note 5 are extremely well coded you can't get root on them without a powerful exploit. With dirtycow available the days are numbered for any phones not patched, of course not patching your phone in the meantime means you are very vulnerable to a nasty exploit.
So how long right? I dunno but it could be awhile.
Patch details:
Google says the fix is called CVE-2016-5195 patched 11-05-2016, however my security patch level is Nov 1st, 2016. The Samsung SVE-2016-7504 is stated to be included in November's patches and there are 14 patches in that set. AT&T N920AUCS4CPK1 has a note about 14 patches from Samsung, the exact number. (so I seem to be patched if I follow the logic even though Google responded on 11/05/2016 but I dunno how to confirm what's in this Nov 1 2016 security patch in the PK1 firmware.)
It doesn't really matter if they've patched it, you can still downgrade your firmware and security level - even on this variant. I used to go between Marshmallow and Lollipop, as it was required by the ps3 controller app.
Turbine1991 said:
It doesn't really matter if they've patched it, you can still downgrade your firmware and security level - even on this variant. I used to go between Marshmallow and Lollipop, as it was required by the ps3 controller app.
Click to expand...
Click to collapse
Which part are you saying you can downgrade? You can't take the Lollipop firmware and flash it if you're currently on the latest firmware update. It will just fall in odin.
That's just not true. The Verizon model can be flashed in Odin, I've done it a few times myself. Here's someone elses word: https://forum.xda-developers.com/verizon-galaxy-note5/general/downgrade-to-lollipop-5-1-1-verizon-t3368250
It's not impossible, you just need to use an official firmware and may need to downgrade the bootloader.
Turbine1991 said:
That's just not true. The Verizon model can be flashed in Odin, I've done it a few times myself. Here's someone elses word: https://forum.xda-developers.com/verizon-galaxy-note5/general/downgrade-to-lollipop-5-1-1-verizon-t3368250
It's not impossible, you just need to use an official firmware and may need to downgrade the bootloader.
Click to expand...
Click to collapse
Uh, Sir, the link you just posted.. *I* am the original poster of that and I'm telling you with official firmware you still CANNOT go from the latest firmware update of Marshmallow back to Lollipop! I even stated in my OP that it's not going to once you accept the BPI3 firmware update you're done and stuck on Marshmallow with no way to go back not even if you follow my original instructions it won't work!! The bootloader is no longer downgradeable thanks to Verizon!
Dirty cow or not is irrelevant. We can upgrade or downgrade and we're able to root this phone just like any other variant.
The only issue is the bootloader's signature checking.
so this is crap, thanks for the further investigation
There's a simply check for a value that they are calling a binary number. What is that? Certain versions will work together but past a certain point something changes. (most often the security storage binaries) .. So the bootloader checks to see if binary # >= current firmware binaries ... If you are on S3 binary and you attempt to flash S2 binaries the bootloader newly rejects this.
I can and have written a tool to over come this problem but there is one catch. system.img is too large for me to hack into place in this way. If I can't rewrite system.img then we are still stuck. ;*(
So what am I doing? I need root so I can just dd write system.img from /sdcard/ to the partition. that's it..
Stop listening to people who are not spending all their free time looking at the Note 5.. I already have too much access for the Note 5 to survive now.. It's going down, it is not the super secure device that will refuse to boot 'ever again' if you modify stuff that Samsung tried to claim.. that was lies and nonsense (don't hack BOTA0 or BOTA1 though)... I haven't tested changes to this partitions, all others have suffered a beating from me. (if you disable certain packages without disabling other packages it will refuse to boot, no wiping will help, reflash time)
droidvoider said:
There's a simply check for a value that they are calling a binary number. What is that? Certain versions will work together but past a certain point something changes. (most often the security storage binaries) .. So the bootloader checks to see if binary # >= current firmware binaries ... If you are on S3 binary and you attempt to flash S2 binaries the bootloader newly rejects this.
I can and have written a tool to over come this problem but there is one catch. system.img is too large for me to hack into place in this way. If I can't rewrite system.img then we are still stuck. ;*(
So what am I doing? I need root so I can just dd write system.img from /sdcard/ to the partition. that's it..
Stop listening to people who are not spending all their free time looking at the Note 5.. I already have too much access for the Note 5 to survive now.. It's going down, it is not the super secure device that will refuse to boot 'ever again' if you modify stuff that Samsung tried to claim.. that was lies and nonsense (don't hack BOTA0 or BOTA1 though)... I haven't tested changes to this partitions, all others have suffered a beating from me. (if you disable certain packages without disabling other packages it will refuse to boot, no wiping will help, reflash time)
Click to expand...
Click to collapse
I tried to tell everyone that this was straight up BS back when I was asking for help and no one wanted to risk it nor did they believe me.. Instead they chose to believe this instead of me..
http://www.idigitaltimes.com/samsung-galaxy-note-5-galaxy-s6-edge-specs-and-features-att-and-verizon-models-wont-468357
Would flashing the tar file in the OP give me the ability with ADB to delete, rename or change the bootsamsung.qmg and bootsamsungloop.qmg files? All I want to do is swap those out for another set. Would I then need to flash something else to bring it back to normal?
MrMike2182 said:
I tried to tell everyone that this was straight up BS back when I was asking for help and no one wanted to risk it nor did they believe me.. Instead they chose to believe this instead of me..
http://www.idigitaltimes.com/samsung-galaxy-note-5-galaxy-s6-edge-specs-and-features-att-and-verizon-models-wont-468357
Click to expand...
Click to collapse
You seem to have a good grasp on the situation and seem to talk sense, so I'll just ask a question. I'm only passing through because I needed some info, but got interested in the thread.
It seems you have the eng boot for the device, but not able to get system to mount rw? Strange because I have checked it and it is a bonafide eng boot.
Anyway I don't own this device, but I thought I'd just share some info that allowed others to get root on a few recent ATT devices with locked bootloaders on MM.
Using Kingroot on the said devices would not work, no matter how many times or which version was used. However flashing the eng boot from the combination firmware (so not even full eng boot as no root shell with adb) and then using Kingroot, Kingroot was able to successfully root these devices even though with some it took several tries. Kingroot was then used to convert to Supersu.
This may have been tried already, but I couldn't see it. Someone tried it with stock, but not using the eng binary.
The combination eng binary allows the device to boot in permissive mode with no dm-verity, but doesn't have a root shell or any write access with adb. The full eng boot you have should do the same obviously with the addition of adb root shell.
It's just for info and I'm not claiming it will work on Verizon devices, but it seems to be pretty successful on ATT and Tracfone devices.
Title says it, apologies in advance for my noobiness on the entire topic of rooting. Got lucky and my previous device was supported via kingroot. Just looking for SuperSU permissions so I can enable my hotspot really.
This phone is through straight talk btw. I've tried Kingroot, iRoot, and quite a few others to no avail. I don't currently have internet due to me moving to the butt-crack of nowhere, Tried srsroot but seems like it interferes with USB tether and says it's successfully rooted but nothing happens upon reboot.
Anyone had any success with this? Thanks in advance.
Anyone?
Please help for the love of god.
mobliife said:
Please help for the love of god.
Click to expand...
Click to collapse
CF- Autoroot might do it. I see that it works on other variants for the J7. Here's a link with CF-Autoroot and detailed instructions. Hope it works for you. Let me know how it goes.
http://www.theandroidsoul.com/root-samsung-galaxy-devices-cf-auto-root-odin/
mobliife said:
Title says it, apologies in advance for my noobiness on the entire topic of rooting. Got lucky and my previous device was supported via kingroot. Just looking for SuperSU permissions so I can enable my hotspot really.
This phone is through straight talk btw. I've tried Kingroot, iRoot, and quite a few others to no avail. I don't currently have internet due to me moving to the butt-crack of nowhere, Tried srsroot but seems like it interferes with USB tether and says it's successfully rooted but nothing happens upon reboot.
Anyone had any success with this? Thanks in advance
Is this your first time rooting a device. after srsroot says successfully rooted did you verify root by going into playstore and trying a root check app.
Click to expand...
Click to collapse
I tried srsroot 5.1 multiple exploit and it said rooted. I open root checker and it said phone wasn't rooted. I also tried dr. Phone and they didn't have a working root method for j7 sky pro and i was desperate enough to try king root. None of these worked. The guy than mention c.f. auto root, thats for a version of the j7 that was released in other countries. Those variants of the j7 have exoynus processors and us version have snap-dragon processors so the root procedure might brick your phone.
---------- Post added at 03:46 PM ---------- Previous post was at 03:43 PM ----------
When ever I get some free time I'm going to try using adb commands to try and root.
Hopefully not too much longer before someone can root this thing... I'm also looking!
wondering if anyone has seen this video or tried it??
Code:
https://www.youtube.com/watch?v=UtktE0jccnw
I can't open the link but all the videos iv seen on YouTube seems to be j700's and other variants not for s727v.l From my research the devices are a listed under samsung j models but the they all have different hardware, i.e. boards, processors, chipsets,. I did a cross referience with cf-auto root to try and find a divice with the same hardware and builds, there wasnt any other device with the same hardware that would suggest compatibility. Cf-auto root flashes a root file to your device and if it's not compatible you could completely brick your device
Hello, First of, you shouldn't have used kingroot whatever the situation was
However https://play.google.com/store/apps/details?id=com.inkwired.droidinfo&hl=en
download this and capture the system and device tray
Yeah but it was worth a shot. I figured if it worked I could replace it with superSu. I will post those specs In a few. When ever. I get time and free WiFi in going to try adv root
System and device
I'm going to try adb root method when ever I get the time
Trying this again. I try posting last night but it didn't go through
dorain said:
Trying this again. I try posting last night but it didn't go through
Click to expand...
Click to collapse
Hello,
It did pass, however, your device seems to be a Verizon varient, it's hard to root it and there is no really a method to root it.
Sorry I couldn't help
dorain said:
I can't open the link but all the videos iv seen on YouTube seems to be j700's and other variants not for s727v.l From my research the devices are a listed under samsung j models but the they all have different hardware, i.e. boards, processors, chipsets,. I did a cross referience with cf-auto root to try and find a divice with the same hardware and builds, there wasnt any other device with the same hardware that would suggest compatibility. Cf-auto root flashes a root file to your device and if it's not compatible you could completely brick your device
Click to expand...
Click to collapse
Need to talk to mark manning tell to send thread to me please private matter
Thanks for the look and the reply. Im gonna try crack this one. Ive been preparing my computer with Ubuntu, android sdk, and cleaning old drivers. Iol, I'm gonna see what I can do, hopefully I can break it.
dorain said:
Thanks for the look and the reply. Im gonna try crack this one. Ive been preparing my computer with Ubuntu, android sdk, and cleaning old drivers. Iol, I'm gonna see what I can do, hopefully I can break it.
Click to expand...
Click to collapse
Verizon bootloader is most of time locked you can't flash it.
I may have a method for rooting s727vl. I can't test until I get home where I will have unrestricted data in case something goes wrong. I'm gonna keep this short and simple assuming everyone have
knowledge of using odin.
Developer option usb debugging oem unlock no frp or passwords
Download odin
Download latest superSu, this isn't the same as superuser in the playstore. It's used for rooting systemless root os. Yes that what marshmallow is.
After downloading supersu place it on your phones sd card
This is what I'm not sure on. Download clockwork mod RECOVERY. Zip , not the one in the playstore. And place on pc
Use odin to flash cwm to s727vl
Please refer to guide on installing cwm
After flashing cwm go to it in recovery mode and use cwm to flash the supersu zip file and reboot phone. It could take a few minutes but it should boot with root access. Or wait for auto reboot.
What I'm not sure on is cwm compatibility with s727vl, I couldn't find a yeah or nay on compatibility. Cwm say it's compatible with any android.
Hopefully this will work. Make sure u have your data backed up and your stock rom in case things go south. If anyone try this please let me know the result. I'm anxious to try it but I travel a lot and I can't afford to have data throttled by downloading everything I need and I can't risk doing this until I'm i get home.
Possible root method for s727vl straighttalk
Junior Member17 posts Thanks: 1
I may have a method for rooting s727vl. I can't test until I get home where I will have unrestricted data in case something goes wrong. I'm gonna keep this short and simple assuming everyone have
knowledge of using odin.
Developer option usb debugging oem unlock no frp or passwords
Download odin
Download latest superSu and place on phone sdcard
this isn't the same as superuser in the playstore. It's used for rooting systemless root os. Yes that what marshmallow is.
This is what I'm not sure on. Download clockwork mod RECOVERY. Zip ,not the one in the playstore.
And place it on your pc
Use odin to flash cwm to s727vl
Please refer to guide on installing cwm
After flashing cwm go to it in recovery mode and use cwm to flash the supersu zip file and reboot phone. It could take a few minutes but it should boot with root access. Or may reboot on its own.
What I'm not sure on is cwm compatibility with s727vl, I couldn't find a yeah or nay on compatibility. Cwm say it's compatible with any android.
Hopefully this will work. Make sure u have your data backed up and your stock rom in case things go south. If anyone try this please let me know the result. I'm anxious to try it but I travel a lot and I can't afford to have data throttled by downloading everything I need and I can't risk doing this until I'm i get home.
dorain said:
Junior Member17 posts Thanks: 1
I may have a method for rooting s727vl. I can't test until I get home where I will have unrestricted data in case something goes wrong. I'm gonna keep this short and simple assuming everyone have
knowledge of using odin.
Developer option usb debugging oem unlock no frp or passwords
Download odin
Download latest superSu and place on phone sdcard
this isn't the same as superuser in the playstore. It's used for rooting systemless root os. Yes that what marshmallow is.
This is what I'm not sure on. Download clockwork mod RECOVERY. Zip ,not the one in the playstore.
And place it on your pc
Use odin to flash cwm to s727vl
Please refer to guide on installing cwm
After flashing cwm go to it in recovery mode and use cwm to flash the supersu zip file and reboot phone. It could take a few minutes but it should boot with root access. Or may reboot on its own.
What I'm not sure on is cwm compatibility with s727vl, I couldn't find a yeah or nay on compatibility. Cwm say it's compatible with any android.
Hopefully this will work. Make sure u have your data backed up and your stock rom in case things go south. If anyone try this please let me know the result. I'm anxious to try it but I travel a lot and I can't afford to have data throttled by downloading everything I need and I can't risk doing this until I'm i get home.
Click to expand...
Click to collapse
Modt of Verizon phones has a locked bootloader, they can't be flashed with unsigned images
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?