Database Develop

Flash stock updates when twrp is installed

I found an easy and convenient way to flash Huawei updates when twrp is installed. No data loss. In my case I updated from June to July patch without any hiccups.
1. Download the HWOTA8 folder zip to your device and extract it to the root of your SD card. I provided the link at the bottom of the tutorial.
2. Download the Huawei update and wait till it finished.
3. Boot to twrp and go straight to the HWOTA8 folder.
4. Now install the hwota8_update.zip, this will install a special no check version of the stock recovery.
5. After reboot you'll see a failed update attempt, ignore the message and boot to system.
6. Now that we have the stock recovery you can go straight to the update app in the settings and install the update.
7. After 5 minutes the update should be finished and the device will boot to system.
8. The bootloader will be still unlocked so you can modify again with twrp, magisk and so on. No data loss.
Download
https://mega.nz/#!7AxVwBBZ!W9YyQ7qSAxZo-px8xYR18rBIhycKlqOhS4n8ogTioaI

gude, tried this today to upgrade P10plus from .382 to .385. worked as promissed. afterwards just installed the TWRP and magisk to get back root. thx

Dear Sir,
Thank you for the clear and concise method for flashing stock updates when TWRP is installed.
Please help me with instructions how to upgrade my unlocked, rooted and TWRP installed Android 7 ROM to OREO.
My phone model number is: VKY-L09
Build number: VKY-L09C02B102
EMUI version: 5.1
Android: 7.0
Kernel: 4.1.18-gfd75bb
TWRP: 3.1.0-0

there is only one thing that makes me wonder: i cannot install a differential update, this always fails, so the complete package will download ( almost 3GB ), then the installation will be successful. any idea why?

Fingerprint not detecting in custom os since installed official 8.1

Fingerprint not detecting since I have installed custom ROM after I have installed official Oreo
On official Oreo fingerprint shows up in settings but in custom Oreo all works fine and best but fingerprint doesn't show up in any settings I have tried 4 8.1 custom roms like sex pixelexpirience 64 bit versions all works flawlessly tested Google camera it works the best but not detecting fingerprint even after searching fingerprint it only shows up gestures's fingerprint in gestures's system menu PLZZ give me link of official Oreo build OPSS28.65-36-3 with Indian band so I could try to flash via fastboot and then recheck if custom roms fingerprint gets detected or not..

Update ur bootloader to Oreo one and then try flashing the rom

Surya Guduru said:
Update ur bootloader to Oreo one and then try flashing the rom
Click to expand...
Click to collapse
I don't have fastboot official oreo link can anyone give me plzz

hondraopranav said:
I don't have fastboot official oreo link can anyone give me plzz
Click to expand...
Click to collapse
U told u had the official 8.1 ROM ....in that ...... fastboot Flash bootloader bootloader.zip and fastboot flash modem non-hlos.bin

change the base of your fp to nougat base again

Hey check this out

Surya Guduru said:
U told u had the official 8.1 ROM ....in that ...... fastboot Flash bootloader bootloader.zip and fastboot flash modem non-hlos.bin
Click to expand...
Click to collapse
The OP didn't say they had the official 8.1 ROM, they said they had installed official Oreo. AFAIK There is no official 8.1 ROM for Sanders. Some people have taken the OTA for their device and repackaged it into an UNofficial flashable package, but that's not the same thing, and reportedly may be causing problems on EU & US variants, so I wouldn't recommend it.
I have the same problem with my FP reader.
I don't have an official 8.1 ROM (because there isn't one, lol), but I installed stock nougat 7.1.1 (retus, in my case) and then got the OTA upgrade to 8.1, after that fp+VoLTE are 100% working.
Then, as soon as I change to a custom 8.1 (or 9) ROM, VoLTE still works, but the fp is no longer recognized by the system.
If I flash back to stock nougat, FP comes back (and LTE breaks, but can be fixed by installing the 8.1 OTA upgrade again, or by getting to a root terminal and fixing permissions on /persist, I've personally verified both methods to restore functionality (assuming your /persist is unmolested - if it is, you're SoL).
Going from fully working official nougat or official Oreo, to any Oreo (or Pie) custom ROM still seems to break the FP reader again. I'm getting really tired of wiping my device...
Not A Solution #1
As suggested here: With FP + VoLTE working under official 8.1 OTA update, I installed TWRP & backed up /EFS, then installed my custom 8.1 ROM (Validus final) and restored the backed up /EFS, but instead of bringing my FP back, it just caused bootloop and I had to roll back to stock and start over. I skipped rolling back to Nougat before flashing custom, is that important? Why would it matter?
Not A Solution #2
After installing the custom 8.1 ROM I tried flashing the Nougat FP base. It had no effect.
Maybe A Solution? UPDATE: YES. A SOLUTION.
As suggested in this post:
1 - download the latest nougat stock rom (link removed - the correct one will vary depending on your device, up to you to obtain the correct firmware);
2 - unzip the above file and cd into the resulting directory;
3 - reboot your phone in fastboot mode;
4 - from terminal (linux or windows, in linux I had to do it as root user, using sudo), type:
fastboot flash bootloader bootloader.img <enter>
fastboot flash modem NON-HLOS.bin <enter>
fastboot reboot <enter>
By doing above steps, your phone should get fingerprint options back.
I did this, it worked, with one additional step - I had a pattern set before. After the fingerprint reader was 'reinstated' the pattern no longer worked. Rebooting into Recovery and flashing lockfix.zip removed the security so that I could set it up again properly. Find lockfix.zip in this post.

Pixel Experience 10.0 Plus - how to install? Currently bootloop

Hey,
I tried to Install Pixel Experience 10 Plus but failed with bootloop (was on latest stock before)
1. Downloaded from here https://download.pixelexperience.org/g8441 PixelExperience_Plus_g8441-10.0-20200330-1251-OFFICIAL.zip
2. As adviced there downloaded Software binaries for AOSP Android 10.0 – Kernel 4.14 – Yoshino (latest) from https://developer.sony.com/develop/open-devices/downloads/software-binaries
3. Flashed
Code:
fastboot flash oem SW_binaries_for_Xperia_Android_10.0.7.1_r1_v5a_yoshino.img
4. Flashed latest TRWP https://forum.xda-developers.com/xp...t/recovery-twrp-3-1-1-stock-security-t3706704
Code:
fastboot flash recovery twrp-3.3.1-0-lilac-android10-1.img
5. Booted into TRWP recovery
6. Wiped wiped system, cache and data
7. Flashed through TRWP
Bootloop
Tried again, but this time wiped everything in step 6.
Again bootloop :/
Will recover to stock FW now, but what is the proper way to do it ??

I spent a day trying to get that one to boot but.. it just kept crashing out before going to setup so I'd say go stock and go with the unofficial build for now.

Yeah go with the unofficial build for now. It has a few bugs that will likely get fixed but other than it's pretty stable and runs well.

Thx for replies! This is what I got from the maintainer:
Warning, except Tama platform this is beta material
How to flash PE :
for yoshino platform : boot twrp, flash pe zip, reboot fastboot, flash oem, then fastboot -w and reboot
Click to expand...
Click to collapse
So still beta

April 2020 Stock/Magisk-Patched Boot Imgs for FLAME QQ2A.200405.005 [ + Update Guide]

Hi all, I just updated to April 2020 firmware with no issues. Just waiting on a Kirisakura update and we'll be right back to where we left off. =)
edit: nevermind, Kirisakura 4.2.0 works perfectly fine!
In case anyone is looking for them, here is the stock and Magisk Patched boot images:
Magisk v20.4 patched boot image: https://www.androidfilehost.com/?fid=4349826312261763723
Stock boot image: https://www.androidfilehost.com/?fid=4349826312261763724
I'll also post my update procedure in case it helps anyone else out. This was my first OTA on this device (just got it last month), and I was able to update with absolutely no problems, no loss of root, no need to change Magisk or EdXposed settings/modules/etc. SafetyNet still passes, etc. Very seamless and I'm definitely happy with going with a Pixel as my next device. =D
This is ONLY for QQ2A.200405.005 firmware - it goes without saying, PLEASE ONLY FLASH IF YOU KNOW WHAT YOU'RE DOING.

UPDATE PROCEDURE (using a PC. I know there are other posts covering other methods, but this was the fastest, easiest, most reliable and intuitive way for me, and I didn't need to do any additional research, so I chose to do it this way)
** I was previously on March 2020 firmware and these steps therefore correspond as such.
I DID NOT BOOT BACK INTO O/S UNTIL ALL STEPS WERE COMPLETED - I DID THIS TO ENSURE EVERYTHING WOULD BOOT BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
this may not be necessary, but I didn't want to find out, plus this was the quickest and most intuitive way for me anyway.
1. boot into bootloader
----------------
** I was on Kirisakura kernel, so I needed to flash BOTH the stock boot and dtbo March 2020 images - make sure you flash the proper corresponding images to your current pre-update firmware.
2. fastboot flash boot boot.img
3. fastboot flash dtbo dtbo.img
- these steps to restore stock recovery, dtbo.img also necessary for some kernel installations
-----------------
4. use volume keys to change selection to boot to Recovery Mode
* when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload flame-ota-qq2a.200405.005-2b5150a4.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot flame-qq2a.200405.005-magisk_patched-20.4.img
9. done, start the phone
This was a 100% seamless update that required no additional / re-setup of any of my Magisk or EdXposed setups. So far, no issues at all for both me and my wife's phone (P4 XL and P4). Magisk and Xposed are playing nice with these builds so far.
All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
Edit: To be nice to the noobs, and also because I have nothing better to do at this moment thanks to the pandemic, here are the stock boot and dtbo images (FOR MARCH 2020) as well as a direct link to the April 2020 OTA zip:
flame-qq2a.200305.003-factory-dtbo.img: https://www.androidfilehost.com/?fid=4349826312261763748
flame-qq2a.200305.003-factory-boot.img: https://www.androidfilehost.com/?fid=4349826312261763749
April 2020 OTA Zip from Google: https://dl.google.com/dl/android/aosp/flame-ota-qq2a.200405.005-2b5150a4.zip

thanks for the guide and files! i followed it step by step and had no probs at all. i have both the 4 and 4XL and wanted to stop in and say thanks for both guides. update went smooth on both devices
btw i was using stock kernel but restored both the boot and dbto images just in case. no problems there either.

Question How to get Android 12 OTA update?

My device is rooted and I want the OTA update for Android 12. I found some guides out there that basically say to try this:
1. disable automatic update
2. uninstall/restore stock boot image with Magisk
3. install OTA update
4. reinstall Magisk to the inactive slot
5. reboot
For example, https://ihax.io/install-ota-updates-rooted-android/
However when I got to step 3 it's still telling my my device is up to date with Android 11. So how to get this updated to Android 12? (without losing any of my data or settings, of course)

Maybe use the Android Flash Tool

According to the Pixel 5 forums, it's not possible to update to 12 without a wipe. So guess I'll wait until things are sorted out.
READ THIS if you're rooted before you upgrade to Android 12
If you're running rooted Android 11 and plan on updating to Android 12, READ THIS FIRST. Two new Verified Boot features implemented in Android 12 will interfere with attempts to root. I will cover what these are and how they can be bypassed...
forum.xda-developers.com
[Closed] Android 12 Update and Root ***Obsolete***
Update 12-16: I am closing this thread as it is no longer relevant. Please refer to this guide.
forum.xda-developers.com

scarlion said:
According to the Pixel 5 forums, it's not possible to update to 12 without a wipe. So guess I'll wait until things are sorted out.
READ THIS if you're rooted before you upgrade to Android 12
If you're running rooted Android 11 and plan on updating to Android 12, READ THIS FIRST. Two new Verified Boot features implemented in Android 12 will interfere with attempts to root. I will cover what these are and how they can be bypassed...
forum.xda-developers.com
[Closed] Android 12 Update and Root ***Obsolete***
Update 12-16: I am closing this thread as it is no longer relevant. Please refer to this guide.
forum.xda-developers.com
Click to expand...
Click to collapse
IDK that flash tool has an option for deselecting wipe, verity and vbmeta.
But I'm staying on 11 for now.

MrPolite said:
IDK that flash tool has an option for deselecting wipe, verity and vbmeta.
Click to expand...
Click to collapse
Ok I'll ask about that, need to be sure.
MrPolite said:
But I'm staying on 11 for now.
Click to expand...
Click to collapse
How come?

scarlion said:
Ok I'll ask about that, need to be sure.
How come?
Click to expand...
Click to collapse
Aesthetics

It just showed up for me on the day it was released.
Sidenote, is anyone else experiencing the video camera being ridiculously cropped after the Android 12 update? I'm tempted to try to find and sideload the older camera app, if you're still running 11, could you tell me what version it's on?

I'm using this one 8.2.204.362396359.12

You shouldn't have to remove Magisk.
The most important and critical issue is to remember to reflash vbmeta BEFORE your phone boots to system, otherwise you will have to wipe /data again.
There's two ways to update:
1. Sideload the OTA (DO NOT use the automatic OTA). When the sideload finishes, immediately reboot to bootloader, and reflash vbmeta:
Code:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
Now, you can flash a patched boot image, if you already patched it, or you can boot into system to do so, then reboot to bootloader to flash it.
2. Dirty flash the factory image, either via ADB or via Android Flash Tool. To do it via adb:
Code:
fastboot update --disable-verity --disable-verification image-bramble-buildnumber.zip
No need to reflash vbmeta as you already included the flags.
If you want to be able to prevent reboot so you can flash the boot image, add --skip-reboot.

Is not possible now to get Device Certified in PlayStore? After flashing Magisk?

peikojose said:
Is not possible now to get Device Certified in PlayStore? After flashing Magisk?
Click to expand...
Click to collapse
It is - using Universal SafetyNet Fix. I'm using Magisk 23001 + USNF 2.1.1 on my Pixel 5, and pass SafetyNet.