Database Info

need help rooting flipside

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. :/

Changing SuperUser App.

Hii GuyZz... I had a problem and wanna help from you.
My problem is that I had rooted my Karbon A6 From VRoot Software but It gived me a Chinese Superuser.
I had installed supersu from market and then removed the Chinese one. But nothing happened. I had losted my Root access and have to reroot my device via the VRoot Software.
And again that Chinese superuser camed.
Kindly plz help me to change my superuser app.
Thanks In Advance.....

ShubhamDubey said:
Hii GuyZz... I had a problem and wanna help from you.
My problem is that I had rooted my Karbon A6 From VRoot Software but It gived me a Chinese Superuser.
I had installed supersu from market and then removed the Chinese one. But nothing happened. I had losted my Root access and have to reroot my device via the VRoot Software.
And again that Chinese superuser camed.
Kindly plz help me to change my superuser app.
Thanks In Advance.....
Click to expand...
Click to collapse
Here we have 2 scenarios; the first is easy and the second is salty..!!
I hope you got the first scenario; since the second one is handy..!!!
The first scenario: you got custom recovery too:
If so, just get cwm SuperSU from here and flash it in cwm.
Other scenario if you didn't had custom recovery:
- Keep the previous root.
- Download SuperSU with su binary from same thread in previous scenario.
- Extract the content in a folder (we will call it SS so you could follow the procedure) and move it to your sdcard. The SS folder contains su and Superuser.apk).
- Download Terminal Emulator from Google play.
- Open Terminal Emulator and write this code:
Code:
su
mount -o remount,rw /system
dd if=/sdcard/SS/su of=/system/xbin/su
chown root.root /system/xbin/su
chmod 06755 /system/xbin/su
ln -s /system/xbin/su /system/bin/su
Remember to hit enter in between those lines. Don't close Terminal Emulator now, just hit home button to minimize it.
- Now by any root explorer, go to /system/app and delete the Chinese superuser (don't do normal uninstall, you need to delete the apk from /system/app).
- Return back to Terminal Emulator which is still running and write these codes:
Code:
dd if=/sdcard/SS/Superuser.apk of=/system/app/Superuser.apk
chmod 0644 /system/app/Superuser.apk
- Now reboot your device.

Is there any easy method Coz I'm beginner in programming.....

Please help me I don't understand which file to download from previous scenario as I open the thread I don't understand which file to download... if you can share the link..
Thanks in advance.

[Q] SuperSu Installation fails, cannot root

Hi,
I was rooted on my Galaxy S3 I535 (Verizon) on 4.1 and took the 4.3 OTA update as is. Now I am unable to use the Saferoot method because when I launch SuperSu and get the popup to update su, it fails every time (using normal or twrp methods). I've wiped the phone but get the same thing each time. I'm running the latest SuperSU 1.9.3 and I'm wondering if it's failing because of old files that are not getting wiped for whatever reason? Can anyone show me how to manually delete any previous su/root files using adb or terminal emulator?
Thanks

Backup important pics, videos, and docs that are located in your phone storage. You will need to Odin flash the VRUCML1 tar then run Saferoot. You can download the 1+ GB file from my link below. Unzip it then use Odin to flash the entire tar or tar.md5. Doing this will format your phone's storage.
http://forum.xda-developers.com/showthread.php?t=2586319
Sent from my SCH-I535 using Tapatalk 4

shark_dude said:
Hi,
I was rooted on my Galaxy S3 I535 (Verizon) on 4.1 and took the 4.3 OTA update as is. Now I am unable to use the Saferoot method because when I launch SuperSu and get the popup to update su, it fails every time (using normal or twrp methods). I've wiped the phone but get the same thing each time. I'm running the latest SuperSU 1.9.3 and I'm wondering if it's failing because of old files that are not getting wiped for whatever reason? Can anyone show me how to manually delete any previous su/root files using adb or terminal emulator?
Thanks
Click to expand...
Click to collapse
Give this a try while phone connected to PC, run "adb shell" command, you should see $ prompt, then run "/system/xbin/su", you see root's # prompt. Please verify this before we proceed further.

buhohitr said:
Give this a try while phone connected to PC, run "adb shell" command, you should see $ prompt, then run "/system/xbin/su", you see root's # prompt. Please verify this before we proceed further.
Click to expand...
Click to collapse
Confirmed, I get the # prompt after running "/system/xbin/su"
Titanium backup says it's not rooted via the /system/bin/su attempt and every root checker app fails as well although it seems like I'm rooted via command line?

shark_dude said:
Confirmed, I get the # prompt after running "/system/xbin/su"
Titanium backup says it's not rooted via the /system/bin/su attempt and every root checker app fails as well although it seems like I'm rooted via command line?
Click to expand...
Click to collapse
Type:
mount -o remount,rw /system
rm /system/bin/su
mount -o remount,ro /system
Now run SuperSU app in the phone, it should update binary ok and prompt you to reboot.

buhohitr said:
Type:
mount -o remount,rw /system
rm /system/bin/su
mount -o remount,ro /system
Now run SuperSU app in the phone, it should update binary ok and prompt you to reboot.
Click to expand...
Click to collapse
Done. It seems to be working as expected now (so far). Now I'm assuming I can run Saferoot again?

shark_dude said:
Done. It seems to be working as expected now (so far). Now I'm assuming I can run Saferoot again?
Click to expand...
Click to collapse
No, once you update SuperSu and reboot, you should be rooted. No need to run saferoot.

buhohitr said:
No, once you update SuperSu and reboot, you should be rooted. No need to run saferoot.
Click to expand...
Click to collapse
Ah, yes I'm rooted now! Thank you for the assistance as well as to you SlimSnoopOS for the unbrick method, I wasn't aware of that solution yet.
So what exactly was my problem? Did the Saferoot script crap out at some point leaving the necessary files on the phone but not fully set up yet to keep root privileges?

shark_dude said:
Ah, yes I'm rooted now! Thank you for the assistance as well as to you SlimSnoopOS for the unbrick method, I wasn't aware of that solution yet.
So what exactly was my problem? Did the Saferoot script crap out at some point leaving the necessary files on the phone but not fully set up yet to keep root privileges?
Click to expand...
Click to collapse
The issue was you already have none working superuser as root on the phone (from previous install) then you tried to install supersu through saferoot and your phone is using the old superuser as default instead of the new supersu. So basically the command execute the right root which is supersu, then removed the old superuser, this will allow the supersu to update the binary and now your phone is using the default supersu as root.

buhohitr said:
The issue was you already have none working superuser as root on the phone (from previous install) then you tried to install supersu through saferoot and your phone is using the old superuser as default instead of the new supersu. So basically the command execute the right root which is supersu, then removed the old superuser, this will allow the supersu to update the binary and now your phone is using the default supersu as root.
Click to expand...
Click to collapse
Nice work! Thanks for finding that fix.
Sent from my SCH-I535 using Tapatalk 2

buhohitr said:
The issue was you already have none working superuser as root on the phone (from previous install) then you tried to install supersu through saferoot and your phone is using the old superuser as default instead of the new supersu. So basically the command execute the right root which is supersu, then removed the old superuser, this will allow the supersu to update the binary and now your phone is using the default supersu as root.
Click to expand...
Click to collapse
Gotcha, thanks again! I appreciate the prompt responses :good:

i cnt see $ prom
buhohitr said:
Give this a try while phone connected to PC, run "adb shell" command, you should see $ prompt, then run "/system/xbin/su", you see root's # prompt. Please verify this before we proceed further.
Click to expand...
Click to collapse
i also got the same problem whre i cnt root,,its always failed. so now when i run using 'adb shell' i cant see the $ promt. i just see ''install and memo file'' what should i do? sorrry my bad english.

DrunkenZombie said:
i also got the same problem whre i cnt root,,its always failed. so now when i run using 'adb shell' i cant see the $ promt. i just see ''install and memo file'' what should i do? sorrry my bad english.
Click to expand...
Click to collapse
Just continue with the following command:
/system/xbin/su hit enter, you should see the # prompt. Then do the following:
mount -o remount,rw /system
rm /system/bin/su
mount -o remount,ro /system
Now run SuperSU app in the phone, it should update binary ok and prompt you to reboot.

NEED HELP Rooting a ZTE WHIRL

I have tried to root this phone it does root but it is only temperorary it goes away after reboot.
I got busyinstalled in the /system/bin but no SU
The system is RO
I have tried this code to no avail
busybox mount-o remount,rw /dev/block/mmcblk0p18
cant be found in proc/mounts
busybox dd if=/sdcard/cwm.img of=/dev/block/mmcblk0p18
permmsion denied
I used framaroot and it said sucess then it said binary cant be installed any help would be great a thnk you ahead of time

se7encircles said:
I have tried to root this phone it does root but it is only temperorary it goes away after reboot.
I got busyinstalled in the /system/bin but no SU
The system is RO
I have tried this code to no avail
busybox mount-o remount,rw /dev/block/mmcblk0p18
cant be found in proc/mounts
busybox dd if=/sdcard/cwm.img of=/dev/block/mmcblk0p18
permmsion denied
I used framaroot and it said sucess then it said binary cant be installed any help would be great a thnk you ahead of time
Click to expand...
Click to collapse
I've tried to root the ZTE Whirl also with the same results as you. It is my understanding that it cannot be permanently rooted unless the write protection is disabled. I read on other forums that this was done on the HTC One X and Motorola MOTOX with a recovery installed zip. I don't know if the file in the zip "wp_mod.ko" would work on the ZTE Whirl and without access to the RUU, I really don't know how an update zip could be made. I'm no developer but this is my understanding from my research.

se7encircles said:
I have tried to root this phone it does root but it is only temperorary it goes away after reboot.
I got busyinstalled in the /system/bin but no SU
The system is RO
I have tried this code to no avail
busybox mount-o remount,rw /dev/block/mmcblk0p18
cant be found in proc/mounts
busybox dd if=/sdcard/cwm.img of=/dev/block/mmcblk0p18
permmsion denied
I used framaroot and it said sucess then it said binary cant be installed any help would be great a thnk you ahead of time
Click to expand...
Click to collapse
Download Vroot.. turn on USB Debugging..and tick on usb debugging to active it on your phone setting/developer option
connect your phone to pc..and wait untill it detect..click root...and it will reboot..done..only one click root..i use this already 2 year..work find..if this help..press thank button :laugh::good::laugh:

Daniel Dunhill said:
Download Vroot.. turn on USB Debugging..and tick on usb debugging to active it on your phone setting/developer option
connect your phone to pc..and wait untill it detect..click root...and it will reboot..done..only one click root..i use this already 2 year..work find..if this help..press thank button :laugh::good::laugh:
Click to expand...
Click to collapse
Vroot cannot root this device at all. Framaroot can root device. The problem is that the system is write protected. In other words, it is temporary until you reboot etc. I have found that if I already have Supersu.apk installed when I root that I will have super user permissions etc., however, when I open Supersu and attempt to update binaries, it fails and root is immediately lost. I have also rooted and used Total commander to remount r/w and could paste files to system directories etc. but SuperSU still failed to update and lost root. When I attempt to install SuperSU or any zip via stock recovery, it verifies etc but in the end aborts installation. I am beginning to thing that its not just write protected but active defense against any changes to system from stock. BTW, you don't have to drain the battery to root: When I loose root (after restart etc.) I uninstall Framaroot apk, shut down device (not restart), start device, install Framaroot and am able to root with Gandalf option.
Bottom line: This write protection or whatever it is needs to be removed or disabled for root to be permanent.

Daniel Dunhill said:
Download Vroot.. turn on USB Debugging..and tick on usb debugging to active it on your phone setting/developer option
connect your phone to pc..and wait untill it detect..click root...and it will reboot..done..only one click root..i use this already 2 year..work find..if this help..press thank button :laugh::good::laugh:
Click to expand...
Click to collapse
Try using pootdebug.apk

[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?