I have been modifying my device by installing custom roms rooting etc. I know my warranty is void but my device won't even get recognized in smart manager when entering IMEI. when booted up to odin mode i don't see an option anymore to see "show Barcode". My device is still functional but I want to try to go back to stock official everything. Is there a way to fix this issue by installing or flashing anything? I think its because of the installation of xposed. Please reply.
JerryIsaMaster said:
I have been modifying my device by installing custom roms rooting etc. I know my warranty is void but my device won't even get recognized in smart manager when entering IMEI. when booted up to odin mode i don't see an option anymore to see "show Barcode". My device is still functional but I want to try to go back to stock official everything. Is there a way to fix this issue by installing or flashing anything? I think its because of the installation of xposed. Please reply.
Click to expand...
Click to collapse
Flash the official firmware for your model via ODIN, that is the way to get back to stock.
Use your serial number not imei in smart switch
Sent from my SM-G920F using XDA Free mobile app
that hasn't worked but i did fix it by flashing stock firmware over Odin and update through smart switch and i am now on the latest update with samsung pay, i wish i could use actually use it
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
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
I've checked on my download mode screen and Knox isn't tripped and my device status is official.
However, today, after installing official Samsung software, Samsung health claims it can't run on a rooted device, which mine isn't. I have tried reinstalling it and factory resetting. I've tried installing the PHE firmware which it supposedly came with, but to no avail. What can I do?
Also, what is a foolproof way to know which specific firmware my phone came with?
Thank you.
Good Morning Everyone
As the title suggests, i am looking to return my S22 Ultra back to stock.
i was on beyond rom for a bit, but too many apps complaining that my device was rooted has forced my hand to return my device back to stock once again.
I flashed the stock rom via odin, then locked my bootloader and wiped all data.
However i am still getting messages that my device is modifed.
Anyone got any ideas how to can truely return to full stock?
Thanks in advanced.
And yes i did do a search on the internet before asking, but i have been unable to find any advice outside of what i have already done.
happend to me, too. But only on the latest firmware. When I flash an older firmware, it won't appear. But after updating again to the latest ROM the message appears
Cheers mate. I'll give that a go.
Also note that if the device was rooted then you triggered the Knox flag and that one CANNOT BE RESET, it's an "efuse" (a hardware component that once changed it's state can only be reset by replacing it, i believe you need to replace the entire motherboard for that).
So, if the application checks the Knox status it will fail.
Here are a few apps that i know that will not work anymore :
- Knox itself (and any app that uses the Knox library/API )
- Samsung Pay
- Samsung Health
- Secure Folder
A few years ago I also had a banking app that failed to worked with a Knox flag triggered (on a Note 8), but after an update it allowed me to use the phone as long as i didn't have it rooted.