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
Related
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
Hello everyone I am new to this but last night I rooted my phone everything was going well but this morning when I was going through y phone I've decided to turned on OEM lock(I had it off so I was able to root my phone ) but to some rrason I out it back on like a a idiot now my phone is in a brick state where I can't load the is I can use Odin to restore to stock I can't use smart switch to do a emergency back up I am pulling my hair out one hair at a time. I am frustrated and I don't know whatto do please help me I am using the s7 sm-g930w Canadian version for rogers
Did you ever find out what to do? Because I'm in this exact same situation now.
As title said I have the flat SM-G930U because I love being able to switch provider, and so far I'm ok with the phone, but I really do miss my root. I was ecstatic when I saw that root was achieved and bought my unlocked S7 off swappa.
Long story short, every time I try to install the flat G930A eng-boot tar to my G930U through the modded Odin, the phone "WILL" force restart itself soon after booting into the main screen, or even when I leave the screen off. This process is reproducible every time from a stock restored G930U image.
So far I've had to resort to restoring to a stock image to fix the problem so I cannot get to the rooting part yet. Is there any other better method out there? I hate to have to back up and restore my data through cumbersome means like Samsung Switch or Helium.
If you have this G930U model as well, can you share your experience with the rooting process, and/or the experience with the phone so far with root installed?
kawaiichi said:
As title said I have the flat SM-G930U because I love being able to switch provider, and so far I'm ok with the phone, but I really do miss my root. I was ecstatic when I saw that root was achieved and bought my unlocked S7 off swappa.
Long story short, every time I try to install the flat G930A eng-boot tar to my G930U through the modded Odin, the phone "WILL" force restart itself soon after booting into the main screen, or even when I leave the screen off. This process is reproducible every time from a stock restored G930U image.
So far I've had to resort to restoring to a stock image to fix the problem so I cannot get to the rooting part yet. Is there any other better method out there? I hate to have to back up and restore my data through cumbersome means like Samsung Switch or Helium.
If you have this G930U model as well, can you share your experience with the rooting process, and/or the experience with the phone so far with root installed?
Click to expand...
Click to collapse
I think that nobody has yet rooted it, since it just recently came out. The reason why it doesn't work for you, is that the engboot is meant for another model. You'll just have to wait, until the engboot is also released for your model.
I have the exact same problem. SM-G930U reboot loop after loading the engboot. I would love to root this phone if someone can release or locate a compatible bootloader!
Actually, it has been almost a year now. Surely a bootloader for this device is available now? I cannot find it though.
ecm77 said:
I have the exact same problem. SM-G930U reboot loop after loading the engboot. I would love to root this phone if someone can release or locate a compatible bootloader!
Actually, it has been almost a year now. Surely a bootloader for this device is available now? I cannot find it though.
Click to expand...
Click to collapse
Hi
Ask in the right forum , this is for the exynos version your is snapdragon
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
MAX 404 said:
Hi
Ask in the right forum , this is for the exynos version your is snapdragon
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
Click to expand...
Click to collapse
Cool, did not catch that.
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 recently bought a Galaxy S6 (SM-G920A), that has been factory reset and has been Samsung Account locked. I've done a lot of research and can't find a method that works for me to recover the phone.
Most recently, I flashed the combination rom (G920AUCU7ARA1), hoping to maybe achieve something by enabling usb debugging, but I'm not sure where to go from there or if it's even possible.
Also, I can't remember what exact firmware was on the phone before flashing the combination rom but it was on 6.0.1. Is there anyway to find out what firmware I was on? Can I just re-flash any firmware back onto it as long as it's 6.0.1?
Edit: Also, the combination rom is 5.0.2, so could I downgrade that far? I've read something about the bootloader version preventing that but since the combination rom is already this version wouldn't it make sense that I could install the same version of original firmware?
I've spent pretty much every hour I've had off work for the past 3 days trying to figure it out to no avail. Any help would be very much appreciated. Thanks.
I've seen/read multiple times about a bluetooth headset bypass by accessing voice assistant. Can anyone confirm on 6.0.1 G920A?
I should also add that I don't really mind if KNOX is tripped or whatever. There's no warranty anyways and that's all KNOX is for, right?
So, I flashed G920AUCS7ERA2, which is the newest firmware available. For some reason this was the only firmware that would work with odin - I'm guessing because of the bootloader version of the combination file being '7'.
Anyways, bluetooth doesn't work with the emergency call and also talkback isn't available, it's been replaced with voice assistant.
Any way I can downgrade to enable bluetooth or anything that would work? I'm honestly desperate at this point. I'm out $100 for the phone and the pawn shop can't give me the information for the original owner. Am I screwed or can anyone offer any assistance?
I'm willing to pay at this point.
I was able to downgrade to G920AUCU6EQCF. I don't know how but I am now able to enable bluetooth. I bought these, and they don't work. Google doesn't come up. Nothing does. Does it have to be a headset?
try to flash LineAgeOS roms....
Another easy solution can be found here:
[Guide] Unlock FRP / Deactivate Reactivation lock, Root and recovery for Samsung
Lennvy said:
I was able to downgrade to G920AUCU6EQCF. I don't know how but I am now able to enable bluetooth. I bought these, and they don't work. Google doesn't come up. Nothing does. Does it have to be a headset?
Click to expand...
Click to collapse
Try This Trick from XDA