Tag: failed

4.4 kitkat – ADB Reboot Failed: -1 When using “adb reboot bootloader”. (Infocus M530)

I have an Old Infocus M530 running on Android 4.4.2 (KK) (Which i believe is made by Foxconn), I’ve been trying to make some Custom Recoveries for this device for quite some time and i always end up leaving it because of this problem that I’ve been having for about a year now. This device just doesn’t reboot into bootloader/fastboot.

I tried “adb reboot bootloader” and adb gives “reboot failed: -1”, tried “adb reboot fastboot” then the device just reboots normally back to system.

Also this device uses a program called “SUTL” to flash it’s stock firmware which i have used numerous times since I’ve bricked it by removing several apps via root. (I gained root via Kingoroot). The firmware image(archive) also can’t be extracted via 7Zip or similiar programs because it probably have some modified or custom header.

Tho this device works fine i can’t seem to get the bootloader unlocked on it. I can’t even pull images of partitions via adb shell it gives me “Permission denied” error.

So all i wanted to know at the moment is how can i unlock it’s bootloader so i can pull some system images. Thanks.

error unlocking dev/sdb1: failed to activate device: operation is not supported

please help Ive typed my password correct but it still comes up with: "error unlocking dev/sdb1: failed to activate device: operation is not supported"

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

dnd 5e – Does the 3rd benefit of the (UA) Fizban’s Platinum Shield spell stack with Evasion, so that the character only takes 1/4 damage on a failed Dex save?

The new UA, Unearthed Arcana: Draconic Options, introduces a 6th-level spell called Fizban’s platinum shield that can be cast on a creature within 60 feet of the caster, granting them a few benefits. The description of the final benefit reads as follows:

  • If the creature is subjected to an effect that allows it to make a Dexterity saving throw to take only half damage, the creature instead takes no damage if it succeeds on the saving throw, and only half damage if it fails.

This has the same effect as the Evasion feature of a Monk or Rogue (or Hunter ranger, maybe).

Since this spell benefit and Evasion have the same effect but different names from different sources, would they stack with each other?
For instance, in the case of a 7th-level monk failing a Dex save against the fireball spell while under the effect of this spell, would they take a quarter damage?

ERROR IN in my SPFX WebPart : Module parse failed: Unexpected token You may need an additional loader to handle the result of these loaders

I have created an SPFx project with reactJS. I am using .jsx extension – functional components.

Now, the spfx webpart is already working fine, but I saw a material kit that I want to reuse its components.

When I referenced the components, I am presented with this error

(SPLoaderError.loadComponentError):
***Failed to load component (WebPart). Original error: ***Failed to load entry point from component WebPart). Original error: Module parse failed: Unexpected token (30:4)
File was processed with these loaders:
./node_modules/source-map-loader/index.js
You may need an additional loader to handle the result of these loaders.

enter image description here

It seems that I cannot use the “footer” tag?

enter image description here

Synology, trying to bring back a failed RAID array

so I manage to destroy some of my data… I have a ds916+ and would like to recover the data from the drives, I ordered a new drive because one was failing, and another one failed during resync… so ye, double disk failure.

Here I’m now:

root@NAS:~# mdadm --detail /dev/md2
/dev/md2:
        Version : 1.2
  Creation Time : Sat Mar  3 14:15:17 2018
     Raid Level : raid10
     Array Size : 3897385088 (3716.84 GiB 3990.92 GB)
  Used Dev Size : 1948692544 (1858.42 GiB 1995.46 GB)
   Raid Devices : 4
  Total Devices : 3
    Persistence : Superblock is persistent

    Update Time : Wed Apr 14 21:28:42 2021
          State : clean, FAILED
 Active Devices : 3
Working Devices : 3
 Failed Devices : 0
  Spare Devices : 0

         Layout : near=2
     Chunk Size : 64K

           Name : NAS:2  (local to host NAS)
           UUID : 928d46c6:72c08f44:8997f935:c9c219cf
         Events : 11818

    Number   Major   Minor   RaidDevice State
       0       8        3        0      active sync set-A   /dev/sda3
       1       8       19        1      active sync set-B   /dev/sdb3
       -       0        0        2      removed
       3       8       51        3      faulty active sync set-B   /dev/sdd3

Now, when I do a:

mdadm --manage /dev/md2 --add /dev/sdc3

This drive is being added as a spare:

root@NAS:~# mdadm --detail /dev/md2
/dev/md2:
        Version : 1.2
  Creation Time : Sat Mar  3 14:15:17 2018
     Raid Level : raid10
     Array Size : 3897385088 (3716.84 GiB 3990.92 GB)
  Used Dev Size : 1948692544 (1858.42 GiB 1995.46 GB)
   Raid Devices : 4
  Total Devices : 4
    Persistence : Superblock is persistent

    Update Time : Wed Apr 14 21:28:12 2021
          State : clean, FAILED
 Active Devices : 3
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 1

         Layout : near=2
     Chunk Size : 64K

           Name : NAS:2  (local to host NAS)
           UUID : 928d46c6:72c08f44:8997f935:c9c219cf
         Events : 11817

    Number   Major   Minor   RaidDevice State
       0       8        3        0      active sync set-A   /dev/sda3
       1       8       19        1      active sync set-B   /dev/sdb3
       -       0        0        2      removed
       3       8       51        3      faulty active sync set-B   /dev/sdd3

       4       8       35        -      spare   /dev/sdc3

What I would like to achieve, is that the sdc3 will jump back to it’s place and with that I hope I get access to some of the data, the drive was working before replacement.

Also, the following mdadm command doesn’t work:

root@NAS:~# mdadm --manage /dev/md2 --re-add /dev/sdc3
mdadm: --re-add for /dev/sdc3 to /dev/md2 is not possible

Here is also some additional information which may help:

root@NAS:~# mdadm --examine /dev/sdc2
/dev/sdc2:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : fea95269:e7e6ab4e:cced5de7:ca715931 (local to host NAS)
  Creation Time : Sat Jan  1 01:00:09 2000
     Raid Level : raid1
  Used Dev Size : 2097088 (2047.94 MiB 2147.42 MB)
     Array Size : 2097088 (2047.94 MiB 2147.42 MB)
   Raid Devices : 4
  Total Devices : 4
Preferred Minor : 1

    Update Time : Wed Apr 14 21:09:33 2021
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0
       Checksum : c01e878e - correct
         Events : 158


      Number   Major   Minor   RaidDevice State
this     2       8       34        2      active sync   /dev/sdc2

   0     0       8        2        0      active sync   /dev/sda2
   1     1       8       18        1      active sync   /dev/sdb2
   2     2       8       34        2      active sync   /dev/sdc2
   3     3       8       50        3      active sync   /dev/sdd2

root@NAS:~# fdisk -l /dev/sd(a-d)
Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x27fe7bf8

Device     Boot   Start        End    Sectors  Size Id Type
/dev/sda1          2048    4982527    4980480  2.4G fd Linux raid autodetect
/dev/sda2       4982528    9176831    4194304    2G fd Linux raid autodetect
/dev/sda3       9437184 3906824351 3897387168  1.8T fd Linux raid autodetect
Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x26a4ac9c

Device     Boot   Start        End    Sectors  Size Id Type
/dev/sdb1          2048    4982527    4980480  2.4G fd Linux raid autodetect
/dev/sdb2       4982528    9176831    4194304    2G fd Linux raid autodetect
/dev/sdb3       9437184 3906824351 3897387168  1.8T fd Linux raid autodetect
Disk /dev/sdc: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x7eba1232

Device     Boot   Start        End    Sectors  Size Id Type
/dev/sdc1          2048    4982527    4980480  2.4G fd Linux raid autodetect
/dev/sdc2       4982528    9176831    4194304    2G fd Linux raid autodetect
/dev/sdc3       9437184 3906824351 3897387168  1.8T fd Linux raid autodetect
Disk /dev/sdd: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xea4cb292

Device     Boot   Start        End    Sectors  Size Id Type
/dev/sdd1          2048    4982527    4980480  2.4G fd Linux raid autodetect
/dev/sdd2       4982528    9176831    4194304    2G fd Linux raid autodetect
/dev/sdd3       9437184 3906824351 3897387168  1.8T fd Linux raid autodetect

Please help! 🙂

MongoDB – Robo3t: Failed to do query, no good nodes, Field ‘cursor’ must be a nested object

When viewing documents of a collection and trying to move between pages using “left” and “right” arrow buttons:

enter image description here

suddenly started to get the following error in Robo3T:

Failed to load documents.
Error:
Failed to do query, no good nodes in MyCluster-shard-0, last error: can’t query replica set node mycluster-shard-xx-xx.xxx.xxx.net:27017 :: caused by :: Field ‘cursor’ must be a nested object in: { conversationId: 7, done: false, payload: BinData(0, 723D424753514D4F432F494C776E73765A7263356774622F42564B695A62746F45523832456A5244475473346E30616B4B597938686352413D3D2C733D6F52614C316438586F…), ok: 1 }

Any idea of why is this happening?

All documents in a collection are of following structure:
enter image description here

Using Robo3T 1.4 on Ubuntu/Windows 10 – same thing on both OS.

svn – Subversion SSL handshake failed and 408 error code

Subversion: version 1.6.11 (r934486)

Operating System: CentOS release 6.8 (Final)

I have a variety of shell scripts that run as cronjobs on a CentOS machine. The shell scripts commit files to and checkout files from Subversion. Today all my scripts started failing with the following error

svn: OPTIONS of ‘https://svn.int.mydomain.edu/eas’: SSL handshake failed: SSL alert received: Error in protocol version (https://svn.int.mydomain.edu)

As a troubleshooting step I have ran the following command

openssl s_client -connect svn.int.mydomain.edu:443

And received the following output ( redacted slightly )

CONNECTED(00000003)
---
Certificate chain
 0 s:/OU=Domain Control Validated/CN=*.int.mydomain.edu
   i:/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certs.godaddy.com/repository//CN=Go Daddy Secure Certificate Authority - G2
 1 s:/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certs.godaddy.com/repository//CN=Go Daddy Secure Certificate Authority - G2
   i:/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./CN=Go Daddy Root Certificate Authority - G2
 2 s:/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./CN=Go Daddy Root Certificate Authority - G2
   i:/C=US/O=The Go Daddy Group, Inc./OU=Go Daddy Class 2 Certification Authority
 3 s:/C=US/O=The Go Daddy Group, Inc./OU=Go Daddy Class 2 Certification Authority
   i:/C=US/O=The Go Daddy Group, Inc./OU=Go Daddy Class 2 Certification Authority
---
Server certificate
-----BEGIN CERTIFICATE-----
REDACTED
-----END CERTIFICATE-----
subject=/OU=Domain Control Validated/CN=*.int.mydomain.edu
issuer=/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certs.godaddy.com/repository//CN=Go Daddy Secure Certificate Authority - G2
---
No client certificate CA names sent
Server Temp Key: ECDH, prime256v1, 256 bits
---
SSL handshake has read 5545 bytes and written 373 bytes
---
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-GCM-SHA384
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : ECDHE-RSA-AES256-GCM-SHA384
    Session-ID: REDACTED
    Session-ID-ctx: 
    Master-Key: REDACTED
    Key-Arg   : None
    Krb5 Principal: None
    PSK identity: None
    PSK identity hint: None
    Start Time: 1618275549
    Timeout   : 300 (sec)
    Verify return code: 0 (ok)
---
HTTP/1.1 408 Request Time-out
content-length: 110
cache-control: no-cache
content-type: text/html
connection: close

<html><body><h1>408 Request Time-out</h1>
Your browser didn't send a complete request in time.
</body></html>
closed

As you can see I am getting a HTTP/1.1 408 Request Time-out at the end of the standard output. I can verify I have access to https://svn.int.mydomain.edu on this box, because a separate installation of svn works fine from that box ( an installation of SVN that came with a Jenkins plugin ).

Does anyone have any thoughts on additional troubleshooting techniques here? I’ve tried to search for this issue but there is no fruitful responses.

ubuntu 18.04 – Openstack: The ext4 file system creation in partition #1 of Virtual disk 1 (vda) failed

I followed the official devstack All-In-One Single Machine installation and after everything installed, when I create an instance with 1GB ram and 10 GB hard disk of ubuntu 18.04 desktop
the messenge show up “The ext4 file system creation in partition #1 of Virtual disk 1 (vda) failed”. My environment is 200 GB hard disk and 10 GB ram with 4 CPU. What is the problem and what should do? Thanks!

flags – Success with cookie, fails with JWT: RuntimeException: Failed to start the session because headers have already been sent

My Controller is working with cookie auth but failing with JWT. This Controller is supposed to flag an entity for the logged-in user.

If I am using cookie auth, there are no errors and everything works as expected.

But when I try to use JWT, although the entity does get flagged correctly, I get the following error in the Drupal logs:

RuntimeException: Failed to start the session because headers have
already been sent by
“/app/vendor/symfony/http-foundation/Response.php” at line 377. in
SymfonyComponentHttpFoundationSessionStorageNativeSessionStorage->start()
(line 150 of
/app/vendor/symfony/http-foundation/Session/Storage/NativeSessionStorage.php)

How do I fix this error?

Here’s how I’m using JWT auth in Postman:

POST http://example.com/api/group_add?_format=json

Headers:

  • Accept: application/vnd.api+json
  • Content-Type: application/vnd.api+json
  • Cache: no-cache
  • Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpYXQiOjE2MTgyMDk4MjAsImV4cCI6MTYyMzM5MzgyMCwiZHJ1cGFsIjp7InVpZCI6IjI3In19.5uDJMtokLXD6K63H5Ikb-F870EYFMrgE4mItTuTT3bI

Request body:

{
    "entity_id": "14"
}

As for the Controller, here’s MYMODULE.routing.yml:

MYMOUDLE.api_flagging.http:
  path: '/api/group_add'
  defaults:
    _controller: 'DrupalMYMODULEControllerApiFlagging::flag'
  methods: (POST)
  requirements:
    _permission: 'view own commerce_order'
    _format: 'json'
  options:
    no_cache: 'TRUE'

Here’s ApiFlagging.php:

<?php

namespace DrupalMYMODULEController;

use DrupalCoreControllerControllerBase;
use DrupalflagFlagServiceInterface;
use SymfonyComponentDependencyInjectionContainerInterface;
use SymfonyComponentHttpFoundationJsonResponse;
use SymfonyComponentHttpFoundationRequest;
use SymfonyComponentHttpKernelExceptionBadRequestHttpException;
use SymfonyComponentSerializerEncoderJsonEncoder;
use SymfonyComponentSerializerSerializer;

/**
 * Class ApiFlagging.
 *
 * Https://www.drupal.org/project/flag/issues/3091824#comment-13336379
 */
class ApiFlagging extends ControllerBase {

  const FLAG_ID = 'ABC';

  /**
   * The flag service.
   *
   * @var DrupalflagFlagServiceInterface
   */
  protected $flagService;

  /**
   * The serializer.
   *
   * @var SymfonyComponentSerializerSerializer
   */
  protected $serializer;

  /**
   * The available serialization formats.
   *
   * @var array
   */
  protected $serializerFormats = ();

  /**
   * Constructs a new ApiFlagging object.
   */
  public function __construct(Serializer $serializer, array $serializer_formats, FlagServiceInterface $flag) {
    $this->serializer = $serializer;
    $this->serializerFormats = $serializer_formats;
    $this->flagService = $flag;
  }

  /**
   * {@inheritdoc}
   */
  public static function create(ContainerInterface $container) {
    if ($container->hasParameter('serializer.formats') && $container->has('serializer')) {
      $serializer = $container->get('serializer');
      $formats = $container->getParameter('serializer.formats');
    }
    else {
      $formats = ('json');
      $encoders = (new JsonEncoder());
      $serializer = new Serializer((), $encoders);
    }

    return new static(
      $serializer,
      $formats,
      $container->get('flag')
    );
  }

  /**
   * Flagging.
   */
  public function flag(Request $request) {
    $format = $this->getRequestFormat($request);

    $content = $request->getContent();
    $flagData = $this->serializer->decode($content, $format);
    $flag = $this->flagService->getFlagById(self::FLAG_ID);
    $flaggableEntityTypeId = $flag->getFlaggableEntityTypeId();

    $my_goals = NULL;
    if (array_key_exists('goals', $flagData)) {
      $my_goals = $flagData('goals');
    }

    $entity = Drupal::entityTypeManager()
      ->getStorage($flaggableEntityTypeId)
      ->load($flagData('entity_id'));

    if ($my_goals === NULL) {
      return new JsonResponse((
        'error_message' => 'Goals not set.',
      ), 400);
    }

    try {
      /** @var DrupalflagEntityFlagging $flagging */
      $flag->set('field_goals', $my_goals);
      $flagging = $this->flagService->flag($flag, $entity);
    }
    catch (LogicException $e) {
      $message = $e->getMessage();
      kint('error', $e);
      return new JsonResponse((
        'error_message' => $message,
      ), 400);
    }

    return new JsonResponse((
      'message' => 'flag success',
      'flagging_uuid' => $flagging->uuid(),
      'flagging_id' => $flagging->id(),
      'flag_id' => $flagging->getFlagId(),
    ));
  }

  /**
   * Gets the format of the current request.
   *
   * @param SymfonyComponentHttpFoundationRequest $request
   *   The current request.
   *
   * @return string
   *   The format of the request.
   */
  protected function getRequestFormat(Request $request) {
    $format = $request->getRequestFormat();
    if (!in_array($format, $this->serializerFormats)) {
      throw new BadRequestHttpException("Unrecognized format: $format.");
    }
    return $format;
  }

}