Galaxy s6 not fully returning to Stock - Galaxy S6 Q&A, Help & Troubleshooting

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

Related

[q] samsung galaxy s3 root accidentyl updated help

I have a rooted android device samsung galaxy s3 and it was running fine and everything till one day it said to install an update. i accepted it and while it was updating all of a sudden it went to that black screen and says, " system software not authorized by Verizon Wireless has been found on your phone. Please turn off you phone and go to the nearest Verizon Wireless store for help." Then thats where i couldn't do anyting with my phone but go to download/ODIN MODE and rebooting system thing where you can reboot system. IM very new and i don't know much about rooting and the meanings of a lot of words like unlock bootloader. If i go to ODIN MODE it says
ODINE MODE
PRODUCT NAME: SCH-1535
CUSTOM BINARY DOWNLOAD: Yes (1 Counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty bit: 1
BOOTLOADER RP SWREV:1
i think this doesn't look good. WHat should i do to make my phone be working again and not showing that black screen.
I already wiped all data and tried to do that StockROm thing on my computer ODIN and still nothing.
Is my bootloader locked? if so do i need to unlock it to make my phone work again? Thanks so much for your time
Same with mine I think it's called a bricked phone and think there is nothing we can do about it, hopefully someone has a solution
Might Work?
Remeax said:
I have a rooted android device samsung galaxy s3 and it was running fine and everything till one day it said to install an update. i accepted it and while it was updating all of a sudden it went to that black screen and says, " system software not authorized by Verizon Wireless has been found on your phone. Please turn off you phone and go to the nearest Verizon Wireless store for help." Then thats where i couldn't do anyting with my phone but go to download/ODIN MODE and rebooting system thing where you can reboot system. IM very new and i don't know much about rooting and the meanings of a lot of words like unlock bootloader. If i go to ODIN MODE it says
ODINE MODE
PRODUCT NAME: SCH-1535
CUSTOM BINARY DOWNLOAD: Yes (1 Counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty bit: 1
BOOTLOADER RP SWREV:1
i think this doesn't look good. WHat should i do to make my phone be working again and not showing that black screen.
I already wiped all data and tried to do that StockROm thing on my computer ODIN and still nothing.
Is my bootloader locked? if so do i need to unlock it to make my phone work again? Thanks so much for your time
Click to expand...
Click to collapse
I dunno if this will work for you. But I had the same message and when I booted in Download mode I just hit Cancel then rebooted and it worked?
If you flashed cyanogenmod, that means you're bootloader is unlocked, which is a good thing.
Can you get into CWM or TWRP? I don't have a samsung so i don't know about ODIN (i presume it's like flashtools for Xperia).
For as long as your phone vibrates (or does pretty much anything when you boot it up) your phone is not hardbricked, which is also good .
Try getting into CWM, shut down your phone completely, wait 5 seconds, then do: Volume Down + Home + Power key . This will get you into bootloader state and try reflashing your old backup, a stock rom or cyanogenmod.
First time with these softbricks is always the most fun ^^. Been there done that, i thought i spend 250 euro's on a phone that was broken .
Btw. Always make a backup for these kind of situations.
Remeax said:
I have a rooted android device samsung galaxy s3 and it was running fine and everything till one day it said to install an update. i accepted it and while it was updating all of a sudden it went to that black screen and says, " system software not authorized by Verizon Wireless has been found on your phone. Please turn off you phone and go to the nearest Verizon Wireless store for help."...
Click to expand...
Click to collapse
You took the 4.3 update. You must now Odin to stock 4.3 to unbrick, do not Odin to any other (previous) version. There is a safe root method.
I do not think there is custom recovery and bootloader is now permalocked.
http://forum.xda-developers.com/showthread.php?t=2270191 has a link to the odin file and the root method in post 2 or 3 i believe.
Ok how do i get it?
afextwin said:
You took the 4.3 update. You must now Odin to stock 4.3 to unbrick, do not Odin to any other (previous) version. There is a safe root method.
I do not think there is custom recovery and bootloader is now permalocked.
http://forum.xda-developers.com/showthread.php?t=2270191 has a link to the odin file and the root method in post 2 or 3 i believe.
Click to expand...
Click to collapse
Ok so is do i do the same thing as i was trying to flash or something like grab a kies file( the ones that take 2+ hours to download) and then flash or get to factory reset with the 4.3 file? if so do you know where i can grab a 4.3 update file to restore? please help me if you have skype or PM me? thanks
afextwin said:
You took the 4.3 update. You must now Odin to stock 4.3 to unbrick, do not Odin to any other (previous) version. There is a safe root method.
I do not think there is custom recovery and bootloader is now permalocked.
http://forum.xda-developers.com/showthread.php?t=2270191 has a link to the odin file and the root method in post 2 or 3 i believe.
Click to expand...
Click to collapse
I just recently ODIN flashed the latest 4.3 stock firmware for my TMO GS3 and then attempted to roll back to 4.1.2. It didn't brick my device, but it didn't work either. I would simply fail to install. I was able to reflash, through ODIN, the 4.3 stock firmware (actually used the root66 version). Then I was able to ODIN flash CWM recovery and install Dandroid 5.1, which is also a 4.3 based ROM. All is well now. I guess I simply can't go back to any previous 4.3 ROMs now, and I'm not sure about any AOSP ROMs. I may give a try at some point to see.

Samsung Galaxy S6 (unlocked) Manual update 5.1.1. UK

Hi, I have a Samsung Galaxy S6 originally on EE and I had it unlocked to 3. I am unable to do an update as via WiFi and I am presented with the following message, "The operating system on your device has been modified in an unauthorised way. Try downloading software updates using Smart Switch on your PC or visit a customer service centre".
I have been told that the unlocking of the phone has resulted in me not being able to use smart switch and that the phone is no longer connected to the Samsung servers.
The build number is LRX22G.G920FXXU1AOCY
I am using Android 5.0.2. at the moment.
If you're rooted you get that message.
Best thing to do is download your current rom again, flash it with odin and that'll restore everything to stock and allow the over the air update to be downloaded. (It doesn't wipe your phone)
Alternately download the latest rom for your model and flash that in odin and it'll update it.
Not that there is no (easy) way to root 5.1.1 without tripping knox.
How do I know if my phone is rooted or not?
Are there any obvious signs that will indicate whether or not the phone is rooted?
If the phone is rooted, where can I find the correct rom for my device and what are the steps to carry out this process?

Hard bricking Galaxy S7

I wrote in separate thread 10 days ago.
I got the rooted Galaxy S7 (SM-G930F) which if I try to boot to recovery gives an error: dm-verity verification need to check drk first.
Then following step by step instructions I installed TWRP.
And flashed custom rom SuperMan-Rom V1.6.5
Rom worked fine until I rebooted the device for the first time. Then I got message:
Code:
Custom Binary Blocked By FRP
Maybe I accidentally turned off OEM unlock in Developer settings, but I honestly don't remember I did that.
And after that I got the hard brick. This is confirmed by @CuBz90 in this thread
So my question is:
1. After the Galaxy S7 is rooted/custom recovery is installed, the DRK is damaged and dm-verity verification will fail if stock rom is installed, right?
2. If user accidentally turn off OEM Unlock the device will be hard bricked, right?
Is that two steps one way ultimate bricking?
I'm asking that because I'm thinking of buying new Galaxy S7 to replace the bricked one, but if hard bricking is that easy, than I'm not really sure I will buy it again.
Dude, try to kill him completly ( nothing on screen ) then send him to warranty, you got nothing to lose.
NeoDJW said:
Dude, try to kill him completly ( nothing on screen ) then send him to warranty, you got nothing to lose.
Click to expand...
Click to collapse
It's not possible since I bought it second hand.
Even if I had a warranty, in my country (Serbia) warranty for smartphones doesn't mean much, I think I could write PhD thesis easier than to make seller replace/fix smartphone with warranty
mss1988 said:
I wrote in separate thread 10 days ago.
I got the rooted Galaxy S7 (SM-G930F) which if I try to boot to recovery gives an error: dm-verity verification need to check drk first.
Then following step by step instructions I installed TWRP.
And flashed custom rom SuperMan-Rom V1.6.5
Rom worked fine until I rebooted the device for the first time. Then I got message:
Code:
Custom Binary Blocked By FRP
Maybe I accidentally turned off OEM unlock in Developer settings, but I honestly don't remember I did that.
And after that I got the hard brick. This is confirmed by @CuBz90 in this thread
So my question is:
1. After the Galaxy S7 is rooted/custom recovery is installed, the DRK is damaged and dm-verity verification will fail if stock rom is installed, right?
2. If user accidentally turn off OEM Unlock the device will be hard bricked, right?
Is that two steps one way ultimate bricking?
I'm asking that because I'm thinking of buying new Galaxy S7 to replace the bricked one, but if hard bricking is that easy, than I'm not really sure I will buy it again.
Click to expand...
Click to collapse
Maybe you can find the solution here:
http://androidforums.com/threads/custom-binary-block-by-frp-lock.977734/
Erik1805 said:
Maybe you can find the solution here:
http://androidforums.com/threads/custom-binary-block-by-frp-lock.977734/
Click to expand...
Click to collapse
Thanks but this will not fix my problem.
Have you tried this: http://pangu.in/frp.error.html
Bright.Light said:
Have you tried this: http://pangu.in/frp.error.html
Click to expand...
Click to collapse
No I didn't but the fact is it will not work.
There is currently no way to fix that. The only way would be to unlock FRP by some box, but it isn't released yet.
What I am asking here is true that Galaxy S7 could be hard bricked that easy? By steps I wrote in my first post.
My questions are partially answered in this article
But I still don't understand what's the problem with dm-variety if I flashed stock rom?
Is there are any other parts of the NAND that are not original/signed and that's why dm-verity fails?
If that's the case can they be backed up then reflashed with the Odin if I get into same problem with new phone?
Thanks
@mss1988 Even if you get message as locked because of FRP, just use Smart switch with Emergency recovery mode and you will get the device back to its original state. This works even if the device is rooted or Twrp'd
harshang2007 said:
@mss1988 Even if you get message as locked because of FRP, just use Smart switch with Emergency recovery mode and you will get the device back to its original state. This works even if the device is rooted or Twrp'd
Click to expand...
Click to collapse
Thanks, but Smart Switch Emergency Recovery is basically the same thing as Kies Firmware update. Which I already tried and that didn't fixed my problem.
mss1988 said:
Thanks, but Smart Switch Emergency Recovery is basically the same thing as Kies Firmware update. Which I already tried and that didn't fixed my problem.
Click to expand...
Click to collapse
@mss1988 I have personally faced this issue on Samsung J7 and J5 and later I had to use Smart Switch's Emergency recovery functionality by enter my Serial number and Device Model Number and Successfully finished flashing the stock ROM. Yes, This works.
harshang2007 said:
@mss1988 I have personally faced this issue on Samsung J7 and J5 and later I had to use Smart Switch's Emergency recovery functionality by enter my Serial number and Device Model Number and Successfully finished flashing the stock ROM. Yes, This works.
Click to expand...
Click to collapse
I don't have the phone anymore to confirm or to deny this. But the whole procedure in Kies and Smart Switch is the same. There are other people with the same problem too in this thread too, and they still didn't found the way to unbrick their devices.
mss1988 said:
I wrote in separate thread 10 days ago.
I got the rooted Galaxy S7 (SM-G930F) which if I try to boot to recovery gives an error: dm-verity verification need to check drk first.
Then following step by step instructions I installed TWRP.
And flashed custom rom SuperMan-Rom V1.6.5
Rom worked fine until I rebooted the device for the first time. Then I got message:
Code:
Custom Binary Blocked By FRP
Maybe I accidentally turned off OEM unlock in Developer settings, but I honestly don't remember I did that.
And after that I got the hard brick. This is confirmed by @CuBz90 in this thread
So my question is:
1. After the Galaxy S7 is rooted/custom recovery is installed, the DRK is damaged and dm-verity verification will fail if stock rom is installed, right?
2. If user accidentally turn off OEM Unlock the device will be hard bricked, right?
Is that two steps one way ultimate bricking?
I'm asking that because I'm thinking of buying new Galaxy S7 to replace the bricked one, but if hard bricking is that easy, than I'm not really sure I will buy it again.
Click to expand...
Click to collapse
I went through this procedure: http://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516 which gives a link to downloading the factory binary (of either version). It reinstated my IMEI which had been turned to a string of zeroes. I will say that when you reboot after flashing the factory binary it's pretty different looking so be prepared for that. I then went to Sammobile and downloaded the appropriate stock ROM for my s7 and flashed that with Odin. I flashed TWRP, formatted internal data when given the opportunity, flashed the no-verity-opt-encrypt.zip, and I was able to use my s7 again. At any rate, you might follow the guide at the link I gave you and see if it helps. As always, no guarantee is given or implied. It's just what I did.
Thanks man, but I can't flash the Factory binary, my FRP is unfortunately ON.
E pa brate nemoj se više onda igrati sa telefonom, nije to za svakoga,...
Mod Edit: Please post in English only:
Well, the brothers do not come then play with the phone, it's not for everyone
now phone detect usb ? i mean adb devices
mss1988 said:
I wrote in separate thread 10 days ago.
I got the rooted Galaxy S7 (SM-G930F) which if I try to boot to recovery gives an error: dm-verity verification need to check drk first.
Then following step by step instructions I installed TWRP.
And flashed custom rom SuperMan-Rom V1.6.5
Rom worked fine until I rebooted the device for the first time. Then I got message:
Code:
Custom Binary Blocked By FRP
Maybe I accidentally turned off OEM unlock in Developer settings, but I honestly don't remember I did that.
And after that I got the hard brick. This is confirmed by @CuBz90 in this thread
So my question is:
1. After the Galaxy S7 is rooted/custom recovery is installed, the DRK is damaged and dm-verity verification will fail if stock rom is installed, right?
2. If user accidentally turn off OEM Unlock the device will be hard bricked, right?
Is that two steps one way ultimate bricking?
I'm asking that because I'm thinking of buying new Galaxy S7 to replace the bricked one, but if hard bricking is that easy, than I'm not really sure I will buy it again.
Click to expand...
Click to collapse
wild guess....
Install dm-verity and force encryption disabler
Wipe Cache
install custom kernel
chandarakk said:
now phone detect usb ? i mean adb devices
Click to expand...
Click to collapse
There's no adb/fastboot access from Samsung recovery or Samsung download mode, as far as I know.
Just get your phone into downloadmode and then flash the stock firmware witch you can find on sammobile. I got also this problem, and then everything will be fine ?
did you try use Kies or Smart swticher to factory restore the phone ?
because as far as i know , even FRP is on , you can still flash stock firmware.
and , try local shop to find any place have z3x box or Octopus box .

Galaxy S6 Edge SoftBrick (DRK)

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't use KNOX after flashing new firmware

i recently tried to root my phone, which it dind't work and broke my phone so i flashed a new firmware on it and my phone worked again but now i wanna use knox but it doesn't work, it keeps saying: Can't install My Knox unautorized software is installed and when i went to samsung's internet app to use secret- mode it dindn't work either.
Can somebody please help me out!
Factory reset, or flash new firmware using CSC instead of HOME_CSC
You've tripped knox, you can't use it ever again, nor can you use s health anymore.

Categories

Resources