yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3a Guides, News, & Discussion] duh1:
Difference is downloading the patched image vs patching it yourself. Wasn't clear how that created the issue. Well written, thx for pointing it out.

So if anyone patches the new version boot image before uninstalling Magisk, they'll get an error. Likewise, patching the current boot image in the manager will allow the uninstall to work correctly...
[Google Pixel 3a Guides, News, & Discussion] pbanj:
you dont need to restore stock to update. the restore is only needed if you want the phone to handle the update. if you sideload the ota in adb it updates fine then you can just flash the new patched boot image. also fun little fact, even if you use the pre-patched images you can still use magisk's internal update method. you just have to do one simple thing....... grab the stock boot.img for your current update, and tell magisk to patch it, it will create the stock backup and then you can just use the magisk update method. i've been meaning to add that to my thread but i've been busy and having some health problems so i haven't been on here in a few days.
[Google Pixel 3a Guides, News, & Discussion] ritchea:
Sorry for the health issues. Take care and get well soon.

Thank you for this post. I was getting confused about the ADB sideload of OTA (which, iirc, didn't work on unlocked BL on my last phone), which you said does work on the 3a. My last phone was the N5X and despite Magisk being available, I stayed with SuperSu (which worked for me as well as suhide and FlashFire). The dual slot is new to me; I think my MOTO Z3 Play has that (I'm not unlocking that one atm) so it really doesn't matter.

If I fastboot flashed the patched boot.img to slot_b, then the next time I flash any boot.img, I will have to direct it to slot_a [fastboot flash boot_a boot.img]? I guess I'll learn as I go along. Next, I'll take current stock boot.img and tell magisk to patch it.
[Google Pixel 3a Guides, News, & Discussion] pbanj:
ya pretty much. every time the phone updates the active slot changes. I'm currently updating my root thread so everything is clearer and in one place.
[Google Pixel 3a Guides, News, & Discussion] duh1:
Just to be sure, sideloading bypasses the OTA package compatibility verification that would give an error during normal update if it detects wrong boot version?
[Google Pixel 3a Guides, News, & Discussion] pbanj:
correct. i had no issue with it, and i friend is the one who told me about it as that's how she installs her updates even though she could use the magisk method
[Google Pixel 3a Guides, News, & Discussion] ritchea:
My brief research (nothing under MM Settings and web info) tells me that in order to let Magisk patch the boot.img, I must uninstall it from the Manager then begin installation again?
[Google Pixel 3a Guides, News, & Discussion] pbanj:
nope, open up magisk then click this

[IMG="magisk1"]https://cdn.discordapp.com/attachments/399670410565910529/588441927163052051/Screenshot_20190612-145732.png[/IMG]

Then click install on the popup that comes up, then click this

[IMG="magisk2"]https://cdn.discordapp.com/attachments/399670410565910529/588441927209189486/Screenshot_20190612-145750.png[/IMG]
[Google Pixel 3a Guides, News, & Discussion] ritchea:
Well, DUH! Another lesson today. Thanks.

I had to change channels from stable to canary to get the options.
[Google Pixel 3a Guides, News, & Discussion] googlephoneFKLenAsh:
You do need to restore stock to even sideload the ota zip. Or you will get error message "E: Failed to verify package compatibility" in recovery when doing sideload. You didn't get this error message because you provided the patched image in the very beginning and you actually just took the OTA with the Magisk method.
[Google Pixel 3a Guides, News, & Discussion] pbanj:
no i didn't do the magisk method. and the original images were made using my nexus 5x. but hey you seem to know what i did more than i do.

---------- Post added at 04:22 PM ---------- Previous post was at 04:05 PM ----------

i have updated my thread and made the updating steps a bit clearer
[Google Pixel 3a Guides, News, & Discussion] Wdenton:
Thanks pbanj! Hope you get well and health improves! I'll leave mine up for now to see if I can find another use for it, unless people want me to take this thread down.
[Google Pixel 3a Guides, News, & Discussion] googlephoneFKLenAsh:
I only speak from my test/experience. I tried to adb sideload ota zip without restoring stock boot image and got error message "E: Failed to verify package compatibility" in recovery. Other people also reported the same error message.

I didn't say I knew more than you did. You wanted to say you knew more than I did and I can tell you don't. Look at your own post in the other thread. You clearly said you used Magisk to restore image and then adb sideload.

https://xdaforums.com/showpost.php?p=79657851&postcount=95.
[Google Pixel 3a Guides, News, & Discussion] pbanj:
You tried to tell me that I did something I didn't, but I'm not going to sit here and argue over it. Let's try to figure out why it didn't work. We're you using ElementalX?
[Google Pixel 3a Guides, News, & Discussion] googlephoneFKLenAsh:
You told everyone in the other post that you used Magisk to restore boot image.

You want to deny yourself? Lol.

I am not here to argue with anyone in this forum. I was trying to help people.
[Google Pixel 3a Guides, News, & Discussion] pbanj:
No I said in my thread that it was allowing me. I didn't use that method because it never gave me the update even after a few days. I ended up sideloading the ota
[Google Pixel 3a Guides, News, & Discussion] googlephoneFKLenAsh:
How did you know Magisk was allowing you to restore image if you didn't actually hit "restore stock image" and restored the stock boot image?

Once you hit the "restore stock image", you actually did restore the stock image. You could then side load the ota zip.

For me, when I hit "restore stock image" in Magisk, it was saying "no stock image found".

I then went to recovery to sideload ota zip, it gave me the error message "E: Failed to verify package compatibility" unless I restored stock boot image manually in fastboot.

So the difference is:

you restored stock image with magisk, then adb sideloaded ota zip.

I restored stock image with fastboot, then adb sideloaded ota zip. If I didn't restore stock image, I got error message when sideloading ota zip.
[Google Pixel 3a Guides, News, & Discussion] pbanj:
How did I know? Because I was like hey let's see if it will restore before I told it to check for the ota. It didn't find the ota, so I told Magisk to reinstall itself. I waited for close to 3 days and never once got the notification for the ota, whether I had magisk restore or not. Every time it didn't find the ota I reinstalled Magisk. When I finally sideloaded the ota all I did was boot into recovery and sideload it. I didn't restore ****. Hell the person who told me that works does it with every update on her 3xl. It's how I knew it would allow me to in the first place.
[Google Pixel 3a Guides, News, & Discussion] pbanj:
so [MENTION=8450023]googlephoneFKLenAsh[/MENTION] were you using elementalx?
[Google Pixel 3a Guides, News, & Discussion] googlephoneFKLenAsh:
No. Only rooted and without any magisk modules.
[Google Pixel 3a Guides, News, & Discussion] pbanj:
Interesting, the only other person I talked to who had the same issue as you was using ElementalX which would most definitely mess stuff up. Did you uninstall system apps?
[Google Pixel 3a Guides, News, & Discussion] googlephoneFKLenAsh:
Didn't uninstall any system apps. Only with root. The only modification I can think of may be build.prop modification for tethering (added one line) using root explorer. I saw the same error on two rooted 3a's.
[Google Pixel 3a Guides, News, & Discussion] pbanj:
did you add the same line to both phones?
[Google Pixel 3a Guides, News, & Discussion] nickmv:
I'm finding if you use the Magisk patch-boot method, it introduces a serious bug where music auto-starts on bootup. Revert to stock boot and it disappears.
[Google Pixel 3a Guides, News, & Discussion] pbanj:
ahahahaha. omg i thought it was a bug with the app i use. it starts but doesnt actually play. i thought i was the only one.
[Google Pixel 3a Guides, News, & Discussion] googlephoneFKLenAsh:
Only one.

On both phones, I installed root explorer. Maybe mounting as RW in root explorer caused this issue.
[Google Pixel 3a Guides, News, & Discussion] pbanj:
yaaaa mounting as r/w can cause issues as you're changing the permissions so it wont match what it is looking for.
[Google Pixel 3a Guides, News, & Discussion] googlephoneFKLenAsh:
This may be the issue.

Many people who rooted their phones may probably already mounted system partition as R/W, at least for those who modified the build.prop in system.
[Google Pixel 3a Guides, News, & Discussion] pbanj:
i havent mounted system r/w in years. if i need to put something into there i just use a magisk mod. because it can mess up a lot of things.
[Google Pixel 3a Guides, News, & Discussion] duh1:
Before systemless roots became available, I flashed the current system and boot images before an OTA to make sure I didn't get errors. Now with systemless, you're supposed to leave the system alone and make all your changes in the Magisk directory. But if you don't and still muck around in there, defeating the systemless aspect of the root, reflashing the system image is a still a good idea before an OTA...
[Google Pixel 3a Guides, News, & Discussion] FA21:
Hey guys,

I am still a beginner. Please check me out...

Because over 1.5 years have passed since the last post, I would be very happy if someone could share information about the current status to apply OTA updates in a safe, proper and preferably convenient way?

My installation (Pixel 3a):

- LOS 17.1

- Magisk (installed over ADB Sideload)

- Riru (over Magisk)

- EdExposed (over Magisk, only for XPrivacyLua)

Every time I update LOS17.1 over OTA I have to ADB Sideload Magisk again... Since I installed Riru and EdExposed, I did'nt make any updates because I am afraid that there will be problems.

I read that the Pixel 3a has two boot slots. Is there anything to consider here? I would be happy to hear from you so that I can read it further.
[Google Pixel 3a Guides, News, & Discussion] dkryder:
In magisk I "restore image". Then boot to recovery. Then sideload the OTA. (stock rom). Then reboot system. Verify all is well. Reboot to bootloader. Flash the new magisk patched kernel. Boot to system. Verify all is well. Then flash ElementalX kernel. THen reboot. Then it's good for another month. Although I've never used magisk with LOS , I'd guess that it's a similar process.
[Miscellaneous Android Development] lopestom:
Hello Everyone, here 's the thread for BLU G9 - Stock Roms and Development.

[IMG="BLU G9"]https://i.imgur.com/KjGHEE5.png[/IMG]​

If you want more about BLU Development:

Full specifications: GSMARENA ------Unboxing & Review: Search Videos

Website BLU Products: about G9 device

Similar devices: None yet

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

Stock ROM BLU G9 - G0130WW:

Files to use with SPFT (Smart Phone Flash Tool).

I really have the Stock ROM (you can see picture in Download Tab). But I will not share the files right now! I have no obligation to do so. Therefore, you should send a request to BLU Products !!

Guide for install DRIVERS correctlly: Drivers MTK windows-10-mtk-vcom-usb-drivers-32-64

SPFT - Smarth Phone Flash Tool: SP Flash Tool New Version v5.xxxx

Guide for install ROM with SPFT: [TUT]MTK Android (Sp flash tool ) tutorial

Thanks [MENTION=1205214]SacredDeviL666[/MENTION] Mod for remove unnecessary link.

Stock ROM:

Guys, Please do not give "reply" with ALL text and images of the first post. :good:

If you like this forum, let me know, press the thanks botton.

:p--------------------------:D

XDA:DevDB Information

[GUIDE] [Unlock bootloader] [TWRP3.3.1] BLU G9 - G0130WW - mt6762 - 64GB, ROM for all devices (see above for details)

Contributors

lopestom

Source Code: https://xdaforums.com/android/general/blu-stock-firmware-repository-mediafire-t3853065

ROM OS Version: 9.x Pie

ROM Kernel: Linux 4.x

ROM Firmware Required: V9.0.03.05

Version Information

Status: Stable

Current Stable Version: v9.0.04.0x

Stable Release Date: 2019-06-20

Current Beta Version: V9.0.03.05

Beta Release Date: 2019-06-05

Created 2019-06-10

Last Updated 2019-10-16
[Miscellaneous Android Development] lopestom:
Unlock / lock Bootloader

I am not responsible for wrong process and people with bad knowledge.

This guide is not for beginners users! Then understand some parts of the alert:

* [B][COLOR="red"][SIZE="5"]BACKUP YOUR STOCK ROM BEFORE ANY ACTIONS![/SIZE][/COLOR][/B]
*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features
* included in this files before flashing it! YOU are choosing to make
* these modifications, and if you point the finger at me for messing
* up your device, I will laugh at you.

Before any actions:

copy all that you need from SDcard internal to PC!

If you want backup calls, messages, contacts (different by goggle contatcs or if you can record all the contacts in your google contacts account directly through the contacts application).

For backup, use any application from google play! Save in your PC! After all the processes you can restore them using the same application that you used.

Unlocking Bootloader WILL set warranty flag to "NO". So think for a few minutes if you need it!

If you have full backup from your phone, BEFORE unlocking, so there is a possibility to restore warranty to "yes".

[*]GUIDE to unlock the bootloader:

Download

- Drivers adb-fastboot (optional)

- platform

- Guide file pdf

Enable Developer options on phone: open settings--> "About device"--> click build number 7 times--> go back one screen in Settings

-->select "System" --> scroll to bottom "Developer options" --> enable "USB debugging" and "OEM unlocking". LOOK in the screen phone about any permission adb!

Now you SHOULD Download Files in Attachment in this post and READ the GUIDE with pictures..........

:angel:
[Miscellaneous Android Development] lopestom:
Stock and Custom Recoveries

These are my files and took time to create them. I created these files to help all users. If you want to make PORT, ask for authorization/permission or put the link on another site, ALWAYS put the credits.

All thanks to the real developers. If it were not for their efforts, none of this would be possible.

Thanks to TEAM WIN [MENTION=912474]Dees_Troy[/MENTION].

[DEV]How to compile TWRP touch recovery

CHANGELOG for 3.3.0-0: TWRP 3.3.0+ will no longer require installer ZIPs

Merge AOSP 9.0 r3 (Dees_Troy)

Use ANDROID_ROOT variable instead of hard coding to /system (CaptainThrowback)

Decrypt FBE on 9.0 and metadata decrypt (Dees_Troy)

vold decrypt updates (CaptainThrowback and nijel8)

Support vibration on LED class devices (notsyncing)

Metadata decrypt support for Pixel 3 (Dees_Troy)

Support rotating the display via build flag (vladimiroltean)

Reboot to EDL mode button (mauronofrio)

Support MTP on FFS devices (bigbiff)

Update FDE decrypt to support keymaster 3 and 4 (Dees_Troy)

Detect mkfs.f2fs version to properly format on f2fs partitions (Dees_Troy)

Allow TWRP to use md5 and sha256 checksums for zip installs (bigbiff)

TWRP can use /data/cache/recovery and /persist/cache/recovery on AB devices with no cache partition (bigbiff)

Switch part of advanced menus in TWRP to use a listbox of options (Dees_Troy)

Use magiskboot to allow repacking boot images for installing TWRP (Dees_Troy with thanks to topjohnwu of course)

YOU SHOUD UNLOCK BOOTLOADER for install Custom Recovery

Recovery Original & Custom Recoveries

Pie

recovery original - < 3e >

recovery original BLU G9

md5: soon

Manually enter recovery:

Turn off your device.

Press the button to turn off with button VOL+ simultaneously.

Looking options in Boot Mode: Recovery - Fastboot - Normal

To manually select: Use VOL+ to go up or to go down.

Use VOL- to confirm.

Choose Recovery and you can look the options.

Custom recovery - TWRP

Pie kernel

md5: done

[/HIDE]

Instructions for flash Stock recovery or Custom recoveries with SPFT:

You have many options like two is better: Use application (ROOT is required) or Use SPFT (knowledge for flash is required - search).

Other way is using adb-fastboot. [GUIDE already have! But upload when it's convenient!]

A very important tip to first step: MAKE NOW BACKUP OF YOUR ROM! ​

:D

ROOT

After TWRP installed and booted is need the Magisk copied on sdcard to install with TWRP!

Search here in xda the files Magisk_vXX.zip​

Without install the ROOT so the stock ROM don't start with TWRP!!

Images of the TWRP are in Attached files.

;)
[Miscellaneous Android Development] lopestom:
Update files - Mods & Custom ROMs (GSI)

Update from company

This guide is intended to remove the update file for added security. If there are errors or you need files related to the device.

Download already in DOWNLOADs TAB: How to remove update_s.zip and install - 2019 - BLU G9 - G0130WW.pdf

I will not leave the update_s.zip file because everyone who has the phone can do it alone and learn a little more....

File Modificated

This file has been modified to remove the message from your device when it has the unlocked bootloader.:

You may have already blocked the bootloader again. But in custom ROMs (GSI - Project Treble) you might need this file if you want.

Download lk MODs zip and unzip in the plattform tools folder for use adb-fastboot for flashing:

fastboot flash lk lk2_Mod_3.bin

fastboot reboot

File already in DOWNLOADs TAB:

Custom ROMs - GSI

Some custom ROMs (GSI) have been tested on the BLU G9 as you can see in the attacked images. So use A/B image for flash!!

List:

ResurrectionRemix90_System-190406-arm64-ab-vanilla-nosu

BootleggersNFound-v4.0-PIE-arm64_AB-20190306

DotOS-v3.0-arm64_AB-vanilla-20190311

AOSP 9.0 v114-phhusson-system-arm64-ab-vanilla-nosu

lineage-16.0-20190609-UNOFFICIAL-treble_arm64_bvN_AB

Havoc-OS-v2.6-20190612-phhgsi_arm64_ab-Official

Evolution-9.0-GSI-ARM64-AB-20190719

Descendant_4.0.1_arm64_ab

AospExtended-v6.5-arm64-ab-vanilla-20190422

MIUI-AB-10-20190904-ErfanGSI [booted but black screen after settings]

Seeing MIUI starting........

BeastROMs-v1.3-arm64-ab-vanilla-20190322 [without SIM signal/network]

Pixel-AB-10-20190904-ErfanGSI [very bugs]

Generic-AB-10-20190818-ErfanGSI

Seeing Generic Android 10-Q starting.......

Some ROMs need modification something to work better in G9 like camera 13MPx & 8MPx..... But need time to do it.
[Miscellaneous Android Development] lopestom:
I tested one Gcam version but it's not much different of stock camera in the G9. So I found of Xiaomi Redmi Note 4 here:

Camera_6.1.013.216795316.apk - kokroo, 2018-12-18

Tested others apk:

Google Camera Port Hub

But some apks stopping or start with very issues. So is need get good apk and make a modification for G9.
[Miscellaneous Android Development] vineethrp:
This thread would have been very much beneficial and I would have been a lot thankful if the Stock ROM for SP Flashtool was shared. I tried asking BLU support, but they would not share the ROM. Can you please share it?
[Miscellaneous Android Development] mcarden2006:
Will this twrp work for Blu G9 Pro?
[Miscellaneous Android Development] lopestom:
I not know. Haven't Pro in my hands.

Probably not! Because different specs.....

Is better PORTing these to Pro. But is need stock recovery from Pro!!
[Miscellaneous Android Development] mcarden2006:
I know how to install recovery, custom ROMs, and root but I have no idea how to send stock recoveries. I just received my pro today and unlocked the bootloader. Now I am trying to root it but without twrp or cwm it is a no go ?
[Miscellaneous Android Development] DrSliperyFists:
im confused a little, is there actually a twrp already made for the blu g9? or do I have to compile it myself? also is the root method based off of the idea of flashing twrp and then installing root or is there another method of root?
[Miscellaneous Android Development] lopestom:
You not see the pictures about TWRP?

That's not good?!

TWRP is not only ROOT. Backup & Restore your own ROM ensures more security than only Rooting with another method!

Have other method?: Try it yourself!
[Miscellaneous Android Development] lebonthedon:
I tried following the bootloader unlock guide and got stuck after phone entered fastboot. fastboot devices command shows my phone but when i put fastboot var all it shows nothing? Anybody had this problem? Im trying to unlock the bootloader so I can put a custom recovery and flash a audiomod such as Viper4Android! Seems like Music playing with headphone quality is great and Volume is low also. Please Help
[Miscellaneous Android Development] lopestom:
You have a BLU V9?!

Fastboot command:

fastboot getvar all

Maybe need other adb-fastboot tool like adb-fastboot minimal. Maybe drivers adb not installed?

Maybe other way because V9 has Unisoc SC9863A GPU: IMG8322?!

Good luck
[Miscellaneous Android Development] lebonthedon:
Yes thats the command given in the Guide that i Tried to use. I just bought this Blu V9 from best buy but the entire time its connected to my PC its being called a G8? I heard Blu rereleases phones with slight modifications to boost sales so who knows. Do you have one and have you successfully unlocked the bootloader and installed the twrp recovery?
[Miscellaneous Android Development] radiophonique:
How does one get the stock recovery from a device without root or custom recovery? I have a G9 Pro but I cannot port twrp without my stock recovery
[Miscellaneous Android Development] lopestom:
I'm helping users G9 Pro. So I have all for G9 Pro too and need a tester for know if my TWRP work.

If anyone want a tester PM me.

Sorry. I have no intention of buying a V9 or G6; G8.
[Miscellaneous Android Development] lebonthedon:
I understand. I made the mistake of thinking this the guide was for the v9. Does anybody know of any support for this device and if so could you please point me in that direction? Thanks ahead of time
[Miscellaneous Android Development] donnasbrt1:
Deleted
[Miscellaneous Android Development] lopestom:
TWRP BLU G9 Pro

This user wrote:

Well, i not know if this user want share the TWRP file. But any user G9 Pro can ask about that directly for the him.....
[Miscellaneous Android Development] lopestom:
Custom ROM info:

That's time for test & solve any issues in the device with GSI ROMs.

If anyone want test and reporting bugs/issues with Resurrection Remix 7.0.3 for install in the BLU G9 so need unlocked bootloader, encrypted vendor (v.9.0.04.05), TWRP installed and patched files (PM me about charge fix) and time to install.
[Miscellaneous Android Development] Derrrrr:
Lopestorm, I sent you a message regarding BLU phones! Please respond if you can.
[Miscellaneous Android Development] TNSMANI:
MOD ACTION:

Thread cleaned and closed.
[ASUS ZenFone 6 (2019) Questions & Answers] Vicxx:
As it's a poor quality IPS, does the screen have any ghosting? I can't find an answer in any review. My old Oneplus 3T and dirt cheap Mi Max 2 also had IPS screens but they had zero ghosting, then I bought a Mate 20 which cost 3x more yet that DOES have ghosting, so if a high-end phone has ghosting it's likely the Zenfone 6 does too, especially if most people are saying it's a poor quality IPS.

This is the only video that mentions it has ghosting but it's the one guy, so I wanted more opinions to confirm:

https://www.youtube.com/watch?v=U8EH9_BEpAA
[ASUS ZenFone 6 (2019) Questions & Answers] _jis_:
Did you mean this part?

https://youtu.be/U8EH9_BEpAA?t=125
[ASUS ZenFone 6 (2019) Questions & Answers] leiros:
I had the G5S+, where I noticed ghosting. Coming to the zenfone I was concerned about the same stuff but there is significantly less ghosting on this screen. I'm actually not sure there are ghosting, if it is its miniscule.