Database Info

TWRP always says 'permission denied' & filenames are completely different

Hi,
I have a Mate 9 , Build No. MHA-L09C432B182
Baseband is 21.516.00.00.010
Kernel: 4.1.18-g0ad0fb3
I unlocked bootloader, it is defenetely unlocked. I am able to install TWRP.
I installed twrp-3.0.2 and also twrp-3.1.0 versions but have same problems in both versions:
filenames/folder names in /sdcard (internal storage) are broken, I mean their original names are gone, all files and folders are named like imbj9yf1fATc4Tvm5zt+ and so on instead of Screenshots for example.
So I cannot find my supersu.zip but however I think it would not install, because of this error:
Also I cannot run a TWRP backup, it shows:
Backup started
Backup Folder /data/media/0/TWRP/Backups/UGM2171100001069/2017-07-21-13-11-39_NRD90M...
Can not create '/data/media/0/TWRP' folder (Permission denied)
Failed to make backup folder
I tried to CHMOD 755 this folder/path, did not work/help
Can anybody help me here?
Thx and best!

/data is encrypted by default using file based encryption. That's why you see those files in /sdcard (/data/media/0/). You can remove encryption by using Wipe - 'Format Data' button.
This will remove everything in /data including your files in /sdcard.
To flash stuff you can use an external SD card or remove encryption or flash this twrp: https://mega.nz/#!xg9hWbpJ!dNOWJVUuD_4JL8N8PiDXYsj3SnvaOfKxBndvWc_4wgo
and adb push (adb push file.zip /cache/file.zip) to /cache and flash from there. /cache is added as storage with that twrp.
If you want to remove encryption, flash official SuperSU 2.82 SR1: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Or Magisk 13.3: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Both require at least twrp 3.1.0.
If you chose to remove encryption you will also have to flash public and HW zips after Format Data, because files in /data/hw_init are removed which are needed for themes to work and 'System Update' and a few Huawei apps.
Public zip for L09C432B182:
http://update.hicloud.com:8180/TDS/...55/f1/full/public/update_data_full_public.zip
Hw zip for L09C432B182: http://update.hicloud.com:8180/TDS/...04/v84355/f1/full/hw/eu/update_full_hw_eu.zip
Flash public first then hw. Both will give errors but install fine.
If you don't want to remove encryption you won't be able to backup /data.
If so use this SuperSU: https://mega.nz/#!18FW1QTQ!3DCA3KrIUSRqEu4L-expci4HcKtk6F25fE1u6ecJV9Q
Or magisk 13.3: https://mega.nz/#!I4FQzbyA!gBZelHmD3lGGwzGISUXkf7GQTUAq5i785d_qPHQOaVE

thanks for all your info.
Can you suggest what to do? Acutually I just want to install root to get titanium to work because I have older backups I want to look into to. After that I want to unroot again.
Not sure if i need encryption or if ishould decrypt now
Whats the best way for me now?

ante0 said:
/data is encrypted by default using file based encryption. That's why you see those files in /sdcard (/data/media/0/). You can remove encryption by using Wipe - 'Format Data' button.
This will remove everything in /data including your files in /sdcard.
To flash stuff you can use an external SD card or remove encryption or flash this twrp: https://mega.nz/#!xg9hWbpJ!dNOWJVUuD_4JL8N8PiDXYsj3SnvaOfKxBndvWc_4wgo
and adb push (adb push file.zip /cache/file.zip) to /cache and flash from there. /cache is added as storage with that twrp.
If you want to remove encryption, flash official SuperSU 2.82 SR1: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Or Magisk 13.3: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Both require at least twrp 3.1.0.
If you chose to remove encryption you will also have to flash public and HW zips after Format Data, because files in /data/hw_init are removed which are needed for themes to work and 'System Update' and a few Huawei apps.
Public zip for L09C432B182:
http://update.hicloud.com:8180/TDS/...55/f1/full/public/update_data_full_public.zip
Hw zip for L09C432B182: http://update.hicloud.com:8180/TDS/...04/v84355/f1/full/hw/eu/update_full_hw_eu.zip
Flash public first then hw. Both will give errors but install fine.
If you don't want to remove encryption you won't be able to backup /data.
If so use this SuperSU: https://mega.nz/#!18FW1QTQ!3DCA3KrIUSRqEu4L-expci4HcKtk6F25fE1u6ecJV9Q
Or magisk 13.3: https://mega.nz/#!I4FQzbyA!gBZelHmD3lGGwzGISUXkf7GQTUAq5i785d_qPHQOaVE
Click to expand...
Click to collapse
thanks for all your info.
Can you suggest what to do? Acutually I just want to install root to get titanium to work because I have older backups I want to look into to. After that I want to unroot again.
Not sure if i need encryption or if ishould decrypt now
Whats the best way for me now?

tobyffm said:
thanks for all your info.
Can you suggest what to do? Acutually I just want to install root to get titanium to work because I have older backups I want to look into to. After that I want to unroot again.
Not sure if i need encryption or if ishould decrypt now
Whats the best way for me now?
Click to expand...
Click to collapse
Then don't bother with decryption.
So you basically just have to place the root of your choice (of the mega ones I linked, because the official ones will remove encryption in your boot image and you will boot loop if you flash the official ones) on an external SD or transfer to /cache with adb after flashing the linked twrp. Then flash root and you're good to go.
I think you can sideload root zip, I haven't tried it. But that's another possibility if you don't have an external SD.

ante0 said:
Then don't bother with decryption.
So you basically just have to place the root of your choice (of the mega ones I linked, because the official ones will remove encryption in your boot image and you will boot loop if you flash the official ones) on an external SD or transfer to /cache with adb after flashing the linked twrp. Then flash root and you're good to go.
I think you can sideload root zip, I haven't tried it. But that's another possibility if you don't have an external SD.
Click to expand...
Click to collapse
Yes, it worked, i flashed supersu and got root acccess now, thx very much.
About unrooting later on, i understand I need to download the full stock rom, create a dload folder and copy update.app into it and reboot phone to download mode. It then will install stock rom and stock recovery, correct?
Will this erase internal storage again same like when unlocking bootloader?
thx!

tobyffm said:
Yes, it worked, i flashed supersu and got root acccess now, thx very much.
About unrooting later on, i understand I need to download the full stock rom, create a dload folder and copy update.app into it and reboot phone to download mode. It then will install stock rom and stock recovery, correct?
Will this erase internal storage again same like when unlocking bootloader?
thx!
Click to expand...
Click to collapse
No need (dload doesn't work anyway, except for AL00C00B115 and L29C636B136). You can uninstall using the SuperSU app or manually by removing /data/SuperSU.apk and restoring stock boot image. Boot image can be extracted from update.app for your model using Huawei Update extractor. Same goes for recovery. If you want to lock bootloader you have to install an update/same build number, you could use Firmware Finder for that or this tool: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
In my experience it will not remove apps, but data seems to go poof (as in app settings and data). Unlocking bootloader again will remove apps though as it does a factory reset.

ante0 said:
/data is encrypted by default using file based encryption. That's why you see those files in /sdcard (/data/media/0/). You can remove encryption by using Wipe - 'Format Data' button.
This will remove everything in /data including your files in /sdcard.
To flash stuff you can use an external SD card or remove encryption or flash this twrp: https://mega.nz/#!xg9hWbpJ!dNOWJVUuD_4JL8N8PiDXYsj3SnvaOfKxBndvWc_4wgo
and adb push (adb push file.zip /cache/file.zip) to /cache and flash from there. /cache is added as storage with that twrp.
If you want to remove encryption, flash official SuperSU 2.82 SR1: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Or Magisk 13.3: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Both require at least twrp 3.1.0.
If you chose to remove encryption you will also have to flash public and HW zips after Format Data, because files in /data/hw_init are removed which are needed for themes to work and 'System Update' and a few Huawei apps.
Public zip for L09C432B182:
http://update.hicloud.com:8180/TDS/...55/f1/full/public/update_data_full_public.zip
Hw zip for L09C432B182: http://update.hicloud.com:8180/TDS/...04/v84355/f1/full/hw/eu/update_full_hw_eu.zip
Flash public first then hw. Both will give errors but install fine.
If you don't want to remove encryption you won't be able to backup /data.
If so use this SuperSU: https://mega.nz/#!18FW1QTQ!3DCA3KrIUSRqEu4L-expci4HcKtk6F25fE1u6ecJV9Q
Or magisk 13.3: https://mega.nz/#!I4FQzbyA!gBZelHmD3lGGwzGISUXkf7GQTUAq5i785d_qPHQOaVE
Click to expand...
Click to collapse
hi,
thx for your last reply!
I am still on root status. I needed to decrypt now, thus I selected format data.
After that, files and folders are named correctly and I am able to create a backup.
I flashed public ziip, the other one was corrupt, mayve because of failed download, however as I understand it is not the reason why it always goes back to encryption, isn't it?
But: Once I reboot to Android and go back to recovery it is encrypted again?
My current problem is: I need to move a TWRP backup to internal storage and run TWRP restore feature from recovery, but it is encrypted. Once I format data it is decrypted but internal storage empty again. So I reboot to Android (because mounting from within TWRP does not work )and put TWRP backup folder to internsal storage, but then I go back to recovery and see it is encrypted again :S like driving in a circle ...
And I cannot put backup folder to external micro sd as it is too large for my small micro sd I have.
Do I need to flash a decrypted bootimage? If yes, which one?
Can you help me on this maybe?

tobyffm said:
hi,
thx for your last reply!
I am still on root status. I needed to decrypt now, thus I selected format data.
After that, files and folders are named correctly and I am able to create a backup.
I flashed public ziip, the other one was corrupt, mayve because of failed download, however as I understand it is not the reason why it always goes back to encryption, isn't it?
But: Once I reboot to Android and go back to recovery it is encrypted again?
My current problem is: I need to move a TWRP backup to internal storage and run TWRP restore feature from recovery, but it is encrypted. Once I format data it is decrypted but internal storage empty again. So I reboot to Android (because mounting from within TWRP does not work )and put TWRP backup folder to internsal storage, but then I go back to recovery and see it is encrypted again :S like driving in a circle ...
And I cannot put backup folder to external micro sd as it is too large for my small micro sd I have.
Do I need to flash a decrypted bootimage? If yes, which one?
Can you help me on this maybe?
Click to expand...
Click to collapse
'Format Data', flash official Magisk 13.3 or SuperSU 2.82 SR1 (mine from mega doesn't remove encryption), flash public zip, flash HW zip. It should now stay decrypted. You might have to go back to TWRP start screen after Format, then select 'Reboot' - 'Reboot Recovery' if it doesn't want to mount /data after Format.
Rebooting to system after formatting but not flashing magisk or supersu will encrypt again.
I can make a decrypted boot image if it doesn't want to stay decrypted.

ante0 said:
'Format Data', flash official Magisk 13.3 or SuperSU 2.82 SR1 (mine from mega doesn't remove encryption), flash public zip, flash HW zip. It should now stay decrypted. You might have to go back to TWRP start screen after Format, then select 'Reboot' - 'Reboot Recovery' if it doesn't want to mount /data after Format.
Rebooting to system after formatting but not flashing magisk or supersu will encrypt again.
I can make a decrypted boot image if it doesn't want to stay decrypted.
Click to expand...
Click to collapse
ok thx.
I redownloaded HW zip and checked md5 sum with the file from first attempt, same md5. However this is what i did:
Format data, tried to flash Magisk, but did not work, there was an error, this is why I flashed SuperSU 2.82 SR1 which worked with no errors. I flashed public zip right away, after that I flashed HW zip, but again, it did not work there were errors. However, encryption seems to be gone anyway. and yes, it keeps being decrypted.
I managed to get TWRP seeing an old TWRP Backup, which I pushed onto internal storage. I started restore of /data/ of that TWRP backup because I want to get the WhatsApp incl. data from data backup.
I booted up to Android and now I am faced with the next fuc*in problem: lock pattern of Dec 16. I cant remember and after few attemps devices is locked for 10 minutes, then for another 30 minutes ...
After google research it should be able to use Android device manager from a browser and to lock device and set a new pin/password to unlock the device. It is communicating as I can let the phone ring with no problem, but all how_tos show me this screen in android device manager interface
{
"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"
}
Of course it is me, who dont get this mask to set a new pin/password ( (
I only can enter an optional phone no and message from browser
Any idea what to do?
Update: I extracted whatsapp from backup with nandroid manager app but it did not restore my data correctly, best way would be to get done the pattern problem when restopring the twrp backup
redaring locking bootloader again:
I went to your link https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
they say to download file for own device here: http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=
I only find:
DUK-L09C432B182
But mine is MHA-L09C432B182, can I go forward with DUK-L09C432B182 anyway? Actually I dont understand what to do, their description is curios.

tobyffm said:
ok thx.
I redownloaded HW zip and checked md5 sum with the file from first attempt, same md5. However this is what i did:
Format data, tried to flash Magisk, but did not work, there was an error, this is why I flashed SuperSU 2.82 SR1 which worked with no errors. I flashed public zip right away, after that I flashed HW zip, but again, it did not work there were errors. However, encryption seems to be gone anyway. and yes, it keeps being decrypted.
I managed to get TWRP seeing an old TWRP Backup, which I pushed onto internal storage. I started restore of /data/ of that TWRP backup because I want to get the WhatsApp incl. data from data backup.
I booted up to Android and now I am faced with the next fuc*in problem: lock pattern of Dec 16. I cant remember and after few attemps devices is locked for 10 minutes, then for another 30 minutes ...
After google research it should be able to use Android device manager from a browser and to lock device and set a new pin/password to unlock the device. It is communicating as I can let the phone ring with no problem, but all how_tos show me this screen in android device manager interface
Of course it is me, who dont get this mask to set a new pin/password ( (
I only can enter an optional phone no and message from browser
Any idea what to do?
Update: I extracted whatsapp from backup with nandroid manager app but it did not restore my data correctly, best way would be to get done the pattern problem when restopring the twrp backup
redaring locking bootloader again:
I went to your link https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
they say to download file for own device here: http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=
I only find:
DUK-L09C432B182
But mine is MHA-L09C432B182, can I go forward with DUK-L09C432B182 anyway? Actually I dont understand what to do, their description is curios.
Click to expand...
Click to collapse
L09C432B156 firmware: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1366/g104/v84355/f1/full/update.zip
L09C432B182 public data zip:
http://update.hicloud.com:8180/TDS/...55/f1/full/public/update_data_full_public.zip
L09C432B182 hw data zip:
http://update.hicloud.com:8180/TDS/...04/v84355/f1/full/hw/eu/update_full_hw_eu.zip
You might as well update to B190 while you're at it..
L09C432B190: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1366/g104/v89786/f1/full/update.zip
L09C432B190 public data zip:
http://update.hicloud.com:8180/TDS/...86/f1/full/public/update_data_full_public.zip
L09C432B190 hw data zip: http://update.hicloud.com:8180/TDS/...l/MHA-L09_hw_eu/update_full_MHA-L09_hw_eu.zip
Rename public data zip to update_data_public.zip.
Rename hw data zip to update_all_hw.zip

ok, to summarize:
1) I download these 3 files:
full update.zip:
L09C432B190: http://update.hicloud.com:8180/TDS/d...ull/update.zip
L09C432B190 public data zip:
http://update.hiclod.com:8180/TDS/d...ull_public.zip
L09C432B190 hw data zip:
http://update.hicloud.com:8180/TDS/d...-L09_hw_eu.zip
2) I extract recovery img file from update zip
3) I uninstall root from within super su app.
4) I rename zip files and flash public zip as well as hw zip from within twrp recovery
5) i put extraced recovery img to device by using "fastboot flash recovery "
Will it work like this? Or do I need to flash public and hw first and after that uninstall root from supersu?
and then in the end "fastboot oem lock" ? to get the bootloader locked and to switch off the boot message "your device cant be trusted" ?
and: I couldnt flash hw zip before as it ended up with errrors, is this why I dont have Search for updates in EMUI 5.0 anymore?

tobyffm said:
ok, to summarize:
1) I download these 3 files:
full update.zip:
L09C432B190: http://update.hicloud.com:8180/TDS/d...ull/update.zip
L09C432B190 public data zip:
http://update.hiclod.com:8180/TDS/d...ull_public.zip
L09C432B190 hw data zip:
http://update.hicloud.com:8180/TDS/d...-L09_hw_eu.zip
2) I extract recovery img file from update zip
3) I uninstall root from within super su app.
4) I rename zip files and flash public zip as well as hw zip from within twrp recovery
5) i put extraced recovery img to device by using "fastboot flash recovery "
Will it work like this? Or do I need to flash public and hw first and after that uninstall root from supersu?
and then in the end "fastboot oem lock" ? to get the bootloader locked and to switch off the boot message "your device cant be trusted" ?
and: I couldnt flash hw zip before as it ended up with errrors, is this why I dont have Search for updates in EMUI 5.0 anymore?
Click to expand...
Click to collapse
No. Follow the guide you linked, that's where you use those files.
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
You could relock but it will say Bootloader Relocked instead of Bootloader Lock.
And if you don't plan on updating to B190 using the guide I suggest you download public and HW Data for B182 and flash those in twrp.
Can cause problems otherwise.
Flash public first. They will give errors because you're not supposed to flash them in twrp, they're official Huawei zips that are flashed using stock recovery.

ante0 said:
No. Follow the guide you linked, that's where you use those files.
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
You could relock but it will say Bootloader Relocked instead of Bootloader Lock.
And if you don't plan on updating to B190 using the guide I suggest you download public and HW Data for B182 and flash those in twrp.
Can cause problems otherwise.
Flash public first. They will give errors because you're not supposed to flash them in twrp, they're official Huawei zips that are flashed using stock recovery.
Click to expand...
Click to collapse
OK and why i currently dont see menue point "search for updates" in EMUI 5.0 ? Maybe i will stay rooted as I see that xposed has now been released.
But I want to receive official OTAs anyway, but currently the full menue point for searching for updates is gone. Any idea?

tobyffm said:
OK and why i currently dont see menue point "search for updates" in EMUI 5.0 ? Maybe i will stay rooted as I see that xposed has now been released.
But I want to receive official OTAs anyway, but currently the full menue point for searching for updates is gone. Any idea?
Click to expand...
Click to collapse
Did you flash back public and HW Data for B182?

ante0 said:
Did you flash back public and HW Data for B182?
Click to expand...
Click to collapse
I was not sure which was the last I flashed during last days, B182 or B190.
However, just redownload B182 files and flashed, first public, then hw zip.
Rebooted device, "search for updates" is available again, thank you very much
But it says B182 is latest update, so OTA not available for me so far yet. How can I manually flash to latest version B190 without loosing 'Search for Update' section?

tobyffm said:
I was not sure which was the last I flashed during last days, B182 or B190.
However, just redownload B182 files and flashed, first public, then hw zip.
Rebooted device, "search for updates" is available again, thank you very much
But it says B182 is latest update, so OTA not available for me so far yet. How can I manually flash to latest version B190 without loosing 'Search for Update' section?
Click to expand...
Click to collapse
You can with that guide i linked a couple of posts back. You can't flash update.zip in twrp, you have to use that guide to flash it. It's pretty straightforward. Download HWOTA BASE, HWOTA WINDOWS and HWOTA MHA (Mate 9), extract all to the same folder (C:\hwota is a good location). Download the files for B190 i linked a couple of posts back. Rename public data zip to update_data_public.zip.
Rename hw data zip to update_all_hw.zip, place them and update.zip in the update folder, run bat (if windows) or sh (Linux) then do what the prompts say. When it asks pick same brand update, then script update folder. It will transfer files for you. Bootloader will be locked when you're done.

ante0 said:
You can with that guide i linked a couple of posts back. You can't flash update.zip in twrp, you have to use that guide to flash it. It's pretty straightforward. Download HWOTA BASE, HWOTA WINDOWS and HWOTA MHA (Mate 9), extract all to the same folder (C:\hwota is a good location). Download the files for B190 i linked a couple of posts back. Rename public data zip to update_data_public.zip.
Rename hw data zip to update_all_hw.zip, place them and update.zip in the update folder, run bat (if windows) or sh (Linux) then do what the prompts say. When it asks pick same brand update, then script update folder. It will transfer files for you. Bootloader will be locked when you're done.
Click to expand...
Click to collapse
Did like described, when it comes to "update should install automatically" it reboots into erecovery, but Software install failed!
The update package does not exists please download the package again
But all 3 files are within the script folder and named correctly i think, pls see my attached screenshot

tobyffm said:
Did like described, when it comes to "update should install automatically" it reboots into erecovery, but Software install failed!
The update package does not exists please download the package again
But all 3 files are within the script folder and named correctly i think, pls see my attached screenshot
Click to expand...
Click to collapse
Are they in the update folder? I think I see the update.bat file there.
Put them in the update folder (for example c:\hwota\update\)

ante0 said:
Are they in the update folder? I think I see the update.bat file there.
Put them in the update folder (for example c:\hwota\update\)
Click to expand...
Click to collapse
yes, that was my fault.
Put to update folder and run again, update was running and finished with 100%. phone rebooted loaded very long. Now android is broken. I see my background image, but cannot do anything it is like hanging hanging hanging, everyhting very slow, like it is loading much of information. rebooted phone and waited some more time. seems now it is working and I am on B190. Now, i have to unlock bootloader again and install supersu again =)
thx for your help so far.
btw: u dont have any solution for my previous posted problem with my twrp backup, dont you? restoring twrp backup ends up in lock screen with pattern which I cant remember. Android Device Manager from PC browser can communictae with the phone but it does not offer me to set a new pin. Do you have any other method in mind how I can go on?

[GUIDE] Manual Update P20 PRO with HuRUpdater and TWRP

If you have unlocked bootloader and TWRP, you can flash a newer firmware using HuRUpdater
This steps can be risky for your device if you don't know what you are doing, so try to read some guide about flashing first
before attempt these operations if you are a new to these things.
I don't take any responsability of catastrophic failures and loss of data.
-- I did a titanium backup before the upgrade, but in my case no restore was needed as all data were retained.
In this simple update no factory reset was triggered.
Please read the HUrupdater thread also for more informations.
- Install Unofficial TWRP by Pretoriano80
- Download HuRUpdater 0.3 and put it in a folder in your sdcard
-Search the firmware for your device with Firmware Finder
Make sure you download the correct firmware version for your device (type, region code)
wrong firmware can brick your device
I used updated firmware files APPROVED for my device checked with firmware finder app.
I don't know if flashing NOT APPROVED files will harm your device. You have been warned.
I successfully updated my device from CLT-L29C636B130 to CLT-L29C636B131
***Don't try to rebrand your phone with this method***
- Use FullOTA-MF images of the firmware and download the 3 files needed
in my case:
update.zip
update_data_full_public.zip
update_full_CLT-L29_hw_spcseas.zip
- rename the 3 files to:
update.zip
update_data_public.zip
update_all_hw.zip
and put the files in the same folder with HuRUpdater 0.3
(optional)
- The Update will overwrite your TWRP custom recovery so to retain it automatically rename the TWRP IMAGE
twrp_clt_0.1.img to recovery.img and put in the same folder with others files.
{
"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"
}
- Remove all security locks from your phone before rebooting to TWRP.
Go to System- Developer Options
Disable Screen lock (third row)
this will suffice to remove the security locks of the phone (sequences, pin,fingerprints)
-Reboot to TWRP
If you are rooted, remove Magisk first with its uninstaller. I don't know if it's needed but better don't have things like that
messing around during the update. You can reroot later anyway.
-Go to the folder with the files and flash the system using the HuRUpdater_0.3.zip ONLY
That great tool will do all the job needed. After system, it will reflash the TWRP recovery IMG you previoulsly renamed
overwriting again the stock ramdisk_recovery that comes with the firmware.
It will take some minutes, don't panic and let the process end.
You will see some red errors but don't worry,it's fine
- Reboot in your TWRP to check (from inside TWRP , reboot - recovery, be sure not to have a usb cable plugged or it will trigger stock EMUI e-recovery)
- Wipe dalvik and cache
- Reroot new system with Magisk
-Reboot to system and restore the security lock in developer options
- Restore your fingerprints and pins
- Enjoy the update.
Thanks to @zxz0O0 for this great Tool, works good on P20 pro too.
And obviously @Pretoriano80 for his recovery.

Reserved

Working adb sideload?

If an update is already approved by Huawei, can we just download the firmware through HFF and place it in the appropriate folder, go to SYSTEM to check for updates, and then install it?
mangusZen said:
If you have unlocked bootloader and TWRP, you can flash a newer firmware using HuRUpdater
This steps can be risky for your device if you don't know what you are doing, so try to read some guide about flashing first
before attempt these operations if you are a new to these things.
I don't take any responsability of catastrophic failures and loss of data.
-- I did a titanium backup before the upgrade, but in my case no restore was needed as all data were retained.
In this simple update no factory reset was triggered.
Please read the HUrupdater thread also for more informations.
- Install Unofficial TWRP by Pretoriano80
- Download HuRUpdater 0.3 and put it in a folder in your sdcard
-Search the firmware for your device with Firmware Finder
Make sure you download the correct firmware version for your device (type, region code)
wrong firmware can brick your device
I used updated firmware files APPROVED for my device checked with firmware finder app.
I don't know if flashing NOT APPROVED files will harm your device. You have been warned.
I successfully updated my device from CLT-L29C636B130 to CLT-L29C636B131
***Don't try to rebrand your phone with this method***
- Use FullOTA-MF images of the firmware and download the 3 files needed
in my case:
update.zip
update_data_full_public.zip
update_full_CLT-L29_hw_spcseas.zip
- rename the 3 files to:
update.zip
update_data_public.zip
update_all_hw.zip
and put the files in the same folder with HuRUpdater 0.3
(optional)
- The Update will overwrite your TWRP custom recovery so to retain it automatically rename the TWRP IMAGE
twrp_clt_0.1.img to recovery.img and put in the same folder with others files.
- remove all security locks from your phone before rebooting to TWRP.
Go to System- Developer Options
Disable Screen lock (third row)
this will suffice to remove the security locks of the phone (sequences, pin,fingerprints)
-Reboot to TWRP
-If you are rooted, remove Magisk first with its uninstaller. I don't know if it's needed but better don't have things like that
messing around during the update. You can reroot later anyway.
-Go to the folder with the files and flash the system using the HuRUpdater_0.3.zip ONLY
That great tool will do all the job needed. After system, it will reflash the TWRP recovery IMG you previoulsly renamed
overwriting again the stock ramdisk_recovery that comes with the firmware.
- It will take some minutes, don't panic and let the process end.
You will see some red errors but don't worry,it's fine
- Reboot in your TWRP to check (from inside TWRP , reboot - recovery, be sure not to have a usb cable plugged or it will trigger stock EMUI e-recovery)
- Wipe dalvik and cache
- Reroot new system with Magisk 16.4
-Reboot to system and restore the security lock in developer options
- restore your fingerprints and pins
- enjoy the update.
Thanks to @zxz0O0 for this great Tool, works good on P20 pro too.
And obviously @Pretoriano80 for his recovery.
Click to expand...
Click to collapse

ekremxx said:
Working adb sideload?
Click to expand...
Click to collapse
I have not tried that, it depends on the TWRP recovery, let us know if you try

sarichter said:
If an update is already approved by Huawei, can we just download the firmware through HFF and place it in the appropriate folder, go to SYSTEM to check for updates, and then install it?
Click to expand...
Click to collapse
I really don't know, and I don't think it will work.
As far as I know this is the only manual update method for now.
I just updated to unapproved .150 for my c636 and all seems fine

If I reinstall twrp by renaming it as recovery.img, will HuRUupdater install the twrp in recovery_ramdisk, or will it replace eRecovery instead?
If twrp doesn't replace eRecovery, how do I get to eRecovery? As of now, whenever I want to enter recovery, it will get to twrp.

sishafie said:
If I reinstall twrp by renaming it as recovery.img, will HuRUupdater install the twrp in recovery_ramdisk, or will it replace eRecovery instead?
If twrp doesn't replace eRecovery, how do I get to eRecovery? As of now, whenever I want to enter recovery, it will get to twrp.
Click to expand...
Click to collapse
eRecovery is not replaced.
To enter there try other volume button or with a cable plugged

Not working adb sideload... How I can install I not know...not have my phone micro SD card slot...puff

sishafie said:
If I reinstall twrp by renaming it as recovery.img, will HuRUupdater install the twrp in recovery_ramdisk, or will it replace eRecovery instead?
If twrp doesn't replace eRecovery, how do I get to eRecovery? As of now, whenever I want to enter recovery, it will get to twrp.
Click to expand...
Click to collapse
when booting there is a screen prompting to whether you want to go to eRecovery by pressing up or just boot into system and something ike that
---------- Post added at 04:23 PM ---------- Previous post was at 04:23 PM ----------
ekremxx said:
Not working adb sideload... How I can install I not know...not have my phone micro SD card slot...puff
Click to expand...
Click to collapse
why you want to do sideload ? guide clearly explained to install it using TWRP.
if you dont have TWRP, then install it first

I install twrp but how can I install whitour sd card I not have sd card slot my Huawei p20 pro one SIM card join no have sd card slot how I can install i not know.. when I try install abd sideload hrudader say cant find update.zip
update_data_public.zip
update_all_hw.zip

ekremxx said:
I install twrp but how can I install whitour sd card I not have sd card slot my Huawei p20 pro one SIM card join no have sd card slot how I can install i not know.. when I try install abd sideload hrudader say cant find update.zip
update_data_public.zip
update_all_hw.zip
Click to expand...
Click to collapse
The guide never said that you need sdcard
it said, that u need to put all those three files in same folder with the HuruUpdater.zip , and of course you can put it in your internal storage
i wont explain anything here. you better re-read the whole main post, as it already very clear
- put all files in one folder
- reboot to twrp
- flash huruupdater.zip
- boot to system
- reboot to twrp
- flash magisk to reroot
which step exactly that not understandable ? :silly:

I can install that's style orjinal filmware ty so much

Forgive me if this is not the appropriate forum, one question:
I have the Huawei P20, for this phone I only have 2 firmware files, the "Update .zip" and the "update_full_EML_L09_hw_eu.zip ".
Can't find the "update_data_public.zip"
Can I install the new firmware with Hurupdater anyway ? Thanks in advance.
Roberto

moghetto said:
Forgive me if this is not the appropriate forum, one question:
I have the Huawei P20, for this phone I only have 2 firmware files, the "Update .zip" and the "update_full_EML_L09_hw_eu.zip ".
Can't find the "update_data_public.zip"
Can I install the new firmware with Hurupdater anyway ? Thanks in advance.
Roberto
Click to expand...
Click to collapse
You should check and ask at P20 and HURupdater threads.
I don't know about P20.

Hello! Thank you very much for this tutorial .. A question.. I am in Chipset-boston 8.1.0. 001 (01DL) I have the bootloader open, just by installing the recovery that you say in the tutorial and then the other steps, I would not have a problem, right?

can I downgrade firmware safely with this method? im on 150 and want to go back to 130

Ferezesal19 said:
Hello! Thank you very much for this tutorial .. A question.. I am in Chipset-boston 8.1.0. 001 (01DL) I have the bootloader open, just by installing the recovery that you say in the tutorial and then the other steps, I would not have a problem, right?
Click to expand...
Click to collapse
You should not have problem, unless you are trying to rebrand.

Allesa said:
can I downgrade firmware safely with this method? im on 150 and want to go back to 130
Click to expand...
Click to collapse
I don't know about downgrading and I would not raccomend it

mangusZen said:
You should not have problem, unless you are trying to rebrand.
Click to expand...
Click to collapse
Thanks you. Only i want to Update... What firm you recommend That improves the duration of the battery?

Tutorial : Decrypt And Flash Any ROM [ Working on Android 10 ][No data loss]

{
"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"
}
FLASHING INSTRUCTION :
Warning : Always Backup Your Internal Storage For safer side
Points to be Noted :
1 : Dirty Flashing sometime works. But might have hidden bugs.
2 : Remove the pattern and also fingerprints before flashing the rom.
3 : Always you have to flash twrp zip file after flashing rom. Else you will loose twrp.
If you are on some other twrp versions, Kindly download Compatible TWRP recovery IMG file from download Section and Flash it in recovery.
TWRP installer zip by mauronofrio - Supports Android 10
This works Fine. I recommend all to use this recovery.
To Decrypt Your Device : [ For First Time ]
Step 1: Place the Full ROM zip file in internal Storage.
Step 2: Now Reboot the phone to TWRP Recovery.
Step 3: Wipe Dalvik cache ,Data , System and Cache.
Step 4: Now select Full ROM zip file and swipe to flash it and then flash the twrp zip file again
Step 5: Format DATA and reboot to recovery.
Step 6: Now in recovery flash magisk 20.4
Step 7: Now Flash the No-verity file - Pie Supported here and Android 10 Supported from here[Important]
Step 8: Reboot the phone.
Step 9: Voila !! Now your device is successfully decrypted and
Now To Flash OOS updates in Your Decrypted Device : - Works For Android 10 Based OOS
Step 1: Place the Full OOS ROM zip file in internal Storage.
Step 2: Now Reboot the phone to TWRP Recovery.
Step 3: Wipe Dalvik cache ,Data , System and Cache.
Step 4: Now Flash OOS Zip and twrp zip file and reboot to recovery.
Step 5: Now in recovery flash magisk 20.4 only
Step 6: Now Flash the No-verity file - Pie Supported here and Android 10 Supported from here[Important]
Step 7: Reboot the phone. Now both TWRP and Magisk will be there and still your device is decrypted too with android 10
To Flash CustoM ROMs in Your Decrypted Device :
Step 1: Place the Full Custom ROM zip file and required base version Rom zip file ( I.e., OOS BETA OR OOS STABLE) in internal Storage.
Step 2: Now Reboot the phone to TWRP Recovery.
Step 3: Wipe Dalvik cache ,Data , System and Cache.
Step 4: Now Flash OOS Zip and twrp and reboot to recovery and Flash oos zip and twrp again and reboot to recovery. Now select Full Custom ROM zip file and swipe to flash.
Step 5: Flash the twrp zip file again and reboot to recovery.
Step 6: Now in recovery flash magisk 20.4
Step 7: Now Flash the No-verity file - Pie Supported here and Android 10 Supported from here[Important]
Step 8: Reboot the phone.
Credits : @topjohnwu, @virtyx and others .
@mauronofrio for his TWRP.

Download Section :
Recovery:
Official TWRP ||
Blu_Spark TWRP || Unofficial TWRP by joemossjr || TWRP installer zip by mauronofrio - Supports Android 10
For Root :
Magisk
To Decrypt :
No Verity Mod for OP6 ​

HatRiGt said:
Download Section :
Recovery:
Official TWRP ||
Blu_Spark TWRP || Unofficial TWRP by joemossjr
For Root :
Magisk
To Decrypt :
No Verity Mod for OP6 ​
Click to expand...
Click to collapse
Please excuse the dumb questions, I am new to these parts (Device Delivery for Tomorrow), but other then Treble and if TWRP isnt decrypting, why else would you want to decrypt your Device? And finally, the No-Verity MOD is the last part of the instructions, so my question is does the device automatically encrypt when all said and done?

Unlocked.Devices said:
Please excuse the dumb questions, I am new to these parts (Device Delivery for Tomorrow), but other then Treble and if TWRP isnt decrypting, why else would you want to decrypt your Device? And finally, the No-Verity MOD is the last part of the instructions, so my question is does the device automatically encrypt when all said and done?
Click to expand...
Click to collapse
keeping your device decrypt will make you to switch between any roms easily. You dont need to wipe internal storage thereafter.
Flashing Untouched OOS ROM will make your device to get force encrypt, so to avoid that you need to flash no verity mod .

I'm running oos 1.5.11 rooted with magisk 17.1 and twrp 3.2.3-0. can I flash this zip now without starting everything over? Sorry if this has already been asked.
---------- Post added at 08:29 PM ---------- Previous post was at 08:28 PM ----------
Oops....5.1.11

mixlex said:
I'm running oos 1.5.11 rooted with magisk 17.1 and twrp 3.2.3-0. can I flash this zip now without starting everything over? Sorry if this has already been asked.
---------- Post added at 08:29 PM ---------- Previous post was at 08:28 PM ----------
Oops....5.1.11
Click to expand...
Click to collapse
If your device is encrypted, first take backup of your internal storage and follow the steps in op

mixlex said:
I'm running oos 1.5.11 rooted with magisk 17.1 and twrp 3.2.3-0. can I flash this zip now without starting everything over? Sorry if this has already been asked.
---------- Post added at 08:29 PM ---------- Previous post was at 08:28 PM ----------
Oops....5.1.11
Click to expand...
Click to collapse
Sadly no. Data format is required to decrypt phone

m8, I don't get step 4 of decrypting device.
I select Full ROM and at the same time we Format Data?
Thanks for the guide!:good:

refedit said:
m8, I don't get step 4 of decrypting device.
I select Full ROM and at the same time we Format Data?
Thanks for the guide!:good:
Click to expand...
Click to collapse
First flash the rom and then format the data.

HatRiGt said:
First flash the rom and then format the data.
Click to expand...
Click to collapse
After formatting data I'm having issues mounting, I tried fastbooting twrp to get mounted to get files over(any chance this would mess anything up?).
Should the no verity mod always be flashed last and does it require a reflash after say flashing a kernel?

snigor said:
After formatting data I'm having issues mounting, I tried fastbooting twrp to get mounted to get files over(any chance this would mess anything up?).
Should the no verity mod always be flashed last and does it require a reflash after say flashing a kernel?
Click to expand...
Click to collapse
1) Actually never use that twrp that has support for MTP. Always use normal twrp.
If you have got any mounting issue, just flash the fastboot rom and then again boot to twrp and then follow the steps in OP carefully.
2) Yes no verity should be always flashed in the last before you boot into the system .
even if you flash kernel / magisk, then you have to flash no verity.

Now ROMs in your decrypted device Flash
After instruction flashed restart always takes place again and again into the recovery
Is there a reason for that

saleappeal said:
Now ROMs in your decrypted device Flash
After instruction flashed restart always takes place again and again into the recovery
Is there a reason for that
Click to expand...
Click to collapse
could you explain it clearly about what you have done ?

give credit where credit is due
https://forum.xda-developers.com/oneplus-6/how-to/test-decryption-t3818775

virtyx said:
give credit where credit is due
https://forum.xda-developers.com/oneplus-6/how-to/test-decryption-t3818775
Click to expand...
Click to collapse
Done bro.

HatRiGt said:
1) Actually never use that twrp that has support for MTP. Always use normal twrp.
If you have got any mounting issue, just flash the fastboot rom and then again boot to twrp and then follow the steps in OP carefully.
2) Yes no verity should be always flashed in the last before you boot into the system .
even if you flash kernel / magisk, then you have to flash no verity.
Click to expand...
Click to collapse
I'm using blu_spark twrp(was recommended both in OP and for flashing pie OB1) and MTP worked fine. Up until formatting, that is.. it does say you might need to restart to use file system(I'm guessing either for mounting or decrypting filesystem after format?). It'll just show the device with no space total or used, and then times out if i try to create a folder or copy something over.. is the trick here to put the needed files on a partition that's not touched when formatting, if that's a thing?
I feel like I'm missing something, but I think my issue was just flashing kernel last.. I'm gonna look into the manual method at some point to get a better idea of what's what! Thanks a lot!:good:

I mean after formatting you end up with no twrp zip to flash and you cant transfer files in twrp…..
Or at least I couldn't at first. I was stuck with no os and an empty internal storage. My newer computer couldn't transfer files.
However after hooking it up to my old computer I was able to transfer files in twrp using blu spark twrp. I put the liquid remix rom, twrp, magisk, gapps and the no verity zip in internal.
flashed rom, flashed twrp, rebooted recovery, flashed gapps, magisk, then flashed no verity and rebooted system.
Pretty sure the only reason I was able to transfer those file is because liquid remix has adb debugging and mtp checked by default in developer settings.
And i'm still decrypted so all is good.

SelfElevated2 said:
I mean after formatting you end up with no twrp zip to flash and you cant transfer files in twrp…..
Or at least I couldn't at first. I was stuck with no os and an empty internal storage. My newer computer couldn't transfer files.
However after hooking it up to my old computer I was able to transfer files in twrp using blu spark twrp. I put the liquid remix rom, twrp, magisk, gapps and the no verity zip in internal.
flashed rom, flashed twrp, rebooted recovery, flashed gapps, magisk, then flashed no verity and rebooted system.
Pretty sure the only reason I was able to transfer those file is because liquid remix has adb debugging and mtp checked by default in developer settings.
And i'm still decrypted so all is good.
Click to expand...
Click to collapse
Actually u can also flash twrp file before formating data. Or format data and boot to recovery using Fastboot method.

In order overcome this file transfer problem after format data I used a USB flash drive and viola, problem solved, hope this helps. cheers.

HatRiGt said:
Actually u can also flash twrp file before formating data. Or format data and boot to recovery using Fastboot method.
Click to expand...
Click to collapse
Yeah but stock rom has USB debugging off by default. So someone that flashes stock wouldn't be able to use fast boot or file transfer. They would have to use the UNbrick tool. You may want to to change the order in instructions so less knowledgeable people don't run into problems.
Even if you flash TWRP before formatting, you still lose the no verity you put in internal storage. A fresh install of stock rom won't let you use fast boot commands as USB debugging is off by default
vtec303 said:
In order overcome this file transfer problem after format data I used a USB flash drive and viola, problem solved, hope this helps. cheers.
Click to expand...
Click to collapse
Yeah I just ordered one on eBay yesterday. I figured that would be a huge help as long as TWRP let's you access the other storage.
Sent from my OnePlus6 using XDA Labs

[RECOVERY][ROOT]TWRP 3.3.1-1 Galaxy J4+/J415F/FN/G/DS

Unofficial release -TWRP recovery for the Galaxy J4 plus 2018 - SM-J415 MSM8917
{
"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"
}
TWRP 3.3.1-0 Released
May 22, 2019
TWRP 3.3.1-0 is out now for most currently supported devices.
What's new in 3.3.1-0:
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
Update - 17/8/2019
TWRP 3.3.1-1 OO/PP build released
Current status - Beta
Treble supported
Bugs: brightness slider
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
*****INSTALL INSTRUCTIONS:*****
Flash with ODIN in the AP slot.
1. Put your device in DOWNLOAD mode.
(Plug in the USB cable and then hold POWER + VOL DOWN + VOL UP)
2. Load the respective file below into the AP slot, uncheck Auto-reboot(not required for twrp_3.3.1-1) and hit start.
twrp_3.2.3-1_sm-j415f_30319
twrp_3.3.1-1_j415x_17819
3. After flashing and ODIN reports PASS immediately force reboot to recovery. (Not required for twrp_3.3.1-1 as it should auto reboot to recovery). You should now see TWRP recovery.
Do NOT let the device boot to the OS.
4. Flash the V3 RMM bypass zip
https://forum.xda-developers.com/showpost.php?p=79745844&postcount=627
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT AND BECOMING RMM LOCKED FOR 7 DAYS.
I ALSO SUGGEST BACKING UP ANYTHING YOU NEED ON INTERNAL STORAGE. AT SOME POINT YOU MAY EXPERIENCE A 'VERIFICATION FAILED MESSAGE' .
THIS IS NORMAL, BUT WILL REQUIRE THE DATA PARTITION TO BE FORMATTED IN TWRP.
5. Reboot to TWRP (Do not boot to the OS yet)
***** ROOT INSTRUCTIONS:*****
OREO ONLY
1. Flash the Forced encryption disabler patch. This is only required if you wish to have full functionality in TWRP.
Flashing this will disable Samsung's forced encryption. Disabling encryption will allow TWRP to mount the data partition.
After flashing the patch it is necessary to *FORMAT* (not wipe) the /DATA partition using the FORMAT DATA button under the wipe options.
PLEASE NOTE THIS WILL DELETE EVERYTHING ON INTERNAL STORAGE AND FACTORY RESET THE DEVICE, SO BACK UP ANYTHING YOU WISH TO KEEP.
J4+J6+_oreo_forced_encryption_disabler
2. To root I suggest installing the latest Magisk beta as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
(NOTE: The DEFEX patched Oreo kernel below may be needed for full root support if certain apps do not work with root):
https://androidfilehost.com/?fid=1395089523397921797
3. Enjoy your rooted device.
PIE ONLY
1. Due to some new securities in Samsung's latest Pie kernels, root will not work with the stock kernel. The patched kernel below is required to gain root on Pie.
Features:
Dmverity, proca, five and defex disabled.
OTG and NTFS file system support.
Selinux permissive switchable.
This kernel may require the U4 bootloader.
(NOTE: flashing a custom kernel on PIe breaks the lockscreen. Ensure NO lockscreen is enabled before installing the kernel.)
J415FXXU4BSF7_patched_boot_318919
2. To root I suggest installing the latest Magisk beta as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/app...mless-t3473445
3. If you wish to have access to internal storage /DATA in TWRP then encryption will need to be disabled. See step 1 of the Oreo root instructions then instead of installing the J4+J6+_oreo_forced_encryption_disabler install the zip below with TWRP:
Disable_Dm-Verity_ForceEncrypt_Quota_08.02.2019
3. Reboot.
The device will take a good 10 mins to boot first time.
Enjoy your rooted device.
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my tester @kapmino269 [MENTION=6037748]Zackptg5 for the DM-VERITY & FORCEENCRYPT DISABLER @teamwin, @corsicanu for RMM V3 bypass zip.
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU

kapmino269 said:
Thank you very much for building twrp but there are bugs :
1- After I make steps all is done I power off it but when I open it isnot boot & i see a message All the words I understood that "you flash unauthornized boot.img & recovery img and return the phone to the company to fix the phone" and phone didnot boot I recognize that when I open internet in phone samsung detect the change in phone so i solved it by:
:good: I repeat the steps but after i connect to internet , i activate magisk and close wifi and download afwall on my sdcard from appkpure by pc and install the app an enable firewall and solved but there message that rules not apply but in fact it is applied and all is done . SOLVED
2-When I close phone and recharge it, it isnot recharged but it continue rebooting not to system but just recharge windows and poweroff and agian to recharge window And so on .
I coulding solve but I sure the error is in boot.img or in another . NOT SOLVED
Sorry for my english.................
Click to expand...
Click to collapse
Thanks for all the info, but does TWRP actually boot?

kapmino269 said:
Twrp is very very good and backup and restore and mount are good but there are bugs in system not in recovery addition the last:
3- the percentage of battery when charging,it isnot change . NOT SOLVED
What is the reason ?
Click to expand...
Click to collapse
Percentage doesn't change in twrp or when power off?

kapmino269 said:
SORRY MR ashyx there isn't bugs in system my charger was cut and it is the reason of rebooting to recovery. But bugs in recovery brightness control and backup encryption.
And your build is good ask twrp.me to make it official.
Click to expand...
Click to collapse
You will need to Format (not wipe) /data to remove encryption and mount the data partition. Samsung encryption isn't supported yet by TWRP.
Brightness isn't a deal breaker, but I'll look into it.
Could you do me a favour and post the recovery.log so I can check it over?

kapmino269 said:
And I forget said that all afwall versions above 2.9.9 doesn't work and Samsung will lock the phone and you should download afwall with date 5/2018
Click to expand...
Click to collapse
What do you need AFwall for?

kapmino269 said:
To prevent Samsung apps detect the change on the boot.img and recovery.img and so on and I told you at first that after flashing and activate magisk I set wifi on and when I power off the device and open it ,I couldn't open phone on any mode ,there is message apear to me told if I boot to system it said as I remember and I understand that "there is boot.img flash to phone by unauthorized way please return device to company or someone you buy the device from him to fix the phone " and replacing when reboot recovery boot.img by recovery. img and as I remember the screen was blue and the text was written in black and red. so I flash sammobile stock with Odin and repeat your twrp installing steps and activate magisk and close wifi and put afwall 2.9.9 (above versions didn't work ) and the error didn't appear again .
Click to expand...
Click to collapse
I don't think that you need AFwall. When you see that message boot to TWRP and format your device, install Magisk and the Oreo encryption disabler.
This should prevent this message appearing again.
Also disable securitylogagent apk.

Can this be used to flash GSI?

Jason Grewal said:
Can this be used to flash GSI?
Click to expand...
Click to collapse
As posted in the OP :
Update 8/12/2018
Current status - Beta (Tested working)
Treble supported
Bugs: brightness slider
Click to expand...
Click to collapse

kapmino269 said:
sorry I see another error in restore in TWRP .
all partitions restored but when I finish restore twrp said unable to mount /system and I couldn't reboot system
Click to expand...
Click to collapse
Have you tried backing up only system again then immediately restoring?
Also which media are you restoring from?
Also need the recovery log after failure.

kapmino269 said:
A1 :No , I will try backup system and system image only.
A2 :I restore from usb otg .
A3 :It success in restore efs boot vendor and others but system not mount and tried to return system again .
££i flash sammobile rom and install magisk as you tell and restore all phone partitions Except system and system image ££ The phone open again.
###I will try restore system again and i will sent you recovery.log BUT WHICH MEDIA I SHOULD USE USB OTG OR SDCARD ###
I am sorry for disturb.
Click to expand...
Click to collapse
Can you try backing up just system, not system image to internal storage then try restore?

kapmino269 said:
ok, I will try .
I would ask you about something else but sending you private message unanable I need to ask you but i couldnot because the question is about something else twrp for j415f how to send the issue to you
Click to expand...
Click to collapse
If it's related to this device then just post it. I don't accept pm's.

kapmino269 said:
A-Restoring system only and other partition is done and succeed and faster from internal storage but if i copy it to pc or sdcard Is all files will copied or not or Error will apper after copy (restoring again).
Thanks for your help .
1- it is related to j415f some apps like busybox and linux deploy and afwall(new version) grant root access but didnot run.
2- #
Another problem :
no,it isnot .it related to wlan monitor mode for gt-i9500 (internal (bcm4335 ) or external (TL-WN22N) ) , I tried linux deploy kali hunter nexmon others ,and please reply if you could help me or reach me to someone help me .
#
please reply me quickly about (2) to delete it
SORRY I havenot any way to reach you except this .
Click to expand...
Click to collapse
1. Isn't really related to twrp but magisk itself. Better posting in the magisk thread.
2. Unfortunately can't help you with this as I don't mess around too much with that kind of stuff.

I wouldnt dare to do anything on this before everything is 100% clear and failproof. This phone behaves like its about to collapse every second idk why but it feels like that

kapmino269 said:
Thank you very much for your help and your interest .
Please ,Can you fix restoring system from usb otg ? and all files you need from me i will send you it ,
you must make your twrp ideal and make it official in #twrp.me# like Alberto86(recognise developer) : make gt-i9500 twrp and ge officialty .
surendrajat(member ) : Make SM-J737S twrp it is in #twrpbuilder.github.io#
I think you should publish the recovery in this sites at the nearest time. I think also you should make video on youtube to make your project spread out faster ,because there are people donot know xda ,I tried to make video but my presentation was very bad so i delete it from youtube .
And Sorry for distrubt
Click to expand...
Click to collapse
I don't think there is anything to fix regarding the restorating of a backup from OTG.
It's just simply a case of some media is not suitable for backup and restore.
I've even seen reports of certain MicroSD cards causing issues with TWRP.
It's likely that if you try a different USB stick you won't have any issues.
As regarding making it official. I will consider it. However I have many, many builds of TWRP for a lot of other devices that are not official either.
This is due to the fact I do not like the convoluted system of getting it made official.
I have discussed this previously with teamwin and asked for a proper submissions page to no avail.

kapmino269 said:
Ok as you like but you can improve twrp .
I mean :
1 -Could you compress encryption disable and
rmm bybass and recovery in twrp.tar file to flash it by odin in one step wihout following install steps that you write , Steps may be difficult with others , With me I try serval times to success and i know some skills about android but others may donot know .
2 - Why your twrp depend on magisk install
,if magisk doesnot install phone doesnot reboot system , I think twrp should not be depend on root & If some one need twrp and doesnot need root.
3 - Busy box i cannot install it in my phone why ,?
Click to expand...
Click to collapse
No I cannot make an all in one to flash in ODIN.
Firstly because its not possible. Odin cannot run scripts, only recovery can.
Secondly if people cannot follow instructions then maybe they shouldn't be attempting to modify their device.
TWRP doesn't depend on Magisk, your device does.
Samsung incorporate many security hurdles to prevent hacking and modification.
These security blocks need to be patched or the device will not boot.
These blocks can be patched manually, however Magisk can patch most of these during the root process.
I have no idea why you cannot install busybox on your device as you have not provided any info of the issue.
In any case busybox is included with Magisk. To use it install the busybox module by osm0sis.

kapmino269 said:
picture
Click to expand...
Click to collapse
I see what your saying, however I will keep things as they are. I'd prefer people to have an understanding of what they are installing and I believe it's simple enough.
Unfortunately I can't help with the busybox issue. However as I stated you can use the busy module provided by osm0sis.
He keeps everything up to date and is highly recommended.

kapmino269 said:
I face issue :
I test j4+ snd s4 security in lookscreen :
1- In j4+ : if I delete /data/system/locksetting.db or all contain locksetting name in twrp buy terminal or file manager or script.
2 -add delete *.key on s4 .
Is there solution from system or twrp to prevent lock screen crack or it hash stolen to crack not tell me (chattr).
Thank you
Click to expand...
Click to collapse
If I'm reading it correctly you want a way of preventing the lockscreen credentials from being deleted.
The only way is to remove TWRP Tbh so no one had access to the file system.
Also this isn't really a twrp related issue and a little off topic.
However I have been looking at possible ways to password TWRP thus preventing access at all.
But even that could be circumvented by simply flashing another version of TWRP.
The only safe way is to remove twrp, unroot your device and disable OEM unlock.

kapmino269 said:
1 - I donot have any ways to reach you and you is the developer of twrp for j4+ and Know all about it and you donot accept pm , I could make
thread and you answer me in it but this issue in twrp so all is well .
2 - I want twrp and root ,Is there any solve ,I have idea may success sent me it may be sucess or not
it is
1- make data partition not mount or read only on twrp .
2- when I need to install something I will mount it by writing command in system terminal only (that command or script or program doesnot be found in twrp ) to be mounted in recovery mode .
3- I mean that data not mount in twrp without enable mounting in system and twrp doesnot have permission to mount data without system access .
but how this will acheive without you man .
another idea the same but replace mounting by read only
Click to expand...
Click to collapse
If you don't want data to be mounted in twrp then why not just leave it encrypted. Then only you have access to it via the OS?
Failing that just remove the mount entry for /data from the fstab.
This way data will only be available and mountable by using terminal commands.
The other way is to only install twrp when you need it.
For example you could use a script which you could run to flash twrp when booted to the OS each time you need it or if you prefer use something like flashify.
When you are done with twrp, simply use the restore option to restore the stock recovery.
This way only you have access to /data.

how to do this on galaxy J4?pls. help
i have a lock bootloader in download mode

Has anyone tried any gsi?
I tried havoc os 2.0 didn't work.

How To Guide Root RUI2.0 and RUI3.0 all models with Magisk

WARNING
Do it at your own risk , neither XDA nor me will be responsible for any damage that may occur
Overview
Rooting your device will give you freedom to enjoy plethora of features like removing OEM bloatwares , using system level Firewall , backing up and restoring all data of Apps , underclocking kernel for better battery life etc .
Requirements ​
Bootloader Unlocked Realme GT Neo 2 (Guide - https://forum.xda-developers.com/t/bootloader-unlocking-on-indian-model-rui-2-0-latest-a07.4391679/ )
A PC (windows or linux) with adb- fastboot installed
USB cable
Magisk Stable Apk
TWRP.img thanks to @ SathamHussainM from his thread on the same topic
Downloads ​ADB-FASTBOOT setup for windows https://forum.xda-developers.com/at...484757/?hash=78ebfa42e75a5def462676a93fff24c7
TWRP.img file link https://www.androidfilehost.com/?fid=17825722713688258515
Magisk23 apk Click here
Root Checker App link https://apkpure.com/root-and-safetynet-checker/com.atominvention.rootchecker/download?from=details
STEPS​Copy this file to your PC C:\adb folder and rename it to twrp.img
{
"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"
}
Boot your device into fastboot mode Open Command Line
Go To C:\adb folder , press shift and do a right click , select open Powershell window here
Now type
fastboot devices
, press enter it should show your device now
now type
fastboot boot twrp.img
Process will take 10 second
Your device will reboot and after some time it will show TWRP logo ( it takes time 1 min approx )
wait some time
then In PC file explorer it will show realme gt neo 2 , open it
go to internal storage > Downloads and copy paste the twrp.img file and magisk alpha apk
In twrp backup BOOT , EFS, Modem ,Persist-Image
after backup is done come back to TWRP home and tap on Install button go to the folder where you saved both the files
and select Install image button , now it will show twrp.img file , tap on it then select recovery partition and swipe to confirm flash
After process is complete press Back button and come to TWRP home
Again press install button and select magisk.apk and swipe to confirm flash , this will install Magisk 23 after process is complete press home button go to reboot tab and select system
, Now phone will reboot to system
In phone open file manager and install magisk.apk
Open magisk app it will show magisk installed
just to be sure press the install button and select direct install and press Lets GO
After process is complete press the reboot button and it will boot back to system mode now
Your phone is rooted with magisk 23 and you are eligible to enjoy variety of mods and themes for your device .

Q1) Why are you not flashing recovery directly ?
A) Becuase Its risky (very low chance of flashing failing from fastboot ),So
first we boot this twrp file temporarily and backup all important partitions
When it is clear recovery is working fine , we copy the twrp.img and flash it from twrp to make it permanent .

Q2) Why are you not flashing magisk patched image ?
Ans) Becuase Its risky (the patched boot image you got may not be of your model or software version which will cause bootloop , SO
we trust in magisk to use our device boot.img to create a patched boot.img with magisk support , then we reflash magisk from magisk App to confirm it .

Is there any way to flash stock rom if twrp is installed?

This post says "for all models" but your bootloader unlocker post is for Indian model?
Just asking. It can cause misunderstanding.

Spl1tz said:
This post says "for all models" but your bootloader unlocker post is for Indian model?
Just asking. It can cause misunderstanding.
Click to expand...
Click to collapse
This guide will work for all variants of GT NEO 2 , however the unlocking guide is for Indian Variant only .
So if you somehow managed to unlock Non-Indian Model of RMX3370 you can safely follow this guide (no liabilities of OP ) to install TWRP then root your device

ultimatesprit said:
Is there any way to flash stock rom if twrp is installed?
Click to expand...
Click to collapse
Why do you want to flash stock ROM ?
If it is booting problem you can read this guide
If you just want to reset you have to first remove magisk then from TWRP do factory reset from WIPE section.
However you can try this RollBack ZIP for Indian Variant of Realme GT NEO 2

Email44841 said:
This guide will work for all variants of GT NEO 2 , however the unlocking guide is for Indian Variant only .
So if you somehow managed to unlock Non-Indian Model of RMX3370 you can safely follow this guide (no liabilities of OP ) to install TWRP then root your device
Click to expand...
Click to collapse
Ah gotcha. And now i see bootloader unlock for all variants too. Finally!
Thank you for your hard work

Email44841 said:
Why do you want to flash stock ROM ?
If it is booting problem you can read this guide
If you just want to reset you have to first remove magisk then from TWRP do factory reset from WIPE section.
However you can try this RollBack ZIP for Indian Variant of Realme GT NEO 2
Click to expand...
Click to collapse
This is my first realme device.I would prefer to keep a stock rom to flash incase any boot loop. Not decided to flash twrp permanently. i hope i can boot to stock recovery and flash rollback package to be in stock..Will it work?

Is it possible to use Kernal editor app after root to undervolt/overvolt GPU?

I have moved magisk23aplha.apk to /sdcard/download, but i can't find it in the path after click 'Install Zip', how?

lspgzz said:
I have moved magisk23aplha.apk to /sdcard/download, but i can't find it in the path after click 'Install Zip', how?
Click to expand...
Click to collapse
sry for disturbe, i got it. Just rename the file into '.zip' and install it

Spl1tz said:
ow i see bootloader unlock for all variants too
Click to expand...
Click to collapse
Incorrect. Not all variants

can we update the magisk to latest version (stable or beta) ?

Yes
reversegear said:
can we update the magisk to latest version (stable or beta) ?
Click to expand...
Click to collapse
You can Safely update to latest Magisk releases

My twrp says "internal storage 0 MB", rui3.0 any idea how to fix this?

I booted in twrp when i click any option it makes a hissing noise (in twrp) and when i try to backup says unable to mount storage (unable to mount /data/media/TWRP/.twrps faild to mount '/data' (invalid argument) also i cant see my device on my computer.

theogr91 said:
I booted in twrp when i click any option it makes a hissing noise (in twrp) and when i try to backup says unable to mount storage (unable to mount /data/media/TWRP/.twrps faild to mount '/data' (invalid argument) also i cant see my device on my computer.
Click to expand...
Click to collapse
Are you able to boot into ROM ?
What have you done before this started happening ?
coz that happens when rui gets corrupted and is unable to mount /data and If unable to boot into saystem then the only solution is to do flash stock boot.IMG and wipe all data

RMX3370 said:
Are you able to boot into ROM ?
What have you done before this started happening ?
coz that happens when rui gets corrupted and is unable to mount /data and If unable to boot into saystem then the only solution is to do flash stock boot.IMG and wipe all data
Click to expand...
Click to collapse
After i unlocked bootloader i flashed ui 2 twrp to ui3 and bricked i fixed it with ofp flash sideload from twrp i can use my phone just bs on twrp