yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] display64:
smartphone completely armored and closed to any change, I hope someone tries ...
[Android Q&A, Help & Troubleshooting] Dr. lagg 1.1:
Buenas, yo también tengo un oppo a9 2020, estoy buscando como rootear lo y todavía no he encontrado nada, espero que aquí en xda que es donde siempre encuentro lo consigan hacer, sino significaría que este teléfono es de los más difíciles hasta ahora ya que todos los teléfonos que he tenido los he conseguido rootear y aquí siempre tienen la solución, aunque aveces tengo que ir a HTC pero está de xda es la mejor, saludos y espero que encuentren solucion al rostro del oppo a9 2020, si encuentro algo les pasó la info
[Android Q&A, Help & Troubleshooting] Supermatt01:
Just don't buy OPPO devices if you're looking to root. They don't allow it and XDA encourages them.
[Android Q&A, Help & Troubleshooting] acristobalj:
Hi, I have a Oppo a9 2020 too.

In a telegram group I have been told that you can root with these steps: (don´t have permission for url)

androidresult.com/root-oppo-a9-2020

Has anyone tried it?

Thanks so much
[Android Q&A, Help & Troubleshooting] Naxil:
dump

dump your phone rom and people can look how to root it. i have oppo a5 and have flashboot blocked
[Android Q&A, Help & Troubleshooting] Vipermaxx75:
Dump rom?

Forgive me, I'm unsure how to dump my rom so people can look at it? Can you explain or direct me to a specific thread on how to accomplish this? Thank you for your time.
[Android Q&A, Help & Troubleshooting] fosco_:
These are generic rooting instructions, first you need is a TWRP recovery image for the A9 which doesn't even exist.
[Android Q&A, Help & Troubleshooting] sresam89:
Why do you XDA is encouraging them?
[Android Q&A, Help & Troubleshooting] sresam89:
Why do you say XDA encouraged them? [MENTION=3211017]Supermatt01[/MENTION]

---------- Post added at 11:04 PM ---------- Previous post was at 11:03 PM ----------

Why do you say XDA encouraged them? [MENTION=3211017]Supermatt01[/MENTION]
[Android Q&A, Help & Troubleshooting] Supermatt01:
OPPO won't allow unlocking the bootloader and rooting. And XDA promotes OPPO devices any way. They used to not promote anything that wasn't development friendly. Now they seem to promote any company that makes them money.
[Android Q&A, Help & Troubleshooting] h4ckShit:
need help for root this f*cking device

:(:(:(:(
[Android Q&A, Help & Troubleshooting] TapaSte:
Any other owner of this decent device... that after the update to color os 7.1 has became more nice and reliable ?

:)
[Android Q&A, Help & Troubleshooting] purplecircle:
Mine is much more stable and seems faster but I really wish Oppo would unlock the bootloader. I need a few apps that only run on rooted devices so I carry my old rooted Moto G4 just so I can use those apps.
[Android Q&A, Help & Troubleshooting] enzolan:
Can you tell me how to record phone calls on Oppo A9 2020?

Thank you all
[Android Q&A, Help & Troubleshooting] Ax33_NightFall:
Oppo doesnt allow modifying their device's ..
[Android Q&A, Help & Troubleshooting] gardina:
Hi, I have an OPPO A9 , specifically, OPPO A9 2020 Snapdragon and I unlocked the boot loader..

I mainly followed this article https://www.androidjungles.com/how-to-unlock-bootloader-oppo-phone/

I already had adb platform installed on my laptop.. and that includes fastboot..

The guide said to download mediavcom drivers, I didn't do that.

So most of it was fairly standard.. I found the 'build' option in about, that you tap 7 times to get developer options. Option was in settings..about..version..build

then settings..additional settings..developer options..

from developer options, enable OEM unlock (So that's a bit unusual)

and of course enable usb debugging, as normal.

then it tells you to run some commands but really beforehand, you should choose "revoke usb debugging authorisations"

One unusual thing though was at one point when I tried to run one of the commands mentioned, it said "error: device unauthorized". And I got a similar message with the command adb devices.

The solution to that is mentioned at the accepted answer here https://stackoverflow.com/questions/23081263/adb-android-device-unauthorized

go to the developer options on the phone and click "Revoke USB debugging authorization", (which I suppose maybe revokes the need to have special authorization to allow USB debugging) then

adb kill-server, adb start-server, reconnect the device. And then running 'adb devices' (i'm glad to say) shows no message about the device being 'unauthorized', and other commands don't show any error of unauthorized either.

adb devices (click 'allow' if phone pops up with a message about usb debugging)

adb reboot bootloader

then the phone reboots, check if it shows the bootloader locked or not

fastboot devices

fastboot oem unlock

fastboot reboot

those commands are probably fairly standard in guides and are mentioned in that article.. + that article mentions some specifics re this phone that i've mentioned here re the oter options you need to choose in developer options - .. OEM unlocking and revoking usb debugging authorization.

EDIT- I did write this after I had already closed the cmd prompt..and was working off memory.. i'm currently in some doubt exactly what commands I used, and even if the phone is indeed unlocked.. I will update this post to make it more correct if I find out..I did use that link and that SO article. Though i'm a bit baffled 'cos at the moment I see fastboot isn't working.
[Android Q&A, Help & Troubleshooting] alecxs:
head over the Oppo A5 CPH1931 thread, there is a boot.img you can try (do not flash!)

try to boot from fastboot without flashing:

fastboot boot boot.img
[Android Q&A, Help & Troubleshooting] alecxs:
if the above boot.img does not work, download A9_2020_11_OTA_0430_all_MQg0Gb6DH3yF.ozip and check boot.img with HxD Hex Editor if it says OPPOENCRYPT! the file must decrypted with ozipdecrypt.py first. after successful decrypted check again with HxD must show ANDROID! - only then patch the (decrypted) boot.img with Magisk Manager and flash magisk_patched.img into boot partition (from fastboot).

If device boot-loop flash (decrypted) boot.img to restore it's original state.
[Android Q&A, Help & Troubleshooting] gardina:
Thanks.. I had written in one post that my phone was A5 by accident when it was A9, but I edited it and corrected it to A9. Out of curiosity, when you say "if the above boot.img does not work" , how would I (safely) determine whether a boot.img works?
[Android Q&A, Help & Troubleshooting] alecxs:
i wrote A5 intentionally because the devices are exactly the same.. if you type 'fastboot boot boot.img' and your phone boots you know it works ;)
[Android Q&A, Help & Troubleshooting] gardina:
Thanks, I will try the second file you mention

But here are some output from the first file you mention - the file that was in the thread you referenced.

OPPO A5 2020(CPH1931 )DEAD BOOT ALIVE BY AKSHAY BHANDARE.rar I extracted boot.bin and renamed it boot.img

Notice that besides fastboot boot boot.img giving a "waiting" message, fastboot reboot bootloader gives a "waiting" message.

C:\Users\User\Downloads>adb shell

adb server version (39) doesn't match this client (41); killing...

* daemon started successfully

127|OP4B80L1:/ $ exit

C:\Users\User\Downloads>adb devices

List of devices attached

6a129752 device

C:\Users\User\Downloads>fastboot boot boot.img

< waiting for any device >

^C

C:\Users\User\Downloads>

C:\Users\User\Downloads>adb shell

OP4B80L1:/ $ exit

C:\Users\User\Downloads>dir boot.img

Volume in drive C has no label.

Volume Serial Number is 4645-5DCE

Directory of C:\Users\User\Downloads

19/11/2019 12:25 100,663,296 boot.img

1 File(s) 100,663,296 bytes

0 Dir(s) 43,326,087,168 bytes free

C:\Users\User\Downloads>fastboot reboot bootloader

< waiting for any device >

^C

C:\Users\User\Downloads>
[Android Q&A, Help & Troubleshooting] alecxs:
you are mixing up fastboot with adb commands. the only useful adb command is adb reboot bootloader which reboots device in fastboot mode (alternative method to enter fastboot mode from Volume Down + Power)
[Android Q&A, Help & Troubleshooting] gardina:
adb reboot bootloader, on my oppo, just restarts it and makes it show the normal screen as if I'd just restarted my phone normally. (So the command doesn't work properly on my Oppo phone!), it's not going to the bootloader. (I know that for example on other phones you'd get a picture of an android robot, indicating IIRC that it's in the bootloader).

having my Oppo phone off and doing vol down and power up, boots up to a low level menu where I can choose "English" then it says "Color OS Recovery". (So maybe not the bootloader maybe a stock recovery)

You suggested fastboot boot boot.img but it just says "waiting for any device". I don't know if that indicates I should try the other file you mentioned?
[Android Q&A, Help & Troubleshooting] alecxs:
if fastboot devices say "waiting for any device" that mean device is not in fastboot mode. you posted that instructions. if fastboot not working, how did you unlock bootloader then? it's impossible without fastboot
[Android Q&A, Help & Troubleshooting] gardina:
That's a good point.. I did write post #25 after the fact , from memory, and after the cmd prompt I did it from was closed.. so I can't check exactly what commands I used... Now i'm in doubt if indeed the phone is unlocked.. I can't verify if I did indeed get the fastboot command to work..

without being able to get the fastboot command working, Is there a way I can check if it is unlocked?

I just tried doing power and vol down and a menu comes up offering "English", maybe a stock recovery, and fastboot isn't working for me from there either.

I guess fastboot is meant to only work from the "boot loader", and, I don't know what the situation was before, but now, I can't seem to get to the boot loader on the oppo.
[Android Q&A, Help & Troubleshooting] alecxs:
unlocking bootloader will cause factory reset, so if your device did not lose all data indeed your bootloader is not unlocked, yet.

for fastboot mode

try

Volume Down + Home + Power

or

Volume Down + Camera + Power

or try to downgrade ColorOS 6.0.1 from MSM Download Tool and use this Magictricks.zip from recovery

https://gearallnews.com/how-to-unlock-the-bootloader-of-oppo-a5guide

EDIT: never mind, it's for Oppo F1 only. hate these untested guides posting stuff that can't work at all :(
[Android Q&A, Help & Troubleshooting] gardina:
I mentioned that adb reboot bootloader (or same thing, adb reboot-bootloader), then it restarts into the normal system.. Another detail is that after doing that command, then the screen goes black as it restarts, then in a flash it says "fastboot" for a moment, then it goes to the OPPO logo and just starts the normal system, restarting normally.

So it looks like any kind of fastboot mode has been overridden.

I also heard of an unlock tool.. https://firmwarecare.com/oppo-free-unlock-v1-0 but wary that it might be malware I set up a fresh windows 7 on a comp I have.. it seems legit, I didn't scan it before running it(cos i'm wary that maybe virus scanners might give false positives and I don't want the false FUD), but anyhow, as you see from the screenshot it didn't work

virustotal lists it as bad..

VirusTotal

VirusTotal

www.virustotal.com

though virustotal could give false positives https://support.virustotal.com/hc/e...imate-software-I-have-developed-what-can-I-do

Also, I tweeted @OPPOCareGlobal asking them if they stop /block users from unlocking their bootloader. And I said adb reboot boot-loader isn't working.

They asked why I want to do that. I said I want to do a byte by byte backup.

They blabbered about how they don't encourage users to do the setting. And " we do not allow such service in OPPO devices. "

So I said i'm not asking about their policy, and i'm asking do they actually stop/block users from doing so?

They said " Regarding your inquiry, the ColorOS system simply do not allow this service as it would cause unknown malfunctions. "

I contacted their support email address and they said

"We are sorry to hear about the issue you are experiencing, we understand the issue, but unfortunately at the moment OPPO has their own recover that is overloading the default bootloader. Unfortunately, OPPO does not allow rooting or access to the bootloader as it will void the warranty.

There is however a developer program to submit their candidature, but it is only available for Chinese residents. We are sorry for the inconvenience once again, but there is not much we can do regarding this at the moment. "

I have noticed that there is a negative review about this on the amazon link for the device, and quite frankly there should be more. It's one thing for a company to void warranty over doing it, it's quite another for them to actively block/stop the user from doing it.

I have noticed on the coloros site it mentions something about "deeptest" about unlocking oppo phones https://community.coloros.com/thread-50668-1-1.html
[Android Q&A, Help & Troubleshooting] alecxs:
no big surpise ... same as iPhone, Huawei, and also Samsung stopped unlocking recently
[Android Q&A, Help & Troubleshooting] Vijay sharma3321:
How to read my oppo a9 2020
[Android Q&A, Help & Troubleshooting] Vijay sharma3321:
How to root my

oppo a9

2020
[Android Q&A, Help & Troubleshooting] Morphine1:
Thanks for the detailed info, that really sucks from OPPO.

I need to repair the imei from an OPPO A9 2020 CPH1941. I need qualcomm diagnostic mode, and to enable such mode I need to root it first, which it seems to be impossible. No fastboot mode (phone reboots as mentioned above) only got qualcom com port edl mode via Adb reboot edl.

Another issue from the same device that my aunt owns is she forgot the password and if I want to wipe data via recovery it asks password over n over, and the phone can't boot, so I cannot flash the firmware and I cannot boot into edl mode to deep flash the full stock rom.

It seems both phones are going to be stuck forever without a damn fix just because of OPPO not letting us android tech users fix them.
[Android Q&A, Help & Troubleshooting] sahelkhan022:
i'm late but i have full solution for Oppo A9 2020
[Android Q&A, Help & Troubleshooting] eathtespagheti:
Can you elaborate?
[Android Q&A, Help & Troubleshooting] llxxVENOMxxll:
Pls post the solution.
[Android Q&A, Help & Troubleshooting] monfrix:
any updates? sahelkhan022 said they found a solution, that was back in august
[Android Q&A, Help & Troubleshooting] Jerzey84:
Lol he is breaking his device by unlocking bootloader tutorial on some useless blog and got his phone broken and he found a solution that is sell his phone
[Android Q&A, Help & Troubleshooting] Tawshiq:
Does this Device root? I'm want to install a custom rom pronto.
[Android Q&A, Help & Troubleshooting] JJAJJA:
Oppo impossible to root?
[Android Q&A, Help & Troubleshooting] unst4bl3:
Possible! you have to edit boot image with hex editor to allow fastboot work/stay instead of rebooting. After editing flash official firmware with edited bl through SP Tool! Voila! u done!

Now just type cmd: adb reboot bootloader

fastboot oem unlock

& enjoy flashing stuffz!
[Android Q&A, Help & Troubleshooting] kingsemperor:
Hello killerboychetan ! What are the changes to be made to this boot.img file ? I got mine from this file :

Oppo_A9_2020_CPH1941_EX_11_A.16_191019

That is the version I downloaded from the internet. There is another one which is cph1937 but my Oppo A9 2020 model is CPH1941 (Global)

The following is the screenshot from my boot.img file:
[Android Q&A, Help & Troubleshooting] alecxs:
nothing. you are mixing up boot with devinfo partition
[Android Q&A, Help & Troubleshooting] unst4bl3:
Ya, i attached wrong ss overthere at that time.
[Android Q&A, Help & Troubleshooting] unst4bl3:
Instead of this try hydra tool 🔧

I had heard it worked for some people.
[Android Q&A, Help & Troubleshooting] unst4bl3:
Or try this guide... this guy unlocked bootloader for oppo a37f(which also has fastboot disabled by Oppo)

And it worked for me. Maybe if you try something similar maybe that can work for your device.
[Android Q&A, Help & Troubleshooting] Warriordarkus:
Is there any way to root this phone? Got a new Xiaomi and would love to root the OPPO A9 2020.

Wont ever get any OPPO again, the fastboot lock is a mesh.
[Android Q&A, Help & Troubleshooting] shiciro:
will someone do this, it will be very appreciated. im really desperate to get root on this phone.
[Android Q&A, Help & Troubleshooting] unst4bl3:
But no one will... if some had then there must be a guide till now... yk it's a long time since this phone launched...

Basically, what am saying is that you only have to find a way to root it.. nobody's gonna come...
[Android Q&A, Help & Troubleshooting] Kw4tro20:
up
[Nokia 7.2 ROMs, Kernels, Recoveries, & Other Devel] sayaoks:
NFT 2.0.7 & 1.2.3- Nokia Flash Tool to flash stock ROM

This tool can make you easier to install stock roms

This program is made for Windows, with .NET Framework 4.5.1 This is VB.net program

v.1.1.0

What the tool can do:

- Flash phone - the tool supports the following phones out of the box: Nokia 8.1, Nokia 9 PureView, Nokia 7.2, all Nokia phones on the SDM_660 family, And other Nokia Phones

- Requires the bootloader to be unlocked.

- Support for more phone models can be easily added by adding a new profile and defining the partitions to flash and matching it to file names to be flashed.

- Able to create custom flash process

- Able to import profile (partition and flash data) from a txt file (check sample format)

- Can dump your current partitions to create a flashable file for recovery (this function needs root access)

- Switch slot on A/B devices which support slot change

Thanks to:

- Hikari Calyx (hikaricalyx.com)

- Narender Singh (TechMesto.com)

System requirements:

- Windows 7, 8, 8.1,10 or higher, 32bit or 64bit

- .NET Framework 4.5.1

- USB Data Cable

- Phone

Downloads:

NFT v.1.2.4 (Stable)

NFT v.2.0.8 ( Stable )

NFT v.2.0.9 ( Stable ) - new 08 Dec 2020

NFT v.2.1.0 ( Stable ) - new 11 nov 2021

Firmware :

Firmware 7.2 (1_390)

Firmware 6.2 (1_160)

*Work with Payload

- install python 3

- make sure user Environment variables link to Python folder and Python folder\script

Bugs:

v.1.1.1

-nokia 9 profile & dump (fix on 1..1.2)

v.1.1.2

- language failed to saved on second times ( fix on 1.1.3)

- some word failed to translate to CN ( fix on 1.1.3)

v1.1.3

- abl skip not work after add language (fix on 1.1.3a)

v1.1.3a

-none

v1.1.4

- on some case Nokia 8.1 switch to A slot After flash (fix on 1.1.5)

v.1.1.5

- dump on nokia 7.2, 6.2 because new naming process (fix on 1.1.6 )

v.2.0.7

- ota flash not work (fix on 2.0.8 )
[Nokia 7.2 ROMs, Kernels, Recoveries, & Other Devel] sayaoks:
Update & change Logs

NFT v1.1.0

- New design

- Add support phone

- Add auto-detect mode

- Add some feature on profile management

NFT v.1.1.1

- Fix detect Device for MTK & A-only Device

- Fix dump for nokia 8.1

- add dump profile for nokia 8 & Sirocco

NFT v1.1.2

- FIx Nokia 9 profile and dump

- now dump partition Work on FTM mode And Normal mode

- Add Language Setting : Simplified Chinese & English...

NFT v1.1.3

- fix save language in setting

- Fix some translate in CN language

- Add warning when flash Payload.bin

- Now NFT only process payload.bin with size more than 1Gb

(make sure use full system update payload.bin..)

NFT v1.1.3a

-fix minor bugs

NFT v1.1.4

- support more python name (for multiple python installed) default : python3, python, py . can add more

- add install protobuf on script

- add check slot on dump

- add custom dump setting..

- to change saved filename partition double click file name

*for best restore dump please use default file name for splash partition

NFT v1.1.5

- Fix auto-switch to slot A, after Flashing Nokia 8.1

- add Russian Language

- add Indonesia Language

- dump files Now naming Base installed Rom.

27 Des.

- fix auto-detect for new devices (7.2 ,6.2 , etc)

29 Des

- add Donate link... for donate

- add logs

v1.1.6

- fix dump problem on nokia 6.2, nokia 7.2

- new menu - Create homebrew from OTA FILES (extracted)

3 januari 2020

- fix name file Homebrew ( Minor)

- add error handle homebrew Clean temp files

- update Logs

27 januari 2020

- fix naming dump for some devices... when dump inactive slot

-fix minor bugs

V2.0.0

- New UI

- Restore Partition from ADB

28 januari 2020

V2.0.1

- Fix restore partition From ADB

- Tweak Side menu animation(Faster)

- now support flash partition structure (for convert CN - Global)

V.1.1.7

- now support flash partition structure (for convert CN - Global)

v2.0.2 & v1.1.8

- fix 4.2 & 3.2 Support

- note for nokia 4.2 & 3.2: Before do anything on flash form set profile to nokia 4.2 and nokia 3.2

v2.0.3 & v1.1.9

- fix minor bug for nokia 9

- fix nokia 7.2/6.2 didn't boot after flash ( Vbmeta problem)

v2.0.4 & v1.2.0

- NOw Support .zip file ( Ota File & Cutom rom )

- fix English translate

v2.0.5 & v1.2.1

- NOw Support .zip file ( Ota File & Cutom rom )

- fix English translate

- add separate setting For vbmeta flash script ( because -disabled-verify on some device will cause failed to update ota )

v2.0.8 & v1.2.4

- add support raghu vagma Homebrew Firmware

v2.0.9

- remove unused messagebox

* note for nokia 4.2 & 3.2: Before do anything on flash form set profile to nokia 4.2 and nokia 3.2
[Nokia 7.2 ROMs, Kernels, Recoveries, & Other Devel] sayaoks:
Reserved

How to :

* Flash phone

- Open NFT

- Choose Flash Normal

- Select Folder which Contain Firmware File

- Select Profile ( U can create Your Own profile In manage button)

- Flash

* Flash phone With Payload.bin

- Extract Full Ota FIle .zip

- Open NFT

- Choose Payload.bin File

- Choose Slot

- FLash

* Create Dump Partition Profie

- Open NFT

- Select Tools

- Select Dump partition

- Select manage

- Connected Phone with USB Debuging SET ON With Root Permision Granted

- Add New

- Select Which Partition Do you Want to backup

- Naming Profile

- Save

* Dump Partition

- Open NFT

- select Tools

- Select Dump Partition

- Connected Phone with USB Debuging SET ON With Root Permision Granted

- Select Profile

- Select Slot

- Dump Partition

* Homebrew From FULL OTA FIle

- Extract Full Ota FIle .zip

- Open NFT

- select Tools

- Select Make HomeBrew From Full OTA FILES

- Select Payload.bin File

- Choose Folder To save Homebrew

- Make Homebrew

* HomeBrew Security update

- Root Phone

- Follow instruction How to update phone on Magisk forum

- after update don't restart and don't Pacth boot.img to other slot

- Open NFT - Tools -Dump Partition

- Select Profile Homebrew For your Device

- Set inactive Slot on Slot option (if active Slot 'a' then choose 'b' , if active Slot 'b' then choose 'a')

- dump partition
[Nokia 7.2 ROMs, Kernels, Recoveries, & Other Devel] singhnsk:
Thank you ? Now I can mod my Nokia 7.2 without worrying too much.
[Nokia 7.2 ROMs, Kernels, Recoveries, & Other Devel] hikari_calyx:
Nice work!
[Nokia 7.2 ROMs, Kernels, Recoveries, & Other Devel] pattiandy:
anyone have valid link to stock firmware? thank you in advance
[Nokia 7.2 ROMs, Kernels, Recoveries, & Other Devel] sayaoks:
Click hikari calyx name in NFT to download firmware
[Nokia 7.2 ROMs, Kernels, Recoveries, & Other Devel] lilmonkw:
I tried flashing OTA using payload mode. After the operation was finished, my devise's screen turned black and now it does not turn on anymore. Is there anything I can do to fix it?

so it's some sort of 9008 mode I guess. and I couldn't find any nb0 firmware. I am absolutely clueless about what to do now.
[Nokia 7.2 ROMs, Kernels, Recoveries, & Other Devel] sayaoks:
i put information in about button

for payload mode...it only for full rom OTA.. size about 1,5GB or more..

let me know what payload u use..

and what devices???

firmware download click on hikari name on NFT tools...

for 7.2 u need extract every zip in firmware and put it in one folder..

Flash using normal flash