yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
Have you flashed the factory image to both slots prior to sideloading? Adb flashes to the opposite slot, so flashing the factory image on just the active slot is not enough
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] usablefawn:
This was my issue. Had to flash factory image to both slots first and then sideloaded rom.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ART:
Did this bring back the config center?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] usablefawn:
Yes indeed.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Xdevillived666:
trying to extract on mac and it only creates a new file format of zip

---------- Post added at 09:34 AM ---------- Previous post was at 09:16 AM ----------

Installing on pixel 3 so far is working . Just follow instructions on page 11 about custom boot image and sideloading

Edit- getting nonstop freezes and reboots. Dont install to blueline, lol
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dhacke:
[MENTION=6864870]slothdabski[/MENTION],

Will there be weekly builds? Or monthly when a new security patch comes out?

I'm just asking because i'm considerung to change to the pixel devices due of the fast and direct updates from Google (but don't want to use stock rom so i need a reliable custom rom).

And one other thing. I only used Sony Smartphone so far. Because of this i don't have any experience regarding flashing stock rom on Pixel devices.

So can you tell me the procedure or link to the right thread where i can get the needed information?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] usablefawn:
I'd check the pinned guide under the Pixel 3XL Guides for information regarding unlocking, rooting, flashing ROMs, etc.

https://xdaforums.com/pixel-3-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3857195
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
Most likely be weekly builds since 10 ROMs are still new and source will likely be updated often.

Pixel 3 xl doesn't have twrp for Android 10, so flashing custom ROMs consists of flashing a boot.img in fastboot, then sideloading the zip in adb
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dhacke:
Yes that twrp isn't still not ready for Android 10 i read but i have a high faith in the guys from twrp team. So i guess it will come in the near future.

Luckily Magisk is possible without twrp too and HavocOS supports signature spoofing. So Installation from microG should be possible too:)

Mayby you give me some information about Custom Roms based on Android 10 for the pixel 3/4. Are they already in the pipeline? Or is it too early to ask this?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
Gapps are included in havoc builds for our device. Microg isn't an option since I'm only release gapps builds
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dhacke:
Oh ok. Any specific reason for included GApps?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] darkstar73:
I recently flashed this ROM in the hopes it would fix an issue I'm having with the stock ROM. Everything is working good so far except that I can't get Google Fi to activate. I deleted/reinstalled the app, but that didn't work. It continually force closes. Any ideas on how I can get it to activate?

Edit: Got to work by deleting the app, then rebooting and reinstalling Fi. Anybody know how to get this ROM to pass safetynet? I used Google Pay quite a lot, but the ctsProfile check fails. Using the magiskhide props config module doesn't work.

Edit 2: Reading is fundamental!! Answer in post #102 regarding safetynet.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
It's the easiest way to make sure all pixel features work (except for squeeze on 10 right now).

Not many people who get pixels are interested in being gapps-free
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Xdevillived666:
I know someone asked earlier but will havoc based on Android 10 also come to blueline?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] FcukBloat:
see in blueline section, it is under testing apparently ;)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
Yes, I am working on blueline and will release once everything works
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dhacke:
Can you make mayby seperated builds? One with Gapps and one without?

Then the people have the choice.

For me get rid of GApps is the main reason why i use custom roms.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
Sorry, I will only be releasing builds with gapps
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] sliding_billy:
I am up and running except for some last second config. I was in adb shell earlier with no issues. Now, shen I type adb shell, I get error: exec '/system/bin/sh' failed: Permission denied. Everything else seems to be OK including terminal emulator and su command in there. Any thoughts?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nkhater:
Can I dirty flash on top of Havoc-OS Pie?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
I'm not sure. I just tried and was able to get adb shell from my computer and even request/grant root for shell. Maybe reboot and try again?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
No, you will have to flash q factory image to both slots before flashing this rom
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] el_pelosss:
everything works fine for me but the edges that are pressed to use the assistant do not work for me
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
Active edge is not supported at this time, hopefully soon!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] sliding_billy:
That's the odd thing. I was using it earlier for nothing big, but i did take a reboot from one of the props config module commands while connected.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] el_pelosss:
and another question .... if after installing the start rom I go back to fastboot and flash your root file does not start ... I don't know if I do something wrong but it stays in the G logo and the havoc one does not come out and no Starts
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
Did you flash factory image to both slots first? Also are you verifying the zip sideload completed successfully? It should say status 0 if adb sideload succeeds
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] el_pelosss:
I have flashed the stock image in the two slots. Then I have done everything perfect until two o'clock, and when I flash the boot patched, that happens to me. and if adb says everything ok
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
Don't flash the patched image. Just reboot after flashing the rom zip. You can flash the rooted image after successfully booting once
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] el_pelosss:
that's what I do. I flash the patched image once I have started the rom minimum once. but it always stays in the g. I do it in both slots too
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
Are you clean flashing? You don't need to flash the magisk patched image to both slots and you don't have to mess with slots at all once you boot the first time. Just reboot to bootloader, flash the magisk patched image, and reboot
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] TheProblemCauser:
I had that same issue.

After sideloading the ROM, I switched slots

fastboot set_active other

and sideloaded the ROM again. It worked after that

---------- Post added at 11:12 PM ---------- Previous post was at 11:11 PM ----------

He's having the same issue I had. Its not booting to the right slot for some reason. He does not get the Havoc Boot Animation.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] vn00914361:
Is it possible if you guys can port Android Beam from Android 9 to this ROM? Please please please
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ART:
Would we need to always flash factory images to both slots before doing this for future havoc updates?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
It should only be required for the initial flash.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] naimi5885:
please help me,i want flash this rom this say error applying update 28
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] darkstar73:
I was hoping this ROM would fix the issue I was having on stock 10, but it didn't. Looks like I'm going to have to downgrade to 9 since it doesn't have the problem, which is I'm constantly having to hold the power button to reboot the phone because the screen won't turn on. This mostly happens after charging overnight. Hopefully, the Nov update will fix my issue and I can flash Havoc again.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
If you are having the same issue on stock, I'm inclined to believe that there is some sort of mod or add-on that you are using to cause this issue. hopefully you can figure it out and try this ROM again in the future
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ins5736:
Silly question, but these screenshots are from 9/pie, right? Trying to make sure I didn't goof the process.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
Yes they are still from pie
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] darkstar73:
Also happens in safe mode so it's not an app or mod.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Jiggs82:
Hmm could be a sensor issue from Android 10?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] darkstar73:
Wasn't that fixed in the Oct update?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] FcukBloat:
no. if you are affected, at the moment you still have to fix it yourself (persist fix)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] STALKER18:
If its a sensor problem u can disable all sensors by following these steps :

Enable developer options.

Navigate to : Quick settings developer tiles.

Turn on : sensors off.

Pull down the status bar and u will find the button right there. I believe the 1st one on the left.

It will disable camera, mic, ambient sensor, proximity sensor, gyro, accelerometer, gps(I think). Maybe others.

I hope this gonna help u for now.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
The sensor issue many people experienced was due to TWRP corrupting the device's persist partition.

Not saying this is your issue, but it may be.

https://xdaforums.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904/page18
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] darkstar73:
Thanks! I have disabled the sensors. If my phone doesn't lock up in the next 24 hours, I obviously have the sensor issue. I have been reading the sensor thread and it doesn't look like the fix is all that difficult to implement.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Vember31:
Hey all just got the 3 XL and am trying to flash the latest Pie version of Havoc but keep getting a bootloop. I've been flashing for years (including on a different A/B device, the PH1). Can anyone see what I might be doing wrong here?

1. starting on stock Android 10 latest image

2. downloaded Havoc 2.8 (that's Pie-based right? or is that android 10?), as well as twrp and magisk

3. boot the twrp img

4. wipe all partitions (should I not do this for Pie?)

5. flash havoc and then the twrp zip

6. reboot bootloader, which switches to the other slot where the rom was installed

7. flash magisk

All of this is successful, and then I reboot and get a bootloop. Any of my steps there look off? I've read the guide several times as well and don't think I have missed anything egregious. Thanks for your help guys :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
You need to flash most recent pie image if you are trying to flash pie rom
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Vember31:
Got it - will do. One more question - should I be wiping anything in twrp prior to flashing the havoc zip? Such as wiping /system? Or do we simply wipe data/userdata, and flash the rom on top?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
Only thing you need to wipe is /data
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] sliding_billy:
Happy Day (Not)! I managed to kill ADB shell again after another completely fresh Havoc install. I checked after installing and rooting to be sure I could get in with the minimum to get into shell (Windows 10) and grant superuser rights with an su. I did all the rest of my work that required terminal/shell work in Terminal emulator to be sure it wasn't something I did while in the shell. After finishing installing and configuring everything, I finally went back to check shell and got the exact same error. I guess I have no shell unless someone smarter than me has an idea (It is not an absolute necessity since I can still do everything I need to in the emulator). I managed to get it to bootloop and soft brick (somewhat intentional) various things before I started the reinstall. So, if anyone has a reason to be in shell and confirm it is working or not I can think about possible similarities. Probably the one thing that a good amount on this ROM have done is modify the fingerprint to the 3 XL Pie fingerprint using the MagiskHide Props Config module.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] darkstar73:
Since I disabled the sensors, my phone hasn't locked up. I will follow the the instructions in that thread to permanently fix!!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] FcukBloat:
you may want to wait next google update before trying the persist fix of another phone, maybe google will fix it on november update. in any case, backup your persist partition first. I didn't do that, and now I have a working phone but lost all my original configuration files for my sensors, and I'm using some other configuration files, so not really ideal.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] pahlerc1:
so I had the google stock rom "pimped" all the way out, but since this next monday will be the first monday of the month --> September Security Update. I decided to go ahead and flash this. I had already flashed the Android 10 to both slots for the Oct update. So just to be safe i removed all my magisk modules then booted to bootloader and followed instructions. So far all is well! got all my apps back on the phone.

thanks for the first ROM available on Android 10. Seems pretty smooth so far.. the flasher in me just had to try it! Also i was able to flash the patched boot.img with unicornblood kernel just as expected!

following instructions does wonders!! :)

thanks again!
[MTCD Android Head Units General] omit94:
My head unit doesn't turn on 9 out of 10 times. The screen stays black. I've tried flashing different MCU firmwares, different ROMs, unplugging and plugging back in the power, holding the power button until the lights flash. Nothing helps.

Anyone with the same problem? Could it be the PX5 core board? It's an Erisin 5062GD Android 6 unit.
[MTCD Android Head Units General] marchnz:
What are your results from checking power to the unit? What other tests have been made?

If no fault with power feed, what does the reseller suggest?
[MTCD Android Head Units General] omit94:
I've ran it from the car as intended and also used +12V from an ATX power supply. Both give the same results: Very rarely will it actually turn on.

I haven't yet contacted the seller because I've bought it over a year ago, but I'll do that too.

Update: I've ordered a new PX5 core board to test. Will update the post when I try it.
[Tilt, TyTN II, MDA Vario III General] gqstatus0685:
Is there a way to find out whose calling my phone on private? Is it true that on your monthly statement private numbers are not shown but instead show the actually number?
[Tilt, TyTN II, MDA Vario III General] samo.chan:
regarding monthly bills, I don't know if you get charged for recieving calls (we don't over here), but it will be VERY unliekly the number will pop up on the bill... Something against privacy, I guess.

It would also be unlikely that you can get the private number to show on your phone, because these the number is broadcasted from the phoner's side, and if they don't broadcat it, then you won't get it!

Hope that clears things up
[Tilt, TyTN II, MDA Vario III General] whk:
To my knowledge the following is true - even if you BLOCK your caller ID it is still broadcast - however - there must be two levels at the receiving end - here are my thoughts as to why this must be true -

In the states if you call 911 (even with your callerid blocked) they still have your phone number - TRUST ME - callerID displays at the emergency end even with it blocked. SO -

CALLERID blocking does not really BLOCK the sending of this number - it merely puts a code on it (or something like that) so that the receiving phone says - AHHHH - PRIVATE.

Now - as has already been said - it is obvious that if you do not want your phone number known and PAY to have it blocked - why on earth would you let someone on the other end see it?

Bill
[Tilt, TyTN II, MDA Vario III General] gwnorth:
You're correct that there is just a flag set to not display the number (as opposed to it not being sent at all, and yes, that is why 911 operators still see the number). But the phone company here in the USA would need a court order to NOT observe those flags, so they are not going to violate the law and give you the number just because you want it.

There is also equipment to capture and see the number despite the block flag, but I know they are illegal to use by private citizens or corporations, and it may even be illegal to buy them.
[Tilt, TyTN II, MDA Vario III General] drutort:
can someone explain to me how it is possible to have fake numbers show up? shouldn’t that be illegal too? i had partial numbers, or things that are just not possible... i heard this is spam/ads and or done somehow with the internet...
[Tilt, TyTN II, MDA Vario III General] whk:
It is getting less and less true - but there are carriers in some areas of the country that have not implemented callerid yet - frequently SPAMMERS and other less reputable people specifically use these carriers so that they can get an unblocked number that does not pass on their number - if you get my meaning. ;)

Sometimes 800 numbers (toll free) will not pass on their number correctly but not block it - since people can now pay to BLOCK callers with specifically BLOCKED phone numbers having a number that is not blocked but does not pass on their number can be worth its weight in gold. (At least they THINK so. What ever possesses someone to think that someone who BLOCKS blocked numbers would appreciate THEM getting through and actually purchase what they are selling is beyond me.

Bill
[Tilt, TyTN II, MDA Vario III General] gqstatus0685:
I was only going by what someone told me. They told me that if someone calls you private take a note of time and date and look on your statement. The number will display on your bill. I'm asking because I have these girls calling my number from a private number. They always call me saying that I'm ****ing hot, sexy, blah blah blah. They know my name too. Just wanted to see who it was. Curiosity always killed the cat.
[Tilt, TyTN II, MDA Vario III General] kareeem:
There are certain sites that will let you do this (for a monthly fee of course). It will let you call and it'll appear whatever the caller wants it to appear.
[Tilt, TyTN II, MDA Vario III General] drutort:
thats just messed up, so your ex could drive you crazy huh... or someone who wants to get on your case for ****z and giggles, they can... this is beyond me why they would even let something like this happen.

How is something like that legal?
[Tilt, TyTN II, MDA Vario III General] gqstatus0685:
it's life. The power of technology and the internet.
[Tilt, TyTN II, MDA Vario III General] xxx_mosh:
or you can do it yourself for free its called caller id spoofing
[Tilt, TyTN II, MDA Vario III General] gqstatus0685:
Where do I start?
[Tilt, TyTN II, MDA Vario III General] denco7:
Hey drutort, are you a 60 year old bald, fat, perv from Seattle or a hot 16yr old farmgirl with big ------- from Nebraska or a 30 something tech geek who is into gadgets from Arizona ? No one here knows. You can be whomever you want these days and we will never find out. ( at least without a court order)

I remind my teenagers of this constantly, everytime they " step " into a chat room.
[Tilt, TyTN II, MDA Vario III General] JimmyMcGee:
I think this video somes up my feelings on this issue... http://www.youtube.com/watch?v=Uu1RP34FLXU
[Samsung Galaxy J7 Questions & Answers] dodo2244:
Hi Devs!

Are there any Devs still interested in the ooold Samsung J700 F/M/H from 2015 ?:silly:

Anyways, now that there's an [I]OFFICIAL LineageOS 16[/I] for the Samsung S5 Neo, that maybe our old workhorse J7 could get some lineage love?

Please! Please?!? :):good:

Samsung S5 Neo ?? that cousin of ours shares the same chipset and gpu as our J7. So I assume porting the LOS is possible.

Galaxy J700F/M/H compared to S5 Neo

S5 Neo LineageOS 16 official download page

Please Devs !
[Samsung Galaxy J7 Questions & Answers] dodo2244:
>> 100 views, no willing Devs amongst you ??
[Samsung Galaxy J7 Questions & Answers] vote4obama2008:
bump...

bump
[Samsung Galaxy J7 Questions & Answers] El_Diabolical:
Yeah I'm super interested in a Lineage OS Build for the J7 2015's,I'm currently on OSKiller v2 Final Port for my J7 Exynos 7580 (MetroPCS)
[Samsung Galaxy J7 Questions & Answers] tasnim_tamim:
My old and very underpowered phone compared to J7, Galaxy Grand Prime has LineageOS 16 almost stable even though dev and people are abandoning that device. Seeing J7 not having LOS 16 is quite disappointing. :(
[Samsung Galaxy J7 Questions & Answers] Ah9m7ed:
I know this is old but there is a build for j7 avaliable here https://sourceforge.net/projects/lo...181003-TEST1-UNOFFICIAL-j7eltexx.zip/download

the only problem is that the sim cards don't work and I don't own the rom