MOD EDIT @gregbradley
Also, users should be aware that Kingo root sends your IMEI to an unknown IP address in china during the root process, you have been warned. For more information read the whole OP here
XPERIA ANDROID 5 LOLLIPOP EASY ROOT :
ALL LOCKED&UNLOCKED BOOTLOADERS.
1-) Copy ALP folder in phone memory.
2-) Settings >Security > Unknown sources make it open. And Settings > Developer Options > USB debugging make it on. (If developer options exist go Settings > About phone and click Build number (7 times))
3-) Install Root.apk Allow all messages.
4-) Install Recovery.apk
5-) Install Busybox.apk
6-) Open KingRoot and click Root button.
MOD EDIT @gregbradley
Also, users should be aware that Kingo root sends your IMEI to an unknown IP address in china during the root process, you have been warned. For more information read the whole OP here
6-) Wait to complete. İf you see a chinese blue button click it. All of messages you will allow.
7-) When you see blue tick symbol or %100 its ok.
Look to the menu KingUser its in here ok. No problem don't open it.
9-) Open busybox and install it. When you see It looks like busybox installed succesfully congratulations message its ok.
10-) Open XZRecovery and click Install Recovery .
11-) Phone will be reboot and recovery will open.
12-) Install > find ALP folder and select SuperSU.zip then swipe and install it.
13-) Complete the install Wipe Cache/Dalvik and reboot the phone.
14-) You can see SuperSU in menu and check with rootchecker your root access.
15-) Everything OK. You can enjoy with your rooted Android 5 lollipop device.
16-) You can uninstall KingRoot, busybox, Xzrecovery app. (won't delete supersu or ndrutils)
PREPARED BY ALPEREN ÇUBUK.
DOWNLOAD LİNK : https://yadi.sk/d/qMsejobDgedBw
MIRROR :
https://app.box.com/s/86e7vlwfmu5z62lo95vu2kfej38uj01q
NOTE: Extract downloaded zip and copy ALP folder your phone memory.
Thanks for the comprehensive guide. For some reason step 11) Getting my D6653 into recovery is not working (Also tried ADB reboot recovery)
Any ideas?
EDIT: After updating BusyBox, and then re-installing the Recovery, it re-started and is now stuck in a bootloop..
EDIT2: The bootloop is very likely related to this (from this post: http://forum.xda-developers.com/showthread.php?t=2261606):
"@vaisakh7 found a busybox updater which seems to be compatible with XZDualRecovery: Busybox On Rails, which installs a version of busybox created by stericson, which leads me to believe his Busybox installer should also install a version which works together with XZDualRecovery.
Either case, be careful with updating busybox as there still is a possibility it will break your ability to enter recovery or even break full root, which means you might not be able to recover from the broken situation. Your best bet is the installer version, using that to break the lock on the system partition and reinstall the correct busybox."
Recommended to NOT update BusyBox
Busybox can never be installed through this process always failed and there is no other option left once busybox installation failed except to reinstall the whole firmware please add the steps to guide for busybox installation too
Does this method null the waranty?
Sent from my Xperia Z3
What's guys.
I've done root on my Moto G5 Plus, everything is fine, except for 2 things.
First, I was unable to make Freedom work, but I've download Root Explorer and everything is good.
Second, is about this thread and Magisk root.
As I play Super Mario Run, there's a opition at Magisk called Madisk Hide.
But it is not working properly, as a press SafetyNet check and I receive a error CTS profile mismatch.
Could someone help with that?
PS: Sorry for my bad english.
I'm getting the same CTS profile mismatch.
Follow Steps :
1. Enable Magisk hide
2. Disable Android Debugging
3. Clear mario app data
It should work.
Mrdeviljv said:
Follow Steps :
1. Enable Magisk hide
2. Disable Android Debugging
3. Clear mario app data
It should work.
Click to expand...
Click to collapse
The problem is the mismatch on Magisk.
I tried that.
I have to download using Apteoide, beucase of root, the game was hide on playstore.
I've already tried that with no sucess.
I can play the game on the first level and tutorial, but when it's download the data, the game doesn't work anymore...
I have the same 'CTS profile mismatch' with Magisk, and Root Uninstaller says "have rooted but have not rw permission in /system" (Or something like that..)
i can't uninstall bloatware, i'm using led apk and other root functions, but uninstaller not working and adfree also fails blocking ads (sorry bad english)
Leodev said:
I have the same 'CTS profile mismatch' with Magisk, and Root Uninstaller says "have rooted but have not rw permission in /system" (Or something like that..)
i can't uninstall bloatware, i'm using led apk and other root functions, but uninstaller not working and adfree also fails blocking ads (sorry bad english)
Click to expand...
Click to collapse
In android n you have to mount system partition in order to remove bloatware follow below steps :
1.install busybox and terminal app
2.issue following command in terminal
Su
Now grant root access to terminal
3.now issue following command
busybox mount -o rw,remount system
That's it now you should be able to remove bloat.make sure to install busybox as mentioned in step 1
Hello there!
I want to show you my way to enable Google Assistant on your Xperia Z5 Compact.
First to say I'm not a developer. I read a lot on XDA and try it sometimes on my own phone. I can't answer you to any specifical questions.
I want to enable the Google Assistant on my Z5C without editing the build.prof. I don't want editing anything of system partition.
I have systemless superSU so I find the following way.
Requiered:
- latest Google App
- Android 7
- systemless root e.g. superSU
Guide:
1. make a script and name it "00set.prop.script" or else
2. write in to the script:
Code:
setprop ro.opa.eligible_device 1;
3. copy the script to /su/su.d/
4. clear all data und cache from Google App
5. reboot phone
6. have fun
If you don't know what you do make a full backup for your own security.
About enable google assistant
How can I do that with magisk? Do you know how? Thanks
zlatkomas said:
How can I do that with magisk? Do you know how? Thanks
Click to expand...
Click to collapse
Place the script in the folder " /magisk/.core/service.d/ ".
Hi,
I recently got my M1 A1 from Elisa, in Estonia(packages says Global Version). I've been looking for a guide to enable camera2 API, and since I'm not interested in root or other functionalities, I figured I could only edit build.prop file in /system with the relevant
Code:
persist.camera.HAL3.enabled=1
line.
My steps so far:
1. Unlock the bootloader.
2.Temporarily boot into TWRP:
Code:
PS C:\platform-tools> .\adb reboot bootloader
PS C:\platform-tools> .\fastboot devices
28833e59 fastboot
PS C:\platform-tools> .\fastboot boot recovery-tissot.img
downloading 'boot.img'...
OKAY [ 0.755s]
booting...
OKAY [ 0.592s]
finished. total time: 1.353s
3. Mount /system from TWRP
4. Try to pull out build.prop:
Code:
PS C:\platform-tools> .\adb pull /system/build.prop c:\platform-tools
adb: error: failed to stat remote object '/system/build.prop': No such file or directory
At this point, I was starting to worry: wrong TWRP, /system was not mounted properly, etc.. But then I tried:
Code:
PS C:\platform-tools> .\adb pull /system/default.prop
/system/default.prop: 1 file pulled. 0.0 MB/s (893 bytes in 0.052s)
...and it worked perfectly:
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
security.perf_harden=1
ro.adb.secure=1
ro.allow.mock.location=0
ro.debuggable=0
ro.oem_unlock_supported=true
ro.zygote=zygote64_32
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
ro.dalvik.vm.native.bridge=0
dalvik.vm.usejit=true
dalvik.vm.usejitprofiles=true
dalvik.vm.dexopt.secondary=true
dalvik.vm.appimageformat=lz4
pm.dexopt.first-boot=quicken
pm.dexopt.boot=verify
pm.dexopt.install=quicken
pm.dexopt.bg-dexopt=speed-profile
pm.dexopt.ab-ota=speed-profile
debug.atrace.tags.enableflags=0
ro.logdumpd.enabled=0
#
# BOOTIMAGE_BUILD_PROPERTIES
#
ro.bootimage.build.date=Wed Jan 10 14:39:53 WIB 2018
ro.bootimage.build.date.utc=1515569993
ro.bootimage.build.fingerprint=xiaomi/tissot/tissot_sprout:8.0.0/OPR1.170623.026/8.1.10:user/release-keys
persist.sys.usb.config=mtp
So, my question: where does that build.prop live or hides? And can default.prop be used instead for the same purposes as build.prop?
What other steps I've tried so far:
- factory reset(twice);
- full firmware flash with MiFlash(and factory reset after);
- different versions of TWRP(best one from here:https://forum.xda-developers.com/showpost.php?p=75357241&postcount=817 )
Oh, and what I've noticed weird is this message, when invoking adb shell:
Code:
PS C:\platform-tools> .\adb shell
linker: error reading config file "/system/etc/ld.config.txt" for "/sbin/busybox" (will use default configuration): error reading file "/system/etc/ld.config.txt": Too many symbolic links encountered
WARNING: linker: error reading config file "/system/etc/ld.config.txt" for "/sbin/busybox" (will use default configuration): error reading file "/system/etc/ld.config.txt": Too many symbolic links encountered
/system/system/build.prop
You should be interested in root in this case, because whenever you mount the system with write privileges which you do, you loose OTAs. Magisk let you to modify the system systemlessly and whenever you receive OTA, you can install it.
sorry but which is the utility of OPR..?
maross said:
You should be interested in root in this case, because whenever you mount the system with write privileges which you do, you loose OTAs. Magisk let you to modify the system systemlessly and whenever you receive OTA, you can install it.
Click to expand...
Click to collapse
I guess I'll just dirty flash new firmwares with MiFlash . Maybe even restore original build.prop, MiFlash, then modify build.prop again. Rooting sometimes affects some apps, i.e. some banking apps won't install, Neflix won't let you download content, and so on.
sidbyron said:
sorry but which is the utility of OPR..?
Click to expand...
Click to collapse
It's just a naming convension for the firmware filename that Xiaomi uses.
quad_bx said:
I guess I'll just dirty flash new firmwares with MiFlash . Maybe even restore original build.prop, MiFlash, then modify build.prop again. Rooting sometimes affects some apps, i.e. some banking apps won't install, Neflix won't let you download content, and so on.
Click to expand...
Click to collapse
Just use Magisk with Magisk hide feature. You will achieve the same with less effort. Btw. direct modification of system will break Safetynet as far as I know, so you won't be able to install Netflix anyway [emoji846]
_mysiak_ said:
Just use Magisk with Magisk hide feature. You will achieve the same with less effort. Btw. direct modification of system will break Safetynet as far as I know, so you won't be able to install Netflix anyway [emoji846]
Click to expand...
Click to collapse
Well, let's take for example TWRP installation.... The official variant does not work on the last Oreo build(internal storage size is seen as 0, can't install). And for Magisk, I could not find a detailed tutorial to follow.
Anyway, let me see if I can find the hidden build.prop and what happens.
quad_bx said:
Anyway, let me see if I can find the hidden build.prop and what happens.
Click to expand...
Click to collapse
So, I've found it. On the plus side, editing it and re-uploading it did not trip SafetyNet. But... camera2 API is not enabled
I've even managed to edit it twice, in system_a and system_b, same result. Rebooting, clearing the app cache for the apps where I wanted to get RAW shooting did not help either.
I confirm build.prop is in /system/system after mounting it with TWRP.
I can pull it, change it, and push it, but nothing actually changes in the phone.
I confirm that going into "adb shell" generates that error.
Issue is: I DON'T WANT to install Magisk, I DON'T WANT to root.
I want auxiliary tele lens exposed to OpenCamera and gCam porting, and I want Whatsapp forced to use HAL1 specifics (as inner Whatsapp camera brakes after enabling Camera2api).
It means to convert this line:
camera.hal1.packagelist=com.skype.raider,com.google.android.talk
To this
camera.hal1.packagelist=com.skype.raider,com.google.android.talk,com.whatsapp
... and nothing more.
To me it sounds stupid to root, installa Magisk and leave the phone unlocked just to tell Whatsapp to use HAL1.
Also for exposing aux camera, it means to turn:
#Expose aux camera for below packages
vendor.camera.aux.packagelist=org.codeaurora.snapcam,com.android.camera,com.huaqin.factory,com.mi.AutoTest
#add by yaoshaorong for Expose aux camera for D2AO-892 for packagelist can't more than 91 byte
vendor.camera.aux.packagelist2=com.android.systemui
to
#Expose aux camera for below packages
vendor.camera.aux.packagelist=org.codeaurora.snapcam,com.android.camera,com.huaqin.factory,com.mi.AutoTest
#add by yaoshaorong for Expose aux camera for D2AO-892 for packagelist can't more than 91 byte
vendor.camera.aux.packagelist2=com.android.systemui,net.sourceforge.opencamera
But it simply doesn't work.
Is this the right file, or do we need to modify something else?
Dm verity and the related error correction changes your modifications back to the stock build.prop
Before following this guide, you'll want to grab the MSM unbricking tool, specifically for this device (not the global or other Oneplus 8 versions). Use it if you brick yourself.
Here's how I got microG to work on my Visible Oneplus 8 running Oxygen OS 11:
Unlock the boot loader and flash Lineage's instantnoodle recovery (The small recovery image ~96MB, not the large rom file)
Reboot into recovery and adb sideload the Magisk zip file, from the recovery's 'Apply Update'.
Follow this guide to enable signature spoofing, but with the following few changes:
Place this specialized hook services file ( 11-hook-services-OxygenOS.jar.dex ) in the same folder as 11-hook-services.jar.dex.
When you get to the `java -jar` command in the guide, do this instead:
Code:
java -jar dexpatcher-1.8.0-beta1.jar -a 11 -M -v -d -o ./ services.jar 11-hook-services-OxygenOS.jar.dex 11core-services.jar.dex
Do not install the microG provided in the guide! But go ahead and install your `spoof_AVDapi30.zip` through magisk as the guide says.
Confirm that signature spoofing is working (you can download Signature Spoofing Checker from F-droid)
Inside the magisk app, search for and install the plugin "microG installer Revived". Reboot.
Grant microG all the permisisons that you can in microG settings' Self-Check.
Tap and install GmsCore.apk located at '/system/priv-app/GmsCore/". You need to do this step even though its already installed because until you do this, it will only be installed as a system app. Doing this installs it as a user app, which fixes the location permission issue (somehow this issue is encountered). If it doesn't fix it right away you may need to reboot.
Open the microG settings again, and give yourself the location settings (and SMS if still needed)
I hope this helps someone. I know I had a lot of frustration because so much that works for other instantnoodles simply doesn't work on this device. Instantnoodle custom roms like lineageOS (as of writing this) and automated patchers like smali and nanodroid don't work, so at least we have this one option.
Ciao @Calebdvn
Trying to apply this fix on OP6 OOS11.1.2.2 but nothing happends
trying the standard method I were stuck at bootlogo, using this file the system volta, but, signature spoofing Is not working
Caould you kindly support me ?