Author Topic: Installing rooted android on TWRP boot 2 in order to put UBPorts in 4. Any cons?  (Read 355 times)

idc

  • Jr. Member
  • **
  • Posts: 75
    • View Profile
Hi,
I would like to install Ubuntu Ports on my Cosmo and need therefore to free up boot 4, but would like to retain Gemian in boot 3. If I don't need wireless for rooted Android, is there any reason I shouldn't install rooted Android into boot 2 instead of TWRP? Would I be losing anything useful? So far as I can tell TWRP is of no particular use on this machine. The instructions here are ambiguous as to whether or not this is possible, referring to boot 2 only working with 'recovery mode', and suggesting only boot 3 and 4 can take rooted Android. (Let me know if I've missed something here.)

On my Cosmo I have Android in boot 1, Gemian in boot 3 and rooted Android in boot 4. (Though since reinstalling Gemian I can now see six options on booting: 1 NORMAL; 2 RECOVERY; 3 TWRP; 4 Debian/KDE; 5 ROOTED_ANDROID; 6 FASTBOOT.) I only ever use rooted Android once in a while in order to run Titanium backup, backing up to an SD card — because I use Android without logging in to Google and therefore, I believe, nothing is backed up by default. Presumably I could do this just as well with rooted Android in boot 2. Has anyone else done this?

Will the process of installing rooted Android in boot 2 mean I have to reinstall Titanium Backup or change any other settings, or am I right in thinking that rooted Android keeps everything (or nearly everything?) in the same partitions as unrooted Android, so reinstalling rooted Android to boot 2 as per the instructions would leave me with Titanium Backup and its settings unchanged?

Sorry for so many questions and thanks in advance for any help/advice you can offer. Despite using Android for a number of years, I still feel it is an OS I don't really understand.
Ian

MonkeyControl

  • Jr. Member
  • **
  • Posts: 79
    • View Profile
    • http://
I couldn't find much to help you other than this post warning about no modem access:  https://www.oesf.org/forum/index.php?topic=36413.msg296945#msg296945, and you suggested you didn't need wireless, but other than that I don't know.  Maybe do a backup and give it a go, or contact PC and see what they have to say about it.  I have Android, Recovery, Debian, UBPorts, FastBoot options on my Cosmo.  UBPorts is my default and I have no use for Android, but I may have a go this weekend out of curiosity, if I'm feeling brave. 

idc

  • Jr. Member
  • **
  • Posts: 75
    • View Profile
Thanks for that. When I've some time, I shall give it a go. If you do get there before me, I'd be interested to hear your experience. Are you using Ubuntu as a phone or just as a mobile computer? How do you find the battery life?
Thanks again for your input.

MonkeyControl

  • Jr. Member
  • **
  • Posts: 79
    • View Profile
    • http://
Thanks for that. When I've some time, I shall give it a go. If you do get there before me, I'd be interested to hear your experience.
I didn't have time last weekend, definitely this weekend though, full backup then a deep breath. 
Are you using Ubuntu as a phone or just as a mobile computer?
Full time phone, part time computer, I suppose.  Maybe you don't quite get the full desktop package experience that you do with Debian, but for me UT fits my use case, and it's very stable and has a really nice interface. 
How do you find the battery life?
From an overnight charge I get a day's work out of it, maybe a little topup in the evening if I'm caning the browser.  UT seems a lot lighter on battery than Debian, and also better signal coverage, not sure if the two things are related. 

idc

  • Jr. Member
  • **
  • Posts: 75
    • View Profile
Cool. It does sound like it might meet my use case. Let me know how you get on if you manage this weekend.

MonkeyControl

  • Jr. Member
  • **
  • Posts: 79
    • View Profile
    • http://
Cool. It does sound like it might meet my use case. Let me know how you get on if you manage this weekend.
My weekend didn't go to plan, but I did get a little trial run. 
I managed to get to a stage where all the options: 
    [1] NORMAL
    [2] RECOVERY
    [3] ROOTED_ANDROID
    [4] DEBIAN_KDE
    [5] UBPORTS
    [6] FASTBOOT
appear on bootup, but rooted android doesn't boot.  Also note the recovery option is still there after I tried to put rooted android into 'EMPTY_RECOVERY_BOOT_2'. 
I'll have another go this weekend, maybe changing the sequence I load stuff up, or putting stuff in different slots. 
The order I tried (following the instructions from the Planet website (https://support.planetcom.co.uk/index.php/Linux_for_Cosmo) using firmware V3) was: 
1.  Debian into EMPTY_NORMAL_BOOT_3, (worked okay)
2.  Tried Rooted Android into EMPTY_RECOVERY_BOOT_2, (appeared below recovery on boot options, but didn't boot)
3.  Rooted Android into EMPTY_NORMAL_BOOT_4, (seems okay, but android is still ugly) :)
4.  Ran out of time and needed Ubuntu Touch back, so installed as per instructions here (https://www.oesf.org/forum/index.php?topic=36413.0). 
I wrote the procedure down as I went along, it's a bit long winded for a post, but I'll pm it to you if you are interested. 
I'll have another crack this weekend if I get time. 
Sorry, can't be more help than that at the moment, I'm short of time and really don't know what I'm doing :)