Database Info

XT1575 February 2016 Security Update OTA (24.201.3.en.US) + Updated Stock ROM

Pulled from my US X Pure Edition.
Place in Internal Storage and flash in recovery.
Untested with flashing via TWRP as I've waited all day on complete stock ROM to capture and pull this zip.
MUST BE ON STOCK RECOVERY TO FLASH IT. If you flash it in TWRP and boot loop, without making a backup beforehand, you're on your own. You should've made a backup AS ALWAYS.
Screenshots:
{
"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"
}
February 2016 Security Update OTA
Google Drive: blur_version.24.11.18.clark_retus.retus.en.us (flash in stock recovery ONLY)
MD5: e08d5e837d59d9b4ecd88f15ba2906f7
Stock odexed ROM with the February 2016 Security Update applied. No root. Flash in TWRP.
Google Drive: stock_marshmallow_for_moto_x_pure_edition-mphs24.49-18-3 (flash in TWRP)
MD5: 2a1505d2626aa1ef1d18da904a3d5093
Modified boot.img post for use with traditional SuperSU root by DaMadOne here:
http://forum.xda-developers.com/showpost.php?p=65541582&postcount=61
Stock 6.0 Marshmallow Recovery:
IMG version
Google Drive: stock-6.0-mph24.49-18-recovery.img (flash in fastboot or TWRP)
MD5: 2ac9b589a3dc14d4000cbbe082b36ba9
ZIP version
Google Drive: stock-6.0-mph24.49-18-recovery.zip (flash in TWRP)
MD5: a59bb1d9eca25608658cd67f7b4707c2
NOTE: If you get "No command" while booting into stock recovery, hold the power button and press up on the volume key. Options should now be available. I'm not sure why it does that but it used to do it on Nexus devices (and probably still does.)

Spasticdroid said:
Pulled from my US X Pure Edition.
Place in Internal Storage and flash in recovery.
Untested with flashing via TWRP as I've waited all day on complete stock ROM to capture and pull this zip.
Screenshots:
Google Drive: blur_version.24.11.18.clark_retus.retus.en.us
Click to expand...
Click to collapse
So is this captured ota or a stock twrp backup

Google~Android said:
So is this captured ota or a stock twrp backup
Click to expand...
Click to collapse
Spasticdroid said:
capture and pull this zip.
Click to expand...
Click to collapse
It's the OTA.

Hi do you know how to flash this using twrp? I tried and it failed. Thank you in advance.

Hey dude, I just got the notification. I'm using the stock ROM, rooted and obviously bootloader unlocked, also using xposed, do you know if it's safe for me to install the update from the notification? I just don't want to screw it and start from scratch.

I flashed supersu 2.66 as I had done previous but wouldn't boot past the logo. Anyone gotten this rooted?
Nexus 10

Vinrock2244 said:
Hi do you know how to flash this using twrp? I tried and it failed. Thank you in advance.
Click to expand...
Click to collapse
What error? Where's your recovery log?
Doesn't work with TWRP 3.x? Use an older version.
Doesn't work with the older TWRP 2.x? Use TWRP 3.x.
Not working with TWRP period? Flash stock recovery, flash the OTA, put TWRP back.
blkcr said:
Hey dude, I just got the notification. I'm using the stock ROM, rooted and obviously bootloader unlocked, also using xposed, do you know if it's safe for me to install the update from the notification? I just don't want to screw it and start from scratch.
Click to expand...
Click to collapse
I don't use Xposed so I wouldn't know if the OTA will work even after uninstalling it. Also, if you're not using systemless root, you'll have to wipe clean. Back up data apps using Titanium or similar. Systemless root however restores original kernel and files.
rocketsaucev2 said:
I flashed supersu 2.66 as I had done previous but wouldn't boot past the logo. Anyone gotten this rooted?
Nexus 10
Click to expand...
Click to collapse
2.67 systemless works fine.

Spasticdroid said:
2.67 systemless works fine.
Click to expand...
Click to collapse
Do you have a link handy? Is it just twrp flashable?
Nexus 10

Also in for a twrp flashable version

rocketsaucev2 said:
Do you have a link handy? Is it just twrp flashable?
Nexus 10
Click to expand...
Click to collapse
Google SuperSU Beta. Should be the first link to Chainfire's thread.
Run this in a Terminal app (with su) or TWRP's Terminal
Code:
echo "SYSTEMLESS=true" >> /data/.supersu
Then flash SuperSU 2.67.

Spasticdroid said:
Google SuperSU Beta. Should be the first link to Chainfire's thread.
Run this in a Terminal app (with su) or TWRP's Terminal
Code:
echo "SYSTEMLESS=true" >> /data/.supersu
Then flash SuperSU 2.67.
Click to expand...
Click to collapse
Got it. Thanks
Nexus 10

Just popped up on mine as well. Small.

Interesting, the zip contains baseband patches but the version in the OP remained the same. Anyone notice any differences in reception?

Decided to give this a go... Have combined storage and was on a custom stock rom with xposed and viper.
Flashed stock system and recovery, did not wipe data.
Reboot system, let everything update, verify combined storage untouched.
Stock recovery could not find the update since I have combined storage.
Tried TWRP with no success
Flashed stock recovery and sideloaded the update
Update flashed succesfully
Reboot to bootloader and flash TWRP and kernel of choice.
Reboot system
Reboot to bootloader and flash super su, xposed etc.
2.67 non systemless did not work for me. 2.64 worked fine as usual. Well maybe not, getting a lot of system fc's. Will update once I have it worked out.
So flashing 2.62-3, then flashing 2.64 got me out of bootloops and system fc's. Seems to be good to go now.

I am very interested in systemless root specifically for the security updates and benefits of root.
Using this guide
http://forum.xda-developers.com/showpost.php?p=64624664&postcount=454
and SuperSU beta should all be ok?
I am ATM on trupurexmm 2.6.2, frankenclark v0.7, xt1575 and twrp 3.0.0-1.

Can someone on an untouched stock system pull /system after the update and upload it for me? I would like to create a flashable zip so we don't have to go through all this nonsense to update.

Is there any detailed guide on how to make this OTA update work on a machine with root + twrp?

blkcr said:
Hey dude, I just got the notification. I'm using the stock ROM, rooted and obviously bootloader unlocked, also using xposed, do you know if it's safe for me to install the update from the notification? I just don't want to screw it and start from scratch.
Click to expand...
Click to collapse
Same boat here. Stock rooted with Xposed. Rooted with 2.62.
---------- Post added at 09:02 AM ---------- Previous post was at 08:54 AM ----------
There is a stock 6.0 twrp backup file available. Perhaps you could restore that, take the OTA, then root again?

bostonirishguy13 said:
Same boat here. Stock rooted with Xposed. Rooted with 2.62.
---------- Post added at 09:02 AM ---------- Previous post was at 08:54 AM ----------
There is a stock 6.0 twrp backup file available. Perhaps you could restore that, take the OTA, then root again?
Click to expand...
Click to collapse
I was thinking of this same thing.
For I, I have a stock non root twrp backup. Was thinking of flashing the stock ota mm that I have then flashing the recovery to stock then take the ota. Install twrp, then root.
Sent from XT1575,TPXMM 2.6.2,Frankenclark v0.7

shoman94 said:
Can someone on an untouched stock system pull /system after the update and upload it for me? I would like to create a flashable zip so we don't have to go through all this nonsense to update.
Click to expand...
Click to collapse
I was going to keep this to myself and one other person on here. It's unmodified, meaning no root, and odexed. Only converted to be flashable.
Also note that I have included other items in the ROM including radios/modem and an unmodified logo.bin, meaning you will get the "bootloader unlocked" splash.
Too lazy to make a thread for it. Any one wants to? Have at it.
https://drive.google.com/file/d/0B5AiGacWcBRzMTBlWmppOC1DS3c/view?usp=docslist_api
Sent from my XT1575 using Tapatalk

[GUIDE] How to root Nougat on Moto G4 Plus [UPDATED for NPJ25.93-11/12/14]

** WARNING **
If you are on NPJ25.93-11/12/14 (non-soak test Nougat), you MUST flash the ElementalX kernel (link) after step 4. Make sure to backup the stock kernel before proceeding.
I'm glad we're among the first ones to get updated to Nougat but what about root? Just follow this guide and enjoy!
Before starting
An unlocked bootloader is required.
Download Fastboot and install/extract it to a folder.
Download TWRP and put it in the same folder as fastboot.
Download phh's SuperUser (thread) zip file, open the zip file and then inside you will find config.txt. The default content is
Code:
eng verity crypt
change it to
Code:
eng noverity nocrypt
and save. Copy this zip file to your phone afterwards.
Steps
Power off your device.
Boot into bootloader mode (Vol Down + Power).
Connect your phone to your PC with USB and flash TWRP using the following command:
Code:
fastboot.exe flash recovery twrp-3.0.2-0-athene.img
Boot into TWRP by using volume buttons to navigate and power button to select "Recovery Mode".
Install/flash superuser.zip within TWRP.
Reboot.
Install the phh's SuperUser app from Play Store.
Enjoy your root!

Is stable twrp?
Enviado desde mi Moto G (4) mediante Tapatalk

Did any one tried it did it worked?
Sent from my Moto G4 Plus using Tapatalk

HerH2 said:
Is stable twrp?
Click to expand...
Click to collapse
TWRP is stable as usual.
VN_bunny said:
Did any one tried it did it worked?
Click to expand...
Click to collapse
Works fine for me
{
"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"
}

doomed151 said:
TWRP is stable as usual.
Works fine for me
Click to expand...
Click to collapse
Nice!
Enviado desde mi Moto G (4) mediante Tapatalk

i flashed this supersu along with systemless root method. but there is no supersu app in drawer.

srgudhka said:
i flashed this supersu along with systemless root method. but there is no supersu app in drawer.
Click to expand...
Click to collapse
7. Install the Superuser app from Play Store.
Click to expand...
Click to collapse
You need to install the app from Play Store. Also, this is not SuperSU, this is phh's SuperUser.
When I tried rooting with SuperSU, it broke Wi-Fi and mobile network.

Works perfect on 1642

doomed151 said:
You need to install the app from Play Store. Also, this is not SuperSU, this is phh's SuperUser.
When I tried rooting with SuperSU, it broke Wi-Fi and mobile network.
Click to expand...
Click to collapse
lol my bad. got too excited and forgot to read that step xD

works like charm
only thing needed is to observe the steps carefully. enjoying root on nougat now.. thanks a million.. button pressed too..

What about xposed?

GuSoares said:
What about xposed?
Click to expand...
Click to collapse
Not available yet.

Or you can go full systemless using Magisk and phh superuser module.
http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Stuff like adaway are also working fine.
Edit: typo

I unlocked my bootloader and installed TWRP from post. I'm with a XT1626, and not worked for me.
I have done all steps correctly 3 times, but no lucky.
Im TWRP it shows that supersu have been installed but when i open root checker, it is not rooted.
What to do now? I have not tried to reinstall 7.0 rom because i don't know how. I think i need to wipe rom and lock bootloader? Any tips?
In CPU-Z Shows "Yes" for root, but when i check root it says "Root Access Not Installed Properly". When i try to install BusyBox it says that i'm not rooted

Did you really flash phh's SuperUser (superuser.zip) instead of SuperSU?

GuSoares said:
I unlocked my bootloader and installed TWRP from post. I'm with a XT1626, and not worked for me.
I have done all steps correctly 3 times, but no lucky.
Im TWRP it shows that supersu have been installed but when i open root checker, it is not rooted.
What to do now? I have not tried to reinstall 7.0 rom because i don't know how. I think i need to wipe rom and lock bootloader? Any tips?
In CPU-Z Shows "Yes" for root, but when i check root it says "Root Access Not Installed Properly". When i try to install BusyBox it says that i'm not rooted
Click to expand...
Click to collapse
Did you do step #7?

doomed151 said:
Did you really flash phh's SuperUser (superuser.zip) instead of SuperSU?
Click to expand...
Click to collapse
For sure
SoNic67 said:
Did you do step #7?
Click to expand...
Click to collapse
Yes, it was the First thing i have done when rebooted my phone after flashing phh's SuperSU in TWRP. I used all files provided here too. I have no clue what to do to make it work

actually i unlocked bootloader and flashed twrp after updating to android n what happened was after flashing recovery the device was always rebooting in twrp mode only i dont know why even rebooting to system was not working so i flashed beanstalk rom and that worked the mobile rebooted properly so i guess after updating to android n and then flashing recovery might not work

There is no point in flashing TWRP if you plan to stick with the stock Nougat. I just boot in TWRP, but not flash it.

Please, rename the step #7 from "SuperUser app" to "phh's SuperUser" Ahahaha! i was with wrong app
Now rooted! Thanks mate

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:

[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.

[FASTBOOT] [daisy] Patched boot.img for V11.0.10.0 (Android 10)

I followed my usual guide to upgrade...
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863/
The August update is 11.0.10.0. I have a patched boot with Magisk 20.4
https://yasmar.net/xda/patched_boot_11.0.10.0_204.img.gz
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_11.0.10.0.img.gz

Can you tell how to to update I have only magisk Installed I want to keep magisk.

Aadil Gillani said:
Can you tell how to to update I have only magisk Installed I want to keep magisk.
Click to expand...
Click to collapse
The Magisk thread has the process.
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
You don't need a PC because Magisk backs up the vanilla boot and restores it.
It's TWRP that comlicates otas.

a1291762 said:
The Magisk thread has the process.
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
You don't need a PC because Magisk backs up the vanilla boot and restores it.
It's TWRP that comlicates otas.
Click to expand...
Click to collapse
I only have Magisk and tried the process in the link but I'm always getting the "Couldn't update, installation problem" error. Can I update my phone by simply flashing the patched boot image?

elvinguitar said:
I only have Magisk and tried the process in the link but I'm always getting the "Couldn't update, installation problem" error. Can I update my phone by simply flashing the patched boot image?
Click to expand...
Click to collapse
No, but you may be able to install the OTA if you flash the vanilla image for your version.
The update process tells you which partitions are modified. Details in my guide.
Or just flash the whole rom.

a1291762 said:
No, but you may be able to install the OTA if you flash the vanilla image for your version.
The update process tells you which partitions are modified. Details in my guide.
Or just flash the whole rom.
Click to expand...
Click to collapse
Will I lose my data by flashing the vanilla image?

elvinguitar said:
Will I lose my data by flashing the vanilla image?
Click to expand...
Click to collapse
Flashing a boot image won't lose data unless you use the wrong version and get unlucky.
Flashing any of the partitions that the OTA touches won't lose data.

a1291762 said:
The Magisk thread has the process.
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
You don't need a PC because Magisk backs up the vanilla boot and restores it.
It's TWRP that comlicates otas.
Click to expand...
Click to collapse
I've unlocked my bootloader and I've read through the guide a few times now, but there's one thing I need to know before I begin. I'm running stock Android 10 build 11.0.10.0 only having the bootloader unlocked.
Am I able to flash the patched boot.img for V11.0.10.0 that you linked in your other post straight away without having installed any other boot.img previously?
I've only ever flashed Samsungs and a few Sony phones and I'd like to be thorough without cocking up.

RyanCM said:
I've unlocked my bootloader and I've read through the guide a few times now, but there's one thing I need to know before I begin. I'm running stock Android 10 build 11.0.10.0 only having the bootloader unlocked.
Am I able to flash the patched boot.img for V11.0.10.0 that you linked in your other post straight away without having installed any other boot.img previously?
I've only ever flashed Samsungs and a few Sony phones and I'd like to be thorough without cocking up.
Click to expand...
Click to collapse
Yes...
If you flash a patched boot.img then Magisk won't have a backup and you can't OTA without flashing the vanilla image. That's why the standard process is to boot the patched image and then use Magisk Manager to install Magisk.
If you're going to install TWRP then you need to install it before Magisk. There is no flashable TWRP, only the installer, and it trashes Magisk. You must use Magisk Manager to install Magisk after TWRP (or flash it from TWRP) since they both live on the same partition.

a1291762 said:
Yes...
If you flash a patched boot.img then Magisk won't have a backup and you can't OTA without flashing the vanilla image. That's why the standard process is to boot the patched image and then use Magisk Manager to install Magisk.
If you're going to install TWRP then you need to install it before Magisk. There is no flashable TWRP, only the installer, and it trashes Magisk. You must use Magisk Manager to install Magisk after TWRP (or flash it from TWRP) since they both live on the same partition.
Click to expand...
Click to collapse
Thank you. All I want to do for the meantime is root and try out Magisk. I just wasn't sure if I was able to flash the patched .img without needing to flash anything beforehand.
Hopefully I don't make a mistake here and will come back to this thread once I've succeeded/messed up.
---------- Post added at 05:02 AM ---------- Previous post was at 04:24 AM ----------
RyanCM said:
Thank you. All I want to do for the meantime is root and try out Magisk. I just wasn't sure if I was able to flash the patched .img without needing to flash anything beforehand.
Hopefully I don't make a mistake here and will come back to this thread once I've succeeded/messed up.
Click to expand...
Click to collapse
I successfully flashed the patched boot.img and installed Magisk Manager and the only options I have are to flash a zip in recovery (I don't have recovery, hindsight) and "select and patch a file". I don't know how to proceed with either of those options.
EDIT: When flashing the patched boot.img, I didn't realise I had to flash both A/B partitions and that is why it said Magisk wasn't installed. I'm now fully rooted and Magisk is installed.

RyanCM said:
EDIT: When flashing the patched boot.img, I didn't realise I had to flash both A/B partitions and that is why it said Magisk wasn't installed. I'm now fully rooted and Magisk is installed.
Click to expand...
Click to collapse
That's why the standard way is to BOOT the patched image and use Magisk Manager to install.
If you want to flash partitions, you need to use the correct set (a or b). Fastboot can tell you (getvar current-slot). Flashing both is useless, since the inactive set of partitions is only used when doing OTA (or dual boot, for some brave souls).
If you're coming from phones without a/b partitions you should definitely read about them. Several things are quite different.

Please help me boot sign.img unsing img kar do please a kar na ka leya pc ka zaroorat
Please help me boot sign.img unsing img kar do please a kar na ka leya pc ka zaroorat hai mara pass pc nahe ha bootsign.img file link=https://drive.google.com/file/d/1Q172DYs7t7bIo0K_LENCO1OAo6tg0FTz/view?usp=drivesdk and video how to boot sign.img unsing img link=https://youtu.be/ZWphK23KLew

a1291762 said:
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_11.0.10.0.img.gz
Click to expand...
Click to collapse
Offline ... can you please reup?

networxpsc said:
Offline ... can you please reup?
Click to expand...
Click to collapse
It's hosted on Google drive. It just loaded for me (private window to simulate anon user). The preview won't work because it's not that kind of file. Just click download.
{
"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"
}