yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] kgp700:
OOPS!!

i was scared:eek:

i'm making korea galaxy s2 kernel

and i'm using samsung stock rom

today my kernel recovery change to CWM6 v6.0.1.2 (it was CWM 5.8.1.5) and Add efs_backup.sh

kernel flashing with odin, and boot to normal

boot complete but phone signal replaced prohibit symbol

and display baseband version 'Unknow'

i think EFS was brick

I'm revert to CWM5.8.1.5 and delete efs_backup.sh

and build kernel , flash kernel with odin

and boot

no problem now

it's clear

nice work 3g and phone

still i don't understand...

i think maybe caused by CWM 6 or efs_backup.sh

how about think?

i'm immediately backup EFS

--------------------------------------------------------------------------------

solved

i was tried change sbin/adbd change to stock

and etc folder deleted (my kernel use /sbin/busybox ln -s /misc /etc)

thats all...

no problem now..
[Galaxy S II Original Android Development] Phil3759:
It will not break your EFS

maybe a mount error because of something you did...
[Galaxy S II Original Android Development] Phil3759:
Update:

Just started with my own custom stock based kernels featuring CWM6 permanent recovery

Original thread and support here:

http://xdaforums.com/showthread.php?t=1877270
[Galaxy S II Original Android Development] harshana8181:
Thank you, I rooted my p6800 ICS with the help of your guide and the link by Astrix Ashburn "http://xdaforums.com/showthread.php?t=1849235"

Thank You,

Harshana
[Galaxy S II Original Android Development] stefan2519:
Thanks, great work!

This worked great on GT-P6800 ICS LP5 Rom.
[Galaxy S II Original Android Development] sos_sifou:
thanks for this great method, it was ported by astrix and I confirm that it is working on

stock Hong Kong honeycomb 3.2 galaxy tab 7.7 GT - P6800

best regards

Sifou

Galaxy Tab 7.7
[Galaxy S II Original Android Development] Granite1:
OK, first off awesome job on the utility! :good:

I've been reading through the thread, and I've not found my answer. I saw this was a universal root tool for ICS, now does this work across manufacturers, or is this for Sammy phones only?

Reason being I've been asked if this will work for ICS HTC phones like the Evo LTE?

My assumption is no, but I figured I'd better ask first. :)
[Galaxy S II Original Android Development] Phil3759:
It should work, yes, but...

You need to get a CWM from here probably: http://www.clockworkmod.com/rommanager

There's one for your phone, but in img format, so need a PC flash

and maybe replace binary-update in zip file. Not sure about HTC
[Galaxy S II Original Android Development] Granite1:
Wow, this is cool indeed. Thanks!!

Last I checked the CWM for the LTEvo was borked. It was corrupting the Misc. partition. We've moved over to TWRP pretty much exclusively. I should read up and see if they ever fixed it.

I'll get one of the HTC guru's to take a look and see if they can get everything figured out. I know just enough to make me extremely dangerous, if you know what I mean.

I appreciate it, thanks for sharing this with the community!! :good:
[Galaxy S II Original Android Development] Phil3759:
TWRP is as fine as CWM for flashing such zip files

But, yes, better be sure about the update-binary. Sometimes, small edit in edify code is also needed in updater-script

I do not use specific mount points, but generic ones. This should avoid most break issues
[Galaxy S II Original Android Development] m00ts:
Thanks very much! I can confirm this works with XWLPT, I flashed Directly from stock recovery and tested with root checker. Confirmed working! Thank you for this guide!
[Galaxy S II Original Android Development] dud3me:
Nvm
[Galaxy S II Original Android Development] Phil3759:
You can go with second one. If one app complains about busybox missing, use busybox alone installer zip later

No need to root to install any of these kernels. Just launch temporary cwm6 and instead of flash my root zip file, flash the kernel

This method comes with only fake, that is temporary cwm6. If you want permanent cwm6, look at my PhilZ-cwm6 kernel in signature

Siyah comes with a custom touch recovery. PA comes with CWM non touch recovery. So, each custom kernels will come with its recovery box

Flashing in odin a full rom + wipe data and cache will reset it to new

Also is it even possible to take a nandroid of the stock rom and then restore it w/o bricking the phone? Though this probably isn't even necessary since I can get back to stock with the firmware.

It's a custom kernel based on stock one, just adding very small changes + CWM6 permanent, not teh fae temporary

Files attached here are not roms, only root scripts and files. Seems you are confusing ROM, kernel and update zip files
[Galaxy S II Original Android Development] dud3me:
Thanks for the quick reply!

Edit: Now rooted. So I went ahead and rooted using the first method and the first root file (w/o busybox) and installed PA and siyah. Thanks a lot! This was surprisingly do ti when I actually decided to go through with it. :)
[Galaxy S II Original Android Development] m00ts:
Hi Phil, I just rooted via the flash from stock recovery method on 4.04 XWLPT. Is it safe to flash Siyah 4.1.5 from temporary CWM 4.X? If I have a problem flashing the kernel what can I do since I can't restore without bricking as I have affected eMMC chip, Thanks. :)
[Galaxy S II Original Android Development] Phil3759:
Flash a safe 4.0.3 in odin before or my PhilZ-cwm6 kernel in signature. It is safe for wipe.
[Galaxy S II Original Android Development] Phil3759:
Update post 1:

Request: if someone know about a kernel using cwm6 6.0.1.3 touch or the source changes for touch cwm6, let me know please
[Galaxy S II Original Android Development] ducy1:
Is it possible to root Galaxy S3 by this method? (e.g., 1st method)?
[Galaxy S II Original Android Development] Phil3759:
Yes, but you need a cwm since stock recovery in S3 is locked

So, odin is needed to first flash a cwm to recovery partition.
[Galaxy S II Original Android Development] nick61:
Hi,

I've succeeded to root my i9100 with the universal method described here (thank you Phil):

I would like to know several things:

1. Which one of the following methods is the "cleanest" one for unrooting, if I need to use warranty:

a. with the unroot file posted here

b. with odin and downloaded original firmware, with phone started in download mode

c. with Kies "emergency recover" option

2. If there will be an update for the original firmware, do I need to unroot first to aply that update ?

Thanks a lot for your support,
[Galaxy S II Original Android Development] Phil3759:
1b is best for warranty

2: no, but often you will loose root as new fw comes with flashing a /system partition which removes root files. So, only apply root file again
[Galaxy S II Original Android Development] chx:
It would be great to find a way to digitally sign the package for flashing in S3 straight from the stock recovery as we do on the S2. Any chances of doing that?
[Galaxy S II Original Android Development] Phil3759:
probably 0 chances
[Galaxy S II Original Android Development] Matt_7:
Hi Phil, when I first got my phones about a week ago I didn't exactly 100% sure what I was doing, but a member on our forum provided a link to your thread here and I managed to root both my phones:cool:.

As both my phones are new with no personal data on them, I was in a testing mode and I installed:

1) Root_SuperSU.0.95.Only-signed.zip (using SD card)

2) Busybox from Playstore

3) Galaxy s unlock by helroz from Playstore

I subsequently used SuperSU to uninstall/remove Busybox, Galaxy s unlock and then also uninstall/remove SuperSU using the built in uninstall/remove function.

Please help me with these questions when you have the time and thanks in advance.

1) Even with the uninstall/removing all three of the above, both my phones are still unlock (meaning could still use/accept different SIMs/carriers), is this supposed to be this way?

2) Using SuperSU menu to remove Busybox, Galaxy s unlock and subsequently using the built in function to remove SuperSU itself, would there be any traces or leftover files left?

3) Is there any harm or negative effects for reinstalling Root_SuperSU?

4) If I'm guessing correctly, the Root_SuperSU doesn't need Busybox to root, and the reason for installing Busybox is for Galaxy s unlock by helroz to unlock my phones, right?

5) What is the difference between Root_SuperSU.0.95.Only-signed.zip and Root_SuperSU.0.96.Only-signed.zip

6) What is the difference between Busybox from Playstore "Stephen (Stericson)" and the one included in Root_SuperSU.0.96-Busybox.1.20.2-S2-signed.zip (Linus Yang)

Best regards.
[Galaxy S II Original Android Development] Phil3759:
1) sorry, never played with locked phones, but I suppose it is the normal behavior once unlocked

2) SuperSU menu removes only permission settings, not the app.

However, it was a very bad idea to install busybox from a market installer, they put tons of crap in your /system

3) installing the root zip in this thread will not do any harm, basically, you just copy 2 files to /system

4) busybox has nothing to do with root. It is a bunch of linux commands needed by many programs in fact. You would be better installing the busybox in the post 1 as it is a clean install that you can completely undo using my Busybox Uninstaller script v1.0 (see signature)

5) SuperSU 0.96 is the newer binary/app. If you install the 0.95, you can just update in market

6)Stephen Market version comes with a market uninstaller that I would really not recommand at all. Otherwise, both builds do the same but Linus Yang comes with significant more commands. Depending on the apps you use and the scripts you need, I advise the Linus Yang version
[Galaxy S II Original Android Development] Matt_7:
Thanks for the quick reply, you are great!:good:

1) OK, so now I'll start from fresh and using Root_SuperSU.0.96-Busybox.1.20.2-S2-signed.zip, but before that how do I clean up Busybox from Playstore "Stephen (Stericson) or delete/remove all traces of previously installed applications?

or do I need to use Odin 1.85 and I9100MUGLD3_I9100MBMCLD3_I9100MXXLD3_HOME.tar.md5 to restore my phones (clean up the mess)?

2) Just in case for future sake, is there anything like "Galaxy s unlock by helroz from Playstore" that I can download here and NOT downloading/installing anything from Playstore in the future.

Thanks again.
[Galaxy S II Original Android Development] Phil3759:
1) Try the busybox Uninstaller 1.0, some people reported success restoring from phone issues after the market installer

Of course, an odin flash will clean things 100%

2) sorry, really do not know about these unlockers, but, when you need busybox, just install it from here
[Galaxy S II Original Android Development] Matt_7:
Thanks and have a great day!
[Galaxy S II Original Android Development] Phil3759:
Updated post 1 with newest CWM 6.0.1.4 non touch version
[Galaxy S II Original Android Development] zero_3:
Just want to say thank you phil3759 for this wonderful rooting method. I was able to flash cm 9 and other custom roms and kernels using cwm and my counter never increased and no yellow triangle. Best part of it I can always go back to stock and unroot for warranty puposes.
[Galaxy S II Original Android Development] vigaruhul:
I'm sorry, but i can't download unroot superuser ,maybe my mistake or the link can't be accessed?
[Galaxy S II Original Android Development] Phil3759:
Just tested and the attachment works perfectly
[Galaxy S II Original Android Development] Phil3759:
Important notice for people that downloaded previous non touch versions 6.0.1.3 and 6.0.1.4 from post 1

20 Sep 2012

: Update non touch version to 6.0.1.4 ** Recommanded Update from previous 6.0.1.4 attached here **

People using my previous non touch versions 6.0.1.3 and 6.0.1.4 are strongly advised to move to this updated 6.0.1.4

Previous version was not a static binary and could behave unexpectedly under some circumstances

Actual 6.0.1.2 touch and non touch are fine to use

I removed previous 6.0.1.3 and 6.0.1.4 files to avoid confusion
[Galaxy S II Original Android Development] aktp-iciook:
Thanks a lot "Phil3759" :) I have been searching for this latest Root method and it finally works. Great job.

Just to confirm that "Root_SuperSU.0.96-Busybox.1.20.2-S2-signed.zip" works perfectly fine with my Samsung Galaxy S2 (I9100T).

Please keep up your great work mate :)

Cheers,

Milk
[Galaxy S II Original Android Development] Kevin.Ranara:
This worked for me, thanks. :)
[Galaxy S II Original Android Development] schlex2010:
Does not work for Acer Iconia Tab A210 :(
[Galaxy S II Original Android Development] s2bal:
please help

Hello

Thank you very much for such useful thread. Im very new to this kind of stuff. I got s2 on official 4.0.4. (Baseband version I9100XXLQ6, kernal version XWLPT).

I see so many issues with current version so thinking neutrino rom. As part of it used below procedure to root the phone.

1) downloaded Root_SuperSU.0.96.Only-signed.zip from this thread.

2) copied above file to sd card

3) rebooted to recovery (vol up + home + power) and choose upgrade from externalsdcard and install above file.

4) reboot

Now i see supersu.

Like i said above, want to flush neutrino rom. One of the instruction says

3. Select "wipe data" & "wipe cache partition" & "advanced and "Wipe Dalvik cache".*

I cant see advaced option in recover mode. Please advice what i need to do.

Thanks in advance.
[Galaxy S II Original Android Development] Phil3759:
XWLPT is an unsafe kernel. Before wiping or using update.zip with format commands (can come in the ROM you flash), flash a safe kernel:

PhilZ-cwm6 (see my signature), CF-Root. Siyah...
[Galaxy S II Original Android Development] s2bal:
Wow you are fantastic. Such a quick reply. Can you kindly answer following questions aswell please.

1. Do I need to unroot the phone before I follow the procedure you mentioned. Please let me know the instructions if I need to.

2. Can I just flush the rom (neutrino) I wanted after following the procedure you mentioned above.

Thanks in advance.
[Galaxy S II Original Android Development] Phil3759:
1- no need

2- yes, you can just flash what you like from safe kernels. My bad, cf-root is not patched, so not safe if format commands in update.zip. Use one of the other 2 and flash your new rom
[Galaxy S II Original Android Development] s2bal:
Thanks for response. I am still figuring out which procedure to use from the link you mentioned. I can't see procedure for the kernal version i got. Any help is much appreciated.
[Galaxy S II Original Android Development] Phil3759:
You are on LPT stock (unsafe kernel)

Flash PhilZ-cwm6 from this link:

http://xdaforums.com/showthread.php?t=1877270

you will be on stock patched (safe) LPT

Now, boot into recovery and flash your custom ROM
[Galaxy S II Original Android Development] s2bal:
Thanks for reply.

Below is the procedure i am planning to follow to root.. Can you please confirm

1. Download attached Philz-cwm6-CWMManager-v1.1.zip file (at bottom of this post)

2. Flash it in recovery

3. After reboot, you will have permanent support for CWMManager

4. Big thanks and donations go to Chainfire for this app

5. To uninstall it, you can flash the Philz-cwm6-CWMManager-v1.1-Uninstall.zip file. You can also manually remove CWMManager app and delete the CF-CWMManager-PhilZ file from your init.d folder (/system/etc/init.d)
[Galaxy S II Original Android Development] Phil3759:
You are completely wrong

Before flashing anything, please, read completely the 6 firsts posts here:

http://xdaforums.com/showthread.php?t=1877270

And the first post from this thread, METHOD1

After that, you can flash safely. Continuing this way without fully reading will brick your phone and I will not responsible...
[Galaxy S II Original Android Development] s2bal:
Thank you very much for your help. Much appreciated . I will read those threads.
[Galaxy S II Original Android Development] s2bal:
I read the other thread few times. I am thinking of below steps i need to perform.

1. Download xxx-signed.zip kernel matching your ROM

2. Put the previously downloaded xxx-signed.zip file on your external sd card

3. Boot into stock recovery (volume up+home+power)

4. Select "apply update from external storage".

5. Now select the xxx-signed.zip file you copied in previous step

6. You are rooted + new PhilZ-cwm6 kernel with CWM6

If you think i am correct, then i will give it a try, Only question is Which xxx-signed.zip i shoud use. Like i mentioned i am on XWLPT, but can't find any kernel for this.

If you think i am still worng, i would give up. :crying: May be i am not good with these kind of things.

Thanks for all your support. Much appriciated. Hats off for your cracking job.

---------- Post added at 10:57 AM ---------- Previous post was at 10:47 AM ----------

Apologies, found kernal for XWLPT. Will follow those steps if you think i am correct. thanks.
[Galaxy S II Original Android Development] Phil3759:
Those are the exact right steps, yes :)
[Galaxy S II Original Android Development] s2bal:
:good:

Great thanks for confirming. Will do tonight and let you know the outcome. Can't wait.
[Galaxy S II Original Android Development] pasanjay:
I used the first method and rooted my s2 running on stock 4.04 (XXLQ6). Can I install custom Roms using the temp recovery?? or should I flash a kernal which has permanent recovery?? plz help
[Galaxy S II Original Android Development] s2bal:
A big thanks

Rooting is successful. :cool: Thank you very much. :good:
[Galaxy S II Original Android Development] Phil3759:
There is a big debate here

But, it seems, only wipe operations are safe in CWM6+stock

All recoveries are suspected to be vulnerable to a brick bug issued by format commands in update.zip with bad binary-update

To sum it: to install a custom ROM, it is strongly advised to flash a safe kernel, the only 100% proved protection

Look at PhilT-cwm6 kernel in my signature for that
[Galaxy S II Original Android Development] keaboard-billy:
Very cool thing!

I've rooted today my S2 GT-I9100 with the recommended method.

First I've removed the old version of a installed BusyBox with the "Busy_Box_Uninstaller_v1.0-signed.zip".

Then I rebooted the S2.

Again I've started the recovery mode and then I used the "Root_SuperSU.0.96-Busybox.1.20.2-S2-signed.zip"and I rebooted once more.

Great! The S2 is rooted now :)

But I haven't seen the icon for the BusyBox app (???)... Well, I've downloaded and installed it from the play store again. And now it's all complete :D :D :D.

Just for information:

> Modellnummer: GT-I9100

> Android-Version: 4.0.4

> Basisbandversion: I9100XXLQ6

> Kernel-Version: 3.0.15-1056084dpi@DELL168#3 SMP PREEMPT Wed Aug 22 22:55:24 KST 2012

> Buildnummer: IMM76D.XWLPW

Well' done work - big THANKS to the developer!

Greetz,

Billy
[Galaxy S II Original Android Development] Phil3759:
Big mistake...

Busybox is not an application, it does not have icon. It is a command interpreter. Market apps will make it even crappier. They install tons of buggy stuff. Basically, they are just an app which is supposed to push the binary into your device. But, many try to compile, compare, keep different versions...

1- Uninstall market app

2- After that run my uninstaller

3- Finally reapply busybox only installer from post 1, no need to the root file again
[Galaxy S II Original Android Development] keaboard-billy:
Hi Phil3759,

thank you for your very quick response :) .

I did all the steps you've described in your last post (I used the file "Root_Busybox_1.20.2_Only_(No_SuperSU)-S2-Update3-signed.zip" - seems to be the correct one, isn't it?).

Finally I rebooted my device and it seems that it runs very well, so far :D.

Greetz,

Billy
[Galaxy S II Original Android Development] Phil3759:
yes, that's the correct file
[Galaxy S II Original Android Development] viewedit:
I used method one now can I flash a custom ROM

If I boot to cwm which you have recommended I should be able to flash a custom ROM. Am I right? If no then how can I?

---------- Post added at 06:01 PM ---------- Previous post was at 05:32 PM ----------

Its OK I get the answer on the previous page.
[Galaxy S II Original Android Development] appagom:
You forgot possibly the most obvious method..

rip your rom from kies and just copy su into the ROM (/bin or /xbin) before flashing it.

It does require more skill than using a zip but it's more universal except for the part about how to get a copy of your stock ROM.

To do it, you need to untar the rom and mount factoryfs.img as a loop mount on a linux system. On some roms.. you need to decompress the factoryfs.img first, adn recomperss but the tool is around here. For anyone with basic linux skills, it takes a couple of minutes.

---------- Post added at 06:34 AM ---------- Previous post was at 06:24 AM ----------

Once you're at it you can write a quick script to also copy in SuperSu, busybox, titanium backup if you want, remove that annoying social networking app you hate, add your favorite modded calendar apk etc.. all in one shot.
[Galaxy S II Original Android Development] Phil3759:
Thanks for the input. That's the way prerooted roms work. But, if i am not wrong, you will need a different tool for each phone and android version
[Galaxy S II Original Android Development] appagom:
Yes and no... for figuring out how to get your rom in the first place, maybe, but there are usually torrents available within hours of release for that anyway. As for the rest.. the only thing I know of that has changed is the filesystem type used and the fact that now it's compressed (sparse) on at least some ROMS.

In the end getting root just requires one file on the rom granting shell permissions. SuperSu's su binary is a good one since it is unprotected for adb access. You can even isntall the apk later if you want. But getting the rom and copying a file into it is to me the most universal way to get well.. get a file into a ROM. All other ways depend not just on how android files are laid out, but on how they actually function.

The method of

tar -xf ROM.tar

possibly uncompress the factoryfs.img in some way

mkdir /mnt/rommount

mount -o loop -t somefilesystem factoryfs-uncompressed.img /mnt/rommount

cp su /mnt/rommount/bin

chown 0.0 /mnt/rommount/bin/su

chmod 6755 /mnt/rommount/bin/su

umount /mnt/rommount

modify whatever else you want

possibly recompress factoryfs-uncompressed.img -o mynewfactorfyfs.img

retar if you use odin, or not if you use heimdall.

flash

...

will basically stay the same so long as ROM flashing is possible. Extracting the rom files and copying it there will always work on any phone.

The only questions are a) how to get the rom and b) how to uncompress and recompress the file. Since android must be able to read and write to the /system directory, that should never be complicated or secret.

For how to uncompress, it's here:

http://xdaforums.com/showthread.php?t=1081239

If your rom uses a yaffs2 filesystem for /system, you might need to install support for that filesystem in your linux first but this doesn't sound scary to most linux users I think. As for knowing what fs it is, without needing root, in adb:

cat /proc/mounts

I know your basic one-click windows gui user doesn't want to do this. On the other hand, for your basic linux user, once you write those commands out once.. they keep working and you can do more and more with it... like I added a loop to go through copying and setting perms on any apks and binaries I toss into my modding directories.

Most of these other methods, certainly mobile odin, are going to have issues from time to time too that require you to wait on the dev (which was said to be a main point of the thread). If you have some basic skills and no android knowledge other than what I just told you, there's a good chance you can figure this out without waiting or at least be part of the discussion.

It's your thread, but to me this method is fundamental enough to deserve a mention, especially since the premise is to not wait on someone else to root the rom for you.
[Galaxy S II Original Android Development] :
I've got the sgs2 gt i9100

Android ics 4.0.3

I9100dxlpa baseband

Kernel 3.0.15

Which root do I use? I'm a noob. Please forgive me.

sent by me