yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] razorloves:
not sure how some of you are ending up with messed up gps.

gps has been working fine for me in multiple apps.

using mindthegapps.

according to a log someone sent me with gps not working, the permissions on the Google Play Services app is broken. this can happen from not installing gapps properly.

if your gps isn't working do these adb commands. should fix it.

adb root

adb shell pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION

adb shell pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION

adb shell pm grant com.google.android.gms android.permission.ACCESS_BACKGROUND_LOCATION

then reboot.

if it still doesn't work, send me a pm with logcat showing the problem.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jkl7878:
You're right, it's because I didn't follow your initial GApps installation procedures exactly. I factory reset it and followed your directions and it's working now. Thank you!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] faheyd:
Just used the Lineage Updater on phone and updated from 18.1 5May2021 to 18.1 18May2021 build. All went smooth and reboot successful. Thank you !
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] FcukBloat:
yeah cool i didn't know we could update ota without twrp available! great it worked here too :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] zimral.xda:
haha commercial phone manufactorers dream about that full featured updater since early ages of android. I switched from TWRP to LOS recovery as i started using 18.1 on my Pixel2 and my Galaxy S5. OTA updates running very smooth with LOS recovery. I still use a 3rd phone a Pixel 3 for business usage. As soon as it will run out of support this winter, i will flash LOS to extend its life and to support this wonderful project.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] razorloves:
ota updating doesn't involve the recovery at all, on devices with a/b slot partitions. never has.

the update is installed while in android (to the other slot). same as on stock rom.

this is not a new thing. lineage has been doing it for a few years. since google implemented it in aosp. started with first gen pixel.

so it doesn't matter what recovery is installed.

A/B (seamless) system updates | Android Open Source Project

source.android.com
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] zeppelin03:
Thanks for putting this together. I'm excited to have a phone updated beyond Google's arbitrary cutoff.

The one issue I've encountered is that bedtime mode in digital wellness will not cause the screen to go into greyscale. It does trigger do not disturb overnight though. Could a reinstall of mindthegapps fix this?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] zimral.xda:
I have a question regarding the "Digital Wellness" stuff. I assume that it needs the google/playstore services to collect all the necessary data, right?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dethzord:
Just got an 3xl, fresh out of the box. Upgraded to stock android 11 immediately, then installed Lineage. Installed mindthegapps. Installed magisk. Everything looked good until I discovered my phone won't rotate, no GPS. Testing app says no gyro, no accelerometer, no compass.

Is this a mistake with how I installed gapps, or do I have a bad device? Pretty sure I installed correctly, didn't boot prior to gapps install. If the former, can I do a wipe, and reinstall mindthegapps? Or would I need to re-flash Lineage?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] FcukBloat:
i think you got the sensors bug, see relevant thread in guides section..
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dethzord:
Thanks for the tip. Looking at that thread brings a couple things to my mind.

It mentions Android 10. Will the same fixes suggested apply to Android 11 as well? Also, the guide suggests none of the sensors work. I was able to confirm some do work (light/proximity, for example). Still seem like the same bug?

Pardon if I am being overly cautious. Been running a Verizon Galaxy S7 rooted for a good while, which runs like complete ass. I'm so looking forward to having a decent phone again, I really don't want to brick this thing.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] namlas:
I created a bug report for my issue: https://gitlab.com/LineageOS/issues/android/-/issues/3498

Appears that I'm the only one seeing this behavior, so far. Hoping something comes out of reporting this as a bug. Phone is locks up and requires a hard reset every couple of days; sometimes multiple times a day.

@razorloves if there's any information I can provide, please let me know
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] landry314:
I do not have an Updater section in my System Settings... it just isn't there. Anyone else missing this? I have searched my Apps info with "All apps" for "update" nothing there either...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] zimral.xda:
Goto settings/System, last entry maybe "extended" ( i am using the german version) hit that and scroll down. The "updater" should be the last menue entry. Use that.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] landry314:
updater was a disabled app for some reason. i enabled it with oandbackupx and now it works. sorry guys, my bad. highly recommend oandbackupx btw! open source backup manager for your rooted phone.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] landry314:
When a new version comes out every week, a new recovery is also released but it has the same file size exactly down to the byte... is it the same file?

I ask this because I am using Magisk and when I update it using the built-in LOS Updater it seems to be flashing the boot partition also and then I have to flash Magisk again. To do this I have to download the new recovery, copy it to my phone, patch it, copy it back to my laptop, then boot to bootloader and flash it to both boot slots, as I always have. I am wondering if it would work the same to just deselect the option "Update recovery" in the Updater then I could save all this time and effort. If the recovery is the same every week, why flash it over my Magisk patched boot partition?

And yes, I always do a $ ./fastboot flash --slot all boot Magisk_recovery.img when I flash the patched Magisk boot image so the other partition of A/B will have already had Magisk ready to go when it switched after the update...

Can we ignore the recovery update every week and go about our business as long as both boot_a and boot_b are Magisk ready?

UPDATE: I just tried to disable "Update recovery" and it wouldn't allow me to. This means I HAVE TO flash Magisk every time if I use the Updater BUT can I flash the same patched boot partition I used last time or do I have to download the new recovery file from the LineageOS every time and use that one to patch? Even if it is the same file I think it might have a different signature or something...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] faheyd:
I don't know if it's my computer or the way the Pixel does recharging, but with the pixel charger, I get good 1.600mA flow, but on my computer through several differing usb3 ports, I get 'little' to 'no' charging. Sometimes taking overnight to charge on my computer (I have a recent MSI 470 chipset motherboard). I'm going to try to use the USB-C on the back of the motherboard next and see if the Pixel will talk nicely with that. Just thought I'd throw this one out there.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] justDave:
Just stop that. All you have to do is sideload magisk once (adb sideload, not fastboot). After you do that it will survive an OTA. You won't have to sideload again until next time you sideload a new major version of Lineage.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] lpedia:
If your PC's running Windows, have a look at Control Panel > Power Options > Change plan settings > Change advanced settings > USB settings. If 'selective suspend' is enabled (and I think it is the default), USB ports are supposed to turn off after a short time if there's no data going through the port. Just supplying power to a connected device won't keep the port awake.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] landry314:
oh he updated the install instructions! i see that now. i was following the older boot patch method at the beginning of this thread. this is much easier. thank you! i guess it uses /system/addon.d or something?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] razorloves:
Just a heads up...

Google made a screwed up change in the newest version of google camera (8.2.400) that came out about a week ago.

It reads a value from the build.prop and only accepts numbers, but lineage uses numbers and letters. This causes google camera to crash when using night sight and possibly other features.

you can revert to the older version of google camera (8.2.300).

or do the following commands:

adb root

adb remount

adb shell sed -i 's/ro.build.version.incremental.*/ro.build.version.incremental=123456789/' system/build.prop

then reboot, and google camera should work fine.

EDIT: if you have magisk it breaks the adb root command, so you can do these commands instead.

adb shell

su

remount

sed -i 's/ro.build.version.incremental.*/ro.build.version.incremental=123456789/' system/build.prop

EDIT #2: This issue has been fixed in the newest builds so this workaround is no longer needed.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Knuxyl:
I can confirm this works on the Pixel 5. Before, it would crash right after taking a picture, now gcam is working again. Will this break OTA updating? Thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] justDave:
Doesn't editing build.prop trip safetynet? To be safe I changed the property with MagiskHide Props Config instead. Confirmed that the camera does work with that change.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] rczrider:
I couldn't get this to work, but then I'm not especially familiar with the module and gave up when neither props nor su props did anything in Termux.

Other than the astrophotography time-lapse mode, are there any major differences in 8.2.300 and 8.2.400? I assume the next LineageOS will address the issue (or perhaps the next GCam release will revert back), so I figured it was easier to just grab the 8.2.300 APK and downgrade.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] leaveNOW:
the new update google camera from play store... every choose night mode... apps is crash.. always force close...

and for simple solution is just uninstall update and pure using google camera from stock rom...

this bugs? or just me?

**i'm croshhatch

Thanks
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] justDave:
Definitely just you

Read the last few posts.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] leaveNOW:
wowww
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dikamsiyoung:
Pico GAPPS is out 🔥
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] StarLord21:
Please how do I solve insufficient storage space when flashing GAPPs?
[Samsung Gear S3] krnflyboy:
does anyone have a gwd file for Gorilla watch ?

or know how to convert a watchmaker file to gwd?

only thing I can find is from the watchfacesbe and it's a WatchMaker file...

Thanks in advance!
[Touch Diamond, MDA Compact IV ROM Development] brettroul:
Hey guys.

Second time I have went with a cooked/modded ROM on a TouchDiamond.

The update process has been 100% sucessful each time.

But now I am trying to get back to the original Telstra ROM - Telstra_WWE_1.38.841.5 on the Asia HTC eClub website. This is also the original ROM on the unit when it shipped.

Using the guide located at:

http://modmydiamond.info/index.php?option=com_content&task=view&id=22&Itemid=26

I installed Hard-SPL 1.40 Olinex SIGNED – Once this was installed I was under the impression somehow it would allow me to go back to Original ROM if needed. As I though the Hard-SPL was a backup before messing with ROM.

I was then using Elite 3.0 – But need to get the unit back to the Original ROM before it is sent away for work use.

I am trying to run the Telstra ROM RUU Installer but receive an ERROR 262 - This occurs when the unit still show 0%.

Any ideas on what I can do.

Also – thank you, as your help and time is much appreciated

Brett
[Touch Diamond, MDA Compact IV ROM Development] sumitescp:
Hi, install the unsigned hard spl developer edition then install that stock rom.
[Touch Diamond, MDA Compact IV ROM Development] jakontil:
hi sumitescp,

is the SPL 1.93 unsigned referred to as unsigned hardspl developer edition?
[Touch Diamond, MDA Compact IV ROM Development] l3v5y:
You'll either need to get the ROM signed for HardSPL, or use the unsigned HardSPL.
[Touch Diamond, MDA Compact IV ROM Development] teoskalp:
I believe that with the term "unsigned hardspl developer edition" we reffer to the unsigned olinex 1.40 hardspl.

It is the first attachment in this thread http://xdaforums.com/showthread.php?t=400950

That is the recommended one.

But I think 1.93 unsigned SPL would work too, but first try the recommended one.
[Touch Diamond, MDA Compact IV ROM Development] Laubscherc:
First Install the ROM, and then downgrade the SPL. (Is this for warranty return?)
[Touch Diamond, MDA Compact IV ROM Development] udayrulz:
Use Unsigned SPL ., Flash the ROM :p

Yes for warranty return
[Touch Diamond, MDA Compact IV ROM Development] 1-2-Hak:
Do you have a copy of the Telstra 1.38 SPL? I didnt think the Original reloads back the SPL?
[Touch Diamond, MDA Compact IV ROM Development] brettroul:
This isn't actually for a warrenty return. I have had the phone for 2 weeks and been reading quite a bit about it on here - and thought i'd give the Elite v3.0 a go -

Love the speed imporvement of it - The unit just responds so much quicker. But i have then realisied i need the telstra MyPlace apps - My Account, Sensis, Foxtel etc..

So am deciding to go back to the original ROM.

Anyways - So i can re run the Hard SPL installer with an unsigned HardSPL installer and it will over right the exisiting one?

Then this will allow me to install the original ROM from the HTC Site? Is this correct.

In the above guide (as i mentioned the the first post) they reccomend:

"Hard-SPL 1.40 Olinex Developer Edition-unsigned" as the HardSPL Unsigned tool to use.

From there i have the choice of 3 HardSPL installers:

http://xdaforums.com/showthread.php?t=400950

Unsigned-Hard-SPL-Diamond-OliNex.zip (1.92 MB)

HardSPL_Olinex137_Unsigned.zip (137.4 KB)

RUU_Signed_1_93OliNex_HSPL_UnsignedEdition.zip (136.6 KB)

Which one do you reccomend?

Once again - thanks for all your support on this issue. I very much appriciate it and your time.

Brett
[Touch Diamond, MDA Compact IV ROM Development] 1-2-Hak:
RUU_Signed_1_93OliNex_HSPL_UnsignedEdition

is what I am using on the telstra diamond.

The others left me with some flickering in TF3D

I installed this one over the Signed Hard SPL without any issues.
[Touch Diamond, MDA Compact IV ROM Development] brettroul:
Hey guys.

Installed the Unsigned HardSPL and then was aloud to install the Original Telstra Rom v1.38...... hate it - but o well. I'll live.

Thanks once again for your help and time

Brett
[Nexus 6P Q&A, Help & Troubleshooting] devil meru:
Can we have lineage microg 16 or 17 for angler ??
[OnePlus 7 Pro Questions & Answers] RogerNZ:
Hi.

I upgraded to 10.3.6, retained twrp and magisk.

Now I cannot connect to phone signal or txt.

I do have data connection.

My phone sees the two sim cards but identifies both as inactive.

I have removed, cleaned and replaced both sim cards.

Neither phone carrier are having problems their end.

Also, no sound.

Edit:

Solution:

Reboot into other slot and repeat upgrade correctly.
[OnePlus 7 Pro Questions & Answers] aaryan45:
Does com.android.phone (Phone Services) has stopped error comes?
[Moto Z2 Force  Questions & Answers] H411UCIN093NIC:
So, I have tried various flashalls to try and bring my device back to stock. It seems that no matter what I do, I am always stuck at the bootlogo which then will either hang or force restart (depends on the firmware). I have even tried to flash the hybrid android 9 firmware that is available hoping that the newer firmware would solve the issue but it always seems that no matter what I do I am stuck with the same problem. I have tried about 3 different tools for generating flashalls, and am watching each file write with success.

Each time I flash I do indeed see the changes, obviously I can see the new version info in fastboot, also the bootlogo changes depending on the firmware, I can also flash twrp with ease. Ive tried to install lineage with hopes that it would fix the issue but no.

Now I also have tried to boot to recovery post flash then back to system, also yields no boot for me.

I did notice, that if I try to go into EDL mode that I am thrown back into a bootloop. In fastboot RSD-lite can see the device but I am greeted with a message of cannot boot into fastboot if I try to use it. (Perhaps I am using RSD wrong and the first command is an adb command?)

I also noticed that while my bootloader background image on Partition A changes with each flash, My bootloader Background image on partition B is the same Black and white Motorola background. Lastly I am making sure I am using an old windows 7 computer for this process and my newer computer will recognize the device, but cannot write to it.

Ill be honest, I put this phone in a drawer after being stumped with it about a year ago, trying to bring it back to life now. Any help would be appreciated. Thank you all for the wonderful work you do here on this forum. <33
[Moto Z2 Force  Questions & Answers] sd_shadow:
RSD lite doesn't work with windows 10

What does getvar all say?

fastboot getvar all

Try LMSA's Flash Rescue option

https://xdaforums.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
[Moto Z2 Force  Questions & Answers] H411UCIN093NIC:
When using LMSA it does not detect my phone properly. It says that my device info is: []

This is the result on both windows 10 and windows 7
[Moto Z2 Force  Questions & Answers] cgigate:
It appears you lost the baseband, so the LMSA cannot read IMEI and cannot flash....

Windows 7 or 10 does not matter....
[Moto Z2 Force  Questions & Answers] H411UCIN093NIC:
I have tried both of these Flashalls with no luck https://xdaforums.com/z2-force/development/rom-tmo-z2-force-27-1-5-flashall-march-t3917070 along with 8.0 oreo no luck then even tried the hybrid 9.0 version with no luck either. I saw a specific post where someone created a flashable with the ability to bring back baseband however, the file no longer exists on googledrive. You wouldnt happen to have it, would you?
[Moto Z2 Force  Questions & Answers] cgigate:
You need build a new blankflash by yourself to save your device....(search the blankflash build guide in xda).

If you still don't know how, then trash it to go forward...
[Moto Z2 Force  Questions & Answers] H411UCIN093NIC:
I forgot, this is where I was at a year ago xD. Ill look into it right now. Thank you very much for your help
[Moto Z2 Force  Questions & Answers] H411UCIN093NIC:
Found it, was actually linked to an old post I made a year ago (facepalm)

If anyone one else needs it its here

https://xdaforums.com/showpost.php?p=77623934&postcount=5
[Moto Z2 Force  Questions & Answers] H411UCIN093NIC:
Using fastboot oem blankflash returns

(bootloader) Command Restricted
[Moto Z2 Force  Questions & Answers] H411UCIN093NIC:
Happen to know an option for me if baseband is gone and fastboot oem blankflash returns that the bootloader is command restricted? Of course my device is indeed unlocked. I do not need cellular service for this phone, honestly don't even care if the phone turns into a brick, its this learning trial and error that excites me personally. If you know any methods that are even more so risky please let me know lol. I did have a question however, since I cannot get my phone to go into 9008 mode through fastboot oem blankflash will I be able to use an EDL shorting cable to push the device into QCM? I am only asking you, because you seem to be highly knowledgeable. Again, I don't care if the device turns into a paper weight or bursts into flames, so if there is anything more risky that you normally wouldn't suggest I am game. I am not shy to linux if there is a better way.
[Moto Z2 Force  Questions & Answers] sd_shadow:
Try to boot TWRP then Use

adb reboot edl
[Moto Z2 Force  Questions & Answers] H411UCIN093NIC:
Thanks for the reply, but that has the same outcome. It just bootloops with the moto screen. I also tried a modded fastboot for the <fastboot reboot-edl command> with no luck either.
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] hayabusa1300cc:
Beta 2. ZTJG to ZTK1

I will find out how to pull the zip or download link. Edit: Link belowView attachment 5129729

Here if the download link. Rename to update.zip and flash, I'm sure. I am unlocked on Sprint btw.

Link: http://fota-secure-dn.ospserver.net...57:52&px-unum=&px-nb=UGtezEZ854jbmFcvWGxLEA==
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] eric6268:
Show us, plz
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] hayabusa1300cc:
Not sure what I am looking for
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] hayabusa1300cc:
Got it

http://fota-secure-dn.ospserver.net...57:52&px-unum=&px-nb=UGtezEZ854jbmFcvWGxLEA==
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] dottat:
flashed it via adb sideload myself (stock recovery is picky about what file system your SD card is).

Can't wait to see what bugs they addressed.....
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] netnerd:
freaking Visible !

i enrolled the beta, on Visible simcard, it doesnt show any update.

when i put the expired tmobile simcard in, it shows there' a update.
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] DarkMidnight:
So I'm on AT&T though Wing and previously, did not have WiFi-Calling. Updated to Beta2 via system update and now I have WiFi-Calling enabled / address registered.

I turned on airplane mode, turned WiFi back on and confirmed it worked so those of you rocking unlocked firmware with AT&T, it appears that at least for this second beta, Wifi-Calling is enabled.

Not sure why it wasn't previously. Coincidence?
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] dottat:
I can't get rcs working again for tmobile.

Edit. Had to apply settings a couple times and leave it be for a while then reboot. Could be maintenance window activity or something else
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] Tonyy1206:
What firmware did you update from? You used any of the links above? Appreciate any feedback in advance.

U1 XAA device purchased from Samsung on TMB sim. Haven't been able to get my hands on a r15 sim yet.. requested one but they sent a TM one.. that's a whole different topic lol
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] birdMan6279:
Or, do it thru your dialer. keypad UCCD CODE style, are u familiar, wth, I'll throw it up for everyone (ink to paper) for everyone:
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] paatha13:
Anyone know why I'm getting this error trying to upgrade to beta 2 from latest stable Android 10 version.

Or need to be in beta 1 in order to update to beta 2?View attachment 5129769

I didn't had similar problems when couple days ego upgrade from Android 10 version to beta 1 via adb method.