Related
Disclaimer 1 : I tried to look for something like this but I did not found it. Then I tried to achieve it. Sorry if they are well known steps
This guide allows to root a Nexus One with unlocked bootloader with NO need to flash recovery
USE THAT INFORMATION AT YOUR RISK!!
Updated: Added a line to work with Gingerbread
That steps are for Ubuntu. If you are any interested windows user, please let me know.
Prerequisites:
Unlocked bootloader
adb working properly
1. Download fastboot
Code:
wget --referer=http://developer.htc.com/adp.html http://dl4.htc.com/RomCode/ADP/fastboot.zip
unzip fastboot.zip
chmod u+x fastboot
rm fastboot.zip
2. Obtain busybox (anyone have any direct link?) - NOT GOING TO FLASH CM, JUST GETTING busybox from a trusted place
Code:
wget http://download.cyanogenmod.com/get/update-cm-7.0.0-N1-signed.zip
unzip update-cm-7.0.0-N1-signed.zip system/xbin/busybox
rm update-cm-7.0.0-N1-signed.zip
3. Download su
-- UPDATE: that link broken, you have to donwload it from Google Play
Code:
wget http://dl.dropbox.com/u/6408470/su-releases/su-2.3.6.1-ef-signed.zip
unzip su-2.3.6.1-ef-signed.zip system/app/Superuser.apk system/bin/su
rm su-2.3.6.1-ef-signed.zip
4. Download recovery-RA - NOT GOING TO FLASH IT, DON'T WORRY!!!
Code:
wget -O recovery-RA-passion-v2.2.1.img http://files.androidspin.com/files/amon_ra/RECOVERY/recovery-RA-passion-v2.2.1.img
md5sum recovery-RA-passion-v2.2.1.img
echo ... Validate md5sum is 3def709ab1c9e051a92a1c8b1504a36a
5. Reboot to bootloader - JUST BOOTING WITH, NO FLASHING
Code:
adb devices
adb wait-for-device
adb reboot-bootloader
fastboot boot recovery-RA-passion-v2.2.1.img
echo ... Waiting for recovery image load
while [ -z `adb shell pwd 2> /dev/null` ]
do
sleep 1
done
6. Root it!
Code:
adb shell mount /system
adb push system/xbin/busybox /system/bin/busybox
adb shell chmod 4755 /system/bin/busybox
adb push system/bin/su /system/bin/su
adb shell chmod 4755 /system/bin/su
adb push system/app/Superuser.apk /system/app/Superuser.apk
adb shell chmod 4755 /system/app/Superuser.apk
7. Reboot and enjoy rooting
Code:
adb shell reboot
Will this work on stock Gingerbread?
If you are running Nexus One with Gingerbread, as I understand, it can work. I've not tried, you can try.... at your risk ;-)
Helleqn said:
Will this work on stock Gingerbread?
Click to expand...
Click to collapse
If you have an unlocked bootloader, yes, it will work. If you have an unlocked bootloader, you can install pretty much anything you want, whenever you want...
Sent from my Nexus One using XDA Premium App
Helleqn said:
Will this work on stock Gingerbread?
Click to expand...
Click to collapse
I've added a adb command (mount /system) to work with Gingerbread. It works on mine.
It also works on 2.3.4
Yep. Worked great for me. But with all due respect, it seemed a little fishy to me that your directions have users pull busybox from Cyanogenmod but then have them pull su and Superuser.apk from a random file on a Dropbox account especially since both files are available in the already trusted Cyanogenmod download that was used for busybox. And even more so because the Superuser.apk file using your instructions is a larger file than the one included with Cyanogenmod. So I only used the files from CM and it worked like a charm.
Not accusing you or anything. I'm just pointing that out.
The easier way is to do step 5, then flash the su zip from step 3, and you're pretty much done. You can install busybox through the Market app...
Don't worry for the link, I toke it from the original post for that su release:
http://forum.xda-developers.com/showthread.php?t=682828
I agree it's enough with CM but I intend to get the last version... may be it's not the best option...
Thanks for your comments.
hey guys since "one-click" rooting is now available i though i might post a few instructions on how to install busybox on the ARC/Play/Neo devices...
DO NOT RUN THIS IF U ALREADY HAVE BUSYBOX INSTALLED
download the attached file... it contains busybox v1.17.2 & adb files & will install busybox to /system/xbin/
extract the package in some temporary folder
[ Step 0 ] Root ur device
Root ur device using GingerBreak app
[ Step 1 ] Verify that ur device is rooted
browse to the "files" folder where u extracted package and launch the command prompt in the folder (holding down SHIFT key on keyboard right click and select "Open command window here")
keep the device screen unlocked (also might help to keep screen timeout to >5 mins so that u dont miss the superuser prompts)
now execute the following command in the command prompt
Code:
adb shell "su"
a popup/prompt will come on ur device asking for Superuser permissions... click allow...
if u get permissions denied that means either u did not allow Superuser prompt OR the device was not rooted
[ Step 2 ] Install busybox
{A}
in the same command window (from Step 1) execute the following:
Code:
runme.bat
popup/prompt will come multiple times on ur device asking for Superuser permissions... click allow...
if u get any error or "permission denied" in any of the steps check part {B}
{B} (only if the Step 2 A fails)
<if any popup/prompt comes on ur device asking for Superuser permissions... click allow...>
in the same command window (from Step 1) execute the following:
(this will copy busybox to /data/local/tmp/)
Code:
adb push busybox /data/local/tmp/.
(launch adb shell)
Code:
adb shell
(the following commands are to be input in the adb shell itself)
Code:
su
(remounting system as rw)
Code:
mount -o remount,rw -t yaffs2 `mount | /data/local/tmp/busybox grep /system | /data/local/tmp/busybox awk '{print $1}'` /system
(copying busybox to /system/xbin/)
Code:
dd if=/data/local/tmp/busybox of=/system/xbin/busybox
(verifying ownership)
Code:
chown root.root /system/xbin/busybox
(verifying permissions)
Code:
chmod 04755 /system/xbin/busybox
(installing busybox in /system/xbin/)
Code:
/system/xbin/busybox --install -s /system/xbin
(removing temporary files)
Code:
rm -r /data/local/tmp/busybox
[ Step 3 ] Verify busybox installation
in the same command window (from Step 1) execute the following:
Code:
which busybox
this should return
PHP:
/system/xbin/busybox
and
Code:
ls -l /system/xbin/
this should return a LOT of files lists (which are basically symlinks to /system/xbin/busybox)
if u see only one file (dexdump) then installation was not successful
Search for "Busybox Installer" in the market, I think it's as simple as that
Here's the link https://market.android.com/details?id=com.jrummy.busybox.installer
itskapil said:
Search for "Busybox Installer" in the market, I think it's as simple as that
Here's the link https://market.android.com/details?id=com.jrummy.busybox.installer
Click to expand...
Click to collapse
Busybox Installer sometimes installs in /system/bin and messes up toolbox symlinks... also its option to install in /system/xbin doesnt always work...
it works for my ARC, without busybox, Titium backup not working, after install busybox from market, it T backup works.
keijames said:
it works for my ARC, with busybox, Titium backup not working, after install busybox from market, it T backup works.
Click to expand...
Click to collapse
did u try the manual way i posted in 1st post of this thread?
cause i tested this yesterday night on my Arc and TB, Root Explorer, SetCPU, ScreenShot, AbsoluteSystem, all work with the manual way i posted here in OP (1st post of this thread)...
It is much simpler to use the busybox installer, it works and takes much less time
All I did is root my phone installed titanium and installed busybox through titanium and everything works perfect for me no problems watsoever
Sent from my LT15i using XDA Premium App
i would agree with installing from the market its much more easier and hasssle free! i could not gain acesss to titanium backup, but after i installed bb from market, everything works fine
SiRIus[X] said:
i would agree with installing from the market its much more easier and hasssle free! i could not gain acesss to titanium backup, but after i installed bb from market, everything works fine
Click to expand...
Click to collapse
+1, the market one is as good as you can get...
Sent from my arc using tapatalk
PollPixx said:
+1, the market one is as good as you can get...
To TS, thanks for your time and input! Its not flaming you, but the job can be done much easier
Sent from my arc using tapatalk
Click to expand...
Click to collapse
Sent from my arc using tapatalk
can any body upload the 1.19 version for us on mediafire
I just downloaded titanium back up, clicked on Problems? Which then installed busybox
Sent from my LT15i using XDA App
Awesome guide.
Instead of ADB, you can do it all in terminal emulator.
Regarding market installers, they usually work fine.
But some people experience bugs with them or have limited version's to choose from.
So this is a sure fire way to get what you want installed without hassles.
mount not prmited
it say mount not permitted on my sony xperia t3 please help me. been looking for years to install busybox on my phone.
HI, The latest version of stock firmware for galaxy mini is MJKT3, now how do I root it?
http://www.mediafire.com/?p0oh96olw9h2v72
hi
this will root all versions even the latest one? or like released by 1 minute? or new ones that has been released 1-10 seconds ago?
just try it if it worked just thank me and the Dev of the update package
if not do something else
I forgot to tell you that you will need to flash that package in stock recovery (in CWM it will not work)
It doesn't work.
it doesn't work for me too
super one click can't be used too
Flash this zip in stock recovery. http://www.mediafire.com/?dg360wy61szduv3
Sent from my SGM using Official Cyanogenmod 7.2 (STABLE)
i did flash it
---------- Post added at 06:42 AM ---------- Previous post was at 06:14 AM ----------
can
ashu.bigsmoke said:
Flash this zip in stock recovery. http://www.mediafire.com/?dg360wy61szduv3
Sent from my SGM using Official Cyanogenmod 7.2 (STABLE)
Click to expand...
Click to collapse
can someone tell me if this one will work?
17thGwydion said:
can someone tell me if this one will work?
Click to expand...
Click to collapse
no
I did try another .zip but not succeeded, it just installed super user
you can flash cwm then with the help of adb you can remount system and can push su to /system
tut
dheeraj (dhlalit11) said:
you can flash cwm then with the help of adb you can remount system and can push su to /system
Click to expand...
Click to collapse
can u give me a tutorial on how to push SU to system? or remount system? or full tutorial.. thanks
full tut plz
still no good
still no good feedback, someone try it please
flash cwm with odin
boot into it
connect your mobile with pc
configure your adb connection correctly
open cmd cd to the folder where you are having adb.exe file
copy your su file in the folder where you have adb
type adb remount
adb push su /system/xbin
adb shell chmod 06755 /system/xbin/su
adb shell
if you will get # you are rooted
Can't set SetUID or SetGID bit.
adb shell chmod 06755 /system/xbin/su
"chmod: operation not permitted"
SuperOneClick doesn't work also.
/system partition is 100% full, you have to delete something to push su binary. (i deleted stock samsung apps, and wallpapers)
dheeraj (dhlalit11) said:
flash cwm with odin
boot into it
connect your mobile with pc
configure your adb connection correctly
open cmd cd to the folder where you are having adb.exe file
copy your su file in the folder where you have adb
type adb remount
adb push su /system/xbin
adb shell chmod 06755 /system/xbin/su
adb shell
if you will get # you are rooted
Click to expand...
Click to collapse
you were able to push su which means you have proper access
my be permission change is not needed
try type adb shell su
or use aroma file manager v1.80 and change su permission from that
Unfortunately permission change is a must. You must set setuid and setgid (06755), because upon the su binary execution it will pass the owner's (root) permissions.
Can't use aroma file manager to set permissions because /system/xbin/su owner is root and a plain user can't change permission on files that he doesn't own.
I don't know how to solve this issue.
edit:
I can mount the system partition as rfs:
mount -rw -t rfs /dev/block/stl12 /system
Then, i can set chmod 06755 su.
But after unmount or reboot, permission will be set back to 00755...
dheeraj (dhlalit11) said:
you were able to push su which means you have proper access
my be permission change is not needed
try type adb shell su
or use aroma file manager v1.80 and change su permission from that
Click to expand...
Click to collapse
it is too much weird
can you use linux
you may be able to change the permission of the su file in Linux desktop and then can push it to system with adb
in this way permissions would remain same
Ok, it's solved!
I tried with ubuntu's adb. Unpacked the universal_gb_root_v25.zip. I mounted the system partition in adb. Then pushed all files with correct permissions to /system/xbin (the apks goes to /system/app).
First:
chown all files to root:shell
Second:
chmod 06755 /system/xbin/su
chmod 04755 /system/xbin/busybox
chmod 04755 /system/xbin/sqlite3
chmod 04755 /system/xbin/ssh
now it looks like this:
-rwsr-xr-x 1 root shell 853044 Jun 22 2011 busybox
-rwxr-xr-x 1 root shell 60264 Dec 6 10:28 dexdump
-rwsr-xr-x 1 root shell 125024 Jun 22 2011 sqlite3
-rwsr-xr-x 1 root shell 146720 Jun 22 2011 ssh
-rwsr-sr-x 1 root shell 91980 Jun 22 2011 su
It works after unmount or reboot.
Finally i have root access.
dheeraj (dhlalit11) said:
it is too much weird
can you use linux
you may be able to change the permission of the su file in Linux desktop and then can push it to system with adb
in this way permissions would remain same
Click to expand...
Click to collapse
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **
This has been tested with the LG LEON V10c-EUR-XX
This procedure removes Kingroot , installs superSU ,root binaries and busybox on your system.
Rootable Versions: V10a , V10b , V10c , V10g
Non-root Versions: , V10e
I'm not sure yet about V10d , in some people is working and some not. I think if you use latest kingroot version will work.
Non tested: V10f
If you want to downgrade follow this GUIDE!
Requirements
Make sure your PC can communicate with our LG Leon via adb.
Driver Pack for LG Leon ( Link can be found on #2 Post!)
The success of this method depends on following the procedure very carefully. So read the instructions and make sure you understand every step before you try it.
Procedure
1- Install and run Kingroot 4.0. You can google and download it or you can use the one in the attached zip file. When Kingroot runs it is all in Chinese, but basically you need to be connected to the internet for it to work. It will do its thing and show progress up to 100% after which you can exit the program. Now your phone is rooted. The following steps replaces the Kinguser with SuperSU.
2- Unzip the attached file in your adb directory and then open an adb terminal and make sure the PC can see your phone (you can check that by typing adb devices). Then type the following:
Code:
adb push su /data/local/tmp
adb push busybox /data/local/tmp
adb shell
3- In the shell that you get type the following and make sure you give the permission when the phone prompts you:
Code:
su
4- Continue by typing the following commands:
Code:
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/xbin/busybox && chmod 0755 /system/xbin/busybox
daemonsu -d &
The key is to keep this session running while you continue with the rest, so be careful with typos and monitor this window for any errors.
5- At this point, leave the adb terminal window running and go to your phone, open the Kinguser app, open settings (the wheel at the top right corner of the screen), Root authorization setting, and Remove Root permission. The app will self-uninstall.
6- Uninstall the other two Kingroot programs that are still on your phone (KingRoot and the other one with the blue icon and Chinese text under it).
7- Back to the adb terminal, and type the following:
Code:
cat /data/local/tmp/su >/system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/xbin/ku.sud
busybox chattr -ia /system/xbin/supolicy
rm /system/xbin/ku.sud
rm /system/xbin/supolicy
rm /system/bin/rt.sh
rm /system/bin/install-recovery.sh
rm /system/bin/shipclean
rm /system/bin/start-ssh
busybox chattr -ia /system/etc/install-recovery.sh
busybox chattr -ia /system/etc/install-recovery.sh-ku.bak
rm /system/etc/install-recovery.sh
rm /system/etc/install-recovery.sh-ku.bak
rm /system/etc/install_recovery.sh
rm /system/usr/icu/icusuflag.conf
busybox chattr -ia /system/usr/iku/isu
rm -rf /system/usr/iku
rm /system/kroot_*
rm /sdcard/kr-stock-conf
rm -rf /sdcard/Kingroot
rm -rf /data/data-lib/com.kingroot.RushRoot
rm -rf /data/data-lib/com.kingroot.kinguser
rm -rf /data/data-lib/king
Again, leave the adb terminal window running and go to your phone.
8- Install superSU (from the attached file) on your phone, run it, and let it update the SU binary.
9- Reboot the phone. After about 5 minutes your root is ready.
Downloads + Troubleshooting stuff will be in the 2nd post!
Troubleshooting & Downloading
Troubleshooting
1- Most of the problems that I noticed people have encountered is due to not reading the instructions fully. So make sure you read the OP word by word.
2- If you miss a step or mess up something go back to installing Kingroot and start over from the beginning.
3- Finally, I noticed that with an AT&T sim card in the phone Kingroot fails (why am I not surprised?) Either a reboot occurs in the middle of rooting or it completes the cycle without accomplishing root. If that occurs, my best advice is to change your phone company. If that fails, you may need to factory reset your phone or even install the firmware from scratch and try again without the sim card.
Downloading
MediaFire
Mega (Complete pack)
Drivers
Please do not mirror my links ,I'm counting em!
Hit the thanks button if i help you If you have a question feel free to post it. If you want to say "thank you" you can press the button , isn't worth to reply it
EDIT: If someone test it in another device or V10b etc.. , leave a feedback at comments so i could add it!
Two questions:
1: Are you terryg4 from androidforums? http://androidforums.com/threads/root-rooting-lg-leon-v10c-eur-xx-change-kingroot.946345/
2: Which kingroot 4.0 you talking about? Any minor version?
Plus, here is a fail from v10c..
Please don't copy-paste non-working solutions.
xfce4 said:
Two questions:
1: Are you terryg4 from androidforums? http://androidforums.com/threads/root-rooting-lg-leon-v10c-eur-xx-change-kingroot.946345/
2: Which kingroot 4.0 you talking about? Any minor version?
Click to expand...
Click to collapse
Two answers
1. Yes i'm that guy at androidforums
2. if link is broken i will replace it! I use this version of kingroot and it works for me! Read instructions again!
xfce4 said:
Plus, here is a fail from v10c..
Please don't copy-paste non-working solutions.
Click to expand...
Click to collapse
It's impossible! Send me pics of your android firmware! Maybe you have to downgrade
bkpaokfc said:
It's impossible! Send me pics of your android firmware! Maybe you have to downgrade
Click to expand...
Click to collapse
Here you go then..
Also using your exact version gave me the same response, only Chinese this time.
xfce4 said:
Also using your exact version gave me the same response, only Chinese this time.
Click to expand...
Click to collapse
I don't know nothing about your version. It should work but still don't know why. Anyway if your country have more Firmwares try downgrading.
If still doesn't work use this http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197 maybe it will solve your problem.
Today I reflashed Stock Android 4.2 on a Xperia T.
Before there was Cyanogenmod (Android 5) installed.
I forgot to delete all user files/folder in internal memory.
Now, I cannot delete or access old user files and folders, even as root!?!
Its a problem of the permissions, I guess.
I can RENAME folders, but cant delete/open/chmod/change permissions recursiv, not with a file manager (as root), not with adb, not with "rm - rf", nothing.
So how I can get rid of those old folders?
E.g., for camera I had to rename DCIM to DCIMold, and create a new folder to get saving pictures to work.
Hi did you use neo's cm12.1. if you did use his, did you flash uninstaller,zip if didn't flash it here is a link https://www.androidfilehost.com/?fid=95916177934533137 and if you didn't use neos im sorry i dont know
If I helped please be kind and click like :good::good:
Yes, it was neo's cm12.1.
No,i didnt flash any uninstall.zip
Thank you for the info.
But I guess its to late now?
rrutk said:
Yes, it was neo's cm12.1.
No,i didnt flash any uninstall.zip
Thank you for the info.
But I guess its to late now?
Click to expand...
Click to collapse
nope dont think its to late just flash a custom kernel and then flash the uninstaller
If i helped please be kind and click like :good::good:
alial04 said:
nope dont think its to late just flash a custom kernel and then flash the uninstaller
If i helped please be kind and click like :good::good:
Click to expand...
Click to collapse
if I send the only command from the uninstall.zip
find /sdcard -user 1023 -exec chown 2800:2800 {} \;
in Terminal as SU, nothing changes....
Will it be a difference while flashing it?
If you want to use stock rom write this in terminal:
Code:
su
chmod 777 /mnt/media_rw/sdcard0
chown 2800:2800 /mnt/media_rw/sdcard0
chown -R 2800:2800 /mnt/media_rw/sdcard0
krasimiretov said:
If you want to use stock rom write this in terminal:
Code:
su
chmod 777 /mnt/media_rw/sdcard0
chown 2800:2800 /mnt/media_rw/sdcard0
chown -R 2800:2800 /mnt/media_rw/sdcard0
Click to expand...
Click to collapse
I'm already on stock ROM now.
I did the above mentioned, but I have to use "/mnt/sdcard", because "mnt/media_rw/sdcard0" seems not exist.
chmod 777 /mnt/sdcard
chown 2800:2800 /mnt/sdcard
works.
su busybox chown -R 2800:2800 /mnt/sdcard
gives "read only filesystem".
if I do a "mount -o remount rw /sdcard" before the command it works, BUT NOTHING CHANGES.
cant delete the files.
crazy.
do I really need to flash another kernel before?
cant understand why root has no access to the files.
SOLVED.
Correct is (as SuperUser):
busybox chmod -R 777 /mnt/int_storage
busybox chown 2800:2800 /mnt/int_storage
busybox chown -R 2800:2800 /mnt/int_storage
rrutk said:
I'm already on stock ROM now.
I did the above mentioned, but I have to use "/mnt/sdcard", because "mnt/media_rw/sdcard0" seems not exist.
chmod 777 /mnt/sdcard
chown 2800:2800 /mnt/sdcard
works.
su busybox chown -R 2800:2800 /mnt/sdcard
gives "read only filesystem".
if I do a "mount -o remount rw /sdcard" before the command it works, BUT NOTHING CHANGES.
cant delete the files.
crazy.
do I really need to flash another kernel before?
cant understand why root has no access to the files.
Click to expand...
Click to collapse