ianmacd
Senior Member
Yes. Everything returns to normal.
The issue is triggered by the unlocking of the bootloader, not by Knox, so there is always a return path for the curious or remorseful user.
Question Unlocking bootloader will disable the camera?
- Thread starter 白い熊
- Start date
The issue is triggered by the unlocking of the bootloader, not by Knox, so there is always a return path for the curious or remorseful user.
I'm trying to relock the bootloader, but i'm having some trouble with it. Could you tell me how you did it?
When I boot to bootloader it just reboots and when I get to recovery and choose go back to bootloader it just reboots too. Faastboot doesn't detect the device.
When I boot to bootloader it just reboots and when I get to recovery and choose go back to bootloader it just reboots too. Faastboot doesn't detect the device.
I'm not remorseful — but I've never even considered this: I'm rooted now, can I lock the bootloader keeping root etc and just use it like this, with root?
This might be missing the obvious — but I've always thought once rooted and not wishing to go back to factory it must stay unlocked.
If so, also how do you lock it? Toggle the OEM lock in Developer options back and then upon reboot to Download mode go through some special key sequence?
Will the camera somehow work is anyone managed to stick a custom ROM on it? Or is the disable of the camera intergrated into the bones (hardware) of the phone?
ianmacd
Senior Member
Just boot to download mode with the device connected over USB to a computer, then long-press Vol Up to get to Unlock mode, and give one more press of Vol Up to relock the bootloader. The device will reset and the camera will work again afterwards.
ianmacd
Senior Member
If you have rooted the device, you cannot simply relock the bootloader. You are correct about that. If you try, the device will detect the changes you have made and refuse all service until you reflash it with stock firmware.
If you ever do want to relock it, you simply return to Unlock mode from download mode and press Vol Up again. This is what I do before I hand a device down to another family member.
This issue got some attraction. Article’s on tech sites and a post on reddit. Do you guys think Samsung would ever consider to revert this back? I got so excited for the Fold 3 and now I’m thinking of canceling my order. @ianmacd is there anything we can do to help you figure this out? I’m really wondering if time will fix this or not. Samsung voids our warranty after Knox being tripped is that not enough? I don’t want to change oem‘s I want to stay with Samsung but this is too much.
And then there are these morons that comment „why would you even need to root?“ or „I didn’ root since the S3 days!“ good for you. Just stfu some people clearly still value the benefits of root access.
And then there are these morons that comment „why would you even need to root?“ or „I didn’ root since the S3 days!“ good for you. Just stfu some people clearly still value the benefits of root access.
I haven’t upgraded yet, still on the 2, but I Hate them for this. genuinely hate them and I rarely feel that deeply about a phone company, but I’m tired of them and every one of them ****ing with our purchases. This is such an insanely **** move that my head hurts..how you know it’s them being dicks is because the damn thing can b3 reversed if you play by their rules..I’m going back to the Notes, maybe a 10+ 5G.
It has come to my attention that on another forum, an user has reported camera lockout in his S20.
He says he got the update this morning and was unable to deny it.
Please be wary of updating.
It may be good to spin S20 discussion off onto another thread.
He says he got the update this morning and was unable to deny it.
Please be wary of updating.
It may be good to spin S20 discussion off onto another thread.
You can always disable OTA updates or clear the system cache to purge the download (haven't tested this though).
The first thing I do is disable updates. If I really want a particular update, only then.
Android 10 and above, NO.
Updates will eventually destroy the usability of the phone especially with carrier variants.
My 10+ is still running strong on Pie, zero issues.
Current OS load is over a year old, still fast and very stable with very little maintenance.
Rather agree on your "skipping updates" statement. I have a J7 Prime and it has been on a Nougat based stock ROM for 4 years now.
Very stable. I like it a lot.
kingwicked
Senior Member
im a Note 20 Ultra 5G ,A51 and Tab S7 4G user. this doesnt look good unless someone makes a magisk module or a fix to resolve it. Im neither updating these devices anymore or buying any Samsung device till then.
Certainly. I have an A51, so I'm worried too.
Thankfully I have AFWall+, so it's unlikely the phone will be updating without my awareness.
kingwicked
Senior Member
well thankfully i have magisk on all three devices so they wont update without me doing it manually
Top Liked Posts
-
There are no posts matching your filters.
-
24
Yes, my Fold3 (F926B) arrived yesterday and I unlocked its bootloader this afternoon.
I can confirm that all cameras stop working afterwards. This means that facial recognition also fails. Anything that uses any of the cameras will fail.
I tried installing a third-party camera app, but this also failed. I took a logcat of the failure:
Code:07-12 13:50:51.413 1384 31574 W ServiceManager: Permission failure: android.permission.CAMERA_OPEN_CLOSE_LISTENER from uid=10291 pid=8927 07-12 13:50:51.413 1384 31574 D CameraService: CameraDeviceState for CameraManager 07-12 13:50:51.413 8927 9780 I CameraManagerGlobal: Camera 0 facing CAMERA_FACING_BACK state now CAMERA_STATE_CLOSED for client net.sourceforge.opencamera API Level 1 07-12 13:50:51.413 8927 9780 I CameraManagerGlobal: Camera 1 facing CAMERA_FACING_FRONT state now CAMERA_STATE_CLOSED for client android.system API Level 2 07-12 13:50:51.413 8927 9780 I CameraManagerGlobal: Camera 2 facing CAMERA_FACING_BACK state now CAMERA_STATE_CLOSED for client android.system API Level 2 07-12 13:50:51.414 8927 9780 I CameraManagerGlobal: Camera 20 facing CAMERA_FACING_BACK state now CAMERA_STATE_CLOSED for client android.system API Level 2 07-12 13:50:51.414 8927 9780 I CameraManagerGlobal: Camera 21 facing CAMERA_FACING_BACK state now CAMERA_STATE_CLOSED for client android.system API Level 2 07-12 13:50:51.414 8927 9780 I CameraManagerGlobal: Camera 23 facing CAMERA_FACING_BACK state now CAMERA_STATE_CLOSED for client android.system API Level 2 07-12 13:50:51.414 8927 9780 I CameraManagerGlobal: Camera 3 facing CAMERA_FACING_FRONT state now CAMERA_STATE_CLOSED for client android.system API Level 2 07-12 13:50:51.414 8927 9780 I CameraManagerGlobal: Camera 4 facing CAMERA_FACING_FRONT state now CAMERA_STATE_CLOSED for client android.system API Level 2 07-12 13:50:51.414 8927 9780 I CameraManagerGlobal: Camera 52 facing CAMERA_FACING_BACK state now CAMERA_STATE_CLOSED for client android.system API Level 2 07-12 13:50:51.414 8927 9780 I CameraManagerGlobal: Camera 71 facing CAMERA_FACING_FRONT state now CAMERA_STATE_CLOSED for client android.system API Level 2 07-12 13:50:51.414 8927 9780 I CameraManagerGlobal: Camera 73 facing CAMERA_FACING_FRONT state now CAMERA_STATE_CLOSED for client android.system API Level 2 07-12 13:50:51.414 8927 9780 I CameraManagerGlobal: Camera 91 facing CAMERA_FACING_FRONT state now CAMERA_STATE_CLOSED for client android.system API Level 2 07-12 13:50:51.415 1384 31574 D CameraService: getNumberOfCameras E 07-12 13:50:51.416 1384 31574 W ServiceManager: Permission failure: android.permission.SYSTEM_CAMERA from uid=10291 pid=8927 07-12 13:50:51.416 1384 31574 D CameraService: getNumberOfCameras X: ok 07-12 13:50:51.416 1384 31574 D CameraService: getNumberOfCameras E 07-12 13:50:51.416 1384 31574 W ServiceManager: Permission failure: android.permission.SYSTEM_CAMERA from uid=10291 pid=8927 07-12 13:50:51.416 1384 31574 D CameraService: getNumberOfCameras X: ok 07-12 13:50:51.416 1384 31574 D CameraService: getCameraInfo E: 0
At a glance, I'm confident that this can be fixed using Magisk (i.e. root), but I can't rule out the camera having been disabled in other ways, too. The situation may not be recoverable.
After relocking the bootloader, the camera works again.
It's really obnoxious of Samsung to do this, and I am in two minds now about keeping the device and working on a fix for the issue, or simply returning the unit in disgust. This is the kind of practice I expect from Apple, and I always tell Apple users to vote with their wallet when confronted with such anti-consumer practices.10Apologies that we haven't really been updating every step along the way the last few days! Joined a telegram group with other devs for fold 3 issues, which now is mostly about the camera, and just kind of been updating each other in the group.
But we did stumble upon 2 odd things today.
1 - the newest bootloader force closes the camera app and causes the phone to restart, where the original one just gives you an error message when you try to use the camera.
2 - when you do try to use the camera, the lens does try to focus, meaning that the drivers and libraries are all loaded up and working properly. And it takes a few seconds for the camera app to say the camera isn't working (because another thread is opened when calling for the camera to the isp to display what the camera sees which takes a moment.)
Both of those are kind of contradictory.
(the rest of this comment is purely my opinion and doesn't explicitly represent the opinions of the rest of the dev group)
The first implies that the actual bootloader impliments the lockout, whereas the second infers that it's software related.
I potentially think a couple options as to what might be going on.
1 - going with the simplest idea that should have been checked first, it could be as simple as SafetyNet Attestation built into the camera app that checks if the BL is unlocked right after starting the camera, which would explain the breif delay. So I'm going to check that tomorrow.
2 - using the camera contexts, you can shut down the isp after the phone has booted as there is a couple of Contexts in the kernel talking about it. Shutting down the isp itself would stop the camera from being able to process and display what the camera sees (explains why opening the app takes a few seconds of black screen to say it doesn't work)
3 - I know there was a 3, but my brain is fried as I'm about to go go bed so I'll edit-updates tomorrow when I am awake and back at my computer.
However, this doesn't exactly explain why the new bootloader causes a force close and then phone reboot unless Samsung either messed up code somewhere in the new BL, or did it intentionally to create more frustration. Nor does it say how.
We are all working very hard on this and working from different angles to try to cover as much ground as possible. Ivan said he had a possible fix, but he's been Mia for a week and no one has been able to get ahold of him so we can't rely on that right now!8Just to update since it's been a while.
I have not been able to do a lot with this recently. The team has been working on it, but I have had numerous situations pull me away. Busy season for business since it's starting to get cold so I've been working nonstop. In the process of hiring more people so I can have more free time.
Really debating doing a few things that I can't talk publicly about atm in order to get more Intel on the camera.
I do apologize about the lackluster update because I know a lot of people are really looking forward to this8
If you try to relock the bootloader with an unsigned firmware, it will brick your phone and you'd have to use Odin to flash factory firmware to fix it.
I'm getting close to finding solutions, just hang tight.
Still have half of our kernel code to go through. But I found the camera drivers and source code, which helps me know what to look for7So I'm not an android developer (been using Linux for 29 years though) and I do not yet have this phone but am planning on it. Still using rooted Note 8.
Question - did any of you look at this from a different perspective - like what actions happen when you unlock the bootloader? If you can find the instructions that are executed when you "flip that switch" you can see the command that they are running to disable the cameras. I don't know if you can do strings searches for whatever the message is that is shown when you unlock the BL on the phone, but you should be able to download most of the software from / to your PC and search from there. Maybe they're are doing something like a linux module blacklist. I don't know where Android keeps the files like modules.conf (I'll search my rooted Note8 later) but that could be a possibility.
Are there tools in Android where you can closely monitor when new jobs start to maybe see what happens when the BL is unlocked? If so, then maybe you can upload 'strace' and repeat the process to see what is executed.
I figure for them to be able to change your phone on the fly that quickly, AND to put it back once the BL is locked (assuming no flashes) it has to be something like a command or a module. Since it also looks to see if anything was flashed I'm leaning towards a program, although if these things still run dm-verity then a command might not be necessary since flashes should be seen on boot.
If it's a command it could be a new one. Maybe if someone has the earlier Fold (rooted) they could do a "ls -latR /" and someone could do the same on the Fold 3 - then do a diff to see what new commands show up.
Then again - maybe I'm just too familiar with Linux and there are too many differences with Android. Hopefully this at least helps spur thought.
