Related
Back a year ago I rooted my nexus one phone, but the thing is I uninstalled a few stock apps. I had no idea that my updates would be a pain.
What I found out is that each new google update does a ton of asserts on files that it expects to be there. I had a problem with google books when I tried to update from 2.3.3 to 2.3.4, but someone on this forum hack a cracked version that allowed me to do so.
Now the annoying problem is back again, and this time, it's saying something about assert_failed: apply patch check ("system/app/EmailGoogle.apk...
I tried to find an EmailGoogle.apk out there, and I was able to find it, but if I was to use it, it wouldn't connect at all, then it would crash. I also placed it in system/app folder, and still same problem.
Is there a way for me to hack the update.zip so I can tell it to ignore these assertions?
AHH! I figured it out!
After much searching for updating scripts, I found out that there is indeed a file that tells your phone how to perform a patch update.
This involved me rebooting the phone 7 times (with about 5 times prior with previous experimentation)
Okay what I had were the following items
-Dropbox
-Root Explorer
-Laptop
Initially I got the error after running anon ra recovery, but I lost it when I accidently updated 2.3.4 again (I stupidly named my files as update.zip, update1.zip, update2.zip). Actually, I lost root (the phone still had the unlocked thing on it, but it was fooled). So I used this website (to root my phone again):
http://chensun.net/android-development/root-nexus-one-with-android-2-3-3-gingerbread/8/
So to get the specific error
1.you shut down your phone
2. reboot by pressing power button and down volume and hold it
3. Select recovery by navigating using the down volume, and select it by pressing power button.
4. After it reboots again, scroll down using your trackball and select Flash zip from sdcard
5. make sure you toggle signature verification to disable
6. select your update.zip
thats how you get your error
to fix:
1. So I took the signed zip file, and uploaded it to my dropbox
2. I opened the file using winrar (DO NOT UNZIP THIS FILE TO EDIT) the reason you do not want to unzip is because if you zip it up again you lose the signature, and your phone won't find the script
3. I used winrar to navigate to the following:
META-INF-->com-->google-->android
4. Open update-script using notepad
5. crtl-f on each package-name searching through the file:
emailgoogle.apk
GenieWidget.apk
Mms.apk
Talk.apk
Twitter.apk
VoiceDialer.apk
(ugh.. I forgot I uninstalled all those)
they existed twice. Once to assert to make sure the file exists, and the second to apply the patch
You have to remove both, you can keep the progress bar command there, that's just to update the progress of your update on your screen
example
;assert(apply_patch_check("/system/app/Twitter.apk", "48dcef1792760138acb1c10e2a2341dfbee69258", "e3e34aa0a72d0eaf76d80a06828bd14ea8450d34"))
apply_patch("/system/app/Twitter.apk", "-",
48dcef1792760138acb1c10e2a2341dfbee69258, 1596937,
e3e34aa0a72d0eaf76d80a06828bd14ea8450d34, package_extract_file("patch/system/app/Twitter.apk.p"));
so after repeating this over and over, it finally updated
anyways, going to sleep
Unzip the file on your phone with eStrongs file manager.
Edit the update script (eStrongs again).
Rezip (eStrongs again).
Sign with ZipSigner, or toggle signature verification in recovery.
Flash.
Note, if you use the "flash zip from SD" option, you don't need to name the file "update.zip"
thanks danger-rat, seen your posts many times before, I saved lots of your comments in my evernote
I already knew about renaming update.zip, I just got into a dumb naming habit, the last 5 tries I just kept the name as it was
my root explorer (file manager) by speed software does what eStrongs does, I can edit, zip, tar, unmount folders, set permissions etc, maybe you should check it out
but i've learned two new things about your post
never heard of zipsigner, and eStrongs
thanks for showing the quicker way of doing this, the dropbox thing was a bit of a hassle, but I love editting this on my computer rather than my phone using the trackball touchpad combo :-|
I'm wondering why a solution wasn't even there when I was looking for answers around the web? I searched for hours too. I'm also glad I didn't brick my phone!
Yeah, I use Root Explorer a lot. I prefer the interface on eStrongs and love the LAN capabilities and Dropbox interface, but Root Explorer is much better when you need root permission.
I am having problems with some evidence of modules and the phone will not start. What we need is that the corresponding zip climb to disable Xposed from recovery since the beta 2 version lollipop Disable-xposed-recovery.zip not create the file. Of course I appreciate any help.
Desde mi Super Note N7000
When I had problems with xposed, I just reboot phone, just after the boot logo appears, I press power button several times until at every power key press the device vibrates slightly. After 3 or 4 vibrations, I only wait for the device to boot normally or sometimes I made it power off and power it on.
Radamantys-N7000 said:
I am having problems with some evidence of modules and the phone will not start. What we need is that the corresponding zip climb to disable Xposed from recovery since the beta 2 version lollipop Disable-xposed-recovery.zip not create the file. Of course I appreciate any help.
Desde mi Super Note N7000
Click to expand...
Click to collapse
franzpimp87 said:
When I had problems with xposed, I just reboot phone, just after the boot logo appears, I press power button several times until at every power key press the device vibrates slightly. After 3 or 4 vibrations, I only wait for the device to boot normally or sometimes I made it power off and power it on.
Click to expand...
Click to collapse
You can also use your Recovery's file manager. Goto /data/data/de.robv.android.xposed.installer and create a new file called "disabled" (without quotes and no extension).
If you cant create a new file, try copying the modules.list file and then paste it somewhere, rename it "disabled" (without quotes) and put back into that folder.
Then your phone will boot up w/ xposed disabled and you can then uncheck the module that isn't compatible, and delete the "disabled" file you created.
(this looks complicated but its actually very simple)
Hope that helps
USHERROB said:
You can also use your Recovery's file manager. Goto /data/data/de.robv.android.xposed.installer and create a new file called "disabled" (without quotes and no extension).
If you cant create a new file, try copying the modules.list file and then paste it somewhere, rename it "disabled" (without quotes) and put back into that folder.
Then your phone will boot up w/ xposed disabled and you can then uncheck the module that isn't compatible, and delete the "disabled" file you created.
(this looks complicated but its actually very simple)
Hope that helps
Click to expand...
Click to collapse
What is being proposed to modify or create a file, it is impossible to do it from recovery since we have a file manager with which to work, so the idea is to have a flashable zip to disable or delete Xposed modules. From already thank you very much for the input!
Desde mi Super Note N7000
It's actually far from impossible. You can simply boot into TWRP, then 'adb shell' from your computer. From there, simply 'touch /data/data/de.robv.android.xposed.installer/disabled'. Then you can reboot.
USHERROB said:
You can also use your Recovery's file manager. Goto /data/data/de.robv.android.xposed.installer and create a new file called "disabled" (without quotes and no extension).
If you cant create a new file, try copying the modules.list file and then paste it somewhere, rename it "disabled" (without quotes) and put back into that folder.
Then your phone will boot up w/ xposed disabled and you can then uncheck the module that isn't compatible, and delete the "disabled" file you created.
(this looks complicated but its actually very simple)
Hope that helps
Click to expand...
Click to collapse
Radamantys-N7000 said:
What is being proposed to modify or create a file, it is impossible to do it from recovery since we have a file manager with which to work, so the idea is to have a flashable zip to disable or delete Xposed modules. From already thank you very much for the input!
Desde mi Super Note N7000
Click to expand...
Click to collapse
If you get a zip of aroma file manager you can use recovery to flash that, you can use it to manage files on your device. It has a terminal built-in too, and a much nicer keyboard IMO.
syndre said:
If you get a zip of aroma file manager you can use recovery to flash that, you can use it to manage files on your device. It has a terminal built-in too, and a much nicer keyboard IMO.
Click to expand...
Click to collapse
Yea thats exactly what i used. I probably shouldve mentioned that, i kinda just assumed. Oops! lol. But yes you are correct Download the latest aromafm zip and place in correct directory, then change settings in twrp to use aroma file manager.
EDIT: Latest that worked for me was v2.00 b6
https://github.com/amarullz/AROMA-Filemanager/releases/tag/2.00
Xposed Alpha 3/ disable-xposed.zip not generate the file in the proper place, that file you're talking about when they say they use Aroma? Thanks
Desde mi Super Note N7000
USHERROB said:
You can also use your Recovery's file manager. Goto /data/data/de.robv.android.xposed.installer and create a new file called "disabled" (without quotes and no extension).
If you cant create a new file, try copying the modules.list file and then paste it somewhere, rename it "disabled" (without quotes) and put back into that folder.
Then your phone will boot up w/ xposed disabled and you can then uncheck the module that isn't compatible, and delete the "disabled" file you created.
(this looks complicated but its actually very simple)
Hope that helps
Click to expand...
Click to collapse
Can i just create a file "disabled" and place it somewhere else while my phone is working fine and copy it to the xposed directory when I want to disable xposed? Does this really work?
Edit : Creating this file does not disable xposed.
motorolag said:
Can i just create a file "disabled" and place it somewhere else while my phone is working fine and copy it to the xposed directory when I want to disable xposed? Does this really work?
Edit : Creating this file does not disable xposed.
Click to expand...
Click to collapse
it should work, but you have to set the correct permissions after copying to xposed data directory
Problem installing xposed
Please refer to attachment i need help.
Mine is Z1 deodexed 5.1
firdyRAY said:
Please refer to attachment i need help.
Mine is Z1 deodexed 5.1
Click to expand...
Click to collapse
Xposed doesn't work on 5.1 yet unfortunately
Hi guys, I have a quick question.
I want the newest Magisk version, to install every time I update my system, using CyanDelta. This however, requires that I manually move each update to the CyanDelta folder and edit the app setting to install the newest version with each update.
I would like to have a dummy zip, with an installer-script, that will use wild cards, to flash the newest magisk-**.zip
Something like
install("/sdcard/MagiskManager/Magisk-v****.zip")
Essentially, CyanDelta will "flash" this dummy zip. This dummy zip will then call the newest Magisk zip, to install.
Is this possible? Has anyone already done this? If so, mind linking me to the zip file already made (or the code already typed out)?
Alternatively, any tasker task to easily rename and move the latest update, automatically, once the new update is downloaded?
mkhcb said:
Hi guys, I have a quick question.
I want the newest Magisk version, to install every time I update my system, using CyanDelta. This however, requires that I manually move each update to the CyanDelta folder and edit the app setting to install the newest version with each update.
I would like to have a dummy zip, with an installer-script, that will use wild cards, to flash the newest magisk-**.zip
Something like
install("/sdcard/MagiskManager/Magisk-v****.zip")
Essentially, CyanDelta will "flash" this dummy zip. This dummy zip will then call the newest Magisk zip, to install.
Is this possible? Has anyone already done this? If so, mind linking me to the zip file already made (or the code already typed out)?
Alternatively, any tasker task to easily rename and move the latest update, automatically, once the new update is downloaded?
Click to expand...
Click to collapse
I dunno if a zip can call another zip...
However with Tasker... You can use RUN SHELL with a 'su -c' in front of the command to rename and move your magisk zip to your flashaftetupdate directory...
Then just call on it with your recovery
Sent from my Nexus 6 using Tapatalk
Hello,
I'm trying to create my own Magisk module based on working modules and referencing the module instructions. Before getting too far, I wanted to make sure that the compression process worked correctly.
So, I downloaded a .zip module from the Magisk app (e.g. Wifi5ghzdisabler), moved .zip to my Ubuntu 20.04 PC using Google Drive, extracted the .zip (using Extract Here in Files context menu), compressed the module folder back to a .zip file (using Compress... in Files context menu) and then moved the new .zip back to the phone using Google Drive. No changes to any files were made. Then, I tried to install it from storage in the Magisk app (v23.0) on a OnePlus Nord N100 running Android 10, but I encountered the following error.
Installation Failed!
- Copying zip to temp directory
! Unzip error
Is this a compression issue or a permissions issue on the phone? I'm probably missing something simple. Thanks in advance.
DanHoliday said:
Hello,
I'm trying to create my own Magisk module based on working modules and referencing the module instructions. Before getting too far, I wanted to make sure that the compression process worked correctly.
So, I downloaded a .zip module from the Magisk app (e.g. Wifi5ghzdisabler), moved .zip to my Ubuntu 20.04 PC using Google Drive, extracted the .zip (using Extract Here in Files context menu), compressed the module folder back to a .zip file (using Compress... in Files context menu) and then moved the new .zip back to the phone using Google Drive. No changes to any files were made. Then, I tried to install it from storage in the Magisk app (v23.0) on a OnePlus Nord N100 running Android 10, but I encountered the following error.
Installation Failed!
- Copying zip to temp directory
! Unzip error
Is this a compression issue or a permissions issue on the phone? I'm probably missing something simple. Thanks in advance.
Click to expand...
Click to collapse
You should upload your zip.
Thanks for the reply.
I've attached the original WiFi5GhzDisabler-v1(1).zip module downloaded from inside the Magisk app.
I've also attached WiFi5GhzDisabler-v1(1)-re-compressed.zip after downloading, extracting and re-compressing the original module it as described in my first post. I didn't make any changes to the files/folders themselves. I did notice they are different sizes (6.1KB original versus 8.6KB re-compressed).
I'm trying to learn more about the correct compression process/tool for these modules. I searched the forum and found a thread with a similar issue. Basically, the OP shared a .zip file that didn't work and another member did something and uploaded a "fixed" version with minimal insight into how it was done.
[HELP] This zip is not a Magisk Module
I would assume there isn't anything wrong with the files in the original module since it was probably reviewed before it was hosted in the Magisk app. It is also strange that the .zip file downloaded from the github repos for various modules don't work for me either, but that may be a separate issue.
Any ideas? The instructions do not include how to compress the module.
Take a close look at the original zip again, and compare it to the one you recompressed. You've put all the files in a directory inside the zip, in comparison to putting them directly in the root of the zip...
There's your problem.
Didgeridoohan said:
You've put all the files in a directory inside the zip, in comparison to putting them directly in the root of the zip...
There's your problem.
Click to expand...
Click to collapse
You're exactly right. I was incorrectly zipping the module folder itself rather than the files inside the folder. As you correctly pointed out, this creates a folder inside the zip that adds an extra layer between the files and the root of the zip.
Wow, what a simple mistake. With your help, the recompressed module installs fine now. I was able to install my own module too!
Thank you so much for your help. My issue has been resolved.
Hello, I'm trying to root a Android TV, following this post as a guide, however whenever I get to Magisk and try and patch the image, it fails with a "no application can handle this operation" error whenever I try and open the image file, I assume this is due to the lack of Files app on the device. I tried installing the files app from an apk, however that immediately crashes on the device.
Did you try other file managers like fx file explorer? Also you need not patch boot.img or recovery.img on the device you want to root. You can just transfer it to your phone, patch it and copy it back.