Hello Guys,
to keep the other Thread clean i thought lets create a new Thread where we discuss and share our Progress in Rooting the new Android 6.0.1 MM Firmware.
Here is the latest Information about Root Status for LB/UB
6.0.1 ROM for LB/UB
Prerooted, ByeSELinux, RIC Defeat and Recovery included
LB/UB supported [Windows/Flashable]
Wolfbreak said:
Hey guys i present you RecRoot v4.
Please report back if it works!
Instructions
You need to have Root already and a Windows PC or working Recovery
Run install.bat on Windows and connect Phone or flash in your already working Recovery to keep Root
The Windows Variant only installs Recovery
Features
New TWRP 3.0.2 Recovery from shoey63
ByeSELinux
RIC Defeat
Fixed sqsh mount in Script
Recovery uses its own Busybox now
Updated Busybox to 1.24.2
SuperSU 2.71 in System Mode
Download
Download RecRoot Combined v4 for Android 6.0.1 Marshmallow [all MM Firmwares supported]
Credits
serajr for Scripts
shoey63 for Recovery
NUT for his Scripts
zxz0O0 for ByeSELinux and RIC Defeat
Chainfire for SuperSU
Click to expand...
Click to collapse
Custom Stock Kernel with Recovery included [UB only]
shoey63 said:
Ok guys with Unlocked Bootloaders
Here is the latest iteration of a rootable boot.img for mm-beta https://www.androidfilehost.com/?fid=24459283995297395
You know the drill:-
- Rename to boot.img
- Flash via Fastboot
- Enter recovery
- Flash a Systemless SuperSU eg: BETA-SuperSU-v2.68-20160228150503.zip
- Reboot.
FIXED
- Black Camera
- Root apps hanging while waiting for Supersu to grant permission
- RIC. Big thanks to @Gustavo RD78 for working this out :good:
Note
- The first boot may take some time, and give the impression that you are in a bootloop. Just wait and it will boot up normally eventually.
- Recovery is working, if you have Problems look here
Enjoy fully functional root on MM-Beta
Click to expand...
Click to collapse
So you guys are able to run recovery on unlocked bootloader?
I ve got now root and rw access with kingroot and camera working so i gess at least i got the correct boot.img running
Any help please
Enviado desde mi D6603 mediante Tapatalk
juanpirulo said:
So you guys are able to run recovery on unlocked bootloader?
I vevgot know root and rw access with kingroot and camera working so i gess at less i got the correct boot.img running
Any help please
Enviado desde mi D6603 mediante Tapatalk
Click to expand...
Click to collapse
Unfortunetly i only have locked Bootloader but i didnt understand your Question either, sorry.
Edit: Understand it, see under this Post.
juanpirulo said:
So you guys are able to run recovery on unlocked bootloader?
Click to expand...
Click to collapse
No
Does any Z3 Recovery even work with MM yet? Locked Bootloader we will have to wait for [NUT] but im asking about Unlocked Bootloader.
Yes there is a recovery for unlocked bootloader for z3 running on mm. I flash the shoey recovery before till l i had to come back again to lollipop because i ve got a bootloop trying diferent things to get root and system rw. But now i try the new method by shoey but recovery its not working
juanpirulo said:
Yes there is a recovery for unlocked bootloader for z3 running on mm. I flash the shoey recovery before till l i had to come back again to lollipop because i ve got a bootloop trying diferent things to get root and system rw. But now i try the new method by shoey but recovery its not working
Click to expand...
Click to collapse
Ok. Im sure shoey63 will fix it as soon as possible.
@shoey63
I think we need a fix for unlocked Bootloader Recovery.
Updated the byselinux attachment in my post here:
http://forum.xda-developers.com/showpost.php?p=65852374&postcount=406
zxz0O0 said:
Updated the byselinux attachment in my post here:
http://forum.xda-developers.com/showpost.php?p=65852374&postcount=406
Click to expand...
Click to collapse
Congrats my friend, you just rock!! \m/
Device booted up as it should, but root.
Edit: Root seems to be ok, but system mountable as r/w! ric?
Can someone create a flasheable zip of the beta MM for UB? I have tried to download to many times the backup from MEGA but when I try to extract the backup, it says " Unexpected end of file".
serajr said:
Edit: Root seems to be ok, but system mountable as r/w! ric?
Click to expand...
Click to collapse
For system mount rw try my RICDefeat flashable zip: https://github.com/dosomder/SonyRICDefeat
If you have root you can also run the script from /data/local/tmp
Or easier step is:
unzip update-binary to /data/local/tmp
copy RICDefeat.zip to /data/local/tmp
Code:
su
cd /data/local/tmp
chmod 777 update-binary
./update-binary 3 1 /data/local/tmp/RICDefeat.zip
serajr said:
Congrats my friend, you just rock!! \m/
Device booted up as it should, but root.
Edit: Root seems to be ok, but system mountable as r/w! ric?
Click to expand...
Click to collapse
have you try ricdefeat?
zxz0O0 said:
Updated the byselinux attachment in my post here:
http://forum.xda-developers.com/showpost.php?p=65852374&postcount=406
Click to expand...
Click to collapse
I confirm Root works now but System cant be mounted RW in Root Explorer for Example.
zxz0O0 said:
For system mount rw try my RICDefeat flashable zip: https://github.com/dosomder/SonyRICDefeat
If you have root you can also run the script from /data/local/tmp
Click to expand...
Click to collapse
F*** yeah!! Thank you so much!!! \m/
Just to speed up things, used this one!
Proof:
zxz0O0 said:
For system mount rw try my RICDefeat flashable zip: https://github.com/dosomder/SonyRICDefeat
If you have root you can also run the script from /data/local/tmp
Or easier step is:
unzip update-binary to /data/local/tmp
copy RICDefeat.zip to /data/local/tmp
Code:
su
cd /data/local/tmp
chmod 777 update-binary
./update-binary 3 1 /data/local/tmp/RICDefeat.zip
Click to expand...
Click to collapse
so in order to do a flashable zip for z3 with the ftf i am doing it will work if i add to the flashable the supersu the ricdefeat and byserlinux zips. cheers
I am trying to flash Xposed before loosing recovery after reboot...
EDIT - flashing xposed-v80-sdk23-arm without problem, wiped cache/dalvik, reboot ok, Android is optimizing ))
EDIT2 - Xposed framework active and working, supersu and rw access as well.. F*cking GOOD JOB!!! guys...
---------- Post added at 20:30 ---------- Previous post was at 20:24 ----------
juanpirulo said:
so in order to do a flashable zip for z3 with the ftf i am doing it will work if i add to the flashable the supersu the ricdefeat and byserlinux zips. cheers
Click to expand...
Click to collapse
Yes.... hopefully we are getting some sort of recovery, although it is tough work
Maybe some sort of Flashify could work before we get real recovery... @[NUT]
It is a f*cking happiest day as smartphone user ... I have resisted over couple of years before getting my first smartphone (ok I had Samsung Galaxy2 Mini before, but it is not smart ....), and now happy that we have rooted M (and if sh*t not happens, it will be easy to root official Z3 Android M)... So I don't have to sell my lovely renewed Z3...
ondrejvaroscak said:
I am trying to flash Xposed before loosing recovery after reboot...
EDIT - flashing xposed-v80-sdk23-arm without problem, wiped cache/dalvik, reboot ok, Android is optimizing ))
---------- Post added at 20:30 ---------- Previous post was at 20:24 ----------
Yes.... hopefully we are getting some sort of recovery, although it is tough work
Maybe some sort of Flashify could work before we get real recovery... @[NUT]
Click to expand...
Click to collapse
you have the link for mm xposed? or its the same for lollipop? so i can integrated in flashable prerooted?
juanpirulo said:
you have the link for mm xposed? or its the same for lollipop? so i can integrated in flashable prerooted?
Click to expand...
Click to collapse
The do 2 version, one with xposed and one without - not everybody wants xposed..
xposed is the same version as for Lollipop, just sdk23 (Lollipop is sdk21 for 5.0 and sdk22 for 5.1)
http://forum.xda-developers.com/showthread.php?t=3034811
Awesome! Great Job. I'll just wait a little time to do this!
Sorry for asking of it is asked already but if we flash this on locked bl we have root also ?
Sorry just waked up ^^
Edit:
Yes read it works also on locked bl
Great job RXS bro @Wolfbreak and the cooperating DEVS
Related
Hello Everyone.
Yesterday, I updated my "Global" Z1 firmware to Android 4.3 and then {Of course} I had no root. I already had a TA backup from 4.2 (534) and already un/relocked the bootloader so I am not worried about warranty. So I tried something to get Full root on Locked bootloader.
What I basically did is that I unlocked the bootloader, turned on USB debugging, downloaded doomkernel (Made by @DooMLoRD) and then in fastboot I wrote the command:
Code:
fastboot boot boot.img
Then it restarted and booted doomkernel once (fast boot filename.img makes the phone boot that kernel once) and then flashed the latest SuperSU zip using TWRP recovery (VOL Down) and then went to Advanced → Fix Permissions. Then tried mounting /system as R/W but with no success. So I then flashed doomkernel using the following fastboot command:
Code:
fastboot flash boot boot.img
and then installed the latest XZDualRecovery by @[NUT] and then I had 4 recoveries So I flashed stock kernel and XZDualRecovery wasn't uninstalled, So what I did is that I flashed the SuperSU zip again (using TWRP) and then booted up.
In the first boot, I couldn't mount /system as R/W but I restarted for some reason. and tried to mount as R/W and it worked!
So I relocked my bootloader (by restoring the TA) and now I have full root on TOTALLY STOCK 4.3 Locked bootloader :victory:
Now, when I go to /system/etc/init.d I find a file named "99SuperSUDaemon" and I remember reading somewhere that init.d has something to do with what should work on boot (other than system booting things, cuz I only see that file). So maybe that fixed the "Partial root" problem. Don't know where it came from, but it works :highfive:
Just thought that it might be good to share some info with others, might be useful for people who doesn't want to use ftf's of other places like someone in MEA (me) doesn't want to use UK or US or any other ftf cuz of more bloatware.
Regards,
~J2C
May I ask you how you can verified if you have a Full Root or Semi Root?
Well, I have been removing system apps and I can mount /system as R/W.
If there's a way I can check, please tell me how.
Edit: I actually don't know what does "Semi Root" mean.
Regards,
~J2C
That was allready told here, with links to the description.
http://forum.xda-developers.com/showthread.php?t=2588331
Just2Cause said:
Edit: I actually don't know what does "Semi Root" mean.
Click to expand...
Click to collapse
Not Full Root. Half and Half.
eclyptos said:
Not Full Root. Half and Half.
Click to expand...
Click to collapse
Yes, I have full root.
In case if you're on 4.2 and you can OTA to 4.3 (and you have root) try to copy the file 99SuperSUDaemon to /system/etc/init.d and then reboot, uninstall dual recovery, update to 4.3 OTA and check if you have full root. If you DO have full root, then you can install XZDualRecovery again and enjoy android.
Edit: uploaded the file, unzip (NOTE: it's NOT a flashable zip!) and copy it to /system/etc/init.d and give it permissions rwsr-xr-x
Regards,
~J2C
Just2Cause said:
Yes, I have full root.
In case if you're on 4.2 and you can OTA to 4.3 (and you have root) try to copy the file 99SuperSUDaemon to /system/etc/init.d and then reboot, uninstall dual recovery, update to 4.3 OTA and check if you have full root. If you DO have full root, then you can install XZDualRecovery again and enjoy android.
Edit: uploaded the file, unzip (NOTE: it's NOT a flashable zip!) and copy it to /system/etc/init.d and give it permissions rwsr-xr-x
Regards,
~J2C
Click to expand...
Click to collapse
Could you please explain step by step? I mean for example when fid you install dual recovery?
Sent from my C6903 using Tapatalk
Just2Cause said:
In case if you're on 4.2 and you can OTA to 4.3 (and you have root) try to copy the file 99SuperSUDaemon to /system/etc/init.d and then reboot, uninstall dual recovery, update to 4.3 OTA and check if you have full root. If you DO have full root, then you can install XZDualRecovery again and enjoy android.
Click to expand...
Click to collapse
I do not use OTA, I don't have it. So I have to find a different way. I can only update to 4.3 from recovery or flashtool.
ArashMiniStar said:
Could you please explain step by step? I mean for example when fid you install dual recovery?
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
I installed dual recovery after flashing doomkernel
eclyptos said:
I do not use OTA, I don't have it. So I have to find a different way. I can only update to 4.3 from recovery or flashtool.
Click to expand...
Click to collapse
I can go to cwm and create a flashable zip from there and give it to you if you want
@eclyptos
I know you didn't ask for a 4.3 flashable zip but here it is:
Update.zip
I don't know if something needs to be removed from the zip, but all I did is that I wen to cwm and clicked on "Clone ROM to update.zip" and then uploaded it to google drive.
Regards,
~J2C
Which rom it's exactly in the zip file? Stock?
eclyptos said:
Which rom it's exactly in the zip file? Stock?
Click to expand...
Click to collapse
Yes, Global stock.
But I removed some apps that I don't want/use (most of them are extensions for twitter and flickr and such things) and I added some apps.
Regards,
~J2C
Root for locked bootloader but need to be unlock-able?!
If the BL is unlockable then it is useless to say it is for locked bootloader, if it's lock it's lock.
Once it is unlocked user can flash a pre rooted rom or kernel...
babylonbwoy said:
Root for locked bootloader but need to be unlock-able?!
If the BL is unlockable then it is useless to say it is for locked bootloader, if it's lock it's lock.
Once it is unlocked user can flash a pre rooted rom or kernel...
Click to expand...
Click to collapse
Can you try this for me? You'll find attached zip containing the file in the original post in page 1.
Just2Cause said:
In case if you're on 4.2 and you can OTA to 4.3 (and you have root) try to copy the file 99SuperSUDaemon to /system/etc/init.d and then reboot, uninstall dual recovery, update to 4.3 OTA and check if you have full root. If you DO have full root, then you can install XZDualRecovery again and enjoy android.
Edit: uploaded the file, unzip (NOTE: it's NOT a flashable zip!) and copy it to /system/etc/init.d and give it permissions rwsr-xr-x
Regards,
~J2C
Click to expand...
Click to collapse
Works!
I don't have init.d folder but I gained full root as well as my bionz is intact....
The hot new security update is live, and you maybe want some root love without flashing custom kernel.
(Stock Image here : https://developers.google.com/android/nexus/images#volantis)
Handy modified root compatible boot image for the latest stock image MRA58N. Pure stock kernel modified from the stock images.
You have two choices:
The traditional root in system, which breaks OTA functionality.
(It's more stable now)
New "systemless" approach, which means the root stuffs are only in DATA and BOOT, the system will stay intact and it will accept OTAs.
(Note that this method is still in beta stage according to CF)
Instructions:
System:
Unzip system-root.zip, flash the boot.img through fastboot
Flash SuperSU 2.52
Systemless:
Be sure you haven't used any other root method(like the one above), if you've rooted with other methods, please re-flash your system back to pure stock
Unzip systemless-root.zip, flash the boot.img through fastboot
Download SuperSU-v2.56-20151030013730.zip in this thread, and flash it through TWRP
Important!! Please choose "Do not install SuperSU" when reboot in TWRP if appears.
When a new OTA appears I can just apply it and it will work? Do I keep root or do I have to reroot it again?
Are the attached zip files for the wifi model only?
I have this Kernel:
3.10.40-g909db78
[email protected] #1
Fri Aug 28 21:16:30 UTC 2015
Is this a stock one?
And with method shall I use to get rooted MRA58N?
Jeltel said:
When a new OTA appears I can just apply it and it will work? Do I keep root or do I have to reroot it again?
Click to expand...
Click to collapse
You can revert to stock boot and stock recovery to apply OTA
corkiejp said:
Are the attached zip files for the wifi model only?
Click to expand...
Click to collapse
Yes, I can make a LTE compatible version though.
sejmand said:
I have this Kernel:
3.10.40-g909db78
[email protected] #1
Fri Aug 28 21:16:30 UTC 2015
Is this a stock one?
And with method shall I use to get rooted MRA58N?
Click to expand...
Click to collapse
Yes, and yes
topjohnwu said:
You can revert to stock boot and stock recovery to apply OTA
Yes, I can make a LTE compatible version though.
Yes, and yes
Click to expand...
Click to collapse
A LTE compatible version would be great!!!
topjohnwu said:
You can revert to stock boot and stock recovery to apply OTA
Click to expand...
Click to collapse
So that's a no
I flashed factory image MRA58N (system gets encrypted, because it wasn't under MRA58K)
then twrp
then systemless-root (boot.img)
then superuser 2.56.....
EVERYTHING WORKS FINE:
encrypted with root!
how to flash boot.img (command for flashing)
topjohnwu said:
The hot new security update is live, and you maybe want some root love without flashing custom kernel.
(Stock Image here : https://developers.google.com/android/nexus/images#volantis)
Handy modified root compatible boot image for the latest stock image MRA58N. Pure stock kernel modified from the stock images.
You have two choices:
The traditional root in system, which breaks OTA functionality.
(It's more stable now)
New "systemless" approach, which means the root stuffs are only in DATA and BOOT, the system will stay intact and it will accept OTAs.
(Note that this method is still in beta stage according to CF)
Instructions:
System:
Unzip system-root.zip, flash the boot.img through fastboot
Flash SuperSU 2.52
Systemless:
Be sure you haven't used any other root method(like the one above), if you've rooted with other methods, please re-flash your system back to pure stock
Unzip systemless-root.zip, flash the boot.img through fastboot
Download SuperSU-v2.56-20151030013730.zip in this thread, and flash it through TWRP
Important!! Please choose "Do not install SuperSU" when reboot in TWRP if appears.
Click to expand...
Click to collapse
how to flash boot.img for system less (partition ?)
Lightnyboy said:
how to flash boot.img for system less (partition ?)
Click to expand...
Click to collapse
Unzip systemless-root.zip which will give you a "boot.img" file.
Then while in fastboot
"fastboot flash boot boot.img"
Anyone have the boot files for LTE yet?
Nice. Could you add the link to CF original post in systemless root.
thebrainkafka said:
Nice. Could you add the link to CF original post in systemless root.
Click to expand...
Click to collapse
topjohnwu said:
[*]Download SuperSU-v2.56-20151030013730.zip in this thread, and flash it through TWRP
[*]Important!! Please choose "Do not install SuperSU" when reboot in TWRP if appears.
Click to expand...
Click to collapse
Already linked? Click on "this thread" above!
Updated for LTE... Sorry for the late update.
Also looks like rovo89 just put up xposed for marshmallow in his xposed for lollipop thread. Yes!
xposed marshmallow
topjohnwu said:
Updated for LTE... Sorry for the late update.
Click to expand...
Click to collapse
Thanks for the modified boot images for LTE, I linked back here from my thread in Q&A forum.
have problems getting it to work...
am on MRA58N stock.
My exact steps.
adb reboot bootloader
Device reboots to bootloader.
fastboot flash boot boot.img (extracted from volantisg-mra58n-boot-systemless.zip)
fastboot boot twrp.img (extracted from https://dl.twrp.me/flounder/twrp-2.8.7.1-flounder.img)
From here, I manage to get into TWRP but they are asking for a PIN. I had to cancel and mounted an external USB storage and manage to flash SuperSU-v2.56-20151030013730.zip successfully. Rebooting after and not installing the the SuperSU that TWRP prompts.
After rebooting, I still don't have root. What did I do wrong?
madbat99 said:
Also looks like rovo89 just put up xposed for marshmallow in his xposed for lollipop thread. Yes!
xposed marshmallow
Click to expand...
Click to collapse
I haven't run N version yet as my N9 is finally working without lags/reboots. But, the lure of the close all recent apps button (and very successful experience with xposed/gravity box on N5 after a year) in GB was too great. It works beautifully!
This may seem off-topic, but since root is required, maybe readers can allow exception.
Sent from my Nexus 9 using Tapatalk
chesterchen said:
have problems getting it to work...
am on MRA58N stock.
My exact steps.
adb reboot bootloader
Device reboots to bootloader.
fastboot flash boot boot.img (extracted from volantisg-mra58n-boot-systemless.zip)
fastboot boot twrp.img (extracted from https://dl.twrp.me/flounder/twrp-2.8.7.1-flounder.img)
From here, I manage to get into TWRP but they are asking for a PIN. I had to cancel and mounted an external USB storage and manage to flash SuperSU-v2.56-20151030013730.zip successfully. Rebooting after and not installing the the SuperSU that TWRP prompts.
After rebooting, I still don't have root. What did I do wrong?
Click to expand...
Click to collapse
You don't need to extract twrp.img, you should flash the full image "twrp-2.8.7.1-flounder.img".
That version should not ask for PIN anymore.
Note: system-less is still experimental
If I want to switch from the systemless root to regular system modified root, are there specific cleanup actions to take?
Thanks!
maximumentropy said:
If I want to switch from the systemless root to regular system modified root, are there specific cleanup actions to take?
Thanks!
Click to expand...
Click to collapse
Reflash the stock image then you're good
Hi Friends, here is my latest contribution for the Z1 Compact community, hope you find it useful
D5503_Customized DE_1279-6978_14.6.A.1.236 PREROOTED for Sony Xperia Z1 Compact done with PRFCreator.
What you get:
Flashable Zip File - for Updating your rom with custom recovery (TWRP). This is rooted with SuperSu (2.46) and comes with latest
XZDualRecovery (2. 8.23) bundled.
Install:
1. Download file
2. Copy flashable-prerooted-signed.zip to your sdcard
3. Boot to recovery (USE TWRP NOT Philz!!!!! If PhilzTouch Recovery used, you WILL loose Root!!!) and install flashable-prerooted-signed.zip
4. Reboot to system
Download:
ZIPFILE: flashable-prerooted-signed.zip
MD5: c37aece6d7479156b21d5ee39af68049
SHA1: 455664ebe9f49a870421831a95d79d679c6c7d49
TESTS: I have tested the flashable.zip as descriped below to ensure the rom is fully working as expected.
CONDITIONS:
1. Flash over running and fully functional Lollipop 5.1.1 (14.6.A.1.216) with XZDualRecovery 2.8.21. Bootloader is LOCKED, no xposed framework installed.
RESULTS:
1. Flashing the Rom - Works. After Flash with XZDualRecovery 2.8.21. No Errors in XZ Logwindow
2. Root Check: Testet with: Root Checker (fro mFree Android Tools, joeykrim, and Burrows Apps): No Problems, all apps show full root is present.
3. Remove System Apps: Testet with: SD Maid Pro, System App Remover (Jumobile, TopDev): Works too, im able to remove system apps without any errors.
4. Install Xposed Framework v78 SDK22: Works, no Bootloops.
5. Install and use of XperiaXposed (LP) latest lolipop version from original xda thread: Installation and modul activation works
- Modding User Interface (More Homesceens, gestures (swiping down for Quicksettings, Up App drawer, roud edges, additional quick settings) - Works.
- Xperia Home: (Hide Apps, Widges scalable, labels). Works
- Media: Volume Keys to skipping tracks, camerabutton start/stop. Works.
- Power Menu: Edit some of the options. Works
6. XPrivacy. Installation, Modul activation works. After reboot (no bootloops) xprivacy works like expected. No Problems with that
Thx to zxz0O0 for the PRFCreator.
can i proceed with fresh install ?
Sure but untested.
dirty flashed it over .216, flashed xposed v78 at the same time - works excellent, xprivacy was active all the time :good:
BS86 said:
dirty flashed it over .216, flashed xposed v78 at the same time - works excellent, xprivacy was active all the time :good:
Click to expand...
Click to collapse
Nice to know, i have removed xposed before i flashed cuz i was afraid of bootloops
Hi guys,who tested the zip,with fresh install?
Sent from my D5503 using Tapatalk
hosein_824 said:
Hi guys,who tested the zip,with fresh install?
Sent from my D5503 using Tapatalk
Click to expand...
Click to collapse
now testing...
no bootloops or problems so far!
what's the difference to 14.6.A.1.216?
I can't find an update log on Sony's page
ThreeMMM said:
Nice to know, i have removed xposed before i flashed cuz i was afraid of bootloops
Click to expand...
Click to collapse
For that, I always do a backup in twrp before flashing
If it loops, I go back to backup and then do it step by step
Sent from my Sony Z1 compact using a Tardis
Im doning the same, but i dont like to waste time if something failed
Flashed the firmware using recovery, now I'm unrooted. No more recovery either. Any ideas?
HalNeinThousand said:
Flashed the firmware using recovery, now I'm unrooted. No more recovery either. Any ideas?
Click to expand...
Click to collapse
Did you flash with Philz Touch Recovery? Then this was the culprit.
I did this two times and lost root and recovery as you
The recommended recovery to use is TRWP.
tramp20 said:
Did you flash with Philz Touch Recovery? Then this was the culprit.
I did this two times and lost root and recovery as you
The recommended recovery to use is TRWP.
Click to expand...
Click to collapse
Is there any way to re-try without having to wipe and downgrade? I don't want to unlock my bootloader and lose features either.
HalNeinThousand said:
Is there any way to re-try without having to wipe and downgrade? I don't want to unlock my bootloader and lose features either.
Click to expand...
Click to collapse
I've had the exact same problem. I also had the Philz Touch Recovery installed. After the update both Recovery and Root were gone. I've found an APK called KingRoot to regain Root:
http://forum.xda-developers.com/devdb/project/dl/?id=12586
I've installed it on my Xperia Z1 Compact (there where a few security warnings). Root access will return, but I'm still trying to figure out how to boot into Recovery
Root access will return, but I'm still trying to figure out how to boot into Recovery
Click to expand...
Click to collapse
Hi dude i think you just have to install a recovery again, by the install.bat from your PC (or install.sh for apple) for example from here http://forum.xda-developers.com/showthread.php?t=2261606 and you'll have your recovery back.
Naytmer-fr said:
Hi dude i think you just have to install a recovery again, by the install.bat from your PC (or install.sh for apple) for example from here http://forum.xda-developers.com/showthread.php?t=2261606 and you'll have your recovery back.
Click to expand...
Click to collapse
Thanks!
This did the trick.
First I've replaced KingRoot with SuperSu: http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
And then I've installed DualRecovery: http://forum.xda-developers.com/showthread.php?t=2647480
@elvispr Glad to be helpful !
Yes there even is a xda thread for replacing kingroot with super su http://forum.xda-developers.com/xperia-z/general/super-su-xperia-device-lollipop-easy-t3119006
Coming from 14.6.A.0.368, nothing to report except it changed my "4G" icon for a "LTE" one, everything works fine, i didn't loose root nor recovery !
Thanx to you @ThreeMMM !
Naytmer-fr said:
Coming from 14.6.A.0.368, nothing to report except it changed my "4G" icon for a "LTE" one, everything works fine, i didn't loose root nor recovery !
Click to expand...
Click to collapse
If your icon has changed that means you've flashed different customization of ROM (ie. you were on CE1, now you're on DE) - but that's not a problem
If someone already did with Philz, can get again Root Permission with Kingroot. It works.
Just flashed, clean install through TWRP, everything working as it should be... Thanks OP!
Steps 1 :
-Be On android 5.1.1 root and recovery ( TWRP )
-Have patience
Steps 2 :
-make a backup of your valuable info .
-optional ( before shutting down the Xperia , delete " android" folder in SDCARD )
-Get In TWRP ( recovery volume button -)
-Make The corresponding Wipe ( for a clean installation, in Wipe , advance , the wipe from top to under to internal storage , NO external storage those down)
I -after install zip pre rooted ( will be delayed a bit )
I -after install zip RICDefeat.Zip
-After, Back and give Reboot system
-this process takes , so patience
-Finish :good:
Sorry For my English jajaja
PD: I work to D5803_23.5.A.0.570_R2D_Latin America Generic_1290-6916
Links: (join link)
RICDefeat.zip: drive.google. com /file/d/0B-qjWcbCuedGczVmN2l6Y0ZsWFk/view
Rom PreRoot: drive.google. com /file/d/0B-qjWcbCuedGbjNxX2VVSmVzeVk/view
++To install TWRP and for full root access you need first install a busybox. (BusyBox On Rails from PlayStore) ++
++Recovery Here http://forum.xda-developers.com/showpost.php?p=66232031&postcount=328 ++
++ This works for both locked and unlocked! you just use the recovery ++
Thanks for reply everybody
Special Thanks: @zxz0O0 For Files To Root :highfive::highfive:
I'm going to try this and come back to share the results, thanks.
Edit. IT WORKS, thank you. Now I have to get recovery.
This release works. Thanks!
Is this for Locked Bootloader or Unlocked Bootloader?
heross said:
Is this for Locked Bootloader or Unlocked Bootloader?
Click to expand...
Click to collapse
This works for both locked and unlocked! you just use the recovery
DestroyeRCo said:
I'm going to try this and come back to share the results, thanks.
Edit. IT WORKS, thank you. Now I have to get recovery.
Click to expand...
Click to collapse
did u use recovery? if yes, let we how to make
Is it okay to install this in Germany? Will I have problems because this ROM is Latin America Generic?
edit
Rom works great in Germany.
I have installed on locked bootloader and root access is ok, but i have no more a recovery. Why? Can i install XZDualRecovery 2.8.26 on this rom?
heross said:
Rom works great in Germany.
I have installed on locked bootloader and root access is ok, but i have no more a recovery. Why? Can i install XZDualRecovery 2.8.26 on this rom?
Click to expand...
Click to collapse
dual recovery doesn't work on 6.0.1, you have to install TWRP
Gracias Amigo, You are the mvp!
root works, in half, try to remove app with titanium backup reboot and app i back
To install TWRP and for full root access you need first install a busybox. (BusyBox On Rails from PlayStore)
Recovery install here: http://forum.xda-developers.com/showpost.php?p=66232031&postcount=328
you need install busybox
question can you save something to SD Card? I mean example : from TB do backup to SD Card?
pls refresh link
RAZR-MikePL said:
pls refresh link
Click to expand...
Click to collapse
Links work fine
busybox installed, i still do not have full root access
przem16325 said:
busybox installed, i still do not have full root access
Click to expand...
Click to collapse
mmmm :s curious, I have full acces root
I know, tried everything, hmm, flashed from 4.4.4, maybe it's a reason
Hi everyone!
This is a compilation of the steps i took to make Systemless Root + Xposed + Safetynet Check Pass on my Moto X 2014.
This is none of my work, I simply make this thread because I saw many of you asking for it in the Q&A section, so I thought it was better to have a Step by Step Thread.
Magisk is not working properly on our devices right now (if you don't know what this is and want to know: Magisk v6), because of problems with the Motorola's boot image. So the method I used was Suhide by Chainfire (Suhide v0.53), all credits go to him.
You need to have Android 6.0 and TWRP 3.0.2 or Flashfire.
So this is what I did:
1). Unroot, Remove any trace of other versions of Xposed if you have one. I did this but my system partition was too dirty and I couldn't get it to work, so I would totally recommend a clean stock rom, this will avoid many bootloop problems and such. I read that it's not working properly on cm13 so I would also recommend specifically Stock Image. After returning to stock, try a Safetynet Checker to see if you are really on a clean rom.
2). Once on a clean system image, flash the (Systemless Root Enabler) by @glauberlima (Thanks a lot for this), and the latest version of SuperSU.
3). Now flash the latest version of Suhide, please download it from the suhide thread page, as we are not allowed to redistribute his files: Suhide Thread. Files are in the attachments part.
4). Flash the Systemless Xposed v86.2 by @topjohnwu. Its important to flash the v86.2 version, because it's the one working "properly" with suhide.
5).Profit
Suhide automatically hides root for Safetynet so you don't have to do anything more. However, if you want to know how to blacklist another app please go to the Suhide thread for more information.
This should supposedly work on every model, I have an XT1096 on a XT1095 ROM and its working perfect, the only bug I encountered was the ART cache not building properly, but that's a suhide problem. Feel Free to ask any questions! Thanks a lot!
It sure reads like will work. I'll try it when I get home. Just to advance, did you test Pokemon Go? It really is the only app that I want to pass...
Do i need to restart the phone in every steps or i can flash all files at once without need to restart?
made everything exactly, except for xposed. safetynet already pointed up my system as non-CTS.
I surrender. f*** pokemon and f*** android pay
live long and prosper to root and xposed!
felipeap said:
It sure reads like will work. I'll try it when I get home. Just to advance, did you test Pokemon Go? It really is the only app that I want to pass...
Click to expand...
Click to collapse
Yup.. Im currently playing
Enviado desde mi XT1095 mediante Tapatalk
yunior597 said:
Do i need to restart the phone in every steps or i can flash all files at once without need to restart?
Click to expand...
Click to collapse
I did it all at once.. But its always recommended to reboot at least in the supersu flash
Enviado desde mi XT1095 mediante Tapatalk
drico_649 said:
made everything exactly, except for xposed. safetynet already pointed up my system as non-CTS.
I surrender. f*** pokemon and f*** android pay
live long and prosper to root and xposed!
Click to expand...
Click to collapse
Maybe you have busybox installed on system.. I went completely back to stock because I had the same problems as you
Enviado desde mi XT1095 mediante Tapatalk
Damn wish I had 6.0
Sent from my SM-J320P using XDA-Developers mobile app
Musa95 said:
Maybe you have busybox installed on system.. I went completely back to stock because I had the same problems as you
Enviado desde mi XT1095 mediante Tapatalk
Click to expand...
Click to collapse
I reinstalled stock ROM all the way (system, boot, recovery, even bootloader) and did a full wipe. started everything from zero. Installed root and suhide, safetynet already knew whats going on. neither lost my time installing xposed. just went back to my old backup with all the things I need.
And all of this just because I wanted to play pokemon go. lol
Musa95 said:
Hi everyone!
This is a compilation of the steps i took to make Systemless Root + Xposed + Safetynet Check Pass on my Moto X 2014......
Click to expand...
Click to collapse
Works perfectly on Stock 6.0 thank you very much!
But i want cm13 on my phone, there is a way to flash superSu in systemless-mode on cm13? I'm continuiung to receive "failure, aborting" during boot.img patch by superSu
Sorry for my bad english
valeriopastore20 said:
Works perfectly on Stock 6.0 thank you very much!
But i want cm13 on my phone, there is a way to flash superSu in systemless-mode on cm13? I'm continuiung to receive "failure, aborting" during boot.img patch by superSu
Sorry for my bad english
Click to expand...
Click to collapse
Its not working right now.. Maybe in future releases of suhide
Enviado desde mi Nexus 6P mediante Tapatalk
drico_649 said:
I reinstalled stock ROM all the way (system, boot, recovery, even bootloader) and did a full wipe. started everything from zero. Installed root and suhide, safetynet already knew whats going on. neither lost my time installing xposed. just went back to my old backup with all the things I need.
And all of this just because I wanted to play pokemon go. lol
Click to expand...
Click to collapse
That's really a shame bro, you should ask for help in the suhide thread, but personally I think that PoGo doesn't worth it lol, better keep root and xposed
Enviado desde mi Nexus 6P mediante Tapatalk
Musa95 said:
That's really a shame bro, you should ask for help in the suhide thread, but personally I think that PoGo doesn't worth it lol, better keep root and xposed
Enviado desde mi Nexus 6P mediante Tapatalk
Click to expand...
Click to collapse
completely agree with u. prefer my root/xposed and other tricks than a game that, at least for me, Lost The fun already. I can play pokémon in a lot of emulators (including a DS one that I bought xD ).
but, thanks for The help and for creating The thread, Will help a lot of people!
Sent from my Moto X using XDA Labs
drico_649 said:
completely agree with u. prefer my root/xposed and other tricks than a game that, at least for me, Lost The fun already. I can play pokémon in a lot of emulators (including a DS one that I bought xD ).
but, thanks for The help and for creating The thread, Will help a lot of people!
Sent from my Moto X using XDA Labs
Click to expand...
Click to collapse
Thanks to you to stop and read!
Enviado desde mi Nexus 6P mediante Tapatalk
I spent the better part of yesterday trying to figure out how this could be applied to CM13.
Clean installation of CM13 followed by unrooting allows it to pass the Safetynet check. The problem comes when trying to install SuperSU in systemless mode. As best as I was able to figure out, SuperSU fails to patch the boot image because the LZMA compression method is used by the current CM13 nightlies, but only GZIP is supported. If somebody is able to successfully re-pack the boot.img file in one of the current nightlies to use entirely GZIP instead of LZMA, I believe the rest of the process could be followed to get systemless root and bypass Safetynet on CM as well as stock.
valeriopastore20 said:
Works perfectly on Stock 6.0 thank you very much!
But i want cm13 on my phone, there is a way to flash superSu in systemless-mode on cm13? I'm continuiung to receive "failure, aborting" during boot.img patch by superSu
Sorry for my bad english
Click to expand...
Click to collapse
anubus45 said:
I spent the better part of yesterday trying to figure out how this could be applied to CM13.
Clean installation of CM13 followed by unrooting allows it to pass the Safetynet check. The problem comes when trying to install SuperSU in systemless mode. As best as I was able to figure out, SuperSU fails to patch the boot image because the LZMA compression method is used by the current CM13 nightlies, but only GZIP is supported. If somebody is able to successfully re-pack the boot.img file in one of the current nightlies to use entirely GZIP instead of LZMA, I believe the rest of the process could be followed to get systemless root and bypass Safetynet on CM as well as stock.
Click to expand...
Click to collapse
I've done it... works perfectly... i can play Pokemon Go
---------- Post added at 12:43 AM ---------- Previous post was at 12:00 AM ----------
Musa95 said:
Hi everyone!
This is a compilation of the steps i took to make Systemless Root + Xposed + Safetynet Check Pass on my Moto X 2014.
This is none of my work, I simply make this thread because I saw many of you asking for it in the Q&A section, so I thought it was better to have a Step by Step Thread.
Click to expand...
Click to collapse
------------------- For cm13 users -----------------------------------------------
First of all i'm sorry for my bad english
Before to follow the thread guide we need to convert the boot.img of the cyanogenmod zip. To do that download the latest cyanogenmod and the tool"Android image kitchen (AIK)" AIK
Now..
Extract AIK and copy the boot.img from cm zip to AIK folder, then drag the boot.img on unpackimg.
Go to split_img folder and change the extension of .lz4 file to ".gz"
Come back and run repackimg
Rename the "new-image" in "boot" and copy and substitute in cm zip.
Copy the cm zip on your device, wipe system and flash cyanogenmod and gapps (if you use them), reboot...
Using a file manager delete the "su" file from System/bin and System/xbin (using root permission enabled in developer options)
Now just follow the main guide
valeriopastore20 said:
I've done it... works perfectly... i can play Pokemon Go
---------- Post added at 12:43 AM ---------- Previous post was at 12:00 AM ----------
------------------- For cm13 users -----------------------------------------------
First of all i'm sorry for my bad english
Before to follow the thread guide we need to convert the boot.img of the cyanogenmod zip. To do that download the latest cyanogenmod and the tool"Android image kitchen (AIK)" AIK
Now..
Extract AIK and copy the boot.img from cm zip to AIK folder, then drag the boot.img on unpackimg.
Go to split_img folder and change the extension of .lz4 file to ".gz"
Come back and run repackimg
Rename the "new-image" in "boot" and copy and substitute in cm zip.
Copy the cm zip on your device, wipe system and flash cyanogenmod and gapps (if you use them), reboot...
Using a file manager delete the "su" file from System/bin and System/xbin (using root permission enabled in developer options)
Now just follow the main guide
Click to expand...
Click to collapse
Perfect. You filled in the missing gap with AIK. I was able to get this working perfectly with CM13. Safetynet check passes, and root is fully functional along with Pokemon Go and Android Pay.
Steps followed from top to bottom:
1: BACKUP BACKUP BACKUP
2: Download latest CM13 nightly
3: Extract boot.img file from zip and split it using "unpackimg.bat" from AIK
4: Rename boot.img-ramdisk.cpio.lz4 to boot.img-ramdisk.cpio.gz and run "repackimg.bat"
5: Replace new boot.img in CM zip file
6: Flash modded CM13 zip file and GApps
7: Enable Root in Dev Options, then full unroot with SuperSU app
8: Flash Systemless root enabler, SR1-SuperSU-v2.78, and SuHide
9: Restore app backups (if applicable)
10: Everything works (so far).
I was able to restore several system backups using Titanium Backup and remove system apps I didn't want without running afoul of the Safetynet checker, so this is quite functional for the moment it looks like.
how do i turn root on? i installed and all but cant find the way to turn root on.
I did all the steps mentioned above, and didn't work.
Still not passing the Safetynet Test. :crying:
Did someone else succeed?
yunior597 said:
how do i turn root on? i installed and all but cant find the way to turn root on.
Click to expand...
Click to collapse
You have to enable Developer Options (Tap "Build Number" 7x times) and then enable it there.
kratuslogan said:
I did all the steps mentioned above, and didn't work.
Still not passing the Safetynet Test. :crying:
Did someone else succeed?
Click to expand...
Click to collapse
I've been wiping the system partition as well beforehand. A good way to go about this is to do one step at a time, and check safetynet between each step. After you do the full unroot, you should be passing it every time, check it between each step after and see if you can find where along the line it's getting broken.