yashsingh1/xdaforums huggingface dataset:
[OnePlus 8 Pro Questions & Answers] hole896:
Yep, already contacted OnePlus the other day and they are supposed to be setting up a remote session, but I haven't heard from them yet...
[Huawei P40 Questions & Answers] jasonhelene:
Hello,

Is there any possibility for a port from Lineage OS to the P40 Lite E ? This google thing is a big problem, even after installing some apps are not working as they should, without a custom firmware this phone is pretty useless.

Is there any change that we can get some custom firmware over it? :mad:

Thank you in advance.
[Huawei P40 Questions & Answers] bender_007:
Sure, so..you got the bootloader unlocked?
[Huawei P40 Questions & Answers] Billabomb75:
There was a way but looks like the place i used last year doesnt support the P20 and up series.

https://www.dc-unlocker.com/supported_models_1/huawei_phones
[Huawei P40 Questions & Answers] naack:
as far as i know there is a test point for this model, could that be useful ? thats usually useful for unlocking the phone which also needs an unlocked bootloader.
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] SomebodySomebody:
Anybody had a similar issue and fixed it? I have heard that in order to fix it I need to download a different version of my operation system.
[SuperSU] Marnes:
Context: my motorola g4 is 5 years old and saw many different kinds of root attempts and amateurish handling (like modifying the system image) in its early days. I settled on magisk when it became a thing. Now I'm trying to go back to being rootless, including removing left-behind stuff like addon.d scripts.

TWRP shows a /supersu folder in the root fs, containing the usual apk, sh scripts, etc. I can delete this folder, but next time I boot my device (even just recovery!) it gets restored _somehow_. This is the only remaining trace of rooting I'm aware of, aside from the image just "not being untouched stock" anymore.

I'd like to get this folder permanently removed, without erasing my data.

Things I've tried:

- flash the stock rom: somehow it's defective (Package Installer crashes and I can't fix it by any means), despite it being the same zip I flashed two years ago and still use today, so this is not an option

- flashed stock boot

- unSU https://xdaforums.com/showpost.php?p=63615067&postcount=2459

- installed supersu just to run its own unroot procedure, then ran unsu again, then flashed stock boot again

It just keeps coming back after every time I delete it and I'm out of ideas to stop it. All the threads I've found online offered only the above solutions that don't work.

Thanks for any good tips
[SuperSU] Didgeridoohan:
[MENTION=5870277]Marnes[/MENTION] That sounds like it's TWRP's superuser. It won't exist if you are not booted to TWRP and it'll be repopulated everytime you boot to TWRP...
[SuperSU] Marnes:
[MENTION=4667597]Didgeridoohan[/MENTION] I hadn't considered that possibility... I guess there's no way to verify it since checking after a regular boot if the folder is there would require rooting again. Thanks for the input!
[Google Pixel 5 Questions & Answers] jobhax:
What's everyone's view of rooting the pixel unlocked version? What features won't work? I know knox for samsung trips when unlocking. Is it the same concept with Pixels? My last device similar was a nexus 6 so yeah..
[Google Pixel 5 Questions & Answers] SteveYoungs:
Any feature that relies on Safetynet won't work and there is simply no way around that.
[Google Pixel 5 Questions & Answers] navalynt:
With Samsung, KNOX is a "fuse" that gets tripped so after you unlock the bootloader there's no going back. It'll forever know the bootloader has been unlocked at some point which messes with certain features (depending on make/model). With the Pixel phones you can flash the stock software and then re-lock the bootloader if you want. Once re-locked the OS sees the factory state and everything works as usual. Just make sure you've got the stock software flashed before you re-lock the bootloader or you risk bricking the device.

As a side note, with biometric security, make sure you've properly logged out of your Google account and removed all stored fingerprints or faces BEFORE you unlock. The unlocking process will wipe the device but your biometrics are still stored. If that happens you have to go through the setup process without biometrics and then perform a "proper" factory reset within the Android OS in order to get biometrics working again.

Of course the Pixel 5 is a new phone, so I'm giving this info based on currently released devices. There are always risks when you alter the factory state so be warned. There's a phrase my old boss used to use: "Pioneers take the arrows, settlers take the land." Not very PC but the underlying concept is sound.
[Google Pixel 5 Questions & Answers] kboya:
I'll root asap. These days, I use it mainly for effective Adblock. The occasional app goes wonky, but it's a game of cat and mouse with safety-net.

YMMV etc
[Google Pixel 5 Questions & Answers] SteveYoungs:
The cat and mouse game is over, Google won. With hardware backed encrypted key negotiation it is no longer possible or feasible to beat. TNMTV (There's No Mileage To Vary)

That doesn't mean you can't root, just that there are consequences. For me, those consequences far outweigh any perceived benefit of having root access. I won't be rooting any more phones.
[Google Pixel 5 Questions & Answers] likepeas:
What's the best adblocker for a non-rooted phone right now?
[Google Pixel 5 Questions & Answers] Nightwish1976:
Guys, since Android 9 you don't have to root in order to adblock. Just use the private DNS option together with something like nextdns.io . It's also battery efficient, since it's not a VPN.
[Google Pixel 5 Questions & Answers] kboya:
We'll see what happens because, as you make clear when you include experiences, MAV (Mileage Always Varies).

---------- Post added at 05:20 PM ---------- Previous post was at 05:15 PM ----------

True, but when I tried that after 9's release it wasn't particularly effective or at least not as effective as Adaway w Magisk's systemless solution. Maybe I'll give it another go on the P5.
[Google Pixel 5 Questions & Answers] saturday_night:
Blockada, but download the App from the developer Website (play store Version doesnt get Updates Quick)

Pixel 5 will be the first device i dont plan to unlock+root, most benefits of rooting are gone in the last years because they got baked into Android. For adblocking there is Blockada which is as good as rooted adblock. I dont need a custom rom with stock clean Android and monthly Updates anymore. For debloating you dont need root, just a PC so i am going to deactivate most Google Apps.
[Google Pixel 5 Questions & Answers] ridobe:
Adblock so has a non-root version now.
[Google Pixel 5 Questions & Answers] SteveYoungs:
Prediction: I'll eventually die of old age and you still won't be passing Safetynet. ☺
[Google Pixel 5 Questions & Answers] vandyman:
If you know what you are doing there is no issues with Android 11, Magisk and safety net.

I can still use Google Pay and my banking apps without modules and nonsense coding. Just use Magisk and that is it. Oh of course you will need to hide a few apps in the Magisk settings.
[Google Pixel 5 Questions & Answers] jimv1983:
One thing to keep in mind is warranty and insurance (if you have insurance) claims.

If you have to use the warranty or insurance and you are unable to revert to factory default then warranty and insurance claims will be a huge pain.
[Google Pixel 5 Questions & Answers] SteveYoungs:
Sorry, but no. See: https://www.xda-developers.com/safetynet-hardware-attestation-hide-root-magisk
[Google Pixel 5 Questions & Answers] vandyman:
Anything is possible, we go through this year after year with new updates to the software.

Google has always aloud its devices to have an unlocked boot loader and to be developed.

I personally don't see Google closing down its development. If they do, they will be out of the phone business. Most peeps buy the Google device for the freedom of development. I for one would buy something different if I could not root anymore.

Now for other manufacturers, it is a lot harder for them because they have there own software for their hardware and it is not compatible with the Google OS.
[Google Pixel 5 Questions & Answers] Eudeferrer:
The Verizon versions of the Google Pixel 3Xl were locked down. I wouldn't say Giggle always allowed phones to be rooted. However, the ones sold by Google were rootable.

Sent from my Pixel 3 XL
[Google Pixel 5 Questions & Answers] vandyman:
You are right. Verizon versions of Google devices will always be locked down.

If I remember correctly the last and only time that version allowed a Google unlocked device was a Samsung/Google Galaxy Nexus.
[Google Pixel 5 Questions & Answers] OhioYJ:
You said your not rooted right? You can still force basic key attestation (only needed for some devices), change device fingerprint, etc. Lots of things to do to pass safety net at the moment. Has worked fine for me ever since topjohnwu releaased that news.
[Google Pixel 5 Questions & Answers] SteveYoungs:
Hardware attestation does not prevent you from unlocking your boot loader, and it does not prevent you from rooting. What it does do is make passing Safetynet impossible if you are rooted, unlocked boot loader.

This is not something that will one day be worked around. The days of passing Safetynet on a rooted device are behind us.
[Google Pixel 5 Questions & Answers] vandyman:
Nothing has changed yet! I still can use Gpay with Magisk and without any add on.
[Google Pixel 5 Questions & Answers] sidhaarthm:
For those who have received their Pixel 5 today, anyone unlocked their bootloader? I am aware we will need to wait until the factory ROM is released to actually root the device.
[Google Pixel 5 Questions & Answers] ridobe:
You're right. I'd go ahead and unlock the bootloader but to your point, I'd wait to root. Today is release day everywhere but the US. I guess we have to wait until the 29th for the image drop?
[Google Pixel 5 Questions & Answers] SteveYoungs:
No. I said that I would not be rooting any phones from now on. My current phone, a Nexus 6, is rooted but it doesn't support hardware attestation so no worries there. ☺
[Google Pixel 5 Questions & Answers] sidhaarthm:
I've already unlocked the bootloader and set up the device to my liking. So once the stock images drop, I don't need to clean wipe storage ? Not sure when the images will be released though. Surely Google won't make us wait till the November update? On a side note, loving the silky smooth experience of the Pixel 5 so far. Display is absolutely gorgeous and the size is just right. I am extremely happy for the 4-5 hours I've used my phone :o
[Google Pixel 5 Questions & Answers] sacredsoul:
If you unlock the bootloader, does it trip SafetyNet?

Also, other than to root, is there any reason to unlock the BL? For custom recoveries and ROMs I believe?
[Google Pixel 5 Questions & Answers] Nightwish1976:
Yes.

And yes.
[Google Pixel 5 Questions & Answers] M94pok:
5g android phone with no hardware attestation

So, I've just brought a pixel 5, it's being delivered today, however I was totally unaware of this hardware attestation crap that they're pushing on pixels. Are there any 5g phones out there that do not have this hardware attestation and which do you guys reccomend?

I love the pixel but I need a root, unless there's a way to enable the following on an unrooted pixel?

Call recording

JamesDSP

System wide ad blocking.

If I can get them three things to work on P5 without rooting, that would be the dream scenario.. many thanks in advance ?
[Google Pixel 5 Questions & Answers] den_zel:
What exactly wouldn't work after rooting? I mean except for banking apps
[Google Pixel 5 Questions & Answers] jaythenut:
It's not adaway but works ok with no root will do for now

https://blokada.org/index.html
[Google Pixel 5 Questions & Answers] ridobe:
I don't mess with custom recoveries any more, and I can get around having root (would prefer not to have to) but I unlock the bootloader and flash the monthly full images every month manually. I have never taken an ota. Much cleaner and gives me a safety net.
[Google Pixel 5 Questions & Answers] Signor Rossi:
Use Pi-hole. And use a VPN to your home network when not at home.

Gesendet von meinem Nokia 9 mit Tapatalk
[Google Pixel 5 Questions & Answers] vandyman:
Google Pay. It's not a big deal for me, I only used it for vending machines anyway.

Custom Roms maybe, I really don't know. I have not used a Custom rom since Android 7.
[Google Pixel 5 Questions & Answers] den_zel:
OK, that doesn't sound like a bad deal. I anyway don't use Google Pay and also didn't use custom roms since a lot of companies are close to stock android.

So I guess I would prefer the advantages of rooting above using Google Pay.

Change my mind
[Google Pixel 5 Questions & Answers] ridobe:
Images are up.
[Google Pixel 5 Questions & Answers] matssa:
Tested flashing with latest magisk canary and it doesn't even pass the Google logo so might need to wait a bit

At least that's when I tried, maybe others will have better results?
[Google Pixel 5 Questions & Answers] M94pok:
Fingers crossed! Please let me know if you have any luck! I was so excited when I seen that the images were on the Google site ?
[Google Pixel 5 Questions & Answers] John Markley:
Just to be sure, will unlocking BL and thus tripping SafetyNet

disable

SafetyNet for protection from malicious apps/traffic, or just result in the warning message at boot-up?
[Google Pixel 5 Questions & Answers] dirtyreturn:
I think it was posted here already, but, under the network options in settings there's the option for private dns.

A service that's come in handy for me is NextDNS.io . AND, for unlimited dns queries it's just 1.99 per month.

I'm just thinking here, but, call recording https://play.google.com/store/apps/details?id=org.skvalex.cr

This app might work without root. IM not sure though.

And system wide volume increase in not sure.
[Google Pixel 5 Questions & Answers] YandereSan:
SafetyNet doesn't protect you against anything. You're thinking of Play Protect, which is hardly reliable as there is tons of malware on the Play Store. Only common sense will protect you.

It's progress. Before the phone was released, I wasn't even able to patch the boot image.
[Google Pixel 5 Questions & Answers] jaythenut:
Anyone managed to root

I can't seem to patch boot img with magisk
[Google Pixel 5 Questions & Answers] dethknite:
My P5 is still on the way... but I have a theory I that the boot.img patching may require a rooted phone to process properly. I patched the redfin P5 boot.img for Oct on my rooted phone with the latest magisk that should support the new v3 boot.img header... and was wondering if you or anyone might give it a try. I will be trying this when my P5 comes, unless a new version of Magisk comes out between then fixing the issue.

https://drive.google.com/file/d/1TPLfXsNw7eWlPeRv3zbfm76EDk8WR68M/view?usp=sharing
[Google Pixel 5 Questions & Answers] Raz0Rfail:
Hi I got mine P5 today and tried it aswell.

At first i downloaded the entire rom from https://developers.google.com/android/images

Then I unzipped the boot.img from it.

At third I installed magisk manager and tried to install Magisk 21.0 on the image, but it failed to create an patched boot.img.

I had the same thought as you and tried it to patch on my rooted Xperia XZ1 Compact, but same result.

I'll try your patched version.

Attached is the log from magisk:

- Device platform: arm64-v8a
- Copying image to cache
2026+0 records in
2026+0 records out
2074624 bytes (2.0MB) copied, 0.016505 seconds, 119.9MB/s
1381+1 records in
1381+1 records out
1415016 bytes (1.3MB) copied, 0.012911 seconds, 104.5MB/s
- Unpacking boot image
Parsing boot image: [/data/user_de/0/.pxazydnxywpiyhx/install/boot.img]
HEADER_VER [0]
KERNEL_SZ [11562673]
RAMDISK_SZ [369099082]
SECOND_SZ [0]
EXTRA_SZ [3]
PAGESIZE [0]
NAME []
CMDLINE []
CHECKSUM [0000000000000000000000000000000000000000000000000000000000000000]
Floating point exception
- Checking ramdisk status
- Stock boot image detected
- Patching ramdisk
Add entry [init] (0750)
Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[true]
Create directory [.backup] (0000)
Add entry [.backup/.magisk] (0000)
Dump cpio: [ramdisk.cpio]
Parsing boot image: [/data/user_de/0/.pxazydnxywpiyhx/install/boot.img]
HEADER_VER [0]
KERNEL_SZ [11562673]
RAMDISK_SZ [369099082]
SECOND_SZ [0]
EXTRA_SZ [3]
PAGESIZE [0]
NAME []
CMDLINE []
CHECKSUM [0000000000000000000000000000000000000000000000000000000000000000]
Floating point exception
- Repacking boot image
! Unable to repack boot image!
! Installation failed

EDIT:

Your patched version stuck only on a black Google Logo. I waited 10 Minutes and no change.
[Google Pixel 5 Questions & Answers] BokeB:
As far as i understand the image is already patched. You don't have to do this again. Just flash it.

If you want to patch by yourself you have to use canary magisk app at least. For me creating boot.img was fine with canary build but ended in a bootloop.
[Google Pixel 5 Questions & Answers] Raz0Rfail:
I tried magisk manager in canary build but failed aswell.

Nevermind had to reinstall magisk manager, now I could patch boot.img with magisk 21.004.

I did it on both devices.

On Pixel 5 I got the exact Filehash as dethknites boot.img

On Xperia XZ1 Compact the boot.img file hash was different.

So dethknites boot.img doesn't work, so I tried with Xperia Xz1 Compact patched version.

But result was same, stuck on Google Logo :(.

Magisk canary build Log:

- Device platform: arm64-v8a
- Copying image to cache
2026+0 records in
2026+0 records out
2074624 bytes (2.0MB) copied, 0.016170 seconds, 122.4MB/s
1381+1 records in
1381+1 records out
1415016 bytes (1.3MB) copied, 0.012914 seconds, 104.5MB/s
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
HEADER_VER [3]
KERNEL_SZ [11562673]
RAMDISK_SZ [14119455]
OS_VERSION [11.0.0]
OS_PATCH_LEVEL [2020-10]
PAGESIZE [4096]
CMDLINE []
KERNEL_FMT [lz4]
RAMDISK_FMT [lz4_legacy]
- Checking ramdisk status
Loading cpio: [ramdisk.cpio]
- Stock boot image detected
Loading cpio: [ramdisk.cpio]
- Patching ramdisk
Add entry [init] (0750)
Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[true]
Found fstab file [first_stage_ramdisk/fstab.sm7250]
Remove pattern [,avb=vbmeta_system]
Remove pattern [,avb=vbmeta_system]
Remove pattern [,avb=vbmeta]
Remove pattern [,avb]
Loading cpio: [ramdisk.cpio.orig]
Backup mismatch entry: [first_stage_ramdisk/fstab.sm7250] -> [.backup/first_stage_ramdisk/fstab.sm7250]
Backup mismatch entry: [init] -> [.backup/init]
Create directory [.backup] (0000)
Add entry [.backup/.magisk] (0000)
Dump cpio: [ramdisk.cpio]
Patch @ 0145FFC6 [736B69705F696E697472616D667300]->[77616E745F696E697472616D667300]
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
HEADER_VER [3]
KERNEL_SZ [11562673]
RAMDISK_SZ [14119455]
OS_VERSION [11.0.0]
OS_PATCH_LEVEL [2020-10]
PAGESIZE [4096]
CMDLINE []
- Repacking boot image
KERNEL_FMT [lz4]
RAMDISK_FMT [lz4_legacy]
Repack to boot image: [new-boot.img]
HEADER_VER [3]
KERNEL_SZ [11428111]
RAMDISK_SZ [14469359]
OS_VERSION [11.0.0]
OS_PATCH_LEVEL [2020-10]
PAGESIZE [4096]
CMDLINE []

****************************
Output file is written to
/storage/emulated/0/Download/magisk_patched.img
****************************
- All done!
[Google Pixel 5 Questions & Answers] Golf c:
Wu obviously doesn't have the device. He claims to have added Pixel 5 support to the latest Canary build. He failed. Blind building is bad.
[Google Pixel 5 Questions & Answers] spencer92a:
He said he "might" have everything ready
[Google Pixel 5 Questions & Answers] dethknite:
Thanks for checking... that is disappointing... hopefully the bug gets fixed soon enough. Perhaps pass along the magisk.log in the magisk issues thread on github if you have it.
[Google Pixel 5 Questions & Answers] Golf c:
Hence, the blind building
[Google Pixel 5 Questions & Answers] Raz0Rfail:
I only have the install logs to build the boot image.

Don't know how to get logs if Kernel can't boot up :(
[Google Pixel 5 Questions & Answers] androidfreak11:
so anyone rooted yet?
[Google Pixel 5 Questions & Answers] dethknite:
When the phone is booting.. have it plugged into your PC, and when you see the boot loading.. you should hear a sound of the USB and phone device when available... at this point you can use adb to gather some stuff.

To pull the entire logcat:

adb logcat -d > logcat.log

To tail the logcat:

adb logcat > logcat.log

To pull the kmsg files:

adb pull /proc/kmsg ./

adb pull /proc/last_kmsg ./

To pull the console-ramoops:

adb pull /sys/fs/pstore/console-ramoops ./
[Google Pixel 5 Questions & Answers] Tulsadiver:
That is one large boot.img. 98mb compared to the usual 65ish mb
[Google Pixel 5 Questions & Answers] Raz0Rfail:
At the Google Logo I have no sound from connecting a USB Device.

adb devices is empty aswell.

Device Manager doesn't change if i connect / disconnect the p5.

I only got connection in windows if the Word "Google" switched to G only. And with the boot images i tested it stuck only on "Google".

A friend said someone should have a look at the kernel source, who knows about this :D

https://android.googlesource.com/device/google/redfin-kernel/
[Google Pixel 5 Questions & Answers] dethknite:
The logcat can be ran on your pc before turning it on... it will wait.

adb logcat > logcat.log

If this doesn't work or get adb... you may not be able to get this info (also, turn adb debugging on in Android before rebooting/flashing the patched.img).

As for the kmsg.. you can also get them from recovery.. VolUp+Power.. go to recovery.

adb shell cat /proc/last_kmsg > last_kmsg.txt

adb shell cat /proc/kmsg > kmsg.txt

Logcat and kmsg would be the two helpful logs I would imagine for this...

This is a helpful post on gathering logs..

https://xdaforums.com/showthread.php?t=1520508

*EDIT: Nevermind.. you will not be able to get them from the stock recovery... I just tried.
[Google Pixel 5 Questions & Answers] wgrant:
Logs will be needed for root to get fixed sooner. Topjohnwu is a smart guy but those logs are crucial when developing for something you don't have.

You coming to the P5?
[Google Pixel 5 Questions & Answers] Tulsadiver:
I'm not planning on it. I don't really like hole punch cameras. I plan on modding some stuff for the Pixel 5 and 4a (5g) if possible.
[Google Pixel 5 Questions & Answers] Raz0Rfail:
The problem is that when I try to start the recovery mode, it returns directly to the fastboot mode where I can choose what I want to do.

If I may guess, there is no TWRP or an original recovery that I could flash for this either :(.

So I have no Idea to get the logs.

EDIT:

Flashed back stock Kernel, restarted and I got a logcat.log, but I don't know if this logcat.log is helpful.
[Google Pixel 5 Questions & Answers] Tulsadiver:
Check to see if your patched image is the same as mine.

https://www.androidfilehost.com/?fid=10763459528675565677
[Google Pixel 5 Questions & Answers] wgrant:
I figured I would give it a whirl and if I don't like I'll just return it and pay the restocking fee. Minor loss in my opinion.

It'll be good to have you dev for the phones though. You do some great work.
[Google Pixel 5 Questions & Answers] Raz0Rfail:
status_bar.xml ? is this an correct link, because don't know what to do with it.
[Google Pixel 5 Questions & Answers] wgrant:
Wrong url

Try - https://androidfilehost.com/?fid=10763459528675565692
[Google Pixel 5 Questions & Answers] Tulsadiver:
Sorry, lol! I've got two phones going.

https://www.androidfilehost.com/?fid=10763459528675565692
[Google Pixel 5 Questions & Answers] Raz0Rfail:
FileHash is exact as from my P5 and from dethknite:

Algorithm Hash

--------- ----

SHA256 B6D9937026C5A062962A974488E66F45F3E06ABF5AF1E545E2F03061BC070EB5
[Google Pixel 5 Questions & Answers] Tulsadiver:
Okay. Thought I'd try.
[Google Pixel 5 Questions & Answers] dethknite:
Sweet! If it is a logcat from the bootloop, it may have helpful info on where it is getting stuck...
[Google Pixel 5 Questions & Answers] androidfreak11:
does your rooted p5 start and work?