Hello, I have a Note 8 that I have previously rooted a few months ago, then came back to stock OS. I have been wanting to install a custom rom now, but the OEM unlock switch is not in settings despite waiting a week. I rebooted into download mode, and there it shows OEM lock: off, along with RMM: Normal. I attempted to install TWRP to it, but it gets blocked with "Custom binary blocked due to remaining installment payment". I've also noticed that there is a entry in about phone > status that shows "Installment payments: Outstanding". Does that mean I have to pay off my phone fully, or pay the current balance on the carrier account? Does CRHA have the same issue? Or is there a workaround that I don't know off?
Edusa said:
Hello, I have a Note 8 that I have previously rooted a few months ago, then came back to stock OS. I have been wanting to install a custom rom now, but the OEM unlock switch is not in settings despite waiting a week. I rebooted into download mode, and there it shows OEM lock: off, along with RMM: Normal. I attempted to install TWRP to it, but it gets blocked with "Custom binary blocked due to remaining installment payment". I've also noticed that there is a entry in about phone > status that shows "Installment payments: Outstanding". Does that mean I have to pay off my phone fully, or pay the current balance on the carrier account? Does CRHA have the same issue? Or is there a workaround that I don't know off?
Click to expand...
Click to collapse
Not familiar with this message, but just based on the wording alone it sounds like your carrier blocked it until it's paid off. Maybe part of an update somewhere along the way? I would probably phone them for more info and then go from there.
sefrcoko said:
Sounds like your carrier blocked it until it's paid off. Maybe part of an update somewhere along the way? Suggest phoning them for more info.
Click to expand...
Click to collapse
It was only happening in the recent updates when the installment payment showed up in settings, but I doubt the customer service will even know what a bootloader is. Otherwise I would have to wait 2 more years to be able to unlock it, and by then I'll probably have a Note 11 or whatever is out by then. Did the CRHA firmware have that feature?
Edusa said:
It was only happening in the recent updates when the installment payment showed up in settings, but I doubt the customer service will even know what a bootloader is. Otherwise I would have to wait 2 more years to be able to unlock it, and by then I'll probably have a Note 11 or whatever is out by then. Did the CRHA firmware have that feature?
Click to expand...
Click to collapse
Hmm I googled the error message and found a bunch of sites and posts describing the issue. Seems like it's actually another message related to RMM state, which would also explain why you don't see the OEM unlock toggle at the moment. I never had this particular message before, but if I did my next step would likely be trying a factory reset and reflashing latest original stock firmware for the device and seeing if OEM toggle appears in 7 days (or using the date-change trick to speed it up, if that still works). Maybe someone else has other suggestions too.
sefrcoko said:
Hmm I googled the error message and found a bunch of sites and posts describing the issue. Seems like it's actually another message related to RMM state, which would also explain why you don't see the OEM unlock toggle at the moment. I never had this particular message before, but if I did my next step would likely be trying a factory reset and reflashing latest original stock firmware for the device and seeing if OEM toggle appears in 7 days (or using the date-change trick to speed it up, if that still works). Maybe someone else has other suggestions too.
Click to expand...
Click to collapse
I'll try it during the weekend then. Odd that it happens even with a unlocked CSC (BTU)
Same problem
Bought my phone off of Swappa, which they claimed was good.
To date - I have installed 2 different factory firmwares to no avail. Have the same message and same status. Get stuck on Factory Binary screen trying to run combination ROM.
Bought this phone specifically to root and use on AT&T. Glad I paid little more than 1/2 of new...and tried calling Samsung support but they are of no help!
Definitely looking forward to any suggestions on what to do, to help determine what the problem is.
Thanks in advance, as well.
---------- Post added at 09:39 PM ---------- Previous post was at 09:35 PM ----------
sefrcoko said:
Hmm I googled the error message and found a bunch of sites and posts describing the issue. Seems like it's actually another message related to RMM state, which would also explain why you don't see the OEM unlock toggle at the moment. I never had this particular message before, but if I did my next step would likely be trying a factory reset and reflashing latest original stock firmware for the device and seeing if OEM toggle appears in 7 days (or using the date-change trick to speed it up, if that still works). Maybe someone else has other suggestions too.
Click to expand...
Click to collapse
The RMM state is listed as off, not prenormal, which is what I am guessing you are referring to.
Flashing latest firmware takes this to V4 bootloader which may/may not be something OP is interested in.
Might be a bit of a bump
On the Android Pie betas for the Note8, the OEM unlock button shows, and it toggles as expected, and the installment balance entry also does not show anymore in settings. However, it still won't let me flash TWRP or any binary, showing the exact same message as above. Has a fix been found for this issue, or am I stuck unrooted? Could the S10 have the same issue?
Related
DOK2 all stock firmware here.
Got my phone back in december. My phone has been chugging alone fine until yesterday. not sure what happened but the lock screen takes minutes to come back. I tried doing a factory reset via software and when I did that the phone was still sluggish. Tried a stock recovery reset, and afterwards when i tried signing into my account and connecting to wifi at the initial setup the phone just rebooted back to the start screen again which i thought was real odd. It's currently restoring apps from the app store right now and it intermittently reboots itself while doing stuff. all while it's completely stuttering if i try to use it...
Is my phone starting to have internal memory failure? no SD card in the phone at the moment.
Should I try reflashing the DOK2 firmware via odin and then doing a reset again? Is that even possible with all the restrictions?
used it for about 30 minutes on my way to work and then it rebooted on me with the following error :
ddi: mmc_read failed
Check this thread for a workaround. I use an app to keep my phone from going into deep sleep.
http://forum.xda-developers.com/showpost.php?p=64584244&postcount=39
dtrinh4000 said:
used it for about 30 minutes on my way to work and then it rebooted on me with the following error :
ddi: mmc_read failed
Click to expand...
Click to collapse
Wouldn't hurt to reflash stock. Google usually restores apps when you check box at first boot for backup and restore. I'm wondering if you installed an app that doesn't agree with your phone... if so, you may continue seeing this issue so long as app is installed.
Bruce lee roy said:
Wouldn't hurt to reflash stock. Google usually restores apps when you check box at first boot for backup and restore. I'm wondering if you installed an app that doesn't agree with your phone... if so, you may continue seeing this issue so long as app is installed.
Click to expand...
Click to collapse
Did a factory reset and cleared cache, reflashed stock DOK2 from sammobile website using odin, cleared cache. things were going a little bit better at first but now just stuttering all over the place and randomly rebooting still. I only have very few apps downloaded, including facebook updates, instagram, all the samsung and google crap that forces updates...
Also want to add that booting into recovery takes a very long time, longer than i've ever noticed it taking... 7 min+ sometimes it will say "installing system updates" with the android guy chugging along, other times it will just have the android guy chugging....
Is there anything else I can try? Is there something I can test to verify that it's a hardware issue and not a software problem, like a flash memory checker?
This phone is out of warranty, and knox has been tripped so I have very limited options here. Would the Tmobile store let me do an exchange for a fee?
bump... anyone? am i really screwed?
dtrinh4000 said:
bump... anyone? am i really screwed?
Click to expand...
Click to collapse
Sprint user here. I thought it might be a carrier issue, but it would seem It's at least Tmo & Sprint
Can't seem to find any complaints on the Verizon/ATT forums but that doesn't mean it isn't happening.
Could it be Touchwhiz?
Here is the Sprint post:
http://forum.xda-developers.com/note-4-sprint/help/random-shut-freezes-download-mode-stuff-t3302822
cuteman said:
Sprint user here. I thought it might be a carrier issue, but it would seem It's at least Tmo & Sprint
Can't seem to find any complaints on the Verizon/ATT forums but that doesn't mean it isn't happening.
Could it be Touchwhiz?
Here is the Sprint post:
http://forum.xda-developers.com/note-4-sprint/help/random-shut-freezes-download-mode-stuff-t3302822
Click to expand...
Click to collapse
I do get some touch wiz crashes and random app crashes . since I'm on dok2 is there any other rom or recovery I can flash ? Or so some super duper erase method? I'm pretty much ready to cut my losses and sell it for parts on eBay.
i'm not alone it seems
http://forum.xda-developers.com/note-4-tmobile/help/note-4-major-slowdown-bugs-boot-loops-t3311297
http://forum.xda-developers.com/note-4-tmobile/help/looping-screen-t3319204
http://forum.xda-developers.com/note-4-tmobile/help/reboot-shutdown-wont-removing-battery-t3316875
I am having same issue. Was running stock until 3 days ago, when I got fed up with the stock reboot and slow-down. I guess it's time to save up and get a new phone.
Samsung must have activated some self destruct feature on their hardware to get people to upgrade to the galaxy s7 i guess....
dtrinh4000 said:
Samsung must have activated some self destruct feature on their hardware to get people to upgrade to the galaxy s7 i guess....
Click to expand...
Click to collapse
Well, fool me once.... Having spent $800 on a phone that broke in just over a year, hell would have to freeze over before I give Samsung any money again.
Hi, (spent some time searching for answers; if this is covered elsewhere I missed it, sorry)
So, I'm a bit late to the party but I went and found a site still offering Nexus 6 "Factory new" XT1103 unit still in stock after so long, and bought myself one.
(1) I love it, and totally understand why so many people love it
(2) I'm a little concerned in that the bootloader seems to ALREADY be *unlocked*. I certainly didn't do it. Did Google ship these out with the bootloader pre-unlocked? (I tried to google this and found nothing; it strikes me as unlikely). And when booting into the fastboot mode, I don't see any entry saying "secure boot", which bothers me a bit since my Nexus 4 has this (is this deprecated and I missed the news?).
So, I assume that I can just download factory images off Google and flash them myself in order to be sure about my firmware (a little quicker since the bootloader is already unlocked, yeah?). But how do I verify that the bootloader *itself* isn't compromised in any way such that there's no issue with persistent malware, say?
(why yes, people HAVE said that I'm pretty paranoid, why do you ask? Have you been following me around?)
If you download the full firmware image and run the flash-all.bat command, it will overwrite the bootloader and erase everything on the phone. So even if the bootloader were somehow compromised (I really doubt it) this will take care of the problem.
Thanks, I'll do that. On the Google Nexus download page I see both "factory" and "OTA" images - I presume I should use the "factory" image?
I'm really spooked as to WHY the bootloader is unlocked, though, since I certainly did not do it and the box was shrinkwrapped. Does anybody know if anyone else has ever received a Nexus 6 "pre-unlocked"?
New and refurbished units from Motorola did not come shrink-wrapped. In order to open the box you needed to cut the label at the dotted line on the back of the box. Yours could not have been new nor a factory refurb, not just because the box wouldn't have been shrink-wrapped, but also because a refurbished unit would have had the motherboard refurbished so the bootloader status code would be set to 1 (Locked). A previously unlocked bootloader that has been locked would have a status code of 2, with unlocked having a status code of 3.
Strephon Alkhalikoi said:
New and refurbished units from Motorola did not come shrink-wrapped. In order to open the box you needed to cut the label at the dotted line on the back of the box. Yours could not have been new nor a factory refurb, not just because the box wouldn't have been shrink-wrapped, but also because a refurbished unit would have had the motherboard refurbished so the bootloader status code would be set to 1 (Locked). A previously unlocked bootloader that has been locked would have a status code of 2, with unlocked having a status code of 3.
Click to expand...
Click to collapse
...
ok the first time I ever looked, my status code was 3.
I definitely was not the guy who unlocked it.
argggggghhhhhhhhhhh
ok, so would flashing with the full factory image (per the first reply above) be sufficient for me to not have to worry about persistent malware lurking in e.g. a compromised bootloader? I'm not in a position to get a different unit and I'm just really bummed out about this now (especially since I've already logged in with my google account on the phone).
How could I check/verify (some kind of hash) after a full flash that everything is "as it should be"?
weilt said:
...
ok the first time I ever looked, my status code was 3.
I definitely was not the guy who unlocked it.
argggggghhhhhhhhhhh
ok, so would flashing with the full factory image (per the first reply above) be sufficient for me to not have to worry about persistent malware lurking in e.g. a compromised bootloader? I'm not in a position to get a different unit and I'm just really bummed out about this now (especially since I've already logged in with my google account on the phone).
How could I check/verify (some kind of hash) after a full flash that everything is "as it should be"?
Click to expand...
Click to collapse
Simply flash one of the factory images from Google's pages and all your concerns will be eliminated. But, you're being needlessly paranoid regarding the bootloader. All the bootloader does is transfer control from the low level firmware of the device to the Android kernel. Once it does that it sits quietly until the next time you boot. It has no contact with the outside world that I'm aware of so any malware in the bootloader would be useless.
got it, thanks so much for the help!
(I don't know enough about the android bootchain so was envisioning there'd be e.g. enough space allocated for the bootloader such that it would be possible to put in some sort of persistent malware that could be injected into subsequent boots; if it's just a tiny thing (especially if it gets overwritten anyhow when there's a full flash!) then alrighty I'm already safe since I already nuked the firmware twice
I purchased my first Samsung tablet today after a long, loving relationship with Asus Transformers (wanting something smaller). To my surprise OEM Unlocking was not available in Dev Mode. Having not owned a Samsung device since my S5 I searched high and low on Google and nothing worked. Tons of suggestions for S8's/9's but nothing for my new little SM-T380. I tried variations of everything I found and when none of them worked, started back at the top of the list. I FINALLY GOT LUCKY.
TL;DR - Today's date is 12/1/2018, time was 9:32pm (central).
I toggled my date/time to manual.
I manually set my date to 11/1/17. (YES, ONE YEAR AND ONE MONTH EARLIER)
Before wifi had time to reconnect after the date change I manually checked for updates and it errored out.
Without pressing anything else, I held the power button and restarted.
After restart I checked to see if OEM Unlocking was there and it wasn't.
I then adjusted the date back farther to a random interval. (Ended up being 03/1/17)
Manually check for updates again.
Selected dev options on the left again and OEM Unlocking finally appeared!!!!!1
Notes:
SM-T380
7.1.1
ARB3 build
B1G7r33! said:
I purchased my first Samsung tablet today after a long, loving relationship with Asus Transformers (wanting something smaller). To my surprise OEM Unlocking was not available in Dev Mode. Having not owned a Samsung device since my S5 I searched high and low on Google and nothing worked. Tons of suggestions for S8's/9's but nothing for my new little SM-T380. I tried variations of everything I found and when none of them worked, started back at the top of the list. I FINALLY GOT LUCKY.
TL;DR - Today's date is 12/1/2018, time was 9:32pm (central).
I toggled my date/time to manual.
I manually set my date to 11/1/17. (YES, ONE YEAR AND ONE MONTH EARLIER)
Before wifi had time to reconnect after the date change I manually checked for updates and it errored out.
Without pressing anything else, I held the power button and restarted.
After restart I checked to see if OEM Unlocking was there and it wasn't.
I then adjusted the date back farther to a random interval. (Ended up being 03/1/17)
Manually check for updates again.
Selected dev options on the left again and OEM Unlocking finally appeared!!!!!1
Notes:
SM-T380
7.1.1
ARB3 build
Click to expand...
Click to collapse
What's the REAL difference between what you did today and what we did days ago.? Is the same thing we came up with 3 days ago.. Just your version of the same thing..
Three days ago?
This didn't work for me. Neither have any of the other similar date-spoofing methods people have suggested or linked to on this forum. I'd be happy to be wrong, but there doesn't seem to be a legitimate way to trick this tablet into letting you bypass the 7 day wait for OEM Unlock to appear.
@B1G7r33!, if your method actually works, can you replicate the process and prove it? Can you wipe your data, flash back to stock firmware, go to Settings>About tablet>Status, and take a screenshot that shows the "Up time" of the tablet, go through your suggested date-spoofing method, then if OEM Unlock appears, take another screenshot of your tablet's up time, and one screenshot of your developer options menu.
I'm not calling you a liar, it's just that this and similar methods haven't worked for me and haven't been confirmed as working by anyone else yet. If it actually works, then great, but it's not working for me, so I'd like to pinpoint the problem and solve it.
B1G7r33! said:
Three days ago?
Click to expand...
Click to collapse
actually starting on 14th November 2018, 07:17 PM and ending about 4 days ago.. with ptballers solution.
post 118 was the beginnings of it on the thread: https://forum.xda-developers.com/ga...10-02-2018-t3747564/post78159074#post78159074
but even THAT came from earlier works that weren't detailed enough and reconstructed.
the builds seem to be way different here in the solution, i had luck with what we came up with but have only done that once so far.
I am using build NMF26X.T380DXU1ARB3 myself, what about you?
we need to figure out what ptballer is using and everyone else too as we confirm stuff so we know what to do with tablets based upon builds.
seems there is no single solution yet, and that's what we really need too keep confusion cut down to a minimum.
---------- Post added at 06:16 PM ---------- Previous post was at 06:12 PM ----------
Evul1 said:
This didn't work for me. Neither have any of the other similar date-spoofing methods people have suggested or linked to on this forum. I'd be happy to be wrong, but there doesn't seem to be a legitimate way to trick this tablet into letting you bypass the 7 day wait for OEM Unlock to appear.
@B1G7r33!, if your method actually works, can you replicate the process and prove it? Can you wipe your data, flash back to stock firmware, go to Settings>About tablet>Status, and take a screenshot that shows the "Up time" of the tablet, go through your suggested date-spoofing method, then if OEM Unlock appears, take another screenshot of your tablet's up time, and one screenshot of your developer options menu.
I'm not calling you a liar, it's just that this and similar methods haven't worked for me and haven't been confirmed as working by anyone else yet. If it actually works, then great, but it's not working for me, so I'd like to pinpoint the problem and solve it.
Click to expand...
Click to collapse
did you clear out your storage cache after changing the date and then turn on developer options?
what build are you working with btw.
Trying this on round two after root yielded no results. I also tried the clear cache method from your post I found which has a MUCH more consistent process to follow and still got nothing.
Perhaps starting from the bottom would be beneficial here.
Flash stock with odin --> find method that works --> add to root process.
It adds two more steps but that seems like a small price for consistency.
This is f***ing infuriating.
7r33
capriorn1971ad said:
did you clear out your storage cache after changing the date and then turn on developer options?
what build are you working with btw.
Click to expand...
Click to collapse
Yes, I tried that as well and it didn't work. Are you suggesting that this has worked for you? If so, can you reset your tablet right now and try it again to confirm?
I'm using the same build you are using, NMF26X.T380DXU1ARB3
Evul1 said:
Yes, I tried that as well and it didn't work. Are you suggesting that this has worked for you? If so, can you reset your tablet right now and try it again to confirm?
I'm using the same build you are using, NMF26X.T380DXU1ARB3
Click to expand...
Click to collapse
thats quite a bit of work to do, but yes it worked for me.
I was planning on writing a guide on rooting this and what to do if and when it fails in laymans terms and utilizing this, but if it isn't working for everyone.. if it isn't the cache then what is causing it to show for some and not others?
to do the guide i was going to start from a failed installation so i could write part 2 first and finish with part 1 (the actual initial rooting), which would require me to reset the tablet but if this isn't working right.. then i need to hold off on that idea.
maybe i should just do it and spend my day tearing around on that, sounds fun and all but i have to go to Burbank tomorrow to sign up at Central Casting (they are actually looking for someone like me right now, i am going with inside information) and it will be an all day endeavor, tuesday would be much better for me in truth, that allows me to use that tablet while i wait, and i will have hours to wait, but of course with my luck they will call me wednesday and null and void that.
B1G7r33! said:
Trying this on round two after root yielded no results. I also tried the clear cache method from your post I found which has a MUCH more consistent process to follow and still got nothing.
Perhaps starting from the bottom would be beneficial here.
Flash stock with odin --> find method that works --> add to root process.
It adds two more steps but that seems like a small price for consistency.
This is f***ing infuriating.
7r33
Click to expand...
Click to collapse
when you flash stock, restart the device and set the date back 2 months, then do a factory reset AFTER that and it will work.
after rooting it DO NOT reboot it until the OEM unlock shows up again, you can't rely on a method to bypass the second 7 days that requires rebooting, it null and voids the rooting by doing such.
this tablet is awefully touchy, i lost root 2 1/2 weeks after rooting and being able to reboot having OEM unlock showing and all.. but i didn't set up magiskhide..
don't know how the tablet detected it and figured it out..
yes it is infuriating, least you have company to work on it with..
capriorn1971ad said:
thats quite a bit of work to do, but yes it worked for me.
I was planning on writing a guide on rooting this and what to do if and when it fails in laymans terms and utilizing this, but if it isn't working for everyone.. if it isn't the cache then what is causing it to show for some and not others?
to do the guide i was going to start from a failed installation so i could write part 2 first and finish with part 1 (the actual initial rooting), which would require me to reset the tablet but if this isn't working right.. then i need to hold off on that idea.
maybe i should just do it and spend my day tearing around on that, sounds fun and all but i have to go to Burbank tomorrow to sign up at Central Casting (they are actually looking for someone like me right now, i am going with inside information) and it will be an all day endeavor, tuesday would be much better for me in truth, that allows me to use that tablet while i wait, and i will have hours to wait, but of course with my luck they will call me wednesday and null and void that.
Click to expand...
Click to collapse
It shouldn't be that much work at all if your method to get OEM Unlock to display actually works, as your bootloader will then be unlocked and you can immediately re-root, re-flash TWRP, and restore a nandroid backup. Rooting this tablet [flashing TWRP and su and/or magisk and/or a nandroid image] is actually quite simple and can be done in 5 minutes once you have OEM Unlock displayed.
You certainly wouldn't need a whole day just to try this. But I understand. Samsung's security nonsense makes the initial root of this tablet rather fragile if you don't know all the potential roadblocks beforehand. And a comprehensive root guide that explains all of this would certainly help people looking to root this tablet, so I don't want to rush you.
capriorn1971ad said:
when you flash stock, restart the device and set the date back 2 months, then do a factory reset AFTER that and it will work.
after rooting it DO NOT reboot it until the OEM unlock shows up again, you can't rely on a method to bypass the second 7 days that requires rebooting, it null and voids the rooting by doing such.
this tablet is awefully touchy, i lost root 2 1/2 weeks after rooting and being able to reboot having OEM unlock showing and all.. but i didn't set up magiskhide..
don't know how the tablet detected it and figured it out..
yes it is infuriating, least you have company to work on it with..
Click to expand...
Click to collapse
I found out the reboot after root no-no the hard way, lol.
After playing with it all day today, I think you're on the right path with it being application based. If we could log which run before and after, the chances of finding it and being able to adb uninstall/disable would be significantly increased.
So what can be used to low-level log WITHOUT root?
B1G7r33! said:
I found out the reboot after root no-no the hard way, lol.
After playing with it all day today, I think you're on the right path with it being application based. If we could log which run before and after, the chances of finding it and being able to adb uninstall/disable would be significantly increased.
So what can be used to low-level log WITHOUT root?
Click to expand...
Click to collapse
don't think we can really.
trial and error..
thought i was on the right path earlier, but if it didn't work for you then it isn't the solution, cause the solution will work for everyone.
has to be some small thing were overlooking i would assume.
I worked for Metricom through Verso Technologies back in the late 90's, the first coast to coast wireless provider, had dealings with the big wigs and all, but they always opted for less security and more accessibility in most everything pertaining to networking, always afraid to give up backdoors.
i need to go back to what you said too and see what slight differences there are, did you have any luck this time around? was it repeatable?
sucks to know i am going to have to root to cause a failure to try to bypass and root again only to cause a second failure to verify, and to get it right it is going to take that really, the bypass has to be repeatable, i think setting the date back before the systems restore is key to it, but i could be wrong.
if you would lose root and be able to get it pass the first 7 days OEM unlock then your good, because even if you can't get the second, and something goes wrong to where you need it, your gonna have to wipe anyways, which means you just wipe, set date back and then do the factory reset, not being able to reboot afterwards until the OEM unlock appears and not being able to advance it through the last 7 days means little so long as the root is good and right, funny thing really, took me a while to realize that, there is no real need to rush the second 7 days, only the first 7, but it would be nice to be able to reboot it again afterwards, the same day, and not have to worry about it anymore, but like i said earlier, i got detected somehow and lost root still., wish i knew how.
that's alot of my problem though, i do things and try to document them afterwards rather than as, and i am not 20 years old anymore with a mind like a razor, it's just a serrated steak knife now at almost 50, wish i wasn't like that, because i lose bits and pieces as i go.
so if my tablet auto updates to Oreo 8.1 ... then i'm SOL huh?
Hi everyone,
I just bought a Google Pixel 5 with Android 11 that was declared "new" and when I got it, from the first time powering it on, I got the security alert that the bootloader is unlocked, see photo attached. For several personal reasons I cannot easily send it back, so I tried to understand what this means but I am no developer. I tried an entire day to install ADB, put the phone in developer mode and download the firmware image from the official source, I got to the point where the ADB devices command showed the phone as connected but then nothing else worked. In every video or guide online, the steps varied from what I had in front of me, or did not yield the same results, or how the files looked was different (I downloaded the same firmware version that is installed on the phone from the official Google page but never had an image file, just various other very non-descript files in it). As I am pretty clueless, I tried googling my way around the error codes I got but everything I tried didn't work. I either got more error codes, answers like the ADB server is already killed, or that flashing command that just returned something like "waiting for available device" and got stuck on it, or nothing happened at all. Then I figured out that the option in the developer menu "Allow OEM unlocking" is greyed out and I read then that there are phones where you simply cannot lock or unlock the bootloader. However, all online guides I see are from people who have a locked bootloader and want to unlock it, and in my case it's exactly the other way around, it came unlocked and I want to lock it. I also tried a normal reset of the phone from the settings menu, deleting all data, and it didn't work. When I got into fastboot mode, I only could choose between Recovery Mode, Rescue Mode and Restart Bootloader, I tried all of them and none worked, and often the last thing that happened was that the screen turned into a small Android with an open chest, and a line "No command" and the only way to get the phone out of this was by pressing the power button for more than 10 seconds. Every time it restarts, the bootloader unlocked safety advice is showing.
After reading all day long about this, I suspect that the phone was probably refurbished. I wondered whether they maybe accidentally forgot to lock it or whether it was intentional, and in case it was intentional, if there is any way someone would have digital access to the phone. I want to understand if it would be possible for me to keep it without having security issues. I read that the unlocked bootloader is a physical problem, if your phone gets stolen or you physically lose it, someone might hack your PIN easier, or get easier access to your data. However, the PIN code and the standard data encryption also seem to protect my data enough. And tbh, as soon as my phone would be lost or stolen, I would delete all data via Find My Device. So I wondered... if it's impossible for me to lock the bootloader, can I still safely keep the phone and use it, with all standard security apps installed like an anti virus app, Google Play Protect and standard security features like PIN and fingerprint unlock and encryption and be safe, or is there any danger I am not aware of? Or is there any way to enable OEM lock or fix this somehow that I would be able to get done as a non-developer? As mentioned before, sending it back is too difficult at the moment so I am just trying to understand what this bootloader unlocked means for me and if it poses a threat to my security as a normal user? (Watching videos, online banking, emails, sending work-related but not highly data sensitive documents, paying with NFC..)
Thanks in advance! I really appreciate any insights to help me understand what this is, if there is any solution to it or if it actually poses no danger if I secure my data another way.
wehramausi said:
Hi everyone,
I just bought a Google Pixel 5 with Android 11 that was declared "new" and when I got it, from the first time powering it on, I got the security alert that the bootloader is unlocked, see photo attached. For several personal reasons I cannot easily send it back, so I tried to understand what this means but I am no developer. I tried an entire day to install ADB, put the phone in developer mode and download the firmware image from the official source, I got to the point where the ADB devices command showed the phone as connected but then nothing else worked. In every video or guide online, the steps varied from what I had in front of me, or did not yield the same results, or how the files looked was different (I downloaded the same firmware version that is installed on the phone from the official Google page but never had an image file, just various other very non-descript files in it). As I am pretty clueless, I tried googling my way around the error codes I got but everything I tried didn't work. I either got more error codes, answers like the ADB server is already killed, or that flashing command that just returned something like "waiting for available device" and got stuck on it, or nothing happened at all. Then I figured out that the option in the developer menu "Allow OEM unlocking" is greyed out and I read then that there are phones where you simply cannot lock or unlock the bootloader. However, all online guides I see are from people who have a locked bootloader and want to unlock it, and in my case it's exactly the other way around, it came unlocked and I want to lock it. I also tried a normal reset of the phone from the settings menu, deleting all data, and it didn't work. When I got into fastboot mode, I only could choose between Recovery Mode, Rescue Mode and Restart Bootloader, I tried all of them and none worked, and often the last thing that happened was that the screen turned into a small Android with an open chest, and a line "No command" and the only way to get the phone out of this was by pressing the power button for more than 10 seconds. Every time it restarts, the bootloader unlocked safety advice is showing.
After reading all day long about this, I suspect that the phone was probably refurbished. I wondered whether they maybe accidentally forgot to lock it or whether it was intentional, and in case it was intentional, if there is any way someone would have digital access to the phone. I want to understand if it would be possible for me to keep it without having security issues. I read that the unlocked bootloader is a physical problem, if your phone gets stolen or you physically lose it, someone might hack your PIN easier, or get easier access to your data. However, the PIN code and the standard data encryption also seem to protect my data enough. And tbh, as soon as my phone would be lost or stolen, I would delete all data via Find My Device. So I wondered... if it's impossible for me to lock the bootloader, can I still safely keep the phone and use it, with all standard security apps installed like an anti virus app, Google Play Protect and standard security features like PIN and fingerprint unlock and encryption and be safe, or is there any danger I am not aware of? Or is there any way to enable OEM lock or fix this somehow that I would be able to get done as a non-developer? As mentioned before, sending it back is too difficult at the moment so I am just trying to understand what this bootloader unlocked means for me and if it poses a threat to my security as a normal user? (Watching videos, online banking, emails, sending work-related but not highly data sensitive documents, paying with NFC..)
Thanks in advance! I really appreciate any insights to help me understand what this is, if there is any solution to it or if it actually poses no danger if I secure my data another way.
Click to expand...
Click to collapse
When the bootloader is unlocked, "allow oem unlocking" is greyed out.
You use fastboot commands when flashing firmware and locking the bootloader
Code:
fastboot devices
The factory image downloaded from this page includes a script that flashes the device, typically named flash-all.sh (On Windows systems, use flash-all.bat
Click to expand...
Click to collapse
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
fastboot flashing lock
or, for older devices, run:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Click to expand...
Click to collapse
wehramausi said:
Hi everyone,
I just bought a Google Pixel 5 with Android 11 that was declared "new" and when I got it, from the first time powering it on, I got the security alert that the bootloader is unlocked, see photo attached. For several personal reasons I cannot easily send it back, so I tried to understand what this means but I am no developer. I tried an entire day to install ADB, put the phone in developer mode and download the firmware image from the official source, I got to the point where the ADB devices command showed the phone as connected but then nothing else worked. In every video or guide online, the steps varied from what I had in front of me, or did not yield the same results, or how the files looked was different (I downloaded the same firmware version that is installed on the phone from the official Google page but never had an image file, just various other very non-descript files in it). As I am pretty clueless, I tried googling my way around the error codes I got but everything I tried didn't work. I either got more error codes, answers like the ADB server is already killed, or that flashing command that just returned something like "waiting for available device" and got stuck on it, or nothing happened at all. Then I figured out that the option in the developer menu "Allow OEM unlocking" is greyed out and I read then that there are phones where you simply cannot lock or unlock the bootloader. However, all online guides I see are from people who have a locked bootloader and want to unlock it, and in my case it's exactly the other way around, it came unlocked and I want to lock it. I also tried a normal reset of the phone from the settings menu, deleting all data, and it didn't work. When I got into fastboot mode, I only could choose between Recovery Mode, Rescue Mode and Restart Bootloader, I tried all of them and none worked, and often the last thing that happened was that the screen turned into a small Android with an open chest, and a line "No command" and the only way to get the phone out of this was by pressing the power button for more than 10 seconds. Every time it restarts, the bootloader unlocked safety advice is showing.
After reading all day long about this, I suspect that the phone was probably refurbished. I wondered whether they maybe accidentally forgot to lock it or whether it was intentional, and in case it was intentional, if there is any way someone would have digital access to the phone. I want to understand if it would be possible for me to keep it without having security issues. I read that the unlocked bootloader is a physical problem, if your phone gets stolen or you physically lose it, someone might hack your PIN easier, or get easier access to your data. However, the PIN code and the standard data encryption also seem to protect my data enough. And tbh, as soon as my phone would be lost or stolen, I would delete all data via Find My Device. So I wondered... if it's impossible for me to lock the bootloader, can I still safely keep the phone and use it, with all standard security apps installed like an anti virus app, Google Play Protect and standard security features like PIN and fingerprint unlock and encryption and be safe, or is there any danger I am not aware of? Or is there any way to enable OEM lock or fix this somehow that I would be able to get done as a non-developer? As mentioned before, sending it back is too difficult at the moment so I am just trying to understand what this bootloader unlocked means for me and if it poses a threat to my security as a normal user? (Watching videos, online banking, emails, sending work-related but not highly data sensitive documents, paying with NFC..)
Thanks in advance! I really appreciate any insights to help me understand what this is, if there is any solution to it or if it actually poses no danger if I secure my data another way.
Click to expand...
Click to collapse
Trade you for a locked 4a 5g...
sipotek said:
Hey Bro can you share a method that how can I root Google Pixel 5, I tried a lot but i can't update the recovery mode? can you share some simple method like with the help of any Apk, or recovery file.
Click to expand...
Click to collapse
Lots of threads and guides online that show how to root
Looking for help on this one. Every 3-5 days my Ultra gets into a state where no voice can be heard by either myself or the person on the other phone when a call is made or received, but I can hear the ring tone if I'm calling prior to the person answering, and my phone rings as normal if someone calls me. But when answering the call it's just silence on both sides. A reboot fixes this only for it to happen again 3-5 days later, requiring another reboot.
At first I assumed it was a corruption of the rom I had installed, so I flashed back to my stock image with Odin, including a fresh VOD CSC install. Unfortunately, it's still happening after this. Speaking as an engineer, it's unusual but not unheard of for a device to have a hardware issue of this type and it be rectified each and every time with a reboot, that would normally point to a software/firmware error of some sort. However, the fact it's continuing to happen after a completely fresh re-flash of stock Android suggests my worst fears that it is hardware. I could try some things, like not installing Magisk or even re-locking my bootloader, but I don't believe either would be a factor. I only used Magisk for rooting and don't install additional modules. I've also ruled out the sim card or sim slots by swapping to an e-sim, only for it to still happen.
Anyway, any suggestions would be welcome, especially if you have suffered something similar. There is an easy fix, which is to schedule a reboot every morning at around 3am, but I'd sooner not have to do this before working out what the underlying cause is.
I don't have a solution for you but I just wanted to share that I am having the same issue. But I'm not using Magisk and not unlocked, or rooted. The only thing I did was flash stock Samsung and disable some bloat.
I was having the issue the other night (for the second time) when calling my carrier (AT&T) about an order. I just assumed it was them at first. I disabled wifi calling (after them not hearing me several times) then tried again and it worked.
Were you using wifi calling at the time? I haven't been able to reproduce the issue yet so I don't know if disabling wifi calling had anything to do with it working.
Just to clarify, you say you're using Magisk but you're not unlocked or rooted? That isn't possible, but perhaps you just worded it wrong and you meant you're not using Magisk.
Funny you should mention Wifi-Calling, when it happened a few weeks back I force closed Wifi calling in an attempt to track down any potential services that might be causing the problem. And when I did that the calling started working again without a reboot. I thought I'd tracked it down and thought I'd test it again once it happened again a few days later, I would then freeze wifi-calling (something I never use) which would hopefully stop it ever re-occurring. However, the second time I force stopped wifi-calling it didn't fix the issue.
Beefheart said:
Just to clarify, you say you're using Magisk but you're not unlocked or rooted? That isn't possible, but perhaps you just worded it wrong and you meant you're not using Magisk.
Funny you should mention Wifi-Calling, when it happened a few weeks back I force closed Wifi calling in an attempt to track down any potential services that might be causing the problem. And when I did that the calling started working again without a reboot. I thought I'd tracked it down and thought I'd test it again once it happened again a few days later, I would then freeze wifi-calling (something I never use) which would hopefully stop it ever re-occurring. However, the second time I force stopped wifi-calling it didn't fix the issue.
Click to expand...
Click to collapse
I missed a word when I first replied. I added "not" to Magisk but you must have seen it before I fixed it.
I've had many work meetings (on phone) since then and haven't had it pop up. I haven't changed anything and even have wifi calling back on, so I'm at a loss.
OK, traced this to possibly be linked to the attached logcat. Any suggestions?
Also, contrary to my claim in the opening post, the dial tone can only be heard sometimes.
An additional oddity, whilst the fault is occurring (prior to a reboot), voice calls on WhatsApp work fine.
Perhaps a form of modem fault?
I give up on this. I flashed the stock VOD rom in Odin and relocked the bootloader to take it as close to stock as possible (minus the knox flag being tripped which is unavoidable at this point) and it still showed the issue after a couple of days. I've also disabled Bluetooth at a service level to no avail as I thought it might be a glitch with that.
It's clearly a hardware issue that will only be resolved with a logic board replacement. Which currently aren't available.
One good thing is that a full reboot isn't required to fix it, a soft reboot seems to do it. So I've got a link to do that on my home page, only takes 10-15 seconds.
Beefheart said:
OK, traced this to possibly be linked to the attached logcat. Any suggestions?
Also, contrary to my claim in the opening post, the dial tone can only be heard sometimes.
Click to expand...
Click to collapse
Hi, sorry to re-open this old topic. My S21 has the same problem from the beginning, but I have the stock rom. Did you get this log using *#9900# tool? Which log level did you use? Which file is the attached one? BTW, I'm almost sure that it's an hardware failure, did you solve it? Thanks
nrg84 said:
Hi, sorry to re-open this old topic. My S21 has the same problem from the beginning, but I have the stock rom. Did you get this log using *#9900# tool? Which log level did you use? Which file is the attached one? BTW, I'm almost sure that it's an hardware failure, did you solve it? Thanks
Click to expand...
Click to collapse
I'm afraid not, I ended up selling it as parts or repair a few weeks after that post.
Beefheart said:
I'm afraid not, I ended up selling it as parts or repair a few weeks after that post.
Click to expand...
Click to collapse
Thanks anyway, I will try to bring mine to the repair center.