Database Info

Verizon Pixel XL stuck on 7.1.2 - I think?

Been reading all of the relevant threads.
Installed the latest Android Studio / SDK tools.
Verizon Pixel XL, Android 7.1.2, Build NHG47N, June 5 2017 Security Patch.
Bootloader is locked.
Every time I attempt to do an OTA update over WiFi (To Oreo 8.0), it downloads successfully, and then fails.
A locked Bootloader on a Verizon Pixel XL is a showstopper for flashing ANY version of Android from a computer - Correct?
If a Pixel XL won't install an OTA update after downloading, there's nothing that can be done to correct it - Correct?
I am... in a dead end? Correct?
-FP

tenbbs said:
Been reading all of the relevant threads.
Installed the latest Android Studio / SDK tools.
Verizon Pixel XL, Android 7.1.2, Build NHG47N, June 5 2017 Security Patch.
Bootloader is locked.
Every time I attempt to do an OTA update over WiFi (To Oreo 8.0), it downloads successfully, and then fails.
A locked Bootloader on a Verizon Pixel XL is a showstopper for flashing ANY version of Android from a computer - Correct?
If a Pixel XL won't install an OTA update after downloading, there's nothing that can be done to correct it - Correct?
I am... in a dead end? Correct?
-FP
Click to expand...
Click to collapse
Side loading ota and beta/preview builds should still work/I think/ but you should probably just request an RMA cuz Google seems to like to throw money at replacing these phones when they can and I'm pretty sure OTA failure is something they cover

Blu Vivo XL4 Rooting and Custom Rom Questions

I want to root this phone, mainly to turn off dm-verity because it keeps popping up even after a factory reset and this may be my only good option, but what custom rom should I use for this? I tried looking around and couldn't find any recommended ones. Blu Vivo XL4 android version 8.1.0 and the roms I looked at (Corvus OS, AOSPExtended) did not list my device for the downloads at all. Any suggestions or help for rooting this thing? First proper rootable phone I have gotten and I'm not sure the best process for this.

Jewel724 said:
I want to root this phone, mainly to turn off dm-verity because it keeps popping up even after a factory reset and this may be my only good option, but what custom rom should I use for this? I tried looking around and couldn't find any recommended ones. Blu Vivo XL4 android version 8.1.0 and the roms I looked at (Corvus OS, AOSPExtended) did not list my device for the downloads at all. Any suggestions or help for rooting this thing? First proper rootable phone I have gotten and I'm not sure the best process for this.
Click to expand...
Click to collapse
Vivo doesn't allow bootloader to be unlocked

That's nonsense, I can enable OEM unlocking in the developer settings, ain't that what's required?

Austinredstoner said:
Vivo doesn't allow bootloader to be unlocked
Click to expand...
Click to collapse
It's not Vivo company! That's a BLU company.
Jewel724 said:
I want to root this phone, mainly to turn off dm-verity because it keeps popping up even after a factory reset and this may be my only good option, but what custom rom should I use for this? I tried looking around and couldn't find any recommended ones. Blu Vivo XL4 android version 8.1.0 and the roms I looked at (Corvus OS, AOSPExtended) did not list my device for the downloads at all. Any suggestions or help for rooting this thing? First proper rootable phone I have gotten and I'm not sure the best process for this.
Click to expand...
Click to collapse
You need a special steps for work. Not a exclusive file to your phone because GSI (actual custom rom for any device with Android 8.1 and next android version) need some files to fix booting that in your device. But the happy notice is about actual GSI files not need very files for fix or maybe nothing.
Try install AOSP from phhusson Android 9 and Android 10 repository to know. Other great GSI is crDroid by eremitein or other GSI files by him. Need testing.

DragonPitbull said:
It's not Vivo company! That's a BLU company.
You need a special steps for work. Not a exclusive file to your phone because GSI (actual custom rom for any device with Android 8.1 and next android version) need some files to fix booting that in your device. But the happy notice is about actual GSI files not need very files for fix or maybe nothing.
Try install AOSP from phhusson Android 9 and Android 10 repository to know. Other great GSI is crDroid by eremitein or other GSI files by him. Need testing.
Click to expand...
Click to collapse
I'm on.. what's it called, Oreo? Android 8. Not sure if that's going to cause any trouble for roms.

Jewel724 said:
I'm on.. what's it called, Oreo? Android 8. Not sure if that's going to cause any trouble for roms.
Click to expand...
Click to collapse
Yes! Android 8 from very OEMs/companies not have Treble/GSI compatibility.
Only Android 8.1 has that.
Update: Install this app https://play.google.com/store/apps/details?id=tk.hack5.treblecheck&hl=en-US in the phone and know what architecture your phone/firmware has. That will show you which type of GSI file you can test.

Listing what that app says..
Required Image: Needs an image file named system-arm64-aonly.img.xz
Treble and VNDK: Supports legacy version of Treble, using VNDK version 27.0
System as Root: Does not support, use an a-only OS.
ARM-64 archetecture.
Seamless Upgrades not supported.
Does not use Dynamic Partitions.
Unless I missed anything, is this what was needed? Also I am on 8.1.0 for android version, I didn't know if that was just Oreo or if 8.1 had it's own name.

Jewel724 said:
Listing what that app says..
Required Image: Needs an image file named system-arm64-aonly.img.xz
Treble and VNDK: Supports legacy version of Treble, using VNDK version 27.0
System as Root: Does not support, use an a-only OS.
ARM-64 archetecture.
Seamless Upgrades not supported.
Does not use Dynamic Partitions.
Unless I missed anything, is this what was needed? Also I am on 8.1.0 for android version, I didn't know if that was just Oreo or if 8.1 had it's own name.
Click to expand...
Click to collapse
In the first update Android 7.1 [Nougat] to 8.0 and after upgrade to 8.1 [Oreo]. Normal.
All informations good to know what GSI you should test.
Now you can install with fastboot or Custom Recovery [TWRP]. So if has is better and fast.
If not so can using fastboot commands.
Obviusly need bootloader unlocked!
You can read and find more threads but this is good: https://forum.xda-developers.com/t/guide-blu-vivo-xl4-vivo-xi-vivo-xi.3877294/
The only part I should warn you about is the loss of IMEI. So soon as you can do backup from your phone the files NVRAM; NDATA; NVCFG with SPFT or other way like fastboot you won't have wasted time and hassles.

DragonPitbull said:
In the first update Android 7.1 [Nougat] to 8.0 and after upgrade to 8.1 [Oreo]. Normal.
All informations good to know what GSI you should test.
Now you can install with fastboot or Custom Recovery [TWRP]. So if has is better and fast.
If not so can using fastboot commands.
Obviusly need bootloader unlocked!
You can read and find more threads but this is good: https://forum.xda-developers.com/t/guide-blu-vivo-xl4-vivo-xi-vivo-xi.3877294/
The only part I should warn you about is the loss of IMEI. So soon as you can do backup from your phone the files NVRAM; NDATA; NVCFG with SPFT or other way like fastboot you won't have wasted time and hassles.
Click to expand...
Click to collapse
I'll give it a shot. In terms of performing a backup, I would assume that' typical "copy all files on phone to desktop folder just in case"

I should've mentioned, I don't have an SD card in my device, just a SIM card. I don't think I can use TWRP, which is going to complicate matters.

Hello I have a Blu Vivo XL4 android 8.1.0 Oreo, I'm trying to install a custom rom, I looked everywhere not a single rom is made for Blu phones.
bootloader unlocked
according to treble info:
System-arm64-aonly.img.xz
Your device supports the legacy version of project treble using VNDK version 27.0
Use an A-ONLY operating system
ARM64
Seamless upgrades are not supported
NO dynamic partitions
HELP
thanks

General Lenovo P12 Pro Android 12L Developer Preview Program (TB-Q706F)

Just read the news https://www.xda-developers.com/android-12l-developer-preview-1-lenovo-p12-pro/
It looks like it's still on early stage but here is the link for instructions and download:
DPP
dev.lenovo.com
The first large screen optimized Android OS with new APIs for application developers to provide a better app usage
experience in landscape mode, including easier multitasking, system UI optimization and more.
Security patch updated to 2021-11-01
Android 12L DP1 image is available.
Click to expand...
Click to collapse

WORD OF WARNING!!
DO NOT USE THE LENOVO SMART RECOVERY ON THE CHINESE XIAOXIN VARIENT. If you flash the P12 firmware to the XIOAXIN Variant you will be stuck in the boot loader with no access to Recovery or ADB.

I actually did use the Lenovo RSA (Recovery and Smart Assistant) on my Xiaoxin variant trying to get it to something more English-based. Didn't work w/ what RSA downloaded which was TB_Q706F_USR_S211043_2111300010_Q00243_ROW which showed up recently. Flash happened w/o problems but upon reboot it was not happy and said H/W was incompatible and then powered off. I got it back into fastboot and was about to reflash 12L.
I was able to get into recovery and my Linux laptop was able to push 12L to it even though adb said device was unauthorized. Maybe that was because I had used it on that laptop before? Idk, I just used recovery to go into fastboot mode and then all the fastboot flash/erase commands worked fine.

Slimerang said:
I actually did use the Lenovo RSA (Recovery and Smart Assistant) on my Xiaoxin variant trying to get it to something more English-based. Didn't work w/ what RSA downloaded which was TB_Q706F_USR_S211043_2111300010_Q00243_ROW which showed up recently. Flash happened w/o problems but upon reboot it was not happy and said H/W was incompatible and then powered off. I got it back into fastboot and was about to reflash 12L.
I was able to get into recovery and my Linux laptop was able to push 12L to it even though adb said device was unauthorized. Maybe that was because I had used it on that laptop before? Idk, I just used recovery to go into fastboot mode and then all the fastboot flash/erase commands worked fine.
Click to expand...
Click to collapse
That's great news at least you're tablet isn't useless?!
I believe they may be releasing the final updated for android 12L via ota. (there is a post on the Lenovo forums). If you're lucky this may be a back door to an eventual better rom than the Chinese junk. To clarify it's not the fault of the language that is the issue with the Chinese rom it's the problems with the security app, lack of open CL, broken sound in key apps (JustPlayer) and missing DTS codec which is present on the 2021 Pad Pro 11"

Help with rooting/Nethunter on Pixel 3a

Hello, I've been searching and lurking.. I've unlocked the bootloader on my Pixel 3a. I've rooted before, restored before, nandroids etc etc. So I've been in the game for a little while. (all the way back to my LG Ally!) Anyways. I was wondering what would be the best method of Rooting and installing TWRP on the Pixel 3a at this point in time, and if TWRP is even possible at this point. (September 2022) Should I use Magisk? NetHunter seems to rely on the device having TWRP in order to flash the kernel. (but we don't NEED it to flash the kernel do we?) I keep coming across old posts which do not apply to the build of my phone and I'm feeling very lost. This phone is not my daily driver, and I am confident when it comes to restoring a soft-brick. It's a Google Fi pixel, bought from the google store, maybe that helps.
Android 11, RQ2A.210405.005 (info from recovery)
BL Version : b4s4-0.3-7062600 (fastboot)
Baseband Ver: g670-00105-210113-B-7078968 (fastboot)
Secure Boot - Yes (fastboot)
HW Ver - MP1.0 (fastboot)
EDIT: Rooted phone successfully using Magisk/patched boot.img.
NEW ISSUE! : The phone is showing up as a Pixel 5 now. In rootchecker, my first successful root shows Pixel 3a as the device. This has never happened to me before. Any input would be greatly appreciated!

Question Downgrade A53 (A536B) from android 13 to 12

Hey guys all good?
I got my hands on an A53 already on Android 13 (U.I 5.1), then I unlocked the bootloader, rooted, magisk working but then I decided to downgrade from 13 to 12 because of a few things
I tried via Odin (13.14.4 and 13.12.7) and both didn't work the first odin it fails the flashing and the second pass but it didn't flash the whole thing just reset the phone
any idea? or I'm now stuck with Android 13?
Cheers

From what I can find, Odin supposedly won't allow a downgrade if the boot loader version is lower.
That's just what people seem to say about Samsung devices and downgrading. I've never tried it and never will. Would immediately use multiple OS versions however if Android actually supported dual booting. Its fantastically messed up that it doesn't.
Not sure if TWRP will. Didn't look that one up. You didn't bring that one up but it might be a way to do it.

sandsofmyst said:
From what I can find, Odin supposedly won't allow a downgrade if the boot loader version is lower.
That's just what people seem to say about Samsung devices and downgrading. I've never tried it and never will. Would immediately use multiple OS versions however if Android actually supported dual booting. Its fantastically messed up that it doesn't.
Not sure if TWRP will. Didn't look that one up. You didn't bring that one up but it might be a way to do it.
Click to expand...
Click to collapse
Thanks for the reply. I was thinking something about that too. Not that the bootloader is lower but that it was modified (root) i guess
Unfortunately TWRP is not compatible yet with Android 13 UI 5.1 at least accordingly to this topic
So i guess I'm stuck for now

biustech said:
Thanks for the reply. I was thinking something about that too. Not that the bootloader is lower but that it was modified (root) i guess
Unfortunately TWRP is not compatible yet with Android 13 UI 5.1 at least accordingly to this topic
So i guess I'm stuck for now
Click to expand...
Click to collapse
You could flash a GSI image, but I guess that wouldn't be OneUI anymore

Hello you all hope you're having a good day, so no way to downgrade a53 5g from Android 13 to android 12 ??? I found some firmwares for Android 12 but the binary number is 4 and Android 13 is actually on binary number 5 , no way to do the downgrade with Odin?
I read somewhere that is not possible to flash a firmware with different binary number is it true ?? I would like to comeback to android 12 it's better