Related
Some of you might face the next error during systemless SuperSU install:
...
- Decompressing ramdisk
failed
--- Failure, aborting
*************************
IMPORTANT NOTICES
*************************
First reboot may take a
few minutes. It can also
...
This means that the ramdisk of your boot image was compressed in a non gzip format.
Unfortunately SuperSU can only decompress and tweak gzip compressed ramdisks up to now.
However i tried to make a little script that will uncompress your boot image/ramdisk and recompress it to gzip then after flashing SuperSU it recompresses the ramdisk to the original format.
This way one can achieve systemless root temporarily on such devices by installing SuperSU.
Idk maybe it can also be used for Magisk???
Download v1.1 (rce_univ.zip):
http://viid.me/qoESak
in case you face any proglems with the above version, try the old one v1.0 (rce_univ_1.0):
http://viid.me/qir1u5
How to:
Boot into TWRP 3.0.0 or above (never tested below) and install rce_univ.zip before and after SuperSU.zip!
Video: http://viid.me/quIbOi
Consider flashing Chainfire's Boot image signer (in case you get soft bricked after the above steps):
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Detailed description in comment nr.3 (https://forum.xda-developers.com/showpost.php?p=70428981&postcount=3)
Supported ramdisk compressions:
bzip2, lz4, lzo, lzma, xz
Requirements:
Unlocked bootloader on most newer (marshmallow and lollipop) devices
Don't expect it to be working on every device!
The script is basically fool proof. I mean if anything goes wrong it will promt you and quit.
Then you can simply restore your boot partition (if you didn't forget to back it up) and boot up normally and deal with the non rooted idea...
Also it's not supposed to mess up anything that would cost you a hard brick. Soft brick is only possible if you forget to make backup of your boot image or if you get SuperSU intalled and rec_univ.zip cannot recompress your ramdisk (this is pretty much impossible anyways)
Naturally there are those Samsung and Sony devices with some tricky boot images... idk. Never tested but most likely not gonna work.
Probably there will be many devices on which there are not enough space to decompress and recompress ramdisks/boot images in TWRP.
In comment nr. 2 i will collect the devices that are compatible with this script and the method itself.
If you can't find your device there as i said it's fool proof but you better be careful! You can simply test it by backing up your boot images between each install and with the mount mtp function you put it on PC (you can't quit TWRP during the whole process - i mean during step 2) and with carliv image kitchen (https://forum.xda-developers.com/android/development/tool-cika-carliv-image-kitchen-android-t3013658) you check if you can unpack them normally.
Or if you don't care so much you just try and the worst case you reflash your framework...
If you are about to post any errors or complains do it the right way:
- attach recovery.log
- describe your device (model name, firmware version, ...)
- attach your boot image you backed up (upload it somewhere and link it)
If you are about to post a succesful attempt of a not yet added device:
- describe your device (model name, firmware version, ...)
- maybe link to its thread
No promises... and no responsibility i take... !!!
Please don't upload it anywhere else just use link to this thread!
I have to say thanks jcadduono for LazyFlasher boot image patcher script i used for the ramdisk compression exchanger and also thanks goes to Chainfire for SuperSU (especially for the boot image finder srcipt which is took from the SuperSU installer).
The xz archiver was used from XZ Utility For Android by Tukaani http://tukaani.org/xz/ - i hope he doesn't mind. Let me know if he does!
Supported devices until now:
Lg K8 - https://forum.xda-developers.com/lg-k10/how-to/friendly-root-method-lg-k8-k10-t3531223
Lg K10 - https://forum.xda-developers.com/lg-k10/how-to/friendly-root-method-lg-k8-k10-t3531223
Note 4 n910v (7.1.1 rom) https://forum.xda-developers.com/showpost.php?p=72491391&postcount=18
Detailed description
Systemless root with SuperSU on devices with non gzip compressed ramdisk bootimage
0. Download rce_univ.zip from here: http://viid.me/qir1u5 and download SuperSU (latest or there are some cases that requires earlier versions): https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703 and put them on your sd card (external sd card is usually necessary since sometimes TWRP cannot decrypt your data partition/internal sd).
1. Unlock your bootloader
1.1. Additional step for those who has no "...device corrupt..." message during every boot up after unlocking bootloader on Marshmallow and some Lollipop devices(*)
- Boot into TWRP
- on the keep system read only? screen of the TWRP let it allow modifications (swipe!)
- reboot to System
- from now on you should have the message at every boot up
2. Boot into TWRP
- cancel decrypt data
- keep system read only
- go to Backup -> Backup your boot image! Maybe it comes handy later.
- go back from backup to install and install rce_univ.zip right after install SuperSUxxx.zip and then rce_univ.zip again.
- do not wipe anything during and after this step, just reboot! (this might take a while and a few bootloops...)
Video guide: http://viid.me/quIbOi
(3.) Verified boot?
In case of soft brick (or if you're sure you need the proper signature in the end of your boot partition - cos your device has verified boot) try flashing Chainfire's Boot image signer as a very last step before rebooting from TWRP:
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
(*) on some devices if there is no "device corrupt" message at every boot up after bootloader unlock then anything you do or change in your boot image or system partition your device will not boot up anymore but turning off right after showing you that device corrupt message.
but if you do that trick as written in step 1.1 and that message appears at every boot up then most likely you're goot to go...
You can find some video guides on my thread for the above steps: https://forum.xda-developers.com/lg-k10/how-to/friendly-root-method-lg-k8-k10-t3531223
Pricniple of the installer - rce_univ.zip
What the script does:
Install rce_univ.zip before SuperSU:
1. Finds the boot partition (same way as SuperSU)
2. Dumps the boot image and unpacks it
3. Determines the format the ramdisk was compressed in
4. Uncomresses it then recompresses to gzip (so SuperSU can handle it).
5. Repacks the boot image and flashes it back on boot partition
Here is where you install SuperSU
Install rce_univ.zip after SuperSU:
1. Finds the boot partition
2. Dumps the boot image and unpacks it
3. Reads back the original format of the ramdisk compression
4. Uncomresses it then recompresses the ramdisk with the original compression method(so now the device can handle it).
5. Repacks the boot image and flashes it back on boot partition
As about me:
I was not a complete noob when i started it however it took a lot of effort and time. If you care to understand a bit more what it's about and you want to follow my struggling this is where it started (you can click through the threads):
https://forum.xda-developers.com/apps/supersu/supersu-v2-66-installed-lz4-compressed-t3296508
didn't work at samsung galaxy S2, it only have 8Mb space at boot partition. any solution ?
edit i use LineageOS 14.1 (cm 14.1) android 7.1.1
haris1976 said:
didn't work at samsung galaxy S2, it only have 8Mb space at boot partition. any solution ?
edit i use LineageOS 14.1 (cm 14.1) android 7.1.1
Click to expand...
Click to collapse
Can attach recovery log? And maybe boot image that you backed up in TWRP
this recovery log
haris1976 said:
this recovery log
Click to expand...
Click to collapse
I can not fully open it (no editor can fully load it). Could you zip it and attach compressed or just attach again?
gottlasz said:
Can attach recovery log? And maybe boot image that you backed up in TWRP
Click to expand...
Click to collapse
back up boot from twrp
---------- Post added at 03:23 PM ---------- Previous post was at 03:05 PM ----------
gottlasz said:
I can not fully open it (no editor can fully load it). Could you zip it and attach compressed or just attach again?
Click to expand...
Click to collapse
maybe tommorow i have bad connection when upload recovery & boot with the zip
haris1976 said:
back up boot from twrp
---------- Post added at 03:23 PM ---------- Previous post was at 03:05 PM ----------
maybe tommorow i have bad connection when upload recovery & boot with the zip
Click to expand...
Click to collapse
Okay, you can send it in PM if you want...
gottlasz said:
Okay, you can send it in PM if you want...
Click to expand...
Click to collapse
recovery & boot
haris1976 said:
this recovery log
Click to expand...
Click to collapse
Now i could open the recovery log.
Unfortunately this part means that even if it's a 3.0.2 TWRP something is missing:
"- Found boot partition at: /dev/block/mmcblk0p5- Dumping & unpacking original boot image...WARNING: linker: /tmp/boot_repack/tools/armv7/unpackbootimg: unused DT entry: type 0x6ffffef5 arg 0x560"
Maybe you should try with a newer version of TWRP if there is one.
Or if you follow my older guide which was a manual unpacking and repaking with carliv image kitchen, that could work.
Check my old guide: https://forum.xda-developers.com/lg-k10/how-to/twrp-root-lg-k8-k350n-t3475807
Anyways give me until tomorrow, ill take a look at the script maybe i can avoid this error.
gottlasz said:
Now i could open the recovery log.
Unfortunately this part means that even if it's a 3.0.2 TWRP something is missing:
"- Found boot partition at: /dev/block/mmcblk0p5- Dumping & unpacking original boot image...WARNING: linker: /tmp/boot_repack/tools/armv7/unpackbootimg: unused DT entry: type 0x6ffffef5 arg 0x560"
Maybe you should try with a newer version of TWRP if there is one.
Or if you follow my older guide which was a manual unpacking and repaking with carliv image kitchen, that could work.
Check my old guide: https://forum.xda-developers.com/lg-k10/how-to/twrp-root-lg-k8-k350n-t3475807
Anyways give me until tomorrow, ill take a look at the script maybe i can avoid this error.
Click to expand...
Click to collapse
Same error for me on LG K8 4G Vodafone Spain (LGK350n, build MRA58K, MT6735, Android 6.0), i fix it change booting the TWRP image to k350n10f (k8_10f_twrp.img, https://forum.xda-developers.com/lg-k10/development/recovery-twrp-3-0-2-lg-k8-k350-mtk-t3517894). It avoid for me" Error: Unpacking boot image failed!- Aborting..."
Works like a charm!!! thanks to gottlasz and XDA group!
sorry for my english
You should recompile all the used binaries as static, that should avoid a lot of issues.
Also, don't bother with older Samsung (everything before S3) and older Sony devices (not really sure until when). These use non-standard boot images that are very tricky to patch without outright recompiling. It can be done - I have done it in the past - but it is a major hassle and very errorprone.
Chainfire said:
You should recompile all the used binaries as static, that should avoid a lot of issues.
Also, don't bother with older Samsung (everything before S3) and older Sony devices (not really sure until when). These use non-standard boot images that are very tricky to patch without outright recompiling. It can be done - I have done it in the past - but it is a major hassle and very errorprone.
Click to expand...
Click to collapse
Thank you Master!
I know about the compiling situation, however the problem is that i did not compile anything since the whole stuff is based on jcadduono's LazyFlasher. He compiled the binaries I only tweaked the script and added some stuff... i don't have the resources to compile. Now i'm collecting static binaries to exchange them in the installer in order to solve these compatibility issues.
Basically i just wanted to help some of those unfortunate as me who has lz4 or other compressed ramdisks and unable to intall SuperSU. Well..., at least a handful of them.
New version is up. A few TWRP related compatibility issues are solved.
gottlasz said:
New version is up. A few TWRP related compatibility issues are solved.
Click to expand...
Click to collapse
i test the new version but no luck
this is the recovery log
haris1976 said:
i test the new version but no luck
this is the recovery log
Click to expand...
Click to collapse
How far does supersu intaller goes?
I mean can it unpack your boot image?
Install only supersu and make a recovery log please.
I tried to unpack your boot image with carliv image kitchen and no luck...
I think supersu can't even unpack your boot image and then there is no chance to install it. Even if we could change the ramdisk compression...
Are you sure supersu intaller gives you the same error message as it is stated in the OP?
I believe you have a non standard boot image as chainfire talked about.
It works great on 7.1.1 roms on Note 4 n910v. Thanks!
Dear all,
I currently use the Minotaurus S8 Port V11.0 (pre-rooted ROM) on a Samsung S7 Edge.
During the installation I chose SuperSU.
Now I'd like to switch to MagiskSU - if possible without flashing the complete ROM one again.
Nevertheless my efforts currently are not successful.
I read that I have to unroot first what I did with using osm0sis unSU. This worked and root was gone.
Trying then to install Magisk (v12) ended up with an error:
****************************************
Magisk v12.0 Boot Image Patcher
****************************************
- Mounting /system(ro), /cache, /data
- Device platform: arm64
- Constructing environment
- /data/magisk.img detected!
- Found Boot Image: /dev/block/sda5
- Unpacking boot image
- Checking patch status
- SuperSU patched boot detected!
- Adding ramdisk patch script for SuperSU
- We are using SuperSU's own tools, mounting su.img
! SuperSU image mount failed...
! Magisk scripts are placed correctly
! Flash SuperSU immediately to finish installation
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/S7E Minotaurus/Magisk/Magisk-v12.0.zip'
Updating partition details...
...done
Then I installed SuperSU v2.82 again which brought back root (with SuperSU).
I tried to flash Magisk v13.0 (96f8efc) but again end up in an error:
****************************************
Magisk v13.0 (96f8efc) Installer
****************************************
- Mounting /system(ro), /cache, /data
- Device platform: arm64
- Constructing environment
- /data/magisk.img detected!
- Mounting /data/magisk.img to /magisk
- Found Boot Image: /dev/block/sda5
- Unpacking boot image
- Checking ramdisk status
! Boot image patched by other programs!
! please restore stock boot image
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/S7E Minotaurus/Magisk/Magisk-v13.0(96f8efc).zip'
Updating partition details...
...done
Is anybody able to help me and give me some guidance to get MagiskSU (with v13.0)
Thank you in advance,
Best regards,
MarkusTh
Besides flashing the unSU script you'll need to also flash a boot image without the SuperSU patches. That's gonna be an issue on a pre-rooted ROM. You say you chose SuperSU during installation? Did you have any other options (Magisk or no root)? If so, reinstall the ROM and make a different choice.
Didgeridoohan said:
Besides flashing the unSU script you'll need to also flash a boot image without the SuperSU patches. That's gonna be an issue on a pre-rooted ROM. You say you chose SuperSU during installation? Did you have any other options (Magisk or no root)? If so, reinstall the ROM and make a different choice.
Click to expand...
Click to collapse
Thanks for the quick answer.
Yes, the other options mentioned by you are available.
Is it possible to do a "dirty" flash over the current ROM without having to reinstall everything again afterwards ?
If yes, I assume the steps would be:
1) "dirty" flash of original ROM with choosing "MagiskSU" or "no root"
2) reboot necessary ?
3) flashing Magisk v13
4) reboot and ready ?
That easy ?
Thx,
MarkusTh
Or extract the kernel from your ROM.zip and flash it in TWRP.
Nothing in your current ROM will change.
So...
1.) unsu.zip
2.) Flash unpatched kernel (just go to "Install" in TWRP and choose in the bottom right "Select Image" > Select you boot.img and choose "boot" as partition in the next screen)
3.) Flash Magisk Beta v13
4.) Reboot
That's how I did it on my HTC 10.
Maik268 said:
Or extract the kernel from your ROM.zip and flash it in TWRP.
Nothing in your current ROM will change.
So...
1.) unsu.zip
2.) Flash unpatched kernel (just go to "Install" in TWRP and choose in the bottom right "Select Image" > Select you boot.img and choose "boot" as partition in the next screen)
3.) Flash Magisk Beta v13
4.) Reboot
That's how I did it on my HTC 10.
Click to expand...
Click to collapse
Thanks so much for this!! I would have been in a mess without this method which worked perfectly on my Samsung GS6. Thanks.
MarkusTh said:
Dear all,
I currently use the Minotaurus S8 Port V11.0 (pre-rooted ROM) on a Samsung S7 Edge.
During the installation I chose SuperSU.
Now I'd like to switch to MagiskSU - if possible without flashing the complete ROM one again.
Nevertheless my efforts currently are not successful.
I read that I have to unroot first what I did with using osm0sis unSU. This worked and root was gone.
Trying then to install Magisk (v12) ended up with an error:
****************************************
Magisk v12.0 Boot Image Patcher
****************************************
- Mounting /system(ro), /cache, /data
- Device platform: arm64
- Constructing environment
- /data/magisk.img detected!
- Found Boot Image: /dev/block/sda5
- Unpacking boot image
- Checking patch status
- SuperSU patched boot detected!
- Adding ramdisk patch script for SuperSU
- We are using SuperSU's own tools, mounting su.img
! SuperSU image mount failed...
! Magisk scripts are placed correctly
! Flash SuperSU immediately to finish installation
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/S7E Minotaurus/Magisk/Magisk-v12.0.zip'
Updating partition details...
...done
Then I installed SuperSU v2.82 again which brought back root (with SuperSU).
I tried to flash Magisk v13.0 (96f8efc) but again end up in an error:
****************************************
Magisk v13.0 (96f8efc) Installer
****************************************
- Mounting /system(ro), /cache, /data
- Device platform: arm64
- Constructing environment
- /data/magisk.img detected!
- Mounting /data/magisk.img to /magisk
- Found Boot Image: /dev/block/sda5
- Unpacking boot image
- Checking ramdisk status
! Boot image patched by other programs!
! please restore stock boot image
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/S7E Minotaurus/Magisk/Magisk-v13.0(96f8efc).zip'
Updating partition details...
...done
Is anybody able to help me and give me some guidance to get MagiskSU (with v13.0)
Thank you in advance,
Best regards,
MarkusTh
Click to expand...
Click to collapse
Mate, just unroot from supersu as you did earlier, then copy original boot image to internal memory, boot into TWRP, flash original boot image and then flash Magisk. It should work now.
atf2m4 said:
Mate, just unroot from supersu as you did earlier, then copy original boot image to internal memory, boot into TWRP, flash original boot image and then flash Magisk. It should work now.
Click to expand...
Click to collapse
I got the same issue and I tried to fix that but I don't know where the original boot image is located respectively where can I get the orginal boot image back? Could you help me out with my Samsung S8?
Thanks a bunch!
cocolish said:
I got the same issue and I tried to fix that but I don't know where the original boot image is located respectively where can I get the orginal boot image back? Could you help me out with my Samsung S8?
Thanks a bunch!
Click to expand...
Click to collapse
SOLVED! I managed to extract the boot.img from the original Samsung firmware and flashed the original boot.img via TWRP!
Maik268 said:
Or extract the kernel from your ROM.zip and flash it in TWRP.
Nothing in your current ROM will change.
So...
1.) unsu.zip
2.) Flash unpatched kernel (just go to "Install" in TWRP and choose in the bottom right "Select Image" > Select you boot.img and choose "boot" as partition in the next screen)
3.) Flash Magisk Beta v13
4.) Reboot
That's how I did it on my HTC 10.
Click to expand...
Click to collapse
Im having a similar problem. i have an lgms550. my problem is when i flash the stock boot img, magisk still states unable to mount. im not sure whats wrong here
So, I got a Huawei P9 (L09) and want to UnSU as well to install Magisk.
I once took apart an update file and therefore also have a boot.img from this package.
Is this file the one I would need to restore my boot partition on this phone?
If so, then I got super lucky here.
I am on J7 Prime (SM-G610F) the issue is I'm on the stock Nougat ROM which comes in a .tar.md5 format which I don't know how to disassemble.
The .md5 files are in fact .TAR files with the MD5 sum appended at the end.
If you rename each .md5 to a .tar file, they can be unpacked with 7zip or Winrar.
Can someone please please help me. I have j7 prime with supersu & trying to move on magisk but it says boot image is patched by another program. I'm soo tired with this issue please help me.
MarkusTh said:
Dear all,
I currently use the Minotaurus S8 Port V11.0 (pre-rooted ROM) on a Samsung S7 Edge.
During the installation I chose SuperSU.
Now I'd like to switch to MagiskSU - if possible without flashing the complete ROM one again.
Nevertheless my efforts currently are not successful.
I read that I have to unroot first what I did with using osm0sis unSU. This worked and root was gone.
Trying then to install Magisk (v12) ended up with an error:
****************************************
Magisk v12.0 Boot Image Patcher
****************************************
- Mounting /system(ro), /cache, /data
- Device platform: arm64
- Constructing environment
- /data/magisk.img detected!
- Found Boot Image: /dev/block/sda5
- Unpacking boot image
- Checking patch status
- SuperSU patched boot detected!
- Adding ramdisk patch script for SuperSU
- We are using SuperSU's own tools, mounting su.img
! SuperSU image mount failed...
! Magisk scripts are placed correctly
! Flash SuperSU immediately to finish installation
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/S7E Minotaurus/Magisk/Magisk-v12.0.zip'
Updating partition details...
...done
Then I installed SuperSU v2.82 again which brought back root (with SuperSU).
I tried to flash Magisk v13.0 (96f8efc) but again end up in an error:
****************************************
Magisk v13.0 (96f8efc) Installer
****************************************
- Mounting /system(ro), /cache, /data
- Device platform: arm64
- Constructing environment
- /data/magisk.img detected!
- Mounting /data/magisk.img to /magisk
- Found Boot Image: /dev/block/sda5
- Unpacking boot image
- Checking ramdisk status
! Boot image patched by other programs!
! please restore stock boot image
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/S7E Minotaurus/Magisk/Magisk-v13.0(96f8efc).zip'
Updating partition details...
...done
Is anybody able to help me and give me some guidance to get MagiskSU (with v13.0)
Thank you in advance,
Best regards,
MarkusTh
Click to expand...
Click to collapse
I can't find mt boot.img file
And unsu.zip is not unrooting my phone
And unroot failed saying in supersu
Please help????
And magisk 14.0 is not flashing saying error 1
Same as described
---------- Post added at 07:37 PM ---------- Previous post was at 06:39 PM ----------
Maik268 said:
Or extract the kernel from your ROM.zip and flash it in TWRP.
Nothing in your current ROM will change.
So...
1.) unsu.zip
2.) Flash unpatched kernel (just go to "Install" in TWRP and choose in the bottom right "Select Image" > Select you boot.img and choose "boot" as partition in the next screen)
3.) Flash Magisk Beta v13
4.) Reboot
That's how I did it on my HTC 10.
Click to expand...
Click to collapse
I did bit nothing happens
Showing my device is rooted even after uninstalling supersu
I can't flash magisk
First of all I've no boot.img file in my phone
brdude said:
I can't find mt boot.img file
And unsu.zip is not unrooting my phone
And unroot failed saying in supersu
Please help????
And magisk 14.0 is not flashing saying error 1
Same as described
---------- Post added at 07:37 PM ---------- Previous post was at 06:39 PM ----------
I did bit nothing happens
Showing my device is rooted even after uninstalling supersu
I can't flash magisk
First of all I've no boot.img file in my phone
Click to expand...
Click to collapse
The boot image you can extract from your device's factory image/firmware/ROM.
One of the best ways to unroot is to flash the unSU zip and then restore the stock boot image. That should be it.
If it doesn't work, provide logs (recovery log from flashing) and more details about your setup.
What is recovery log????
I have only copy log in my twrp recovery
And i tried copy log still saying boot image patched by other program
---------- Post added at 09:23 PM ---------- Previous post was at 09:12 PM ----------
I tried recently that unsu.zip
But still showing root is properly installed
brdude said:
What is recovery log????
I have only copy log in my twrp recovery
And i tried copy log still saying boot image patched by other program
---------- Post added at 09:23 PM ---------- Previous post was at 09:12 PM ----------
I tried recently that unsu.zip
But still showing root is properly installed
Click to expand...
Click to collapse
That is the recovery log.
Save the log after flashing the unSU zip and upload it. Or, just wipe and clean flash your device. Sounds like it might be easier... There are so many questions raised from your posts, but so few answers...
I'd suggest to go over to your device's forum and read up on the basics.
I have uninstalled SuperSU by flashing unsu.zip .
But when i tried to install magisk,it is failed showing this message "Boot image patched by other program,please restore stock boot image "
What to do??
madhuresh11 said:
I have uninstalled SuperSU by flashing unsu.zip .
But when i tried to install magisk,it is failed showing this message "Boot image patched by other program,please restore stock boot image "
What to do??
Click to expand...
Click to collapse
You do what the message says (the unSU zip doesn't restore the stock boot image for you)...
You'll find some pointers here:
https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
Didgeridoohan said:
You do what the message says (the unSU zip doesn't restore the stock boot image for you)...
You'll find some pointers here:
https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
Click to expand...
Click to collapse
Thanks. It worked!!
As part an academic development effort, I need to re-build and re-flash kernel numerous times on a Pixel running Android 8.0.0. Every time I re-flash the kernel, I also need to re-flash SuperSu SR5 from TWRP to regain root access. Is there any patching script for SuperSu which can patch boot.img on disk (on laptop) so that I can just flash the patched boot image (with SuperSu patch already applied)?
was going to look into the same thing.
Hello everybody.
I've read that 18.1 supports 4.2+ so I've tried to install in two MTK6589T devices I've. One running 4.2, the other running 4.4
CMW/TWRP gave an error mounting system, so I mounted system manually and it started flashing. Firstly it detected old root installed and disabled the old root. But when it tried to find the boot, installation was aborted because installator claims cannot find the boot on both phones.
Then I though, okay, lets reboot back to android, I will try to install a few days later, maybe its buggy now, but both phones cannot boot.
I can easily fix them by flashing rom again I guess, but I would like to know where's the issue and also post it for more people could face the same problem.
Any idea where's the problem/how to fix without rom reflashing? I've tried magisk uninstaller but after mounting system in recovery it is also giving error.
Thanks
UPDATE: For now, if no other solution is found, bootloop can be bypassed by dirty installing the rom again. But it has to be an easier workaround...
We know now that the problem is caused because of two factors merging:
1- Using Magisk.zip installer through custom recovery
2-In the case that the custom recovery CMW/TWRP installed in the phone is very old (for instance, CMW automade for MTK6589X or TWRP 2.5.0).
While installing, Magisk tries to send commands to the custom recovery that cant be understood by it, leaving the installation incomplete after some modifications in /system (read below recovery log).
Acording to the recovery, it seems that Magisk did some modifications without running correctly survival script - Adding addon.d survival script ("Unrecognized option '-Xnodex2oat'") and .zip installer is not designed to revert actions in this case.
Also, Magisk couldn't reach the boot modification step, so boot is not damaged, therefore workarounds for restoring boot won't work.
Using Magisk Unistaller.zip is also not possible as the uninstaller is mainly designed for boot backup restoration, and again, this is not the case.
Currently needed: Find what's wrong in system due to the incomplete Magisk installation to revert it back to the original state (before faulty magisk.zip installation).
Recovery log:
************************
* Magisk v18.1 Installer
************************
- Mounting /system, /vendor
- Target image: /dev/bootimg
- Device platform: arm
- Removing system installed root
- Constructing environment
- Adding addon.d survival script
Unrecognized option '-Xnodex2oat'
up!
I' also having the same problem. My Samsung J2 Prime stuck at logo after updating to 18.1. Any tips on how to fix it without resetting my phone? Thanks.
Update: Bootloop fixed. I used TWRP to restore boot image. I then update Magisk by flashing zip file from TWRP. Everything went back to normal. Hope this help.
trol_sg said:
Hello everybody.
I've read that 18.1 supports 4.2+ so I've tried to install in two MTK6589T devices I've. One running 4.2, the other running 4.4
CMW/TWRP gave an error mounting system, so I mounted system manually and it started flashing. Firstly it detected old root installed and disabled the old root. But when it tried to find the boot, installation was aborted because installator claims cannot find the boot on both phones.
Then I though, okay, lets reboot back to android, I will try to install a few days later, maybe its buggy now, but both phones cannot boot.
I can easily fix them by flashing rom again I guess, but I would like to know where's the issue and also post it for more people could face the same problem.
Any idea where's the problem/how to fix without rom reflashing? I've tried magisk uninstaller but after mounting system in recovery it is also giving error.
Thanks
Click to expand...
Click to collapse
If you have a backup of your boot image, you can just restore it using TWRP. But in case that you have no backup of boot image, you can try to get boot image from the internet and restoring using it. In my case, this is what I did.
1. Go to TWRP and then make backup of boot image of the faulty phone*. (Folder 1)
2. I used another J2 prime to create a boot image backup. (Folder 2)
3. Once that is done, copy and replace the files inside the Folder 2 into Folder 1.
4. Reboot to TWRP again then use that to restore the boot image on my stuck J2.
Tips: make backup in SD card so you can easily swap it in between the bad and good phone.
*This is to create a folder of the backup file. I did tried to directly copy and paste the backup boot image file from another good phone but TWRP didn't detect it. So this is the workaround that I come with. And it worked for me.
Thanks for your answer but I doubt your case is mine. Your device is much newer than mine and according to your comment, you've sucesfully installed previous version of Magisk without issues. This is not a problem while updating, as Magisk v. earlier than 18.1 was not compatible with android 4.2+. I think Magisk is not compatible with MT6589T even if they run 4.2 or 4.4.
I think that it cannot be a boot problem as TWRP/CWM displayed msg 'Boot cannot be found' while installing Magisk, so that I don't think boot was replaced or modified in any ways. Moreover, the bootloop is not in the boot loading, as phone can pass boot image without any problem, but it is stuck in android loading image. I'm thinking in some script or root modification that Magisk did before trying to unpack the boot, however I'm not that deep into the Magisk install to find the proper workaround.
I can restore boot backup and also I can take boot file from the original rom and flash, because in Mediatek-based devices, boot.img is inside de zip, but I dont think it will solve the problem. Anyhow I'll get back ASAP with the answer.
Any more ideas??
Nothing, boot/uboot restoration or flashing again just the boot won't fix the problem, so it's something that Magisk installator touch in /system or /data I guess, but what?
trol_sg said:
Nothing, boot/uboot restoration or flashing again just the boot won't fix the problem, so it's something that Magisk installator touch in /system or /data I guess, but what?
Click to expand...
Click to collapse
Have you read/tried this?
didgeridoohan(dot)com/magisk/MagiskIssues
Ato09 said:
Have you read/tried this?
didgeridoohan(dot)com/magisk/MagiskIssues
Click to expand...
Click to collapse
Yes, I've read them before I made the post. I've also looked for a solution in some of the threads and using search, but couldn't find a way.
Here I attach recovery.log if someone is interested to see the detailed problem.
Also, here below I attach the lines concerning the installation. All other is uninstallation tries and so on:
************************
* Magisk v18.1 Installer
************************
- Mounting /system, /vendor
- Target image: /dev/bootimg
- Device platform: arm
- Removing system installed root
- Constructing environment
- Adding addon.d survival script
Unrecognized option '-Xnodex2oat'
dalvikvm: [options] class [argument ...]
dalvikvm: [options] -jar file.jar [argument ...]
The following standard options are recognized:
-classpath classpath
-Dproperty=value
-verbose:tag ('gc', 'jni', or 'class')
-ea[:<package name>... |:<class name>]
-da[:<package name>... |:<class name>]
(-enableassertions, -disableassertions)
-esa
-dsa
(-enablesystemassertions, -disablesystemassertions)
-showversion
-help
The following extended options are recognized:
-Xrunjdwp:<options>
-Xbootclasspath:bootclasspath
-Xcheck:tag (e.g. 'jni')
-XmsN (min heap, must be multiple of 1K, >= 1MB)
-XmxN (max heap, must be multiple of 1K, >= 2MB)
-XssN (stack size, >= 1KB, <= 256KB)
-Xverify:{none,remote,all}
-Xrs
-Xint (extended to accept 'ortable', ':fast' and ':jit')
These are unique to Dalvik:
-Xzygote
-Xdexopt:{none,verified,all,full}
-Xnoquithandler
-Xjniopts:{warnonly,forcecopy}
-Xjnitrace:substring (eg NativeClass or nativeMethod)
-Xstacktracefile:<filename>
-Xgc:[no]precise
-Xgc:[no]preverify
-Xgc:[no]postverify
-Xgc:[no]concurrent
-Xgc:[no]verifycardtable
-XX:+DisableExplicitGC
-X[no]genregmap
-Xverifyopt:[no]checkmon
-Xcheckdexsum
-Xincludeselectedop
-Xjitop:hexopvalue[-endvalue][,hexopvalue[-endvalue]]*
-Xincludeselectedmethod
-Xjitthreshold:decimalvalue
-Xjitcodecachesize:decimalvalueofkbytes
-Xjitblocking
-Xjitmethod:signature[,signature]* (eg Ljava/lang/String\;replace)
-Xjitclass:classname[,classname]*
-Xjitoffsetffset[,offset]
-Xjitconfig:filename
-Xjitcheckcg
-Xjitverbose
-Xjitprofile
-Xjitdisableopt
-Xjitsuspendpoll
Configured with: debugger profiler hprof jit(armv7-a-neon) smp show_exception=1
Failed to initialize runtime (check log for details)
- Unpacking boot image
MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/dev/bootimg]
No boot image magic found!
! Unable to unpack boot image
- Unmounting partitions
E:Error executing updater binary in zip '/sdcard/Magisk-v18.1.zip'
Error flashing zip '/sdcard/Magisk-v18.1.zip'
@trol_sg I'm gonna guess it's got to do with the absolutely ancient TWRP you're using. It just can't handle everything that the Magisk installation script is trying to do...
Your best bet (if Magisk will work at all on your device) is to patch the boot image with the Magisk Manager and then flash the patched image manually. There are new and shiny installation instructions available here: https://topjohnwu.github.io/Magisk/
Didgeridoohan said:
@trol_sg I'm gonna guess it's got to do with the absolutely ancient TWRP you're using. It just can't handle everything that the Magisk installation script is trying to do...
Your best bet (if Magisk will work at all on your device) is to patch the boot image with the Magisk Manager and then flash the patched image manually. There are new and shiny installation instructions available here: https://topjohnwu.github.io/Magisk/
Click to expand...
Click to collapse
Thank you so much for your answer. So it's the recovery, but can't find newer ones, sadly. Too old phones I know, but just curious if I could make Magisk working on them, lol.
I was going into the boot modification manually right now, but in order to patch the boot I need manager installed first, and phone couldn't boot so I did dirty flash of the rom to be able to boot into it again.
Lets see what happens then. I'll be right back.
Anyhow, this is not a solution to fix the problem of bootloop that I am requesting help in case someone could face the same and did not make a backup of the phone and didn't want to make dirty re-flash. Any idea?
Update: After I did dirty flash of the rom, and now Jiayu g3s android 4.4 booted.
UPDATE: So, after patching manually boot and installing (using restore in TWRP 2.5 as image flash is not yet implemented AFAIK), phone booted and yes Magisk is working.
Magisk installation .zip through a very old recovery is making the bootloop. So that, a thing learnt now.
But, for other people facing this bootloop, can we do a research to find what magisk.zip did to the phones to leave them in bootloop? Maybe we can revert without rom flashing easily if we knew what's the issue...
Thanks in advance!
Doing a bit more tests I found that magisk.zip did something in /system so that it is left in bootloop, but still no idea why/whats causing that...
There are delay complete boot like 4 5 second in j7 prime. I didn't love this version
any more help?? up!!
trol_sg said:
Yes, I've read them before I made the post. I've also looked for a solution in some of the threads and using search, but couldn't find a way.
Click to expand...
Click to collapse
Try this.
Quote:
Originally Posted by void74
I faced this problem too this morning.
I have a Redmi Note 5 with AOSiP ROM, I don't know if it's the right way to do it, but I solved the bootloop problem this way:
- volume up and then boot to TWRP
- copied magisk uninstall to phone memory
- installed magisk uninstall
- rebooted in fastboot/bootloader mode
- flashed original boot.img extracted from stock image zip file ("fastboot flash boot boot.img")
- rebooted to TWRP
- installed magisk 17.0 zip file
- rebooted to system, all OK!
Only problem is that I lost previous magisk configuration, but it's a snap to reconfigure it!
Quote:
Originally Posted by Mangraviti
Here is what to do, if you HAVE NOT installed the new version:
1) Do not update via Magisk Manager.
2) Do not update via TWRP using the zip you can download via Magisk Manager.
3) Uninstall Magisk using Magisk uninstaller (ZIP).
4) Boot to Android.
5) Reboot to TWRP
6) Install V17 ZIP via TWRP and boot to Android.
If you HAVE INSTALLED and got a bootloop:
1) Download the uninstaller ZIP.
2) Enter TWRP during the bootloop.
3) Uninstall using the uninstaller ZIP.
4) Boot to Android.
5) Download V17.
6) Reboot to TWRP and flash the V17.
7) Boot to Android it it should be working.
-------------
Original post. https://forum.xda-developers.com/apps/magisk/bootloop-magisk-update-t3836904
Hope it help.
Ato09 said:
Try this.
Quote:
Originally Posted by void74
I faced this problem too this morning.
I have a Redmi Note 5 with AOSiP ROM, I don't know if it's the right way to do it, but I solved the bootloop problem this way:
- volume up and then boot to TWRP
- copied magisk uninstall to phone memory
- installed magisk uninstall
- rebooted in fastboot/bootloader mode
- flashed original boot.img extracted from stock image zip file ("fastboot flash boot boot.img")
- rebooted to TWRP
- installed magisk 17.0 zip file
- rebooted to system, all OK!
Only problem is that I lost previous magisk configuration, but it's a snap to reconfigure it!
Quote:
Originally Posted by Mangraviti
Here is what to do, if you HAVE NOT installed the new version:
1) Do not update via Magisk Manager.
2) Do not update via TWRP using the zip you can download via Magisk Manager.
3) Uninstall Magisk using Magisk uninstaller (ZIP).
4) Boot to Android.
5) Reboot to TWRP
6) Install V17 ZIP via TWRP and boot to Android.
If you HAVE INSTALLED and got a bootloop:
1) Download the uninstaller ZIP.
2) Enter TWRP during the bootloop.
3) Uninstall using the uninstaller ZIP.
4) Boot to Android.
5) Download V17.
6) Reboot to TWRP and flash the V17.
7) Boot to Android it it should be working.
-------------
Original post. https://forum.xda-developers.com/apps/magisk/bootloop-magisk-update-t3836904
Hope it help.
Click to expand...
Click to collapse
Hello, thanks
This method won't work in my case as in the step:
- installed magisk uninstall = gives error
Note 5 is much newer phone with a recent recovery TWRP that allows all Magisk.zips commands, but unluckyly not this case.
Also, this method is for wrong boot installation/damaged boot. In my case what Magisk damage is /system, not boot.
I wish it could be boot, because that is very easy to fix (flashing through fastboot/SP Flash tools in the case of MTK, recovering boot twrp "backup" even if you didn't make backup...) as you mentioned.
Hope someone have a great idea to revert system to origin, then we could post the solution for those who would like to install Magisk in 4.2+ old phones, and instead of doing boot flash manually, they try to flash magisk.zip and they got bootloop.
Main post updated with all thread information. Up!
Nothing?? Up!!
trol_sg said:
Hope someone have a great idea to revert system to origin, then we could post the solution for those who would like to install Magisk in 4.2+ old phones, and instead of doing boot flash manually, they try to flash magisk.zip and they got bootloop.
Click to expand...
Click to collapse
The only part of the Magisk installation that actually touches /system is if it installs the addon.d survival script. The log you posted earlier shows that it's trying to do this, for some reason, and failiing. I'd start looking there...
Hi, i tried many times to use MAGISK app on a tablet ASUS FONEPAD 7 (model K00E) with Lollipop in order to patch the BOOT.IMG.
Always failed during the patching, with the messages:
DEVICE PLATFORM: x86
COPYING IMAGE TO CACHE
UNPACKING BOOT IMAGE
CHECKING RAMDISK STATUS
STOCK BOOT IMAGE DETECTED
PATCHING RAMDISK
REPACKING BOOT IMAGEUNABLE TO REPACK BOOT IMAGE!
INSTALLATION FAILED
I have searched for all the possible articles etc, without success.
I have tried many different versione of MAGISK, the last 20.4 and MANAGER 8.0.2 (i have used MAGISK install >> go >> method select and file update >> boot.img)
Obviously i have the original BOOT.IMG file, loaded on internal memory.
Please, may you help me?
Thanks in advance
Marco G
That's a pretty old device, and since Asus has been known to not quite follow Android standards I wouldn't be surprised if it's simply not compatible...
Since you say that you used Magisk v20.4 it might be worth it to try the Canary build (just in case there's been some kind of improvement upstream). You can find the Canary Manager on GitHub:
https://github.com/topjohnwu/Magisk
And providing the actual installation log is always a good idea (there's a disc icon in the flashing window).