Related
https://opensource.samsung.com/rece...hod=reception_search&searchValue=SGH-I777_ATT
this is awesome , this means we can have a rooted kernel on launch day!!!!
AT&T Galaxy S II Sub-Forum?
Where is the love for our own forum since we now have the kernel?
Edit: Well, it just happened this morning. Cool, our own forum.
The AT&T version is close enough to the international version that maybe they should keep the same forum? Or just have a sub forum for the dev board like i9003 on the i9000 board.
anilkuj said:
https://opensource.samsung.com/rece...hod=reception_search&searchValue=SGH-I777_ATT
this is awesome , this means we can have a rooted kernel on launch day!!!!
Click to expand...
Click to collapse
Hope the devs can find something they may be able to use on our version of this great phone.
I uploaded the file here also in case site goes down or anything
http://www.multiupload.com/R7CG8ZR085
Wow. Samsung releases something ahead of hardware and a carrier to boot. More reason to boot atnt.
I voided my warranty and your mum.
anilkuj said:
https://opensource.samsung.com/rece...hod=reception_search&searchValue=SGH-I777_ATT
this is awesome , this means we can have a rooted kernel on launch day!!!!
Click to expand...
Click to collapse
Nice head start for the devs
pukemon said:
Wow. Samsung releases something ahead of hardware and a carrier to boot. More reason to boot atnt.
I voided my warranty and your mum.
Click to expand...
Click to collapse
Awesome sig sir.
sent from my stock Infuse at Tranquility Base.
Looking forward to this... but I hear Sammy has been really good with the stock ROMs for this model. Great starting points for our amazing devs
Sure hope a custom ROM gets put up soon after launch. I'm sure the stock one will suffice for a few days. Not looking for anything fancy, just want some good 'ol root access.
bigblue95z said:
Sure hope a custom ROM gets put up soon after launch. I'm sure the stock one will suffice for a few days. Not looking for anything fancy, just want some good 'ol root access.
Click to expand...
Click to collapse
I'm sure you will be able to root it pretty quick. A custom kernel may take a few days... a good one will take a few weeks, if someone is able to dedicate some real time to it. Sure you will get some quick ROMs that are basically stock with a custom theme and bloatware removed, but I digress.
I THINK I read that DG already has something SETUP for the ATT version and just waiting to ha e it in hand to test it. Would be awesome to get some tentative roms set up before launch day so I can flash the same day
Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
RockRatt said:
I THINK I read that DG already has something SETUP for the ATT version and just waiting to ha e it in hand to test it. Would be awesome to get some tentative roms set up before launch day so I can flash the same day
Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
Click to expand...
Click to collapse
Heck yeah! Where'd you read that?
RockRatt said:
I THINK I read that DG already has something SETUP for the ATT version and just waiting to ha e it in hand to test it. Would be awesome to get some tentative roms set up before launch day so I can flash the same day
Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
Click to expand...
Click to collapse
Yep He will be developing the same ROMs for both phones although the Kernel will have to be reoriented due to the button on the international version like the i9000 was re the Captivate. I believe ROMS will be interchangeable but not kernels.
anilkuj said:
https://opensource.samsung.com/rece...hod=reception_search&searchValue=SGH-I777_ATT
this is awesome , this means we can have a rooted kernel on launch day!!!!
Click to expand...
Click to collapse
Depends on how different the initramfs is - fortunately it probably won't be significantly different.
Here's a recommendation I have from my experience with the Infuse community - I'm on the fence about upgrading Sunday, but since the AT&T GSII variant has a smaller screen and no Wolfson I'm likely to stick with the Infuse:
On launch day, have some people on IRC coordinating. Once a root kernel is developed, don't immediately post it here. Pick a handful of people to flash and test. Once they have root, their first order of business should be getting a clean stock system dump.
Once you have a system dump you can make an Odin/Heimdall-flashable system image with root - have someone who did NOT flash the root-injection kernel flash THAT in order to get a dump of the stock kernel. Without that you'll be flying blind as far as initramfs.
A few tips:
http://forum.xda-developers.com/showpost.php?p=17777056&postcount=42 - my initial tips for the Epic 4G Touch crew
http://forum.xda-developers.com/showthread.php?t=1081239 - You'll need this to make a Heimdall-flashable image from your system dump
https://github.com/mistadman/Extract-Kernel-Initramfs - Once you've dumped a stock kernel image, use that script to extract the initramfs. Put that up on github ASAP.
Also, I strongly recommend putting a straight unmodified source tarball up on github, and then work on getting it to a compilable state from there. That way the process of "cleaning up" the Samsung source is documented in git commits. See the early commits from LinuxBozo at https://github.com/Entropy512/linux_kernel_sgh-i997r/commits/master?page=2 as an example
If all goes well, I will have my GS2 Sunday morning, and be on IRC as well, ready to test flash the rooted kernel for you guys.
Hmm, I get bored @ SGS2.
If someone can post stock initramfs, aka "adb pull /"
Remove /data and /cache from the local files on your computer and then zip it up and post it here, you have root
netchip said:
Hmm, I get bored @ SGS2.
If someone can post stock initramfs, aka "adb pull /"
Remove /data and /cache from the local files on your computer and then zip it up and post it here, you have root
Click to expand...
Click to collapse
Hmm - good point, I don't think anything in initramfs has permissions set such that a non-root ADB user can't read it.
Entropy512 said:
Hmm - good point, I don't think anything in initramfs has permissions set such that a non-root ADB user can't read it.
Click to expand...
Click to collapse
Sorry, miss understand.
It is not required to have root, I am now testing with my SGS2.
netchip said:
Sorry, miss understand.
It is not required to have root, I am now testing with my SGS2.
Click to expand...
Click to collapse
That's what I meant - Previously I was assuming that to get a "good" initramfs dump, root would be required. However, after reading your post I realized that all of the relevant files in the initramfs SHOULD be readable by any user, even without root permissions.
Still it's ideal to get a direct initramfs extract from the kernel zImage as soon as possible.
Entropy512 said:
That's what I meant - Previously I was assuming that to get a "good" initramfs dump, root would be required. However, after reading your post I realized that all of the relevant files in the initramfs SHOULD be readable by any user, even without root permissions.
Still it's ideal to get a direct initramfs extract from the kernel zImage as soon as possible.
Click to expand...
Click to collapse
Yeah, I know.
But I will give you root kernel if you give me: /lib, /res, all *.rc files, /vendor and /sbin.
Stock system dump (this is not cwm flashable, this is for devs needing a base rom) all credit goes to drenner99
Deodex'd Version (cwm flashable)
this will allow themeing and your phone should run slightly faster
will someone please tell me what this does?
rj_22 said:
will someone please tell me what this does?
Click to expand...
Click to collapse
Nothing as of right now a dev has to cook a ROM using this as a base
Sent from my MB855 using xda premium
rj_22 said:
will someone please tell me what this does?
Click to expand...
Click to collapse
shabbypenguin said:
Stock system dump (this is not cwm flashable, this is for devs needing a base rom) all credit goes to drenner99
deodex version coming up here shortly
Click to expand...
Click to collapse
and here i thought i did...
It's just a system dump from the Motorola Electrify. It's more or less the same as our stock system dump.
Well let the rom making begin! I wanna root and flash my phone badly....but I dont wanna do it until there is a way I can go back to stock for warranty purposes.
deodex'd uploaded guys
shabbypenguin said:
deodex'd uploaded guys
Click to expand...
Click to collapse
shabbypenguin, the link you posted is password protected - fyi
thanks
shhhh no its not >.>
Thanks for the hard work, guys.
I wish I were able to make roms.
Unfortunately I'm running into an error when attempting to flash via cwm.
Getting status error 0.
:/
superuser in stock dump?
@shabbypenguin,
I was reading through your AIO root thread and it occurred to me that I had rooted prior to extracting the system dump that is posted in op as "Stock". Therefore, there is a version of superuser present in /app that I assume may not have been there as delivered. Of course, I may be making an incorrect assumption.
Is it appropriate then to call this stock, or is it a given that rooting would have been necessary to perform the dump in the first place?
I also don't know if this would affect your deodexed version?
Just wondering if this fact needs to be mentioned somewhere, unless I just did.
b4ifuru18 said:
Unfortunately I'm running into an error when attempting to flash via cwm.
Getting status error 0.
:/
Click to expand...
Click to collapse
It's says in op that you can't flash using cwn
Sent from my MB855 using xda premium
First off, thanks for all your efforts to provide us with this...
Second, root is a requirement for the dump and so even with the Superuser app, what you supplied is most definitely stock.
Unless of course you deleted anything in /system/ prior to the dump...
drenner99 said:
@shabbypenguin,
I was reading through your AIO root thread and it occurred to me that I had rooted prior to extracting the system dump that is posted in op as "Stock". Therefore, there is a version of superuser present in /app that I assume may not have been there as delivered. Of course, I may be making an incorrect assumption.
Is it appropriate then to call this stock, or is it a given that rooting would have been necessary to perform the dump in the first place?
I also don't know if this would affect your deodexed version?
Just wondering if this fact needs to be mentioned somewhere, unless I just did.
Click to expand...
Click to collapse
edward.hidalgo said:
It's says in op that you can't flash using cwn
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
I'm referring to the stock deodex that is cwm flashable according to shabby.
Beach_Head said:
First off, thanks for all your efforts to provide us with this...
Second, root is a requirement for the dump and so even with the Superuser app, what you supplied is most definitely stock.
Unless of course you deleted anything in /system/ prior to the dump...
Click to expand...
Click to collapse
Nothing was deleted
and thank you for your guidance in helping to get this done...
b4ifuru18 said:
I'm referring to the stock deodex that is cwm flashable according to shabby.
Click to expand...
Click to collapse
This is simply a stock from from the Photon's "sister," the Electrify. No one has even identified if there are any benefits/improvements hidden inside this ROM, much less how compatible it is with the Photon.
Just because something IS flashable doesn't mean you SHOULD flash it. OP was very clear - this is for devs only, not public consumption. If you don't know enough, then you're better off exercising some patience and waiting for further announcements.
actually im gunna guess that the man has an electrify and my cwm script is busted
I would venture to guess that you guys will have the same issue we do with the photon roms. As other members on my team verified that root, recovery, kernel and unlock work from the photon. The kernel needed wifi fixed which was pretty simple. In which I pm'd shabby about earlier. The roms also work but some things need fixed to get it working.
I don't know all the details besides what weasel told myself. But mms, 3g I believe works but going back to stock it wouldn't, eri says sprint, blur e-mail fc's and activation for sprint kept popping up to where you have to skip it. Weasel has fixed most of the stuff in the homebase port. I believe e-mail still fc's and mms is still broke.
But here is the first deodex rom weasel and myself did if you want to add it to the first post. http://2fastroms.com/viewtopic.php?f=116&t=265
Then here is the kernel shabby did with wifi fixed ready to install. Only rc-1 since wifi was broke in rc-2. If the electrify people want to install it just grab it from shabby's thread. There was reports of 3000's+ in bench's. Not sure of rom it was on but I would venture to guess our stock rom. http://2fastroms.com/viewtopic.php?f=118&t=334
Then here is the port for homebase weasel is playing with http://2fastroms.com/viewtopic.php?f=116&t=268 if you guys wanted to look at it.
i would gather a lot of frameworks issues, as with services.jar would happen between the phones.
edit: you keep saying you fixed wifi. but the only way to fix it, is by rebuilding the modules using my config file.. which only i have...
unless im missing some other way to replace it?
hi there,
I'm aware that the CF-root-kernel is used a thousand-times by many people but this makes this question even more important: has it been completely reviewed by other developers in fact because the source is open?
don't get me wrong, I really don't want to allege anything to chainfire, but since it's the kernel, the core of the system, this component should be fully reviewed and proofed as clean and safe. otherwise no droidwall can ever detect e.g. silent data transmissions (sent on kernel-level) or spy-attack etc....
so if the whole CF-Root-Code is released e.g. on github I think things like that could be revealed/proofed. if it's completely closed it's just a question of trust...
unfortuanately it's seems like it's kept secret... because https://github.com/Chainfire says "Chainfire doesn’t have any public repositories yet"...
does chainfire keep his CF-Root-Source closed and secret and due to that could theoretically put some secret kits in there?
so I'd like to know if the CF-Kernel (made by chainfire) is open source or alternatively chainfire released his source code, and this code could and has been reviewed by others (e.g. experienced senior members)?
btw: if it's closed sourced and due to this potentially "unsafe"... are there any other fine root-kernels with cwm which are open source and due to can be fully trusted?
Hullo.
Well some developers like to have their hard work protected from stealing so they are using closed source approach. You should not fear using a kernel or ROM when it's downloaded from the official site, even better with md5 checksum.
Sent from outer space by aliens on tapatalk using SGS2
AJ.Rockwell said:
Hullo.
Well some developers like to have their hard work protected from stealing so they are using closed source approach. You should not fear using a kernel or ROM when it's downloaded from the official site, even better with md5 checksum.
Sent from outer space by aliens on tapatalk using SGS2
Click to expand...
Click to collapse
it doesn't provide any security if "it's downloaded from the official site" when the source of the "official site" has never / could never been reviewed. neither does a md5 checksum... if CF-Root is really closed source it's like blind faith and I think when in comes to kernels, the core of your phone... blind faith isn't a good idea...
CF-Root has no patches to the actual kernel, it's "only" the initramfs that is edited to give you everything you ask from his kernel.
Open a terminal, type "cd /" and off you go inspecting everything.
OpenSource would give you not a single bit of more "secure feeling" - what if the backdoor is simply not included in the source, but built into the binary release?
May I ask what exactely you are afraid of?
And on a sidenote:
Yes, I did a rather deep "walk through" the files of CF's kernel and you have no reason to believe and trust me more than CF himself, but let me state it anyways:
It's totally cool, save, no backdoors, everything is A-OK!
Hope that helped a bit
A thought about why would well known kernel/ROM devs place backdoors in their products is way beyond me. There surely is a botnet full of siyahkernel users haha jk... Just take it easy, CIQ is more of an issue lately..
Sent from outer space by aliens on tapatalk using SGS2
AJ.Rockwell said:
There surely is a botnet full of siyahkernel users haha jk...
Click to expand...
Click to collapse
*LOL*
That one really made me laugh XD
at first, thank you for your reply!
HellcatDroid said:
CF-Root has no patches to the actual kernel, it's "only" the initramfs that is edited to give you everything you ask from his kernel.
Click to expand...
Click to collapse
ok, but how can this be checked? how can it be proofed, that is the original kernel? can I proof it in anyway for my self? and maked shure that there is no backdoor in it?
HellcatDroid said:
initramfs
Click to expand...
Click to collapse
because I want to learn more... what is "initramfs" in particular?
HellcatDroid said:
Open a terminal, type "cd /" and off you go inspecting everything.
Click to expand...
Click to collapse
sorry that I ask so silly, but what will this command reveal, other than the content of the actual folder? how does this help to inspect the kernel in detail?
HellcatDroid said:
OpenSource would give you not a single bit of more "secure feeling" - what if the backdoor is simply not included in the source, but built into the binary release?
Click to expand...
Click to collapse
yeah, there you're right, what brings me to the question (see above) how the compiled files can be checked/verified/proofed?
HellcatDroid said:
May I ask what exactely you are afraid of?
Click to expand...
Click to collapse
just like you mentioned... something like backdoors, secret data transmissions which can be revealed because they happen on kernel-level...
HellcatDroid said:
And on a sidenote: Yes, I did a rather deep "walk through" the files of CF's kernel and you have no reason to believe and trust me more than CF himself, but let me state it anyways:
It's totally cool, save, no backdoors, everything is A-OK! Hope that helped a bit
Click to expand...
Click to collapse
hehe, thats right, I don't know neither you nor chainfire... although I appreciate you posting.
AJ.Rockwell said:
A thought about why would well known kernel/ROM devs place backdoors in their products is way beyond me. There surely is a botnet full of siyahkernel users haha jk... Just take it easy, CIQ is more of an issue lately..
Sent from outer space by aliens on tapatalk using SGS2
Click to expand...
Click to collapse
so I think it's no so odd to ask about the trustworthiness of CF-Kernel as well, isn't it? especially if it's kept secret by cf... no one should blind faith, when it comes to kernels...
In loose order of your questions above:
*
You can grab one of the kernel initramfs (see answer to what that is below) dumpers, most of them split the zImage into the actual kernel (code) and said initramfs.
The kernel (code) image should be almost 100% identical (almost due to some headers and those things that might be different due to the edited initramfs).
*
When the kernel is started, there is nothing - like on god's first day during creation (don't laugh, I kinda mean it like that! )
There is no system (that's still sitting somehwere on the flash or HDD or wherever) and nothing.
But the kernel needs a place to start booting up the system and to load additional kernel (driver) modules from that are not statically compiled into the kernelcode itself.
So the zImage has an image of a small, base filesystem that is placed into a RAM disc just before the kernel code is started (usually done by the bootloader).
This filesystem is the "initramfs" (short for "initial RAM-disk filesystem").
In the SGS2 case (or Android in general) /system and /data (and some others) are mounted into this so the system can finally be booted up by the kernel.
*
with "cd /" you change to the uppermost, "root" directory of the system, it's where everything starts in Unix/Linux world and where the mentioned initramfs is.
So by browsing the folders in there (except for additionally mounted in one's like /syste, /data, /efs, /tmp and some more) you are exploring the contents of the initramfs - it's not really secret.
Though, it can be made more secret, of course.
*
there is about one bazillion tools and apps that can compare files
CF Root is the most vanilla out of all the Kernels. It is just the Samsung stock Kernel + root. It has been tried by thousands of people without a problem and is 100% clean, safe and open source.
if in doubt
chainfire specifically mentioned that his kernel is taken from the stock samsung firmware, modified to get "root", CWM and busybox. he didn't mention of any specific tweaks (to make it better than stock).
so when in doubt, after rooting (and used up all the goodies of CF-root kernel), flash back to stock kernel. he included in his post how to do it.
have you reviewed the stock kernel's source? is it safe?
Paranoid much ? I'd be more worried about crap (Carrier IQ, etc) your telco has put on their particularly branded phone (particularly if you have a US variant of the SGS2) than anything Chainfire might do.
if youre so afraid, stay stock
oh and on a side note, theres this website called Google (go to www.google.com)
and search for answers.
Any app you download from the Market may have backdoors in them. Any app with network access may potentially connect back to the developer and send all sorts of information, or even files, back.
So, if you want to be "safe", you have no choice but to stick to the base stock software. But then ... maybe Samsung could have placed stuff in your phone doing stuff you may not be happy with.
And we can't forget Windows OS either, how many time may that connect and send info and files back, and have various backdooes we don't know about ?
As it has been pointed out, simply having "open source" doesn't guarantee you anything, unless you compile that yourself as well as.
Break out the tin-foil hats
Once u hear its chainfire... its safe. Good dev.
looks like an iphone but powered by android baby!!!!
It's a legitimate question. We are flashing modified software to our phones made by others. It can be a security risk, anyone could modify a rom and let it send privacy information to his server. It is someting we should consider everytime we flash a rom. That we always presume that the roms on XDA are safe, does not rule out the possibility that it will happen in the future. Smartphones are getting more interesting for people with bad intentions.
As mentioned above, it's the same with installing apps from unknown sources and even the Android Market.
But if there is any developer I would trust, it is Chainfire. He has done more for XDA then most of us ever will.
Thanks for all the replies!
postfatal said:
CF Root is the most vanilla out of all the Kernels. It is just the Samsung stock Kernel + root. It has been tried by thousands of people without a problem and is 100% clean, safe and open source.
Click to expand...
Click to collapse
Yes, I'd agreed that thousands of people use it without even think about it. I know / read that it's a very common and known root-kernel. but I think precisely because the latest scandals with spysoftware... it's important to look into these CF-Kernels. unfortunately I'm not able to review it myself, because I'm not that into Unix-Coding. What makes you so shure about it's really "Samsung stock Kernel + root"?
ngokula said:
chainfire specifically mentioned that his kernel is taken from the stock samsung firmware, modified to get "root", CWM and busybox. he didn't mention of any specific tweaks (to make it better than stock).
so when in doubt, after rooting (and used up all the goodies of CF-root kernel), flash back to stock kernel. he included in his post how to do it.
have you reviewed the stock kernel's source? is it safe?
Click to expand...
Click to collapse
Yeah, anyone can say anything he wants, like "chainfire specifically mentioned that...". yeah he might have mentioned it, but if his kernels aren't reviewed before they're used by thousands of people... hmm... as I mentioned I really don't want to allege anything to chainfire. I think he's doing a great job. I just wanted to ask, if there could be something in it, or if there are reviewd and proofed, not only used with blind faith...
Touché! The stock kernel could be unsafe as well. but the included "stock" kernel is not from samsung directly, but from chainfire as well... so it's the same source... that doesn't make it any better...
MistahBungle said:
Paranoid much ? I'd be more worried about crap (Carrier IQ, etc) your telco has put on their particularly branded phone (particularly if you have a US variant of the SGS2) than anything Chainfire might do.
Click to expand...
Click to collapse
yeah, you're right there. but wouldn't it be better if there's at least nothing added even more?
androidkid311 said:
Once u hear its chainfire... its safe. Good dev.
looks like an iphone but powered by android baby!!!!
Click to expand...
Click to collapse
yeah I have the same "feeling" about this, but this is just blind faith on my side. is is blind faith on your side, too, or do you have any hard proofs about this?
Lennyz1988 said:
It's a legitimate question. We are flashing modified software to our phones made by others. It can be a security risk, anyone could modify a rom and let it send privacy information to his server. It is someting we should consider everytime we flash a rom. That we always presume that the roms on XDA are safe, does not rule out the possibility that it will happen in the future. Smartphones are getting more interesting for people with bad intentions.
As mentioned above, it's the same with installing apps from unknown sources and even the Android Market.
But if there is any developer I would trust, it is Chainfire. He has done more for XDA then most of us ever will.
Click to expand...
Click to collapse
thanks for your approval. and I agree on you, too. I think only a few people even have a slight thought about what they flash there on their phone... I think this should always be peer-reviewed by professional devs, before its possible to download such files...
I personally would rather see people question things like this. People should NOT download crap from nobodies...
So to answer your question about CF-Root, here's why it's safe...
1) CF-Root is NOT a recompiled kernel. It's the 100% totally stock kernel. You can split the zImage into ramdisk and kernel image, and compare the kernel image SHA1 with that of the split stock zImage. If it's the KL1 CF-Root, compare to the KL1 stock. You'll find the two match identically.
2) CF-Root is a modified initramfs, to give functionality such as auto rooting, and much more. If you take your stock initramfs, and compare it to the CF-Root one, you can see the changes for yourself. It's shell scripts (bash), so it's plaintext.
You'll see binaries added to the initramfs - busybox for example... So go compare that to the generally available busybox and you'll see it's fine
In short? Yeah it's fine. In long? It's fine for the reasons above
pulser_g2 said:
I personally would rather see people question things like this. People should NOT download crap from nobodies...
So to answer your question about CF-Root, here's why it's safe...
1) CF-Root is NOT a recompiled kernel. It's the 100% totally stock kernel. You can split the zImage into ramdisk and kernel image, and compare the kernel image SHA1 with that of the split stock zImage. If it's the KL1 CF-Root, compare to the KL1 stock. You'll find the two match identically.
2) CF-Root is a modified initramfs, to give functionality such as auto rooting, and much more. If you take your stock initramfs, and compare it to the CF-Root one, you can see the changes for yourself. It's shell scripts (bash), so it's plaintext.
You'll see binaries added to the initramfs - busybox for example... So go compare that to the generally available busybox and you'll see it's fine
In short? Yeah it's fine. In long? It's fine for the reasons above
Click to expand...
Click to collapse
thank you very much! this is a well formulated and consistent answer! so chainfaire doesn't have to release his source, cause it's completely plain text... If that's true, it could be reviewed (and was I think), and that's fine.
So as the title says my gs2 is on its way! Unlocked international version. I plan on rooting, and installing cwm, do a nandroid of stock, then install an ics rom which rom is the most stable and have everythijng if not almost everything working properly?
Sent from my SPH-D700 using Tapatalk
PLS search and read ...
PLS search and read ... there are a lot of threads covering ICS.
Wrong section = Q&A
ICS is not released test at your own risk .
jje
jerseykat1 said:
So as the title says my gs2 is on its way! Unlocked international version. I plan on rooting, and installing cwm, do a nandroid of stock, then install an ics rom which rom is the most stable and have everythijng if not almost everything working properly?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
WTF??? A quick Google of SPH-D700 shows that to be the Samsung Epic 4G, which is a Sprint phone. The I9100 is a GSM phone. Sprint is a CDMA network. I hope you're planning on changing carriers if you hope to use the I9100.
Unless you're just confused, and actually ordered a Sprint variant of the Galaxy SII, which is the SPH-D710, or as they call it, the Epic 4G Touch.
Just so I'm clear, the I9100 will NOT work on Sprint's network.
Yea I'm aware that I am on sprint right now. I am aware that the i9100 is GSM, and yes I will be using att.
Sent from my SPH-D700 using Tapatalk
jerseykat1 said:
Yea I'm aware that I am on sprint right now. I am aware that the i9100 is GSM, and yes I will be using att.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Hey, I had to check. Some folks just make uninformed decisions and are baffled when the equipment they order doesn't work on their network.
LP6 with my GPS fix works pretty damn well. FM Radio is the only real issue I have encountered. If you want a more ICS experience, push trebuchet or NOVA launcher to /system/app and it will be much better.
Sent from my Galaxy Tab 10.1 iPad knockoff
It's so popular it's one of those phones - like Desire HD - that's known inside and out Been out in europe for ages, but the US had better carrier specific devices, faster CPUs, etc. At it's core the same device mind.
I was in no rush for ICS but tried WanamLite and all was fine, although the launcher freezes now and then which I put down to a full phone, and an early rom.
This used the CM9 trebuchet launcher. I've got to say almost everything about ICS is cleaner, faster, smoother than previous roms - custom or not. Easy task control, nice display, and little things I still keep discovering like when you connect via USB you get a choice of media device or camera (with the usual USB development option off).
I've had this thing months and must have flashed 50+ roms lol. In the end I stuck with Leomars then the combined Leomar/Checkrom HD because of the kitchen app for easy addons and upgrades.
If youve never used a samsung dont worry, its usually a simple app that will root it and install a recovery console <- very important, cause after that you can flash anything, and as long as you get back to recovery youll be fine. Backup often - complete rom via the recovery (power on, vol down) and a data/app backup with Titanium.
I don't think you need worry about ADB or odin anymore, but if you do just follow instructions on this site...
Your reward? the best phone around esp if the rom you use adds neat things like Jkays extensions, modded apps, kitchens, good theme engine, etc. For pure Android go for AOSP roms, otherwise they're a mish mash of parts.
Change the boot anim if you want, you might get a yellow warning triangle because the sammy knows the roms "illegitimate" but its easily removed.
Finally, should you need to, the stock roms and kernels and modems are here too if you need to get everything back to default, best get them quick as the download sites are dissapearing, or rip yours first before you burn another...
Have fun! You couldn't pick a better handset right now
essjayar said:
It's so popular it's one of those phones - like Desire HD - that's known inside and out Been out in europe for ages, but the US had better carrier specific devices, faster CPUs, etc. At it's core the same device mind.
I was in no rush for ICS but tried WanamLite and all was fine, although the launcher freezes now and then which I put down to a full phone, and an early rom.
This used the CM9 trebuchet launcher. I've got to say almost everything about ICS is cleaner, faster, smoother than previous roms - custom or not. Easy task control, nice display, and little things I still keep discovering like when you connect via USB you get a choice of media device or camera (with the usual USB development option off).
I've had this thing months and must have flashed 50+ roms lol. In the end I stuck with Leomars then the combined Leomar/Checkrom HD because of the kitchen app for easy addons and upgrades.
If youve never used a samsung dont worry, its usually a simple app that will root it and install a recovery console <- very important, cause after that you can flash anything, and as long as you get back to recovery youll be fine. Backup often - complete rom via the recovery (power on, vol down) and a data/app backup with Titanium.
I don't think you need worry about ADB or odin anymore, but if you do just follow instructions on this site...
Your reward? the best phone around esp if the rom you use adds neat things like Jkays extensions, modded apps, kitchens, good theme engine, etc. For pure Android go for AOSP roms, otherwise they're a mish mash of parts.
Change the boot anim if you want, you might get a yellow warning triangle because the sammy knows the roms "illegitimate" but its easily removed.
Finally, should you need to, the stock roms and kernels and modems are here too if you need to get everything back to default, best get them quick as the download sites are dissapearing, or rip yours first before you burn another...
Have fun! You couldn't pick a better handset right now
Click to expand...
Click to collapse
Just FYI. Bold/Italic/Underlined part is not exactly true. Some of the US carrier specific models have completely different hardware, and have faster clock speeds because they use inferior CPUs.
i got my i9100 today. but i am having some problems trying to get it rooted. using this method here http://forum.xda-developers.com/showthread.php?t=1125414 when i go to get the insecure kernel my kernel is not listed, and my original kernel is not listed either. So i am not sure if i do this rooting method using any kernel from the list if it will brick my phone or not.
waiting a reply from someone in the threads before i proceed.
2.6.35.7-i9100xwkj2-cl676699
[email protected] #2
jerseykat1 said:
i got my i9100 today. but i am having some problems trying to get it rooted. using this method here http://forum.xda-developers.com/showthread.php?t=1125414 when i go to get the insecure kernel my kernel is not listed, and my original kernel is not listed either. So i am not sure if i do this rooting method using any kernel from the list if it will brick my phone or not.
waiting a reply from someone in the threads before i proceed.
2.6.35.7-i9100xwkj2-cl676699
[email protected] #2
Click to expand...
Click to collapse
From what I can tell, you need the insecure KJ2 kernel. That kernel is no longer directly linked on Odia's insecure kernel page, but there's a link to his Hotfile upload site where all older kernels are stored.
ctomgee said:
From what I can tell, you need the insecure KJ2 kernel. That kernel is no longer directly linked on Odia's insecure kernel page, but there's a link to his Hotfile upload site where all older kernels are stored.
Click to expand...
Click to collapse
never dawned on me that i had an older kernel and that i should look at the older kernel list.. (i did just buy the phone) Duuuuuhhh.. no i am not being sarcastic (text doesnt always translate your true intentions, just thought i would clear that up)
Thank you.
jerseykat1 said:
never dawned on me that i had an older kernel and that i should look at the older kernel list.. (i did just buy the phone) Duuuuuhhh.. no i am not being sarcastic (text doesnt always translate your true intentions, just thought i would clear that up)
Thank you.
Click to expand...
Click to collapse
Tech moves at lightspeed.
ctomgee said:
Tech moves at lightspeed.
Click to expand...
Click to collapse
I am officially rooted. Thank you very much. now to get CWM installed!
I personally think that a bunch of people who come across custom roms for their 4.0 galaxy players ask themselves this question, "why aren't there very many roms for my device that are simply flashed through clockwork recovery?" Is it because this device is not very popular? Is it because not very many people know how to put a custom rom in a cwm package? In no way do I want to sound rude, but when I have to flash multiple things onto my device from my computer in order for the tomorto work right as well as not brick my device, it just ruins it for me. There is nothing wrong with roms that require a computer to install, but I personally think that with all those instructions that might not be too clear on what you are support to do, something is bound to go wrong.
Sent from my YP-G1 using xda app-developers app
NATO556 said:
I personally think that a bunch of people who come across custom roms for their 4.0 galaxy players ask themselves this question, "why aren't there very many roms for my device that are simply flashed through clockwork recovery?" Is it because this device is not very popular? Is it because not very many people know how to put a custom rom in a cwm package? In no way do I want to sound rude, but when I have to flash multiple things onto my device from my computer in order for the tomorto work right as well as not brick my device, it just ruins it for me. There is nothing wrong with roms that require a computer to install, but I personally think that with all those instructions that might not be too clear on what you are support to do, something is bound to go wrong.
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
This is not that it can't be done, but it the case of ics for the 4.0, it's a bug in the kernel that force us to flash a kernel from heimdall. If this bug was not here, the rom would be simply flashed with cwm. So the answer is it's not because dev don't want to do it like this, it's because they can't.
Couldn't they fix it?
Sent from my YP-G1 using xda app-developers app
NATO556 said:
Couldn't they fix it?
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
They don't fix it because they don't know what is broken, this is not a choice. This is not that easy to find what is causing a bug and to repair it. You should be a little more thankful of what you already have because without them there would be no custom rom and no recovery. If you really want it so bad just go ahead and fix it then share it with the dev and they will include it.
ti-pich said:
They don't fix it because they don't know what is broken, this is not a choice. This is not that easy to find what is causing a bug and to repair it. You should be a little more thankful of what you already have because without them there would be no custom rom and no recovery. If you really want it so bad just go ahead and fix it then share it with the dev and they will include it.
Click to expand...
Click to collapse
The problem is that the param.lfs isn't getting updated, probably because their kernel isn't compatible with Samsung's proprietary param.ko (so the bootloader still thinks you're in recovery). If it's not, there's nothing that can be done about it. If it is, they should include that module in the ramdisk. and insmod it with init.rc, and the recovery bootloop will be gone.
Mevordel said:
The problem is that the param.lfs isn't getting updated, probably because their kernel isn't compatible with Samsung's proprietary param.ko (so the bootloader still thinks you're in recovery). If it's not, there's nothing that can be done about it. If it is, they should include that module in the ramdisk. and insmod it with init.rc, and the recovery bootloop will be gone.
Click to expand...
Click to collapse
You seem to know what your're talking about, maybe you could explain this to zaclimon, the last time I tried to help him he was trying to change the onenand driver so the device have the good partirion layout. It would be nice to get rid of that bootloop.
ti-pich said:
You seem to know what your're talking about, maybe you could explain this to zaclimon, the last time I tried to help him he was trying to change the onenand driver so the device have the good partirion layout. It would be nice to get rid of that bootloop.
Click to expand...
Click to collapse
Well, that's part of it too. I think on the 4.0, the problem may be more complicated than that, due to it's storage layout, (I have the 5.0) but rest assured the devs are working on it.
Please let me know when they fix this bug what I need to do from there.
Sent from my YP-G1 using xda app-developers app
Mevordel said:
The problem is that the param.lfs isn't getting updated, probably because their kernel isn't compatible with Samsung's proprietary param.ko (so the bootloader still thinks you're in recovery). If it's not, there's nothing that can be done about it. If it is, they should include that module in the ramdisk. and insmod it with init.rc, and the recovery bootloop will be gone.
Click to expand...
Click to collapse
There's this but mostly because we change the partition (we completely ditch the j4fs support). Also the bootloaders expect to run BML/STL partitions so the bootmode isn't cleared. The thing that teamhackung made is that they created a partition named reservoir that would handle all the bad blocks. This partition is used to flash the boot partition which is the kernel one. This is still an undergoing experimentation for me but I'll try to compile a CM9 with this new type of flashing. An example of the partition layout is here:
https://github.com/CyanogenMod/andr...ung-3.0-ics/drivers/mtd/onenand/samsung_gsm.h
I may miss some things too but this is the things simplified.
Also NATO I do know how you feel about it and I'm trying to do my best (with han and oisis gone) to solve everything as soon as I can. (Don't forget that I have school too )
Sent from my Nexus 7 using Tapatalk HD
Actually most of the GB ROMs for the 4.0 are CWM flashable zips,
http://forum.xda-developers.com/showthread.php?t=1834375
http://forum.xda-developers.com/showthread.php?t=1718339 (older versions)
http://forum.xda-developers.com/showthread.php?t=1821860
http://forum.xda-developers.com/showthread.php?t=1895629
http://forum.xda-developers.com/showthread.php?t=1884557
http://forum.xda-developers.com/showthread.php?t=1719685
http://forum.xda-developers.com/showthread.php?t=1759949 (several ROMs)
http://forum.xda-developers.com/showthread.php?t=1825281
there are 2 or 3 more ROMs that are CWM zips but there based on the OLD CM7 port and with no deep sleep there not worth the time IMO (not the Porting DEVs fault, it was a known issue of the CM7 base).
NOT ENOUGH FOR YOU?
The ones that aren't are because of data corruption issues.
As for ICS, well thats been covered.
Thank you guys for all you do. I really am thankfull to have a website like this one to turn to for help.
Sent from my YP-G1 using xda app-developers app
As soon as the glitch is fixed please let me know. Another question, will there ever be an official CWM release on the player? And will Tardis_Balor update the Terra Silent Kernel once the glitch is corrected?
Sent from my YP-G1 using xda app-developers app
Also, why is hanthesolo's ethereal tomorrow not on this list?
Sent from my YP-G1 using xda app-developers app
rom*
Sent from my YP-G1 using xda app-developers app
BTW, the link for v2.0 of Icy Fusion is dead.
Sent from my YP-G1 using xda app-developers app