← previous next →
Pages: [1]

Author Topic: partitioning tool woes  (Read 5435 times)

death

  • Newbie
  • *
  • Posts: 10
    • View Profile
partitioning tool woes
« on: February 23, 2019, 05:21:01 pm »
this tool:
http://support.planetcom.co.uk/partitionTool.html

used to give the option to put sailfish as a secundary boot.

but now i can only get it as i the main boot option.

i dont really mind having it as a first boot but if i go that way then kali and debian seem to disapear from the 3rd and 4th option.

i would like:
1 - android
2 - recovery
3 - kali
4 - sailfish

OR also fine:

1 - sailfish
2 - recovery
3 - android
4 - kali


has something changed and its no longer possible to have sailfish as non first boot option?
Logged

OPDA

  • Newbie
  • *
  • Posts: 10
    • View Profile
partitioning tool woes
« Reply #1 on: February 25, 2019, 03:17:40 am »
You are right - a lot of options are now not working anymore. I do not know sailfish, but it looks like it has to do with it, because kali should not be affecting this boot sequence. I wonder why do not have others these problems? No more multibooter??
Regards, Andy
Logged

Charliest

  • Newbie
  • *
  • Posts: 8
    • View Profile
partitioning tool woes
« Reply #2 on: February 25, 2019, 06:57:57 pm »
Quote from: OPDA
You are right - a lot of options are now not working anymore. I do not know sailfish, but it looks like it has to do with it, because kali should not be affecting this boot sequence. I wonder why do not have others these problems? No more multibooter??
Regards, Andy

It seems that the latest version was issued with insufficient explanation. The Gemini user is not an appliance user and should not be treated as such.

BTW, has anyone been able to use Magisk (or for that matter any superuser app) installed in rooted android?
Logged

gidds

  • Sr. Member
  • ****
  • Posts: 324
    • View Profile
partitioning tool woes
« Reply #3 on: March 03, 2019, 02:12:12 pm »
Quote from: Charliest
BTW, has anyone been able to use Magisk (or for that matter any superuser app) installed in rooted android?
Yes, I did.  I don't recall any particular problems, except that you have to install Magisk Manager, which is different from Magisk itself.  After doing that, I can use ‘tsu’ in Termux to run stuff as root.
Logged
   Andy/
Psion 3a → Psion 5 → Psion 5mx → Gemini → Astro

idc

  • Jr. Member
  • **
  • Posts: 93
    • View Profile
partitioning tool woes
« Reply #4 on: March 03, 2019, 04:37:34 pm »
Quote from: OPDA
You are right - a lot of options are now not working anymore. I do not know sailfish, but it looks like it has to do with it, because kali should not be affecting this boot sequence. I wonder why do not have others these problems? No more multibooter??
Regards, Andy

It appears that the old way of putting Sailfish and Debian on together, was to use a 'stowaways' folder on the Debian partition. The new way of putting Sailfish on is to setup an LVM volume. In due course Debian TP3 may come out and it may again be possible to have a separate Debian partition.
See here for a more knowledgeable explanation:
https://www.oesf.org/forum/index.php?showto...st&p=291329

Why they didn't explain this in their notes in order to avoid confusion, I don't know.
All the best,
Ian
Logged

Charliest

  • Newbie
  • *
  • Posts: 8
    • View Profile
partitioning tool woes
« Reply #5 on: March 06, 2019, 01:36:27 pm »
Quote from: gidds
Quote from: Charliest
BTW, has anyone been able to use Magisk (or for that matter any superuser app) installed in rooted android?
Yes, I did.  I don't recall any particular problems, except that you have to install Magisk Manager, which is different from Magisk itself.  After doing that, I can use ‘tsu’ in Termux to run stuff as root.

I tried again and met with success after installing a bunch of unrelated apps. I am baffled. but at least Magisk is working.
Logged

rodgos

  • Jr. Member
  • **
  • Posts: 68
    • View Profile
partitioning tool woes
« Reply #6 on: March 07, 2019, 10:48:02 pm »
This might be off thread. Apologies if it is. I've just completed a dual boot installation, with Rooted Android,  which certainly did not go according to the Flashing Guide notes, but finally worked. Now I've come to the part about Magisk. All went well, more or less, until step 4 (Open the application. Magisk Manager???). I get the error message "Magisk is not installed". According to the notes I should go to step 5 "when asked about Additional Setup, tap on Yes and let the process complete". Except, there is nothing asked, so nothing to reply yes to. I gather a box should come up for downloading the Magisk setup zip, but there's no information as to how to get there.
Logged

rodgos

  • Jr. Member
  • **
  • Posts: 68
    • View Profile
partitioning tool woes
« Reply #7 on: March 08, 2019, 06:45:02 pm »
How odd. After spending some time re-populating apps, and at time invoking Magisk Manager, with the same response, "Magisk is not installed" On yet another opening of the Magisk app, the required pop-up with the appropriate message "Requires Additional Setup" appeared. On saying "yes" to that, it all worked and it would seem that I now have a rooted Android
Logged

mithrandir

  • Full Member
  • ***
  • Posts: 191
    • View Profile
    • http://www.mygnu.de
partitioning tool woes
« Reply #8 on: May 28, 2019, 05:46:31 pm »
Hmm, I don't like the options of the new tool. Always had Debian in the primary slot. Any way to keep it this way, probably by manually editing the scatter file? Is it possible to update the Android without having to reinstall Debian?
Logged
Pages: [1]
← previous next →