Database Develop

[Q] help on CM11 EMMC install

I am trying to install CM11 EMMC to my nook HD+ with stock rom on it. The instruction I followed is here
http://forum.xda-developers.com/showthread.php?t=2600572
1.Download the initial sdcard image
2.ungzip and write to sdcard using dd (winimage or whatever for those stuck on Windows)
3.Instert the card into your nook and reboot
4.Flash the recovery image
5.Flash cm11 image
6.Flash whatever other extra things you need like gapps
7.remove the sdcard
8.reboot the nook
I did wipe data and cache after step 3. I finished steps 4 and 5. However, flashing gapps in step 6 failed with information of error in gapps zip file [status 6]. The gapps is downloaded from here
http://forum.xda-developers.com/showthread.php?t=2397942
I use the mini modular package. I am quite sure the gapps zip file is good since i have finished SD install with the gapps zip file. However, it failed in EMMC install. Now the nook can boot to CM11, but without any google stuff.
Any suggestion?

I'd suggest that you try a different, smaller size package (you can always add those apps not included later from the Playstore).
Also, if needed an alternate source for Gapss is http://wiki.cyanogenmod.org/w/Google_Apps, use the "small" version.

Thanks for the suggestion. Other gapps on http://forum.xda-developers.com/show....php?t=2397942 does not work. The gapps on the wiki page works, though it is for 4.4.2. I think the orginal thread on CM11 EMMC install should notice users on the possible problem.
digixmax said:
I'd suggest that you try a different, smaller size package (you can always add those apps not included later from the Playstore).
Also, if needed an alternate source for Gapss is http://wiki.cyanogenmod.org/w/Google_Apps, use the "small" version.
Click to expand...
Click to collapse

Status 6 install error
junl2000 said:
Thanks for the suggestion. Other gapps on http://forum.xda-developers.com/show....php?t=2397942 does not work. The gapps on the wiki page works, though it is for 4.4.2. I think the orginal thread on CM11 EMMC install should notice users on the possible problem.
Click to expand...
Click to collapse
I'm a total newbie to this but I think I have the same issue.... This is what I done and the results:
Used Win32imager onto 32gb Sandisk to write unpacked image of emmc-cwm-early3.1.img.gz then loaded onto card the following files:
cm-11-20141212-NIGHTLY-ovation.zip
cwm-recovery-ovation-6.zip
pa_gapps-stock-4.4.4-20141214-signed.zip
pa_gapps-modular-mini-4.4.4-20141214-signed.zip
Re-booted and did backup of stock and cleared/formatted internal card. Installed cwmrecovery images, and CM11 nightly. Tried installing to gapps stock and mini both came up with a Status 6 failed installation error .
Tried reverting to stock and couldn't recover due to error so re-installed CM and had same error. Copied off and removed restore apks to ensure enough space and tried again - still
status 6 error.
Checked to see whether script files has LF/CR but script file is dummy and the binary all seems to be in LF format. Running out of ideas as all of this is new to me.
So looks like i'm in same situation - HD+ which boots to CM but no stock googleapps.
I know it doesn't help but looks like same issue - any ideas?

grungewort said:
I'm a total newbie to this but I think I have the same issue.... This is what I done and the results:
Used Win32imager onto 32gb Sandisk to write unpacked image of emmc-cwm-early3.1.img.gz then loaded onto card the following files:
cm-11-20141212-NIGHTLY-ovation.zip
cwm-recovery-ovation-6.zip
pa_gapps-stock-4.4.4-20141214-signed.zip
pa_gapps-modular-mini-4.4.4-20141214-signed.zip
Re-booted and did backup of stock and cleared/formatted internal card. Installed cwmrecovery images, and CM11 nightly. Tried installing to gapps stock and mini both came up with a Status 6 failed installation error .
...
So looks like i'm in same situation - HD+ which boots to CM but no stock googleapps.
I know it doesn't help but looks like same issue - any ideas?
Click to expand...
Click to collapse
Did you try using the Gapps packages from http://wiki.cyanogenmod.org/w/Google_Apps? They are for CM11, the apps are a bit dated but after installation can be updated (via Google Playstore) to their most current version.

Status 6 install error solved
digixmax said:
Did you try using the Gapps packages from your CM link. They are for CM11, the apps are a bit dated but after installation can be updated (via Google Playstore) to their most current version.
Click to expand...
Click to collapse
Deleted the pa_gapps-stock-4.4.4-20141214-signed.zip file.
Downloaded the two files from your link:
gapps-kk-20140606-signed.zip
gapps-kk-20140105-signed.zip
dropped both onto the card, re-booted and installed the larger 20140606 version which installed without any error messages. Removed card and re-booted - extra apps all look in place. Will now make sure they all run OK.
Thanks very much for your help - much appreciated. Can you tell me what the difference is in the installers that make the PA versions crash or is that too long winded?
Regards
Grungewort

.3.2.4 Rollback Images

Hello All,
Warning: Do not flash these files unless you are on .3.2.4 or Nexus ROM 2.0.x.
Here are rollback images (prerooted) which will enable you to get back to .3.1.0
Instructions:
1. Backup your /data partition in Safestrap if desired and copy it to your computer
2. Flash the appropriate file for you device
3. From Safestrap do a factory reset
4. Reboot to 13.3.2.4 modified stock (the screen will go blank for about 15-20 seconds - no problem)
5. Do not connect to WiFi or register your kindle
6. Select Complete Setup Later
7. Copy the .3.1.0 stock update file to the root of your sdcard
8. Initiate update from device options.
Links
- Apollo Rollback Image
- Thor Rollback Image

Reserved

Thanks @ggow !

Thanks for this man.

What are the benefits to go back to 3.1.0 as 3.2.4 is fully rootable and necessary for Nexus 2.0?
I'm still using 3.1/Nexus 1.4 and planned to update the device to 3.2.4/Nexus2.0. But now I'm wondering if I just should keep the current installation.

Unlocked bootloader!

what steps do i take if i m using nexus 2.02 on stock slot?
i have the original stock image 3.2.4 backed up in TWRP if it helps

Warning
Thanks ggow, but this is a warning to all apollo (HDX 8.9) users - do not use file (with md5 hash: 0f9f3b084500b888fc66415a8539a341) to rollback attempt! If you downloaded file Apollo Rollback Image before and want to use it later, please redownload, @ggow just posted corrected file (with md5 hash: 119b5004e96a41eb073c8b324712fe23)

jeryll said:
Thanks ggow, but this is a warning to all apollo (HDX 8.9) users - do not use this file to rollback attempt!
@ggow you forgot to edit build.prop file, so after anyone boot from this file (md5 hash: 0f9f3b084500b888fc66415a8539a341), kindle will not continue with downgrade to 14.3.1.0 :crying:
No harm done for me, as I backuped everything I can, but beware, if you dont want problems (I found extremely difficult install anything through adb on this installed/running rollback ... you can try edit build.prop file to correct values for downgrade by yourself, but messing with build.prop is highly risky and small mistake and brick is for sure, so you have been warned) WAIT for ggow to upload correct rollback image, or correct edited build.prop for downgrade
Click to expand...
Click to collapse
I have taken the file offline, Sorry about that @jeryll, will correct file and re-upload.

The corrected Apollo rollback image is uploading now. I'll post the new link in the morning.
Sent from my Kindle Fire HDX using Tapatalk

nymica said:
Unlocked bootloader!
Click to expand...
Click to collapse
So the benefit is to install "TWRP Recovery" to be able to install any Custom Rom without Safestrap?

ands2 said:
So the benefit is to install "TWRP Recovery" to be able to install any Custom Rom without Safestrap?
Click to expand...
Click to collapse
Yes full TWRP recovery and yes we can effectively install any ROM we want.
Credit goes to @vortox for making it possible with his signature bypass tool.

Corrected Apollo Image
@jeryll,
The corrected Apollo Rollback Image is up.

Thanks
ggow said:
@jeryll,
The corrected Apollo Rollback Image is up.
Click to expand...
Click to collapse
Thank you sir, successfully rolled back to 14.3.1.0, installed TWRP 2.8.1.0 and now I will play a little with TWRP

ggow said:
Hello All,
1. Backup your /data partition in Safestrap if desired and copy it to your computer
2. Flash the appropriate file for you device
3. From Safestrap do a factory reset
4. Reboot to 13.3.2.4 modified stock (the screen will go blank for about 15-20 seconds - no problem)
5. Do not connect to WiFi or register your kindle
6. Select Complete Setup Later
7. Copy the .3.1.0 stock update file to the root of your sdcard
8. Initiate update from device options.
Click to expand...
Click to collapse
i followed the steps but not sure where it went wrong for me
step 2. that would be the 13.3.2.4_rollback for thor correct? (i have 7 inch fire hdx)
was not sure where to flash this - i used rom slot 2
that installs 13.3.0.9_user into rom slot2 (i dont understand why we still have to update to 13.3.1.0 i guess
13.3.0.9 is not vulnerable?)
following the rest of the steps and rebooting kindle fire system recovery comes up
would be nice to put a link to 13.3.1.0 stock into the OP i found it in the forum)
i did reboot kindle (didnt dare to do reset to factory defaults)
that gets me back to 13.3.0.9
retrying the steps and after reboot rebooting into safestrap i see
openrecovery script installing zip (13.3.1.0)
if i let this continue and reboot i get a flashing screen and then a black screen
what am i doing wrong
p.s. luckily i have safestrap so rom slot 1 and stock still work

2. Flash the appropriate file for you device
Does it mean: Flash the appropriate (rollback) file for you device (in safestrap) (to Stock ROM slot)?
ggow said:
Hello All,
Warning: Do not flash these files unless you are on .3.2.4 or Nexus ROM 2.0.x.
Here are rollback images (prerooted) which will enable you to get back to .3.1.0
Instructions:
1. Backup your /data partition in Safestrap if desired and copy it to your computer
2. Flash the appropriate file for you device
3. From Safestrap do a factory reset
4. Reboot to 13.3.2.4 modified stock (the screen will go blank for about 15-20 seconds - no problem)
5. Do not connect to WiFi or register your kindle
6. Select Complete Setup Later
7. Copy the .3.1.0 stock update file to the root of your sdcard
8. Initiate update from device options.
Links
- Apollo Rollback Image
- Thor Rollback Image
Click to expand...
Click to collapse

@shadowcliffs - yes flash the rollback image to the stock slot...

Guess the file has to be flashed to Stock ROM instead of any other rom slot.
andPS2 said:
i followed the steps but not sure where it went wrong for me
step 2. that would be the 13.3.2.4_rollback for thor correct? (i have 7 inch fire hdx)
was not sure where to flash this - i used rom slot 2
that installs 13.3.0.9_user into rom slot2 (i dont understand why we still have to update to 13.3.1.0 i guess
13.3.0.9 is not vulnerable?)
following the rest of the steps and rebooting kindle fire system recovery comes up
would be nice to put a link to 13.3.1.0 stock into the OP i found it in the forum)
i did reboot kindle (didnt dare to do reset to factory defaults)
that gets me back to 13.3.0.9
retrying the steps and after reboot rebooting into safestrap i see
openrecovery script installing zip (13.3.1.0)
if i let this continue and reboot i get a flashing screen and then a black screen
what am i doing wrong
p.s. luckily i have safestrap so rom slot 1 and stock still work
Click to expand...
Click to collapse

shadowcliffs said:
Guess the file has to be flashed to Stock ROM instead of any other rom slot.
Click to expand...
Click to collapse
Correct

Hi,
Thanks of all your efforts on this. Is it possible to flash the roll back image any other way than installing and using safestrap ?

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.

Updater process ended with ERROR: 1

Hello, help would be amazing as this is my 2nd day trying to root my xPeria XZ Premium!
I've finally flashed twrp , I'm trying to install this rom:
https://forum.xda-developers.com/xz-premium/development/kernel-sony-xz-premium-5-2018-t3784669
But I'm getting stuck when trying to install magisk, OR move any zip files from my SD card to my Internal Storage.
Could anyone guide me through how to resolve this? :crying:

Have unlocked boot loader?

Need to format data first

xStatiZx said:
Hello, help would be amazing as this is my 2nd day trying to root my xPeria XZ Premium!
I've finally flashed twrp , I'm trying to install this rom:
https://forum.xda-developers.com/xz-premium/development/kernel-sony-xz-premium-5-2018-t3784669
But I'm getting stuck when trying to install magisk, OR move any zip files from my SD card to my Internal Storage.
Could anyone guide me through how to resolve this? :crying:
Click to expand...
Click to collapse
Hey my dude follow these steps, in twrp select wipe->format data (You'll lose all your files) now try flash the rom, you should find a custom kernel for your device as well and install it after the rom. If the Kernel doesnt install magisk now would be a good time to do it :highfive:

Matthewwwww1998 said:
Hey my dude follow these steps, in twrp select wipe->format data (You'll lose all your files) now try flash the rom, you should find a custom kernel for your device as well and install it after the rom. If the Kernel doesnt install magisk now would be a good time to do it :highfive:
Click to expand...
Click to collapse
This isn't necessary. Just extract boot.img from whatever rom.zip you're using, flash that in recovery, reboot to recovery again and magisk should install.

murph187 said:
This isn't necessary. Just extract boot.img from whatever rom.zip you're using, flash that in recovery, reboot to recovery again and magisk should install.
Click to expand...
Click to collapse
You're a GOD. Thank You!!!!!

updater process ended with error: 1
I was able to install magisk but after that if i try to install nethunter I get this same error. I am using redmi 4(santoni). have installed lineage OS 15.1
Can someone please help me?
logs

I had similar error shown below while installing a custom ROM:
Error applying update: 7 (ErrorCode:: kInstallDeviceOpenError )Updater process ended with ERROR: 1 Error installing zip file
Solved by using slightly older version of TWRP

i try and didnt work how to extract boot image in steps ??

magicstep said:
I had similar error shown below while installing a custom ROM:
Error applying update: 7 (ErrorCode:: kInstallDeviceOpenError )Updater process ended with ERROR: 1 Error installing zip file
Solved by using slightly older version of TWRP
Click to expand...
Click to collapse
which version you use

murph187 said:
This isn't necessary. Just extract boot.img from whatever rom.zip you're using, flash that in recovery, reboot to recovery again and magisk should install.
Click to expand...
Click to collapse
Hi, which option may i have to choose? there are 4 options

magicstep said:
I had similar error shown below while installing a custom ROM:
Error applying update: 7 (ErrorCode:: kInstallDeviceOpenError )Updater process ended with ERROR: 1 Error installing zip file
Solved by using slightly older version of TWRP
Click to expand...
Click to collapse
3.2.2 worked for me.

In my case unmounting all the partitions fixed it for me, the boot.img method didn't work.

magicstep said:
I had similar error shown below while installing a custom ROM:
Error applying update: 7 (ErrorCode:: kInstallDeviceOpenError )Updater process ended with ERROR: 1 Error installing zip file
Solved by using slightly older version of TWRP
Click to expand...
Click to collapse
I had flashed new version on firmware but forgot to update TWRP recovery that is why I was getting this error. I updated TWRP recovery. also flashed boot.img image then I was able to fix this issue.

guys please help me i have xiaomi mi a2 lite whit twrp 3.5.0_9 installed and unlocked bootloader i downloaded android 11 rom link: https://forum.xda-developers.com/t/rom-11-0-daisy-aosp-11-0.4167961/. When i go to recovery mode i flash the rom and appears this error: Updater process ended whit error: 1 to flash additional zips please reboot recovery to switch to the updated slots. Error installing zip file rom.zip. please help me.
THANKS

samyxy said:
guys please help me i have xiaomi mi a2 lite whit twrp 3.5.0_9 installed and unlocked bootloader i downloaded android 11 rom link: https://forum.xda-developers.com/t/rom-11-0-daisy-aosp-11-0.4167961/. When i go to recovery mode i flash the rom and appears this error: Updater process ended whit error: 1 to flash additional zips please reboot recovery to switch to the updated slots. Error installing zip file rom.zip. please help me.
THANKS
Click to expand...
Click to collapse
I was having the same issue... After hours of research I finely managed to fix it. Try the following:
1 - Install TWRP (I also had the 3.5.0_9 version).
2 - Format data and wipe all the advanced options possible.
3 - Download the program "payload_dumper-win64".
3.1 - Following the payload dumper instructions, I've copied the payload.bin from my custom ROM to the payload_input folder.
3.2 - Execute payload_dumper.exe and wait, a lot!
3.3 - Copy the resulted files (boot.img, system.img, vendor.img) in to the phone.
4 - In TWRP, go to install, select from images, and, one by one, install the images you've just copied.
4.1 - Note that during the install process, you will have to select the correct "slots" to flash the images. In my case, there where to options for system and vendor. I've chosen the "System Image" and "Vendor Image" option.
5 - Restart.
That's it! I didn't had to change slots nor wipe data after the installation... I don't know if this was the correct approach, but after many tries this is what worked for me
Sorry about my bad english...

Sometimes it is caused due to corrupted file. While transferring file through MTP it is likely to corrupt large files. I had the same problem. Then I tried copying file while in TWRP (sure it is also MTP) and it worked.

PendiukG said:
I was having the same issue... After hours of research I finely managed to fix it. Try the following:
1 - Install TWRP (I also had the 3.5.0_9 version).
2 - Format data and wipe all the advanced options possible.
3 - Download the program "payload_dumper-win64".
3.1 - Following the payload dumper instructions, I've copied the payload.bin from my custom ROM to the payload_input folder.
3.2 - Execute payload_dumper.exe and wait, a lot!
3.3 - Copy the resulted files (boot.img, system.img, vendor.img) in to the phone.
4 - In TWRP, go to install, select from images, and, one by one, install the images you've just copied.
4.1 - Note that during the install process, you will have to select the correct "slots" to flash the images. In my case, there where to options for system and vendor. I've chosen the "System Image" and "Vendor Image" option.
5 - Restart.
That's it! I didn't had to change slots nor wipe data after the installation... I don't know if this was the correct approach, but after many tries this is what worked for me
Sorry about my bad english...
Click to expand...
Click to collapse
It's legit procedure. Also you don't need to manage slots here, caz recovery automatically does that for you.

Hello guys, i'm from Russia, sorry for my bad English. I using Poco X3 Pro, and i have some troubles. I wanted to install custom firmware. First ROM
delivered successfully, unlike the second. After clearing all sections except sd cart and otg, I tried to install the original MIUI build, but it didn't work. I downloaded the original MIUI, but still. When installing, it says: "Update process ended with ERROR: 1" The methods from the top didn't help, please help!

Sushanthn94 said:
updater process ended with error: 1
I was able to install magisk but after that if i try to install nethunter I get this same error. I am using redmi 4(santoni). have installed lineage OS 15.1
Can someone please help me?
logs
Click to expand...
Click to collapse
Kali Nethunter on redmi 4x (santoni) is updated here:
Releases · Neternels/android_kernel_xiaomi_msm8937
Redmi 4X (santoni) NetHunter Kernel. Contribute to Neternels/android_kernel_xiaomi_msm8937 development by creating an account on GitHub.
github.com
Follow it and flash firmwares (if needed).

Magisk 19.3 and Samsung GT-I9001 (LineageOS 14.1, TWRP 2.8.1.0) does not work

Hi,
my Samsung GT-I9001 runs with LineageOS 14.1 (Nougat 7.1.2):
https://forum.xda-developers.com/ga...opment/i9001-lineageos-galaxy-s-plus-t3793783
As recovery TWRP 2.8.1.0 (F2FS-support) is installed.
Wenn trying to install Magisk 19.3 using magisk-v19.3.zip via TWRP it does not work: Error message ""Error execute updater binary in zip" and no flash is done.
Any idea what is the reason? The TWRP 2.8.1.0 is the latest version I found for the I9001.
The I tried patching the stock-bootloader via the Magisk-Manager. The bootloader-file is a .tar-file, e.g. in
https://forum.xda-developers.com/showpost.php?p=24831012&postcount=1330.
Magisk works with .tar, too, but seems to exspect an .img-file inside. But inside the I9001-"Boot_loader.tar" is no .img-file but 3 .mbn-files and 1 .bin-file.
So I am asking for help. Is there no way using Magisk with the I9001 (and LineageOS 14.1/TWRP)?

You're not supposed to use the bootloader, but the boot image. Two very different parts of the system setup...
And since you have such an old TWRP you're going to have to use the patching method, but it is very far from certain that your device is compatible. Only way to know is to try though.

Oops. Sorry, my mistake. I am a newbie with this and until I was not aware of boot.img ... I supposed it as the "real" filename of the bootloader. And again learning something new. Thank a lot for teaching.
Fortunately I have made a backup of the stock-ROM with TWRP before flashing the ROM. In the backup I find the file boot.emmc.win. This seems to be the stock-boot.img. Is it corrcect that I only have to rename the file to boot.img?
If the I9001 is not compatible with Magisk, means patching of the boot.img would result in a not working code/boot.img (the patching-procedure itself worked w/o errors, but does thos mean, that the result is o.k.?) - is the real risk bricking the device?

That should be the boot image and it should work fine by just renaming it. But, if it's the boot image from the stock Samsung system it won't work with LineageOS. You'll find the boot image for the ROM inside the ROM zip.
If the boot image is incompatible the Manager will let you know by an error message. Save the installation log if that happens and it could possibly tell you in more detail what went wrong.
If everything goes smoothly and the Manager manages to patch the file without issue and you still end up not being able to boot your device after flashing it you can simply restore the unpatched boot image and everything will be back to normal again.

Thanks for the further explanations. But I am not sure understanding correct.
In my understanding of the Magisk-installation manual I have to use the original boot.img always, in every case.
Do I understand correct that this understanding is wrong and that I have to use for patching with the Magisk-Manager the specific boot.img of the actual running OS? So I have to extract the boot.img of the lineageos-14.1-.tar-file (or rename the boot.emmc.win from one of my later backups of the lineagos-14.1-system)?
I have tested patching meanwhile with the "original" boot.img from the old ("original") backup and also with a boot.img extracted from a complete stock-ROM I have found in the web. Magisk Manager patched both fles w/o problems.
btw: Need the patched file the name "boot.img" or doesn´t matter the ame of the patched file (when flashing with fastboot or Odin)?
Unfortunately - or fortunately - I was not able to flash the patched boot.img to the i9001:
adb can communicate with the i9001 when it is running normal (USB debug enabled) and attached via USB. But although Odin is realizing the i9001 attached in download-mode (what means that the USB-cable is working and the driver are installed) fastboot does not realize the i9001 attached in download-mode. I have tested a lot of cables, ports and USB-drivers - no success.
So I tried to flash the boot.img with Odin. For this the boot.img must be converted to a .tar- (or .tar.md5-)file. When searching for converting-tools I found the explanation how to change the output-format of the patched boot.img in Magisk-Manager to .tar. Unfortunately I do not find this option in the current/latest version of Magisk-Manager. What is wrong - is there a secret, a hidden way to activate this option or is this option available in older versions of Magisk Manager only - and if so can I use an older version only for patching and getting a .tar-boot-image-file?

What the documentation is talking about is indeed the untouched boot image of your currently running OS. Don't mix and match.
When flashing with Odin the image indeed need to be in tar-format. With the current Manager there is no option to change the output format because the Manager will take care of that itself. Feed it a tar file and it'll output a tar file. Unfortunately you'll likely get plain image files from the TWRP backups, so those files will be no good unless you convert them before patching.
But, you might not have to use Odin since you have TWRP. It can flash the patched boot image for you. No computer required...

Again thanks a lot for this teaching. I am a newbie in modifying, tuning, flashing smartphones, and although I have learned a lot in the last weeks there are yet a lot of thing I do not know.
I know that I can flash new OS as .zip-file with TWRP (and other files if the manual says that I have/can do it with TWRP ) but I did not know that I can flash with TWRP a boot.img-file. So I would like to ask for a brief guide how to do this. Or is this the same procedure as flashing any .zip-file?
Addition 1: TWRP 2.8.1.0 does not see/list the .img-Files ....
O.k., found in the web: Directly flashing .img: Version 2.8.4.0 and above ....
So I am back again where I started ... fastboot does not see the i9001 and Odin needs a .tar ...
Addition 2: In reg. of the boot.img of the actual used OS:
I have looked into the "original" flashed lineage-14.1-20180523-UNOFFICIAL-ariesve.zip and found the boot.img. But this boot.img is smaller (4.670 byte) than the boot.emmc.win of it´s backup (5.120 byte). In fact every boot.emmc.win of every TWRP-backup (doesn´t matter what OS I have tested) ist 5.120 bytes and larger than the boot.img of the .tar/.zip-file for flashing (different sizes). So if the files are not identical - how can just simply renaming the boot.emmc.win in boot.img result in a valid boot.img?

It's practically the same thing. You just have to switch to "Image" after choosing the install option and then pick what partition to flash to after selecting the file.

Didgeridoohan said:
It's practically the same thing. You just have to switch to "Image" after choosing the install option and then pick what partition to flash to after selecting the file.
Click to expand...
Click to collapse
But not in version 2.8.1.0 - and there is no newer TWRP for the i9001.

MarkFalk said:
But not in version 2.8.1.0 - and there is no newer TWRP for the i9001.
Click to expand...
Click to collapse
Yes. I'm going to forcefully introduce my palm to my face for a moment... Forgot about that tiny but crucial detail.
Just use the boot image file from the LineageOS zip. Patch it and flash the patched image to your device. If you can't get that working I'm going to have to hand this over to someone else, because I have practically zero knowledge on working with Samsung devices and their shenanigans.

Thanks. The small detail of "flashing" into the i9001 is the remaining problem.
As said fastboot does not see the i9001 in it´s download-mode although Odin sees the device and can flash e.g. the bootloader. Odin on the other hand needs a .tar-file and I do not find a way how to converting the (patched) boot.img into a .tar-file that Odin would accept as valid file.

In these cases I usually ask someone like @jenslody or @ianmacd. They usually have a lot more knowledge about Samsung stuff...

I have found a workaround:
1. Make a pure boot-backup with TWRP
2. Copy the backup-folder into/with a new name
3. Copy boot.emmc.win and boot.emmc.win.md5 from the backup to pc or root
4. Rename boot.emmc.win to boot.img
5. Patch boot.img with Magisk-Manager
6. Rename the result to boot.emmc.win
7. Copy boot.emmc.win to the new backup-folder
8. Make a RD5-hash of boot.emmc.win
9. Replace the hash in boot.emmc.win.rd5 with the new hash
10. Copy boot.emmc.win.rd5 to the new backup-folder
11. Boot into TWRP and restore boot from the new folder
It works with the i9001 and lineageOS14.1 and TWRP 2.8.1.0 and the newest Magisk, but it should work with all devices.