Hello, all. I’m new to the forum. I’ve successfully rooted phones before and installed LineageOS, but I’m having trouble with the FP4.
I want to install LineageOS microG on a new FP4 and I downloaded the latest zip files. I installed LOS recovery (and regretted it) and rooted with Magisk.
I then tried to install LOS microG using adb but kept getting a “protocol fault: (no status)” error.
So based on bad info I got on the internet I tried to install the LOS zip file from inside Magisk. Of course it failed, and all it appeared to do was install the LOS boot.img.
After that, my FP4 now randomly reboots.
̶F̶r̶o̶m̶ ̶a̶d̶b̶ I’ve retried
fastboot reboot boot_patched.img
from the FP4 Magisk root procedure but it did not work.
Thanks for the fast support.
I tried to do the “step-by-step” before installing LOS but it still reboots.
I can boot into fastboot. What does installing to to the other slot do?
Ich meinte auch gar nicht zwingend den anderen Slot falshen. Aber wenn fastboot geht, ggfls einfach FPOS installieren und dann neu anfangen, erst LOS drauf dann rooten…oder halt wie von @hirnsushi oben verlinkt LOS neu und dann rooten.
Not sure why I wrote german🙃
So again: i didnt mean to flash the other slot. As long as fastboot works you can always install FPOS and start from scratch wirh LOS and after that root, or follow what hirnsushi stated above and again below.
Are you able to boot into proper Android at all or are you stuck in fastboot? Can you still get into recovery?
And could you please post the output of fastboot oem device-info && fastboot flashing get_unlock_ability
Don’t mess with the slots if you don’t have a good reason to!
If your phone didn’t magically lock the bootloader again (pretty unlikely) you should still be able to just follow the LineageOS install instructions. Whatever you did in the Magisk app don’t try to fix it, just start fresh
I don’t understand Magisk slots so until I do I don’t want to mess it it.
I had tried to install LOS microG using adb but kept getting a “protocol fault: (no status)” error. My fallback was just to use a rooted FP4 with the installed OS. But I’m also using adb31 Windows) because I get errors with adb35.
I’m going to try to install adb35 on a computer that never had adb installed before and see if that works out.
Also, one other thing. If I power down the FP4 from Android using the power key, the FP4 shuts down, then restarts. I have to shut it down by holding down the power button until it turns off.
Thank you everyone for your help. Usually I’m the one providing support so I appreciate everyone’s efforts.
EDIT: Ah, I get it. Each slot is a full bank of flash memory that stores the OS. We do the same thing in embedded systems, you install a new/updated OS to a memory bank (slot) then switch that to the active bank. It’s more reliable than storing the update in RAM. https://source.android.com/docs/core/ota/ab#slots
UPDATE: I installed adb on a Win10 laptop that never had any Android tools installed on it before. I successfully installed LOS microG!
It’s been 20 minutes and my FP4 has not rebooted!!!
My only regret is I wish I had TWRP installed, as I could not find a good guide for installation and many came with bricked phone warnings.
I have a second FP4, can someone point me to a good guide for installing TWRP on FP4? Is it safe to try to install TWRP on my first FP4 that already has LOS recovery?
I want to thank everyone for your support, and I look forward to when I learn enough about this phone so I can do the same here for others.
The TWRP install instructions begin by saying “grab the vbmeta image from the ROM you are on”. How do I get that? Do I extract vbmeta.img from the phone, or download it? Is vbmeta different on my stock FP4 compared to my LOS FP4?
Also, from the FAQ is TWRP not able to access internal and sdcard storage? That would limit its usefulness.
LOS4microG provides it as a separate download but you generally can just extract it from the factory images of the ROM you are using.
Nope, TWRP isn’t really helpful in most cases when it comes to the FP4. I don’t think I’ve needed it in the last two years, not like with older Android versions /custom ROMs.
I wouldn’t replace LineageOS recovery with it, there’s a reason everyone ships their own one now, they aren’t necessarily compatible. You don’t really gain anything but you definitely increase the amount of problems you can run into
Thanks. If TWRP can’t access storage then I can’t apply updates or backups, so its useless - OTOH I can easily do that from adb in recovery. I would like to be able to do a full backup, but I remember adb can do that, too.
I lost root when I installed LOS. What boot.img do I use to regain root?
EDIT: Using my first patched boot.img didn’t work, I had to repatch the boot.img from microG. I now have a rooted FP4 with microG!
That hasn’t been possible for a while, sorry. Since you are rooted something like Neo Backup is an option.
Otherwise Seedvault, which is the default backup solution on several custom ROMs (just called “Backup” in the launcher), plus in app backups for apps it can’t backup yet would be another one.
I’ve spent last night and most of today moving everything from my present phone which was an LG G5 running LineageOS 14.1 to my FP4 - yeah, I know, an old OS but the LG is small which was crucial at the time. I’ve successfully moved most apps over to my FP4.
My last steps are to move
Call Logs
Contacts
SMS
then move the SIM to the FP4.
I used Titanium Backup Pro (TBP) to successfully backup my LG call logs and restore to the FP4. Call logs opened fine in FP4 Phone app.
I then tried to do the same thing with TBP with Contacts. No go! Phone and Contacts apps now crash when I open them. Clearing data and cache on both Phone and Contacts allows the phone app to open, but it crashes when I switch to the Contacts tab.
I tried to restore my call logs to the FP4 using TBP a second time but this time the restore fails. I installed Simple Dialer hoping a new phone/contact app would work but that crashes too.
I’ve belatedly read that using Titanium Pro to move contacts is a bad idea.
I was able to extract all my LG contacts to a .vcf file, but importing the .vcf into my FP4 fails.
I’m thinking that maybe deleting everything in
/data/data/com.android.providers.contacts/databases/
would fix it, but I’ve made enough mistakes improvising so I’m asking here first.
