Root for J3 v 3rd Gen? Model SMJ337VZKA - Samsung Galaxy J3 (2017) Questions & Answers

Hello, I'm getting in a J3 (2018) V 3rd Gen from Verizon and it's impossible for me to find anything for this model, thus far. Has anyone had any success rooting or unlocking this phone?
SMJ337VZKA

torsitch said:
Hello, I'm getting in a J3 (2018) V 3rd Gen from Verizon and it's impossible for me to find anything for this model, thus far. Has anyone had any success rooting or unlocking this phone?
SMJ337VZKA
Click to expand...
Click to collapse
You won't be able to root that device. It's bootloader locked.

ashyx said:
You won't be able to root that device. It's bootloader locked.
Click to expand...
Click to collapse
Are you certain of that? :crying: I can deal with a locked bootloader but not being able to root it is disappointing

Just for other peoples' reference, the phone came in today and the model on the box is indeed SMJ337VZKA.
SW-VER or Firmware: J337VVRU1ARG1 which I believe I've seen before online (looks familiar). Other documentation online for this phone on Samsungs site and Verizon suggested to me it would have the J337VPP firmware, so it is interesting indeed.

torsitch said:
Hello, I'm getting in a J3 (2018) V 3rd Gen from Verizon and it's impossible for me to find anything for this model, thus far. Has anyone had any success rooting or unlocking this phone?
SMJ337VZKA
Click to expand...
Click to collapse
I requested a more appropriate thread for your device on xda's new device forum requests thread. I recommend you to buy an lg phone because they still have bootloader unlock methods as far as i can tell. since the device your looking at is from verizon well i say your luck isn't there because verizon is notorious for locking bootloaders on all phones.

ashyx said:
You won't be able to root that device. It's bootloader locked.
Click to expand...
Click to collapse
Hi. Is that going to be the case for att variant also? I had a sm-j320a with a locked bootloader and you were able to get us an Odin flashable engineering root. Is that out of the realm of possible anymore?

J337VVRU1ARG1_ENG_boot_noidodroid.tar.md5.zip
jonpjingleheimler said:
Hi. Is that going to be the case for att variant also? I had a sm-j320a with a locked bootloader and you were able to get us an Odin flashable engineering root. Is that out of the realm of possible anymore?
Click to expand...
Click to collapse
I have the english boot for this, here download - (Attachment at bottom of post)
Samsung Galaxy J3 2018
9/29/2018
ENG Boot
File Information:
Device Name :
J3 2018
Device Model :
SM-J337V
Version :
J337VVRU1ARG1
OS Version :
File Type :
ENG Boot
Brand :
Samsung
File Size :
21.59 MB
File Name :
J337VVRU1ARG1_ENG_boot_noidodroid.tar.md5.zip
Instructions :
For Samsung Galaxy android devices only.
Extract the (Zip,Rar,7z) file using 7z.
Download Odin
Extract Odin ZIP file
Open Odin.exe
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button and you know the rest

<OSM> MD5 hash value is invalid
repacking without md5 gives a different error
<ID:0/009> boot.img
<ID:0/009> RQT_CLOSE !!
<ID:0/009> Complete(Write) operation failed.

dosent work, say check fail
ant other ideas to bypass Google lock?
Samsung Galaxy J3 2018
9/29/2018
ENG Boot
File Information:
Device Name :
J3 2018
Device Model :
SM-J337V
Version :
J337VVRU1ARG1
OS Version :
File Type :
ENG Boot
Brand :
Samsung
File Size :
21.59 MB
File Name :
J337VVRU1ARG1_ENG_boot_noidodroid.tar.md5.zip
Instructions :
For Samsung Galaxy android devices only.
Extract the (Zip,Rar,7z) file using 7z.
Download Odin
Extract Odin ZIP file
Open Odin.exe
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button and you know the rest[/QUOTE]
---------- Post added at 08:01 PM ---------- Previous post was at 07:59 PM ----------
I was curious if you have had any success with rooting your device. I am stuck, any help would be appreciated.
ashyx said:
You won't be able to root that device. It's bootloader locked.
Click to expand...
Click to collapse

I might be able to root this with our boot root method. Would just need to get the boot.img and give it a try. Ill try to give it a run for its money. While not likely there is still a chance. Not the first boot loader locked device rooted.

P just to catch up this was able to be rooted via or method but it's just a work root

Run sd card as internal storage?
Can you put an sd card in this phone and format the sd card to run as internal storage? If anyone knows please let me know.
P.S. Can this be rooted as well?

Computerguy777 said:
Can you put an sd card in this phone and format the sd card to run as internal storage? If anyone knows please let me know.
P.S. Can this be rooted as well?
Click to expand...
Click to collapse
I don't think you can use a SIM card in that specific model for adopted storage but you can always use app2sd which works great or that other one I forget its name but it is the other top one the competitor of app2sd. I always just use app to SD for most Parts on older phones
Sent from my SM-G955U using Tapatalk

@ashyx So i bought a license for Chimera to temp remove KGLock on the j337u, to unlock OEM toggle.
After flashing the patched boot, almost instantly the phone locks up with a message saying something about Needing Authorization to use phone. Ive thought of anything and everything trying to disable encryption without TWRP to.flash the zip. no dice so far. So... my question to you would be, willing to port it? I have of files, etc.... i beliebe i remember seeing you tagged as a porter of twrp. If not so, would you be anle to point me in the right direction? would be eXtremely grateful. THANKS in advance for takin the time to read this.
Also, question 2. So, i noticed that ONCE knox connects to internet it updates and throws that lock up. I read its in boot or kernel, is it possivle to flash a another j337u fw, that wont have that baked in? Or will every fw i.find be the same, or...?
-MB

I bypassed Google lock on my galaxy J337 v using the sim pin method and it worked awesome. Only took me a month lol.

Related

NAND write error - same ol' story

Hi all,
I was asked to look at a Galaxy Note 10.1 GT-N8000 by a colleague. It had been upgraded to 4.4.2, all was fine for a few days until it crashed. It's now in a bootloop spinning on the Samsung screen.
I can access Download mode, but no recovery.
Download screen says:
ODIN MODE
Product Name: GT-N8000
Current Binary: Samsung Official
System Status: Official
RP SWREV: A2
I've tried multiple versions of Odin, multiple official firmwares and multiple recoverys (custom/stock). Generally I get a NAND write Start.. FAILED message for most things. One bootloader file gave me "invalid magic string", and by manually packing files to .tar.md5 format, I can get a blue download bar appear on the tablet but nothing ever happens.
Heimdall is able to read the pit file from the device, but not flash anything (unable to confirm end of file transfer)
This seems to either be failed eMMC, or the bootloader is locked and I just haven't hit the correct software yet. I've been on this for days and don't seem to be getting anywhere.. Where do I go from here? And am I correct in thinking that I cannot access ADB from download mode; the device would need to boot to enable USB debugging?
Thanks in advance.
See PIT files flashing .
http://forum.xda-developers.com/showthread.php?t=2363703
Hi JJEgan,
Forgot to include that in my original post.
I've tried a few PIT files with no success. It fails at re-partitioning with Odin, and fails to transfer the pit with Heimdall.
Cheers
artois7 said:
Hi all,
I was asked to look at a Galaxy Note 10.1 GT-N8000 by a colleague. It had been upgraded to 4.4.2, all was fine for a few days until it crashed. It's now in a bootloop spinning on the Samsung screen.
I can access Download mode, but no recovery.
Download screen says:
ODIN MODE
Product Name: GT-N8000
Current Binary: Samsung Official
System Status: Official
RP SWREV: A2
I've tried multiple versions of Odin, multiple official firmwares and multiple recoverys (custom/stock). Generally I get a NAND write Start.. FAILED message for most things. One bootloader file gave me "invalid magic string", and by manually packing files to .tar.md5 format, I can get a blue download bar appear on the tablet but nothing ever happens.
Heimdall is able to read the pit file from the device, but not flash anything (unable to confirm end of file transfer)
This seems to either be failed eMMC, or the bootloader is locked and I just haven't hit the correct software yet. I've been on this for days and don't seem to be getting anywhere.. Where do I go from here? And am I correct in thinking that I cannot access ADB from download mode; the device would need to boot to enable USB debugging?
Thanks in advance.
Click to expand...
Click to collapse
I've been facing the same thing these days. I was able to install a STOCK ROM here that worked. Well, it's a 4.0.4 android version and it's not recognizing my SIM card, hahaha but it worked until I figure out how to get back to my Gnabo rom OR any other one that can work properly and be rooted after. I can't tell that the same rom i used will work for you cause of the region, but If you would like to try, I can post here and you can flash it and see what happens. Although there is PIT files for 4.0.4 that might me suitable for the rom I've used. =D
vitortakeda said:
I've been facing the same thing these days. I was able to install a STOCK ROM here that worked. Well, it's a 4.0.4 android version and it's not recognizing my SIM card, hahaha but it worked until I figure out how to get back to my Gnabo rom OR any other one that can work properly and be rooted after. I can't tell that the same rom i used will work for you cause of the region, but If you would like to try, I can post here and you can flash it and see what happens. Although there is PIT files for 4.0.4 that might me suitable for the rom I've used. =D
Click to expand...
Click to collapse
What were your symptoms? worth a shot. Thanks.
I have a problem on /efs stuff, well so far I wasn't able to solve it, but as I said, the only rom that was able to be installed was the 4.0.4.
That is the rom i've used.
http://eusouandroid.com/tutorial-rom-original-galaxy-note-10-1-gt-n8000-android-4-0-4/
artois7 said:
Hi all,
I was asked to look at a Galaxy Note 10.1 GT-N8000 by a colleague. It had been upgraded to 4.4.2, all was fine for a few days until it crashed. It's now in a bootloop spinning on the Samsung screen.
I can access Download mode, but no recovery.
Download screen says:
ODIN MODE
Product Name: GT-N8000
Current Binary: Samsung Official
System Status: Official
RP SWREV: A2
I've tried multiple versions of Odin, multiple official firmwares and multiple recoverys (custom/stock). Generally I get a NAND write Start.. FAILED message for most things. One bootloader file gave me "invalid magic string", and by manually packing files to .tar.md5 format, I can get a blue download bar appear on the tablet but nothing ever happens.
Heimdall is able to read the pit file from the device, but not flash anything (unable to confirm end of file transfer)
This seems to either be failed eMMC, or the bootloader is locked and I just haven't hit the correct software yet. I've been on this for days and don't seem to be getting anywhere.. Where do I go from here? And am I correct in thinking that I cannot access ADB from download mode; the device would need to boot to enable USB debugging?
Thanks in advance.
Click to expand...
Click to collapse
I found the solutions from another forum.. It's must repair with Z3X box flasher..
forum*gsmhosting.com/vbb/f672/n8000-logo-only-done-via-z3x-jtag-direct-emmc-step-step-inside-1959278/
Can anyone in the UK do this for me? Happy to pay obviously!
derekcfoley2 said:
Can anyone in the UK do this for me? Happy to pay obviously!
Click to expand...
Click to collapse
Local mobile repair shop that carries the tool .
Sent from my SM-N930F using XDA-Developers mobile app

Custom Binary Blocked By FRP Lock - after regular boot

Hi all,
I have this model
Phone: SM-G955F
Android version: 7.0
Build number: NRD90M.G955FXXU1AQDD
I haven't touched anything or updated anything in at least 6 months and the work has been working fine.
I did update yesterday the "Samsung music" app however, not sure if that has anything to do with my problem.
This morning I got a message "Please restart your device, some apps are overloading the system".
So I did a reboot and now the device won't start.
I hate the red message "Custom Binary Blocked By FRP Lock" and the device stays turned off.
I didn't touch anything, so what on earth caused this?!
OEM Lock appears to be ON. FPR Lock is also ON now.
I had the phone rooted when I bought it but I'm using stock firmware.
Also, haven't had any issues in over 6 months so this I am very curious what could cause this to suddenly happen.
I read some guides that I have to re-flash stock firmware again, but I don't see how that will prevent the issue from happening again
Please help
I downloaded Odin and then what looks like the latest stock firmware.
Not sure how that is going to help. I had stock firmware before too
Hum. What can you boot into, recovery (is it stock recovery)? download mode? will it boot to setup in system, as it should if you have an FRP happening.
I had a nightmare of a day yesterday.
Downloaded the latest stock rom and flashed it using Odin. That worked fine.
Then I added TWRP and the phone got soft-bricked because apparently TWRP is not compatible with any of the latest firmware versions (who knew!)
Then I spent hours looking at hacks and found that Notorious zip that you can flash after getting into TWRP via the old BL/smash Start on Odin trick
Then phone showed verification error with the only option to Wipe all data (which I didn't want to do)
Then I managed to reflash the latest stock rom and leave it unrooted for now.
It's a learning experience but I don't like the high stress levels.
The most important thing is that I did nothing to cause the FPR lock and I'm now afraid it might randomly happen every few months
nkomp18 said:
I had a nightmare of a day yesterday.
Downloaded the latest stock rom and flashed it using Odin. That worked fine.
Then I added TWRP and the phone got soft-bricked because apparently TWRP is not compatible with any of the latest firmware versions (who knew!)
Then I spent hours looking at hacks and found that Notorious zip that you can flash after getting into TWRP via the old BL/smash Start on Odin trick
Then phone showed verification error with the only option to Wipe all data (which I didn't want to do)
Then I managed to reflash the latest stock rom and leave it unrooted for now.
It's a learning experience but I don't like the high stress levels.
The most important thing is that I did nothing to cause the FPR lock and I'm now afraid it might randomly happen every few months
Click to expand...
Click to collapse
Generally for the 955F (Exynos, yes?), it's a pretty straight forward process. Yes, you do have to make sure you have the correct TWRP . . .
https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
once you flash TWRP, right at the end, or just before then end of the flash, press Vol up, Bixby and power to boot directly into TWRP. Should work just fine. If not, usually re-flashing TWRP and a direct boot to recovery works. Sometimes it take a few times to get the key pressing/timing down.
Yeah, you are right, it can feel pretty stressful.
hi, did you finally fix this problem? I have a s9+ stock firm, got TWRP and rooted and has been using it for a couple of months without issue, including reboot. but today I was using a bank app it kept stopping itself, so without further thinking I restarted the phone and got the red FRP lock on the screen. tried getting into TWRP but said it's blocked by FRP lock. then using ODIN I reflashed the same stock firm, got into the phone, everything is there except root, and of course Titanium works no more!
my question is, if anyone is reading this, is the TWRP still there or not? in order to find out I'll have to flip the OEM lock off and tried to get into TWRP, but would that trigger a factory reset? but if the TWRP is not there anymore, in order to root I'll have to do a system wipe. either way it gonna be troublesome. and besides, what's to prevent its happening all over again?
I'd appreciate any help! thanks))
Simple solution to that DONT turn the OEM unlocking OFF
This toggle unlocks the bootloader for use with custom binarys and recoveries such as TWRP toggling the OEM unlocking off will stop any custom recovery from being flashed with odin and will also not allow the custom recovery on it to be booted for security reasons related to the FRP lock
The OEM lock is linked to the FRP lock both are run through the same toggle you would have noticed when you enabled it that a warning message appeared about the device losing all FRP security measures when enabled if you switch this toggle back to off your FRP lock re activates and the custom recovery that is already installed will now be blocked from being used and the system will render it a security issue and will not allow your system to boot,
So again to save you all this trouble in the future DO NOT tuurn off your oem unlock while you have a custom binary installed,
Yes your devices security is gone but this is the cost you pay when you decided you wanted to root your device,
There is an alternative though if you know what your doing enable oem unlock flash TWRP flash your root and what not then when finished if you know how to pull the recovery from stock firmware and make it into a flashable file with odin you can have root and what not and also keep your oem unlock switched to off bu ti strongly suggest do your reaearch if you choose to take this path.
Hope this helps guys
Matty1993 said:
Simple solution to that DONT turn the OEM unlocking OFF
This toggle unlocks the bootloader for use with custom binarys and recoveries such as TWRP toggling the OEM unlocking off will stop any custom recovery from being flashed with odin and will also not allow the custom recovery on it to be booted for security reasons related to the FRP lock
The OEM lock is linked to the FRP lock both are run through the same toggle you would have noticed when you enabled it that a warning message appeared about the device losing all FRP security measures when enabled if you switch this toggle back to off your FRP lock re activates and the custom recovery that is already installed will now be blocked from being used and the system will render it a security issue and will not allow your system to boot,
So again to save you all this trouble in the future DO NOT tuurn off your oem unlock while you have a custom binary installed,
Yes your devices security is gone but this is the cost you pay when you decided you wanted to root your device,
There is an alternative though if you know what your doing enable oem unlock flash TWRP flash your root and what not then when finished if you know how to pull the recovery from stock firmware and make it into a flashable file with odin you can have root and what not and also keep your oem unlock switched to off bu ti strongly suggest do your reaearch if you choose to take this path.
Hope this helps guys
Click to expand...
Click to collapse
thanks Matty! now that I think about it I might have turned OEM unlock off because some bank app suddenly stopped working and I was trying to guess what went wrong.
Matty1993 said:
Simple solution to that DONT turn the OEM unlocking OFF
This toggle unlocks the bootloader for use with custom binarys and recoveries such as TWRP toggling the OEM unlocking off will stop any custom recovery from being flashed with odin and will also not allow the custom recovery on it to be booted for security reasons related to the FRP lock
The OEM lock is linked to the FRP lock both are run through the same toggle you would have noticed when you enabled it that a warning message appeared about the device losing all FRP security measures when enabled if you switch this toggle back to off your FRP lock re activates and the custom recovery that is already installed will now be blocked from being used and the system will render it a security issue and will not allow your system to boot,
So again to save you all this trouble in the future DO NOT tuurn off your oem unlock while you have a custom binary installed,
Yes your devices security is gone but this is the cost you pay when you decided you wanted to root your device,
There is an alternative though if you know what your doing enable oem unlock flash TWRP flash your root and what not then when finished if you know how to pull the recovery from stock firmware and make it into a flashable file with odin you can have root and what not and also keep your oem unlock switched to off bu ti strongly suggest do your reaearch if you choose to take this path.
Hope this helps guys
Click to expand...
Click to collapse
hi i need your help, i have a samsung galaxy s7 and it's locked by frp (sorry for my english but i'm italian), i try to install official firmware by odin but it say an error sboot.bin fail! (with bt file) and say recovery.img fail! (with ap file), now i understand that my bootloader il blocked by oem block, there is a way to unlock by odin mode or others? i can't have access to recovery or phone.
please help me i'm desperate!
corvasce03 said:
hi i need your help, i have a samsung galaxy s7 and it's locked by frp (sorry for my english but i'm italian), i try to install official firmware by odin but it say an error sboot.bin fail! (with bt file) and say recovery.img fail! (with ap file), now i understand that my bootloader il blocked by oem block, there is a way to unlock by odin mode or others? i can't have access to recovery or phone.
please help me i'm desperate!
Click to expand...
Click to collapse
You need to flash the correct bootloader version to your device IE check the binary number on the firmware file and compare to what is listed on download mode
File binarys have the letter U? example is
G930FXXU2ARA1 or G930FXXU3ARA1
Take note of the number
Now in download mode on the device
Find AP SWREV B: ? An example is
AP SWREV B:2 K:0 S:0
The 2 signifies it's a bit 2 bootloader so the firmware package needed for this device would be for example G930FXX"U2"ABCD
all you have to do is match them up,
AP SWREV B1 = U1 or S1
AP SWREV B2 = U2 or S2
AP SWREV B3 = U3 or S3
As for the flash error message " custom binary blocked by frp lock" means someone has tampered with the firmware, I'd assume you didnt get it from sammobile ? or it's not made for model number check the backing to your S7 model number is located at the bottom in small writing
Will be G930"F" for example also compare the letter to the binary file to make sure your flashing the correct model,
Also what version of odin3 are you using to flash as 6.0 to 7.0 binaries can be flashed with V3.12 as the binary files don't use .lz4 compression however 8.0 binaries do use .lz4 compression this is a new type of compression so requires Odin3 3.13.1 as this odin3 has the capabilities to read and flash the .lz4 binaries to the device
And I'm not sure if your aware but the factory binaries dont have OEM unlock in them to remove the FRP however there is a way that I know how to do it on this particular model but it will vary the B:? In download mode and to if a combination rom is available for your binary number COLOR="Silver"]
---------- Post added at 04:08 AM ---------- Previous post was at 03:57 AM ----------
[/COLOR]
snooyy said:
thanks Matty! now that I think about it I might have turned OEM unlock off because some bank app suddenly stopped working and I was trying to guess what went wrong.
Click to expand...
Click to collapse
All good mate , yeah once that OEM unlock is turned back off all security features are re activated that was your problem did you manage to fix it yet if not all you gotta do is flash the stock recovery and you shouldn't lose your data
Matty1993 said:
---------- Post added at 04:08 AM ---------- Previous post was at 03:57 AM ----------
All good mate , yeah once that OEM unlock is turned back off all security features are re activated that was your problem did you manage to fix it yet if not all you gotta do is flash the stock recovery and you shouldn't lose your data
Click to expand...
Click to collapse
thanks mate yes I got my data back, but re-root it would mean loosing them so I'm running without the root now. good thing is Netflix, prime vedio, bank stuff are all working, bad thing is no titanium(
Matty1993 said:
You need to flash the correct bootloader version to your device IE check the binary number on the firmware file and compare to what is listed on download mode
File binarys have the letter U? example is
G930FXXU2ARA1 or G930FXXU3ARA1
Take note of the number
Now in download mode on the device
Find AP SWREV B: ? An example is
AP SWREV B:2 K:0 S:0
The 2 signifies it's a bit 2 bootloader so the firmware package needed for this device would be for example G930FXX"U2"ABCD
all you have to do is match them up,
AP SWREV B1 = U1 or S1
AP SWREV B2 = U2 or S2
AP SWREV B3 = U3 or S3
As for the flash error message " custom binary blocked by frp lock" means someone has tampered with the firmware, I'd assume you didnt get it from sammobile ? or it's not made for model number check the backing to your S7 model number is located at the bottom in small writing
Will be G930"F" for example also compare the letter to the binary file to make sure your flashing the correct model,
Also what version of odin3 are you using to flash as 6.0 to 7.0 binaries can be flashed with V3.12 as the binary files don't use .lz4 compression however 8.0 binaries do use .lz4 compression this is a new type of compression so requires Odin3 3.13.1 as this odin3 has the capabilities to read and flash the .lz4 binaries to the device
And I'm not sure if your aware but the factory binaries dont have OEM unlock in them to remove the FRP however there is a way that I know how to do it on this particular model but it will vary the B:? In download mode and to if a combination rom is available for your binary number COLOR="Silver"]
---------- Post added at 04:08 AM ---------- Previous post was at 03:57 AM ----------
[/COLOR]
All good mate , yeah once that OEM unlock is turned back off all security features are re activated that was your problem did you manage to fix it yet if not all you gotta do is flash the stock recovery and you shouldn't lose your data
Click to expand...
Click to collapse
thanks for answer, in odin mode it say rp swrev b3 k1 s2, where can i find the frmware with my binary number?
corvasce03 said:
thanks for answer, in odin mode it say rp swrev b3 k1 s2, where can i find the frmware with my binary number?
Click to expand...
Click to collapse
No worries so you have a bit 3 bootloader what does the model number say also in download mode ?
I'll provide you the link to the correct firmware to download that will be 100% official
matty1993 said:
no worries so you have a bit 3 bootloader what does the model number say also in download mode ?
I'll provide you the link to the correct firmware to download that will be 100% official
Click to expand...
Click to collapse
all it say
odin mode
download speed: Fast
product name: Sm-g930f
current binary: Samsung official
system status: Custom
frp lock: On
secure download: Enabled
warranty void: 1 (0x030c)
rp swrev: B3 k1 s2
corvasce03 said:
all it say
odin mode
download speed: Fast
product name: Sm-g930f
current binary: Samsung official
system status: Custom
frp lock: On
secure download: Enabled
warranty void: 1 (0x030c)
rp swrev: B3 k1 s2
Click to expand...
Click to collapse
Yep sweet also what region are you in also so I can make sure the firmwares modem is also region appropriate as they all run on different frequencies other than that that's all the info I need my friend product name is model number you have the same model as me I have G930F also give me two seconds and I'll get the link for you for the correct firmware, as for frp lock your very much quite lucky the warranty void is only "warranty void 1 (0×030c)
If it were : 1 (0×500b) youd be royally screwed for some reason combination roms will not boot on any Knox tripped S7 with : 1 (0×500b) but will boot on any Knox tripped device with : 1 (0×030c) I know this as I have a variety of S7 as I run a phone repair shop and have tested on tripped devices with Knox tripped as both
---------- Post added at 05:34 PM ---------- Previous post was at 05:27 PM ----------
corvasce03 said:
all it say
odin mode
download speed: Fast
product name: Sm-g930f
current binary: Samsung official
system status: Custom
frp lock: On
secure download: Enabled
warranty void: 1 (0x030c)
rp swrev: B3 k1 s2
Click to expand...
Click to collapse
Not sure what region you are but here the link to the S7 G930F pages just scroll down select your country and the select the first available firmware that appears with a U3 or S3 when you have selected your region,
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/
Matty1993 said:
Yep sweet also what region are you in also so I can make sure the firmwares modem is also region appropriate as they all run on different frequencies other than that that's all the info I need my friend product name is model number you have the same model as me I have G930F also give me two seconds and I'll get the link for you for the correct firmware, as for frp lock your very much quite lucky the warranty void is only "warranty void 1 (0×030c)
If it were : 1 (0×500b) youd be royally screwed for some reason combination roms will not boot on any Knox tripped S7 with : 1 (0×500b) but will boot on any Knox tripped device with : 1 (0×030c) I know this as I have a variety of S7 as I run a phone repair shop and have tested on tripped devices with Knox tripped as both
---------- Post added at 05:34 PM ---------- Previous post was at 05:27 PM ----------
Not sure what region you are but here the link to the S7 G930F pages just scroll down select your country and the select the first available firmware that appears with a U3 or S3 when you have selected your region,
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/
Click to expand...
Click to collapse
ok thanks i try to download it and update you if it go or not
corvasce03 said:
ok thanks i try to download it and update you if it go or not
Click to expand...
Click to collapse
Hey mate no it will 100% work just select your country all firmware from sammobile is guaranteed to be 100% official I use them myself, the only thing however is you need to make an account but the good news its 100% free to make an account but then there another little downfall download speeds are a little slow in free subscription but well worth the wait as I guarantee it will work
Matty1993 said:
Hey mate no it will 100% work just select your country all firmware from sammobile is guaranteed to be 100% official I use them myself, the only thing however is you need to make an account but the good news its 100% free to make an account but then there another little downfall download speeds are a little slow in free subscription but well worth the wait as I guarantee it will work
Click to expand...
Click to collapse
thanks!!!!! it workk it's beautiful!!! thanks thanks thanks!
OK someone please help. I'm having this same issue, except I got a galaxy s6, however when I boot into download mode and plug cable up it recognizes the driver as a modem or sometimes I get it to show up in ports but its named USB serial device, so I'm unable to flash anything through odin. I tried plugging my wife's galaxy s7 up to PC through download mode and her phone doesn't even show up as a USB diagnostic port....I'm seriously stumped on this and having a hell of a time trying to find any info on this My dumbass had stay awake checked at the time and when I went to turn it off I must have accidently unchecked the OEM unlock option resulting in.....a good headache lol....thanks for ur time guys.
corvasce03 said:
thanks!!!!! it workk it's beautiful!!! thanks thanks thanks!
Click to expand...
Click to collapse
No problem mate glad I could help
---------- Post added at 01:56 AM ---------- Previous post was at 01:49 AM ----------
jfoley420 said:
OK someone please help. I'm having this same issue, except I got a galaxy s6, however when I boot into download mode and plug cable up it recognizes the driver as a modem or sometimes I get it to show up in ports but its named USB serial device, so I'm unable to flash anything through odin. I tried plugging my wife's galaxy s7 up to PC through download mode and her phone doesn't even show up as a USB diagnostic port....I'm seriously stumped on this and having a hell of a time trying to find any info on this My dumbass had stay awake checked at the time and when I went to turn it off I must have accidently unchecked the OEM unlock option resulting in.....a good headache lol....thanks for ur time guys.
Click to expand...
Click to collapse
Hey mate i run a phone repair shop it's got nothing to do with the phones it's the computer or drivers
#1 What version of Odin are you using, you should be using the latest I use 3.13.1 as it supports new .lz4 compression for 8.0 oreo firmware,
#2 did you install the latest Samsung drivers.exe because if you didnt the information is not on your computer to read samsungs devices all the information to communicate to the device is stored in these drivers,
If you havent this is your problem, go to Google type in "latest Samsung USB driver.exe download" or check the forums here for it also, download it and simply open the exe and install the drivers,
Reboot and now try, if you still have the same issue what USB cord are you using, try an original Samsung USB cable or decent branded one,
If there error still persists what version of windows are you using,
Thanks

G930F locked on Combination firmware

Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
marcoar said:
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
Click to expand...
Click to collapse
Try to connect with smart switch.
On windows pc or laptop
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 11:21 PM ---------- Previous post was at 11:20 PM ----------
marcoar said:
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
Click to expand...
Click to collapse
It will flash stock firmware and solve all binary problem
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 11:22 PM ---------- Previous post was at 11:21 PM ----------
marcoar said:
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
Click to expand...
Click to collapse
Intall smart connect or smart switch in pc
Sent from my [device_name] using XDA-Developers Legacy app
marcoar said:
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
Click to expand...
Click to collapse
Flash latest stock firmware for your region and enable OEM unlock in developer settings to avoid FRP in future. Also try to remember your google account password :silly:
Solved. I flash the latest firmware with an old version of odin
frp lock
marcoar said:
Solved. I flash the latest firmware with an old version of odin
Click to expand...
Click to collapse
Hi ! Which version of odin did you use ? Marcoar
And which version of android do you have before the flash ?
kira31390 said:
Hi ! Which version of odin did you use ? Marcoar
And which version of android do you have before the flash ?
Click to expand...
Click to collapse
Odin 3.12.5
Firmware: fxxu2drb6
marcoar said:
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
Click to expand...
Click to collapse
Hi there
When you flashed the combination rom you described did it actually boot into the factory binary ?
Im just curious as i have the same combination rom though my firmware is G930FXXU2DRBE and when i flash the binary with odin it will turn on but wont boot past the samsung S7 screen rhough the blue light comes on and pulsates though this is all it does i was just wonderng if yours did the same.
Thanks
Matty1993 said:
Hi there
When you flashed the combination rom you described did it actually boot into the factory binary ?
Im just curious as i have the same combination rom though my firmware is G930FXXU2DRBE and when i flash the binary with odin it will turn on but wont boot past the samsung S7 screen rhough the blue light comes on and pulsates though this is all it does i was just wonderng if yours did the same.
Thanks
Click to expand...
Click to collapse
after the combination file flash, the phone normally starts with the combination firmware
marcoar said:
after the combination file flash, the phone normally starts with the combination firmware
Click to expand...
Click to collapse
Thanks so much for the reply i appreciate it i might try my combination file with the G930FXXU2DRB6 firmware you used as i need to test my hardware and fix imei but cant get the factory binary to boot on G930FXXU2DRBE firmware my thinking that it wouldnt boot was as its FA60 is android 6.0 MM where as my U2DRBE firmware is FA70 7.0 nougat is your device nougat or marshmallow ? Just trying to work out whats going wrong where for it to not boot on my device as ive lost my imei number flashing a custom rom and dont have access to my TWRP back up for another 3 weeks
Thanks
Hello. I have a similar problem. I have the latest firmware on it: G930FXXS2DRDI There are no ways to lift the Google lock. I have tried everything possible: Bluetooth does not work, Talkback, Realterm, etc. Please for help
My Android Version is: 7.0 (Nougat)
Frp g930fxxu2ara1
Hello my friend, i have this problem too. Have you a fix? this security patch for FRP is incredible....
You CAN bypass FRP on later Samsung models using Combination FW. I have succsesfully done this with S8+/G955F, it should work with any device that has compatible Stock/Combinaton FW.. Here are the steps. Download a compatible STOCK ROM, and some similar COMBINATION FW (by similar i mean both FW to be with the same binary and same android version, duh..) Here are some firmware download links, but you can use whatever you want, according to your device.. G930F STOCK ROM/G930F Combination FW
First, using Odin flash the COMBINATION FW to your phone. After flashing is complete and the phone reboots, allow a few minutes for the phone to boot. If it doesn't boot/gets stuck at bootlogo, reboot/boot to recovery and wipe data/cache, and reboot again. MOST IMPORTANT THING! After the phone boots, go to Settings, enable Developer Options if not enabled, enable USB Debugging, and turn the device OFF using Power button. After the device shuts down, enter Download mode, open Odin, place all 4 files in their respective fields (BL,AP,CP,CSC), and here is the SECOND MOST IMPORTANT THING! In the CSC field place the CSC file that starts with HOME/HOME_CSC (There will/should be 2 different CSC files in the FW archive, one starting with CSC, and the other with HOME_CSC). After flashing is complete, allow the phone to boot normally (don't do anything, don't enter recovery/wipe data). If you followed my instructions correctly, after the phone boots, you should be able to finish the initial setup/skip all steps, without requiring any account. Then go to Settings, enable Developer Options, turn OEM Unlock ON, and finally factory reset the device to complete the process and start fresh.
Don't forget to hit THANKS button if this method worked fo you!
ATRAC3, do you have the combination files and firmware for the SAMSUNG S7 SM-G930FD please and thank you for your wonderful tutorial here.
my odin(tried on v3.12.5/v3.12.7/v3.13.1 ) keep failing while flashing HOME_CSC but will success with CSC, and still required to login google account, what is the issue here ? (are we supposed to insert the pit file by ATRAC3 ? )
flashing at the lastest FW G930FXXS2DRCE
phone version:SM-G930F
ATRAC3 said:
You CAN bypass FRP on later Samsung models using Combination FW. I have succsesfully done this with S8+/G955F, it should work with any device that has compatible Stock/Combinaton FW.. Here are the steps. Download a compatible STOCK ROM, and some similar COMBINATION FW (by similar i mean both FW to be with the same binary and same android version, duh..) Here are some firmware download links, but you can use whatever you want, according to your device.. G930F STOCK ROM/G930F Combination FW
First, using Odin flash the COMBINATION FW to your phone. After flashing is complete and the phone reboots, allow a few minutes for the phone to boot. If it doesn't boot/gets stuck at bootlogo, reboot/boot to recovery and wipe data/cache, and reboot again. MOST IMPORTANT THING! After the phone boots, go to Settings, enable Developer Options if not enabled, enable USB Debugging, and turn the device OFF using Power button. After the device shuts down, enter Download mode, open Odin, place all 4 files in their respective fields (BL,AP,CP,CSC), and here is the SECOND MOST IMPORTANT THING! In the CSC field place the CSC file that starts with HOME/HOME_CSC (There will/should be 2 different CSC files in the FW archive, one starting with CSC, and the other with HOME_CSC). After flashing is complete, allow the phone to boot normally (don't do anything, don't enter recovery/wipe data). If you followed my instructions correctly, after the phone boots, you should be able to finish the initial setup/skip all steps, without requiring any account. Then go to Settings, enable Developer Options, turn OEM Unlock ON, and finally factory reset the device to complete the process and start fresh.
Don't forget to hit THANKS button if this method worked fo you!
Click to expand...
Click to collapse
Hi mate ive used the G930FXXU2DRBE XSA Firmware and also G930FXXU2DRB6 firmware with the G930FXXU2ARA2 combination rom however it will not boot past the samsung logo the nad passes and is provisioned in top left corner and when plugged into the computer comes online with ADB bypass flasher but it just sits there even if i do a cache wipe and factory reset it comes up with a tango console error or something like that when reset then reboots back to samsung logo and when re installing firmware HOME-CSC will fail every time the only thing ive been able to put it down to is that (1) the firmware is FA_70 which is nougat OS and the combination rom is FA_60 MM or (2) my knox warranty bit is tripped and will not allow a samsung factory binary to be run on it, may i ask what would be the difference with the firmware you have listed to the firmware im already using with the combination rom ? Need to sort my imei number out with the factory nad asap dont have access to my TWRP backup for another week and a half, if it helps my device is not FRP locked and is oem unlocked.
Thanks
Matthew
P.S to all those whom have a bit 2 bootloader on S7 all the loopholes have been patched the only way is to use the combination files ive been through absolutely everything and tried everything this new bootloader update is impenetrable i can google unlock samsung S8 and S9 no dramas and with S9 the OEM lock option dissapears for a week if tampered with but still 15 minutes and its done this **** but got me goin loco holmes !!!!! Maybe they figured this out also as there is only bit 1 bootloaders for both the S8 and the S9 however with S8 i found a stock firmware that allows another way to unlock the device without the need to flash any combination rom.
So in short no hope now to unbrick our Samsung S7 SM-G930F/FD or what.....?
LEVY P said:
So in short no hope now to unbrick our Samsung S7 SM-G930F/FD or what.....?
Click to expand...
Click to collapse
If it gets stuck on the console error and wont reboot to download mode then hold the power button volume down button and power button for 40 seconds and it will re boot to download mode for stock firmware re installation in short basically no theres way to remove the FRP unless you can get the combination rom to boot which from what ive seen some will boot the binary but then it also depends if HOME_CSC will flash to keep usb debugging enabled to use adb bypass program im now using the new G930FXXU2ERE2 8.0 OREO so I've given up on the binary 2 nougat FRP unlocking for now might be best to wait a while for someone to receive a factory binary on the nougat or oreo when sent off and returned so it can be dumped and built into a flashable rom until then not much can be done and i may have to wait another week and a half for my EFS backup :'(
We will be waiting from u for the new combination file when out bro, our hope are hinged on u!
No one is coming up with any method about the bootloader binary 2 for the Samsung S7 G930FD...?
Sent from my SM-G930F using Xposed Modules
FRP can be done so easy from any GSM tool by combination, anyone need it it will be my pleasure to help

Problem with TWRP Recovery v3.1.1 on my Samsung SM-j701M

Hello there
I bought a Samsung J7 Neo (SM -J701M) on another country than mine (Im from Argentina, device bought on Paraguay). Anyway, I started to look another way to get some space on the internal storage and I remember that android had an option to expand it, using a SD Card. Unfortunately, i realize this option is not allowed on samsungs device, but it works (i read it, because can't do it) if you get root user.
So I looked how to do it and i found a group of files
ODIN v3.12
Magisk v.14.5
twrp v.3.1.1 -j7 neo
Im not sure if I downloaded the right files, but im start the process anyway.
I followed point by point
First I installed TWRP Recovery v3.1.1 (which is supposed to be correct to my model) and then already on twrp rom I installed magisk 14.5 from sd card and did wipe data.
Turned on the phone and I restored all apps from a google backups, and I realized I cant find app "Magisk" on the device, so I decided to reboot the phone and it starts to do a bootloop with this error "kernel rev. check fail, device:2 binary:1"
At this point, I failed every attempt to fix this error
I tried installing the last official firmware that i found (and Im not sure if its the correct one)
J701MUBU3ARC2_J701MUWT3ARC1_UFN
And I got this error
"SW REV. CHECK Fail (BOOTLOADER) Device :5 Binary 3:
I searched on google this kind of error, and I found that I have to downgrade the bootloader. And this is why im here beacause I dont know how to do this, and if its works, i don´t know how to continue the process to root and expand my internal storage. So I really appreciate if someone one could help me with this. I can learn fast and I love to do this things by myself.
Thanks for your time!
Fernando
If you have to downgrade the boot loader, it means the firmware you are flashing is older than the one on your fon.
Go to www.updato.com and look for the he latest J701M firmware.
You can sort the list by date and by region.
And the site is download manager friendly ?
Good luck!
Sent from my SM-J700F using Tapatalk
Thanks for your answer! One more question about the region. Should I download firmware from the country that I bought the phone or firmware from the country that I am?
Look for your country specific firmware first.
Otherwise Samsung usually has regional software - i.e for several countries in a region e.g. Argentina, Paraguay.
Sent from my SM-J700F using Tapatalk
MikeEinziger said:
Hello there
I bought a Samsung J7 Neo (SM -J701M) on another country than mine (Im from Argentina, device bought on Paraguay). Anyway, I started to look another way to get some space on the internal storage and I remember that android had an option to expand it, using a SD Card. Unfortunately, i realize this option is not allowed on samsungs device, but it works (i read it, because can't do it) if you get root user.
So I looked how to do it and i found a group of files
ODIN v3.12
Magisk v.14.5
twrp v.3.1.1 -j7 neo
Im not sure if I downloaded the right files, but im start the process anyway.
I followed point by point
First I installed TWRP Recovery v3.1.1 (which is supposed to be correct to my model) and then already on twrp rom I installed magisk 14.5 from sd card and did wipe data.
Turned on the phone and I restored all apps from a google backups, and I realized I cant find app "Magisk" on the device, so I decided to reboot the phone and it starts to do a bootloop with this error "kernel rev. check fail, device:2 binary:1"
At this point, I failed every attempt to fix this error
I tried installing the last official firmware that i found (and Im not sure if its the correct one)
J701MUBU3ARC2_J701MUWT3ARC1_UFN
And I got this error
"SW REV. CHECK Fail (BOOTLOADER) Device :5 Binary 3:
I searched on google this kind of error, and I found that I have to downgrade the bootloader. And this is why im here beacause I dont know how to do this, and if its works, i don´t know how to continue the process to root and expand my internal storage. So I really appreciate if someone one could help me with this. I can learn fast and I love to do this things by myself.
Thanks for your time!
Fernando
Click to expand...
Click to collapse
@MikeEinziger
Hi There,
Did you have any luck with your Phone? I have the same exact model but I have Android Version 8.1.0, Samsung Experience version 9.5; Android security patch level -Feb 1, 2019; Baseband version: J701MUBS6BSB3 and like you, I love doing things myself, and I can't seem to abide a smartphone that's not rooted.
I'm not exactly a newbie, I've been assisting devs with testing and such on AT&T SGS3 for quite some time. But I can't seem to find a stable method for rooting for this phone, no one seems to be doing any development on it.
I would love to hear your story thus far.
im needing help myself, i have the SM-J701M (J7 NEO), with android pie 9 official, but the binary is 7 (because Argentina Geniuses of course) and of all the things i tried nothing works, and the only thing they did was brick the phone, so i flash and stock firmnware to be usable again
Ezeka93 said:
im needing help myself, i have the SM-J701M (J7 NEO), with android pie 9 official, but the binary is 7 (because Argentina Geniuses of course) and of all the things i tried nothing works, and the only thing they did was brick the phone, so i flash and stock firmnware to be usable again
Click to expand...
Click to collapse
What have you done? I saw your messages on TG but everyone ignores usually, I had another problem and footbed the solution myself as I got ignored for days.
So, what have you done? Maybe we can figure it out a way to root it, but to avoid telling you things that you may have already done it is better if you let us know your already followed steps.
Jemec26 said:
What have you done? I saw your messages on TG but everyone ignores usually, I had another problem and footbed the solution myself as I got ignored for days.
So, what have you done? Maybe we can figure it out a way to root it, but to avoid telling you things that you may have already done it is better if you let us know your already followed steps.
Click to expand...
Click to collapse
i tried flashing TWRP like a guide said (Latest version) but then got stuck with a boot loop in the Samsung Galaxy Logo, then when i enter to flash the latest global firmware it didn't work because it was binary 6, so i searched for the version in Argentina that has binary 7, after that i didn't try anything else in fears of getting fully bricked, i was thinking of the magisk canary way of rooting (patching the AP) but i don't know what happen if it fails the flash
Hi, i have the same device, SM-J701M, but when i try to flash the stock, it says that the device binary is 9 and the rom is 8, but i cant find the binary 9 rom in any place, only 8. I have the trwp installed, so I was thinking if I format all data (system and files) and try to flash again, it will work ?
Also im from Brazil (SM-J701MT), and the device was buyed in Paraguay (SM-J701M) too. Should i install the SM-J701MT ROM right ?
Some success.
iKmaster01 said:
Hi, i have the same device, SM-J701M, but when i try to flash the stock, it says that the device binary is 9 and the rom is 8, but i cant find the binary 9 rom in any place, only 8. I have the trwp installed, so I was thinking if I format all data (system and files) and try to flash again, it will work ?
Also I'm from Brazil (SM-J701MT), and the device was buyed in Paraguay (SM-J701M) too. Should i install the SM-J701MT ROM right ?
Click to expand...
Click to collapse
Ok, guys, I've had a bit of progress with my device Samsung Galaxy J 7 Neo (SM-J701M- Android version 8.01)
On this phone, the option to unlock the bootloader was missing in Dev Opt and I knew that in order to achieve anything I was going to have to unlock the bootloader.
I searched and found that, via adb/fastboot (Google's Platform Tools) rebooting the phone to the bootloader you could enter the code: 'fastboot oem unlock' or 'fastboot flashing unlock' and voila! everything would be fixed...But...my device wasn't even being recognized by "fastboot" ! adb yes but no fastboot! Always the message: "Waiting on any device". Trying to find and install the drivers to do this was next to impossible.
It actually caused me soft brick my device. However, it was a blessing in disguise; I knew what had to be done, I was going to have to reinstall the firmware via Odin. I searched the site (Sammobile - you'll have to create an account.) and found the Oreo and the Pie Firmware, I downloaded both but played it safe and restored my device with the Oreo first.
And lo and behold the option to unlock bootloader was there! No hesitation, clicked that sucker fast!!
Now, I'm running PIE (No one has done a Custom ROM for this baby just yet) and with the unofficial TWRP in the first link below, it's a bit buggy but until they make an official one for us ... I guess we'll have to wait.
Oh! And don't forget to make a backup with Smart Switch!
And pay attention to the advice here:
Code:
1. Extract the firmware file you just downloaded. You should get 5 files:
AP (System &Recovery)
BL (Bootloader)
CP (Modem / Radio)
CSC_*** (Country / Region / Operator)
HOME_CSC_*** (Country / Region / Operator)
2. Add each file to its respective field in Odin v3.14.4. Use CSC_*** if you want to do a clean flash or HOME_CSC_*** if you want to keep your apps and data.
3. Reboot your phone in Download / Odin mode (make sure your device is off) with the following button combo: POWER + VOLUME DOWN + BIXBY
Other options in case first option did not work or isn't possible.
Option 2 VOLUME DOWN + VOLUME UP then USB cable
Option 3 POWER + VOLUME DOWN + VOLUME UP
Option 4 POWER + VOLUME DOWN + HOME BUTTON
Option 5 (Note9) USB cable + VOLUME DOWN + BIXBY
Option 6 (Note10) POWER + VOLUME UP
4. Once in download mode, connect your phone to the PC, preferably using the original USB cable you got with your phone. Odin should detect your device and a BLUE box will show up with the COM port number. (Be sure, the SAMSUNG-drivers are installed on your PC!)
Do NOT tick any extra boxes. The only options to be ticked are F.Reset Time and Auto-Reboot.
5. Click the start button, wait for Odin to say 'PASS' in a GREEN box. Once the flash is complete, your phone will reboot, and you can disconnect your phone from the PC
These are some of the links I found helpful:
https://unofficialtwrp.com/root-twrp-galaxy-j7-neo-sm-j701m/
https://www.androidexplained.com/galaxy-note-9-restore-firmware/
https://forum.xda-developers.com/galaxy-j7/samsung-galaxy-j7-prime--j7-on-nxt-exynos7870/recovery-twrp-3-2-0-galaxy-j7-prime-t3716355
---------- Post added at 01:39 PM ---------- Previous post was at 01:30 PM ----------
iKmaster01 said:
Hi, i have the same device, SM-J701M, but when i try to flash the stock, it says that the device binary is 9 and the rom is 8, but i cant find the binary 9 rom in any place, only 8. I have the trwp installed, so I was thinking if I format all data (system and files) and try to flash again, it will work ?
Also im from Brazil (SM-J701MT), and the device was buyed in Paraguay (SM-J701M) too. Should i install the SM-J701MT ROM right ?
Click to expand...
Click to collapse
I think that's because you have to be specific with the carrier; Orange; Nextel; Movistar...that makes a lot of difference in with the firmware. If you can, check to see what you had before and try that first.
CoperaN said:
Ok, guys, I've had a bit of progress with my device Samsung Galaxy J 7 Neo (SM-J701M- Android version 8.01)
On this phone, the option to unlock the bootloader was missing in Dev Opt and I knew that in order to achieve anything I was going to have to unlock the bootloader.
I searched and found that, via adb/fastboot (Google's Platform Tools) rebooting the phone to the bootloader you could enter the code: 'fastboot oem unlock' or 'fastboot flashing unlock' and voila! everything would be fixed...But...my device wasn't even being recognized by "fastboot" ! adb yes but no fastboot! Always the message: "Waiting on any device". Trying to find and install the drivers to do this was next to impossible.
It actually caused me soft brick my device. However, it was a blessing in disguise; I knew what had to be done, I was going to have to reinstall the firmware via Odin. I searched the site (Sammobile - you'll have to create an account.) and found the Oreo and the Pie Firmware, I downloaded both but played it safe and restored my device with the Oreo first.
And lo and behold the option to unlock bootloader was there! No hesitation, clicked that sucker fast!!
Now, I'm running PIE (No one has done a Custom ROM for this baby just yet) and with the unofficial TWRP in the first link below, it's a bit buggy but until they make an official one for us ... I guess we'll have to wait.
Oh! And don't forget to make a backup with Smart Switch!
And pay attention to the advice here:
Code:
1. Extract the firmware file you just downloaded. You should get 5 files:
AP (System &Recovery)
BL (Bootloader)
CP (Modem / Radio)
CSC_*** (Country / Region / Operator)
HOME_CSC_*** (Country / Region / Operator)
2. Add each file to its respective field in Odin v3.14.4. Use CSC_*** if you want to do a clean flash or HOME_CSC_*** if you want to keep your apps and data.
3. Reboot your phone in Download / Odin mode (make sure your device is off) with the following button combo: POWER + VOLUME DOWN + BIXBY
Other options in case first option did not work or isn't possible.
Option 2 VOLUME DOWN + VOLUME UP then USB cable
Option 3 POWER + VOLUME DOWN + VOLUME UP
Option 4 POWER + VOLUME DOWN + HOME BUTTON
Option 5 (Note9) USB cable + VOLUME DOWN + BIXBY
Option 6 (Note10) POWER + VOLUME UP
4. Once in download mode, connect your phone to the PC, preferably using the original USB cable you got with your phone. Odin should detect your device and a BLUE box will show up with the COM port number. (Be sure, the SAMSUNG-drivers are installed on your PC!)
Do NOT tick any extra boxes. The only options to be ticked are F.Reset Time and Auto-Reboot.
5. Click the start button, wait for Odin to say 'PASS' in a GREEN box. Once the flash is complete, your phone will reboot, and you can disconnect your phone from the PC
These are some of the links I found helpful:
https://unofficialtwrp.com/root-twrp-galaxy-j7-neo-sm-j701m/
https://www.androidexplained.com/galaxy-note-9-restore-firmware/
https://forum.xda-developers.com/galaxy-j7/samsung-galaxy-j7-prime--j7-on-nxt-exynos7870/recovery-twrp-3-2-0-galaxy-j7-prime-t3716355
---------- Post added at 01:39 PM ---------- Previous post was at 01:30 PM ----------
I think that's because you have to be specific with the carrier; Orange; Nextel; Movistar...that makes a lot of difference in with the firmware. If you can, check to see what you had before and try that first.
Click to expand...
Click to collapse
Hey, I noticed we have the same android version and and phone model, I wanted to know which version of Twrp you used . I am guessing version 3.1.1?
It's an Un-official version of TWRP, so the version #( 3.2.1-0) may not count, you can check the links out to get more information.
hola tengo un problema, tengo un sm-j701m binario 11 android 9 y quiero intalarle un twrp pero no se cual descargar y que funcione
Don't know if anyone's still following this thread or even still has this phone but there's been quite some progress with this device. (i.e: SM-J701M) The posts below will certainly help to bring your device up to date re: rooting; flashing etc.
https://forum.xda-developers.com/t/...or-galaxy-j7-nxt-neo-core-10-08-2021.4222703/
https://forum.xda-developers.com/t/...laxy-j7-nxt-neo-core-j701-02-02-2021.4227921/
These posts contain links to ROMS and recoveries which have been sucessful, I can personally attest to this, my device was rooted and a custom ROM installed. I hope you will find them helpful.
Good Luck

Wrong sboot.bin on Samsung Xcover 3 - Hardbricked?

Greetings, everyone! Usually I have good knowledge regarding rooting, custom recovery and flashing a new system. But this time I tried to downgrade the Samsung Xcover 3 of my friend and flashed the Android 4.4.4 sboot.bin with Heimdall - unfortunately I forgot to tick the "no reboot" option. The moment it rebootet, I know do not have any access to the phone anymore.
When trying to bring it into download mode, it vibrates, but nothing else. Neither Linux nor Windows recognizes the phone. Is it dead? How to gain access so that I can flash the correct sboot.bin? Any tricks you recommend?
back2nature said:
Greetings, everyone! Usually I have good knowledge regarding rooting, custom recovery and flashing a new system. But this time I tried to downgrade the Samsung Xcover 3 of my friend and flashed the Android 4.4.4 sboot.bin with Heimdall - unfortunately I forgot to tick the "no reboot" option. The moment it rebootet, I know do not have any access to the phone anymore.
When trying to bring it into download mode, it vibrates, but nothing else. Neither Linux nor Windows recognizes the phone. Is it dead? How to gain access so that I can flash the correct sboot.bin? Any tricks you recommend?
Click to expand...
Click to collapse
If you can find a "debrick.img" or "debrick.bin" for your specific model number, there is a method that uses your external sdcard to boot the phone then repair it while it is booted.
But, first, you need to find a debrick.img or debrick.bin for your specific model number. If you can't find a copy for your model number, you can try finding another member here that has a rooted Xcover 3 with the exact same firmware as your device had and have them pull a copy of debrick.img or debrick.bin from their device then upload it for you to download.
If you can't find that, the only other options are to send the device to a repair shop for JTAG service or replace the motherboard.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
If you can find a "debrick.img" or "debrick.bin" for your specific model number, there is a method that uses your external sdcard to boot the phone then repair it while it is booted.
But, first, you need to find a debrick.img or debrick.bin for your specific model number. If you can't find a copy for your model number, you can try finding another member here that has a rooted Xcover 3 with the exact same firmware as your device had and have them pull a copy of debrick.img or debrick.bin from their device then upload it for you to download.
If you can't find that, the only other options are to send the device to a repair shop for JTAG service or replace the motherboard.
Click to expand...
Click to collapse
I did not even expect that someone would answer here. THANK YOU SO MUCH, @Droidriven! That gives me hope to rescue the phone instead of having o buy a new one for my friend. Here is what I actually did wrong: In my attempt to "downgrade" from 5.1.1 Lollipop to Android 4.4.4 Kitkat (downgrade needed to be able to root the phone) I flashed the sboot.bin of Android 4.4.4 Kitkat with Heimdall and forgot to tick the NO REBOOT option.
That being said, the phone now only vibrates when using my JTAG (yes, I actually have one and the phone vibrates, but does not boot into download mode and is not recognized by neither Windows nor Linux). So, how to build this unbrick image? Could you help me with that? Both firmwares are to be found here:
Code:
https://samsungfirmware.net/samsung-galaxy-xcover-3-sm-g388f-stock-firmware
Another thread with sadly no file uploaded was to be found here:
Code:
https://forum.xda-developers.com/general/help/search-g388f-xcover3-debrick-img-sdc-t3399231
As for the creation of the unbrick image, do you recommend this tool? I currently have no Windows at hand but can provide you with the original PIT file if you can run this tool to create it:
Code:
http://forum.gsmhosting.com/vbb/f609/atf-v12-70-update-31-mar-2017-a-937102/index5.html#post10127092
DOWNLOAD LINK ATF_v12.70_Full_Installer:
Code:
http://www.mediafire.com/file/l1c9o7ibv2jypfv/ATF_v12.70_Full_Installer_%2528xdarom.com%2529.rar/file
Furthermore, I actually wanted to install LineageOS on that phone. Not sure if you have a Google-foo so strong that you are able to find a working one for me?
Thanks a lot for your help. May god return your efforts in helping me!
back2nature said:
I did not even expect that someone would answer here. THANK YOU SO MUCH, @Droidriven! That gives me hope to rescue the phone instead of having o buy a new one for my friend. Here is what I actually did wrong: In my attempt to "downgrade" from 5.1.1 Lollipop to Android 4.4.4 Kitkat (downgrade needed to be able to root the phone) I flashed the sboot.bin of Android 4.4.4 Kitkat with Heimdall and forgot to tick the NO REBOOT option.
That being said, the phone now only vibrates when using my JTAG (yes, I actually have one and the phone vibrates, but does not boot into download mode and is not recognized by neither Windows nor Linux). So, how to build this unbrick image? Could you help me with that? Both firmwares are to be found here:
Code:
https://samsungfirmware.net/samsung-galaxy-xcover-3-sm-g388f-stock-firmware
Another thread with sadly no file uploaded was to be found here:
Code:
https://forum.xda-developers.com/general/help/search-g388f-xcover3-debrick-img-sdc-t3399231
As for the creation of the unbrick image, do you recommend this tool? I currently have no Windows at hand but can provide you with the original PIT file if you can run this tool to create it:
Code:
http://forum.gsmhosting.com/vbb/f609/atf-v12-70-update-31-mar-2017-a-937102/index5.html#post10127092
DOWNLOAD LINK ATF_v12.70_Full_Installer:
Code:
http://www.mediafire.com/file/l1c9o7ibv2jypfv/ATF_v12.70_Full_Installer_%2528xdarom.com%2529.rar/file
Furthermore, I actually wanted to install LineageOS on that phone. Not sure if you have a Google-foo so strong that you are able to find a working one for me?
Thanks a lot for your help. May god return your efforts in helping me!
Click to expand...
Click to collapse
Sorry, I'm just now seeing this. Did you ever make any progress? Yes, I think there are some reliable methods to create debrick.img/debrick.bin files, there is one such method posted here at XDA in a random post in a thread here but I can't remember exactly what thread it is.

Categories

Resources