Hello
I have upgraded my TF300T with the last ASUS update (4.2.1).
After the upgrade, I have a partially rooted device.
All the apps already declared in the whitelist of Superuser are still gaining the root permission (root explorer...). But any new installed applications cannot access root
After a few hours of research with google I found that supersuser app is not compatible with Android 4.2 but I didn't any clue to repair that.
[UPDATE] Solution in post 4
Thx
Re: [Q] New 4.2.1 update + root partially lost with Superuser App
Do not uninstall anything that has root! I had the same problem when updating from ICS earlier in year. Will post update when I find my notes.
Sent from my DROID RAZR HD using xda app-developers app
---------- Post added at 12:35 PM ---------- Previous post was at 12:14 PM ----------
http://forum.xda-developers.com/showthread.php?t=1995207
Check out this thread - you can see where I thanked the poster near the end. I downloaded the binary as instructed. I use ES File Explorer. I checked the permissions of the installed su. I then copied the new binary replacing the old one. I checked permissions again. I don't remember if I had to change them or not but they were the same when I was done. I then believe I updated the binary from the market. Lastly with fingers crossed I rebooted. For me root was completely restored and I was good to go.
Sent from my DROID RAZR HD using xda app-developers app
Reilly1812 said:
Do not uninstall anything that has root! I had the same problem when updating from ICS earlier in year. Will post update when I find my notes.
Sent from my DROID RAZR HD using xda app-developers app
---------- Post added at 12:35 PM ---------- Previous post was at 12:14 PM ----------
http://forum.xda-developers.com/showthread.php?t=1995207
Check out this thread - you can see where I thanked the poster near the end. I downloaded the binary as instructed. I use ES File Explorer. I checked the permissions of the installed su. I then copied the new binary replacing the old one. I checked permissions again. I don't remember if I had to change them or not but they were the same when I was done. I then believe I updated the binary from the market. Lastly with fingers crossed I rebooted. For me root was completely restored and I was good to go.
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
Thanks for your reply but it does not work for me.
Solution
After several tries, I found a way to solve my problem.
As it could be useful for some other people, here are the steps to repair your root
All credit goes to Koush for the fix
Requirements : adb / su binary
Follow this link and dowload su binary on your computer
Extract the contents to a folder
Start a cmd window
Run adb shell
In adb shell type
Code:
/system/bin/su
Check you are root (id or # prompt)
Remount system as RW
Code:
mount -o remount,rw /dev/block/mmcblk0p1 /system
Open a new CMD window and push the su binary from step 1 to the internal storage
Code:
adb push <your path>\su /sdcard/
From the adb session where you got root, type
Code:
mv /system/bin/su /system/bin/su.back
cat /sdcard/su > /system/bin/su
chmod 6755 /system/bin/su
Done (maybe reboot)
If it does not work for you, you can restore your old binary if you prefer...
worked for me
fuzzynco said:
worked for me
Click to expand...
Click to collapse
Is there any way to do this from a terminal app on the device? I just updated and had this happen. I'm suprised more people didn't have an issue/ no general warning went out.
Related
I successfully installed Android Revolution HD 3.1.1 on my HTC Sensation, but now I've lost root. When an app (e.g., Titanium Backup) asks for root rights, it gets denied. BusyBox is installed, and the phone was rooted previously. What could be going on?? Could I really have "lost" root? (I didn't think it was even possible to be running Revolution HD and not be rooted!)
Thanks....
---------- Post added at 09:31 AM ---------- Previous post was at 08:55 AM ----------
Running Root Check, I get the following error report:
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 3.0-beta4 is installed!
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as root
Standard su binary location: ls -l /system/bin/su:
lrwxrwxrwx root root 2011-09-12 10:24 su -> /system/xbin/su
Standard su binary location: ls -l /system/xbin/su:
-rwsr-sr-x root root 22228 2008-08-01 05:00 su
Alternate su binary location:
/sbin/su: No such file or directory
Alternate su type binary location:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
I double checked, and /system/bin/su is there but /system/xbin/su is not. So it seems that somehow su is not configured correctly, but I'm not sure what to do about it. Help!?
---------- Post added at 10:07 AM ---------- Previous post was at 09:31 AM ----------
Hmm. I uninstalled two different BusyBox installers and now I have root again. Don't know why, but things seem okay now. Odd.
Odd, yeah. But great that you got it back.
I found this thread through google, I just have a question for the same problem:
using:
HTC Desire HD
Android Revolution HD 6.1.1
S-OFF
lost ROOT
I've deinstalled root, and reinstalled but without luck. installed beta 3, without luck.
I'm not using busy box. What could I do to get this fixed?
lost root on 6.1.3?
I just installed Revolution HD 6.1.3 with full wipe (upgrading from 5.1.x).
I noticed that /etc/hosts file only contains 1 entry for localhost, when I installed adfree, superuser crashes.
Root checker shows the same as above. Could I lose root?
Looked into downloaded 6.1.3 rom zip and it contains only localhost entry in /etc/hosts.
How can it be? Any ideas?
Thanks.
Got root back
The problem was in superuser version 3.0.4 (which is bundled with revolution hd 6.1.3). Found 3.0.2 version, cleared data of 3.0.4 (Settings-Application-Superuser, stop app, clear data), installed 3.0.2 and root is back.
Hello everyone,
Been following posts here for a little while and I'm aware there is no right place to post this question. I have a rogers SGH-I727R which was rooted via SuperOneClick. After attempting to reinstall busybox I lost root access and can't quite seem to get it back. I've tried going through SuperOneClick to unroot/root however the program hangs and I'm forced to kill the process. The following are my results from "Root Checker Pro":
Superuser Application Status:Superuser application - version 3.0.7 - is installed!System File Properties for Root Access:Standard LocationCheck Command: ls -l /system/bin/su:Result: lrwxrwxrwx root root 2012-01-03 21:20 su -> /system/bin/busyboxAnalysis: File: su is a symbolic link pointing to another file: /system/bin/busyboxStandard LocationCheck Command: ls -l /system/xbin/su:Result: -rwsr-sr-x root root 22228 2012-01-0301:53*suAnalysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!Alternative LocationCheck Command: ls -l /sbin/su:Result: /sbin/su: Permission deniedAnalysis: File system permissions restricted and denied access.Alternative LocationCheck Command: ls -l /system/xbin/sudo:Result: /system/xbin/sudo: No such file or directoryAnalysis: File /system/xbin/sudo does not exist.Root User ID and Group ID Status:SU binary not found or not operating properlySystem Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbinADB Shell Default User:ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1Results provided on your SGH-I727R device
I apologize for the messy format. Any and all help would be greatly appreciated.
- Cam
Forget the one click, amd just use this method http://forum.xda-developers.com/showthread.php?t=1340526
---------- Post added at 03:44 PM ---------- Previous post was at 03:43 PM ----------
For one are you android 2.3.6? Id suggest just following the link i posted
I am currently on 2.3.5 and it is the LTE HD not sure if it makes a difference or not but I noticed I forgot to mention that, thank you for the timely reply.
silver03wrx said:
For one are you android 2.3.6? Id suggest just following the link i posted
Click to expand...
Click to collapse
+1
I could not get SuperOneClick to work after I did the ota update to 2.3.6 with my original SR.
I had to exchange that phone and my replacement is on 2.3.5
SuperOneClick worked on my 2.3.5 phone first try.
---------- Post added at 02:51 PM ---------- Previous post was at 02:49 PM ----------
Never mind. Just saw your reply above.
Not sure about the LTE HD.
Yes it does. The recovery tar is for i727 skyrocket. Dont try it on a different device. I not sure what to tell you as you have a different device.
Root for ZTE z990g aka ZTE Merit
by jcase - [email protected] - http://twitter.com/TeamAndIRC
June 16 2012 - Copyright 2012 CunningLogic
Do Not Distribute or republish without permission. (Sad that this is needed, but people/blogs like to profit off the work of others without credit)
Want to support my work? Donations are always appreciated, but never required:
Paypal: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=LZ62YFU3XCEK8
Amazon Giftcards: [email protected]
Required files:
http://dl.dropbox.com/u/8699733/chainsdd-su.zip
Unzip chaindsdd-su.zip and then get a shell with adb
Code:
adb shell
Set up the dirs, so shell owns them prior to logging. If shell does not own them then we can not control them. If the logs dir already exists, you may have to do a factory reset to remove them. They should not exist unless someone attempted this previously.
Code:
mkdir /data/local/logs
mkdir /data/local/logs/kernel
Open emode's logset activity. First button should be for enabling log set, enable it. Do not exit the activity, but if you do just repeat the below command.
Code:
am start -a android.intent.action.MAIN -n com.zte.emode/.logset
Confirm the log_kernel.txt file exists, if it does not wait a minute and check again.
Code:
ls -l /data/local/logs/kernel/log_kernel.txt
If it exists, delete it and immediately symlink it to /data/local.prop, logset may recreate it, if it does delete and try symlinking again.
Code:
rm /data/local/logs/kernel/log_kernel.txt
ln -s /data/local.prop /data/local/logs/kernel/log_kernel.txt
Now we want to wait for /data/local.prop to be created, it may take a minute or two. Keep checking until it exists.
Code:
ls -l /data/local.prop
Now once /data/local.prop exists, go back to the logset activity and disable logset. If you don't disable it, it will slowly eat away at all the disk space, and possibly overwrite the local.prop before you get root. Now lets set qemu=1 then reboot.
Code:
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
adb reboot
Once you have rebooted, remount, install su.
Code:
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
Clean up your mess!
Code:
adb shell rm /data/local.prop
adb shell rm -r /data/local/logs
Reboot, install the Superuser app from the market and enjoy
Code:
adb reboot
Might Not Work As Expected
I just tried this procedure from JCase at the RootzWiki dot com site with mixed results. The phone is a ZTE Merit Z990G from Straight Talk.
I went through all the steps and everything performed as expected. When I start start an app that requires superuser permissions, the app reports that the device has not been properly rooted. I have repeated the process as outlined four times, including downloading the SU file, and have the same results. Titanium Plus, Busy Box Pro and Root Check Basic report that the device is not rooted.
However, a couple of the Google apps - music, movies and reader seem to think the phone is rooted. Any ideas or suggestions will be very appreciated.
bitshifter52 said:
I just tried this procedure from JCase at the RootzWiki dot com site with mixed results. The phone is a ZTE Merit Z990G from Straight Talk.
I went through all the steps and everything performed as expected. When I start start an app that requires superuser permissions, the app reports that the device has not been properly rooted. I have repeated the process as outlined four times, including downloading the SU file, and have the same results. Titanium Plus, Busy Box Pro and Root Check Basic report that the device is not rooted.
However, a couple of the Google apps - music, movies and reader seem to think the phone is rooted. Any ideas or suggestions will be very appreciated.
Click to expand...
Click to collapse
Sounds like band permissions on su, try
adb shell ls -l /system/xbin/su
if the permissions come out as "-rwsr-sr-x" then you are rooted, try updating su with the suepruser app, or finding a different copy of su.
If the permissions are different or it says it doesnt exist, then you need to repeat the instructions as you missed one or two
jcase said:
Sounds like band permissions on su, try
adb shell ls -l /system/xbin/su
if the permissions come out as "-rwsr-sr-x" then you are rooted, try updating su with the suepruser app, or finding a different copy of su.
If the permissions are different or it says it doesnt exist, then you need to repeat the instructions as you missed one or two
Click to expand...
Click to collapse
Thank you for the fast response. Here are the permissions for the SU file and based on what you are saying they look good:
C:\SDK>adb shell ls -l /system/xbin/su
-rwsr-sr-x root root 22364 2012-06-17 12:47 su
I have located and downloaded a couple of "su" files from XDA and similar sites and the files are identical. I will continue searching for a different "su" file and see if that makes a difference.
---------- Post added at 06:15 PM ---------- Previous post was at 05:43 PM ----------
bitshifter52 said:
Thank you for the fast response. Here are the permissions for the SU file and based on what you are saying they look good:
C:\SDK>adb shell ls -l /system/xbin/su
-rwsr-sr-x root root 22364 2012-06-17 12:47 su
I have located and downloaded a couple of "su" files from XDA and similar sites and the files are identical. I will continue searching for a different "su" file and see if that makes a difference.
Click to expand...
Click to collapse
I looked around and did not find any "su" files that were different than what I downloaded according to the root process. Just for grins I copied the "su" file from my Noot Tablet which is rooted and tried that file. Sadly, it did not make a difference.
Please let me know if there is any other information I can provide or if you would like me to try something else.
What happens when you open the Superuser app (note this is not supersu) and go to settings/options and attempt to update su?
bitshifter52 said:
Thank you for the fast response. Here are the permissions for the SU file and based on what you are saying they look good:
C:\SDK>adb shell ls -l /system/xbin/su
-rwsr-sr-x root root 22364 2012-06-17 12:47 su
I have located and downloaded a couple of "su" files from XDA and similar sites and the files are identical. I will continue searching for a different "su" file and see if that makes a difference.
---------- Post added at 06:15 PM ---------- Previous post was at 05:43 PM ----------
I looked around and did not find any "su" files that were different than what I downloaded according to the root process. Just for grins I copied the "su" file from my Noot Tablet which is rooted and tried that file. Sadly, it did not make a difference.
Please let me know if there is any other information I can provide or if you would like me to try something else.
Click to expand...
Click to collapse
It Worked - But Don't Know Why...
jcase said:
What happens when you open the Superuser app (note this is not supersu) and go to settings/options and attempt to update su?
Click to expand...
Click to collapse
I re-installed Superuser and Superuser Elite and now the phone says it's rooted. I've been in IT for over 35 years and it makes me nervous when software "magically" fixes itself. But now that it's working I won't question it and proceed from here. I appreciate your help and your effort.
Cheers
bitshifter52 said:
I re-installed Superuser and Superuser Elite and now the phone says it's rooted. I've been in IT for over 35 years and it makes me nervous when software "magically" fixes itself. But now that it's working I won't question it and proceed from here. I appreciate your help and your effort.
Cheers
Click to expand...
Click to collapse
Generally you have to run superuser once to get it to work I've found, at least recent builds (or maybe its recent android builds)
Problem.
Hello, i have followed this entirely but at parts it says "Access denied" when im on certain parts when i tryed to check if the Kernel log was there it said "access denied" same with some folders.
root or no root
followed steps, ended up with this...
$ ls -l /system/xbin/su
ls -l /system/xbin/su
-rw-rw-rw- root root 22364 2012-07-15 09:25 su
the superuser app shows all blank under apps and logs, when i try to update it, it says "checking" for a few secs and then nothing... also wondering how to do a factory reset cuz if i didn't screw the phone up yet, i will thx in advance
Has you can see I'm new here. I'm old and retired I would love to root my ZTE Merit 2.3.5 but this is over my head.
I was wondering if there's any accomplished phone rooters in the NC area that would be willing to walk me through this or do this for me
I'd be more than willing to make a donation to make this happen,
custom recovery
I was wondering if someone would make q custom recovery for this phone because the stock recovery is really bad
Not working
I can't even get past step 2, I have the file installed and unzipped on both my computer and my smart phone. The only thing I can find to put in the codes is command prompt which says "error: device not found" when I type in adb shell. My ZTE Merit phone has very low internal memory due to all the retarded system apps that came on the phone, I would very much like some assistance removing them from my phone. I also downloaded superuser elite onto my phone and it doesn't show up with ANYTHING. The first page says
superuse v3.1.3(46)
tap to display changelog
elite installed
su binary not found
a check in the box "outdated binary notification
unchecked box, temp unroot (When tapped it does nothing)
unchecked box ota survival (Again when tapped it does nothing)
I scroll over to the apps section of the program and it says "No apps in list"
What am I doing wrong? This lack of space is quite irritating
Worked!
omg I've wanted to root my phone. Thank you thank you! I thought I would brick my phone at first.
SIM Carrier unlock a ZTE Merit Z990G Straight Talk
I'm currently a T mobile prepaid customer and received the Merit from a friend of mine for doing some painting. I have looked for a month now and had a few unlock websites fail at attempting to unlock the phone via the IMEI (which the phone does have ). I have attempted to put my tmobile sim in the Merit but there is NO place to enter an unlock code. I really DONT wanna change my service to straight talk and would be willing to pay a decent amount to anyone that is capable of unlocking this phone for use with tmobile. If you think you have what it takes PM me and i will give you the IMEI and we can work out a deal. I challenge ANYONE achieve the impossible and get me the unlock code and a way to input it into the phone.
Cannot get local.prop
I have waited 20 minutes after trying to create the local.prop file and it simply won't create it. Any suggestions?
Can't get SU to upload
Hey I'm new to rooting android. I get to the point of installing SU but windows keeps telling me file not found. Would really like some help in fixing this issue. I have installed SU file to C:\Android\android-sdk\SU. Up to this point everything works fine.
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
Any help would be really appreciated.
Thnks
Help getting Started
Hey Anyone and everyone that may be online, I have a real quick and probably REALLY EASY question for ya... I'm trying to get started Rooting my ZTE Merit and I need to find out how to get to or where to find the screen where I type in the commands. I already downloaded the chainsdd zip file. So now I'm supposed to get shell with adb. If someone would be so kind and put me in the right general direction, I sure would
be grateful.
Thanks in advance,
Jason
Not a Damn thing...
Rather sad....I have everything going as it should....all input correct...still no root after final reboot...I followed every step to a T several times -rw-rw-rw- grrr...ive rooted many devices none this big of a pain in tha butt!
Used updated su binary on root just for fun...same result
Help plz!
im a noob to this but have been messing around with ubuntu for some time now can someone show me step by step on how to root my zte merit plz? is there a video tut on how? i tried all the quick methods but they don't work, this one obviously does on this page, can someone help start me out plz, im learning still and love to learn more!
---------- Post added at 08:59 AM ---------- Previous post was at 08:45 AM ----------
Univarseman said:
I can't even get past step 2, I have the file installed and unzipped on both my computer and my smart phone. The only thing I can find to put in the codes is command prompt which says "error: device not found" when I type in adb shell. My ZTE Merit phone has very low internal memory due to all the retarded system apps that came on the phone, I would very much like some assistance removing them from my phone. I also downloaded superuser elite onto my phone and it doesn't show up with ANYTHING. The first page says
superuse v3.1.3(46)
tap to display changelog
elite installed
su binary not found
a check in the box "outdated binary notification
unchecked box, temp unroot (When tapped it does nothing)
unchecked box ota survival (Again when tapped it does nothing)
I scroll over to the apps section of the program and it says "No apps in list"
What am I doing wrong? This lack of space is quite irritating
Click to expand...
Click to collapse
help me, whats the first step then i can get the gearz in motion, i have not a clue on how to start this but if i do i can usually figure it out from them sometimes
Start menu
jjflappy said:
Hey Anyone and everyone that may be online, I have a real quick and probably REALLY EASY question for ya... I'm trying to get started Rooting my ZTE Merit and I need to find out how to get to or where to find the screen where I type in the commands. I already downloaded the chainsdd zip file. So now I'm supposed to get shell with adb. If someone would be so kind and put me in the right general direction, I sure would
be grateful.
Thanks in advance,
Jason
Click to expand...
Click to collapse
Start menu then type CMD hit enter
This will void your warranty, like all root exploits. Use this at your own risk. Do not take OTAs on rooted devices unless you know what you are doing, as it may cause a bootloop or a soft brick.
RockMyMoto is designed for MotoXs that have recieved the Camera update, patching PwnMyMoto. If you are unsure of your firmware, try PwnMyMoto first.
First step is to install Cydia Impactor, by Saurik. http://www.cydiaimpactor.com/ This is required. You will also need adb installed and working, and be comfortable with the command line. Your phone must be on the same network as your PC.
Figure out the ip address of your phone:
adb shell getprop dhcp.wlan0.ipaddress
Click to expand...
Click to collapse
unzip RockMyMoto-{version}.zip and push the exploit and su to /sdcard/:
adb push su /sdcard/
adb push RockMyMoto.jar /sdcard/
Click to expand...
Click to collapse
Run Impactor and select "# start telnetd as system on port 2222", then hit start.
Once the process is complete, run telnet:
telnet {your phone's ipaddress} 2222
Click to expand...
Click to collapse
Run the exploit through telnet
dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
Click to expand...
Click to collapse
The exploit will tell you to use adb to reboot:
adb reboot
Click to expand...
Click to collapse
Run the exploit through telnet for the second time, it will reboot on it's own:
dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
Click to expand...
Click to collapse
Run the exploit through telnet for the third time, it will not reboot:
dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
Click to expand...
Click to collapse
Wait 0-60 seconds, for su to install, then install SuperSu from the market.
Enjoy!
Known issues:
If you have AP isolation mode enabled in your AP (aka WiFi router) you won't be able to connect to your phone via telnet, disable isolation.
Windows users having trouble see here
Amazing! Trying now...
You are the man!!!!!!!!!!
Sent from my XT1060 using Tapatalk
Doing this now. Wonderful job jcase.
Edit: It works.
OMG It worked like a charm! Thank you jcase!!!
one thing though
adb push RockMyMoto-1.0.zip /sdcard/
Click to expand...
Click to collapse
should have been
adb push RockMyMoto.jar /sdcard/
which should have been extracted with su from the zip.
Okay. I have never rooted like this before. Adb = command prompt? Do I need the SDK? Or just the rockmymoto and the other program?
Sent from my XT1060 using Tapatalk
holyevilcow said:
OMG It worked like a charm! Thank you jcase!!!
one thing though
should have been
adb push RockMyMoto.jar /sdcard/
which should have been extracted with su from the zip.
Click to expand...
Click to collapse
Thanks, fixed
Quick question, does this method force us to reboot recovery for system r/w like pwnmymoto?
d4mi3n said:
Quick question, does this method force us to reboot recovery for system r/w like pwnmymoto?
Click to expand...
Click to collapse
yes it does
Works on windows perfectly. AWESOME WORK !
You never cease to amaze. Nice work bro,
Thanks a ton
Sent from my Nexus 7 using Tapatalk
Major Kudoos to Jcase and saurik. Up and running like a boss.
Thanks jcase! Followed your steps and worked like a charm.
Sent from my XT1058 using XDA Premium 4 mobile app
I haven't taken the update so could I just unfreeze apps, unroot, uninstall root apps, take the update, then run this? I don't want to RSD a third time today.
Sent from my Moto Ghost
Thanks bro, amazing work as usual!
Sent from my XT1058 using XDA Premium 4 mobile app
---------- Post added at 03:22 AM ---------- Previous post was at 03:13 AM ----------
Also if anyone is not by a PC you can just type getprop and whatever command to get the info you need using terminal emulator. Just don't type adb shell before getprop. And just typing getprop in terminal emulator will list your whole build.prop or you can just type getprop ro.secure & hit enter & that will tell you whether your s-off or not by listing a 0 or a 1. That was just a example if you just want to find out just 1 line like jcase first command to get your ipaddress. You would just type getprop dhcp.wlan0.ipaddress & hit enter & terminal emulator will list your sensitive data if your not by a PC
Sent from my XT1058 using XDA Premium 4 mobile app
thanks bro! worked beautifully
does anyone know of a way to get the native tethering working after rooting this way on a camera updated vz moto x? thanks
edit: this works: http://forum.xda-developers.com/showthread.php?t=2443562
Quote:
adb push su /sdcard/
adb push RockMyMoto.zip /sdcard/
When I do this step I get an error about no such directory. Please help
---------- Post added at 02:48 AM ---------- Previous post was at 02:38 AM ----------
Now says "read only file system"
---------- Post added at 03:09 AM ---------- Previous post was at 02:48 AM ----------
Okay got past that.
Know saying telnet is not reconized as command
---------- Post added at 03:50 AM ---------- Previous post was at 03:09 AM ----------
Okay I finally got it!! Yay Root!
When I try the telnet action, I get an error that the 'link failed File exists'. If I try to proceed to the next step, same error. My router is an Asus router and I made sure Isolation was unchecked, and there was a setting for telnet (never used this before) and I tried both on and off for that one.
Anybody have a clue how I can get through this?
Thanks!
Hi guys... I'm new here, and I'm losing my hope resolving my problem.
at first I have my rooted phone with kingroot installed, and I installed busybox and worked fine with root apps.
it start when I got confused to move busybox in /system/bin since it is not available in system/xbin. at first it can't install. what I did was I changed permission to r/w of system/bin try to install busybox applet in there and it succeas . but it gave me a big problem. my kingroot failed to recognize I'm rooted or I have lost my root? or root access. I tried rooting it but it can't go. it only get to 70% as always but failed. and I lost a high rate of succession. actually my first root was fast and ez.
I tried checking my su and root with some root/su checkup.
using DevCheck available in GPlaystore, it says
"Device is rooted" and
Busybox: "system/bin/busybox".
upon using RootCheckerBasic , its says " Sorry! Root access is not properly installed in this device."
and using Busybox Checker... its gives Busybox Available: YES
Path: /system/xbin, and SuperUser gives
Su Available: YES
Su access given: NO
Path: /system/xbin/su
Version info busybox and su: both not found.
so please help me with this. for the future this would be helpful.
mobile: Cherry mobile astro 2 (Philippines)
Model: Q490
Android: 5.1 lollipop
sc7731c
You need to unlock the bootloader
Hello, from what you said, that it happened after moving BusyBox to /system/bin instead of /system/xbin?
but there must be files for bb in /system/xbin and /system/bin
and if bb gives you the option to uninstall do it.
and then, reboot
---------- Post added at 04:50 AM ---------- Previous post was at 04:49 AM ----------
thaiphuoc1 said:
You need to unlock the bootloader
Click to expand...
Click to collapse
read the whole thread before posting, we apprentice that you are trying to help, but copying the same statement all over the forum won't help, read the post first