Develop Bugs

superuser,busybox and mount system

I was going to make a Rom but as we are waiting for 2.1 I saw no point!I did this instead.....
This update.zip should be flashed through a custom recovery!! it will root and install busybox.Also includes a script to mount system.
after obtaining su and pressing allow type mnt in shell or terminal to mount system.
saves having to type mount -o re,remount -t yaffs2 /dev/block/mtdblock3 /system everytime.
Also contains apps2sd which is working (as far as i can see) on a standard kernel!
to turn it on..
in cmd window type
adb shell mnt followed by apps2sd on this will only work if you have a ext2/3 partition BEWARE it may remove your apps so you will need to reinstall them
download...
http://www.multiupload.com/05RYNZXFMX

Does it work with stock kernel?

yes I am using stock kernel from 2.73.405.66

Oh.. great news! I am trying to install busybox for days without any success...
But could you tell us what to do with these scripts ?
Thanks a lot!

i would call it a zipfile, not a script, and looking at it it seems that it should be flashed through the custom recovery image...
btw, will this be suitable to root the final release, once it is out? i suppose it will have ro.secure=0 and therefore boot.img needs to be altered?

it contains no boot.img yet so is useable on any rom i think?
As for the script all it does is mount the system like adb remount but on a standard kernel/rom it will say operation not permitted or something similar, so instead with this update.zip type (in a cmd window) adb shell then mnt
and it will say System mounted OK. Voila the system is mounted to allow such things as apps2sd on,rm <FILE> etc..
Installing it through custom recovery SHOULD install all the parts inside and give permissions.
Have updated first post..

what i meant is will it work on a stock rom with release-keys?
but nevermind, i'll just try when it is there...

i have reflashed my phone with WWE 2.73.405.5 146733 CL#61267 release-keys and yes,it works.
I wouldnt just go flashing the 2.1 update when it arrives though you should look into extracting a rom.zip from RUU and only flash the boot.img and the system.img. Otherwise you could end up with a perfected SPL and never be able to root

have now tried with ALL available release key kernels and confirm it works well.Apart from apps2sd,this is random on what kernels it works.
when 2.1 is released I will edit the standard kernels ro.secure thing and will be available here.

[FIX] Hero Music Volume Standy not working [FIX]

This is a fix for changing volume of media while the screen is off.
from my knowledge this is a bug in all Villain ROM v5.
Step 1:
Download this file
rapidshare.com/files/393135722/hero-keypad.kl
Step 2:
Copy to SD Card and then change to Charge Mode from phone
Step 3:
from adb shell
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
Code:
cp /sdcard/hero-keypad.kl /system/usr/keylayout
Step 4:
Restart Phone
or from adb
Code:
reboot
Goodluck

bulletproof_dav said:
This is a fix for changing volume of media while the screen is off.
from my knowledge this is a bug in all Villain ROM v5.
Step 1:
Download this file
rapidshare.com/files/393135722/hero-keypad.kl
Step 2:
Copy to SD Card and then change to Charge Mode from phone
Step 3:
from adb shell
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
Code:
cp /sdcard/hero-keypad.kl /system/usr/keylayout
Step 4:
Restart Phone
or from adb
Code:
reboot
Goodluck
Click to expand...
Click to collapse
Thanks!

YEESSSSS!!!!!!!!!!
It works. Well done that man. Superb work!

Buletproof, any chance to add option to change song by long press?

update.zip will be nice..
good work..

Very nice
There's also a file "heroc-keypad.kl" in there, which has a similar content. I renamed it and it works too. But the MENU button now doesn't activate the phone only the POWER button does and with the MENU button you can still unlock your phone.

Second the update.zip request. That's the only problem I have with Cronos 1.4.1.
Feeyo - if you can add this fix to 1.5, that'd also be cool.

mikeyd85 said:
Second the update.zip request. That's the only problem I have with Cronos 1.4.1.
Feeyo - if you can add this fix to 1.5, that'd also be cool.
Click to expand...
Click to collapse
http://www.villainrom.co.uk/viewtopic.php?p=12450#p12450 is an update.zip by kendon

doesnt work on cronos 1.4.1. buttons dont work

Sychie, I got it working on Chronos 1.4.1 by using the adb method, although it wouldn't work until I removed some programs first (like teeter).

the update zip works great on superhero with oc kernel. Big thanks! Been missing this feature alot.

now works. i dont know why didnt before.
great!

once flashed the zip, my hero running cronos 1.4.1 freeze after system loads main screen
back to standard until I manage to have adb working :/

[GUIDE] Flash any recovery easily on the phone using flash_image

Background
To update (flash) a recovery image onto your phone allows you to update or replace your recovery environment on your phone. There are a number of ways to flash a new recovery image, some of the more commonly used methods are using a tool such as ROM Manager or using development tools such as Fastboot. There is also a third method using a standalone utility "flash_image" which allows the flashing of recovery using the terminal emulator on the phone.
flash_image is not a new tool, it has been used on Android since the beginning, many custom ROMs include the utility as part of the ROM itself though not all stock ROMs (including the stock ROM on the G2) include it.
Requirements
1. A permanently rooted (with S-OFF) phone
2. The flash_image binary
3, A recovery image that is compatible with your phone and ROM
3. A terminal emulator application on the phone or use of an ADB shell
Overview:
1. Get the flash_image binary and recovery image onto your phone
2. Copy or move the flash image binary to your system and make executable
3. Use flash_image to update your recovery environment
Stage 1: Get flash_image and recovery image on your phone
1. Download the flash_image binary (not needed if you are running a custom ROM that includes this binary)
2. Download the recovery image you wish to use
You can either directly download the files onto your phone or onto your PC and transfer to your phone. Probably the easiest way to do this is to connect your phone to your computer via USB and mount USB storage, then copy the files to your SD Card. Alternatively you can use ADB Push, bluetooth file transfer or several other methods.
Stage 2: Copy or move the flash image binary to your system and make executable
In terminal emulator:
su
mount -o remount, rw /system
cd /sdcard (or wherever you downloaded/copied the file)
cp flash_image /system/bin
cd /system/bin
chmod 777 flash_image
Click to expand...
Click to collapse
Stage 3: use flash_image to update your recovery environment
In terminal emulator:
su (not needed if using the same terminal session used in the steps above)
cd /sdcard (or wherever you downloaded/copied the recovery image)
flash_image recovery recovery.img (use the appropriate file name for the image file you are flashing)
Click to expand...
Click to collapse
Reboot into recovery and verify that the correct recovery environment is installed
Notes
Any of the commands that call for using a terminal emulator on the phone should work fine using an ADB shell if you prefer.
This was tested on G2 but I can't think of why it would not work on Desire Z or any other phone for which this version of flash_image works. Obviously different phones have different compatible recovery images.
I've attached a zip file containing the flash_image binary that I extracted from the CM 6.1 update zip. I suspect most custom ROMs already have flash_image.
If you are wondering "Why should I use this method over using ROM Manager?" you could be using a recovery image that ROM manager doesn't support, for example ClockWorkMod Recovery 3.x which is required for some experimental ROMs.
If you are wondering "Why should I use this method over using fastboot?" The two main reasons are you can't use fastboot if you are not with a computer with working ADB and using fastboot requires that you have previously flashed the engineering HBOOT.
This is my first guide so I'm open to suggestions or feedback.

Nice one
Though I would suggest that
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
could be simplified to :
Code:
mount -o remount,rw /system
Edit - actually /system isn't even on /dev/block/mtdblock3, and it's not a yaffs2 file system, I suspect that's come from another phone model ?

"dd" will do exactly the same, but no need to install extra stuff since its already there.

dhkr123 said:
"dd" will do exactly the same, but no need to install extra stuff since its already there.
Click to expand...
Click to collapse
I wouldn't have a problem using dd myself. But I would have thought it was much more risky, since instead of typing something relatively user-friendly like "recovery", you're typing in /dev/xyz/abc or similar, which if you get it slightly wrong could be disastrous ?

Excellent, worked for me, flashed CW 3.0 without fastboot

steviewevie said:
Nice one
Though I would suggest that
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
could be simplified to :
Code:
mount -o remount,rw /system
Edit - actually /system isn't even on /dev/block/mtdblock3, and it's not a yaffs2 file system, I suspect that's come from another phone model ?
Click to expand...
Click to collapse
Interesting, I've been using that command since forever (since I first rooted my G1 in early 2009) and it definitely does work on my G2 as well as my wife's MT4G.
I just tried "mount -o remount,rw /system" on my phone and it does not work, mount gives me the "Usage:" messages which seems to mean it wants more parameters.

steviewevie said:
I wouldn't have a problem using dd myself. But I would have thought it was much more risky, since instead of typing something relatively user-friendly like "recovery", you're typing in /dev/xyz/abc or similar, which if you get it slightly wrong could be disastrous ?
Click to expand...
Click to collapse
Unless you run wpthis before dd, you're perfectly safe. The radio partitions are all protected by the power-on write protect feature of the eMMC AS WELL as the linux kernel write protect on low addresses. Worst you can do is blow away your system, data, cache, misc, boot, or recovery partitions, and these are trivial to recover from.

raitchison said:
Interesting, I've been using that command since forever (since I first rooted my G1 in early 2009) and it definitely does work on my G2 as well as my wife's MT4G.
I just tried "mount -o remount,rw /system" on my phone and it does not work, mount gives me the "Usage:" messages which seems to mean it wants more parameters.
Click to expand...
Click to collapse
Depends on whether or not the mount command can tell the associations between the devices and mount points, which is determined by either system configuration, or what mount command you are using (i.e. android's mount or busybox mount).

raitchison said:
Interesting, I've been using that command since forever (since I first rooted my G1 in early 2009) and it definitely does work on my G2 as well as my wife's MT4G.
I just tried "mount -o remount,rw /system" on my phone and it does not work, mount gives me the "Usage:" messages which seems to mean it wants more parameters.
Click to expand...
Click to collapse
Sorry, there should have been an extra space, this works on my phone :
Code:
mount -o remount, rw /system
I don't have a "/dev/block/mtdblock3" on my system. My system partition is mounted on /dev/block/mmcblk0p25, and it is ext3 not yaffs2.
What ROM are you running ? I am running the stock DZ 1.34 ROM. I wonder if you are running Gingerbread ?

steviewevie said:
Sorry, there should have been an extra space, this works on my phone :
Code:
mount -o remount, rw /system
I don't have a "/dev/block/mtdblock3" on my system. My system partition is mounted on /dev/block/mmcblk0p25, and it is ext3 not yaffs2.
What ROM are you running ? I am running the stock DZ 1.34 ROM. I wonder if you are running Gingerbread ?
Click to expand...
Click to collapse
I'm running the Stock G2 T-Mobile post-OTA ROM, definitely not Gingerbread.
Edit: I just tried your method and it works, I will update the guide because your way is simpler and sounds like a safer choice.

you could just rename the CW 3.x.x recovery to the exact named recovery slap it in the cloclwork download folder after you delete the old one and flash it with CW just a quicker trick for GB roms

Not sure that's actually quicker, at least I don't think it would be for me, especially if you are changing recoveries with any frequency (like if tying out Gingerbread ROMs then going back to a 2.2 ROM) because you'd need to constantly rename your recovery images. With my method you would only need to leave the two files named as they are, or for expediency you could rename to recovery.img and recovery3.img then when you wanted to switch you could just execute:
flash_image recovery recovery.img
Click to expand...
Click to collapse
or
flash_image recovery recovery3.img
Click to expand...
Click to collapse
Depending on which recovery you wanted at that point & time.
As I said in the guide, there are already a number of options available, using ROM Manager and fastboot are the most commonly seen in guides but your method and mine are other options for people for whom they work better.

Works!!!
Hi my friends!
It worked for me flawlessly. I was using virtuos 0.9 on my desireZ

Great description, but file did not work for me
It's a very good description that a novice like me can follow. And, I am sure the provided file works for many of you, since many of you reported it to work. After following this guide, and not getting it to work (Stopping Signal error), I decided to find another binary file for flash_image, and the other flash_image file worked for me on my Sprint CDMA Hero. My phone currently has aospMod v0.9.9.2 | AOSP 2.2.1(12/10/2010), if it matters.
One can download a flash_image from here http://cyanogen-files.carneeki.net/flash_image.zip
Then unzip and place on sdcard - follow all the steps in the original post of this thread.
It is my understanding that this file is not unique for different android phones, but if I am incorrect, someone please reply to this thread to correct me.
Again, great job in summarizing the steps.
Regards,
Sanjiv

so darn easy! thank you!

Also usable for splash screen ??
Just curious,
Anybody tried to use flash_image to flash a custom splash screen ?
Something like :
flash_image splash1 customsplash.img

very good post for a newbie like me, just want to make sure, do i need to do the stage 2 every time I flash the recovery?

jaoyina said:
very good post for a newbie like me, just want to make sure, do i need to do the stage 2 every time I flash the recovery?
Click to expand...
Click to collapse
No, you only need to do stage 2 once, whenever you update/change recoveries from that point forward just use stage 3.

Is there a way I can reflash a recovery without access to the ROM?
I'm stuck at the HTC splash screen, so I'm basically stuck in my current (broken) recovery.

sanjivp2000 said:
One can download a flash_image from here (..)[/URL]
Click to expand...
Click to collapse
The flash_image in the start post did not work for me, the one above did.
Also, my HTC Hero was missing the cp command.
Instead, I used: cat /sdcard/flash_image > /system/bin/flash_image
Successfully flashed recovery again

LG Optimus Chic (E720) Rooting, Custom Recovery and ROM

How to install custom ROM
For LG Optimus Chic (E720)
Please note that I do not assume any responsibility in case of brick or malfunction of your device! Do it at your own risk!
Step 1: Rooting your device
Root your device using an app like Z4Root to permanently give root access to the Optimus.
• Go to http://forum.xda-developers.com/showthread.php?t=833953 and download the .apk
• Allow unknown sources to install apps on your devices (done by going to Settings - Applications)
• Install Z4Root
• Once it’s install, open the app from the Launcher and chose Permanent Root.
• Once Z4Root has done, your phone will reboot and you should have the SuperUser app installed
• To check that you really have root access you can install Terminal Emulator form the Play Store as we’ll need it after. https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=fr
• After you’ve install it, open a terminal session and you should see a «$». Just type ‘’su’’ and a window will open prompting you to allow super user. Chose «Allow». You will notice that the «$» had changed for a «#» this meaning that you have rooted your Android device !
Step 2: Install a custom recovery
In order to have a custom ROM, we will need a recovery to flash the .zip to the phone
• Download the recovery image and the flash_image by going to http://forum.xda-developers.com/showthread.php?t=1046135
• Once both files are downloaded, unzip them on the root of your SD card.
• After that, form the Terminal Emulator or an ADB Shell type the following commands in order to install the custom recovery.
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 0755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak (notice this file install-recovery.sh may not be on your device if it gives an error or file not found move on)
flash_image recovery /sdcard/recovery-alessi-gnm.img
sync
• Power off your phone and boot in recovery mode by holding the Vol+ , Vol- and Power until you see the recovery on the screen.
• The message «E: bad boot» is normal. It will show up for everyone.
• You now have a custom recovery installed. It’s now time for the ROM itself!
Step 3: Installing the ROM
To make sure if anything go wrong, please do a nandbackup by going to Backup/Restore on the recovery before proceeding.
• First of all you got to find the right ROM for you. I choose a nighty version of CM7 because it’s light, fast and easy to find not like a CM9 ROM. You can download it form http://get.cm/?device=e720
• Because this ROM don’t have Gapps (Goolgle Apps) in it, we will download it to have the Play Store working on our device. http://goo.im/gapps/gapps-gb-20110828-signed.zip
• Once all of the files are copied on the root of the SD card (Make sure you haven’t unzip them!) boot into recovery mode and perform a wipe of your device.
• After, flash the ROM on the device and after the GApps.
• When everything is done, you can proceed in the process of rebooting.
• Take note that the first boot after you have flashed a ROM may take WAY longer than usual.
• Voilà! You now have your phone running CM7! Make sure to have fun!

Thanks emidesja
I followed your guide and it worked great. I would offer the following links for those not familiar with setting up ADP. It sure beats using a terminal emulator on the phone.
What is ADP - addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
Android Debug Bridge (commands) - developer.android.com/tools/help/adb.html
I think I only used the commands ADB devices, then ADB shell before being able to enter your code. Also, after entering su I needed to click allow superuser on the phone. I can also add that when booting to recovery I needed to push quite firmly between volume up and down, so that the whole button is pressed and not toggled. In step 3 the wipe you mentioned offers many options. I choose to wipe only to wipe the cache partition and the Dalvik Cache.
Thanks again.

Achieving root on Xperia Z1 - 14.6.A.1.216

After dabbling around in some murky waters trying to achieve root, and going trough some 2010 stuff I did, I did discover a method I devised back then works to some extent, strangely.
Using fastboot (boot) to a TWRP recovery image (TWRP_v2.8.6.0_honami-f2fs_from_cm12.1_150423.img), mounting /system, and pushing a version of busybox, bash and using the supersu su binary already in the TWRP recovery image.
boot-new.img.bz2.zip (rename to boot-new.img.bz2 before extracting -.Just TWRP_v2.8.6.0_honami, with a different kernel and dt image included to boot from fastboot)
bash and busybox i compiled from git and debian sources yesterday/today
Basically this; (use only for reference.)
Code:
# Magically push all files in place here.
# Optionally, move /system/bin/sh out of the way and link /system/bin/sh to bash
./"$ADB" shell "chmod 755 /system/bin/bash && chown 0.0 /system/bin/bash"
./"$ADB" shell "chmod 4755 /system/bin/busybox && chown 0.0 /system/bin/busybox"
# TWRP
#./"$ADB" shell "cp /supersu/su /system/bin/_su"
./"$ADB" shell "cp /supersu/su /system/bin/su"
./"$ADB" shell "cp /supersu/supolicy /supersu/su /system/xbin"
./"$ADB" shell "cp /supersu/libsupol.so /system/lib/"
./"$ADB" shell "chmod 0644 /system/lib/libsupol.so && chown 0.0 /system/lib/libsupol.so"
./"$ADB" shell "cp -r /supersu /system/app/SuperSU"
./"$ADB" shell "chmod 0755 /system/app/SuperSU && chown 0.0 /system/app/SuperSU && chmod 0644 /system/app/SuperSU/SuperSU.apk"
#
#./"$ADB" shell "chmod 4755 /system/bin/_su && chown 0.0 /system/bin/_su"
#./"$ADB" shell "echo "busybox su -c "_su"" > /system/bin/su" # or busybox su -c "_su -c /system/bin/sh-org"
./"$ADB" shell "chmod 4755 /system/bin/su /system/xbin/su* && chown 0.0 /system/bin/su system/xbin/su*"
# Quite dangerous - Suggest moving passwd when in normal use
./"$ADB" shell "echo "root::0:0:0:/root:/system/bin/sh" > /system/etc/passwd"
./"$ADB" shell "chmod 0644 /system/etc/passwd"
Next step, to remount /system with write permissions from a normal boot, I think, would be to modify boot.img/default.prop and set "ro.secure=0"
Thought I had done this prior, I run with touch disabled as I cracked my screen (impressively massive drop of at least 30 cm! - onto object.. ) ... I could not remount system when I first tried.
Notes:
If i adb in early i can use supersu/su to gain root, when system is loaded busybox su -c ""supersu/"su" works. - NO AUTH

Hm, updated SuperSU via google play and suddenly it realized it was rooted . = ) Still keeping the supersu/su intact in /system/*bin

Thankfully I've been unsuccessful in grabbing root from /data/local/tmp this way as of now. Seems the permissions are reset. Though getting root without any auth is a serious matter no matter how you flip the coin. At least it's not as easy as pushing an archive to /data/local/tmp and running busybox su -c su. Also with a modified busybox you could easily skip the part where I write a /etc/passwd with no password.. Incredibly handy if you need root without Android running, say with setprop ctl.stop zygote, media and bootanim. But incredibly dangerous!

Fastboot to attached TWRP and install [STABLE][2016.02.02] SuperSU v2.65 - http://forum.xda-developers.com/showthread.php?t=1538053 - drop the zip to somewhere on the device and use the install function, i installed supersu via google play first. Attached is the kernel image i'm using. On a side-note, the script above failed .
Apart from this, the attached gnu-tools i will have to update... Got a neon flags optimized for out cpu and all, but that's for a different day.
Cheers, have a good one mates

Noob question: what is the difference between using this method for root and kingroot method? Which is better to use?

I've not checked Kingroot. But my thought is not to rely on nasty kernel exploits and have an as clean as possible root. Kingroot was not working when i first started this post. Also i dont leave system read write mountable. To do system modification i fastboot the TWRP image

threader said:
I've not checked Kingroot. But my thought is not to rely on nasty kernel exploits and have an as clean as possible root. Kingroot was not working when i first started this post. Also i dont leave system read write mountable. To do system modification i fastboot the TWRP image
Click to expand...
Click to collapse
Kingroot give you root but not supported and their binary are weired but when you replace it with supersu you can't mount system read/write cause of ric but thanks to Chainfire and his tools I find way to root with kingroot and replace it by supersu and disable ric

Noticed my boot img was rebooting sometimes, went off and updated my compiler toolchain and had a look at the kernel and recent developments.
Had a look at X-Honami v6 and ported some parts of that effort to the latter Sony kernel used in 14.6.a.1.216.
* Messed around with memutils and implemented ARM_PLD_64BYTE and USE_LDRDSTRD_OVER_LDMSTM atop memutils from the Xperia-dev unified kernel. - this needs some testing but appears to be stable at least with the options turned on.
* Slight overclock of GPU to 533 mhz, and underclock to 27 mhz on idle.
* Has kexec hardboot
I cannot busybox su -c su with this kernel. Which is only useful for developers anyway. You'd be wise in running some benchmarks before and after the flash.
Kernel needs to be flashed via fastboot.
Source:
https://github.com/threader/kernel-copyleft-14.6.A.1.xxx-backports/

DectonX said:
Kingroot give you root but not supported and their binary are weired but when you replace it with supersu you can't mount system read/write cause of ric but thanks to Chainfire and his tools I find way to root with kingroot and replace it by supersu and disable ric
Click to expand...
Click to collapse
I have rooted my phone with king root , downloaded SuperSU-ME-PRO_9.3.8 to replace kingroot with supersu but the app stucks in middle while processing data. Can you please help me with the following things:
1. Which chainfire apk to use to replace kingroot with supersu (kingroot ver is 4.9.2)
2. I need to install Xposed framework, for which i belive i need to flash a recovery. As i am on stock based kernel and rom can you help me which recovery should i flash and further steps to get the xposed framework in my xperia z1 (5.1.1)

VikasG09 said:
I have rooted my phone with king root , downloaded SuperSU-ME-PRO_9.3.8 to replace kingroot with supersu but the app stucks in middle while processing data. Can you please help me with the following things:
1. Which chainfire apk to use to replace kingroot with supersu (kingroot ver is 4.9.2)
2. I need to install Xposed framework, for which i belive i need to flash a recovery. As i am on stock based kernel and rom can you help me which recovery should i flash and further steps to get the xposed framework in my xperia z1 (5.1.1)
Click to expand...
Click to collapse
Ok i have done step #1 by manually updating supersu and it deleted the kingroot by itself. Now i need answer for #2 only, Which recovery should i install in stock based rom ?

VikasG09 said:
I have rooted my phone with king root , downloaded SuperSU-ME-PRO_9.3.8 to replace kingroot with supersu but the app stucks in middle while processing data. Can you please help me with the following things:
1. Which chainfire apk to use to replace kingroot with supersu (kingroot ver is 4.9.2)
2. I need to install Xposed framework, for which i belive i need to flash a recovery. As i am on stock based kernel and rom can you help me which recovery should i flash and further steps to get the xposed framework in my xperia z1 (5.1.1)
Click to expand...
Click to collapse
long steps but 100% works
1. Download kingroot and root your phone
2.Download replace kingroot with SuperSU and extract it to internal memory
3.Download XZDual Recovery for your phone
4.Download Terminal emulator for play store
5.Download FlashFire by Chainfire from play store
6.Download SuperSU zip package
what you will do
1. Get root using kingroot
2.open terminal and write
Code:
su
sh /sdcard/mrw/root.sh
3. it will open SuperSU.... press update manual
warn : Don't click Reboot, if you rebooted phone ric will work and you will not have access to system partition
4. open FlashFire and grant SuperSU then press on lighting button
5. choose XZDual Recovery zip file and tick auto remount and press on flash or lighting button
black screen will apear preparing files and flash it then phone will reboot
6. when you see the green led press vol down to enter TWRP
7. flash SuperSU package
Note : if there is bootloop , enter recovery and go to setting> fix premission
and reboot
now you have SuperSU working 100%
Notes : no recovery will bring you xposed.... just try to open Xposed thread and download the package for your SDK
the recovery i use is XZDual Recovery from [NuT] it's very good for locked bootloaders
hit thanks if helped

DectonX said:
long steps but 100% works
1. Download kingroot and root your phone
2.Download replace kingroot with SuperSU and extract it to internal memory
3.Download XZDual Recovery for your phone
4.Download Terminal emulator for play store
5.Download FlashFire by Chainfire from play store
6.Download SuperSU zip package
what you will do
1. Get root using kingroot
2.open terminal and write
Code:
su
sh /sdcard/mrw/root.sh
3. it will open SuperSU.... press update manual
warn : Don't click Reboot, if you rebooted phone ric will work and you will not have access to system partition
4. open FlashFire and grant SuperSU then press on lighting button
5. choose XZDual Recovery zip file and tick auto remount and press on flash or lighting button
black screen will apear preparing files and flash it then phone will reboot
6. when you see the green led press vol down to enter TWRP
7. flash SuperSU package
Note : if there is bootloop , enter recovery and go to setting> fix premission
and reboot
now you have SuperSU working 100%
Notes : no recovery will bring you xposed.... just try to open Xposed thread and download the package for your SDK
the recovery i use is XZDual Recovery from [NuT] it's very good for locked bootloaders
hit thanks if helped
Click to expand...
Click to collapse
Thanks a lot..

I still suggest using the fastboot method with the TWRP boot image attached in the first post, mount the system partition, select install Zip SuperSu, forum.xda-developers.com/showthread.php?t=1538053 .
Cheers
I've got a kernel-copyleft-14.6.A.1.xxx to finish up and officially forum post ; ) https://github.com/threader/kernel-copyleft-14.6.A.1.xxx-backports/ . And update and official post might come this week. Been running this for months now and its stable, and fast, whee.
VikasG09 said:
Thanks a lot..
Click to expand...
Click to collapse

threader said:
I still suggest using the fastboot method with the TWRP boot image attached in the first post, mount the system partition, select install Zip SuperSu, forum.xda-developers.com/showthread.php?t=1538053 .
Cheers
I've got a kernel-copyleft-14.6.A.1.xxx to finish up and officially forum post ; ) https://github.com/threader/kernel-copyleft-14.6.A.1.xxx-backports/ . And update and official post might come this week. Been running this for months now and its stable, and fast, whee.
Click to expand...
Click to collapse
I just used kingroot, unlocked bootloader, flashed dual recovery, flashed prerooted Rom. That's it. Easy as pie.
Sent from my D5503 using Tapatalk