Search results

  1. D

    Post [MOD][Z2] MultiROM v33d

    Please find the latest files in the attachment. The app does not work anymore since I have re-setup the server and did not install the package for the file service again. Given the age of the device, this is acceptable IMO.
  2. D

    Post [MOD][Z2] MultiROM v33d

    Probably, you found out already: Please use the alternate installation method as written in the OP...
  3. D

    Post [MOD][Z2] MultiROM v33d

    I'd advise you to install the experimental version while you are on stock. Then, boot to recovery and copy or move the stock rom from the primary slot to the secondary (e.g., internal sdcard). After that, follow the normal instructions to install carbon (that will include a factory reset and...
  4. D

    Post [MOD][Z2] MultiROM v33d

    Unfortunately, F2FS is not supported. It will come when I switch the build environment from an Omni-7.1-based to an Omni-8.1-based one (One of the next steps before the stable release). However, you should be able to do a file-based backup, reformat, and move the data back.
  5. D

    Post [MOD][Z2] MultiROM v33d

    New experimental build is up! You may need to use the manual installation depending on your primary rom (the apk in the download folder may be non-functional): https://diewald-net.com/files/public/MultiRom/sirius/experimental/ Since this is just an experimental release to support the current...
  6. D

    Post [MOD][Z2] MultiROM v33d

    --- Deleted ---
  7. D

    Post [MOD][Z2] MultiROM v33d

    A small heads-up: I will delay the experimental release with proper 8.1 support for 1-2 days since I was busy with the dtb implementation (see earlier posts). It is now properly implemented (IMHO). Due to that I did not have time left to properly test other setups and stock roms. After doing so...
  8. D

    Post [MOD][Z2] MultiROM v33d

    BTW, I am currently creating a fix for the problems with the secondaries. I got it working so far, but need refactor and improve the current patch set to avoid one unsafe hack such that we can merge it in the upstream project after code review. When the refactoring and improvement is done, I...
  9. D

    Post [MOD][Z2] MultiROM v33d

    All recent 8.1 distributions function properly as primaries, not as secondaries. The limitation mentioned earlier applies ONLY to secondaries.
  10. D

    Post [MOD][Z2] MultiROM v33d

    Yes, the nougat version of carbon rom is fine. Same holds for Oreo 8.0. It is a requirement to have an unlocked bootloader in order to use MultiROM at all.
  11. D

    Post [MOD][Z2] MultiROM v33d

    Hmmm, LP... I've tested stock only with MM version: That's something you could try. Before doing so, please wipe the apps_log partition (with FlashTool) to exclude any problems resulting from there. These have been resolved in the last version, but just to be on the safe side :)
  12. D

    Post [MOD][Z2] MultiROM v33d

    It's written in the installation instructions (probably not included in "everywhere" ;P ). And once again, xda didn't notify me of the new post :rolleyes: Also, for your information: Recent 8.1 based roms (released since the new year) will not work: Android Oreo introduced a changed such that...
  13. D

    Post [DEV][β] OmniROM [Unofficial] [8.1] [D6603/33/53/83] Z3 (Leo)

    To avoid any confusion early enough: The shinanos are NOT treble-enabled devices with the latest release! Treble requires more than just the definition of hardware services. It also requires a separate vendor partition and that ALL device-specific files are placed in this partition (the latter...
  14. D

    Post [DEV][β] OmniROM [Unofficial] [8.1] [D6603/33/53/83] Z3 (Leo)

    The reason for this are the permissions of GApps. If you install them jointly with the rom, all the ones requested from the package will be set automatically. Otherwise, each permission would need to be set manually. This happens since Android N. Just FYI :)
  15. D

    Post [ROM][Z3/DUAL] LineageOS 15.0 [Updated 11/18][OTA]

    Please keep the link to the sources more recent. The linked manifest points to cm14.1 branches. Regarding the kernel: Any of the sources you have linked to not have the fix for the BT vulnerability. Since I doubt that you expose your users of this risk, please link at least these sources. The...
  16. D

    Post [MOD][Z2] MultiROM v33d

    Just try and report back. Stock is supported in general. However, LP is really outdated and supported here any more ;)
  17. D

    Post [MOD][Z2 Tablet] MultiROM v33c

    Bugfix release v33d: - Fix the apps_log issue for good (FINALLY). - Support for LOS in combination with stock. Special thanks to @akshay2shah for testing!
  18. D

    Post [MOD][Z2] MultiROM v33d

    Bugfix release v33d: - Fix the apps_log issue for good (FINALLY). - Support for LOS in combination with stock. Special thanks to akshay2shah for testing!
  19. D

    Post [MOD][Z2] MultiROM v33d

    Thanks for the logs, I will dig into this problem during the weekend.
  20. D

    Post [MOD][Z2 Tablet] MultiROM v33c

    Ok, so I tried to debug this issue with the Z2 Tablet, findings below. I can open a remote shell on the device using "adb shell" with or without a rom residing in the system partition. Also, if I run "getprop ro.product.device" in the shell I get the string "castor" back in both cases. This...
  21. D

    Post [MOD][Z2] MultiROM v33d

    If you have this problem, unfrotunately not. The fstab file is contained in the boot image and is extracted to the Ram during boot, so I need to patch it on the fly with multirom. Of course, you could still extract the boot image modify the fstab and repack it. But that's not what I expect from...
  22. D

    Post [MOD][Z2 Tablet] MultiROM v33c

    I have just tested the device name via getprop on my sirius (Z2) and it showed the correct string, also "adb shell" worked, both with the system partition wiped. I will re-test this when I have access to my castor test device in the next days again. I'll write here again when I did this...
  23. D

    Post [MOD][Z2] MultiROM v33d

    Many thanks, it's like I thought. Line 5 should not be there. I am a bit surprised that it is still exists, since I actually made a fix for that which also removed this line when I tested it... :confused: Anyways, I will test this next week again and fix it ASAP. Thanks for reporting.
  24. D

    Post [MOD][Z2] MultiROM v33d

    It's in the root directory, i.e. "/fstab.shinano". If the problem is caused by the "appslog partition problem", you can wipe it using flashtool: it has a switch for that, but please ensure that everything else is unticked :D
  25. D

    Post [MOD][Z2] MultiROM v33d

    Hmm, this is strange. Could you upload the content of the fstab.* file (* = shinano or sirius) after booting the N rom somewhere, e.g. pastebin? The fix for the appslog problem is that the fstab is modified when booting the N rom such that it is not mounted in the "/misc" folder. If the fix...
  26. D

    Post [MOD][Z2] MultiROM v33d

    Then it's possible that you booted the recovery which came with the kernel image. From Arbicot's FAQ: Q : Does this kernel include recovery ? A : Yes ! You can access by pressing buttons when the led is lighting. Volume down to go to TWRP and Volume up to load recovery from FOTA..
  27. D

    Post [MOD][Z2] MultiROM v33d

    Hi, I think the most probable reason is that you flashed the wrong file. Which rom do you refer to with "Android 6.0.1"? Stock?
  28. D

    Post [MOD][Z2] MultiROM v33d

    Not yet, unfortunately. Since this question is posted public, please edit your post to include information about the issue you are observing. Thanks.
  29. D

    Post [MOD][Z2 Tablet] MultiROM v33c

    Well, I should have thought of this earlier... These additional scripts, update zips, etc. may cause these issues for non-primary roms. You can either remove the assert from the update zip (dangerous), but this seems a rom issue to me, since I other roms installed fine for me after wiping...
  30. D

    Post [MOD][Z2 Tablet] MultiROM v33c

    Hi, thanks for the report and the log! From the log, I can see that there multiple attempts to root the rom (SuperSU and some other). Did you try to root it by installing some additional zip, or is the log about the rom installation exclusively (i.e., only installing the rom's zip, then getting...
  31. D

    Post [MOD][Z2] MultiROM v33d

    Isn't that obvious? ;) If you want to use mrom you'll always use the Mrom recovery.
  32. D

    Post [MOD][Z2] MultiROM v33d

    No, you don't need a custom kernel. Stock kernels are supported as well as custom ones.
  33. D

    Post [MOD][Z2] MultiROM v33d

    Please retry with Multirom Recovery. This typically fixes the problem.
  34. D

    Post [MOD][Z2] MultiROM v33d

    No, because it's not needed. Kernel and Rom are matching.
  35. D

    Post [MOD][Z2] MultiROM v33d

    You're welcome. Multrom itself is agnostic towards a rom being stock or not. The only thing where multirom differentiates is the whether a rom is installed as primary (aka normal installation) or secondary.
  36. D

    Post [MOD][Z2] MultiROM v33d

    When you reboot from the secondary rom, the primary's kernel is loaded since it has been flashed back again (see item #5). Therefore, the multirom selection dialog is shown again.
  37. D

    Post [MOD][Z2] MultiROM v33d

    The information written in that post is not entirely correct since the behaviour changed in the nikexec implementation. It has been correct for nokexec v2, but no longer for v4. The primary kernel is flashed backed when booting a secondary rom to have the device in a consistent state. Here is...
  38. D

    Post [MOD][Z2] MultiROM v33d

    AFAIK, yes.
  39. D

    Post [MOD][Z2] MultiROM v33d

    Thanks for the notification! I fixed it in the description file on the server. For some reason, this error did not show up during the pre-(test) release process... And yes, it's the recent version.
  40. D

    Post [MOD][Z2 Tablet] MultiROM v33c

    New build is out: v33c Main feature: You can now use stock as secondary rom. Please follow the instructions in the OP. Other than that, there are mainly maintenance updates. Further, the update notification from the app should now function correctly, as the version information is now...
  41. D

    Post [MOD][Z2] MultiROM v33d

    New build is out: v33c Main feature: You can now use stock as secondary rom. Please follow the instructions in the OP. Other than that, there are mainly maintenance updates. Further, the update notification from the app should now function correctly, as the version information is now correctly...
  42. D

    Post [MOD][Z2] MultiROM v33d

    Just install the zip from the Multirom recovery and check the "inject multirom" option in the "swip to confirm" dialog. That's all :)
  43. D

    Post [MOD][Z2] MultiROM v33d

    Hi, those are my builds that I am using to develop for AOSP. They have basically the same bugs as rcstar's builds (except some slight deviation), but are likely more unstable since they often include also work in progress patches, hence the experimental label.
  44. D

    Post Call notification on Urbane 2

    If you place a SIM card in the watch, then it is possible. Of course, the SIM card in the watch must have the same number as the one in your phone. Please note that not a provider offer this so-called MultiSIM option.
  45. D

    Post Systemless SuperSU for stock roms

    IF you need stock for that then: probably yes. But I am not into this android pay stuff (which has even more scurity mechanisms AFAIK to even detect systemless root), so at least I can't give you an answer to this. Anyone? Yep.
  46. D

    Post Systemless SuperSU for stock roms

    Custom kernels are not using the ELF format. The boot_bridge is for the stock kernel, not custom kernels compiled from stock sources.
  47. D

    Post Systemless SuperSU for stock roms

    To be safe, uninstall supersu before. Either via a the uninstaller or by flashing stock.
  48. D

    Thread Systemless SuperSU for stock roms

    Hello all, as you may know installing systemless SuperSU for Z2 Tablet stock roms was not possible until now due to the ELF format of the boot image. As a workaround one was required to install SuperSU in system mode, but support for this installation type seems to fade away... In order to...
  49. D

    Thread Systemless SuperSU for stock roms

    Hello all, as you may know installing systemless SuperSU for Z2 stock roms was not possible until now due to the ELF format of the boot image. As a workaround one was required to install SuperSU in system mode, but support for this installation type seems to fade away... In order to have...