Database Develop

I can't install Magisk v14

after reformatting my device and flashing stock rom through twrp, i went and download the zip file with magisk manager latest version and then i fully unroot my device with full unroot of supersu. after i rebooted to twrp, i installed magisk v14 zip and this is what it tells me after i flashed it.
Installing '/sdcard/Magisk-v14.0.zip...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
************************
* Magisk v14.0 Installer
************************
- Mounting /system, /vendor, /cache, /data
- Device platform: arm
- Constructing environment
! Unable to detect boot image
- Unmounting partitions
E: Error executing updater binary in zip ' /sdcard/Magisk-v14.0.zip'
Error flashing zip ' /sdcard/Magisk-v14.0.zip'
Updating partition details...
...done
i have few questions.
1. unable to detect boot image. what do you mean by that? where can i get this boot image?
2. what's that updater binary in the zip file?
what can i do to be able to use magisk? thank you in advance
my device is oppo neo 7 android 5.1

The boot image is a part of your device's software. It's what Magisk modifies to do it's thing. If the installer can't recognise it, there's not much you can do... Except providing logs, that is.
The update binary is a part of the installer. It's the script that modifies the boot image to install Magisk on your device.
When you have these kind of errors, save the recovery log after flashing the zip (Advanced -> Copy Log) and post that (attach it or use Pastebin or similar, don't copy it directly to the post). It's so much easier to troubleshoot with proper logs.
First thing you can try is to use the latest beta and see if that works.

Didgeridoohan said:
The boot image is a part of your device's software. It's what Magisk modifies to do it's thing. If the installer can't recognise it, there's not much you can do... Except providing logs, that is.
The update binary is a part of the installer. It's the script that modifies the boot image to install Magisk on your device.
When you have these kind of errors, save the recovery log after flashing the zip (Advanced -> Copy Log) and post that (attach it or use Pastebin or similar, don't copy it directly to the post). It's so much easier to troubleshoot with proper logs.
First thing you can try is to use the latest beta and see if that works.
Click to expand...
Click to collapse
i got the log, how do i upload it here? im only using android browser.
so itried to install magisk v14 and it didnt detect bootimg but v14.5 did detect but still failed to install.

rajoholic said:
i got the log, how do i upload it here? im only using android browser.
so itried to install magisk v14 and it didnt detect bootimg but v14.5 did detect but still failed to install.
Click to expand...
Click to collapse
I guess you can't attach a file, being so new... You can upload it somewhere and provide the link or use Pastebin and provide the link/id for it.

Didgeridoohan said:
I guess you can't attach a file, being so new... You can upload it somewhere and provide the link or use Pastebin and provide the link/id for it.
Click to expand...
Click to collapse
https://dropmb.com/download/aca1616df3f0d913cb70d1f88176d9d4.html
here it is. thanks for the help

I m also facing same problem
rajoholic said:
after reformatting my device and flashing stock rom through twrp, i went and download the zip file with magisk manager latest version and then i fully unroot my device with full unroot of supersu. after i rebooted to twrp, i installed magisk v14 zip and this is what it tells me after i flashed it.
Installing '/sdcard/Magisk-v14.0.zip...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
************************
* Magisk v14.0 Installer
************************
- Mounting /system, /vendor, /cache, /data
- Device platform: arm
- Constructing environment
! Unable to detect boot image
- Unmounting partitions
E: Error executing updater binary in zip ' /sdcard/Magisk-v14.0.zip'
Error flashing zip ' /sdcard/Magisk-v14.0.zip'
Updating partition details...
...done
i have few questions.
1. unable to detect boot image. what do you mean by that? where can i get this boot image?
2. what's that updater binary in the zip file?
what can i do to be able to use magisk? thank you in advance
my device is Micromax canvas nitro a310 current android version is cyanogen mode 13
Click to expand...
Click to collapse

rajoholic said:
https://dropmb.com/download/aca1616df3f0d913cb70d1f88176d9d4.html
here it is. thanks for the help
Click to expand...
Click to collapse
That was a bit of a shady file sharing site. Anyway...
Your installed TWRP is pretty old. That might have something to do about it. Update TWRP, or you could try letting the Magisk Manager patch the boot image and then flash the patched image with TWRP. Installation instructions in the release thread.

Didgeridoohan said:
That was a bit of a shady file sharing site. Anyway...
Your installed TWRP is pretty old. That might have something to do about it. Update TWRP, or you could try letting the Magisk Manager patch the boot image and then flash the patched image with TWRP. Installation instructions in the release thread.
Click to expand...
Click to collapse
sorry bout that. i just search the google free and temporary storage online. haha! thank you for the help. I'll try what u just said

Didgeridoohan said:
That was a bit of a shady file sharing site. Anyway...
Your installed TWRP is pretty old. That might have something to do about it. Update TWRP, or you could try letting the Magisk Manager patch the boot image and then flash the patched image with TWRP. Installation instructions in the release thread.
Click to expand...
Click to collapse
how do i flash the patched boot.img with twrp? i cant find it in my sd card. it's not showing up. i already got the patched boot img

rajoholic said:
how do i flash the patched boot.img with twrp? i cant find it in my sd card. it's not showing up. i already got the patched boot img
Click to expand...
Click to collapse
Hm.... It might be that your TWRP is to old, but it should be the same procedure as when flashing a zip file except you switch to image flashing by pressing the "Image" button after going to the "Install" screen.
If that doesn't work, use fastboot (or whatever is available for your device).
Code:
fastboot flash boot patched_boot.img

Didgeridoohan said:
Hm.... It might be that your TWRP is to old, but it should be the same procedure as when flashing a zip file except you switch to image flashing by pressing the "Image" button after going to the "Install" screen.
If that doesn't work, use fastboot (or whatever is available for your device).
Code:
fastboot flash boot patched_boot.img
Click to expand...
Click to collapse
So I did what u told me and flashed the boot.img succesfully. Now after flashing that, I flashed v14 and still error in executing update binary. Same with 14.5. But this time after I saw that, I rebooted my device and found magisk manager on my phone. It says v14 installed. Is it installed already?

rajoholic said:
So I did what u told me and flashed the boot.img succesfully. Now after flashing that, I flashed v14 and still error in executing update binary. Same with 14.5. But this time after I saw that, I rebooted my device and found magisk manager on my phone. It says v14 installed. Is it installed already?
Click to expand...
Click to collapse
Yes, if you flash the patched boot image you don't have to do anything else. The Magisk Manager has already taken care of everything.
If you want v14.5 beta, you should now be able to change the update channel (in Manager settings) to beta and update. Just as a FYI, you could have done this already when patching the boot image.
Sounds like it's working now, or? Can you install modules?

Didgeridoohan said:
Yes, if you flash the patched boot image you don't have to do anything else. The Magisk Manager has already taken care of everything.
If you want v14.5 beta, you should now be able to change the update channel (in Manager settings) to beta and update. Just as a FYI, you could have done this already when patching the boot image.
Sounds like it's working now, or? Can you install modules?
Click to expand...
Click to collapse
I installed an app and gave it root permission. It looks like it's working. However the module part, I'm still unsure. When I try to add modules, the screen took me in storage. Looks like it requires me to import something? Where can I download modules?

rajoholic said:
I installed an app and gave it root permission. It looks like it's working. However the module part, I'm still unsure. When I try to add modules, the screen took me in storage. Looks like it requires me to import something? Where can I download modules?
Click to expand...
Click to collapse
First of all, don't even mention that piece of piracy software on xda. It's used to steal from developers and is not allowed here.
In the "Modules" part you can manually install modules that you've previously downloaded. If you want to install directly from the Magisk repo, you (unsurprisingly ) go to the "Downloads" section of the Manager. If you can't see "Downloads", make sure the Manager has internet access.

Didgeridoohan said:
First of all, don't even mention that piece of piracy software on xda. It's used to steal from developers and is not allowed here.
In the "Modules" part you can manually install modules that you've previously downloaded. If you want to install directly from the Magisk repo, you (unsurprisingly ) go to the "Downloads" section of the Manager. If you can't see "Downloads", make sure the Manager has internet access.
Click to expand...
Click to collapse
Sorry I didn't know. What I had in mind is that I'll give u all the details without leaving none so u know what I do and be able to help fast. Anyway, again I'm sorry. I didn't mean it.
I tried to dl greenify4magisk and I successfully download and install it. Rebooting the device now

rajoholic said:
Sorry I didn't know. What I had in mind is that I'll give u all the details without leaving none so u know what I do and be able to help fast. Anyway, again I'm sorry. I didn't mean it.
I tried to dl greenify4magisk and I successfully download and install it. Rebooting the device now
Click to expand...
Click to collapse
Sir, did you manage to install? when i tried to install log is failed.

Error installing zip file '/sdcard/MAGISK/Magisk-v16.0.zip'

Good evening from Spain.
I tried to flash Magisk onto my SM-J530F (Samsung Galaxy J5 2017) but not successfully.
Here's the log:
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled.
Installing zip file '/sdcard/MAGISK/Magisk-v16.0.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
********************
* Magisk v16.0 Installer
********************
- Mounting /system, /vendor
- Found boot/ramdisk image: /dev/block/mmcblk0p10
- Device platform: arm
- Constructing environment
- Unpacking boot image
- Checking ramdisk status
! Boot image patched by other programs.
! Please restore stock boot image
- Unmounting partitions
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/MAGISK/Magisk-v16.0.zip'
Updating partition details...
Failed to mount '/system' (Device or resource busy)
...done
Consider that I did the following:
- Flashed stock rom (J530FXXU2ARB3_J530FPHE2ARB3_PHE.zip content)
- Flashed "CF-Auto-Root-j5y17lte-j5y17ltexx-smj530f.tar" in Download mode via Odin, to root and install SuperSU, since it's needed
for flashing TWRP to avoid any bootloop.
- Flashed TWRP.
- Since I already have TWRP, I tried to uninstall SuperSU from the very app, in Options > Full unroot but gave "Uninstallation error", so then I tried to uninstall SuperSU by flashing "UPDATE-unSU.zip" on TWRP.
- Once that is done, I tried to flash "Magisk-v16.0.zip" and it throwed the log I've above mentioned.
- Since it says: "! Boot image patched by other programs.
! Please restore stock boot image", I rebooted it onto Download Mode, and flashed ONLY the BL (bootloader/boot) slot. Came back to TWRP, I flashed again "Magisk-v16.0.zip" but still have the same problem.
Hope there's any solution to install Magisk onto my SM-J530F. Thank you.

Your issue is that the boot image still is patched by SuperSU. Until you restore the stock boot image you won't be able to install Magisk.
https://www.didgeridoohan.com/magisk/Magisk#hn_Boot_image_patched_by_other_programs
Edit: I don't do Samsung, but from what I remember, you might need to flash AP (or something like that).

Didgeridoohan said:
Your issue is that the boot image still is patched by SuperSU. Until you restore the stock boot image you won't be able to install Magisk.
https://www.didgeridoohan.com/magisk/Magisk#hn_Boot_image_patched_by_other_programs
Edit: I don't do Samsung, but from what I remember, you might need to flash AP (or something like that).
Click to expand...
Click to collapse
Well, something changed!!!
The problem related with the boot image is solved but I still have the " Failed to mount '/system' "
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled.
Installing zip file '/sdcard/MAGISK/Magisk-v16.0.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
********************
* Magisk v16.0 Installer
********************
- Mounting /system, /vendor
- Found boot/ramdisk image: /dev/block/mmcblk0p10
- Device platform: arm
- Constructing environment
- Unpacking boot image
- Checking ramdisk status
- Stock boot image detected
- Backing up stock boot image
- Patching ramdisk
- Repacking boot image
- Flashing new boot image
- Unmounting partitions
- Done
Updating partition details...
Failed to mount '/system' (Device or resource busy)
...done
Thank you very much.
EDIT: Despite this problem: "Failed to mount '/system' (Device or resource busy)", your solution was correct! Now I have Magisk correctly installed.
Thank you

Nice to hear it worked. Just for the record, the "Failed to mount /system" message is a TWRP thingy. The Magisk installation is done at the "-Done" line.

Hi, I have the same problem of error 1 while trying to install Magisk from TWRP.
I looked everywere and they say that it is related to a boot image that have to be reinstalled. I did that and no luck, I tryed with boot.img, no working, I even restored ALL the ROM Stock from Samsung ( AP, BL, CP and CSC) and it is not working. I dont know what to do anyware...
Regeet the time was easy to root Samsung with CF autoRoot,
I tried that and ask me to restore all thephone, so still no root??
Some can help please??
Thx

saoudien07 said:
Hi, I have the same problem of error 1 while trying to install Magisk from TWRP.
I looked everywere and they say that it is related to a boot image that have to be reinstalled. I did that and no luck, I tryed with boot.img, no working, I even restored ALL the ROM Stock from Samsung ( AP, BL, CP and CSC) and it is not working. I dont know what to do anyware...
Regeet the time was easy to root Samsung with CF autoRoot,
I tried that and ask me to restore all thephone, so still no root??
Some can help please??
Thx
Click to expand...
Click to collapse
Provide a recovery log or it's going to be impossible to say what the issue is...

Didgeridoohan said:
Provide a recovery log or it's going to be impossible to say what the issue is...
Click to expand...
Click to collapse
Thx for the reply, I am trying to open the content and upload the report here, but no luck. how can I open the log??? can not get a program to do so .......

saoudien07 said:
Thx for the reply, I am trying to open the content and upload the report here, but no luck. how can I open the log??? can not get a program to do so .......
Click to expand...
Click to collapse
The log is just a text file. Did you check the link I posted? In TWRP: Advanced - Copy log, and then post the resulting file.

Didgeridoohan said:
The log is just a text file. Did you check the link I posted? In TWRP: Advanced - Copy log, and then post the resulting file.
Click to expand...
Click to collapse
I got a file "recovery.log" thats why I can not open it, maybe change the extention to "txt" ???

saoudien07 said:
I got a file "recovery.log" thats why I can not open it, maybe change the extention to "txt" ???
Click to expand...
Click to collapse
That would work, but you should be able to open it directly with pretty much any text editor as well. If you're going to post the log text directly, please at least use HIDE tags...

So here what I just did:
I wanted to do a last try to get that error 1 msg and get the repport directly to publicate it here...
So I decide to go to a clean basis. So,
1- Install all the stock ROM with odin. I choose the Home_CSC
Was another just CSC without Home, dont know exactly which one I had to choose, I choose Home_CSC.
2- Turn the fone off
3- Turn it back to download mode
4- Install the TWRP recovery, and I did not reboot.
5- Turn off the fone.
6- Turn on to recovery mode.
7- Format the data (yes)
8- Reboot to Recovery mode.
9- Install Magisk!
AT MY BIG SURPRISE I DID NOT GET ANY ERROR MSG!!! The installation finished without error!
So I continued...
10- install No verity
11- install SuperUS 2.82
13- Reboot the phone.
I was thinking that the root was ok, now I have a new pb. When I tryed to verify with Root Checker, it says no root. When I entered the app, it said BINARY OCCUPIED.
So any suggestion?

saoudien07 said:
9- Install Magisk!
...
11- install SuperUS 2.82
Click to expand...
Click to collapse
Say what...? You've misunderstood something, somewhere. Use Magisk OR SuperSU. Magisk is it's own root solution...
Are you by any chance using some old and outdates guides? Previously you could use SuperSU with Magisk, but that has not been the case since v13.0, well over a year ago, and MagiskSU has been around since v11.0, introduced a year and a half ago.

Didgeridoohan said:
Say what...? You've misunderstood something, somewhere. Use Magisk OR SuperSU. Magisk is it's own root solution...
Are you by any chance using some old and outdates guides? Previously you could use SuperSU with Magisk, but that has not been the case since v13.0, well over a year ago, and MagiskSU has been around since v11.0, introduced a year and a half ago.
Click to expand...
Click to collapse
You guessed right, I am not using a so old tuto, it says it is for oreo...
So I have to use or Magisk or SuperSU,right?
The thing is that i thought SuperSu is to install the SuperSU app, I did notknow that it root also the phone...
I am kind of newby to Android world, u figured it already...
So what are insterest of using Magisk or no-verity??
---------- Post added at 08:22 PM ---------- Previous post was at 08:17 PM ----------
Didgeridoohan said:
Say what...? You've misunderstood something, somewhere. Use Magisk OR SuperSU. Magisk is it's own root solution...
Are you by any chance using some old and outdates guides? Previously you could use SuperSU with Magisk, but that has not been the case since v13.0, well over a year ago, and MagiskSU has been around since v11.0, introduced a year and a half ago.
Click to expand...
Click to collapse
Can I put a link to the tuto here??
For you guys to have a lock at it?

saoudien07 said:
You guessed right, I am not using a so old tuto, it says it is for oreo...
So I have to use or Magisk or SuperSU,right?
The thing is that i thought SuperSu is to install the SuperSU app, I did notknow that it root also the phone...
I am kind of newby to Android world, u figured it already...
So what are insterest of using Magisk or no-verity??
---------- Post added at 08:22 PM ---------- Previous post was at 08:17 PM ----------
Can I put a link to the tuto here??
For you guys to have a lock at it?
Click to expand...
Click to collapse
The root management app for Magisk/MagiskSU is the Magisk Manager. SuperSU and it's accompanying app is a whole different root solution (that has been sold by @Chainfire and seemingly abandoned by it's new owners).
Magisk usually takes care of dm-verity itself, so there shouldn't be any need for an extra no-verity zip. Sometimes it is needed, but I would skip it until you've tried using Magisk only. If you don't know, dm-verity is used by Android to determine if your device has been tampered with. If you wan't to root your device (tampering), you usually have to disable dm-verity or the device won't boot at all.
If you want root with Magisk, do your list again, but skip step 10 and 11. If it doesn't boot after that, go back to TWRP and flash the no-verity zip.

Didgeridoohan said:
The root management app for Magisk/MagiskSU is the Magisk Manager. SuperSU and it's accompanying app is a whole different root solution (that has been sold by @Chainfire and seemingly abandoned by it's new owners).
Magisk usually takes care of dm-verity itself, so there shouldn't be any need for an extra no-verity zip. Sometimes it is needed, but I would skip it until you've tried using Magisk only. If you don't know, dm-verity is used by Android to determine if your device has been tampered with. If you wan't to root your device (tampering), you usually have to disable dm-verity or the device won't boot at all.
If you want root with Magisk, do your list again, but skip step 10 and 11. If it doesn't boot after that, go back to TWRP and flash the no-verity zip.
Click to expand...
Click to collapse
I just repeated all the procedure, this time just with Magisk, like you said. its installation finished without any error.
I just tryed ROOT Checker, any I finally have the root on my fone!! Thanx you very much for the support, and the explanation.
Can I use Backup/Restoration with TWRP knowing that I rooted with Magisk??

saoudien07 said:
I just repeated all the procedure, this time just with Magisk, like you said. its installation finished without any error.
I just tryed ROOT Checker, any I finally have the root on my fone!! Thanx you very much for the support, and the explanation.
Can I use Backup/Restoration with TWRP knowing that I rooted with Magisk??
Click to expand...
Click to collapse
Great to hear! :good:
You can use TWRP without any issues. Magisk has no impact on it and TWRP has it's own su.

Didgeridoohan said:
Great to hear! :good:
You can use TWRP without any issues. Magisk has no impact on it and TWRP has it's own su.
Click to expand...
Click to collapse
Thx you one more time. Going to install some of my app and configure my new fone then do a backup, for a clean restoration in some months...

I have a problem for the Backup with TWRP. When I want to do a Backup, I get this msg:
failed to mount /data (Invalid argument)
I ve looked on google to fix it, the solution I found is to change data to ext2, then back to ext4.
The pb is that it is removing everything from my phone?
Anyone is having the same issue??

Didgeridoohan said:
Your issue is that the boot image still is patched by SuperSU. Until you restore the stock boot image you won't be able to install Magisk.
https://www.didgeridoohan.com/magisk/Magisk#hn_Boot_image_patched_by_other_programs
Edit: I don't do Samsung, but from what I remember, you might need to flash AP (or something like that).
Click to expand...
Click to collapse
Hi, i am rooting samsung a5 a520w. I am following the steps in the instructions (https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535).
Now I met a problem like this:
! Boot image patched by other programs!
! Please restore stock boot image
Updater process ended with ERROR:1
Error installing zip file '/sdcard/MagiskManager/Magisk-v17.1.zip'
I have no idea where is the boot.img located. All documents in the external card is:
RMM-State_Bypass;
no-verity-opt-encrypt-6.0;
Magisk_17.1

@imcn001 Your answer is in the link from the post you quoted.

Error 7 on TWRP when flashing SM-t817t with Lineage 14.1

I have a rooted SM-t817t and have been attempting to flash Lineage 14.1 to it through TWRP 3.1.0-1_ashyx.
I have tried to flash with the gts210ltexx and the gts210wifi and the results are the same, receive the Error 7 message.
After reading up on other threads I attempted to alter the script to either tell it that the ROM is for the gts210ltexx or just remove it entirely and still getting the error.
Also attempted to run it without authentication.
I have read that the t817x tablets can be flashed with the t810 ROMs but have had zero success with doing so at this time.
I am unsure how to proceed from this point.

TheBigby said:
I have a rooted SM-t817t and have been attempting to flash Lineage 14.1 to it through TWRP 3.1.0-1_ashyx.
I have tried to flash with the gts210ltexx and the gts210wifi and the results are the same, receive the Error 7 message.
After reading up on other threads I attempted to alter the script to either tell it that the ROM is for the gts210ltexx or just remove it entirely and still getting the error.
Also attempted to run it without authentication.
I have read that the t817x tablets can be flashed with the t810 ROMs but have had zero success with doing so at this time.
I am unsure how to proceed from this point.
Click to expand...
Click to collapse
Format (not wipe) DATA and if that doesn't work FORMAT the system partition.
If neither works then maybe you should use an updated twrp.

ashyx said:
Format (not wipe) DATA and if that doesn't work FORMAT the system partition.
If neither works then maybe you should use an updated twrp.
Click to expand...
Click to collapse
Thank you for the advice, I will update to the latest TWRP and then format the data and try that. Will report back with results.

After formatting the data and updating to the latest TWRP, 3.2.3-1, I come across the same error 7.
Have updated the script filed to make certain no trace of verification exists for the ROM and still receive the error.
Have now attempted at least five different ROMS all with the same results.
The following is a summarized look at the details it gives.
Installing zip file 'lineage.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
Warning: No file_contexts
detected filesystem ext4 for /dev/block/platform/15540000.dwmmc0/by-name/SYSTEM
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 7
Error installing zip file '/lineage.zip'
Updating partition details...
Failed to mount '/hidden' (Invalid argument)
...done

Update: I have now wiped data but have not yet formatted it. I believe I will need to install Magisk for that.
However based on other recommendations I have come to find out about the encryption on the Samsung storage and that it might be causing the issue.
I have tried to circumvent this by formatting the data into ext2 then back to ext4 and restarting recovery, but so far this has not worked. The error 7 message persists regardless.
Will come back with further updates.

TheBigby said:
Update: I have now wiped data but have not yet formatted it. I believe I will need to install Magisk for that.
However based on other recommendations I have come to find out about the encryption on the Samsung storage and that it might be causing the issue.
I have tried to circumvent this by formatting the data into ext2 then back to ext4 and restarting recovery, but so far this has not worked. The error 7 message persists regardless.
Will come back with further updates.
Click to expand...
Click to collapse
You didnt read my previous post correctly.
You don't need Magisk to FORMAT DATA.
The FORMAT DATA button is right there under the wipe options.
However what you did would have formatted DATA anyway.
Now do the same for the system partition after formatting DATA.
Do not reboot just check DATA and SYSTEM can be mounted then try and install the zip again.

ashyx said:
You didnt read my previous post correctly.
You don't need Magisk to FORMAT DATA.
The FORMAT DATA button is right there under the wipe options.
However what you did would have formatted DATA anyway.
Now do the same for the system partition after formatting DATA.
Do not reboot just check DATA and SYSTEM can be mounted then try and install the zip again.
Click to expand...
Click to collapse
Formatted the data and the system. Verified they were both mounted. Then attempted to flash the ROM.
Error 7 message still appearing. As does the unable to mount hidden.

TheBigby said:
Formatted the data and the system. Verified they were both mounted. Then attempted to flash the ROM.
Error 7 message still appearing. As does the unable to mount hidden.
Click to expand...
Click to collapse
What device is the ROM intended for?

ashyx said:
What device is the ROM intended for?
Click to expand...
Click to collapse
Have tried multiple ROMs, all intended for either the t810 or the t815. They include Lineage, Resurrection Remix, Paranoid Android, AOSP, and a couple more besides.

TheBigby said:
Have tried multiple ROMs, all intended for either the t810 or the t815. They include Lineage, Resurrection Remix, Paranoid Android, AOSP, and a couple more besides.
Click to expand...
Click to collapse
It may be that the system partition sizes are different?

Unknown. I have tried reflashing the stock firmware and that still failed in Odin.
I have given up at this point and restored from a backup. Thanks for the help however.

Same issue with Lineage 15.1

TheBigby said:
I have a rooted SM-t817t and have been attempting to flash Lineage 14.1 to it through TWRP 3.1.0-1_ashyx.
I have tried to flash with the gts210ltexx and the gts210wifi and the results are the same, receive the Error 7 message.
After reading up on other threads I attempted to alter the script to either tell it that the ROM is for the gts210ltexx or just remove it entirely and still getting the error.
Also attempted to run it without authentication.
I have read that the t817x tablets can be flashed with the t810 ROMs but have had zero success with doing so at this time.
I am unsure how to proceed from this point.
Click to expand...
Click to collapse
Can you share root procedure for the sm-t817t my roommate has one for sale, I'll only buy it if I can root it though.

[HELP] [URGENT] ONLY OxygenOS not Booting up !!!!

Hi guys
I am having a weird issue , I am able to flash ANY custom ROM ( mark my words "any") be it skydragon os, havoc os, lineage os but I am unable to flash OxygenOS (tried 5.0.7 and 5.0.8) . When I start the first boot after flashing the OOS zip file, it always get stuck on boot animation and the animation goes on forever. Please Help !!!!!
Note:
- Have tried with different versions of TWRP but no success
- Always Did a clean install
- When after being stuck at boot animation for 40 mins , i FORCE restarted my phone to recovery and found that all system files and folders have been made as normally so i think there was no error in flashing process but still ROM not booting up.
Also:
- If someone has successfully booted the latest OOS from scratch ( I mean clean install) so please can you provide your ( links !)
1. TWRP file
2. OOS zip file

PreciousPulkit said:
Hi guys
I am having a weird issue , I am able to flash ANY custom ROM ( mark my words "any") be it skydragon os, havoc os, lineage os but I am unable to flash OxygenOS (tried 5.0.7 and 5.0.8) . When I start the first boot after flashing the OOS zip file, it always get stuck on boot animation and the animation goes on forever. Please Help !!!!!
Note:
- Have tried with different versions of TWRP but no success
- Always Did a clean install
- When after being stuck at boot animation for 40 mins , i FORCE restarted my phone to recovery and found that all system files and folders have been made as normally so i think there was no error in flashing process but still ROM not booting up.
Also:
- If someone has successfully booted the latest OOS from scratch ( I mean clean install) so please can you provide your ( links !)
1. TWRP file
2. OOS zip file
Click to expand...
Click to collapse
If you're coming from a decrypted data partition and then flash stock OOS and nothing else, it will re-encrypt your data. This could take a long time.
I recently did some testing of TWRP for fixing formatting and decryption (see https://forum.xda-developers.com/on...al-twrp-touch-recovery-t3742894/post78339714) and I did a totally clean install of OOS including formatting the data partition.
I used a TWRP version from this post https://forum.xda-developers.com/on...al-twrp-touch-recovery-t3742894/post78332159. The one I used is the very last one which is described as:
-----update2
This one fixes ext4 encryption on Pie: https://androidfilehost.com/?fid=11410963190603866112
PS: you can get the OOS 5.0.8 zip from https://www.oneplus.com/au/support/softwareupgrade
Sent from my OnePlus3T using XDA Labs

BillGoss said:
If you're coming from a decrypted data partition and then flash stock OOS and nothing else, it will re-encrypt your data. This could take a long time.
I recently did some testing of TWRP for fixing formatting and decryption (see https://forum.xda-developers.com/on...al-twrp-touch-recovery-t3742894/post78339714) and I did a totally clean install of OOS including formatting the data partition.
I used a TWRP version from this post https://forum.xda-developers.com/on...al-twrp-touch-recovery-t3742894/post78332159. The one I used is the very last one which is described as:
-----update2
This one fixes ext4 encryption on Pie: https://androidfilehost.com/?fid=11410963190603866112
PS: you can get the OOS 5.0.8 zip from https://www.oneplus.com/au/support/softwareupgrade
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Exactly How Much Time can the re-encryption process could take?? Cause I gave it good 1 hour
Also to make sure i am getting it right , you mean to say that i should use the TWRP file you mentioned below your statement
"-------update 2" or is it some (img file) that i need to flash through TWRP

BillGoss said:
If you're coming from a decrypted data partition and then flash stock OOS and nothing else, it will re-encrypt your data. This could take a long time.
I recently did some testing of TWRP for fixing formatting and decryption (see https://forum.xda-developers.com/on...al-twrp-touch-recovery-t3742894/post78339714) and I did a totally clean install of OOS including formatting the data partition.
I used a TWRP version from this post https://forum.xda-developers.com/on...al-twrp-touch-recovery-t3742894/post78332159. The one I used is the very last one which is described as:
-----update2
This one fixes ext4 encryption on Pie: https://androidfilehost.com/?fid=11410963190603866112
PS: you can get the OOS 5.0.8 zip from https://www.oneplus.com/au/support/softwareupgrade
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
To Avoid Any Further Confusion , Could You Give me step by step instructions for what to do , please?
Please also give me details to which TWRP to use and all the configurations ( like ext4 or f2fs on system or data , whether to use format button, or advanced wipe) all that! Thanks in advance

Issue solved !!
How I solved ?
1. Using TWRP 3.2.2-0 I first Formatted data.
2.Then used advanced wipe to clean everything.
3.Then using change file system option in WIPE category changed my "data" partition from whatever to f2fs.
4.Then changed back to ext4.
5.Then changed back to f2fs.
6.Using PC transferred OOS zip file (5.0.8) to internal storage.
7.Flashed The file
8.Bingo !!! Phone booted up without a problem
Thanks @BillGoss , your provided links helped alot, though i used nothing from it but they helped me to recognize what the problem was, it was i think an encyption as well as changed file system format issue due to my previous flashing of pie roms.:good:

PreciousPulkit said:
How I solved ?
1. Using TWRP 3.2.2-0 I first Formatted data.
2.Then used advanced wipe to clean everything.
3.Then using change file system option in WIPE category changed my "data" partition from whatever to f2fs.
4.Then changed back to ext4.
5.Then changed back to f2fs.
6.Using PC transferred OOS zip file (5.0.8) to internal storage.
7.Flashed The file
8.Bingo !!! Phone booted up without a problem
Thanks @BillGoss , your provided links helped alot, though i used nothing from it but they helped me to recognize what the problem was, it was i think an encyption as well as changed file system format issue due to my previous flashing of pie roms.:good:
Click to expand...
Click to collapse
Well done. And because you worked this out yourself, you've learnt a lot.
Sent from my OnePlus3T using XDA Labs

[Recovery][Exynos][Unofficial] Upstreamed TWRP Android-8.1

Unofficial TWRP Upstream for hero2lte
- TWRP 3.3.0-0
- Built on top of latest kernel source and upstreamed to 3.18.138
- Support for Samsung ROMs and can mount data after using them
- Code was cleaned up a lot and it should be more stable.
Credits to Ivan Meler for kernel and device sources and exynos-linux-stable for the upstreaming of linux kernel for our devices.
Instructions:
How to install TWRP recovery.img
1. Boot into an existing TWRP build
2. Download recovery image.
3. Copy TWRP image to your device
3. Click the 'Install' button
4. Click the 'Install Image' button
5. Navigate to where you downloaded the image and click on it
6. Select 'Recovery' partition option from the list, and swipe to confirm flash
7. Reboot back into recovery and you'll be in the updated recovery.
--
How to install Odin recovery.tar
1. Download Odin3 v3.13.1
2. Download Odin flashable
4. Restart your device in to Download mode (by holding Vol- & Home & Power)
5. Connect your device to your computer
6. Click 'AP' and select the .tar image you downloaded
7. Click the 'Start' button to flash the recovery
8. Reboot into recovery (by holding Vol+ & Home & Power) after successful flash.
Downloads:
16-04-19
————-
TWRP recovery.img
Odin recovery.tar
Sources: https://gitlab.com/developerlukeroms/twrp-hero
​

Thank you! I'm already using Tkkg1994's moded version but I guess you made some updates and improvments on it.
gonna flash it later.
edit: No freezing while changing time zone and language. Working really smooth. I think it's also faster while getting back-up and creating diggest.
Adding it to my signature since many people asking about mount data problems on custom rom threads. Once again thank you for the great work.

is there quota support like tkkg1994-version?

I flashed this version and everything went ok but i only noticed that battery level is always lower in twrp but not a big deal,thanks.

dangerhouse said:
is there quota support like tkkg1994-version?
Click to expand...
Click to collapse
Yep

Can I use it while having an android pie rom?(confused after reading the title that says android 8.1)

Champ16 said:
Can I use it while having an android pie rom?(confused after reading the title that says android 8.1)
Click to expand...
Click to collapse
I'm using it on pie port, working great. you can take it as Android 8.1+

Champ16 said:
Can I use it while having an android pie rom?(confused after reading the title that says android 8.1)
Click to expand...
Click to collapse
Yes, android 8.1 means the twrp base, not what rom it works for. it works perfectly on pie roms

huge thank you dude!!

turbolukex5 said:
Unofficial TWRP Upstream for hero2lte ​
Click to expand...
Click to collapse
Is there a way to make TWRP settings permanent? It reset to default after some time. (It's like that with official one too) also anychance to have it without Official TWRP app? I uninstall it but after 1st recovery boot it comes back again. Have to keep it disabled.​

The settings for twrp saved in internal sdcard... Don't delete the TWRP folder

wurstherpes said:
The settings for twrp saved in internal sdcard... Don't delete the TWRP folder
Click to expand...
Click to collapse
That really helped Thank you!

rroyy said:
Is there a way to make TWRP settings permanent? It reset to default after some time. (It's like that with official one too) also anychance to have it without Official TWRP app? I uninstall it but after 1st recovery boot it comes back again. Have to keep it disabled.
Click to expand...
Click to collapse
You can't if you wipe internal storage, plus theres an option to uncheck installing twrp app in the recovery.

Is it possible to add f2fs data and cache

Good working ty so much

Nice work
But can it keep data decrypted after I install magisk?
Currently using root with supersu

gupt07ash said:
Nice work
But can it keep data decrypted after I install magisk?
Currently using root with supersu
Click to expand...
Click to collapse
As long as dm-verity is disabled, it will keep decrypted, without this twrp it wouldnt mount to twrp although being decrypted

turbolukex5 said:
As long as dm-verity is disabled, it will keep decrypted, without this twrp it wouldnt mount to twrp although being decrypted
Click to expand...
Click to collapse
This worked like a charm. I can read internal partition over magisk now. But I'm getting an error while making a backup. the recovery says "E: recv error on uevent". this error does not interrupt the backup progress and the backup can still be completed but its an error I keep getting.

gupt07ash said:
This worked like a charm. I can read internal partition over magisk now. But I'm getting an error while making a backup. the recovery says "E: recv error on uevent". this error does not interrupt the backup progress and the backup can still be completed but its an error I keep getting.
Click to expand...
Click to collapse
E: recv error on uevent is harmless message, no need to worry about it.

turbolukex5 said:
E: recv error on uevent is harmless message, no need to worry about it.
Click to expand...
Click to collapse
Bruh if you made this, you're a legend!
I can finally use root hide and make full backups
Thanks :good: