OESF Portal | OESF Forum | OESF Wiki | LinuxPDA | #planetgemini chat on matrix.org | #gemini-pda chat on Freenode | #zaurus and #alarmz chat on Freenode | ELSI (coming soon) | Ibiblio

IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
> Update Android Oreo on existing multiboot device
Jess R
post May 27 2019, 02:48 AM
Post #1





Group: Members
Posts: 12
Joined: 16-June 18
Member No.: 824,577



Hi folks,

Back in July last year, I installed a multi-boot Android 7.1 and Debian system onto my Gemini (wifi-only). Now I'm looking at the Android 8.1 release, and wondering what steps are needed to update that (without killing the linux install or preferably the android user data).. I don't see any instructions for that anywhere, beyond some vague hints.. Can anyone clarify?

I'm assuming:
* I don't need a new scatter file? (I already did the partitioning)
* I need a copy of the new Wifi android firmware - Gemini_WIFI_FOTA3_17052019.zip - or do I? is this the same as the "base firmware" the partitioning tool mentions? Do I need that instead?

After that I get more confused - I assume I rerun the flash tool, choosing the firmware somehow (or do I need to recreate the "unzip base zip, copy scatter file and linux files into it" folder first?

Do I choose firmware update, or download only in the flash tool ? (confusing names, those).. and unselect all partitions but... which one?

Yours, confused,

Jess


Go to the top of the page
 
+Quote Post
OPDA
post May 27 2019, 05:51 AM
Post #2





Group: Members
Posts: 10
Joined: 16-April 18
Member No.: 821,128



Hi,
yes, it is not that easy. Since I struggle with the update since 1 week, I am not the best, but let me throw in:
It could work that you just use your old scatter file and you just update what is "new" - do you have a rooted android image?
If you hope to just update the system to 8.1 and everything regarding your data stays untouched I am afraid this will not happen when you switch to the new orea plattform. And if it works you will get problems I am sure. But we are not talking about dirty flashing...
You are always on the safe side if you use Titanium Backup, backup everything, and start with a new scatter file (from the new page which now works after 2 weeks) and all the new zips (WIFI gemini, and debian).
The description for multiboot flashing is quite good on their homepage.
cheers, andreas
Go to the top of the page
 
+Quote Post
Jess R
post May 27 2019, 07:27 AM
Post #3





Group: Members
Posts: 12
Joined: 16-June 18
Member No.: 824,577



QUOTE(OPDA @ May 27 2019, 02:51 PM) *
Hi,
yes, it is not that easy. Since I struggle with the update since 1 week, I am not the best, but let me throw in:
It could work that you just use your old scatter file and you just update what is "new" - do you have a rooted android image?
If you hope to just update the system to 8.1 and everything regarding your data stays untouched I am afraid this will not happen when you switch to the new orea plattform. And if it works you will get problems I am sure. But we are not talking about dirty flashing...
You are always on the safe side if you use Titanium Backup, backup everything, and start with a new scatter file (from the new page which now works after 2 weeks) and all the new zips (WIFI gemini, and debian).
The description for multiboot flashing is quite good on their homepage.
cheers, andreas


No, its not rooted, just Standard Android.

I really hope/assume there is a way without splatting everything - it seems like there should be.
Go to the top of the page
 
+Quote Post
Vincent
post Jun 13 2019, 09:37 AM
Post #4





Group: Members
Posts: 5
Joined: 12-June 19
Member No.: 849,826



Basically you can follow this instruction:

http://support.planetcom.co.uk/index.php/A...d_Manual_Update

Yet i noticed i needed a new scatter file, because in the base firmware the filenames had changed. So what i did is:

1) Create a new scatter file exactly like the previous one, in my case with 2 boots, Sailfish 40G and Android 16G.
2) I did a diff between the previous and the new scatter file in order to check that only file names had changed.
3) Then used the new scatter file.

To keep everything as it was, your data, settings and desktops, be absolutely sure to UNcheck "userdata" in FlashTool. In the end you should have everything checked, except 2x boot (only the boot of android must be checked, in my case boot2) and except "userdata".

That worked for me to upgrade Android without destroying anything.
Go to the top of the page
 
+Quote Post
Jess R
post Jun 15 2019, 03:35 AM
Post #5





Group: Members
Posts: 12
Joined: 16-June 18
Member No.: 824,577



QUOTE(Vincent @ Jun 13 2019, 06:37 PM) *
Basically you can follow this instruction:

http://support.planetcom.co.uk/index.php/A...d_Manual_Update

Yet i noticed i needed a new scatter file, because in the base firmware the filenames had changed. So what i did is:

1) Create a new scatter file exactly like the previous one, in my case with 2 boots, Sailfish 40G and Android 16G.
2) I did a diff between the previous and the new scatter file in order to check that only file names had changed.
3) Then used the new scatter file.

To keep everything as it was, your data, settings and desktops, be absolutely sure to UNcheck "userdata" in FlashTool. In the end you should have everything checked, except 2x boot (only the boot of android must be checked, in my case boot2) and except "userdata".

That worked for me to upgrade Android without destroying anything.


Thanks! Just to clarify - that means I need to make sure I use the same sizes for the new scatter file ...
And that won't overwrite the existing linux partition(s) ?

Jess
Go to the top of the page
 
+Quote Post
Vincent
post Jun 15 2019, 11:00 AM
Post #6





Group: Members
Posts: 5
Joined: 12-June 19
Member No.: 849,826



Yes, exactly the same sizes. And afterwards make absolutely sure that the only diff with the previous scatter file are lines with different file names (use a diff tool). If you find more differences, something went wrong with setting "the same sizes".

My Sailfish partition and Android settings were all intact after flashing.
Go to the top of the page
 
+Quote Post
Jess R
post Jun 19 2019, 01:04 AM
Post #7





Group: Members
Posts: 12
Joined: 16-June 18
Member No.: 824,577



QUOTE(Vincent @ Jun 15 2019, 08:00 PM) *
Yes, exactly the same sizes. And afterwards make absolutely sure that the only diff with the previous scatter file are lines with different file names (use a diff tool). If you find more differences, something went wrong with setting "the same sizes".

My Sailfish partition and Android settings were all intact after flashing.


Hrm.. using the new tool, the closest I get is setting 24 GB/32.407 GB - which puts a partition_size of 0x7e8700000 for SYS30, however in my old file its 0x7e7600000 (31.615234375 GB versus 31.6318359375 GB) .. so now I'm tempted to just change them manually in the scatter file..

Go to the top of the page
 
+Quote Post
Jess R
post Jun 19 2019, 01:19 AM
Post #8





Group: Members
Posts: 12
Joined: 16-June 18
Member No.: 824,577



Aha, it doesn't help either, that my initial scatter file doesnt/didnt have a Recovery partition in it, that wasnt available when I created it.. so I've got an extra partition in the new one (and if I re-use the link to the current 7 partition tool, there too).. so I think I may be a bit stuffed in terms of replicating the sizes.. Shame that the new tool doesn't allow Recovery to be optional.

Time to backup /home, /etc and so on, and overwrite the linux part too, methinks.

Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 13th December 2019 - 02:58 AM