yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] gpgorbosjr:
Coming from HTC/Motorola phones primarily the development for this phone has confused me a bit. Those phones used to get a normal root method pretty soon after release without having to worry about messing around the kernal.

Is there going to be a day where you can just root it and leave the kernal alone or is the kernal/root thing exclusive to Samsung phones?
[Samsung Epic 4G Touch] Will of fire:
Whsn i was on att i would use superoneclick. I too was wondering this.
[Samsung Epic 4G Touch] bman55:
We need this.
[Samsung Epic 4G Touch] stangdriverdoug:
The root for this phone is as easy as it gets. I just rooted my friends inspire and while it is only one click the process it goes through us way more complex.

Samsung Galaxy S II
[Samsung Epic 4G Touch] paranoid android85:
Yeah I have to say this was a very easy process to root coming from an evo4g
[Samsung Epic 4G Touch] edisonalvarez:
I think he meant the fact that ur using the kernel to get to root instaed the more conventional root method we are used to seeing on devices like htc and so on. It is pretty strange the fact u flash a kernel and then flash to get root its typically gain root then flash somethingy. Or at least thats what my noob ass is used to lol
[Samsung Epic 4G Touch] gpgorbosjr:
All the root methods are simple to execute for someone who can read. But I am referring to the fact (as edison said) that you have to flash a new kernal to achieve root. I'm personally waiting for a more typical root method before I root.

Not that I don't appreciate/love the dev community but I like a COMPLETE stock setup with root before I go messing around experimenting because I don't necessarily trust EVERY dev and don't have the technical expertise to fix stuff myself.
[Samsung Epic 4G Touch] stefan.buddle:
Only solution is to just wait, I don't think many would be working on another root method because this one isn't complex, is noob friendly and works 100% I don't see any pressing reason for another method
[Samsung Epic 4G Touch] stangdriverdoug:
Yup I hear ya. You can always root then odin bubbys pulled stock kernel for a complete stock root. It's not one click but it's close. Only draw back it there is no recovery.

Samsung Galaxy S II
[Samsung Epic 4G Touch] nabbed:
Conventional root?

What is that?
[Samsung Epic 4G Touch] squshy 7:
Umm...there is no other way? There's no exploit anymore guys...it's either flash a rooted kernel or flash a rooted /system. And that's easy as hell
[Samsung Epic 4G Touch] dayv:
Unless you can get hold of Samsung's signing keys for creating a signed update.zip or find a new exploit (which would have to be fixed eventually because exploits are essentially security holes) you are pretty much stuck with the current methods.
[Samsung Epic 4G Touch] JohnCorleone:
Wow,so no more one click roost with cwm then we can flash any kernel and be good? Shizznit, one click was good stuff
[Samsung Epic 4G Touch] ipetloudog:
I miss z4root. Im not a newber but I know I like my simplicity redundantly simple.

Sent from my SPH-D710 Galaxy S II [suck it]
[Samsung Epic 4G Touch] hayabusa1300cc:
Honestly odin is pretty the one click we need.

.: sent from my Samsung Galaxy S II Epic 4G Touch :.
[Samsung Epic 4G Touch] shaneleelevin:
Dude samsung released the source and practically handed us root on a silver platter
[Samsung Epic 4G Touch] Epix4G:
Why should anyone find a exploit to root the phone when the bootloader

Is open and allows you to root much easier....google keeps closing holes in software making it harder and harder to root ...its not a htc where they s-off the phone .....this will probably be the only way to root because there is no reason to find another
[Samsung Epic 4G Touch] ilostmypistons:
What could be easier than putting this in Odin http://xdaforums.com/showthread.php?t=1282415 and hitting the start button
[Samsung Epic 4G Touch] satur9ine:
I think the point people are trying to make here is that they wish there was a way to have root and recovery and remain bone stock. So far there is no way to do this. Alot of people don't want to flash a custom kernel at this point because of all the problems people are reporting. Myself included. I am still stock and won't root until devs get this stuff sorted. Maybe koush will figure it out...
[Samsung Epic 4G Touch] manekineko:
It's not really clear from the titles in the development section, but there is a way to root without flashing a kernel.

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

That's a stock system image, simply modified to include root. No kernel at all.
[Samsung Epic 4G Touch] Tahde:
Exactly.

The other methods of gaining root along with recovery as easy and its great that there are options. But I'm with some of the others. I (personally) am not ready to mess with the kernel yet. No biggie/rush to root yet (for me atleast), but if there was root for this method, it would be nice. Totally understandable why there isnt and if I really need to flash that bad, I'll just use one of the methods now.
[Samsung Epic 4G Touch] gpgorbosjr:
Last I checked even the "stock" kernal available was not actually the "stock" kernal.....

And, yes, the point is: root without messing with the kernal.
[Samsung Epic 4G Touch] naerok:
use odin to flash the stock odexed with root + busybox.

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

It does not touch the kernel, so it will be the exact same way you have your phone except with superuser + busybox. You don't even have to wipe anything.
[Samsung Epic 4G Touch] cidica:
How was the evo hard? (mind you I rooted my first one like a week ago) from what I used (revolutionary) it's was a damn cake walk ended up doing 4 more phones with it the next day no issues.
[Samsung Epic 4G Touch] naerok:
The newer one click methods are definitely cake walk as you say.

This is the method I used when the Evo first came out, before one click methods were available.

[TUTORIAL] How To Root The HTC EVO ~ Part-1 \0/ http://xdaforums.com/showthread.php?t=690762

[TUTORIAL] How To Unlock Nand Protection ~ Part-2 [Gaining RW Access/Full Root] http://xdaforums.com/showthread.php?t=701835

It's not rocket science, but definitely a step above one click methods.
[Samsung Epic 4G Touch] cidica:
Ah ok yeah I saw those while I was looking for the info to root my friends evo. I've done that to a point before with my old MyTouch Slide 3G with T-Mobile def not rocket science but yeah takes a bit longer.
[Samsung Epic 4G Touch] ptfdmedic:
I'm not sure why we are still using rooted kernels? All you have to do is Odin a kernel with CW recovery and flash a prerooted ROM.

I get why we used Odin at first but not now. Odin is a very simple process but user error can be fatal. I bricked my first Touch using Odin. Totally my fault but it happens.

Once your rooted it doesn't matter because as long as you flash a rooted ROM, you'll be fine.
[Samsung Epic 4G Touch] eyecon82:
How about a root that doesn't increase LOS? Where can I find that?
[Samsung Epic 4G Touch] ungovernable1977:
I love Odin... except how it defaults to the last folder for PDA... almost flashed an OG epic GB leak on my touch :eek: :p Id love to see a stripped out version of Odin that eliminates the no-no options... make it near impossible to botch...

So to get this straight, your ROM for example, gains root through /system and doesn't necessarily touch the kernel (i know you use custom kernels, but the act of gaining root, is it through /system like mentioned above)? I think people are just worried because the old exploits altered the exact system that was already on their phone, and are skeptical of 'stock kernels'... I know most of the devs who put these out from the OG epic, and I trust them, but we have a lot of sammy noobs here... (no disrespect HTC/Moto converts!)

---------- Post added at 09:14 PM ---------- Previous post was at 09:07 PM ----------

im pretty sure thats highest priority.

But I wonder why it SEEMS that even with a stock kernel+root, the LoS increases... make me break out my tinfoil hat... just seems like a little easter egg for rooting... not trying to stir up conspiracy theories, but I think someone needs to explain how root is obtained in one of the main LoS threads, and try to narrow down why a supposedly stock kernel somehow exacerbates this issue... maybe tied to the yellow triangle? Its just confusing...
[Samsung Epic 4G Touch] Epix4G:
Yes revolutionary is really easy you do know it took like 2 months to find a exploit and to get it done....its not overnight like some think
[Samsung Epic 4G Touch] Overstew:
Android has been updating its OS quite a bit as of late and these updates patch previous exploits. So, since all previous exploits for root has been patched, we simply use Odin to flash a rooted kernel instead of spending valuable time searching for a new exploit.
[Samsung Epic 4G Touch] AbsolutZeroGI:
Don't take this the wrong way, I'm not trying to flame at all.

But what do you mean by "more conventional root"? All root methods basically do the same thing: use a security exploit to gain administrative (a.k.a. root) access to our phones which allows us to read AND write files to otherwise protected partitions.

From what I understand here, the ability to do just this can be implemented into either a kernel or a rom. In order to get you can:

Flash a kernel w/root and recovery

or

Flash a kernel with recovery, then either flash root or a rooted rom in recovery.

To unroot? Flash a stock rom tar in odin + factory reset (which we have readily available). This is also the same method techs use to restore phones to stock.

The conventional method I'm used to (as a prior htc user):

Use a typically noob neutral (meaning not friendly or unfriendly) command prompt/terminal emulator process to break the security in the bootloader...sometimes it can flash a recovery but fails 35-40% of the time.

If it fails, find and flash a recovery in bootloader.

Then flash a rooted rom

Flashing kernels optional.

To unroot? Find the stock rom (which is sometimes harder than you think), often called an RUU and find the "unroot" tool made by the people who made the software that rooted your phone to begin with. Flash the unroot tool over and over again until your bootloader says "s-off", then flash the RUU in the bootloader and pray you downloaded the most up-to-date one.

In a venn diagram, our current root method would be at the intersection of "easier to root than most", "less unstable than some, more stable than others" and "easier to unroot than most".

I can understand the uneasiness of it. When i rooted my phone I was like "really...that's it?" but, frankly, i've never seen a phone with such a clean process. In one click you've got recovery. another and you've got root. Badda bing badda boom.

Additionally, and I promise I'm not flaming, we know exactly what we're doing to our phones. I know the Revolutionary people keep their root methods a secret so HTC doesn't patch it, but does anyone actually know what "zerging root" means?

Now, I'm going to close by saying that I began this post blatantly saying that I don't understand what's going on here lol. So if I missed something please feel free to let me know with the proper amount of noob flaming (but not too much, please :P ).

TL;DR

As far as I can tell, we have a simple process that gives us root + recovery and Odin carries the same dangers as other root methods. So I don't see the problem.
[Samsung Epic 4G Touch] Epix4G:
No the real problem is that the person doing the rooting and recovery is not .....unrevoked or some other that came from htc .....it just hits me as some here just don't trust the devs .....
[Samsung Epic 4G Touch] ptfdmedic:
Great to see you ;-)

That's what sorta happened to me. Only one used the wrong Pit and bricked my 3 hour old Touch.

I love odin and I'm glad we have it. I didn't mean to insinuate otherwise. I just prefer that for emergencies.
[Samsung Epic 4G Touch] kingsway8605:
I think you have a misunderstanding of what root is. Any root is an exploit, similar to the exploits trojans use. It is all about what the exploit does after it is executed that separates the good from the bad. Different phones have different exploits.

If you mean when is it going to be possible to have su permissions with completely stock software and kernel, well it already is. Check the dev section.
[Samsung Epic 4G Touch] bluefire808:
After having a htc eris and htc evo 4g rooting ET4g with odin is as easy as peeing in the shower :)
[Samsung Epic 4G Touch] satur9ine:
You are correct about root, but not CWM recovery. Half the point of root is having a custom recovery so that you can backup and flash to your hearts content. We don't have that on stock kernel with this phone because of the way recovery is baked in with kernel.
[Samsung Epic 4G Touch] mkasick:
I understand folks's reservations about installing custom kernels. It's not so much the fault of kernel developers, but the fact that Samsung didn't release EG30 source code. What they released has subsequent modifications that may or may not be relevant to the issues that folks are seeing with custom kernels.

In any event, it's certainly possible to make a kernel that's totally stock code wise, but with an initramfs modified to use test-keys. This means stock kernel, stock recovery, but still can flash test-keys signed update.zips (e.g., superuser) and can even boot a "fake-flash" ClockworkMod, where CWM itself is an update.zip that's applied in, and (temporarily) replaces stock recovery at runtime.

I can make such a kernel if folks would like. I don't have an E4GT to test though. As for a fake-flash ClockworkMod, I don't know if Koush still prefers that method on SGS devices or not. I don't use CWM myself, so I'm less familiar with recent developments with it.

---------- Post added at 09:04 PM ---------- Previous post was at 08:50 PM ----------

There's actually two major methods to "rooting" a phone.

The first is an exploit of a (local) root vulnerability. If such a vulnerability exists on a device, it's a convenient means to get root privileges. And as you correctly say, it's convenient for "us" in order to grant root privileges to applications we want to use. It's also convenient to malware authors, who can use them to silently install malware without our knowledge. In general root vulnerabilities are not preferred, since we don't like to have compromised devices. However they're a necessary evil on locked devices (most Motorola handsets, some older HTC ones, etc.)

The second method for rooting a phone is to flash modified software, be it a kernel, recovery imagine, or system ROM, that provides root privileges. This isn't taking advantage of an exploit, but is using an official or "blessed" mechanism for making software modifactions to the device. This can only be done on unlocked or unlockable phones. This includes Google-branded (Nexus) devices, recent HTC devices that they provide an official unlock mechanism for, and all Samsung handsets.

Furthermore, source-based Android ROMs have always had an official mechanism for providing root capability. Engineering ROMs include development tools and adbd runs with root permissions ("adb shell" run as root), while User Debug ROMs allow the option of restarting adbd with root permissions with "adb root"--see "adb help" for a description of that option.

It's just User Release ROMs that don't support root capabilities out of the box, which is reasonable poicy since developers and folks who want to take advantage of them are capable and willing of making the necessary software modificatoins to support such. But there's no exploit here, it's intentional.
[Samsung Epic 4G Touch] satur9ine:
@mkasik The fake flash CWM recovery is what was used for the US SGS Captivate. I would love to see this for this phone so that we could retain a completely stock kernel. I had heard somewhere that this wouldn't be possible since no one has the keys to make a signed update.zip file.
[Samsung Epic 4G Touch] mkasick:
Right, it won't work with a completely stock kernel. You have to take the kernel, extract the initramfs, replace the signing public key with a well known one (e.g., test-keys from AOSP), package the initramfs back up and slip it back in the kernel image.

So yes, it involves flashing a non-stock kernel image. However, the kernel itself (that is, the code) is completely unmodified/stock, as is the remainder of the initramfs contents.
[Samsung Epic 4G Touch] chris41g:
I tried that, but no matter what I did, I could not get the repacked kernel to boot... although I don't have the phone.. I do suspect it has something to do with how they are signing the kernels now...
[Samsung Epic 4G Touch] satur9ine:
Okay now this convo is getting exciting! I really believe this is the direction we need to go to stay as close to stock as possible. Would love to see the keys issue resolved!
[Samsung Epic 4G Touch] rfeagan:
I took plunge, I did this 2 days ago, works perfect. Thanks!
[Samsung Epic 4G Touch] mkasick:
Is there information on how they're signing kernels? I'll try to look into it when I can, TODO list is getting rather long.

In any event, if it's just the bootloader checking for a kernel signature at the end of the zImage, two things can be done to resolve this:

1. Strip the signature off the zImage, which would hopefully make the bootloader recognize it as an unsigned/custom kernel, even though the code is actually the same.

2. Pack "Image" with the decompressor from the open source release. I've been doing this with kexec stuff. Basically the zImage decompressor code that wraps the gziped kernel would come from the open source release. But that's fine, since it's probably unmodified from EG30 (which I can confirm), and the decompressor is abandoned on boot anyways, so there's no long-term state. The actual kernel code is still unmodified from stock.

If someone is willing to test, I might be able to get to this tomorrow (Saturday).
[Samsung Epic 4G Touch] Devi0124:
LoStkernel
[Samsung Epic 4G Touch] Scaplet:
Same. I'm still stock and haven't had one problem with my phone, no LOS issues, nothing. Seems as if even those flashing 'stock' kernals are having problems.
[Samsung Epic 4G Touch] rfeagan:
Zero LOS issues here... Yet... Knocks wood.
[Samsung Epic 4G Touch] xlGmanlx:
from what i read and understand, this makes the most sense. But i have no clue on what the level of effort is for that to happen!!
[Samsung Epic 4G Touch] zelduy:
Here here... I also still in stock.. this is the only phone that makes me think twice just to root.. so far no LoS or anything... I'l just play with the stock for another month then..
[Galaxy S II Android Development] rizdroid:
Yes, no custom binary, no triangle! :)

In Brazilian mod:

Brazilian NTP server for faster GPS fix

Brazilian CSCs (ZTA, ZTM, ZTO & ZVV)

BusyBox v1.19

GTalk A/V

In Portuguese mod:

Portuguese NTP server for faster GPS fix

Stock CSC (OPT)

BusyBox v1.19

GTalk A/V

How to:

Download the file for your fw version

Unzip it

Run ODIN

Click on PDA

Select the unzipped file (xxxxxx.tar)

Click on Start

Done!

Files

ZTA-KI4 (Claro, Brazil)

ZTM-KH3 (Tim, Brazil)

ZTO-KI1 (Unbranded/Oi, Brazil)

ZVV-KI2 (Vivo, Brazil)

OPT-KI4 (Optimus, Portugal)

Thanks

jazzor for this thread, where I learned how to play w/ Android img files

Chainfire for his CF-Root, which I used to play with all this

ChainsDD for his Superuser

SOURCE: http://www.portalandroid.org/comunidade/viewtopic.php?f=84&t=13991&p=110610#p110610

PS - if you think this info is useful, click on Thanks ;)
[Galaxy S II Android Development] rizdroid:
XWKI8

-- Root w/o increasing custom counter & triangle

In this mod:

BusyBox v1.19

GTalk A/V

European NTP server for faster GPS fix

Stock CSCs (AUT, COS, CYO, DNF, EUR, NEE, ODK, ORG, ORS, PAN, SEB, SUN, TDC, TMS, TPH, TRG, VDH, VOM, XEE, XEH, XEO, XEZ & XSK)

How to:

Download the file

Unzip it

Run ODIN

Select PDA

Select the unzipped file

Click on Start

Done!

File:

KI8_NEW_ROOT.RAR

EDIT:

As I said, I used ChainFire's CF-Root to play with all this and have just realized I could flash his kernel in order to have ClockworkMod recovery. We can do it using ADB or terminal (dd if=/sdcard/zImage of=/dev/block/mmcblk0p5 bs=4096), but the easiest way to do that is using

his

CWM Manager. If you want to have ClockworkMod recovery:

Download this file

Unpack it

Copy the unpacked files to your SDCARD

Using My Files app (in the app drawer) install CWMManager.apk (by ChainFire)

Run CWM Manager

Scroll down and tap on Flash kernel option

Select zImage

Your Galaxy S II will reboot after few seconds

Done!

Thanks ChainFire!

PS: this procedure won't increase custom binary counter... if you think this info is useful, click on Thanks ;)
[Galaxy S II Android Development] rizdroid:
BUMP! 10char
[Galaxy S II Android Development] rizdroid:
Hi there -

SOURCE has been updated (in Portuguese): http://www.portalandroid.org/comunidade/viewtopic.php?f=84&t=14007

Cheers!
[Galaxy S II Android Development] rizdroid:
Added XWKI8 (2nd post)
[Galaxy S II Android Development] uronfire:
Nice post was looking for this
[Galaxy S II Android Development] rizdroid:
2nd post has been updated with info about how to get ClockworkMod recovery using ChainFire's kernel.
[Galaxy S II Android Development] pan24:
if i flash one kernel via odin will i have yellow triangle?
[Galaxy S II Android Development] mariosraptor:
you should read firsr post before asking this kind of questions.

so for the record OP says no triangle and no custom binary count.

if you will use this do not forget to say thanks to OP:D
[Galaxy S II Android Development] rizdroid:
Yep!

If you flash a non-official kernel via Odin

, you'll have triangle on boot and your custom bin counter will be increased.

cheers!
[Galaxy S II Android Development] rizdroid:
Added XWKI4 - Optimus, Portugal (1st post)
[Galaxy S II Android Development] mbevc1:
Any feedback flashing this rooted version? Is there KJx on the way? Thanks!
[Galaxy S II Android Development] ferreinf:
Nice to see you here.... ;)
[Galaxy S II Android Development] sperb:
Hi Rizdroid. Can I install and use this rom (XWKI8) in Brazil. Are all the functions (GPS, radio, wi-fi, 3G, camera, etc) ok?

Thank you brother
[Galaxy S II Android Development] timberwolf60:
Hi friends you can try this Easy rooting and unrooting here: http://xdaforums.com/showthread.php?t=1319653.

No triangle and no counter increased. If need CWM then used DARKYROM2.apk from market to flash siyah kernel 2.1.1.tar or 2.2b15.tar. Upon successfully done and you will have a rooted phone with CWM V5.apk. Hope you enjoy!
[Galaxy S II Android Development] hawkdown77:
I am now with this rom ... if I want to do the procedure with which factoryfs firware version of the root already have to install?

XXKI3

firmware info

PDA: XXKI3

PHONE: XXKI3

Date: 15/09/2011

Android 2.3.5

XEO (Poland): http://www.multiupload.com/XTRG43JVEG
[Galaxy S II Android Development] rizdroid:
DO IT YOURSELF: unbranded Brazilian firmware version LA2, Android 2.3.6 (in Portuguese): http://www.portalandroid.org/comunidade/viewtopic.php?f=84&t=17117
[AT&T Samsung Galaxy S II SGH-I777] bykr_dude15:
I am a huge fan of the Galaxy S phones but doesn't it bother anyone that the phone is only a 480 x 800 resolution while other phones like the htc amaze 4g (which has a 1.5 ghz snapdragon processor) has 540 x 960 and the iphone 4 has 640 x 960.

Honestly I don't know much about resolution but i would like to know that the phone i have wont be obsolete in the next few months.
[AT&T Samsung Galaxy S II SGH-I777] mcorrie1121:
The screen will be the very least of your worries, not that anything else should worry you.
[AT&T Samsung Galaxy S II SGH-I777] bykr_dude15:
No nothing else worries me this phone is fast as hell it will take some time before this phone is obsolete in any of the other areas
[AT&T Samsung Galaxy S II SGH-I777] arctia:
Go to the store and take a look at the screen, it is incredibly gorgeous, that you won't even pay attention to the resolution.