Recently rooted my Z1 using the method outlined here: http://forum.xda-developers.com/showthread.php?t=2784900
It seems as if the process hasn't fully worked - I almost have a "half-rooted device." Root checker apps state the device is rooted, however:
- Busybox does not install
- Cannot find anything to do with/update binaries
- File Manager cannot gain access to write /system
- AdAway will not complete patching the host file (error)
Using SuperSU by the way. Is the only option for me to reflash stock firmware with flashtool, and do the whole thing again?
Cheers in advance.
Carlover1998 said:
Recently rooted my Z1 using the method outlined here: http://forum.xda-developers.com/showthread.php?t=2784900
It seems as if the process hasn't fully worked - I almost have a "half-rooted device." Root checker apps state the device is rooted, however:
- Busybox does not install
- Cannot find anything to do with/update binaries
- File Manager cannot gain access to write /system
- AdAway will not complete patching the host file (error)
Using SuperSU by the way. Is the only option for me to reflash stock firmware with flashtool, and do the whole thing again?
Cheers in advance.
Click to expand...
Click to collapse
try to root it again by using that method
Ben Ling said:
try to root it again by using that method
Click to expand...
Click to collapse
Wow, thanks very much - it worked!
Related
UPDATE: If you're already on an unrooted 10.1.D.0.343 - a new exploit has been found so check out this thread to root it.
After much digging through the threads and the net looking for a working Rooted 10.1.D.0.343 ROM for the SO-02E with no luck I decided to make my own and share it to everyone who own the SO-02E variant from Docomo.
This ROM is fully stock with the exception of having Superuser and XZDualRecovery installed. No default files have been tweaked in anyway.
I made this ROM using the guide from [NUT]
All the scripts were made by [NUT] - I just replaced some files to make XZDualRecovery work for the SO-02E.
I am not a developer or anything - I'm just some guy who loves his SO-02E
I tested this on my SO-02E, upgraded from 10.1.D.0.333 to 10.1.D.0.343 and everything works.
No reboot issue when mounting the system as R/W and no issues booting into recovery.
No data is lost and all apps are retained when upgrading so you should be good - but backup your data just in case.
Prerequisite:
Rooted 10.1.D.0.333
Recovery Installed (e.g. XZDualRecovery)
Installation:
1. Copy SO-02E_10.1.D.0.343_system.zip to your SDCard
2. Flash SO-02E_10.1.D.0.343_stripped.ftf with Flashtool (make sure nothing is ticked)
3. Boot straight into recovery
4. Flash SO-02E_10.1.D.0.343_system.zip
5. Clear cache (optional but it doesn't hurt to)
6. Reboot
7. Profit!!!
Special thanks to [NUT] for getting XZDualRecovery working on the SO-02E
Stock Odexed Files:
(I split SO-02E_10.1.D.0.343_system.zip into two files for download so you need to join them with 7zip and copy the .zip file to the SDCard )
SO-02E_10.1.D.0.343_stripped.ftf
Download
Mirror
SO-02E_10.1.D.0.343_system.zip.7z.001
Download
Mirror
SO-02E_10.1.D.0.343_system.zip.7z.002
Download
Mirror
[MOD]
[MOD] Stock ROM 10.1.D.0.343 Deodexed and zipaligned
Installing this mod will update your 10.1.D.0.343 so it's deodexed and zipaligned.
Prerequisite:
Rooted stock 10.1.D.0.343
Installation:
1. Copy 343.deodex_zipaligned.zip to your SDCard
2. Boot into recovery
3. Flash 343.deodex_zipaligned.zip
4. Clear cache
5. Reboot
6. Profit!!!
343.deodex_zipaligned.zip.7z.001
Download
Mirror
343.deodex_zipaligned.zip.7z.002
Download
Mirror
--------------------------------
[SMALL APP] Serajr Power Toggles - 23 Toggles Set - v1.1 - 10/06/13
Check out this thread for more info
Tweaked for 10.1.D.0.343
Install in Recovery
Download
-----------------------------
Nice to see my guide put to good use, this is exactly why I made it in the first place! :highfive:
Have fun with this release people :good:
Must I join 2 files: "SO-02E_10.1.D.0.343_system.zip.7z.001 and SO-02E_10.1.D.0.343_system.zip.7z.002" before I copy it to SD card?
nak89 said:
Must I join 2 files: "SO-02E_10.1.D.0.343_system.zip.7z.001 and SO-02E_10.1.D.0.343_system.zip.7z.002" before I copy it to SD card?
Click to expand...
Click to collapse
It's my fault for not be more clear - yes you need to join them with 7zip (or whatever program that recognizes 7z formats). From there you'll end up with SO-02E_10.1.D.0.343_system.zip, copy the .zip to the SD and use TWRP or CWM to flash.
I'll update my OP to make it more clear.
nak89 said:
Must I join 2 files: "SO-02E_10.1.D.0.343_system.zip.7z.001 and SO-02E_10.1.D.0.343_system.zip.7z.002" before I copy it to SD card?
Click to expand...
Click to collapse
Yes. Extract both of them together and put it in one folder.
I did it, but I only can upgrade to .343 but it has not root?
nak89 said:
I did it, but I only can upgrade to .343 but it has not root?
Click to expand...
Click to collapse
It does have root. What version were you coming from before? If you're already on an unrooted 10.1.D.0.343 then you'll need to downgrade to 10.1.D.0.333 via Flashtool, root it, install XZDualRecovery, then upgrade to 10.1.D.0.343 as written in the OP.
lancebukkake said:
It does have root. What version were you coming from before? If you're already on an unrooted 10.1.D.0.343 then you'll need to downgrade to 10.1.D.0.333 via Flashtool, root it, install XZDualRecovery, then upgrade to 10.1.D.0.343 as written in the OP.
Click to expand...
Click to collapse
In .333, What tool do you use to root? I'll try it Thanks!
nak89 said:
In .333, What tool do you use to root? I'll try it Thanks!
Click to expand...
Click to collapse
Check out this thread on rooting .333
After you have root you need to install XZDualRecovery.
lancebukkake said:
Check out this thread on rooting .333
After you have root you need to install XZDualRecovery.
Click to expand...
Click to collapse
Thank so much, I had 343 with root + deodex
nak89 said:
Thank so much, I had 343 with root + deodex
Click to expand...
Click to collapse
glad to help :good:
lancebukkake said:
glad to help :good:
Click to expand...
Click to collapse
Why does my Root Explore always force close?
nak89 said:
Why does my Root Explore always force close?
Click to expand...
Click to collapse
hmmm...that's strange. I tested it, with nothing installed except for Root Explorer and it doesn't FC on me. I've tested R/W to system and all is good.
nak89 said:
Why does my Root Explore always force close?
Click to expand...
Click to collapse
Take a look at this thread - this should help.
Nice thread sir..now I can root the Z docomo of my cousin thanks again
i'm on 10.31b.0256 .. what can i do?
tufoz said:
i'm on 10.31b.0256 .. what can i do?
Click to expand...
Click to collapse
if you the easiest root way, go [URL="http://cubeundcube.blogspot.jp/2013/11/xperiarootz-so-02e-so-04e.htm]this linkl[/url], clik the rootkitZ_20131112.zip. I've tried this and works.
Hello, everyone!
TL;DR: You're about to perform a systemless root installation on your phone so make sure you have uninstalled Xposed Framework, uninstalled root, the device's bootloader is unlocked and your phone's boot image is in its untouched stock state. Then boot into TWRP and install SuperSU-v.279-SR3 or newer.
UPDATE 2017-01-19:
- Provided missing bootloader information regarding root. Thanks, @Charlita for the heads-up!
- Moved TL;DR section to the top.
UPDATE 2017-01-15:
- SuperSU-v.279-SR3 learned how to use systemless mode as default flashing method for Motos. This is great news as the installation process now is just a matter of flashing the SuperSU installer. The segmentation fault had been fixed on SR2 and this version also includes that fix.
- Included a TL;DR section.
UPDATE 2016-12-25:
- SuperSU-v.279-SR1 contains a regression bug regarding the "segmentation fault". Skip this version for now. I've already contacted Chainfire.
- suhide: as the Chainfire himself stated, the tool is a losing game so I'm not putting any further effort here.
UPDATE 2016-11-03:
- As of SuperSU-v2.78-SR3 boot image patching works out-of-the-box. Just install it and you're done!
- TWRP version 3.x works as expected.
- Unfortunately, SafetyNet checking fails as Google constantly updates the server-side code.
- WIP: Check if Chainfire's suhide are able to help here.
UPDATE 2016-08-08:
- Added a backup reminder.
- Added flashable zip systemless_root_enabler_by_glauberlima.zip.
After a few days playing with it, I finally managed to perform a systemless root install for our beloved Moto X 2014
Benefits:
- Install OTA updates when they arrive;
- SafetyNet checking will pass so Android Pay can be used (not available in Brazil yet).
Requirements (links below) :
- Android 6 Marshmallow
- Bootloader must be unlocked otherwise you won't be able to root your phone;
- Boot partition must be in its original untouched stock state otherwise, SuperSU installer won't be able to patch it;
- System partition must be untouched as well but a simple uninstall of applications that have changed it should be enough. This step is not mandatory but if your system partition remains changed SafetyNet checking will fail;
- Your device must be unrooted. SuperSU has the option "Completly remove root". Use it;
- If you have Xposed Framework installed, uninstall it;
- You'll need ADB and Fastboot in order to flash stock boot.img if applicable;
- TWRP. Version 3.0.2-2 works just fine. If you prefer 2x series, I highly recommend version 2.8.7.1;
- SuperSU-v2.79-SR3 zip installer (or a newer version). DO NOT TRY AN OLDER VERSION. WILL NOT WORK;
Install guide:
- Make a Nandroid backup first using TWRP;
- Uninstall Xposed Framework if applicable;
- Uninstall SuperSU;
- Connect your device to your computer via USB;
- Reboot into bootloader:
Code:
adb reboot-bootloader
- Restore stock boot partition (you can skip this step if you already been on stock boot):
Code:
fastboot flash boot xt1097_boot_stock_with_may_2016_update.img
VERY IMPORTANT: The binary file boot xt1097_boot_stock_with_may_2016_update.img is device dependent. I have extracted stock boot.img from victara May 2016 update full ROM package and put it here. If you are trying on the other variants, make sure you will use the right image.
- Reboot into Recovery (TWRP);
- Flash the attached zip file systemless_root_enabler_by_glauberlima.zip. This will set both variables SYSTEMLESS=true and BINDSYSTEMXBIN=false. Without these variables set, SuperSU will fail to systemless root the device. Feel free if you want to manually enter the commands in the Command Prompt:
Code:
adb shell "echo SYSTEMLESS=true>/data/.supersu"
adb shell "echo BINDSYSTEMXBIN=false>>/data/.supersu"
- Install SuperSU and reboot system. If the first boot fails, just wait - the second will work I promise you!
- As soon as Android UI shows up you should be systemless rooted;
- Confirm SuperSU is installed by recognizing the green icon on your app drawer;
- Open up any root app you have. The world-famous Superuser permission request dialog should pop-up;
- Install SafetyNet Helper, in order to attest your Android, is passing Google's SafetyNet checking: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Now you should be good. Congrats!
Go ahead and get some systemless apps:
- Systemless Xposed Framework
- Systemless Adaway
This procedure should work for the other variants too - all you need is the original boot.img
If you need any help feel free to ask.
Attached you can find the screenshots taken from my XT1097 after the procedure
Related links:
SuperSU-v2.79-SR3:
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
Latest stable SuperSU:
http://download.chainfire.eu/supersu-stable
Systemless Xposed Framework:
http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Systemless AdAway:
http://forum.xda-developers.com/showthread.php?t=2190753
Material Design Xposed Installer:
http://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
Minimal ADB and Fastboot:
http://forum.xda-developers.com/showthread.php?t=2317790
TWRP for Moto X 2014:
http://forum.xda-developers.com/mot...recovery-twrp-2-8-0-0-touch-recovery-t2911523
Thanks:
@Chainfire
Even if I am on stock I have to flash boot*.img?
Sent from my XT1097 using Tapatalk
rtrotsky said:
Even if I am on stock I have to flash boot*.img?
Sent from my XT1097 using Tapatalk
Click to expand...
Click to collapse
Since your device already has the untouched stock boot you don't need to flash anything.
I seem to be having trouble installing the "Systemless Xposed". It errors out with - ! Failed: Unable to extract zip file!
I have verified "systemless root - ver 2.76" and tried re-downloading the zip. Any thoughts?
jbaumert said:
I seem to be having trouble installing the "Systemless Xposed". It errors out with - ! Failed: Unable to extract zip file!
I have verified "systemless root - ver 2.76" and tried re-downloading the zip. Any thoughts?
Click to expand...
Click to collapse
Could you provide your recovery.log from TWRP so we can see the detailed logging information?
You can pull it from your device by running the following command in command prompt:
Code:
adb shell cat /tmp/recovery.log | clip
This will copy recovery.log contents to the clipboard. Paste it into notepad then save and attach here.
glauberlima said:
Could you provide your recovery.log from TWRP?
You can pull it from your device by running the following command in command prompt:
Code:
adb shell cat /tmp/recovery.log | clip[code]
This will copy contents to the clipboard. Paste it in notepad then save and attach here.[/QUOTE]
This is pretty neat. Given what I read as the requirements am I correct this only works with stock ROM? (and test will only pass on stock).
Click to expand...
Click to collapse
vpxf said:
This is pretty neat. Given what I read as the requirements am I correct this only works with stock ROM? (and test will only pass on stock).
Click to expand...
Click to collapse
Hi @vpxf
The unmodified boot.img is a requirement for SuperSU as it tries to patch the boot image on-the-fly during the install process (by the time you flash it using TWRP). If the image is not in its original state, SuperSU will fail to install in systemless mode.
Regarding your question about custom ROMs compatibility I don't know if the SafetyNet checking will pass/fail. That's a good test to perform.
glauberlima said:
Could you provide your recovery.log from TWRP so we can see the detailed logging information?
You can pull it from your device by running the following command in command prompt:
Code:
adb shell cat /tmp/recovery.log | clip
This will copy recovery.log contents to the clipboard. Paste it into notepad then save and attach here.
Click to expand...
Click to collapse
I've attached the log. I did notice "unzip: zip flags 1 and 8 are not supported".
NOTE: I was able to flash the 85.7 version found in the second post of the "Systemless Xposed" thread. The newest 86.2 is the one giving me troubles.
As glauberlima found out in the other thread, you need to re-zip the xposed installer with 7-zip (that's what i used at least) and the install will work.
bertolehm said:
As glauberlima found out in the other thread, you need to re-zip the xposed installer with 7-zip (that's what i used at least) and the install will work.
Click to expand...
Click to collapse
jbaumert said:
I've attached the log. I did notice "unzip: zip flags 1 and 8 are not supported".
NOTE: I was able to flash the 85.7 version found in the second post of the "Systemless Xposed" thread. The newest 86.2 is the one giving me troubles.
Click to expand...
Click to collapse
As stated by @bertolehm I've discussed in the other posts the exactly same issue with the zip installer you have reported @jbaumert. Take a look at them:
http://forum.xda-developers.com/showpost.php?p=67792193&postcount=1193
http://forum.xda-developers.com/showpost.php?p=67805517&postcount=1233
Regarding your device being systemless rooted check with SafetyNet Helper Sample app. If everything turns green you are good
** Duplicated **
Thanks for the tutorial.
The first boot fails, ok ; but how long is the second boot ?
I wait a long time (around 15 minutes) blocked at the first screent (static moto logo) and I stop it, reboot and reinstall my backup. I panic a little
oyoyl said:
Thanks for the tutorial.
The first boot fails, ok ; but how long is the second boot ?
I wait a long time (around 15 minutes) blocked at the first screent (static moto logo) and I stop it, reboot and reinstall my backup. I panic a little
Click to expand...
Click to collapse
Which variant is your X?
glauberlima said:
Which variant is your X?
Click to expand...
Click to collapse
XT1092
oyoyl said:
XT1092
Click to expand...
Click to collapse
15 minutes... That's definitely too much.
I'm about to update this guide with my new findings so If you don't mind I'd like to suggest you this:
Repeat the steps but this time skip the update to latest version. After the reboot access SuperSU. It should display a message regarding your su needs update. Accept it.
Make sure your nandroid backup is up to date.
Same thing, but it's possible that my boot image is not up to date and I have no other boot backup to test.
I have only a complete backup (boot + system without root), perahps I'll try later with complete restore ...
Thanks
Something went wrong, the root works fine, but when I run the SafetyNet test, I got "CTS profile match: false", I just want to keep the OTA upgrades working, if I did something wrong, is there any way to unroot and do the systemless root again?? Thankss
Hi! Hey, I followed the steps and my MotoX got stuck when rebooting after flashing. I'm trying to enter fastboot with power+Volume down but no luck so far, any idea? I hope you can help me!
oyoyl said:
Same thing, but it's possible that my boot image is not up to date and I have no other boot backup to test.
I have only a complete backup (boot + system without root), perahps I'll try later with complete restore ...
Thanks
Click to expand...
Click to collapse
OK. Just leave a reply by the time you have the result of your test.
guilhermoaraujo said:
Something went wrong, the root works fine, but when I run the SafetyNet test, I got "CTS profile match: false", I just want to keep the OTA upgrades working, if I did something wrong, is there any way to unroot and do the systemless root again?? Thankss
Click to expand...
Click to collapse
One of your installed apps modified system partition. Did you test on a completly stock image?
I have a problem when I go to open SuperSU tells me: SU Binary occupied, so it does not allow me to properly use the magisk manager.
I followed the guide for huawei, I did everything step by step, but nothing has ever given me this message.
How do I fix it?
Same here
I had this 2 but managed to fix it wat version of supersu are u using wat version of magisk r u using also
ditto.
SuperSU Free v2.82 & Magisk v13.3
eonix said:
ditto.
SuperSU Free v2.82 & Magisk v13.3
Click to expand...
Click to collapse
Since Magisk v13, there's no longer any compatibility for SuperSU. If you've flashed Magisk you're rooted with MagiskSU and that's why SuperSU is complaining about the binary being occupied.
You're unfortunately going to have to choose one or the other.
Am using asus zenfone 2 laser ze500kl..I rooted my device and when i booted my phone super su app is installed..but when i open the app it says su binary occupied..root checker app says that the root access is not properly installed...pls help
Vchuz said:
Am using asus zenfone 2 laser ze500kl..I rooted my device and when i booted my phone super su app is installed..but when i open the app it says su binary occupied..root checker app says that the root access is not properly installed...pls help
Click to expand...
Click to collapse
Hi! Had your same problem today with my Asus Zenfone 2 Laser ze500kl. Solved by following the exact steps of this guide, but instead of downloading and installing the suggested SuperSu zip file I found this older SuperSu version, downloaded the zip file, placed it in the internal storage and followed the exact steps of the guide. (For good measure, I did all the steps in the guide again).
Once you reboot your phone, you will be able to update the SuperSu app form the PlayStore to get the latest version. Should work just fine.
Hello everyone,
So I wanted to root my Honor 5c (NEM-L51) under android 7.0, so I have unlocked the bootloader, I have installed a custom recovery compatible with android 7.0 which is twrp-3.1.0-2-hi6250 I think ...
Then I tried to flash the supersu.zip, I had to try several versions because many did not work and indicate "image boot patcher" failure aborting "then I flash a supersu that works but I have the impression that the root has badly installed ...
I explain, first I test with root checker which tells me that everything is fine, but I can not update the binaries su as the supersu app asks me ... I reboot remove , Reinstall the app supersu NOTHING does !! So I wanted to remove the root to reinstall it properly but it does not want to be deleted (root checker still shows the presence of the root) more so I wanted to delete it manually but the file "system / bin / su " and "xbin / su "are not found there is only one su "su" file at the root directory...
Maybe the best method would be to flash the emui stock rom 5.0 but it is not found, and it seems to me that you must also remove the root to avoid any "brick"..
if you have solutions to my questions it would be fine !!!!!
Thank you in advance !!!
Curiosity2000 said:
I explain, first I test with root checker which tells me that everything is fine, but I can not update the binaries su as the supersu app asks me ... I reboot remove , Reinstall the app supersu NOTHING does !! So I wanted to remove the root to reinstall it properly but it does not want to be deleted (root checker still shows the presence of the root) more so I wanted to delete it manually but the file "system / bin / su " and "xbin / su "are not found there is only one su "su" file at the root directory...
Click to expand...
Click to collapse
I have the same problem with the latest stable SuperSU (2.82) that asks me to update the su binary and fails.
As for the su binary not found in /system/bin and /system/xbin it's probably because SuperSU made a systemless root (check this).
And be advised there might be some problem with restoring in the TWRP version you found (see here).
[EDIT]: I was able to update my SuperSU installation by flashing the latest stable version from the official thread with TWRP.
sclarckone said:
I have the same problem with the latest stable SuperSU (2.82) that asks me to update the su binary and fails.
As for the su binary not found in /system/bin and /system/xbin it's probably because SuperSU made a systemless root (check this).
And be advised there might be some problem with restoring in the TWRP version you found (see here).
[EDIT]: I was able to update my SuperSU installation by flashing the latest stable version from the official thread with TWRP.
Click to expand...
Click to collapse
Okay , thanks you for yours answers, I have effectively a supersu systemless I will test yo flash the latest supersu, if it don't work I will remove the su and flash an other twrp or flash the rom stock I think ...
[EDIT] I success to remove the Root systemless with flash the boot.img , but the latest supersu doesnt work for me . I try to install Magisk
[REEDIT] Okay, I success to flash Magisk 13.3 I am root
Stay with magisk, it is better than SuperSU
PalakMi said:
Stay with magisk, it is better than SuperSU
Click to expand...
Click to collapse
Okay thanks you !
Curiosity2000 said:
Okay thanks you !
Click to expand...
Click to collapse
No prob
SM-A520F flashed with Russian (SER) 7.0 A520FXXU2BQH4_A520FOXE2BQG7
Rooted with with SuperSU
Steps followed in TWRP:
1. Factory Reset (To start fresh)
2. Flashed no-verity-no-encrypt_ashyx
3. Format data
4. Flashed SR3-SuperSU-v2.82-SR3-20170813133244.zip
5. Reboot
Root checker shows Rooted.
However, it isnt properly rooted , it seems, because:
1. AdAway shows a *SU Binary Could not be found*
2. ES File Explorer 's Root explorer isn't working: *Sorry, test failed* message pops up.
Any idea how to get properly rooted?
EDIT:
More info: It seems the root is working for certain apps like Droidwall which I use to block internet access.
The system is not properly Writable (has read access only) which is causing the issue with some root apps. So, I guess I need a solution to make the System Writable.. Help?
Hi, I have the same problem on Italy ITV Nougat.
The phone seems to be rooted ("Check Root" give sucessfully rooting), but when I try to delete app from "App Remover Root" it doesn't work and the same if I try to uninstall/delete the apk from ADB.
Any idea?