yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
OK, so what i tried is:

I load PGPT part into WWR to see tables. acording that i found Start and Lenght of "metadata" partition.

View attachment 6090703

So in spflash set :

Region: EMMC_USER

start:0x5688000

lenght:0x2000000

This should readback only "metadata" partition right? ( i am using BROM mode to readback, holding volumeup before connecting)

Interesting part is after connecting. It loads red bar "downloading DA 100%) and after 4-5 seconds it stuck on 0% readback and just counting time.

View attachment 6090708

After about 5 mins. i get error code:

View attachment 6090710

I found that this error should mean that readback lenght is too large and i should skipp userdata and cache. But iam trying to dump only metadata so it shouldn´t be large. ( can different cable help? or reinstall MTK VCOM drivers?)

Interesting part is that sometimes It readback 2% or 6% and stuck after that.. sooo should i just keep trying to readback to 100%?

View attachment 6090713

(edit: even at try to dump full rom with "Full volume of GPT) it behave same.)
[Android Q&A, Help & Troubleshooting] alecxs:
drivers are ok, maybe error with usb connection, or maybe emmc wear-out? at least that explains why mtkclient failed. sometimes it can be useful to try another PC with usb 2.0 port, but you have dumped preloader earlier and it was working fine, so most likely usb connection is fine too.

I could imagine that is caused by secure boot, some kind of read protection maybe. But this is end of my support, I have no idea what is going on.

search for SLA/DAA bypass, this is a secure boot exploit that is applied right before SP Flash Tool is connected (mtkclient already does this automatically)

It's now easy to bypass MediaTek's SP Flash Tool authentication

A group of developers has created a Python utility to bypass the authentication routine of MediaTek SP Flash Tool. Check it out now!

www.xda-developers.com
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
I will try it somehow. Anyway thank you for support. Can i inform you in case i will dump metadata to continue?
[Android Q&A, Help & Troubleshooting] alecxs:
yes of course please keep us updated ;)
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
So just an update:

I tried python method to disable autentication . everything went smooth (installation, drivers etc.)

I runthis code which should disable protection.

python main.py

but i get different result as on screenshots. I should get "protection disabled" and start readback in sp flashtool next with disabled protection. But this is my result.

View attachment 6090999

I noticed it says Device download agent authorization: False . Does this mean that device is not protected to readback? Question is why than SPflashtool have problem to readback..hmm.This is like some magical circle..

Option2:

I found some modified verison of SP flash tool by Kurdish firmware which should have Auth bypass integrated into software.

but results are the same: ( readback 0% and counting time)

I will be trying more and maybe try all steps inside Linux interface again..
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
I just tried different cable and different USB port on my PC. And tried readback only Metadata part again with :

Region : EMMC_USER

Start:0x5688000

lenght: 0x2000000

And now it readback 12% (4MB file)

View attachment 6091038

Soo maybe just problem is interupting and unstable connection?
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
Ok next update. With some miracle i get respond from official manufacturer Doogee from Shenzhen , China. after explanation of situation and confirming ownership of device they provide me official ROM with best drivers and SP flash tool verison which should be best for this. So i will give it a try and compare scatter files and other. View attachment 6091055

View attachment 6091056

So atleast i will be sure that scatter files / preloader and partitions are correct.
[Android Q&A, Help & Troubleshooting] alecxs:
either this, or

either this, or eMMC wear-out. latter one would prevent to bring back device to life with factory reset.
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
Hello again,

just small update. I unzip and download all files from manufacturer. There are like 8 version of firmware depending of update version of system in whole years of support. Funny thing is if i open any scatter file in SP flah tool it it completely different with adresses as ONE which i was using till now to dump preloader.

My thoughts are that maybe i had wrong firmware and scatter file, that mean maybe ROM_0 dump was not correct and even MTK client can´t complete metadata dump due bad preloader given?

Any way i will try to repeat whole process ( ROM_0 dump , ROM_1 (pgpt) dump, and Mtkclient metadata dump ) with every scatter and every version given from Doogee and let you know results.

EDIT: I just realize that preloader nad pgpt will still be 0x0 and 0x40000 so it will readback same files. Nevermind my bad
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
Just an idea, Flash device with Official firmware and after that restore backup from sdcard won´t work? it will change crypto footer? and cannot decrypt files?

Isn´t whole problem that i put device in factory reset about 2 years ago?
[Android Q&A, Help & Troubleshooting] alecxs:
no

yes

no

Right, and there is no way to recover it. what you do is just for learning... examination of metadata partition might give you clarification that indeed the crypto-footer is located in metadata partition (and therefore not included in backup)
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
OK, so I think i am on dead end now. Basically today manufacturer confirmed me that it is located in metadata and that device is really FDE. So i dont see any need to continue. I am sure that i will not recover lost data and access to gallery. But that is ok , at least i finally know after years.

Anyway i want to say Thank you. It was really a path. I learned sooo many things. Thank you for every spent minutes you dedicate to my problem. I really appreciate it and wish you all best to whole XDA community. you helped a lot. With newly learned knowledge and wisdom i will try to unbrick my device at least ( I think i can do it now with no problems after years) :) Thank you so much again.
[Android Q&A, Help & Troubleshooting] alecxs:
curious about factory reset. update result?
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
So Update:

Device was bricked and stuck in bootloop with Volume Up + power button i was able to open menu:

1- Normal Boot

2 -Fast Boot

3- Recovery boot

No option from this works and device just restart over and over.

So i tried Firmware upgrade in Sp flash tool with official ROM from Doogee and all finished and now device is fully functional and working. So device is working with new software so atleast all this "training" was beneficial. Thanks again to everyone involved.
[Android Q&A, Help & Troubleshooting] alecxs:
more exercise.. unlock bootloader, disable force encryption and format userdata to stay unencrypted ;)
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
That sounds interesting and due i have now working spare device it will be fun to lear new things.

Anyway just a theoretical question. I already know that now "crypto footer" changed and there is no way to recover it to be able decrypt my backup files. But i was just wondering, searching and thinking. Is there any possible way to decrypt those data? maybe idk bruteforce or maybe some professional forensic company. Is it even possible. I found some company which is presenting they are decrypting MTK data but after contacting them they are doing it only for goverment purpose. That is ok but now i have in my mind it is possible somehow. Do you have maybe some clue?
[Android Q&A, Help & Troubleshooting] alecxs:
it's possible to bruteforce pin on healthy crypto-footer. but if crypto-footer is broken or missing, no company in the word can bruteforce that. have a look into how crypto-footer looks like :)

https://xdaforums.com/t/android-10-encryption-issue-after-rom-downgrade.4168821
[Introductions] SirCyril:
Hi to everyone!

Glad I found this forum and I hope I will find the answer to my Android phone problems!

Thanks in advance, have wonderful days!
[Introductions] EllieCat:
Welcome to XDA! Hope you have a nice time here!
[OnePlus 9] absolute_noob:
PixelOS is an AOSP-based ROM, with Google apps included and all Pixel goodies. We aim to provide an experience similar to Google Pixel phones with numerous performance enhancements and a small amount of useful additional features.

/* 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 ROM
* 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.
*/

Our Blog
​

Device-specific issues:

None

Requirements

OnePlus 9 with OOS 13.1 running

Downloads

Download Rom PixelOS_lemonade-14.0-20240520-1219.zip

Firmware Flasher Firmware_OnePlus9.zip

Notes

• Encryption is enabled by default

• Latest Firmware is included

• KernelSU can be flashed seperately

• SafetyNet Passed (Device Level Integrity)

Flashing Instructions

Clean flash (coming from a different ROM):

• Download ROM PixelOS_lemonade-14.0-20240520-1219.zip

• Download Firmware Flasher Firmware_OnePlus9.zip

• Reboot to bootloader

• Run Pixelos_Flasher.bat from Firmware Flasher

• Format data

• Sideload ROM zip `adb sideload PixelOS_lemonade-14.0-20240520-1219.zip`

• Reboot to recovery & reboot system and voila!

• To get root access, Install KernelSU.apk".

Updating to a newer build (dirty flash):

• Sideload ROM zip and optionally Magisk

• Reboot and voila!

Read our blog https://blog.pixelos.net

Join our Telegram Group https://t.me/PixelOSChat

Join PixelOS OnePlus 9/ 9 Pro Community = https://t.me/PixelOS_9pro

If you've noticed anything that isn't translated in a language you speak, please consider helping out with the translations.

https://translate.pixelos.net

Testings are done by

@AxE_MaNhaunt, @davut000

Donate to me using UPI!

rootme@ibl

Source Code

PixelOS http://github.com/PixelOS-AOSP

Device Tree https://github.com/absoluten00b/device_oneplus_lemonade

Vendor Tree https://github.com/TheMuppets/proprietary_vendor_oneplus_lemonade

Kernel Tree https://github.com/absoluten00b/kernel_oneplus_sm8350

ROM OS Version: Android 14.

ROM Kernel: Linux 5.4.x
[OnePlus 9] absolute_noob:
####Changelogs (20/05/24)######

Added OOS CAM

KernelSU Inbuilt

Source Rebase

QPR2 Merged

Improved Battery life & Haptics
[OnePlus 9] absolute_noob:
reserved #2
[OnePlus 9] shadabkiani:
@absolute_noob Great work. Thanks for doing this for OnePlus 9.

Does it have OOS cam?

Also, what is the firmware version? Could you please rename the firmware flasher zip with with version number included, just like crDroid's? And also put the firmware version number in upcoming changelogs for builds?
[OnePlus 9] robmau:
Just posting here the issues ive encountered:

-No fingerprint unlock

-Camera doesn't work properly, is stuck on Wide angle lens, no way to use regular lens. Crashes when switching to video camera etc.

-Notch for camera is in wrong place

-The edges of the screen are beveled a lot, moreso than whats visually available on the Oneplus 9 screen. Maybe this is from the Pixel ROM, but it would be nice to be able to use the whole screen.

Otherwise amazing work. Thank you.
[OnePlus 9] absolute_noob:
can u give me a video recording of notch and these issues?
[OnePlus 9] absolute_noob:
post it at https://www.t.me/binaryninja01/
[OnePlus 9] absolute_noob:
no
[OnePlus 9] xlinux_:
Dude seriously? It's an unofficial build no ones got time for that.
[OnePlus 9] shadabkiani:
What's your problem? I simply asked humbly if he could. It's not like I complained. And you said no ones got time for that, but you got time to post stupidity.
[OnePlus 9] xlinux_:
Okay.

To be Frank I was genuinely confused with your enquiry.
[OnePlus 9] borg79:
Is it possible to sign the rom zip file so that the no bootloader warning will show up ?
[OnePlus 9] Vikramgophane:
No updates???
[OnePlus 9] leezaal:
Many thanks
[OnePlus 9] absolute_noob:
Added OOS CAM and it's fully working
[OnePlus 9] rtal_kebda:
Guys can I dirty flash this coming from CrDroid A14 ?
[OnePlus 9] shadabkiani:
Better not to. Do a clean flash when jumping from a different ROM.
[OnePlus 9] Elerir9:
Hello,

Regarding the may security patch update that checks for rom signature to pass device integrity, is this rom signed?

thank you
[OnePlus 9] korudero:
Heads up, unzipping otacerts only lists a testkey. I'm getting consistent failure to meet device integrity no matter what fix I try to apply. If you could update the ROM so it's signed, that'd be great. I'm on the latest 05/20 build.
[OnePlus 9] mikiwinds:
Hi, where do I download the updates from and how do I install them? Ota? ADB? thk
[OnePlus 9] shadabkiani:
Don't use this ROM. It's not updated for regular OnePlus 9. Last build was in May, which wouldn't be signed. Google now requires signed builds in order for Play Integrity to pass. This ROM would fail that and your banking apps won't work. Use MatrixX or Nameless ROM. Their threads are in OnePlus 9 Pro's forum but builds are also available for regular OnePlus 9. I recommend MatrixX since it is frequently updates and is stable and tons of features.
[Samsung Galaxy S24] pman321:
I set up a 4-digit pin for my screen lock and it doesn't work the ok button dose not light up i have been locked out for a week.
[Android Q&A, Help & Troubleshooting] SirCyril:
Hi everyone!

I bought a Realme C31 phone - 3 GB RAM, 32 GB ROM - in May 2023.

I travel a lot, so the phone just sat unopened in a drawer until a few days ago.

Then the weirdest thing happened:

Setting the phone up for the first time, I went into the Display settings to increase the luminosity (I wear glasses...)

The available options for color were - gentle, vivid, bright. I put the phone on "vivid"

After a time I noticed the display became very dim and the colors were "washed-out"

I went into the Settings again, and now the only available color mode is "gentle sRGB for an easy viewing". All the other color modes have vanished!

It runs on Android 11, May 2023; I did not update the phone, it was set up without network.

The "night light", "adaptive brightness", "battery saving" are all turned off.

I also noticed it is impossible to enter the reset Android mode by pressing the power and volume down buttons; it just turns on as usual. And the developer option to "unlock the bootloader" which was available when I started setting up the phone, is now greyed-out.

What is happening?

Is there any way to solve this?

As I said I wear glasses and I need the screen to be very bright.

I can't return it since I bought it 8 months ago.

Thanks in advance for any solutions!
[Android Q&A, Help & Troubleshooting] zinkles:
Can you reset it through the phones' settings, or by some dial code?

Can you verify if those buttons are indeed functional?

The unlock bootloader button/OEM unlock usually greys out once you've already unlocked the bootloader.

if USB debugging is enabled, you could try plugging it into a PC and then using adb reboot recovery to get into the recovery mode and reset the phone from there. if reset doesn't bring any luck, you can try flashing the stock ROM by going into fastboot mode (adb reboot-bootloader).
[Android Q&A, Help & Troubleshooting] Alexander92013:
you can flash your firmware
[Android Q&A, Help & Troubleshooting] SirCyril:
Thanks for the answers!

The buttons work ok, usb debugging is enabled, the PC sees it.

I tried getting into adb recovery, it does not respond.

It just gets into fastboot mode and stay stuck there until I force it to turn off.

All I wanted was for it to recover the "vivid" and "bright" display colors...

I am not very technical, so am not sure exactly how to flash the firmware.

If you have any suggestions, thanks once more!
[Android Q&A, Help & Troubleshooting] zinkles:
you need to be able to get into fast boot or recovery mode to be able to flash or recover. Or you could try a dial code to open up the updater and manually update from there using the firmware update.zip file
[Android Q&A, Help & Troubleshooting] SirCyril:
Thanks very much for the reply!

I will try to flash the firmware and hope not to break the phone...

Will keep you posted!

Have a nice weekend!
[OnePlus 12] chrissss91:
Hi OP12 owners 🙌,

I find that Bluetooth volume is really too low so I would like to boost it (and do not touch to Speaker).

I used Viper4Android on my OP5 but had given up to make it work on my Xiaomi Mi11 Ultra.

Do you know if there is a working Viper4Android/ViPER4Android-RE/ViperFX RE/... for our dear OP12 (preferably a Magisk module) ?

If you have any advice on how to manage sound level per device don't hesitate.
[OnePlus 12] nanodan:
Viper4Android RE works just fine for me on NA version of OOS 14 rooted with Magisk Canary 27001.

Releases · AndroidAudioMods/ViPER4Android

ViPER4Android app configuration files. Contribute to AndroidAudioMods/ViPER4Android development by creating an account on GitHub.

github.com
[OnePlus 12] chrissss91:
Nice, it works without having to modify anything.

It makes my day.

Thank you very much !
[OnePlus 12] bbortel93:
Can confirm it's working and setup is a breeze. However playback gain control doesn't work with my OnePlus buds or through the speaker and it doesn't work at all connected to Android Auto.

Anyone found a solution to this?
[OnePlus 12] chrissss91:
Hi,

"Playback gain control" works for my OnePlus Buds (tested with Spotify).

I had to disable Spacial Audio in OOS for V4A to work with the Speakers (otherwise there is no sound when V4A is activated).

Some apps are not compatible, Youtube Revanced for exemple.
[OnePlus 12] bbortel93:
Really? My spatial audio setting is disabled and still playback gain control is greyed out. Can you confirm with a SS?
[OnePlus 12] chrissss91:
Oh, you're right, I confused it with Master limiter/Output Gain.
[OnePlus 12] bdvince:
For me, V4A does not seem to work with any audio streaming apps (Youtube Music, Spotify, etc..). The sound immediately cuts out and Driver Status is Abnormal with INVALID_CHANNEL_COUNT error.

Switching to Legacy Mode does allow the sound to start working however then the options don't actually do anything and there is no sound processing even though the Driver reports a normal status.

I'm going to attempt to apply some Audio Mods (Audio Compatibility Patch, Audio Modification Library) however I really wanted something that could boost OP12 poor in-call volume. I might play around with the mixer_paths.xml later and see what results I can get.
[OnePlus 12] asdor:
I can be mistaken but if you want to use gain control to increase the volume of your speakers or earphones there is a nice app Volume Booster https://play.google.com/store/apps/details?id=com.goodev.volume.booster.

Always worked for me with all of my phones, no root needed.
[OnePlus 12] nanodan:
It works perfectly for me for Spotify without Legacy mode. It however does not work for apps that use a different mixer configuration, like SoundCloud, or Instagram, Twitter, etc. I tried to use the Audio compatibility patch which used to be able to at least get SoundCloud to work too, however neither patching method worked. Spotify is really the only main thing I need it to work on though so I've been satisfied.

I'm not sure what makes it apparently not work for some people, all I had to do was root, flash the magisk module, install the apk, reboot, and launch viper. I do however have both the audio compatibility patch (remove logic) AND the modification library module installed at this point, even though I don't think the ACP is working. Do note that Viper4Android RE is in development and does not have all the functionality of the original viper yet. They are trying to reverse engineer (hence the RE) viper to have an open source code base.
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] kolakid111:
So i ve i ve using fastboot flash recovery_ab recovery.img in fastboot mode and phone just bootloop
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] kolakid111:
wow it boots with OrangeFox-R11.1_5-Beta-marble.img
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] NOSS8:
for REC version

fastboot flash recovery_ab twrp.img(cmd)

or

./fastboot flash recovery_ab twrp.img(Power Shell)
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] kolakid111:
C:\Program Files (x86)\ADB and Fastboot++>fastboot flash recovery_ab twrp-v8.3_A14-marble-skkk.img

Sending 'recovery_ab' (102400 KB) OKAY [ 4.824s]

Writing 'recovery_ab' (bootloader) Partition recovery_a flashed successfully

(bootloader) Partition recovery_b flashed successfully

OKAY [ 0.786s]

Finished. Total time: 6.622s
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] kolakid111:
and it booltoops after i twrped him...
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] kolakid111:
with orange fox its ok but i want twrp. or it doesnt matter?
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] NOSS8:
What rom on the phone (full name)?
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] kolakid111:
orange fox said there is already no rom on my phone, but was aospa. paranoid. i wiped everything
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] kolakid111:
orange cant see why usb otg =\
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] kolakid111:
now i want to flash https://xdaforums.com/t/rom-14-0-marble-project-elixir-official-stable-aosp.4657694/

they linked this twrp on their forum
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] NOSS8:
Is the current system in A14?
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] kolakid111:
there

there is no current system, i wiped everything and format, no im copying project elixir
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] NOSS8:
You formatted the data not the system, so what is the current system?
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] kolakid111:
[ROM][14] Paranoid Android Uvite - POCO F5 / Redmi Note 12 Turbo (marble)​

but in already flashed

[ROM] [14.0] [MARBLE] Project Elixir [OFFICIAL] [Stable][AOSP] and its booting!!!​
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] NOSS8:
Flash a fastboot rom corresponding to the firmware requested for the rom then install the TWRP.
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] kolakid111:
ok.then i will sit on orange fox
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] Blank504050:
Do you have to use the miflash tool for that? Or just fastboot?
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] NOSS8:
As you wish, just with the script it is faster since there is no need to install Miflash and configure it, the only advantage is that it provides a precise log which can be useful if there is a problem and also provides the drivers.
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] Blank504050:
By "script" you mean fastboot flash rom.zip ?
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] NOSS8:
Nope, the script included in the folder extracted from the fastboot rom (tgz).
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] Blank504050:
Oh didn't know that. Thanks.

Where do you find these roms btw? XFU? Or someplace else?
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] NOSS8:
HyperOs

XM Firmware Updater

The ultimate script that provides firmware packages for Xiaomi devices.

xiaomifirmwareupdater.com

Miui

XM Firmware Updater

The ultimate script that provides firmware packages for Xiaomi devices.

xiaomifirmwareupdater.com
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] Gieare91:
help i also encountered a problem updating recovery sssk version 8.6

using old version 8.0 flashed both a and b then boot only in fastboot
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] NOSS8:
Try flashing the old one.
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] NOSS8:
Use Miflash or Fastboot as indicated on this thread.