yashsingh1/xdaforums huggingface dataset:
[Nexus One General] 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
[Nexus One General] jasonlotp:
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. :)
[Nexus One General] seven2099:
Method for using GingerBreak for the Atrix listed in my signature :)

Woot!
[Nexus One General] efrant:
Great. Why are you posting it in the Nexus One forum?
[Nexus One General] 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
[Nexus One General] sarshadd:
@hellbunny and pilot-calc22

If you tried

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.
[Nexus One General] :
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
[Nexus One General] 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!
[Nexus One General] 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 :D
[Nexus One General] sarshadd:
install custom recovery, shootme app, titanium backup app, delete bloatware apps, anything else you want, custom roms, kernals- overclocking/underclocking cpu
[Nexus One General] curiousitykilledthepat:
Great tutorial! Thanks efrant! My nexus one is finally rooted! :D
[Nexus One General] 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?
[Nexus One General] 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???
[Nexus One General] :
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.
[Nexus One General] hungryTux:
My Nexus One's Rooted alright!

This worked like a charm on my first attempt!!:D

Anyone attempting this, do remember to clean up your SD card and to reboot after that, before you actually run the exploit.
[Nexus One General] flixos:
I've tried for three times, each step, checked everyone...but i'm still stuck on the "sendmsg() failed?" message. Seems that my only choice left, right now, is to clean the SD card and try again.

But i can´t understand why there are some guys out there that, actually, made this work without doing anything to their SD cards.
[Nexus One General] bourne-nolonger:
I definitely want to give this a go.

I was wondering if someone could help me confirm a few things though..

Using this method to root, I should still be able to receive OTA updates on the phone. When the update comes down it should install, but I might lose root. Is this correct?

If the update should fail (I have seen a few people having problems), is there any real risk to the phone? Or should the phone continue to function after a failed attempt?

Sorry for the dumb questions. I just wanted to clear those things up before attempting.

Cheers
[Nexus One General] efrant:
Correct. It will download and install, and you WILL lose root.

No real risk of damage. There is always a slight risk that it will mess up your ROM, and you would have to re-flash a new one.
[Nexus One General] bourne-nolonger:
thank you efrant, much appreciated for clearing that up!

hmm, the chance of messing up the ROM is a little scary.

I currently run the stock gingerbread ROM and wish to stay completely stock but have root (it looks like that is how you are running looking at your sig). So if I were to somehow mess up the stock gingerbread ROM, could I download (if it is available somewhere), a stock gingerbread ROM and flash that?

on a completely unrelated note efrant I see you used to rock the HTC Tytn II.. thats awesome.. I used to love that phone.. although I never owned one.
[Nexus One General] efrant:
If your boot loader is locked, the easiest way is to get back to stock Gingerbread is to download the FRG33 (Froyo) shipped image from here, extract the zip with the zip, rename it to PASSIMG.zip, place it in the root of your sdcard and boot into the bootloader. It should recognize it and ask you if you want to flash. Then you'll receive all the OTA updates. However, if you have to do that, you might as well root the FRG33 (using something like SuperOneClick), and flash a pre-rooted stock image... Much easier than trying to root Gingerbread.
[Nexus One General] bourne-nolonger:
Thank you again for helping me clear that up!

It makes sense that it would make more sense to simply go with a ROM that is stock with root already achieved, hopefully it will not come to that though :)

I am going to give this a try and hopefully all will go well!
[Nexus One General] MitchRapp:
when you say "clean the sd card" you mean format it completely... but then why do that? Might as well unlock the bootloader and wipe everything and start over no? SD cards nowadays contain 50% or more of our apps

can I just stick a blank sd card and put back the sd with all the data on it after rooting?
[Nexus One General] MitchRapp:
blank sd works

put the original back after - no data lost, just takes 1 more reboot.
[Nexus One General] sarshadd:
Question, now that I'm rooted with a custom recovery I'm going to play around with flashing different ROMS.

Once I start flashing ROMs is there an easy way to get back to stock without losing root? Or will I have to go back to stock then re-root?
[Nexus One General] danger-rat:
Just flash a pre-rooted stock ROM, theres a few floating around...
[Nexus One General] darkeingel:
Why people still trying to root "the old way"?

There's a little up out there that automate the whole process.

GingerBreak apk is on our forums, and worked for me with no faults (was on stock neverrooted before 2.3.3 OTA).
[Nexus One General] BennyInc:
I did it the "old way" yesterday, as it was out a little longer and had more positive feedback. Also, I like going into the details a little more manually to know why something goes wrong if it does.
[Nexus One General] efrant:
Because this is a developer forum and members generally want to understand what they are doing, not just use a "1-click" and not know what is happening behind it all... What matters is understanding the journey...
[Nexus One General] bra1nDeaD:
Indeed. As a developer myself I do not want to leave my phone, that is very personal to me, in a state where I don't know what has happened to it.

Also, I rooted my phone with GingerBreak a few hours when the hack came out, while the APK was not even conceived yet. So knowing what you're doing gives you more power, but I do see the benefit of having a simple way of rooting so that more people are able to do it. Not everyone on this forum is a developer :D
[Nexus One General] CJSnet:
Since running these instructions and successfully rooting, I have noticed the following issues:

1) Gmail search no longer works. It just stays at 'Loading conversations...' after searching. I have tried uninstalling updates, deleting its data and cache, rebooting, then reinstalling updates. No good. Any ideas?

2) All my apps went haywire that had been installed on the SD card before. When I put my original SD card back in, they all force closed, requiring a complete uninstall and reinstall of perhaps 15 apps. A real pain. Even then, I ended up with 10MB less space on the phone than before - like some apps were still hidden but taking up space, even after uninstall and reinstall. I've resolved it all now, but still fear I've lost space. Any ideas? This shouldn't happen surely.

3) Will the next OTA work with this root in place?
[Nexus One General] danger-rat:
1 - Delete data from Gmail, using the app manager.

2 - Sorry, could be a number of things...

3 - Won't effect updates, unless you start changing things. Still, if you install a custom recovery, you could always install the updates yourself (preferably pre-rooted versions)
[Nexus One General] CJSnet:
Thanks

Re 1 as mentioned I already deleted Gmail data. Twice. What else could cause this weird problem? I really need search.
[Nexus One General] CJSnet:
Oh, and it works fine on my Gmail account but not my Google Apps account. Worked fine before the flash I'm sure. Weird hmm?
[Nexus One General] danger-rat:
You could also try deleting data from Google Services Framework?
[Nexus One General] CJSnet:
Thanks, how do I do this?
[Nexus One General] danger-rat:
Exactly the same way you did it for Gmail:

Menu> settings> applications> manage applications> select the All tab, find Google Services Framework, select and delete data. Reboot phone...
[Nexus One General] CJSnet:
Thanks that did it!
[Nexus One General] CJSnet:
Actually turns out it was the LauncherPro Gmail widget causing this blockage issue. Deleting the widget from the homescreen fixed it. Same applies to any other third party apps that access your Gmail apparently.

Hope this helps someone else.
[Nexus One General] NameMaciek:
Android 2.2.1 Froyo

$ ls -l
ls -l
-rwxr-xr-x shell shell 1926944 2010-03-22 20:29 busybox
-rwxr-xr-x 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 13:41 GingerBreak
$ ./GingerBreak
./GingerBreak

[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi

[**] donate to 7-4-3-C@web.de if you like
[**] Exploit may take a while!

[+] Detected Froyo!
[+] Found system: 0xafd14189 strcmp: 0xafd1cbfd
[+] Found PT_DYNAMIC of size 264 (33 entries)
[+] Found GOT: 0x000142c0
[+] Using device /devices/platform/goldfish_mmc.0
[*] vold: 0067 GOT start: 0x000142c0 GOT end: 0x00014300
[*] vold: 0067 idx: -3072 fault addr: 0x000131f8
[+] fault address in range (0x000131f8,idx=-3072)
[+] Calculated idx: -1998
[*] vold: 0669 idx: -0001998
[*] vold: 0669 idx: -0001997
[*] vold: 0669 idx: -0001996
[*] vold: 0669 idx: -0001995
[*] vold: 0669 idx: -0001994
[*] vold: 0669 idx: -0001993
[*] vold: 0669 idx: -0001992
[*] vold: 0669 idx: -0001991
[*] vold: 0669 idx: -0001990
[*] vold: 0669 idx: -0001989
[*] vold: 0669 idx: -0001988
[*] vold: 0669 idx: -0001987
[*] vold: 0669 idx: -0001986
[*] vold: 0669 idx: -0001985
[*] vold: 0669 idx: -0001984
[*] vold: 0669 idx: -0001983
[*] vold: 0669 idx: -0001982
[*] vold: 0669 idx: -0001981
[*] vold: 0669 idx: -0001980
[*] vold: 0669 idx: -0001979
[*] vold: 0669 idx: -0001978
[*] vold: 0669 idx: -0001977
[*] vold: 0669 idx: -0001976
[*] vold: 0669 idx: -0001975
[*] vold: 0669 idx: -0001974

[!] dance forever my only one
# id
id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet)
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# chmod 777 /system/bin
chmod 777 /system/bin
# ./busybox cp busybox /system/bin
./busybox cp busybox /system/bin
cp: can't create '/system/bin/busybox': Cannot allocate memory
[Nexus One General] efrant:
If you are on Froyo, then use rageagainstthecage instead of GingerBreak. It is much more stable: http://xdaforums.com/showpost.php?p=9953100&postcount=11
[Nexus One General] irahim:
Has anyone verified if this works with nexus one 2.3.4?
[Nexus One General] GnatGoSplat:
I've verified it does not. It just spins and spins. I read on some blog last night that whatever security hole Gingerbreak was using, has been closed in 2.3.4.
[Nexus One General] HiON:
So, how can I prevent my phone from auto installing the update on next reboot?

(I have original GRI40 Firmware)
[Nexus One General] danger-rat:
Are you rooted?
[Nexus One General] droidexplorer:
I used Gingerbreak on 2.3.3 to get root. Then installed

Custom recovery Amon-RA's one. Flashed GRJ22 manually and flashed su.zip immediately after. Did the trick for me. Now stock rooted on 2.3.4.
[Nexus One General] GnatGoSplat:
I don't know, but it's easy enough to re-root. If your firmware, bootloader, and recovery are 100% stock, all you need to do after taking the update is to unlock the bootloader, flash to Amon-Ra or Clockworkmod recovery, then flash SU.zip. My bootloader was already unlocked as it had a custom ROM in the past, so I just had to flash Clockworkmod recovery, then SU.zip. Didn't have to worry about anything else because SuperUser was already installed from Gingerbreak.
[Nexus One General] HiON:
I dont what to void my warranty. So I will root my Nexus One only with kinds of this methods, not unlocking the bootloader.
[Nexus One General] efrant:
See post 91...

1) Root your 2.3.3

2) Flash Amon_RA's recovery

3) Download the update from the Google link

4) Download ChainsDD's Superuser zip

5) Flash the Google update and DON'T reboot

6) Flash the Superuser zip

7) Reboot. Done.
[Nexus One General] MitchRapp:
yup that all worked, thanks!

1) flashed amon_RA from within ROM Manager

2) rebooted into recovery

3) removed sig verification

4) flashed update.zip

5) flashed su.zip

6) rebooted (long reboot)

7) #winning !

thanks !
[Nexus One General] HiON:
And this wont void the Warrenty?
[Nexus One General] efrant:
Of course it does. Installing anything to the /system partition, other than official updates, voids the warranty. However, you can undo everything so no one would know the difference. ;)

(As an aside: I never really understood why people were soo concerned about the warranty anyway. It's not like you get a new phone -- it's refurbished...)
[Nexus One General] GnatGoSplat:
I would also remove the Recovery folder from your update.zip so it doesn't overwrite your 3rd party recovery with the stock one.
[Nexus One General] hakkiesco:
----------------------------------------

Hello folks..

The whole process goes just fine until the end where I check to see if I gained root access..

c:\Program Files (x86)\Android\android-sdk\tools>adb shell
$ su
su
su: permission denied
$

I'm on a HTC Desire HD 2.3.3

any thoughts?

The strange thing is when I run GingerBreak 1.2 on the device it does not restart but I get root access until next reboot.. I can't do anything with it since the sd card won't mount..
[Nexus One General] efrant:
This step by step is for the Nexus One only. It won't work on the Desire HD for two reasons:

1) the Desire HD is NAND locked. You can only get temporary root by using the first part of this guide You need to remove the NAND lock before the rest will work.

2) the partitions on the HD are different than on the N1. On the N1, the system partition is mtdblock3. You will need to mount the right one on the HD as r/w (once you unlock the NAND).
[Nexus One General] hakkiesco:
Thanks for the replay.. I'll be deeply grateful if you could explain a littile bit more about this procedure "You need to remove the NAND lock" or direct me to the right path..

Thanks in advance
[Nexus One General] efrant:
I suggest you look/ask in the Desire HD forum. This is the Nexus One forum...
[Nexus One General] curiousitykilledthepat:
I accidentally updated OTA to 2.3.4 and my root from 2.3.3 got erased. i have a broken power button and gingerbreak was the only way i rooted my N1. tried doing the same procedure and it failed. how do i do it now?

are there any updates to gingerbreak?

how do i downgrade to 2.3.3 or to froyo? i've been trying the PASSIMG.ZIP but all i get is "no image found" on the bootloader after it scanned passimg.

I really want to root my phone. I was stupid to update :(((((
[Nexus One General] efrant:
Try using a different sdcard. It might solve the "no image found" issue. As well, make sure the file is named correctly, i.e., PASSIMG.zip, not PASSIMG.zip.zip and check 5o make sure that it is not a zip file inside another zip file.
[Nexus One General] Haeriz:
Downgrade Failed

I have followed the steps but fails in

./gingerbreak

im not getting root #
[Nexus One General] danger-rat:
What version of android are you trying this on?
[Nexus One General] :
Doesn't work on SGS I with Samsung 2.3.4?

Hi,

I've tried to follow procedure manually using Linux ADB but it just sits there without printing anything for over an hour:

$ pwd
/data/local/tmp
$ ls -l
-rwx------ shell shell 16830 2011-04-21 07:41 GingerBreak
-rw-rw-rw- shell shell 196521 2010-10-16 22:04 Superuser.apk
-rw-rw-rw- shell shell 26324 2011-02-13 15:43 su
-rwxr-xr-x shell shell 1062992 2010-10-16 23:29 busybox
-rw-rw-rw- shell shell 24120 2010-10-16 22:04 sqlite3
-rwx--x--x shell shell 16830 2011-06-13 08:14 boomsh
-rw------- shell shell 82840 2011-06-13 08:14 sh
-rw------- shell shell 11157 2011-06-13 08:20 crashlog
$ ./GingerBreak

[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi

[**] donate to 7-4-3-C@web.de if you like
[**] Exploit may take a while!

[+] Plain Gingerbread mode!
[+] Found PT_DYNAMIC of size 232 (29 entries)
[+] Found GOT: 0x000284b8
[+] Using device /devices/platform/s3c-sdhci.0/mmc_host/mmc0
[*] vold: 0000 GOT start: 0x000284b8 GOT end: 0x000284f8

What else can I do?

Thanks.
[Nexus One General] Dambo:
Please help.

Can not install GingerBreak APK on my device.

LG P350

Android 2.2.2

Gives error "Parse Error

There is problem parsing the package"

Thanx
[Nexus One General] Jack_R1:
You don't need GingerBreak for Android 2.2.2, it won't help you at all.

Use Visionary+.

And you're in the wrong section.
[Nexus One General] CCpotter:
This is exactly what i'm looking for, thank you very much, but i still have to be careful about re-booting my cellphone, one of my friend get his Desirez obsoleted by re-booting.
[Nexus One General] cipjanin:
does this works on 2.3.5, its running 30mins already its that normal?
[Nexus One General] efrant:
I don't think it will work. You need zergrush. It's easily found in these forums.
[Nexus One General] sidlo:
Hi, I have Motorola Defy+ from Vodafone with android 2.3.6. Can I possibly you this manual and insted of Gingerbreak use zergRush file from SuperOneClick?

Thanks for your help.
[Nexus One General] efrant:
Yes, it will work, however, you would need to have the correct mounting path for /system for the Defy. The path stated in the second post is for the Nexus One.
[Galaxy S I9000 Q&A, Help & Troubleshooting] darkfangex5:
ok so i had stock 2.1 update 1 , gt i9000T , and flashed I9000XWJS8 europe , i ACCIDENTALLY (or accidentally used a pit file) checked re-partition and now this retarted recovery screen with "your storage not prepared yet, please use UI menu for format and reboot actions"

"copy default media content failed"

funny thing though even tho i get looped into that screen i can just use speedmod k13E and bypass it and get a forceclose error on the welcome screen and everything works i think didnt really test it , under sd card stuff i have 0.00 gb on the bottom is that correct? but when i enter speedmod and go clockwork and back to recovery 3e it shows the same error. anyone know how to get rid of that bs? and i used odin 1.7
[Galaxy S I9000 Q&A, Help & Troubleshooting] azzledazzle:
mmm... internal sd card.

what i would do, (not saying you have to do this) is download a firmware with three files and 512 PIT, check the re-partition box in odin, then after the successful flash. boot into recovery and format my sd card. along with data / cache / dalvik cache.

then rebooting should be back to normal. apply a restore and everything is normal :D
[Galaxy S I9000 Q&A, Help & Troubleshooting] #G#:
Hello!

I am in the same situation with a Galaxy Tab 7 aka gt_p1000... I wanted to reset the tablet. No way through normal os procedure ->

I did a super silly "dd if=/dev/zero of=/dev/mmblkp2" from local root terminal

/dev/mmcblkp2 was the device mounted in /data :) yahoo I now need to format the partition... so now I should mkfs /dev/mmcblkp2... but how?

I tried to install the latest for europe p1000

P1000XXJQ1_P1000XXJQ1_P1000XXJPZ_HOME.tar

Used odin repartitioning applying pit and tar for pda section, repartitioning. (tried not repartitioning too)

I then applied dbdata.tar not repartitioning.

Completes but when rebooting gives this message as darkfangerex5

"your storage not prepared yet, please use UI menu for format and reboot actions"

"copy default media content failed"

SO your suggestion is what I'd go for..

"download a firmware with three files and 512 PIT" on samfirmware I have no way of knowing if there is any similar rom config.

Can you point any rom to use? My tablet is stuck at the moment :(((

@darkfangerex5

did you solve your problem and how?

Thanks for any help :)

G
[Galaxy S I9000 Q&A, Help & Troubleshooting] #G#:
SOLVED

I solved using Overcom GB safe stock procedure.

http://www.teamovercome.net/p1000/?page_id=17

Pointed by www.androidiani.com/forum/samsung-galaxy-tab-7/100307-rom-3-file-dove-la-trovo.html

Cheers :)