[Q] i9001 CWM update problems - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi, i have a problem upgrading from CM 11-20140216-UNOFFICIAL-dev_connection_team-ariesve (4.4.2 I9001XXKF8)
to CM11 (4.4.4) on my Samsung Galaxy S plus
http://forum.xda-developers.com/showthread.php?t=2579431
The problem is, that my existing CWM 6.0.3.5 refuses to update
to the required 6.0.4.9. I created a copy of these files on my phones internal
memory listed in the thread for latest CWM and TWRP. Checksums are ok.
Then i booted into CWM recovery -> install zip -> choose zip from sdcard -> and so on
But it quits installation with this error message:
Code:
Can't open /sdcard/blablabla.zip (bad)
The path is existing and so are the files. The displayed path is ok.
Does anyone know what to do? The last updates just went fine,
except my previous custom recovery was replaced by CWM when upgrading from CM9 to 10.
I think it was TWRP before, but i am not really sure. When it is possible i would like to replace CWM with TWRP again.

Bitmuncher said:
Hi, i have a problem upgrading from CM 11-20140216-UNOFFICIAL-dev_connection_team-ariesve (4.4.2 I9001XXKF8)
to CM11 (4.4.4) on my Samsung Galaxy S plus
http://forum.xda-developers.com/showthread.php?t=2579431
The problem is, that my existing CWM 6.0.3.5 refuses to update
to the required 6.0.4.9. I created a copy of these files on my phones internal
memory listed in the thread for latest CWM and TWRP. Checksums are ok.
Then i booted into CWM recovery -> install zip -> choose zip from sdcard -> and so on
But it quits installation with this error message:
Code:
Can't open /sdcard/blablabla.zip (bad)
The path is existing and so are the files. The displayed path is ok.
Does anyone know what to do? The last updates just went fine,
except my previous custom recovery was replaced by CWM when upgrading from CM9 to 10.
I think it was TWRP before, but i am not really sure. When it is possible i would like to replace CWM with TWRP again.
Click to expand...
Click to collapse
I had the same problem a couple of times before. I found out that zip file was corrupt, hence the Can't open .zip (bad) error.

Related

Can't Root Galaxy Mini (GT-S5570)

Hi
I've a Galaxy Mini with XWTN firmware (flashed via ODIN from here )
I had them with the stock recovery and without root, but due to the low memory I wanted to root them for install a sd-ext partition. I did these steps:
- Replaced the stock recovery with this and next with this
-Formatted the sd card using CWM for create a 256 MB sd-ext partition
- Attempted to root the phone flashing Universal_gb_root_v25.zip and Upd_1.zip. The two files failed and CWM show me an error status 7. Also I used SuperOneClick 2.3.3, but doesn't work
- I looked into the updater-script of flashable zips and I noticed that the "Universal_gb_root_v25.zip" updater-script contains a reference to "ro.product.device=GT-S5570L". I looked into the build.prop of my ROM and I noticed that "ro.product.device" is GT-S5570, not GT-S5570L. So, I edited the updater-script into the zip for match "GT-S5570", thinking I could solve the problem, but CWM continues to show me an status 7 error. The other zip I tried, "Upd_1.zip", have the "ro.product.device=GT-S5570" in their updater-script, but CWM show the error anyway.
Considering that these zips are for flash with stock recovery, and I'm using CWM, maybe if I use the stock recovery the zips works? Is there a way to back to stock recovery without flashing the whole rom in ODIN again? (due to data lose)
Thanks.
xsam123 said:
Hi
I've a Galaxy Mini with XWTN firmware (flashed via ODIN from here )
I had them with the stock recovery and without root, but due to the low memory I wanted to root them for install a sd-ext partition. I did these steps:
- Replaced the stock recovery with this and next with this
-Formatted the sd card using CWM for create a 256 MB sd-ext partition
- Attempted to root the phone flashing Universal_gb_root_v25.zip and Upd_1.zip. The two files failed and CWM show me an error status 7. Also I used SuperOneClick 2.3.3, but doesn't work
- I looked into the updater-script of flashable zips and I noticed that the "Universal_gb_root_v25.zip" updater-script contains a reference to "ro.product.device=GT-S5570L". I looked into the build.prop of my ROM and I noticed that "ro.product.device" is GT-S5570, not GT-S5570L. So, I edited the updater-script into the zip for match "GT-S5570", thinking I could solve the problem, but CWM continues to show me an status 7 error. The other zip I tried, "Upd_1.zip", have the "ro.product.device=GT-S5570" in their updater-script, but CWM show the error anyway.
Considering that these zips are for flash with stock recovery, and I'm using CWM, maybe if I use the stock recovery the zips works? Is there a way to back to stock recovery without flashing the whole rom in ODIN again? (due to data lose)
Thanks.
Click to expand...
Click to collapse
I think, you have followed the tutorial of rooting wrongly..
If you wanna root your mini, you can try this tutorial..
xsam123 said:
Hi
I've a Galaxy Mini with XWTN firmware (flashed via ODIN from here )
I had them with the stock recovery and without root, but due to the low memory I wanted to root them for install a sd-ext partition. I did these steps:
- Replaced the stock recovery with this and next with this
-Formatted the sd card using CWM for create a 256 MB sd-ext partition
- Attempted to root the phone flashing Universal_gb_root_v25.zip and Upd_1.zip. The two files failed and CWM show me an error status 7. Also I used SuperOneClick 2.3.3, but doesn't work
- I looked into the updater-script of flashable zips and I noticed that the "Universal_gb_root_v25.zip" updater-script contains a reference to "ro.product.device=GT-S5570L". I looked into the build.prop of my ROM and I noticed that "ro.product.device" is GT-S5570, not GT-S5570L. So, I edited the updater-script into the zip for match "GT-S5570", thinking I could solve the problem, but CWM continues to show me an status 7 error. The other zip I tried, "Upd_1.zip", have the "ro.product.device=GT-S5570" in their updater-script, but CWM show the error anyway.
Considering that these zips are for flash with stock recovery, and I'm using CWM, maybe if I use the stock recovery the zips works? Is there a way to back to stock recovery without flashing the whole rom in ODIN again? (due to data lose)
Thanks.
Click to expand...
Click to collapse
First...you were supposed to root first and then replace the recovery...
Second...I didnt wanted to thanks...
Sent from my GT-S5570 using xda app-developers app
Try flashing a custom rom in your phone They usually comes up with a super user access (it means that you are rooted )
[ROM][CM7.2][ODEXED][30-04-2013] New Experience v9.8.0 - xda-developers
http://forum.xda-developers.com/show....php?t=1648213
This rom also comes up with many scripts/tweaks!
This is the one that I'm using
Im not saying its the best, there are many roms that have different features !
Please press thanks if I helped!

[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

Issue with installation of rom with temporary cwm recovery by shaaan

I am having issues with the installation of a Custom ROM on my Galaxy S Advance.
I have done it before, and it went smoothly. But later I reverted back to official one.
Now I am doing it again. But having a few problems with the CWM recovery (v6.0.2.8). I am having an old file which was probably uploaded by Shaaan.
The file name is "update.zip".
I tried downloading the new file from one of his new threads, but that download infected my laptop with a large number of viruses, malwares and adwares that were on the host site. So I am using the old file itself.
So the issue is, I used the "root.zip" file to root my phone and it was done successfully as the Root Checker app also verified the root.
Later, I booted using the CWM Recovery.
Did the Wipe Data/ Fatory Reset.
Did Wipe Cache Data.
Did Wipe Dalvic Cache.
Then I moved to Installation of ROM.
When I select the option, "CHOOSE ZIP FROM SDCARD", there comes an error saying...
"E: Can't Mount /sdcard/"
I browsed the internet and found a solution that said CHANGING THE FILE SYSTEM OF THE SDCARD. So I did that too. Tried with NTFS as well as FAT32, but nothing happened.
I even tried to install by placing the ROM files in Internal Memory since they are not even getting cleaned after Wipe Data operation. But that too resulted in negative.
This is happening every time. By now, I have installed the official firmware 4 times, so as to start the process afresh, but no luck.
The ROM files are also not corrupted, as I have used them earlier.
Here are the images of the issue I am encountering. (Please tell how to upload images, as all that I can see is an option to add URL and not an image, also an error like posting 10 posts)
EXPECTING A SOLUTION TO IT ASAP, as the Official Jellybean version has again started to lag too much.

[Solved!] I want to update TWRP, but ...

Hi!
I have a Nook HD+ running CM 12.1 (Android 5.1.1). The tablet is not rooted. Right now I have TWRP v2.7.1.0 installed, but would like to update to a newer version.
Installing v2.7.1.0 was a breeze. I booted into recovery mode (ClockWorkMod at the time), then flashed an Ovation TWRP ZIP file that I downloaded online. Looking for the most recent Ovation version, it seems it's only available as an IMG file. I can't find a version of TWRP more recent than v2.7.1.0 for Ovation in a ZIP format. Since the tablet is not rooted, I can't flash the newer version using Flashify or similar apps (as far as I can tell, that is) since they all require root access. And I can't flash an IMG file with v2.7.1.0, since that feature wasn't included until a later version (v2.8.5.0 I think). Therein lies the problem. I need a newer version to update, but I can't update until I have a newer version!
I've struggled with the suggested methods of installing TWRP from an IMG file, and would really like to simply flash a ZIP file (I'm already pretty good at doing that). So I've come up with a possible method that sounds too easy and too good to be true. Examining the ZIP folder for v2.7.1.0 (using Linux Archive Manager), I can see that there is a recovery IMG file and a folder labeled META-INF. If I replaced the v2.7.10 recovery IMG file with a more recent TWRP IMG file and left the META-INF file as is, would that work? Or, does the META-INF folder only support v2.7.1.0?
Thanks for your help ... and for not laughing at my possibly nutty idea
MaydayMalone said:
Hi!
I have a Nook HD+ running CM 12.1 (Android 5.1.1). The tablet is not rooted. Right now I have TWRP v2.7.1.0 installed, but would like to update to a newer version.
Installing v2.7.1.0 was a breeze. I booted into recovery mode (ClockWorkMod at the time), then flashed an Ovation TWRP ZIP file that I downloaded online. Looking for the most recent Ovation version, it seems it's only available as an IMG file. I can't find a version of TWRP more recent than v2.7.1.0 for Ovation in a ZIP format.
Click to expand...
Click to collapse
More recent versions of TWRP in flashable zip for HD+ (ovation) are available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778, but you should check for their compatibility with your CM12.1 ROM.
...
I've struggled with the suggested methods of installing TWRP from an IMG file, and would really like to simply flash a ZIP file (I'm already pretty good at doing that). So I've come up with a possible method that sounds too easy and too good to be true. Examining the ZIP folder for v2.7.1.0 (using Linux Archive Manager), I can see that there is a recovery IMG file and a folder labeled META-INF. If I replaced the v2.7.10 recovery IMG file with a more recent TWRP IMG file and left the META-INF file as is, would that work? Or, does the META-INF folder only support v2.7.1.0?
...
Click to expand...
Click to collapse
I have successfully updated flashable recovery zip files (for both the Nook NT and Nook HD+) with more updated recovery images by using an archive manager tool (mostly Windows 7-zip) to swap the recovery img files, just as you're contemplating -- see my brief discussion of this at https://forum.xda-developers.com/showpost.php?p=71402570&postcount=270.
There is a possibility that the update-binary and updater-script in the given flashable zip are not compatible with the newer recovery file image (in which case one would get an error trying to flash it) but I have yet to encounter it, presumably because the versions of old and new recovery images involved have been relative close to one another.
digixmax said:
More recent versions of TWRP in flashable zip for HD+ (ovation) are available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778, but you should check for their compatibility with your CM12.1 ROM.
I have successfully updated flashable recovery zip files (for both the Nook NT and Nook HD+) with more updated recovery images by using an archive manager tool (mostly Windows 7-zip) to swap the recovery img files, just as you're contemplating -- see my brief discussion of this at https://forum.xda-developers.com/showpost.php?p=71402570&postcount=270.
There is a possibility that the update-binary and updater-script in the given flashable zip are not compatible with the newer recovery file image (in which case one would get an error trying to flash it) but I have yet to encounter it, presumably because the versions of old and new recovery images involved have been relative close to one another.
Click to expand...
Click to collapse
Thanks for your response. You told me exactly what I needed to know.
I have viewed D. Andrei Măceș dropbox in the past, but I neglected to check it for TWRP updates (my bad). I'll keep this in mind the next time I want to explore new possibilities for my HD+.
The idea of creating my own zip was a temptation that I couldn't resist (since I was now feeling confident that I wouldn't brick my tablet, blow up Pittsburgh, or be responsible for something equally catastrophic). So, instead of downloading a zip file from the dropbox, I used Linux Archive Manager (I switched to Linux Mint some time ago to escape the more-frequent-than-I-could-bear crashes with Windows), to delete the file named recovery.img in the v2.7.1.0 zip, then inserted a recovery.img file for TWRP v3.1.1.0 in it's place. It worked perfectly, and I feel like a genius (I'm very easily impressed)!
Thanks for letting me know that my idea wasn't as dumb as I feared it might be.
digixmax said:
More recent versions of TWRP in flashable zip for HD+ (ovation) are available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778, but you should check for their compatibility with your CM12.1 ROM.
I have successfully updated flashable recovery zip files (for both the Nook NT and Nook HD+) with more updated recovery images by using an archive manager tool (mostly Windows 7-zip) to swap the recovery img files, just as you're contemplating -- see my brief discussion of this at https://forum.xda-developers.com/showpost.php?p=71402570&postcount=270.
There is a possibility that the update-binary and updater-script in the given flashable zip are not compatible with the newer recovery file image (in which case one would get an error trying to flash it) but I have yet to encounter it, presumably because the versions of old and new recovery images involved have been relative close to one another.
Click to expand...
Click to collapse
Hello,
I tried using the TWRP 3.0.1.0 - ovation and 2.8.7.5. and they both receive the status 7 error:
"This package is for device: ovation ; this device is .
E: Error in /external+sd/twrp-3.0.1-0-ovation.zip
(Status 7)
Installation aborted"
I currently run on CWM Recovery 6.0.4.6, with cyanogenbootloader, lineage os 14.1. Unfortunately I cannot turn off my device (Nook HD+) no matter what, it keeps turning itself on until it empties battery (if I don't pay attention).
I keep trying to install the zips from CWM Recovery but I cannot do it.
Is there any way for me to install TWRP from CWM?
Thank you
pnkye said:
Hello,
I tried using the TWRP 3.0.1.0 - ovation and 2.8.7.5. and they both receive the status 7 error:
"This package is for device: ovation ; this device is .
E: Error in /external+sd/twrp-3.0.1-0-ovation.zip
(Status 7)
Installation aborted"
Click to expand...
Click to collapse
Did you use one of the flashable TWRP zip files from https://www.mediafire.com/#6a4rivb8kkdfu?
I currently run on CWM Recovery 6.0.4.6, with cyanogenbootloader, lineage os 14.1. Unfortunately I cannot turn off my device (Nook HD+) no matter what, it keeps turning itself on until it empties battery (if I don't pay attention).
Click to expand...
Click to collapse
Did you tried holding down the power button for 30+ sec?
Thank you for the answer.
1. The link doesn't work (https://www.mediafire.com/#6a4rivb8kkdfu?) leads me to an upload page.
2. I tried all the options I could find online. If I let it be for 1 week (I use it for reading and sometimes youtube) it turns itself on at some point and the battery goes empty. And it is so hard to turn it on again. When I plug it for charging the battery and is completely empty, the led stays green - instead of orange - for a long time and is not responsive to anything I do until it reaches 80%+ , so I let it be for 2hrs while plugged.
3. What I try to do is actually root it for overclocking or make it a little bit faster because it lags in every thing I do with it. Although in some variants of the Android which I installed over the years it used to be more responsive.
Unfortunately I cannot root it because CWM doesn't recognize the install of SuperSU zip from Lineage website. Do you have any advice on that?
Thanks
pnkye said:
...
The link doesn't work (https://www.mediafire.com/#6a4rivb8kkdfu?) leads me to an upload page.
Click to expand...
Click to collapse
Try this link: https://www.mediafire.com/folder/6a4rivb8kkdfu/Nook+HD+
digixmax said:
Try this link: https://www.mediafire.com/folder/6a4rivb8kkdfu/Nook+HD+
Click to expand...
Click to collapse
Thank you very much! You really helped me with this one!
I just did it! Flashed it with the cwm.flashable.twrp zip from your link!
I run now the TWRP 3.0.1-0.
I couldn't flash any higher versions (3.2.x) directly from this installed version
Anyway my booting time is faster and so far (1min time) the turning on/off procedure works normal, as it should be.
What lineage OS version is the best one for the nook hd+?
I just installed the 14.1 version from the lnos-ovation-ota-NJH47F.181223.zip found at: https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778
This version, however, has landscape mode as default viewing mode and it keeps spinning here and there.
At the moment I find myself in the latest stage of my process: rooting the device so I can try and overclock it.
Trying to install the official lineage "addonsu-14.1-arm-signed.zip" , from their website (https://download.lineageos.org/extras), but it doesn't work.
I mean it installs it successfully in the TWRP recovery. It is enabled in the developer options for both Apps and Adb. But the root checker app says it is not rooted.
Is there a proper way to root it? If so could you please share a solution when you have time?
Also any ideas on how to properly overclock (make the tablet a little snappier, besides the animation scale option from dev options)?
Cheers!
pnkye said:
I just did it! Flashed it with the cwm.flashable.twrp zip from your link!
I run now the TWRP 3.0.1-0.
I couldn't flash any higher versions (3.2.x) directly from this installed version
Click to expand...
Click to collapse
There should be an option in TWRP to "flash image" you can use to directly flash .img binary of a newer TWRP version.
What lineage OS version is the best one for the nook hd+?
I just installed the 14.1 version from the lnos-ovation-ota-NJH47F.181223.zip found at: https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778
This version, however, has landscape mode as default viewing mode and it keeps spinning here and there.
Click to expand...
Click to collapse
You should be able to disable auto-rotation in Settings->Display.
At the moment I find myself in the latest stage of my process: rooting the device so I can try and overclock it.
Trying to install the official lineage "addonsu-14.1-arm-signed.zip" , from their website (https://download.lineageos.org/extras), but it doesn't work.
I mean it installs it successfully in the TWRP recovery. It is enabled in the developer options for both Apps and Adb. But the root checker app says it is not rooted.
Click to expand...
Click to collapse
Try disabling and exit Settings->Developer Options, then come back and re-enable it.
digixmax said:
There should be an option in TWRP to "flash image" you can use to directly flash .img binary of a newer TWRP version.
You should be able to disable auto-rotation in Settings->Display.
Click to expand...
Click to collapse
My device is with default landscape. If I disable it it stays in landscape and never goes to portrait.
digixmax said:
Try disabling and exit Settings->Developer Options, then come back and re-enable it.
Click to expand...
Click to collapse
It still doesn't work.
Thanks for the overall guidance!

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).

Categories

Resources