I will download /e/ now. After that i will keep you posted about my progress or my problems. Thanks so far.
Yeah I think the Librem is slow compared to a newer android or Iphone, and physically itās very 2013ā¦ As for running a rooted phone as a main device I have a Lineage fork and zero Gapps running and it is significantly faster and simpoler than before root.
Itās all about using the right rom and installing and configuring the best apps and Magisk modules. All of which of course takes time, especially if youāre rooting for the first time - which ALWAYS causes panic and much frustration. But a de-googled android set up correctly is the best experience iāve had using a phone.
1 Like
No worries. Iāll be about.
If it all seems to go terribly wrong - donāt panic. Iāve done this many times and only once has it run without a hitch. Iāve yet to face a bricked device that couldāt be rescued
My microSD-card is brokenā¦ So i canāt install /e/
Thereās always a hitch at first. Something always frustrates the install. Maybe try wiping it in TWRP then load the zips again via a computer and place the card back in the phone. worked for me a few times. otherwise give me a shout when you get a new one and if you need help.
You could use a USB OTG as well. I had the /e/ zip on one. Plugged it into the phone and booted into TWRP. In there I chose OTG as the source.
1 Like
What Pebcak said - perfect.
Another option is to sideload using ADB via your computer terminal and the sideload function in TWRP.
1 Like
I tried it and my sd card is dead.
So i tried what you were saying and /e/ is loading.
1 Like
@Buddha
I get this error: https://abload.de/img/screenshot_20210506-1tnk45.png
Ok youāre trying to sideload I take it.
Basics
-
do you have android tools installed on your PC?
-
when trying to to establish aADB connection you must do so as root.
-
howās your usb cable - go toāmountā in TWRP and āmount us storageā while connected via the cable. A connection should be established if the cable is of good enough quality
-
this option of mountiing usb can sometimes kick-start connection and enable sideload connection to function.
-
once connection is ok go to āadvancedā in TWRP and click adb sideload.
Com eback to me if this gets you up and running - top of my head I canāt rememner sideload command as it goes on samsung so Iāll go check
No i donāt have installed android tools on my pc. Which one do i need?
I donāt have any experience with adb and google android tools
instal android tools from the AUR
git clone https://aur.archlinux.org/android-sdk-platform-tools.git
cd android-sdk-platfrom-tools
makepkg -si
Youāre then going to be able to check ADB connection between PC and Android by using the command - ensure youāre in root -
adb devices
if a device identifier shows up youāre golden
[endlich@pc android-sdk-platform-tools]$ su
Password:
[root@pc android-sdk-platform-tools]# adb devices
bash: adb: command not found
[root@pc android-sdk-platform-tools]#
Did i do something wrong?
did android tools install ok? if so make sure the android is in recovery mode. You can also check by using the TWRP mount usb storage and watching for the device to show up in your file manager on the PC
Yeah i installed adb tools successful.
Iām now in TWRP Recovery mode on my phone and have established a connection between pc and phone. I can add and delete files to my phone through file manager on my pc.
But i canāt mark the USB Storage box, itās still not possible to check that.
if connection is established transfer rom zio file to the device - id suggest into the TWRP folder as itās easy to find
I already did that and GApps, too.
Then i wiped the phone and dalvik etc.
Installed /e/ file in .zip file and everything went smooth, but then i get this error shown above in the earlier post.
Flash the zips. Wipe only the dalvik.cache - nothing else once zips flashed
I wiped everything off my phone. Then i transfered e-zip on my phone. Then i installed e and deleted afterwards dalvik cache. Last but not least reboot and installation/setup of e.