Background:
So I first suceesfully rooted my device (Samsung S7 SM-G930W8) with Odin, no-verify, and superSU.
I then find out about magisk and decide that I rather use it. (This way I could still use certain apps while rooted)
I did a full unroot and installed TWRP (following multiple guides/tutorials until I found the solution.)
But, I ran into issues...
Problems:
I can no longer enable OEM unlocking in my developer options whether I'm rooted or unrooted
I can't install Magisk as I'm getting "Error 1" and I cannot locate boot.img file. I've searched everywhere and the closest thing I found was boot.ph (it too did not work to resolve error 1.)
Any advice to get a fresh start on this? Or solve these problems? I can be more specific or give more information if required.
Thanks in advance!
ScoobDoob69 said:
Background:
So I first suceesfully rooted my device (Samsung S7 SM-G930W8) with Odin, no-verify, and superSU.
I then find out about magisk and decide that I rather use it. (This way I could still use certain apps while rooted)
I did a full unroot and installed TWRP (following multiple guides/tutorials until I found the solution.)
But, I ran into issues...
Problems:
I can no longer enable OEM unlocking in my developer options whether I'm rooted or unrooted
I can't install Magisk as I'm getting "Error 1" and I cannot locate boot.img file. I've searched everywhere and the closest thing I found was boot.ph (it too did not work to resolve error 1.)
Any advice to get a fresh start on this? Or solve these problems? I can be more specific or give more information if required.
Thanks in advance!
Click to expand...
Click to collapse
UPDATE:
I thought I'd include what my Download Mode says in the event it is helpful:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G930W8
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: OFF
Secure Download : Enabled
WARRANTY VOID: 1 (0X0500)
RP SWREV: B:7 K:4 S:5
Also, a guy on reddit offered to help, but I wasn't sure whether to trust him as he wanted to use teamviewer (I've heard things about vulnerabilities in RATs) so that kind of sketched me out on whether or not to trust him. But, he did ask if I had a GSPN login, which I do not... Is that needed to fix this or can I fix this with the use of Odin or TWRP?
There may be a chance that in 7 days I could enable OEM unlocking again. But, trying to trick my phones date & time (a method for bypassing RRM/KG locks) did not work.
Thanks in advance to anyone that may reply!
I'm still going to continue researching and will update with any changes :good:
ScoobDoob69 said:
UPDATE:
I thought I'd include what my Download Mode says in the event it is helpful:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G930W8
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: OFF
Secure Download : Enabled
WARRANTY VOID: 1 (0X0500)
RP SWREV: B:7 K:4 S:5
Also, a guy on reddit offered to help, but I wasn't sure whether to trust him as he wanted to use teamviewer (I've heard things about vulnerabilities in RATs) so that kind of sketched me out on whether or not to trust him. But, he did ask if I had a GSPN login, which I do not... Is that needed to fix this or can I fix this with the use of Odin or TWRP?
There may be a chance that in 7 days I could enable OEM unlocking again. But, trying to trick my phones date & time (a method for bypassing RRM/KG locks) did not work.
Thanks in advance to anyone that may reply!
I'm still going to continue researching and will update with any changes :good:
Click to expand...
Click to collapse
I was told recently that if one has TWRP installed they need not to have OEM unlocking enabled.
Yesterday I attempted to reinstall the stock firmware for my phone, but Odin froze every time. I tried three seperate version of Odin, including the latest version.
I might try again on a different computer and with a different usb cable... we'll see what happens :crying:
Related
This is for both US Cellular Samsung S6 and S6 Edge variant. Thanks also goes to @g.lewarne for his work on Unikernel as a couple of their ramdisk/kernel commits were needed to get this going. Also, thanks to @datajosh for this template And @bpdev for testing the 925R4 version...
This will trip KNOX. It will. Trip. KNOX. IF YOU HAVE NOT TRIPPED KNOX YET - THIS WILL TRIP IT. ALSO - you CANNOT downgrade after you take the OTA so be sure you want it.
I hope that's clear enough?
Instructions:
After you've booted into OF7, go to Settings > About device and tap Build number 7 times to enable Developer Mode.
Go back and select Developer options and turn on OEM unlocking
Reboot in to download mode (Power + Home + Volume Down)
Use ODIN to flash 925R4root.tar or 920R4root.tar (depending on your device)
After your phone boots you will now have root!
If you notice constant messages about security issues because of KNOX and the kernel being permissive. To get rid of these, open Titanium Backup (or your personal favorite app freezing app) and freeze SecurityLogAgent.
Downloads
925R4 - http://1drv.ms/1HeDWXO
925R4 Source
920R4 - http://1drv.ms/1NUVJ8B This is untested...I did not have a tester for this version....
920R4 Source
The 925R4 version may or may not work with the Sprint 925P variant...no working data confirmed!
ENJOY!
Man I wish we could just find a damn exploit already lol gone this long without tripping Knox. And with the fact that I've received the "Fingerprint scanner has encountered an error, use your backup password." error 4-5x already I'm worried about tripping Knox, although you'd think they'd still fix that considering just rooting shouldn't break the scanner lol.
So this requires me to stay on that kernel huh? I couldn't go back to stock kernel huh?
cpfeifer said:
Man I wish we could just find a damn exploit already lol gone this long without tripping Knox. And with the fact that I've received the "Fingerprint scanner has encountered an error, use your backup password." error 4-5x already I'm worried about tripping Knox, although you'd think they'd still fix that considering just rooting shouldn't break the scanner lol.
So this requires me to stay on that kernel huh? I couldn't go back to stock kernel huh?
Click to expand...
Click to collapse
You could go back to the stock kernel, but you would loose root. Also as stated above you would trip knox.
someone on a sprint s5 edge said the only thing they noticed didnt work was data..just posting for them since they under 10 post..so thats awesome! if we could get data goin..we can have root!!
---------- Post added at 03:29 PM ---------- Previous post was at 03:17 PM ----------
this kernel has working data on the edge...if you could port the data stuff in yours it should be fine http://forum.xda-developers.com/spr...t/5-1-1-stock-of7-kernel-root-7-4-15-t3150350
Does this method then require flashing a custom recovery then SuperSU.zip (or CF Auto Root)? Just curious because all that's in the .rar is a boot.img and some are having issues with following the method and not having root immediately.
borxnx said:
Does this method then require flashing a custom recovery then SuperSU.zip (or CF Auto Root)? Just curious because all that's in the .rar is a boot.img and some are having issues with following the method and not having root immediately.
Click to expand...
Click to collapse
It should be flashed using ODIN...I believe I updated the link in the OP to fix that issue since I derp'd...
Sent from my SM-G920P using Tapatalk
Flashed on a 920r4, but it is not rooted.
Funny enough, I get knox warnings about threats and stuff. But when I check with root checker, I don't have root.
sintro said:
Flashed on a 920r4, but it is not rooted.
Funny enough, I get knox warnings about threats and stuff. But when I check with root checker, I don't have root.
Click to expand...
Click to collapse
Perhaps you still have to install SuperSU or another super user app.
Sent from my SM-G925R4 using Tapatalk
cpfeifer said:
Perhaps you still have to install SuperSU or another super user app.
Sent from my SM-G925R4 using Tapatalk
Click to expand...
Click to collapse
I reflashed back to stock, then installed supersu. Then opened it up, obviously it said "supersu binary not installed". Next, I flashed this kernel and once booted up supersu still repeats the previous message. In addition, root checker shows that phone is not rooted.
The only thing in the .tar file, for 920r4 at least because that's all I downloaded, is a modified kernel. Nothing about SuperSU or its binaries. This method alone does not root. This merely installs a modified SELinux permissive stock kernel. More steps are necessary to obtain root. You must flash either CF Auto Root or a custom kernel + SuperSU.zip.
Bump? Nobody? OP, amirite? Because the method you describe, and thank you so much for the SELinux permissive kernel, does not complete all of the steps between stock and fully rooted.
borxnx said:
Bump? Nobody? OP, amirite? Because the method you describe, and thank you so much for the SELinux permissive kernel, does not complete all of the steps between stock and fully rooted.
Click to expand...
Click to collapse
920R4 http://1drv.ms/1HzSj73 try this...
I've redone the ramdisk and use the exact same files on my 920P...and kept the carrier parts for US Cellular...
Let me know if this works...
djvoleur said:
920R4 http://1drv.ms/1HzSj73 try this...
I've redone the ramdisk and use the exact same files on my 920P...and kept the carrier parts for US Cellular...
Let me know if this works...
Click to expand...
Click to collapse
Thank you for redoing the ramdisk.
Will try out and let you know.
Anyone experiencing issues with 925r4? I have service but see no signal bars no matter where I go.
https://youtu.be/y7EpSirtf_E
djvoleur said:
920R4 http://1drv.ms/1HzSj73 try this...
I've redone the ramdisk and use the exact same files on my 920P...and kept the carrier parts for US Cellular...
Let me know if this works...
Click to expand...
Click to collapse
This does indeed work. Thank you so much!
Edit...Added instructions I used to complete the root process.
First of all, I wanted to thank the OP of this thread for posting this guide and getting me headed in the right direction.
Credit to @djvoleur
I just wanted to share the method I used to root my USC Galaxy S6 with the Android 5.1.1 update. You will notice that the instructions are similar in the beginning. I added the extra steps that I used to complete the root process. I do not know if this method works for the Edge version.
As the OP states: This will trip knox. Personally, it doesn’t matter to me. I am too impatient and too much of a flash-a-holic to wait for a method that doesn’t trip knox.
Also, I am not a dev and I am unable to answer any questions other than how I obtained root. I am not responsible for any damage that might happen to your phone. Follow this procedure at your own risk.
Having stated these disclaimers, it really isn’t very difficult to implement. I’ve done it twice and both times worked perfectly.
Files you will need for flashing in Odin:
Odin 3.10.7 found here: http://tinyurl.com/puyq4v9
Rooted kernel 920R4root.tar found in the OP.
TWRP 2.7.8.0 (Sprint version, but I can confirm it worked for me. YMMV.) Here: http://tinyurl.com/phvrkaf
Files for flashing in TWRP:
Updated V-Kernel 920R4-071615.zip found here: http://tinyurl.com/o2h8rv4
Super SU v2.49 (beta) found here: http://tinyurl.com/or6mmqr
Now, PLEASE read these instructions before starting so that you will have a good understanding of what to do. After reading, you may begin.
Don’t forget to put the files for flashing in TWRP on your SD card (phone) before beginning this process.
After you've booted into OF7, go to Settings > About device and tap Build number 7 times to enable Developer Mode.
Go back and select Developer options and turn on OEM unlocking
Boot into download mode (Power + Home + Volume Down)
Use ODIN to flash 920R4root.tar
Use ODIN to flash TWRP and make sure that reboot is NOT checked in options.
Unplug the phone and hold the Power + Volume Down key to reboot. When the screen goes blank, quickly hold the Power + Home + Volume Up key to boot into TWRP. If it doesn’t boot to TWRP, you may have to start over.
In TWRP flash the updated V-Kernel file first, then the Super SU file, and then reboot.
After your phone boots you will now have root!
If you notice constant messages about security issues because of KNOX and the kernel being permissive. To get rid of these, open Titanium Backup (or your personal favorite app freezing app) and freeze SecurityLogAgent. (Worked for me.)
You now should be able to install Chainfire's Super SU app from the Play Store, and you can also use Root Checker to confirm you are rooted.
Good Luck!
Would this work on G920R7... J4 (rather than OF7) 5.1.1? That's what I have.
I see there is a PC1 update available also for my G920R7 which is 6.0 marshmallow.
Hard to believe I've had this device for a year with no root... Anyone can help me get this rooted? Thanks!
so after installing the intial kernel that did not work I scrolled through and saw the updated version...you should probably update the link for the untested r4 to the working version later posted...
my problem is that Im unable to load in anything but download mode due to kernel not seandroid enforcing basically not enabling me to load into recovery mode so I need the zipped version of the kernel to install via odin in download mode if possible otherwise im waiting on a 2 hour download of the stock kernal to install
i just picked up a us cellular note 5 (SM-N920R4 on OJ5)
its trying to download and update to a new firmware so i turned off wifi and that appears to stop it but i cant do any of the gazillion updates from play store like we normally do after you receive a new phone or do a factory data reset.
please advise what i need to do since im already on OJ5 and can not connect to wifi as it will auto install whatever update its trying to download.
thanks again
en11gma said:
i just picked up a us cellular note 5 (SM-N920R4 on OJ5)
its trying to download and update to a new firmware so i turned off wifi and that appears to stop it but i cant do any of the gazillion updates from play store like we normally do after you receive a new phone or do a factory data reset.
please advise what i need to do since im already on OJ5 and can not connect to wifi as it will auto install whatever update its trying to download.
thanks again
Click to expand...
Click to collapse
Use TB to remove the update apps - green phone icons in TB. That's how it always gets stopped on any samsung.
Hello,
As the title suggests, I'm looking for a way to completely backup my stock device without root.
This would include firmware and stock recoveries, basically system files - as I'm not really too terribly worried with saving personal data.
I've searched through various threads but I think I'm in one of those "in-over-my-head" situations, so let me explain why I haven't just flashed a custom recovery and made a nandroid backup.
My device is the C-Spire Note 5, SM-N920R7, running 5.1.1 - recognized by Smart Switch with no updates available.
I received this device in the mail today - because I somehow managed to brick my old device with the "custom binary blocked" FRP.
There is no stock firmware available for download to flash in Odin, and it was impossible to boot the device in regular or recovery mode, leaving me with Download mode.
In order to root my old device, I had to unlock the OEM in Developer Settings and flash the "Beastmode" kernel via Odin:
http://forum.xda-developers.com/spr...rnel-beastmode-modified-stock-1-0-sm-t3196174
Then, I flashed a TWRP recovery and used it to install SuperSU - and voila! I had rooted my device.
Fast forward a few months... My battery died one day and it somehow triggered the FRP lock - with only Download mode available and no C-Spire stock firmware to flash.
Naturally, I want to root my device again, but first I want to create a complete backup of my device that would be flashable in Odin even with the FRP lock on.
So ladies and gentlemen, any help or advice would be appreciated.
I would of course, upload my firmware publicly so that anyone else using this device doesn't brick their phone like I did.
Did you ever get an answer to this? I'm in the same boat and want to do the same thing.
theophile2 said:
Did you ever get an answer to this? I'm in the same boat and want to do the same thing.
Click to expand...
Click to collapse
The only way I've seen involves capturing temporary files during an update through Kies or Smart Switch.
Being on C-Spire, that probably will not ever happen.
Maybe C-Spire will get it together and push out 6.0.1 OTA like the rest of the world - as well as actually providing an alternate (non-OTA) download method.
Apparently some guy on the C-Spire Dev forums paid for a ROM on a Chinese site that works with our phones - which would serve as a nice backup if he would ever upload it.
I asked him to - and apparently he contacted the admins asking for a way to upload the file to the forums.
After they responded to him, he must have never uploaded the file.
i know this is a newer phone but i'm still pretty surprised i haven't been able to find anyone that's rooted it yet. i've been all over the internet it seems. this is the :
Samsung Galaxy J3(6)
SM-J320VPP
Android 6.0.1 Marshamllow
Verizon pre-paid plan/network
i see lots of videos and guides for other j320f or j320p (close but no cigar) and nothing works. what i've tried so far:
- Dev mode enabled, USB debugging and OEM unlocked.
- any/all 1 click root apps. none worked, and i'd like to avoid these anyway unless you know it works 100% for my version. at this point i'll try anything.
- recovery / flash superSU. only i haven't even gotten past flashing a recovery. i've tried several different versions of Odin with several different versions of recovery .tar's and for each combination i've tried Odin simply fails. big red FAIL button in upper left corner. sadness. this seems like what i need help with. i have SuperSU downloaded so if i can just get a custom recovery working for my phone i'm hoping it's a simple process from there of booting into the custom recovery and then installing the SuperSU. presto.
is there no hope? is there no tested, confirmed working recovery that i can flash to my phone using Odin? i've tried Odins 3.07, 3.09, and 3.11.1. various custom recovery .tars but the only one i know for sure is the J2 version official from TWRP's website (yes i know it says J2 but someone on another thread said it's similar enough to someone ELSE's model "j320f" or something so i gave it a shot) the other recovery .tars i tried are suspect since they had generic names "recovery.tar" and were downloaded from links provided in many different "guides" that i've googled.
internet, you have failed me. thus do i issue this challenge to all those mighty phone hackers of the land. come forth and slay the evil giant that is my phone's ludicrous security (seriosuly how is this even a thing still in 2016. my phone can do so much more, so much better but for these shenanigans).
thanks so much in advance!
EDIT: not sure about the bootloader. i may be a complete idiot. yes. ok. i'm onto something. gonna post this anyway for any other poor soul that has this version phone, but i think Odin's probably failing because the bootloader is still locked. and Samsung doesn't make this easy like motorola or HTC. T_T. once more into the fray! i'll see if i can't track down a method for unlocking the bootloader on my phone. should i return victorious i'll go ahead and share my steps with the rest of the class.
EDIT2: there is no waking from this nightmare. i dig and dig and dig and can find no root. *sigh*
-- i've got android studio installed. and the java SDK platform-tools which contains the adb.exe, fastboot.exe, etc.
-- something i should explain here: in all these guides whenever there's a step that requires the phone to be connected to the PC, it simply says to, you know...connect your phone. but MY phone by default only uses the cable for battery charging. i have to (on my phone) swipe down from the top, select the "connected for charging" message bringing up "Use USB For" options, then select "Transferring media files" option. THEN my phone shows up both in my windows explorer and displays as a device when i run "adb devices".
--when i run "adb reboot bootloader" this does the same thing as holding down pwr/home/vol down - phone boots up into a blue (teal?) background with a large down arrow in center, below that it says "downloading...do not turn off target". in the upper left are several lines of system font style text:
ODIN MODE
PRODUCT NAME: SM-J320VPP
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: OFF*
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, H1, R1, A1, P1*
SECURE DOWNLOAD: ENABLE
*the R's above may be A's or vice versa...hard to read font. sorry
--but as soon as i've rebooted into this mode, my phone disappears from adb devices' list of devices attached. regardless when i run the "fastboot oem unlock" command from the adb shell on my PC at this point i get the infamous "waiting for any device" message and then, of course, nothing....forever. i've also installed PDAnet but i think it's hitting the same road block where my phone is only using the cable for battery charging and i can't toggle that option from ODIN MODE. there's also a "USB Configuration" choice under development options on the phone that has the same options as "Use USB for" but this doesn't stick when booting into ODIN MODE. sadness. i need to retire my brain thoughts at this point. will post TL;DR. you're a saint of geeks if you've made it through my WoT to here.
EDIT3: just an observation - the only thing (so far) that will detect my phone in ODIN MODE is ODIN itself. is there a way to use ODIN to unlock the bootloader?
TL;DR: i think odin is failing when attempting to flash because of locked bootloader. need help with unlocking bootloader first? phone defaults to use USB cable for charging only so i CAN change that to MTP while phone is on normal and then run "adb reboot bootloader" but then phone vanishes from adb devices list once it reboots (and cable is then only charging). thus, cannot run "adb fastboot oem unlock" cuz it hangs displaying "waiting for any device" -- can i unlock the bootloader on this phone? or did i buy a phone that's IMPOSSIBLE TO ROOT!?!?
I have the same problem! I need to root it to install the Patch to change from CDMA to GSM! Because I tried without root and it tells me "E: Signature verification failed"
Thanks
Still nothing?
This is starting to look hopeless
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
News?
There is nowbody that had been rooted his J3 Verizon yet?? We need help with this trouble!
In this forum (http://forum.xda-developers.com/android/help/galaxy-j3-sm-j320vpp-configuring-cdma-t3414049) Sergio said:
" try root with this root is only for Snapdragon 410 MSM8916
http://forum.gsmhosting.com/vbb/f723...t1994-1946985/ "
The J320VPP has a "1.2 GHz, Quad-Core". There is no place that sais it's a "Qualcomm Snapdragon 410 Msm:8916" processor. You think this suggestion could work?
NerdmastaX said:
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
Click to expand...
Click to collapse
I think I've managed to get the recovery.img with KIES... However flashing the image I've extracted doesn't work but if anyone is ready to help me port a recovery I might try !
Whusky said:
I think I've managed to get the recovery.img with KIES... However flashing the image I've extracted doesn't work but if anyone is ready to help me port a recovery I might try !
Click to expand...
Click to collapse
im gonna try and do a reflash with kies and grab that file myself, ill work a bit on it because i love this phone but no basic root is driving me insane. if you can beat me to posting tell me how you got the file, otherwise ill post here once i find out. I'm not a top of the line developer but i can work my way around and try my best since nobody else is offering to help.
wish me luck.
sorry for the double post but got the files via the verizon software assistant no problem. it ended up in C:\Users\YOURNAME\AppData\Roaming\Verizon_AR\SM-J320VPP_J320VPPVRU1APC3_FACTORY for me, and even decrypted and unzipped itself for me, now we just need to mod a custom thingy into those files and we can work towards rooting. so as i sit here and watch my phone finish flashing back to factory i will look into how we can mod the recovery. if someone is capable of doing it faster i can upload the files very quickly as its only 1.4 gb
well turns out verizon locks the flashing with signature verfication. so unless verizon changes or root is found for marshmellow there will be zero possible root for this phone.
NerdmastaX said:
sorry for the double post but got the files via the verizon software assistant no problem. it ended up in C:\Users\YOURNAME\AppData\Roaming\Verizon_AR\SM-J320VPP_J320VPPVRU1APC3_FACTORY for me, and even decrypted and unzipped itself for me, now we just need to mod a custom thingy into those files and we can work towards rooting. so as i sit here and watch my phone finish flashing back to factory i will look into how we can mod the recovery. if someone is capable of doing it faster i can upload the files very quickly as its only 1.4 gb
Click to expand...
Click to collapse
Hi I'm currently rooted with TWRP 3.0.2 recovery and mabey this might help http://forum.xda-developers.com/general/help/samsung-galaxy-j3-sm-j320fn-how-to-root-t3369511
Sparko612 said:
Hi I'm currently rooted with TWRP 3.0.2 recovery and mabey this might help http://forum.xda-developers.com/general/help/samsung-galaxy-j3-sm-j320fn-how-to-root-t3369511
Click to expand...
Click to collapse
verizon blocks flashing of modified recoveries. so unless someone finds a root exploit for marshmallow we will have no luck.
Has the kingroot method worked for root on your device ??
NerdmastaX said:
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
Click to expand...
Click to collapse
Hi to all, im new here and i am having the exact same problem! You say that there has to be a root specifically for the 6.0.. So i found that in the Chainfire page they have this https://download.chainfire.eu/986/CF-Root/CF-Auto-Root/CF-Auto-Root-j3lteusc-j3lteusc-smj320r4.zip already (i dont know if i can post links, so if i cant, sorry), it is marshmallow but the model is J320R4, so i was wondering if this could be the solution. i'll be waiting here for a response, i seriously love this phone :c
MetAJFA said:
Hi to all, im new here and i am having the exact same problem! You say that there has to be a root specifically for the 6.0.. So i found that in the Chainfire page they have this https://download.chainfire.eu/986/CF-Root/CF-Auto-Root/CF-Auto-Root-j3lteusc-j3lteusc-smj320r4.zip already (i dont know if i can post links, so if i cant, sorry), it is marshmallow but the model is J320R4, so i was wondering if this could be the solution. i'll be waiting here for a response, i seriously love this phone :c
Click to expand...
Click to collapse
No, this is not the solution. When using a utlity like CF Auto Root, it must be specific to your model / carrier. Trying to install that will do 1 of 2 things.
1) Just fail in Odin
or
2) Soft brick your device
Since VZW doesn't bother to put out the full firmware files to reflash the device, it's not worth attempting without having the backup plan of the original firmware to flash via Odin.
an twrp is already available for j320p u can try to root your device using it
es0tericcha0s said:
No, this is not the solution. When using a utlity like CF Auto Root, it must be specific to your model / carrier. Trying to install that will do 1 of 2 things.
1) Just fail in Odin
or
2) Soft brick your device
Since VZW doesn't bother to put out the full firmware files to reflash the device, it's not worth attempting without having the backup plan of the original firmware to flash via Odin.
Click to expand...
Click to collapse
Understood, thank very much you for clearing that out. Since all this is pretty much a kick in the butt, do you think there will be some kind of solution to this or should we just lose hope? :/
can Someone here help me with this.
someone wrote:
I have the same problem, I already got 4G LTE data with the correct APN and also I change to lte/gsm with the help of a network app and with commands in adb shell :
pm clear com.android.providers.telephony
settings put global preferred_network_mode 9
settings put global preferred_network_mode1 9
settings put global preferred_network_mode2 9
Click to expand...
Click to collapse
but i dont know how to initiate this adb mode in the phone. anyone?
anyone fix ?
i have few units J320VPP same problem .. searching for service .
That's a Verizon device with a locked bootloader, you cannot try twrp or modified files meant for 320f or other models on this one.
Sent from my SM-N920G using Tapatalk
So has anyone found any luck with this device? It's driving me crazy not having root
Android: 6.0.1
Build number: MMB29K
Hello people, I was wondering if anyone could please root this device. I am not asking for any custom roms, but maybe just a twrp recovery. I would like to root it, because look at the potential of a phone like this. Maybe we could have a bootloader unlock or something like that. I am ok with dedicating my phone to be a dev board. Also, I have tried all of the major rooting tools, and its a no-go. I've even tried SRS-ROOT and that is a failure even though it says that it works. Any help would be appreciated. -Thanks
Have you had any luck I'm also looking for a root same specs... Preferably a no computer solution.....
Root successful...........but at&t?
I was able to root with firmware version J120AUCS3AQE1 but because mine is an AT&T phone the bootloader is "locked and signed" meaning it's never going to unlock........? I have the latest version of firmware that came out in may 2017 and it will be available to you as soon as I can post an outside web address............ Every Recovery image that I flashed caused everything to fail and a big triangle that said AT&T detected software on your device that is not allowed on our device so I guess this one is never really your own........ but you can Root with Kingroot and supersume pro to get rid of bloatware and such but other than that no custom stuff on this one.
If Kingroot keeps freezing just restart phone and keep trying it took me a long while to obtain root.
mechanicguy30 said:
I was able to root with firmware version J120AUCS3AQE1 but because mine is an AT&T phone the bootloader is "locked and signed" meaning it's never going to unlock........? I have the latest version of firmware that came out in may 2017 and it will be available to you as soon as I can post an outside web address............ Every Recovery image that I flashed caused everything to fail and a big triangle that said AT&T detected software on your device that is not allowed on our device so I guess this one is never really your own........ but you can Root with Kingroot and supersume pro to get rid of bloatware and such but other than that no custom stuff on this one.
If Kingroot keeps freezing just restart phone and keep trying it took me a long while to obtain root.
Click to expand...
Click to collapse
Could you please provide detailed steps to root J120A, I also have the same firmware version and my Att phone is unlocked, just need to root the device but couldn't get enough details to root it.
Appreciate your quick help.
[email protected] said:
Could you please provide detailed steps to root J120A, I also have the same firmware version and my Att phone is unlocked, just need to root the device but couldn't get enough details to root it.
Appreciate your quick help.
Click to expand...
Click to collapse
I used cf-autoroot by Chainfire(of the SuperSU fame) it's a little zip package his website(although the thread and q&a is here on xda) what give u not just the root tool, but a XWM custom for ur divice(our device, rather, lol) AND the simple to use tool called Odin to flash it all 4 you!
I can't give links yet, but just search c'f-autoroot chainfire' inside xda, and it was either the second or 3rd link.
Step by step instructions incl!
Hope that helps!
Hi, everyone. I've successfully rooted several Android phones in the past, but this one's got me stumped. Has anyone successfully rooted this specific model, and if so, how?
I have a J1 mini prime, specifically a J106M. It is running Marshmallow 6.0.1 with a pending update that I've paused. I was under the impression the bootloader would be unlocked since it's not tied to a carrier. I now assume it isn't because I've tried:
kingoroot, kingroot, iRoot, towelroot (doesn't work with modstring codes either), latest framaroot (device not vulnerable to exploits error), framaroot 1.5.3 (same error), chainfire (causes soft brick bootloop, but has since been restored).
I can't even figure out how to verify if the bootloader is unlocked for sure. I tried using ADB. cd fastboot command simplay restarts the phone, and fastboot oem unlock command my phone or just sits there saying "waiting for device."
When I boot the phone holding down the volume, home, and power buttons, it brings me to a blue screen that I believe is Odin mode. Others seem to get a different screen that has the bootloader info right there.
It's been a few weeks since I've had time to mess with this. I'm pretty sure that's everything I attempted.
To verify, I have developer mode on, OEM unlocking on, debugging on, allow unknown sources on.
Other specs:
Baseband version : J106MUBU0AQF1
Kernel: 3.10.65-11653963
Build: MMB29Q_J106MUBU0AQF2
Thanks in advance to anyone who can assist a semi-noob. I've never posted on a forum before, and I'm not usually one to ask for help, but I'm out of ideas here lol.
Hello Bahamut,
Are you familar with the Odin tool flashing Samsung firmware? If yes, there is a universal root method Magisk root. There are two ways to root using Magisk:
1. install a TWRP recovery (flash by Odin) & install Magisk Root using TWRP recovery
2. Extract boot.img from the firmware; modify it by Magisk apk; flash the modified img by Odin.
Both ways successfully rooted my Samsung J3 Pro. I've google search for a while & see firmware/TWRP are available for your device J106M.
You should study Odin, Magisk before you go ahead.
Thanks. Somewhat familiar, I was saving that as a last resort out of apprehension that I completely brick the device lol I used Odin when attempting the chainfire files.
I forgot I had downloaded TWRP at one point, but I must be missing something because it appears to be a catch 22 as TWRP was asking for root access in the first place to perform this function. Is there a work around such as using a PC version instead of the app or am I just way off base here?
If TWRP recovery has a problem, you could try method 2 which involve Odin flashing only.
chankk0101 said:
If TWRP recovery has a problem, you could try method 2 which involve Odin flashing only.
Click to expand...
Click to collapse
Unfortunately, the Odin flashing is how I wound up soft-bricking it twice and decided I'd need assistance on this model. I was hoping someone could walk me through it with the specifics, but I guess this isn't a very popular phone.: