SORRY ABOUT MY BAD ENGLISH
I am writing this tread because i recently unlocked the frp lock on my bricked ROOTED samsung galaxy note 5 (SM-N920C). I faced problem in flashing stock firmware as my phone lost drk. And hence i do research and it took about a month to find a solution. I am sharing it here.
Tools i used.
1. Samsung tool pro( cracked version)
2. SM-N920C Combination file:
http://shell.boxwares.com/default.aspx?DeviceModel=SM-N920C&Type=All#fh5co-table
Because i am on nougat firmware the Samsung tool pro doesn't work and at the same time i am not able to down grade the firmware due to frp lock.
3. TWRP RECOVERY
https://twrp.me/samsung/samsunggalaxynote5.html
PROCEDURE:
1. Flash the combination file in download mode. And wait for the phone to boot. In my case the phone doesn't boot.
Then go to download mode agian and remove frp lock with samsung tool.
2. Flash TWRP.
3. Flash any custome rom from TWRP. :good:
simply go to download mode and flash official firmware
after phone starts go to settings>>developer mode>>enable oem unlock toggle
that's all no frp lock anymore. i wonder why it took you 1 month to figure this out.
tucking fypo said:
simply go to download mode and flash official firmware
after phone starts go to settings>>developer mode>>enable oem unlock toggle
that's all no frp lock anymore. i wonder why it took you 1 month to figure this out.
Click to expand...
Click to collapse
Actually, when the phone is under the frp lock. Flashing stock firmware under odin will not work. At least it happened to my n920g. I used the emergency restore through the samsung smart switch app.
Sent from my SM-N920G using XDA-Developers Legacy app
loppv said:
Actually, when the phone is under the frp lock. Flashing stock firmware under odin will not work. At least it happened to my n920g. I used the emergency restore through the samsung smart switch app.
Sent from my SM-N920G using XDA-Developers Legacy app
Click to expand...
Click to collapse
but i could easily go to download mode even with frp lock on. only i could not restart my phone and not enter twrp. but download mode worked fine forme
Since i lost Drk i can't able to boot after repair with smart switch. And thats why i tried this method.
rahulkr0507 said:
Since i lost Drk i can't able to boot after repair with smart switch. And thats why i tried this method.
Click to expand...
Click to collapse
It's simple flash twrp with odin and flash magisk or supersu with twrp and voila...the phone is booted with stock rooted kernel
ebusuhejbi said:
It's simple flash twrp with odin and flash magisk or supersu with twrp and voila...the phone is booted with stock rooted kernel
Click to expand...
Click to collapse
We can't able to flash custom recovery in this case. The phone will not allow it.
ebusuhejbi said:
It's simple flash twrp with odin and flash magisk or supersu with twrp and voila...the phone is booted with stock rooted kernel
Click to expand...
Click to collapse
flashing any custom recovery wont work on frp locked. it will fail in odin.
If flash stock boot the phone and check oem unlock
Drk matters
ebusuhejbi said:
If flash stock boot the phone and check oem unlock
Click to expand...
Click to collapse
If there is no drk in the phone it won't boot. I lost drk and not able to flash the stock rom.
rahulkr0507 said:
If there is no drk in the phone it won't boot. I lost drk and not able to flash the stock rom.
Click to expand...
Click to collapse
And I lost drk but seems i checked the oem unlock on when rooted the phone and when I flash stock firmware the phone is booted without drk but I can flash twrp with odin and reroot the phone again
ebusuhejbi said:
And I lost drk but seems i checked the oem unlock on when rooted the phone and when I flash stock firmware the phone is booted without drk but I can flash twrp with odin and reroot the phone again
Click to expand...
Click to collapse
Yes its possible but in my case the oem unlock git disabled i dont know how its happened. After that i can't do anything other than the above procedures to make the device working.
Could you change the destination of SM-N920C Combination file, because I can`t download it from your link. Thank you.
Try to rename firmware .tar.md5 to .tar (remove.md5).and flash it via odin .it work
lawong said:
flashing any custom recovery wont work on frp locked. it will fail in odin.
Click to expand...
Click to collapse
try rename firmware original samsung from .tar.md5 to .tar only(remove.md5).and flash it via odin again.it work for me
tassotti said:
Could you change the destination of SM-N920C Combination file, because I can`t download it from your link. Thank you.
Click to expand...
Click to collapse
Its not my link i just given the link from i downloaded the files.
I just checked the link and its working.
rahulkr0507 said:
Its not my link i just given the link from i downloaded the files.
I just checked the link and its working.
Click to expand...
Click to collapse
I found this file on another place. Thank you.
Sent from my SM-N920C using Tapatalk
Help with FRP Locked
I need help with this. I have tried several methods, 2 different ODIN versions, several different firmwares...I cannot get out of FRP lock. Please, Please help me.
Please explain the problem in detail. Whats shown in phone about the failure?
lonewolf5557 said:
I need help with this. I have tried several methods, 2 different ODIN versions, several different firmwares...I cannot get out of FRP lock. Please, Please help me.
Click to expand...
Click to collapse
Flashing firmwares will not undo FRP. No matter how many you flash. Solving the FRP problem lies elsewhere. And to another comment some FRp locked sammys will flash in odin under lock,Others will not. FRP lock is contained in a Partition in the device that is not touched by odin. If flashing orig stock firmware does not boot due to DRK problem then that has to be addressed first. I have not had a Note 5 in a while but This much I do know.
TheMadScientist said:
Flashing firmwares will not undo FRP. No matter how many you flash. Solving the FRP problem lies elsewhere. And to another comment some FRp locked sammys will flash in odin under lock,Others will not. FRP lock is contained in a Partition in the device that is not touched by odin. If flashing orig stock firmware does not boot due to DRK problem then that has to be addressed first. I have not had a Note 5 in a while but This much I do know.
Click to expand...
Click to collapse
Where do I start then, please. Thank you.
Related
Hello guys hoping to get some help with this issue. So...I flashed the update for SuperSU on my S7 Edge using FlashFire, after flash it went into boot and this is what i got; "Custom binary blocked by SECURE BOOT (boot.img)" on left cornor and "Security Error: This phone has been flashed with unauthorized software & is locked. Call your phone operator for additional support." I can go into recovery mode, I tried to factory reset but did not work. Any help would be greatly welcome. I am still noob at this so please go ez on me
Stock Firmware for S7 Edge G935T UVU3APG1
Duggi1663 said:
Hello guys hoping to get some help with this issue. So...I flashed the update for SuperSU on my S7 Edge using FlashFire, after flash it went into boot and this is what i got; "Custom binary blocked by SECURE BOOT (boot.img)" on left cornor and "Security Error: This phone has been flashed with unauthorized software & is locked. Call your phone operator for additional support." I can go into recovery mode, I tried to factory reset but did not work. Any help would be greatly welcome. I am still noob at this so please go ez on me
Click to expand...
Click to collapse
Update..
So... I decided to flash Stock Firmware and now its working like a charm . hope this helps others with the same situation. Cheers
Duggi1663 said:
Update..
So... I decided to flash Stock Firmware and now its working like a charm . hope this helps others with the same situation. Cheers
Click to expand...
Click to collapse
Its not necessary to flash stock, simply reflashing the engboot will suffice, and does not wipe the device.
First of all you wanted to Flash SuperSu.... Did you enable Android Debugging.... Then check OEM Unlock?
If not you messed up there...
Next You need use Odin to flash CF-Root. You are now running a patched Kernel and SuperSU
Use TWRP app to install twrp for your device.
i have the same exact problem, been trying to flash stock firmware but cant get it to work. help please!!!! which firmware? can i get a link please!!!!!!!!!!
qwewqa said:
Its not necessary to flash stock, simply reflashing the engboot will suffice, and does not wipe the device.
Click to expand...
Click to collapse
Hello, having same issue. Didn't realize you can only make backups with flashfire, not actually flash them back with the program too...
I have the original files I installed with Odin, are one of these the engineering boot file? (BL, AP, CP, CSC?)
Or are you talking about something else...? Thanks!
BobTheTenth said:
Hello, having same issue. Didn't realize you can only make backups with flashfire, not actually flash them back with the program too...
I have the original files I installed with Odin, are one of these the engineering boot file? (BL, AP, CP, CSC?)
Or are you talking about something else...? Thanks!
Click to expand...
Click to collapse
You flash the engboot file you used to root the device, the one you placed in AP and is around 20 mb in size (not the actual firmware) .
qwewqa said:
You flash the engboot file you used to root the device, the one you placed in AP and is around 20 mb in size (not the actual firmware) .
Click to expand...
Click to collapse
Thanks!
Recovery locked
hello everyone, my galaxy s8 was on stock rom, it was rooted with odin and super su, i made a mistake....
i installed twrp and wanted to flash it, it said that that it all flashed correctly, when i rebooted the phone it got stuck on the galaxy s8 logo, wont turn off and wont enter recovery mode, only thing i can do is enter download mode.
i tried to do whats written in this topic:
https://forum.xda-developers.com/galaxy-s8/help/stuck-bootloop-flashing-aqg5-fix-t3636857
im not 100% sure of my firmware version, its the one that came out with galaxy s8 when it launched 6.1 or 7.1
so i download the BL file to use it in odin, i tried the 1AQF7 and 1AQG7 also 1AGDG...
nothing helps, whenever i enter download mode and press START on odin with BL file added and straight away after pressing start hold down the volume down, plus bixby plus power i get the writing in odin NAND write start, i can never get beyond that, does that mean no matter how fast i try pressing all 3 buttons down, bixby and power i will never be able to fix the boot? or am i to slow?
can i push the needed file to fix the bootloader with ADB?
what else can i do now? is it anyhow possible to fix the boot, or if not to somehow please recover the data and transfer it to my pc memory? and start from scratch again with the phone as a last solution.
thank you all so much for your help in advance, been trying all day to fix it with odin, but no luck.
when i enter download mode this is written on my screen, maybe it helps:
odin mode
download speed:fast
product name: sm-g950f
current binary: custom
system status: custom
fap lock: off
oem lock: off
secure download: enabled
CCIC=S2MM005 hw: 6 boot 7 main:35
WARRANTY VOID 1 (0x0500)
RP SWREV: B:1 K:1 S:1
DID =0077ce53b1c2
EVT 1.1
LOT_ID=NBV09
rest is chip id etc which i think cant help anything.
thank you all once more
can someone please give me any help to boot back into android or recovery or recover my files ?
drazenm said:
can someone please give me any help to boot back into android or recovery or recover my files ?
Click to expand...
Click to collapse
i do not think you will b able to recover or boot back into android but you should be able to flash an official firmware using odin to get your phone up and running again.
you should always back up important stuff on your phone before attempting any flashing
How about using Odin to 'dirty' flash the exact firmware last working on your phone? For "dirty", I meant flashing home_csc which doesn't force a data wipe.
ikeny said:
How about using Odin to 'dirty' flash the exact firmware last working on your phone? For "dirty", I meant flashing home_csc which doesn't force a data wipe.
Click to expand...
Click to collapse
i have nothing to loose, how can i perform that? i think i know the firmware that ive used, but if i dont how can i be sure which one ive used ?
thank you .
if anyone can help/explain, so i know if i can do anything or i will have to wipe my phone
drazenm said:
i have nothing to loose, how can i perform that? i think i know the firmware that ive used, but if i dont how can i be sure which one ive used ?
thank you .
Click to expand...
Click to collapse
Go to sammobile.com, search firmware by country and carrier.
ikeny said:
Go to sammobile.com, search firmware by country and carrier.
Click to expand...
Click to collapse
i downloaded the firmware that i think i used, and i also downloaded the newest one. so what do i do now ?
drazenm said:
i downloaded the firmware that i think i used, and i also downloaded the newest one. so what do i do now ?
Click to expand...
Click to collapse
Google - how to flash firmware with Odin.
ikeny said:
Google - how to flash firmware with Odin.
Click to expand...
Click to collapse
i know how to flash firmware with odin but how am i to do it to repair my current firmware or patch it up as you have said?
so i dont overwrite and loose ma data?
thank you
I have issue too. I flash custom binary and bootloader don't allow boot to recovery via hard buttons. Now I boot to recovery via computer or rooted rom.
Hello everybody,
I got a Samsung Galaxy S7 Edge (SM-G935F) DBT version and flashed a Custom ROM (Firmware? idk the difference).
I did that like this: youtube.com/watch?v=_1ofpLHMVvA
Unfortunately there were a few problems there, like the camera is awful now (Bad quality and other camera apps didnt made it better).
So now I want back my Stock ROM. (Yes, Unfortunately I didnt made a Backup)
But I cant get it back, neither with TWRP or with Odin.
At Odin its stops at system.img and fails than and at TWRP I guess I used the wrong Rom because is said Zip file is corrupt!.
The following Stock ROM did I use for Odin and TWRP: updato.com/firmware-archive-select-model?record=2A12F0CE03CD11E7963AFA163EE8F90B
At Odin I unziped it and added it the right way: (BL, AL, CP and CSC).
At TWRP I didnt unziped it and used it like it is.
I hope you can help me there.
I have already made the following:
Changed USB Port
Changed USB cabel
Used Smart Switch
And yes, I can still install custom roms like LineageOS and Resurrection easily via TWRP.
Greetings, Darkatzu.
bump
Darkatzu said:
bump
Click to expand...
Click to collapse
Which procedure you followed to root and install custom rom?
Sent from my S7 Edge using XDA Labs
shah22 said:
Which procedure you followed to root and install custom rom?
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Is that important? I dont think so...
Darkatzu said:
Is that important? I dont think so...
Click to expand...
Click to collapse
It is, because you will need no verity opt encrypt to flash too alongside official stock rom in order to use stock rom if you rooted by system modification method, with oreo 8.0 I think no verity zip is not working, so you need to flash latest nougat for your country/region alongside twrp , no verity zip and super su, you can download latest stock firmware for your region from samfirm application or updato, also download odin version 3.13.1, latest twrp recovery, super su and no verity opt encrypt from here on xda forums, first check and enable oem unlock, flash stock rom and then flash twrp through odin, then boot in twrp recovery and flash no verity and super su zips, to get detailed info on above steps search the forums. AND PLEASE TELL WHATS ASKED IF YOU WANT TO GET HELPED.
!! NOTE : IF YOU ROOTED FIRST TIME BY SYSTEM MODIFICATION METHOD, AND THEN INSTALLED CUSTOM ROM, THEN FLASHING STOCK ROM BACK WILL PUT YOU ON A DM VERITY ERROR. ALWAYS REMEMBER TO ENABLE OEM UNLOCK IN DEVELOPER OPTIONS BEFORE DOING ANYTHING!
HAVING OEM UNLOCK DISABLED AND THEN ROOTING VIA SYSTEM MODIFICATION METHOD, AND THEN FLASHING STOCK ROM WILL PUT YOU IN A HARD BRICK SITUATION WITH BOTH DM VERITY ERROR AND CUSTOM BINARY BLOCKED ERROR !!
As far as I know the above situation has no solution if you get into this mess and only a memory swap on board or some box can fix this. I know many users here on xda are stuck on this situation. Some users said they fixed this by using nand erase all and re partition using pit file options during flashing in odin, but I really doubt enabling these options will solve this if not making problems worse. Anyone is welcomed to correct me if the above situation has any solution. BUT THAT IS WHY SYSTEMLESS ROOT IS THERE TO AVOID ALL THIS...
Sent from my S7 Edge using XDA Labs
shah22 said:
It is, because you will need no verity opt encrypt to flash too alongside official stock rom in order to use stock rom if you rooted by system modification method, with oreo 8.0 I think no verity zip is not working, so you need to flash latest nougat for your country/region alongside twrp , no verity zip and super su, you can download latest stock firmware for your region from samfirm application or updato, also download odin version 3.13.1, latest twrp recovery, super su and no verity opt encrypt from here on xda forums, first check and enable oem unlock, flash stock rom and then flash twrp through odin, then boot in twrp recovery and flash no verity and super su zips, to get detailed info on above steps search the forums. AND PLEASE TELL WHATS ASKED IF YOU WANT TO GET HELPED.
!! NOTE : IF YOU ROOTED FIRST TIME BY SYSTEM MODIFICATION METHOD, AND THEN INSTALLED CUSTOM ROM, THEN FLASHING STOCK ROM BACK WILL PUT YOU ON A DM VERITY ERROR. ALWAYS REMEMBER TO ENABLE OEM UNLOCK IN DEVELOPER OPTIONS BEFORE DOING ANYTHING!
HAVING OEM UNLOCK DISABLED AND THEN ROOTING VIA SYSTEM MODIFICATION METHOD, AND THEN FLASHING STOCK ROM WILL PUT YOU IN A HARD BRICK SITUATION WITH BOTH DM VERITY ERROR AND CUSTOM BINARY BLOCKED ERROR !!
As far as I know the above situation has no solution if you get into this mess and only a memory swap on board or some box can fix this. I know many users here on xda are stuck on this situation. Some users said they fixed this by using nand erase all and re partition using pit file options during flashing in odin, but I really doubt enabling these options will solve this if not making problems worse. Anyone is welcomed to correct me if the above situation has any solution. BUT THAT IS WHY SYSTEMLESS ROOT IS THERE TO AVOID ALL THIS...
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
I showed a Video Tutorial how I did that.
The reason why I did that, is for me: Not important.
And yes, I did OEM unlock.
shah22 said:
so you need to flash latest nougat for your country/region alongside twrp
Click to expand...
Click to collapse
So far so good.
shah22 said:
you can download latest stock firmware for your region from samfirm application or updato
Click to expand...
Click to collapse
As I did. (both)
shah22 said:
also download odin version 3.13.1, latest twrp recovery
Click to expand...
Click to collapse
Already done.
shah22 said:
super su and no verity opt encrypt from here on xda forums
Click to expand...
Click to collapse
Ok I didnt done that, but now I got I did.
shah22 said:
first check and enable oem unlock
Click to expand...
Click to collapse
Done.
shah22 said:
flash stock rom
Click to expand...
Click to collapse
Aaaand failed as I described already.
Darkatzu said:
I showed a Video Tutorial how I did that.
The reason why I did that, is for me: Not important.
And yes, I did OEM unlock.
So far so good.
As I did. (both)
Already done.
Ok I didnt done that, but now I got I did.
Done.
Aaaand failed as I described already.
Click to expand...
Click to collapse
Maybe you are using an older bootloader ? Can't say for sure whats causing it, the method you used above I think required system modifications, but you are using a march 2017 stock rom, so it looks updato don't has V2 bootloader firmwares for DBT, problems may happen when flashing an older bootloader on a newer one, it could also be your pc or other hardware problem, but in case try again and download samfirm from here : https://forum.xda-developers.com/attachment.php?attachmentid=3803841
Enter DBT as your region and model SM-G935F , it will download the latest stock available, be sure option for auto decrypt, check crc32 and binary nature are ticked.
After that check oem unlock and usb debugging is enabled and follow the steps :
1. Put phone in download mode, use original usb cable, and make sure pc usb port is working correctly. Also phone must be charged above 50%.
2. Download odin 3.13.1 from here https://forum.xda-developers.com/attachment.php?attachmentid=4431597&d=1519662712
Latest twrp available https://eu.dl.twrp.me/hero2lte/twrp-3.2.1-1-hero2lte.img.tar.html
Latest no verity opt encrypt https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip
Latest stable super su https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
3. Put phone in download mode, extract the firmware downloaded above from samfirm tool and put the respective files in their boxes, use CSC and NOT HOME_CSC. Make sure no option other than F.reset time is ticked in odin options. Begin the flash procedure. After it is completed, don't reboot and place twrp zip downloaded from above in the AP tab of odin. After it is completed, stay in download mode and hold power+home+vol down to reboot from download mode and immediately switch to vol up button to boot in twrp recovery menu.
4. In twrp recovery menu, you need to swipe for system modifications or tick read only ( if you previously allowed for system modifications then you can do it again it doesn't matter, but if you previously didn't swipe for system modifications then tick read only and download systemless zip from https://forum.xda-developers.com/s7-edge/development/samsung-systemless-devbase-encryption-t3517178 )
I will recommend this as you won't need to flash dm verity.
5. Now, go to wipe> format data in twrp recovery, after its done, flash super su and system less zip through twrp to get system less root if you don't want to get dm verity error hassle when flashing stock roms OR flash super su and no verity opt encrypt if you already have allowed system modifications. After that reboot. It may take sometime.
Also to note if you never allowed system modifications before in twrp, and you don't want to root either, then you can safely flash stock without flashing twrp or going through further steps.
This is what I could best explain according to my limited knowledge, if you still fail to flash stock in odin, then I am not sure it may be your pc or other hardware problem and you may need a repair box, try checking on another pc or some expert user to help. Good Luck.
These steps are only for installing stock rom back on previously rooted S7 edge devices using custom roms and for rooting a stock rom.. and only applies to SM-G935F
Sent from my S7 Edge using XDA Labs
shah22 said:
Maybe you are using an older bootloader ? Can't say for sure whats causing it, the method you used above I think required system modifications, but you are using a march 2017 stock rom, so it looks updato don't has V2 bootloader firmwares for DBT, problems may happen when flashing an older bootloader on a newer one, it could also be your pc or other hardware problem, but in case try again and download samfirm from here : https://forum.xda-developers.com/attachment.php?attachmentid=3803841
Enter DBT as your region and model SM-G935F , it will download the latest stock available, be sure option for auto decrypt, check crc32 and binary nature are ticked.
After that check oem unlock and usb debugging is enabled and follow the steps :
1. Put phone in download mode, use original usb cable, and make sure pc usb port is working correctly. Also phone must be charged above 50%.
2. Download odin 3.13.1 from here https://forum.xda-developers.com/attachment.php?attachmentid=4431597&d=1519662712
Latest twrp available https://eu.dl.twrp.me/hero2lte/twrp-3.2.1-1-hero2lte.img.tar.html
Latest no verity opt encrypt https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip
Latest stable super su https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
3. Put phone in download mode, extract the firmware downloaded above from samfirm tool and put the respective files in their boxes, use CSC and NOT HOME_CSC. Make sure no option other than F.reset time is ticked in odin options. Begin the flash procedure. After it is completed, don't reboot and place twrp zip downloaded from above in the AP tab of odin. After it is completed, stay in download mode and hold power+home+vol down to reboot from download mode and immediately switch to vol up button to boot in twrp recovery menu.
4. In twrp recovery menu, you need to swipe for system modifications or tick read only ( if you previously allowed for system modifications then you can do it again it doesn't matter, but if you previously didn't swipe for system modifications then tick read only and download systemless zip from https://forum.xda-developers.com/s7-edge/development/samsung-systemless-devbase-encryption-t3517178 )
I will recommend this as you won't need to flash dm verity.
5. Now, go to wipe> format data in twrp recovery, after its done, flash super su and system less zip through twrp to get system less root if you don't want to get dm verity error hassle when flashing stock roms OR flash super su and no verity opt encrypt if you already have allowed system modifications. After that reboot. It may take sometime.
Also to note if you never allowed system modifications before in twrp, and you don't want to root either, then you can safely flash stock without flashing twrp or going through further steps.
This is what I could best explain according to my limited knowledge, if you still fail to flash stock in odin, then I am not sure it may be your pc or other hardware problem and you may need a repair box, try checking on another pc or some expert user to help. Good Luck.
These steps are only for installing stock rom back on previously rooted S7 edge devices using custom roms and for rooting a stock rom.. and only applies to SM-G935F
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
As I already said: As I did. (both)
I already tried with samfire.
Same error.
Sorry I couldn't be much help. Does it always stucks in odin at system.img? Looks like its a hardware problem in your pc/usb ports or phone's usb jack. Try getting your phone checked by a repairer, flashing from another pc or changing usb cable. Also try running odin as an admin or try with an older odin version. Good Luck
Sent from my S7 Edge using XDA Labs
shah22 said:
Sorry I couldn't be much help. Does it always stucks in odin at system.img? Looks like its a hardware problem in your pc/usb ports or phone's usb jack. Try getting your phone checked by a repairer, flashing from another pc or changing usb cable. Also try running odin as an admin or try with an older odin version. Good Luck
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Yes it suck always at system.img!
And I can easily flash custom roms via. TWRP.
And I can flash TWRP via Odin without any errors.
Do u even read my post?
Changed USB cabel
Click to expand...
Click to collapse
And yes, I changed PC 2 and yes tryed other versions of Odin LIKE where AP is named as PDA.
Strange thing if you could flash recovery but not the stock rom, looks like you need to get it checked by a tech. But as a last resort did you tried using pit file and repartition ticked? To get the pit file extract the CSC file and you will find .pit file there, open pit tab in latest odin and select that pit file, then tick repartition box and proceed to flash with all other files selected in their respective boxes. If its still the same then I guess I can be of no more help. Cheers !
!! Warning : Using pit file is never recommended and it could brick your phone permanently if there is any power outage/usb disconnection during flashing with pit, it is used to correct file system partitions if they are changed/corrupted. Its better to outweigh benefits with potential danger. Also a pit file will erase all partitions first, then write flash data from beginning and if you again stuck at system.img when using pit file, you will be left with a permanent brick. So I will recommend to get it checked by a tech if you want stock rom that bad and don't do any risky thing with your pricey phone
Sent from my S7 Edge using XDA Labs
shah22 said:
Strange thing if you could flash recovery but not the stock rom, looks like you need to get it checked by a tech. But as a last resort did you tried using pit file and repartition ticked? To get the pit file extract the CSC file and you will find .pit file there, open pit tab in latest odin and select that pit file, then tick repartition box and proceed to flash with all other files selected in their respective boxes. If its still the same then I guess I can be of no more help. Cheers !
!! Warning : Using pit file is never recommended and it could brick your phone permanently if there is any power outage/usb disconnection during flashing with pit, it is used to correct file system partitions if they are changed/corrupted. Its better to outweigh benefits with potential danger. Also a pit file will erase all partitions first, then write flash data from beginning and if you again stuck at system.img when using pit file, you will be left with a permanent brick. So I will recommend to get it checked by a tech if you want stock rom that bad and don't do any risky thing with your pricey phone
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
A tech is 2 expensive for me.
And yes, I already did it with pit file and the whole CSC file.
#push
#push
#push
#push
Darkatzu said:
#push
Click to expand...
Click to collapse
try with chimeratool, it worked for me, l use a free license to download the firm from server and install it
#push
shah22 said:
It is, because you will need no verity opt encrypt to flash too alongside official stock rom in order to use stock rom if you rooted by system modification method, with oreo 8.0 I think no verity zip is not working, so you need to flash latest nougat for your country/region alongside twrp , no verity zip and super su, you can download latest stock firmware for your region from samfirm application or updato, also download odin version 3.13.1, latest twrp recovery, super su and no verity opt encrypt from here on xda forums, first check and enable oem unlock, flash stock rom and then flash twrp through odin, then boot in twrp recovery and flash no verity and super su zips, to get detailed info on above steps search the forums. AND PLEASE TELL WHATS ASKED IF YOU WANT TO GET HELPED.
!! NOTE : IF YOU ROOTED FIRST TIME BY SYSTEM MODIFICATION METHOD, AND THEN INSTALLED CUSTOM ROM, THEN FLASHING STOCK ROM BACK WILL PUT YOU ON A DM VERITY ERROR. ALWAYS REMEMBER TO ENABLE OEM UNLOCK IN DEVELOPER OPTIONS BEFORE DOING ANYTHING!
HAVING OEM UNLOCK DISABLED AND THEN ROOTING VIA SYSTEM MODIFICATION METHOD, AND THEN FLASHING STOCK ROM WILL PUT YOU IN A HARD BRICK SITUATION WITH BOTH DM VERITY ERROR AND CUSTOM BINARY BLOCKED ERROR !!
As far as I know the above situation has no solution if you get into this mess and only a memory swap on board or some box can fix this. I know many users here on xda are stuck on this situation. Some users said they fixed this by using nand erase all and re partition using pit file options during flashing in odin, but I really doubt enabling these options will solve this if not making problems worse. Anyone is welcomed to correct me if the above situation has any solution. BUT THAT IS WHY SYSTEMLESS ROOT IS THERE TO AVOID ALL THIS...
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
hi, i used this thread to root my regular s7 from sprint, am i going to be able to just flash the latest firmware back to stock and be good to go or am i hosed?
thanks
hikouka71 said:
hi, i used this thread to root my regular s7 from sprint, am i going to be able to just flash the latest firmware back to stock and be good to go or am i hosed?
thanks
Click to expand...
Click to collapse
No, i don't think so as you already flashed engineering kernel, i won't recommend but if you already tried, do post your results ..
Sent from my S7 Edge using XDA Labs
Hello xda Community,
it's me again but this time in the S7 Edge section.
I have a very big problem. I have a Galaxy S7 Edge and I think it's bricked.
The Phone won't turn on and I'm not able to enter the recovery mode but the download mode is working.
I have tried to flash the Oreo Stock Rom but this didn't worked. Moreover I've tried to flash the TWRP recovery but this failed too
I get errors like Kernel Rev check fail device or sw rev check fail Bootloader.
I should mention that the FRP Lock is ON
Please help me guys I thank you all for the ideas
PS: I'm very sorry about my English. I know, it's not perfect :laugh:
Your stock software should match with mobile type .If they are same it wont be a problem..
Najam9849 said:
Your stock software should match with mobile type .If they are same it wont be a problem..
Click to expand...
Click to collapse
it doesn't work for me. I have tried to left the BL part empty but this also failed
does somebody has an idea ? :crying:
Pick a right version from sammobile and do this with old version of odin .Try try try and you might end up in success.
xTheGerman said:
Hello xda Community,
it's me again but this time in the S7 Edge section.
I have a very big problem. I have a Galaxy S7 Edge and I think it's bricked.
The Phone won't turn on and I'm not able to enter the recovery mode but the download mode is working.
I have tried to flash the Oreo Stock Rom but this didn't worked. Moreover I've tried to flash the TWRP recovery but this failed too
I get errors like Kernel Rev check fail device or sw rev check fail Bootloader.
I should mention that the FRP Lock is ON
Please help me guys I thank you all for the ideas
PS: I'm very sorry about my English. I know, it's not perfect :laugh:
Click to expand...
Click to collapse
I did the same thing but i managed to get it working by flashing TRWP again through odin. It would also be better if u copy over a custom rom aswell using the adb push command in terminal because i accidentaly set off DM verity.
anonymous4272 said:
I did the same thing but i managed to get it working by flashing TRWP again through odin. It would also be better if u copy over a custom rom aswell using the adb push command in terminal because i accidentaly set off DM verity.
Click to expand...
Click to collapse
My S7 Edge is blocking the flash process with Odin because of the FRP Lock
Thats why I am not able to Flash TWRP
Flash twrp and then a custom rom afterwards..
Najam9849 said:
Flash twrp and then a custom rom afterwards..
Click to expand...
Click to collapse
I already said that I'm not able to flash TWRP. The reason is that my phone denies the flash process because of the FRP Lock
you can try https://forum.xda-developers.com/s7-edge/how-to/how-to-remove-frp-lock-guide-t3855793
I had this exact same problem a month back, I forgot to enable OEM unlock and I faced the same issues.
I downloaded the very latest stock rom at the time, and it was the 1st November security patch version. Try that and let me know.
Go to grifofdev and then ask the admin.He is a helpful person and will solve your problem..
Download the latest oreo firmware from updato, sammobile download speed is ridiculous. The latest at the time solved it for me 100%
sibozzy29 said:
Download the latest oreo firmware from updato, sammobile download speed is ridiculous. The latest at the time solved it for me 100%
Click to expand...
Click to collapse
It helped me aswell!!
Samsung Galaxy A5 2016
Guys, a major problem here. So i cant turn on my phone..
Its stuck on boot screen with the following message "Custom Binary blocked by FRP Lock"
Can't boot to twrp custom recovery (power+home+volup)
------
The only thing it can do is boot in to Odin downloader (power+home+voldown)
So i have already searched for a solution but all of those require a computer and a total hard reset of my phone. Which i don't want to. Because i don't want to lose all of my apps etc.
Is there a way i can bypass this frp lock? Without any major reset?
Pakoszz said:
Samsung Galaxy A5 2016
Guys, a major problem here. So i cant turn on my phone..
Its stuck on boot screen with the following message "Custom Binary blocked by FRP Lock"
Can't boot to twrp custom recovery (power+home+volup)
------
The only thing it can do is boot in to Odin downloader (power+home+voldown)
So i have already searched for a solution but all of those require a computer and a total hard reset of my phone. Which i don't want to. Because i don't want to lose all of my apps etc.
Is there a way i can bypass this frp lock? Without any major reset?
Click to expand...
Click to collapse
Flash twrp and take backup and reset
bunnyy said:
Flash twrp and take backup and reset
Click to expand...
Click to collapse
You mean flash twrp with odin and restore backup trough twrp and then its fine?
Pakoszz said:
You mean flash twrp with odin and restore backup trough twrp and then its fine?
Click to expand...
Click to collapse
Aren’t you on stock??
bunnyy said:
Aren’t you on stock??
Click to expand...
Click to collapse
I am on stock ROM with root, but recovery isn't stock its twrp.
I installed twrp back in 2017 to make backups.
Luckily i made a recent 2019 backup.
Ok, so i have tried to flash twrp with odin. At first it looks like its flasing. But then suddenly it says FAIL! in red collor! On my PC
And on my phone in Odin screen it shows me a message.
"Custom Binary(RECOVERY) Blocked by FRP Lock
So what do i do now?
Cant start the phone , cant acces twrp..
Pakoszz said:
Ok, so i have tried to flash twrp with odin. At first it looks like its flasing. But then suddenly it says FAIL! in red collor! On my PC
And on my phone in Odin screen it shows me a message.
"Custom Binary(RECOVERY) Blocked by FRP Lock
So what do i do now?
Cant start the phone , cant acces twrp..
Click to expand...
Click to collapse
Then there’s no option other than restoring your phone to factory state.
bunnyy said:
Then there’s no option other than restoring your phone to factory state.
Click to expand...
Click to collapse
Okay, thats ok. Most of my new data is on my sd card.
Just one question, i have never done a hard reset with this phone.. Where do i find a stock Samsung a5 2016 europe rom to flash? And a tutorial?
Pakoszz said:
Okay, thats ok. Most of my new data is on my sd card.
Just one question, i have never done a hard reset with this phone.. Where do i find a stock Samsung a5 2016 europe rom to flash? And a tutorial?
Click to expand...
Click to collapse
Sammobile or updato for samsung firmware make sure to download the correct firmware
For steps its pretty easy
Just download the zip extract it
Open Odin and in the AP section select the file
Make sure your phone is connected to pc in download mode
And start the flashing wait for it to complete
Done[emoji1303][emoji1303]
bunnyy said:
Sammobile or updato for samsung firmware make sure to download the correct firmware
For steps its pretty easy
Just download the zip extract it
Open Odin and in the AP section select the file
Make sure your phone is connected to pc in download mode
And start the flashing wait for it to complete
Done[emoji1303][emoji1303]
Click to expand...
Click to collapse
Thanks for the help. :good:
bunnyy said:
Sammobile or updato for samsung firmware make sure to download the correct firmware
For steps its pretty easy
Just download the zip extract it
Open Odin and in the AP section select the file
Make sure your phone is connected to pc in download mode
And start the flashing wait for it to complete
Done[emoji1303][emoji1303]
Click to expand...
Click to collapse
Just an update for future users passing by.
So basically everything went ok. Even better then ok!
I used Odin to flash a ROM which i found on Updato.. Used the PHN ROM version.
And surprisingly it didn't erase anything of my phone. It just gave it an update. Everything is the same again, data is intact, apps are still there. But with some updated apps from Samsung itself. I guess they included some security patches too.
Previously my phone wouldn't be able receive OTA updates, because it would say. You phone is modified/rooted or something like that.
Seems to me that flashing, updated everything without losing anything.
Good, couldn't be happier. Thanks again!.