Installation worked now under Windows 10. I also believe that the Platform Tools of Linux installed from the repository were outdated.
In the beginning Windows fastboot did not find the installation files but I remembered that they must be included into the same file were adb is situated.
One of you gave this info in the past in this or in the /e/-forum. Think it was Ingo.
After unzipping you have to open IMG-e-0.9-p-2020042851613-dev-FP3 and to copy the 10 individual .img-files into the file of adb. This file was on my computer under windows (c:) Programme (x86)- Minimal ADB and Fastboot.
Now I hope to enjoy my new /e/!!!
Everything I tested up to now works well. Even LTE works out of the box. For FP2 and FP3 stock ROM is was necessary to correct APN.
But one question:
Last step on installation /e/ was:
" fastboot flashing lock
The last command will ask you to confirm on the device to lock the bootloader. Select LOCK THE BOOTLOADER with Volume + and valid with Power."
Did this but on reboot found in the Developer options that OEM lock is allowed.
If I swipe this in the Developer Option to “not allowed”
What will happen? Would this brick the phone and I could not go back at a later stage to stock ROM?
the state of the bootloader: can be “locked” or “unlocked”
the developer option to allow the bootloader to be unlocked: can be allowed or not allowed
So after fastboot flashing lock you have locked your bootloader but anyone booting the FP3 in fastboot can unlock again.
If you don’t want anyone to unlock the bootloader, you should disable it in the developer options.
Later, when you feel the need to unlock the bootloader again, you can come back to the developer options and set it to allowed.
Change from stock to /e/ Android 9 went without problems under Linux Mint. Bootloader is unlocked.
Upgrade with same computer to /e/ Android 10 resulted already with the first command in following error:
~$ fastboot -w
Invalid erase-block-size 512: must be a power of 2 and at least 4096.
Invalid logical-block-size 512: must be a power of 2 and at least 4096.
mke2fs 1.45.5 (07-Jan-2020)
/tmp/TemporaryFile-Cr5SDk: Nicht implementierte Ext2-Bibliotheksfunktion beim Erstellen des Superblocks
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
Does anyone has an idea?
Did install directly from Google as I know that ADB in the Linux Repo is not always up to date.
What is funny for me: From stock to /e/ under Android 9 there where no problems at all even with old ADB from Mint repo.
May be confusing but I changed in May from Stock to /e/ with problems. You are right. Than I changed again back to stock. Some weeks ago for testing again to /e/ 9 and this went with Standard repository ADB Linux very well. Was the quickest install ever. Now I tried to go from /e/ 9 to 10 and had the same problem as in May. First try was with Standard Repo ADB and then with new Google download ADB. I also deleted the old ADB prior to installing new one.
Anyway, I was busy the whole day but this afternoon I will try Win ADB (New download)
I am now completely frustrated. After many hours and with win 10 installed /e/ and locked bootloader again but after several reboot-attempts e did not start. I am now a prisoner in recovery mode and this with locked bootloader. So it seems I cannot install any OS or TWRP. Hope that I did not brick my phone!
Could it help to go back to stock ROM due to the locked bootloader and then if stock is installed unlock bootloader again and install any custom ROM?
That sounds as if the “Minimal ADB and Fastboot” installation does not contain the mke2fs binary.
IIRC nowadays the suggestion is to just install the latest official “platform-tools” package from Google.
Thanks for your help.
After 2 days hard work /e/ Android 10 is running!!!
I have to admit that the big problems are not caused by /e/ software directly but by 3 reasons:
Tried to flash with Linux. Currently there seems to be a bug within adb/fastboot. Use Windows until further notice. Hope it will run in future under Linux.
Did not use the latest platform-tools. Even under Win Minimal ADB and Fastboot is very old and not suitable. Always download latest platform-tools (do not use Minimal ADB and Fastboot) as adviced by Ingo and AnotherElk.
I made a very severe mistake and continued installation after receiving the info:
" fastboot -w
CreateProcess failed: Das System kann die angegebene Datei nicht finden. (2)
error: Cannot generate image for userdata"
All further commands work (that is the problem!!!) and also lock bootloader but then the system does not start.
This resulted in a completely unusable phone with locked bootloader and I had the impression that it is bricked. With your help I unlocked bootloader again.
After 2 days “try and error” I found a solution by chance:
a) installed the new
This is a very effective and lightweight recovery. With this recovery is was possible to delete and format.
Then back to /e/ it was no problem under win 10 with latest platform-tools to execute commands :
fastboot -w and all other commands.
Hint: You should always copy and paste commands to avoid any typing errors.
I now belong to the happiest people of the world as my FP3 is working again
I didn’t have problem to flash /e/ Q with linux (opensuse Leap 15.2) and in the /e/ forum I’m pretty sure there were others who were able to successfully flash it with linux.
True, if someone has access to both OS and it doesn’t work on one, it might be an idea to use the other.
But I wouldn’t advice against linux in general. Otherwise people could refrain from trying to flash /e/ when they simply have no windows machine around.