This is being released for TESTING PURPOSES ONLY. This is not intended to be a full release.
This is an SD Card release ONLY, if you want to flash the entire phone, visit the original thread. Beyond that, the build is 100% unchanged from the 7/10/2010 release of Incubus26Jc's Super FroYo 2.2 [Deodexed] [RLS10] - this is not the all languages release, just the standard RLS10 as downloadable from here.
All original information is in Incubus' original thread: http://forum.xda-developers.com/showthread.php?t=712310
I may just be being impatient, but this froze up on me a couple of times right after completing setup and beginning sync. Still, I have been able to fully install, boot the phone through HaRET, get text messages, and a little more. I've barely had much time to test this, but it's a step above your traditional proof of concept, so try it out!
Note, this release is not intended to either show up Incubus26Jc, nor claim his work as my own. I simply made the conversion and RAR'd it up. I'm sure Incubus26Jc chooses not to make an SDCard version available for his own reases and possibly doesn't want his name associated for whatever reason, I didn't clear this release in advance, and if requested, I will delete the thread.
>>>Direct Download Nu-Incubus Super FroYo 2.2 RLS10SD<<<
NuAngel said:
I actually bought a few pieces of software to do the conversion, but I figured a few bucks was worth it for something fun like this. Although, if anybody would like to donate a few bucks to the cause, PM me and I can get you my paypal address.
Click to expand...
Click to collapse
What exactly did you "convert"? And what software did you need? From first glance it just looks like you just threw the tar in with all the sdcard files found in other builds. The extracted tar and tgz are the same size... and you said that it's 100% the same thing... so why do we need a separate thread for this? Just ask Incubus if he could add the andboot files in a separate download in the original thread...
Well, in most basic terms all I did was convert the TGZ to a TAR, then grabbed the necessary HaRET files - but after this many releases, Incubus has intentionally had no SDCard version of his releases, so I just thought I'd toss this one out there for those like me who were interested in trying his latest release, but don't want to completely make the switch to Android and just like running it through WinMo.
NuAngel
NuAngel said:
Well, I'll just say the most basic thing I did was convert the TGZ to a TAR, then grabbed the necessary HaRET files - but after this many releases, Incubus has intentionally had no SDCard version of his releases, so I just thought I'd toss this one out there for those like me who were interested in trying his latest release, but don't want to completely make the switch to Android and just like running it through WinMo.
NuAngel
Click to expand...
Click to collapse
I read a post a while back by dzo on incubus' thread that in order to boot the TGZ from HaRet, you need to modify something in the default.txt (add a couple of lines in the cmd). Thanks for this though...
egzthunder1 said:
I read a post a while back by dzo on incubus' thread that in order to boot the TGZ from HaRet, you need to modify something in the default.txt (add a couple of lines in the cmd). Thanks for this though...
Click to expand...
Click to collapse
I am using Androidinstall.tgz files. Just install it to the SD card using the norootfs method that has been used for a while. His builds aren't anti-SD card from what I can tell...
Thanks for the kind words, EGZ. Wasn't trying to take any attention away from Incubus at all, I just wanted to tinker with it, myself, which was why I released it! I don't really intend to keep up with future releases, unless people actually want me to continue.
And the reason I had to spend money is because I don't currently have a single Linux machine in my place, and WinRAR doesn't make TAR files.
NuAngel
Do I understand this correctly?
Are you basically just wanting to install the Incubus FroYo build on the SD card? I was unsure about the exact method to do this as well. Here are the steps I followed to make it happen.
I think I did something similar to what you are doing here, except the convert the tgz to tar. All I did was take the tgz file and rename the extension to tar. No zipped or rar file program needed. Then I grabbed the basic haret files from Myn's eclair along with the updated zImage file. I threw it all in the andboot dir on the SD card. Everything installed just fine. Is this what you are trying to accomplish?
Vivafutbol - yup, pretty much the same process - I just never expected renaming the TGZ to TAR to work - they're similar fromats, but not identical... surprised it worked!
Still, if anyone is interested in checking it out, they can download it from the link above, no need to do any work.
NuAngel
NuAngel said:
And the reason I had to spend money is because I don't currently have a single Linux machine in my place, and WinRAR doesn't make TAR files.
NuAngel
Click to expand...
Click to collapse
There is no need to spend money for what you did. TGZ is just a gzipped TAR file and many freeware archivers can extract TAR from TGZ - like 7-Zip http://www.7-zip.org/ ..
Also, HaRET can handle TGZ..
NuAngel said:
And the reason I had to spend money is because I don't currently have a single Linux machine in my place, and WinRAR doesn't make TAR files.
NuAngel
Click to expand...
Click to collapse
Just out of curiosity, what program did you have to purchase that does this?
milanche said:
There is no need to spend money for what you did. TGZ is just a gzipped TAR file and many freeware archivers can extract TAR from TGZ - like 7-Zip http://www.7-zip.org/ ..
Also, HaRET can handle TGZ..
Click to expand...
Click to collapse
Doesn't HaRET just boot the zImage? Then in the kernel is where you would activate the system image like in the old days, or the adroidinstall.tar or tgz?
Forget I tried.
Oh, and 7-Zip will extract TGZ's - but the TGZ had folders in it, not another TAR file - thus getting those folders back in to a TAR required another piece of software - 7Zip doesn't create tar files.
It's okay, it was like $10. I didn't expect this to become the focal point of the ROM. Jesus.
NuAngel said:
Forget I tried.
Click to expand...
Click to collapse
It's great that you tried. You won't get the experience unless you do try.
The only problem I have with all of this is that you indirectly asked if people would donate to you. You couldve done a little research and found out that you didnt need to spend any money.
I'm not trying to attack you, you just couldve went about it differently. Asked Incubus if he could host it in the original thread (and at least given you credit), or if he would mind if you opened a new thread. I'm not speaking for him but I'm sure he would'nt have mind.
Again, I think it's great that you tried this on your own. We need more people like that in this community.
NuAngel said:
Oh, and 7-Zip will extract TGZ's - but the TGZ had folders in it, not another TAR file - thus getting those folders back in to a TAR required another piece of software - 7Zip doesn't create tar files.
It's okay, it was like $10. I didn't expect this to become the focal point of the ROM. Jesus.
Click to expand...
Click to collapse
I did it manually as well, and I didn't even rename the .tgz to .tar
I admit I had to hunt around for some files, so this does help, thank you
Its not my rom either. Its dzo's rom. I just done a few things to it. The reason i never put up sd install files in the roms is because of all the problems people usually have until they flash nand and all is better. I can put the haret files on the OP if you would like. No harm done buddy.
I saw your windows rom but haven't tried it yet because i'm still using nfsfan. Apreciate someone new taking an interest in vogue. Also I did flash froyo to my sd card but did have to read quite a bit. I am sure I would have appreciated being spoon fed. Thanks.
Since the last few posts have been pretty positive, one thing I might work on is slapping in an updated zImage file, since I did use a slightly olde one to try and boost stability (those who know my Windows Mobile ROM know that's my central focus).
NuAngel
NuAngel said:
Since the last few posts have been pretty positive, one thing I might work on is slapping in an updated zImage file, since I did use a slightly olde one to try and boost stability (those who know my Windows Mobile ROM know that's my central focus).
NuAngel
Click to expand...
Click to collapse
Also, the initrd.gz is very old (Maybe before the .tgz support was implemented). Try using THIS ONE (taken from HERE) with the tgz to see if it works.
I hope you did not take my post on the negative side. At the very least this thread has created some good conversation about how these files actually work together. I did have to search around for a while to get an understanding of which files should be used.
I personally like the SD version of the builds, because I don't have the guts to wipe out the windows install and risk breaking this great little device.
When I first flashed my GT-I9000 I didn't know about the ClockworkMod backup option, so used the Dump option in ODIN3 - thinking this would cover all bases.
Now I've got a .odin3.dump file and don't know what to do with it.
The PDA field only allows .tar .md5 and .smd files
but the PHONE field allows .bin files
Do I rename it to .bin and use it as a PHONE file?
If so - What would be the settings to flash i.e. 512.pit / Re-Partition / EFS Clear?
I've founds lots of posts asking what to do with the .odin3.dump file, but no answers - I'm sure a lot of folk would welcome an answer to this.
GalaxyS_JAB said:
When I first flashed my GT-I9000 I didn't know about the ClockworkMod backup option, so used the Dump option in ODIN3 - thinking this would cover all bases.
Now I've got a .odin3.dump file and don't know what to do with it.
The PDA field only allows .tar .md5 and .smd files
but the PHONE field allows .bin files
Do I rename it to .bin and use it as a PHONE file?
If so - What would be the settings to flash i.e. 512.pit / Re-Partition / EFS Clear?
I've founds lots of posts asking what to do with the .odin3.dump file, but no answers - I'm sure a lot of folk would welcome an answer to this.
Click to expand...
Click to collapse
I would... lol Ever find out?
Nope, still hoping someone will reply with what the dump file is for.
Hello:
I'm interested in creating and maintaining a custom rom for the Samsung Galaxy S. I've read a ton of tutorials and guides - on site and off - but I'm unable to get started due to one small problem.
After downloading the base firmware I'd like to use (specifically UGJK3 - firmware for Bell Canada) and opening it, I see a .tar file, and within that I see the following files:
param.lfs, zImage, modem.bin, cache.rfs, factoryfs.rfs.
I've mounted the .rfs files, but I'm still unable to cook the rom due to the absence of the system.img and boot.img files. I'm using the HTC Android kitchen to cook the rom, and it requires these files (or an update.zip file, etc) in order to start cooking.
I've searched far and wide, but I'm unable to find an answer on how to create these two .img files from the stock firmware provided by Samsung.
Any help is appreciated.
Thanks.
So, I've done a bit more research and apparently the way Samsung handles their firmware is different than other manufacturers. This leads me to believe that I must convert their rom into a usuable format before attempting to import it in the HTC Kitchen.
However, I'm unsure how to exactly do this.
I'm going to try flashing the stock firmware then performing a nandroid backup, then using that to create my custom rom. It'd be much, much easier if I knew how to just create the .IMG files from the Samsung firmware.
Anyone have an idea on how to do this?
Last bump before I give up.
Hello,
trying to repair an error that is bugging me to hell. When you run the recovery than thers a thing, this thing (error '/system/csc/MOT/system/', proceeding with MULTI CSC)
So I was thinking that when I would flash it with the correct CSC file from my carrier MOT (I9070MOTLE2) and get rid of the the Multi one.
And yes, does any one know why is my stock recovery written in red - is this normal? Da faq ;/
Thanks in Advance
I know that i can edit the previous post, but let this serve as a bump.
Is there a way lets say I could copy my carriers csc into the multi one and delete all others and then rename the whole flashable zip with the right name as it were my carriers separate csc file and just integrate it into the multi csc file. Probably I can do it this way, but in the multi csc zip there are three files in it;
- cache.img.md5
- GT-I9070_EUR_XX8G.pit.md5
- hidden.img.md5
so which of them should be modded to? How are those two files involved in the cache one which has the csc info? Why is there a pit file again? Or in other words.. which files trigger the correct order to successfully apply the modded csc.
If you can help me, I can guaranty that there will be "thanks" raining as Im not alone with this problem.
Corresponding thread: http://forum.xda-developers.com/showthread.php?t=2100642
Have a nice day
Hello, I'm looking for ways to eliminate MULTI CSC, but I have not found anything.
Hello, I think this would be the right subforum to post this thread but if it ain't feel free to move it where it belongs.
I'm helping out a friend which has an S5570I. His phone used to work but all of a sudden it didn't so he downloaded Odin and started to do god knows what with it following a YouTube video until it failed. End result: the phone seems to be soft-bricked.
In essence if started normally it would stay put in the Samsung logo, recovery can be accessed and the download mode apparently too. It was too bad this morning when I didn't see a procedure detailed here to (try to) restore the phone, so I'll try that when I have the chance.
Before knowing that it was bricked I was downloading the stuff necessary for a reflash, the questions I have are related to the firmware for the device.
I looked for the right firmware for it: matching model number and latest version matching current customization (just in case) which happens to be Movistar (Spain). I downloaded an archive with the firmware. Then I downloaded the latest version I could find of Odin (4.43 although I have 4.38 and 4.42 around here as well) and an OPS file for the model (named TASS_v1.0.ops).
So doing a dry-test here (without the actual phone) I did the following:
- Opened Odin (4.38 and later 4.43).
- Selected the OPS file.
- Checked the "One Package" option.
- Selected the tar.md5 file in the proper section.
And that's where Odin crashed, so at first I though "OK... bad firmware image?". I went on and downloaded a different one, customized for Spain as well but without any operator branding specifics; only to arrive at the same result. So the thing should be the image unless that other one was corrupted as well...
I started researching about that "tar.md5" format and it seems it should be a tar file (in ustar format) with the results of an md5sum execution appended to it.
Examining any of the firmware files I have through an hex editor I saw the output of the md5sum program in the end, which was expected, but then what should be a tar archive didn't seem to be (or I don't recognize its format). There is no magic number at 0x101, and the "file" utility in Linux recognizes the files as data instead or tar archives.
I'd like to know if anyone knows something about this, if there's anything wrong with the firmware or if those files were created in different way. I'd like to convert them to the appropriate format to use with Odin once/if the phone is debricked.
Thanks everyone for the time dedicated to at least read all this .
PS. I uploaded the files I have here to a hosting place so that you may download them if you wish to help out, here are the links (add https:// before the link because I don't seem to be allowed to post links just jet):
(S5570IBGMB2_S5570IXECMB1_XEC in SamMobile)
Link: copy.com/poYZ64CZLLvU
(S5570IXXMC1_S5570IOXXLK3_PHE in SamMobile)
Link: copy.com/onfqEYD3rQlw
PPS. By the way, how should I detect the phone when connected in download mode in the device manager? I'm unsure of what to look for there.