Related
Can anyone help me.
Having problems with the OTA update from 4.4 to 4.4.2
I'm running Stock OS rooted with TWRP, BusyBox 1.2.1.1 & SuperSU 1.80
When I run the update TWRP gives the following error in the log:
Code:
I:Switching packages (TWRP)
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'
Installing '/cache/4f6d2fc7377dbb48caecaa658bb139da2b063b33.signed-occam-KOT49H-from-KRT16S.4f6d2fc7.zip'...
Checking for MD5 file...
I:Cannot find file /cache/4f6d2fc7377dbb48caecaa658bb139da2b063b33.signed-occam-KOT49H-from-KRT16S.4f6d2fc7.zip.md5
Skipping MD5 check: no MD5 file found.
I:Zip does not contain SELinux file_contexts file in its root.
Verifying current system...
file "/system/bin/app_process" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "/system/bin/app_process" has unexpected contents.
"/system/bin/app_process" has unexpected contents.
E:Error executing updater binary in zip '/cache/4f6d2fc7377dbb48caecaa658bb139da2b063b33.signed-occam-KOT49H-from-KRT16S.4f6d2fc7.zip'
Error flashing zip '/cache/4f6d2fc7377dbb48caecaa658bb139da2b063b33.signed-occam-KOT49H-from-KRT16S.4f6d2fc7.zip'
Updating partition details...
I:Data backup size is 2457MB, size: 13231MB, used: 8064MB, free: 5299MB, in data/media: 5606MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'main2'
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
Think it's something to do with BusyBox and how it installs, is it fixable without a total wipe?
Had the same issue with the OTA upgrade to 4.4 (had to do a total wipe and lost a lot of files on the virtual SDcard as a result).
Not sure if it is busybox causing your issue or not. What the error means is that something in your system is not as it should be. Did you remove or modify any system apps?
You can have root and a custom recovery, but you must be TOTALLY stock in order for the OTA to work.
*slap my head and call me stupid*
Just remembered I installed the exposed framework.
That's what's causing the problem. Uninstalled and the ota ran fine.
s0litaire said:
*slap my head and call me stupid*
Just remembered I installed the exposed framework.
That's what's causing the problem. Uninstalled and the ota ran fine.
Click to expand...
Click to collapse
Yep, I did the same thing. It's even worse when you notice it clearly says "app_process" in the Xposed installer.
korockinout13 said:
Yep, I did the same thing. It's even worse when you notice it clearly says "app_process" in the Xposed installer.
Click to expand...
Click to collapse
same here i still cant update altough i do factory reset and get this message
"/system/bin/app_process" has unexpected contents.
E:Error in tmp/update.zip
(Status 7)
Instalation Aborted
what should i do?
ditrix99 said:
same here i still cant update altough i do factory reset and get this message
"/system/bin/app_process" has unexpected contents.
E:Error in tmp/update.zip
(Status 7)
Instalation Aborted
what should i do?
Click to expand...
Click to collapse
Did you read this thread? It clearly explains in several posts above. You need to uninstall Xposed framework.
Same problem but a little different
korockinout13 said:
Did you read this thread? It clearly explains in several posts above. You need to uninstall Xposed framework.
Click to expand...
Click to collapse
So I am trying to upgrade to 4.4.3 and having the same issue however i cannot uninstall Xposed. The xposed uninstaller does not find process_app.orig to uninstall/resotre the original file. Where can I get this original file. Any suggestion on what to do next?
buysellonline said:
So I am trying to upgrade to 4.4.3 and having the same issue however i cannot uninstall Xposed. The xposed uninstaller does not find process_app.orig to uninstall/resotre the original file. Where can I get this original file. Any suggestion on what to do next?
Click to expand...
Click to collapse
Have you installed xposed right? You have to open Xposed App and tap to "Install/Update" then "Uninstall". Remember to remove also all modules.
You should remove also ROOT files, just open SuperSU and uninstall it from SuperSU settings.
Agosh13 said:
Have you installed xposed right? You have to open Xposed App and tap to "Install/Update" then "Uninstall". Remember to remove also all modules.
You should remove also ROOT files, just open SuperSU and uninstall it from SuperSU settings.
Click to expand...
Click to collapse
- Yes, I have installed xposed correctly and have been using it for months.
- Yes, I have deleted all modules from within xposed prior to attempting to uninstall.
- Yes, I have used xposed to do the uninstall - it fails, to restore the process_app.
- Uninstalling from any other app will not restore the original process_app file.
I need to push the file to my phone manually but I do not where I can get it from and unfortunately xposed did not make a copy of it for some odd reason. So here you have it. I guess if I cannot locate the file, my only option to fastboot a full version of the 4.4.3 losing everything on the phone. I know how to do that, I hope
s0litaire said:
*slap my head and call me stupid*
Just remembered I installed the exposed framework.
That's what's causing the problem. Uninstalled and the ota ran fine.
Click to expand...
Click to collapse
I can't believe I didn't think of that... I'm glad I'm not the only one that's done this though!
buysellonline said:
- Yes, I have installed xposed correctly and have been using it for months.
- Yes, I have deleted all modules from within xposed prior to attempting to uninstall.
- Yes, I have used xposed to do the uninstall - it fails, to restore the process_app.
- Uninstalling from any other app will not restore the original process_app file.
I need to push the file to my phone manually but I do not where I can get it from and unfortunately xposed did not make a copy of it for some odd reason. So here you have it. I guess if I cannot locate the file, my only option to fastboot a full version of the 4.4.3 losing everything on the phone. I know how to do that, I hope
Click to expand...
Click to collapse
I have the same problem. There is no app_process.orig file in the /system/bin directory. Does anyone have an original 4.4.2 app_process file for the Nexus 10?
This link shows how to use the full image without losing your data. I haven't tried it myself and would have preferred to just use the OTA image instead. But I may end up having to fall back on that approach.
Hi, been trying to update OTA with no success here. No idea if it's the same issue with app_process but here's what I've done
- Device status: Custom, so installed xposed framework, installed wanam, tick Fake system status and Device status changed to Official
- Choose System Update, and it's working fine up till this point
- Install the update and update will failed since wanam is still enabled (and it deletes the update file, so next time I want to OTA I have to redownload all 600 megs again )
- Now I tried to disable wanam and uninstall xposed (because I don't think I should uninstall xposed without disabling wanam first), however whenever I disabled wanam Device status will then reverted to Custom, preventing the install even if the update has been successfully downloaded (and yes, it deletes the update file again)
So any idea how to do it correctly then? Thanks
Garock said:
Hi, been trying to update OTA with no success here. No idea if it's the same issue with app_process but here's what I've done
- Device status: Custom, so installed xposed framework, installed wanam, tick Fake system status and Device status changed to Official
- Choose System Update, and it's working fine up till this point
- Install the update and update will failed since wanam is still enabled (and it deletes the update file, so next time I want to OTA I have to redownload all 600 megs again )
- Now I tried to disable wanam and uninstall xposed (because I don't think I should uninstall xposed without disabling wanam first), however whenever I disabled wanam Device status will then reverted to Custom, preventing the install even if the update has been successfully downloaded (and yes, it deletes the update file again)
So any idea how to do it correctly then? Thanks
Click to expand...
Click to collapse
First off, next time you get the ota go into /cache and copy the zip file somewhere else so you don't have to download it again. You need to uninstall xposed from within the app
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
First off, next time you get the ota go into /cache and copy the zip file somewhere else so you don't have to download it again. You need to uninstall xposed from within the app
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yep, tried that as well. However even if I copied update.zip back to /cache/fota, software update still redownload the whole thing again
And yeah, I uninstalled xposed from the app
Question, in my previous post, after each steps (disable wanam, uninstall xposed) I always rebooted to apply the changes and device status reverted back to Custom after I disabled wanam and then reboot. Should I uninstall xposed without rebooting first?
I mean should it be like disable wanam (no reboot) then uninstall xposed (again no reboot) and straight to do software update?
Thanks for the reply though
Edit:
Okay, tried this.
Disable wanam (no reboot) so Device status still at Official. Then uninstall xposed (no reboot), app_process has also reverted to original. Last temporary disable root using Voodoo OTA Rootkeeper. But still software update failed
Any idea what other things causing software update refuse to updating?
I did however modify /system/csc/feature.xml, does it matter?
s0litaire said:
*slap my head and call me stupid*
Just remembered I installed the exposed framework.
That's what's causing the problem. Uninstalled and the ota ran fine.
Click to expand...
Click to collapse
Thanks
OK, so I've got 5.0 on my N10, and I'm rooted. Two problems I'm having regarding F-Droid and AdAway:
- After installing F-Droid, no applications display in the F-Droid "Available" list.
- Since I couldn't install AdAway through F-Droid, I installed the apk, and get this error trying to enable blocking: " Not enough space on partition! Try changing the target hosts file in preferences to /data/data/hosts". I changed the host file location as indicated, then when I tried again I got a "Symlink missing" error: "Symlink from your target to /system/etc/hosts is not existing or incorrect! AdAway will not work if it is not pointing to the right file"
So- I'm guessing both of these apps will need updates to be useful with 5.0? Anyone have an AdAway success story?
P.S. One bit of good news: Muzei now works on my N10. I could never get it to work on KitKat.
dberthia said:
OK, so I've got 5.0 on my N10, and I'm rooted. Two problems I'm having regarding F-Droid and AdAway:
- After installing F-Droid, no applications display in the F-Droid "Available" list.
- Since I couldn't install AdAway through F-Droid, I installed the apk, and get this error trying to enable blocking: " Not enough space on partition! Try changing the target hosts file in preferences to /data/data/hosts". I changed the host file location as indicated, then when I tried again I got a "Symlink missing" error: "Symlink from your target to /system/etc/hosts is not existing or incorrect! AdAway will not work if it is not pointing to the right file"
So- I'm guessing both of these apps will need updates to be useful with 5.0? Anyone have an AdAway success story?
P.S. One bit of good news: Muzei now works on my N10. I could never get it to work on KitKat.
Click to expand...
Click to collapse
Same here. Really sucks ��
---------- Post added at 07:51 AM ---------- Previous post was at 07:22 AM ----------
Ok it seems I've fixed by deleting an app under /system/app. I chose an unused keyboard and then re installed adaway and busybox. Then it worked
There's indeed critically low free space. Can't even install busybox after rooting: http://forum.xda-developers.com/nexus-10/help/5-0-lack-free-space-install-busybox-t2939729
The trick with deleting apps from /system/app works obviously, until you decide to accept new OTA.
Yeah I know. I will crosss that bridge when I get there
Just couldn't live without adaway.
For the time being, I'm solving it by CWM tar+gzip backup of stock (deleting data.* from backup folder (to save the space)) and deleting some of the apps (like Korean keyboard etc.). When OTA comes, I'll restore the /system partition and proceed with update.
I'd like to know a better solution though... If there is any.
Are there any partition resizers available for Android? Or would it require an Fdisk delete and create?
Sent from my SCH-I545 using Tapatalk
There is an easy workaroud read help. You go to setting, change path to host to data then when downloading filters it will propose a symlink. You'done
Missing Adaway on new nexus 6: unlocked-rooted-and willing
Khaon said:
There is an easy workaroud read help. You go to setting, change path to host to data then when downloading filters it will propose a symlink. You'done
Click to expand...
Click to collapse
Mr. Khaon, happy Friday - I found this thread from a google search after i downloaded F-Droid and it was shooting blanks - nothing.
Would you mind provided some additional detail on the "easy workaround" you mentioned? i.e. what "help" should I read, which settings do you change the path, etc.
Thanks.
JMacD said:
Mr. Khaon, happy Friday - I found this thread from a google search after i downloaded F-Droid and it was shooting blanks - nothing.
Would you mind provided some additional detail on the "easy workaround" you mentioned? i.e. what "help" should I read, which settings do you change the path, etc.
Thanks.
Click to expand...
Click to collapse
just go to the settings and under hosts file you check for host files target path and you select another one where you can write( /data for example)
This must be on here somewhere but I can't find any answers. I added a second user to my 6P and I'd like to get GB and a few other modules running. Xposed is installed correctly and I have granted multi-user access to SuperSU on the parent/admin user. When I attempt to install an Xposed module it fails. Can anyone tell me what I'm missing? Thanks a lot.
Let me ask a question this way.. Apparently I need to "install" SuperSU on both users. It says to "install SuperSU in the /system folder".
I already have SuperSU installed and running on the primary user acct but I see nothing of interest in the /system folder that looks like it could be copied over for example.
Does anyone know how to install SuoerSU into the /system folder?
hello im getting the following message everytime i try and download the lists "copying of host file failed! please read help for more information"
ive just updated to the android 7.0 through the developer program, twrp custom recovery installed with root access build number NRD90M
just wondering what could be causing this and if i can do anything to try and fix it thanks
Is your /system set to read only, or read/write? If read only, adaway will not be able to update /system/etc/hosts
dratsablive said:
Is your /system set to read only, or read/write? If read only, adaway will not be able to update /system/etc/hosts
Click to expand...
Click to collapse
i have it set to read write im gonna try to flash the systemless hosts right now ill update how it goes
flashing the AdAway_systemless_hosts_v2.zip in the recovery, then unistalling and reinstalling the app seems to have worked
you can also use Magisk now to enable complete systemless root and then the hosts file /system/etc will be forwarded to the systemless version
I didn't even install Adaway, I just downloaded a host file and replaced it in /etc/
Works good enough for me and one less app running...
kennehh said:
hello im getting the following message everytime i try and download the lists "copying of host file failed! please read help for more information"
ive just updated to the android 7.0 through the developer program, twrp custom recovery installed with root access build number NRD90M
just wondering what could be causing this and if i can do anything to try and fix it thanks
Click to expand...
Click to collapse
In the exact same boat. Frustrating. Tried Adfree, to no avail. Adaway, to no avail. Tried the adaway bind zip file, making hosts writable, and even System to writable. Nothing.
treoo0_1 said:
In the exact same boat. Frustrating. Tried Adfree, to no avail. Adaway, to no avail. Tried the adaway bind zip file, making hosts writable, and even System to writable. Nothing.
Click to expand...
Click to collapse
i have fixed this by converting adaway from user apps to system apps using Link2SD, reboot and adaway working properly again
Very old thread, but I've had exactly the same problem installing AdAway on the last 3 or 4 phones -- all but one running Nougat 7.0, the other on Oreo 8.1. This was when trying to install AdAway versions 3.1 and 3.3.something.
I finally got it to write hosts file updates using one of the following, not sure which was the key:
-- Installed version 3.2 which had been running problem-free on an old phone for years. The biggest difference is this older phone is running Resurrection Remix 5.8.3 (Nougat 7.1.2).
-- Before trying to update the hosts file on this fresh install, I went straight to AdAway preferences and set "Check for updates daily", "Enable webserver", and "Start webserver on boot". After making those settings I tapped Download Files and Apply Ad Blocking, and it successfully wrote to the hosts file.
Again I don't know which was the fix. It seems weird that version 3.2 would work when a version just before and after it didn't work for me. But of course it is possible that the version is the difference. It seems even more weird that those 3 little preference settings make any difference at all . . . unless it's just the act of writing changes to the AdAway app itself.
Before installing 3.2, using Root Explorer I checked permissions on the working phone and one non-working phone, for the systems and etc folders, and for the hosts file itself. (In all cases AdAway is/was set to use /systems/etc/hosts.) I also checked Android permissions in the Apps list. All permissions were exactly the same on both phones: 0755 for system, 0755 for etc, and 0644 for hosts. No permissions assigned via Android.
Hoping this bump will also get fresh attention from somebody who might know the details of a real answer.
@Moondroid
Why the hell you trying to make some really old ass version of it work instead of installing the newest version? Lol
I've been using 4.2.7 and though its kind of weird on a fresh install I need to update and apply the hosts twice before searching for newer hosts comes back its up to date. But at least it works.
Hello, I'm on the latest 6.0.1 stock. I've used Nexus Root Toolkit to unlock my bootloader, root (SuperSU), and flash TWRP. I flashed Xposed using the Xposed installer. Now I'm looking to get AdAway up and running. I've done some searching and I see some conflicting reports about whether this needs to be done systemless, and how to get it working. Stuff I've heard is:
1. Just install the apk from XDA and install normally, update hosts, and you're good.
2. Install apk, use a program (like Titanium Backup) to make it a system app, update hosts, done.
3. Install apk, flash some sort of AdAway package in TWRP, update hosts, done.
4. Install apk, do some adb process to create a symlink of some sort, update hosts, done.
5. I haven't heard anyone really mention it, but in Preferences I see an option to "Enable systemless mode" which I haven't seen anyone really mention.
Can someone tell me which way I need to use, please?
>>> I also saw someone say that I need to use a file explorer after updating hosts to manually switch the permissions of the hosts file, in order to improve performance. Can anyone tell me if this is accurate, and if so how to do it?
Thanks!
kwest12 said:
Hello, I'm on the latest 6.0.1 stock. I've used Nexus Root Toolkit to unlock my bootloader, root (SuperSU), and flash TWRP. I flashed Xposed using the Xposed installer. Now I'm looking to get AdAway up and running. I've done some searching and I see some conflicting reports about whether this needs to be done systemless, and how to get it working. Stuff I've heard is:
1. Just install the apk from XDA and install normally, update hosts, and you're good.
2. Install apk, use a program (like Titanium Backup) to make it a system app, update hosts, done.
3. Install apk, flash some sort of AdAway package in TWRP, update hosts, done.
4. Install apk, do some adb process to create a symlink of some sort, update hosts, done.
5. I haven't heard anyone really mention it, but in Preferences I see an option to "Enable systemless mode" which I haven't seen anyone really mention.
Can someone tell me which way I need to use, please?
>>> I also saw someone say that I need to use a file explorer after updating hosts to manually switch the permissions of the hosts file, in order to improve performance. Can anyone tell me if this is accurate, and if so how to do it?
Thanks!
Click to expand...
Click to collapse
Hello... Just allow SU permission, tic "enable systemless mode" in preferences if you use systemless Root. Tap on "disable" next to the red cross and let it download the new host. When prompted, reboot. Done...
Never seen anything about setting extra permissions... I don't read the XDA thread anyway and downloaded the app from here: https://f-droid.org/repository/browse/?fdid=org.adaway
Cheers...