yashsingh1/xdaforums huggingface dataset:
[Asus ZenFone Max Pro M1  Questions & Answers] akhil850:
Just Flash Stock rom via fastboot to fix this issue. Dont bother about bootloader getting relocked.( U may unlock it ri8 after flashing)

And one more thing.

If u flash Decrypt.zip used for Stock Oreo roms on Stock Pie, you will loose wifi and fingerprint options.(I experimented this thoroughly)

So flash decrypt.zip for pie on Pie Stock(Beta or Stable).

Tested personally and worked fine.:good:

Hit thanks if it helped,:svetius:
[Asus ZenFone Max Pro M1  Questions & Answers] defurious:
This must be the problem then because I didn't know there was a decrypt for pie beta and i usually do flash decrypt coz i have a phobia that my internal data will get encrypted with no password to recover. ?

Can you provide a link for pie beta decrypt please? I can't find it here in xda. Thanks
[Asus ZenFone Max Pro M1  Questions & Answers] akhil850:
Here https://xdaforums.com/asus-zenfone-max-pro-m1/how-to/decrypt-zip-asus-stock-pie-roms-t3923265

Hit thanks if i helped.:svetius:
[MX Player] fede01_8:
When I rewind a couple of seconds, it goes back to the same spot I was watching. I have to swipe my finger longer than I want to rewind or fast forward.
[MX Player] MXPlayer:
Thanks for choosing MX.

MX Player always seeks to a keyframe position for the better responsiveness and performance. It may happen when there is no key-frame at the position where you are trying to seek. Request you to try the following for timestamp accurate seeking.

Open MX Player Settings > Player.

Disable Fast Seeking.

Now Play the video in HW+ decoder or change the decoder to HW+ after starting the playback.

Now check again.

If the problem persists, kindly provide us with a sample file and the position you were trying to reach. It will help us to investigate further.
[MX Player] fede01_8:
This worked, thanks!
[Moto X4 Questions & Answers] bluedragon12:
its name like this but i cant find a source from where to download it PAYTON_FI_PPW29.69-39-1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
[Moto X4 Questions & Answers] glenb77:
i was able to upgrade to the march patch on rooted fi phone, but have not heard or had notice on phone of upgrade to april patch set. i would like to get the march xml.zip file so it could be used to upgrade to next ota but i have not seen it in the mirror. does anyone know where the march file can be downloaded from. ??
[Moto X4 Questions & Answers] dhruvagg:
https://drive.google.com/open?id=1Bpc8XxWHs7IJllIfTV8uw3bplg-Hk58q
[Moto X4 Questions & Answers] LankiCat:
Thanks! This is the April update right? It ends in -2, The March one was -1. My question is: is there a place to find them every month? I have had a hard time finding them in the past and had to load older versions then go through three or four updates to get current. For some reason un-rooting my phone doesn't help me take the OTA
[Google Pixel 3 XL Guides, News, & Discussion] farfegnugen:
I just have a couple questions pls-

1) Do the above instructions work on the Verizon Pixel 3 XL

2) I'm currently runned the official Android Q Beta (April 5). Do I need to leave the beta, then restore back to stock Android P (and do I do all those updates before starting root instructions)?
[Google Pixel 3 XL Guides, News, & Discussion] mcwups1:
Should I be concerned if my phone hasn't informed me of an April update?

I don't remember if I unlocked the bootloader before or after the updates to the March security update. Does it matter?
[Google Pixel 3 XL Guides, News, & Discussion] HACK3DANDR0ID:
Is your bootoader Locked or Unlocked?

---------- Post added at 08:08 AM ---------- Previous post was at 08:07 AM ----------

No it does NOT matter which build you unlocked your BL

*edit*

Try to go into settings and force the update or you can always flash the entire factory img for april
[Google Pixel 3 XL Guides, News, & Discussion] rczrider:
1.) If you somehow have an unlocked bootloader, yes, it would work for the Verizon Pixel 3 XL. However, I was under the impression that Google will not unlock the BL for the Verizon variant and there is currently no way to "hack" it.

2.) It should work the same whether you're on P or Q, though if you want to remain with Q, make sure you download the beta files directly from Google (rather than the P images) and use Magisk 19.0 instead of 18.1.

You can force it to check for updates; when you unlocked the BL shouldn't matter if you're using a patched boot image.
[Google Pixel 3 XL Guides, News, & Discussion] farfegnugen:
I haven't done anything to the phone since I got it 3 weeks ago but hoping to. Can the VZ version be unlocked? If so please point me in the right direction. :)
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
No, but they working on finding a way to unlock it: [Bounty] Unlock Bootloader VZW Pixel 3 XL by coolhandz
[Google Pixel 3 XL Guides, News, & Discussion] farfegnugen:
Thanks so much for the info! Its difficult trying to find the current status of all the diff devices' root statuses.
[Google Pixel 3 XL Guides, News, & Discussion] CadTechBGMC:
Thanks for this guide, when using the flash-all.bat and wiping the device will this method flash to both slots?
[Google Pixel 3 XL Guides, News, & Discussion] SacredDeviL666:
yes, if you are flashing with wipe all option (without removing -w) it does flash to both slots.
[Google Pixel 3 XL Guides, News, & Discussion] EMJI79:
Regarding getting to fastboot:

Since I have flashed April security update and after lightly bricking my Pixel 3Xl, (I have not lost data but I was unable to boot till solving the brick), the phone doesn't stay in fastboot when I use the adb command to get into it and all I can do to get to stay in fastboot is the power and volume down combo for more than 40 seconds.

I have my pixel working perfectly with root and kirisakura kernel but it is a bit of a pain getting to boot TWRP from fastboot for flashing stuff.
[Google Pixel 3 XL Guides, News, & Discussion] SacredDeviL666:
yeah if i try to get into fastboot directly from a power on state it doesn't stick on fastboot blinks for a second and then starts with reboot process, probably we are pressing it too long.

what i do normally is to power off the device first wait for few seconds then then use key combination to get it to fastboot from power-off state. Booting from fastboot to twrp never had any issues unless i had messed up the twrp installation due to some mess i did.
[Google Pixel 3 XL Guides, News, & Discussion] EMJI79:
I have to press the keys 40 seconds even from power off.
[Google Pixel 3 XL Guides, News, & Discussion] SacredDeviL666:
definitely not 40seconds from power off state for me. not sure whats happening there :(
[Google Pixel 3 XL Guides, News, & Discussion] CadTechBGMC:
Maybe a short video would be a help to some of us newbies
[Google Pixel 3 XL Guides, News, & Discussion] Drashnar:
Dumb question. Probably gonna upgrade from an original Pixel XL soon. As long as I buy it from store.google.com, I should be able to unlock the bootloader without worrying about a crack/hack, correct? Thanks!
[Google Pixel 3 XL Guides, News, & Discussion] sliding_billy:
That is correct. I made the same switch from an OG Pixel and Pixel XL to P3 and P3XL right after release. Unlock the bootloader before you mess around a lot since it will do a factory reset.
[Google Pixel 3 XL Guides, News, & Discussion] mcwups1:
How about backups? Does anyone backup and restore, or not?

If so, how do you do it with this 2 partition system?
[Google Pixel 3 XL Guides, News, & Discussion] kingrat:
installed and I like it. I cant get the clock off the lock screen. all settings says it is off.

wished it had MicroG installed instead of gapps
[Google Pixel 3 XL Guides, News, & Discussion] GartimusPrime:
I recently got my Pixel 3 XL and got it home and unlocked the bootloader installed TWRP and flashed Magisk before I did anything, probably because that's what I have done with every device I have had for years.

I am wondering how difficult it is to go back to stock? I havent done anything with root and would like to try Android Q Beta, thanks
[Google Pixel 3 XL Guides, News, & Discussion] wangdaning:
Flash the most recent factory image.
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
Do #4 'keep data' in the other guide.
[Google Pixel 3 XL Guides, News, & Discussion] kingrat:
i just did this as well, you extract the oem and in fastboot enter "flash-all"
[Google Pixel 3 XL Guides, News, & Discussion] GartimusPrime:
So with TWRP and Magisk installed that's all I do? The only reason I am asking is because I have read some people have bricked their devices by trying to go back to stock.

So once I figure out how, I just flash the latest factory image and that's it?
[Google Pixel 3 XL Guides, News, & Discussion] kingrat:
That's what I did and I screwed mine up a few times. It would only boot to fastboot. I downloaded the latest version and unzipped it and put it in the same directory with adb
[Google Pixel 3 XL Guides, News, & Discussion] wangdaning:
Well, if all you changed was adding TWRP and Magisk, then you just need to flash factory boot.img
[Google Pixel 3 XL Guides, News, & Discussion] yoderz:
Thanks for the guide! I tried to do everything using another tutorial and it didn't end very well. This was great. The only thing you might want to add for Windows 10 users is to include .\ when using the Power Shell for adb and fastboot commands.
[Google Pixel 3 XL Guides, News, & Discussion] morphlinqq:
This stuff with photo uploading in web and gives you results is awesome.
[Google Pixel 3 XL Guides, News, & Discussion] GartimusPrime:
Ok, so here I am again! I have been running Android Q Beta 5 and it has been great. I wanted to go back to Pie so I downloaded the latest firmware and followed googles directions on how flash via ADB sideload. All was going well, then it aborted and rebooted back to Q, am I missing something?
[Google Pixel 3 XL Guides, News, & Discussion] tmenzzz:
after updating to Q i can no longer boot into twrp via "fastboot boot twrp.img" using 3.3. is there a new procedure? cmd windows says finished then the phone boots into the OS and not the recovery.
[Google Pixel 3 XL Guides, News, & Discussion] Eudeferrer:
TWRP had not been updated yet to work on Android 10. We must wait patiently for developer to do his magic.

Sent from my Pixel 3 XL
[Google Pixel 3 XL Guides, News, & Discussion] GROOVYJOSHCLARK:
Applying OTA via ADB sideload

[*]This does not require an unlocked bootloader, but does require USB debugging (see above)

I am of course locked bootloader (Verizon), so I was trying to follow the steps to restore my original boot.img (pulled from full firmware release from Google) to get sideload working for a full OTA to start over fresh. I went from official P, to beta Q, then to official 10 (from the Beta), so I was going to flash back the stock image to install a full OTA to clean up the device (I hate OTA upgrades). I am unable to flash the boot.img with the locked bootloader. Any ideas, I am using the latest ADB from Google and its in my Win10 path with USB debugging enabled in dev options? I am more asking if we know this actually works with a locked BL on the Verizon crosshatch version (OR if I did something wrong):

View attachment 4817359

---EDIT, wait, may have been my fault, trying something new---

Yup sideloading the OTA finally worked, but I never had to flash the boot.img, that never worked because I am locked. Sideloading worked though once I was able to get recovery working.
[Google Pixel 3 XL Guides, News, & Discussion] sliding_billy:
For reference, you cannot flash the boot.img on a locked BL. It is not an ADB command but a fastboot command that works in BL mode.
[Google Pixel 3 XL Guides, News, & Discussion] truongtvd1992:
Hi I using Pixel 3 Verizon. but i cannot slideloading. My device is alert "cannot find valid operating system". I cannot boot to recovery
[Google Pixel 3 XL Guides, News, & Discussion] dtgo:
same issue here , i cant flash anything and recovery is gone
[Google Pixel 3 XL Guides, News, & Discussion] catass:
Stuck on fastboot, fastboot not recognizing phone in adb device list

Hi,

I recently attempted to root my Pixel 3 XL with Magisk. USB debugging is enabled. OEM bootloader is unlocked.

I was able to flash my magisk_patched.img using fastboot, but after rebooting the bootloader, it gets stuck on fastboot with Enter Reason: error boot prepare.

At this point I'm ok with merely wiping with flash-all.bat, but the command prompt tells me that it is not a valid command or file. What am I doing wrong?

Also, when running the adb devices command, it returns an empty list, so does this mean fastboot/adb is not recognizing my phone?
[Google Pixel 3 XL Guides, News, & Discussion] crixley:
Put the files in the platform tools folder and CMD cd to that directory, then try.

Also you shouldn't need to wipe. Remove the -w from the flash all batch file using notepad or whatever.
[Google Pixel 3 XL Guides, News, & Discussion] catass:
Which exact files do I move to the directory?
[Google Pixel 3 XL Guides, News, & Discussion] crixley:
All the files you downloaded from the zip. There is a folder inside and you place all the files from that folder, including the flash all file, in there.
[Google Pixel 3 XL Guides, News, & Discussion] Juls317:
So we're just still SOL on Android 10 TWRP, right? Is there another way to get root/Magisk installed?
[Google Pixel 3 XL Guides, News, & Discussion] wangdaning:
Follow the guide on magisk github.
[Google Pixel 3 XL Guides, News, & Discussion] spotmark:
April images are up. Sideloaded, rooted, good to go.
[Google Pixel 3 XL Guides, News, & Discussion] dbama1:
How did you do it?
[Google Pixel 3 XL Guides, News, & Discussion] spotmark:
Sideloaded the OTA, rebooted, and then rooted the traditional way by patching the boot image and then flashing it in fastboot.
[Google Pixel 3 XL Guides, News, & Discussion] dbama1:
Is there a guide to patch the boot image?
[Google Pixel 3 XL Guides, News, & Discussion] spotmark:
You might want to start with the OP.
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
New Update: SDK Platform-Tools: r30.0.0
[Google Pixel 3 XL Guides, News, & Discussion] sharky17:
Can someone please help. I'm trying to flash the stock image via fastboot and when I do the part fastboot -w update image.zip, I'm getting an error when it goes to the "sending product" part it fails. I'm not sure what else to do. Image matches the version the phone was on. And now I can't boot to anything except bootloader. This was on Android 10 005 update (I think that is the April one)

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

Bootloader Version...: b1c1-0.2-6085603

Baseband Version.....: g845-00096-200114-B-6134206

Serial Number........: 91PY17NNE

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

extracting android-info.txt (0 MB) to RAM...

Checking 'product' OKAY [ 0.055s]

Checking 'version-bootloader' OKAY [ 0.051s]

Checking 'version-baseband' OKAY [ 0.045s]

Setting current slot to 'a' OKAY [ 0.372s]

extracting boot.img (64 MB) to disk... took 0.240s

archive does not contain 'boot.sig'

Sending 'boot_a' (65536 KB) OKAY [ 0.319s]

Writing 'boot_a' OKAY [ 0.357s]

extracting dtbo.img (8 MB) to disk... took 0.021s

archive does not contain 'dtbo.sig'

Sending 'dtbo_a' (8192 KB) OKAY [ 0.128s]

Writing 'dtbo_a' OKAY [ 0.101s]

archive does not contain 'dt.img'

archive does not contain 'recovery.img'

extracting vbmeta.img (0 MB) to disk... took 0.001s

archive does not contain 'vbmeta.sig'

Sending 'vbmeta_a' (4 KB) OKAY [ 0.118s]

Writing 'vbmeta_a' OKAY [ 0.060s]

archive does not contain 'vbmeta_system.img'

archive does not contain 'vendor_boot.img'

extracting super_empty.img (0 MB) to disk... took 0.001s

Rebooting into fastboot OKAY [ 0.058s]

< waiting for any device >

Sending 'system_a' (4 KB) OKAY [ 0.000s]

Updating super partition OKAY [ 0.007s]

Resizing 'product_a' OKAY [ 0.006s]

Resizing 'system_a' OKAY [ 0.005s]

Resizing 'vendor_a' OKAY [ 0.005s]

archive does not contain 'boot_other.img'

archive does not contain 'odm.img'

extracting product.img (1980 MB) to disk... took 9.912s

archive does not contain 'product.sig'

Sending 'product' (2027852 KB) FAILED (Write to device failed (Invalid argument))

fastboot: error: Command failed
[General Questions and Answers] shreyasjadhav:
PLEASE HELP ME ITS VERY URGENT AND SERIOUS ISSUE

I was trying to flash pixel experience rom on my moto g5s plus

i opened twrp

i didnt enterned password and then i clicked some other option, then i saw the twrp interface i thought i had done it correctly.

then i reboot to system

i was in my stock oreo rom factory reseted

i copied the zip file of pixel experience rom in my internal storage

i booted to twrp

backed up and wiped data

then i went to install the zip file, but i didnt find it

then i went to reboot to system,

it shows NO OS INSTALLED

i tried to restore

but it showed the messege error 255

i tried to install zip using sideloader but again the same error

i wiped again everything and now no backup

PLEASE TELL ME WHAT TO DO IM VERY SCARED NOW PLEASE PLEASE PLEASE HELP ME
[OnePlus 5T  Questions & Answers] halfbytecode:
I have tried a number of custom ROMs, Oreo and Pie based. They all have this issue where signal is mostly on zero bars, and it leads to flaky VoIP calls, and low data throughput on LTE. I have read even OOS has this flaky LTE, but it is masked to some extent.

However, I have also heard that some people only have this issue on custom ROMs and not OOS.

• Is there a way to fix the flaky LTE signal, on custom ROMs?

LTE signal used to be so much better, and reliable on Nexus 5, that I never even had to turn on WiFi.
[OnePlus 5T  Questions & Answers] Nobodyslight:
I can confirm that this really seems to affect custom roms more than Oxygen OS. For me this has affected my battery life, and i have a bit of a theory: the way android handles signal is that whatever the system reports as its signal affects what the system believes is the max data throughput (such as if your signal was really a 4G signal but you were being registered as a 3G, Android will only pull data as fast as it can believe a 3G signal can), the power it uses on the cellular antennas ( Less "signal" = more power drain). the reason i have come to think this is because i have been testing this theory on both custom roms and Oxygen OS, and in the same locations with the same kind of usage, and custom roms always seem to suffer the symptoms of a low signal, along with a lower reporting signal than Oxygen OS. This can either be due to custom rom devs using an inferior kernel than Oneplus uses, or its truly due to the signal reporting. i dont believe its the kernel, as this issue has been identical in all the custom roms i've been using (CRDroid, Pheonix, Omni, Treskmod, and even Lineage). now as for a solution....... I'm afraid we might be out of luck most people who COULD help live in higher reception areas so they don't understand how this affects those of us in lower reception ares, so they won't be much help as they don't really care. I can't really help because im in college and have two jobs and can't really afford to take the time to finally learn to develop on android (C++ takes enough time right now as it is)(and even though ive been doing android stuff for 8 years i still havent learned any lawl). and ive looked through our forums and some others and havent really found anything of help to us. If I remember correctly, it seems like Havoc OS would actually do like oxygen OS and "Lie" about the reception, but i dont think its had an update in a while. so i think the best bet is just to keep asking around and maybe someone will see this forum and have some help of some sort.
[OnePlus 5T  Questions & Answers] halfbytecode:
Thanks for the reply. I wonder if reporting the signal like on OOS would help.

I also have mobile data issues, like voice being muted on VoIP calls, when signal drops to 0 bars.

I hope it gets fixed in custom ROMs.
[OnePlus 5T  Questions & Answers] halfbytecode:
[MENTION=3208754]codeworkx[/MENTION] suggested changing the preferred network type to Global, to an user having LTE signal issues on just custom ROMs.

Looking at the network type in phone info, after dialing *#*#4636#*#*, it appears to be LTE/CDMA/UMTS auto (PRL).

Source: https://xdaforums.com/showthread.php?p=78517417
[OnePlus 5T  Questions & Answers] Nobodyslight:
I'll try this again and see, but before I tried this and it didn't really help. AT&T in my area is just horrible and unusable. when I went to D.C. this last summer i had better service and had none of these problems.. maybe someone will make a magisk module that can fix all this...
[OnePlus 5T  Questions & Answers] halfbytecode:
After setting the preferred network type to Global, LTE signal and throughput seem to be close to what Nexus 5 used to have, in the exact same area and network provider.

Webpages also seem to load a tad faster. I will still keep an eye on the signal today.
[OnePlus 5T  Questions & Answers] Manaljn:
I second this. Have been using AEX for a while now and the signal issue persists which makes me want to go back to stock OOS. I get a max of 2 bars and battery life has taken a hit with SOT of 5-6 hrs on average, before it would be between 8-9 hrs. It's a hard price to pay for all the customization but I feel I'll go back to stock so that I can have better call/signal.

I have tried [MENTION=3208754]codeworkx[/MENTION]'s suggestion but that didn't help much. Hopefully there's a solution soon.
[OnePlus 5T  Questions & Answers] neilrayer:
Yeah me too have that issue. At 1st I thought that the tower nearby my area is not proper. But it's the issue with custom rom
[OnePlus 5T  Questions & Answers] Nobodyslight:
What network type do you guys have? I'm on at&t, and I'm gonna try fiddling with apn settings and other stuff and see if there's anything I can figure out, I'm wondering if it's a frequency thing that custom roms struggle with.
[OnePlus 5T  Questions & Answers] neilrayer:
I am using Jio . It's india
[OnePlus 5T  Questions & Answers] Manaljn:
Updated to AEX 1.9. Network has improved a lot. I've currently set on Global and I'm getting LTE on Airtel India. Connectivity is on par with stock OOS. If you're on AEX, I'd recommend the update.
[OnePlus 5T  Questions & Answers] halfbytecode:
Thanks for pointing that out. I looked at the changelog for AEX 1.9, and stumbled upon this change:

https://gitlab.com/APOPHIS9283/frameworks_base/commit/7eee9cb50155c01f03d76f050dd956c9a16abefa

It seems to precisely deal with the signal bars. I guess it's time to request other ROM developers to include this commit in their ROMs.
[OnePlus 5T  Questions & Answers] halfbytecode:
Found more about this. Apparently Xiaomi phones also have similar signal issues on custom ROMs. Fix is the same as above, but there are other ways of implementing the fix.

https://piunikaweb.com/2019/01/22/x...tual-cellular-signal-strength-from-end-users/

Edit: Apparently Samsung, Google, LG, Xiaomi, OnePlus and possibly other manufacturers have this change made in stock ROMs!
[OnePlus 5T  Questions & Answers] halfbytecode:
Carbon ROM has a few commits related to fixing flaky LTE signal, that are not the same as ones mentioned above.

Carbon ROM may not have LTE signal issues, too. It needs to be tested though.
[OnePlus 5T  Questions & Answers] sleepwalking0593:
But this would only change visual representation of signal what about change in actual signal
[OnePlus 5T  Questions & Answers] Nobodyslight:
I forgot about the testing menu accessed by the activity launcher (I'm using AOSiP) and I changed two options: set my radio band country (in the 3 dot menu) to America, and also changed my network type there to LTE/UMTS (PRL Auto) . The network has been slightly improved, but I may go try AEX and see if it's better there.