Related
Hi i just did wipe and formatted system. Now i got (status 7) error and installation aborted when installing rom from external sd_card. :crying:
What should i do now i noticed 6.0.2.8 ver cwm.
Hallako said:
Hi i just did wipe and formatted system. Now i got (status 7) error and installation aborted when installing rom from external sd_card. :crying:
What should i do now i noticed 6.0.2.8 ver cwm.
Click to expand...
Click to collapse
install cwm 6.0.3.1
How
Flying_Bear said:
install cwm 6.0.3.1
Click to expand...
Click to collapse
I tried searching how to install it but can i boot now?
Is there way to install it with older cwm ?
sorry i am little new with android devices.
and ofc i dont have backup
Hallako said:
I tried searching how to install it but can i boot now?
Is there way to install it with older cwm ?
sorry i am little new with android devices.
and ofc i dont have backup
Click to expand...
Click to collapse
install rom toolbox from google play store, install latest cwm from there, and then flash werewolf rom
but
Flying_Bear said:
install rom toolbox from google play store, install latest cwm from there, and then flash werewolf rom
Click to expand...
Click to collapse
But i cant boot now when formatted system
Re flash official 20a with kdz flasher then
Flying_Bear said:
Re flash official 20a with kdz flasher then
Click to expand...
Click to collapse
i am now trying but when i start update flasher crashes when extracting kdz.
log
oblem signature:
Problem Event Name: APPCRASH
Application Name: KDZ_FW_UPD.exe
Application Version: 1.0.4.4
Application Timestamp: 4ac2a689
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.17514
Fault Module Timestamp: 4ce7bafa
Exception Code: e06d7363
Exception Offset: 0000b727
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1035
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
><
You can do several things:
If your adb is working, i think you can push latest cwm to recovery partition. Find dexters topic on how to do it, but instead of 6.0.2.8, download latest from cwm website and push it.
Alternatively, download zaiben rom, put it on sdcard ext and flash it, then use rom manager etc.
Another thing you can do is search for topic "fixed cm flashable", and flash that cm, then update to latest.
There is one more way, you can edit cm's zip and delete lines checking for device id.
Good luck
Flying_Bear said:
><
You can do several things:
If your adb is working, i think you can push latest cwm to recovery partition. Find dexters topic on how to do it, but instead of 6.0.2.8, download latest from cwm website and push it.
Alternatively, download zaiben rom, put it on sdcard ext and flash it, then use rom manager etc.
Another thing you can do is search for topic "fixed cm flashable", and flash that cm, then update to latest.
There is one more way, you can edit cm's zip and delete lines checking for device id.
Good luck
Click to expand...
Click to collapse
Oh right ill try all i can.
Thanks for helping and that luck is needed.
i got it working after adb push latest cwm and then cm.
UPDATED
Since these issues have been fixed in newer builds but as a s2 hd lte users, we have no option but to use older builds which have many issues. I found a workaround for them. If you are having wifi or other radio related issues, contact the ROM developer. This post can't help you. Flashing latest baseband helped me and could work well for you as well. Lets talk about two of the most common bug that haunts our device
1 Apps auto closing->( only for LMY48G builds,if you have newer builds,just flash gapps and reboot. to check go to about phone-> build number)
This is a webview related bug.
Download latest gapps from opengapps.org.
I prefer aroma installer as smaller packages don't have webview included,which will make the bugs worse.
Flash gapps. Dont forget to select 'android system webview' from the aroma installer.
Download the zip file from the
link
https://mega.nz/#!0d5Tiaja
Decryption key !JAG5Im-T75YN1CKIOiOcyDDaBH2ILD6dzwxw4xnhrBc
Extract "libwebviewchromium.so" and "libwebviewchromium_plat_support.so"
It is taken from stock samsung ROM and only works on armv7 devices.
Copy them to /system/libs using ESfile explorer or any other root explorer.
Overwrite the original file if asked.
give permission (-rw-r-r) to both file
Reboot to recovery
Flash this file "cm12.1 android system webview" from this thread(only for cm12.1, will cause bootloops in Xenon hd and resurrection remix)
http://forum.xda-developers.com/xperia-m/themes-apps/mod-google-android-webview-t3109216
Apps will now no longer auto close in your face without warning
((-> After testing for a month, I concluded that these steps are optional and use only if you want to have google android webview instead of cm12.1's built in 'android system webview'))
2) Now the most important part, random reboots.
This was reported on earlier builds of lollipop by many users.This is mostly caused by minfree that android uses to manage memory. If you navigate to sys/modules/lowmwemorykiller/parameters you can see 4 or 5 files. two of those files have wrong permissions. They are "adj" and "minfree".
If you give them (rw-r-r) permissions, you can adjust minfree values. the stock values are too aggressive and would cause constant reboots, freezes. Download romtoolbox, navigate to task manager, swipe left. you can choose to use any presets. i use 8,12,24,60,70,80 as minfree values.
Dont check "auto apply on boot" because you need to repeat this whole process after a reboot as those two files"adj and minfree" will be replaced from boot.img on boot by kern
Permanent fix: unpack boot.img. Navigate to ramdisc and open init.rc file in notepad. Find the line
chmod 0220 /sys/module/lowmemorykiller/parameters/minfree
chmod 0220 /sys/module/lowmemorykiller/parameters/adj
Change both values to 0644
save and close
Repack boot.img
Put it back inside the zipfile using winrar or use flashify from playstore to update boot.
I found tool to unpack qualcomm boot.img from this website. Full credits to the developer who made this tool.
http://www.droidbeep.com/how-to-unpa...-img-qualcomm/
download ROM toolbox and apply your preferred values
3. Low storage and optimizing apps(configuring ART compiler)
After google updated android runtime from JIT to ART, apps take up huge space and "optimizing app" takes forever. But there is workaround for that too.
1)Open build.prop in any text editor.
2) find these two lines:
dalvik.vm.image-dex2oat-filter=........(blah blah)
dalvik.vm.dex2oat-filter=...(blah blah)
3) Change both of these lines to
dalvik.vm.image-dex2oat-filter=speed
dalvik.vm.dex2oat-filter=Verify-none
If these lines doesn't exist, in your build.prop,you have to add them manually
4) save your build.prop file
5) reboot to recovery and wipe dalvik cache
After this check your storage space, You will have plenty of storage left and optimizing apps should be faster. It works just like old JIT compiler from older android versions.
if this doesn't work for you, you have to edit these same lines from default.prop by unpacking boot.img
I have fixed this issue by editing init.rc inside boot.img, but i dont know if i should post it here or not.
diabolicalprophecy said:
I have fixed this issue by editing init.rc inside boot.img, but i dont know if i should post it here or not.
Click to expand...
Click to collapse
please, for e120s
OIAUser said:
please, for e120s
Click to expand...
Click to collapse
Please extract Boot.img from the zip file and send it. I don't have boot.img for e120s, or i can tell you how to do it yourself if you are interested.
Tell me how, I'll try to do it myself.
I will be very grateful
any way to fix wifi & soft reboot on e120s ???
if you need log or any thign about my devices i will link it to you!!
OIAUser said:
Tell me how, I'll try to do it myself.
I will be very grateful
Click to expand...
Click to collapse
I have updated the post on how to do it. You can find the required tool here with detailed instructions
http://www.droidbeep.com/how-to-unpack-and-repack-boot-img-qualcomm/
kdlinh said:
any way to fix wifi & soft reboot on e120s ???
if you need log or any thign about my devices i will link it to you!!
Click to expand...
Click to collapse
You can try wiping phone efs through odin in order to fix radio issues
1 Download stock jb rom
2 Check "phone efs clear". This is most important.
3 Click pda
4 click start
5 wait for phone to boot up
6 go to settings->software update to check if you are running latest jb build. Soft reboots and radio issues are usually caused by old baseband version.
7 Proceed with usual old way to install lollipop.
This way odin will wipe your efs settings to rebuild from scratch.
still ploblem ??? :? wait how to clear efs
at first time i have checked this box but failded ,
kdlinh said:
still ploblem ??? :? wait how to clear efs
at first time i have checked this box but failded ,
Click to expand...
Click to collapse
you need Stock jb rom to do this. I also had this issue in e120l, but clearing phone efs fixed radio issues for me. you need odin3v 1.85 and samsung usb drivers.
You can find it alongside " phone bootloader update". Be careful not to select this one by accident.
diabolicalprophecy said:
you need Stock jb rom to do this. I also had this issue in e120l, but clearing phone efs fixed radio issues for me. you need odin3v 1.85 and samsung usb drivers.
You can find it alongside " phone bootloader update". Be careful not to select this one by accident.
Click to expand...
Click to collapse
i have checked this efs box but failed :crying::crying:
kdlinh said:
i have checked this efs box but failed :crying::crying:
Click to expand...
Click to collapse
which firmware did you tried this with? i have no problem doing this with astap 8 or stock jb rom for e120l.
http://i4khmers.blogspot.com/2015/09/official-firmware-samsung-galaxy-sii.html try this
its E120SKSJMH3 version
Once again, I read the instructions .. understand. But in the archive libraries are no libvebvievhromium .so file. "There's a file" libwebviewchromium_loader. "This is critical?
OIAUser said:
Once again, I read the instructions .. understand. But in the archive libraries are no libvebvievhromium .so file. "There's a file" libwebviewchromium_loader. "This is critical?
Click to expand...
Click to collapse
you get "libWebviechromium .so" file while installing gapps package. Go to opengapps.org and download aroma installer.
there are two files in the archive i uploaded, libwebviwechromium_loader.so and libwebviewplatsupport.so. You need to extract and replace those files in system-> libs after flashing gapps package. The built in webview will cause random apps shutdowns. this file is critical. You need libwebviewchromium_loader to start webview app. your system will not function properly without it.
diabolicalprophecy said:
which firmware did you tried this with? i have no problem doing this with astap 8 or stock jb rom for e120l.
http://i4khmers.blogspot.com/2015/09/official-firmware-samsung-galaxy-sii.html try this
its E120SKSJMH3 version
Click to expand...
Click to collapse
failed it still this error it seems like i stuck , have at least one error when i up rom to an open source cook rom
kdlinh said:
failed it still this error it seems like i stuck , have at least one error when i up rom to an open source cook rom
Click to expand...
Click to collapse
have you checked debugging option from developer options before doing this? Make sure your data cable is not faulty. please make sure you have a backup of efs partition if you are having network issues with all ROMs. try hellcat and stock based roms for testing to make sure you are not having this issue only on lollipop or kitkat. Also try to wipe boot from recovery menu before flashing.
diabolicalprophecy said:
have you checked debugging option from developer options before doing this? Make sure your data cable is not faulty. please make sure you have a backup of efs partition if you are having network issues with all ROMs. try hellcat and stock based roms for testing to make sure you are not having this issue only on lollipop or kitkat. Also try to wipe boot from recovery menu before flashing.
Click to expand...
Click to collapse
i means that when i up the stock based roms none of error found but when i up rom to cm11 cm10 hellkat miui cm12 & ressuction
ERROR at least found one in this open source rom
kdlinh said:
i means that when i up the stock based roms none of error found but when i up rom to cm11 cm10 hellkat miui cm12 & ressuction
ERROR at least found one in this open source rom
Click to expand...
Click to collapse
I also had this the same issue.
There is a link to latest baseband in hellkat thread. Thats where i got it. Sadly Its only for E120L
Search the hellkat thread to see if there is one for e120s as well.
I obviously didn't look further as i don't own e120s.
diabolicalprophecy said:
I also had this the same issue.
There is a link to latest baseband in hellkat thread. Thats where i got it. Sadly Its only for E120L
Search the hellkat thread to see if there is one for e120s as well.
I obviously didn't look further as i don't own e120s.
Click to expand...
Click to collapse
can you give me the links , at least what i can do now is tried to install your baseband
it will brick your phone. Its for E120L only
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.
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).
Hey guys, I bought RM3 few days ago.
I want to root it.
It's the global version. Can anyone please make a video on how to root global version of RM3? PLEASE
Thread is here - https://forum.xda-developers.com/red-magic-3/how-to/red-magic-3-root-guide-t3933148
Texan1 said:
Thread is here - https://forum.xda-developers.com/red-magic-3/how-to/red-magic-3-root-guide-t3933148
Click to expand...
Click to collapse
Can you please make a video?
I'm on global version. Why do I have to install Chinese version?
Saurabh Kash said:
Can you please make a video?
I'm on global version. Why do I have to install Chinese version?
Click to expand...
Click to collapse
Easy setup
Download magisk
Search magisk on google
Sorry can't post links
Download your current global zip file
Extract zip file , copy boot.img and put it into you internal storage phone
Now open magisk and press install, Then batch boot file. Then select your boot.img
A new boot file will be added to your download folder named. Boot_patced.img
Now open you cmd , and flash your new boot_patched.img
And thats it your rooted
em902566 said:
Easy setup
Download magisk
Search magisk on google
Sorry can't post links
Download your current global zip file
Extract zip file , copy boot.img and put it into you internal storage phone
Now open magisk and press install, Then batch boot file. Then select your boot.img
A new boot file will be added to your download folder named. Boot_patced.img
Now open you cmd , and flash your new boot_patched.img
And thats it your rooted
Click to expand...
Click to collapse
I'm new to this kinda stuff and don't wanna mess things up. Can you please make a video?
em902566 said:
Easy setup
Download magisk
Search magisk on google
Sorry can't post links
Download your current global zip file
Extract zip file , copy boot.img and put it into you internal storage phone
Now open magisk and press install, Then batch boot file. Then select your boot.img
A new boot file will be added to your download folder named. Boot_patced.img
Now open you cmd , and flash your new boot_patched.img
And thats it your rooted
Click to expand...
Click to collapse
Please make a video for international Asia version. And I couldn't find link to global rom
em902566 said:
Easy setup
Download magisk
Search magisk on google
Sorry can't post links
Download your current global zip file
Extract zip file , copy boot.img and put it into you internal storage phone
Now open magisk and press install, Then batch boot file. Then select your boot.img
A new boot file will be added to your download folder named. Boot_patced.img
Now open you cmd , and flash your new boot_patched.img
And thats it your rooted
Click to expand...
Click to collapse
And will I still get ota update after root?
Saurabh Kash said:
And will I still get ota update after root?
Click to expand...
Click to collapse
No.
A suggestion: don't. You obviously don't know a lot about rooting and stuff and RM3 is a bit atypical amongst android phones, so it's more risky.
Why do you need root anyway?
Nightpwish said:
No.
A suggestion: don't. You obviously don't know a lot about rooting and stuff and RM3 is a bit atypical amongst android phones, so it's more risky.
Why do you need root anyway?
Click to expand...
Click to collapse
To restore my important backup that I made with titanium and to use theme engines because dark in built theme isn't working on my phone
Saurabh Kash said:
To restore my important backup that I made with titanium and to use theme engines because dark in built theme isn't working on my phone
Click to expand...
Click to collapse
I will say this the above posted is the only way to root global. If an OTA comes out you better not try to update. What you will have to do is BACKUP anything important to you, complete uninstall Magisk and modules, go into fastboot relock the bootloader which will factory reset the phone then update via OTA, re-unlock the bootloader and re-root with the updated boot.img which you will have to download.... Especially important if OTA updates security patch. You have to understand custom ROMs are developed for rooting, stock ROMs are not.... Hence all the trouble.
Hi,
Two things worth mentioning :
- it seems the procedure indicated to rrot does not work with EU v. 1.15 ; I just tried and phone reboots, but with no root
- rooting the phone will not allow OTA. You will get notified of an update, but the update will not apply to the end.
Regards.