I have a Tissot (mi a1) with TWRP dual booted by separating vendor_a, vendor_b, userdata_a, userdata_b. It is dual booted by cosmicdan's twrp with Resurrection remix ( slot_a) official and Dotos official ( slot_b). I want to mount userdata_b in resurrection remix or vice verse. I have already tried these steps by no result.

  1. create a folder named 'data2' in " /data/local/tmp/data2" .
  2. open terminal.
  3. run su.
  4. Enter "mount -o rw /dev/block/mmcblk0p52 /data/local/tmp/data2" (as 52 is my userdata_b partition).
  5. no error showing but nothing mounted.

Is there any way to mount this?


Go to android update if it's update is available than the phone would have to be connected to a power source while it rebooted to recovery mode and actually flashed the update.All in, you're talking 30 minutes to an hour to install an update, and nobody has time for that. Even disregarding that hurdle, many users would just ignore the update out of fear for the bugs and UI changes it might bring, leaving their systems dangerously exposed to malware and hacks.

When you take a new phone out of its box, the operating system is installed on the first hard drive (partition "A"). When an update becomes available, it gets downloaded and installed to the second hard drive (partition "B").

The next time you restart your phone, it simply boots off of the "B" partition instead, which means you're now running the new Android update.A/B system updates, also known as seamless updates, ensure a workable booting system remains on the disk during an over-the-air (OTA) update.

This reduces the likelihood of an inactive device afterward, which means fewer device replacements and device reflashes at repair and warranty centers. This approach is already explored successfully by other commercial-grade operating systems, such as ChromeOS, and Android 8.0 comes with the necessary platform changes to conduct streaming updates.

Allow to cancel a proxy resolution request 1 Fix terminating a transfer while resolving proxies 2 Add unittest for TerminateTrasnfer between ranges 3 Cleanup the RetryTimeoutCallback()

A/B system updates affect:

Interactions with the bootloader Partition selection The build process OTA update package generation The existing dm-verity feature guarantees the device will boot an uncorrupted image. If a device doesn't boot, because of a bad OTA or dm-verity issue, the device can reboot into an old image.

  • My system is already rooted and custom recovery and custom os installed, with dual booted. – Sudipta Sarkar Jun 18 '18 at 10:39

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.