Database Info

OMG I can´t Root!!!

Hello guys,
So, I am extremely frustrated with LG. Besides linger for a lifetime upgrade their phones, yet it seems to create some blocking to simple process root.
I've been researching on the web about the root of Optimus Black (the unit is good, what is bad is the LG) and all processes seem to be complicated.
I need help from you guys to see if I can finally give this blessed root to my device. He is with version 2.3.4 (just the model is P970h),the firmware is the V20a. I Want to apply a custom rom and play with it a bit, since LG has not given up any indicative of whether or not to launch the ICS on it (maybe who knows when Google launched Android 12.1, or the man get to Mars. ..)
I have faced some problems and I will report here to see if they can help me.
Problem # 1:
I can not under any circumstances recognize the phone on my pc (win vista home basic ¬ ¬).
I've tried everything. I downloaded the drivers directly with LG and nothing ... I downloaded the personnel that provided the xda forum and nothing ...The windows is insistently asking such a CDC serial driver (something of the sort ...) and the phone just not recognized.
Already installed, reinstalled the drivers and nothing! I have installed the LG PC sync and nothing to .. (Seems that my phone and my pc just does not want to share the same connection!)
I don´t have another pc (unfortunately) so I can´t install the drivers.
Simply for this reason I can´t install Clockworkmod, or do any procedure that requires root install drivers on pc (root unlock, blackjack, oneclick...)
2nd Problem:
I've been reading that there is a apk root tools for the phone, the Gingerbreak. But apparently this not works on my phone. It is infinitely loading and does not reboot.
I installed the 1.1 and 1.2 versions and nothing!
I run the Root Checker Pro App and get the log:
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
The SuperSU application is an alternative application for managing root access.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-xr-x shell shell 0 2012-08-29 23:49 su
Analysis: Setuid attribute present BUT root user ownership NOT present. Root access is NOT correctly configured for this file!
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your LG-P970h device by Root Checker Pro version 1.2.8 from joeykrim in the Android Market
Click to expand...
Click to collapse
So can anybody help me to root my phone??

Don't have an LG, i have an Samsung and rooted with this app SuperOneClick (http://forum.xda-developers.com/showthread.php?t=803682), and searching through the forum i saw this thread ( http://forum.xda-developers.com/showthread.php?p=22495442&highlight=optimus+black#post22495442 ), a user that succeeded root of an Lg Optimus Black.
But I only have an Samsung so I can't guarantee that will work.
Hope to have helped.
Best regards!

Wo retusou
pjm_9 said:
Don't have an LG, i have an Samsung and rooted with this app SuperOneClick (http://forum.xda-developers.com/showthread.php?t=803682), and searching through the forum i saw this thread ( http://forum.xda-developers.com/showthread.php?p=22495442&highlight=optimus+black#post22495442 ), a user that succeeded root of an Lg Optimus Black.
But I only have an Samsung so I can't guarantee that will work.
Hope to have helped.
Best regards!
Click to expand...
Click to collapse
So,
I can´t connect my phone to my pc... I don´t know why!!

Anyone can help me?
Sent from my GT-P6800 using xda app-developers app

Here's what I did.
I was having the same problem, seemingly. I went to Android Central and learned about an app called kingo root.
First, I went to LG and downloaded the drivers for USB connection to my Win7 64 PC. After they loaded, I made sure the E980 was configured to install programs from PC via USB, instead of charge only. Also, I set debugging on. Then, I hooked up the USB cable. Then, a window came up asking if I wanted to use LG Programs, which I replied OK. Then it said I was connected successfully. Went to the PC, installed kingo root (google it) and it ran a program or two that rooted the device. Piece o' cake!
Since then, I downloaded freegee and twrp, rebooted into recovery and installed CM11. KitKat goodness!
Ken

[Q] Corrupted root?

Let me start this acknowledging my own idiocy. I have been rooted for a long time this morning I think I screwed myself. My S3 has been prompting me for the OTA and I have been ignoring it. However this morning when my alarm when off, my blind groping to shut it off ended up initiating the OTA. The update took, and as expected, I lost my root.
I didn't have a custom ROM so I decided all I need is my root back and life will be fine. I looked up how to root with the 4.3 update and came across the safe root method. I went through this process and everything went smoothly until the reboot. Once the phone came back up I tried to run SuperSU and was met with the message that "Installation Failed! Reboot and try again." Several attempts at rebooting, uninstalling, and rerunning safe root changed nothing.
I ran a terminal emulator and tried to run /system/bin/su and was greeted with an error. I then tried to run /system/xbin/su and got the prompt from SuperSU to grant root access. I approved and when I open SuperSU I can see terminal emulator is on the list approved applications (although it still crashes when trying to update).
I decided to try Root Checker to see what it had to say and got this output:
>Root Access is not properly configured or was not granted.
>
>Super User Application Status:
>SuperSU application - version 1.86 - is installed!
>
>System File Properties for Root Access:
>Standard Location
>Check Command: ls -l /system/bin/su:
>Result: -rwxr-xr-x root shell 380532 2013-07-22 14:41 su
>Analysis: Setuid attribute is NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
>
>Standard Location
>Check Command: ls -l /system/xbin/su:
>Result: -rwsr-sr-x root root 104800 2014-01-08 18:12 su
>Analysis: Setuid attribute is present and root user ownership is present. Root access is correctly configured for this file! Executing this file can >grant root access!
>
>Alternative Location
>Check Command: ls -l /sbin/su:
>Result: /sbin/su: Permission denied
>Analysis: File system permissions restricted and denied access.
>
>Alternative Location
>Check Command: ls -l /system/xbin/sudo:
>Result: /system/xbin/sudo: No such file or directory
>Analysis: File /system/xbin/sudo does not exist.
>
>Root User ID and Group ID Status:
>SU binary not found or not operating properly
>
>System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
>
>ADB Shell Default User:
>ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Is there a way to repair this root? Or have a screwed myself with the OTA update?

Choboking said:
Let me start this acknowledging my own idiocy. I have been rooted for a long time this morning I think I screwed myself. My S3 has been prompting me for the OTA and I have been ignoring it. However this morning when my alarm when off, my blind groping to shut it off ended up initiating the OTA. The update took, and as expected, I lost my root.
Is there a way to repair this root? Or have a screwed myself with the OTA update?
Click to expand...
Click to collapse
Quickest way is backup all your stuff, do a factory reset, then Odin this factory ML1 firmware http://www.androidfilehost.com/?fid=23269279319199798 ..then try to root again with saferoot.

[Q] Latest kitkat update no more ROOTED DEVICE

I updated my motorola xoom to 4.4.2 3 weeks ago
(thread []http://forum.xda-developers.com/showthread.php?t=2593757&__utma=248941774.598456778.1394750856.1394750856.1394750856.1&__utmb=248941774.2.10.1394750856&__utmc=248941774&__utmx=-&__utmz=248941774.1394750856.1.1.utmcsr=google|utmccn=%28organic%29|utmcmd=organic|utmctr=%28not%20provided%29&__utmv=-&__utmk=22130616 ) -
all was excellent I got my xoom functioning like new - received update for my OS 3 or 5 days ago (Version from Screenshot of my Xoom http://imgur.com/ekkKd0J ) which i did to update the current 4.4.2 and worked like a CHARM;
just opened Titanium Backup said device NOT ROOTED. used root checker Pro, Supersu, Superuser and all show device not rooted.
Downloaded TWRP and reinstalled but did not hlep.
ROOT CHECKER PRO gives the following analysis so please hope someone can help me. (I can see a solution in the analysis below but dunno wot to do) Cheers, Roger
Root Checker Pro:
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - version 1.93 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-sr-x root root 71140 2008-08-01 16:00 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your Xoom LTE device by Root Checker Pro version 1.2.8 from joeykrim in the Android Market - http://goo.gl/NcnHn

TheKicKer69 said:
I updated my motorola xoom to 4.4.2 3 weeks ago
(thread []http://forum.xda-developers.com/showthread.php?t=2593757&__utma=248941774.598456778.1394750856.1394750856.1394750856.1&__utmb=248941774.2.10.1394750856&__utmc=248941774&__utmx=-&__utmz=248941774.1394750856.1.1.utmcsr=google|utmccn=%28organic%29|utmcmd=organic|utmctr=%28not%20provided%29&__utmv=-&__utmk=22130616 ) -
all was excellent I got my xoom functioning like new - received update for my OS 3 or 5 days ago (Version from Screenshot of my Xoom http://imgur.com/ekkKd0J ) which i did to update the current 4.4.2 and worked like a CHARM;
just opened Titanium Backup said device NOT ROOTED. used root checker Pro, Supersu, Superuser and all show device not rooted.
Downloaded TWRP and reinstalled but did not hlep.
ROOT CHECKER PRO gives the following analysis so please hope someone can help me. (I can see a solution in the analysis below but dunno wot to do) Cheers, Roger
Root Checker Pro:
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - version 1.93 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-sr-x root root 71140 2008-08-01 16:00 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your Xoom LTE device by Root Checker Pro version 1.2.8 from joeykrim in the Android Market - http://goo.gl/NcnHn
Click to expand...
Click to collapse
I see that you have omni. Have you tried reflashing the root from omni thread?

Until now I only followed to the letter that Thread and this is how i jumped from 4.2 to 4.4.2; and in that thread it clearly says if u r upgrading from that update u won't need to wipe so when i got the notification 4 or 5 days ago there is a newer update to 4.2.2 I did and it went smooth only thing that went berserk is it says device ain't rooted.
Dunno wot else to do (I reinstalled like i said above latest TWRP [used to use CWM but if i need to update i will have to wipe everything as the thread says] and Supersu)
tx for the help,
Roger

I think I can help you
TheKicKer69 said:
Until now I only followed to the letter that Thread and this is how i jumped from 4.2 to 4.4.2; and in that thread it clearly says if u r upgrading from that update u won't need to wipe so when i got the notification 4 or 5 days ago there is a newer update to 4.2.2 I did and it went smooth only thing that went berserk is it says device ain't rooted.
Dunno wot else to do (I reinstalled like i said above latest TWRP [used to use CWM but if i need to update i will have to wipe everything as the thread says] and Supersu)
tx for the help,
Roger
Click to expand...
Click to collapse
Hi Roger,
Boy, I don't know how to stress this enough. Before doing anything, make a backup. After you are finished, you should reinstall your programs from the backup manually. Don't do an automatic reinstallation as there are some CM11 Program files that would make the Omnirom installation go into an endless loop.
CM11 has the Su built into it. If you use Omnirom you should first clear your Dalvik Cache and Cache, preferably doing a factory reset before installing your Rom as I mentioned about looping above.. You might want to install a newer Gapps file, as well as flashing a Superuser file-this last is a must with Omnirom
These 3 files should all be installed from your external sdcard. Just be careful not to format either of your sdcards.

k, I did a full install just like in the thread and for some strange reason it is still NOT rooted! wot gives lol. (remember the first time i did it i got my xoom working flawlessly.
is there any other thread that also provides kitkat for my xoom - i really don't care about omni or any other developer just need to have my xoom with latest kitkat.
tx,
Roger

TheKicKer69 said:
k, I did a full install just like in the thread and for some strange reason it is still NOT rooted! wot gives lol. (remember the first time i did it i got my xoom working flawlessly.
is there any other thread that also provides kitkat for my xoom - i really don't care about omni or any other developer just need to have my xoom with latest kitkat.
tx,
Roger
Click to expand...
Click to collapse
keeps getting weirder and weirder! This is from Root Access Pro! wth is going on? (remember did complete reflashing and followed all steps that i did the 1st time when it worked flawlessly - and yes i did d/l Superuser and SuperSu and also reflashed SuperSu that comes with the thread for updating)
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - is NOT installed!
The Superuser application, available in the Android Market, is recommended for managing root access.
SuperSU application - is NOT installed.
The SuperSU application is an alternative application for managing root access.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 104800 2014-03-28 14:52 su
Analysis: Setuid attribute NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your Xoom LTE device by Root Checker Pro version 1.2.8 from joeykrim in the Android Market - http://goo.gl/NcnHn

[Resolved] [Q] Help needed rooting G Pro! T_T

*Since this problem can happen to other LG devices, I'm writing here.
-Summarized Question for Busy XDAers-
1.Installed su binary and busybox through Android System Recovery 3e.
2.Can get root access from LG Recovery mode, half access on ordinary boot+adb shell, Permission denied on terminal emulator app. SuperSu not working, and 'root' is granting permission every 5 minutes.
3.HELP PLEASE!
-Full Question-
Maybe it can be a real noobish question, but I need help rooting my G Pro.
LG started Kitkat update a week ago, and G Pro also got Kitkat update.
I tried to root my device using old methods, and new methods for other G devices, but none of them worked.
So! I tried making one for me, using Android System Recovery 3e(maybe it could be a problem?)
I booted my device to recovery using
Code:
'adb reboot recovery'
and sideloaded zip file containing su binary and busybox.
Of course I signed it with testkey, so I could get SuperSu, su binary, and busybox installed on my system.
But, after rebooting my device, I felt something went wrong.
I typed
Code:
'su'
command on terminal enulator, and got
Code:
'Permission Denied'
error.
Assuming it's related to permission and owner of su binary, I tried
Code:
ls -al /system/bin/su
.
Here's the result:
Code:
[email protected]:/ $ su
Permission denied
1|[email protected]:/ $ ls -al /system/bin/su
-rwsr-sr-x root root 85096 2008-08-01 21:00 su
It seems...nothing's wrong!
So I tried with adb, and got # without asking Superuser app.
But I couldn't mount system, as well as other commands require root access.
I removed SuperSu and downloaded Superuser by ChainsDD, but that didn't work.
Instead, I could see on log that 'root' was granting permission every 5 minutes.
Not knowing what the problem is, I rebooted device to LG recovery(diffrent from Android Recovery 3e).
I could access adb from there, and got root access and removed some garbage apps.
Then, it means su binary and busybox is working.
What is the problem??? Please help!
EDIT:It was binary version problem lol

[Working]Root Kindle Fire HD8 6th Gen

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?