Solution is in end of first page
We can install sdk22 v80 for 64 bit in our device
It works very well
But one problem that camera force stop everytime
If we uninstall it then camera works perfectly
Plz help someone how to make camera work for our device with xposed installed
sumitkhkh said:
We can install sdk22 v80 for 64 bit in our device
It works very well
But one problem that camera force stop everytime
If we uninstall it then camera works perfectly
Plz help someone how to make camera work for our device with xposed installed
Click to expand...
Click to collapse
Use another app for camera??
Enviado desde mi D6653 mediante Tapatalk
no camera is best than sony
To fix the camera issue for me it worked to use this method:
http://forum.xda-developers.com/crossdevice-dev/sony/z4-z5-z5c-fix-camera-fc-installing-t3246962
So, give it a try...
can you plz upload deodexed folders
oenke said:
To fix the camera issue for me it worked to use this method:
http://forum.xda-developers.com/crossdevice-dev/sony/z4-z5-z5c-fix-camera-fc-installing-t3246962
So, give it a try...
Click to expand...
Click to collapse
Works very well on E5563, thanks.
I'm having this when trying to deodex the camera app: Boot.oat Extraction Failed
Does anyone know how to solve it
{
"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"
}
PnPZik said:
I'm having this when trying to deodex the camera app: Boot.oat Extraction Failed
Does anyone know how to solve it
Click to expand...
Click to collapse
You could try to update to a newer Java version. As I see in the image you use Java 6. Maybe it depands on that.
In that threat, post #2 it is said:
Works with both Java 7 and 8
Click to expand...
Click to collapse
.
oenke said:
You could try to update to a newer Java version. As I see in the image you use Java 6. Maybe it depands on that.
In that threat, post #2 it is said: .
Click to expand...
Click to collapse
I've update my Java to version 8 but somehow it's still 6 in the sofware. I have to fully uninstall all version of Java on my computer and reinstall the 7 version and now it works.
Thanks !
problem Solved
Copy the files-.apk to their folder using your filemanager app
and /system/priv-app/CameraCommon/CameraCommon.apk
You must have system-partition with read/write/delete access.
Dont forget do change file privilege chmod with the Root explorer touch-interface to permission-mode "644"
Link
http://forum.xda-developers.com/attachment.php?attachmentid=3619981&d=1453581171
Enjoying Phone Now
i want to install xposed on my c5 ultra dual(E5563) lollipop 5.0 . i already download files. but i don't know how to install cwm or twrp recovery on my phone.
waiyanwin said:
i want to install xposed on my c5 ultra dual(E5563) lollipop 5.0 . i already download files. but i don't know how to install cwm or twrp recovery on my phone.
Click to expand...
Click to collapse
Okay, so you have two files, the .apk file for the Xposed Installer app and the .zip, which you need to flash for it to work.
It is now super easy to flash it using TWRP, which is a custom recovery now available for C4/5 thanks to @bigrammy (I'm very thankful for the hard work and detailed instructions!):
forum.xda-developers.com/xperia-c5-ultra/development/bootloader-unlocked-custom-recovery-t3285521
Read everything carefully. I was able to get TWRP and SuperSU then easily flashed the Xposed Framework .zip via TWRP.
According to the second post in the thread I linked to above, it's confirmed to be working on Firmware Version 5.0.2 and 5.1.1 for the C5 Single, Dual, and World Wide for all Variants with Boot Loader 0.5, so the method may work for your phone.
---------- Post added at 11:13 PM ---------- Previous post was at 11:04 PM ----------
sumitkhkh said:
Solution is in end of first page
We can install sdk22 v80 for 64 bit in our device
It works very well
But one problem that camera force stop everytime
If we uninstall it then camera works perfectly
Plz help someone how to make camera work for our device with xposed installed
Click to expand...
Click to collapse
I'm sorry if this is an OT post, but I can't seem to find a dedicated place for the C4, and the C4 and C5 seem so close in terms of specs (other than the screen size, for example) that they're often used interchangeably in this forum, so I wanted to post about my own experience with the Xperia C4 (E5303). I want to confirm that I was also able to get the Xposed Framework working, gave it root privileges via SuperSU, and even installed a module. It seems to be working fine so far.
However, I also ran into the problem of the camera and album FC. Since none of the files linked to here are for my device and I'm afraid that using them might have an adverse affect because they're only compatible with the C5 Ultra, I'm going to try the Deodexer and report back here to let you know what happens.
boot.oat not found . and i keep getting annoying errors...
gsser said:
boot.oat not found . and i keep getting annoying errors...
Click to expand...
Click to collapse
Could you please provide more details about this error? What were you doing?
I think I got a similar error when using LBD2.5, but I know why. I tried to deodex my system folder, and it failed to deodex the CameraCommon app because I didn't delete the "arm" folder in CameraCommon. I delete it then received the error you mentioned above probably because everything but CameraCommon had already been deodexed. What I did to resolve it was copying the respective files from my device to my pc once more then trying again, and it was successful, so it's worth a try.
Okay, I can't seem to figure this out... I was able to download LBD2.5, and it worked fine when deodexing CameraCommon.apk with no errors after I followed all the instructions in the first post (only leaving arm64 in the CameraCommon directory), but after a reboot it still didn't work. My album seems to be working fine now, though, and I'm not sure why that is.
I tried leaving just arm in the directory and then tried neither arm64 nor arm, but they both failed to even doedex completely. Nothing seems to be working for me. I'm able to do everything in the first post, but the camera never works.
I even downloaded the file attached, although it's not for my Xperia C4 (E5303), and that didn't work either. I'm going to try a free camera app for the time being until I can figure this out. If anyone has any suggestions, please let me know.
xperia_c4_hater said:
Could you please provide more details about this error? What were you doing?
I think I got a similar error when using LBD2.5, but I know why. I tried to deodex my system folder, and it failed to deodex the CameraCommon app because I didn't delete the "arm" folder in CameraCommon. I delete it then received the error you mentioned above probably because everything but CameraCommon had already been deodexed. What I did to resolve it was copying the respective files from my device to my pc once more then trying again, and it was successful, so it's worth a try.
Click to expand...
Click to collapse
i just took a deodexed camera apk and gave the right permissions then did a reboot now its working
gsser said:
i just took a deodexed camera apk and gave the right permissions then did a reboot now its working
Click to expand...
Click to collapse
I'm happy for you! :good: However, mine still isn't working, even when I just tried again by downloading an already deodexed apk and giving it the right permissions.
xperia_c4_hater said:
I'm happy for you! :good: However, mine still isn't working, even when I just tried again by downloading an already deodexed apk and giving it the right permissions.
Click to expand...
Click to collapse
I had the same problem with my C5 Ultra Dual E5563. I've tried both downloaded deodexed file on xda and deodexed the file myself but none of them work, of course I've set chmod 644 for the file.
I did it like that: gave root permission to es file manager, deleted cameracommon.apk under system priv app. then reboot and again placed the deodexed apk to priv app and changed name to cameracommon. then gave the permissions 0644 and again did a reboot then it got fixed. hopefully it helps you
gsser said:
I did it like that: gave root permission to es file manager, deleted cameracommon.apk under system priv app. then reboot and again placed the deodexed apk to priv app and changed name to cameracommon. then gave the permissions 0644 and again did a reboot then it got fixed. hopefully it helps you
Click to expand...
Click to collapse
Thanks for explaining what you did in detail!
I just tried it now, but it still didn't work for me.
Related
Hello!!
The #HYPE is correct.
OPT devs are on the job for creating the best base of CM12.1
Meanwhile here is my guide to install the Xposed Framework on Stock Oxygen OS after Root.
1) YOU NEED PERFECT ROOT WITH SU. Follow THIS awesome simple guide.Before Starting to Unlock Your Boot Loader
Backup Every Bit of Your Data
Perform fill wipe op your mobile
Don't use encrypted mobile. REMOVE Encryption
Have patience, After OEM Unlock, Don't Reboot.
(Hold Volume Down + Power) to open the TWRP else you will end up in STOCK Recovery.
2) Make a NANDROID
Click to expand...
Click to collapse
Since OPT is based on ARM64, Get the following from Official Xposed Thread Here
You should get these two files
1)
{
"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"
}
xposed-v73-sdk22-arm64.zip - (5.62 MB)
2)
XposedInstaller_3.0_alpha4.apk - (611.8 KB)
Once You are ready with all the above quoted prerequisites, start
Step 1:
Download the above said two files in a folder of your OPT Internal Memory
Step 2:
Boot to recovery
Step 3:
Flash 1st file which is a Zip File
Step 4:
Reboot your Mobile after flashing normally.
Step 5:
Open the Second File (.apk) from your file browser and install.
Step 6:
Open the Exposed Installer from you app Menu.
Step7:
If everything goes well, You should find this..
Hope From this you can take off downloading the modules you would like to and enjoy tweaking the Stock ROM...
This is Youtube PopUp Module (Second one from the list) Working on my OPT
This is the Lockscreen Mod
Enjoy Guzy.. Hit Like if this guide Helped
are there any bugs? will we get OTA if we install this? can we uninstall this ? will warranty be affected? please confirm
---------- Post added at 10:10 PM ---------- Previous post was at 09:35 PM ----------
Can you tell us which are the modules that are safe and working here? so that we can test and confirm ?
Hi Bharat
OTA have no issues so far.
See my screens below running Latest of Oxygen OS
Will be certain if any more updates are out. As of now, no issues.
All modules which are for lollipop are working absolutely fine. No issues if you go through the description of each module before installing. However device specific modules which are developed for Xperia.. Samsung.. HTC.. Etc.. Can't work.
Hope this helps.
No SU for Xposed Installer
I installed the framework on my rooted OPT as per your instructions (great guide btw) but the xposed installer doesn't get SU permissions. I set it up with the same options checked as in my OPO with CM 12.1.1 . Any ideas why ?
Thanks for your time.
fpavoncelli said:
I installed the framework on my rooted OPT as per your instructions (great guide btw) but the xposed installer doesn't get SU permissions. I set it up with the same options checked as in my OPO with CM 12.1.1 . Any ideas why ?
Thanks for your time.
Click to expand...
Click to collapse
Open Xposed Installer->Framework->Reboot Grant SU permission.
Tapped from my ①+②=❸
vaisakh7 said:
Open Xposed Installer->Framework->Reboot Grant SU permission.
Tapped from my ①+②=❸
Click to expand...
Click to collapse
That didn't work, that's why I posted the question.
With only Greenfy and Bootmanager modules installed, I rebooted a dozen times but it didn't get SU permissions.
The problem was solved later on when I installed the "true silent mode" module (it doesn't work in case you want to know), wich I guess needed the permission.
Anyway, problem solved, now it has SU permissions. Thank for the help anyway.
fpavoncelli said:
I installed the framework on my rooted OPT as per your instructions (great guide btw) but the xposed installer doesn't get SU permissions. I set it up with the same options checked as in my OPO with CM 12.1.1 . Any ideas why ?
Thanks for your time.
Click to expand...
Click to collapse
Hi there..
Its because of improper rooting.
I Suggest you to re-start the rooting process from the guide above.
After OEM Unlock and recovery flashing.. DO NOT REBOOT
Then Reboot to recovery and then Don't forget to slide (RECOVERY IMAGE STABILIZING)
Then after rebooting to system..
Reset your Phone (Prefer to take a NANDROID after this)
Then Flash SU and check with Rootaccess Checker
If everything Goes well
Then Flash the Xposed Framework given above an then Install and REBOOT before opening.
Then when you open the Xposed application, then SU should popup for permission..
Hope this helps...
Did you suggest some interesting modules for Xposed on OPT ?
ps000000 said:
Did you suggest some interesting modules for Xposed on OPT ?
Click to expand...
Click to collapse
No, I just got it, and I'm trying to figure out Oxygen OS lack of funcions compared with Cyanogen wich is what sold me on the OPO.
Maybe in the next few days I will.
Just my 2 cents:
Download xposed-uninstaller-20150831-arm64.zip and keep it on your internal sd card!
In case of a bootloop caused of a trouble making Xposed mod you just flash the uninstaller to get rid of the bootloop.
Then uninstall or deactivate the mod in Xposed Installer app and reinstall Xposed again.
So when i checked the official thread for xposed it showed a newer file version than what is mentioned here. However in that v74 there are 2 versions again
xposed-v74-sdk21-arm64.zip -
xposed-v74-sdk22-arm64.zip -
not sure which one to use with my Oxygen OS 2.1
Anyone has any information on the above.
Edit : Never mind mound it.
Dude_Virus said:
So when i checked the official thread for xposed it showed a newer file version than what is mentioned here. However in that v74 there are 2 versions again
xposed-v74-sdk21-arm64.zip -
xposed-v74-sdk22-arm64.zip -
not sure which one to use with my Oxygen OS 2.1
Anyone has any information on the above.
Edit : Never mind mound it.
Click to expand...
Click to collapse
so which did you use? the 22?
I used v74sdk22
Sdk 22 is the right one.
Sdk 21 was for Android 5.0
Oxygen OS 2 is based on Android 5.1
Full list of SDK versions and corresponding Android version:
http://developer.android.com/reference/android/os/Build.VERSION_CODES.html
does whole xposed module work well on OPT? any bugs or app that isn't working or so?
22vlaja said:
does whole xposed module work well on OPT? any bugs or app that isn't working or so?
Click to expand...
Click to collapse
No issues so far!I'm running Amplify, Gravitybox,Greenify,Powernap,Notification Counter,AppOpsXposed.
Tapped from my ❶+❷
vaisakh7 said:
No issues so far!I'm running Amplify, Gravitybox,Greenify,Powernap,Notification Counter,AppOpsXposed.
Tapped from my ❶+❷
Click to expand...
Click to collapse
Did u notice some strange behavior after installing Xposed? and did u follow tutorial flash from first site?
22vlaja said:
Did u notice some strange behavior after installing Xposed? and did u follow tutorial flash from first site?
Click to expand...
Click to collapse
1.Flash the Xposed V74-arm64-SDK22 from here.
2.Wipe cache and dalvik cache after flashing.
3.Reboot and install the XposedInstaller-alpha4.apk
4.Open the app->Framework->Reboot.
5.Grand SuperSU access.
Done!
You might have missed the second step.That's not mentioned in the OP.
Tapped from my ❶+❷
allready installed Xposed, just wanted to be sure that this steps is ok!
one more thing, why did you installed AppOpsXposed? its implemented in Oxygene.
22vlaja said:
allready installed Xposed, just wanted to be sure that this steps is ok!
one more thing, why did you installed AppOpsXposed? its implemented in Oxygene.
Click to expand...
Click to collapse
AppOpsXposed is needed to handle GooglePlayServices.
Tapped from my ❶+❷
So recently I've rooted my galaxy s5 tmobile sm-g900t and install viper4andriod. I have Busybox installed through google play and installed on both my xu and system folder. I also made sure there was enough space. Around 30mb of space. I then installed SeLinuxMode Changer and Universal init.d so that i can force the SeLinixmode changer to stay on permissive. There is a bug where restarting and exiting out the app would reset SeLinux mode you have selected. Now that that SeLinusMode restarts on permissive, i was able to install Viper4Andriod. I then continued and installed the driver, but after installation, i checked to see if anything changed in the sound. Nothing changed so i checked the driver status. It turns out to be Abnormal and unsupported. I'm running 2.3.40, and have also tried the latest version of Viper4Andriod, but both doesn't seem to work. I have stock touchwiz rom and completely disabled and removed Knox. I checked my root with Root Checker, and it passed. But for some reason going into recovery mode, it asks me to install supersu because it was missing. But at the same time, i am running PhilzTouch, which is outdated. I have tried other methods, but it doesn't seem to work. I just need to get pass the driver status problem.
If anyone know the solution to this, I'd very much appreciate it if you help us all out.
Same for me : with 6.0.1 rooted, the driver was unsupported.
What worked for me was to install viper4android from the play store, as the 2.3.4.0 version has better sound (in my own opinion) than the 2.4.0.1 that can be found elsewhere. After installing the driver in high quality, it showed as unsupported.
I had to flash two additional files that you can find here http://forum.xda-developers.com/showpost.php?p=52106530&postcount=609 : Viper4A-[Build.Prop-Tweaks]-CWM.zip and Viper4A-[Soundfix-LibFiles]-CWM.zip. I am no expert, and probably only the second file is required but I flashed both and it just worked.
Also, you don't need a SElinux permissive kernel. You can simply flash the file linked here http://forum.xda-developers.com/showthread.php?p=61242973#post61242973, and it will patch your system. As long as you have supersu installed, you will be able to use viper4android in enforcing.
For full steps, you can also have a look at maximumentropy post here :
maximumentropy said:
...
Install the APK in the standard way (not in priv-app or most convolvers won't work).
Install the highest quality drivers and reboot to recovery
Flash the update here from recovery to allow V4A execution with SELinux Enforcing: http://forum.xda-developers.com/showthread.php?p=61242973#post61242973
Flash the Viper4A-[Soundfix-LibFiles]-CWM.zip from this message (but not the others) to replace the system sound libraries in /system/lib/soundfx with V4A-compatible versions: http://forum.xda-developers.com/showpost.php?p=52106530&postcount=609
Reboot
In Viper settings, use Normal mode, not Compatible.
Enable V4A-FX in the desired profile (it is not necessary to use Force Enable V4A)
...
Click to expand...
Click to collapse
alexbelgium said:
Same for me : with 6.0.1 rooted, the driver was unsupported.
What worked for me was to install viper4android from the play store, as the 2.3.4.0 version has better sound (in my own opinion) than the 2.4.0.1 that can be found elsewhere. After installing the driver in high quality, it showed as unsupported.
I had to flash two additional files that you can find here http://forum.xda-developers.com/showpost.php?p=52106530&postcount=609 : Viper4A-[Build.Prop-Tweaks]-CWM.zip and Viper4A-[Soundfix-LibFiles]-CWM.zip. I am no expert, and probably only the second file is required but I flashed both and it just worked.
Also, you don't need a SElinux permissive kernel. You can simply flash the file linked here http://forum.xda-developers.com/showthread.php?p=61242973#post61242973, and it will patch your system. As long as you have supersu installed, you will be able to use viper4android in enforcing.
For full steps, you can also have a look at maximumentropy post here :
Click to expand...
Click to collapse
It says its only for kitkat rom? Do you knw if it works for gs5 sm-g900t?
Frankie_Xenon said:
It says its only for kitkat rom? Do you knw if it works for gs5 sm-g900t?
Click to expand...
Click to collapse
Well I am sure that it works both for SM-G900F on 5.0 and 6.0.1 roms. The best for you is to make a backup of your system before trying. As it only impacts the system and not the kernel, it should work whether it is g900f or g900t...
alexbelgium said:
Same for me : with 6.0.1 rooted, the driver was unsupported.
What worked for me was to install viper4android from the play store, as the 2.3.4.0 version has better sound (in my own opinion) than the 2.4.0.1 that can be found elsewhere. After installing the driver in high quality, it showed as unsupported.
I had to flash two additional files that you can find here http://forum.xda-developers.com/showpost.php?p=52106530&postcount=609 : Viper4A-[Build.Prop-Tweaks]-CWM.zip and Viper4A-[Soundfix-LibFiles]-CWM.zip. I am no expert, and probably only the second file is required but I flashed both and it just worked.
Also, you don't need a SElinux permissive kernel. You can simply flash the file linked here http://forum.xda-developers.com/showthread.php?p=61242973#post61242973, and it will patch your system. As long as you have supersu installed, you will be able to use viper4android in enforcing.
For full steps, you can also have a look at maximumentropy post here :
Click to expand...
Click to collapse
Do you know if this works for lollipop 5.1.1? It said for kitkat rom?
Frankie_Xenon said:
Do you know if this works for lollipop 5.1.1? It said for kitkat rom?
Click to expand...
Click to collapse
Mmh I answered just above to that question? I tested it both on touchwiz with android 5 (lollipop) and 6 (marshmallow) and it works! It said "only kitkat" because at that time lollipop wasn't out you can see that the original post was dated from early 2014.
alexbelgium said:
Mmh I answered just above to that question? I tested it both on touchwiz with android 5 (lollipop) and 6 (marshmallow) and it works! It said "only kitkat" because at that time lollipop wasn't out you can see that the original post was dated from early 2014.
Click to expand...
Click to collapse
My apologies lol. My phone lagged and i ended up replying twice. Thanks ill give it a shot!
alexbelgium said:
Mmh I answered just above to that question? I tested it both on touchwiz with android 5 (lollipop) and 6 (marshmallow) and it works! It said "only kitkat" because at that time lollipop wasn't out you can see that the original post was dated from early 2014.
Click to expand...
Click to collapse
For some reason the driver keeps asking me to install it after flashing 2 the zips.
Guys, can you check this ROM(lollipop 5.1.1) for geiti94 which have all ready included this app. Very stable and battery friendly.
https://mega.nz/#!HdggTITL!C9bVqBlPwh8Kg8R7eeJQ_NokENEBwqmhkXBMNjwOZUs
Frankie_Xenon said:
For some reason the driver keeps asking me to install it after flashing 2 the zips.
Click to expand...
Click to collapse
Is your kernel still permissive? If not you can also try to flash the supolicy fix.
You can also try to remove completly the viper4android app and reinstall it.
Lastly there are some identified issues with some supersu versions. I am sure that the driver installation works with supersu 2.52 (my main one when I was on lollipop) and 2.68 (the one I use on marshmallow). Changing your supersu to 2.52 could perhaps help you. This is identified in the main viper4android thread here "If you see V4A installation pop-up loop, its probably due to incomplete root."
Hi. I have a G900H with stock rom, just rooted and Selinux enforcing and Viper works just fine. I just installed it and also installed busybox and flashed a file I got somewhere on xda to permit Viper on enforcing. I also had to verify my settings on supersu to uncheck the entry for namespaces. Hope it helps
Enviado desde mi SM-G900H mediante Tapatalk
So op, did you manage to make viper4android work?
alexbelgium said:
So op, did you manage to make viper4android work?
Click to expand...
Click to collapse
read the reply above you it gives you the solution
---------- Post added at 12:09 AM ---------- Previous post was at 12:04 AM ----------
alexbelgium said:
So op, did you manage to make viper4android work?
Click to expand...
Click to collapse
mannyvzla said:
Hi. I have a G900H with stock rom, just rooted and Selinux enforcing and Viper works just fine. I just installed it and also installed busybox and flashed a file I got somewhere on xda to permit Viper on enforcing. I also had to verify my settings on supersu to uncheck the entry for namespaces. Hope it helps
Enviado desde mi SM-G900H mediante Tapatalk
Click to expand...
Click to collapse
works like a charm thank you! lets spread this so more people will enjoy it
Also make sure "Mount Namespace Separation" is off in SuperSU.
{
"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"
}
Hey Guys,
in this Tutorial I will show you how to activate the Adoptable Storage function on the M4 Aqua with the help of the Xposed Framework.
Attention: Me or not anyone else is responsible if you proceed with this. We do not take any responsibility for any bricked phones, dead sd cards, void warranties or anything else.
At first let's talk about what we need:
- Android 6.0.1 (I used the Customized FR version. (Build R5C))
- Xposed Framework Installer: Download
- Xposed SDK23 ZIP File (I used v86): Download
- (Minimal) ADB: Download
- Unlocked Bootloader, ROOT and TWRP
So let's go:
1. Unlock your Bootloader and install TWRP like described here. (It may works also like described here without unlock your Bootloader but I didn`t test this.)
2. Install Root like described here.
3. Install the Xposed Framework Installer.
4. Boot into your TWRP. (Press PowerButton + Vol- Button to start your Phone into TWRP)
5. Connect your Phone with USB on your PC. (Make sure you've got all Drivers installed. You will find them in the Flashtool install location.)
6. Move the Downloaded Xposed ZIP to the install location of your (Minimal) ADB
7. Open an Shell were you've installed your (Minimal) ADB
8. Type the following:
Code:
adb devices
If your Phone is now listed you can continue
Code:
adb shell
Now you should see a command line like this: ~#
Then Type:
Code:
mount -w /dev/block/platform/soc.0/7824900.sdhci/by-name/system /system
mount -w /dev/block/platform/soc.0/7824900.sdhci/by-name/userdata /data
mount -w /dev/block/platform/soc.0/7824900.sdhci/by-name/cache /cache
If you become an response that your Resource is busy don't wory. This means it's already mounted.
Now type this:
Code:
twrp sideload
adb sideload xposed-v*-sdk23-arm64.zip
For the * use the version number of your Downloaded Xposed ZIP.
If this is complete type:
Code:
adb reboot
Now it may takes up to 10-20 Minutes until your Phone is booted the first time with Xposed.
After Boot open your Xposed Installer App and go to "Framework". It should look like this, if it is successfully installed:
{
"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"
}
9. Download the SystemUI Patcher for Lollipop+
10. Acitvate it in Xposed App (don't wonder if in the screenshot is another Module... you don't need this):
Open the Xposed Installer App --> Go to "Modules" --> Tick the Checkbox
11. Open the SystemUI Patcher App, scroll down, select "Enable adoptable storage" and restart your phone:
11. Insert your SD-Card and select "use it as internal storage". (I can't make a Screenshot of this by myself because I've done this before making this Tutorial):
12. Congratulations you've got successfully enabled adoptable storage on your M4 Aqua.
I tested it with the E2303. But it should work with any Version.
Special thanks to @depressed_ for the tipp with the SystemUI Patcher in this post.
And to @alby_var for the Tutorial how to install Xposed on Android 5, because I used this for orientation.
Known Issues: (Everything I or anybody else found)
- Stock Camera App didn't work for me after doing this! .-. It says "Memory unavailable" (I use now the App CameraMX ... This works fine!)
- On your storage settings will be shown some wired Numbers. (See Screenshot(s))
What about some screen(s)? Does it work 100% without any mini errors? People were complaining about their storage. It showed them weird numbers.
Btw thx for mentioning me.
Is this the original android feature being enabled? I think this should work without many problems if it is from android...
Pls make some screen.. Thanks
Sent from my E2303 using XDA-Developers mobile app
Seems good but how can you deactivate it?
Obblet said:
Seems good but how can you deactivate it?
Click to expand...
Click to collapse
I think so. Just go in your Settings --> Storage --> Internal Storage --> Migrate Data --> After this go to your SD-Card --> "Format as Portable"
For the other things:
Disable the Module in the Xposed Installer App and Uninstall the Xposed Framework.
For root and TWRP I use to flash the Original FTF File. (May there is another way... I don't know)
If there's an way to (re)lock the Bootloader, you can do this too. I heard somewhere that there is an way to do this but I don't know how. Sorry.
DarkerJava said:
Is this the original android feature being enabled? I think this should work without many problems if it is from android...
Click to expand...
Click to collapse
I think so because everything looks like the original, but to tell you the truth I don't know this. But it works. :good:
Not working. Memory shows -245677 or somethink. And camera doesn't work...
MK99 said:
Not working. Memory shows -245677 or somethink. And camera doesn't work...
Click to expand...
Click to collapse
Look at the "Known Issues" in first Post.
Camera and installing apps don't work... Is it because of my slow SD Card or is it the common issue?
lukas1838 said:
I think so because everything looks like the original, but to tell you the truth I don't know this. But it works. :good:
Click to expand...
Click to collapse
Thank you for your answer...
Sent from my E2303 using XDA-Developers mobile app
lukas1838 said:
I think so because everything looks like the original, but to tell you the truth I don't know this. But it works. :good:
Click to expand...
Click to collapse
Huh, judging from the new pictures, it seems that it is similar to the adb function... not the real adoptable storage tool.
Obblet said:
Camera and installing apps don't work... Is it because of my slow SD Card or is it the common issue?
Click to expand...
Click to collapse
My camera isn't working too, but installing apps works fine.
lukas1838 said:
My camera isn't working too, but installing apps works fine.
Click to expand...
Click to collapse
So the installing apps error is my SD Card's speed problem? I'm planning to buy a Samsung evo+. will it work?
Obblet said:
So the installing apps error is my SD Card's speed problem? I'm planning to buy a Samsung evo+. will it work?
Click to expand...
Click to collapse
I've got an EVO+ so it should work when the speed is the problem
same here , camera doesnt work but the installing apps works peffectly
Yes, now everything works, and if you want a camera, download a different camera app.
can i uninstall system camera app ? and make another camera app as system app ?
lukas1838 said:
I think so because everything looks like the original, but to tell you the truth I don't know this. But it works. :good:
Click to expand...
Click to collapse
Well, since my E2306 pdated and at first boot running android 6 recognized my SD and enabled it by itself, I guess yes, this might be a stock rom's hidden (in your device) function.
whatsapp cant download image after activate adoptable storage
After using partition in sd card like this link
http://forum.xda-developers.com/m4-aqua/general/adoptive-storage-marshmallow-t3421828/page1
All work fine
Hello everyone,
Just wanted to share my personal build based off the latest concept rom, saw that there weren't any active builds for concept so I decided to share my own, nothing fancy, just a few basic features
{
"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"
}
Features:
Code:
Based off latest Sony Concept Firmware- .3657
Full root access- (Rooted with Super SU (2.79) + DM-verity removed + latest busybox (1.26.2))
Deodexed
Removed AOSP core apps- replaced with Google apps- Dialer, Contacts, Messaging
Debloated (Apps can be found in Play Store)
Zipalign
Init.d support in system & kernel + init.d tweaks
Sqlite tweaks
Superuser mod for signature verification
Optimized Qualcomm GPU files
Plus a few other things :)
Disclaimer
Code:
Flash at your own risk, I am not responsible for any data loss, any bricked or dead phones. Always make backups
Instructions:
*** Please make sure your bootloader is unlocked and you are already rooted and running the latest concept rom ***
D5803 only
1) Reboot recovery- TWRP is recommended
2) Wipe the following partitions:
System
Data
Cache
Dalvik
3) Install rom
4) *** Recommended- Install DRM Fix to restore camera functionality here ***
Reboot
Please note first boot may take a long time- be patient
Important- Go to settings-apps-default apps-set Phone to Google Dialer
Screenshots
Downloads
Please note this initial release is a beta, everything should work as intended but you never know
https://www.androidfilehost.com/?fid=745425885120702422
MD5: 3f92a785b954cd7b62b8e362fe4aa271
Coming Soon
Extra debloating + guide
Battery life guide for concept + recommended apps
Feel free to suggest improvements
Credits
Sony Concept Team
@Chainfire
@Ticklefish
@osm0sis
@serajr
@franciscofranco
@DavidMKD
@Androxyde
If I forgot to add you to credits please let me know and I will add ASAP :good:
Please press thanks if you like the rom
.
Debloat Guide
Below is a list of system apps that are potentially safe to remove.
Always make sure to have backups.
My recommended app is Titanium Backup to remove/disable apps.
If you are unsure, try freezing/disabling a few apps to see how things go
Second List- Stats
This is a list of system Sony Data collection /Stats apps. I have been testing these for a day or so and they appear fine to remove but this one is a maybe, please note that I do not use sony apps like keyboard or xperia home, only the xperia email so thse sony apps may/may not be related to those apps. You can always try for yourself and see:
If you are unsure about an app I will do my best to try and figure out what it is. Also if I missed any or if anything needs to be added please let me know :good:
To state the obvious, if you are uninstalling things like stock launchers, keyboards and things, always make sure to have the replacement app set up before you uninstall things
Good Luck
One more
First! ... this ROM is based Stock? Compatible with the model D5833?
Thank you very much for the support
pickandrew said:
First! ... this ROM is based Stock? Compatible with the model D5833?
Thank you very much for the support
Click to expand...
Click to collapse
Hi there,
This is not based off stock, this is based off Sonys Concept Rom, you can find more info here:
https://forum.xda-developers.com/z3-compact/general/sonys-android-concept-marshmallow-t3229536
It's more lightweight than stock and is closer to AOSP, with a few sony features.
I dont have a D5833 so I cannot confirm if this works or not, if you want to try it you can, just make sure to a have a backup ready
Hey there, thanks for this ROM!
I'm on latest Concept with SuperSU 2.79SR3 and Xposed installed. Could I dirty flash your ROM if I uninstall Xposed first? Or should I wipe everything?
What about the camera quality in comparison to stock? Is fisheye effect present?
systemallica said:
Hey there, thanks for this ROM!
I'm on latest Concept with SuperSU 2.79SR3 and Xposed installed. Could I dirty flash your ROM if I uninstall Xposed first? Or should I wipe everything?
Click to expand...
Click to collapse
Clean flash is always recommended to prevent future issues. Best to play safe and do a full wipe :good:
birsir said:
What about the camera quality in comparison to stock? Is fisheye effect present?
Click to expand...
Click to collapse
Camera quality should be same as stock, no fisheye.
This ROM is based off official Sony Concept firmware
Second post updated with debloating list. If you want me to provide explanations for each app I am happy to do so.
As always, make sure to backup before modifying your system., I always recommend Titanium Backup to remove/backup apps.
I have taken system apps down from about +-150 to about 85.
I have also disabled a few extra things that are not on the list like NFC services because I don't use this feature.
Good luck :good:
I get error 7 when installing. I delete this lines in the zip and get error 6. I can' t install the rom! What can i do?
dav6wat said:
I get error 7 when installing. I delete this lines in the zip and get error 6. I can' t install the rom! What can i do?
Click to expand...
Click to collapse
Zip installs fine for me, please can you provide more information? Just saying you get status 7 is not very helpful.
1) Have you tried re-downloading the rom and checking the md5 to make sure it is not corrupted.
2) This has only been tested on D5803, D5833 may not work
Also make sure you are running the latest version of TWRP and that you are already running concept rom and is rooted
22sl22 said:
Zip installs fine for me, please can you provide more information? Just saying you get status 7 is not very helpful.
1) Have you tried re-downloading the rom and checking the md5 to make sure it is not corrupted.
2) This has only been tested on D5803, D5833 may not work
Also make sure you are running the latest version of TWRP and that you are already running concept rom and is rooted
Click to expand...
Click to collapse
My device is D5803 too. I try 2 downloaded rom ams checked md5. Is this the latest TWRP recovery https://dl.twrp.me/z3c/twrp-3.0.2-1-z3c.img.html ?? I think could be the recovery...
may I suggest including DRM restore function?
https://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672
Edit: I saw it's included in OP.
dav6wat said:
I get error 7 when installing. I delete this lines in the zip and get error 6. I can' t install the rom! What can i do?
Click to expand...
Click to collapse
Try redownloading the ROM.
This is the screenshot of the error 7. I' m in Concept 3657, rooted with superSU 2.79, with TWRP 3.0.2-1.
If i edit script in zip file, deleting assets line, and rename file to 220117_Concept_Plus_Beta2.zip, then gives me error 6.
dav6wat said:
This is the screenshot of the error 7. I' m in Concept 3657, rooted with superSU 2.79, with TWRP 3.0.2-1.
If i edit script in zip file, deleting assets line, and rename file to 220117_Concept_Plus_Beta2.zip, then gives me error 6.
Click to expand...
Click to collapse
Have you tried redownloading the rom
---------- Post added at 10:50 AM ---------- Previous post was at 10:48 AM ----------
So I am having Bluetooth issues and when someone is calling me it doesn't display the thing where it says to answer,I need to wait for the person to hang up then call them back.
Could it be because I flashed this ROM over CM12.1?
Have you tried redownloading the rom
Click to expand...
Click to collapse
Yes, I redownloaded 4 times, and same error.
dav6wat said:
Yes, I redownloaded 4 times, and same error.
Click to expand...
Click to collapse
For me sometimes it would work to flash TWRP MultiROM recovery from here:
http://www.dl.myself5.de/aries/MultiROM/TWRP-Multirom-20160606-00-aries.img
If it doesn't want to download then long press on the link and press the last option which should say like "Download connection".
Dinkec27 said:
Have you tried redownloading the rom
---------- Post added at 10:50 AM ---------- Previous post was at 10:48 AM ----------
So I am having Bluetooth issues and when someone is calling me it doesn't display the thing where it says to answer,I need to wait for the person to hang up then call them back.
Could it be because I flashed this ROM over CM12.1?
Click to expand...
Click to collapse
Yes, possibly. As per first post, please make sure you are already running the concept rom and are rooted. Also make sure to set Google Dialer as default dialer
22sl22 said:
Yes, possibly. As per first post, please make sure you are already running the concept rom and are rooted. Also make sure to set Google Dialer as default dialer
Click to expand...
Click to collapse
Oh okay,then I will reflash to concept,root it and install the rom again and I will keep you up to date.
Hello people!
First of all, excuse my lousy English! I'm using the translator.
Well, as soon as I upgraded my A5 (2017) to Nougat I looked for tutorials that would allow me to root to remove the useless apps that Samsung inserts into the device, and install those that are useful but not available to the average user (without root).
Among these is the ViPER4Android FX, which I could not use because of the SELinux (enforcing) native Kernel.
I have found a way to work without having to change the kernel.
What we need?
1. The minimum of prior knowledge.
2. Device with root.
3. Recovery modified. (like TWRP)
4. ViPER4Android FX zip file. (thanks guitardedhero)
5. supolicy zip file.
6. audio_effects.conf file.
7. File manager with root privileges. (like Root Browser)
8. Flash facilitator Application. (like Flashify)
9. Busybox. (like Stericson)
10. Application uninstaller. (like Root Uninstaller)
How to proceed?
1. With the Application Uninstaller remove Adapt Sound and SoundAlive.
2. With the flash facilitator, flash the ViPER4Android FX zip, after supolicy and reboot.
3. When you start, install Busybox.
3. Open the File Manager, navigate to /system/vendor/etc, and rename the audio_effects.conf file to audio_effects.conf.bak.
4. Copy the downloaded file of the same name, and paste it into the folder.
5. Set the -rw-r-r-- permission on the file and reboot.
6. When you start, open the ViPER4Android FX, allow root access and, if prompted, install the driver.
7. Set the settings in the application and enjoy a great sound experience!
Attached is the file with the settings I use. Put it in the ViPER4Android folder, at the root of your storage, and load the perfil in the application.
All merit goes to the people who made it possible by creating files and tutorials. I'm just sharing the information.
Works . Thank you :good:
i have a problem, busybox failed to be installed, can anyone help?
I use busybox in magisk and it's installed
what shoud driver status to be?
How can I know if it is work or not, coz nothing change in the sounds
{
"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"
}
@Dinhodroid
Any help guys
Hi, has somebody tested V4A Fx fully working in A520F nougat? I'm extremely impressed with the audio quality of V4A Fx and I am using it in my Lenovo smartphone. I'm gonna root my A5 device if this is fully working. Appreciate any feedback please. TIA
@am2006 The procedure is described in the post, however I do not use the Magisk, so I do not know if the problem is related to it.
It can be the busybox installation site.
waltermsalomon said:
Hi, has somebody tested V4A Fx fully working in A520F nougat? I'm extremely impressed with the audio quality of V4A Fx and I am using it in my Lenovo smartphone. I'm gonna root my A5 device if this is fully working. Appreciate any feedback please. TIA
Click to expand...
Click to collapse
It works 100%!
Use on my A5 with Nougat.
Dinhodroid said:
@am2006 The procedure is described in the post, however I do not use the Magisk, so I do not know if the problem is related to it.
It can be the busybox installation site.
Click to expand...
Click to collapse
please show me your driver status to compare
am2006 said:
please show me your driver status to compare
Click to expand...
Click to collapse
attached
EDIT SOLUTION:
replacing the audio_effects.conf file in system/etc worked
hi all
can anyone please help me? i am using a samsung galaxy A5 2017 SM520F but with marshmallow
. https://imgur.com/gallery/buIa0
i have installed viper4android and it is enabled and everything seems good, execpt it never processes. i have tried with google play music and also the samsung music player, but it always says "Processing: No" in the driver status.
any ideas?
superjase said:
EDIT SOLUTION:
replacing the audio_effects.conf file in system/etc worked
hi all
can anyone please help me? i am using a samsung galaxy A5 2017 SM520F but with marshmallow
. https://imgur.com/gallery/buIa0
i have installed viper4android and it is enabled and everything seems good, execpt it never processes. i have tried with google play music and also the samsung music player, but it always says "Processing: No" in the driver status.
any ideas?
Click to expand...
Click to collapse
Try this: https://forum.xda-developers.com/oneplus-3t/themes/v4a-fix-processing-using-magisk-t3572819
Dinhodroid said:
It works 100%!
Use on my A5 with Nougat.
Click to expand...
Click to collapse
Thanks. Working perfectly on my A5. Phone speaker volume is a little low but works just amazingly on my skullcandy earphones.
It works 100% on A7 2017 (SM-A720F) THANKS!
Does this work on A3 Nougat?
pmajci said:
Does this work on A3 Nougat?
Click to expand...
Click to collapse
Yes.
dj_gilquirino said:
It works 100% on A7 2017 (SM-A720F) THANKS!
Click to expand...
Click to collapse
I need detailed tutorials on this. I need help. Thanks. I have A7 2017 too.
İ couldnt install the Busybox too.
am2006 said:
i have a problem, busybox failed to be installed, can anyone help?
I use busybox in magisk and it's installed
what shoud driver status to be?
How can I know if it is work or not, coz nothing change in the sounds
Click to expand...
Click to collapse
Hello, İ couldnt install the Busybox too. I think the problem is Magisk. cuz you and me are using the magisk for root. We had same problem. Any solution for us guys? Just failed to Busybox install..
---------- Post added at 09:35 AM ---------- Previous post was at 09:32 AM ----------
dj_gilquirino said:
It works 100% on A7 2017 (SM-A720F) THANKS!
Click to expand...
Click to collapse
which root are you using dude?(supersu or magisk?) Did you follow the guide step by step?
turkishield said:
Hello, İ couldnt install the Busybox too. I think the problem is Magisk. cuz you and me are using the magisk for root. We had same problem. Any solution for us guys? Just failed to Busybox install..
---------- Post added at 09:35 AM ---------- Previous post was at 09:32 AM ----------
which root are you using dude?(supersu or magisk?) Did you follow the guide step by step?
Click to expand...
Click to collapse
I use magisk, bro.
to bypass the busybox problem, flash this instead.
https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
dj_gilquirino said:
I use magisk, bro.
to bypass the busybox problem, flash this instead.
https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
Click to expand...
Click to collapse
im using magisk too..im sure i followed the guide step by step. i couldnt work viper4android i almost get crazy do you have any advice ?
Hi, I cannot get Viper4A working on my A5 after the latest nougat update. It says that busybox is not properly installed. Could someone help me fix this? TIA
Update - I got it 100% working by reflashing ViPER4Android FX and supolicy.