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
TWRP Recovery
For Galaxy Ace
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
BUGS:
If you have found a bug, please consider posting it here.
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
SPECIAL NOTE:
This is the first build of TWRP and may have some unknown bugs. I take no responsibility of your devices. This is "testing" phase (for some days only). Help in testing if you wish to otherwise stay away until a final release. Don't post back here that: "You destroyed my phone", "You are cheating", "You are playing with my device".
One more thing, we are using androidarmv6 sources and if you are asking for help on IRC channel mentioned above then please mention there that: "we are not using CM or OMNI sources, we are using androidarmv6 sources".
CREDITS:
TeamWin: For this awesome open-source recovery.
androidarmv6 team: To make all these possible.
Me: For compiling it for Galaxy Ace.
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes.
DOWNLOAD:
http://www.upload.ee/files/3991497/recovery.img.html
INSTALLATION / UPDATING:
-From the above download link, you'll get a 'recovery.img' file.
-Put that file at the root of sdcard (means, not in any folder)
-Now, open Terminal Emulator and give this command:
Code:
su
You'll be asked to grant superuser permissions, grant them.
-Now, give this command:
Code:
flash_image recoveryonly /sdcard/recovery.img
And wait for 2-3 seconds until it jumps to a new line. Now, close Terminal Emulator.
-Now, normally reboot to recovery and enjoy new recovery!
About the current build:
STABLE
Nice job. Is it working on Cm9?
Sent from my GT-S5830 using xda app-developers app
aurisltu said:
Nice job. Is it working on Cm9?
Sent from my GT-S5830 using xda app-developers app
Click to expand...
Click to collapse
I think, I should remind you: Recovery is independent of ROM.
It can flash everything which the new kitkat update-binary allow.
If anything fails to flash, just replace /META-INF/com/google/android/update-binary file inside that zip from cm11 or omni4.4 and it will flash.
well im using this recovery for a while and its responding better than the normal recovery , plus the other features in it , thanks for you great work
keep it up
sent from my kitkat ACE
works great, but if formatting or installing and you accidentaly bump the back button it stops what it is doing, can also corrupt the partition, installs ALL roms from cm9 through to cm11 and all scripts/mods install too,, thanks for this version,, i didnt like the other versions they were a yuck colour, i like the black and gray theme
I just had some look today on your device's development forum and found that @Mardon has already made this recovery for your device (Because, I was confused as I didn't receive a single THANK on any of my posts).
Please note that my TWRP has no relation with @Mardon's TWRP. He has used omniarmv6 sources while I've used official omni sources and the androidarmv6 sources.
I've worked hard enough and researched on everything and have made this recovery. This build is the closest one to an official build unlike little buggy build of @Mardon: Bad colors (not official colors), maybe brightness settings are missing, maybe you can't flash some zips with that recovery, etc.
And...ofcourse, you won't be able to flash stock rom using this recovery because it uses samsung's crappy rfs.
Here's something I need you guys to test:
[ROOT]TWRP Coordinator
It's a newly released app (released just before 10-15 minutes) by TeamWin.
I just need a report if everything's working as it should or not.
WARNING: Don't use the option to update TWRP because we are using an unofficial build. Other than that, everything should work but the app is still BETA...Try at your own risk.
What to do?
-Install my TWRP.
-Remember, app needs root.
-Then, start using app's features and report here if found any bugs.
Your report would be appreciated! Thanks.
Thanks Bro for the recovery.
Bhargav97 said:
Here's something I need you guys to test:
[ROOT]TWRP Coordinator
It's a newly released app (released just before 10-15 minutes) by TeamWin.
I just need a report if everything's working as it should or not.
WARNING: Don't use the option to update TWRP because we are using an unofficial build. Other than that, everything should work but the app is still BETA...Try at your own risk.
What to do?
-Install my TWRP.
-Remember, app needs root.
-Then, start using app's features and report here if found any bugs.
Your report would be appreciated! Thanks.
Click to expand...
Click to collapse
Bhargav97 said:
Here's something I need you guys to test:
[ROOT]TWRP Coordinator
It's a newly released app (released just before 10-15 minutes) by TeamWin.
I just need a report if everything's working as it should or not.
WARNING: Don't use the option to update TWRP because we are using an unofficial build. Other than that, everything should work but the app is still BETA...Try at your own risk.
What to do?
-Install my TWRP.
-Remember, app needs root.
-Then, start using app's features and report here if found any bugs.
Your report would be appreciated! Thanks.
Click to expand...
Click to collapse
Work fine bro.. good job.. :fingers-crossed:
Thanks for this recovery, really works great, with CM9 too!
Bhargav97 said:
DOWNLOAD:
http://www.upload.ee/files/3991497/recovery.img.html
INSTALLATION / UPDATING:
-From the above download link, you'll get a 'recovery.img' file.
-Put that file at the root of sdcard (means, not in any folder)
-Now, open Terminal Emulator and give this command:
Code:
su
You'll be asked to grant superuser permissions, grant them.
-Now, give this command:
Code:
flash_image recoveryonly /sdcard/recovery.img
And wait for 2-3 seconds until it jumps to a new line. Now, close Terminal Emulator.
-Now, normally reboot to recovery and enjoy new recovery!
Click to expand...
Click to collapse
I follow the above steps, but nothing happens.I am on same recovery as before using the above steps.BTW thanks for recovery. I am currently using AOSP GingerBread 2.3.7 [COOPER] V3 by SpaceCaker (http://forum.xda-developers.com/showthread.php?t=2375459)
Bhargav97 said:
Code:
flash_image recoveryonly /sdcard/recovery.img
And wait for 2-3 seconds until it jumps to a new line. Now, close Terminal Emulator.
-Now, normally reboot to recovery and enjoy new recovery!
Click to expand...
Click to collapse
not working ... failed with error: -1
GalaxyAce User said:
I follow the above steps, but nothing happens.I am on same recovery as before using the above steps.BTW thanks for recovery. I am currently using AOSP GingerBread 2.3.7 [COOPER] V3 by SpaceCaker (http://forum.xda-developers.com/showthread.php?t=2375459)
Click to expand...
Click to collapse
Busybox is needed for flash_image command to work. If you are using any Stock Based ROM, I doubt you have Busybox. If you can't manage to get it done this way (I don't get, why?) then you can replace recovery.img inside any recovery flashable zip file (of recovery, i.e. CWM-x.x.x.x.zip) from the one given in the link of first post. Now flash that zip file using your current recovery.
kjub6 said:
not working ... failed with error: -1
Click to expand...
Click to collapse
What I said above, also applies to you.
Thank you
Installed over Mardon's latest version as I was having issues with his (failure to flash certain files etc). Will test over next while and report if I find any issues.
Thanks again.
S.
sdembiske said:
Installed over Mardon's latest version as I was having issues with his (failure to flash certain files etc). Will test over next while and report if I find any issues.
Thanks again.
S.
Click to expand...
Click to collapse
it´s not compatible with android 4.4. but it´s working great with CM9/10/10.x, for kitkat roms you need the latest TWRP or CWM
Thank you ...
Viper The Ripper said:
it´s not compatible with android 4.4. but it´s working great with CM9/10/10.x, for kitkat roms you need the latest TWRP or CWM
Click to expand...
Click to collapse
Yes, found that out - neither this nor Mardon's TWRP version worked on Mardon''s CM11 latest. Took the recovery.image file out of CWM-6.0.5.3-cooper and flashed it using terminal command:
su
flash_image recoveryonly /sdcard/recovery.img
Worked like a charm and all's well now. Would like to know though what settings you recommend on SuperchargerV6 on Mardon's CM 11 with your patch for it installed - have not successfully managed to get it past the Samsung boot screen at 50% Supercharged the two times I have tried.
Thanks again, Steve
Link to dowload
Hi Bhargav97,
I don't found link for to dowload, it's possible that can u send me this link?
Many thaks!
NOTE:
This post is/was only relevant for users of the original modded stock recovery for YP2. For the newer & better TWRP recovery for YotaPhone 2 installing unsigned packages such as Xposed framework is not an issue.
Please note that the Xposed version below is outdated, Xposed alpha 4 is available. See Xposed for Lollipop thread.
Old post content:
Not exactly a proper development thread, but posting it here anyway because of the relation with the modded recovery, ad the slightly technical angle.
Xposed framework for Lollipop allows you to install modules that tweak/change many aspects of Android. It's pretty powerful as it can hook into existing software and change it's functionality. The version referred to in this post is an alpha version.
Therefore:
Warning: I recommend you don't install this unless you're a nerd. It's not yet stable, and may cause trouble (such as boot-loops).
Also: by the time you read this there may be newer versions, so read the Xposed thread for updates.
Background
The modded recovery image allows to install software signed by either Yota Devices (such as ota update zips) or signed with testkeys, but it does not allow to flash UNsigned zips. Many flashable zips are signed with testkeys (like SuperSU) but rovo89's Xposed flashable zip for LP in the current 20150430 version are unsigned, so we can't flash them as-is.
Flashing it anyway:
There's two ways: the harder and slightly educational way (useful for e.g. when new Xposed versions are released) and the lazy but convenient way.
1) Signing the Xposed framework zip yourself:
You need:
- signapk.jar plus test key and certificate
Get SignApk.jar from somewhere (build it from AOSP source, or download a zip from this thread (I used zipaligner 1.2, linux). This zip contains other stuff, but we need testkey.pk8, testkey.x509.pem and signapk.jar
- Xposed framework zip for LP 5.0 (xposed-sdk21-arm-20150430.zip) from the official thread from here
- java environment (JDK or JRE)
To sign the file put all files in one dir (including xposed-sdk21-arm-20150430.zip) and run:
Code:
java -jar signapk.jar -w testkey.x509.pem testkey.pk8 xposed-sdk21-arm-20150430.zip xposed-sdk21-arm-20150430_signed.zip
You just created xposed-sdk21-arm-20150430_signed.zip that you can flash.
2) Using a pre-Signed zipfile:
I attached a testkey-signed version of rovo89's file xposed-sdk21-arm-20150430.zip to this post for convenience, so you can skip the steps above.
Steps to install the Xposed framework for LP
1) put device in fastboot/download mode and boot the modded recovery image (see recovery thread)
2) choose "apply update from ADB" from recovery menu
Code:
adb sideload <yourpath>/xposed-sdk21-arm-20150430_signed.zip
3) reboot
4) choose allow 'unknown sources' in settings->security
5) copy the file XposedInstaller_3.0-alpha2.apk to your phone (or scan the QR code on the Xposed page to download this file to your phone directly.
6) use a file manager (like ES File Explorer, or the built-in Cabinet) to browse to and open XposedInstaller_3.0-alpha2.apk and install it.
Now you can download Xposed modules through the Xposed Installer app. I tried GravityBox [LP] (make sure you select the right version!) to change the launcher grid to 5x5 instead of 4x4. After a reboot that worked. I'm not saying that using GravityBox is safe, they warn that it may cause trouble with non-standard ROM's (such as ours).
Please not that I can't/won't provide any support for Xposed itself, please see the relevant Xposed threads for that.
Credits:
rovo89, author of the Xposed Framework
nice one, many thanks
Does anyone have then latest version please that's signed for this device
Sent from my YD201 using Tapatalk
read the start topic good, every thing you need is in there with links
Gojira-r32 said:
read the start topic good, every thing you need is in there with links
Click to expand...
Click to collapse
Which version of xposed is for yotaphone I see a few different versions on the xposed thread. Link From the op
Sent from my YD201 using Tapatalk
I used xposed-v68-sdk21-arm.zip just two days ago, and signed it myself according to the instructions.
It seems to play well, at least for two days
I just booted TWRP and sideloaded it, I never flashed the TWRP.
Had a little mess getting the driver to install in windows, when TWRP sideloads, it had a new identity in the device manager and I was unable to make accept the drivers I had. So I made a little manual edit in the .inf file from the yotaphone flashtool package, and then was able to load the driver needed. Google was my friend, but I can paste the change here later if someone want it.
Those who are using xposed do you notice any long freeze on the epd and reboots.
Sent from my YD201 using Tapatalk
adamo86 said:
Those who are using xposed do you notice any long freeze on the epd and reboots.
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
Nope. I am running latest Xposed framework with gravitybox and youtube adaway. No crashes or freezes, but the battery life does fluctuate quite a bit sometimes. But I think that that is because of Lollipop.
No issues with xposed here either. Running alpha4 I believe.
Installed but not active.. That's what i get! Why is thaT?
Thanks!
I signed the last version of xposed using the method in the first post, and flashed (file attached) using TWRP. no issues so far.
no need to say, make sure you backup first!
Bootloop
I have accidentally flashed the xposed-sdk21-arm-20150430_signed.zip...so my phone stuck in bootloop. How can I uninstall it?
Wanderess said:
I have accidentally flashed the xposed-sdk21-arm-20150430_signed.zip...so my phone stuck in bootloop. How can I uninstall it?
Click to expand...
Click to collapse
SOLVED. Stock rom (4.4.3 HK) flashed with Yota Flasher. After this everything went smoothly.
Oficial Xposed running with no problems, well just one named Lollipop
Jeopardy said:
Nope. I am running latest Xposed framework with gravitybox and youtube adaway. No crashes or freezes, but the battery life does fluctuate quite a bit sometimes. But I think that that is because of Lollipop.
Click to expand...
Click to collapse
The same with me, Lollipop because using the EPD is so much better, otherwise I would happily be on KitKat, battery life on Lollipop is awfull, I also have the Xposed installed the official one with no problems, running some Modules to prevent battery from draining as much as possible in this Google Sucking Lollipop...
Hey guys, i quite unfortunately own a galaxy a8 (a800i). It has almost no dev support. After rooting my phone, i tried converting an app to system(through limk2sd). It did but when i rebooted my phone the app disappeared! Had to manually locate the system files (yes they were there, including the apk) and delete them.
Again,tried it with titanium backup, didnt work out.
Also tried moving the folders manually and i took care to set the correct permissions, the app just wouldnt appear.
At last, after deleting all the system app data and files again, i finally placed the apk with correct permissions in the/system/app folder and rebooted my phone. The app was there but it was force closing.
I tried doing this with 4 different apps, to no avail.
I run stock firmware.
(please note- Although a800F and A800i have same hardware, a800i will not support the others custom recovery, root methods,kernels etc.)
Any devs who might be interested in this? Id be glad.
You need to create a folder with the same name as the apk and push the folder to system app.
Then put apk in the folder with same name
Sent from my SM-G903F using Tapatalk
LastStandingDroid said:
You need to create a folder with the same name as the apk and push the folder to system app.
Then put apk in the folder with same name
Sent from my SM-G903F using Tapatalk
Click to expand...
Click to collapse
Tried that too, been working on this since 2 days. Nothing seems to work. I have never encountered an error like this before on any other of my devices. All the pre installed system apps are odexed, and the one im trying is not, for obvious reasons. Do you think it has got something to do with the error?
abhinavparasher said:
Tried that too, been working on this since 2 days. Nothing seems to work. I have never encountered an error like this before on any other of my devices. All the pre installed system apps are odexed, and the one im trying is not, for obvious reasons. Do you think it has got something to do with the error?
Click to expand...
Click to collapse
Hmm missing Libs? Or the odex file itself?
Sent from my SM-G903F using Tapatalk
LastStandingDroid said:
Hmm missing Libs? Or the odex file itself?
Sent from my SM-G903F using Tapatalk
Click to expand...
Click to collapse
No, the lib and the .dex file of the user app im trying to move to system is intact, all im trying to ask is that do you think the system is not accepting the converted app because it has a .dex instead of the regular .odex file which is the case with all system apps?
This assumption might be wild, but considering that i have never faced such an issue before in 10-12 android devices that i have owned in the past, it might be of some use.
abhinavparasher said:
No, the lib and the .dex file of the user app im trying to move to system is intact, all im trying to ask is that do you think the system is not accepting the converted app because it has a .dex instead of the regular .odex file which is the case with all system apps?
This assumption might be wild, but considering that i have never faced such an issue before in 10-12 android devices that i have owned in the past, it might be of some use.
Click to expand...
Click to collapse
Has nothing do do with it, if it's a "user app" as long if the app has all needed files in correct folder it should run. it should be working if it doesn't it might be any issue that the app won't run while in system/app
Sent from my SM-G903F using Tapatalk
So for now, we havnt arrive to any conclusion. All apps break if they are converted to system apps. Tried to do it via TB/Link2sd/various other tools and manually. App components are present in /system/app including the apk and lib, but the app wont appear anywhere on the phone.
abhinavparasher said:
So for now, we havnt arrive to any conclusion. All apps break if they are converted to system apps. Tried to do it via TB/Link2sd/various other tools and manually. App components are present in /system/app including the apk and lib, but the app wont appear anywhere on the phone.
Click to expand...
Click to collapse
That's because it has to be placed inside a folder with the same name as the app
Like /system/app/viper/viper.apk
It can't be /system/app/viper/base.apk
Also libs should be in
System/app/viper/lib/arm/*****.so
Hope this issue helps
Sent from my SM-G903F using Tapatalk
i did try this before. tried it again. It doesnt work. I was extremely careful with directries, app names, libs and permissions.
Like ive said iv done this countless times before on other devices, and it has always worked.
Something else i would like to mention- Thought the app shortcut doesnt appear anywhere, whenever i open the apk file (on my sd card) it says "do you want to update the app" which means the app is actually already installed. I click yes and the app is installed, app icon returns.
I open application manager and open up this app's settings. I get the option of "Uninstall updates" instead of uninstall apps which proves the first time i moved to system, the app became a system app but it disappeared. If i click uninstall updates, the app disappears again. If i try to integrate update with link2sd the app disappears any ways.
There is just no reason for this to happen! So basically im stuck with a phone which barely got a root method, doesnt have a custom recovery, has a enforcing kernel, and doesnt allow me to move apps to /system.
Do you think it might be possible to "flash" the app zip file via a custom recovery? (if we get one for a800i lol)
abhinavparasher said:
i did try this before. tried it again. It doesnt work. I was extremely careful with directries, app names, libs and permissions.
Like ive said iv done this countless times before on other devices, and it has always worked.
Something else i would like to mention- Thought the app shortcut doesnt appear anywhere, whenever i open the apk file (on my sd card) it says "do you want to update the app" which means the app is actually already installed. I click yes and the app is installed, app icon returns.
I open application manager and open up this app's settings. I get the option of "Uninstall updates" instead of uninstall apps which proves the first time i moved to system, the app became a system app but it disappeared. If i click uninstall updates, the app disappears again. If i try to integrate update with link2sd the app disappears any ways.
There is just no reason for this to happen! So basically im stuck with a phone which barely got a root method, doesnt have a custom recovery, has a enforcing kernel, and doesnt allow me to move apps to /system.
Do you think it might be possible to "flash" the app zip file via a custom recovery? (if we get one for a800i lol)
Click to expand...
Click to collapse
Well to be honest I did face same issue with Samsung s health I'm not sure what causes it, can be system related or something.
Don't you have spacex kernel which is set to permissive?
Sent from my SM-G903F using Tapatalk
The only difference is that it happens with me for every app lol.
I did hear about it but im pretty sure its for a800F. Anything related to a800F causes a bootloop in a800i. Someone on the forum tried the spacex kernel. Do you think you can make it compatible somehow?
If nothing works i might just compile a kernel with always_enforce set to false. Then i should be able to change the policy to permissive with seteneforce 0 command.
abhinavparasher said:
The only difference is that it happens with me for every app lol.
I did hear about it but im pretty sure its for a800F. Anything related to a800F causes a bootloop in a800i. Someone on the forum tried the spacex kernel. Do you think you can make it compatible somehow?
If nothing works i might just compile a kernel with always_enforce set to false. Then i should be able to change the policy to permissive with seteneforce 0 command.
Click to expand...
Click to collapse
Are you the dude that's going to test twrp?
I have built a permissive kernel for this device also.
You are welcome to try it.
Sure il try that too. Permissive kernel is something that many of us need. Infact i was gonna make it. Thanks for the effort!
You can pass me the flashable tar file. In the meanwhile, il test the recovery and get back to you.
abhinavparasher said:
Sure il try that too. Permissive kernel is something that many of us need. Infact i was gonna make it. Thanks for the effort!
You can pass me the flashable tar file. In the meanwhile, il test the recovery and get back to you.
Click to expand...
Click to collapse
Here you go, flash with odin or extract the boot.img from the archive and flash with TWRP.
SM-A800I_A800IXXU2AOL2 _boot
ashyx said:
Here you go, flash with odin or extract the boot.img from the archive and flash with TWRP.
SM-A800I_A800IXXU2AOL2 _boot
Click to expand...
Click to collapse
The kernel works perfectly! Root+ selinux set to permissive. Flashed the boot.img with the twrp recovery provided by @ashyx . The recovery as well as the kernel work with no issue whatsoever. The problem with the wifi did not occur this time. Must be related to the old kernel i flashed, it somehow changed the build.prop everytime i flashed something (Including the recovery)
Anyways, now we know that the kernel as well as the recovery works as it should.
I think you should make the post official, recovery as well as root+selinux set to permissive.
Thanks!
abhinavparasher said:
The kernel works perfectly! Root+ selinux set to permissive. Flashed the boot.img with the twrp recovery provided by @ashyx . The recovery as well as the kernel work with no issue whatsoever. The problem with the wifi did not occur this time. Must be related to the old kernel i flashed, it somehow changed the build.prop everytime i flashed something (Including the recovery)
Anyways, now we know that the kernel as well as the recovery works as it should.
I think you should make the post official, recovery as well as root+selinux set to permissive.
Thanks!
Click to expand...
Click to collapse
Released on XDA in Development section: http://forum.xda-developers.com/sam.../kernel-permissive-ll-5-11-kernel-sm-t3312817
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
:bump:
abhinavparasher said:
:bump:
Click to expand...
Click to collapse
Tried flashing your apps with twrp?
Sent from my SM-G903F using Tapatalk
LastStandingDroid said:
Tried flashing your apps with twrp?
Sent from my SM-G903F using Tapatalk
Click to expand...
Click to collapse
Yes, thats the only thing that works. This issue really garners my interest as i have never seen this happening before.
As the title states, I want to make it get help making or have someone make(lol) a flash able zip to install hosts file of my choosing to /system/etc
Have you tried adaway? Only issue ive had is Google adverts on shopping listings.
Good idea though, but you'd need to update constantly.
Adaway is way more practical.
You need to use magisk, either a module or adaway with systemless hosts enabled in magisk manager.
^this!
dladz said:
Have you tried adaway? Only issue ive had is Google adverts on shopping listings.
Good idea though, but you'd need to update constantly.
Adaway is way more practical.
Click to expand...
Click to collapse
Lossyx said:
You need to use magisk, either a module or adaway with systemless hosts enabled in magisk manager.
Click to expand...
Click to collapse
galaxys said:
^this!
Click to expand...
Click to collapse
Adaway does not work for, even using systemless mode with magisk. I have an older twrp flashable zip that works for Oero and older but don't know how to update it to work with Android 10+
jamescable said:
Adaway does not work for, even using systemless mode with magisk. I have an older twrp flashable zip that works for Oero and older but don't know how to update it to work with Android 10+
Click to expand...
Click to collapse
That's just not true buddy, I'm using it now.
I have zero ads...what version have you got installed??
dladz said:
That's just not true buddy, I'm using it now.
I have zero ads...what version have you got installed??
Click to expand...
Click to collapse
I've tried version 4.03 all the way to newer version. The newer version doesn't work because I get not enough space which IS wrong because I would even delete apps from /system and /product to ALLOW more space just in case
jamescable said:
I've tried version 4.03 all the way to newer version. The newer version doesn't work because I get not enough space which IS wrong because I would even delete apps from /system and /product to ALLOW more space just in case
Click to expand...
Click to collapse
Your don't have enough space because you're not using systemless mate, no other reason.
I'm currently on 4.38
Everybody using xXx using using it, everybody who's rooted is probably using it
dladz said:
Your don't have enough space because you're not using systemless mate, no other reason.
I'm currently on 4.38
Everybody using xXx using using it, everybody who's rooted is probably using it
Click to expand...
Click to collapse
Maybe it's because I am on custom rom RR
jamescable said:
Maybe it's because I am on custom rom RR
Click to expand...
Click to collapse
Ahhh buddy, this is why you explain what operating system you're on, what firmware when asking about a problem, especially when it seems odd to others.
This question should be asked in the RR thread, as it's not relevant anywhere else.
I've never used RR but anything I suggest is going to be futile because of the fact that you're running RR.
For example, Titanium does not work for me on Carbon, simply would not see root so I couldn't restore a thing.
The advice I've provided in regards to what needs to be done in magisk to get adaway working is accurate..
For RR id have thought that it would be the same, now I don't think that's the case.
See what they say in the RR thread mate.
jamescable said:
Adaway does not work for, even using systemless mode with magisk. I have an older twrp flashable zip that works for Oero and older but don't know how to update it to work with Android 10+
Click to expand...
Click to collapse
jamescable said:
I've tried version 4.03 all the way to newer version. The newer version doesn't work because I get not enough space which IS wrong because I would even delete apps from /system and /product to ALLOW more space just in case
Click to expand...
Click to collapse
You can't delete them, it's impossible. All devices launched with Android 10 and dynamic partitions have read only system, vendor, product etc and zero free space is by design. That's why magisk is the only option.
Tell your custom rom dev to reserve free space and allow R/W for system when compiling the ROM, that's the only way to directly modify the system.
Systemless hosts does work on custom ROMs, I have tried it myself. After enabling systemless hosts, reboot, then open adaway and try again.
^there you have it!
galaxys said:
^there you have it!
Click to expand...
Click to collapse
Not really. No one paid attention to the title. Update the flashable zip so we can just flash a hosts file of our choice and no apps needed
jamescable said:
Not really. No one paid attention to the title. Update the flashable zip so we can just flash a hosts file of our choice and no apps needed
Click to expand...
Click to collapse
It will need to be updated pal
dladz said:
It will need to be updated pal
Click to expand...
Click to collapse
Yes, and it's called Energized Protection or whatever adblock module in manager. Take the source (as reference), edit hosts and zip it up.
It's pointless to update the zip because whatever installation method it has won't work, only a module will work which is basically creating a whole new zip.
Lossyx said:
Yes, and it's called Energized Protection or whatever adblock module in manager. Take the source (as reference), edit hosts and zip it up.
It's pointless to update the zip because whatever installation method it has won't work, only a module will work which is basically creating a whole new zip.
Click to expand...
Click to collapse
My point was, that the hosts change, it will need to continually need to be updated.
Counterintuitive.
dladz said:
My point was, that the hosts change, it will need to continually need to be updated.
Counterintuitive.
Click to expand...
Click to collapse
Not really. I used that SAME zip for 4 years and had no ads system wide. No ads in apps, youtube, chrome, etc never updated
jamescable said:
Not really. I used that SAME zip for 4 years and had no ads system wide. No ads in apps, youtube, chrome, etc never updated
Click to expand...
Click to collapse
I see, well good for you..
I've also used this method and they do slip through, that happened in a lot under 4 years???
Either way I can't help with this.
So, not possible to flash a hosts file to /system_root/system/etc/ ? It seems that everytime I flash the file it get overwritten at boot.
jaheaga said:
So, not possible to flash a hosts file to /system_root/system/etc/ ? It seems that everytime I flash the file it get overwritten at boot.
Click to expand...
Click to collapse
It doesn't get overwritten because it doesn't modify anything in the first place. It's not possible to modify the system on stock software. Either magisk or VPN based adblocker like Blokada is your option.