yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy J7 Prime / J7 On NXT (Exynos7870)] HassanSYR:
nice work

:D:):):):):):):)
[Samsung Galaxy J7 Prime / J7 On NXT (Exynos7870)] sooheb:
Link dead
[Samsung Galaxy J7 Prime / J7 On NXT (Exynos7870)] MightyStang:
Bugs

The bugs I have found so far is:

- mobile data is not working for some reason.

- when I install it with cwm I was having touch delay issue but when installed with twrp it doesn't appear to be an issue any more ;)

- can't access WhatsApp camera, just black screen for a sec then it close it self :confused:

- THERE IS NO FM RADIO ?

I think that's it, if any one know how to fix these bugs specially the mobile data and a way to port the FM radio that will be awesome:laugh:

Replay ASAP Please :)
[Samsung Galaxy J7 Prime / J7 On NXT (Exynos7870)] :
Did you download the bootleggers ROM from this thread (by douglas) ?? If yes, then plz switch to another newer bootleggers (by jbjoshuaa).. might fix some of your problems...

Also, i think setting up FM Radio in AOSP is a hassle. There used to be an app that ran FM Radio online through internet.
[Samsung Galaxy J7 Prime / J7 On NXT (Exynos7870)] MightyStang:
i did fix some issues

First of all THANK YOU so much for replying:o

yes i did download the rom from this thread (from the orignal link)

- about the mobile data i found that the APN was wrong for some reason, but i end up fixing it.

- I need something like "spirit 2" to play real fm waves (without internet), i was thinking android PIE don,t have support for it but when i tried "BlackBird OS" it was there !!

so there must be away to port it to Bootleggers rom or something like that...

i am still trying and if i found a way i will post it in here right away

-there is also the USB preference bug that i forget to mention it, I know that i can change it from dev option but it,s much easier to do it from the notification, if you know i way to fix it through adding a line in the build prop or something like that it will be awesome

-also found a solution for whatsapp !!, just delete (com.whatsapp) from (vendor.camera.hal1.packagelist) :D

-the touch delay is still present though !!

that is it thank you again ;)
[Samsung Galaxy A6 Questions & Answers] hckrtmfn:
how i can install google apps on my samsung a6s
[Xiaomi Poco F1 Questions & Answers] kris_95:
Tried usual method, i.e, changing the bootanimation.zip in system/media, gave usual rw-r--r-- permission, didn't change a thing.

Then tried with magisk, still the same.

What could be the reason?
[Xiaomi Poco F1 Questions & Answers] Saswata Chakraborty:
The black screen with Poco by Xiaomi that you see while booting the device, is not bootanimation. It's splash screen.
[Xiaomi Poco F1 Questions & Answers] CosmicDan:
Try re-applying the default theme. I think the theme engine supports bootanimation changes, which means the usual one at /system/media/ is only used as a default template - the active bootanimation would be somewhere on /data if this is the case.
[Xiaomi Poco F1 Questions & Answers] kris_95:
Thank you genius, but I'm saying the "bootanimation" isn't changing, it's showing the same "pocophone/by Xiaomi" even though I changed it, via magisk and via changing zip with permission 644
[Xiaomi Poco F1 Questions & Answers] kris_95:
That probably could be the case. Thank you. Brb

Edit: Nope. Still not working.
[Google Pixel 3 XL Questions & Answers] eec007:
Hello, I purchased a Pixel 3 XL off craigslist and it is working fine, but the bootloader is unlocked therefore I am receiving a warning when restarting the phone and Google Pay does not work. How can I re-lock the bootloader? Do I need to flash the latest standard google image? The build number is: "crosshatch-userdebug 9 PQ1A.181105.013 5027108 dev-keys". When in bootloader the bootloader version is: b1c1-0.1-5004167. Obviously a n00b here, please be gentle. Thank you for any help.
[Google Pixel 3 XL Questions & Answers] superchilpil:
Do you have a computer? If so what OS do you use?
[Google Pixel 3 XL Questions & Answers] eec007:
I do have a computer, a Windows 10 Pro
[Google Pixel 3 XL Questions & Answers] sliding_billy:
Are you planning on rooting? If so, you can use Magisk Hide (after using Magisk to root of course) to get Google Pay to work. I would be hesitant to re-lock the BL unless you are certain that it is completely stock otherwise. Re-locking a modified phone can brick the device. Better to just learn how to root, etc and keep it unlocked. You have come to the right place to learn.
[Google Pixel 3 XL Questions & Answers] eec007:
No, I don't plan on rooting. But I am afraid of bricking the phone since I don't know what has been done to it. Is there a way to determine what was done to unlock the bootloader? Otherwise I will follow your recommendation of using Magisk Hide. I would prefer to keep the phone stock. Thanks.
[Google Pixel 3 XL Questions & Answers] coolhandz:
If you live in Denver I'll trade you my Verizon one for yours. It has a locked bootloader. ;)
[Google Pixel 3 XL Questions & Answers] sliding_billy:
The two obvious things you can check are that you have stock recovery and that the phone is not rooted. Manually power on to bootloader (hold volume down and press power then use the volume keys to select recovery and press power. you should get a no command android screen if in stock recovery. assuming you don't have a Magisk icon, you are probably not rooted but you can confirm by installing and running a root app like root checker. likely, the previous owner did nothing but unlock the BL given how recently it came out, but if someone where really creative they could have done work in the other partition. there are no exploites, so doing it normally (running fastboot flashing unlock from a prompt) is pretty much all that would have been done other than enabling developer options and OEM unlocking in settings.

Personally, I think you have a good chance to learn your device, root (you need to be rooted for Magisk hide) and keep the bootloader unlocked. Besides rooting, being able to install a full factory image instead of an OTA is so much better in my opinion. The amount of work it would take to be 100% confident that the only thing done was the BL unlock would take as much work as at least getting a working knowledge of rooting and reinstalling the OS.

P.S. Keeping a phone "stock and rooted" has advantages. That is how I run my 3 XL and how I ran my OG XL. No custom OS. Not even a kernel.
[Google Pixel 3 XL Questions & Answers] eec007:
lol, what I don't get is that I thought the google edition could have the bootloader unlocked in the developer options. So why go to this hassle of unlocking the bootloader from fastboot? FYI, in the Developer options the OEM unlocking is greyed out and says "Bootloader is already unlocked".
[Google Pixel 3 XL Questions & Answers] eec007:
Thank you! Root Checker says that "root access is not properly installed on this device". The recovery mode screen just has a warning about the bootloader is unlocked and a link to a google help page. I figure that I can always unlock the bootloader again if I need to later, but for now I just want everything to work (bank and pay app) and not worry about updating anything myself. I think I may try fastboot to lock the bootloader for now. Thanks for all the help.
[Google Pixel 3 XL Questions & Answers] sliding_billy:
Hope it all works out for you. I assume you did a factory reset on the device since you got it used. Re-locking will do another factory reset.
[Google Pixel 3 XL Questions & Answers] eec007:
Yeah, so I locked using "fastboot flashing lock" but then it doesn't start, saying that there is no operating system or something like that. I freaked out and was able to unlock again using "fastboot flashing unlock". Now all is wiped. I guess I need to flash the oem rom first, then lock. I'll have to do this all later tonight. Just glad that I didn't brick it yet.
[Google Pixel 3 XL Questions & Answers] bobby janow:
I haven't rooted or bl unlocked in some time now so if I make a mistake someone please correct me. After buying it from a 3rd party I'd wipe the device entirely. Download the correct image and install the latest platform tools for Windows (here) https://developer.android.com/studio/releases/platform-tools and make sure you can connect with adb devices and fastboot devices commands. Then extract the latest full image from here https://developers.google.com/android/images to your platform-tools directory and run the flashall.bat command if you wish to wipe the entire device and get rid of anything the previous owner might have "inadvertently" installed. (this is what I would do but not necessarily what you should do if you want to keep the current apps and system intact) This will reset your device and then you can lock the bootloader with no worry and you'll have a stock system.

I agree that since you can unlock it at any time and you don't need it now then relock it. But there are those here that disagree with me and fight with Magisk and OTAs constantly. But they are not noobs and know what they're doing. If you want to learn there is a wealth of information here so it's your call. Just my 2 cents. But please check my steps before you do anything that might cause issues.

edit: darn, sorry I just saw above that you already tried to lock it. I hope what I said to do will get you out of the predicament.
[Google Pixel 3 XL Questions & Answers] eec007:
Your steps are basically what I will try tonight. Currently the phone is working again, so there was no harm done yet (just the restore of all apps and such). But I'm going to flash the oem image tonight and start all over again.
[Google Pixel 3 XL Questions & Answers] bobby janow:
One thing I would do before I relocked the bl would be to do the full login procedure, email everything other than apps. Then make sure you're on the Nov update in about phone, I'm sure you will be, and then fastboot relock the bl with the proper command. It will wipe the device again but it's a small price to pay for about 10 minutes of work. Then once it reboots and there is no more error message you'll be fully stock. Enable dev options again and make sure the oem switch is active allowing bl unlock. Then you're done. I've gotten to the point on my 5X where I even flip the oem switch so it can't be bl unlocked until I go in and flip it back. Dangerous if you're flashing stuff but not so much if you're just taking OTAs. That's of course your call entirely. Good luck.
[Google Pixel 3 XL Questions & Answers] TonikJDK:
That will stay grayed out until you relock the bootloader. That slider "allows" unlocking. Then you boot into fastboot and unlock it.

So you would reverse the process, hit fastboot and relock the bootloader. Then you can toggle the slider back to not allow unlocking.

Relocking the bootloader will wipe your phone.

You should not do this until you first flash the full factory image to make sure the phone is 100 percent stock. And if it were my phone I would wait for the next OTA update after flashing it back to stock to make sure it goes ok. Then lock it.

And then I would wait awhile before hitting the slider.

You are playing with fire here, if you mess it up and lock it and hit the slider you will not be able to fix it. And no offense, but since you have not done this all before on this phone chances are good you will mess it up.

So, flash to stock and leave it unlocked.

Then wait for the next OTA.

Then lock it.

Then wait a bit more before you hit the slider.

And remember, since you are not the original buyer you will not be able to warranty it.
[Google Pixel 3 XL Questions & Answers] michaelbsheldon:
They're right to mention that relocking a modified device can result in a brick.

Your best bet is to go to https://developers.google.com/android/images#taimen

Follow the directions to the "T", then relock it if you are really really sure that the unlock screen bothers you.

Would suggest to do this anyway, no matter future unlock status.
[Google Pixel 3 XL Questions & Answers] bobby janow:
I agree with most of your post other than waiting for the next OTA before you lock the bootloader. Why would he need to do that? If he's stock, and he'll see that immediately, then relock it. He doesn't want root or Magisk but only wants banking and Pay. With the slider allowing bl unlock he's in no danger whatsoever. Lock and relock whenever he wants. OTA will not disallow the slider once it's set.
[Google Pixel 3 XL Questions & Answers] eec007:
Thank you for explaining this. I had thought that the Developer Option slider was to unlock the bootloader, but your explanation clarifies it, the slider is to allow the bootloader to be unlocked...
[Google Pixel 3 XL Questions & Answers] eec007:
Ok, so I tried to flash the factory image using adb flash-all and it keeps getting the error:

Sending sparse 'vendor_a' 2/2 (193888 KB) FAILED (Error reading sparse file)

Now the phone is not working at all and says that "device is corrupt" and will not boot past the white google screen. I can try again using adb, but it is the same error each time. I tried to download the image again and same sparse error. I can also fastboot in TWRP, but not sure what to do in there. What am I doing wrong? I guess I should've rooted and used Magisk like others have said. :(
[Google Pixel 3 XL Questions & Answers] eec007:
turns out changing to a different cable resolved my sparse error and I was then successfully able to apply the factory image and lock the device. Thanks everyone for the help.
[Google Pixel 3 XL Questions & Answers] sliding_billy:
Glad you got it done!
[Google Pixel 3 XL Questions & Answers] bobby janow:
Excellent news. So just to clarify, you are now stock November update and bl locked with the OEM switch able to toggle still? If so, leave everything alone allowing bl unlock. Congrats.
[Google Pixel 3 XL Questions & Answers] eec007:
Yup, my Pixel 3 XL is now back to the stock November 2018. The bootloader is locked and the Developer option OEM switch is toggle-able again. Google Pay is working and everything restored.

FYI, for the curious, I was using a USB-C/USB-C cable from my Windows 10 to P3XL, the flash failed at the same spot everytime I tried, even with different versions of ADB. I then switched to a USB-A/USB-C cable and the latest ADB and it worked fine. Not sure what is wrong with my USB-C/USB-C cable, it works fine for charging.
[Google Pixel 3 XL Questions & Answers] bobby janow:
It's been a known issue since the Pixel 2 over a year ago. I'm not sure anyone has definitively figured it out but the A - C cable always worked when the C - C didn't. Since I don't root or unlock I can't test out my C - C cable on my HP. I know I can fast charge and transfer files back and forth but not certain what it would be like to flash something from recovery or fastboot. Good job on sticking with it. I saw your frustration and hoped you wouldn't give up and you didn't. Bet you learned a lot in the process. ;)
[Google Pixel 3 XL Questions & Answers] dmalikyar:
I'm thinking of doing the same. Can you list the exact steps you followed or point me to a link that has the exact steps?
[Google Pixel 3 XL Questions & Answers] Bryanx86:
-download platform tools(newest)

-set up adb on your Linux or windows machine

-tap build number seven times in settings on your device to enable "developer options"

-Go to "developer options" in settings

-toggle adb debugging on in "developer options"

-plug your phone into your computer with adb(platform tools) installed

-give permission on your phone for computer to have adb access to your phone

- download latest factory image from Google and put in ADB folder

-extract image.zip and other files from system image download.

-select flash.all to flash all partitions

-reboot

-make sure you go to settings again and toggle adb and allow computer access (this is important)

- reboot bootloader in ADB

-"fastboot flashing lock" in bootloader mode
[Google Pixel 3 XL Questions & Answers] dmalikyar:
What are the advantages? I rooted my phone to edit the build.prop and then discovered that buildprop editor can edit the build.prop without root being enabled. I'd prefer not to have it rooted as I'd have to flash any updates.
[Google Pixel 3 XL Questions & Answers] sliding_billy:
There are other command line edits that need you in root to execute (device level tether to get away from carrier provisioning for example), but honestly there are simply a loot of root only apps and modules that require root that many users have made a part of their everyday configuration . Other than the occasional app that it takes some time to get around their root checks with Magisk Hide or other methods, the benefits far outweigh the negatives. As for flashing images instead of taking OTAs, for pretty much every other device I can see your point. With the Pixel however, you are still going to get the ability to install the new image the day it is released and not have to wait for someone to rebuild a custom or stock based ROM. After you have done the stock image flash a couple of times, I think you might agree that it is actually easier, safer and more consistent than any OTA.
[Google Pixel 3 XL Questions & Answers] dmalikyar:
Excellent points. The reason I rooted the phone initially was because of the carrier provision item you cited. However, I read an article that said the I could edit the build.prop without root by using the buildprop editor app. Is that correct?
[Google Pixel 3 XL Questions & Answers] coolhandz:
I tried it, but it asks for root. It says it needs root in the description of the app too.
[Google Pixel 3 XL Questions & Answers] sliding_billy:
What you might have read was someone claiming to be able to read/edit the prop file, but the problem is saving it. Pulling the file is one thing, but saving to the system partition is another. Pull/push build.prop methods might work on some devices, but they cannot be done on the Pixel as far as I know. Even if they could, the odds of bricking your device are huge and I can pretty much guaranty an OTA would fail miserable. Just let root and an editor do the heavy lifting.
[Google Pixel 3 XL Questions & Answers] eec007:
Pretty sure you'll need root if you want to edit the buildprop.

But the steps that were given to re-lock the bootloader are correct if you wanted to do it.
[Google Pixel 3 XL Questions & Answers] purple.epod:
This really depends what you want to do. I am rooted so that I could use Magisk (primarily for Ad-away) and also, since I am not in the US I had to edit XML config files in the system partition to enable Google's Call Screening feature, since it's not enabled for anyone outside of the US by default at the moment. As you mentioned, the downside to this is that you need to manually flash future updates, though to be honest it's not that big of a hassle. taking only a couple of minutes if you know what you're doing.
[Google Pixel 3 XL Questions & Answers] ychongy13:
Did you have any trouble with ota updates after relocking boot loader? Feb 05 2019 update is stuck at 0% for me then fails. I was able to relock my bootloader. But Im unsure if I need to flash a full factory image back to oct or november? Which factory image do I need? Also do I need to unlock my boot loader again to install the image? Thanks.
[Google Pixel 3 XL Questions & Answers] Bryanx86:
To flash a factory image you need to have an unlocked bootloader. But to flash a locked bootloader, you can do so through your recovery. Download OTA from link at the bottom of this reply, there should be directions there. Basically boot to recovery, have the OTA.zip ADB accessible, and type. ADB sideload OTA.zip (or whatever name it is). Then it will update through your recovery. Select update through ADB while in recovery. ota.zip Download is device specific
[Google Pixel 3 XL Questions & Answers] gtrehling:
Okay I am having the exact same problem you were.

so what ended up happening? were you able to lock your bootloader without bricking your phone?
[Google Pixel 3 XL Questions & Answers] RhaegarTargaryen:
oh bro, my phone is same with yours

if u deal with this issue, plz tell me.that is so hard for me to use a phone like this.
[Xiaomi Mi A1 Themes, Apps, and Mods] joeyhuab:
Xiaomi Mi A2 Camera port​

FEATURES

MiuiCamera.apk from Mi A2 stock ROM

DOWNLOAD FROM THE MAGISK REPO

REQUIREMENT: https://xdaforums.com/mi-a1/themes/magisk-stock-camera-hal-custom-roms-t3900493

LICENSE

Copyright © 2019 joeyhuab. Licensed under the GNU General Public License v3.

CREDITS

[MENTION=5997954]ramesh1686[/MENTION] for his original module

[MENTION=6302075]sipollo[/MENTION] for his telephoto fixes and zoom support

SOURCES

Original XDA thread

Mi A2 Camera Github
[Xiaomi Mi A1 Themes, Apps, and Mods] Wyroczen:
On LOS 16 with 4.9 kernel 3/4 of the picture is green when using A2 camera, I haven't tested A1 cam.
[Xiaomi Mi A1 Themes, Apps, and Mods] empossathorn:
Thank a lot!!
[Xiaomi Mi A1 Themes, Apps, and Mods] babakhad:
nice work

is it possible to we have twrp flashable zip file too ??
[Xiaomi Mi A1 Themes, Apps, and Mods] seanmcken:
bothh can be installed at a same time?
[Xiaomi Mi A1 Themes, Apps, and Mods] joeyhuab:
You can flash this with TWRP as well.
[Xiaomi Mi A1 Themes, Apps, and Mods] joeyhuab:
Yes but only 1 can be enabled at a time. You need to uncheck the other module.
[Xiaomi Mi A1 Themes, Apps, and Mods] JortonMV:
Thanks! I tried them on Arrow OS Pie.

With Mi A1 camera everything works well! but with Mi A2 camera, Google Camera crashes when I take a photo.
[Xiaomi Mi A1 Themes, Apps, and Mods] Moon_420:
When the camera sees a person It disconnects and app disables xd?
[Xiaomi Mi A1 Themes, Apps, and Mods] manpildo:
Hi!

Does this mean the modules will also enable api2, or does it simply mean that they utilize it and it has to be enabled separately?
[Xiaomi Mi A1 Themes, Apps, and Mods] NuxRo:
Hello,

Any way to disable the shutter sound? Unchecking it in the settings doesn't do anything.
[Xiaomi Mi A1 Themes, Apps, and Mods] schmellic:
Same for me on HavocOS with kernel 4.9

Both A1 and A2 cameras are the same
[Xiaomi Mi A1 Themes, Apps, and Mods] Ilija8:
Yeah, it seems to be happening only on 4.9. I've been using this on previous ROMs and it was working perfectly before.
[Xiaomi Mi A1 Themes, Apps, and Mods] ChasingHaze:
Same here on Pixel Experience Pie 3/4 Upper left corner green.
[Xiaomi Mi A1 Themes, Apps, and Mods] Gshrestha:
Hi , can we install both mi a1 and A2 camera at once ?? If no , then could you please make it able to do so ??
[Xiaomi Mi A1 Themes, Apps, and Mods] k.jo99:
Suggest me the best version of gcam....

I'm on MIUI 8.10.25
[Xiaomi Mi A1 Themes, Apps, and Mods] schmellic:
Just updated to latest version of Liquid Rom and Magisk v18 so thought I'd give it another go... Latest version of the A2 camera is working now (downloaded via Magisk manager), tested portrait mode and all good ?
[Xiaomi Mi A1 Themes, Apps, and Mods] gelarman:
hi,dev can u please make the one for twrp flash,i cannot use root in my phone to work,so i cannot using magisk
[Xiaomi Mi A1 Themes, Apps, and Mods] Suman1408:
IS the yellow tint fixable for 4.9 kernel based roms??
[Xiaomi Mi A1 Themes, Apps, and Mods] maruashok:
Why Its removed from magisk repo..??

I think magisk repo has latest version compared to sourceforge.
[Xiaomi Mi A1 Themes, Apps, and Mods] imsivaswagger:
I have green tint on stock mi a1 port running 4.9 kernel please fix it soon
[Xiaomi Mi A1 Themes, Apps, and Mods] saski4711:
With latest LOS15.1 I have black & white images with rear camera unless I turn on the flash. Any solution? I use khusika's canting kernel 3.18.132
[Xiaomi Mi A1 Themes, Apps, and Mods] august17:
is it work on pie ROM? I'm using RR 7.0.0
[Xiaomi Mi A1 Themes, Apps, and Mods] thezinq:
No this won't work with 4.9 based kernels
[Xiaomi Mi A1 Themes, Apps, and Mods] august17:
thanks m8
[Xiaomi Mi A1 Themes, Apps, and Mods] sgkul:
[MENTION=7055721]august17[/MENTION]

Except portrait mode everything works on 4.9
[Xiaomi Mi A1 Themes, Apps, and Mods] nahuelvvn:
Thanks! A2 port working great in A1 stock PIE, almost the same but looks nicer :p
[Xiaomi Mi A1 Themes, Apps, and Mods] BBOrno:
portrait moode isnt showing in a1 camera...... what should i do??