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 .
Related
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.
Hi,
I am using samsung galaxy S5 SM-G900R7, i am able to root this phone then started trying flashing of custom boot.img contating custom zImage. ODIN is showing successful flashing , but when i am restarting its always going in download mode with error message "couldn't do normal boot" . In download mode there is a line "QUALOCM SECUREBOOT : ENABLE". I doubt this is beacuse of locked bootloader.
I want to know is it really beacuse of locked bootloader?
I downloaded kernel for my phone model from samsung official website mentioned below and built in same way they have given instruction, so i ahve less doubt on custom zImage.
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=900r7
if yes then i have second question is it unlockable or not, i am not getting any unlocking method for samsung galaxy S5. whatever info i am getting regarding unlocking is upto galaxy S3 but not helpful for galaxy S5. PLease help me to come to a final conclusion on flashing custom zImage to phone.
arvind3023 said:
Hi,
I am using samsung galaxy S5 SM-G900R7, i am able to root this phone then started trying flashing of custom boot.img contating custom zImage. ODIN is showing successful flashing , but when i am restarting its always going in download mode with error message "couldn't do normal boot" . In download mode there is a line "QUALOCM SECUREBOOT : ENABLE". I doubt this is beacuse of locked bootloader.
I want to know is it really beacuse of locked bootloader?
I downloaded kernel for my phone model from samsung official website mentioned below and built in same way they have given instruction, so i ahve less doubt on custom zImage.
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=900r7
if yes then i have second question is it unlockable or not, i am not getting any unlocking method for samsung galaxy S5. whatever info i am getting regarding unlocking is upto galaxy S3 but not helpful for galaxy S5. PLease help me to come to a final conclusion on flashing custom zImage to phone.
Click to expand...
Click to collapse
As far as I'm aware most Samsung devices if not all have unlocked bootloaders, as for a soloution I haven't seen anything really but some say you need to re-flash stock then try from scrath or make a backup after reflashing stock and a custom recovery then format and restore to get it working.
TechMinerUK said:
As far as I'm aware most Samsung devices if not all have unlocked bootloaders, as for a soloution I haven't seen anything really but some say you need to re-flash stock then try from scrath or make a backup after reflashing stock and a custom recovery then format and restore to get it working.
Click to expand...
Click to collapse
Thanks a lot for your reply,
I searched regarding this and i found latest samsungs are coming with KNOX security in which SECUREBOOT is there, which doesn't allow phone to boot with any boot image if chacksum value doesn't match. so i feel even if bootloader is not locked here but same thng KNOX security is doing. Help me if you have any idea how to disable it in samsung galaxy S5. Getting way how to disable in previous series but not finding method how to do for galaxy S5.
arvind3023 said:
Thanks a lot for your reply,
I searched regarding this and i found latest samsungs are coming with KNOX security in which SECUREBOOT is there, which doesn't allow phone to boot with any boot image if chacksum value doesn't match. so i feel even if bootloader is not locked here but same thng KNOX security is doing. Help me if you have any idea how to disable it in samsung galaxy S5. Getting way how to disable in previous series but not finding method how to do for galaxy S5.
Click to expand...
Click to collapse
Looks like getting rid of KNOX is a difficult task but not impossible: http://www.s4miniarchive.com/2013/12/how-to-remove-knox-bootloader-from-new.html
TechMinerUK said:
Looks like getting rid of KNOX is a difficult task but not impossible: http://www.s4miniarchive.com/2013/12/how-to-remove-knox-bootloader-from-new.html
Click to expand...
Click to collapse
Thanks for your reply,
I think your post brought me closer to soltution. Tommorw i have to try this. The only problem now i have that i am not getting firmware for my phone model SM-900R7, I am getting firmware for model number SM-900R6 which is very close to this not not exactly for SM-900R7. I have to search more to get it, i hope i will be able to find it.
Thanks again for your valuable post.
arvind3023 said:
Thanks for your reply,
I think your post brought me closer to soltution. Tommorw i have to try this. The only problem now i have that i am not getting firmware for my phone model SM-900R7, I am getting firmware for model number SM-900R6 which is very close to this not not exactly for SM-900R7. I have to search more to get it, i hope i will be able to find it.
Thanks again for your valuable post.
Click to expand...
Click to collapse
No problem, good luck with removing KNOX
TechMinerUK said:
No problem, good luck with removing KNOX
Click to expand...
Click to collapse
Hi,
Yesterday night you posted a link, that link was good but still my requirement is different.Yesterday i was not able to go through whole link you provided to me, today i was reading the whole article. its looks like they are trying to save warrany of phone even after flashing custom ROM. They are deleting bootloader contents of flashing ROM, even i will flash custom ROM with deleted bootloader contents, In phone bootloader will remain same with KNOX SECUREBOOT feature. My target is to flash with KNOX disabled bootloader so it will not stop booting with custom zImage.
TechMinerUK said:
No problem, good luck with removing KNOX
Click to expand...
Click to collapse
Actaully that link was removing KNOX from firmware which you are going to flash not from phone if you have already KNOX is there. That is for if your mobile is not having KNOX and you dont want KNOX when you are going to flash with recent updated firmware so you can delete KNOX contents from firmware and can flash.
arvind3023 said:
Actaully that link was removing KNOX from firmware which you are going to flash not from phone if you have already KNOX is there. That is for if your mobile is not having KNOX and you dont want KNOX when you are going to flash with recent updated firmware so you can delete KNOX contents from firmware and can flash.
Click to expand...
Click to collapse
Hmm, it appears it not possible due to it having a locked bootloader/KNOX not being removable
http://forum.xda-developers.com/verizon-galaxy-s5/help/g900r7-problem-t2877527
TechMinerUK said:
Hmm, it appears it not possible due to it having a locked bootloader/KNOX not being removable
http://forum.xda-developers.com/verizon-galaxy-s5/help/g900r7-problem-t2877527
Click to expand...
Click to collapse
Thats my problem is i am not getting concrete answer either some good link or something official from samsung to come to conclusion of NO, searching searching trying this and that with a hope that its possible.
arvind3023 said:
Thats my problem is i am not getting concrete answer either some good link or something official from samsung to come to conclusion of NO, searching searching trying this and that with a hope that its possible.
Click to expand...
Click to collapse
I would pressume their will be some method of doing it and if it's not released yet it will be soon...
I guess it's just best to bide time and wait untill a concrete method has been developed
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
Well, this is my story. I tried to revive my old Verizon SIII because I really like that model. The problem is I never noticed the 4.4 bootloader lock. I rooted my device after a factory reset, I tried to install the cyanogenmod but at the start the custon recovery wont trigger despite installing the adequate app, first I believed KNOX was the issue so I proceeded to unistall it with TitanimBackup, that made the "custom" Samsung boot screen appear but then a "Unauthorized sofware blah blah blah" message from Verizon appeared so I used download mode to reboot sucessfully, then I remembered that the bootloader wasnt unlocked so I proceeded to unlocked with EZunlocker and the unlock was successful, when the TWRP manager app asked me to reboot to install the custom recovery it never did, just bricked. My questions are, my phone was already running a form of custom rom for region-free SIM card operation, as far I know the device was NOT on 4.4 since it wasn't even on the US anymore and Verizon update services don't operate here, as I remember my sytem version was 4.0.4 why did it bricked? if I buy another device what I must check to avoid another bricking? Is there any way to recover my device? it is a hard brick, noob here.
I have a Samsung S7 edge I need to Google unlock I tried to download Odin to my SD card then install it but nothing works Please help.
Also can I network unlock a icon 3 by cricket and how
CALI_SAVAGE said:
I have a Samsung S7 edge I need to Google unlock I tried to download Odin to my SD card then install it but nothing works Please help.
Also can I network unlock a icon 3 by cricket and how
Click to expand...
Click to collapse
Odin runs on a PC under Windows. (Saying you downloaded it to an SD card made me think you were trying to run it on your tablet.)
Try to use the Search function on the site. There's probably a thread on rooting the S7 Edge. There's definitely a thread on Magisk.
Here are the Magisk installation instructions.
Don't start with "I don't know anything, somebody tell me how." Read a lot of posts, at least learn some words.
Was I wrong to assume you want to root your tablet? What made you decide you wanted Odin? What is stopping you from Googling "unlock"?
Before you do anything destructive, find and download a copy of your current ROM, so you'll be in a position to recover. You can test burning a ROM without unlocking the bootloader, as long as it is an official Samsung-packaged ROM.
Good luck.
CALI_SAVAGE said:
I have a Samsung S7 edge I need to Google unlock I tried to download Odin to my SD card then install it but nothing works Please help.
Also can I network unlock a icon 3 by cricket and how
Click to expand...
Click to collapse
Hi and welcome to the xda family.
As J.Michael mentioned, you will have better help in the S7 threads.
[xdaForum] - Samsung Galaxy S7
Cheers.
J.Michael said:
Odin runs on a PC under Windows. (Saying you downloaded it to an SD card made me think you were trying to run it on your tablet.)
Try to use the Search function on the site. There's probably a thread on rooting the S7 Edge. There's definitely a thread on Magisk.
Here are the Magisk installation instructions.
Don't start with "I don't know anything, somebody tell me how." Read a lot of posts, at least learn some words.
Was I wrong to assume you want to root your tablet? What made you decide you wanted Odin? What is stopping you from Googling "unlock"?
Before you do anything destructive, find and download a copy of your current ROM, so you'll be in a position to recover. You can test burning a ROM without unlocking the bootloader, as long as it is an official Samsung-packaged ROM.
Good luck.
Click to expand...
Click to collapse
I am trying to run Odin on my galaxy 7 edge
CALI_SAVAGE said:
I am trying to run Odin on my galaxy 7 edge
Click to expand...
Click to collapse
Well, you can't. Odin is an IBM PC program that runs under Windows. It is used to ship ROM files to a Samsung tablet. The tablet must be in "download mode".
J.Michael said:
Well, you can't. Odin is an IBM PC program that runs under Windows. It is used to ship ROM files to a Samsung tablet. The tablet must be in "download mode".
Click to expand...
Click to collapse
Then how do I beat Google lockon my Samsung 7 edge cause I can't do it
CALI_SAVAGE said:
Then how do I beat Google lockon my Samsung 7 edge cause I can't do it
Click to expand...
Click to collapse
Find the S7 Edge forum for help unlocking.
Odin is not part of unlocking. Odin is for downloading software to the device. I think you can use Odin without unlocking -- you will only be able to flash images. You could try flashing a stock image for a different language, just to see if it works. (Pick a language you think you will understand well enough to see how to change the language back to your preferred language.)
A separate step, with no reference to Odin, is unlocking. I think it is usually delete any Google account you have attached to the device, enable Developer Options, enable "bootloader unlock" in Developer Options, reboot to recovery or download mode (I'm not sure which), expect some message like "hit Volume Down to unlock" (could be Volume Up), accept that it will wipe data.
Once you are unlocked (verify by booting Android again, and checking the Developer Options to see if the "unlock bootloader" option is still enabled, but is now greyed out), you can try using Odin to download non-stock software. In particular, it is at this point that you might try to flash a Magisk-patched software to try to install Magisk. With Samsung, as of when I did it, installing Magisk will again require wiping data, so do not spend a lot of time configuring your device between unlocking the bootloader and installing Magisk.
one can't bypass FRP lock on Samsung devices. what you try with Odin3 is impossible, it won't reset FRP.
find another method for that model, there exist some cheats on YouTube
Pixel 3a - How to bypass FRP?
Hello, I've tried all of the Youtube instruction videos and they never work for me. I got this phone from my now deceased Grandma and I want to use it as a secondary camera. I tried her email I had for her and everything, but nothing works. I...
forum.xda-developers.com