Related
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?
Hi guys,
Here is my complete foolproof guide on how to update your system. Please note that there may be other maybe easier ways that cut-out some steps but this worked for me. It is intended for Noobies so I apologise to more advanced users if it seems tedious and long-winded. But that's how Noobies like it with everything explained in detail.
IMPORTANT NOTE: If you have previously used parallel apps then before doing any of this process you must delete user 999 from the system, otherwise you backups will not work!!!
From a terminal window (I use terminal emulator from play store ) type su and enter. Now type the command pm remove-user 999 and enter. Now you shouldn't have to worry about parallel apps messing up your backups.
Thanks to @dgunn for this :good:
https://forum.xda-developers.com/on...estore-999-t3801632/post76760812#post76760812
Also, please note that I have NEVER previously installed an un-official twrp on my device (wanted to wait for official ), however, I was unlocked, and rooted with magisk v16.0 and on stock oos 5.1.5 before beginning this upgrade process.
If you already have an un-official twrp installed, then I cannot guarantee that this guide will work for you. It might, it might not
Disclaimer: This is a guide for helping others. It is your choice to follow it and I take no responsibility for any problems you encounter as a result of following this guide. You do it at your own risk
Ok, lets get started......................
Actually, before we do let's get one thing clear that is confusing a lot of people regarding fastboot and twrp. There are 2 ways of putting twrp recovery onto your phone. A temporary way (disappears after rebooting and goes back to stock recovery) and a permanent way (the best way that stays put - what we all want right?). This guide assumes that you don't currently have twrp on your phone.
In order to put a permanent official twrp on your phone, first we have to boot (NOT flash!) into a temporary version of twrp. The fastboot command for this is "fastboot boot path_to_temporary_twrp.img" (without the quotes of course )
The difference between temporary twrp and permanent twrp is in whether we either fastboot boot or fastboot flash.
Ok, let's begin
First of all, as a precaution, disable all security on your device like pin, pattern, password, fingerprint. Make sure that when you wake your phone it goes straight to the homescreen without any prompts for pins etc etc. May not be needed but it's what I did
1. Download the following files to the following locations....
a. Official oxygen OS 5.1.6 zip file (full zip) > to root of sdcard .
b. Official twrp installer ZIP file > to root of sdcard. (This is our permanent twrp file)
c. Magisk root zip file (I used v 16.0 but v16.4 zip file should be okay too) > to root of sdcard.
d. Official twrp installer IMG file > to your PC in the same folder as your fastboot files. (This is our temporary twrp file)
These files are available for download in other threads on XDA just search for them.
Once that is done proceed as follows.....
2. Go to settings>system updates and click the gear icon in the top right and choose "local upgrade" and then select the Oxygen 5.1.6 zip file from your sdcard. The system will now begin to update itself. Once finished it will prompt you to reboot, do this, and the system will boot back up into Oxygen OS 5.1.6 :good:
3. Now, long press your power button and select reboot and select bootloader option and your phone will reboot into bootloader (fastboot) mode.
4. On your PC go to your fastboot folder and open a command prompt in that folder (don't forget you previously put the temporary twrp image file in here)
5. Now plug your phone into the PC
6. At the command prompt enter following command fastboot devices
and your phone should show up as connected and recognised.
7. We are now going to boot the phone into the temporary twrp. Type the following command fastboot boot <name of temporary twrp file (from your fastboot folder)>.img
8. Your phone will now boot into the temporary twrp recovery and from here we can now flash the permanent version of twrp that we previously put on our sdcard.
9. On your phone, select Install, then find the twrp zip file on the root of your sdcard, select it and swipe to flash.
10. Once this has flashed successfully, we now need to reboot into this new permanent recovery. DO NOT REBOOT TO SYSTEM AT THIS POINT! Now, select "Reboot" option and select "Recovery". Your phone will now reboot into the new permanent twrp. You can now forget about the other temporary twrp from earlier
11. Once the phone goes back into recovery select Install option and find the Magisk root zip file on your sdcard and select it. Now swipe to flash it. After successfully flashing Magisk, you are now ready to enjoy the fruits of your labours
Go back to the twrp homepage and select Reboot>system.
The system will now boot normally and if you have followed these steps to a Tee you will be on OOS 5.1.6 and rooted!
I have also done a successful twrp backup without any error messages. Your previous data will be untouched and you can now set-up your security again.
One final thing to note - because the boot and recovery partitions are now combined, this means that everytime you flash something to your boot partition, your new permanent twrp recovery will be lost and you will have to re-install twrp again from scratch initially through fastboot.
Enjoy
carlos67 said:
From a terminal window (I use terminal emulator from play store ) type su and enter. Now type the command pm remove_user 999 and enter. Now you shouldn't have to worry about parallel apps messing up your backups.
Click to expand...
Click to collapse
I bet the terminal command should be:
pm remove-user 999
I've made almost the same without problem
After many years of being actively involved in unlocking, flashing, and tinkering. I feel I'm starting from scratch. This quick guide is exactly what I've been waiting for as I'm in the same situation with being simply unlocked and rooted lol. I'll be replicating these steps shortly ?.
Only thing I'm wondering, once everything is done and running... If I flash a rom with the official "permanent" twrp, it's gone gone? Let's just say, renovate ice ROM?
Maybe it's the 16 hour day I worked and lack of sleep... But having it replaced upon a single rom flash and carrying the name "permanent" seems like 2 opposing ideas lol
Kiddman said:
I bet the terminal command should be:
pm remove-user 999
Click to expand...
Click to collapse
Yes, well spotted and corrected :good:
InflatedTitan said:
After many years of being actively involved in unlocking, flashing, and tinkering. I feel I'm starting from scratch. This quick guide is exactly what I've been waiting for as I'm in the same situation with being simply unlocked and rooted lol. I'll be replicating these steps shortly ?.
Only thing I'm wondering, once everything is done and running... If I flash a rom with the official "permanent" twrp, it's gone gone? Let's just say, renovate ice ROM?
Maybe it's the 16 hour day I worked and lack of sleep... But having it replaced upon a single rom flash and carrying the name "permanent" seems like 2 opposing ideas lol
Click to expand...
Click to collapse
If you were to flash a full OTA official update then yes, your "permanent" twrp will be gone because the boot partition gets flashed to stock and you'd need to re-install twrp starting in fastboot. However, for custom rom flashes, it depends if their is a kernel bundled in with the rom. If not then twrp should remain, if yes then as with official update, re-install twrp.
It's more normal for a custom rom to simply overwrite system partition without touching boot partition and twrp, but, sometimes custom rom's like Renovate come bundled with a kernel (TBalden's) and wipe out twrp.
If I'm wrong on this I stand to be corrected.
Kiddman said:
I bet the terminal command should be:
pm remove-user 999
Click to expand...
Click to collapse
Yes you are correct because this was my finding and thank you OP for not giving credit
My findings of the 255 error (999)
https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632
dgunn said:
Yes you are correct because this was my finding and thank you OP for not giving credit
My findings of the 255 error (999)
https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632
Click to expand...
Click to collapse
My apologies, an oversight, corrected
carlos67 said:
My apologies, an oversight, corrected
Click to expand...
Click to collapse
Thank you sir. And great write up btw
Something to note is the Renovate ICE 1.0 magisk module messed with the text in settings on OOS 5.1.6. It went back to normal when I disabled that module.
I thought it was the VoEnabler module initially but I wasnt correct.
I put the zip in the root folder (Not the actual folder named root) but the local upgrade isn't showing anything in there.
I'm on 5.1.5 rooted with Magisk 16.0 and have 5.7 magisk manager installed along with xposed and gravity box.
Any idea why my local upgrade isn't detecting the upgrade zip? I downloaded it from Funk Wizards post. I got clicked the "official" link for OOS 5.1.6
I have a custom kernel and magisk installed, can I still follow this guide?
surface13 said:
I put the zip in the root folder (Not the actual folder named root) but the local upgrade isn't showing anything in there.
I'm on 5.1.5 rooted with Magisk 16.0 and have 5.7 magisk manager installed along with xposed and gravity box.
Any idea why my local upgrade isn't detecting the upgrade zip? I downloaded it from Funk Wizards post. I got clicked the "official" link for OOS 5.1.6
Click to expand...
Click to collapse
Figured it out, it was because the ro.product.device=OnePlus 6 instead of OnePlus6 in the build.prop file.
I had originally changed it to sailfish to see if I can get Daydream working. When I changed it back I accidentally added a space =/
Anyone done this on a phone with unofficial TWRP to start out yet?
Lownita said:
I have a custom kernel and magisk installed, can I still follow this guide?
Click to expand...
Click to collapse
Yes you can.
Considering that many of us have been rooted with patched boot image and no custom recovery, this guide is very well written.
Simple Guide is Already available | No Root | No Rom
youtube.com/watch?v=a7rh4NpYD7E
I followed the above youtube guide . Very simple .
Steps :
Install VPN app like Surf Easy Android VPN
Change Region to Canada or Germany
Again try to update the Oxygen OS
It will show in update available .
"
2. Go to settings>system updates and click the gear icon in the top right and choose "local upgrade" and then select the Oxygen 5.1.6 zip file from your sdcard. The system will now begin to update itself. Once finished it will prompt you to reboot, do this, and the system will boot back up into Oxygen OS 5.1.6
"
After that I got constant reboot with the message " System UI has stopped"
x111 said:
"
2. Go to settings>system updates and click the gear icon in the top right and choose "local upgrade" and then select the Oxygen 5.1.6 zip file from your sdcard. The system will now begin to update itself. Once finished it will prompt you to reboot, do this, and the system will boot back up into Oxygen OS 5.1.6
"
After that I got constant reboot with the message " System UI has stopped"
Click to expand...
Click to collapse
Could be a corrupt download file. I suggest you do the following.....
Re-download the file and check it's good using an MD5 checker app/tool. Then, boot your phone into bootloader (fastboot) mode by powering off first and then pressing and holding the vol up button.
Then follow steps 4-to-10 in my guide for installing (1st) temporary twrp and then (2nd) permanent twrp. Once you have permanent twrp and are booted into it you should then copy the "new" download zip for the OTA that you md5 checked from your PC onto the root of your sdcard and install it by flashing the zip file in twrp. Now you should reboot to system which will change the active slot to the updated OOS you just flashed and then if you want boot back into recovery to flash a custom kernel (if you so wish) and Magisk root zip (again if you so wish).
carlos67 said:
Could be a corrupt download file. I suggest you do the following.....
Re-download the file and check it's good using an MD5 checker app/tool. Then, boot your phone into bootloader (fastboot) mode by powering off first and then pressing and holding the vol up button.
Then follow steps 4-to-10 in my guide for installing (1st) temporary twrp and then (2nd) permanent twrp. Once you have permanent twrp and are booted into it you should then copy the "new" download zip for the OTA that you md5 checked from your PC onto the root of your sdcard and install it by flashing the zip file in twrp. Now you should reboot to system which will change the active slot to the updated OOS you just flashed and then if you want boot back into recovery to flash a custom kernel (if you so wish) and Magisk root zip (again if you so wish).
Click to expand...
Click to collapse
Thanks for response.
https://forum.xda-developers.com/showpost.php?p=76773727&postcount=153
Followed the procedure: Installed EX Kernel as well. Now I'm getting a popup message after every reboot: There's an internal problem with your device. Contact your manufacturer for details.
No issues as such but I'm getting this message everytime I reboot. Any suggestions?
Alternative Option For Applying December (or any other OTA updates) without using ADB or Fastboot.
Pros:
+ No need for fastboot or ADB
+ Can be done without a PC
+ OTA is applied from within Android, using Android's normal update process
+ Retains root
+ Retains any installed Magisk Modules
Cons:
- Until Magisk is updated, requires that you fake a backup by compressing a stock boot image and renaming the resulting file.
- Only works on phones with duel partitions
- Slightly harder to do without a PC
The Pixel 4/4XL has duel partitions. This allows for an alternative option for installing OTA updates without losing root (Magisk) or wiping data. The process is outlined in the Magisk guide here: https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
The problem with following that guide is that since there is no TWRP for Pixel 4 / Android 10, most of us patched Magisk into a stock boot image manually, leaving us without an automatically created backup. Then, when you attempt to uninstall Magisk and restore the backup boot image, you get a message stating "No backup image found". However, it is easy to copy a stock boot image to your phone and have Magisk treat it as a backup. Magisk can then uninstall itself, you apply the OTA without restarting, reinstall Magisk by patching OTA image in the inactive partition, then reboot. After reboot you will be running the OTA version with Magisk patched in.
The process is a little easier if you have a PC, but it can be done completely on the phone itself, without any other hardware.
Here is a full process:
Requirements:
A rooted Pixel with Magisk Manager installed
A file explorer app that has a root broswer (I use Total Commander)
A text editor that can open arbriatry files (I used Quick Edit)
A tool to zip files (I used 7-Zip on a Windows PC, then transfered the file via USB, but you can do this completely without a computer)
The unpatched boot.img file that corresponds to your current build. (Get it from https://developers.google.com/android/images#coral
Create a backup image that Magisk can auto-restore
On your Android phone, open the following file: /sbin/.magisk/config
Copy the SHA1 hash (you want to copy everything after the = sign)
Download the factory image that corresponds to your current build. Extract the zip, then from the zip extract the boot.img file (Yes, there is a zip within a zip). This is easier to do on a computer, but can be done directly on the phone.
Create a new .gz archive that contains the boot.img file and nothing else. On Windows, I used 7zip for this, selecting gzip as the method, and using all of the defaults.
Rename the .gz achive to the following: 'stock_boot_<hash>.img.gz' where <hash> is the SHA1 hash that you coped from the Magisk config file.
Copy the .gz file to your phone and place it in the /data directory. The full path on your phone should be /data/stock_boot_<hash>.img.gz.
You can now follow the rest of the guide from https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md, but an abbreviated version is included
Uninstall Magisk and Apply the OTA
Launch Magisk Manager on your phone
Select "Uninstall", then choose "Restore Images". Magisk will be uninstalled and you will be back to running stock boot.
Go to Settings --> Systems --> Advanced --> System Update, then check for and apply updates. You will need to select "resume" to force the update to happen immediately. DO NOT RESTART THE PHONE. The December update can take a while. I was on the "optimizing apps" message for a good 20 - 30 minutes.
After the udpate has been installed, the screen will have the option to restart. Don't select it.
Install Magisk to the updated boot and restart
Start Magisk Manager
Select Install (we are installing Magisk, not Magisk Manager)
When prompted, choose to install to an inactive partition
Read the warning and confirm. The OTA boot image will be patched with Magisk.
Restart your phone.
You should now have the OTA update (verified by checking Settings --> About Phone --> Build number)
You should also have a new stock_boot_<hash>.img.gz file in your /data directory. Next time there is an OTA update, you can skip the first part of this and go straight to uninstalling Magisk and applying the OTA.
Thanks to reyqn and Nephiel for commenting on https://github.com/topjohnwu/Magisk/issues/1870.
Hi. What do you mean " Copy the SHA1 hash " because in /sbin/magisk/config. i don't see any file name SHA1 hash?
Sent from my Pixel 4 XL using Tapatalk
GrimEcho said:
...when you attempt to uninstall Magisk and restore the backup boot image, you get a message stating "No backup image found"...
...Create a backup image that Magisk can auto-restore
On your Android phone, open the following file: /sbin/.magisk/config
Copy the SHA1 hash (you want to copy everything after the = sign)
Download the factory image that corresponds to your current build. Extract the zip, then from the zip extract the boot.img file (Yes, there is a zip within a zip). This is easier to do on a computer, but can be done directly on the phone.
Create a new .gz archive that contains the boot.img file and nothing else. On Windows, I used 7zip for this, selecting gzip as the method, and using all of the defaults.
Rename the .gz achive to the following: 'stock_boot_<hash>.img.gz' where <hash> is the SHA1 hash that you coped from the Magisk config file.
Copy the .gz file to your phone and place it in the /data directory. The full path on your phone should be /data/stock_boot_<hash>.img.gz....
Click to expand...
Click to collapse
I think they fixed Magisk/Magisk Manager: Opened Magisk Manager ==> Tapped Uninstall ==> Tapped Restore images
Not getting this message: "No backup image found"
Appreciate the instructions to "Create a backup image that Magisk can auto-restore.":good:
---------- Post added at 11:44 AM ---------- Previous post was at 11:10 AM ----------
DinarQ8 said:
Hi. What do you mean " Copy the SHA1 hash " because in /sbin/magisk/config. i don't see any file name SHA1 hash?
Click to expand...
Click to collapse
Everything after SHA1= in sbin/.magisk/config (file) is the 'hash'.
Thanks for this guild.... I just wondering if we could use EX kernel Manager (or anything similar) to flash the stock boot.img (so everything returned to stock), then apply OTA, then use Magisk Manager to patch the inactive slot...
Although this requires another app, but we don't need to create backup specific for MM... Just a stock boot.img is needed...
Haven't tried this yet... Will try on Jan update.....
For some reason if the config file says recoverymode=true then magisk will still not find the backup image. If you change it to recoverymode=false then you can continue on with the rest of the steps. I wonder why?
StoicSage said:
For some reason if the config file says recoverymode=true then magisk will still not find the backup image. If you change it to recoverymode=false then you can continue on with the rest of the steps. I wonder why?
Click to expand...
Click to collapse
Or you can Open Magisk Manager, Tap Advanced Settings and uncheck Recovery Mode.
DinarQ8 said:
Hi. What do you mean " Copy the SHA1 hash " because in /sbin/.magisk/config. i don't see any file name SHA1 hash?
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
/sbin/.magisk/config is the name of the file. There is no extension to it, but it is a text file.
Open the file in an editor and the last line should have the SHA1 hash.
Homeboy76 said:
I think they fixed Magisk/Magisk Manager: Opened Magisk Manager ==> Tapped Uninstall ==> Tapped Restore images
Not getting this message: "No backup image found"
Appreciate the instructions to "Create a backup image that Magisk can auto-restore.":good:
---------- Post added at 11:44 AM ---------- Previous post was at 11:10 AM ----------
Everything after SHA1= in sbin/.magisk/config is the 'hash'.
Click to expand...
Click to collapse
I think it depends on what method you used to originally root the Pixel 4. If you copied over a .boot.img file to the phone, then used Magisk Manager to patch the file while you didn't have root then Magisk won't make a backup, since it doesn't have access to copy the backup /data. But if you have root when you use Magisk Manager to create a patch (via TWRP, or because root is still enabled from an in memory magisk), then it can copy the file.
lssong99 said:
Thanks for this guild.... I just wondering if we could use EX kernel Manager (or anything similar) to flash the stock boot.img (so everything returned to stock), then apply OTA, then use Magisk Manager to patch the inactive slot...
Although this requires another app, but we don't need to create backup specific for MM... Just a stock boot.img is needed...
Haven't tried this yet... Will try on Jan update.....
Click to expand...
Click to collapse
I think this would work as long as you can flash stock using Ex Kernal Manager while Magisk is still installed, and don't have to reboot. Magisk needs root access to be able to patch the OTA in the inactive slot, so if you flashed stock, then restarted, Magisk Manager couldn't access the inactive slot any longer (I think). I haven't used EX Kernal Manager though, so I'm not positive.
GrimEcho said:
I think this would work as long as you can flash stock using Ex Kernal Manager while Magisk is still installed, and don't have to reboot. Magisk needs root access to be able to patch the OTA in the inactive slot, so if you flashed stock, then restarted, Magisk Manager couldn't access the inactive slot any longer (I think). I haven't used EX Kernal Manager though, so I'm not positive.
Click to expand...
Click to collapse
O think you are absolutely right! The key is "do not reboot after flash the stock boot.img" so MM can still do the magic on patch the inactive partition. Your original idea does open a good avenue on OTA without PC.. which saves a lot of troubles......
GrimEcho said:
I think it depends on what method you used to originally root the Pixel 4. If you copied over a .boot.img file to the phone, then used Magisk Manager to patch the file while you didn't have root then Magisk won't make a backup, since it doesn't have access to copy the backup /data. But if you have root when you use Magisk Manager to create a patch (via TWRP, or because root is still enabled from an in memory magisk), then it can copy the file.
Click to expand...
Click to collapse
I did this while on the November 2019 Factory Image:
- opened MM, tapped uninstall, tapped restore images (root gone)
- downloaded December 2019 Factory Image
- extracted the boot.img
- opened MM, tapped install, tapped install, tapped patch a file, selected the December boot.img
- After, it finished patching the boot.img, there was a backup file in /data folder.
I could be wrong but I think the key to ensuring a back up file is made it to turning off Recovery Mode prior to patching the boot.img: Open MM, tap Advanced Settings, and uncheck Recovery Mode.
Amazing this worked! Thanks so much.
Just to note: I had to use QuickEdit to set the RECOVERYMODE=false unchecking the box in Magisk didn't seem to work for me.
One question, I'm now on "Security patch level: November 5, 2019". I'm pretty sure my stock boot.img was from October some time. To get the December update, should I download the latest factory image and redo the process? Therefore, everytime we want to do an OTA, we must download the latest factory image and extract the boot.img?
foaf said:
Amazing this worked! Thanks so much.
Just to note: I had to use QuickEdit to set the RECOVERYMODE=false unchecking the box in Magisk didn't seem to work for me.
One question, I'm now on "Security patch level: November 5, 2019". I'm pretty sure my stock boot.img was from October some time. To get the December update, should I download the latest factory image and redo the process? Therefore, everytime we want to do an OTA, we must download the latest factory image and extract the boot.img?
Click to expand...
Click to collapse
Short answer is yes to the factory image and extracting the boot.img every month before taking the ota. Just make sure the OTA and factory image build numbers match :good:
**UPDATE** - flashing the boot.img from the October Factory Image seems to have fixed the touch screen issue. So, now I gotta figure out why the OTA keeps failing...
I have question, I attempted this method but the update would not install... I kept getting an installation error. So, I just reinstalled Magisk from the Magisk Manager. However, when I rebooted the touch screen no longer works... So I can't unlock my phone.
What is the easiest way to fix this? I was on the original factory image (October) and I bought the phone directly from Google (non-carrier version).
I've attempted to just flash-all using the Dec factory image from fastboot (using key-combo to get into fastboot) but I get the flash in fastbootd error. I'm assuming flash-all from the correct October factory image will fix me up, but I honestly can't remember exactly which October factory image came with the device. Any help would be greatly appreciated.
ihuntinde said:
**UPDATE** - flashing the boot.img from the October Factory Image seems to have fixed the touch screen issue. So, now I gotta figure out why the OTA keeps failing...
I have question, I attempted this method but the update would not install... I kept getting an installation error. So, I just reinstalled Magisk from the Magisk Manager. However, when I rebooted the touch screen no longer works... So I can't unlock my phone.
What is the easiest way to fix this? I was on the original factory image (October) and I bought the phone directly from Google (non-carrier version).
I've attempted to just flash-all using the Dec factory image from fastboot (using key-combo to get into fastboot) but I get the flash in fastbootd error. I'm assuming flash-all from the correct October factory image will fix me up, but I honestly can't remember exactly which October factory image came with the device. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Can't you flash the December image but do it manually? Pain in the ass but should get it done.
p70shooter said:
Can't you flash the December image but do it manually? Pain in the ass but should get it done.
Click to expand...
Click to collapse
I tried to flash-all the December image but it kept failing with flash with fastbootd. Even though I have the most up to date platform-tools.
I believe I know what I did though... I didn't read the instructions clearly and i used the december boot image when i uninstalled magisk.... I'm attempting it again doing the instructions exactly as it states... fingers crossed...
foaf said:
Amazing this worked! Thanks so much.
Just to note: I had to use QuickEdit to set the RECOVERYMODE=false unchecking the box in Magisk didn't seem to work for me.
One question, I'm now on "Security patch level: November 5, 2019". I'm pretty sure my stock boot.img was from October some time. To get the December update, should I download the latest factory image and redo the process? Therefore, everytime we want to do an OTA, we must download the latest factory image and extract the boot.img?
Click to expand...
Click to collapse
If you are willing to wait for the OTA updates then you don't need to keep doing the download/extract/zip process. After the first OTA update, when you use Magisk to root patch the inactive partition with the installed OTA, Magisk will create a new backup. So next time there is an OTA, you can just uninstall Magisk and restore. It should now find the backup.
ihuntinde said:
I tried to flash-all the December image but it kept failing with flash with fastbootd. Even though I have the most up to date platform-tools.
I believe I know what I did though... I didn't read the instructions clearly and i used the december boot image when i uninstalled magisk.... I'm attempting it again doing the instructions exactly as it states... fingers crossed...
Click to expand...
Click to collapse
Yep, it sounds like that is the issue. It can be easy to mix up. You need to fake a restore of the boot image for the version your phone is currently on (pre-OTA). But after you apply the OTA and install Magisk to the inactive partition, Magisk will create a new backup of a new unpatched boot image with the OTA applied, so each update will roll forward.
@GrimEcho
man, thx you so much. I've just updated from dec to jan ota build, without any issues! xD
This worked beautifully. Unfortunately it only moved me up to December. Will be great if I don't have to remake the boot.img file to go to January.
Recovery mode being on in magisk caused this to fail. I had to edit the config file as mentioned by another, kill magisk then it worked at next launch. Toggling it off within magisk left the flag active in the config file.
Appreciate the writeup.
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
Goodmorning everyone. I have a problem with magisk and lineageos 18.1
I have a xiaomi mi mix 2 unlocked
Premise: I've never had any problems with magisk and lineage until now.
I installed magisk scrupulously following the official instructions and using both the boot.img patch system and the direct installation via recovery (adb sideload & lineage recovery)
In both cases magisk appears as not installed when looking from magisk manager and the wifi stops working (the phone connects to the various networks I have tried but reveals them as without internet.)
clearing cache does nothing
resetting network connections does nothing
Updating to the latest version of the radio firmware does nothing
restore boot.img OR reinstall lineage corrects the problem
In all cases I don't get root ...
Honestly, everything is beyond my understanding .. can you help me?
Ork_77 said:
Goodmorning everyone. I have a problem with magisk and lineageos 18.1
I have a xiaomi mi mix 2 unlocked
Premise: I've never had any problems with magisk and lineage until now.
I installed magisk scrupulously following the official instructions and using both the boot.img patch system and the direct installation via recovery (adb sideload & lineage recovery)
In both cases magisk appears as not installed when looking from magisk manager and the wifi stops working (the phone connects to the various networks I have tried but reveals them as without internet.)
clearing cache does nothing
resetting network connections does nothing
Updating to the latest version of the radio firmware does nothing
restore boot.img OR reinstall lineage corrects the problem
In all cases I don't get root ...
Honestly, everything is beyond my understanding .. can you help me?
Click to expand...
Click to collapse
It seems to me like you aren't properly flashing the patched boot.img. What method are you using to flash the patched boot.img?
Droidriven said:
It seems to me like you aren't properly flashing the patched boot.img. What method are you using to flash the patched boot.img?
Click to expand...
Click to collapse
I used both the method I'm aware of
1) I install magisk manager, extract the boot.img from lineage zip, upload it to the phone, patch it with magisk manager (operation ends fine), pass the modified version back to the pc reboot the phone in recovery and install the new boot with adb (installation ends correctly).
2) I rename the magisk app as .zip and then I install it through recovery
The result is the same.
In the past (with lineage 17) i always used the second method and I lived happy and with root for years.
Ork_77 said:
I used both the method I'm aware of
1) I install magisk manager, extract the boot.img from lineage zip, upload it to the phone, patch it with magisk manager (operation ends fine), pass the modified version back to the pc reboot the phone in recovery and install the new boot with adb (installation ends correctly).
2) I rename the magisk app as .zip and then I install it through recovery
The result is the same.
In the past (with lineage 17) i always used the second method and I lived happy and with root for years.
Click to expand...
Click to collapse
Since you have TWRP, you don't need the patched boot.img.
The Magisk Manager app has the root binaries built in now, all you should need to do is a Magisk Manager flashable zip.
Read this:
The Magisk Manager APK can now be flashed from within TWRP
Magisk is now distributed as part of the Manager APK, meaning you no longer need to flash a separate ZIP file from a custom recovery.
www.xda-developers.com
...
Droidriven said:
Since you have TWRP, you don't need the patched boot.img.
The Magisk Manager app has the root binaries built in now, all you should need to do is a Magisk Manager flashable zip.
Read this:
The Magisk Manager APK can now be flashed from within TWRP
Magisk is now distributed as part of the Manager APK, meaning you no longer need to flash a separate ZIP file from a custom recovery.
www.xda-developers.com
Click to expand...
Click to collapse
Yes...this is exatcly what I did.
Method 2.
Ork_77 said:
Yes...this is exatcly what I did.
Method 2.
Click to expand...
Click to collapse
You said that you converted the apk into a flashable zip. I think you should be able to find a MagiskManager.zip that is prepackaged for you to download and flash.
Also, if you use the patched boot.img method, you should rename the patched boot.img to "boot.img", then place the boot.img in your fastboot folder on PC. Then right click inside the fastboot folder and choose the option to open a cmd terminal, then boot your device into fastboot mode, connect your device to PC, type the following command:
fastboot devices(press enter)
If it returns a serial number, you are connected. Next, type the following command:
fastboot flash boot boot.img(press enter)
This should flash the patched boot.img correctly. Then reboot the device to system and try installing the Magisk Manager apk file from your internal storage instead of flashing it as a zip in recovery. If that doesn't work, try flashing the apk as a zip in recovery, wipe cache and dalvik cache after flashing the zip(DO NOT FACTORY RESET OR FORMAT ANYTHING), then reboot to system and see if it works correctly.
Droidriven said:
You said that you converted the apk into a flashable zip. I think you should be able to find a MagiskManager.zip that is prepackaged for you to download and flash.
Also, if you use the patched boot.img method, you should rename the patched boot.img to "boot.img", then place the boot.img in your fastboot folder on PC. Then right click inside the fastboot folder and choose the option to open a cmd terminal, then boot your device into fastboot mode, connect your device to PC, type the following command:
fastboot devices(press enter)
If it returns a serial number, you are connected. Next, type the following command:
fastboot flash boot boot.img(press enter)
This should flash the patched boot.img correctly. Then reboot the device to system and try installing the Magisk Manager apk file from your internal storage instead of flashing it as a zip in recovery. If that doesn't work, try flashing the apk as a zip in recovery, wipe cache and dalvik cache after flashing the zip(DO NOT FACTORY RESET OR FORMAT ANYTHING), then reboot to system and see if it works correctly.
Click to expand...
Click to collapse
Hi Droidriven, thank you for your answers. Perhaps, synthesizing my steps too much, I gave the impression of not being particularly capable in computer science (you even tell me to press "enter" after commands ...). Well, let's say it's not my case.
All steps are performed correctly.
all steps end without errors.
No matter what I do, in the end Magisk appears as n / a, I don't have root, and the data connection doesn't work. Small addition about the latter aspect: when rebooting the wifi connection works for a variable time between 10 and 20 seconds, after which the network appears as without internet (or intranet) but the phone remains connected.
At the reboot, history repeats itself
Restoring the original boot everything returns to normal.