Related
Get superuser whitelist. I pulled mine off a rooted Galaxy Tab:
Code:
linux$ adb pull /system/app/Superuser.apk
linux$ adb pull /system/bin/su
From a machine with ADB working, and communicating with your Nook:
Install Superuser.apk, and copy the su binary to /data/local:
Code:
linux$ adb install Superuser.apk
linux$ adb push su /data/local/
Shell into the Nook, remount the system partition read/write, and install the su utility to /system/bin:
Code:
linux$ adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
-rwsr-sr-x root root 26264 2010-12-01 10:27 su
#
reboot Nook Color to get Superuser to show up in "extras." Now, you can get root from inside the Better Terminal Emulator Pro shell.
Thanks for the info. Just a quick note that on Cyanogenmod 6.1 RC2 (Nexus One), the su binary is actualy at /system/xbin/su rather than /system/bin/su
hharte said:
Get superuser whitelist. I pulled mine off a rooted Galaxy Tab:
Code:
linux$ adb pull /system/app/Superuser.apk
linux$ adb pull /system/bin/su
From a machine with ADB working, and communicating with your Nook:
Install Superuser.apk, and copy the su binary to /data/local:
Code:
linux$ adb install Superuser.apk
linux$ adb push su /data/local/
Shell into the Nook, remount the system partition read/write, and install the su utility to /system/bin:
Code:
linux$ adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
-rwsr-sr-x root root 26264 2010-12-01 10:27 su
#
reboot Nook Color to get Superuser to show up in "extras." Now, you can get root from inside the Better Terminal Emulator Pro shell.
Click to expand...
Click to collapse
Thank you, very useful instruction!
Couple of questions though:
1. Any public repo where the working in NC Superuser.apk could be downloaded from? Not everyone out of NC owners owns Galaxy Tab.
2. More elaboration on "whitelist", please
3. If possible, show some example why someone might need this. I'd rather try to edit build.prop: pixel density, whatever, plus changing stock system Droid Sans into, say, much more beautifil Segoe WP. But it's just me though.
Thank you
aludal said:
Thank you, very useful instruction!
Couple of questions though:
1. Any public repo where the working in NC Superuser.apk could be downloaded from? Not everyone out of NC owners owns Galaxy Tab.
2. More elaboration on "whitelist", please
3. If possible, show some example why someone might need this. I'd rather try to edit build.prop: pixel density, whatever, plus changing stock system Droid Sans into, say, much more beautifil Segoe WP. But it's just me though.
Thank you
Click to expand...
Click to collapse
For #3, somebody may want to replace system fonts to support other languages than English. I have done that to Android 2.1 phones too.
aludal said:
Thank you, very useful instruction!
Couple of questions though:
1. Any public repo where the working in NC Superuser.apk could be downloaded from? Not everyone out of NC owners owns Galaxy Tab.
Thank you
Click to expand...
Click to collapse
Here you go: http://forum.xda-developers.com/showthread.php?t=665974
hharte said:
Get superuser whitelist. I pulled mine off a rooted Galaxy Tab:
linux$ adb pull /system/bin/su
Click to expand...
Click to collapse
Thanks Man, this was the part i didn't get and it's working now
PTzero said:
Here you go: http://forum.xda-developers.com/showthread.php?t=665974
Click to expand...
Click to collapse
So I installed this version of the Superuser apk but it seems to be an old version (2.0.3) with the ninja icon.
The latest version is 2.3.6.1 but I can't seem to get it to install (INSTALL_FAILED_UPDATE_INCOMPATIBLE).
Which is the latest version of Superuser apk that works with nC that has the 'Android Skull and Crossbones' icon and does anyone have the apk?
califrag said:
So I installed this version of the Superuser apk but it seems to be an old version (2.0.3) with the ninja icon.
The latest version is 2.3.6.1 but I can't seem to get it to install (INSTALL_FAILED_UPDATE_INCOMPATIBLE).
Which is the latest version of Superuser apk that works with nC that has the 'Android Skull and Crossbones' icon and does anyone have the apk?
Click to expand...
Click to collapse
That's odd. I was able to install 2.3.6.1 with no problem. I pulled it the apk off my Nexus One.
dark79 said:
That's odd. I was able to install 2.3.6.1 with no problem. I pulled it the apk off my Nexus One.
Click to expand...
Click to collapse
Could you pull and post your Superuser apk and your /system/bin/su file? I don't have a nexus one and when I tried using the Superuser apk and su file from the cyanogen 6.0 Nexus ROM it didn't seem to work either
EDIT:
Nevermind I got it working using the files attached (latest version 2.3.6.1)
(from here: http://forum.xda-developers.com/showthread.php?t=682828)
I also noticed that it had to grant itself Superuser permissions when I hit the "settings" tab. Under the settings tab I also noticed my 'su' version was 'original' and there was an update available which changed it to version '2.3.1-ef'. Not sure if this needs to be done for it to work right or not but thought I should mention it.
Will this work on just linux or windows?
You can do it on windows using ADB
califrag said:
Could you pull and post your Superuser apk and your /system/bin/su file? I don't have a nexus one and when I tried using the Superuser apk and su file from the cyanogen 6.0 Nexus ROM it didn't seem to work either
EDIT:
Nevermind I got it working using the files attached (latest version 2.3.6.1)
(from here: http://forum.xda-developers.com/showthread.php?t=682828)
I also noticed that it had to grant itself Superuser permissions when I hit the "settings" tab. Under the settings tab I also noticed my 'su' version was 'original' and there was an update available which changed it to version '2.3.1-ef'. Not sure if this needs to be done for it to work right or not but thought I should mention it.
Click to expand...
Click to collapse
What did you do to get this? I tried installing using ADB and Android Commander. I get the same error that says INCOMPATIBLE. This is the only program giving me issues.
sminker said:
What did you do to get this? I tried installing using ADB and Android Commander. I get the same error that says INCOMPATIBLE. This is the only program giving me issues.
Click to expand...
Click to collapse
Make sure to download the 'eclair\froyo' version.
this is the file im using
su-2.3.6.1-ef-signed
i did have it installed once and uninstalled, but now i cant reinstall it
sminker said:
this is the file im using
su-2.3.6.1-ef-signed
i did have it installed once and uninstalled, but now i cant reinstall it
Click to expand...
Click to collapse
use adb shell and go into /data/data and do an 'ls'
remove any directory there that looks like 'com.noshofou'
i was able to use z4root to get it installed
when I do:
cat /data/local/su > su
I get:
Cannot create su: remote access failed
Is there a Windows tutorial for how to install Super User on the NC or an apk that does the same thing?
Is there any advantage to put the binary into xbin versus bin
discourse said:
Is there a Windows tutorial for how to install Super User on the NC or an apk that does the same thing?
Click to expand...
Click to collapse
I would like a windows walkthrough also
Hi guys, I'm working on a toolkit for the optimus me (p350), more exactly on the rooting part, but I've got a problem, I can't find a tutorial of how to do a manual root using adb shell with the gingerbreak exploit.
Can anyone help me? Thanks
I think you'd do something like the following commands:
Code:
adb push GingerBreak /data/local/tmp
adb shell chmod 755 /data/local/tmp/GingerBreak
adb shell
cd /data/local/tmp/
./GingerBreak
adb remount
adb push su /system/bin
adb push su /system/xbin
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
exit
adb install Superuser.apk
You might want to also push busybox I guess.
Use doomlord's root method.
Just open the runme.bat(i think this is the name), and you'll see which commands use.
I've used as base to manually root Ideos X5 a lot of times.
Thanks
Thanks both, i have already try the second solution, but it isn't compatible with my phone. I will try the fist method.
Thanks guys.
Hi guys
I've imported the SH-06D from Japan and the phone is running great, however I'd like to remove some system apps etc to help speed up the phone (it's still on 2.3.5) and obviously tweak it as well.
I know there is an existing thread on the SH-01D (predecessor to the SH-06D) but I'm wondering if anyone has successfully rooted the SH-06D and if so, is there an (easy) process to do this?
Another reason I want to root, is to install the UI from the upcoming Evangelion Nerv edition of the SH-06D that is due to be released in a few days.
ICS for the SH-06D is just around the corner (due to be released in July) but I'd realy appreciate any help, assistance or tips in rooting the phone as it is now.
Cheers! :fingers-crossed:
Anyone?
:-(
here is a link to root the sh-06d :
http://itsuki.ddo.jp/gadget/index.php?SH-06D
THANK YOU!
Have you tried this method and does it work? Can you assist me in following those directions?
Cheers
interfreak said:
THANK YOU!
Have you tried this method and does it work? Can you assist me in following those directions?
Cheers
Click to expand...
Click to collapse
i haven't tried since i don't have this phone.
i can try to help you if you want.
testnumero said:
i haven't tried since i don't have this phone.
i can try to help you if you want.
Click to expand...
Click to collapse
Thanks mate!
I'm fumbling through the process now - it's a little hard when you are using google translate lol!
OK, I've run through all the steps but..
When I get to the end of the process:
C:\Users\interfreak\Desktop
$ su
su
su: permission denied
:-(
interfreak said:
OK, I've run through all the steps but..
When I get to the end of the process:
C:\Users\interfreak\Desktop
$ su
su
su: permission denied
:-(
Click to expand...
Click to collapse
i don't know what is the problem, try to do steps again.
Tried, same result. :-(
interfreak said:
Tried, same result. :-(
Click to expand...
Click to collapse
i'll ask to translate it
Thanks mate!!! :highfive:
I want to know untill now has SH-06D been rooted?
I wish someone could dump ROM or launcher from SH-06 NERV version:fingers-crossed:
I'm working on the translation for root on Sharp Aquos SH-06D.
Please give me one or two more days!
That is highly impossible, having full root in J Phone are hard enough. Unlocking the bootloader is a wet dream for almost everyone who likes J phone
lightout said:
I want to know untill now has SH-06D been rooted?
I wish someone could dump ROM or launcher from SH-06 NERV version:fingers-crossed:
Click to expand...
Click to collapse
I'm trying to hard reset my SH-06D, but I can't do it via settings-privacy. I can select to wipe, but nothing happens.
Any suggestions?
I got the Nerv edition
Hey man, how did the rooting go? I ordered the Nerv edition of this phone, and I want to root it (mainly to pair my sixaxis controller for psx emulation) but wanted to consult with you first as a precaution.
Here is the a rough translation of the root guide found here:
http://itsuki.ddo.jp/gadget/index.php?SH-06D
Big thanks to testnumero for the help!
Please don't ask me directly for help. I don't own this phone.
A quick look at root
• With root you can freeze preinstalled bloatware and backup application settings and game save data.
• 3D content from /system can be played on other devices and 3DTVs.
Unresponsive apps can be frozen which will help the device run smoother and have a longer battery life.
Applications which are frozen disappear from your drawer making the device look cleaner and keeping your mind at ease.
• The process is similar to the one used for SH-01D.
• If an update patch is released or the Android 4.0 summer update is released then this guide will no longer be of help.
(Make sure your device is the following: Android Ver. 2.3.5 Build No. 01.00.03)
• If your device becomes a paperweight I won’t be held responsible.
• Follow this guide at your own risk.
↑
Preparations – Before you begin
• Install Android SDK and SHARP ADB USB drivers and make to use ADB.
• 「Settings」→「Applications」→「Development」→「USB Debugging」 checked.
• SH-06D and micro USB cable to connect to your PC
↑
Required Files
• Download "shdisphook" from the following link and extract.
http://goo.gl/Bs6Iq
• Download shsdgetroot-omap4.zip from the following link and extract.
http://www1.axfc.net/uploader/File/so/78144
• Download shbootgetroot-su.lzh from the following link and extract.
http://www.mediafire.com/?6i0n32jlwbxe8cp
• Keep all extracted files in the same folder.
↑
Creating files
• Create a file named "shdisphook.bat" in the folder with the extracted files.
Copy and paste the following and save.
adb push onload.sh /data/local/
adb push libsdservice_jni.so /data/local/
adb push shdisphook /data/local/
adb shell chmod 755 /data/local/onload.sh
adb shell chmod 755 /data/local/shdisphook
adb reboot
adb wait-for-device shell /data/local/shdisphook
pause
• Create a file named "oncmd.sh" and put the following in the description.
(Save the line break as LF)
chmod 777 /cache
chmod 666 /cache/recovery
• Replace the contents of the file "installfile.cmd" with the following and save.
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/mount -o rw,remount -t rootfs rootfs /"
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/chmod 777 /sbin"
adb push su /sbin
adb push busybox /sbin
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/chown 0.0 /sbin/su"
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/chown 0.0 /sbin/busybox"
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/chmod 6755 /sbin/su"
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/chmod 755 /sbin/busybox"
adb shell /data/local/shsdgetroot-omap4 -c "/sbin/busybox --install -s /sbin"
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/chmod 755 /sbin"
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/mount -o ro,remount -t rootfs rootfs /"
adb push Superuser.apk /data/local/
adb shell /system/bin/pm install -t -f -r /data/local/Superuser.apk
adb shell /system/bin/rm /data/local/Superuser.apk
exit /b
↑
Step 1
• Open command prompt to the folder with the extracted files and navigate to "shdisphook".
Execute "shdisphook.bat". (You can also just double click on the .bat file)
• The device will reboot so just wait for the [Press any key to continue] message to appear.
If more than a few minutes have passed and nothing has appeared then, force close and execute "shdisphook.bat" again.
(When you fail your PC will reboot or your SH-06D WiFi will start. There is a high rate of success when you immediately unlock the lock screen for your device when it goes to sleep.)
↑
Step 2
• Open command prompt and send oncmd.sh to SH-06D to change permissions
adb push oncmd.sh /data/local/oncmd.sh
adb shell chmod 755 /data/local/oncmd.sh
• 「Settings」→「microSD and device storage」→「Unmount microSD」 This will execute the file "oncmd.sh" , which was sent to the device earlier.
(Cancel the message for 「Unmount microSD」)
• Enter the following commands.
adb shell mv /cache/recovery /cache/recovery_
adb shell ln -s /dev/shsd /cache/recovery
• Execute the following adb shell ls -l /cache and if you see the following message you have succeed.
drwxrwx--- root root 2011-11-11 03:39 lost+found
drw-rw-rw- system cache 2012-01-24 10:48 recovery_
lrwxrwxrwx shell shell 2012-03-02 13:24 recovery -> /dev/shsd
• Next execute adb shell ls -l /dev/shsd you should get the following message if you were successful.
crw-rw-rw- system cache 231, 0 2012-04-23 02:01 shsd
↑
Step 3
• Execute adb push shsdgetroot-omap4 /data/local
• Execute adb shell /system/bin/chmod 755 /data/local/shsdgetroot-omap4
• Execute adb shell /data/local/shsdgetroot-omap4 -v -m -u
• The “# “mark will appear there will be no response. Close command prompt for now.
• Execute installfile.cmd
• Check if you have root with the following adb shell→su
↑
After you reboot
• After you reboot you will lose root rights so execute shdisphook.bat→Cancel Unmount microSD →execute installfile.cmd and you should have root again.
The reason why you cannot do a clean wipe or nothing happen is because the recovery section has been move out into another location, causing it to not loading the recovery correctly.
Check with SH-01d part, I have asked similar question there and I revert the recovery in order to wipe the phone..
You need to rearrange the following section like on the sh-01d when you hit this part:
(Following is Original command that you relocated the recovery for root)
adb shell mv /cache/recovery /cache/recovery_
adb shell ln -s /dev/shsd /cache/recovery
And replace with the revert command found on sh-01d thread. You will need to redo all the steps from step 1 to step 2 and STOP AFTER YOU REVERT the RECOVERY.
You should be able to do a full wipe with no issue then. DO NOT POWER DOWN or RESET!!! You will have to REDO it again as it REQUIRES SHDSIHOOK to input shell command.
Hope it helps
waiting！！！！！！！！！！
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.
Hi all! I have a Chinese tablet that I need to root in order to run some applications. It mounts a 4.4.2 Android version and I can access via adb by opening an adb root shell. The table is called letine lt707a .
This is what I did:
Code:
adb shell mount -o remount,rw /system
adb push su /system/xbin
adb shell busybox chmod 6755 /system/xbin/su
Then I installed a version of Superuser.apk. When I open a terminal emulator app from the device, if I write "su" I obtain a "Permission denied" message.
Where is the problem? Maybe I have an old binary su?
I also tried with SuperSU without any results.
Thank you for your help!
I have just to push the correct su in the folder, but I don't know where to find it. After that in case of error I must undersand how Superuser communicates with the su. Anyone?
I think the problem is with kit kat. I pushed the su binary that came from superSU, but when I open a terminal emulator to write su I obtain a number zero as output.
If I start superSU I obtain a warning message: the program doesn't find the su binary.