Related
Please help before installing and apply nvidia patch my games like plant vs zombie running without problem.
but after unsuccessful attempt of play nvidia games on my deivce Samsung SGSL i9003.
i uninstall this, set plugin to default and uninstall drivers.
But Still my games are no longer running.
I face problem with plant vs zombie. it crash as it start but before chainfire3d it run perfectly.
waiting for reply asap..
manrock111 said:
Please help before installing and apply nvidia patch my games like plant vs zombie running without problem.
but after unsuccessful attempt of play nvidia games on my deivce Samsung SGSL i9003.
i uninstall this, set plugin to default and uninstall drivers.
But Still my games are no longer running.
I face problem with plant vs zombie. it crash as it start but before chainfire3d it run perfectly.
waiting for reply asap..
Click to expand...
Click to collapse
bro the same problem happened to my phone so i reflashed my custom rom.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
I have the same problem. Chainfire caused me many problems. I want to completely remove it, but I can't.
I put another ROM and whiped data, and it still makes problems. Please help!
manrock111 said:
Please help before installing and apply nvidia patch my games like plant vs zombie running without problem.
but after unsuccessful attempt of play nvidia games on my deivce Samsung SGSL i9003.
i uninstall this, set plugin to default and uninstall drivers.
But Still my games are no longer running.
I face problem with plant vs zombie. it crash as it start but before chainfire3d it run perfectly.
waiting for reply asap..
Click to expand...
Click to collapse
Hy i have same problem . Can you solve this problem? /clear completly chainfire3d/
Same problem, I used to be able to run The Settlers and other games, now I can't..
I uninstalled drivers, set plugin to default, then uninstalled the app, but still it doesn't work
Having root access from recovery is a must to solve problems if you run into them (run "/system/lib/cf3d_uninstall.sh" as root to remove the driver and restore the old one)
1. boot into jb recovery mode
2. run "adb devices" - to make sure the phone drivers are ok (should output a long hex string and "device")
3. run "adb shell" from command prompt
4. in shell prompt "sh system/lib"
5. still in shell "sh /cf3d_uninstall.sh"
phone will reboot and you have working jb system
- it worked for me but no guarantee it'll work for you!
hope it helps.
if sh /cf3d_uninstall.sh doesnt work , try 'sh /system/lib/cf3d_uninstall.sh" instead.
another solve
guys at first i tried to use adb
i got no permissions
so i thought i can use terminal emulator
first open terminal emulator
write SU and give terminal the superuser rights
now use the command
"/system/lib/cf3d_uninstall.sh"
or
"sh /cf3d_uninstall.sh"
after success
your phone will stop giving orders and responding
now you can remove the battery and you are done
ty i hope i helped
mido1122 said:
guys at first i tried to use adb
i got no permissions
so i thought i can use terminal emulator
first open terminal emulator
write SU and give terminal the superuser rights
now use the command
"/system/lib/cf3d_uninstall.sh"
or
"sh /cf3d_uninstall.sh"
after success
your phone will stop giving orders and responding
now you can remove the battery and you are done
ty i hope i helped
Click to expand...
Click to collapse
Under JB, I don't find any system/lib folder at all... Any idea where's the chainfire3D placed in it?
Same problem in my gt2 p3100
manrock111 said:
Please help before installing and apply nvidia patch my games like plant vs zombie running without problem.
but after unsuccessful attempt of play nvidia games on my deivce Samsung SGSL i9003.
i uninstall this, set plugin to default and uninstall drivers.
But Still my games are no longer running.
I face problem with plant vs zombie. it crash as it start but before chainfire3d it run perfectly.
waiting for reply asap..
Click to expand...
Click to collapse
please help chainfire3d has spoiled my android gaming life.
Terminal emulator displaying ''not found''
mido1122 said:
guys at first i tried to use adb
i got no permissions
so i thought i can use terminal emulator
first open terminal emulator
write SU and give terminal the superuser rights
now use the command
"/system/lib/cf3d_uninstall.sh"
or
"sh /cf3d_uninstall.sh"
after success
your phone will stop giving orders and responding
now you can remove the battery and you are done
ty i hope i helped
Click to expand...
Click to collapse
Terminal emulator displaying ''not found''
dailyuse17 said:
Terminal emulator displaying ''not found''
Click to expand...
Click to collapse
Below is my Logs:
######## Below was executed from Windows command prompt. I have "adb.exe" installed in the Desktop\404 ##########
C:\Users\Chu\Desktop\404>adb kill-server
C:\Users\Chu\Desktop\404>adb wait-for-device
* daemon not running. starting it now *
* daemon started successfully *
C:\Users\Chu\Desktop\404>adb shell
########## After you've executed 'adb shell', i will login to the phone as user shell ##########
[email protected]:/ $ su
########## You have to switchuser to root to gain full access, as seen below, you are "root" ##########
[email protected]:
# cd /system
cd /system
[email protected]:/system # cd lib
cd lib
########## Above, i change directory to /system/lib ##########
[email protected]:/system/lib # ls cf*
ls cf*
cf3d_uninstall.sh
########## Found the file to be cf3d_uninstall.sh and execute the shell script with the command below ##########
[email protected]:/system/lib # sh cf3d_uninstall.sh
sh cf3d_uninstall.sh
rm failed for /system/lib/cf3d_sh, No such file or directory
usage: reboot [-n] [-p] [rebootcommand]
########## There, the phone will restart, and you'll get back your phone. Just ignore the "no such file or directory" error above. It'll still work ##########
Good luck.
manchuks said:
Below is my Logs:
######## Below was executed from Windows command prompt. I have "adb.exe" installed in the Desktop\404 ##########
C:\Users\Chu\Desktop\404>adb kill-server
C:\Users\Chu\Desktop\404>adb wait-for-device
* daemon not running. starting it now *
* daemon started successfully *
C:\Users\Chu\Desktop\404>adb shell
########## After you've executed 'adb shell', i will login to the phone as user shell ##########
[email protected]:/ $ su
########## You have to switchuser to root to gain full access, as seen below, you are "root" ##########
[email protected]:
# cd /system
cd /system
[email protected]:/system # cd lib
cd lib
########## Above, i change directory to /system/lib ##########
[email protected]:/system/lib # ls cf*
ls cf*
cf3d_uninstall.sh
########## Found the file to be cf3d_uninstall.sh and execute the shell script with the command below ##########
[email protected]:/system/lib # sh cf3d_uninstall.sh
sh cf3d_uninstall.sh
rm failed for /system/lib/cf3d_sh, No such file or directory
usage: reboot [-n] [-p] [rebootcommand]
########## There, the phone will restart, and you'll get back your phone. Just ignore the "no such file or directory" error above. It'll still work ##########
Good luck.
Click to expand...
Click to collapse
my phone camera doesnot work well due to chainfire3d how to uninstall completely . at this time i m completely uninstall the chai fire 3d but camera does not work . my camera shows the blur photos when in the camera mode
How to do this when installed it by mistake on samsung gt-i9505 please? thanks.
---------- Post added at 02:36 AM ---------- Previous post was at 02:05 AM ----------
Ok, like i didn't see the file in the folders concerned, this saved me (applied it without looking or searching the file i didn't see). big up and thanks.
http://forum.xda-developers.com/showpost.php?p=39301435&postcount=8
Help me please...
bolibo said:
Having root access from recovery is a must to solve problems if you run into them (run "/system/lib/cf3d_uninstall.sh" as root to remove the driver and restore the old one)
1. boot into jb recovery mode
2. run "adb devices" - to make sure the phone drivers are ok (should output a long hex string and "device")
3. run "adb shell" from command prompt
4. in shell prompt "sh system/lib"
5. still in shell "sh /cf3d_uninstall.sh"
phone will reboot and you have working jb system
- it worked for me but no guarantee it'll work for you!
hope it helps.
Click to expand...
Click to collapse
Hi.. i tried what you have suggest but still not able to recover my phone...please help me
:crying::crying::crying::crying::crying::crying::crying:
:\android-sdk-windows\platform-tools>adb devices
List of devices attached
0123456789ABCDEF device
C:\android-sdk-windows\platform-tools>adb shell
[email protected]:/ $ sh /system/lib/cf3d_uninstall.sh
sh /system/lib/cf3d_uninstall.sh
mount: Operation not permitted
/system/lib/cf3d_uninstall.sh[4]: can't create /system/lib/libGLESv1_CM.so: Read
-only file system
Unable to chown /system/lib/libGLESv1_CM.so: Read-only file system
Unable to chown /system/lib/libGLESv1_CM.so: Read-only file system
Unable to chown /system/lib/libGLESv1_CM.so: Read-only file system
Unable to chown /system/lib/libGLESv1_CM.so: Read-only file system
Unable to chmod /system/lib/libGLESv1_CM.so: Read-only file system
/system/lib/cf3d_uninstall.sh[11]: can't create /system/lib/libGLESv2.so: Read-o
nly file system
Unable to chown /system/lib/libGLESv2.so: Read-only file system
Unable to chown /system/lib/libGLESv2.so: Read-only file system
Unable to chown /system/lib/libGLESv2.so: Read-only file system
Unable to chown /system/lib/libGLESv2.so: Read-only file system
Unable to chmod /system/lib/libGLESv2.so: Read-only file system
rm failed for /system/lib/cf3d_uninstall.sh, Read-only file system
rm failed for /system/lib/cf3d_sh, No such file or directory
usage: reboot [-n] [-p] [rebootcommand]
reboot: Operation not permitted
reboot: Operation not permitted
reboot: Operation not permitted
reboot: Operation not permitted
reboot: Operation not permitted
reboot: Operation not permitted
1|[email protected]:/ $
Help
Hello, guyz. the solution for this problem is that you should unistalled the divers you have installed to reduce the graphics (which u have installed in chainfire 3d) unistalled it and you are ready play your game again with the same graphic which you have earlier
thanks!
manju_xda said:
Hi.. i tried what you have suggest but still not able to recover my phone...please help me
:crying::crying::crying::crying::crying::crying::crying:
:\android-sdk-windows\platform-tools>adb devices
List of devices attached
0123456789ABCDEF device
C:\android-sdk-windows\platform-tools>adb shell
[email protected]:/ $ sh /system/lib/cf3d_uninstall.sh
sh /system/lib/cf3d_uninstall.sh
mount: Operation not permitted
/system/lib/cf3d_uninstall.sh[4]: can't create /system/lib/libGLESv1_CM.so: Read
-only file system
Unable to chown /system/lib/libGLESv1_CM.so: Read-only file system
Unable to chown /system/lib/libGLESv1_CM.so: Read-only file system
Unable to chown /system/lib/libGLESv1_CM.so: Read-only file system
Unable to chown /system/lib/libGLESv1_CM.so: Read-only file system
Unable to chmod /system/lib/libGLESv1_CM.so: Read-only file system
/system/lib/cf3d_uninstall.sh[11]: can't create /system/lib/libGLESv2.so: Read-o
nly file system
Unable to chown /system/lib/libGLESv2.so: Read-only file system
Unable to chown /system/lib/libGLESv2.so: Read-only file system
Unable to chown /system/lib/libGLESv2.so: Read-only file system
Unable to chown /system/lib/libGLESv2.so: Read-only file system
Unable to chmod /system/lib/libGLESv2.so: Read-only file system
rm failed for /system/lib/cf3d_uninstall.sh, Read-only file system
rm failed for /system/lib/cf3d_sh, No such file or directory
usage: reboot [-n] [-p] [rebootcommand]
reboot: Operation not permitted
reboot: Operation not permitted
reboot: Operation not permitted
reboot: Operation not permitted
reboot: Operation not permitted
reboot: Operation not permitted
1|[email protected]:/ $
Click to expand...
Click to collapse
You must be rooted to do that.
Help!!
El_Dark said:
You must be rooted to do that.
Click to expand...
Click to collapse
Hi, i'm a boy from Finland. I have the same problem as "manju_xda" but i have the root permissions in my device..
The question is.. .. I'm stucked with chainfire 3d and my adb shell tells that "adbd cannot run as root in production builds" .. What to do?
And sorry for my bad english
For those who found this thread on Google, I found my solution in here: http://forum.xda-developers.com/showthread.php?t=2362873
This will only work if you can access a root prompt (#) in adb shell! THIS WAS DONE AFTER DOING A WIPE FROM THE VOLUME DOWN MENU WHEN BOOTING THE PRIME! I do not know if this will work without the wipe, but it very well may. Maybe someone more knowledgeable can chime in here.
It may be possible to restore from a su-backup if you have a su binary still in /system/bin or xbin. Even if you can't access a root prompt (#) by just typing su, read starting at page 6. Places to look for a su-backup include /system/ /system/usr/we-need-root/ and /system/bin/
I have a batch script in the works that will determine if you can re-root and take the appropriate steps to do so if possible.
I had to do a voldown wipe after my update to JB. My prime would reboot after 5-10 seconds into the homescreen after boot. After wiping, I thought for sure my root was screwed until a new exploit was found.
I accessed my device through adb, and realized that I could invoke a root prompt using the su command at the $ prompt. Using ES file explorer, I could see su in /system/bin/ but no su-backup or superuser.apk in /system/app/.
I tried simply installing superuser from the market, but it did not work. The busybox installer would not work, either.
ATTACHED ARE THE EXACT THREE FILES I USED. I do not know if using different version will affect the process!
Here is what worked for me:
1. adb shell
2. su
(# - you should see this now! This will not work without this specific prompt!)
3. type 'exit' press enter, and then 'exit' again. You will now be back at the regular command prompt.
4. adb push C:\(location of attached files)\superuser.apk /data/local/tmp
5. adb push C:\(location of attached files)\su /data/local/tmp
6. adb push C:\(location of attached files)\busybox /data/local/tmp
7. Access the adb shell again, and type su
8. chmod 644 /data/local/tmp/superuser.apk
9. chmod 755 /data/local/tmp/busybox
10. chmod 6755 /data/local/tmp/su
11. mount -o remount,rw /system
12. dd if=/data/local/tmp/Superuser.apk of=/system/app/Superuser.apk
13. dd if=/data/local/tmp/busybox of=/system/bin/busybox
14. dd if=/data/local/tmp/busybox of=/system/xbin/busybox
14a. Chmod 755 /system/bin/busybox
14b. Chmod 755 /system/xbin/busybox
15. Reserved
16. busybox rm /system/bin/su
17. busybox cp /data/local/tmp/su /system/bin
18. type su once again to assure you still have access to the # prompt
18a. Chmod 644 /system/app/superuser.apk
18b. mount -o remount,ro /system
19. type exit, and exit again, returning to the regular windows command prompt.
20. type 'adb reboot' (without quotes)
NOTE - you will not need to install the superuser.apk app in the normal sense. It will be installed upon the reboot as a system app automatically!
21. Once your prime has rebooted, go download root checker basic or the like from the play store. Open it, and wait for your superuser prompt!
22. Get the busybox installer from the play store as well, and use that to get the newest version of busybox.
23. Get SuperSU from the market. It seems to be the safest method to keep root with JB...
ALSO! Make sure to keep a backup root with voodoo or super su after completing this guide! I have lost root (VERY WELL may have been my own fault... too much poking around) Anyway, better safe than sorry!!!
Thanks to daymz from the debugfs thread in development for the basic instructions of what needed to be done!! And also thanks to all before me who got us root in the first place!
I will answer questions to the best of my ability. I am not a developer and do not try to present myself as so... I can tinker with the best, and after losing root, I set out to see if I could figure it out!
Changes made as per tsmt971
I have fellow this method and it was failed at step 16 in my case because of the permission issue but I managed to make it move and regained the root. The details of the issue as below.
Step 16 failed because step 13, 14 which will copy busybox to /system/bin and /system/xbin with a wrong executive permission.
To correct in my case: after step 13, 14 follow those steps below:
- chmod 755 /system/bin/busybox
- chmod 755 /system/xbin/busybox
- skip step 15
- continue steps 16, 17, 18
- chmod 644 /system/app/Superuser.apk
- continue step 19, 20, 21, 22
Then you will get your root back, it worked in my case. Good luck guys.
To the OP, please verify and update those steps if necessary.
[email protected] said:
I have fellow this method and it was failed at step 16 in my case because of the permission issue but I managed to make it move and regained the root. The details of the issue as below.
Step 16 failed because step 13, 14 which will copy busybox to /system/bin and /system/xbin with a wrong executive permission.
To correct in my case: after step 13, 14 follow those steps below:
- chmod 755 /system/bin/busybox
- chmod 755 /system/xbin/busybox
- skip step 15
- continue steps 16, 17, 18
- chmod 644 /system/app/Superuser.apk
- continue step 19, 20, 21, 22
Then you will get your root back, it worked in my case. Good luck guys.
To the OP, please verify and update those steps if necessary.
Click to expand...
Click to collapse
Thanks! Confirmed...it was late
It helped me. THX!!
thenrz said:
This will only work if you can access a root prompt (#) in adb shell!
Click to expand...
Click to collapse
Can anyone help me get ADB back. It worked fine before the update but now I can't get it to recognise the device at all - just get the blank list and device not found when I am connected. The drivers look fine like before in Device Manager when I plug in (Asus Android Composite ADB Interface). I have switched USB Debugging on and do not have Asus Sync installed. Everything on the ADB side works with my phone OK.
I used Rootkeeper to restore root after upgrade though it now seems that was only partial. I did a factory reset to clear out a few gremlins. Now Rootkeeper has the Root permission granted box unchecked but the rest checked but I guess since it doesn't have root access anymore it won't do anything. I have tried uninstall and reinstall Superuser but it fails at updating the binary.
Any suggestions to get ADB back much appreciated .
thenrz said:
This will only work if you can access a root prompt (#) in adb shell! THIS WAS DONE AFTER DOING A WIPE FROM THE VOLUME DOWN MENU WHEN BOOTING THE PRIME! I do not know if this will work without the wipe, but it very well may. Maybe someone more knowledgeable can chime in here.
I had to do a voldown wipe after my update to JB. My prime would reboot after 5-10 seconds into the homescreen after boot. After wiping, I thought for sure my root was screwed until a new exploit was found.
I accessed my device through adb, and realized that I could invoke a root prompt using the su command at the $ prompt. Using ES file explorer, I could see su in /system/bin/ but no su-backup or superuser.apk in /system/app/.
I tried simply installing superuser from the market, but it did not work. The busybox installer would not work, either.
ATTACHED ARE THE EXACT THREE FILES I USED. I do not know if using different version will affect the process!
Here is what worked for me:
1. adb shell
2. su
(# - you should see this now! This will not work without this specific prompt!)
3. type 'exit' press enter, and then 'exit' again. You will now be back at the regular command prompt.
4. adb push C:\(location of attached files)\superuser.apk /data/local/tmp
5. adb push C:\(location of attached files)\su /data/local/tmp
6. adb push C:\(location of attached files)\busybox /data/local/tmp
7. Access the adb shell again, and type su
8. chmod 644 /data/local/tmp/superuser.apk
9. chmod 755 /data/local/tmp/busybox
10. chmod 6755 /data/local/tmp/su
11. mount -o remount,rw /system
12. dd if=/data/local/tmp/Superuser.apk of=/system/app/Superuser.apk
13. dd if=/data/local/tmp/busybox of=/system/bin/busybox
14. dd if=/data/local/tmp/busybox of=/system/xbin/busybox
14a. Chmod 755 /system/bin/busybox and /system/xbin/busybox
15. Reserved
16. busybox rm /system/bin/su
17. busybox cp /data/local/tmp/su /system/bin
18. type su once again to assure you still have access to the # prompt
18a. Chmod 644 /system/app/superuser.apk
19. type exit, and exit again, returning to the regular windows command prompt.
20. type 'adb reboot' (without quotes)
NOTE - you will not need to install the superuser.apk app in the normal sense. It will be installed upon the reboot as a system app automatically!
21. Once your prime has rebooted, go download root checker basic or the like from the play store. Open it, and wait for your superuser prompt!
22. Get the busybox installer from the play store as well, and use that to get the newest version of busybox.
Thanks to daymz from the debugfs thread in development for the basic instructions of what needed to be done!! And also thanks to all before me who got us root in the first place!
I will answer questions to the best of my ability. I am not a developer and do not try to present myself as so... I can tinker with the best, and after losing root, I set out to see if I could figure it out!
Changes made as per tsmt971
Click to expand...
Click to collapse
I accessed my device through adb, and invoked a root prompt using the su command at the $ prompt. Using ES file explorer, I saw su in /system/bin/ but no su-backup or superuser.apk in /system/app/. Followed the steps. After completing the steps, and rebooting, I have Superuser.apk in system/app, however with root checker, root not found!
Install busybox installer says that my device is rooted, but install failed.
No root for me
Edit: I got it. I am now rooted. Thanks for everyone's assistance!
RootKeeper says that I have:
- Superuser app installed (yes)
- Device rooted (no)
- Root permission granted (no)
- /system supports root protection (yes)
- Protected su copy available (yes)
However, I can't get true SU and the # prompt. When I enter shell and type 'su' I get:
1|[email protected]:/
So, I'm stuck at instruction #11 when I attempt to mount /system as rw.
Any ideas if I'm still eligible to root this baby?
work beautifully for me!! :good::good:
now have root after a wipe.
thanks for sharing mdpgc.
Failed Step
thenrz said:
This will only work if you can access a root prompt (#) in adb shell! THIS WAS DONE AFTER DOING A WIPE FROM THE VOLUME DOWN MENU WHEN BOOTING THE PRIME! I do not know if this will work without the wipe, but it very well may. Maybe someone more knowledgeable can chime in here.
I had to do a voldown wipe after my update to JB. My prime would reboot after 5-10 seconds into the homescreen after boot. After wiping, I thought for sure my root was screwed until a new exploit was found.
I accessed my device through adb, and realized that I could invoke a root prompt using the su command at the $ prompt. Using ES file explorer, I could see su in /system/bin/ but no su-backup or superuser.apk in /system/app/.
I tried simply installing superuser from the market, but it did not work. The busybox installer would not work, either.
ATTACHED ARE THE EXACT THREE FILES I USED. I do not know if using different version will affect the process!
Here is what worked for me:
1. adb shell
2. su
(# - you should see this now! This will not work without this specific prompt!)
3. type 'exit' press enter, and then 'exit' again. You will now be back at the regular command prompt.
4. adb push C:\(location of attached files)\superuser.apk /data/local/tmp
5. adb push C:\(location of attached files)\su /data/local/tmp
6. adb push C:\(location of attached files)\busybox /data/local/tmp
7. Access the adb shell again, and type su
8. chmod 644 /data/local/tmp/superuser.apk
9. chmod 755 /data/local/tmp/busybox
10. chmod 6755 /data/local/tmp/su
11. mount -o remount,rw /system
12. dd if=/data/local/tmp/Superuser.apk of=/system/app/Superuser.apk
13. dd if=/data/local/tmp/busybox of=/system/bin/busybox
14. dd if=/data/local/tmp/busybox of=/system/xbin/busybox
14a. Chmod 755 /system/bin/busybox and /system/xbin/busybox
15. Reserved
16. busybox rm /system/bin/su
17. busybox cp /data/local/tmp/su /system/bin
18. type su once again to assure you still have access to the # prompt
18a. Chmod 644 /system/app/superuser.apk
19. type exit, and exit again, returning to the regular windows command prompt.
20. type 'adb reboot' (without quotes)
NOTE - you will not need to install the superuser.apk app in the normal sense. It will be installed upon the reboot as a system app automatically!
21. Once your prime has rebooted, go download root checker basic or the like from the play store. Open it, and wait for your superuser prompt!
22. Get the busybox installer from the play store as well, and use that to get the newest version of busybox.
Thanks to daymz from the debugfs thread in development for the basic instructions of what needed to be done!! And also thanks to all before me who got us root in the first place!
I will answer questions to the best of my ability. I am not a developer and do not try to present myself as so... I can tinker with the best, and after losing root, I set out to see if I could figure it out!
Changes made as per tsmt971
Click to expand...
Click to collapse
I fail on step 11... (mount: Operation not permitted). Any suggestions?
tontorus said:
I fail on step 11... (mount: Operation not permitted). Any suggestions?
Click to expand...
Click to collapse
If your prompt isnt turning to the # symbol after SU you don't actually have root =/
hx4700 Killer said:
If your prompt isnt turning to the # symbol after SU you don't actually have root =/
Click to expand...
Click to collapse
Try the steps again. I know I had to do it several times before it was successful for me
I used these steps exactly
1. adb shell
2. su
(# - you should see this now! This will not work without this specific prompt!)
3. type 'exit' press enter, and then 'exit' again. You will now be back at the regular command prompt.
4. adb push C:\(location of attached files)\superuser.apk /data/local/tmp
5. adb push C:\(location of attached files)\su /data/local/tmp
6. adb push C:\(location of attached files)\busybox /data/local/tmp
7. Access the adb shell again, and type su
8. chmod 644 /data/local/tmp/superuser.apk
9. chmod 755 /data/local/tmp/busybox
10. chmod 6755 /data/local/tmp/su
11. mount -o remount,rw /system
12. dd if=/data/local/tmp/Superuser.apk of=/system/app/Superuser.apk
13. dd if=/data/local/tmp/busybox of=/system/bin/busybox
14. dd if=/data/local/tmp/busybox of=/system/xbin/busybox
15. chmod 755 /system/bin/busybox
16. chmod 755 /system/xbin/busybox
17. busybox rm /system/bin/su
18. busybox cp /data/local/tmp/su /system/bin
Type su once again to assure you still have access to the # prompt
19. chmod 644 /system/app/Superuser.apk
20. type exit, and exit again, returning to the regular windows command prompt.
21. type 'adb reboot' (without quotes)
NOTE - you will not need to install the superuser.apk app in the normal sense. It will be installed upon the reboot as a system app automatically!
22. Once your prime has rebooted, go download root checker basic or the like from the play store. Open it, and wait for your superuser prompt!
23. Get the busybox installer from the play store as well, and use that to get the newest version of busybox.
Are you suggesting that if I do a system wipe on my stock rom JB and run your commands I will eventually get root?
Hx4700, i got stuck doing a wipe after the update, and this worked for me. The wipe does not seem to remove su from /system/bin/ meaning we have a way back in through adb.
But, what if Voodoo didn't work before and you are unable to get su through adb in the first place? Are you suggesting that a wipe will resolve the blocked root access or did you have different circumstances?
hx4700 Killer said:
Are you suggesting that if I do a system wipe on my stock rom JB and run your commands I will eventually get root?
Click to expand...
Click to collapse
Anakin_SW said:
But, what if Voodoo didn't work before and you are unable to get su through adb in the first place? Are you suggesting that a wipe will resolve the blocked root access or did you have different circumstances?
Click to expand...
Click to collapse
If you cannot access a root prompt, then i do not believe it will work. Using a file explorer like es, does a su file exist in /system/bin? I had to wipe as i was bootlooping, and cant comment on how it pertains to how i was able to get root back!
thenrz said:
If you cannot access a root prompt, then i do not believe it will work. Using a file explorer like es, does a su file exist in /system/bin? I had to wipe as i was bootlooping, and cant comment on how it pertains to how i was able to get root back!
Click to expand...
Click to collapse
Yes, one does. Also su-backup in /system... Any feelings?
Hm, weird you cant get a root prompt through adb. From my experience, if su exists there, adb should be able to invoke a root prompt. Do you have any issue using adb push?
thenrz said:
Hm, weird you cant get a root prompt through adb. From my experience, if su exists there, adb should be able to invoke a root prompt. Do you have any issue using adb push?
Click to expand...
Click to collapse
Nope adb push works fine. But I can't mount /system rw, which is causing me the headache. Really wish I had known the voodoo update switched around things. I feel so foolish haha.
hx4700 Killer said:
If your prompt isnt turning to the # symbol after SU you don't actually have root =/
Click to expand...
Click to collapse
I figured that would be the problem... Should I root my device using the ICS method first or that wouldn't work any more?
tontorus said:
I figured that would be the problem... Should I root my device using the ICS method first or that wouldn't work any more?
Click to expand...
Click to collapse
Nothing is for me and many others.
Okie doke so lets saying you are happily trying too root your tab executing this http://forum.xda-developers.com/showthread.php?t=1887447 script.
everything goes as planned until you reboot and try to start the terminal and nothing appears. One method is to inject a VpnFaker you have signed using Zipsigner2 if that doesn't work you can rollback using this code
adb shell
cd /data
mv system system3
mv system- system
mv app app3
mv app- app
If nothing works then here is a way I found to fix it. once you get to code TZ=0 under it will say rw-rw-rw which means the VpnFaker will disappear once you reboot.
type in /data/app/VpnFaker.apk it will say permission denied that means it is indeed there. so to fix it we type:
chmod 644 /data/app
this worked for me on ICS no revision when trying to root!! hope it does for you if you are on ICS with revision do
chmod 644 /data/app/VpnFaker.apk
otherwise you will have to reupdate because doing it the other way will cause you to lose adb.
OK, I'm running into difficulties with this phone..
..It arrive pre-rooted, I installed Titanium Backup and removed iReader.
In the Play store I noticed that SuperUser and Google Keyboard needing updating but when I tried to do so all I got was "Error Installing - Package file was not signed correctly" which I assume has something to do with a slightly different version of the program initially installed?
Then I went into SuperUser itself, clicked on the spanner icon, scrolled down and tapped on the check for updates button..
..indeed it found an update and proceeded to update in a similar style terminal box.
However.. according to Titanium I no longer have root access, I quickly downloaded Root Checker Basic which also confirmed this.. bugger I thought.
Moving onwards, I just downloaded SRS Root from srsroot.com. Tried rooting and it exited out saying I already had root access.. hmmm, so then I removed root access, the phone rebooted and then I re-applied the root.
Although I am still suffering from not having proper root access :crying:
Please help me to get full root access back again, thanks in advance. :angel:
SpongeR0b said:
OK, I'm running into difficulties with this phone..
..It arrive pre-rooted, I installed Titanium Backup and removed iReader.
In the Play store I noticed that SuperUser and Google Keyboard needing updating but when I tried to do so all I got was "Error Installing - Package file was not signed correctly" which I assume has something to do with a slightly different version of the program initially installed?
Then I went into SuperUser itself, clicked on the spanner icon, scrolled down and tapped on the check for updates button..
..indeed it found an update and proceeded to update in a similar style terminal box.
However.. according to Titanium I no longer have root access, I quickly downloaded Root Checker Basic which also confirmed this.. bugger I thought.
Moving onwards, I just downloaded SRS Root from srsroot.com. Tried rooting and it exited out saying I already had root access.. hmmm, so then I removed root access, the phone rebooted and then I re-applied the root.
Although I am still suffering from not having proper root access :crying:
Please help me to get full root access back again, thanks in advance. :angel:
Click to expand...
Click to collapse
UPDATE : After running Root Checker Pro it told me that SuperSU wasn't installed.. I downloaded that from the play store and re ran Root Checker Pro, it now tells me..
Root Access is not properly configured or was not granted.
Super User Application Status:
SuperSU application - version 1.91 - 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 22364 2014-01-27 21:08 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: root user - ro.secure=0
Results provided on your K47/C9_89 device by Root Checker Pro version 1.3.4
Click to expand...
Click to collapse
I still have Root Explorer on the phone and seem to be able to navigate through the normally hidden directories.
Suggestions please!
To my surprise, I bit the bullet today and reset my phone to stock defaults..
..unfortunately even this still did not fix the incomplete root
Please help!
EDIT : I've been tinkering again.. Here's what I understand (and what I've done)
System\bin\ - Kinda not the most important place to store a file relating to an installed .apk's
System\xbin\ - The more important place (kinda like the System32 directory) relaing to installed .apk's
System\app\ - The directory where the .apk file's themselves live (kinda like Program Files\xxx Application)
Well I noticed I had an .apk in apps called root_Superuser.apk and this was present even after un-rooting my phone.
I removed this file, using these commands :
adb remount
adb pull /system/app/root_Superuser.apk
Seemingly this didn't remove the file, so then I tried :
adb remount
abd shell rm -f /system/app/root_Superuser.apk
After a quick reboot this had indeed removed Superuser, then I reused the SRS Tool to re-root.
Then I read that SU 3.0.2 was a safer bet.. (although it was a post from 2011 - attached)
So I downloaded that and proceeded to push the superuser.apk and su files into their correct places (as below)
adb remount
adb push superuser.apk /system/app/
adb push su /system/xbin/
adb push su /system/bin/
After the files were correctly in place I needed to set the correct file permissions, I did this as follows :
abd shell
[email protected]:/ # CHMOD 644 /system/app/superuser.apk
[email protected]:/ # CHMOD 777 /system/xbin/su
[email protected]:/ # CHMOD 777 /system/bin/su
Finally I realised I had given /xbin/su the incorrect permissions so ammended them to :
abd shell
[email protected]:/ # CHMOD 4755 /system/xbin/su
[email protected]:/ # CHMOD 4755 /system/bin/su
The reason why I am writing exactly what I did is so I myself don't forget anything and also to show others how to do stuff should I be doing it correctly!? I wasn't sure if the su needed to go into xbin or bin so I put it into both directories and thus I can remove which ever one is incorrect once I get a reply from somebody!
Here's my current log from Root Checker Pro - I shall not be doing anything else without further assistance.
Root Access is not properly configured or was not granted.
Super User Application Status:
Superuser application - version 3.0.2 - is installed!
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-xr-x root root 22140 2008-02-29 02:33 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!
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-xr-x root root 22140 2008-02-29 02:33 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: root user - ro.secure=0
Results provided on your K47/C9_89 device by Root Checker Pro version 1.3.4
Click to expand...
Click to collapse
SpongeR0b said:
To my surprise, I bit the bullet today and reset my phone to stock defaults..
..unfortunately even this still did not fix the incomplete root
Please help!
EDIT : I've been tinkering again.. Here's what I understand (and what I've done)
System\bin\ - Kinda not the most important place to store a file relating to an installed .apk's
System\xbin\ - The more important place (kinda like the System32 directory) relaing to installed .apk's
System\app\ - The directory where the .apk file's themselves live (kinda like Program Files\xxx Application)
Well I noticed I had an .apk in apps called root_Superuser.apk and this was present even after un-rooting my phone.
I removed this file, using these commands :
adb remount
adb pull /system/app/root_Superuser.apk
Seemingly this didn't remove the file, so then I tried :
adb remount
abd shell rm -f /system/app/root_Superuser.apk
After a quick reboot this had indeed removed Superuser, then I reused the SRS Tool to re-root.
Then I read that SU 3.0.2 was a safer bet.. (although it was a post from 2011 - attached)
So I downloaded that and proceeded to push the superuser.apk and su files into their correct places (as below)
adb remount
adb push superuser.apk /system/app/
adb push su /system/xbin/
adb push su /system/bin/
After the files were correctly in place I needed to set the correct file permissions, I did this as follows :
abd shell
[email protected]:/ # CHMOD 644 /system/app/superuser.apk
[email protected]:/ # CHMOD 777 /system/xbin/su
[email protected]:/ # CHMOD 777 /system/bin/su
Finally I realised I had given /xbin/su the incorrect permissions so ammended them to :
abd shell
[email protected]:/ # CHMOD 4755 /system/xbin/su
[email protected]:/ # CHMOD 4755 /system/bin/su
The reason why I am writing exactly what I did is so I myself don't forget anything and also to show others how to do stuff should I be doing it correctly!? I wasn't sure if the su needed to go into xbin or bin so I put it into both directories and thus I can remove which ever one is incorrect once I get a reply from somebody!
Here's my current log from Root Checker Pro - I shall not be doing anything else without further assistance.
Click to expand...
Click to collapse
Great to see the Root Checker apps being used! Given you posted a link back to this thread in the Root Checker thread I'm posting my reply here.
The route I usually take and recommend, which does all of those steps you've performed, such as copying files and setting the correct permissions, is to load an "official" .zip file from the custom recovery.
If you have a custom recovery, I'd recommend loading SuperSU.zip, which has worked very well for me on my devices: http://forum.xda-developers.com/showthread.php?t=1538053
From the XDA post, there is a link to the .zip file that can be downloaded and loaded in the custom recovery: http://download.chainfire.eu/supersu
If you don't have a custom recovery, I think most of the steps you've taken are correct, but based on the Root Checker Pro output I'd be concerned that the Superuser.apk file you installed and the su binary aren't communicating and might be out of sync. This can be caused by many reasons but the solution is to make sure you installed a matching .apk and su binary.
Hope that helps and good luck!
joeykrim said:
Great to see the Root Checker apps being used! Given you posted a link back to this thread in the Root Checker thread I'm posting my reply here.
The route I usually take and recommend, which does all of those steps you've performed, such as copying files and setting the correct permissions, is to load an "official" .zip file from the custom recovery.
If you have a custom recovery, I'd recommend loading SuperSU.zip, which has worked very well for me on my devices: http://forum.xda-developers.com/showthread.php?t=1538053
From the XDA post, there is a link to the .zip file that can be downloaded and loaded in the custom recovery: http://download.chainfire.eu/supersu
If you don't have a custom recovery, I think most of the steps you've taken are correct, but based on the Root Checker Pro output I'd be concerned that the Superuser.apk file you installed and the su binary aren't communicating and might be out of sync. This can be caused by many reasons but the solution is to make sure you installed a matching .apk and su binary.
Hope that helps and good luck!
Click to expand...
Click to collapse
Thanks for your reply JoeyKrim, unfortunately I don't think a custom recovery is available for this phone at present? I've had SuperSu on my device and to be honest not a great deal worked using it. I've also had both CWM / TWRP installed on the phone and both of them cannot find a suitable ROM to implement. I guess because of the phone being fairly new and a knock off doesn't exactly help me! :cyclops:
I will re-root my device and if that isn't successful manually try to match both superuser.apk and su binary with yet another version of superuser!
EDIT :
Here's what I've tried this morning (unfortunately now I have ran out of time and must get ready for college)
adb remount
adb push Superuser.apk /system/app/
adb push su /system/xbin/
adb push su /system/bin/
adb shell
[email protected]:/ # CHMOD 644 /system/app/Superuser.apk
[email protected]:/ # CHMOD 4755 /system/xbin/su
[email protected]:/ # CHMOD 4755 /system/bin/su
Superuser available to download from http://hosted.androidsu.com/superuser/
Using: su-3.0.1-d-signed.rar I get Superuser v3.0.1 (36), Su binary vnull (legacy)
su-3.0.1-efgh-signed.zip I get Superuser v3.0.1 (36), Su binary vnull (legacy)
Unsure of differences between d & efgh versions? Moved onto next version..
su-3.0.2-efgh-signed.zip I get Superuser v3.0.2 (37), Su binary vnull (legacy)
Renamed ([email protected]:/ # mv Superuser.apk root_Superuser.apk) seemingly no difference?
I was wondering if root allowed apps were renamed as root_appName.apk - I've left the file
name as this (i.e. Superuser.apk is NOT in my system/app/ directory and yet Superuser still
runs fine???)
Superuser-3.0.6-efgh-signed (Only binary updated) v3.0.2 (37), Su binary vnull (legacy)
su-bin-3.0.3.2-efghi-signed.zip Superuser v3.0.2 (37), Su binary vnull (legacy)
Isn't Su binary 3.0.3.2 the more up to date binary??? According my my Superuser's self update
it is?
Trying this release? - Also copied Superuser.apk to root_Superuser.apk as well this time..
Superuser-3.1-arm-signed Unable to check the versions.. different menu
Additionally myt Root Explorer (root_Root explorer.apk) now cannot gain root access which
is the first time this has EVERY occured
Superuser-3.1.1-x86-signed Unable to check the versions.. different menu
OK, so I know for sure that 3.1 is a more recent version of Superuser than I have ever had on
my phone, and of course root explorer doesn't now work, so trying an older version..
Superuser-3.0.7-efghi-signed.zip Superuser v3.0.7(41), Su binary v3.1
Again.. Root explorer no longer working.. tried deleting root_Superuser.apk
(adb shell rm -f /system/app/root_Superuser.apk)
Hasn't seemed to do anything different.. Removing all SuperUser files, ran out of time to
experiment with. Annoyed that now even my Root Explorer isn't working, I seem to be going
backwards and not forwards!!
After un-rooting (using SRSRoot) I once again have access to my Root Explorer??? Weird.
Click to expand...
Click to collapse
O.K, I'm ready for step by step instructions, anybody know how to help me please?
EDIT :
Thanks to tijsh111 for providing a working root solution to my problem..
http://forum.xda-developers.com/showthread.php?t=2219062&nocache=1
What is init.d?
init.d is a folder placed in /system/etc wich has been legendary used since the old android times to run scripts at boot. I've decided to make this simple script becouse lots of my users on my AmazBoost MOD thread were asking how they can enable init.d on stock ROM or simply on an unsupported ROM. It's easy to run and doesn't require any kind of coding skills!
What you need
- AmazFit Stratos/Pace
- Rooted ROM
How to install
1) Download the mod zip from download link and unzip it
2) Connect the wath to the PC
3) Place the enable.sh file inside your adb folder and open there a command prompt (or terminal for Mac OS/linux) then type the following codes:
Code:
adb root
adb push enable.sh /sdcard/
adb shell sh /sdcard/enable.sh
4) Done!
5) You NEED to reinstall the mod running the installer after every ROM update!
Changelog
First release!
Download and enjoy!
https://goo.gl/HYqEZt
If my work was useful always press thanks!
There is a typo in the script:
touch /system/ect/install-recovery.sh
chmod 755 /system/etc/install-recovery.sh
chown 0:2000 /system/ect/install-recovery.sh
should be
Code:
touch /system/etc/install-recovery.sh
chmod 755 /system/etc/install-recovery.sh
chown 0:2000 /system/etc/install-recovery.sh
jprelay said:
There is a typo in the script:
touch /system/ect/install-recovery.sh
should be
Code:
touch /system/etc/install-recovery.sh
Click to expand...
Click to collapse
Ooops didn't check it perfectly just used a Compiler to see if there were some syntax errors, thanks I'll updating the file now!
Inviato dal mio G8141 utilizzando Tapatalk
Script name and command name don't match either, enabler.sh
I think that I found a solution..I wish is helpful !
1) First of all you need to have unlock bootloader and then run the temporary root
(check in "PERMANENT INSTALL" description)
AFTER ROOTING LETS GO FOR UNIT SUPPORT!
I used the init.d support through terminal emulator
2) Download the term-init.sh v3 .
3) Connect the watch to your PC.
4) Place the term-init.sh file inside your adb folder and open the command prompt.. then type the following codes:
(if adb shell or adb root not working, try to disconnect and connect your watch )
Code:
adb root
adb push term-init.sh /sdcard/
(or you can drag and drop it in your sdcard)
adb shell sh /sdcard/ term-init.sh
5) After that go and run the installer.bat file from Amazboost folder!
6) Done!
I tried this tools but i have error
Code:
+ $'\r'
: not foundble.sh[12]:
/sdcard/enable.sh[13]: syntax error: 'if' unmatched
tminhnhat said:
I tried this tools but i have error
Code:
+ $'\r'
: not foundble.sh[12]:
/sdcard/enable.sh[13]: syntax error: 'if' unmatched
Click to expand...
Click to collapse
Same here too, the OP seems to have been making a lot of mistakes in his scripts
How is the init.d supposed to be enabled?
Hi, i want to enable AmazBoost so i came to this post to enable init.d but i lost, i dont understand what i need to do, when i follow the instructions i get this error.
########################################################
# #
# AmazFit universal init.d enabler by @AmazDev #
# #
########################################################
Mounting system...
Usage: mount [-r] [-w] [-o options] [-t type] device directory
: not foundbler.sh[12]:
/sdcard/enabler.sh[13]: syntax error: 'if' unmatched
I have Stratos 2 A1619
I have a Stock ROM 2.3.6.0 Unlocked
Thanks
---------- Post added at 05:20 PM ---------- Previous post was at 05:04 PM ----------
Hi, i tried with the other instructions but again i have a error:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell sh /sdcard/term-init.sh
Init.d Enabler by Ryuinferno @ XDA
Script NOT running as root!
Superuser access not granted!
Please type 'su' first before running this script...
C:\Program Files (x86)\Minimal ADB and Fastboot>su
'su' is not recognized as an internal or external command,
operable program or batch file.
kostasntamas said:
I think that I found a solution..I wish is helpful !
1) First of all you need to have unlock bootloader and then run the temporary root
(check in "PERMANENT INSTALL" description)
AFTER ROOTING LETS GO FOR UNIT SUPPORT!
I used the init.d support through terminal emulator
2) Download the term-init.sh v3 .
3) Connect the watch to your PC.
4) Place the term-init.sh file inside your adb folder and open the command prompt.. then type the following codes:
(if adb shell or adb root not working, try to disconnect and connect your watch )
Code:
adb root
adb push term-init.sh /sdcard/
(or you can drag and drop it in your sdcard)
adb shell sh /sdcard/ term-init.sh
5) After that go and run the installer.bat file from Amazboost folder!
6) Done!
Click to expand...
Click to collapse
hi mate, do you modify the term-init.sh?
may i know which version of busybox that you are using?
currently im using the busybox from here: https://forum.xda-developers.com/showpost.php?p=78031249&postcount=107
and when i try to install term-init.sh, i encountered below error:
Code:
grep applet NOT FOUND!
run-parts applet NOT FOUND!
Required applets are NOT FOUND!
Please reinstall busybox!
illkid69 said:
hi mate, do you modify the term-init.sh?
may i know which version of busybox that you are using?
currently im using the busybox from here: https://forum.xda-developers.com/showpost.php?p=78031249&postcount=107
and when i try to install term-init.sh, i encountered below error:
Code:
grep applet NOT FOUND!
run-parts applet NOT FOUND!
Required applets are NOT FOUND!
Please reinstall busybox!
Click to expand...
Click to collapse
i have same problem do u find any solution?
Is anybody enable init.d on stock fw?
Hi,
I'm trying to install the Amazboost tweaks on my rooted Stratos (A1619) with Global FW (2.3.10.5) but I suspect that the installation of the tweaks via busybox is not running correctly. I have followed precisely the procedures with success but there is no log in the AmazBoost/LOGS folder after the reboot.
I have installed the last version of busybox (V1.29.3 for MIPS) in both /system/bin and /system/xbin but no log at all.
Some posts said that init.d is not working with stock fw.
Is that true?
Is anybody can help me to check if init.d can be enabled on my rooted Stratos (A1619) with Global FW (2.3.10.5)? And how can we verify that it works?
Thanks
Hi,
I'm still trying to understand why init.d is not running on my Stratos (A1619) with Global FW (2.3.10.5).
The init.d script refers to the "run-parts" file located in the /system/xbin/ directory.
But run-parts is not present.
I have found one file coming from the xperia x10 forum but it is not working on the Stratos: /system/xbin/run-parts: not executable: 32-bit ELF file
Is somebody could provide me this run-parts file compliant with the Stratos? (or help me to understand why the amazboost tweaks are not correctly installed)