Related
I have rooted my G2X and since changing roms didn't do anything to help fix the rebooting issues I've decided to send it back for a different one. I just want to make sure that I won't have a problem once they get my phone. I followed the instructions at http://forum.xda-developers.com/showthread.php?p=14159600#post14159600 but for some reason when I click unroot it seems to get stuck at a certain point.
I did make a backup of the ROM that came with the phone, but i also tried a few custom ROMs as well as trying the LG updated ROM. Currently if I open Android Terminal Emulator and type 'su' it gives me a permission denied error. If I try the 'Root Checker" app under basic it will say the phone isn't rooted and busybox isn't installed but when I go under advanced half the time I click verify it'll say it's not rooted and other times it will say it is rooted... so it's confusing me. Advanced still shows busybox as not installed, so it's just root that changes between rooted and not rooted under advanced in root checker.
Root Checker Basic > "Sorry, you don't have root access. For detailed output, please use the advanced mode" - It will say that EVERY time I try.
Root Checker Advanced >
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - is not installed!
The application Superuser is recommended as it provides basic security and is available for free in the android market.
Standard su binary location:
/system/bin/su: No such file or directory
Standard su binary location:
/system/xbin/su: No such file or directory
Alternate su binary location: /sbin/su: Permission denied
SU binary not found in the system declared PATH
Then if I hit Verify Root again it may show the above a few times, but eventually (sometimes 1 click after) it will show:
Congratulations! You have root access!
Superuser.apk - com.noshufou.android.su - is not installed!
The application Superuser is recommended as it provides basic security and is available for free in the Android Market
Standard su binary location:
/system/bin/su: No such file or directory
Standard su binary location:
/system/xbin/su: No such file or directory
Alternate su binary location:
/sbin/su: Permission denied
Root user id:
Root not properly returning its user id
Root group id:
Root not properly returning its group id
So I guess I'm wondering why it's showing as not rooted EVERY time under basic, but showing rooted and unrooted under advanced. If terminal emulator is giving su a permission denied error instead of a # doesn't that mean it's not rooted? Sorry for the long post, but I can't take the chance of sending the phone back rooted. Also, when I used the LG Update it updated my baseband to July 15th which isn't the one that came with the phone or the one that was with the stock rom i'm using now... could that be an issue? If anyone can help me I'd really appreciate it, thanks!
Also, since when I used the LG update it updated my baseband is it possible to revert it back to the stock baseband that was on it when I purchased the phone?
since you already did the LG update it seems like with the new baseband- why not use the stock 2.3.3 rom found here:
http://forum.xda-developers.com/showthread.php?t=1196019
i believe that after you flash this rom you will lose root- so you should be able to send back to tmobile with no prob- just make sure to flash back to stock recovery.
thanks for the reply, was actually in the process of doing that as you posted lol... thanks again, appreciate the help, at least now i know i'm going in the right direction ^_^
I installed 2.3.3, flashed back to stock recovery... terminal emulator still gives permission denied when i type 'su' and root checker still says not rooted for basic and switches between rooted and not rooted under advanced... is there a way to verify my phone isn't rooted besides root checker? I don't want to send back a rooted phone and the root checker is giving me mixed results under advanced so i don't know what to do at this point
i have a motorola flipside with 2.2.2 installed. somehow it lost its root and will not reroot z4root keeps shuting down and giving some odd error saying The application z4root (process com.z4mod.z4root) has stopped unexpectedly. Please try again and leaves only the option to force close the app. i left gingerbreak running all night and when i woke up it was still running not getting anywhere theyed superoneclick it will not finish im getting very fustrated with this phone i even went as far as asuming somthing on the phone went bad and flashed it to a stock att rom and still cannot get the root to finish and apply. is there some way i can mannualy root this phone? also yes usb debuging is on allow unknown aps to install is enabled
anyone please this dam phone is practicaly useless without a root to me id rather be using my stupid windows 7 phone at this rate because at least it had my ringtones and allowed me to use a different backround image than stock att ones.
---------- Post added at 02:09 PM ---------- Previous post was at 01:47 PM ----------
ok i have come accross this but i am a little lost at the steps
wiki.rootzwiki.com/index.php/Motorola_Flipside
it says to download 3 files psneuter busybox and super user unzip the downloads into the same folder. then it says to open a terminal and change to the folder i dont understand this what am i suposed to to? it then says i need android sdk installed and working witch i do i installed it for android screencast. then it says adb devices but does not say how im suposed to enter this command. after that im fairly sure its from the cmd entering the commands shown on that link. can anyone tell me how to get throgh the first few steps please?
copyed from link
Manual Root
[edit] Download
psneuter: Download
Superuser: Download
busybox: Download
Unzip the downloaded files into the same folder
Open a terminal and change to the folder.
You need the android SDK and ADB working. To make sure type:
adb devices
if your device lists, then you are ready to go!
[edit] Gain Root
Run the following commands:
adb push psneuter /data/local/temp/psneuter
adb shell
chmod 755 /data/local/temp/psneuter
./data/local/temp/psneuter
ADB should hang, wait a little while and then type:
adb shell
NOTE: You should have the "#" sign instead of the "$". If you do, you have temporary root, and can continue on.
Type:
exit
adb push busybox /data/local/temp/busybox
adb shell
chmod 755 /data/local/temp/busybox
./data/local/temp/busybox mount -o rw,remount /system
The last command should return nothing
update i learned how to do the procedure and finished sucesfully however the phone is still not rooted. i did reboot the phone after it seems faster now but not rooted.i downloaded the root checker app and scaned the phone it emailed me a log and here is that log
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 2.3.6.3 is installed!
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
/sbin/su: Permission denied
Alternate su type binary location: ls -l /system/xbin/sudo:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your MB508 device by Root Checker version 3.7 from joeykrim in the Android Market
is it even posible to root this phone?
i guess im not allowed to be helped or somthing.
i have a procedure here that i had to build up from 2 seperate write ups. i had to use this one http://androidforums.com/droid-all-...oid-without-rsd-lite-up-including-frg83d.html along with this one together http://wiki.rootzwiki.com/index.php/Motorola_Flipside to get it to root properly.
here is what i did. u will need the downloads from both links for this to work i beleive. follow the steps from the second link to gain root once u get to where the number simbole is shown in the command line u need to switch to the instructions in link 1 and start at step 13 and follow to the end. this works to root your flipside when nothing els will work at least for me it did none of the apps that are suposed to root for you worked for me.
thank you me for having to figure this out on my own have fun
Problem rooting
I rooted my Flipside at its stock state and it worked fine. And then I upgraded my software to 2.2.2 Froyo and lost the root so now I am trying to reinstall z4root and re-root the phone but z4root now doesn't work. It gets successfully installed but when I hit PERMANENT ROOT it just stays in that window with the turning wheel and gets stuck there. It doesn't completely root. I've tried the hard reset by pulling the battery, and hitting the back key and forced closing it and then trying it again. Nothing works! HELP!
I once had a flipside. I rooted it the stock rom and then updated to gingerbread and then rooted again. I used superoneclick though. I'm not sure which version, but there is (or was) a flipside forum here on xda with documentation on the entire process.
Edit: here's the forum link: http://forum.xda-developers.com/forumdisplay.php?f=772
jovanphilip said:
I once had a flipside. I rooted it the stock rom and then updated to gingerbread and then rooted again. I used superoneclick though. I'm not sure which version, but there is (or was) a flipside forum here on xda with documentation on the entire process.
Edit: here's the forum link: http://forum.xda-developers.com/forumdisplay.php?f=772
Click to expand...
Click to collapse
Really? I thought the only upgrade I can do to it is from stock to Froyo. How'd you do that? I'm sorry. I am totally untechie. :/
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.
i can't find any way to root my phone.. anyone can help me?? i tried to flash j100h prerooted rom but it didn't work.. thanks
same
same here. my phone sm j100f cant root . any method that can use ? i try other root tools . but its failed . and other thing . my phone got stuck up in samsung logo . but i fix it using firmware
up.. anyone can help us???
yurusaki said:
i can't find any way to root my phone.. anyone can help me?? i tried to flash j100h prerooted rom but it didn't work.. thanks
Click to expand...
Click to collapse
Try to root using Kingoroot, Framaroot or VRoot.
up for this...
no success with all available tools till date.......... anyone if successful in rooting, plz update here
Me too.... i can't find any way to root my phone
up for this thread!! still no way to root///
up!! anyone can help us?? thanks
yurusaki said:
up!! anyone can help us?? thanks
Click to expand...
Click to collapse
I managed to root it using Odin and ROOT FOR J100FN BY HOSAM KASHTO
I can't post links so search for root-j100fn-1969414 and go to the .gsmhosting.com site
Now i'm stuck to unlock it. Managed to get the nv_data.bin but i can't find the correct value to unlock it and i've got no ide what to look for.
use frama root app
Tp root. Your phone use frama root app hear is a xda link
http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
Did you root your j1 if yes can you send me the keyboard, message and new call screen(small call screen app).
i am facing the same problem bro. Can you please tell me from where i can download the firmwhere?
My phone stucked on samsung logo. Please help!
the root by hosam makes the phone show it is rooted but thats it. i don't get any root access on the apps
tried to push the su and busybox to bin but output is access denied. read-only
my phone is now rooted. just follow the instruction by hosam kashto .. search it (j100f hosam kashto) and it will appear.. up
yurusaki said:
my phone is now rooted. just follow the instruction by hosam kashto .. search it (j100f hosam kashto) and it will appear.. up
Click to expand...
Click to collapse
what firmware version did you use?
I was able to root mine after a lot of tries.
First install the boot image by hosam kashto (using odin)
you need adb on your computer.(Get it in C:\Users"username"\AppData\Local\Android\sdk\platform-tools [if you have android studio] be sure to hold down the shift key while right-clicking to get the open comand prompt option in the context menu).
when you run "adb shell" you should see [email protected]:/ # (this means your phone has root access but you can't use it on any apps unless you have the su and busybox binaries).
in the same "adb shell" command input mount -ro remount,rw /system (it will make the system partition writable so you can run a rooting app) [I used kingo root but if there is a better option you can tell me]
after kingo root is done you'll be able to run apps as root but there is one issue. any time i tried using another superuser apk that isn't kingosu the rooting had to be done over from the point of using kingo root
I hope this helps
---------- Post added at 11:15 AM ---------- Previous post was at 11:10 AM ----------
In short you can use "mount -ro remount,rw /system" in adb shell
then push the su and busybox binaries to the bin, sbin, and xbin. (push su in bin, sbin and xbin; busybox should be in xbin only)
"mount -o remount,ro /system" makes the system read-only again, I didn't use it but i am not sure if that will cause a problem
User33333 said:
I was able to root mine after a lot of tries.
First install the boot image by hosam kashto (using odin)
you need adb on your computer.(Get it in C:\Users"username"\AppData\Local\Android\sdk\platform-tools [if you have android studio] be sure to hold down the shift key while right-clicking to get the open comand prompt option in the context menu).
when you run "adb shell" you should see [email protected]:/ # (this means your phone has root access but you can't use it on any apps unless you have the su and busybox binaries).
in the same "adb shell" command input mount -ro remount,rw /system (it will make the system partition writable so you can run a rooting app) [I used kingo root but if there is a better option you can tell me]
after kingo root is done you'll be able to run apps as root but there is one issue. any time i tried using another superuser apk that isn't kingosu the rooting had to be done over from the point of using kingo root
I hope this helps
---------- Post added at 11:15 AM ---------- Previous post was at 11:10 AM ----------
In short you can use "mount -ro remount,rw /system" in adb shell
then push the su and busybox binaries to the bin, sbin, and xbin. (push su in bin, sbin and xbin; busybox should be in xbin only)
"mount -o remount,ro /system" makes the system read-only again, I didn't use it but i am not sure if that will cause a problem
Click to expand...
Click to collapse
what firmware version did you use ?
J100fnxxu0aoc2
Oops. For SM-J110F, not J100F.
Ladies and Gentleman,
I was able to root the HD8 6th Gen using Kingoroot while in airplane mode. I download the executable and ran it directly from my computer. My Fire tablet is on version 5.3.1.1 and was never registered with Amazon. I can run su in adb but the SuperUser app is not working on my tablet. I am looking into replacing the KingoRoot SuperUser app with SuperSU. I suggest you block updates as soon as you achieve root.
look at this thread to see if you can remove Kingroot and replace
https://forum.xda-developers.com/am...rtool-root-t3272695/post69855730#post69855730
This applied to 7" but may be same issue you are having. Note I would suspect you at least need to install the app since you used the PC version but then that might allow replacement fully. The Rootjunky script basically installs supersu and removes the kingroot app following this approach: https://www.droidmen.com/remove-kingroot-kinguser-with-supersu/
So now the questions are:
* Does the app work too or just PC version
* Does a device which has been used and registered with Amazon work? I am on 5.3.1.1, have OTA disabled, have Novalauncher sort of working, and managed to get Amazon to disable the ads lock screen but right now the device does not leave home due to Opendns constraints as I did not want to lose 5.3.1.1 while waiting.
Decided to try this on 5.3.2.1, ran Kingroot for PC few times (version 3.4.0 build 1142). Did not work. Hope it works for you 5.3.1.1 guys.
I believe 5.3.2 can be downgraded to 5.3.1.1 but I also believe 5.3.2.1 is confirmed to not be downgradable.
I was lucky and got my BF unit with 5.3.1.1 and blocked OTA right away
I register to reply this thread and tell everyone that 5.3.1.1 CAN BE ROOT using KingoRoot(not KingRoot)
blocked OTA and planning to place Kingoroot with Supersu now.
go kingoapp.c0m(replace 0 with o) and download the PC one.
Tried APK one but seems stuck at 90% or not enough patient?
---------- Post added at 05:17 PM ---------- Previous post was at 05:12 PM ----------
chemie99 said:
look at this thread to see if you can remove Kingroot and replace
https://forum.xda-developers.com/am...rtool-root-t3272695/post69855730#post69855730
This applied to 7" but may be same issue you are having. Note I would suspect you at least need to install the app since you used the PC version but then that might allow replacement fully. The Rootjunky script basically installs supersu and removes the kingroot app following this approach: https://www.droidmen.com/remove-kingroot-kinguser-with-supersu/
So now the questions are:
* Does the app work too or just PC version
* Does a device which has been used and registered with Amazon work? I am on 5.3.1.1, have OTA disabled, have Novalauncher sort of working, and managed to get Amazon to disable the ads lock screen but right now the device does not leave home due to Opendns constraints as I did not want to lose 5.3.1.1 while waiting.
Click to expand...
Click to collapse
my device is registered with amazon and it works
Detailed instruction on post#38
so what is difference between
kingoroot
and kingroot
??
I am familiar with Kingroot but kingoroot seems to be another animal? Is kingo safe? We have a total of 3 lifetime posts from two accounts who are speaking its benefits....
chemie99 said:
so what is difference between
kingoroot
and kingroot
??
I am familiar with Kingroot but kingoroot seems to be another animal? Is kingo safe? We have a total of 3 lifetime posts from two accounts who are speaking its benefits....
Click to expand...
Click to collapse
honestly I dunno, I'm new to android, just bought the kindle to start playing with android...
but I found it difficult to replace the kingoroot with supersu, when I type su in terminal, it show nothing, can't give root permission to terminal emulator.
I replaced kingoroot with supersu following instruction from androidforums.com/threads/script-replace-kingoroot-with-supersu.919175/
After it's done, supersu doesn't prompt for root access. So I set 'default access' to 'grant' in supersu settings, and it seems to be working.
g4ry12 said:
Decided to try this on 5.3.2.1, ran Kingroot for PC few times.
Click to expand...
Click to collapse
I was not paying attention, it's KingoRoot, not KingRoot. Downloaded KingoRoot for PC (v1.4.9), and tried on 5.3.2.1. Rooting failed, unfortunately.
I ran the PC kingo and rooted.
I then tried to remove and replace with supersu and it failed
I lost root
I tried to rerun Kingo PC but it wanted debugging enabled even though it was
tried the apk kingo (from kingoapp.com; playstore it is a adware hack)
got stuck at 90%
exited and kindle was really sluggish; maybe something to do with my novalauncher or something?
power off reboot and stuck in boot up (Fire image). Now can't boot.
Message is be careful with kingo when removing....will try restore now.
Edit: wiping data and cache did not help. Did brick recovery to 5.3.1.1 (which is what it was on when I got it), and managed to recover. Glad I don't have to send this one back to Amazon!
I will now restart kingo root effort and if it works will report back steps (including supersu replacement).
So I have root according to kingo but "root checker basic" says I do not have root.
Try to open "superuser" (which is a kingo superuser app) and it is just a blank screen then back to Home.
The removal tool that @2ig2ag linked did not work.
It failed on "mount -w -o remount /system" with "mount: operation not permitted"
I also tried to manual cp the su file over and get error "read only file system"
Edit: Despite kingo saying you have root, you don't. At least not complete root. I am unable to copy anything into system/app via ES File explorer too. I am unable to grant programs that want access, that access. For example, Titanium BackUp is unable to detect "Su and Busybox" so no go.
I am able to pm disable the firelauncher for example but that is about it
chemie99 said:
So I have root according to kingo but "root checker basic" says I do not have root.
Try to open "superuser" (which is a kingo superuser app) and it is just a blank screen then back to Home.
The removal tool that @2ig2ag linked did not work.
It failed on "mount -w -o remount /system" with "mount: operation not permitted"
I also tried to manual cp the su file over and get error "read only file system"
Edit: Despite kingo saying you have root, you don't. At least not complete root. I am unable to copy anything into system/app via ES File explorer too. I am unable to grant programs that want access, that access. I am able to pm disable the firelauncher for example but that is about it
Click to expand...
Click to collapse
I soft-bricked once, stuck at fire logo, sideload adb and resumed normal.
I didn't use the root checker to check, the superuser included will crash when I launch it,
but I can su in adb shell..
@2ig2ag's way not work for me either,
I cannot run the script, it said permission denied, then I try to run it manually,
I can remount /system, it do not show any error, but I am stopped at "cp ./su /system/xbin/daemonsu",
it said "daemonsu" text file in use.
tried ultra explorer as another way to get to /system and it just locks up when trying to detect root.
Tried manually installing supersu.apk and it locks up and requires reboot to get back to working device.
@phpbb88 I retried "mount -w -o remount /system" and it worked; maybe I wasn't in su at the time. I get the same error on file copy
So to summarize:
you can: adb su
you can: pm disable fire launcher and OTA (not sure if unrooted allows this too?)
you can not:
write to /system
install any apk that require root and grant root access
switch to supersu
adb remount (fails)
I would not call this a successful root. I am not even sure of the pm disables will last more than 24 hours.
chemie99 said:
tried ultra explorer as another way to get to /system and it just locks up when trying to detect root.
Tried manually installing supersu.apk and it locks up and requires reboot to get back to working device.
@phpbb88 I retried "mount -w -o remount /system" and it worked; maybe I wasn't in su at the time. I get the same error on file copy
So to summarize:
you can: adb su
you can: pm disable fire launcher and OTA (not sure if unrooted allows this too?)
you can not:
write to /system
install any apk that require root and grant root access
switch to supersu
adb remount (fails)
I would not call this a successful root. I am not even sure of the pm disables will last more than 24 hours.
Click to expand...
Click to collapse
I am using a file explorer called "ES File explorer", it cannot view the system file when it is not root.
After Kingoroot, I can view them, but I still cannot create file in /system by using that File explorer.
However I can successfully create a dir in /system in adb shell, shown below.
[email protected]:/system # mkdir 123
[email protected]:/system # ls
123
app
bin
build.prop
data
etc
fonts
framework
lib
lib64
lost+found
media
priv-app
recovery-from-boot.p
sbin
security
sqfs
tts
usr
vendor
xbin
[email protected]:/system #
I have made progress...with kingo install I did this:
copy the files of the kingo root removal to sdcard/kingo
adb shell
su
mount -w -o remount /system
cd /sdcard/kingo
cp ./su /system/xbin/daemonsu
fails because it is locked. Then I started to think that the steps were for the kingo app and not the PC so
with adb window still open, run PC program and remove root
then
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
./step1.sh
got some errors
then sideload the supersu apk via ES file explorer
then allow supersu to do it thing and reboot.
Now I have supersu running!''
edit:
but do I have root?
Titanium backup still fails but ultra explorer does say it has root
now adb shell su fails.....
chemie99 said:
I have made progress...with kingo install I did this:
copy the files of the kingo root removal to sdcard/kingo
adb shell
su
mount -w -o remount /system
cd /sdcard/kingo
cp ./su /system/xbin/daemonsu
fails because it is locked. Then I started to think that the steps were for the kingo app and not the PC so
with adb window still open, run PC program and remove root
then
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
./step1.sh
got some errors
then sideload the supersu apk via ES file explorer
then allow supersu to do it thing and reboot.
Now I have root with supersu!
Titanium backup still fails but ultra explorer does say it has root
Edit: hmmm..
now adb shell su fails.....
Click to expand...
Click to collapse
I cannot run the step1.sh, still show permission denied.
I tried manually, but got another permission error...
[email protected]:/sdcard/Kingo # cp ./su /system/xbin/daemonsu
[email protected]:/sdcard/Kingo # chmod 0755 /system/xbin/daemonsu
[email protected]:/sdcard/Kingo # daemonsu -d &
[1] 8434
[email protected]:/sdcard/Kingo # ./step1.sh
sh: ./step1.sh: can't execute: Permission denied
[1] + Done daemonsu -d
126|[email protected]:/sdcard/Kingo # cp ./su /system/xbin/su
[email protected]:/sdcard/Kingo # chmod 0755 /system/xbin/su
[email protected]:/sdcard/Kingo # ./chattr.pie -ia /system/xbin/ku.sud
sh: ./chattr.pie: can't execute: Permission denied
126|[email protected]:/sdcard/Kingo # ./chattr.pie -ia /system/xbin/supolicy
sh: ./chattr.pie: can't execute: Permission denied
126|[email protected]:/sdcard/Kingo #
after the errors, did you install supersu.apk?
I ignored the errors thinking they were from differences between kingo apk and kingo PC versions of what they put on device.
Supersu does manage to install itself but root checker still says I do not have root.
chemie99 said:
after the errors, did you install supersu.apk?
I ignored the errors thinking they were from differences between kingo apk and kingo PC versions of what they put on device
Click to expand...
Click to collapse
I didn't finish all the steps in step1.sh, cause I have installed SuperSU at the beginning of time,
I then try to run Supersu and it said blahblahblah error, need to reboot my device.
wola, i lost my connection to root adb shell, and now going to root it again
phpbb88 said:
I didn't finish all the steps in step1.sh, cause I have installed SuperSU at the beginning of time,
I then try to run Supersu and it said blahblahblah error, need to reboot my device.
wola, i lost my connection to root adb shell, and now going to root it again
Click to expand...
Click to collapse
I only install supersu as the step after running step1; it worked, and took hold (at least no errors and opening the program looks normal). The issue is that it won't grant access to anything (TB, flashfire, etc)
chemie99 said:
I only install supersu as the step after running step1; it worked, and took hold (at least no errors and opening the program looks normal). The issue is that it won't grant access to anything (TB, flashfire, etc)
Click to expand...
Click to collapse
Kingoroot PC asked me to grant root access to it by pressing OK on my device's pop up when my device is under root,
but my device wouldn't show anything.
Is there any problem on fire OS that wouldn't show this pop up?