GingerBreak released

[HellBunny]

I can't get my root to stick.

I have SuperUser.APK 2.3.6.1 installed ( my su is apparently out of date the .zip it placed on my SDcard is bad so i can't flash it). Is the out of date su the reason why superuser isn't granting, or asking to grant, things root?

or could su itself not have the right permissions set?

nvm it was the stupid out of date su, i flashed it manually.

I can't get the root to stick either. I am using the su bundled with Superuser.apk 2.3.6.1. Are you saying the su in the apk is out of date? Where did you get the right version of su?

 

[jasonlotp]

It seems that clearing out you SD card is key to making Gingerbreak run fast.
I've got past running GingerBreak but now I'm stuck at a supposedly root shell with permission issues:

# ls -l
ls -l
-rws--x--x root root 82840 2011-04-22 09:09 sh
-rwx--x--x shell shell 16830 2011-04-22 09:09 boomsh
-rwxr-xr-x shell shell 1926944 2010-03-22 20:29 busybox
-rw-rw-rw- shell shell 26264 2010-08-17 17:44 su
-rw-rw-rw- shell shell 196521 2010-09-05 15:47 Superuser.apk
-rwx------ shell shell 16830 2011-04-21 04:40 Gingerbreak
# ./busybox cp busybox /system/bin/
./busybox cp busybox /system/bin/
cp: can't create '/system/bin/busybox': Permission denied

Any ideas?

 

[HellBunny]

I had the same problem. I follow the steps in post #9.

Execute the following before copying files to /system/bin

# chmod 777 /system/bin

Reset the permission afterward.

# chmod 755 /system/bin

However, I can't get the root to stick after existing the shell. Permission denied when trying to execute su.

 

[danger-rat]

Check your permissions on busybox and su. I blindly assumed they had changed, but when I checked, they hadn't. Check, and re do the permissions...

 

[soiioz]

after resetting the permissions, u need to type
chmod 4755 /system/bin/su
chown root /system/bin/su
chmod 4755 /system/bin/busybox

I'm not sure about the second line, but i managed to make the root stick after typing these commands

Sent from my Nexus One using XDA App

 

[HellBunny]

@danger-rat & soiioz

Thanks both for the tips. What will the ls-l outputs look like for busybox and su if the permission is changed successfully? I will give it a shot again tonight.

 

[danger-rat]

There seems to be some variation in the preferred permissions, but you're basically looking for 755 as either of the following (in /system/bin):
rwx r-x r-x
rws r-x r-x

FWIW, these are just basic binary, r = read, w = write, x = execute, and the columns contain values of 4, 2, and 1 respectively.
rwx = 4+2+1 = 7
r-x = 4+0+1 = 5
r-x = 4+0+1 = 5

rwx r-x r-x = 755

 

[jasonlotp]

The procedure that worked for me (with help from other commenters):

Now, We need to make the root permanent by installing su:
1) Mount the system partition as read/write: mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
2) Change directory to where you pushed su, busybox and superuser.apk: cd /data/local/tmp
3) Run busybox to copy itself to the proper directory: ./busybox cp busybox /system/bin
4) Change the permissions on busybox: chmod 4755 /system/bin/busybox
5) Run busybox to copy Superuser.apk to the proper directory: busybox cp Superuser.apk /system/app
6) Run busybox to copy su to the proper directory: busybox cp su /system/bin
7) Change the permission on su: chmod 4755 /system/bin/su
8) Mount the partition as read-only: mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
9) Exit the root shell: exit
10) You should now see $ instead of #
11) Exit the shell: exit

Add these steps in to the original procedure
Step 2.1: chmod 777 /system/bin
Step 3.1: chown root /system/bin/busybox
Step 4.1: chmod 777 /system/app
Step 5.1: chmod 755 /system/app
Step 6.1: chown root /system/bin/su
Step 7.1: chmod 755 /system/bin

With these extra steps the root will stick.

 

[seven2099]

Method for using GingerBreak for the Atrix listed in my signature

Woot!

 

[efrant]

Method for using GingerBreak for the Atrix listed in my signature

Woot!

Great. Why are you posting it in the Nexus One forum?

 

[pilot-calc22]

also if all command (chmod 777 chmod 755 etc.etc. ) are OK, when I type "su" in out i Have "permission denied"

help me

 

[sarshadd]

@hellbunny and pilot-calc22

If you tried

The procedure that worked for me (with help from other commenters):



Add these steps in to the original procedure
Step 2.1: chmod 777 /system/bin
Step 3.1: chown root /system/bin/busybox
Step 4.1: chmod 777 /system/app
Step 5.1: chmod 755 /system/app
Step 6.1: chown root /system/bin/su
Step 7.1: chmod 755 /system/bin

With these extra steps the root will stick.

and your root still isn't sticking, it might be because your SU bundled with the 2.3.6.1 superuser.apk was outdated like mine. Accordingly, it would be more accurate to say su, being out dated, is not recognizing when apps are asking for root permissions therefore superuser.apk cannot ask you to approve them.

to fix this had to install a custom recovery, turn off signature verification, and flash the the eclair/froyo build of 2.3.6.1 superuser from here. This overwrote the old su and gave it the correct permissions etc etc root stuck etc etc.

Hope that helps.

 

[lutheyus]

Not working on N1 (GRI40, S-ON)

Hi guys

I've got the message saying "dance forever my only one" but the prompt hasn't changed to #.

Regards

 

[HellBunny]

Success. Applying chmod 777 to both /system/bin and /system/app before changing the permission on busybox and su did the trick. Root is sticking now!

 

[j00m]

Hi all, what will you do after got root?

With me, do'nt know what to do, except internal space is added size with Superuser.apk, su, busybox

Give me a the way

 

[sarshadd]

install custom recovery, shootme app, titanium backup app, delete bloatware apps, anything else you want, custom roms, kernals- overclocking/underclocking cpu

 

[curiousitykilledthepat]

Great tutorial! Thanks efrant! My nexus one is finally rooted!

 

[curiousitykilledthepat]

Oh wait, does this make me permanently rooted? cos I'm planning to download CM7

Root check says I have root access.
Standard su binary location: /system/xbin/su: No such file or directory
Root user id: uid=0(root)

is that okay?

 

[jmoren44]

How can i remove boomsh and sh files? my laptop shut down and now i can't run gingerbreak again until i remove both files, but my phone isn´t rooted, so... any help???

 

[edychen]

Waiting a while worked for me:

[+] Calculated idx: -2003
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[*] vold: 23005 idx: -0002003
[*] vold: 23005 idx: -0002002
[*] vold: 23005 idx: -0002001
[*] vold: 23005 idx: -0002000
[*] vold: 23005 idx: -0001999
[*] vold: 23005 idx: -0001998
[*] vold: 23005 idx: -0001997
[*] vold: 23005 idx: -0001996
[*] vold: 23005 idx: -0001995
[*] vold: 23005 idx: -0001994


[!] dance forever my only one
#

Didn't reformat my sd card at all.

Edit: Karma's a *****. Root didn't stick and I can't get it to root again. Wtf.