Related
Hi All
Yesterday I received the update via OTA. When it rebooted into the TWRP recovery is started with the patch install process.
Then it failed.
After that it offered to fix the root, nice of him, which I did, and rebooted. Build version was still JWR66V.
This is what I got from the recovery log file:
Code:
Unpacking new recovery...
minzip: Can't create target file "/system/etc/install-recovery.sh": Permission denied
minzip: Extracted 0 file(s)
Symlinks and permissions...
set_perm: chown of /system/etc/install-recovery.sh to 0 0 failed: Operation not permitted
set_perm: chmod of /system/etc/install-recovery.sh to 544 failed: Operation not permitted
script aborted: set_perm: some changes failed
set_perm: some changes failed
E:Error executing updater binary in zip '/cache//8b2531d9d9a686c7dcf347513ce8141d59a251c6.signed-nakasi-JWR66Y-from-JWR66V.8b2531d9.zip'
E:Error installing zip file '/cache//8b2531d9d9a686c7dcf347513ce8141d59a251c6.signed-nakasi-JWR66Y-from-JWR66V.8b2531d9.zip'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Switching packages (TWRP)
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /data/media/0/recovery.log
Has anyone ran into this issue with the update?
Any solution to this?
dbenyakar said:
Hi All
Yesterday I received the update via OTA. When it rebooted into the TWRP recovery is started with the patch install process.
Then it failed.
After that it offered to fix the root, nice of him, which I did, and rebooted. Build version was still JWR66V.
This is what I got from the recovery log file:
Code:
Unpacking new recovery...
minzip: Can't create target file "/system/etc/install-recovery.sh": Permission denied
minzip: Extracted 0 file(s)
Symlinks and permissions...
set_perm: chown of /system/etc/install-recovery.sh to 0 0 failed: Operation not permitted
set_perm: chmod of /system/etc/install-recovery.sh to 544 failed: Operation not permitted
script aborted: set_perm: some changes failed
set_perm: some changes failed
E:Error executing updater binary in zip '/cache//8b2531d9d9a686c7dcf347513ce8141d59a251c6.signed-nakasi-JWR66Y-from-JWR66V.8b2531d9.zip'
E:Error installing zip file '/cache//8b2531d9d9a686c7dcf347513ce8141d59a251c6.signed-nakasi-JWR66Y-from-JWR66V.8b2531d9.zip'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Switching packages (TWRP)
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /data/media/0/recovery.log
Has anyone ran into this issue with the update?
Any solution to this?
Click to expand...
Click to collapse
You need to have stock recovery to run ota update. Plus your Rom has to be stock unmodified there that it checks for everything that comes factory with it.
Sent from my HTC One using Tapatalk 2
My Nexus 7 was rooted since day 1 and with a custom recovery, and always got the OTAs.
Why is this a problem now?
Are other people with rooted devices encountered the same issue?
Same Issue !!
dbenyakar said:
Hi All
Yesterday I received the update via OTA. When it rebooted into the TWRP recovery is started with the patch install process.
Then it failed.
After that it offered to fix the root, nice of him, which I did, and rebooted. Build version was still JWR66V.
This is what I got from the recovery log file:
Code:
Unpacking new recovery...
minzip: Can't create target file "/system/etc/install-recovery.sh": Permission denied
minzip: Extracted 0 file(s)
Symlinks and permissions...
set_perm: chown of /system/etc/install-recovery.sh to 0 0 failed: Operation not permitted
set_perm: chmod of /system/etc/install-recovery.sh to 544 failed: Operation not permitted
script aborted: set_perm: some changes failed
set_perm: some changes failed
E:Error executing updater binary in zip '/cache//8b2531d9d9a686c7dcf347513ce8141d59a251c6.signed-nakasi-JWR66Y-from-JWR66V.8b2531d9.zip'
E:Error installing zip file '/cache//8b2531d9d9a686c7dcf347513ce8141d59a251c6.signed-nakasi-JWR66Y-from-JWR66V.8b2531d9.zip'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Switching packages (TWRP)
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /data/media/0/recovery.log
Has anyone ran into this issue with the update?
Any solution to this?
Click to expand...
Click to collapse
I've got the same issue... it rebooted into the TWRP recovery, but the screen just freezed and touch didin't worked. Had to remove battery and reboot. After that, JWR66V was still there! And now, it doesn't prompt the update again. I'm thinking about flashing 4.3 again, root but not to install TWRP recovery, only 4.3 stock and root !! As @dbenyakar asked "any solution to this" ?
In time, mine is a Galaxy Nexus I9250...
dbenyakar said:
My Nexus 7 was rooted since day 1 and with a custom recovery, and always got the OTAs.
Why is this a problem now?
Are other people with rooted devices encountered the same issue?
Click to expand...
Click to collapse
Hi, dbenyakar...
The reason why the OTA that updates from JWR66V to JWR66Y fails if you are rooted concerns a file call /system/etc/install-recovery.sh and the different way that root now works under Jellybean 4.3.
Root uses the file install-recovery.sh to launch sudaemon that provides root, and during the process of gaining root, this file is set as 'immutable' to prevent root from being accidently lost. But this also prevents the OTA from modifying it, including the setting of permissions during the last stage of the OTA... therefore the OTA fails. See also this.
There are several different ways this problem can be resolved...
1) There is a slightly modified version of the OTA here, which 'rems out' the setting of permissions for /system/etc/install-recovery.sh, and allows the OTA to successfully complete. This modified OTA can be flashed in TWRP and was the method I used to upgrade.
2) Before allowing the OTA, unroot by going to SuperSU>>settings>>Full Unroot. Allow the OTA, and then re-root by flashing Chainfires SuperSu 1.51 in TWRP.
In any event, you'll probably need to re-root after the OTA anyway. I certainly had to.
Hope this helps.
Rgrds,
Ged.
So based on that is this something that will occur every OTA (i.e. you will have to unroot every OTA to avoid problems)?
GedBlake said:
Hi, dbenyakar...
The reason why the OTA that updates from JWR66V to JWR66Y fails if you are rooted concerns a file call /system/etc/install-recovery.sh and the different way that root now works under Jellybean 4.3.
Root uses the file install-recovery.sh to launch sudaemon that provides root, and during the process of gaining root, this file is set as 'immutable' to prevent root from being accidently lost. But this also prevents the OTA from modifying it, including the setting of permissions during the last stage of the OTA... therefore the OTA fails. See also this.
There are several different ways this problem can be resolved...
1) There is a slightly modified version of the OTA here, which 'rems out' the setting of permissions for /system/etc/install-recovery.sh, and allows the OTA to successfully complete. This modified OTA can be flashed in TWRP and was the method I used to upgrade.
2) Before allowing the OTA, unroot by going to SuperSU>>settings>>Full Unroot. Allow the OTA, and then re-root by flashing Chainfires SuperSu 1.51 in TWRP.
In any event, you'll probably need to re-root after the OTA anyway. I certainly had to.
Hope this helps.
Rgrds,
Ged.
Click to expand...
Click to collapse
OK great. Thanks for that. Will try it tonight.
I tried to use the OTA Root Keeper to temporarily unroot my device, only to realize it does not support 4.3.
So I guess I will have to unroot, update and re-root using your method. No shortcuts here. Once the OTA Root Keeper application will be compatible with 4.3 then it will be easier.
threi_ said:
So based on that is this something that will occur every OTA (i.e. you will have to unroot every OTA to avoid problems)?
Click to expand...
Click to collapse
Hi, threi_...
It's speculation, obviously, as one cannot know the contents of future OTAs beyond the current one which updates to build JWR66V... but it seems likely you will have to unroot, and then re-root again after the OTA.
But there may be workarounds... as I've indicated in my previous post, somebody has already posted a modified version of the current OTA that skips setting permissions for install-recovery.sh, and allows the OTA to complete successfully.
And to elaborate on my previous comments, here's why...
Root modifies /system/etc/install-recovery.sh in order to launch the su root daemon, and it contains the following lines...
Code:
#!/system/bin/sh
# If you're implementing this in a custom kernel/firmware,
# I suggest you use a different script name, and add a service
# to launch it from init.rc
# Launches SuperSU in daemon mode only on Android 4.3+.
# Nothing will happen on 4.2.x or older.
# If you want to force loading the daemon, use "--daemon" instead
/system/xbin/daemonsu --auto-daemon &
# Some apps like to run stuff from this script as well, but the
# installer will have done "chattr +i" on this file to prevent
# accidental modification and deletion. In your code, just search
# this file for "install-recovery-2.sh", and if present, write
# there instead.
/system/etc/install-recovery-2.sh
And during flashing Chainfires SuperSU root updater, the following operation is performed...
Code:
chattr +i /system/etc/install-recovery.sh
This 'locks' the file, using the +i flag ('immutable'), and prevents even system updates from modifying it.
You should be able to reverse this with...
Code:
su
mount -o rw,remount /system
chattr -i /system/etc/install-recovery.sh
mount -o ro,remount /system
...in Android Terminal Emulator, but you will need Busybox installed.
So it's probably just easier to unroot... allow the OTA as normal (or flash the OTA .zip in recovery)... and then re-root again. And I can't see this changing with future OTA's... but as I stated at the beginning of this post, this is just speculation on my part.
Rgrds,
Ged.
Hi. I am on 4.3 stock rooted with m kernel a61 and with advanced power menu mod and awesome beats. Cant update .read everything about this new update and also opened a thread but still cant find a way to update.flashing failed.tried full unroot and faild again.trid modified grouper.zip and that also failed.
Any ideas???
Sent from my Nexus 7 using xda premium
dobrun.franjo said:
Hi. I am on 4.3 stock rooted with m kernel a61 and with advanced power menu mod and awesome beats. Cant update .read everything about this new update and also opened a thread but still cant find a way to update.flashing failed.tried full unroot and faild again.trid modified grouper.zip and that also failed.
Any ideas???
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hi, dobrun.franjo...
Any modifications to system (including kernel) need to be removed before any OTA can proceed... and I suspect 'advanced power menu mod and awesome beats' have modified system.
This is because OTAs run a checksum on all files in system BEFORE 'patching' (meaning updating) them, to ensure they haven't been removed or changed in anyway. After all, an official OTA can't be expected to update files it has no knowledge of, that have been added by the user. If even one fails this checksum test, the OTA will abort, with no changes made.
So... remove advanced power menu, remove awesome beats and fastboot flash the factory stock kernel for Jellybean 4.3. Even then, there are no guarantees the OTA will work, without knowing (and being able to reverse) EXACTLY what files where changed as a consequence of your modifications... but it's worth a shot.
Good luck.
Rgrds,
Ged.
threi_ said:
So based on that is this something that will occur every OTA (i.e. you will have to unroot every OTA to avoid problems)?
Click to expand...
Click to collapse
As long as the new root process goes through the installrecovery.sh, correct
dbenyakar said:
Once the OTA Root Keeper application will be compatible with 4.3 then it will be easier.
Click to expand...
Click to collapse
Supercurio has already said as long as it stays this way, OTA rootkeeper won't be possible anymore.
supercurio said:
It means preserving root with OTA Root Keeper won't be possible anymore as new rooting techniques rely on more than just a setuid su binary in /system.
I'll look into solution of course to preserve the functionality if possible, but until then please follow Chainfire's job on SuperSU betas.
Click to expand...
Click to collapse
NeoMagus said:
As long as the new root process goes through the installrecovery.sh, correct
Supercurio has already said as long as it stays this way, OTA rootkeeper won't be possible anymore.
Click to expand...
Click to collapse
Yes however a method has been found for 4.3, so I'll look into that soon
dobrun.franjo said:
Hi. I am on 4.3 stock rooted with m kernel a61 and with advanced power menu mod and awesome beats. Cant update .read everything about this new update and also opened a thread but still cant find a way to update.flashing failed.tried full unroot and faild again.trid modified grouper.zip and that also failed.
Any ideas???
Click to expand...
Click to collapse
As the previous poster said, you screwed with system, OTA's won't work. Easiest way to update at this point IMO is to grab the YJWR66 factory image from Google and fastboot flash system, then re-root.
Today I have update with OTA and same error appear.
Now I have unroot the nexus with supersu's app but how I can update it? It doesn't give any update now
Thx guys.
Inviato dal mio Nexus 7 usando Tapatalk 4
GedBlake said:
Hi, dbenyakar...
The reason why the OTA that updates from JWR66V to JWR66Y fails if you are rooted concerns a file call /system/etc/install-recovery.sh and the different way that root now works under Jellybean 4.3.
Root uses the file install-recovery.sh to launch sudaemon that provides root, and during the process of gaining root, this file is set as 'immutable' to prevent root from being accidently lost. But this also prevents the OTA from modifying it, including the setting of permissions during the last stage of the OTA... therefore the OTA fails. See also this.
There are several different ways this problem can be resolved...
1) There is a slightly modified version of the OTA here, which 'rems out' the setting of permissions for /system/etc/install-recovery.sh, and allows the OTA to successfully complete. This modified OTA can be flashed in TWRP and was the method I used to upgrade.
2) Before allowing the OTA, unroot by going to SuperSU>>settings>>Full Unroot. Allow the OTA, and then re-root by flashing Chainfires SuperSu 1.51 in TWRP.
In any event, you'll probably need to re-root after the OTA anyway. I certainly had to.
Hope this helps.
Rgrds,
Ged.
Click to expand...
Click to collapse
OK I did it your way. Thank you very much for that.
I had some problems with my SuperSU and could not access the SuperSU>>settings but eventually I managed to unroot the device and continue with the installation and re-root. :laugh:
GedBlake said:
Hi, dbenyakar...
The reason why the OTA that updates from JWR66V to JWR66Y fails if you are rooted concerns a file call /system/etc/install-recovery.sh and the different way that root now works under Jellybean 4.3.
Root uses the file install-recovery.sh to launch sudaemon that provides root, and during the process of gaining root, this file is set as 'immutable' to prevent root from being accidently lost. But this also prevents the OTA from modifying it, including the setting of permissions during the last stage of the OTA... therefore the OTA fails. See also this.
There are several different ways this problem can be resolved...
1) There is a slightly modified version of the OTA here, which 'rems out' the setting of permissions for /system/etc/install-recovery.sh, and allows the OTA to successfully complete. This modified OTA can be flashed in TWRP and was the method I used to upgrade.
2) Before allowing the OTA, unroot by going to SuperSU>>settings>>Full Unroot. Allow the OTA, and then re-root by flashing Chainfires SuperSu 1.51 in TWRP.
In any event, you'll probably need to re-root after the OTA anyway. I certainly had to.
Hope this helps.
Rgrds,
Ged.
Click to expand...
Click to collapse
I tried step one and it failed in twrp. I downloaded grouper for my WiFi version. Any ideas why it failed? Is it because I'm trying to flash over clean ROM 4?
Sent from my Nexus 7 using xda app-developers app
tu3218 said:
I tried step one and it failed in twrp. I downloaded grouper for my WiFi version. Any ideas why it failed? Is it because I'm trying to flash over clean ROM 4?
Click to expand...
Click to collapse
2000+ posts and you don't realize you can't flash a stock OTA over $randomrom ? Just wow.
khaytsus said:
2000+ posts and you don't realize you can't flash a stock OTA over $randomrom ? Just wow.
Click to expand...
Click to collapse
Well its a small zip. Not a full ROM. So I figured it was just patching the updated files. Clean ROM is a pretty stock ROM so I was thinking it may have worked. Normally updates are full roms.
Sent from my Nexus 7 using xda app-developers app
tu3218 said:
Well its a small zip. Not a full ROM. So I figured it was just patching the updated files. Clean ROM is a pretty stock ROM so I was thinking it may have worked. Normally updates are full roms.
Click to expand...
Click to collapse
Updates are never full ROMs, they're a set of patches against checksummed files. Any single checksum difference and it'll fail. IE: Modify the ROM in almost any way, you can't use OTAs.
When you're on a custom ROM, use the custom ROM updates as they come out, no real difference between modified stock and say Cyanogenmod in this respect.
khaytsus said:
Updates are never full ROMs, they're a set of patches against checksummed files. Any single checksum difference and it'll fail. IE: Modify the ROM in almost any way, you can't use OTAs.
When you're on a custom ROM, use the custom ROM updates as they come out, no real difference between modified stock and say Cyanogenmod in this respect.
Click to expand...
Click to collapse
Yeah you're right. Not sure what made me think it would work. I guess I was thinking it was modified, but its still just the stock ota with a slight adjustment to be installed properly on rooted devices.
It doesn't appear clean ROM will be updated as scott has ,moved onto the newer nexus 7. So I have to find out my next best move. I'm fine with stock, just getting there.
Sent from my Nexus 7 using xda app-developers app
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!!
Hi, may I ask how do I fix this error? First post on this group
this is the error I got when installing Magisk using TWRP twrp-3.0.2-0-ze500kl
my device is ze500kl firmware WW-13.1010.1612.53
Updating partision details...
...done
Full Selinux support is present.
MTP Enabled
Installing ZIP file '/sdcard/Magiskmanager/magisk-v13.3.zip
Checking for MD5 file...
Skipping MD5 Check: no MD5 file found
*****************************
*Magisk v13.3 Installer
*****************************
-Mounting /System, /Vendor, /cache, /data
-Device platform: arm64
-Constructing environment
-/data/magisk.img detected!
-Mounting /data/magisk.img to /magisk
-Found Boot Image: /dev/block/mmclk0p34
-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 '/sdcard/MagiskManager/Magisk-v13.3.zip'
Updating partition details...
...done
knorcube71 said:
Hi, may I ask how do I fix this error? First post on this group
this is the error I got when installing Magisk using TWRP twrp-3.0.2-0-ze500kl
my device is ze500kl firmware WW-13.1010.1612.53
Updating partision details...
...done
Full Selinux support is present.
MTP Enabled
Installing ZIP file '/sdcard/Magiskmanager/magisk-v13.3.zip
Checking for MD5 file...
Skipping MD5 Check: no MD5 file found
*****************************
*Magisk v13.3 Installer
*****************************
-Mounting /System, /Vendor, /cache, /data
-Device platform: arm64
-Constructing environment
-/data/magisk.img detected!
-Mounting /data/magisk.img to /magisk
-Found Boot Image: /dev/block/mmclk0p34
-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 '/sdcard/MagiskManager/Magisk-v13.3.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
Hello. Use the magisk_uninstaller.zip first. From what I saw in your log, your boot.img is already patch by something else. You need to install magisk on your stock boot.img
Envoyé de mon SM-N935S en utilisant Tapatalk
https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
Is there a way I can install Magisk without stock boot image? I installed a custom ROM that installs SuperSU and I want to uninstall SuperSU and install Magisk.
keeganjk said:
Is there a way I can install Magisk without stock boot image? I installed a custom ROM that installs SuperSU and I want to uninstall SuperSU and install Magisk.
Click to expand...
Click to collapse
You'll probably be able to find an untouched boot image inside the ROM zip. I believe I've written about this in the link I shared above...
Didgeridoohan said:
You'll probably be able to find an untouched boot image inside the ROM zip. I believe I've written about this in the link I shared above...
Click to expand...
Click to collapse
Could you elaborate on that?
---------- Post added at 12:16 AM ---------- Previous post was at 12:05 AM ----------
Didgeridoohan said:
You'll probably be able to find an untouched boot image inside the ROM zip. I believe I've written about this in the link I shared above...
Click to expand...
Click to collapse
I want to keep my custom Rom installed
keeganjk said:
Could you elaborate on that?
I want to keep my custom Rom installed
Click to expand...
Click to collapse
I already have, in the link provided above... Look under "Moving from another systemless root solution to MagiskSU".
I have been using FreedomOS on my OnePlus 5. I try to install Burgerhunter over it with OOS. The nethunter zip installs SuperSU and downgrades Magisk to v2.82 or something like that, so after the install I select "switch superuser app" and it removes SuperSU. However, once it reboots, I try to download and install the Magisk upgrade, but results in an error.
keeganjk said:
I have been using FreedomOS on my OnePlus 5. I try to install Burgerhunter over it with OOS. The nethunter zip installs SuperSU and downgrades Magisk to v2.82 or something like that, so after the install I select "switch superuser app" and it removes SuperSU. However, once it reboots, I try to download and install the Magisk upgrade, but results in an error.
Click to expand...
Click to collapse
The option you want to use in the SuperSU app is "complete unroot". (Or something like that. Haven't used SuperSU in a long time).
Didgeridoohan said:
The option you want to use in the SuperSU app is "complete unroot". (Or something like that. Haven't used SuperSU in a long time).
Click to expand...
Click to collapse
I'll try that when I get a chance...
---------- Post added at 04:12 PM ---------- Previous post was at 03:26 PM ----------
Didgeridoohan said:
The option you want to use in the SuperSU app is "complete unroot". (Or something like that. Haven't used SuperSU in a long time).
Click to expand...
Click to collapse
It didn't work; terminal crashes when I try to open it.
Flash Magisk V11.1
I was in the same situation and saw this in another forum...works pretty well...
benyou54 said:
Hello. Use the magisk_uninstaller.zip first. From what I saw in your log, your boot.img is already patch by something else. You need to install magisk on your stock boot.img
Envoyé de mon SM-N935S en utilisant Tapatalk
Click to expand...
Click to collapse
I already did what you say, but now I get the error :
*****************************
*Magisk Unnstaller
*****************************
-Mounting /System, /Vendor, /cache, /data
-Device platform: arm64
-Constructing environment
-/data/magisk.img detected!
-Mounting /data/magisk.img to /magisk
-Found Boot Image: /dev/block/mmclk0p34
-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 '/sdcard/MagiskManager/Magisk-uninstaller-20170928.zip'
Updating partition details...
...done
Adicct0 said:
I already did what you say, but now I get the error :
*****************************
*Magisk Unnstaller
*****************************
-Mounting /System, /Vendor, /cache, /data
-Device platform: arm64
-Constructing environment
-/data/magisk.img detected!
-Mounting /data/magisk.img to /magisk
-Found Boot Image: /dev/block/mmclk0p34
-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 '/sdcard/MagiskManager/Magisk-uninstaller-20170928.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
So restore your original (stock or custom) boot.img with odin by creating a tar file flashing in the AP case of odin [emoji6]
Envoyé de mon SM-N950F en utilisant Tapatalk
can you please explain the process with corresponding download links. Even i faced the same error at both the cases. And am using AOSP 8.1 for redmi note 4.
Me too help
Exact same error
keeganjk said:
Is there a way I can install Magisk without stock boot image? I installed a custom ROM that installs SuperSU and I want to uninstall SuperSU and install Magisk.
Click to expand...
Click to collapse
No. you will need a stock boot image to install magisk because since Super SU replaces demon with SUdemon and the Magiskdemon is not scripted to patch any other superuser scripts other than that in stock boot image
I want to install magisk app in samsung galaxy grand neo plus . And want to remove it. I tried to install magisk app by twrp but due to " updater process ended with error 1 " it not install . Please help me to install magisk
[email protected] said:
I want to install magisk app in samsung galaxy grand neo plus . And want to remove it. I tried to install magisk app by twrp but due to " updater process ended with error 1 " it not install . Please help me to install magisk
Click to expand...
Click to collapse
Recovery log needed...
https://www.didgeridoohan.com/magisk/Magisk#hn_Asking_for_help
Didgeridoohan said:
Recovery log needed...
https://www.didgeridoohan.com/magisk/Magisk#hn_Asking_for_help
Click to expand...
Click to collapse
I had the same error solve with f2fs-loopback-bug-workaround-2018.1.24.zip
rosel11078 said:
I had the same error solve with f2fs-loopback-bug-workaround-2018.1.24.zip
Click to expand...
Click to collapse
The f2fs issue is certainly a possibility, but "error 1" can mean just about anything. So without a log it's impossible to know for sure...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
" #DroidOnTime "
ROM Version: 3.1
Device: axon7
Maintainer: SaintZ93
Build Status: Unofficial
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
"This is a user-friendly thread, all your suggestions are important to us and will be taken into consideration.."
dotOS is an Android ROM which focuses on performance and stability. We focus on making our rom look and feel great without struggling on Performance and Battery! So that one can get most out of his/her device.....
CLEAN FLASH :
Download the latest build and GApps
Reboot to recovery
Make NAndroid backup (Not Necessary)
Wipe System, Data, Cache , Dalvik, Vendor
Flash the latest build and GApps
Reboot
DIRTY FLASH :
Download the latest build
Reboot to recovery
Flash the latest build
Wipe Cache
Reboot
Note: GApps only has to be flashed once whereas Magisk/Su is to be flashed every time you Dirty Flash the OTA Update.
DotOS Axon7 Downloads
OpenGApps
Note : Pico, Nano or Micro Gapps are recommended. We don't prefer STOCK/HEAVY Gapps
Code:
[LIST]
[U][B]STATUSBAR:[/B][/U]
[*]Battery Icon Style
[*]Clock and Date
[*]Statusbar icons
[*]Brightness Control
[*]Show 4G icon instead LTE
[*]Roaming Indicator
[*]Battery Bar Customisation
[*]Status Bar Gestures
[*]Volte Icon Toggle
[*]Wake up on charge plugged/unplugged
[*]Show DotOS logo on statusbar
[U][B]Navigation Bar:[/B][/U]
[*]Navbar modes(Stock, Smartbar, Fling)
[*]Smartbar tweaks
[*]Navbar Pulse
[*]Fling mode gestures
[*]All DUI nav tweaks
[U][B]QUICK SETTINGS:[/B][/U]
[*]Brightness slider toggle
[*]Titles visibility
[*]Tiles track accent color toggle
[*]Qs panel Opacity
[*]Vibrate when touching QS tiles
[*]Rows and columns tweaks
[U][B]RECENTS:[/B][/U]
[*]Toggle to switch between pie and oreo recents
[U][B]LOCKSCREEN:[/B][/U]
[*]Double-tap to sleep
[*]Lockscreen Tuner
[*]Charging info
[*]Lockscreen shortcuts
[*]Media cover art toggle
[*]Lockscreen Visualizer
[*]Lockscreen clock widgets
[*]Face auto unlock
[*]Fingerprint Authentication Vibration
[*]Ambient Music Ticker
[*]Lockscreen visualizer
[*]Lockscreen Weather
[U][B]BUTTONS:[/B][/U]
[*]Powermenu tweaks
[*]Powermenu Visibility on lockscreen
[*]Backlight Customisation
[*]H/W keys customization
[*]Volume button tweaks
[U][B]MISC:[/B][/U]
[*]3 finger swipe Screenshot guesture
[*]Battery light charging customisations
[*]Toast app icon switch
[U][B]System wide themes:[/B][/U]
[*]Accent Color Manager - Fruity pebbles
[*]Qs panel Customisation
[*]Neo theme
[U][B]Extras:[/B][/U]
[*]Ablity to reset Battery Stats
[*]Switch to disable Screenshot sound
[*]Auto Call Recording
[*]Set ringtone for each sim slot
[*]Switch to disable/enable Dashboard suggestions
[*]Digital Wellbeing Preinstalled
[/LIST]
DotOSteam
AOSP
JDC Team
Aosp Extended
Dirty Unicorns
And all other open source Devs/Teams.
Mohan CM - Founder/Core Developer
Sam Grande - UI Developer/Project Co-ordinator
Iacob Ionut - UI Developer/ Core Developer
Hari Ambadi - Core GFX/Visual Designer
Special thanks:
Alexc Brookes - Arts & Wallpaper Designer
Paul Petrov - Arts & UI Designer
Important Links
Liked The ROm? Want to Help Us? Then gift us some credits
dot
OS source
dotOS-Device Sources
Device Tree
Kernel Source
Google Plus Community
Telegram Group
Telegram Channel
Website
REPORTING BUGS!
As soon as the problem occurs, take a logcat!
for more READ THIS
XDA:DevDB Information
[UNOFFICIAL][9.0.0_R47] dotOS 3.1 [AXON7][08/13/19], ROM for the ZTE Axon 7
Contributors
SaintZ93
Source Code: https://github.com/DotOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Oreo Baseband
Based On: DotOS
Version Information
Status: Stable
Current Stable Version: 3.1
Stable Release Date: 2019-08-13
Created 2019-08-13
Last Updated 2019-08-13
Thank you for the rom, everything is working ok.
This is the best pie rom I have tried, everything is fast and smooth.
By the way, what does it means the "R47" at the title?
Google source code android release tag
Ah yes, my favorite custom ROM has returned in absolute glory. Thank you for bringing this to the Axon 7. Everything is running smooth and working well, with great stability.
Not working for me, stuck on boot.
Hi all !
I have the same problem @Dragon502
That's ok for me, after doing a Flash EDL Axon7_LOS15.1_180925_B12Oki_TWRP_LABS1.3_FULL_EDL.zip
You didn't follow instructions then. Its been working for everyone, including me.
SaintZ93 said:
You didn't follow instructions then. Its been working for everyone, including me.
Click to expand...
Click to collapse
I can assure you I have, they are not that complex.
If I messed up something is in the "treblerization" which I still find quite confusing. What I did was:
- wiping everying
- creating vendor partion with TWRP w/PARTY mod.
- reflashing Draken's bootstack and modem
- flashing NFound v1.1 zip (vendor's?)
- reflashing TWRP since NFound's zip rolls it back
- wiping everything again (system, vendor, data, cache and dalvik) (rom's instructions)
- flash dotOs
- flash Gapps
- reboot
Notice that on boot I had and still have the "your device is corrupt" thing, but it lets me boot. It would be amazing if someone could help me remove that or at least tell me what component does that.
Anyway, from the reboot it hangs loading on the dynamic initial logo. I waited the first time about 30 min and about 15 the second time I did it.
Now I am running AOKP Oreo which seems to be working fine.
I needed a new a ROM because the AEX I was running messed up the USB connection which I need for app devel.
I believe this is all. Hopefully I recalled correctly what I did even if the "treblerization" thing is still confusing to me, or at least its practical implementation is.
Dragon502 said:
I can assure you I have, they are not that complex.
If I messed up something is in the "treblerization" which I still find quite confusing. What I did was:
- wiping everying
- creating vendor partion with TWRP w/PARTY mod.
- reflashing Draken's bootstack and modem
- flashing NFound v1.1 zip (vendor's?)
- reflashing TWRP since NFound's zip rolls it back
- wiping everything again (system, vendor, data, cache and dalvik) (rom's instructions)
- flash dotOs
- flash Gapps
- reboot
Notice that on boot I had and still have the "your device is corrupt" thing, but it lets me boot. It would be amazing if someone could help me remove that or at least tell me what component does that.
Anyway, from the reboot it hangs loading on the dynamic initial logo. I waited the first time about 30 min and about 15 the second time I did it.
Now I am running AOKP Oreo which seems to be working fine.
I needed a new a ROM because the AEX I was running messed up the USB connection which I need for app devel.
I believe this is all. Hopefully I recalled correctly what I did even if the "treblerization" thing is still confusing to me, or at least its practical implementation is.
Click to expand...
Click to collapse
Do not use NFounds crap as these new ROMs are device related and not GSI.
SaintZ93 said:
Do not use NFounds crap as these new ROMs are device related and not GSI.
Click to expand...
Click to collapse
So I should have removed the vendor's partition to flash this ROM? AOKP seems to work fine but it lacks some feature (like night light) and is still Oreo. Maybe when I find the time I may attempt again.
Dragon502 said:
I can assure you I have, they are not that complex.
If I messed up something is in the "treblerization" which I still find quite confusing. What I did was:
- wiping everying
- creating vendor partion with TWRP w/PARTY mod.
- reflashing Draken's bootstack and modem
- flashing NFound v1.1 zip (vendor's?)
- reflashing TWRP since NFound's zip rolls it back
- wiping everything again (system, vendor, data, cache and dalvik) (rom's instructions)
- flash dotOs
- flash Gapps
- reboot
Notice that on boot I had and still have the "your device is corrupt" thing, but it lets me boot. It would be amazing if someone could help me remove that or at least tell me what component does that.
Anyway, from the reboot it hangs loading on the dynamic initial logo. I waited the first time about 30 min and about 15 the second time I did it.
Now I am running AOKP Oreo which seems to be working fine.
I needed a new a ROM because the AEX I was running messed up the USB connection which I need for app devel.
I believe this is all. Hopefully I recalled correctly what I did even if the "treblerization" thing is still confusing to me, or at least its practical implementation is.
Click to expand...
Click to collapse
- creating vendor partion with TWRP w/PARTY mod.
did you select 512mb and System? That's what you need to use. Anyways the best way would probably be installing LOS 16 as it makes you a vendor partition, but you'd have to delete the previous one for that.
- flashing NFound v1.1 zip (vendor's?)
Yes, that's NFound's vendor files, made for GSI's. This isn't needed as any new device specific ROMs come with a vendor, so it'll get overwritten. hell, you actually wipe vendor after reflashing TWRP. also, no need to be using NFound's ancient stuff anymore, only the TWRP is useful and even then I prefer Oki's
Also you might want to flash Magisk before booting
Choose an username... said:
- creating vendor partion with TWRP w/PARTY mod.
did you select 512mb and System? That's what you need to use. Anyways the best way would probably be installing LOS 16 as it makes you a vendor partition, but you'd have to delete the previous one for that.
Click to expand...
Click to collapse
No, I made a 800mb one from data but from the end of the partition. It should make no difference the size of the partion, shouldn't it?
Choose an username... said:
-
- flashing NFound v1.1 zip (vendor's?)
Yes, that's NFound's vendor files, made for GSI's. This isn't needed as any new device specific ROMs come with a vendor, so it'll get overwritten. hell, you actually wipe vendor after reflashing TWRP. also, no need to be using NFound's ancient stuff anymore, only the TWRP is useful and even then I prefer Oki's
Also you might want to flash Magisk before booting
Click to expand...
Click to collapse
Finally is starting to make sense, therefore these ROMs are "treblerized" but prepackaged to be device specific right?
As concerning the bootstacks, with an A2017G, does it makes sense for me to still have Draken's or I can safely upgrade to a B03 full EDL with the Axon tool? What would change between the versions?
Attempt update
Logs:
Code:
#########################################
# #
# - P A R T Y - #
# #
# The Android Partition Treblerizer #
# #
#########################################
# #
# v0.6 (c) Oki @ XDA 2018-08-31 #
# #
#########################################
This tool creates or removes the vendor
partition taking space from system or
userdata partitions. This way, developers
will be able to create Treble ROMs for
legacy devices. and users can switch back
and forth from Non Treble to Treble ROMs.
Press Vol Up to continue...
CURRENT CONFIGURATION:
SYSTEM size: 5.5 GB
DATA size: 52.41 GB
VENDOR SIZE: 512 MB
- Vendor partition detected after SYSTEM partition.
Do you want to remove Vendor and return to stock
partition table?
Vol UP: YES / Vol DN: NO
- No changes were applied to the partition table.
I:Updater process ended with RC=0
I:Install took 5 second(s).
Updating partition details...
I:Data backup size is 0MB, free: 44461MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I:operation_end - status=0
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:operation_start: 'Flashing'
Installing zip file '/external_sd/dotOS-P-v3.1-axon7-UNOFFICIAL-20190813-0014.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
I:Update binary zip
Verifying package compatibility...
Package doesn't contain compatibility.zip entry
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment not used in updater.
SELinux: Loaded file_contexts
Checking for TZ version TZ.BF.4.0.1-00353Checking for TZ version TZ.BF.4.0.1-00353
script aborted: assert failed: axon7.verify_trustzone("TZ.BF.4.0.1-00353") == "1"
assert failed: axon7.verify_trustzone("TZ.BF.4.0.1-00353") == "1"error: 25
Updater process ended with ERROR: 7
I:Install took 0 second(s).
Error installing zip file '/external_sd/dotOS-P-v3.1-axon7-UNOFFICIAL-20190813-0014.zip'
Updating partition details...
I:Data backup size is 0MB, free: 44461MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I:operation_end - status=1
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'copylog'
I:Set page: 'action_page'
I:operation_start: 'Copy Log'
I:Copying file /tmp/recovery.log to /external_sd/recovery.log
script aborted: assert failed: axon7.verify_trustzone("TZ.BF.4.0.1-00353") == "1"
If I have to guess it seems like the issue comes from the bootstack. I tried with the B04 I found for SL!M8 as I am downloading B03_FULL_EDL.
Update: The "your device is corrupted... " screen went away with Drakens B03 bootsack I have managed to find, but the ROM still throws the same error with the verify_trustzone issue.
Diez3l said:
Hi all !
I have the same problem @Dragon502
That's ok for me, after doing a Flash EDL Axon7_LOS15.1_180925_B12Oki_TWRP_LABS1.3_FULL_EDL.zip
Click to expand...
Click to collapse
Oh, I did not see that. I am going to try that.
---------- Post added at 10:44 PM ---------- Previous post was at 10:04 PM ----------
Yup, LOS 15 Bootstak, although brough back the "your device is corrupted" screen, did the trick. DotOS Pie is working for me.
Now it is time to check if everything works. Thank you both @Diez3l and @SaintZ93.
Hello, I have a problem, I can't switch data service network from sim1 to sim2
Sent from my ZTE A2017U using Tapatalk
Dragon502 said:
No, I made a 800mb one from data but from the end of the partition. It should make no difference the size of the partion, shouldn't it?
Click to expand...
Click to collapse
It does. Your partition is literally all wrong lol, should be System and 512.
Dragon502 said:
Finally is starting to make sense, therefore these ROMs are "treblerized" but prepackaged to be device specific right?
Click to expand...
Click to collapse
Not really - Treble is something inherent to the device, and on new devices, which have treble by default, everything is made to work with it. Think about it as a simple move of some files to a specific partition.
ROMs use Treble but at the same time are made with the actual phone device tree. GSIs use the generic device tree instead
Dragon502 said:
As concerning the bootstacks, with an A2017G, does it makes sense for me to still have Draken's or I can safely upgrade to a B03 full EDL with the Axon tool? What would change between the versions?
Click to expand...
Click to collapse
I'm not getting this one - B03 full EDL? You wanna return to stock?
Choose an username... said:
It does. Your partition is literally all wrong lol, should be System and 512.
Click to expand...
Click to collapse
That is some prerequisite I would write in the installation instruction.
Choose an username... said:
Not really - Treble is something inherent to the device, and on new devices, which have treble by default, everything is made to work with it. Think about it as a simple move of some files to a specific partition.
ROMs use Treble but at the same time are made with the actual phone device tree. GSIs use the generic device tree instead
Click to expand...
Click to collapse
Ah, ok. They are device specific ROMs repackaged to fit in "treblerized" phones.
Choose an username... said:
I'm not getting this one - B03 full EDL? You wanna return to stock?
Click to expand...
Click to collapse
Nope, I wanna understand what is the difference between a full EDL and a boostack zip. Well, I have found that they contain a stock image.
Thank you for the enlightment.
As a final update everything I care about seems to be working (DAC, baddar kernel, Ainur narsil, usb debugging and night light).
Dragon502 said:
That is some prerequisite I would write in the installation instruction.
Click to expand...
Click to collapse
Oki's fault - anyways not many people use Party, and the one swho did sometimes had non-working vendors even though they were correct.
Dragon502 said:
Ah, ok. They are device specific ROMs repackaged to fit in "treblerized" phones.
Click to expand...
Click to collapse
Still no. Our phone IS Treble now, hence the ROM has to be treble. The thing that has been "treblerized" is the Axon7.
You can't take any ROM and "repackage" it, you have to build it specifically for a certain phone. then, it gets whatever it needs to run on it
Dragon502 said:
Nope, I wanna understand what is the difference between a full EDL and a boostack zip. Well, I have found that they contain a stock image.
Click to expand...
Click to collapse
The bootstack zip has some files like fastboot, the boot stuff like boot image and everything that supports it, modem image, etc.
A full EDL zip is the whole damn system, so you also get stock system and the recovery which is 90% of the full edl zip
Choose an username... said:
Oki's fault - anyways not many people use Party, and the one swho did sometimes had non-working vendors even though they were correct.
Still no. Our phone IS Treble now, hence the ROM has to be treble. The thing that has been "treblerized" is the Axon7.
You can't take any ROM and "repackage" it, you have to build it specifically for a certain phone. then, it gets whatever it needs to run on it
The bootstack zip has some files like fastboot, the boot stuff like boot image and everything that supports it, modem image, etc.
A full EDL zip is the whole damn system, so you also get stock system and the recovery which is 90% of the full edl zip
Click to expand...
Click to collapse
This rom does not boot on my axon a2017u bootloops
Hi there,
I´m not able to install AospExtended or any other Custom ROM on my Z2 Pro. I spent several days on troubleshooting without any success. TWRP / RedWolf Error 7. Failed to mount /vendor (Invalid argument)
Tried it with different "Factory2vendor" files. all TWRP Version from 3.1 til the latest 3.3.1.0.
I did some rollbacks to ZU 1.9, 2.5 and 3.1 via QFIL.
recvoery.log
Code:
open "/dev/block/bootdevice/by-name/vendor" failed: No such file or directory
script aborted: E2001: Failed to update vendor image.
E2001: Failed to update vendor image.error: 2001
Updater process ended with ERROR: 7
Can anyone help me out of this issue?
Many thanks!
toto1988
EDIT: right now I´m not able to install factory2vendor.zip --> I got the same message: Failed to mount /vendor (Invalid Argument)
Hi there, I never seen this issue nor tried to install that rom (in my todo list).
But have you tried mounting the vendor partition on twrt before running the rom or zip file?
Got the same issue.... Really in need for a fix
Sorry, I don’t speak English, all depends on Google Translate. Please understand if there is any mistake.
1. You should first flash QFIL into 1.9.104
2. Unlock your phone and swipe into TWRP
3. Flash into the full version of zui3.5.388rom
4. Swipe [Android-10][Z2_row] PixysOS to use Android-10
I tried to flash AospExtended ROM V7.0 and it also failed
Sorry, the resource was found in the China Forum, I am not sure if you can access this resource:
[ROM1.9.104]https://club.lenovo.com.cn/thread-1810687-1-1.html
[ROM3.5.388]https://club.lenovo.com.cn/thread-4511179-1-1.html
chzzl said:
Sorry, I don’t speak English, all depends on Google Translate. Please understand if there is any mistake.
1. You should first flash QFIL into 1.9.104
2. Unlock your phone and swipe into TWRP
3. Flash into the full version of zui3.5.388rom
4. Swipe [Android-10][Z2_row] PixysOS to use Android-10
I tried to flash AospExtended ROM V7.0 and it also failed
Sorry, the resource was found in the China Forum, I am not sure if you can access this resource:
[ROM1.9.104]https://club.lenovo.com.cn/thread-1810687-1-1.html
[ROM3.5.388]https://club.lenovo.com.cn/thread-4511179-1-1.html
Click to expand...
Click to collapse
not working....
Do anyone had a fix? Now I have a second Z2 Pro with the same error. I´m not able to Install a Android 9 or 10 based custom ROM.
- post was moved to other thread -