Database Info

Honor 6 Plus CWM / TWRP Recovery EMUI3.0

Does anyone know or have a copy of a working EMUI3.0 CWM or TWRP recovery for the Honor 6 Plus (6x) PE-TL10
Boot loader unlocked but no root. Tried normal root tools but none yet seems to work, so I was looking to changing the recovery to CWM /TWRP and then flash SU and root that way, returning to stock 3.0 extracted recovery from the latest ROM.
Any assistance appreciated please.

http://forum.xda-developers.com/android/general/huawei-honor-6-plus-root-tutorial-t2991788

Thanks but tried that, recovery does not work on the 6 Plus and the proc may be good for a mate7 but not for the 6Plus. It was just as well I had extracted a stock 3.0 recovery to go back to. I think that this proc may have been written for 2.0 not 3.0, that may be why I get a blank screen on boot in to recovery.
So still waiting...

Sathelp said:
Thanks but tried that, recovery does not work on the 6 Plus and the proc may be good for a mate7 but not for the 6Plus. It was just as well I had extracted a stock 3.0 recovery to go back to. I think that this proc may have been written for 2.0 not 3.0, that may be why I get a blank screen on boot in to recovery.
So still waiting...
Click to expand...
Click to collapse
Hello, I have it running smoothly on my Honor 6 Plus PE-UL00.
If you have bootloader open just puts the recovery with:
fastboot flash recovery recovery_en.img
I leave you with attachment
To flash can also be used Honor 6 MultiTool modifying the bat or renaming the recovery_en.img by the recovery that you download the program
Sorry for my poor English

BoRoU said:
Hello, I have it running smoothly on my Honor 6 Plus PE-UL00.
If you have bootloader open just puts the recovery with:
fastboot flash recovery recovery_en.img
I leave you with attachment
To flash can also be used Honor 6 MultiTool modifying the bat or renaming the recovery_en.img by the recovery that you download the program
Sorry for my poor English
Click to expand...
Click to collapse
Thanks you but the recovery file you attached is only 128bytes bytes big and not a valid file. can you please attach the full recovery file please? I will then try to flash it.

Sathelp said:
Thanks you but the recovery file you attached is only 128bytes bytes big and not a valid file. can you please attach the full recovery file please? I will then try to flash it.
Click to expand...
Click to collapse
I managed to use the Multitool and its recovery_en, so no worry, all done, but here if anyone else is looking for instruction on how I done it, here they are:
I used the Honor 6 Multi-tool from this thread in the XDA pages.
I am not sure if the bootloader unlock works or not, so if you can get it unlocked as above or try this tool.
The tool is for the 6 not especially the 6Plus but using the install CWM recovery works, then I used the boot to recovery and then selected root by sidelobe (install zip/install zip by sidelobe menus). SU was installed permissions set. As I wanted to ensure that the correct stock recovery was used (my EMUI3.0 extracted before) I selected to reboot the phone by exiting the (recovery) and it then asked me if I wanted to fix root, I selected yes, rebooted the phone. Checked that root was working and then went back to bootloader and fastboot flash recovery (my recovery) to get it back to stock.

Sathelp said:
I managed to use the Multitool and its recovery_en, so no worry, all done, but here if anyone else is looking for instruction on how I done it, here they are:
I used the Honor 6 Multi-tool from this thread in the XDA pages.
I am not sure if the bootloader unlock works or not, so if you can get it unlocked as above or try this tool.
The tool is for the 6 not especially the 6Plus but using the install CWM recovery works, then I used the boot to recovery and then selected root by sidelobe (install zip/install zip by sidelobe menus). SU was installed permissions set. As I wanted to ensure that the correct stock recovery was used (my EMUI3.0 extracted before) I selected to reboot the phone by exiting the (recovery) and it then asked me if I wanted to fix root, I selected yes, rebooted the phone. Checked that root was working and then went back to bootloader and fastboot flash recovery (my recovery) to get it back to stock.
Click to expand...
Click to collapse
Thanks in advance for this tutorial My 6 Plus is on its way from China.
What's funny though... I also once owned an Eten X500 and my previous phone was a ZTE V987
My GF is now using it with MIUI v5, but I'll give here my ZTE V5 when my Honor 6 Plus arrived
Aren't you also active on this UK Cloud iBox satbox forum?

No not me. I am on several forums but mainly phones or tablets ( heavy on what was the Eten forum with Bruno Martin who now works here on Gravity Box or on satellite TV forums. I think a lot of us old dual sim users had a near similar list of phones as they developed.
BTW, the Honor 6 plus multi tool has my recovery added, so you can use that now too.

Just for anyone finding or searching and coming on to this thread, I have posted the tools needed at this link.
It has CWM and stock recovery files as well as the SuperSU and install bat file.

Sathelp said:
I used the Honor 6 Multi-tool from this thread in the XDA pages.
I am not sure if the bootloader unlock works or not, so if you can get it unlocked as above or try this tool.
Click to expand...
Click to collapse
You can get unlock code from the site given in Multi-Tool.
{
"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"
}
If the CWM/TWRP for H6 doesn't work on H6Plus i can add custom recoveries that work on your device.
UPDATE: I add "recovery_en" in Multi-Tool. Can anyone tell me what version of CWM is?

VirusPlus said:
You can get unlock code from the site given in Multi-Tool.
View attachment 3124925
If the CWM/TWRP for H6 doesn't work on H6Plus i can add custom recoveries that work on your device.
UPDATE: I add "recovery_en" in Multi-Tool. Can anyone tell me what version of CWM is?
Click to expand...
Click to collapse
As we don't have any custom ROMs, how do we update to latest version when Huawei do release (especially when they release Lillipop)?

ksekhar said:
As we don't have any custom ROMs, how do we update to latest version when Huawei do release (especially when they release Lillipop)?
Click to expand...
Click to collapse
You can always revert back to stock recovery. The tool for Mate 7 from Anzhi BBS forum works great.
I have already done this three times when there has been a new OTA updates.

Sathelp said:
Just for anyone finding or searching and coming on to this thread, I have posted the tools needed at this link.
It has CWM and stock recovery files as well as the SuperSU and install bat file.
Click to expand...
Click to collapse
Maybe I didn't understand your instructions 100% correct, but without getting an unlock code from the Emui site to unlock the Bootloader I wasn't getting anywhere.
So I got the Unlock code from the site and then went through all the steps from VirusPlus tool and that all worked perfectly
In the end I think I would have got exactly the same result with your 6-Plus-only tool.
Anyhow, from within the MultiTool I did the following:
I installed the Universal ADB drivers, got the bootloader unlocked, installed CWM, installed SuperSU, installed Stock recovery... reboot. Winning.
Thanks all for your excellent work

Flow said:
Maybe I didn't understand your instructions 100% correct, but without getting an unlock code from the Emui site to unlock the Bootloader I wasn't getting anywhere.
So I got the Unlock code from the site and then went through all the steps from VirusPlus tool and that all worked perfectly
In the end I think I would have got exactly the same result with your 6-Plus-only tool.
Anyhow, from within the MultiTool I did the following:
I installed the Universal ADB drivers, got the bootloader unlocked, installed CWM, installed SuperSU, installed Stock recovery... reboot. Winning.
Thanks all for your excellent work
Click to expand...
Click to collapse
yes, The VirusPlus tool was updated and works fine now with the recovery and CWM I sent him that I used. There was a small problem at the start but he has corrected it. Glad your all sorted now. I noticed a small update today for the 6 Plus, nothing much but you need to be back on stock recovery to update it. Easy now though to go back to CWM whenever you want to.

Sathelp said:
yes, The VirusPlus tool was updated and works fine now with the recovery and CWM I sent him that I used. There was a small problem at the start but he has corrected it. Glad your all sorted now. I noticed a small update today for the 6 Plus, nothing much but you need to be back on stock recovery to update it. Easy now though to go back to CWM whenever you want to.
Click to expand...
Click to collapse
I reflashed back to stock recovery after installing supersu, do you need to reinstall CWM and supersu after an OTA update or doesn't it affect root?

Flow said:
I reflashed back to stock recovery after installing supersu, do you need to reinstall CWM and supersu after an OTA update or doesn't it affect root?
Click to expand...
Click to collapse
It does depend on the update. Most times (minor updates) it will be fine and survive the OTA update but at least you have the tools to put it back on if it does after a major update or re-flash of the ROM. There is a setting in SuperSU about updates, may be worth checking it out but I think one of the settings is only available on the Pro or donated version.

Sathelp said:
yes, The VirusPlus tool was updated and works fine now with the recovery and CWM I sent him that I used. There was a small problem at the start but he has corrected it. Glad your all sorted now. I noticed a small update today for the 6 Plus, nothing much but you need to be back on stock recovery to update it. Easy now though to go back to CWM whenever you want to.
Click to expand...
Click to collapse
Can this CWM make a full back up? I didn't found any backup files after mention successful backup.....

Did anyone already try the EMUI 3.1 (Android 5.1) ROM on the H6+ and succesfully got Root with this tool?
Android 5.1 ROM: http://www.emui.com/cn/plugin.php?id=hwdownload&mod=detail&mid=125
Mirror: https://mega.nz/#!5ox3wByI!ajcv6SvTnymYH2g4hnpMI1Li0nj80i7NZyATwiHMa0w
Edit:
Warning: Only install the EMUI 3.1 ROM when you have Stock Recovery!
Mine was rooted as well, that was not a problem.
I did loose root after installation though.
Managed to install it and then rooted (SuperSU) with TWRP for EMUI 3.1

Flow said:
Did anyone already try the EMUI 3.1 (Android 5.1) ROM on the H6+ and succesfully got Root with this tool?
Edit:
Warning: Only install the EMUI 3.1 ROM when you have Stock Recovery!
Mine was rooted as well, that was not a problem.
I did loose root after installation though.
Managed to install it and then rooted (SuperSU) with TWRP for EMUI 3.1
Click to expand...
Click to collapse
after you rooted, can it downgraded to emui 3.0 again?

afikri6 said:
after you rooted, can it downgraded to emui 3.0 again?
Click to expand...
Click to collapse
I don't understand your question.
Why would I want to downgrade back to EMUI 3.0 and what does it have to do with root?
My advice in general when installing a complete ROM:
Install Stock Recovery.
Download complete ROM package (inclusing the dload/UPDATE.APP file).
Install as Local update using the Updater app.
I'm not sure if this would work the same with downgrading.

[firmware]STF-L09C432B150 - FullOTA Rollback

Hi guys,
this morning was uploaded STF-L09C432B150 Rollback update (FullOTA) on Huawei server. Here are download links:
http://http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1906/g1642/v105908/f1/full/update.zip
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1906/g1642/v105908/f1/full/STF-L09_hw_eu/update_full_STF-L09_hw_eu.zip
Changelog:
Code:
This update will roll back your phone's operating system to Android 7.0 (EMUI 5.1).
Rollback notes:
1. Please make sure you are currently using the official version of Huawei EMUI, and that no unofficial updates have been installed. Otherwise, there will be risk of an unsuccessful rollback, and an unknown error may occur.
2. Make sure that the current version has not been unlocked or rooted.
3. All user data will be deleted in the rollback. Use an SD card, computer, or Cloud storage to back up all important data before rolling back your phone, and make sure all backed up content is complete and effective.
4. Make sure your phone has more than 50% battery remaining.
5. If you experience any issues during the update, please call the Huawei customer service hotline or visit an authorised Huawei service centre for assistance.
6. The system will restart after the rollback. This will take about 10 minutes. Following the update, your home screen will automatically display the EMUI 5.1 theme.

Pa-Jo said:
Hi guys,
this morning was uploaded STF-L09C432B150 Rollback update (FullOTA) on Huawei server. Here are download links:
http://http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1906/g1642/v105908/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...l/STF-L09_hw_eu/update_full_STF-L09_hw_eu.zip
Changelog:
Click to expand...
Click to collapse
Yes it's mean that Oreo are coming and B150 are the latest stable official version

How can I flash this? Im on b150, but want to flash a clean one.

Sigray said:
How can I flash this? Im on b150, but want to flash a clean one.
Click to expand...
Click to collapse
This is rollback update only, it can be used only if you are using greater official updat from Huawei running on Android 8. and it will downgrade you from Android 8 back to Android 7.

Pa-Jo said:
This is rollback update only, it can be used only if you are using greater official updat from Huawei running on Android 8. and it will downgrade you from Android 8 back to Android 7.
Click to expand...
Click to collapse
I have now beta Oreo STF-L09 8.0.0.323(C432log). So this files are for rollback from this version.
And how to do it? First put update.app from first ZIP file do dload directory and flash it and then do the same with second app? As in this thread: https://androidforum.cz/advanced-search/?keywords=dload&t=76974&sf=msgonly (czech language)

Gnaget said:
Yes it's mean that Oreo are coming and B150 are the latest stable official version
Click to expand...
Click to collapse
yes,, OREO Beta Already running on some Honor 9 devices..
Soon other devices will also get Oreo

hassanjavaid8181 said:
yes,, OREO Beta Already running on some Honor 9 devices..
Soon other devices will also get Oreo
Click to expand...
Click to collapse
Yes I know for the moment Mine phone are running Beta. So far it had been smooth.

Software install failed. It everytime writes this. It does not work for me:-/ Oreo beta doesn't run better than nougat on my phone. How can I downgrade to nougat?
---------- Post added at 01:28 AM ---------- Previous post was at 01:04 AM ----------
I did it without microSD card and copied to the phone. Is the sd card necessary??

Kkozi said:
Software install failed. It everytime writes this. It does not work for me:-/ Oreo beta doesn't run better than nougat on my phone. How can I downgrade to nougat?
---------- Post added at 01:28 AM ---------- Previous post was at 01:04 AM ----------
I did it without microSD card and copied to the phone. Is the sd card necessary??
Click to expand...
Click to collapse
You installing it via dload metbod??

You can use Huawei HiSuite to rollback officially without any hacks

Yes i'm sure because i just did it
{
"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"
}
I have a retail german version of the Honor9
After installing 150 you can also update to 180 via official system -> Update -> Download full package

wow I hope this means Oreo is comming officialy, mine was just updated to B180 since the one that came on the box, I think will be weird get two updates that fast, but I hope it comes soon

It's not ok for me. Not rooted, locked bootloader but when it restarts in recovery it give to me software failed error
I'm really hating Oreo (beta) in Honor 9 because performances are poor and battery too.

Did you do it like explained? Either in Huawei HiSuite or the Phone Manager (App) - No hacks or inofficial ways..

ktwo said:
Did you do it like explained? Either in Huawei HiSuite or the Phone Manager (App) - No hacks or inofficial ways..
Click to expand...
Click to collapse
Using HiSuite I receive the error, even if my device is not rooted, bl is not unlocked and system is not corrupted
I have solved using an approved firmware from Firmware Finder

Oreo rollback
dying_sun said:
Using HiSuite I receive the error, even if my device is not rooted, bl is not unlocked and system is not corrupted
I have solved using an approved firmware from Firmware Finder
Click to expand...
Click to collapse
Hello dying_sun, i have the same problem.
Honor 9, STF L09 (Europe), now with OREO B360
- unlocked bootloader
- TWRP 3.1.1
- rooted with SuperSU
--> after some days I unrooted my device and locked my bootloader
(I use multitool for TWRP and stock recovery)
After unrooting OREO ota came and a realised that the capacitive buttons are not working. Tried different settings, only the home button works
What to do?
--> Rollback to B120.
I downloaded firmwares from different sites and tried different methods
3-button update: Installing failed
dload method sd card: Installing failed (NTFS format, 32 GB)
dload method internal memory: Installing failed
*#*#284...#*#* method, upgrade from sdcard: Installing failed
I tried to flash a kernel.....img (here in forum "Capacity fix" topic) but when I install it over TWRP the device asks me in which flash memory should it be flashed and I do not know what to choose. (system, ODM, splash2, recovery_ramdisk, cache)
I also tried the HWOTA method, but I get the message, that "recovery2" could not be written into ramdisk or something like that and then it stops.
Possible that I did not consider a little detail
Could you please tell me which firmware from firmware finder did you use and which method you choose to make rollback?
Slowly I get desperated with the phone.....
Thanks a lot in advance
Andy

andryuxa20081 said:
Hello dying_sun, i have the same problem.
Honor 9, STF L09 (Europe)
- unlocked bootloader
- TWRP 3.1.1
- rooted with SuperSU
--> after some days I unrooted my device and locked my bootloader
(I use multitool for TWRP and stock recovery)
After unrooting OREO ota came and a realised that the capacitive buttons are not working. Tried different settings, only the home button works
What to do?
--> Rollback to B120.
I downloaded firmwares from different sites and tried different methods
3-button update: Installing failed
dload method sd card: Installing failed (NTFS format, 32 GB)
dload method internal memory: Installing failed
*#*#284...#*#* method, upgrade from sdcard: Installing failed
I tried to flash a kernel.....img (here in forum "Capacity fix" topic) but when I install it over TWRP the device asks me in which flash memory should it be flashed and I do not know what to choose. (system, ODM, splash2, recovery_ramdisk, cache)
I also tried the HWOTA method, but I get the message, that "recovery2" could not be written into ramdisk or something like that and then it stops.
Possible that I did not consider a little detail
Could you please tell me which firmware from firmware finder did you use and which method you choose to make rollback?
Slowly I get desperated with the phone.....
Thanks a lot in advance
Andy
Click to expand...
Click to collapse
First : Are you on nougat or oreo now, and what's your region ?
your phone is booting ok in system, but no capacitives buttons ? So you'll like to fix them before updating ?
When on nougat, for flashing the dload way a service repair nougat firmware, I think you must have formatted your SDcard to exFAT and not ntfs.
I think when using service repair dload files, you must use the same region files the phone is actually.
For info :
3-button update,
dload method,
& *#*#284...#*#* method,
Are all the same.
You also tried the HWOTA method, but which hwota files did you used ?

oslo83 said:
First : Are you on nougat or oreo now, and what's your region ?
your phone is booting ok in system, but no capacitives buttons ? So you'll like to fix them before updating ?
When on nougat, for flashing the dload way a service repair nougat firmware, I think you must have formatted your SDcard to exFAT and not ntfs.
I think when using service repair dload files, you must use the same region files the phone is actually.
For info :
3-button update,
dload method,
& *#*#284...#*#* method,
Are all the same.
You also tried the HWOTA method, but which hwota files did you used ?
Click to expand...
Click to collapse
Hello oslo83,
The phones Emui is now Emui 8.0.0, B360.
I have an unlocked bootloader, booting is ok (message about unlocked bootloader comes first)
Capacitive buttons and flash light are not working --> I would like to fix them (this is the reason why I try to rollback to B120.
I tried to format to FAT 32, but not possible to copy update.app, because of size. With NTFS it worked. --> I try format to exFat
I downloaded a full-service-repair-package for europe from the site 4pda.ru.
Should I use Firmware finder?
What do you mean with "which HWOTA fileS? --> update.zip / update_full_data.zit and a third one..... comlete package, as described.
Thank you in advance.
Andy

andryuxa20081 said:
Hello oslo83,
The phones Emui is now Emui 8.0.0, B360.
I have an unlocked bootloader, booting is ok (message about unlocked bootloader comes first)
Click to expand...
Click to collapse
So, STF-L09CxxxB360.
What's your region ? C432, C10, ...?
andryuxa20081 said:
Capacitive buttons and flash light are not working --> I would like to fix them (this is the reason why I try to rollback to B120.
I tried to format to FAT 32, but not possible to copy update.app, because of size. With NTFS it worked. --> I try format to exFat
Click to expand...
Click to collapse
Maybe to late to use dload as i don't think flashing dload nougat over oreo will work.
And the only public dload service repair firmware available seems to be only nougat.
And downgrading is maybe not usefull as it seems there is a simple fix for you now by flashing kernel...
andryuxa20081 said:
I downloaded a full-service-repair-package for europe from the site 4pda.ru.
Click to expand...
Click to collapse
What version ? What region ? L09CxxxBxxx ?
andryuxa20081 said:
Should I use Firmware finder?
Click to expand...
Click to collapse
No, not in your case.
I think FF won't help for downgrading.
And again, i think you don't need anymore.
andryuxa20081 said:
What do you mean with "which HWOTA fileS? --> update.zip / update_full_data.zit and a third one..... comlete package, as described.
Click to expand...
Click to collapse
No, I meant where did you get your hwota8.rar from ?
Where you using the new one for oreo or the old one for nougat ?
So for you the better will be to flash kernel fix : https://forum.xda-developers.com/newreply.php?do=newreply&p=75772700
Help yourself, follow the instructions and don't try to install it over TWRP as you did before.

oslo83 said:
So, STF-L09CxxxB360.
What's your region ? C432, C10, ...?
No, I meant where did you get your hwota8.rar from ?
Where you using the new one for oreo or the old one for nougat ?
So for you the better will be to flash kernel fix : https://forum.xda-developers.com/newreply.php?do=newreply&p=75772700
Help yourself, follow the instructions and don't try to install it over TWRP as you did before.
Click to expand...
Click to collapse
What's your region ? C432, C10, ...?
Build Nr. STF-L09 8.0.0.360(C432)
No, I meant where did you get your hwota8.rar from ?
I got the HWOTA_base.zip from here "https://4pda.ru/forum/index.php?showtopic=793006&st=920#entry60779691"
Where you using the new one for oreo or the old one for nougat ?
I think that I used one for Nougat...... :-/
There is nowhere a note where to flash this kernel to? --> boot?, recovery_ramdisk? Splash? system? cache?
Do you perhaps know which flash directory should I use?

[Q]How to change root from phh.superuser to Magisk and upgrade firmware?

Hi Guys, I've been an active user of XDA in the past but didn't have time to follow in the last couple of years so my memory about flashing and tinkering is quite blank.
Here is my situation:
Mate 9 MHA-L29C636B158 (very old ROM)
Bootloader unlocked with paid code from dc-unlocker
Rooted with PHH's Superuser (the only root that was available for our device back in March 2017)
EMUI 5.0 and Android 7.0 (that was obvious from my Build number but I just wanted to state it again)
TWRP 3.0.2-2 is installed with system kept read-only. Internal SD seems to be encrypted
I never took any OTAs as I was afraid that they would break something
In the last month's many of my banking or financial apps have stopped working because I'm rooted so I read that Magisk would be able to circumvent this safetynet thing and would allow me to continue using these apps. Google Pay would be a nice addition also.
At this point I would like to upgrade my firmware and get rid of PHH's Superuser switching to Magisk instead
Could someone please write a detailed guide how to do that? It might be interesting for other users also that are in my same situation. I'm willing to donate a few bucks for a complete and foolproof guide.
Thanks a lot

itenos said:
Hi Guys, I've been an active user of XDA in the past but didn't have time to follow in the last couple of years so my memory about flashing and tinkering is quite blank.
Here is my situation:
Mate 9 MHA-L29C636B158 (very old ROM)
Bootloader unlocked with paid code from dc-unlocker
Rooted with PHH's Superuser (the only root that was available for our device back in March 2017)
EMUI 5.0 and Android 7.0 (that was obvious from my Build number but I just wanted to state it again)
TWRP 3.0.2-2 is installed with system kept read-only. Internal SD seems to be encrypted
I never took any OTAs as I was afraid that they would break something
In the last month's many of my banking or financial apps have stopped working because I'm rooted so I read that Magisk would be able to circumvent this safetynet thing and would allow me to continue using these apps. Google Pay would be a nice addition also.
At this point I would like to upgrade my firmware and get rid of PHH's Superuser switching to Magisk instead
Could someone please write a detailed guide how to do that? It might be interesting for other users also that are in my same situation. I'm willing to donate a few bucks for a complete and foolproof guide.
Thanks a lot
Click to expand...
Click to collapse
Do you still have the unlock code? You'll want it, as the update from EMUI 5 to EMUI 8, on every device I've got, has relocked the bootloader.
With that said:
If you want to keep your data, make a backup using Hisuite.
Download the FullOTA firmware for your current version. Extract system, boot, recovery, recovery2 (as you're on EMUI 5) and flash them either in TWRP or fastboot; that should eliminate PHH SU and TWRP, and ultimately leave the system in a clean state.
If you modified other partitions on the device using TWRP or su in general, it wouldn't be a bad idea to use a nocheck recovery or HuRupdater to flash the entire system, to leave everything in a pristine state, since there are partitions you can't flash with fastboot, even with an unlocked bootloader. The instructions for HuR can be found elsewhere on XDA, as can details about nocheck recoveries, though the latter I'd be careful with - using HWOTA7 on Oreo, for example, WILL cause a brick. You've been warned.
Start the update process - you've already been approved for OTAs and they've been offered, so they should happen automatically. When Oreo is installed, it'll automatically relock your bootloader; you can continue updating here, though if you've got a particular target you want to go to, you might want to unlock and use HuR again to flash that specific one now that you're on Oreo. (The latest firmwares can't be rolled back to Nougat.) If you have no intention of going back to Nougat, you have your unlock code, and you aren't planning to do any other modifications like rebranding, then update away, though you may want to hold off of the Pie update if offered. (Shouldn't be, yet, but it could have been approved for your device already; it changes the boot partitions yet again.)
Now that you're on Oreo and presumably unlocked again, make sure you've got the FullOTA image downloaded for that firmware to your PC. (Always a good idea, anyway.)
Magisk can be installed by:
1) Flashing TWRP with fastboot, then flashing a suitable Magisk zip
2) Using Magisk Manager to patch a boot image and flashing that.
For TWRP:
Get a copy of TWRP from the forum here. When I use one, it's the 3.2.1-0 from @Pretoriano80, you'll find it in the development section. Any 3.2.x for Oreo should work though - a Nougat TWRP will not work.
Flash TWRP to recovery_ramdisk in fastboot. Boot to TWRP, flash Magisk.
For Magisk Manager:
Extract "ramdisk" from your FullOTA firmware. Place it in internal storage on your device. Use Magisk Manager to patch the image (install / patch boot image). Transfer the patched_boot.img created by Magisk back to your PC and flash that to the "ramdisk" partition in fastboot.

Just stumbled over your reply, didn't get an email notification from XDA. Thank you so much. Let's see if I can follow your instructions.
irony_delerium said:
Do you still have the unlock code? You'll want it, as the update from EMUI 5 to EMUI 8, on every device I've got, has relocked the bootloader.
Click to expand...
Click to collapse
Yes, I still have the code
irony_delerium said:
With that said:
If you want to keep your data, make a backup using Hisuite.
Click to expand...
Click to collapse
Done
irony_delerium said:
Download the FullOTA firmware for your current version. Extract system, boot, recovery, recovery2 (as you're on EMUI 5) and flash them either in TWRP or fastboot; that should eliminate PHH SU and TWRP, and ultimately leave the system in a clean state.
Click to expand...
Click to collapse
I downloaded the FullOTA with the FirmwareFinder app on my phone and transferred it to my laptop. Extracted the update.app with WinRAR and extracted system, boot, recovery and recovery2 using the Huawei Update Extractor 0.9.9.3.
Just to make no mistake, could you please confirm the order of flashing these 4 files? And maybe the correct command to use in fastboot?
irony_delerium said:
If you modified other partitions on the device using TWRP or su in general, it wouldn't be a bad idea to use a nocheck recovery or HuRupdater to flash the entire system, to leave everything in a pristine state, since there are partitions you can't flash with fastboot, even with an unlocked bootloader. The instructions for HuR can be found elsewhere on XDA, as can details about nocheck recoveries, though the latter I'd be careful with - using HWOTA7 on Oreo, for example, WILL cause a brick. You've been warned.
Click to expand...
Click to collapse
I don't think that I modified any other partitions, at least not willingly. I even left the system in read-only state. Don't know if phh.su did something by itself?
irony_delerium said:
Start the update process - you've already been approved for OTAs and they've been offered, so they should happen automatically. When Oreo is installed, it'll automatically relock your bootloader; you can continue updating here, though if you've got a particular target you want to go to, you might want to unlock and use HuR again to flash that specific one now that you're on Oreo. (The latest firmwares can't be rolled back to Nougat.) If you have no intention of going back to Nougat, you have your unlock code, and you aren't planning to do any other modifications like rebranding, then update away, though you may want to hold off of the Pie update if offered. (Shouldn't be, yet, but it could have been approved for your device already; it changes the boot partitions yet again.)
Now that you're on Oreo and presumably unlocked again, make sure you've got the FullOTA image downloaded for that firmware to your PC. (Always a good idea, anyway.)
Magisk can be installed by:
1) Flashing TWRP with fastboot, then flashing a suitable Magisk zip
2) Using Magisk Manager to patch a boot image and flashing that.
For TWRP:
Get a copy of TWRP from the forum here. When I use one, it's the 3.2.1-0 from @Pretoriano80, you'll find it in the development section. Any 3.2.x for Oreo should work though - a Nougat TWRP will not work.
Flash TWRP to recovery_ramdisk in fastboot. Boot to TWRP, flash Magisk.
For Magisk Manager:
Extract "ramdisk" from your FullOTA firmware. Place it in internal storage on your device. Use Magisk Manager to patch the image (install / patch boot image). Transfer the patched_boot.img created by Magisk back to your PC and flash that to the "ramdisk" partition in fastboot.
Click to expand...
Click to collapse
Will continue to do the above after your kind confirmation of my last questions. Thanks again

itenos said:
I downloaded the FullOTA with the FirmwareFinder app on my phone and transferred it to my laptop. Extracted the update.app with WinRAR and extracted system, boot, recovery and recovery2 using the Huawei Update Extractor 0.9.9.3.
Just to make no mistake, could you please confirm the order of flashing these 4 files? And maybe the correct command to use in fastboot?
Click to expand...
Click to collapse
The order shouldn't be particularly relevant, just that it's safest to reflash all of them:
- boot because phhsu may have modified the boot image to add su to it
- recovery and recovery2 because you loaded TWRP. recovery2 is specified because it's used to be recommended to flash to erecovery as well as normal recovery.
- system because I'm pretty sure that's the biggest thing modified Hy phhsu, and any other system changes you may have made.
Theoretically, other modified partitions won't matter since the upgrade to 8.0 replaces most (all, I think) of them anyway, but if you have to go through update steps through EMUI 5 first before it'll give you 8, then it's safest that they aren't modified. I mentioned other partitions because, with root & TWRP, you technically could have modified any and all of them.

irony_delerium said:
Download the FullOTA firmware for your current version. Extract system, boot, recovery, recovery2 (as you're on EMUI 5) and flash them either in TWRP or fastboot; that should eliminate PHH SU and TWRP, and ultimately leave the system in a clean state.
Start the update process - you've already been approved for OTAs and they've been offered, so they should happen automatically.
Click to expand...
Click to collapse
Flashing of 158 (original ROM version) went fine. Phone rebooted and titanium reported no root access, so it looks good.
After that I started the OTA update to 172 that waited already long time in my settings and it downloaded it. After downloading it gave me an error during the validation process of the file and asked to download it again.
Unfortunately now both the phone updater and the HiSuite app on my laptop say that 158 is the latest available firmware and no update is available.
I guess that I can download directly the newer firmware but I'm not exactly sure how to flash the whole package and what I should do with the other 2 files that come with it besides the update.zip

itenos said:
Flashing of 158 (original ROM version) went fine. Phone rebooted and titanium reported no root access, so it looks good.
After that I started the OTA update to 172 that waited already long time in my settings and it downloaded it. After downloading it gave me an error during the validation process of the file and asked to download it again.
Unfortunately now both the phone updater and the HiSuite app on my laptop say that 158 is the latest available firmware and no update is available.
I guess that I can download directly the newer firmware but I'm not exactly sure how to flash the whole package and what I should do with the other 2 files that come with it besides the update.zip
Click to expand...
Click to collapse
It might be tweaking out about the fact that you'd previously modified system.
I'd grab the last Nougat release (looks like 191; there are 2 of them, be sure it's not the rollback one you grab) and use hurupdater in TWRP to install it, then let the system try running OTA again.

irony_delerium said:
It might be tweaking out about the fact that you'd previously modified system.
I'd grab the last Nougat release (looks like 191; there are 2 of them, be sure it's not the rollback one you grab) and use hurupdater in TWRP to install it, then let the system try running OTA again.
Click to expand...
Click to collapse
I had to insert the SIM card of the country I bought my phone in to get the OTAs coming. Luckily I still had it with a few $ credit on it. It used just a few cents in data roaming for finding the new firmware, then I downloaded through wifi.
After 4 updates now I'm on 378 and no sign of Pie yet so this afternoon if I find some time I'll continue with rooting.

itenos said:
I had to insert the SIM card of the country I bought my phone in to get the OTAs coming. Luckily I still had it with a few $ credit on it. It used just a few cents in data roaming for finding the new firmware, then I downloaded through wifi.
After 4 updates now I'm on 378 and no sign of Pie yet so this afternoon if I find some time I'll continue with rooting.
Click to expand...
Click to collapse
Easy way:
Unlock phone, if you haven't yet again.
Download and flash TWRP from here: https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3783353 (has decryption support) (flash to recovery_ramdisk as Huawei decided to split recovery partition into different parts)
Boot to TWRP, input pin (if you set a pin, else it will decrypt automatically)
Download Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Transfer Magisk to phone.
Flash Magisk zip in TWRP.
Reboot and you're done.
You might have to tinker around with Magisk Hide and hide apps if your banking apps still detect root.

As the Huawei Backup took over 4 hours to finish and i can't use Titanium, which is much faster, because I'm not rooted at the moment, I thought it's a good idea to first upgrade to Pie before unlocking my bootloader and losing all data. If I need to stay a few days without root it's ok.
Is there any way to get to Pie without being rooted? I tried the erecovery method on firmware finder. It says that my IMEI is now registered to download the update but when I enter erecovery it starts downloading the 378 oreo package.
I would like to avoid backing up and restoring twice this lengthy process, probably 16 hours all in all

itenos said:
As the Huawei Backup took over 4 hours to finish and i can't use Titanium, which is much faster, because I'm not rooted at the moment, I thought it's a good idea to first upgrade to Pie before unlocking my bootloader and losing all data. If I need to stay a few days without root it's ok.
Is there any way to get to Pie without being rooted? I tried the erecovery method on firmware finder. It says that my IMEI is now registered to download the update but when I enter erecovery it starts downloading the 378 oreo package.
I would like to avoid backing up and restoring twice this lengthy process, probably 16 hours all in all
Click to expand...
Click to collapse
The erecovery method won't work unless you can change the DNS settings on the network being used - it hijacks some of the requests to Huawei's servers to force the update. (And even then it's a bit finicky; I have yet to successfully use it, all things considered.)

Yesterday I finally received 9.0.1.159 with EMUI 9.0.1 by OTA. It installed fine and it's amazing how fast my phone became and how much screen on time I have now with my 2 year old device (8 full hours!). Good job Google and Huawei.
Being on Pie now I suppose that the instructions to root from you and ante0 are not valid anymore as they were meant for Oreo.
Could you please modify the instructions for Pie? And further, as I see that since yesterday in FirmwareFinder a new Pie update 9.0.1.178 popped up, could you please also add instructions how to take this OTA being rooted with Magisk once it arrives?
I've read a bit in the Magisk thread but I did not really understand the part of having to boot to recovery everytime I switch on the phone. Further they are talking there about EMUI 9 but I have already 9.0.1, is there maybe a difference I have to take care about?
Last but not least, I didn't forget my initial promise to donate a few bucks for the detailed instructions so please drop me your email in PM and I'll sent you a few through PayPal or in alternative, if you have some paid apps on the Playstore I could buy them so they might get more visibility.

itenos said:
Yesterday I finally received 9.0.1.159 with EMUI 9.0.1 by OTA. It installed fine and it's amazing how fast my phone became and how much screen on time I have now with my 2 year old device (8 full hours!). Good job Google and Huawei.
Being on Pie now I suppose that the instructions to root from you and ante0 are not valid anymore as they were meant for Oreo.
Could you please modify the instructions for Pie? And further, as I see that since yesterday in FirmwareFinder a new Pie update 9.0.1.178 popped up, could you please also add instructions how to take this OTA being rooted with Magisk once it arrives?
I've read a bit in the Magisk thread but I did not really understand the part of having to boot to recovery everytime I switch on the phone. Further they are talking there about EMUI 9 but I have already 9.0.1, is there maybe a difference I have to take care about?
Last but not least, I didn't forget my initial promise to donate a few bucks for the detailed instructions so please drop me your email in PM and I'll sent you a few through PayPal or in alternative, if you have some paid apps on the Playstore I could buy them so they might get more visibility.
Click to expand...
Click to collapse
The reason recovery boot is needed for Pie is because Huawei removed the ramdisk - in Pie, it's system as root with no way of forcing a ramdisk except by a recovery boot. So as a workaround, Magisk takes over recovery.
The installation instructions for it on Pie are pretty much the same as Oreo, except:
* Patch recovery_ramdisk, not ramdisk. Latest stable Magisk should work (18.1, iirc, has the patches to support recovery boot.)
* When booting, go to recovery. Magisk will start from there and take over the startup process.

irony_delerium said:
The installation instructions for it on Pie are pretty much the same as Oreo, except:
Click to expand...
Click to collapse
Hmm, where do I find the TWRP for Pie in order to flash?
And most importantly how do I have to behave in case of new OTAs coming?

itenos said:
Hmm, where do I find the TWRP for Pie in order to flash?
And most importantly how do I have to behave in case of new OTAs coming?
Click to expand...
Click to collapse
TWRP on this case, don't bother.
Extract your stock recovery from your firmware's update.app file, patch with Magisk Manager, and flash the patched image. When you want to flash an ota, put the stock recovery back.

[NEED HELP] Unbrick Honor 6x

I've somehow bricked my 6X.
I have an EU version successfully debranded to India variant BLN-L22 and upgraded to EMUI 8.0, unencrypted and rooted with Magisk.
Something went wrong during the flash of AEX for hi6250 devices (which is reported to be 6X compatible ): I was mainly stuck in a bootloop except for two times when the phone booted, but internal storage wasn't recognized properly (in settings I was able to see the correct percentage of available space but in default file manager I wasn't able to access it and also downloading files to internal storage was impossible, as if my it was full - which isn't true since I was able to move file there through TWRP file manager).
At that point I was pretty pissed, I've forced fastboot and used update.bat to flash stock Oreo again and here things screwed up.
I took a full TWRP backup before experimenting with AEX and copied it to my pc; I'm able to push it to internal storage through adb, but then TWRP isn't able to restore it, dunno why.
My phone is in these condition now:
fastboot is available, commands from pc are working here
bootloader is unlocked
FRP is unlocked
I have a working TWRP recovery (askuccio 3.2.3) which I can access and use; I'm able to replace it with Elemental 3.2.1, with the one provided in the "update.bat" thread (which is another 3.2.1 version) or with stock recovery
if I replace TWRP with stock recovery and boot into it, it shows the update screen and it freeze at 5%, then reboot; no factory reset option there
when I'm into TWRP I can push files from pc to internal memory through adb
pretty sure my phone is still decrypted, dunno if it's still rooted tho
eRecovery is gone
I have no idea how eRecovery gone missing since I never touched that partition; trying to flash ERECOVERY_RAMDISK.img through fastboot using "fastboot flash erecovery_ramdisk erecovery_ramdisk.img" which fails (remote: command not allowed) and "fastboot flash recovery2 erecovery_ramdisk.img" which fails (remote: partition length get error) as well as through Multi Tool (the size or path does not match the file system markup); if I try to boot into eRecovery I get error mode screen: Func NO : 11 (recovery image) Error No : 2 (load failed) and I have no idea how to try to restore it in another way (pretty sure all I need is to factory reset through it and then reflash the firmware for unbrick my phone).
Atm I've tried only Multi Tool: I can successfully flash everything in the unbrick section but it doesn't solve my problem (guess it's due to my missing eRecovery).
I still need to try Image Download method (which I would like to keep it as last resource since it requires to disassemble my device and since I have a working fastboot and TWRP), HuRu and dload (I don't have a micro SD big enough atm, only 2GB - dunno if it can can work from internal storage the same).
Thank you for any help.
@player615 @shashank1320 @vovan1982 @RedSkull23

I would say the safest option you have is to restore to Nougat via dloading the b340 image which you might have used for debranding. You should be able to restore easily.

shashank1320 said:
I would say the safest option you have is to restore to Nougat via dloading the b340 image which you might have used for debranding. You should be able to restore easily.
Click to expand...
Click to collapse
How do I do that?
I mean, flash OEMINFO and Custom Bin and then dload method as per debranding guide or HWOTA7, since I'm on Oreo/Emui8 now?

You already debrnaded to Indian version and then updated to Oreo right?

shashank1320 said:
You already debrnaded to Indian version and then updated to Oreo right?
Click to expand...
Click to collapse
Exactly. I was on BLN-L21 Nougat (EU), debranded to BLN-L22 (Indian) through fast method (flash oem and cust bin, dload, update through system update) and then upgraded to Oreo through HWOTA8_BLN - script method.
Multi Tool list my device as BLN-L22 8.0.0.510(C675).

Just dload b340 indian variant. You should be fine

I restored my device countless times with HuRUpdater, the best tool I used on Huawei devices. It always go fine, but a microSD of at least 3GB is required (files to flash are usually 2,70GB). Probably the device won't boot with stock recovery because as you pointed out, it needs to format first before booting since that you was decrypted. HuRUpdater needs to be executed from microSD because it flashes files from there to internal storage, so flashing from there isn't allowed due obvious reasons.
Looks like you'll need to dload, as my friend Shashank1320 said. You need to start again with a fully working system before going elsewhere and at the moment things look bad. The rest is always obtainable again (TWRP, ecc.)

shashank1320 said:
Just dload b340 indian variant. You should be fine
Click to expand...
Click to collapse
RedSkull23 said:
Looks like you'll need to dload, as my friend Shashank1320 said. You need to start again with a fully working system before going elsewhere and at the moment things look bad. The rest is always obtainable again (TWRP, ecc.)
Click to expand...
Click to collapse
dload doesn't work, I guess it's because I miss eRecovery.
If I hold vol+ vol- and power my phone boot into TWRP; I've tried replacing it with stock recovery but it freeze at 5%.
Any way to flash eRecovery from fastboot or as a zip from TWRP?
Gonna get a SD and for HuRu if I won't be able to solve it differently.
Edit: managed to boot into dload screen, but it states "software install failed".

AleNonsense said:
Edit: managed to boot into dload screen, but it states "software install failed".
Click to expand...
Click to collapse
That message is because the package you picked is wrong. What was your build number, BLNL22C636B510CUST..? (Don't remember if this is the build of first Indian Oreo build dated June/July 2018)

RedSkull23 said:
That message is because the package you picked is wrong. What was your build number, BLNL22C636B510CUST..? (Don't remember if this is the build of first Indian Oreo build dated June/July 2018)
Click to expand...
Click to collapse
I'm not sure since I don't have my device at hand atm: yesterday I got a 16GB SD and tried with HuRU but without success (trying to flash the zip returned me an error with every version of the package), so I contacted the assistance since I still have some months of warranty. I've tried to restore it as stock as possible before handling them the phone so I hope they won't make me trouble and fix it :angel:
Anyway I've always used firmware provided by shashank, both to debrand to indian variant and to upgrade to Oreo, so you may recover build number from those threads for scientific purposes!

AleNonsense said:
I'm not sure since I don't have my device at hand atm: yesterday I got a 16GB SD and tried with HuRU but without success (trying to flash the zip returned me an error with every version of the package), so I contacted the assistance since I still have some months of warranty. I've tried to restore it as stock as possible before handling them the phone so I hope they won't make me trouble and fix it :angel:
Anyway I've always used firmware provided by shashank, both to debrand to indian variant and to upgrade to Oreo, so you may recover build number from those threads for scientific purposes!
Click to expand...
Click to collapse
For me HuRUpdater never failed a shot, you just have to choose the correct build and rename the zips as per instructions in OP. Usually the zips are three, by the way. "BLN-L22HNC675CUSTC675D1B510 (8.0.0.510)" is the correct build number for Oreo India, if you use HuRU with the three zips included in this build the successful flash is guaranteed (done it personally many, many times).
Now, if you contacted assistance and you can take advantage of remaining months of warranty wait and see what they say. Good luck!

Reflash EMUI 8 with Hwota 8, but first wipe data partition with TWRP.

player615 said:
Reflash EMUI 8 with Hwota 8, but first wipe data partition with TWRP.
Click to expand...
Click to collapse
Wait: wiping /data with TWRP makes it visible through custom recoveries since that it removes encryption, but when you flash whole EMUI 8 on system stock recovery_ramdisk is reflashed on the recovery partition too, and it forces to reformat /data before booting because if not it'll say that OS is seriously corrupted bla bla bla... EMUI 8 doesn't have to run encrypted?
By the way HuRU is faster, easier and leaves bootloader unlocked.

RedSkull23 said:
If you use HuRU with the three zips included in this build the successful flash is guaranteed (done it personally many, many times).
Click to expand...
Click to collapse
Nope: don't get me wrong, but I'm here since 2012 and I'm pretty used to this kind of stuff.
I can assure you I haven't picked wrong packages nor any other noobish error: in fact I wouldn't even had to post here if I had encountered just some standard problem lol... my device wasn't fixable through usual ways, or else I would have been able to
RedSkull23 said:
Now, if you contacted assistance and you can take advantage of remaining months of warranty wait and see what they say. Good luck!
Click to expand...
Click to collapse
Just heard back from assistance and they are waiting for a new motherboard since there was nothing to do, good to me I was still covered by warranty.
Now it would be nice to know what screwed up my device so bad, since I hadn't any problem till the flash of AEX for hi6250 devices (so 6X compatible) and even in the case it wasn't flashing a wrong rom has never fked up a motherboard in my experience, but whatever.
My only trouble is I'm pretty sure I won't be able to unlock bootloader when my phone will be back, now
Also, thank you to everyone who tried to help!

try this
i had issues also until i found this step by step, i named everything just as he has pictured and made sure to just add the .zips all 3 needed, got correct FW from FW finder and also be sure to put the actual HuRuUpdater.zip in the same folder with the FW files and name the parent folder just like the pic on post shows...poof working stock FW and did not relock my BL....Honor 8 FRD-L04 reverted from no OS to stock 7.0 on EMUI 5 https://www.getdroidtips.com/hurupdater-tool/#comment-109621
RedSkull23 said:
For me HuRUpdater never failed a shot, you just have to choose the correct build and rename the zips as per instructions in OP. Usually the zips are three, by the way. "BLN-L22HNC675CUSTC675D1B510 (8.0.0.510)" is the correct build number for Oreo India, if you use HuRU with the three zips included in this build the successful flash is guaranteed (done it personally many, many times).
Now, if you contacted assistance and you can take advantage of remaining months of warranty wait and see what they say. Good luck!
Click to expand...
Click to collapse

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