Hey guys firstly i want to apologize if i'm on the wrong forum.
I have screwed up and i hope you guys could help.
I have a Samsung S6 that worked perfectly, but i wanted to sell it and buy an S7 and so i have done a "hard" factory reset by pushing Vol up, Home, Power buttons. Turns out i had to do a "soft" factory reset first.
Now when i tried to sell my phone with all parts and documents i have failed!
It turns out that the phone asks for my Samsung ID but obviously i can't remember an ID that i have created more than a year ago that was of no use to me!
I think i still have warranty but that is my last option for something like this, i have not rooted this device it runs on marshmallow.
What can i do to fix it myself?
I haven't tried flashing it with a stock rom simply because i fear that that will trigger KNOX, even though i'm desperate to fix this, i haven't crossed that border of despair.
Guys please help, i'm counting on your replies.
Thank you.
Flashing a stock rom that was made for your phone will NOT trigger knox. You can use samfirm and odin to do it
ankushkatari said:
Flashing a stock rom that was made for your phone will NOT trigger knox. You can use samfirm and odin to do it
Click to expand...
Click to collapse
Thanks for your reply, do you mean from sammobile? Also i do not remember what version if marshmallow i was running, is there a way for me to figure it out now?
Okay i figured out what version of marshmallow i was running simply because i had put updates on automatic so it must be the last 6.0.1
However i do not know anything about samfirm i have used odin before on my s4 like 3 years ago, and i only used it to root my s4.
Could anyone please help me out?
Btw, if i successfully put a stock firmware on it throigh samfirm and odin, will it remove my email? Or is it omly worth a try?
Are you certain that it will not trigger knox?
Okay i tried flashing the same firmware unto my devicd but it seems that i can't flash anything because Reactivation Lock is enabled.
I didn't enable it (at least i don't remember) mayve the marshmallow update enabled Reactivation Lock?
I'm almost at the point of throwing my phone into a wall, it's getting close.
Did you figure it out. I'm in the same boat with my S6 edge
I have a Tmobile Galaxy S6 that I rooted earlier today. I fiddled around trying to get odin to install the root, and I finally found my solution when I enabled OEM Unlock in settings. After I installed the root, I disabled OEM Unlock. I then rebooted my phone and now it gives me the "Custom binary blocked by FRP" message every time I try to turn it on. I have tried many different ways of factory resetting my phone. I have tried to install 3 different firmware files, one of them stock, using 5 different versions of odin and 2 different usb cables. No matter what I do I can't get past the FRP Lock. Is there anything I can do or should I take it to a repair shop?
Try some tutorials from YT
Hi,
I've one (big) problem that I can't fix.
I've been using Android 5.0.1 for more than 1 year as I didn't want to upgrade (it worked pretty well) and because I had the S6 rooted with PingPong root.
However, one month ago it started to run slowly, crashing apps, ... so I decided that, as I wanted to wipe the device, why not upgrade to MM (6.0.1)??, so I did.
I did a backup of all my data and EFS folder and downloaded a 6.0.1 ROM to flash it with ODIN. Everything went OK and finished flashing the rom, but when the S6 restarted it showed this in the recovery:
'dm-verity verificztion failed...
Need to check DRK first...'
And I cant boot.
I've tried some tips that are here and in other websites:
- I've flashed stock rom again
- I've flashed a stock rom without cache.img file.
- I Can't flash some files as I've R/L ON. (I've been trying to disable it for many months but I couldn't).
But the S6 doesn't boot...
Thank you!
What worked for me.
So this is my current issue, but i was able to resolve the issue you are having. so what i did was get the 5.1X OK7 (My phone is Verizon) firmware and flashed through ODIN 3.12.5, this flashed stock 5.1.1 in my phone and it worked good. however i have issue with my phone random restarts and power button not working in recovery or in rom. however i can go in and out of downloading mode or maintenance mode.
Critical_DoubleShot said:
So this is my current issue, but i was able to resolve the issue you are having. so what i did was get the 5.1X OK7 (My phone is Verizon) firmware and flashed through ODIN 3.12.5, this flashed stock 5.1.1 in my phone and it worked good. however i have issue with my phone random restarts and power button not working in recovery or in rom. however i can go in and out of downloading mode or maintenance mode.
Click to expand...
Click to collapse
Thanks for your reply!
I tried to downgrade to 5.1.1 or 5.0.1 but I get an error.
(SW REV CHECK FAIL DEVICE 2 BINARY 1)
That happens when you don't have the right firmware you have.
You CANNOT downgrade to 5.1 or 5.0 since you are on 6.0. The bootloaders refuses to be overwritten.
Critical_DoubleShot said:
That happens when you don't have the right firmware you have.
Click to expand...
Click to collapse
I'm trying to flash another 6.0.1 ROM (a bit older), but I get 'CHECK FAIL. DEVICE: 4, BINARY:3'
I've read that DRK problems are related with EFS files, so... Can I restore EFS folder (I've a backup from Android 5.0.1) to solve?? I don't know how to restore it without booting into the sistem (and without custom recovery)
I am afraid that downgrade to 5.0.1 is not possible, at least I dont know anyone who succedeed in doing that.
If you were on systemless root, probably your Knox is still 0, check it in DL mode, if it is and you have the phone less that 3 yrs (1 yr warranty+2yrs factory warranty) best solution would be to ask in Samsung repair center if the factory warranty would be accepted (ofcourse dont mention flashing, just say you tried official update, and play dumb).
If not you can try custom kernel wich will bypass DRK, and prolly make the phone bootable, but there is no guarantee everything will work well (maybe it will, but mostly it doesnt, forget using Samsung pay, and KNOX tripped)
As for EFS, maybe I am wrong, but I think EFS contains IMEI and sn info, and DRK is something else.
brenner650 said:
I am afraid that downgrade to 5.0.1 is not possible, at least I dont know anyone who succedeed in doing that.
If you were on systemless root, probably your Knox is still 0, check it in DL mode, if it is and you have the phone less that 3 yrs (1 yr warranty+2yrs factory warranty) best solution would be to ask in Samsung repair center if the factory warranty would be accepted (ofcourse dont mention flashing, just say you tried official update, and play dumb).
If not you can try custom kernel wich will bypass DRK, and prolly make the phone bootable, but there is no guarantee everything will work well (maybe it will, but mostly it doesnt, forget using Samsung pay, and KNOX tripped)
As for EFS, maybe I am wrong, but I think EFS contains IMEI and sn info, and DRK is something else.
Click to expand...
Click to collapse
Thank you for your reply!!
I had the device rooted, but with PingPong root, so Knox is still 0. However it shows that the system is "custom".
I'll try the warranty, they may not notice the "custom", just the knox.
I'm with the same problem when trying to flash stock BTU QA7..and only if i flashing cf_root my phone is booting.
Any idea? I don't care about the Knox..
Sent from my SM-G920F using Tapatalk
orbgel10 said:
I'm with the same problem when trying to flash stock BTU QA7..and only if i flashing cf_root my phone is booting.
Any idea? I don't care about the Knox..
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
If you are talking about DRK, the only way to fix it that I know of, other than hw replacement, is via 3rd party professional repair tool. (Octopus/Octoplus box)
If DRK is ok, phone boots normaly, if it is messed up, the only way of booting is with custom kernel which bypass DRK check.
You can check it in recovery, if messed up it will say DM verity failed on bottom of the screen.
Ok, i send my phone to fix, i will tell you what happened.
Sent from my Redmi 3S using Tapatalk
brenner650 said:
I am afraid that downgrade to 5.0.1 is not possible, at least I dont know anyone who succedeed in doing that.
If you were on systemless root, probably your Knox is still 0, check it in DL mode, if it is and you have the phone less that 3 yrs (1 yr warranty+2yrs factory warranty) best solution would be to ask in Samsung repair center if the factory warranty would be accepted (ofcourse dont mention flashing, just say you tried official update, and play dumb).
If not you can try custom kernel wich will bypass DRK, and prolly make the phone bootable, but there is no guarantee everything will work well (maybe it will, but mostly it doesnt, forget using Samsung pay, and KNOX tripped)
As for EFS, maybe I am wrong, but I think EFS contains IMEI and sn info, and DRK is something else.
Click to expand...
Click to collapse
Thanks for your reply!!.
I took my S6 (925F) to a Samsung service center as you said. However, they told me that my S/N was incorrect (I bought a second-hand S6 edge, I think someone changed it) so they couldn't fix it.
Now I'm trying to use SmartSwitch to do a factory reset but it asks me for the S/N and I don't have the original one, just a S/N from a non edge S6 (920F). How can I do the factory reset without my S/N??? Can I use the serial number from another 925F??
Now I'm trying to find an engineering bootloader, to bypass the R/L and flash CF-AutoRoot, custom recovery.... but I only find it for 5.0.1 or... for galaxy S6 G925T, not F.
Finally, I managed to fix my S6 by myself!! (not really, but at least it boots...)
This is what I did:
- I found a factory binary for my S6 so I flashed it via ODIN
- I flashed a 6.0.1 ROM without hidden and without cache
Then it boots without any problems. However, now I can't get into recovery
I hope this will help someone
Can this phone be rooted? iv tried everything iv tried to use king root it didnt work. I tried to flash a recovery with odin but there is no TWRP for it. I tried the j7elite one it didnt work. On some of the tutorials it says Enable OEM unlock but i dont even have that under my developer settings. My android version is 7.0 Can my phone even be rooted yet?
oh im very sorry i just realized this belongs in question and answers. What happens when your a noob Hah.
I have the same phone and same problem
I bought this refurbished from amazon and when i got it it wasnt properly wiped and is frp locked
All i know from trying to use odin to flash it is it fails to flash the device (i got a new usb-c for it) it also looks like it was carrier switched from at&t to t-mobile its on 8.0(which is oreo)
the firmware its showing is G995USQU3CRD4 and i i tried downgrading it and having odin fail getting back to nougat
Ive looked around for the firmware to try to reflash the device but havnt found the current one any help is appriciated as ive neer used odin on any of the main galaxy phones exept a mini remake of the s6 which is the phone ive been using the last few years
ZodiaksEnd said:
I bought this refurbished from amazon and when i got it it wasnt properly wiped and is frp locked
All i know from trying to use odin to flash it is it fails to flash the device (i got a new usb-c for it) it also looks like it was carrier switched from at&t to t-mobile its on 8.0(which is oreo)
the firmware its showing is G995USQU3CRD4 and i i tried downgrading it and having odin fail getting back to nougat
Ive looked around for the firmware to try to reflash the device but havnt found the current one any help is appriciated as ive neer used odin on any of the main galaxy phones exept a mini remake of the s6 which is the phone ive been using the last few years
Click to expand...
Click to collapse
If you're trying to downgrade then the only way to is use the rooted combo by jrkruse in the Verizon forums. That way you can actually get into the phone. Using safe strap there's a flashable zip that will remove any Google account tied to the device
koobie777 said:
If you're trying to downgrade then the only way to is use the rooted combo by jrkruse in the Verizon forums. That way you can actually get into the phone. Using safe strap there's a flashable zip that will remove any Google account tied to the device
Click to expand...
Click to collapse
o thanks ill try to find it later