Hi guys, i mess around with my phone now i cannot put it back to stock. I bought my phone in mauritius ( MUR )
At first i wanted to root the device , but my phone was 6.0.1 with dec-1-2016 security patch, so i watch some video on how to remove the FRP Lock , i was finaly able to with this file :
COMBINATION_OXY_FA51_J700HXXU2APC1_OXY2APC1_CL902935_QB8806508_REV00_user_mid_noship.tar.md5
But this is where my nightmare starts. After that i tried to flash my phone again with several ROM that i have downloaded from Sammobiles , but none was successful :
-J700HXXU1APA3_J700HOJV1AOK6_J700HXXU1APA2
-J700HXXU1AOK5_J700HOJV1AOK6_J700HXXU1AOK8
-J700HXXU2BPL1_J700HOJV2BPL1_J700HXXU2BPL1 ( this one i was able to , but my phone was very laggy )
-J700H_DS_XXU1AOGA_OXY1AOGA_v5.1.1_Repair_Firmware ( 4 files )
-SM-J700H_20151119_J700HXXU1AOK5_J700HOLB1AOK1_5.1.1
From all of the above i got this error code on ODIN 3.10.6 : SW REV. CHECK FAIL. DEVICE:2 BINARY: 1
only this onw i was able to flash , but its origin is philippine and i cannot upgrade my firmware to 6.0.1 again with this ROM .
Please can someone help me out , put back things as they should be. I was able to install TWRP 2.8.7.0 , but i didnt try again .
Regards
@Omegasenpai
Hi, you probably tried to downgrade to an older bootloader, and that's what caused the trouble, try to flash the latest stock rom that has android 6.0.1
i flash it with this : J700HXXU2BPG4_J700HOJV2BPG1_J700HXXU2BPG1 , seems to be working without lag, will test it for a few days and see.
As stated on the title I tried to do SamFAIL on my N950, it was on latest Oreo and I didn't know it would not work (my mistake)
I did the system flash with the .pit file on comsy odin successfully (it finished with fail as expected) but after that I cant flash anything.
I downloaded many official FW packages, Nougat and Oreo everything fails on official Odin, gives model mismatch error on comsy odin.
The only file I can flash is this : HOME_CSC_OYN_N950UOYN4CRD7_CL13303302_QB17839096_REV00
Its from the Oreo official package. If I try the regular CSC it fails as everything else. HOME CSC from nougat versions fail as well.
What I have tried so far:
Other Computer, Windows 7/10, other cable, all versions of odin (only 3.12.3 flashes home csc successfully), Smart Switch says unsupported device, no recovery mode stuck on Emergency Mode, sometimes it boots to normal download Mode
Is there a trick to force the flash? Did I break my device by doing the .pit flash? I thought that official FW would always flash no matter what... Hope someone has some ideas. Thanks in advance!
Hi Guys,
samsung/gts311texx/gts3llte
8.0.0/R16NW/T825XXU2BRL2
really struggling with my TabS3 which is about 1.5years old. Had sent it to Samsung for repair but they sent it back without repairing the problem.
was fine until a few weeks ago the battery had died within a few hours of charging. I charged again and noticed it was just bootlooping but was occasionally giving a blue screen error saying no command then in recovery was showing failed to verify diverity hash tree
It hasnt been possible to get into android to enable OEM unlock due to bootlooping issues
was running stock firmware and not rooted
I tried to reinstall stock firmware from samfirmware via Odin but was just giving an error when flashing AP
now when booting its giving " an error has ocurred while updating the device software. use the emergency recovery function in the smart switch pc software"
in recovery giving error dm-verity verification failed... E:failed to mount system (invalid argument)
any ideas? £20 reward if helps get it sorted!
NI3K said:
Hi Guys,
samsung/gts311texx/gts3llte
8.0.0/R16NW/T825XXU2BRL2
really struggling with my TabS3 which is about 1.5years old. Had sent it to Samsung for repair but they sent it back without repairing the problem.
was fine until a few weeks ago the battery had died within a few hours of charging. I charged again and noticed it was just bootlooping but was occasionally giving a blue screen error saying no command then in recovery was showing failed to verify diverity hash tree
It hasnt been possible to get into android to enable OEM unlock due to bootlooping issues
was running stock firmware and not rooted
I tried to reinstall stock firmware from samfirmware via Odin but was just giving an error when flashing AP
now when booting its giving " an error has ocurred while updating the device software. use the emergency recovery function in the smart switch pc software"
in recovery giving error dm-verity verification failed... E:failed to mount system (invalid argument)
any ideas? £20 reward if helps get it sorted!
Click to expand...
Click to collapse
Just a couple of thoughts. Do you know what error you were getting in Odin? Are you using the latest version of odin, 3.13, and try downloading the stock firmware from updato.
Sent from my [device_name] using XDA-Developers Legacy app
using odin 3.13, when trying to flash its showing no errors in odin just FAIL! (Auth) and tablet screen showing secure check fail: aboot [1]eMMC write fail: aboot
Internal memory issue maybe? tried a version from updato, similar story
NI3K said:
using odin 3.13, when trying to flash its showing no errors in odin just FAIL! (Auth) and tablet screen showing secure check fail: aboot [1]eMMC write fail: aboot
Internal memory issue maybe? tried a version from updato, similar story
Click to expand...
Click to collapse
Are you flahing the same firmware version that's on your device, BLR2? aboot is the bootloader and it looks like it's failing trying to write that. If your flashing an earlier version of firmware you'll get that error. But it could also be caused if eMMC is bad. When you sent it to Samsung did they do anything to it, or tell you anything that might be wrong? When you boot into the bootloader what does it say about FRP lock?
Edit, also, if you're not, run Odin as administrator.
Sent from my [device_name] using XDA-Developers Legacy app
FRP lock: On
I'm not completely sure which firmware was on the device, was assuming BLR2. Done a successful flash in Odin (using BLR2) but still only boots to recovery giving error -
#fail to open recovery_cause (no such file or directory)#
No support SINGLE-SKU
File-Based OTA
Supported API: 3
dm-verity verification failed
Samsung only told me its a non EU device but couldnt tell where it originated from and that they can't help as components are different from EU devices
any ideas?
NI3K said:
FRP lock: On
I'm not completely sure which firmware was on the device, was assuming BLR2. Done a successful flash in Odin (using BLR2) but still only boots to recovery giving error -
#fail to open recovery_cause (no such file or directory)#
No support SINGLE-SKU
File-Based OTA
Supported API: 3
dm-verity verification failed
Samsung only told me its a non EU device but couldnt tell where it originated from and that they can't help as components are different from EU devices
any ideas?
Click to expand...
Click to collapse
Ok, so you don't know what country the device came from? And I assume you're in the EU? There's a few things to try. Have you tried Samsung's smart switch program, Google it. I haven't had luck with their software but maybe it'll work. And might identify your device.
Also, try flashing just the bootloader with Odin. I assume you're trying to flash just the AP binary. Try flashing just the bootloader. Choose BL in Odin and the BL file from the stock firmware. Don't flash anything else. See if that will flash and then boot.
I believe the device was from China but seems to have been running UK software as thats the only firmware that will load without a dev_error
Smart switch didnt identify it as a device which could be repaired
tried flashing bootloader only, same issue of bootlooping or automatically booting to recovery.
I have flashed to older android version T825XXU2BRJ1 but exactly the same issue of bootlooping/recovery
Even im facing same problem without any solution.
I'm so sorry that this happened. I would've tried to help you IF ONLY MY TAB WASN'T HARD BRICKED
Hi, I have a s6 edge on which I had a lineage os rom (android 9) but I wish to get back to stock rom (7) but when flashing via odin I get a failure after cm.bin and an error message on phone something like "invalid SW rev". I have read on other forums and is it possible that it has something to do with bootloader and I am no longer able to downgrade from android 9? Hoping to get some help here. Thanks
EDIT: Please close or delete the thread. I was using the wrong bootloader version.
Before error , installed firmware was unofficial stock firmware (rooted but removed it)
tried install stock firmware ( https://www.sammobile.com/samsung/galaxy-m11/firmware/SM-M115F/INS/download/M115FXXU2AUA3/1537817/ ) but odin failed
locked boot-loader (was unlocked earlier) as thinking it might help
now i am stuck in download mode.
HELP ME
HOPING FOR REPLY
MESSingUPthenLEARNing said:
Before error , installed firmware was unofficial stock firmware (rooted but removed it)
tried install stock firmware ( https://www.sammobile.com/samsung/galaxy-m11/firmware/SM-M115F/INS/download/M115FXXU2AUA3/1537817/ ) but odin failed
locked boot-loader (was unlocked earlier) as thinking it might help
now i am stuck in download mode.
HELP ME
HOPING FOR REPLY
Click to expand...
Click to collapse
Test this Odin
Patched Odin 3.13.1
For those looking for a modified, modded, or patched odin that is a newer build than all the fake and renamed prince comsy 3.12.3 versions floating around. I patch recent Odin versions to offer similar functionality to the princecomsy; in that...
forum.xda-developers.com