zupo_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<ehmry>
is anyone else getting wierd failures from aarch64.nixos.community, like "not an absolute path: 'K'"
Asmadeus has quit [Ping timeout: 258 seconds]
Asmadeus has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Client Quit]
rajivr has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
evils has joined #nixos-aarch64
orivej has joined #nixos-aarch64
<sphalerite>
I'm trying to update my phone with a new robotnix-built image (cc danielrf[m] ) but getting "Device version-bootloader is 's5-0.2-6539975'. Update requires 's5-0.3-7062598'." from fastboot update…
<sphalerite>
How do I update the bootloader?
mschwaig has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
zupo has joined #nixos-aarch64
dev_mohe has joined #nixos-aarch64
dev_mohe has quit [Client Quit]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
rajivr has quit [Quit: Connection closed for inactivity]
cirno-1000 has quit [Ping timeout: 245 seconds]
cirno-1000 has joined #nixos-aarch64
<danielrf[m]>
sphalerite: If it is a pixel phone, you can build the `factoryImg` output from robotnix, unzip it, and run `flash-all.sh`
<danielrf[m]>
It includes the bootloader and modem images as well
<sphalerite>
danielrf[m]: awesome! Thanks!
<danielrf[m]>
For reference: If it's not a pixel phone, you'd need to get a factory image from your vendor, flash it, and then possibly update the phone via an OTA update
<sphalerite>
argh. This erased userdata? Was not expecting that D:
<sphalerite>
guess I'll be finding out how well seedvault works then :x
<sphalerite>
add a disclaimer next time ;)
cirno-1000 has quit [Ping timeout: 265 seconds]
<sphalerite>
nooooooooooooooooooooooooooooooooooo
<sphalerite>
crap.
<sphalerite>
crap crap crap crap crap.
<sphalerite>
UGH.
<sphalerite>
I think I might have wiped my backup in the process of trying to restore my backup.
<sphalerite>
:(
<sphalerite>
At least my pictures aren't gone, thank you syncthing
orivej has quit [Ping timeout: 246 seconds]
e has quit [Quit: edk]
<danielrf[m]>
oh dear, sorry about that. I didn't realize you were trying to retain your existing data
<danielrf[m]>
were your running robotnix on it previously?
<danielrf[m]>
The normal way to upgrade would be through `adb sideload` with the `ota` robotnix output
<danielrf[m]>
Since you were using fastboot I guess I assumed you were starting from scratch
monk has left #nixos-aarch64 ["Error from remote client"]
monk has joined #nixos-aarch64
e has joined #nixos-aarch64
<sphalerite>
yeah I was already using robotnix
<sphalerite>
damn. Well, now I know for next time
<sphalerite>
(and I have now also experienced the joys of trying to keep my signal messages after the phone app is gone)
<danielrf[m]>
I'll be sure to add a note to the docs about installing vs. upgrading
<samueldr>
though flash-all.sh is AFAIUI always including that `-w` flag, even on LineageOS downloads
<samueldr>
(not that it doesn't need to be documented)
figgyc has joined #nixos-aarch64
FRidh has quit [Quit: Konversation terminated!]
luxemboye has quit [Remote host closed the connection]
luxemboye has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
julm has quit [Quit: leaving]
<LinuxHackerman>
OK, now that I've actually tested it I can conclude that seedvault is distinctly screwy but still somewhat usable.
<LinuxHackerman>
I did get back my backup after all, which is very nice
<samueldr>
nice!
<samueldr>
any details about its screwedness?
<LinuxHackerman>
Restoring it is a bit "funny" because if you have nextcloud installed as a user app and in the backup, it will try to restore the data into the app while using the app as a restore source, killing itself in the process.
<LinuxHackerman>
It probably has the same problem if you install nextcloud as a system app
alpernebbi has quit [Quit: alpernebbi]
<samueldr>
ooh, I can guess at what is going on
<samueldr>
I assume if you had put the backup on a flash drive, and used that to restore, or even made a copy to your user storage on android, it wouldn't have tripped over itself
<LinuxHackerman>
yeah
<LinuxHackerman>
good to know that the devs test it this thoroughly :>
<samueldr>
I wonder if they even can do anything about it, short of adding code paths for every "file services"
<samueldr>
because of how recent android requires file management to happen "through apps"
<samueldr>
this could happen with any backend
<LinuxHackerman>
Yeah, though local storage and nextcloud are the backends explicitly implemented in seedvault.
<samueldr>
ah, then I guess it would have been appropriate for it to either start with, or end with, the file storage backend
<LinuxHackerman>
Or copy the backup files to be restored fully before restoring them
zupo has joined #nixos-aarch64
julm has joined #nixos-aarch64
orivej has joined #nixos-aarch64
evils has quit [Ping timeout: 252 seconds]
cole-h has joined #nixos-aarch64
dev_mohe has joined #nixos-aarch64
dev_mohe has quit [Client Quit]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]