yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] appagom:
by the way one of the universal methods I remember was SuperOneClick which was advertised as being the solution to all rooting going forward forever and required installing hundreds of MB of fancy programming framework (Mono or .Net as I recall) to copy in one little file. Well oops it was based not on any fundamentals of how things work, but on a very sneeaky and fragile exploit that we should be glad android fixed, because bad people are catching on to exploits. Don't get me wrong, many people who have no reason to care about linux or su files enjoyed easy rooting with it and that's great. The point though is nothing is universal forever is computing and I think a review of "universal" methods of rooting yourself should have someone in the thread at least (like me) bring up the fundamentals... which as computing stuff goes, are simple.

---------- Post added at 11:44 AM ---------- Previous post was at 11:36 AM ----------

If you don't care about incrementing your flash counter (for warranty repairs sake and don't want to reset it with a USBJIG) just get any rooted kernel like CF's and flash it with odin. If you care about the flash counter, follow one of the mobile odin methods here probably. If you know your way around linux and want to learn something, you can try the way I rooted mine (SHW-M250K is almost identical to and software interchangable with your phone).
[Galaxy S II Original Android Development] The-Hulk:
I have added this to my sticky thread, good guide, thaks for you hard work. HERE
[Galaxy S II Original Android Development] Phil3759:
Happy it helped :-)
[Galaxy S II Original Android Development] Stileth:
Great thread Phil,

I have used your updated files from this thread, but before I have used the original ones from Rachmat3. Do I need to remove any leftovers like superuser or all is overwritten by SuperSU?

Thx
[Galaxy S II Original Android Development] Phil3759:
The script only overwrites same files, nothing else, so it should work.

You can still use the un-root script from Rachmat3 before this one

The advantage with Chainfire SuperSU is that it offers the possibility to unroot completely and to install superuser alternative if you like. The opposite is more complicated (not done within the app)
[Galaxy S II Original Android Development] Phil3759:
Added a new method using S2Root from recognized developer lyriquidperfection. It involves flashing insecure kernel and using a better supported tool than SuperOneClick
[Galaxy S II Original Android Development] gcee:
Phil3759,

What makes method 1 not work on Gingerbread (if anything)?
[Galaxy S II Original Android Development] Stileth:
Because this whole thread is about rooting ICS not GB.
[Galaxy S II Original Android Development] Phil3759:
The CWM script mainly. I never tried on GB, but could do it, have an S2 still on GB

Other methods, the insecure kernels ones, will work on GB however
[Galaxy S II Original Android Development] Phil3759:
I updated first post to include last busybox v1.20.2

The binary is not mine, compiled from Stephen (Stericson) Free Busybox app

https://play.google.com/store/apps/details?id=stericson.busybox

I also include a busybox only file if you already have supersu

No need to update if you already rooted, it will not add much probably compared to v1.20.1

I tested it on my phone and root apps work fine with this busybox
[Galaxy S II Original Android Development] Phil3759:
Minor fix release in post 1 for CWM_Root_SuperSU.0.93-Busybox.1.20.2:

You do not need to flash again if you are rooted. It is a fix for people coming from a rooted phone
[Galaxy S II Original Android Development] jorsolano:
Hey Phil,

Thanks, very nice method. I just test it and it works like a charm.

Despite you mentioning the "no need" or the "two more clicks" to use the advanced CWM, i am more confortable with launching CWM from the app drawer (e.g. CF-root). I guess for those of us who likes flashing it is worth the advanced options on the custom recoveries, like nandroid, cleaning caches, fix permissions, etc.

Is it possible to "replace" the internal recovery with the touch for "good"? :confused:. I have seen that it is possible with other Gs2 models.
[Galaxy S II Original Android Development] Phil3759:
Yes, CWM Manager from Chainfire is the main advantage of CF_Root kernel. No way to run it other than on a CF_Root kernel sadly

To replace stock recovery with CWM recovery, you need a custom kernel, this is the only way. Recovery is overwritten by stock one on each boot. A custom kernel will block that action on boot.

This method is to have root on any ics phone with a cwm image, without waiting for custom kernels

Hope it answered your question
[Galaxy S II Original Android Development] Phil3759:
First post + files update:
[Galaxy S II Original Android Development] Phil3759:
Update (thanks to BrainB0ne)
[Galaxy S II Original Android Development] absro:
Thank you very much!

I managed to root my Galaxy Note LQ3 using your method. However, my device had less than 1 Mb free on the /system partition, so I modified the uninstall to also remove Aurora2.apk and Aurora2.odex (it's a live wallpaper that occupies about 5 Mb); after doing that, everything went very smooth!

If someone else has this issue:

- extract CWM_Unroot_SuperUser-Busybox-Uninstaller-Update1.zip META-INF/com/google/android/updater-script somewhere

- edit the file with an editor able to handle unix-style end of line (Windows Notepad will display everything on 1 line; I used Notepad++)

- after the "Removing Busybox..." message add the lines to delete whatever package you want to delete:

delete("/system/app/Aurora2.apk");
delete("/system/app/Aurora2.odex");

Cheers!
[Galaxy S II Original Android Development] asalah0923:
Great Guide ,

thanks you very much for your work :)
[Galaxy S II Original Android Development] Oujee:
anyone can help me plz? I tried almost every method and got nothing I am on stock JPLPF when using first method in stock recovery it says E:/ faild to mount ..... when tried mobile odin could't detect the phone model can anyone till me how fix the mount error plz?
[Galaxy S II Original Android Development] Phil3759:
You messed things while trying "almost every method"

Only way I know to fix this issue is a full flash using odin, after wipe /data, /cache and ideally /system

- Go into CWM

- wipe data and cache

- format /system

- Reboot in download mode

- Flash a full ROM with odin

An alternative to the wipe in CWM is a flash with odin + corresponding pit + repartition, but probably not needed if above cwm method works

After that, you can root with CF_Root or the method in post 1

Sorry, I never saw a report to fix it in another way

Hope you have a backup of your /data
[Galaxy S II Original Android Development] Idebutterpiep:
Guide to Root your ICS phone S2 Method 1

Method 1 was working for me only for one part. Until: CWM touch recovery interface.

Than I can choose: "install zip from sdcard". Than it goes back to reboot and not to sd card.

What Do I do wrong?
[Galaxy S II Original Android Development] Phil3759:
What is your phone? Get the correct cwm for your phone if not the S2. Also, in cwm, internal sd is the emmc external and sdcard is the actual internal sd
[Galaxy S II Original Android Development] Phil3759:
Thanks for the details. Will look at it later when dine with kernels. My only concern was that i need to change script for each rom or phone. Not sure if they all use same compression... Will look at it. But, actually, for the s2, method 1 is the easiest for any noob around since it only needs an external sd in a new phone

Method 1, download supersu zip and flash in stock recovery directly
[Galaxy S II Original Android Development] appagom:
Yes, I agree actually, that's easier. I'm too used to the m110s where it wasn't even possible so I still forget that sometimes.

oh and the unmount above is wrong. Actually the recompression tool compresses from the directory tree, not the image, so no unmount.
[Galaxy S II Original Android Development] Phil3759:
To spare my time, do you know if all img files for samsung roms are same structure and compression? I have a big doubt...

And is it same as other phones img files? (big doubt here too...)
[Galaxy S II Original Android Development] appagom:
SGS ROMS were uncompressed.

SGSII ROMS use this compression. I'm using it now on mine.

I am now remembering my own FAQ a year ago in my sig about Motorola ROMS... those were a pain to deal with actually and I never did deal with it.

---------- Post added at 06:19 PM ---------- Previous post was at 06:16 PM ----------

as for structure.. just partition images. For SGS it was rfs or yaffs2 or something, I forgot now for /system. For SGS II its ext4 after much pressure from xda members.
[Galaxy S II Original Android Development] pilotn:
galaxy nexus

Does method 1 works for galaxy nexus too?
[Galaxy S II Original Android Development] Phil3759:
Yes but you could need cwm first to bypass signature check. Just test it and report back
[Galaxy S II Original Android Development] appagom:
So for sgsII the compression and decompression tools exist on the ROM in /system/bin.

simg2img and make_ext4fs

and by the end of this post we will only need compression, not decompression anyway...

In the link there was a useful script mkuserimg.sh but it just used make_ext4fs

It's also true that on the ROM all system files are world readable and that you don't need to be root to use some copy of busybox that you push (that would probably surprise most non-dev types greatly, but it's very true, try it) So it's actually possible to grab a copy of the ROM from the phone itself using tar or cp -a or whatever.

Furthermore when you're on the device, you can probe for the filesystem type needed for the mount in a generic way.

With all the tools on board to uncompress and mount and modify it... then it's clearly possible to change my rom modding script into an android script, skip all the kies mess, and where one could use it with nothing but the phone itself.

In a sense, going to that trouble defeats the point of my point which is people who have linux can just do this, but I think it's an amusing solution anyway.

Ok, maybe I'll need a new thread for this at some point.

---------- Post added at 02:14 PM ---------- Previous post was at 01:57 PM ----------

so actually these files are not world readable, and only thes:

/system/etc/bluetooth/audio.conf

/system/etc/bluetooth/auto_pairing.conf

/system/etc/bluetooth/input.conf

/system/etc/bluetooth/main.conf

/system/etc/bluetooth/network.conf

/system/etc/dbus.conf

but that is the generic flaw in reading roms off the phone itself. Modifying them on the phone however, is certainly fine for those without other linux like systems to work with.
[Galaxy S II Original Android Development] Phil3759:
But you will need root at some point to push files in /system

You can only do that through odin or stock recovery for the S2

Thank you for the info, I will look at it later maybe :good:
[Galaxy S II Original Android Development] appagom:
nah.. the point was to

a) possibly get a copy of the rom without dl'ing it somehow.

but more to

b) modify the ROM without installing tools or having linux, for the purpose still of ..

c) flashing it after modifying it... no push.

I modded my own rom to root it, but then of course I just flashed it, but flashing factoryfs only doesn't increment the counter as far as I know and can tell (there's no indication of it in my recovery mode).

Looks like (a) is not the best idea. The ability to do b is still nice though and especially useful for roms with filesystems you don't find ubuntu kernel support for too.
[Galaxy S II Original Android Development] CR5N:
Phil, a small thank you for the stock recovery root/unroot method on SII :)

4717076657477024A
[Galaxy S II Original Android Development] Phil3759:
Thanks for the thought :good:
[Galaxy S II Original Android Development] rez1:
Is it safe for me?

Is it safe for me to root my SGS2 Android 4.0.3 using the signed superSU & busybox?

Its completely stock, just did an update over the air & nothing else...

Please let me know if it is safe to use the first method or not?

Thanks...
[Galaxy S II Original Android Development] Phil3759:
sure, very safe
[Galaxy S II Original Android Development] aziz981:
Thanks a ton Phil.

I was on Indian ICS rom, and just followed the instructions start to finish.

Used the Linus Yang busybox and SuperSu installer and the temporary touch recovery.

Now I am rooted and very much on my dependable stock kernel without the hassles of odin and counters.

Appreciate your guide. Will recommend to others. !! :):cool:
[Galaxy S II Original Android Development] philippe734:
Great, please add an index of these method on the first post.
[Galaxy S II Original Android Development] drraptor:
I just need clarification for

Should I first flash CWM image ?

I'm using Galaxy S2 i9100, stock everything. Not rooted yet.
[Galaxy S II Original Android Development] Phil3759:
No need to flash cwm for the i9100 and n7000 phones
[Galaxy S II Original Android Development] drraptor:
So which method should I follow ? I don't want to increase custom counter and no yellow triangle ? Bit of a noob. So please spare me.
[Galaxy S II Original Android Development] Phil3759:
Flash supersu file in stock recovery as per instructions in Method 1
[Galaxy S II Original Android Development] drraptor:
I should just flash ?
[Galaxy S II Original Android Development] Phil3759:
Yes, in stock recovery, it's magic :laugh:

and safe...
[Galaxy S II Original Android Development] iRviNe48:
can it work on SGS3 international, the bootloader locked ? if not, can i use this method ?
[Galaxy S II Original Android Development] Phil3759:
You need to flash a compatible cwm first for method 1, then flash the root file

Triangle Away later to reset counter and triangle
[Galaxy S II Original Android Development] Sentario:
Would appear its for ICS and not gingerbread and says can flash on i9100 in stock 3e and most s2 in cwm

---------- Post added at 09:23 PM ---------- Previous post was at 09:21 PM ----------

Not going to chance the flash for fear of brick and no USB means permabrick
[Galaxy S II Original Android Development] Phil3759:
Did you read the title?

Be careful to do in the dev section to avoid bad surprises

By the way, this will not brick your phone at all on GB, it will just return a signature check failure and refuse to flash it
[Galaxy S II Original Android Development] Sentario:
What's the chance that there is a ICS firmware that will install from stock recovery 3e
[Galaxy S II Original Android Development] Phil3759:
?

Did not get your meaning

GB recovery is locked, not ICS one, that's it. JB recovery we still do not know
[Galaxy S II Original Android Development] LKML:
Is this method secure for my Device. It's said to have the Brick bug.
[Galaxy S II Original Android Development] Phil3759:
Method 1 is very safe to root, but you won't have a safe kernel after that. If you ever wipe in non stock recovery or flash some zip files, you could still brick

I uploaded for you the patched stock kernel:

http://xdaforums.com/showthread.php?p=33136238#post33136238
[Galaxy S II Original Android Development] Jrincon_v:
Hi friends I have a Note 7000 but i have some problem my device can´t read MicroSD but i want to root it, how i can do it?, Thanks in advance. :confused:
[Galaxy S II Original Android Development] Phil3759:
you are screwed
[Galaxy S II Original Android Development] phyxar:
all methode doesnt work on galaxy chat b5330

All Methode above doesnt work on my galaxy chat b5330, all zip does'nt pass signature verification
[Galaxy S II Original Android Development] Phil3759:
In that case, try other methods or a cwm if it exists for you phone
[Galaxy S II Original Android Development] phyxar:
The other methode is risky, since there is no dev release insecure kernel nor cwm recovery available for this phone
[Galaxy S II Original Android Development] Phil3759:
Sadly have no time to dig into it
[Galaxy S II Original Android Development] RovG:
Hi Phil3759,

When using your CWM 6.0.1.2 with a stock Samsung rom, I am unable to create an image.zip. It does however work with Siyah v5.0b2 and I suspect it would work with any kernel that has CWM embedded (probably because necessay supporting files exist in initramfs)

Time permitting of course, please will you consider providing a touch version of CWM 6.0.1.5. One that supports "Create Image Zip". You may need to include "minizip" because your 6.0.1.2 version fails at the point of creating the zip for me. I suspect that the same maybe true if one tries to create a dedupe backup (because dedupe maybe missing as well) although I haven't personally tested this yet. Including these supporting files should make your version truly "stand-alone".

TIA
[Galaxy S II Original Android Development] Phil3759:
Please try non touch 6.0.1.4 attached in post 1 and let me know. Temporary recovery thread has my philz-cwm6 temp semi touch recovery, soon updated to touch. Post in that temporary cwm6 thread please for discussing issues about cwm6. I will do my best to fix them
[Galaxy S II Original Android Development] Phil3759:
Thread link

http://xdaforums.com/showthread.php?p=30390595
[Galaxy S II Original Android Development] foccacia:
i m a little confused.

1. i m using I9100 n like to go for method 1 but within method 1, there is step 1 n 2. i do not fully understand when step 2 is required. n i do not know if busybox is required.

2. what is difference between stock recovery, your CWM Based Touch Recovery 6.0.1.4 and rom manager?

3. i like to root my I9100, do a nandroid backup of my stock rom before i proceed to flash custom roms. do i need a CWM to do it?

pls help
[Galaxy S II Original Android Development] Phil3759:
No need to cwm6 if you want root.

Just flash the root file.

If you do not know what is busybox, then you do not need it. Use root file without busybox unless you need it
[Galaxy S II Original Android Development] foccacia:
if i wanna flash custom roms like cm9 n AOKP?
[Galaxy S II Original Android Development] Phil3759:
No need to install busybox for that
[Galaxy S II Original Android Development] foccacia:
I meant if I need to flash custom roms, what can I use? If use odin, I need a pc to flash rom?
[Galaxy S II Original Android Development] foccacia:
i managed to root my I9100 but i like to do a nandroid backup. do i need CWM or just stock recovery will do?
[Galaxy S II Original Android Development] Phil3759:
CWM is needed

You'll be more confortable and safe in that case with one of my stock kernels with cwm6 bundled

http://xdaforums.com/showthread.php?t=1877270
[Galaxy S II Original Android Development] foccacia:
I tried using temp cwm6 n got my nandroid backup.

Sorry, I still noob to rooting, kernels n roms. If I flash ur kernel with cwm6 n when I flash other custom rom which comes with recommended kernel, will it be ok n will the cwm6 b lost after flashing other kernel?
[Galaxy S II Original Android Development] Phil3759:
Yes, you will loose my cwm6 and end up with what ever recovery (usually some stock or custom cwm version) the new kernels has
[Galaxy S II Original Android Development] foccacia:
so does it really matter? if i use ur cwm6 to do nandroid backup, can i b read by other version of cwm?
[Galaxy S II Original Android Development] shoey63:
If in doubt just restore with a Philz temp recovery.
[Galaxy S II Original Android Development] Phil3759:
It will be read by any cwm6 version for dedupe format

tar format is backword compatible with anterior cwm5 and probably 4
[Galaxy S II Original Android Development] foccacia:
oh, no wonder i saw the format was a little different. do i need to backup blobs folder into my pc or just the backup folder?
[Galaxy S II Original Android Development] avi1989:
Cannot Mount

I tried to follow the procedures listed here; I coped the linus superSU and CWM touch into my USB storage (I dont have an SD card) and opened up samsung recovery but when I click Apply Update from external storage; I get an error stating

E: failed to mount /sdcard (no such file or directory)

I'm at a loss here, Im using a fully stock GT-i9100 running 4.0.4. It has never had any custom roms installed and is fully stock

Can anyone help me out?
[Galaxy S II Original Android Development] Stileth:
You need SD card for this method. No other way around.

Odoslané z GT-I9100 cez Tapatalk 2
[Galaxy S II Original Android Development] Phil3759:
blobs contains actual backup in the new incremental format: you have to keep it, it contains the backup data. The new dup format adds speed and space gain with incremental backups. It is only compatible with cwm +6 versions

Inside cwm6, you can set default backup format to old style .tar, compatible with previous cwm versions

Hope it is now more clear
[Galaxy S II Original Android Development] fnair:
Has anyone with a newer Samsung phone (i. e. S3 or Note 2) rooted with method 1?

I figure that it won't work with the stock recovery, but has anyone done it with the temporary cwm?
[Galaxy S II Original Android Development] Phil3759:
You need first to flash a recovery to corresponding partition. No way without pc
[Galaxy S II Original Android Development] maddy19900:
Y dis mthod is not worKin for S duos(7562)....??.....What kind of Signed zip file is Required to Root dis phone thru Stock recovery mode..??? ..
[Galaxy S II Original Android Development] AngSanley:
I think samsung won't release the signer...
[Galaxy S II Original Android Development] sanenak.pouthena:
Thank you and a question.

First of all thank you for the detailed instructions. I installed the recommended Chainfire SU and everything worked perfectly. I only have one question. Can I flash the CWM now (for nandroid backup purposes mainly)?
[Galaxy S II Original Android Development] sanenak.pouthena:
I did it. It worked fine without any problems. Just follow the instructions exactly as they are described. Good luck.
[Galaxy S II Original Android Development] fnair:
Which phone do you have and which cwm did you use?
[Galaxy S II Original Android Development] Mustaaa:
Can I flash the cwm recovery version 6 over my cwm version 5 which I have now? I hev the brickbug chip, and I want to flash another ROM. But to be sure, can I flash the zip file of the non touch version 6 in CWM over my existing version 5?
[Galaxy S II Original Android Development] Phil3759:
Yes, it will work

You can, but, if your ROM update.zip have format commands + a non fixed binary_update, it will still brick your phone if you are not on a patched kernel

Look in my signature and get my PhilZ-cwm6 stock patched or any other custom kernel author says it is secure
[Galaxy S II Original Android Development] sanenak.pouthena:
Safe to flash JellyBam?

Is it safe to flash the Jelly Bam rom on a galaxy S2 rooted with the aforementioned method? I am asking because the device has the brick bug (checked with the GotBrickbug app). If it is safe, will the steps for doing so be:

Reboot into recovery mode

Flash CWM

Wipe data/factory reset

Wipe dalvik cache

Install JellyBam zip from internal SDCard

Many thanks in advance.
[Galaxy S II Original Android Development] Mustaaa:
My rom is now wanamlite 10.5, android 4.0.3 and have the stock kernel that comes with it. Thought the brick is only with 4.0.4 ROMs?

Can I flash the newest siyah kernel and then another rom, like paranoid? Or do I need to flash this one first: http://xdaforums.com/showthread.php?t=1877270