Hello!
I am using LYF wind 6 with android lollipop 5.1 and i have rooted with kingroot and as it doesn't have any custom recovery so i wanna use FLASHFIRE but it requires supersu permissions but i have installed kingroot.
i have tried many methods to replace it with supersu but nothing works.
i have used super-sume pro.apk but it stuck at "processing please wait"
i have tried to replace it using terminal emulator but it says " su binary not installed,............there is problem....etc."
i tried to push su in /system/xbin and chmod 775 /system/xbin/su but it says operation not permitted
can any please one help me to replace it please, it very urgent
or can any please one port any custom recovery for my phone i.e. LYF Wind 6
here is the stock recovery for my phone compressed
please!please!please!please!please!please! make a custom recovery for my phone.
alokjkashyap said:
Hello!
I am using LYF wind 6 with android lollipop 5.1 and i have rooted with kingroot and as it doesn't have any custom recovery so i wanna use FLASHFIRE but it requires supersu permissions but i have installed kingroot.
i have tried many methods to replace it with supersu but nothing works.
i have used super-sume pro.apk but it stuck at "processing please wait"
i have tried to replace it using terminal emulator but it says " su binary not installed,............there is problem....etc."
i tried to push su in /system/xbin and chmod 775 /system/xbin/su but it says operation not permitted
can any please one help me to replace it please, it very urgent
or can any please one port any custom recovery for my phone i.e. LYF Wind 6
here is the stock recovery for my phone compressed
please!please!please!please!please!please! make a custom recovery for my phone.
Click to expand...
Click to collapse
Try to download SuperSU and update SU binaries using "Normal" method
Sent from my GT-S7580 using Tapatalk
DodoGTA said:
Try to download SuperSU and update SU binaries using "Normal" method
Click to expand...
Click to collapse
I have tried but it says, 'There is no su binary installed and superSU cant install . there is problem' or something like that and it auto close.
http://forum.xda-developers.com/android/apps-games/replace-kingroot-supersu-t3339950
This method MIGHT work... There's also a chance that it could soft brick, so I wouldn't try unless you have the ability to reflash the original firmware.
es0tericcha0s said:
http://forum.xda-developers.com/android/apps-games/replace-kingroot-supersu-t3339950
This method MIGHT work... There's also a chance that it could soft brick, so I wouldn't try unless you have the ability to reflash the original firmware.
Click to expand...
Click to collapse
Thanks, i hope this work but i cannot try it as i have looses root permission and i am unable to root now.
alokjkashyap said:
Thanks, i hope this work but i cannot try it as i have looses root permission and i am unable to root now.
Click to expand...
Click to collapse
Then I would back up everything then reinstall the original firmware and reroot.
es0tericcha0s said:
Then I would back up everything then reinstall the original firmware and reroot.
Click to expand...
Click to collapse
There is no custom recovery for this device the how can i backup.
es0tericcha0s said:
http://forum.xda-developers.com/android/apps-games/replace-kingroot-supersu-t3339950
This method MIGHT work... There's also a chance that it could soft brick, so I wouldn't try unless you have the ability to reflash the original firmware.
Click to expand...
Click to collapse
And nothing is working for rooting my phone.
Most of the important stuff can be backed up to Google. If you need to backup your calls/texts, they're apps for that. Then copy your internal storage to a PC and that should be the main important stuff.
Finally i tried kingoroot pc app and it rooted my phone but doesn't install any superuser app in my phone, then i installed superSu from playstore and it worked.
Related
I installed Rom Manager and then downloaded the recovery for Samsung galaxy s2. When hit reboot into recovery. I am unable to perform any operations in CWM. I had to connect the phone via usb and issue a "adb reboot" command to get back.
How do we make cwm work.
http://forum.xda-developers.com/showpost.php?p=18160002&postcount=26
ptulluri said:
I installed Rom Manager and then downloaded the recovery for Samsung galaxy s2. When hit reboot into recovery. I am unable to perform any operations in CWM. I had to connect the phone via usb and issue a "adb reboot" command to get back.
How do we make cwm work.
Click to expand...
Click to collapse
Also must people are having issues flashing in cwm after using ROM manager. If you try installing from cwm and get verification error you needed to flash again then kernel and don't use ROM manager
Flashed CWM and nothing is happening
I flashed CWM Recovery 5.0.2.3 using the instructions here http://forum.xda-developers.com/showthread.php?t=1285823. However, when i go into CWM and select something the only thing that happens is the logo for CWM shows up with a black screen. When I push the power button again it will go back to the list.I am using the stock rom and it hasn't even been rooted yet. When I try to root using super one click, it gets stuck at step #5. Please Advise.
NDN
Dont use Rom Manager. It is known to have issues with the S2
I use CWM Manager and have no problems.....
noobdeeznutz said:
I flashed CWM Recovery 5.0.2.3 using the instructions here http://forum.xda-developers.com/showthread.php?t=1285823. However, when i go into CWM and select something the only thing that happens is the logo for CWM shows up with a black screen. When I push the power button again it will go back to the list.I am using the stock rom and it hasn't even been rooted yet. When I try to root using super one click, it gets stuck at step #5. Please Advise.
NDN
Click to expand...
Click to collapse
The key mapping is different. I had the same issue. Try the home key to select in place of the power button and the back key for back
Also if not rooted I do not think CWM will work...
Use this by Entropy512 it is flawless.
http://forum.xda-developers.com/showthread.php?t=1286432
SNadler said:
The key mapping is different. I had the same issue. Try the home key to select in place of the power button and the back key for back
That was it... THANKS!!!
Click to expand...
Click to collapse
SNadler said:
Also if not rooted I do not think CWM will work...
Click to expand...
Click to collapse
Root is having access to root account in os. It has nothing to do with cwm since cwm is loaded before the os loads.
They are irrelevant
Sent from my SAMSUNG-SGH-I777
Pirateghost said:
Root is having access to root account in os. It has nothing to do with cwm since cwm is loaded before the os loads.
They are irrelevant
Sent from my SAMSUNG-SGH-I777
Click to expand...
Click to collapse
In addition, all of our CWM-enabled kernels are "insecure" kernels - They give root at all times to ADB sessions, this is why SuperOneClick works after flashing them.
But only ADB sessions get root, so you use the "rooted" ADB shell to root the system partition. After that you've got perma-root until you nuke su and Superuser.apk from /system
Entropy512 said:
In addition, all of our CWM-enabled kernels are "insecure" kernels - They give root at all times to ADB sessions, this is why SuperOneClick works after flashing them.
But only ADB sessions get root, so you use the "rooted" ADB shell to root the system partition. After that you've got perma-root until you nuke su and Superuser.apk from /system
Click to expand...
Click to collapse
I think I am confused again?
When I flash a kernel, I have root. I have never used super one click. Just flashed your kernel. I thought that is what gave me root? Are you saying I still do not have root for /system files? Or does your kernel push su and superuser when it is flashed?
SNadler said:
I think I am confused again?
When I flash a kernel, I have root. I have never used super one click. Just flashed your kernel. I thought that is what gave me root? Are you saying I still do not have root for /system files? Or does your kernel push su and superuser when it is flashed?
Click to expand...
Click to collapse
Mine does, codeworkx's doesn't.
Setting a kernel to be insecure is a lot easier and takes less time than putting in a robust root-inject script.
SNadler said:
I think I am confused again?
When I flash a kernel, I have root. I have never used super one click. Just flashed your kernel. I thought that is what gave me root? Are you saying I still do not have root for /system files? Or does your kernel push su and superuser when it is flashed?
Click to expand...
Click to collapse
Entropy512 said:
Mine does, codeworkx's doesn't.
Setting a kernel to be insecure is a lot easier and takes less time than putting in a robust root-inject script.
Click to expand...
Click to collapse
Entropy512: Does this mean that codeworkx's kernel must be flashed with SuperOneClick in order to have complete root (to /system)... but with your kernels we don't need to flash SuperOneClick? If so, in order to unroot (without SuperOneClick) I suspect one would have to flash the non-root stock kernel? Thx
DoctorQMM said:
Entropy512: Does this mean that codeworkx's kernel must be flashed with SuperOneClick in order to have complete root (to /system)... but with your kernels we don't need to flash SuperOneClick? If so, in order to unroot (without SuperOneClick) I suspect one would have to flash the non-root stock kernel? Thx
Click to expand...
Click to collapse
Yes. (Unless you flash an su package with CWM instead of SuperOneClick)
Really, all SuperOneClick is doing are the following commands, assuming you've got a proper su binary and Superuser.apk:
Code:
adb remount
adb push su /system/xbin/su
adb shell chmod 6755 /system/xbin/su
adb push Superuser.apk /system/app/Superuser.apk
adb shell chmod 644 /system/app/Superuser.apk
Entropy512 said:
Yes. (Unless you flash an su package with CWM instead of SuperOneClick)
Really, all SuperOneClick is doing are the following commands, assuming you've got a proper su binary and Superuser.apk:
Code:
adb remount
adb push su /system/xbin/su
adb shell chmod 6755 /system/xbin/su
adb push Superuser.apk /system/app/Superuser.apk
adb shell chmod 644 /system/app/Superuser.apk
Click to expand...
Click to collapse
I understand (I think) that chmod 644 is to set the permission but what is chmod 6755?
SNadler said:
Dont use Rom Manager. It is known to have issues with the S2
I use CWM Manager and have no problems.....
Click to expand...
Click to collapse
I have downloaded CWM Manager and I have tried to install it but it has failed. Is there a different type of process to doing this other than opening it through root explorer?
what are you trying to do? just use the 3 button combo or extended power option to boot into recovery and flash away?
Ok, I am having a huge issue with trying to flash a custom rom. I will try to explain this the best way I can. I have had the same problem as above when trying to use CWM in recovery. Here is what I did:
- I unrooted my phone
- flash CWM with "SGH-I777_ClockworkMod-Recovery_5.0.2.3.tar"
- then it boots into CMW recovery and I can't do jack. When I try to select anything I just get a blank screen with the clock workz logo. If I hit the volume up and down buttons again the list of options comes back, but I will be stuck with the same situation if I try to select any options.
I was able to successfully root my phone in another instance using galaxys2root.com's method, however when I tried to use cwm I also ran into the same problem. I have yet to be able to use anything in cwm recovery. Please help me. I have flashed my phone multiple times and probably bricked it also. Luckily i haven't done any damage yet, but i would like to be able to flash roms. I am still kinda new to flashing roms, but i was able to flash my old infuse like a champ without any of these problems.
ducksauce88 said:
Ok, I am having a huge issue with trying to flash a custom rom. I will try to explain this the best way I can. I have had the same problem as above when trying to use CWM in recovery. Here is what I did:
- I unrooted my phone
- flash CWM with "SGH-I777_ClockworkMod-Recovery_5.0.2.3.tar"
- then it boots into CMW recovery and I can't do jack. When I try to select anything I just get a blank screen with the clock workz logo. If I hit the volume up and down buttons again the list of options comes back, but I will be stuck with the same situation if I try to select any options.
I was able to successfully root my phone in another instance using galaxys2root.com's method, however when I tried to use cwm I also ran into the same problem. I have yet to be able to use anything in cwm recovery. Please help me. I have flashed my phone multiple times and probably bricked it also. Luckily i haven't done any damage yet, but i would like to be able to flash roms. I am still kinda new to flashing roms, but i was able to flash my old infuse like a champ without any of these problems.
Click to expand...
Click to collapse
Use the home soft key to select stuff in CWR, not the power button.
Sent from my SGH-I777 using XDA App
i didnt read all of the posts until after i posted. thanks for not slashing me. so it looks like i use the home button to select then the back button still goes back. got it.
On a side not, I do not remember reading about that within the posts for rooting and flashing clockworkz. I tend to skip over things when reading, but I think someone should put that in big fat red letters "USE HOME BUTTON TO SELECT".
i'm quite confused. I believe my phone is partially rooted. I installed SuperSu but it says that i do not have the Su Binary installed. under root checker it says that supersu is not installed but busybox is. I successfully installed Root Explorer and am able to view system files but not edit them.
anyways, i got a verification error when trying to flash CWM-supersu in recovery. I followed al the steps and downloaded all the required recovery.img files etc. I am tempted to flash a custom rom. but afraid if it gets locked up during the process, as there is no back up option with the stock recovery.
Any suggestions?
swift2fly said:
i'm quite confused. I believe my phone is partially rooted. I installed SuperSu but it says that i do not have the Su Binary installed. under root checker it says that supersu is not installed but busybox is. I successfully installed Root Explorer and am able to view system files but not edit them.
anyways, i got a verification error when trying to flash CWM-supersu in recovery. I followed al the steps and downloaded all the required recovery.img files etc. I am tempted to flash a custom rom. but afraid if it gets locked up during the process, as there is no back up option with the stock recovery.
Any suggestions?
Click to expand...
Click to collapse
Update the binaries in superSU settings or reinstall root with CF-Root with Odin, see item 1 in my signature.
gee2012 said:
Update the binaries in superSU settings.
Click to expand...
Click to collapse
will not allow it. "It says that SuperSu can not install it. There is a problem"
I'm on Android version 4.0.4 firmware BULF1
swift2fly said:
will not allow it. "It says that SuperSu can not install it. There is a problem"
Click to expand...
Click to collapse
Yes, flash CF-Root with Odin.
Update your busybox to latest version.then update the su..it will work
Then cwm problem can be solved by using a manual cwm(new cwm from someone)...
gee2012 said:
Yes, flash CF-Root with Odin.
Click to expand...
Click to collapse
ok i will look into that. i gotta find a PC. I've successfully rooted 2 S3s with the method i use on mac but for some reason it's not working on this current phone i'm trying to root.
I am trying to root the stock Lollipop rom of DG280 (can be find in doogee.cc)
i created custom system.img, custom recoveries, unsecured boot.img but even if i root it, it doesn't boot again.
I unpack system.img and put the su binary in xbin, then i pack it and flash , but bootloops.
Unsecured boot.img boots but when i connect phone to pc, it doesn't get recognized. I created a custom recovery based on kitkat and worked, but after installing various rooting packages, like supersu v2.46, phone boots rooted at first time, but after reboot it doesn't boot again!
Please any help appreciated.
gerstavros said:
I am trying to root the stock Lollipop rom of DG280 (can be find in doogee.cc)
i created custom system.img, custom recoveries, unsecured boot.img but even if i root it, it doesn't boot again.
I unpack system.img and put the su binary in xbin, then i pack it and flash , but bootloops.
Unsecured boot.img boots but when i connect phone to pc, it doesn't get recognized. I created a custom recovery based on kitkat and worked, but after installing various rooting packages, like supersu v2.46, phone boots rooted at first time, but after reboot it doesn't boot again!
Please any help appreciated.
Click to expand...
Click to collapse
Not sure if you have it sorted but just thought I would mention what works 100% for me. Just picked up a leo dg280 while waiting for a replacement screen for my main phone.
Anyway use kingroot to root, then google for the mrw script and follow those instructions to replace kingroot with SuperSU. So far has worked everytime for me ( have reflashed lillipop numerous times for different reasons)
Sent from my LEO_DG280 using Tapatalk
frooby said:
Not sure if you have it sorted but just thought I would mention what works 100% for me. Just picked up a leo dg280 while waiting for a replacement screen for my main phone.
Anyway use kingroot to root, then google for the mrw script and follow those instructions to replace kingroot with SuperSU. So far has worked everytime for me ( have reflashed lillipop numerous times for different reasons)
Sent from my LEO_DG280 using Tapatalk
Click to expand...
Click to collapse
I had tried that but never worked (vroot, root genius, kingroot etc). I finally flashed a custom made cwm recovery and installed a kinguser su package.
gerstavros said:
I had tried that but never worked (vroot, root genius, kingroot etc). I finally flashed a custom made cwm recovery and installed a kinguser su package.
Click to expand...
Click to collapse
What recovery did you use? I can't find any that work! Any chance you can pm me a link?
frooby said:
What recovery did you use? I can't find any that work! Any chance you can pm me a link?
Click to expand...
Click to collapse
Ι had made a custom cwm based on kitkat rom i think. It doesn't work properly in lollipop rom, it cannot read internal or external file storage partition although i was sure i had configured correctly the files, you can install a package only via adb sideload. Also it is bigger than the stock recovery and i ' m not sure if that occures any problem.
I m not sure now which file it is, if i make one for lollipop rom i ll upload it
Hello..
We all know that there is a way to get root on the OPX
using the kingroot app without a custom recovery.
But the question is : is it possible to flash TWRP.img through
the terminal emulator? And if it possible, What are the commands ?
Thank you..
I'm not completely sure, but try this..
Do a backup just in-case.
Code:
su
flash_image recovery /sdcard/recovery.img
Here, su is for superuser right and the next command flashes the recovery.
Note that "/sdcard/recovery.img" means that your recovery.img file should be in the root of your Internal storage and should be renamed to "recovery" without quotes.
Kingroot is a "bad" way to root.
IMHO, you should stick on the normal way.
Be sure your BL is correctly unlocked.
Then if your root, you can flash TWRP via an "rashr app"
We king root is a bad way to root? So many times I have tried in many phone's it produces the same result as supersu, and after all i never stick with it. I always replace it with supersu at the end.
Sent from my ONE E1001
sniper20 said:
We king root is a bad way to root? So many times I have tried in many phone's it produces the same result as supersu, and after all i never stick with it. I always replace it with supersu at the end.
Sent from my ONE E1001
Click to expand...
Click to collapse
I just mean here, because some people gave tutos to easily root without unlocking BKL. Some use them, and after stay stucked trying to flash something.
And Kinroot is a software that try to install you a bunch of crap when you use it...
I had recently upgrade my s3 using TWRP recovery from 4.4 to 7.1 lineage os
But I am facing problem with rooting.
I am not able to root my device from
1)TWRP recovery
2)Odin(CF Auto Root)
3)Kingroot(Android and PC )
I have installed TWRP properly
PLz give an idea to root my device
I have checked in developer option
That is ROOT ACCESS
Their is 2 Option only
1)Disable
2)Adb only
But I am not able to get root access any of this Or Adb only
Previously I tried with different ROM
Their is option of
1)disabled
2)Apps only
3)Adb only.
4)apps and Adb
But in this ROM I am not able to find suggest me any way to fix this
I installd 4 time s same ROM to get this root access but failed
Check below screenshot
In SuperSU application
No su binary installed
https://dropfile.to/bRO4jKc
https://dropfile.to/MMWxWrp
As far as I'm aware the rom should be pre rooted and all you'll need to do is install supersu from googleplay and then update the su binaries from within the supersu app.
Set it to option 4 (apps and abd) and go about installing supersu first as the app from googleplay and if no joy then as a flashable zip file.
Beamed in by telepathy.
amitrider04 said:
I had recently upgrade my s3 using TWRP recovery from 4.4 to 7.1 lineage os
But I am facing problem with rooting.
I am not able to root my device from
1)TWRP recovery
2)Odin(CF Auto Root)
3)Kingroot(Android and PC )
I have installed TWRP properly
PLz give an idea to root my device
I have checked in developer option
That is ROOT ACCESS
Their is 2 Option only
1)Disable
2)Adb only
But I am not able to get root access any of this Or Adb only
Previously I tried with different ROM
Their is option of
1)disabled
2)Apps only
3)Adb only.
4)apps and Adb
But in this ROM I am not able to find suggest me any way to fix this
I installd 4 time s same ROM to get this root access but failed
Check below screenshot
In SuperSU application
No su binary installed
https://dropfile.to/bRO4jKc
https://dropfile.to/MMWxWrp
Click to expand...
Click to collapse
Did you try to flash the addonsu.zip from LineageOS website?
You must flash it to get root access in LineageOS 14.1
I have tried to flash addonsu for lineage os
×64
But failed now i am getting just option to
Apps and adb but its not giving me obtain root
Options are available in root acces
Apps only
Adb only
Adb and apps
But if i checked adb and apps or anything
Root checker still says No root
I am not able to get root access:crying:
Flash a stock firmware and start over.
Beamed in by telepathy.
amitrider04 said:
I have tried to flash addonsu for lineage os
×64
But failed now i am getting just option to
Apps and adb but its not giving me obtain root
Options are available in root acces
Apps only
Adb only
Adb and apps
But if i checked adb and apps or anything
Root checker still says No root
I am not able to get root access:crying:
Click to expand...
Click to collapse
Are you sure you flashed the correct addonsu???
As far as i remember, the s3 doesn't have 64x, flash the normal arm version (arm32x).
Bro i have tried to flash ARM AND ARM X86 but it says
update failed in twrp recovery
So i flashed with x64
It was done but not worked properly
Check this
https://s21.postimg.org/99z5kiw07/Screenshot_2017_03_20_12_21_53.png
amitrider04 said:
Bro i have tried to flash ARM AND ARM X86 but it says
update failed in twrp recovery
So i flashed with x64
It was done but not worked properly
Check this
https://s21.postimg.org/99z5kiw07/Screenshot_2017_03_20_12_21_53.png
Click to expand...
Click to collapse
flash supersu.zip 2.79 with twrp it worked for me
Thanks it also worked for me:laugh:
Thank you!!!
That worked for me.
Now i would like to know why this works and not the file from Lineage itself....
Zwolly said:
Thank you!!!
That worked for me.
Now i would like to know why this works and not the file from Lineage itself....
Click to expand...
Click to collapse
It works, you will get an error in recovery, but when you boot, you will get root access normally, i don't why the error happens, but it's harmless anyway.
Root fix
I'm not sure if you have fixed it yet but just in case if this helps the way I got around this is by simply downloading the latest super su zip from the official site and manually flashing via twrp kinda sucks but it works the first boot took a little though so if you try this and it takes forever for your device to not just wait because it can take up to 15 min the first time. So basically as long as you have twrp you are rooted technically it's just based on the rom wether they chose to support it if not the zip always works but you need the app too.
amitrider04 said:
I have tried to flash addonsu for lineage os
×64
But failed now i am getting just option to
Apps and adb but its not giving me obtain root
Options are available in root acces
Apps only
Adb only
Adb and apps
But if i checked adb and apps or anything
Root checker still says No root
I am not able to get root access:crying:
Click to expand...
Click to collapse
amitrider04 said:
Bro i have tried to flash ARM AND ARM X86 but it says
update failed in twrp recovery
So i flashed with x64
It was done but not worked properly
Check this
https://s21.postimg.org/99z5kiw07/Screenshot_2017_03_20_12_21_53.png
Click to expand...
Click to collapse
S3 has arm32. So neither x86 not x64 would work. You should've flashed addonsu.zip for 32.
Sent from my Pixel XL using Tapatalk