Develop Bugs

Bootloop after flashing gapps to any 64bit rom

Model Device: XT1676
Yesterday I unlocked the bootloader, the message "ID: bad key" appeared when the phone was started. I ignored this, I flashed the 64bit twrp and here the problems start - I've tried many roms:
- FireHound v4.5,
- AospExtended v5.4,
- BootleggersROM 2.2,
- dotOS 2.1 and 2.2,
On all roms (except for dotOS 2.1) the same problem appears - the system itself works and starts correctly, but when I flash any version of Open Gapps the phone falls into the bootloop, the exception is dotOS 2.1, it works fine, but there are not many functions has dotOS 2.2, interestingly - when I flash dotOS 2.1, gapps, run the phone and then I do flash update to 2.2, everything works fine, but I would like to use another rom, but all have the same problem, does anyone know how I fix it?
And as for "ID: bad key" - I can not even relock the bootloader and unlock again (I read that helps), because the phone has a bootloader with the NPPS25.137-93-8 stock version, which even can not be downloaded anywhere, and the flash attempt of the older stock is canceled due to the older security patch.

The message bad key is normal - you can replace the splash screen if you want
Make sure you have formatted data
Some roms require a certain type of gapps - if it's a 64bit rom make sure you are using 64bit gapps
Check thread 1st post and user comments for any information on this
Some users have reported booting the rom first without gapps then Data wipe only then flash rom & gapps again
You can also try disabling the welcome screen on first launch
In twrp, mount /system, go to advanced, terminal and type
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop

TheFixItMan said:
The message bad key is normal - you can replace the splash screen if you want
Make sure you have formatted data
Some roms require a certain type of gapps - if it's a 64bit rom make sure you are using 64bit gapps
Check thread 1st post and user comments for any information on this
Some users have reported booting the rom first without gapps then Data wipe only then flash rom & gapps again
You can also try disabling the welcome screen on first launch
In twrp, mount /system, go to advanced, terminal and type
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
Click to expand...
Click to collapse
Booting the rom first without gapps then Data wipe only then flash rom & gapps again didn't help, I use the latest arm64 gapps but I still have a bootloop on almost all the latest roms, disabling setupwizard didn't work - The only roms that work for me are those from before April.
EDIT
I downloaded the build.prop through ADB, edited it over the computer and sent it back to the phone - it helped, thanks for the advice.
Thread to close.

Wanted_X2 said:
Booting the rom first without gapps then Data wipe only then flash rom & gapps again didn't help, I use the latest arm64 gapps but I still have a bootloop on almost all the latest roms, disabling setupwizard didn't work - The only roms that work for me are those from before April.
EDIT
I downloaded the build.prop through ADB, edited it over the computer and sent it back to the phone - it helped, thanks for the advice.
Thread to close.
Click to expand...
Click to collapse
how did you get build.prop by adb? in twrp? what commands? thanks

durc12 said:
how did you get build.prop by adb? in twrp? what commands? thanks
Click to expand...
Click to collapse
Yes, I used ADB, commands:
to download build.prop - adb pull /system/build.prop
after edit, to push file into device:
adb push build.prop /system/
adb shell
cd system
chmod 644 build.prop
There is full tutorial: www.ultimatetech.org/edit-build-prop-file-android-withwithout-root/

Wanted_X2 said:
Yes, I used ADB, commands:
to download build.prop - adb pull /system/build.prop
after edit, to push file into device:
adb push build.prop /system/
adb shell
cd system
chmod 644 build.prop
There is full tutorial: www.ultimatetech.org/edit-build-prop-file-android-withwithout-root/
Click to expand...
Click to collapse
I install the rom, then the gapps, but it says to me that no build.prop is ther with the pull command, I don´t know why
EDIT: finally I did it, but it was neccesary to mount /system in twrp, to check the box in "mount". Thaks for all

[ROM] LINEAGEOS [Android 11] [OFFICIAL] [Nightly]

I'm not sure why no one has posted this on here yet. I see the unstable google drive linked Android 11 Lineage but not the official download links and instructions...
i run this rom on my daily driver.
here is the link:
https://download.lineageos.org/walleye
the instructions are what you should foolow as they know alot more than me about all this but they say to temp flash the recovery, that has never worked for me.
WARNING!!!
IT IS NOT RECOMENDED BY LINEAGE TO USE GAPPS, AS SOME OF THEM WILL OVERWRITE/REMOVE OPTIMIZED LINEAGEOS SYSTEM APPS, AND REDUCE SECURITY/STABILITY!
THE SYSTEM WORKS JUST FINE WITHOUT GAPPS BUT IF YOU CHOOSE TO USE THEM LIKE I DO HERE IS THE INSTRUCTIONS I FOLLOW:
-----------------------------------------------------------------------------------------------------------------------
1. remove password on system
2. copy the downloaded system zip to sdcard
Google usb driver found here: https://developer.android.com/studio/run/win-usb
3. adb reboot-bootloader
google platform tools adb & fastboot found here: https://developer.android.com/studio/releases/platform-tools
4. fastboot boot [twrp]
do not allow modifications, do not change any settings and do not install twrp to recovery
Twrp found here: https://dl.twrp.me/walleye/
5. install [Lineage.zip]
sometimes you can sideload this pkg but others not so i just send it to the sdcard and install from there in twrp, ive had issues with usb 3.1 ports with system pgk but not with gapps.
6. reboot to bootloader and fastboot boot [twrp]
if you do not do step 6 the boot slot will not be correct for installing the gapps and will not be able to boot the system
7. adb sideload [gapps-core] and then adb sideload [addons] (without booting system before all gapps installed)
i get these from here: https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-R/
i only do the core first, then i have a short batch file sideload all the addons i want from here:
https://sourceforge.net/projects/nikgapps/files/Releases/Addons-R/ choosing which ones i need because there is not always enough space.
the ones i sideload in order are named like this [NikGapps-Addon-11-*-signed.zip] below:
GBoard
Gmail
GoogleClock
GoogleContacts
GoogleDialer
GoogleMessages
GoogleCalculator
GoogleCalendar
GooglePhotos
Velvet
GoogleChrome
GoogleFi
GoogleTalkback
GoogleTTS
8. reboot system, and let boot up.
9. adb reboot-bootloader
enable usb debugging first
10. fastboot boot twrp
if you wanted to install twrp to system as recovery do it before magisk at this step.
11. adb sideload magisk.zip
magisk.zip is the magisk.apk, just rename the apk found here: https://github.com/topjohnwu/Magisk/releases
12. reboot
If magisk doesn't seem to want to work at this step:
open app while online, reboot, test again, if still no:
adb install -g [magisk.apk]
did i do something wrong? miss something? want me to take this down? make this better?
any feedback is welcome as this is mainly because i've spent many hours trying to figure all this out so i hope it helps someone.

The original post it's at Pixel 2 XL forum

Tony Ronaldo Matute said:
The original post it's at Pixel 2 XL forum
Click to expand...
Click to collapse
why, because the walleye and taimen kernel merge?
link please?

Solomon M said:
why, because the walleye and taimen kernel merge?
link please?
Click to expand...
Click to collapse
Here is the link
[ROM][OFFICIAL] Lineage OS 18.1 for Pixel 2 / 2 XL
When will it be getting official and updated to December patch?
forum.xda-developers.com
Maybe you can ask permission to @Eamo5 for make thread in P2 session

kurokuroninja said:
Here is the link
[ROM][OFFICIAL] Lineage OS 18.1 for Pixel 2 / 2 XL
When will it be getting official and updated to December patch?
forum.xda-developers.com
Maybe you can ask permission to @Eamo5 for make thread in P2 session
Click to expand...
Click to collapse
Oh! This is a duplicate. My apologies.
I'm not sure how to delete this. Also maybe they should post in the Walleye form instead of the other to help people find walleye related roms or rom info.
Whoever decided to put all walleye stuff with taimen just because they are both wahoo is dumb.
That's like saying let's put all the phone a with b just because some of it is the same. If they where the same then at least they would both be made by the same hardware manufacturer LG != HTC nor vice versa.

Solomon M said:
Oh! This is a duplicate. My apologies.
I'm not sure how to delete this.
Click to expand...
Click to collapse
Thread has been closed.

Fairphone 4: remove Google Apps (microG)

This is a copy of my question on SO.
I want to remove Google apps and services on a new Fairphone 4 (Android 11, now rooted using Magisk. No TWRP build available yet.).
To this end, I am trying to use microG. In the Prerequisites for its usage, signature spoofing and deleting files in `system/priv-app` are listed. For signature spoofing, I followed the *XPosed solution for Android 11 and 12* listed here, i.e. using Magisk + riru + LSPosed + a FakeGApps fork. Not sure, whether or not this worked. All individual steps reported success, but the Signature Spoofing Checker says it didn't work.
Anyway, I'm definitely stuck at the second step, because I don't seem to be able to delete any files in `system_ext/priv-app`. I tried the solutions proposed here and here.
If I try
Code:
adb shell
su
# then confirm on the phone, then
mount -o rw,remount /
I get '/dev/block/dm-0' is read-only. Similar error (with dm-1) if I try mounting /system_ext.
adb root or adb disable-verity don't work, because it's a user build: adbd cannot run as root in production builds, verity cannot be disabled/enabled - USER build.
I even tried to write a Magisk module to replace the directories in question with empty ones, by putting the following in the customize.sh:
Code:
REPLACE="
/system_ext/priv-app/GoogleFeedback
/system_ext/priv-app/GoogleOneTimeInitializer
/system_ext/priv-app/GoogleServicesFramework
/system_ext/priv-app/SetupWizard
/system/system_ext/priv-app/GoogleFeedback
/system/system_ext/priv-app/GoogleOneTimeInitializer
/system/system_ext/priv-app/GoogleServicesFramework
/system/system_ext/priv-app/SetupWizard
"
I think /system/system_ext and /system_ext are hard linked, but not sure whether that matters. After loading that module and rebooting, the contents of those folders are still the same when checking with adb shell.
Any ideas?
For adb I'm using my desktop with Ubuntu 21.10.

Hello,
It's way easier than you can imagine. I did a tutorial there : https://forum.fairphone.com/t/tutorial-install-microg-on-fairphone-os/80016
But as you are quite advanced, the only thing you have to do is to install NanoDroid-MicroG with Magisk : https://downloads.nanolx.org/NanoDroid/Stable/
Just install the Zip and eventually update MicroG on the official website (version packed in NanoDroid is 17, newest one is 22...). This will erase all old Gapps.
PS :signature check spoofer don't work, the package you mentionned (which is the one I use also) only fake signature for Gapps, which is a good thing...

Thanks a ton! Looks like it worked, and it really wasn't more than installing that one module

Better use an ungoogled OS like LeOS-S. It's Android12L and works great an FP4
See https://leos-gsi.de

Gapps in last version LineageOS

Sorry for my English. I have Xiaomi mi8 with last LineageOS. Into root folder of phone I put zip gapps file. But when I turn my phone to fastboot and than to TWRP, I can not find my zip file with gapps. The structure of folders is different than when phone is connected to PC. Maybe you know what to do with it please?

As far as I remember you can/must select the storage, including sdcard (which I prefer to use).
PS: Ahoi

Phone does not have external storage card extension. No, prostě když ten telefon připojím k počítači, je tam určitá struktura složek. nahraju tam zip. Pak dám fastboot, dostanu se do TWRP a dám install a už tam je úplně jiné složení složek a zip nemůžu najít

oh, actually I know only 3 czech words: ahoi, knedliki and staropramen
anyway, in TWRP you can select the storage (bottom left, i think). (gtranslate: v TWRP si můžete vybrat úložiště (myslím vlevo dole).)

I know I can select the storage. But, it is impossible to find my zip file The structure of folders is diffrent than the structure I can see when phone is connected to PC for file transfer

A) Maybe a fast workaround: Use an USB OTG adapter and plug-in some USB stick with the files?
OR
B) In modern Android, there are several partitions and my guess is, that you have the files on another.
So you could study some search results for "android partition layout" like p.e. https://source.android.com/docs/core/architecture/bootloader/partitions/system-as-root

FRQD75 said:
A) Maybe a fast workaround: Use an USB OTG adapter and plug-in some USB stick with the files?
OR
B) In modern Android, there are several partitions and my guess is, that you have the files on another.
So you could study some search results for "android partition layout" like p.e. https://source.android.com/docs/core/architecture/bootloader/partitions/system-as-root
Click to expand...
Click to collapse
I will try it and inform you here I have to order usb otg. Thanks

OK, I installed​MindTheGapps-12.1.0-arm64-20220605_112439.zip​from USB otg adapter. But Gapps are falling. They are in phone, but I can not start them.

Hello guys,
I believe that I faced a similar case.
I am using MI8 pro, and I installed lineageos 20 with mindthegapps for Android 13. The Google services keep stopping.
Then I tried lineageos 19 with mindgapps 12.1 arm64. The same failure is reported.
I am totally confused. I used adb sideload way to install the os image and gapps without interrupt.
Is there any idea in my case?
Regards,

illidanpc said:
Hello guys,
I believe that I faced a similar case.
I am using MI8 pro, and I installed lineageos 20 with mindgapps for Android 13. The Google services keep stopping.
Then I tried lineageos 19 with mindgapps 12.1 arm64. The same failure is reported.
I am totally confused. I used adb sideload way to install the os image and gapps without interrupt.
Is there any idea in my case?
Regards,
Click to expand...
Click to collapse
Today, I tried LiteGapps Nano arm64 13.0 v2.8 official version, based on LineageOS 20. However, it still didn't work on my MI 8 pro. (For the people didn't fimilar with LiteGapps, it's another popular Gapps version, as well. )
But if I only sideload the LineageOS 20, it's perfect running.
So the issue could be related with the compatible of Gapps.

illidanpc said:
Today, I tried LiteGapps Nano arm64 13.0 v2.8 official version, based on LineageOS 20. However, it still didn't work on my MI 8 pro. (For the people didn't fimilar with LiteGapps, it's another popular Gapps version, as well. )
But if I only sideload the LineageOS 20, it's perfect running.
So the issue could be related with the compatible of Gapps.
Click to expand...
Click to collapse
Today i tried a new gapps named BiTGApps, which works fine with LineageOS20. The url of BiTGApps homepage is bitgapps.github.io. The "works fine" means the google login service in setting menu, and google play works fine. There's no more gapps installed which is a minimal setup, i believed.
I used adb sideload way to install bitgapps, even the powershell terminal shows error, but it seems didn't affect the result.
I hope this one would help you, either.

Development [ROM][13][UNOFFICIAL][alioth] PixelExperience for Redmi K40/Poco F3/Mi 11X [AOSP]

Hello,
After a lot of work done by lzgmc, jayanthk and after some tests, I have built an unofficial continuation of PE for alioth.
Motivation:
- I have the device and wanted to have last security patches
- I want to have Netflix, Google Wallet, McDonald app working
- because of lzgmc's and JayanthKandula's hard work, needed changes were reduced to minimum
Changes:
- Updated binaries from the most recent global alioth image
- All updates from PixelExperience, including security updates
- Share the same kernel as munch
Changelog:
05.2023
- small kernel updates
- small performance and ui tweaks
04.2023
- use updated drivers from the most recent version of MIUI Global 14.0.4.0
- use current 4.19 kernel instead of old one
- performance and ui tweaks
Images:
PE - Alioth - Google Drive
drive.google.com
Sources:
https://gitlab.com/lukasz1992-pe/
Instruction:
- you have to flash 05.2023 full image first, if you were on different image
For every next incremental update:
- allow system to boot after flashing
- then reboot to recovery
- flash incremental update
FAQ:
Q: Do you have the device?
A: Yes, I use my ROM on my device
Q: How to report bugs?
A: Write about them here
Q: I do not trust your builds
A: No problem, build image yourself from source or just do not use this rom
Q: What about official support?
A: My ROM is not official (depsite OFFICIAL in name of images). There is already an official maintaner, but has not released images yet.
Q: Why automatic updates are not working?
A: Because alioth is not officially supported, I support it unoficially. Maybe I add updates to my repo.
Q: Why do you publish incremental updates
A: They take less space on my Google Drive and are easier to flash
Q: I want to install 05.2023 (and newer) images directly
A: Flash 04.2023 version first, then install incremental updates one by one (as described in description above)
Q: Incremental update does not work
A: Make sure you are on the correct image, follow the order and allow to boot system after each flash (do not try to flash >1 image without reboot)
Q: Is this a vendor-boot ROM?
A: No
Q: Is there any guarantee?
A: xD

You accidentally used the Question-tag for this thread

Hi, I'm on the 20230420-1753 build but when I try to adb sideload the from-20230420-1753-to-20230516-2127 update I'm getting this error, I'm using the provided recovery image:
Code:
Supported API: 3
Finding update package...
Installing update...
Step 1/2
Error applying update: 20 (ErrorCode::kDownloadStateInitializationError)
ERROR: recovery: Error in /sideload/package.zip (status 1)
Install completed with status 1.
Installation aborted.
I also tried with OrangeFox Recovery, I didn't get this error there but upon reboot I noticed that my version number didn't change.
Also, thanks a lot for keeping PE on the Poco F3 alive, I briefly tried MIU14 but I found it too bloated for my taste.

Could you enable ADB, dump the log from /tmp/ and paste it to pastebin?
Please also confirm you do not have magisk etc.?

lukasz_m said:
Could you enable ADB, dump the log from /tmp/ and paste it to pastebin?
Please also confirm you do not have magisk etc.?
Click to expand...
Click to collapse
Sure, here they are: https://pastebin.com/M5kvav40 https://pastebin.com/VRkbgbvh
I also don't have magisk or anything like that installed.

[DELETED]

Okay, released a new, fixed update - I tested it, it should work

I flashed the new update and its been working fine, thanks for you work!

I flashed the full image on GDrive linked above - thanks very much, works really well. But I think I'm being a blind and can't see the May update? Where do I find that...

Everything okay with your eys. We have some defects with may update again Currently not repaired yet, will publish it when I am sure everything works.

lukasz_m said:
Everything okay with your eys. We have some defects with may update again Currently not repaired yet, will publish it when I am sure everything works.
Click to expand...
Click to collapse
Ah great, thought I was asking a stupid question
Thanks for all your work - had semi-retired my F3 and just bumped it from 12 to 13, its really fast and smooth.

Update - 2023.05 image was reuploaded

Sorry if this is a noob question. Is it possible to dirty flash to this 2023.05 from the latest official build?
And thx for keeping this device updated, really appreciate what you're doing here.

hi, yes - you can do it

Hey Lukasz,
thanks for this work you are doing for all of us.
I I'm on last OFFICIAL PE build from lzgmc and I'm tying to dirty flash with ADB your ROM.
I receive this error whenever I run the ADB sideload comand but Maybe I did something wrong...can you help me ?
Thanks in advance
My version is:
PixelExperience_alioth-13.0-20230119-0644-OFFICIAL
Enabled ADB.
Now send the package you want to apply to the device with "adb sideload <filename Supported API: 3
Finding update package...
Installing update... Step 1/2
Error applying update: 7 (ErrorCode::kInstallDeviceOpenError ERROR: recovery: Error in /sideload/package.zip (status 1)
Install completed with status 1. Installation aborted.
@lukasz_m

It happens when update was interrupted. I do not remember exact names, but please do from ADB:
mount /dev/block/by-name/metadata /metadata
rm -rf /metadata/ota*
reboot to recovery and try again

lukasz_m said:
mount /dev/block/by-name/metadata /metadata
rm -rf /metadata/ota*
Click to expand...
Click to collapse
Sry Lukasz but I don't understand how to run these commands.
I'm surely missing somethig, so it's my ingorance.
I boot the phone and connect it to my pc. I run the "adb devices" command from the platform-tools folder using "command prompt" as administrator.
I get this so ADB is running properly:
List of devices attached
506a3bf9 device
Than what I have to do ?
thanks in advance for your time.

ciottaciotta said:
Sry Lukasz but I don't understand how to run these commands.
I'm surely missing somethig, so it's my ingorance.
I boot the phone and connect it to my pc. I run the "adb devices" command from the platform-tools folder using "command prompt" as administrator.
I get this so ADB is running properly:
List of devices attached
506a3bf9 device
Than what I have to do ?
thanks in advance for your time.
Click to expand...
Click to collapse
First open a shell on your device by entering on your PC: adb shell
Then then you can give shell commands like in the posting above

blonderulez said:
First open a shell on your device by entering on your PC: adb shell
Then then you can give shell commands like in the posting above
Click to expand...
Click to collapse
OK thnaks for the explanation...
After giving "mount /dev/block/by-name/metadata /metadata" command i get:
"mount: bad /etc/fstab: No such file or directory"
When I try to browse it with "cd" and "ls" commands i can browse till /dev/block/by-name/ and I see metadata folder with "ls" than when i go for "cd metadata" i get this "/dev/block/by-name/metadata: Not a directory"

Does this work?
Code:
mkdir /tmp/metadata
mount /dev/block/by-name/metadata /tmp/metadata
rm -rf /tmp/metadata/ota*