the default on Ubuntu 14.04:
simon@vmubuntu1404:~/fairphone_os$ gcc --version
gcc (Ubuntu 4.8.4-2ubuntu1~14.04) 4.8.4
Should work according to the build instructions…
the default on Ubuntu 14.04:
simon@vmubuntu1404:~/fairphone_os$ gcc --version
gcc (Ubuntu 4.8.4-2ubuntu1~14.04) 4.8.4
Should work according to the build instructions…
I’ve been “giving” it one hour now, but still …
How did you flash? Where? What? Can you post details?
I used the Docker-File jftr recommended.
after 24 hrs or so, it said build was successful (or something like that).
Then I flashed in a terminal with fastboot flash boot boot.img etc.
I am using Debian Jessie, with Mate DE.
So you flashed outside docker … with fastboot flashall? Was all that successful? Maybe your are still stuck in fastboot/bootloader? What’s on your screen if you switch the phone on?
My out dir looks like this right now, does yours look similar?
15M boot.img
13M cache.img
5,6M dt.img
4,9M persist.img
2,7M ramdisk.img
1,4M ramdisk-recovery.img
14M recovery.img
6,0M splash.img
426M system.img
137M userdata.img
fastboot flashall brought an error message:
neither -p product specified nor ANDROID_PRODUCT_OUT set
so I flashed only boot system and recovery
How do I flash WITHIN docker?
Yes the out dir is about the same. sizes differ slightly.
and there are some more files:
android-info.txt
boot.img.nonsecure
clean_steps.mk
emmc_appsboot.mbn
aemmc_appsboot.raw
EMMCBOOT.MBN
installed-files.txt
kernel
recovery.img.nonsecure
I know that the phone is not stucked in fastboot (because fastboot doesn’t recognize it) and I also can boot into recovery and restart from there. But it is still hanging on the fairphone logo
Don’t! I just wanted to make sure.
Does “fastboot flash system system.img
” tell you the same? That’s all that comes to mind here. ;(
no.
fastboot flash system system.img
finished without any error messages (just OKAYs and finish time)
Do I have to flash one of the other files as well, maybe?
No. Only the three (boot.img, recovery.img, system.img). Can you do them one by one? Just to see if there is an error message? I don’t have any more ideas here, sorry.
But if those already went through fine, maybe just leave it like that and try a: fastboot -w flash system system.img
:add-shrug-smiley-here:
That’s what I did.
I also tried out the modified boot.img with supersu.
Sorry, there is nothing more I can recommend. But you can still use the recovery to reinstall the OTA right?
sorry, what does OTA stand for? and where do I get that?
I can access the recovery.
Just if all else fails you can use it to reinstall the FP2 stock software back onto your phone. The thread is a bit confusing to read, but it looks like it worked.
Thank you for the link.
Maybe I have to reflash before I send my phone back, bcz I really do not want to have gapps on my phone
If you not in a rush to return the phone … maybe someone else will haven an idea in the meantime. It worked before
Also, I assume you copied all the libs around and the stuff like described in the HOWTO, right? You used docker, so I guess yes, but … sometimes a script can fail for strange reasons … Maybe some logcat logs will help, if available, not sure what state your phone is in after booting …
I have one more week before the phone must be returned.
For building I just followed the (very easy and short) instructions for the docker file.
For a better description of the phone’s state:
How would I find logcat logs?
Good descriptions. I hope someone can use them to help you better. If your phone accepts adb devices
you could try adb logcat
or adb shell
afterwards to see what’s going on inside. Not sure about the default settings in the rom regarding usb debugging. I hope someone else can fill in the blanks here (build properties for debugging are set, right?).
The recovery looks broken, too.
at the bottom it says
“E:Can’t open /dev/block/platform/msm_sdcc.1/by-name/misc
(Permission denied)”
That’s actually nomal. I’ve had it from the start and everythings workd fine for me…
Hei
As you can see from my other posts, something must have gone wrong. My system doesn’t start (yet fastboot mode and recovery seem to work).
How do I restart the compiling process with the Docker image? (best would be without downloading 30GB one more time)