Database Info

OTA update for F1f

A new official ColorOS udpate from OPPO is available in my region and at least all Europe I guess.
This is version F1fEX_11_170327. A copy of the OTA update package is here if anyone needs it: F1EX_11_OTA_896-897_patch_201703271119_3cf702307f.zip on MEGA (56.0 MB).
A few screenshots if you want to see the changelog: http://imgur.com/a/5UiiQ
Before:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After, full about phone capture: http://imgur.com/CIbWrWX
This is still Android 5.1.1 with a 3.10.28 kernel. No Marshmallow
I'm a bit amazed by the continuous support from OPPO, and especially the security patches integrated in those updates. I was not expecting this from this brand. This is part of what's preventing me from completely switching to LineageOS. This is my only smartphone and I need it to just work.

Now I wish I can unroot my phone, lol

You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.

kdd998 said:
You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.
Click to expand...
Click to collapse
Thank you!
But where can I get stock recovery?

You can extract recovery.img from the ColorOS zip.

If someone were to flash this via twrp. When they have followed this thread
https://forum.xda-developers.com/op...pdates-rooted-unlocked-devices-t3395034/page8
They would loose twrp and lose he unlocked bootloader correct?

This zip is only for OPPO*recovery, not for TWRP. It needs to be modified. If modified, I don't think recovery or unlocked state would change as recovery is not included in the original zip.

kdd998 said:
This zip is only for OPPO*recovery, not for TWRP. It needs to be modified. If modified, I don't think recovery or unlocked state would change as recovery is not included in the original zip.
Click to expand...
Click to collapse
The update zip does contain and flash the locked bootloader(emmc_appsboot.mbn) and also the update zips never contain a recovery.img but do have a script(install_recovery.sh) and patches that patch the latest recovery onto latest boot.img and flash it to recovery. So, yes, flashing it will lock everything down. Modifying it to remove bootloader and recovery is easy enough( I'm happy to do it) but it will also check the current build version on the phone before flashing and refuse to flash unless the rom has been updated to the "896" level, which I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now). There is a new download of full rom available for the 896 version which could also be modified to install from twrp without bootloader and recovery but it does require a full wipe. If enough people want it, I guess it would be good to have a more up to date full clean install of colouros.
Do you think it's worth the effort?

MiniBlu said:
The update zip does contain and flash the locked bootloader(emmc_appsboot.mbn) and also the update zips never contain a recovery.img but do have a script(install_recovery.sh) and patches that patch the latest recovery onto latest boot.img and flash it to recovery. So, yes, flashing it will lock everything down. Modifying it to remove bootloader and recovery is easy enough( I'm happy to do it) but it will also check the current build version on the phone before flashing and refuse to flash unless the rom has been updated to the "896" level, which I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now). There is a new download of full rom available for the 896 version which could also be modified to install from twrp without bootloader and recovery but it does require a full wipe. If enough people want it, I guess it would be good to have a more up to date full clean install of colouros.
Do you think it's worth the effort?
Click to expand...
Click to collapse
It would be nice if we ever go back to color os. But don't rush it. Take your time. Its not a big rush. But I would rather the time be spent in lineage first. Up to you

MiniBlu said:
I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now).
Click to expand...
Click to collapse
I have a 010 to 896 patch here if needed: https://mega.nz/#!hxxDxAwb!nLa3aDvz3GubMcTaxqaLowRujDt6UKcn0DohuhkclXY
Thanks for all the info. From my point of view, I don't think it's worth the effort. I'd rather work on LineageOS (maybe I'll have time on monday to try new things)

Deleted

kdd998 said:
You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.
Click to expand...
Click to collapse
what if i still have my stock recovery? can i just flash spectrum os then flash color os to unroot my device? coz i rooted my device also using kingroot. i cant update ota.

wakaranay said:
what if i still have my stock recovery? can i just flash spectrum os then flash color os to unroot my device? coz i rooted my device also using kingroot. i cant update ota.
Click to expand...
Click to collapse
https://www.google.com.au/amp/m.wikihow.com/Unroot-Android?amp=1
That would be the hardest way in my opinion. Try these first.
I would use the supersu app first and if that doesn't work then use the manual delete

Jamie_oppo said:
https://www.google.com.au/amp/m.wikihow.com/Unroot-Android?amp=1
That would be the hardest way in my opinion. Try these first.
I would use the supersu app first and if that doesn't work then use the manual delete
Click to expand...
Click to collapse
both not working. i cant still update tru ota

wakaranay said:
both not working. i cant still update tru ota
Click to expand...
Click to collapse
Have you unlocked your bootloader?

Jamie_oppo said:
Have you unlocked your bootloader?
Click to expand...
Click to collapse
locked bootloader

wakaranay said:
locked bootloader
Click to expand...
Click to collapse
I guess flashing spectrum then color os should work. Not 100% but if you get to spectrum then it will work

Jamie_oppo said:
I guess flashing spectrum then color os should work. Not 100% but if you get to spectrum then it will work
Click to expand...
Click to collapse
thanks. i guess firmware flashing will also work. but i dont know what firmware or when i can get that firmware

wakaranay said:
thanks. i guess firmware flashing will also work. but i dont know what firmware or when i can get that firmware
Click to expand...
Click to collapse
Read post 3 of this thread. Miniblu made a firemware zip. Oops sorry didn't include a link
https://forum.xda-developers.com/oppo-f1/development/rom-unofficial-cyanogenmod-13-t3542718/page23

How to re install the original recovery :crying:

[TOOL][OP7] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)

This is the OnePlus 7's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
​

Is TWRP out for the OP7 yet? Or is this AIO tool basically still a work in progress (not all functions operational yet)?
I don't see the OnePlus 7 posted on TWRP's official website. Or on xda for that matter. I can find a couple dodgy "how to root" guides for the OP7, but they just look like clickbait. One just links to the TWRP main page (instead of an actual file download specific to the OP7). Another actually contains links for the OP6! Not just deceptive, but can possibly cause folks problems!

redpoint73 said:
Is TWRP out for the OP7 yet? Or is this AIO tool basically still a work in progress (not all functions operational yet)?
I don't see the OnePlus 7 posted on TWRP's official website. Or on xda for that matter. I can find a couple dodgy "how to root" guides for the OP7, but they just look like clickbait. One just links to the TWRP main page (instead of an actual file download specific to the OP7). Another actually contains links for the OP6! Not just deceptive, but can possibly cause folks problems!
Click to expand...
Click to collapse
Hi, this tool has all function ready for op7 and op7 pro ( i'm only waiting for the branded unlock bootloader procedure). Actually for what i know there is not a twrp available, but in all cases the tool allow you to flash a third part twrp.img and not only the twrps in the list (I can update the twrp list without updating the tool, so when a new working twrp will be released i will add it in the twrp list). The other functions, like reboots, bootloader unlock,or apk installer/uninstaller are perfectly working because they are a bit generic. For the root is the same problem, the tool use the twrp to root the device so without it you can't root the device with the tool. This tool is available for all others OnePlus devices and i'm official TWRP maintainer for Op6 and Op6T, so when a stock rom will be released i will start also to work on the TWRP and the others features.

anyone got the stock recovery for the Oneplus 7?

Thanks for the good work. However, the tool fails for me. I have an unlocked bootloader.
Version: 1.1.1.6
1. MD5 check error after TWRP download
2. Skip MD5 check throws "unable to open zip file" error
3. Deleted all files and tried again - still the same.

hohinder said:
Thanks for the good work. However, the tool fails for me. I have an unlocked bootloader.
Version: 1.1.1.6
1. MD5 check error after TWRP download
2. Skip MD5 check throws "unable to open zip file" error
3. Deleted all files and tried again - still the same.
Click to expand...
Click to collapse
Thanks, give me a second i will check soon

mauronofrio said:
Thanks, give me a second i will check soon
Click to expand...
Click to collapse
after unlocking bootloader google play shows device not certified..

prachetas13 said:
after unlocking bootloader google play shows device not certified..
Click to expand...
Click to collapse
It's normal
hohinder said:
Thanks for the good work. However, the tool fails for me. I have an unlocked bootloader.
Version: 1.1.1.6
1. MD5 check error after TWRP download
2. Skip MD5 check throws "unable to open zip file" error
3. Deleted all files and tried again - still the same.
Click to expand...
Click to collapse
Should be fixed now

mauronofrio said:
It's normal
Because if it netflix does not start.and its tripping safetynet.
will unlock again when magisk support is available.
Click to expand...
Click to collapse

I want to switch to Oxygen OS from hydrogen OS.
How can I switch from hydrogen OS to Oxygen OS using this tool, please?

prachetas13 said:
after unlocking bootloader google play shows device not certified..
Click to expand...
Click to collapse
Magical hide the play store if it bothers you

Hello Dear Creator
I would like to say thanks to you
I have sucessful rooted my Oneplus 7 indian variant (1901) with your latest unofficial twrp img, installer and magisk
Its was too easy to root it

please help me... how unbreak OP7 GM1900??

IlyaSBD said:
please help me... how unbreak OP7 GM1900??
Click to expand...
Click to collapse
You are in an aosp recovery, what do you.need?

mauronofrio said:
You are in an aosp recovery, what do you.need?
Click to expand...
Click to collapse
I can't clean date or reinstall the firmware. when you turn on the phone hangs the Android logo.

IlyaSBD said:
I can't clean date or reinstall the firmware. when you turn on the phone hangs the Android logo.
Click to expand...
Click to collapse
Go in fastboot mode and flash again the twrp

mauronofrio said:
Go in fastboot mode and flash again the twrp
Click to expand...
Click to collapse
Failed / (remote : Flashing is not allowed in Lock State)
Bootloader is locked. And unlocking is blocked...

IlyaSBD said:
Failed / (remote : Flashing is not allowed in Lock State)
Bootloader is locked. And unlocking is blocked...
Click to expand...
Click to collapse
So you should.use the msmtool

mauronofrio said:
So you should.use the msmtool
Click to expand...
Click to collapse
But where can I find MSM for GM1900 ?

IlyaSBD said:
But where can I find MSM for GM1900 ?
Click to expand...
Click to collapse
You should ask to oneplus or you can try to use the msmtool for gm1913 or gm1917.
Your is the chinese version, so you should search for hydrogeng os msmtool

[Guide] How to install security updates on rooted Nokia 8

Process to install security updates on rooted Nokia 8
Download the Nokia 8 OTA zip files on your Computer from this link in the OTA folder https://bit.ly/nokia-nb1 (it's usually up to date)
Download the Nokia 8 latest FULL ROM OTA zip file on your Computer from this link in the OTA folder https://bit.ly/nokia-nb1 (usually with size above 1 GB, currently it is: NB1-5150-0-00WW-B03-update.zip 1.52 GB)
Connect the phone to the PC using the USB cable and enable USB debugging (after enabling developer options)
Verify connection and drivers are correct on your computer by using the following ADB/Fastboot command(minimal adb fastboot can be found here https://forum.xda-developers.com/showthread.php?t=2317790):
adb devices
Click to expand...
Click to collapse
If you see your device and ID then all good so far
Use the following adb command on your Computer
adb reboot bootloader
Click to expand...
Click to collapse
Alternative to the previous step, you can select ADB sideload from the stock recovery menu after booting into stock.
when the device reboots into bootloader / or ADB sideload is selected from recovery use this command on your computer:
adb sideload path_to_zip/FULL_ROM_OTA.zip
Click to expand...
Click to collapse
Once loaded, reboot using the command
adb reboot
Click to expand...
Click to collapse
Sideload the OTA updates you have downloaded in step 1 using the same process as before OR Update normally through android system settings. Keep updating and restarting until you have the latest update
Download the latest Nokia 8 Stock boot image file on your phone from this link in the STOCK BOOT folder https://bit.ly/nokia-nb1 (it's usually up to date)
Make sure you have the correct Stock boot image file for the the software version you have. (if you have May update, use May image, June update then use June Image, etc....)
Use magisk manager to root the boot image you just downloaded. Use the second option like in the photo below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Transfer the patched image file to your computer
Get back to bootloader (download mode) using any method or the below code (USB debugging on)
adb reboot bootloader
Click to expand...
Click to collapse
When in download mode, use the following command on your computer and take note of the result (in case something goes wrong)
fastboot getvar current-slot
Click to expand...
Click to collapse
Use the following command:
fastboot flash boot path_to_zip/patched_boot.img
Click to expand...
Click to collapse
Reboot
Enjoy
Wait one more month
Repeat
Tested scenarios:
Working on TA-1012 to get the Pie May 2019 update from April update
Working on TA-1012 to get the June 2019 update from May update
Working on TA-1012 to get back to latest rom (NB1-5150-0-00WW-B03-update) from April update
Working on TA-1012 to get back to latest rom (NB1-5150-0-00WW-B03-update) from May update
Working on TA-1012 to get back to latest rom (NB1-5150-0-00WW-B03-update) from June update
Screenshot, showing update using system settings to May update, after sideloading full ROM (NB1-5150-0-00WW-B03-update) from a rooted device on May update, proving downgrading works fine.

June files have been updated to the link: https://bit.ly/nokia-nb1
Thanks to Dorian Stoll

Well I got nowhere. The moment I reboot into bootloader, the device isn't visible in adb anymore, but only under "fastboot devices", so "adb sideload path-" fails because it can't find the device. What gives?

VonZigmas said:
Well I got nowhere. The moment I reboot into bootloader, the device isn't visible in adb anymore, but only under "fastboot devices", so "adb sideload path-" fails because it can't find the device. What gives?
Click to expand...
Click to collapse
Boot into recovery and select "apply update from adb" as shown in the photo below (not mine)

Kiwironic said:
Boot into recovery and select "apply update from adb" as shown in the photo below (not mine)
Click to expand...
Click to collapse
I'm still on TWRP at this stage. I can't get past step 7.

Hi guys,
is it necessary to sideload OTA updates? Can I just update the system in settings and then flash a rooted boot image corresponding to the update version?

VonZigmas said:
I'm still on TWRP at this stage. I can't get past step 7.
Click to expand...
Click to collapse
This is for people like me who are not able to run twrp on their phones. If you have twrp you should be able to flash the zip file easy. This guide assumes you have stock recovery

Update: confirmed working for July update as well.

I'm sorry if this seems dumb, but I'm kinda new to all of this. I have TWRP and now I want the July patch, how can I do it?
Update: I gave up and flashed stock recovery.

helscarthe said:
I'm sorry if this seems dumb, but I'm kinda new to all of this. I have TWRP and now I want the July patch, how can I do it?
Update: I gave up and flashed stock recovery.
Click to expand...
Click to collapse
In twrp it should be straight forward to flash a zip file which includes the update. Another option or if this fails, start sideload from twrp like in the following photos

Hi, links no longer working. Does anyone have working links for V5.15D ? I need stock boot image and OTA update to sideload. Thanks.

Unfortunately the phone has been abandoned by the developers. I have got myself a xiaomi 9t.
I'm sorry

Kiwironic said:
Unfortunately the phone has been abandoned by the developers. I have got myself a xiaomi 9t.
I'm sorry
Click to expand...
Click to collapse
It's ok thanks for your work on it!

Kiwironic said:
Unfortunately the phone has been abandoned by the developers. I have got myself a xiaomi 9t.
I'm sorry
Click to expand...
Click to collapse
Oh man, can you still get stock images or whatnot anywhere? I only need the least that will get me back to stock before I turn it in for warranty but not sure where to start.

Sorry man I relied on the other developer's repository so much that I can't offer any tools nor files. I can help you get to stock easy. As Nokia offers the original Rom on their website officially. I believe it can be found here
https://www.nokia.com/phones/en_int/betalabs
Register for beta labs then de register and download the latest firmware they offer you

Kiwironic said:
Sorry man I relied on the other developer's repository so much that I can't offer any tools nor files. I can help you get to stock easy. As Nokia offers the original Rom on their website officially. I believe it can be found here
https://www.nokia.com/phones/en_int/betalabs
Register for beta labs then de register and download the latest firmware they offer you
Click to expand...
Click to collapse
Hey, sorry for the late reply. I attempted to get back to stock via NOST and the 5150 image he provided https://forum.xda-developers.com/no...re-nokia-to-stock-t3867646/page3#post80627823 , but turns out I don't have critical unlocked and seem to have misplaced the unlock key. What can I do next?

VonZigmas said:
Hey, sorry for the late reply. I attempted to get back to stock via NOST and the 5150 image he provided https://forum.xda-developers.com/no...re-nokia-to-stock-t3867646/page3#post80627823 , but turns out I don't have critical unlocked and seem to have misplaced the unlock key. What can I do next?
Click to expand...
Click to collapse
Try unlocking again using the Nokia unlock Web page

Kiwironic said:
Try unlocking again using the Nokia unlock Web page
Click to expand...
Click to collapse
The web page requires a validation code that you get from the unlock app from your phone and as we know the app gives a nice "Device not support" if you try running it on Pie. Tested myself just in case.

Kiwironic said:
Try unlocking again using the Nokia unlock Web page
Click to expand...
Click to collapse
In the end I've decided to just go for it and see what happens. Shouldn't make things worse. Flashed the stock boot image for my security patch right on top of TWRP. The phone booted, but I still couldn't install updates. Tried flashing the next update (May) from both ADB and the SD card - failed with the same download state initialization error. Figured I may as well try the same but with the full .zip of my current OS version (April) and while it took pretty long, it finished with no issues and OTA's started rolling in without a hiccup. Surprisingly I didn't even lose any of my data in the process, which I was preparing for. I guess all that's left is to lock the bootloader?
Anyway thanks for the help!

[RECOVERY][OFFICIAL] TWRP for Galaxy A40 [A405FN]

Team Win Recovery Project 3.6.1​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Special Notes:
DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options)
KNOX will be tripped once you flash custom binaries to your phone. Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status
Samsung Firmware OTA (aka System Updates) will no longer work once you flash custom binaries. You can flash custom ROMs if you want to keep the OS up-to-date
All apps that use KNOX like Samsung Pay, Secure Folder and maybe more will no longer work
Download:
Recovery
VBMeta
Multidisabler
Changelog:
21.10.2021
Rebased kernel source to CUH4
16.06.2021
Rebased kernel source to CUC2
03.05.2020
Rebased kernel source to BTB8
25.04.2020
Rebased kernel source to ATA4
07.12.2019
Initial Release
Guide:
If you already have a custom recovery installed:
Boot to your custom recovery
Flash the recovery image
If you are starting from scratch:
Go to Developer Settings and enable "OEM Unlock" option
Power off the device and boot in download mode
In download mode, you will see the long press and volume up option to unlock the bootloader
Unlock the bootloader. That will wipe your device so be sure you made a backup of your data
After bootloader unlock, boot up the phone and make sure it is connected to the internet or it will trigger rmm prenormal
Setup the phone without google account and others
Reboot in download mode and flash the recovery and vbmeta images
Boot to TWRP
Format data in TWRP
Flash the Multidisabler zip
Now you can reboot
Contributors
ponces, geiti94, ianmacd
Source Code: https://github.com/TeamWin/android_device_samsung_a40
Kernel Source Code: https://github.com/ponces/android_kernel_samsung_universal7904

Reserved

I'm really tempted to flash this TWRP and root my A40. Though I know Android 10 has been announced (at least in my region) for April 2020. Should I wait until then? My main concern is, if i flash it now, how easy will it be to upgrade to Android 10 then?
The only real thing I use root privileges for is to remove bloatware completely and edit the hosts file, so I can wait a few months. Also what about dm-verity? Are there any problems there?

My question and can I use this recovery on ITV-A405FNXXU2ASK2-20191218161204?

bishsop said:
I'm really tempted to flash this TWRP and root my A40. Though I know Android 10 has been announced (at least in my region) for April 2020. Should I wait until then? My main concern is, if i flash it now, how easy will it be to upgrade to Android 10 then?
The only real thing I use root privileges for is to remove bloatware completely and edit the hosts file, so I can wait a few months. Also what about dm-verity? Are there any problems there?
Click to expand...
Click to collapse
The choice of waiting is only yours.
In my case I need this as I'm using a custom Treble ROM and not Samsung's firmware.
The ease to upgrade to Android 10 relies only on the your expertise on how to flash the original firmware using ODIN.
At the time of the upgrade you need to use ODIN to flash an original firmware from Android 9 to be able to fully restore the original behavior and flash Android 10.
As far as I'm concerned, DM-Verity is related with both DT and DTBO partitions and those partitions are not even touched during this process.
The ones that are changed are BOOT, RECOVERY and VBMETA to disable a few security procedures from Samsung to be able to flash and boot custom binaries.
Because of this, take in consideration the "Special Notes" section in the first post.
Nevertheless, if the need of changing the hosts file is to block ads, you can reach the same goal by using the "Private DNS" feature introduced in Android 9 as explained here.

costa11 said:
My question and can I use this recovery on ITV-A405FNXXU2ASK2-20191218161204?
Click to expand...
Click to collapse
As you can see in the first post, this TWRP version is for the firmware A405FNXXU2ASJ1 (October's update).
I am still waiting for Samsung to drop A405FNXXU2ASK2 (December's update) sources here to update TWRP.
I'll keep you posted when the sources drop and work on TWRP update begins.

ponces said:
As you can see in the first post, this TWRP version is for the firmware A405FNXXU2ASJ1 (October's update).
I am still waiting for Samsung to drop A405FNXXU2ASK2 (December's update) sources here to update TWRP.
I'll keep you posted when the sources drop and work on TWRP update begins.
Click to expand...
Click to collapse
So I tried to install this recovery on the ASK2 firmware and it worked, there is only one problem when it goes down the brightness does not return anymore remains low! Then another thing I rooted with Magisk is it's not working, come up with an error and then I'll try to take a screenshot!

thank you again for your job
i just updated my rom to the SK2 (downloaded the rom, flashed it with Odin)
then installed you twrp (the SJ1 is OK)
then flashed with magisk manager the boot.img to Root the Rom
and then flashed the param.bin with a better boot logo
thank you so much for your job !!

costa11 said:
Then another thing I rooted with Magisk is it's not working, come up with an error and then I'll try to take a screenshot!
Click to expand...
Click to collapse
Magisk-Root is working for me.
I did this:
[*]Backup of ASJ1 with TWRP
[*]Complete odin flash of ASK1
[*]TWRP - ASJ1 - Version
[*]direct reboot into TWRP
[*]Format Data
[*]Flash Multidisabler
[*]Full Boot
[*]Install Magisk.APK from sd-card
[*]Reboot into TWRP
[*]Flash Magisk
[*]Full boot to check of root access => ok
[*]Reboot into TWRP
[*]Restore of ASJ1-Data​
​
Everything working!

Thanks for the recovery, is working fine with latest ITV (Italian no brand) firmware, to have root is only simple necessary to flash latest Magisk ZIP via twrp (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)

i have a big problem about twrp on my phone
I have followed this thread
But when i flash twrp (i have uncheck "reboot" on odin of course) i can't get access to the recovery mode, when i do power button + volume up it doesn't do nothing and show this :
(I have already unlock my boot loader)
I think its DM VERITY who block the access to recovery mode but i can't disable this, cause i can't get access to twrp :/
Thanks for any answers c:

cioce said:
Thanks for the recovery, is working fine with latest ITV (Italian no brand) firmware, to have root is only simple necessary to flash latest Magisk ZIP via twrp (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
Click to expand...
Click to collapse
Can confirm it works with ATA4 (region DBT). Same procedure my post above. With restoring Data as last step there isn't anything lost as well... :good:
Be sure to enable usb debugging after flash of new firmware. Otherwise TWRP flash would fail...
:good:

Leak.dll said:
i have a big problem about twrp on my phone
I have followed this thread
But when i flash twrp (i have uncheck "reboot" on odin of course) i can't get access to the recovery mode, when i do power button + volume up it doesn't do nothing and show this :
...
(I have already unlock my boot loader)
I think its DM VERITY who block the access to recovery mode but i can't disable this, cause i can't get access to twrp :/
Thanks for any answers c:
Click to expand...
Click to collapse
I had some similar problem.
It was a wrong TWRP, I had to try 3 different ones until it finally worked (the one for AJ1 worked for me).
If you are in a bootloop you still can press Volume UP + DOWN and at the same time put the USB cable in when booting. This should set your phone into the download mode and you can flash TWRP or OS again.

Has anyone tried this TWRP build with ATB1 February patch version? It has increased BL version (2->3) so it is not possible to roll back to any older FW...

From my information ATB1 is still the same security patch level as ATA4.
General question: How can I judge the BL version of the firmware?

ruffyrisco said:
Magisk-Root is working for me.
I did this:
Backup of ASJ1 with TWRP
...
Click to expand...
Click to collapse
what TWRP is this and how did you manage to install it before being rooted?

toshibashi said:
what TWRP is this and how did you manage to install it before being rooted?
Click to expand...
Click to collapse
I used the modified TWRP from post #1: https://androidfilehost.com/?fid=4349826312261685733

ruffyrisco said:
From my information ATB1 is still the same security patch level as ATA4.
General question: How can I judge the BL version of the firmware?
Click to expand...
Click to collapse
Well, my info comes from samfw.com/firmware/SM-A405FN/TMZ, not sure how do they extract it.
both ATB1 - samfw.com/firmware/SM-A405FN/TMZ/A405FNXXS3ATB1 and ATA4 - samfw.com/firmware/SM-A405FN/XEZ/A405FNXXU3ATA4 seems like BL (or some OTP bits, I am noob with android internals) bumped from 2 to 3.
(sorry about URL formatting, as a XDA newbie, I am no allowed to post URLs)

xorly said:
both ATB1 - samfw.com/firmware/SM-A405FN/TMZ/A405FNXXS3ATB1 and ATA4 - samfw.com/firmware/SM-A405FN/XEZ/A405FNXXU3ATA4 seems like BL (or some OTP bits, I am noob with android internals) bumped from 2 to 3.
Click to expand...
Click to collapse
As I mentioned earlier ATA4 firmware works fine with TRWP.
But I'm not sure if ATA4 has BL 3.
Does the digit 10 in the firmware number represents the BL?

ruffyrisco said:
But I'm not sure if ATA4 has BL 3.
Click to expand...
Click to collapse
Then reboot into Download mode (you have to do it manually, not via ADB command) and look into top left corner. On ATB1, one of last lines says
Code:
AP SWREV B:3 K:3 S:3
I assume that some fo those numbers (B?) is OTP number set by BL version.
ruffyrisco said:
Does the digit 10 in the firmware number represents the BL?
Click to expand...
Click to collapse
I am not sure which *10* do you mean. It looks like version prefix is bootloader version, number 3 in A405FNXXS3ATB1 or number 2 in A405FNXXU2ASK2. It is the only number which seems to corellate with BL version.
Also, now I can confirm that that this TWRP build (based on A405FNXXU2ASJ1) works with ATB1 firmware! (february sec. patch) Successfuly tested with Phhussons Android 10 GSI quack v213.

(Guide) Relock Bootloader/Back To Stock.

This guide is for those who are on unlocked bootloader/custom roms and want to go back to realme UI 1.0 and relock
Needless to say, me, and the makers of realme flash-tool and TWRP/other recoveries wouldn't be responsible for any damage caused to your device. Having said that, this method has been tested and should be fine for realme UI 1.0.
First things first, if you are on custom rom or on rooted stock rom you need to revert to unmodified stock rom.
*Warning :-Make absolutely sure that you are not relocking by flashing an older version, always flash the current or newer i:e If you unlocked while being on version A.19 make sure to flash A.19 and/or newer versions and not A.17. While I'm not sure if this will result in a brick or not and have no intentions of trying, this may result in a hardbrick.*
Links to firmware (RMX2061/EUxxxxxxx.ozip). Search for realme 6pro from the list.
IN.- https://www.realme.com/in/support/software-update
EU.- https://www.realme.com/eu/support/software-update
*Do not lock bootloader while on custom rom.*
*Do not lock bootloader if you're rooted.*
*Do not lock bootloader with any custom partitions even vbmeta with disabled verity and verification.*
IF YOU DO SO YOU'LL END UP WITH A BRICK WHICH CAN ONLY BE FIXED AT A SERVICE CENTER. YOUR PHONE WILL DISPLAY AN ERROR MESSAGE SAYING PARTITONS ARE CORRUPT/DAMAGED.
Backup your stuff before proceeding.
There are three ways to revert to stock:
1. Using RFT (Realme Flashtool) by @sayaoks :-
Instructions provided on the thread.
https://forum.xda-developers.com/re.../tool-rtf-realme-flash-tool-to-flash-t4144969
2. Using TWRP (use the latest from the recovery section).
*Wipe>Format Data> type yes> format
*Reboot>reboot to recovery
*Install > Select .ozip> Swipe to flash
*Reboot
Do not select disable-vbmeta or avb_patcher or anything of that sort.
Recommended-
https://forum.xda-developers.com/realme-6-pro/development/recovery-twrp-recovery-t4171759
3. Using stock recovery.
From system:- To flash using stock recovery, download and put the .ozip in the root of storage and from realme file manager tap on it. It will start Flashing in the stock recovery.
From recovery:- Download and put the .ozip in the root of storage, then reboot to recovery.
Your Language> Install from storage> enter password(only if you have one)> Phone/SDcard and then select the .ozip.
Any custom recovery.img/boot.img should now be replaced with stock.
After flashing is successful and the device has booted to stock rom reboot to the bootloader.
If you want to be extra careful, and used RFT or TWRP/Custom Recovery to flash stock rom, you can flash the fw again using stock recovery after the phone has booted up(steps mentioned above).
Connect the phone to PC and enter command
Code:
fastboot flashing lock
Now on the phone select lock bootloader with the help of volume up and power buttons.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wait for it to complete... and you will boot into the OS with a locked bootloader.
Thanks to @Satham spot & @sayaoks

I'm on RMX2063_11_A35 I can't find an update more recent than RMX2061EU_11.A.26 Can I use this method and update via OTA and then lock the bootloader?

Andres88z said:
I'm on RMX2063_11_A35 I can't find an update more recent than RMX2061EU_11.A.26 Can I use this method and update via OTA and then lock the bootloader?
Click to expand...
Click to collapse
A35 is the latest version for IN firmware. Latest for EU is A28, which is up on realme EU website.
If you want A35 firmware just visit the Indian downloads page.
And yes you can update to a newer version than whatever you unlocked on and then lock on the newer version. Make sure everything is just stock meaning no twrp,patched boot and/or custom recovery.

Don't have a brick to use the rmx2061 model? instead of device 2063, what method do you recommend.

Andres88z said:
Don't have a brick to use the rmx2061 model? instead of device 2063, what method do you recommend.
Click to expand...
Click to collapse
Well I know someone having Indonesian/Indian model and locking on the EU firmware. It didn't brick but not sure what will happen in the future when an OTA drops.
Lock on the same firmware as the device, like eu device with eu fw and so on (just to be safe).
You can use any methods to get to stock, just to be extra sure, when the phone boots up after flashing stock and before locking, put the fw in the root storage of the phone and re-flash again with the stock recovery. And then proceed to lock.

thanks to carry out the process and start correctly, I got an update of only 300 mb ls which gave me an error, but soon the same RMX2063a1135 came out but 3.5 gb which if it was installed and now I am as I started, without root or magisk, The question is, since the most recent was installed via ota, can I close the bootloader?

Andres88z said:
thanks to carry out the process and start correctly, I got an update of only 300 mb ls which gave me an error, but soon the same RMX2063a1135 came out but 3.5 gb which if it was installed and now I am as I started, without root or magisk, The question is, since the most recent was installed via ota, can I close the bootloader?
Click to expand...
Click to collapse
Yes

can i use orange fox recovery ? which one should i wipe if i use orange fox recovery?

Can this guide help me rollback my realme 6 pro from android 11 beta to android 10? If it does, which steps do I need to add or change. Thanks

noside_143 said:
Can this guide help me rollback my realme 6 pro from android 11 beta to android 10? If it does, which steps do I need to add or change. Thanks
Click to expand...
Click to collapse
Yes but you must use the latest Android 10 image, seem realme blocks to downgrade to older version than this

I have installed custom rom and I need to return to stock rom
all stock versions I found are ui 1.0 only
I unlocked the bootloader while using latest ui 2.0
what should I do to return to stock rom please ?

kiro_koko said:
I have installed custom rom and I need to return to stock rom
all stock versions I found are ui 1.0 only
I unlocked the bootloader while using latest ui 2.0
what should I do to return to stock rom please ?
Click to expand...
Click to collapse
You can use RUI 2.0 to lock. Just be sure that all partitions are stock. Use the .ozips made by @ctapchuk