Search results

I literally flashed the Dec ROM within 15 minutes of it being released. First with Magisk, get on the Canary update channel. My magisk manager is listed as version 315 in magisk.

I flashed full OTA image over my Nov image just fine. Using Magisk 21101 version to patch boot.img.

Will be released today at 12pm CST I think? Or is it 11am CST?

I had pretty much the same problem updating 10 to 11. I flashed 2 monthlies and 11 was noticeably laggier and slower than 10. I was thinking I was going to have to buy a new phone. I first tried to do a full wipe and flash from scratch and that resolved it. It was a night and day difference...

https://developers.google.com/android/images you should flash the stock image from recovery. Basically unzip it all and just run "flash-all.bat"

Stop messing with TWRP. Doesn't work. Did you extract boot.img from the factory image? Then patch it with Magisk? Then copy it back to your PC? Then run fastboot flash boot magisk_patched.img ?

No problems here. Used latest Canary to patch 11 boot.img. Flashed 11 full image. Let it boot up once. Rebooted to bootloader, flashed magisk patch boot.img. Booted up fine.

You can use it by just wiping it, though you would lose his data. Are you trying to retrieve data or just simply make the phone usable?

Yeah, battery life is so stellar on this phone, don't need greenify and apps like that. I don't even check betterbatterystats anymore since I don't have battery anxiety or reason to research battery usage. The fact that there is no working TWRP is probably the biggest reason the modding...

But our device (3a and 3aXL) have the logical partitions that are referred to in the XDA news post. That's the reason we haven't had working TWRP since September or whenever it was last year.

Yes, there is an image, but without partition support its useless.

Anyone attempted TWRP 3.4 that was released 4 days ago? https://www.xda-developers.com/twrp-3-4-0-enables-ozip-decryption-realme-oppo-devices-support-legacy-devices-upgraded-android-10/ Ugh....

Well, not much available at all. It sucks that the 3a is a great phone, but Android Q just killed TWRP and the ability to be mobile and flash. I'm with you, I like to be able to DL roms on the go and flash while mobile, but this just isn't the phone for that. The community just isn't there...

Grabbed the full factory image. Removed the -w in flash-all. Flashed, patched boot.img. Works great!

Considering I was flashing this the day the december update came out, no. I'm pretty sure I was pretty early on this one. I'm sure posts in there where a day or several after I was attempting it. As stated earlier. I was only ever able to do a full wipe. I actually flashed stock rom, then...

If using gestures, you swipe up from the bottom corners of the screen. Or just squeeze.

I checked the time/date stamps each time and they were definitely from today. Doesn't matter much at this point because I already flashed back to stock rom. Was able to room there. Have no clue why I had this problem. I've been on the 3a since the week it came out and I've been flashing...

I ended up wiping my device and flashing stock Dec image. :-/

10.0.0 (QQ1A.191205.011, Dec 2019) Listed right at the bottom for bonito section.

https://developers.google.com/android/images Download the factory image from here. Extract out the boot.img file.

I just flashed the full image (flashall removed the -w) and attempted the magisk boot.img patch that I've been doing since the phone was released for months now. I'm on Magisk canary up to date (7.4.1-72edbfc4 (260)). When I patch the boot.img and reflash it as magisk_patched.img I just get a...

The december update (released yesterday) allows you to use gestures with 3rd party launchers. Update your phone.

Well, if you unlock the bootloader, many apps will flag your phone as rooted/tampered and may not work. Google Pay and Pokemon Go for example. There's actually no advantage to unlocking the bootloader without rooting and using Magisk Hide. I mean, you wouldn't have to wipe your phone later...

Download this file "bonito-qp1a.191005.007-factory-9754d7c6.zip" Extract it out and you will get this file amongst others..... "image-bonito-qp1a.191005.007.zip" The contents of "image-bonito-qp1a.191005.007.zip" should be ... android-info.txt boot.img dtbo.img product.img super_empty.img...

https://developers.google.com/android/images download to your PC. Extract the .zip out. Then extract the boot.img file out of of the large .zip that was extracted from earlier. Copy boot.img to your phone, run Magisk, choose "install" and select that boot.img file. Patch it. Copy that...

Yes, via the Magisk Manager patching boot.img extracted from the full image download. Reflash it back in fastboot. Easy.

I think I found my culprit... The certain Canary version of Magisk I was on. I upgraded to 19308 yesterday morning and it isn't happening (as of yet)!

The problem I get is after anywhere from 24-36 hours of using the phone, I have apps that constantly close right after opening. I get this with Camera, Chase, Chrome (sometimes). Basically many apps that I attempt to open will either open for 1-2 seconds or just open and immediately close. I...

Add Netflix to Magisk Hide. Clear Netflix cache/storage.

Straight from the TWRP thread.... first post. https://forum.xda-developers.com/pixel-3a-xl/development/twrp-3-3-1-pixel-3a-unofficial-t3943419 "Not compatible with Android Q."

Correct. Can't decrypt Q so you basically can't do anything with it. Do the other root method for Q where you extract boot.img and patch it in Magisk, then flash it back to the phone.

https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950 Works for me.

Beta 5 out now https://developer.android.com/preview/download.html

Installed 3.3.1-5 Thanks! ----------------------------- UPDATE: TWRP 3.3.1-5 won't boot untethered for me. I booted 3.3.1-5.img and then flashed 3.3.1-5.zip. It says it completed both A and B. But now I cannot get into recovery at all. Choosing recovery from fastboot gives me the google logo...

Same here. I ultimately had to wipe data and start from scratch.

Flash back the original vendor and system images.

Yes. This is how it has worked in the past. Don't see why it wouldn't work like this currently. If you flash a different vendor image or system image, you'll want to revert back before you restore your old ROM backup.

My TWRP is NOT prompting for pin/pattern. That has to be part of this... Wiped data via google recovery. The phone booted to Pie (i had previously did the OTA from Pie to Q beta 4). So now I'm back on Pie somehow (without reflashing). I booted to TWRP, installed Magisk successfully. So...

I'm on Q DP4. Anyone having luck flashing Magisk (canary)? In B slot it fails to mount system and vendor. I change to A slot. It completes. I reboot on A slot, I get stuck at Google starting logo and the phone never boots. If I attempt to boot B slot afterwards, it boots up fine, but I...

So does anyone know if TWRP + Magisk work on Android Q for root?

Awesome! Thank you so much! So as of this moment, there is only the ability to boot to twrp via fastboot?

I already installed beta4 the other day and just got an OTA for a 10.1MB update QPP4.190502.019. I was already on QPP4.190502.018

That explains it! I turned off find my device a few days ago and Google pay failed to work for me yesterday. Thanks!

Is it possible that GPay will eventually work with your app? Or will Google Pay always fail?

Yeah, Facebook and Facebook Messenger both constantly lock up on me. It makes them damn near unusable. Don't have this problem on stock ROM with Sept image. I really want to use this ROM, but the random lockups in FB and some other apps is making me want to go back to stock.

I did exactly the steps listed here flashing from DP1. Removed lock pattern first though. Don't set a lock pattern until after magisk is installed and verified working.

I can flash to the device without decrypting/unlocking? That doesn't sound right.

Right, but when I boot up TWRP and it asks me to unlock device, it never unlocks. Pin or pattern, nothing unlocks.

Same here. 3.2 TWRP can't decrypt for me. I may just have to wipe entire phone, setup without encryption. Install Magisk and then encrypt.

+1 I use it all the time.