This is the PIT file for stock galaxy 2 on ATT
pulled it from my device via heimdall
it really isn't needed ATM but for the odin users it may come in handy for re-partitions and such.
Download Here
PAulyhoffman said:
This is the PIT file for stock galaxy 2 on ATT
pulled it from my device via heimdall
it really isn't needed ATM but for the odin users it may come in handy for re-partitions and such.
Download Here
Click to expand...
Click to collapse
Don't we need dbdata.rfs as well for re-partition? Correct me if I am wrong.
IlluminatedOne said:
Don't we need dbdata.rfs as well for re-partition? Correct me if I am wrong.
Click to expand...
Click to collapse
rfs? Haha
Sent from my SAMSUNG-SGH-I777 using xda premium
gtg465x said:
rfs? Haha
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
What I meant is, as per my knowledge, pit file won't do the repartition unless it has all the rfs files available. As I mentioned before, I may be wrong.
IlluminatedOne said:
What I meant is, as per my knowledge, pit file won't do the repartition unless it has all the rfs files available. As I mentioned before, I may be wrong.
Click to expand...
Click to collapse
Yup, I got what you meant. I was just making fun of you because this phone doesn't use rfs.
gtg465x said:
Yup, I got what you meant. I was just making fun of you because this phone doesn't use rfs.
Click to expand...
Click to collapse
Oh, I didn't know that. I still haven't got my hands on this device yet.
What file system it is using then?
I just found out yesterday that rfs was not used in this phone as well - very happy to learn that. Also curios which fs is/are used.
Sent from my SAMSUNG-SGH-I777 using XDA App
ext4 is used
gtg465x said:
ext4 is used
Click to expand...
Click to collapse
ext4 is used, and of equal if not greater importance, it uses standard MMC partitioning instead of that wacky FSR (stl/bml) crap.
As a result the kernel has zero proprietary modules, which means we can use CONFIG_LOCALVERSION and can also update the Linux kernel base if we want to without ugly hacks like updating to 2.6.35.9 (or whatever) and hacking it so it reports as .7 so the damn modules will load.
Entropy512 said:
ext4 is used, and of equal if not greater importance, it uses standard MMC partitioning instead of that wacky FSR (stl/bml) crap.
As a result the kernel has zero proprietary modules, which means we can use CONFIG_LOCALVERSION and can also update the Linux kernel base if we want to without ugly hacks like updating to 2.6.35.9 (or whatever) and hacking it so it reports as .7 so the damn modules will load.
Click to expand...
Click to collapse
Wow, I didn't know it uses ext4 fs! Such a much better fs than RFS. If it makes kernel dev/updating easier than I'm all for it
eep2378 said:
Wow, I didn't know it uses ext4 fs! Such a much better fs than RFS. If it makes kernel dev/updating easier than I'm all for it
Click to expand...
Click to collapse
Means we don't have to waste time and complicate things with lagfixes like we had to do with the original Galaxy S line.
Sent from my SAMSUNG-SGH-I777 using xda premium
Voodoo from Supercurio?
That is great news!!! I received my ATT SGS2 2 day ago and I was wondering that, cause even the stock GB feels so smooth and fast.
Question: Do I still have the chance of installing the Voodoo apk to take advantage of the Voodoo Sound features? Such as Bass improvement and others.
________________________
Proud owner of an i777 SGS2
Currently on stock ROM (rooted, busyboxed, deodexed)
Related
Presenting bmlunlock. Unlocks bml7 for writing to it via dd.
http://github.com/CyanogenMod/android_device_samsung_bmlunlock
Nice! Thanks Koush.. it's about time you did some actual work around here..
lol brandon. you know better. he pushed out 2 updates to CWM for us in less than ten minutes last night!
Yeah, I was just kidding. What really makes this useful is this bmunlock and the updated adb access via recovery. Very slick.
BHey would it be possible to use this to flash the kernel of a facinate from a mac? If so could you guys give a quick explanation of how. Us mac users are itching to get ready for roms.
If someone can do the terminal write up for the bmunlock kernel flash on windows we can probably figure out how to do it on our macs..... anyone? Please.
Well first somebody needs to cross-compile that .c source from github for android.
I don't have the tools to do that ATM, but I'll work on that.
From the README on koush's github it looks like you just run the bmunlock executable on the device, which unlocks the partition and then use dd to flash the kernel zImage contained within the tar.zip posted here: forum.xda-developers.com/showthread.php?t=787168
I'll work on this on my Fasc and post clearer instructions if I'm successful.
You rule Koush! Missing your work since i switched from the Droid to Fascinate. Thanks a lot keep it up!
I'm sorry, but what exactly is this?
If you don't know, you don't need it.
It allows devs to flash kernels directly.
adrynalyne said:
If you don't know, you don't need it.
It allows devs to flash kernels directly.
Click to expand...
Click to collapse
Well... guess I don't need it. LMFAO! ... Moving on.
The fascinate needs it.
Sent from my SCH-I500 using XDA App
keith.mcintyre26 said:
The fascinate needs it.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Redbend works as well.
Sent from my SCH-I500 using XDA App
adrynalyne said:
If you don't know, you don't need it.
It allows devs to flash kernels directly.
Click to expand...
Click to collapse
Ah. Then I don't need it. I appreciate the work Koush, but I don't know a thing about programming and I'm not a dev.
How do I compile it for the GB kernel? Do I just need to use the cross compiler?
We have an issue with the Pop Plus (GT-S5570I) flashing kernels via zip files. Sometime they do not flash at all. Others they do. It is a real pain in the butt.
Miche1asso said:
How do I compile it for the GB kernel? Do I just need to use the cross compiler?
We have an issue with the Pop Plus (GT-S5570I) flashing kernels via zip files. Sometime they do not flash at all. Others they do. It is a real pain in the butt.
Click to expand...
Click to collapse
Look at the date of the last response... 2010...
For gingerbread, you can use bmlwrite instead of redbend:
https://github.com/CyanogenMod/andr...s-common/blob/gingerbread/bmlutils/bmlwrite.c
bhundven said:
Look at the date of the last response... 2010...
For gingerbread, you can use bmlwrite instead of redbend:
https://gist.github.com/CyanogenMod...s-common/blob/gingerbread/bmlutils/bmlwrite.c
Click to expand...
Click to collapse
I know… But that is what we have in our custom ROMs and I was hoping someone could still answer, as you did.
I'll check bmlwrite. Thanks!!
I noticed that the community has not successfully made a Kernel thats works without doing a boot-loop. Could it be possible that there is E-Fusish type security measure, like the Droid 2 and X, that prevents users from loading custom kernels that Verizon implemented? Thats the only explanation I can think of why we are having issues with our Galaxy versus other carrier's versions.
Sent from my SCH-I500 using XDA App
Samsung gave us a BUNK defconfig
the bootloader's not locked, kernel isn't signed
I've got a working kernel that boots, but the accelerometer is screwed up
jt1134 said:
Samsung gave us a BUNK defconfig
the bootloader's not locked, kernel isn't signed
I've got a working kernel that boots, but the accelerometer is screwed up
Click to expand...
Click to collapse
Sorry for my next noobish question but has anybody sent an email to Samsung about getting a fixed source code or is it pointless until 2.2 drops?
Sent from my SCH-I500 using XDA App
pointless? I guess that depends on who you ask. But yes, Samsung has received much electronic mail from smartphone enthusiasts over the past few weeks.
jt1134 said:
pointless? I guess that depends on who you ask. But yes, Samsung has received much electronic mail from smartphone enthusiasts over the past few weeks.
Click to expand...
Click to collapse
I will talk to my Samsung rep to see if there is anybody I could escalate this to in their North America branch to get this fixed but highly unlikely thou.
Sent from my SCH-I500 using XDA App
@Jt
I will be back on irc tommorow, but I have the accelerometer fixed on my kernel just no wifi, bluetooth or sound still. Have you found a fix for any of these, or are you still using my config?
AFAICT everything works now. I started with your config as a base
jt1134 said:
AFAICT everything works now. I started with your config as a base
Click to expand...
Click to collapse
This is good news, no?
Very nice gang.. I will block off some time for sure to stop in and see what's shakin' this evening..
Dirrk.. what initramfs are you using? I was able to compile with yamaha_b5 and your ramdisk, then I got the no sound/orientation/etc.. However it seems when JT compiles, he uses koush's ramdisk, and gets sound (orientation still off).
If I compile with b5_yamah + koush ramdisk (from his git), Odin fails to flash every time. If I switch back to your ramdisk, odin flashes, kernel boots, etc..
Sounds like you guys are making some good progress. Thanks for your hard work. Can't wait to be able to overclock this sucker.
jt1134 said:
AFAICT everything works now. I started with your config as a base
Click to expand...
Click to collapse
Are you using a different ramdisk to get it fixed as mentioned below v
namebrandon said:
Very nice gang.. I will block off some time for sure to stop in and see what's shakin' this evening..
Dirrk.. what initramfs are you using? I was able to compile with yamaha_b5 and your ramdisk, then I got the no sound/orientation/etc.. However it seems when JT compiles, he uses koush's ramdisk, and gets sound (orientation still off).
If I compile with b5_yamah + koush ramdisk (from his git), Odin fails to flash every time. If I switch back to your ramdisk, odin flashes, kernel boots, etc..
Click to expand...
Click to collapse
Can you send me koush's ramdisk. I have been out of town working for the past few days
Dirrk said:
Can you send me koush's ramdisk. I have been out of town working for the past few days
Click to expand...
Click to collapse
Maybe JT or someone at a linux box can tar it up if you need it as an archive.. I don't have any git software here at work..
http://github.com/koush/fascinate_initramfs
namebrandon said:
Maybe JT or someone at a linux box can tar it up if you need it as an archive.. I don't have any git software here at work..
http://github.com/koush/fascinate_initramfs
Click to expand...
Click to collapse
Thanks man wow after rereading ur op it says its on koush's git lol
Quick question, i've gotten rom building down with CWM and Amon Ra but now I want to dabble in kernel modding but I want to get a general preference on where everybody started at.
Sent from my SCH-I500 using XDA App
Is there a way to root without flashing an insecure kernel?
Sent from my SAMSUNG-SGH-I777 using xda premium
shadowskorch said:
Is there a way to root without flashing an insecure kernel?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1286432
Thanks a bunch entropy. But i was thinking more along the lines of using superoneclick or something on stock kernel. I've never rooted a Samsung device. I guess the atrix devs made stuff TOO easy.
Sent from my SAMSUNG-SGH-I777 using xda premium
shadowskorch said:
Thanks a bunch entropy. But i was thinking more along the lines of using superoneclick or something on stock kernel. I've never rooted a Samsung device. I guess the atrix devs made stuff TOO easy.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
The devs working on Samsung make it pretty easy too. Odin and One-Click Root have helped me with my original SGS many, many times. Hopefully, we'll see something similar for the SGSII, if it isn't out already.
Yeah, what happened to the good ol days of putting a root file named update.zip and going in to stock recovery to use it?
Sent from my SAMSUNG-SGH-I777 using XDA App
shadowskorch said:
Thanks a bunch entropy. But i was thinking more along the lines of using superoneclick or something on stock kernel. I've never rooted a Samsung device. I guess the atrix devs made stuff TOO easy.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Atrix is not easy haha. this is my second Smasung. once you get to know odin you will reaize its a life saver and sooo easy. you cant brick these things lol
abacon15 said:
Yeah, what happened to the good ol days of putting a root file named update.zip and going in to stock recovery to use it?
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
i'm pretty sure you can't do that anymore because those flaws were patched.
I'm pretty new to the samsung rooting world, this is my first real samsung device. What the heck is odin? What is the difference in rooting using superoneclick and Entropy512's method? Sorry for the newb question.
abacon15 said:
Yeah, what happened to the good ol days of putting a root file named update.zip and going in to stock recovery to use it?
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Stock recovery won't flash ZIPs not signed by Samsung.
On older devices, the road to CWM that was easiest was usually:
Root, replace recovery with a hacked version that disabled signing checks
However, in later versions of Gingerbread, all of the usual methods of rooting were closed because malware was using the same holes. As a result, SOC is unable to root a device without some "help", and on Samsung devices that "help" is an insecure kernel.
SysAdmNj said:
I'm pretty new to the samsung rooting world, this is my first real samsung device. What the heck is odin? What is the difference in rooting using superoneclick and Entropy512's method? Sorry for the newb question.
Click to expand...
Click to collapse
Odin is a program used by Samsung for device updates. It allows flashing of firmware in "download mode". The nice thing about this is that while it's easy to "softbrick" your phone with a bad kernel or corrupted system image, it is EXTREMELY difficult to corrupt the bootloaders used for download mode, especially on newer devices that go to extra lengths to protect their bootloaders from damage. As a result, for example, I know of a total of one hardbricked Infuse and that was the phone of a volunteer performing a dangerous experiment. There's an open-source reimplementation of Odin called Heimdall that a lot of people use, since Odin is Windows-only and Heimdall runs on Windows, MacOS, and Linux. I use heimdall because I run Linux.
The differences between rooting methods are not significant - different ways to achieve the end goal.
Insecure kernel + SuperOneClick - Will trigger "custom binary download" flags in the bootloader, but only requires fairly small downloads (maybe 20MB or so). Requires two steps (flashing the kernel, then SuperOneClicking)
Rooted system image (such as my unbrick) - Should not trigger "custom binary download" flags as the bootloader only seems to check the kernel for modifications. However it's a big download - around 250M if I recall correctly.
If you're going to eventually want to use Clockworkmod Recovery to install alternate ROMs and such, you'll have to install a custom kernel anyway. However my "unbrick" package is nice to have around if you hose up your system.
I'm planning on staying stock no custom kernel, rom or anything on that matter but I really need root. Don't really need CWM. Is there any other way to root beside going back to stock using Odin? I'm to lazy to set my phone back up. Or is superoneclick root working on a solution to easy root like on the infuse?
Sent from my SAMSUNG-SGH-I777 using xda premium
Thanks entropy I'll try your stuff out
Dxtra said:
I'm planning on staying stock no custom kernel, rom or anything on that matter but I really need root. Don't really need CWM. Is there any other way to root beside going back to stock using Odin? I'm to lazy to set my phone back up. Or is superoneclick root working on a solution to easy root like on the infuse?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
In terms of "back to stock" - it means "back to stock firmware" - it won't touch your data partition, so if you're already on stock firmware, you should retain all your data.
shadowskorch said:
Thanks entropy I'll try your stuff out
Click to expand...
Click to collapse
I've had no issues with Entropy's stock+root package. If anything goes wrong, just flash this and your good to go
Found this from Chainfire here Tried it and my device is at risk. If we only had this before the problems with the Leak that was bricking phones.
So, i'm in danger. So what. What can i do?
RatusNatus said:
So, i'm in danger. So what. What can i do?
Click to expand...
Click to collapse
I don't think I'll be using any AT&T leaks. Until they have proven they are safe. At least we can make more informed decisions on what to flash.
blutruck said:
I don't think I'll be using any AT&T leaks. Until they have proven they are safe. At least we can make more informed decisions on what to flash.
Click to expand...
Click to collapse
Already did 8 flashs of aokp. Really great.
No one conplains.
You should try it but Follow the intructions.
Most bricked is user f... up.
Sent from my SGH-I777 using XDA
Wow so i thought this was related to a bad wipe setting Samsung had compiled into their kernels? This is an actual hardware defect now or is it software based??
Sent from my SAMSUNG-SGH-I777 using Tapatalk
I belive AOKP is on the same boat that cm9... ITS SAFE!
Namida said:
It's important to understand that the source of this problem is bad firmware in the eMMC chip. There is nothing technically wrong with the kernel itself. The eMMC claims to support a method of erasure that causes it to write bad data when it's used.
To achieve safety, you either fix the chip so that it supports the method it claims to properly or avoid using that method of erasure.
Cyanogenmod 9 is safe because it doesn't erase using that method. They use their own kernel built from their own source code.
Samsung ICS kernels are not safe because they call the best method the eMMC claims to support when erasing, which is bugged within the chip's firmware.
Anyone who uses the official Samsung ICS kernel or the ICS leaks of Samsung's kernel are at risk. Chainfire's kernel is risky because Chainfire uses Samsung's official kernels and adds Clockwork Mod to them at the binary level. He doesn't have source to modify to make his kernels safe. Samsung must make their kernel safe before Chainfire can release a safe one himself. What Chainfire has done is modify the recovery so that it won't ask the kernel to erase the eMMC in a potentially dangerous way, but it won't stop sources other than that recovery from asking for a potentially bricking erase operation because the kernel hasn't been modified and will still do it if asked to.
Because we know something which versions of the eMMC chip are affected by this flaw, we can determine if a user is at risk simply by asking the chip to identify itself.
Decompiling a kernel is a completely different ball of wax. I wouldn't hold my breath for a tool that can do that and identify if your kernel is patched or not. Besides that, the source of the problem is now known with certainty and can be avoided by not flashing Samsung kernels until Samsung gets off their lazy butt and fixes theirs, or provides the code that can be used to fix the eMMC chip that is the source of all our troubles.
Click to expand...
Click to collapse
Thanks for posting this, I was unaware that the issue had been diagnosed.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
Its not the rom its the kernal and the hardware (emmc) so all the att gs2 are gonna all say the same thing .
Sent from my SAMSUNG-SGH-I777 using XDA
Mine is at risk.
Sent from my SGH-I777 using XDA
looks like an snake oil app to me. this is like running a test for bad sectors on a Standard hard drive for defects. THEY ALL LEAVE THE FACTORY WITH DEFECTIVE SECTORS, but they work just fine, and 95% of users never have any clue of this fact
Only this isn't simply bad sectors. Its a certain chips firmware that gets corrupted and unrecoverable when its simply wiped using an ATT ICS kernel...
Sent from my SAMSUNG-SGH-I777 using Tapatalk
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