Database Info

TWRP not working with encrypted phone memory?

i'm having issues to use TWRP after encrypting the phone memory. I tried the following:
• "TWP-3.0.2-2-E6653.img" is just doing nothing after entering the PIN
• "twrp-3.0.2-0-E6653-20160417.img" shows
○ Unable to mount storage (is this due to no SD present?)
○ After entering the PIN: "Password failed, please try again"
is anyone experiencing the same effect? according to the changelog (https://kernel.andro.plus/kitakami_r2.html) it should work, do you know how to contact the developers?
the phone configuration:
-E6653
-stock rom .253
-the following steps applied (thanks to the other posters, but each post was not working for me at some point, because something was missing. so here is what i did):
references:
http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307
http://forum.xda-developers.com/xpe...ckup-drm-unlock-rootfor-t3373312#post68988474
1.Download the latest Flashtool
http://www.flashtool.net/downloads.php
2.Download 32.0.A.6.200 or any older build for your Z5.(pay attention to download the right firmware. for example you may have E6633 or E6653)
http://www.xperiablog.net/forum/resources/xperia-z5_e6653_32-0-a-6-152_central-europe-5_generic.477/
3.Flash it and power on your phone.
4.Download Iovyroot and use it to back up your DRM key.(don't forget to enable USB debugging)
http://forum.xda-developers.com/cros...-tool-t3349597
5.Copy your DRM keys to a safe back up.(warning:never try to flash another handsets DRM key or you will hardbrick your phone)
6.Unlock your bootloader now.request keys from here.follow the guide
set in developer options:
OEM Unlocking - Yes
USB Debugging - Yes
http://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597
7. update to latest firmware via flashtool / xperifirm
E6653_Customized DE_1298-3675_32.2.A.0.253_R3C
(wipe APPS_LOG, USERDATA)
## optional ## encrypt your phone now
8. androplus kernel / twrp
fastboot flash boot boot.img (Z5_AndroPlusKernel_Permissive_v38.zip)
fastboot flash recovery TWP-3.0.2-2-E6653.img
https://kernel.andro.plus/kitakami_r2.html (go to google drive downloads)
9. supersu (not possible because of defective twrp)
start twrp -> install SR1-SuperSU-v2.78-SR1-20160915123031.zip
cheers

anyone? is encryption really not possible?

It is possible.. I had the internal storage encrypted, but I also had serious problems trying to wipe it via TWRP. Somehow I managed to wipe it flashing stock recovery, I couldn't do it with TWRP.

Hi Lionel,
Which Rom and twrp version did you use? I still can't get access to the data with twrp, see above. Could you create backups with your configuration?

How did u manage to remove encryption by flashing it. i have tried and failed. What settings did u use in Flashtools?
lionelbac said:
It is possible.. I had the internal storage encrypted, but I also had serious problems trying to wipe it via TWRP. Somehow I managed to wipe it flashing stock recovery, I couldn't do it with TWRP.
Click to expand...
Click to collapse

inteltecra1700 said:
How did u manage to remove encryption by flashing it. i have tried and failed. What settings did u use in Flashtools?
Click to expand...
Click to collapse
I had to flash kernel and recovery (both stock), then when rebooted, it started to wipe.
My problem started when I tried to make a factory reset from android. Then every time the phone started it went to TWRP, but it couldn't wipe the user data partition.

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?

decrypt /data

move fstab using official recovery ( adbpull /vendor/etc/fstab.kirin970 and fstab.kirin970.data - remove "avb" and encryption from userdata, replace the encryption line on data with 'encryptable')
format /data in unofficial recovery
install magisk in official recovery
for some reason it only works in that order, if you try and do it all in official or unofficial recovery it doesnt work and magisk recognizes encryption on data.
after each step reboot bootloader and flash respective recovery, then fastboot reboot unplug and hold power and vol up to go straight into recovery and continue, if you boot you have to start over)
when installing magisk zip you should see that it doesnt say keep force encrypt.
and if you go in settings you have the option to encrypt.

virtyx said:
move fstab using official recovery ( adbpull /vendor/etc/fstab.kirin970 and fstab.kirin970.data - remove "avb" and encryption from userdata, replace the encryption line on data with 'encryptable')
format /data in unofficial recovery
install magisk in official recovery
for some reason it only works in that order, if you try and do it all in official or unofficial recovery it doesnt work and magisk recognizes encryption on data.
after each step reboot bootloader and flash respective recovery, then fastboot reboot unplug and hold power and vol up to go straight into recovery and continue, if you boot you have to start over)
when installing magisk zip you should see that it doesnt say keep force encrypt.
and if you go in settings you have the option to encrypt.
Click to expand...
Click to collapse
Hi there
I´m struggling to get lineage 15.1 to install without google framework errors
You mention offical and unofficial recovery. I guess you are talking about twrp
when you say move fstab do you mean remove?
Could this encryption be my problem with lineage and gapps not installing as it should?

buenso80 said:
Hi there
I´m struggling to get lineage 15.1 to install without google framework errors
You mention offical and unofficial recovery. I guess you are talking about twrp
when you say move fstab do you mean remove?
Could this encryption be my problem with lineage and gapps not installing as it should?
Click to expand...
Click to collapse
After you install lineage format /data that should work
Totally irrelevant to OP

If i hadn't tried that i wouldn't ask here.
Not TOTALLY irrelevant, as my question is about the official and unofficial twrp having trouble mounting and wiping before flashing rom..
Please stop trolling

virtyx said:
move fstab using official recovery ( adbpull /vendor/etc/fstab.kirin970 and fstab.kirin970.data - remove "avb" and encryption from userdata, replace the encryption line on data with 'encryptable')
format /data in unofficial recovery
install magisk in official recovery
for some reason it only works in that order, if you try and do it all in official or unofficial recovery it doesnt work and magisk recognizes encryption on data.
after each step reboot bootloader and flash respective recovery, then fastboot reboot unplug and hold power and vol up to go straight into recovery and continue, if you boot you have to start over)
when installing magisk zip you should see that it doesnt say keep force encrypt.
and if you go in settings you have the option to encrypt.
Click to expand...
Click to collapse
If you format data, isn't the device going to be empty?
Only time I've done this before I had to copy a ROM via MTP in recovery and then flash with no Verity.
So forgive me if I'm wrong but if I format data, won't I end up with no operating system?

dladz said:
If you format data, isn't the device going to be empty? J
Only time I've done this before I had to copy a ROM via MTP in recovery and then flash with no Verity.
So forgive me if I'm wrong but if I format data, won't I end up with no operating system?
Click to expand...
Click to collapse
/system is where the system lives
/data is userdata and applications
Noting wrong with formatting, you will lose all apps and data though

virtyx said:
/system is where the system lives
/data is userdata and applications
Noting wrong with formatting, you will lose all apps and data though
Click to expand...
Click to collapse
Legend, thanks for clearing that up.
:good:
I know off topic, but out of interest with the p20 pro, if you did find yourself with no OS how would you get back to a functional phone?
There's no custom ROMs to flash, just never been in this situation before.
Hypothetically

dladz said:
Legend, thanks for clearing that up.
:good:
I know off topic, but out of interest with the p20 pro, if you did find yourself with no OS how would you get back to a functional phone?
There's no custom ROMs to flash, just never been in this situation before.
Hypothetically
Click to expand...
Click to collapse
You can use hurupdater and download the firmware from firmwarefinder on your of
Happened a lot of times for me

Just as a headsup, you dont need to decrypt anything when you just wanna do some changes once and are proper admin level on your desktop machine, ive moved a whatsapp message history from previous phone (also taken from protected space there) to P20P just by attaching it to pc in file transfer mode and then adding myself as full control user in the security tabs of the several system folder properties i went in to, worked like a charm.
The point im trying to make: Android and Windows finally understand each others permission systems (not sure since how long as ive been away from android for a few years) so you can just attach it and use Windows perm system to give yourself access where needed, lots easier & faster then making a bunch of changes to your phone in effect disabling encryption, something you in most cases dont really want to do permanently anyway, so this is a nice workaround that doesn't touch your phone's encryption settings but still lets you mess about with system files.
Just my 2 cents.

virtyx said:
move fstab using official recovery ( adbpull /vendor/etc/fstab.kirin970 and fstab.kirin970.data - remove "avb" and encryption from userdata, replace the encryption line on data with 'encryptable')
format /data in unofficial recovery
install magisk in official recovery
for some reason it only works in that order, if you try and do it all in official or unofficial recovery it doesnt work and magisk recognizes encryption on data.
after each step reboot bootloader and flash respective recovery, then fastboot reboot unplug and hold power and vol up to go straight into recovery and continue, if you boot you have to start over)
when installing magisk zip you should see that it doesnt say keep force encrypt.
and if you go in settings you have the option to encrypt.
Click to expand...
Click to collapse
I did everything step by step, the encryption is gone and yet I still get that stupid permission denied error when I try to do a backup in TWRP. So. F*cking. Annoying.
Update: when I press the "Install" button in TWRP, it shows giberish, but if I go to Advanced>File Manager everything has it's proper name. WTF?!
Hmmm, If I don't tick "Vendor" in the backup, I get this error:
Can not create 'data/media/0/2021-01-20--07-26-51' folder (No such file or directory).
Failed to make backup folder.
Update on update: oof, now everything that's in the internal storage is gibberish, even in the OS.

Problems after Magisk update - can only enter download mode and recovery

Hey there,
I am currently struggeling with my Samsung Galaxy S7 (Exynos) device, running on superman rom (Android 8).
What happened?
For root I´m using Magisk Manager and for banking apps I have Magisk hide running. Then the program told me that there is an update (Magisk App) available. So, as always and recommended, I choosed "Direct Install" but that failed for some reason. OK I thought´, no problem. Later I wanted to reboot my phone but it didn´t. The screen says "Downloading.... Do not turn off device!". I only can enter "Download Mode" and "Recovery Mode via TWRP".
What I tried so far:
1) Wipe cache/dalvik --> not successful
2) Tried to do a factory reset via twrp --> not successful
3) Tried to flash BL via Odin --> not successful
At this time I realised that the same problem occured to my Galaxy Tablet SM-T580. So I came to the point that I did something wrong with updating magisk on both devides.
What I also tried next:
4) Tried to delete magisk modules via twrp --> not successful
5) Tried to uninstall magisk through twrp by downloading the latest Magisk app and rename it to "uninstall.zip" as recommended in installation guide --> Not successful because of Error installing zip file: Unsupported /Unknown image format (unpacking image format)
What can I do next?
Can anyone please help me, since I have two bricked devices now????

A simple kernel flashing would fix the problem, extract the original boot.img of your current ROM, and flash it via TWRP.
Cause it is clearly a problem with your boot.img, if that didn't work (I'm sure it will), then just dirty flash your current ROM.
P.S. If you are encrypted, you might encounter an error doing a simple factory reset, you'll have to format the whole data partition.

Hi @Mohamedkam000,
many thanks for your help. After hours of browsing the web and trying various methods I was able to get my 2nd device (Samsung Galaxy Tab A from 2016) back to life.
What I did: I installed the latest samsung mobile phone drivers on my PC then I connected the tablet to it. I was able to access the internal memory and in the folder "data" Magisk put a backup of the original boot.img. So I installed this "boot.img" via TWRP and voila.......everything works fine again
I´m very happy now.
But unfortunately this method didn´t work with my Samsung Galaxy S7. I just couldn´t find any boot.img file on the phone.
Mohamedkam000 said:
A simple kernel flashing would fix the problem, extract the original boot.img of your current ROM, and flash it via TWRP.
Cause it is clearly a problem with your boot.img, if that didn't work (I'm sure it will), then just dirty flash your current ROM.
Click to expand...
Click to collapse
How do I have to do this? Sorry I´m a little unexperienced so could I get a kind of an step by step guide please?
Mohamedkam000 said:
P.S. If you are encrypted, you might encounter an error doing a simple factory reset, you'll have to format the whole data partition.
Click to expand...
Click to collapse
Don´t understand this. Could you please explain again?
Thank you so much already.
Kind regards,
cap.

capitarider said:
Hi @Mohamedkam000,
many thanks for your help. After hours of browsing the web and trying various methods I was able to get my 2nd device (Samsung Galaxy Tab A from 2016) back to life.
What I did: I installed the latest samsung mobile phone drivers on my PC then I connected the tablet to it. I was able to access the internal memory and in the folder "data" Magisk put a backup of the original boot.img. So I installed this "boot.img" via TWRP and voila.......everything works fine again
I´m very happy now.
But unfortunately this method didn´t work with my Samsung Galaxy S7. I just couldn´t find any boot.img file on the phone.
How do I have to do this? Sorry I´m a little unexperienced so could I get a kind of an step by step guide please?
Don´t understand this. Could you please explain again?
Thank you so much already.
Kind regards,
cap.
Click to expand...
Click to collapse
Glad your tablet revived again.
Magisk creates a backup of the boot.img found just before flashing magisk, it is compressed in gzip format, so you need to pull it, extract it, and push it back to the phone, then flash it.
The file is usually in /data/stock_boot_${SHA1}.img.gz
You can extract it using the built-in terminal of TWRP, if PC is not accessible at the moment by writing and executing the following command:
gunzip {stock-boot-name}.gz
Replace {stock-boot-name} with your backed-up boot name (without the curleybrackets), or you can use the following command:
gunzip *.gz
That'll extract the gzip archive, and the boot.img will be in /data of which you can navigate to it and flash it.
There's another guaranteed method, if you have the file of the ROM you're using right now, you can just open it (it's just a zip archive) and search for the boot.img of your specific phone model and flash it.
Another guaranteed method will be by flashing a custom kernel compatible with your current ROM, like Moro AiO kernel, of which has a wide support for ROMs starting from Oreo, and up to Q, AOSP, or stock-based, just in one file.
Moro's thread: Moro Kernel

you can't access kernel backup because TWRP does not support encryption and Magisk Manager might removed encryption in boot

aIecxs said:
you can't access kernel backup because TWRP does not support encryption and Magisk Manager might removed encryption in boot
Click to expand...
Click to collapse
Doesn't seem like he's encrypted, he found the boot backup of his tablet in /data so he has probably searched for a similar file on his S7, but since it is compressed, he won't find it solely.
Also he would've told us that his /data is empty or something.

start from scratch with older magisk, current 22 has bug
https://github.com/topjohnwu/Magisk/issues/4008

Thank you for your help.
I had a n old twrp backup on another external hard drive. I extracted the boot file and repached it with 7zip to boot.img and flashed through twrp. That also didn´t work for various times. TWRP always said "failed".
In the end I didn´t manage it to bring my phone back to live. Anyway, I decided to flash the latest LineageOS (Android 11) and now its running smooth again.
Thanks again.

Try using sp flash tools flashing the boot.img

Need custom recovery for Mobiistar C1 shine 4g mt 6739 device

Need custom recovery for Mobiistar C1 shine 4g mt 6739 device as m stuck need it urgently and want install android 10 gsi image my device has arm32 a only architecture some suggest me some good and lite gsi images please firstly I need custom recovery twrp please someone help.

It would be hard to support a 2018 device I guess.

[CLOSED] I Will build TWRP for your device!
I wanna build twrp for your device! Pls give info about your device! if possible give stock firmware!
forum.xda-developers.com

i can upload recovery.img file for if you want

its Mobiistar C1 shine (MT6739) arm 32bit a only supported device running on 8.1 i was some how able to root it but unable to install custom recovery if u can please build one for this device i will upload stock recovery.img in few minutes presently its bricked but i will recovery it because i have stock firmware and flashing tool of it....so dont worry just please build a custom recovery like twrp for this device asap if possible

Again: You request a TWRP build for your device going to this thread
[CLOSED] I Will build TWRP for your device!
I wanna build twrp for your device! Pls give info about your device! if possible give stock firmware!
forum.xda-developers.com

any custom recovery bro sorry for that (twrp)

my phone back running again i have flashed it with stock firmware recovery images i have attached earlier and so does phone details screenshot now present situation is 8.1 not rooted stock recovery and firmware so i hope if anyone can help i will be glad

installed latest magisk apk and .zip also by patching boot.img file and flashing that with sp tool to install magisk and got root privilege's

all now i want is proper running and fully functional custom recovery to install custom roms and mods

copvaibhav said:
its Mobiistar C1 shine (MT6739) arm 32bit a only supported device running on 8.1 i was some how able to root it but unable to install custom recovery if u can please build one for this device i will upload stock recovery.img in few minutes presently its bricked but i will recovery it because i have stock firmware and flashing tool of it....so dont worry just please build a custom recovery like twrp for this device asap if possible
Click to expand...
Click to collapse
I am not responsible for any wrongdoing by you. Always have ROM stock files. Any error, install stock recovery again.
First you need to unlock the bootloader if necessary! Unzip file attached and look 2 files.
Then, the installation plan:
0) Flash the TWRP with SPFT or fastboot;
1) Enter TWRP IMMEDIATELY without starting in the system, otherwise TWRP can revert to the stock;
2) When asked to enter the password, select Cancel;
3) Load the file with Magisk (look for any magisk19.zip for TWRP and the decryption file for EXTERNAL memory;
4) Flash Magisk immediately and then install the file data_decrypt_Mobiistar_C1_Shine.zip immediately;
5) Make FORMAT DATA - bottom left button - Type: YES. Go back to the TWRP menu;
6) Make Wipe: data, cache, dalvik (reset to factory settings! Save your data!);
7) Reboot to TWRP (password must not ask);
8) Restart on the system, root is received.

thanks bro for making recovery.img when installing magisk 19.zip its giving error on last step failed to mount /vendor/persist (invalid argument). done
after that i tried to install your data decrypt .zip after one reboot to recovery because i have tried before without reboot recovery once so this time rebooted and installed your data.zip file and again on the last step same error as magisk failed to mount /vendor/persist (invalid argument). done
after that i tried to format by typing yes but again same error failed to mount /vendor/persist (invalid argument).done
just to inform you i have formatted phone from inside by turning it on factory reset but nothing happened....and internal space is not mounting i some how managed to install these things via OTG USB but same error again and again. i am attaching screenshot also which i captured from other phone of mine.
kindly help asap

copvaibhav said:
thanks bro for making recovery.img when installing magisk 19.zip its giving error on last step failed to mount /vendor/persist (invalid argument). done
after that i tried to install your data decrypt .zip after one reboot to recovery because i have tried before without reboot recovery once so this time rebooted and installed your data.zip file and again on the last step same error as magisk failed to mount /vendor/persist (invalid argument). done
after that i tried to format by typing yes but again same error failed to mount /vendor/persist (invalid argument).done
just to inform you i have formatted phone from inside by turning it on factory reset but nothing happened....and internal space is not mounting i some how managed to install these things via OTG USB but same error again and again. i am attaching screenshot also which i captured from other phone of mine.
kindly help asap
Click to expand...
Click to collapse
This is Ok. I made TWRP fast and not remember if the stock partitions has \vendor\persist. So if has that's message is normal. Therefore messages about \vendor\nvdata;nvram;nvcfg is normal too. Very pacth zip files can delete that and the device cannot have IMEI.
First: Is good know the file TWRP worked;
- - You can't install any zip without FORMAT DATA first because FORMAT DATA process can view internal storage. If you don't FORMAT DATA maybe the zip file going wrong with MicroSD & OTG.
In this moment you understand: not use external storage! Put zip in the internal storage an try again.
About MTP: Has anything wrong wiht A8.1 & TWRP. Most devices with A8.1 and TWRP do not have access to MTP. I don't know what happens because I don't know why TeamWin was unable to resolve this.
Now you need put zip with adb command (search how to do) or use sileload on the TWRP.
PS: the picture attached by you show about decrypt. In the first moment you need acept modifications and password you press CANCEL.

lopestom said:
This is Ok. I made TWRP fast and not remember if the stock partitions has \vendor\persist. So if has that's message is normal. Therefore messages about \vendor\nvdata;nvram;nvcfg is normal too. Very pacth zip files can delete that and the device cannot have IMEI.
First: Is good know the file TWRP worked;
- - You can't install any zip without FORMAT DATA first because FORMAT DATA process can view internal storage. If you don't FORMAT DATA maybe the zip file going wrong with MicroSD & OTG.
In this moment you understand: not use external storage! Put zip in the internal storage an try again.
About MTP: Has anything wrong wiht A8.1 & TWRP. Most devices with A8.1 and TWRP do not have access to MTP. I don't know what happens because I don't know why TeamWin was unable to resolve this.
Now you need put zip with adb command (search how to do) or use sileload on the TWRP.
PS: the picture attached by you show about decrypt. In the first moment you need acept modifications and password you press CANCEL.
Click to expand...
Click to collapse
sideload is not starting forgot to mention it i have tried that also booted phone normal put the file in internal but in recovery cant have access to internal storage and yes i have press cancel first and that accepted modification but nothing happened no internal storage access only some how otg thats it i dont know what to do

copvaibhav said:
sideload is not starting forgot to mention it i have tried that also booted phone normal put the file in internal but in recovery cant have access to internal storage and yes i have press cancel first and that accepted modification but nothing happened no internal storage access only some how otg thats it i dont know what to do
Click to expand...
Click to collapse
Okay. Wait my free time and I'll create other TWRP for your device.
Reflash stock recovery if you want & test other file soon.
Update
\|/ Lucky file attached today. So install and test. You can install zip that I put before or Donwload acoording your device cpu has. Read instructions about that again.
Reference Download: https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/

thanks bro i dont know how it worked but it worked again i have to use otg but this time it worked by downloading different force disabler.zip after that i have formatted the data by typing yes it worked then again i flashed your disabler and new recovery image and phone booted magisk installed phone rooted.....thanks a ton i dont know how to say thanks you but thank you all .
can please suggest me as my mt 6739 is 32arm a only device some light gsi for my device actually i want custom mods in gsi so if u can suggest me which also supports my device i will be very thankful

copvaibhav said:
thanks bro i dont know how it worked but it worked again i have to use otg but this time it worked by downloading different force disabler.zip after that i have formatted the data by typing yes it worked then again i flashed your disabler and new recovery image and phone booted magisk installed phone rooted.....thanks a ton i dont know how to say thanks you but thank you all .
can please suggest me as my mt 6739 is 32arm a only device some light gsi for my device actually i want custom mods in gsi so if u can suggest me which also supports my device i will be very thankful
Click to expand...
Click to collapse
Look correct app to know about your device: Treble Info
You need try install AOSP 8 & 9: https://github.com/phhusson/treble_experimentations/releases
Look "bugs"; try solving; keep your time with experiments.....
After you can try LOS, RRMix, Havoc, etc.....
About this thread/ask help about Custom Recovery so Solved. @jerryhou85
Good Lucky!

system-arm-aonly-vanilla-nosu.img.xz
system-arm32_binder64-aonly-vanilla-nosu.img.xz
bro which file shpuld i download as i told you mine is 32bit arm a only (what is arm first link and arm32binder64 aonly difference) kindly tell.
just to clarify i have download both removed.xy from ext. and flashed from recovery system image but phone goes into fastboot after reboot and when rebooting in recovery at the top it shows no os installed.

lopestom said:
Okay. Wait my free time and I'll create other TWRP for your device.
Reflash stock recovery if you want & test other file soon.
Update
\|/ Lucky file attached today. So install and test. You can install zip that I put before or Donwload acoording your device cpu has. Read instructions about that again.
Reference Download: https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/
Click to expand...
Click to collapse
Sir it's stuck on password screen touch not working please fix it, I will always be grateful to you.

Honey2012 said:
Sir it's stuck on password screen
Click to expand...
Click to collapse
The first start need choose the CANCEL. I think you not know about TWRP (unofficial) and the process with device/TWRP without encryption/decryption process.
If you want that so send me some device to develop/have the possibility of getting that option.
Honey2012 said:
touch not working please fix it, I will always be grateful to you.
Click to expand...
Click to collapse
As you read, I not have your device in my hands!
Many 32bits and few 64bits devices have problem with touch screen from kernel. That's not my error! It's from device company.
I not know about touch screen work or not since copvaibhav not write about. But I won't fix this. There is also the possibility to use OTG and plug in a USB Mouse to use in TWRP.
There are solutions to fix the touch screen but I don't have the device and I don't have time to do it. Search and you will know. So solve it yourself and thank your self for it.
Ask copvaibhav for more process and using TWRP.