Purchased this phone in this condition. It is a US unlocked model SM-N975U1.
When the phone boots the screen immediately goes to locked screen stating "Phone locked: This phone can't be used without authorization (0001)". so I am unable to get into Dev. Options to look at anything.
From searching on here there are not a lot of solutions to get past this and the ones I have found involve flashing the Combo/Eng ROM which is not possible anymore without the Samsung token/permission. And on this phone I can't flash anything because of the KG Locked condition not allowing anything to be flashed. "All binaries are not allowed to be flashed due to KG Locked"
Does anybody know what can be done?
Ready to just swap out the main board and be done with it.
Thanks in advance.
Added pics but the site seems to be having problems showing them.
The only thing I can say to you, is this, problems as the one you are exposing here, always are somewhat unsolvable due to the device having a shady or dubious history, legally obtained devices, are always easy to fix by official channels, you will not get any help to unlock or crack the security of any device here in XDA
Related
Well after almost a week of Googling, I've given up.
My Dad's HTC One M7 seems to be soft bricked (i.e. No OS), and will only enter the fastboot menu. All options therein (factory reset, fastboot), just put the device back in fastboot mode.
I then tried to unlock the device on the HTC site. I got to the final stage (flashing with unlock code, which shows as successful on my computer), and the confirmation screen on my phone does not appear. It is still showing *LOCKED*.
Moving from here the only option seemed to be an RUU, however this only seems to work with S-OFF. My S is most definitely ON. To make it S-OFF, I think I'd need to boot onto an OS and enter debug mode.
I have an OTA file for my carrier which seems to be up to date. Is there any chance this would help?
So I'm sort of chasing my tail here, any help would be appreciated. One possible solution would be if I could possibly unlock a bricked device? (A rare request from what I gather, as most phones are bricked after custom ROMs).
I find it so frustrating that this has happened when I've never even rooted/unlocked the device. I'd never seen the bootloader menu before this.
Any help would be appreciated. Thank you.
Before you do anything to trip the tampered tag, call HTC support. Our Verizon HTC ones should still be in the one year warranty. Tell them you're predicament and you should get a free replacement or repair. HTC in the US has a quick turnaround rate. When my Rezound had the dead vibrate brick issue, I got a new one back within days of shipping my old one.
Sent from my HTC6500LVW using XDA Free mobile app
m7misery said:
Well after almost a week of Googling, I've given up.
My Dad's HTC One M7 seems to be soft bricked (i.e. No OS), and will only enter the fastboot menu. All options therein (factory reset, fastboot), just put the device back in fastboot mode.
I then tried to unlock the device on the HTC site. I got to the final stage (flashing with unlock code, which shows as successful on my computer), and the confirmation screen on my phone does not appear. It is still showing *LOCKED*.
Moving from here the only option seemed to be an RUU, however this only seems to work with S-OFF. My S is most definitely ON. To make it S-OFF, I think I'd need to boot onto an OS and enter debug mode.
I have an OTA file for my carrier which seems to be up to date. Is there any chance this would help?
So I'm sort of chasing my tail here, any help would be appreciated. One possible solution would be if I could possibly unlock a bricked device? (A rare request from what I gather, as most phones are bricked after custom ROMs).
I find it so frustrating that this has happened when I've never even rooted/unlocked the device. I'd never seen the bootloader menu before this.
Any help would be appreciated. Thank you.
Click to expand...
Click to collapse
You should have read the forums about this before attempting to do that. You cannot unlock VZW HTC One through htcdev. You have to use rumrunner or firewater.
Edit - you can get a warranty replacement shipped overnight, but since you pushed that code to the phone they may charge you for a tampered device.
ccarr313 said:
You should have read the forums about this before attempting to do that. You cannot unlock VZW HTC One through htcdev. You have to use rumrunner or firewater.
Edit - you can get a warranty replacement shipped overnight, but since you pushed that code to the phone they may charge you for a tampered device.
Click to expand...
Click to collapse
He never said "tampered" was tripped. In the One section (the section for global and oddball variants) they have sent their phones in even after unlocking and restoring to stock, so simply pushing a code to the phone like many have before will not void warranty. In almost all cases unlocking does not trip the tampered tag. It is what you do after unlocking that trips it (custom recovery, messing with system partition, etc)
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
He never said "tampered" was tripped. In the One section (the section for global and oddball variants) they have sent their phones in even after unlocking and restoring to stock, so simply pushing a code to the phone like many have before will not void warranty. In almost all cases unlocking does not trip the tampered tag. It is what you do after unlocking that trips it (custom recovery, messing with system partition, etc)
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
Verizon has been known to charge you if any modification has been done to the system. Even if tampered is not tripped. If you send it to HTC should be fine. Just a week or two turn around vs overnight air replacement from vzw.
Hi everyone. My device just came back from lg, and apparently I've got a brand new mother board. There is a problem though: my rpmb is gone (fastboot states "no rpmb" right next to the secure boot string), and I guess that is what makes my device fail to unlock its bootloader. Now, doing a little searching on the net, what I get is that really little people also encountered this problem, and ALL of them seem to have sent their device to lg from Italy (as have I). Have I got any chance to fix it? Or maybe just take it back to lg for a check? What could I possibly say to them?
Note that I know pretty well how to unlock bootloaders under normal circumstances, as I have already unlocked many nexus devices of mine in the past, so that is not the problem.
Hey there! I found a solution to get root access, here's my post on Reddit about it:
https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader/
Hope this helps!
Hey all,
Sorry, I know that has been covered extensively on here, but I just want to clarify my understanding and make sure I'm not waiting pointlessly and hopefully avoid mucking this up in the future.
So, I've had my Galaxy S9+ long enough that OEM UNLOCK appeared in the developer options menu. I've rooted/flashed installed enough phones in the past that I stupidly didn't read up on any of the newer security features (such as RMM).
I OEM unlocked the phone, restarted, and everything looked fine. I've then rebooted into Odon (3.13.1, downloaded through Sam Mobile) and tried to install the tar file associated with my phone (twrp-3.2.3-0-star2lte).
Odin failed to install, with the error message, "only official released binaries are allowed to be flashed(recovery)" After a quick look around, this error message appears to be associated with a bootloader that is still locked:
If I look at the values at the top of the download menu, I see
RMM STATE: Prenormal
FRP LOCK: Off
OEM LOCK: Off
So, if my OEM lock is off, is it the RMM state preventing me from flashing the device? If so, is this a wait seven days without restarting the phone for RMM state to change to normal or am I missing something entirely?
What I've also read, is it is required to do the TWRP flash mid-OEM unlock (during the reboot of the factory reset), is this something I will still need to do?
Any direction appreciated. Sorry for posting on the same subject so many others have, I just can't quite find any information on it when the OEM is unlocked already.
ta.
jusx10i said:
Hey all,
Sorry, I know that has been covered extensively on here, but I just want to clarify my understanding and make sure I'm not waiting pointlessly and hopefully avoid mucking this up in the future.
So, I've had my Galaxy S9+ long enough that OEM UNLOCK appeared in the developer options menu. I've rooted/flashed installed enough phones in the past that I stupidly didn't read up on any of the newer security features (such as RMM).
I OEM unlocked the phone, restarted, and everything looked fine. I've then rebooted into Odon (3.13.1, downloaded through Sam Mobile) and tried to install the tar file associated with my phone (twrp-3.2.3-0-star2lte).
Odin failed to install, with the error message, "only official released binaries are allowed to be flashed(recovery)" After a quick look around, this error message appears to be associated with a bootloader that is still locked:
If I look at the values at the top of the download menu, I see
RMM STATE: Prenormal
FRP LOCK: Off
OEM LOCK: Off
So, if my OEM lock is off, is it the RMM state preventing me from flashing the device? If so, is this a wait seven days without restarting the phone for RMM state to change to normal or am I missing something entirely?
What I've also read, is it is required to do the TWRP flash mid-OEM unlock (during the reboot of the factory reset), is this something I will still need to do?
Any direction appreciated. Sorry for posting on the same subject so many others have, I just can't quite find any information on it when the OEM is unlocked already.
ta.
Click to expand...
Click to collapse
I'd love any info on this as well.
Unfortunately, I just had to wait the week.
I will say though when you come to install TWRP make sure you follow the instructions. I didn't, then I had to wait another week for the OEM Unlock to re-appear again!
Hi everyone !
Hope I'm not making any double post but I couldn't find any explanation for this very specific situation.
After thorough research it, it seems that most of samsung devices has a secret setting called "OEM unlock" that we have to use to do the first step of rooting the device. In some cases that setting is missing but can be displayed again by some "date settings" tricks or waiting 7 days. In some other cases which seems to be mine, the "OEM unlock" setting is simply removed by probably the carrier of the phone and can't be reinstated.
In that last case which seems to be mine, I can't find any precise information wether we can or we simply can't unlock bootloader by other way and therefore root the phone.
Could anyone enlighten me ?
Thank you very much in advance !
-sofiann- said:
Hi everyone !
Hope I'm not making any double post but I couldn't find any explanation for this very specific situation.
After thorough research it, it seems that most of samsung devices has a secret setting called "OEM unlock" that we have to use to do the first step of rooting the device. In some cases that setting is missing but can be displayed again by some "date settings" tricks or waiting 7 days. In some other cases which seems to be mine, the "OEM unlock" setting is simply removed by probably the carrier of the phone and can't be reinstated.
In that last case which seems to be mine, I can't find any precise information wether we can or we simply can't unlock bootloader by other way and therefore root the phone.
Could anyone enlighten me ?
Thank you very much in advance !
Click to expand...
Click to collapse
I assume you know that the OEM unlock toggle is in the developer settings? To enable developers settings, tap build number repeatedly until it says you are now a developer. You will need no fancy trick to show it as the lock that hides OEM unlock, only came out in oreo. I don't think carriers disable OEM unlock on Samsung's but I could be wrong. Lastly, if you get it figured out, go over here to the right thread and get it rooted. Good luck! https://forum.xda-developers.com/sa.../how-to-root-twpr-flash-a300fu-a300y-t3494362
SnowFuhrer said:
I assume you know that the OEM unlock toggle is in the developer settings? To enable developers settings, tap build number repeatedly until it says you are now a developer. You will need no fancy trick to show it as the lock that hides OEM unlock, only came out in oreo. I don't think carriers disable OEM unlock on Samsung's but I could be wrong. Lastly, if you get it figured out, go over here to the right thread and get it rooted. Good luck! https://forum.xda-developers.com/sa.../how-to-root-twpr-flash-a300fu-a300y-t3494362
Click to expand...
Click to collapse
Thank you for the answer.
You assume right. I enabled developers settings first, saw that I didn't have OEM unlock option visible, then started to look about this issue. It is quick to see that in many case, even for phone not on OREO (I'm with Marshmallow 6.0.1), this OEM unlock is missing. But based on internet available data, it seems that in most of the case there is a trick to make it visible again. It is a sort of samsung security against thief that hide this option for seven days.
The trick didn't work for me and by looking more I saw that some people seems to be facing the same situation as mine. Some suggest that it is disabled by carrier.
But I couldn't find a solution anywhere for that context.
My question remains.
Here is a more detailed explanation :
from https://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
""There are two kinds of phones in this world: Those that let you unlock your bootloader, and those that don’t.
Whether you’re allowed to unlock your bootloader depends on the manufacturer of your phone, the model you have, and even your carrier. Nexus phones are all unlockable by nature, and many phones from Motorola and HTC allow you to unlock your bootloader through a similar process as the Nexus.
Other phones, however–and some carriers–don’t allow you to unlock your bootloader the official way, which means you have to wait for developers to exploit a security vulnerability if you want to root and flash ROMs. If you have one of those phones, this guide will sadly not help you.
The best way to find out which category your phone falls into is to browse its section at XDA Developers. If you have an HTC or Motorola phone, you may be able too research its unlockability on HTC or Motorola’s website. If it doesn’t support unlocking, you’ll have to use an unofficial unlocking or rooting method, which you’ll usually find on the XDA Developers forums.""
-sofiann- said:
Thank you for the answer.
You assume right. I enabled developers settings first, saw that I didn't have OEM unlock option visible, then started to look about this issue. It is quick to see that in many case, even for phone not on OREO (I'm with Marshmallow 6.0.1), this OEM unlock is missing. But based on internet available data, it seems that in most of the case there is a trick to make it visible again. It is a sort of samsung security against thief that hide this option for seven days.
The trick didn't work for me and by looking more I saw that some people seems to be facing the same situation as mine. Some suggest that it is disabled by carrier.
But I couldn't find a solution anywhere for that context.
My question remains.
Here is a more detailed explanation :
from https://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
""There are two kinds of phones in this world: Those that let you unlock your bootloader, and those that don’t.
Whether you’re allowed to unlock your bootloader depends on the manufacturer of your phone, the model you have, and even your carrier. Nexus phones are all unlockable by nature, and many phones from Motorola and HTC allow you to unlock your bootloader through a similar process as the Nexus.
Other phones, however–and some carriers–don’t allow you to unlock your bootloader the official way, which means you have to wait for developers to exploit a security vulnerability if you want to root and flash ROMs. If you have one of those phones, this guide will sadly not help you.
The best way to find out which category your phone falls into is to browse its section at XDA Developers. If you have an HTC or Motorola phone, you may be able too research its unlockability on HTC or Motorola’s website. If it doesn’t support unlocking, you’ll have to use an unofficial unlocking or rooting method, which you’ll usually find on the XDA Developers forums.""
Click to expand...
Click to collapse
The trick didn't work for you because there is no security thing on marshmallow. What carrier are you on if you don't mind telling? Samsung's aren't bootloader unlocked like other phones.
-sofiann- said:
Hi everyone !
Hope I'm not making any double post but I couldn't find any explanation for this very specific situation.
After thorough research it, it seems that most of samsung devices has a secret setting called "OEM unlock" that we have to use to do the first step of rooting the device. In some cases that setting is missing but can be displayed again by some "date settings" tricks or waiting 7 days. In some other cases which seems to be mine, the "OEM unlock" setting is simply removed by probably the carrier of the phone and can't be reinstated.
In that last case which seems to be mine, I can't find any precise information wether we can or we simply can't unlock bootloader by other way and therefore root the phone.
Could anyone enlighten me ?
Thank you very much in advance !
Click to expand...
Click to collapse
The Galaxy A3 2015 (SM-A300FU) has no OEM unlock as A3 from 2015 don't even have FRP Lock, neither it has RMM state. That means there is no lock which prevents you to flash any custom binaries like TWRP recovery with Odin. You'll only lose access to knox apps/services (because of knox 0x1), rest remains the same.
SnowFuhrer said:
The trick didn't work for you because there is no security thing on marshmallow. What carrier are you on if you don't mind telling? Samsung's aren't bootloader unlocked like other phones.
Click to expand...
Click to collapse
Hi !
About my device, here are details :
Samsung A300FU
Android 6.0.1
BASEBAND VERSION : A300FUXXU1CPH3
Build number : MMB29M.A300FUXXS1CQD5
Carrier was French company called Bouygues.
About bootloader lock or not, I can see on various website that many samsung are bootloader locked but can be unlocked easily by this OEM unlock option. Sometimes it is missing. Two reasons for that : Security check that is removed after 7 days or apparently permanently removed by carrier or geographic area control.
If i'm in that last case, is there any other solution to unlock the boatloader ?Or the phone is just unrootable. It seems strange to me that some phone are just unrootable.
Thanks again !
-sofiann- said:
Hi !
About my device, here are details :
Samsung A300FU
Android 6.0.1
BASEBAND VERSION : A300FUXXU1CPH3
Build number : MMB29M.A300FUXXS1CQD5
Carrier was French company called Bouygues.
About bootloader lock or not, I can see on various website that many samsung are bootloader locked but can be unlocked easily by this OEM unlock option. Sometimes it is missing. Two reasons for that : Security check that is removed after 7 days or apparently permanently removed by carrier or geographic area control.
If i'm in that last case, is there any other solution to unlock the boatloader ?Or the phone is just unrootable. It seems strange to me that some phone are just unrootable.
Thanks again !
Click to expand...
Click to collapse
If you read @prototype74 's post it explains it quite well. I think your bootloader is already unlocked if I read right.
SnowFuhrer said:
If you read @prototype74 's post it explains it quite well. I think your bootloader is already unlocked if I read right.
Click to expand...
Click to collapse
Hi !
Thank you very much both of you for your help. Indeed there was no OEM unlock.
Many posts talking about OEM unlock existing on that A3 and the fact that I couldn't check if it was locked or not using the two methods advised (with adb or with a special code to dial up on the phone interface) led me to stop at that step to be sure before going on.
It is advises not to root a divise with a bootloader locked to avoid bricking it.
Anyway, trusting your input I did the whole process of rooting and putting a custom rom and it's all great !
Hi all,
I have spent over 9 hours trying with ODIN, Offical and unofficial guides, Youtube tutorials and the lot, and I cannot figure this out for the life of me. So I wanted to ask anyone to ease the pain I am currently feeling. I have an international S22 (SM-S901B), and CSC is: "EUX" The option to unlock OEM is not there, yet when I boot into "Download Mode", it states, "OEM Lock: ON(L)", which indicates to me it Perma locked, is there any CSC out there that would give me the option?
In regards to this, I am getting the strangest of errors called, "Cause: Custom binary (VBMETA) blocked due to remaining instalment balance (1)" when I try flashing custom ROM. I am just lost at this point; someone, please give me the strength to resolve this issue.
Greetings, I encountered something similar during a brick I had with an S8 device a few years ago, my OEM toggle option was not available from the start.
https://forum.xda-developers.com/t/...ormal-on-oneui-android-pie-9-0.3911862/page-4 : Check my post at page 4. I noticed that the OEM toggle is only available after some time using the ROM, I don’t remember if it also depends on CNC, give it a try.
Edit : skip the flash firmware part since your bootloader is locked, try doing a factory reset instead, then follow the steps to see if the OEM toggle becomes available.
You owe or some one owes money on the device and payment services are enabled. So Knox guard is keeping the bootloader locked uuntil payment services are paid and released
TheMadScientist said:
You owe or some one owes money on the device and payment services are enabled. So Knox guard is keeping the bootloader locked uuntil payment services are paid and released
Click to expand...
Click to collapse
I already paid for the device in full, do you think I should contact Samsung support about it?