@paulakreuzer: No, didn’t help. Now, I made a factory reset via BIOS (holding volume up and power during boot). Ok, all my apps and settings are gone, but I have Google apps again …
Fairphone Updater still crashing. I have to reinstall all my stuff again (thx, I made a backup before).
But, seriously, this update is screwed. I’m very disappointed.
Hello @jopi79,
Given you “played” with modifying the partition layout you might be aware of the dangers here. We have carefully rearranged the partition layout of the “1G13G” builds and the unified partition to ensure that the system partition (containing most of the code) does not change location and size. This allowed for a 2 step re-partitioning where the first step is similar to a normal update (and the system partition gets written first). The second step of the process is the partitioning after an initial reboot.
We can not support people who changed their partition because of the above process(it requires a certain partition layout to start with). If you have ideas how we can help you we can try.
Changing the partitions like this is challenging but it allows us to provide a OTA partition upgrader. The current problem we have with the partition upgrader is caused by plain lack of testing(We tested the upgrader but did not test gapps installation after that).
@keesj For people who ‘played’ with their partitions and are stuck now or in the future: if you use the unbrick/flash route you will reset your partitions layout to the FP1U compatible layout, which should mean less problems in future updates.
On a side-note: Are people who use Unified able to see their internal storage when connected normally to a pc? Or external SD only? Or is this just a quirk for people like mee who have a FP1 original and used Meteos and flashed to FP1U?
If you did the unified partition the content will no longer be exposed over “mass storage”. However it will get exposed as MTP devices and depending on you OS you might not even notice the difference. Perhaps a forum search will help here!
@daveboschma & @keesj I would just like to remind: I and others have not played around with partitions and still we’re stuck as we’re unable to flash any OS after installing only Storage Upgrader manually according to official fairphone manual install site coming from 1.6 old partition layout. I hope that this can be fixed otherwise we’re quite lost although we have tried to follow as close as documented the official Fairphone install recommendations.
Kees, the issue here is that the Recovery Console does not see the /sdcard storage any more and therefore cannot install any OS (or whatever) sent to both internal or external storage.
@Amber I am painfully aware that you followed the official route and still got stuck.
@keesj Thanks for you’re quick reply, will try the MTP-mode in future.
Hello Amber,
We have identified the problem(recovery not being flashed) and fixed it on a soon to be released partition upgrader. We are now working on a fix for the current users who already did the upgrade.
Thankfully the Updater App came back - this time it all went through fine and it updated along with Google apps.
Thank you
Hi all,
Our software team fixed the issue and the Storage Upgrader 1.8.5 is back online - through the Fairphone Updater app and as a manual download.
For the users that are affected by the issue introduced in the previous Storage Upgrader; we are still working on solution for you.
Cheers,
Rick
@daveboschma , when I connect the FP to my pc, I also only see my external SD-card and not internal storage anymore. I did before I ran the manual storage updater.
On the phone itself I see both.
Hi @megalies,
try the following:
When you connect your phone with a USB cable, you’ll get a notification saying “connected as XXX device” Pull down the notification bar, tap the message “connected as XXX device, touch for other USB options” and you’ll see a menu. Choose “Media device (MTP)”
If you’re on Windows (7 or 8), your phone should show up immediately as FP1. If you use Mac, see here: https://fairphone.zendesk.com/hc/en-us/articles/200913399 . If you’re on Linux, see FP, Linux and MTP file transfer for various solutions.
@kgha
I had the same issue, no more internal storage visible on my PC, when connecting my Fairphone.
Thanks to your solution I got it back.
Thank you.
Hello,
I have successfully update from 1.6 to 1.8.5, everything went well, but since the update, my phone keeps looking if there are new updates. How do I stop that ?
Thank you
I have “played” with the partitions of my FP1 and so I’m not able to install the latest software update because of the “cache too small” problem.
So after reading lots of advices in a bunch of forums, I decided to follow jopi79’s and daveboschma’s instructions. But I have screwed it… totally.
I downloaded the “storage 1.8.5” and installed it from internal SD, wiped cache and data and rebooted. Since then my phone only shows the blue screen with no text. After a while “loading” is displayed, screen goes black and blue again. Nothing else happens. It seems to continuosly reboot…
Any idea how I could fix it? Is there a chance to bring it back to live or is it broken?
What is storage 1.8.5? is this the storage upgrader? If this is the case most likely the second stage formatting is failing and this results in a reboot loop.
Can you still enter recovery by pressing volume up + power ?
Hi Paul,
I have the same problem mentioned here (not enough cache space, Update not finishing and Google Apps missing). I know you mentioned there would be a solution soon but that was three days ago so I’m wondering if there is a new solution yet that I have missed or if I should continue to wait.
Apologies if this is repetitive of 100 other people’s posts and questions but I just thought I’d check in directly to be on the safe side. Thanks in advance.
Angela
Yesterday the Fairphone team fixed the Storage Ugrade and re-released it but people, like you, that allready have theese problems have to wait a bit longer.
For the record I’m not a Fairphone employee. As a moderator I’m part of the forum community like you, so I don’t know more than what the FP team posts on the forum.
Angela,
Did you also choose to perform the “storage upgrader” or did you just follow the normal release cycle? How do you know you have a “not enough cache” problem?