Related
This is the ROM i use myself, but I post it here in case other people also want a clean (almost) stock ROM with root and recovery. It works for me, but I provide no guarantee that it will work for you. That said, these ZIP files and procedures have been tested by myself and a few others and seem to work quite well.
FLASH THIS AT YOUR OWN RISK.
Requirements:
Sony Xperia Z.
Only tested on LB, but should also work on UB.
Ability to flash ZIP files via recovery.
Features:
Based on Xperia Z_10.1.1.A.1.307_Unbranded BE.ftf (file uploaded by Psicao).
Removed bloat and other apps you can download from Google Play.
Installed CWM recovery 6.0.2.8 for locked bootloaders v4.
Odexed and zipaligned.
No reboots when mounting system r/w.
Pre-rooted with Koush's Superuser App.
Busybox v1.20.2 installed.
Call recording.
18 Toggles.
36 dpi softkeys.
Changelog:
v8
Added 18 Toggles.
Switched to 36 dpi softkeys.
v7
Added WeatherWidget back due to popular demand.
More robust and less intrusive way to ensure that mounting system r/w doesn't cause a reboot.
v6
Based on 10.1.1.A.1.307
Removed 18 Toggles since it is not compatible with 1.307 yet.
Delete the ric daemon early in the boot process.
v5
Added 18 Toggles.
Applied a few WiFi tweaks to get a (hopefully) more stable WiFi connection.
v4
Removed duplicate notification sound 'vega' (bug in original ROM).
Increased volume a bit.
v3
Created all symlinks found in the original FTF file.
Changed all file and directory permissions to match those in the original FTF file.
Added a more robust script to stop ric.
v2
Fixed reboot issue when mounting system r/w.
Added Notes and NoteWidget back.
Reodexed and zipaligned.
v1
Initial release.
Installation:
Enter recovery.
Flash C6603_10.1.1.A.1.307_DEBLOAT.zip.
Clear user data OPTIONAL STEP - SEE BELOW.
Reboot.
Reboot again once NFC firmware has been upgraded (only needed if upgrading from 1.434 or earlier).
Note regarding unlocked bootloaders: This ROM is designed for LB. If using this on UB flash the following ZIP after installation to remove the CWM recovery for LB: C6603_10.1.1.A.1.307_UBPATCH.zip
Clear data?
If NFC is not working and you're upgrading from a 1.434 ROM, I recommend that you clear your userdata by flashing C6603_10.1.1.A.1.307_ClearData.zip.
You do NOT need to clear user data if you are already running a ROM based on 1.253 or 1.307 and everything is working fine.
MD5 hashes:
2f8fe013da90987447a04c0e5f405998 (C6603_10.1.1.A.1.253_DEBLOAT.zip)
3bba6ffb3cd9bdf7535c5e4b722223d5 (C6603_10.1.1.A.1.253_ClearData.zip)
b889d474290d9b924acbf011277d58e3 (C6603_10.1.1.A.1.307_UBPATCH.zip)
Upgrade kernel and baseband:
Once the ROM is working you might want to flash kernel and baseband from the original FTF via Flashtool in order to get the full 1.307 experience.
Preventing reboots when mounting /system read-write
This ROM uses my own little utility called RICHunter to prevent reboots when mounting /system read-write. If you want to use it yourself in your own ROM you can download it here:
0c766dc58cc909693f5d669264d78f4a (richunter.zip)
Included in the ZIP file is a README.txt that explains how to use it, but you can also read it here:
RICHunter by Carceri @ XDA
1. What is this?
On the Xperia Z Sony have added a small program called ric which
monitors mount options on filesystems and reboots the system if
they deviate from their default values. This causes the system
to reboot e.g. when the /system partition is mounted read-write.
In short, this programs stops this daemon and replaces it with a
dummy version that doesn't do anything, thereby disabling ric.
2. How do I use it?
Just put the file richunter somewhere on your system, for example
/system/bin/richunter, make it executable (chmod 755) and run it
as the root user. This needs to be done every time the system is
restarted.
This can be achieved by putting the following lines in a file
called /system/etc/install-recovery.sh:
#!/system/bin/sh
exec /system/bin/richunter
Another way is to make a wrapper to /system/bin/ctrlaltdel and
call richunter from there:
#!/system/bin/sh
exec /system/bin/richunter
exec /system/bin/toolbox ctrlaltdel "${1}" "${2}" "${3}" "${4}"
Choose either one, or a 3rd solution to automatically run it.
Remember to make the files executable.
3. How does it work?
On the latest kernel, the ric daemon is restarted whenever it
is killed. Therefore the following steps are taken by this
program to stop it without giving it time to reboot the system:
1) The programs runs as a daemon waiting for up to 60 seconds
for ric to start.
2) It detects which CPU ric was last scheduled on, and forces
ric to always run on that CPU in the future.
3) It forces itself to run on the same CPU as ric and sets its
scheduling priority to real-time. This prevents anything
in that CPU from running, including ric.
4) It mounts the rootfs read-write and replaces ric with a
dummy version that just sleeps forever. Finally it kills
the ric process and remounts rootfs read-only.
5) The daemon now exits. When ric is restarted the dummy
version is started instead.
4. What about unlocked bootloaders and custom kernels?
On custom kernels ric has either been removed or not installed
at all. Therefore this is only needed on locked bootloaders.
5. Can I use it in my own ROM?
Sure. Use it as you want.
6. How do I compile it?
You need to have the Android NDK installed. Then set the
correct paths in the included Makefile and run:
1) make prep
2) make
That's it. When you want to recompile you can skip step 1).
7. What license is this released under?
It is UNLICENSED software. See http://unlicense.org/
Hi, i have not tested this exact zip, but the rom i am using now is based on a previous version you posted in another thread.
There is a little issue with your "debloating", you removed "Notes" app, so when you go to "small apps" drawer and choose notes or voice recording, an error pops out, so you have to remove the icons and forget about stock notes or voice recording as they are apps not available on the market to download separately.
As i said, this happens on the first zip you uploaded, i don't know if this was already solved on newer versions.
If NFC is not working, there is still hope to keep user data intact, just delete /data/usf on your phone, take usf folder from your userdata.tar, and put it in your phone in the same place where the older was with same permissions. This step could also be added to the main flash script, no user data is lost and i think all NFC related problems would be gone
Thanks for sharing your work.
RoberM said:
There is a little issue with your "debloating", you removed "Notes" app, so when you go to "small apps" drawer and choose notes or voice recording, an error pops out, so you have to remove the icons and forget about stock notes or voice recording as they are apps not available on the market to download separately.
Click to expand...
Click to collapse
I have added the Notes app back in this zip.
RoberM said:
If NFC is not working, there is still hope to keep user data intact, just delete /data/usf on your phone, take usf folder from your userdata.tar, and put it in your phone in the same place where the older was with same permissions.
Click to expand...
Click to collapse
That was actually the first thing I tried and it didn't work for me. It might work for some and if someone is interested I'll be happy to provide a zip file that just restores this directory and keeps everything else under /data intact.
How do you enable call recording btw? Thanks.
Sent from my C6603
The link is down!! :crying:
mandarjoshiin said:
The link is down!! :crying:
Click to expand...
Click to collapse
Link is back up. I were just in the process if uploading v2
vibranze said:
How do you enable call recording btw? Thanks.
Click to expand...
Click to collapse
Press the menu button during a call.
Carceri said:
This is the ROM i use myself, but I posted this in case other people also want a clean (almost) stock ROM with root and recovery. It works for me, but I provide no guarantee that it will work for you, so FLASH THIS AT YOUR OWN RISK.
Requirements:
- Sony Xperia Z with locked bootloader.
- Ability to flash ZIP files via recovery.
Features:
Based on the first version of the ZIP posted by wawyed on this thread.
...which was based on C6603_Unbranded_10.1.1.A.1.253.ftf (original file uploaded by prakka).
Removed bloat and other apps you can download from Google Play.
Installed CWM recovery 6.0.2.8 for locked bootloaders v4.
Odexed and zipaligned
Pre-rooted with Koush's Superuser App.
Busybox v1.20.2 installed.
Enabled call recording.
Changelog:
v2
Fixed reboot issue when mounting system r/w.
Added Notes and NoteWidget back.
Reodexed and zipaligned.
v1
Initial release.
Installation:
Enter recovery.
Flash C6603_10.1.1.A.1.253_DEBLOAT.zip.
Clear user data OPTIONAL STEP - SEE BELOW.
Reboot.
Say not to "Disable recovery flash" if asked.
Possibly reboot a second time once NFC firmware has been upgraded.
I had problems with NFC not working if I didn't clear user data the first time I upgraded from a version < 1.253. In order to clear user data follow this step:
Flash C6603_10.1.1.A.1.253_ClearData.zip.
These ZIP files and procedures have been tested by myself and a few others and seem to work. However, some people have also experienced issues, but since I don't know their exact setup it is impossible for me to pinpoint the source of these errors. FLASH THIS AT YOUR OWN RISK.
Upgrade kernel and baseband:
Once the ROM is working you might want to flash kernel, fotakernel and baseband from the original FTF via Flashtool in order to get the full 1.253 experience.
Click to expand...
Click to collapse
hello I used your guide and everything works to perfection thanks:laugh:, I invite other people to use this guide to those who want to update your phone with the root installed.:good:
ps. sorry if I use a translator.
ciao ho usato la tua guida e funziona tutto alla perfezzione grazie, invito altri utenti ad usare questa guida per chi vuole aggiornare il telefono con il root installato.
Great, this is the first one deodexed and zipaligned, i am sure a lot of people will be interested.
EDIT: Ok, i didn't read well, it says Re-Odexed
Sorry, i'm a little confused, is this rom odexed or deodexed?
Sent from my C6603 using Tapatalk 2
secondkai said:
Sorry, i'm a little confused, is this rom odexed or deodexed?
Click to expand...
Click to collapse
In changes for version 2 reodexed is written. Attentively read an original post.
Carceri said:
Press the menu button during a call.
Click to expand...
Click to collapse
Thanks, but what I meant was how to incorporate call recording into the ROM, is it something that can be done easily, e.g. editing build.prop, etc or any other method?
Cheers.
Update: I got the answer. Thanks.
picasa album sync is missing in google accounts and album view, is this due to bloat removal ?
jimsey said:
picasa album sync is missing in google accounts and album view, is this due to bloat removal ?
Click to expand...
Click to collapse
I don't think so. Is that feature available on a normal Xperia Z stock ROM?
I think that the original Gallery app installs the required sync adapter. Also if you have Google+ installed it is replaced by Photo Sync.
hello Carceri would like to upgrade to v4 there some procedure to be performed?
fabbiotto said:
hello Carceri would like to upgrade to v4 there some procedure to be performed?
Click to expand...
Click to collapse
If you have installed this ROM before you just need to flash the new ZIP file to get the latest version.
Carceri said:
If you have installed this ROM before you just need to flash the new ZIP file to get the latest version.
Click to expand...
Click to collapse
s now the v2 if I install the v4 just that I do not clear user data to not lose my data?
fabbiotto said:
s now the v2 if I install the v4 just that I do not clear user data to not lose my data?
Click to expand...
Click to collapse
Just flash the new ROM. No need to clear data.
Carceri said:
Just flash the new ROM. No need to clear data.
Click to expand...
Click to collapse
thank you very much:good:
hello v4 does not work well with the DoCoMo Status Bar and the Task Switcher sony disappears, you can take a look please?
by the time I come back to v2
I have successfully created my own bypass to get viper4android to work. Always create a full backup before attempting =)
1. Download viper4android APK
2. Download Root Explorer from the playstore
3. Install Both Apps
4. Launch Root Explorer
5. In root explorer go to /system/lib/soundfx and copy the folder to /data/ (make a soundfx folder)
6. Also copy /system/etc/audio_effects.conf to the /data/soundfx/ folder
7. Using root explorers menu you can create a shortcut (symbolic link) make a shortcut of the /data/soundfx/ folder and a shortcut of the /data/soundfx/audio_effects.conf
8. Boot into TWRP
9.Mount the system partition
10. Rename /system/lib/soundfx to /system/lib/soundfx2
11. Copy soundfx shortcut create earlier to /system/lib/ it will look like a "file" to TWRP
12.Rename the /system/etc/audio_effects.conf to /system/etc/audio_effects.conf1
13. Copy the audio_effects shortcut into /system/etc/ (be sure its name matches the old exactly)
15. Reboot
16. Launch Viper and install driver
I haven't dealt with LPA yet (hasn't had an issue) nor have I done any other modifications at this time which are avail on the viper4android thread.
I was just thinking about symbolic links to get around this S-OFF/ON issue and it appears they work and technically as a workaround we could symbolically link everything in system to another location and access it all. This could easily be put into ROM builds now at least as well!
Build.Prop may be useful to move out via sym link as well
It's not a matter of being s-on or s-off.. It's a matter of having write protection removed then you can do all of that. S-off just allows you to flash any partition on the device.. (radio, hboot etc..) plus you can flash any ruu you want as long as you change to supercid
There is a kernel module in dev and it's working great on my device.
On M7 it seems to me that the S-OFF also disables write protection system on stock rom
Envoyé de mon HTC Butterfly s en utilisant Tapatalk
migascalp said:
On M7 it seems to me that the S-OFF also disables write protection system on stock rom
Envoyé de mon HTC Butterfly s en utilisant Tapatalk
Click to expand...
Click to collapse
But you don't need s-off to disable write protection. You just need a kernel with it disabled or the kernel module which flair posted in the development section. I'm using it and am able to write to the system fine and I'm s-on. The title of the thread should be something like "with write protection on" not s-on.
I just wanted to clarify that with S-OFF this module is useless
migascalp said:
I just wanted to clarify that with S-OFF this module is useless
Click to expand...
Click to collapse
You don't need to clarify that to me. I'm very well aware of that. My point was that for this topic you don't need s-off for this to work.. You just need write protection off. Whether that be with with s-off or with a module.. This working is not dependant on s-off.. It's dependant on write protection being off. That is my point.
Sent from my HTC One using Tapatalk
For anyone who wants the stock kernel with write protection off just use this JMZM8 Kernel and then just install busybox like regular and boom Viper4Android, literally made my M8 sound so much better (not that it wasn't already awesome)
worked with htc 816 running indian stock, which still has no s-off at the moment,
had to go to twrp recovery terminal command, to make the symbolic links or move directories....
viper4android made a lot of difference in this particular model.
the next thing would be to make viper4a a system app, since it tended to close and thus lower the volume, usually after some time.
helloicanseeu said:
worked with htc 816 running indian stock, which still has no s-off at the moment,
had to go to twrp recovery terminal command, to make the symbolic links or move directories....
viper4android made a lot of difference in this particular model.
the next thing would be to make viper4a a system app, since it tended to close and thus lower the volume, usually after some time.
Click to expand...
Click to collapse
you can try and copy the app or push it in recovery to System/app. if you put it manually in not push via adb be sure to set the right permissions if the recovery doesn't set them automatically ! it should work even without s-off
One-M8-Master said:
you can try and copy the app or push it in recovery to System/app. if you put it manually in not push via adb be sure to set the right permissions if the recovery doesn't set them automatically ! it should work even without s-off
Click to expand...
Click to collapse
will try to make it work .... meanwhile from what i gathered in a htc 816 facebook group, most indian pple buying this particular model seems to have no clue about making the most out of its audio properties ... the 816's true selling points were its larger 5.5 " size, great audio output, and relatively low cost compared with other htc flagship models.
One-M8-Master said:
you can try and copy the app or push it in recovery to System/app. if you put it manually in not push via adb be sure to set the right permissions if the recovery doesn't set them automatically ! it should work even without s-off
Click to expand...
Click to collapse
done ... went to twrp recovery,
moved "com.vipercn.viper4android_v2-1.apk" from ""/data/app" to "/system/priv-app"
moved "com.vipercn.viper4anddroid_v2-1/libV4AJniUtils.so" from to "/data/app-lib" to "/system/lib/"
should be working fine, havent extensively tested it out yet though,
reported as a system app, and viper driver is running.
I Can't Get data/soundfx Shortcut to Transfer to /System/lib
In the opening instructions, #11 says that we have to transfer the data/soundfx shortcut to /system/lib. Everytime I try it with TWRP it just says failed. If I try it with root browser,
it will say successful until the phone is rebooted. Any help would be appreciated. I am a newbie to these things.
BaltColts said:
In the opening instructions, #11 says that we have to transfer the data/soundfx shortcut to /system/lib. Everytime I try it with TWRP it just says failed. If I try it with root browser,
it will say successful until the phone is rebooted. Any help would be appreciated. I am a newbie to these things.
Click to expand...
Click to collapse
u need to install twrp recovery for htc 816.
get it from "TeamWin Projects" website.
after successfully installing twrp, boot into recovery mode, use twrp to move data/soundfx shortcut to /system/lib, etc...
hope u get to install viperfx successfully and make full blast of the great audio output of this big value music machine, makes a near perfect combo with my music angel cube speakers(as far as mine human ears tell me), anyone using this combo too?
later htc models based on mediatek chipsets seem to have horrible audio outputs ... maybe even iphone 6 and samsung note4 cant beat htc 816 where mp3 output is concerned
background: htc 816 doesnt has s-off, so its always s-on, which means if u try to write to the "/system" folder, the phone will trigger a reboot immediately, to prevent any modifications to the folder. root browser will not be able to write to /system folder, even if the phone has root access, due to this s-on protection. The only way to edit /system folder is to boot to twrp (in recovery mode).
blewis540 said:
I have successfully created my own bypass to get viper4android to work. Always create a full backup before attempting =)
1. Download viper4android APK
2. Download Root Explorer from the playstore
3. Install Both Apps
4. Launch Root Explorer
5. In root explorer go to /system/lib/soundfx and copy the folder to /data/ (make a soundfx folder)
6. Also copy /system/etc/audio_effects.conf to the /data/soundfx/ folder
7. Using root explorers menu you can create a shortcut (symbolic link) make a shortcut of the /data/soundfx/ folder and a shortcut of the /data/soundfx/audio_effects.conf
8. Boot into TWRP
9.Mount the system partition
10. Rename /system/lib/soundfx to /system/lib/soundfx2
11. Copy soundfx shortcut create earlier to /system/lib/ it will look like a "file" to TWRP
12.Rename the /system/etc/audio_effects.conf to /system/etc/audio_effects.conf1
13. Copy the audio_effects shortcut into /system/etc/ (be sure its name matches the old exactly)
15. Reboot
16. Launch Viper and install driver
I haven't dealt with LPA yet (hasn't had an issue) nor have I done any other modifications at this time which are avail on the viper4android thread.
I was just thinking about symbolic links to get around this S-OFF/ON issue and it appears they work and technically as a workaround we could symbolically link everything in system to another location and access it all. This could easily be put into ROM builds now at least as well!
Build.Prop may be useful to move out via sym link as well
Click to expand...
Click to collapse
Will this method work without busybox?
There is a very specific reason why I'd not like to use busybox, so this may end up being a very good solution for me.
fade2black101 said:
Will this method work without busybox?
There is a very specific reason why I'd not like to use busybox, so this may end up being a very good solution for me.
Click to expand...
Click to collapse
What's wrong with busybox? its a hidden process only used when an app like V4A calls for it, other then that it has no negative effect. why avoid it?
Besides this thread is disinfo, all this is not required to get V4A working, Go to this thread Here and follow instructions.
hi,
I have completed those steps, but the viper4android keeps asking me to install the driver.
I have tried also the steps from helloicanseeu. But still, not working.
please help me, because installing viper4android is never been this hard on my previous device. thank you.
i got stuck after flashing viper . stuck on htc logo then reboots back to recovery..
oulixeus said:
hi,
I have completed those steps, but the viper4android keeps asking me to install the driver.
I have tried also the steps from helloicanseeu. But still, not working.
please help me, because installing viper4android is never been this hard on my previous device. thank you.
Click to expand...
Click to collapse
Which phone u using? What stock rom? I was using stock indian on htc816.
---------- Post added at 09:12 PM ---------- Previous post was at 09:03 PM ----------
XskipperX said:
i got stuck after flashing viper . stuck on htc logo then reboots back to recovery..
Click to expand...
Click to collapse
U followed the steps by blewis?
Why it is so complicated..???.if s-on, unlock bootloader and flash a custom kernel (elementalx). In install options just choose to set SElinux permissive. Then, install driver for Viper and reboot. That is it. If s-off, start with kernel installation...
People are talking about that s-off gives full access to system partition - true but not correct. Unlocked bootloader gives write access to system folder, while s-off in addition allows to change partitions, bootloader, etc.
Sent from my HTC One M8 using XDA Free mobile app
uvt_novice said:
Why it is so complicated..???.if s-on, unlock bootloader and flash a custom kernel (elementalx). In install options just choose to set SElinux permissive. Then, install driver for Viper and reboot. That is it. If s-off, start with kernel installation...
People are talking about that s-off gives full access to system partition - true but not correct. Unlocked bootloader gives write access to system folder, while s-off in addition allows to change partitions, bootloader, etc.
Sent from my HTC One M8 using XDA Free mobile app
Click to expand...
Click to collapse
Welp, it's so complicated because NONE of the instructions seem to work for a huge number of us. I've tried like 5 "failsafe" methods but they just fail and fail.
ONE time I had it working and was all psyched, and then I restarted the phone at some point and that was the end of that. Never worked since.
Hi Xperian , here Deodexed & Zipaligned for Z1 C6903 14.5.A.0.242 Firmware
Some Apk Will Have .odex File like gapps due error fc on app , so i decide not deodex thats app.
Requirements
Locked Bootloader Or Unlocked Bootloader
Rooted
Working Recovery
Please Note That The Zip Only Contained System App,Framework & Priv-App
Additional info:
Zip file include app from z3 firmware like Smart call Handling, Smart rotation, smart backlight, bgdefocus etc,
Some file remove like google stand, google playbook etc.
Tested on z1, xposed module worked fine.
Please follow instruction below
Installation:
1. Download The Zip & Move It To Your Phone
2. Boot Into Recovery
.3. Clear Cache & Dalvik Cache
4. Flash deodex zip
5.. Done
Download:
Deodexed & Zipaligned C6903 LP 5.0.2 14.5.A.0.242 Patch ( 655.3 MB ) - mega.co.nz
Torrent file:
I get repeated force close GAProxy and com.android.phone something
what should I do, I can't use the phone !!
ing005 said:
I get repeated force close GAProxy and com.android.phone something
what should I do, I can't use the phone !!
Click to expand...
Click to collapse
tried two times to flash deodex zip before upload , never get such problem , try force shutdown your phone , (Hold Power + Vol up) , after shutdown , turn on phone + vol up ( boot into recovery) - clear cache and dalvik cache again- reboot.
I did everything, now I have to re-flash stock FW : (
BTW, I have problwm with Titanium Backup-I can't uninstall pre-install app, it keeps comeback whenever i restart the phone. Is that has something to do with odexed-deodexed thing ?
and Xposed said it is not compatibel with my FW either, is that normal ?
ing005 said:
I did everything, now I have to re-flash stock FW : (
BTW, I have problwm with Titanium Backup-I can't uninstall pre-install app, it keeps comeback whenever i restart the phone. Is that has something to do with odexed-deodexed thing ?
and Xposed said it is not compatibel with my FW either, is that normal ?
Click to expand...
Click to collapse
i'm sorry to hear that , try force shutdown the phone , then boot phone + vol down , (TeamWin Recovery ) - mount system , advanced - file manager - go to system\ app directory or priv-app dir , delete fc app .
downloading now......
Good job but I flashed this over German pre-rooted ROM, but got FC on android.phone and GAproxy. Had to reflash complete ROM.
iedafarha said:
Hi Xperian , here Deodexed & Zipaligned for Z1 C6903 14.5.A.0.242 Firmware
Some Apk Will Have .odex File like gapps due error fc on app , so i decide not deodex thats app.
Click to expand...
Click to collapse
awesome. thank you
Vatron11 said:
awesome. thank you
Click to expand...
Click to collapse
welcome, Please perform nandroid backup before flash deodex , i dont know why some people get fc on GAProxy and com.android.phone . Mine everything okey.
FC phone and GA,
hmm.
maybe need original files from each device, but should not
Alvian_P said:
FC phone and GA,
hmm.
maybe need original files from each device, but should not
Click to expand...
Click to collapse
Just now clean install 5.0.3 LP firmware, i use HK base firmware before, flash deodex.zip no fc issue, , what i did :
1.. Clear Dalvik/ART cache and clear cache.
2. flash deodex zip ,
3. reboot phone ..
try it ,, let me know is fc still exist.
still not working i follow your steps to the latter .......................................................i tried twp gaproxy is short for googleanalytical service
i had romve it but i end up with another fc com.android.phone and google.gapp process.......................................................................:crying::crying::crying:
iedafarha said:
Just now clean install 5.0.3 LP firmware, i use HK base firmware before, flash deodex.zip no fc issue, , what i did :
1.. Clear Dalvik/ART cache and clear cache.
2. flash deodex zip ,
3. reboot phone ..
try it ,, let me know is fc still exist.
Click to expand...
Click to collapse
I have do that
Works fine on my c6906, thanks.
I've installed on the xperia z1 c6906 and so far it works correctly.
1. closure of Google Play is presented, and was repaired by installing Google Play again.
2. Now works Xposed and compatible modules like Amplify, Cool Tool, Gravity Box, Greenify, Lookscreen Disabler, etc ..
thank you very much...
iedafarha said:
Just now clean install 5.0.3 LP firmware, i use HK base firmware before, flash deodex.zip no fc issue, , what i did :
1.. Clear Dalvik/ART cache and clear cache.
2. flash deodex zip ,
3. reboot phone ..
try it ,, let me know is fc still exist.
Click to expand...
Click to collapse
The force closes are mainly due to left over odexed apps
make sure every app should be deodexed ( if you got Gapps force close then you would be having some google apps with odex. like youtube, hangouts, gmail etc.,)
and even the apps in vendor/app should be deodexed
i have a small doubt if you dont mine... that will help me
Have you really zipaligned the apps ?
how was that possible ?
thank you,
Best regards
good job friend
venkat kamesh said:
The force closes are mainly due to left over odexed apps
make sure every app should be deodexed ( if you got Gapps force close then you would be having some google apps with odex. like youtube, hangouts, gmail etc.,)
and even the apps in vendor/app should be deodexed
i have a small doubt if you dont mine... that will help me
Have you really zipaligned the apps ?
how was that possible ?
thank you,
Best regards
good job friend
Click to expand...
Click to collapse
i not deodex gapp and anything relations with google app , and i confirm all deodex file zipaligned , since i donno what script code to use for zipalign in folder/folder/*.apk , i pull one by one apk file from their folder manually ( i use komome toolfor zip and zipalign), honestly i dont have problem to install this file , no fc gapproxy or com.android.phone. btw thanks mate for clarifying. :good:
my advice, if any force close, try push manual one by one ?
Alvian_P said:
my advice, if any force close, try push manual one by one
Click to expand...
Click to collapse
you are the man !!! :laugh::laugh::laugh: ,
info about fc app ,
1. GAProxy
Package name: com.sonymobile.googleanalyticsproxy
Path: /data/data/com.sonymobile.googleanalyticsproxy
Apps Data Path: data/data/com.sonymobile.googleanalyticsproxy
2. com . android.phone
Package name: com . android.phone
App path: /system/priv-app/TeleService/Teleservice.apk
Apps Data Path: data/data/com.android.phone
Solution for force close.
Boot into recovery (TeamWin Recovery Project) force shutdown , Power Button + vol down - mount system - advanced - file manager, point to data Path or app path search for odex file and delete it.
iedafarha said:
you are the man !!! :laugh::laugh::laugh: ,
info about fc app ,
1. GAProxy
Package name: com.sonymobile.googleanalyticsproxy
Path: /data/data/com.sonymobile.googleanalyticsproxy
Apps Data Path: data/data/com.sonymobile.googleanalyticsproxy
2. com . android.phone
Package name: com . android.phone
App path: /system/priv-app/TeleService/Teleservice.apk
Apps Data Path: data/data/com.android.phone
Solution for force close.
Boot into recovery (TeamWin Recovery Project) force shutdown , Power Button + vol down - mount system - advanced - file manager, point to data Path or app path search for odex file and delete it.
Click to expand...
Click to collapse
It did not work.
Jorge Luis Alves said:
It did not work.
Click to expand...
Click to collapse
try goto /system/app/GoogleAnalyticsProxy and /system/priv-app/Teleservice/ folder delete arm folder if exist
//Thank you all for 30k+ Views. You're amazing guys//
You want Android 8 with Viper4android to?
Thread created check my profile...
Hi,
at first im not responsible for anything that happens to your phone OK?
Fine Let's Start.
If you are on cm skip all until the cm section
Supported kernel list and known errors/bugs see second post
Step 1
- Flash full Factory Images.
- Install TWRP, remember you have to be decrypted.
Step 2
- Install Android 7 ROM by tupac4u / or any other rom / or leave stock
- Reboot //if nessesairy
Step 3
- Flash ElementalX's N Kernel.
- Flash Viper5.0_Stock.zip in Recovery / or any other viper
- Reboot.
Step 4
- Install driver.
- Open File Explorer and delete /system/vendor/etc/audio_effects.conf
- Reboot.
Step 5
- Set enforcing to permissive (You have to do it at every Reboot!).
- In Viper open Menu->FX-CompatibleMode->yes // you can try without, it may work
- Enjoy Viper.
CM Section
1. Flash arise sound mod ( link down below )
2. And IMPORTANT flash super su
3. Disable audio fx and reboot
SPOTIFY FIX
1. Download that file
https://drive.google.com/file/d/0BxyY1q0qeeeEeUFGT3JHeDZLZkE/view
2. Place it under /system/etc
3. Reboot
PURE NEXUS ONLY WORKS WITH BUILD 10/25!!!
If it worked leave a reply.
Alternative Download link for ARISE Viper here:
http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
Unsupported Rom/Kernel
Kernel:
- Stock
- Jolla
ROM:
F.A.Q.
Q: Spotify isn't working with that
A: Force enable Viper4Android and turn FX Mode to compatible. Then restart both applications.
Q: Why ElementalX Kernel?
A: That's the only Kernel who works with Viper except Stock kernel. Elite Kernel may also work but it hasent been updated since the Dev Previews.
Q: Is that also working with the stock rom?
A: Yup. Also works with (nearly) any stock based ROM.
Is there a definite way of checking if it's working? Not by sound?
Yes, just check driver status in viper when something is playing in the background. If it says 'processing', then it's working.
Btw, why would I need custom kernel for viper?
Sent from my Nexus 5X using Tapatalk
how to set permissive mode permanently?
Nightshadow931 said:
Yes, just check driver status in viper when something is playing in the background. If it says 'processing', then it's working.
Btw, why would I need custom kernel for viper?
Click to expand...
Click to collapse
I found that it isn't working on jolla Kernel and Stock.
Did you enable viper in app itself?
Not sure, but maybe you need to enable it on order to see 'processing'..
Did the installation of driver went well?
Sent from my Nexus 5X using Tapatalk
enzippo said:
how to set permissive mode permanently?
Click to expand...
Click to collapse
use a file exlorer with root privileges like es or root explorer and go to /etc/init.d directory, create a file and named "08setperm" (without quotes) and add the below lines in the file and save it..
#!/system/sh
setenforce 0
And give full permission (rwxrwxrwx)
reboot and you should be good. if for some reason your init.d script doesn't launch then download and install universal init.d tool and enable it.
Nice that someone is trying to get Viper4Android to work on Nexus 5x with Android 7.0 (Nougat). Sadly it does not work, tried your way but it does not enable me to get Viper4Android to work in Spotify.
Selinux is in permissive, your viber4android package is in place, audio_effects.conf removed, Android 7 by tupac4u installed and complete factory image installation before all this. No go..
Viper4android driver status does not complain but processing is always "no".
Try some other app like play music, v4a won't work on all apps if they have their own equalizer.
Sent from my Nexus 5X using Tapatalk
Blinkiz said:
Nice that someone is trying to get Viper4Android to work on Nexus 5x with Android 7.0 (Nougat). Sadly it does not work, tried your way but it does not enable me to get Viper4Android to work in Spotify.
Selinux is in permissive, your viber4android package is in place, audio_effects.conf removed, Android 7 by tupac4u installed and complete factory image installation before all this. No go..
Viper4android driver status does not complain but processing is always "no".
Click to expand...
Click to collapse
For those who want to use Viper4android with Spotify change fx compatible Mode to compatible in Viper settings. Then Open Spotify and go to Settings->Equalizer that should bring up Viper. Select Force enable and close Viper and Spotify. Open up both again and Boom Viper is there.
How find Android 7 by tupac4u ??
EDIT.
I found him already
Did someone get it working with stock rooted ROM?
noidea24 said:
use a file exlorer with root privileges like es or root explorer and go to /etc/init.d directory, create a file and named "08setperm" (without quotes) and add the below lines in the file and save it..
#!/system/sh
setenforce 0
And give full permission (rwxrwxrwx)
reboot and you should be good. if for some reason your init.d script doesn't launch then download and install universal init.d tool and enable it.
Click to expand...
Click to collapse
Idk if this will work on the new version, but this zip I've attached here sets the previous ElementalX-N5x-1.17 kernel permissive permanently. I'm not on nougat yet, waiting for Xposed.
trhacker01 said:
Idk if this will work on the new version, but this zip I've attached here sets the previous ElementalX-N5x-1.17 kernel permissive permanently. I'm not on nougat yet, waiting for Xposed.
Click to expand...
Click to collapse
In gonna give it a try
Nightshadow931 said:
Did someone get it working with stock rooted ROM?
Click to expand...
Click to collapse
Me not
Thargorsson said:
In gonna give it a try
Click to expand...
Click to collapse
Nope it don't works
Thargorsson said:
Nope it don't works
Click to expand...
Click to collapse
thats how im running right now, just checked. only with the universal init.d though
noidea24 said:
thats how im running right now, just checked. only with the universal init.d though
Click to expand...
Click to collapse
Ur saying that permissive zip works with the universal init.d?
trhacker01 said:
Ur saying that permissive zip works with the universal init.d?
Click to expand...
Click to collapse
As long as the zip creates/places a file in the init.d to change selinux then i guess it should work
Caution Only For Oreo 64bit
Hello Guys , This is my First thread . Be Sure To Leave A Reply . All Links Below The Thread.
I Am Using Moto g5 with :-
1. Unlocked Bootloader
2. 64bit Recovery (Thanks To @CodeZero)
3. Aosp Extended Rom (Thanks To @Fedray , You are on Fire)
Steps For HDR+ And Portrait Mode
Note :Currently All Oreo Roms (Not Stock) have patched Camera , so you need to follow as below to enable HAL3 (camera 2 api)
1. Install MagiskManager (latest version) and flash magiskzip (will be available inside magiskmanager)
2.Install MiXplorer and give root access
3.Go to root directory then go to /system/lib/hw
4. Delete or Rename camera.msm8937.so as camera.msm8937.so.bak and rename camera.vender.msm8937.so to camera.msm8937.so
5.Install BuildPropEditor.
6. Add A Line Saying "persist.camera.HAL3.enabled=1"
7.Reboot
8. Install Provided Camera
9. Go To camera Settings - Advanced - Under Front Camera - Manual fixed black level offset- Set To 16 or 12
10.Restart Camera Application.
Boom You Get HDR+ And Portrait Mode .......But I Was Not Able To Record Videos (But Footej Is Working For VIdeos)
If You Want Ar Stickers , then Flash The Zip Below After Following the above tutorial
You May Now Also Install Motion stills apk from the play store.
Magisk Manager - Search Google
MiXplorer - https://forum.xda-developers.com/showthread.php?t=1523691
Camera - https://drive.google.com/file/d/1skMGmQlHOn0pVXh5UD7AS6F6LIQNTF91/view?usp=sharing
Ar Stickers - https://drive.google.com/file/d/1skMGmQlHOn0pVXh5UD7AS6F6LIQNTF91/view?usp=sharing
Pixel Fonts - https://drive.google.com/file/d/1jfHTqLU8bu1FyWelprindMzYpW5wC1OP/view?usp=sharing
BuildProp Editor - https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en_IN
Twrp 64 - https://androidfilehost.com/?w=files&flid=236353
If I Miss To give Credits to Anyone Pls PM me
Any mod for 32bit with Portrait Mode
Fedray used to be on fire but now he doesn't update AEX at all
Exanneon said:
Fedray used to be on fire but now he doesn't update AEX at all
Click to expand...
Click to collapse
Chill man , he is busy.
abhimanyuk said:
Any mod for 32bit with Portrait Mode
Click to expand...
Click to collapse
There is but......you will have to use lensblur
Or else you may use Snapseed for editing and making image blur.. search Google.
Can I run camera files by transferring to android 9?