windows – Unlock GPO enabled “Lock all taskbars” on one PC

I am facing strange problem here. We have GPO that disables “Lock all taskbar” function in Windows 10. One user somehow managed to resize the taskbar and I want to fix this but its giving me a headache because I don’t want to disable this policy for all domain users so I was thinking if there is an option to disable this policy as local gpo. Looks like it’s not working so I tried a lot different methods – searching for a register to disable this policy didn’t work as well because I just cannot edit the registry found in here:
HKEY_CURRENT_USERSOFTWAREMicrosoftWindowsCurrentVersionPoliciesExplorer called LockTheTaskbarand it returns me an error *Error writing the value's new contents*
I am feeling a bit desperate about this problem what seems not a really like a big problem.

I tried easy way of course just to place this PC in OU where this policy excludes. Did a force gpupdate, multiple times restarted machine and no updates. I can confirm that this machine is in our network

rom flashing – Samsung bootloader unlock but failed to flash custom rom

I go to Settings > About Phone > Software Information then tap the Build number 7 times to enable Developer Options.

Then I connected my device to the internet and go to Settings > Developer Options > OEM Unlocking set to Enabled to unlock the Bootloader, (the phone is reset to data factory but the OEM Unlocked says it’s already enabled after that).

Now I want to flash a custom ROM, but I failed to do so and the error in download mode says Only official binaries are allowed to be flashed. I think this is somehow related to Bootloader which is not fully unlocked. Is there anything I should do before flashing custom ROM?

I’m actually trying to root my device and I’m following this tutorial.

DEVICE INFORMATION:

Samsung Galaxy J6 (2018)
SM-J600G/DS
Android 10
Android Patch is Feb. 1, 2021

lock screens – Unlock phone with adb without text or keyevent input


Your privacy


By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.




disk encryption – Is it secure to automatically unlock encrypted system drive using the TPM PCR values?

A simple way of automatically decrypting system drive at boot time:

clevis luks bind -d /dev/yourdrive tpm2 '{"pcr_ids":"4,5"}'

systemctl enable clevis-luks-askpass.path

When I booted another OS on the same machine, tpm2_pcrread listed mostly identical PCR values, except for 4 and 5. I understand that PCR 4 is a hash of the MBR and partitioning data, and PCR 5 is generated by the code in MBR. Besides, it’s an EFI system.
If an attacker makes a copy of the entire disk, can he generate the PCR 4 value by hashing the stolen MBR and partitioning data?

Trying to unlock & access a password locked Android cell phone that has screen damage on a small section so I can’t input the last # of password

I’ve tried going around the password with some of those programs they have advertised, where they claim it will eliminate the password requirement and get you right into your Android device. What I don’t quite understand is what were they thinking of when in the procedures, one of the steps will involve changing the settings in the locked Android (e.g. Debugging must be on, or load this program onto the locked Android….) Did someone actually go through some of these processes before releasing program? I mean, how are you supposed to get into the settings of a phone you’re locked out of, or let alone, load a program or app onto the android you’re trying to unlock? I wanna see that happen.

So anyway, I have an android cell phone, I dropped it, screen cracked and part of the screen has no capacity to input anything, it’s like a dead area; screen works there, but no touch entry.

Is there any way of eliminating the passcode step, get into it, and load it up with mirror app to view and control the device? And, getting another device to recognize the locked device via USB wire connect.

I want to unlock my Byju’S Samsung galaxy a7 tablet

I have tried so many things but doesn’t work.

  1. I press power button for few minutes but it’s only have 2 options power off and restart button. Even I press power off icon for few minutes but nothing appears.
  2. I connected my tab to PC and when I open galaxy files it’s empty.
  3. I tried to go through with settings but it is also locked by sure lock…. scalefusion … And mobilock…

Finally I delete surelock app but nothing happen.

I want to unlock my tab without deleting any data.

adb – Why is suggested to OEM unlock when LinageOS can be installed without it

I have a “LENOVO Tab 2 A10-30” which got frozen after the update in the startup loop – did not start after displaying the Lenovo logo.
I decided to reinstall it with the LineageOS, and for that I needed (according the articles) to do oem unlock.
According articles I should get the OEM unlock key from settings or allow it in the settings – which I can’t access as the device won’t boot up.

So I tried bunch of commands from the commandline (ubuntu 20.04), I could not OEM unlock, but I was able to install LineageOS just fine.
My question is – how come that it worked, even though it should not be able to unlock the OEM? What happened there?

Started device with holding vol up:

$ adb devices
List of devices attached
0123456789ABCDEF    sideload

Then I am not sure now what I selected in the menu, but then I went:

$ fastboot devices
84afc61e    fastboot

$ fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.002s

$ fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.002s

$ fastboot oem get_unlock_data
...
FAILED (remote: unknown command)
finished. total time: 0.002s

fastboot oem device-info
...
(bootloader)    Device tampered: false
(bootloader)    Device unlocked: false
(bootloader)    Device critical unlocked: true
(bootloader)    Charger screen enabled: true
(bootloader)    Display panel: 
OKAY (  0.007s)
finished. total time: 0.007s

But I tried to flash in the TWRP recovery image anyhow:

$ fastboot flash recovery recovery.img
target reported max download size of 262144000 bytes
sending 'recovery' (11700 KB)...
OKAY (  0.446s)
writing 'recovery'...
OKAY (  0.947s)
finished. total time: 1.393s

$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY (  0.449s)
booting...
OKAY (  0.023s)
finished. total time: 0.471s

After that, with volume up on boot I got in to TWRP menu; where I installed gaps and LineageOS zips, and after reboot it was just there.

My research links:

How to unlock with face recognition for multiple users?

We are using our tablet together with my wife. I have added another user profile to the Android tablet (Samsung Tab A7, Android 10). I have switched to her account and we added her face for the recognition.

Question: is there a way to directly unlock the device with either of our faces? Otherwise the experience is awful. I need to turn on the device, click on the profile icon on the top right, catch the correct user in 1 second (otherwise screen turns off), then do the face recognition.

lineageos – How to install a post-market operating system on a Samsung Galaxy S7 with a broken screen that has “OEM unlock” still disabled?

I want to use my old Samsung Galaxy S7 (with a broken screen) as a headless device in my home network.

(Rationale – for the curious readers: Even with a broken screen it could possibly become a Bluetooth audio receiver (A2DP sink) or a CCTV-like device. And with its multiple CPU cores, I could even make it part of my home Kubernetes cluster to crunch some CPU-intensive tasks. This way it can remain of service in its afterlife.)

To prepare the device, I would either like to install PostmarketOS or Lineage OS on it. The installation procedures for both operating systems require installing/flashing TWRP onto the recovery partition. (Installation guides: Lineage OS; PostmarketOS)

Unfortunately, the device has most likely never been OEM unlocked before the screen broke. Based on my reading so far, this seems to be a pre-requisite for any kind of image flashing. At least, this is the most likely reason to me why all my flashing attempts failed. (See below what I’ve tried.)

Since the screen is broken, I cannot enable “OEM unlock” via the normal user interface-based procedure.

Now my questions are:

  1. Is “OEM unlock” being enabled a pre-requisite for flashing custom images onto my Samsung mobile device?
  2. How do I enable “OEM unlock” without having access to the device’s screen?

Since I’m not too attached to the device, I’m really willing to go far in experimentation. Any data on the device has most likely become inaccessible in my previous flashing attempts already (I cannot check with a broken screen), so keeping data is not a concern. I’m also willing to cut an USB cable open to solder myself an USB/UART connector cable if necessary.


Here’s what I’ve already tried:

1. Directly using PostmarketOS’s flasher functionality (which uses Heimdall), i.e. without using TWRP

pmbootstrap init
    (I cut the output of the installation wizard)

pmbootstrap install
    (I cut some of the output)
    (17:06:59) (native) format /dev/installp1 (boot, ext2), mount to mountpoint
    (17:06:59) *** (4/4) FILL INSTALL BLOCKDEVICE ***
    (17:06:59) (native) copy rootfs_samsung-herolte to /mnt/install/
    (17:07:07) (native) make sparse rootfs
    (17:07:13) *** FLASHING INFORMATION ***
    (17:07:13) Run the following to flash your installation to the target device:
    (17:07:13) * pmbootstrap flasher flash_rootfs
    (17:07:13)   Flashes the generated rootfs image to your device:
    (17:07:13)   /home/hauke/.local/var/pmbootstrap/chroot_native/home/pmos/rootfs/samsung-herolte.img
    (17:07:13)   (NOTE: This file has a partition table, which contains /boot and / subpartitions. That way we don't need to change the partition layout on your device.)
    (17:07:13) * pmbootstrap flasher flash_kernel
    (17:07:13)   Flashes the kernel + initramfs to your device:
    (17:07:13)   /home/hauke/.local/var/pmbootstrap/chroot_rootfs_samsung-herolte/boot
    (17:07:13) * If the above steps do not work, you can also create symlinks to the generated files with 'pmbootstrap export' and flash outside of pmbootstrap.
    (17:07:13) NOTE: chroot is still active (use 'pmbootstrap shutdown' as necessary)
    (17:07:13) Done

pmbootstrap flasher
    (17:09:09) (native) flash rootfs image
    (17:09:11) (native) install
    < wait for any device >
    Heimdall v1.4.2
    
    Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
    http://www.glassechidna.com.au/
    
    This software is provided free of charge. Copying and redistribution is
    encouraged.
    
    If you appreciate this software and you would like to support future
    development please consider donating:
    http://www.glassechidna.com.au/donate/
    
    Initialising connection...
    Detecting device...
    Claiming interface...
    Setting up interface...
    
    Initialising protocol...
    Protocol initialisation successful.
    
    Beginning session...
    
    Some devices may take up to 2 minutes to respond.
    Please be patient!
    
    Session begun.
    
    Downloading device's PIT file...
    PIT file download successful.
    
    Uploading SYSTEM
    11%
    ERROR: Failed to confirm end of file transfer sequence!
    ERROR: SYSTEM upload failed!
    
    Ending session...

2. Trying to flash TWRP using Heimdall

heimdall flash --verbose --no-reboot --RECOVERY twrp-3.5.0_9-0-herolte.img
Heimdall v1.4.1

Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
      Manufacturer: "SAMSUNG"
           Product: "Gadget Serial"

            length: 18
      device class: 2
               S/N: 0
           VID:PID: 04E8:685D
         bcdDevice: 021B
   iMan:iProd:iSer: 1:2:0
          nb confs: 1

interface(0).altsetting(0): num endpoints = 1
   Class.SubClass.Protocol: 02.02.01
       endpoint(0).address: 83
           max packet size: 0010
          polling interval: 09

interface(1).altsetting(0): num endpoints = 2
   Class.SubClass.Protocol: 0A.00.00
       endpoint(0).address: 81
           max packet size: 0200
          polling interval: 00
       endpoint(1).address: 02
           max packet size: 0200
          polling interval: 00
Claiming interface...
Setting up interface...

Initialising protocol...
Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.
Please be patient!

Session begun.

Downloading device's PIT file...
PIT file download successful.

Uploading RECOVERY
0%
2%

(...)

98%

100%
ERROR: Failed to unpack received packet.

ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!

Ending session...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer.
ERROR: Failed to send end session packet!
Releasing device interface...

3. Trying to flash TWRP via Odin

Output log:

<ID:0/011> Added!!
<ID:0/011> Odin engine v(ID:3.1401)..
<ID:0/011> File analysis..
<ID:0/011> Total Binary size: 43 M
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> NAND Write Start!! 
<ID:0/011> SingleDownload.
<ID:0/011> recovery.img
<ID:0/011> FAIL!
<ID:0/011> 
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

I also tried flashing original Samsung firmware onto my device, also using Odin. That resulted in a “success” message, making me believe that my ROM is not fried (yet).


A similar question with a more narrow focus had already been posted back in 2016. Back then, the answer was “there’s no public knowledge how to do this”. Since the scope of that other question was focused on a way to enable “OEM unlock” through the modification of a file, I have created this new question with broader goal in mind.

can you unlock a phone from a computer?

i was wondering if i could reset my phone password from my computer since it is locked. i cant open the phone because the screens dead however the phones actually completely fine?