[Q] MIUI , what if ... - Samsung Infuse 4G

Hi guys
I would appreciate if someone [dev] can give me some answers on this ...
Now that we have full CWM , thanks to the devs [@gtg465x]
How about following instructions to flash lastest MIUI for Galaxy S I9000 , using the actual installation guide > http://j.mp/iZSjlh , and try this ROM on the Infuse
Is the Galaxy S I9000 the closest phone [specs] we can have to try this ?
Some step(s) in that guide to be replaced or skipped ?
Worth to try it?
Would it work ?
Would I brick the phone?
I if brick it , would I still be able to un-brick using ODIN [back to factory]
TIA

pvillasuso said:
Hi guys
I would appreciate if someone [dev] can give me some answers on this ...
Now that we have full CWM , thanks to the devs [@gtg465x]
How about following instructions to flash lastest MIUI for Galaxy S I9000 , using the actual installation guide > http://j.mp/iZSjlh , and try this ROM on the Infuse
Is the Galaxy S I9000 the closest phone [specs] we can have to try this ?
Some step(s) in that guide to be replaced or skipped ?
Worth to try it?
Would it work ?
Would I brick the phone?
I if brick it , would I still be able to un-brick using ODIN [back to factory]
TIA
Click to expand...
Click to collapse
Would be very interested in this as well, but not enough to try bricking my phone .

I wouldn't try it.
Just because the partition layout of the original Galaxy S is the same as our device, it does not mean the kernel is compatible.
The current roms are all based on the stock kernel and do not change any of the core of how the device works. We still have TouchWiz built in and won't be changing that until we have custom kernel built and working on this device.
On the other hand, we can flash back to stock with Odin, so you won't completely fubar your phone if you try.

knight4led said:
I wouldn't try it.
Just because the partition layout of the original Galaxy S is the same as our device, it does not mean the kernel is compatible.
The current roms are all based on the stock kernel and do not change any of the core of how the device works. We still have TouchWiz built in and won't be changing that until we have custom kernel built and working on this device.
On the other hand, we can flash back to stock with Odin, so you won't completely fubar your phone if you try.
Click to expand...
Click to collapse
Your right about kernel compatibility , so 1st step not using speedmod kernel [used @ guide]
But I would like to know if the native MIUI kernel used @ the galaxy S is like a "modded kernel" they used to port that rom .. or if its a kind of "universal kernel" ?? . I dont know if Im making myself clear

knight4led said:
I wouldn't try it.
Just because the partition layout of the original Galaxy S is the same as our device, it does not mean the kernel is compatible.
The current roms are all based on the stock kernel and do not change any of the core of how the device works. We still have TouchWiz built in and won't be changing that until we have custom kernel built and working on this device.
On the other hand, we can flash back to stock with Odin, so you won't completely fubar your phone if you try.
Click to expand...
Click to collapse
If the partition layout changes, cannot promise Odin will fix it. Pit, boot.bin and sbl.bin pulled from a phone to flash will most likely cause a hard brick. We need a leaked one-click, or some very crazy testers willing to brick phones left and right to test that. I don't recommend it.
Sent from my SAMSUNG-SGH-I997 using XDA App

h8rift said:
If the partition layout changes, cannot promise Odin will fix it. Pit, boot.bin and sbl.bin pulled from a phone to flash will most likely cause a hard brick. We need a leaked one-click, or some very crazy testers willing to brick phones left and right to test that. I don't recommend it.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
Thanks for that information , exactly what I wanted to read ...
Time to close this thread [MODS please] , and wait for someone who can make this happen !

pvillasuso said:
Thanks for that information , exactly what I wanted to read ...
Time to close this thread [MODS please] , and wait for someone who can make this happen !
Click to expand...
Click to collapse
Not a problem. When a new phone comes out....here's what happens:
1. Root
2. SBF/ODIN
3. CWM recovery
4. Psuedo ROMs based on stock.
5. Source Code drops.
6. Custom kernels (w/CWM built in)
7. Ports for MIUI/CM7/Sense/etc.
In 3 weeks, the community as a whole has completely done steps 1-5. (Usually takes a couple of months).
Next big focus has to be custom kernels. I helped out with some of the initial stuff for CM7 on Captivate before I bought an Atrix, then the Infuse. I'm going to be doing alot of reading and trying to learn alot more about git. Then I will be able to look into kernels. Team Whiskey had some guys working on a kernel with CWM + VooDoo lagfix written up...but I havent heard anything in a few days. So....be patient, its coming! .
Sent from my SAMSUNG-SGH-I997 using XDA App

h8rift said:
Not a problem. When a new phone comes out....here's what happens:
1. Root
2. SBF/ODIN
3. CWM recovery
4. Psuedo ROMs based on stock.
5. Source Code drops.
6. Custom kernels (w/CWM built in)
7. Ports for MIUI/CM7/Sense/etc.
In 3 weeks, the community as a whole has completely done steps 1-5. (Usually takes a couple of months).
Next big focus has to be custom kernels. I helped out with some of the initial stuff for CM7 on Captivate before I bought an Atrix, then the Infuse. I'm going to be doing alot of reading and trying to learn alot more about git. Then I will be able to look into kernels. Team Whiskey had some guys working on a kernel with CWM + VooDoo lagfix written up...but I havent heard anything in a few days. So....be patient, its coming! .
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
You are indeed one of the MAN, I speak for my self thanks dude
Sent from my SAMSUNG-SGH-I997 using XDA Premium App

h8rift said:
When a new phone comes out....here's what happens:
1. Root
2. SBF/ODIN
3. CWM recovery
4. Psuedo ROMs based on stock.
5. Source Code drops.
6. Custom kernels (w/CWM built in)
7. Ports for MIUI/CM7/Sense/etc.
Click to expand...
Click to collapse
Very interesting info , thanks for sharing , didn't know the order of these steps to follow ..
We are closer then ! cool , cant wait to run MIUI @ Infuse

Like others said, we will need a custom kernel for MIUI. However, the Infuse is very similar to the original Galaxy S. I bet it would be really easy to port 2.2.1 Galaxy S ROMs. They would probably boot right up and work fine if you just remove the kernel from them and swap out a few files (ril, camera libs, key layouts).

gtg465x said:
Like others said, we will need a custom kernel for MIUI. However, the Infuse is very similar to the original Galaxy S. I bet it would be really easy to port 2.2.1 Galaxy S ROMs. They would probably boot right up and work fine if you just remove the kernel from them and swap out a few files (ril, camera libs, key layouts).
Click to expand...
Click to collapse
Hey I have one theme in mind, can you give me the details of these files?
(Wait do themes even mess with these files?)
Key layouts I got...
Camera libs? where are those located?
ril? what is that and where?
Thanks much appreciated.
-Ken

slider2828 said:
Hey I have one theme in mind, can you give me the details of these files?
(Wait do themes even mess with these files?)
Key layouts I got...
Camera libs? where are those located?
ril? what is that and where?
Thanks much appreciated.
-Ken
Click to expand...
Click to collapse
I'm used to HTC devices so I can't tell you the exact names of the ril and camera libs on a Samsung device without looking, but they will be in /system/lib. You may also have to swap a few files in /system/etc. Just takes research and then trial and error. I suggest grabbing a GS 2.2.1 ROM, removing the kernal (and modem if that's included) (will have to remove corresponding parts of updater-script as well), and then flashing. Adb logcat will help you to debug and fix issues from there.

Hell id donate an InFuSe to a miui dev that would make it happen!
I run miui on my Desire HD and wont use anything else, ever...
Sent from my SAMSUNG InFuSe using XDA Premium App

Once we get kernel source and a working CM7 build for it, my team is able to port MIUI to it
Well... once we get a device that is
We have been looking for a new device to port MIUI to. If there is enough demand for the Infuse 4G we'll pick one up.
If you guys manage to get it ported we'll create a device forum for you and host your roms, etc. If you need porting help/advice, or just want to talk about MIUI, join our IRC channel #miui-us on Freenode (details in my signature) and look for someone with a + in front of their name (those are the developers).
Anyway, hope to see you guys running MIUI soon!

Now this is what im talking about. If you guys have stuff to test ill snag it up and try it. Cant write but I can install it and test for ya. Not really scared to brick it. Plus its insured. Anyway good luck cant wait for it!!!
Sent from my SAMSUNG-SGH-I997 using XDA App

Are there any good guides/articles to learning how to create custom roms and whatnot?
I'm a software developer and while I've never done anything related to kernals/operating systems normally I'm able to pick up stuff quick and I think learning about stuff like this for Android phones would be awesome. I just really have no idea where to start at.

Frooty said:
Are there any good guides/articles to learning how to create custom roms and whatnot?
I'm a software developer and while I've never done anything related to kernals/operating systems normally I'm able to pick up stuff quick and I think learning about stuff like this for Android phones would be awesome. I just really have no idea where to start at.
Click to expand...
Click to collapse
Unfortunately...that is why there aren't more devs around. No docs. Its all trial and error...especially kernels.
Sent from my SAMSUNG-SGH-I997 using XDA App

Just keep trying you can unbrick anyway with dev gtg465x ultimate unbrick procedure so it is safe, just don't drop the Indie on water,
Sent from my SAMSUNG-SGH-I997 using XDA Premium App

h8rift said:
Unfortunately...that is why there aren't more devs around. No docs. Its all trial and error...especially kernels.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
Would you or one of the other devs be willing to post an intro guide or something in order to help get more developers here?
I know you guys are probably busy working on your roms as well as work/school/doing other things, but it probably wouldn't take too long to make a short intro to help us get started. That way we could hopefully get some more devs around here.
I've been reading others guides and posts about it and I could probably do at least a little work from the start based on what they say is involved in making a rom, but the biggest problem for me is not knowing how to get going. It seems like you need an android kitchen to do a lot of the work but all of the kitchens look like they are phone specific so I don't want to try using one if those on the infuse. Maybe they aren't, but info like that to help us get our feet wet would be extremely helpful.
Sent from my SAMSUNG-SGH-I997 using XDA App

Frooty said:
Would you or one of the other devs be willing to post an intro guide or something in order to help get more developers here?
I know you guys are probably busy working on your roms as well as work/school/doing other things, but it probably wouldn't take too long to make a short intro to help us get started. That way we could hopefully get some more devs around here.
I've been reading others guides and posts about it and I could probably do at least a little work from the start based on what they say is involved in making a rom, but the biggest problem for me is not knowing how to get going. It seems like you need an android kitchen to do a lot of the work but all of the kitchens look like they are phone specific so I don't want to try using one if those on the infuse. Maybe they aren't, but info like that to help us get our feet wet would be extremely helpful.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
I'm with ya. I've got some free time and would be happy to help in anyway.
Sent from Samy Infuse

Related

Porting CM7 Need Help

Looking for someone to help me comb through all the differences in the CM7 build compared to KD1 and move on to getting it packaged and ready for testing. I have edited the Framework classes.dex file but the rom still needs other items changed as it will get stuck at the Samsung Galaxy S4G boot screen. If anyone is up to take the challenge PM me so we can get started.
Bump
sent from MT. OLYMPUS using my kickass sgs4g.
THE GODS ENVY US!!!!!!!!!
Rebuilt the package again, still having a soft brick. Its either the kernel or permissions. Im working with mad_fitter atm do see if I can work out the debug. I can say there is major differences between these two.
Probably because of the libraries. Also you need a gingerbread kernel. May try porting the vibrant cm7 kernel. That should solve your soft brick
Sent from my SGH-T959V using XDA App
dynamicj said:
Looking for someone to help me comb through all the differences in the CM7 build compared to KD1 and move on to getting it packaged and ready for testing. I have edited the Framework classes.dex file but the rom still needs other items changed as it will get stuck at the Samsung Galaxy S4G boot screen. If anyone is up to take the challenge PM me so we can get started.
Click to expand...
Click to collapse
You will have 999999x more luck trying to actually grab the Vibrant CM7 and porting it over.
What you're trying to do is put 2.3 into 2.2, while mixing AOSP with TouchWiz. That's a recipe for very bad things and lots of wasted time.
I agree with you. I have no clue on a port though. I've never attempted one.
sent from the pits of hell (from an sgs4g)
Thats exactly what im doing I have the CM7 Vibrant source, I have edited the files needed for the mounts. Currently still getting a softbrick. Im trying a different GB source atm because its getting a kernel panic.
Oh awesome. Damn son, your all over this!
sent from the pits of hell (from an sgs4g)
I will help any way I can for a GB port! Let me know!
dynamicj said:
Looking for someone to help me comb through all the differences in the CM7 build compared to KD1 and move on to getting it packaged and ready for testing. I have edited the Framework classes.dex file but the rom still needs other items changed as it will get stuck at the Samsung Galaxy S4G boot screen. If anyone is up to take the challenge PM me so we can get started.
Click to expand...
Click to collapse
u cant port cm7... i had tried to when working on ports initially, and it has to do with the filesystem... but more power to u if u figure it out... i softbricked all over the place....
badb4lyfe said:
u cant port cm7... i had tried to when working on ports initially, and it has to do with the filesystem... but more power to u if u figure it out... i softbricked all over the place....
Click to expand...
Click to collapse
Pretty much noticed that as I dug into this more but I believe it will work with the correct kernel. I have moved to trying another GB source and will report back what comes about with it.
You tried even when it was figured out how to flash roms? Its a lil different now.
Im trying this on my daily driver so this is a little slow. I wish I had a extra to mess with . Anyways still the same issues even with the same mounts as posted in other threads. Still looking into the problem.
It shows a fix for the mounts and permissions though. Tried that yet?
I did both. I am giving you links for the Device State and Logcat hopefully someone with a little more knowledge can look it over and point me to the right direction here.
www.dynamicproservices.com/ds.txt
www.dynamicproservices.com/logcat.txt
Thanks again for the help guys!
dynamicj said:
I did both. I am giving you links for the Device State and Logcat hopefully someone with a little more knowledge can look it over and point me to the right direction here.
www.dynamicproservices.com/ds.txt
www.dynamicproservices.com/logcat.txt
Thanks again for the help guys!
Click to expand...
Click to collapse
From looking at the device state, a lot of the java isn't working out (obviously), and also look at line #06-10 21:29:28.208. This tells me that the file system (or parts of it) that your are using is for another device.
Specifically here: ALSALib device/samsung/GT-I9000/alsa-lib/src/control/setup.c:565:
I've never attempted a port with a samsung (hell I've only had mine a little over a week), But there is a thread in this dev section about porting vibrant roms to this device. Did you look over that? A lot of this seems to be related to what I read there.
I did follow that to a T and a few others. I dont think the device name is much of a issue atm. Its the permissions and vm not working correctly.
I also noticed alot of Data permission errors in adb as well as not being able to access anything with SU even with superuser installed and SU in the system as well. Hopefully someone can hop on board with this and help me figure this out.
Ya good call. I'm afraid that in this department I'm not much help. The errors are definitely a familiar one, but I can't think of an explanation except for permissions and java. Seems a lot of folks are having the same kind of issues.
mad_fitter said:
Specifically here: ALSALib device/samsung/GT-I9000/alsa-lib/src/control/setup.c:565:
Click to expand...
Click to collapse
That's because the Vibrant CM7 was ported from Galaxy S - aka I9000.
So you're trying to port a port. By the way, they have all but given up on porting CM7 to the Vibrant last I looked. I just sold my Vibrant about a week ago and I would flash the nightlies as new ones were released. Although they were getting close there were still major issues with them.
My advice... accept the fact that gingerbread will not happen on this phone. But if you're one of those who refuse to accept defeat... much luck in your endeavors! Because ginger love would be amazing.
That is not cm7 as stated earlier but it is a port from a vibrant and cm7 has a few problems mainly it looks like gps which has had issues on most of these Samsung phones.
If someone knows more on the problem please post it so i can.correct them.
Sent from my SGH-T959V using XDA App

ROM Manager 4.7.0.5 Support for Samsung Galaxy S4G (T959V)

Hi All,
I have a Samsung Galaxy S4G(T959V) phone and planning to install a Cyanogenmod 7.1 . I have installed the ROM Manager 4.7.0.5 from market and trying to install the CWM Flash Recovery. When i click on CWM Flash Recovery it is prompting me to enter my Mobile model and i get the following Options - Google Nexus S, Google Nexus S 4G, Samsung GalaxyS i9000, Samsung GalaxyS i9000 (MTD). I am not seeing the T959V model here. I would like to know whether Cyanogenmod 7.1 is supported on Galaxy S 4G. Please let me know.
- Venkat
It's not.
Sent from my SGH-T959V using xda premium
You'll probably boot loop if you flash a ROM like that. Try reading the Bible in-depth before you end up causing a hard brick.
MOD EDIT: ENOUGH
Omfg. I give up on this forum
Sent from my SGH-T959V using xda premium
jager555 said:
Omfg. I give up on this forum
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
*pats your shoulder*
It's okay man. There's plenty more to live for! LOL!
Seriously, under the stickies thread, under the 10 commandments, the second item states not to use ROM manager from the market. You need to flash a kernel with CWM. A 2 second search in this forum will tell you what you need to do. Try FB's guide to gingerbread or just the noobs guide to flashing. Follow the instructions exactly and you will be fine.
Sent from my SGH-T959V using XDA App
MOD EDIT: ENOUGH
MOD EDIT: ENOUGH
I did flash my rom as a vibrant.so wtf can i do more. i get arisk but works.the problem is after flash i scared to install rom from rom maneger.so if someone did befor please tell us.sorry about language.
SGS4G
kernel:2.6.35.7-t959vuvki3-cl611444
GB2.3.5
rom:ice octain
venkatgg said:
Hi All,
I have a Samsung Galaxy S4G(T959V) phone and planning to install a Cyanogenmod 7.1 . I have installed the ROM Manager 4.7.0.5 from market and trying to install the CWM Flash Recovery. When i click on CWM Flash Recovery it is prompting me to enter my Mobile model and i get the following Options - Google Nexus S, Google Nexus S 4G, Samsung GalaxyS i9000, Samsung GalaxyS i9000 (MTD). I am not seeing the T959V model here. I would like to know whether Cyanogenmod 7.1 is supported on Galaxy S 4G. Please let me know.
- Venkat
Click to expand...
Click to collapse
funny thing is that i posted a thread that actually got STICKIED in THIS section which can be found here. but i guess people just don't understand.
MOD EDIT: ENOUGH
MOD EDIT: ENOUGH
MOD EDIT: ENOUGH
MOD EDIT: ENOUGH
on topic no rom manager doesnt work with this phone id uninstall it fast please use kryons cwm final if you need to get out of froyo... and into another rom at least tell u flash a gb rom or froyo rom ( your choice really) and get a kernel that has cwm built inside it
as far as cm7 goes without source to the kernel were dead in the water or tell we work around it which ever comes first if you have any questions feel free to ask also remember to check out the sgs4g bible and any of the how to threads and just read and get informed on what your doing to your device ... Good luck and happy flashing...
Well, I have to say, I'm absolutely appalled at some of the responses in this thread.
The OP is obviously a fairly new member, so how about being helpful instead of being a bunch of assholes.
Time to start handing out infractions and possibly a ban. There's simply NO NEED for the smart ass offensive posts.
the_scotsman said:
Well, I have to say, I'm absolutely appalled at some of the responses in this thread.
The OP is obviously a fairly new member, so how about being helpful instead of being a bunch of assholes.
Time to start handing out infractions and possibly a ban. There's simply NO NEED for the smart ass offensive posts.
Click to expand...
Click to collapse
I agree.
The reason to not use CwM from Rom Manager is that the device tree for the galaxys4g is not complete. It doesn't have voodoo-lagfix, or the mods it takes to run a stock or modded rom:
https://github.com/CyanogenMod/android_device_samsung_galaxys4g
If you want CwM, please follow the instructions here or here.
Also, from what I understand, a majority of the devs working on SGS4G dislike using CyanogenMod. So I wouldn't expect that stuff to work anytime soon.
bhundven said:
I agree.
The reason to not use CwM from Rom Manager is that the device tree for the galaxys4g is not complete. It doesn't have voodoo-lagfix, or the mods it takes to run a stock or modded rom:
https://github.com/CyanogenMod/android_device_samsung_galaxys4g
If you want CwM, please follow the instructions here or here.
Also, from what I understand, a majority of the devs working on SGS4G dislike using CyanogenMod. So I wouldn't expect that stuff to work anytime soon.
Click to expand...
Click to collapse
wrong
wrong
wrong
THe reason rom manger does not support the sgs4g is not that its not complete is the fact the device structure is diffrent then all the other samsung devices diffrent mount pont system stl110 blocks vs mmc blocking that the other roms use. the swapped parttion info. no interal sd card mapping so on so forth..
THe device does have voodoo lag fix... NOt sure where you are getting this info from but 99.99 percent of the roms have lag fix aka ext 4 support in the kernel once again wrong please post correct info..
as far as cwm goes the lack of gingerbread sourcecode is whats holding it up not the devs... Once samsung releases gb and the sourcecode you will see cm7 and more asop roms as we will be able to actually run custom kernels....
the devs here are not against it we just cant control what Samsung does....
RaverX3X said:
wrong
wrong
wrong
Click to expand...
Click to collapse
Really?
RaverX3X said:
THe reason rom manger does not support the sgs4g is not that its not complete is the fact the device structure is diffrent then all the other samsung devices diffrent mount pont system stl110 blocks vs mmc blocking that the other roms use. the swapped parttion info. no interal sd card mapping so on so forth..
Click to expand...
Click to collapse
The bml/stl devices come from the XSR/FSR driver.
If we had GB source, or if we go back to FY source, we could remove this driver and configure mtd block devices. But I don't think you want to move to yaffs2, or god forbid, jffs2.
The mount points are different, because the sgs4g, unlike the other sgs devices does not have internal sd.
RaverX3X said:
THe device does have voodoo lag fix... NOt sure where you are getting this info from but 99.99 percent of the roms have lag fix aka ext 4 support in the kernel once again wrong please post correct info..
Click to expand...
Click to collapse
The recovery has voodoo-lagfix(ext4), not the device.
If we moved to mtd instead of XSR/FSR, we wouldn't need voodoo-lagfix, but we would have to worry about the performance drop of moving to yaffs2.
RaverX3X said:
as far as cwm goes the lack of gingerbread sourcecode is whats holding it up not the devs... Once samsung releases gb and the sourcecode you will see cm7 and more asop roms as we will be able to actually run custom kernels....
Click to expand...
Click to collapse
Yup. I am a kernel dev. Not for android, but for embedded linux. I'm still learning android, but I understand how MTD block devices work, I just need some help when it comes to XSR/FSR.
Lashing out at me with your 'holier then thou' bit is lame.
I refuse to do it to you.
Please talk to me (and the community) like a person.
---------- Post added at 04:35 PM ---------- Previous post was at 04:24 PM ----------
btw, I'd suggest going and looking at the repo link I posted, and looking at the recovery.fstab
Tell me where you see mtdblock* in there.

(Q) best development at&t phone ?

What current phone under at&t has the most developing going on?
I upgraded from my Xperia x10 which had awesome development to the atrix 2 and the dev scene is not great .I'm a flashaholic and love changing my phone up so I'm considering buying a new one.question is which one?
Sent from my MB865 using XDA App
rdavisct said:
What current phone under at&t has the most developing going on?
I upgraded from my Xperia x10 which had awesome development to the atrix 2 and the dev scene is not great .I'm a flashaholic and love changing my phone up so I'm considering buying a new one.question is which one?
Sent from my MB865 using XDA App
Click to expand...
Click to collapse
HTC inspire has pretty good development going on. I have that phone besidesthe ATRIX 2. Im a flashaholic too and I flash like crazy on that phone waiting and hoping development picks up for this phone! Kinda upset I got rid of my of ATRIX. Cause now a lot of development is goin on for that too.
The Inspire is old, though.
Douchewithaphone said:
The Inspire is old, though.
Click to expand...
Click to collapse
Im pretty sure the phones with the BEST development and going to be kinda old...
My vote would be either the international SGSII or one of its variants (I have i777 and things always seem to be booming over there).
Go get a Samsung phone, whichever is the latest one that AT&T has. They always have a TON of developers.
You know on the other hand you could just put in some time and learn and get some great ROMs in the process, lfaber06, cogery, and myself could really use the help, and it really is not all that hard, if you know anything about phones and flashing, and some about computers.
There is a thread in the development section on the tools needed to do this.
jimbridgman said:
Go get a Samsung phone, whichever is the latest one that AT&T has. They always have a TON of developers.
You know on the other hand you could just put in some time and learn and get some great ROMs in the process, lfaber06, cogery, and myself could really use the help, and it really is not all that hard, if you know anything about phones and flashing, and some about computers.
There is a thread in the development section on the tools needed to do this.
Click to expand...
Click to collapse
I would love to learn more about development, but at 52 it's all a bit overwhelming at times. I may have to find something in the 250.00 dollar range and try though.
jimbridgman said:
Go get a Samsung phone, whichever is the latest one that AT&T has. They always have a TON of developers.
You know on the other hand you could just put in some time and learn and get some great ROMs in the process, lfaber06, cogery, and myself could really use the help, and it really is not all that hard, if you know anything about phones and flashing, and some about computers.
There is a thread in the development section on the tools needed to do this.
Click to expand...
Click to collapse
I am considering it greatly .I'm going to start reading up on it.i am skilled in Photoshop and have no problems Modding/theming roms.pretty much anything graphical .i posted some mods past couple days in the themes section.but it ends there . Creating actual roms or porting i need to research,I'd love to contribute so ill look into tonight when home .
Sent from my MB865 using XDA App
rdavisct said:
I am considering it greatly .I'm going to start reading up on it.i am skilled in Photoshop and have no problems Modding/theming roms.pretty much anything graphical .i posted some mods past couple days in the themes section.but it ends there . Creating actual roms or porting i need to research,I'd love to contribute so ill look into tonight when home .
Sent from my MB865 using XDA App
Click to expand...
Click to collapse
BTW here is the link on the toold needed to build ROMs for our phone:
http://forum.xda-developers.com/showthread.php?t=1404442
And if you think you are up for it, sound off in the link below, then PM lfaber06 and I, we are collecting people to help with some dev work, and are going to make some task assignments in the next couple weeks:
http://forum.xda-developers.com/showthread.php?t=1428117
jimbridgman said:
BTW here is the link on the toold needed to build ROMs for our phone:
http://forum.xda-developers.com/showthread.php?t=1404442
And if you think you are up for it, sound off in the link below, then PM lfaber06 and I, we are collecting people to help with some dev work, and are going to make some task assignments in the next couple weeks:
http://forum.xda-developers.com/showthread.php?t=1428117
Click to expand...
Click to collapse
I have a question .hope u can help.i cooked a rom with kitchenbfrom stock 2.3.6 rooted as base but when i make a flashable zip and try n install it ,it says "error code 0" any suggestions? I used updater-script for cwm since i know update script isn't capatible.
Sent from my MB865 using XDA App
rdavisct said:
I have a question .hope u can help.i cooked a rom with kitchenbfrom stock 2.3.6 rooted as base but when i make a flashable zip and try n install it ,it says "error code 0" any suggestions? I used updater-script for cwm since i know update script isn't capatible.
Sent from my MB865 using XDA App
Click to expand...
Click to collapse
I replied to your PM with everything you need to do...

Custom ROMs

Hello all,
Has there been any word on any custom ROMs for this device? Things like MIUI, Cyanogenmod, for example. I wonder if maybe the ROM developers are waiting for official 7+ ICS builds to be available. Anyway, just wanted to check and make sure I'm not missing anything. Thanks!
Sent from my Droid Incredible using XDA App
Hello
i am going to be working on a custom ROM based on stock very soon but i think im the only one as not a lot of people see a point on working on honeycomb as ICS may be available in Q2 but we are not 100% sure as of yet.
and yes you are correct about the matter on waiting for the official ICS update but its also a matter of retrieving the sauce codes from Samsung inc. they seem determined not the share them with the public as they have made an ICS based tab similar to our tab in appearance but totally different as far as the hardware is concerned. The new Samsung galaxy tab 2 it a low grade tab with extreme affordability allowing everyone to taste the sweet ICS within haha
but now Google are saying their is a new version of android coming some time this year called android 5.0 jellybean so that may even boost the development on our device as everyone will be wanting some jellybeans in the tab + haha
kindest regards Joseph Marshall
If you need/want any assistance when you start working on that please let me know, even if you just need a tester.
Sent from my Droid Incredible using XDA App
LauraSakura said:
If you need/want any assistance when you start working on that please let me know, even if you just need a tester.
Sent from my Droid Incredible using XDA App
Click to expand...
Click to collapse
thanks very much i have added a thanks to your thanks meter
MIUI and CM7 are both Android2.3 based (definitely not including MIUI v4), we already get superior firmwares.
Actually most custom roms are just modifications of the official firmware. There is only 1 feature I want and the official does not provide. Just to remove items in the recent task list by swiping/clicking X.
Galaxy tab 7.7 ROMS
Has anybody tried to flash one of the galaxy tab 7.7 roms? I think they have about 3 roms over there. It seems as if they're almost identical in hardware, probably the only difference is the screen size.
i tried flashing entire /framework folder and a lot of system apks. bootloop
then I tried flashing only phone and settings .apk, booted but wouldnt open FC.
p6200 Malaysia.
They would need to be ported over. I kind of remember how to do it with an HTC device (EVO and Incredible had almost the exact same hardware) but Samsung I'm not sure of. Need the Android kitchen up and running on your pc to do it. With an HTC device it was pretty much just taking the boot img file off the device with the ROM you want to port and putting it into the other device. There were step by step instructions somewhere on here but I can't find them.
No thanks, not putting anyones boot.img on my device. I'm sure it could be ported. Ive been checking them out, and they are very similar.
I do have dsixdas kitchen. But Im busy with other things at the moment.
i'm playing around with 7.7 touchwiz... because they can delete the unused page... and we cant... wth samsung... want to see what is the different with their version and ours...
edan1979 said:
i'm playing around with 7.7 touchwiz... because they can delete the unused page... and we cant... wth samsung... want to see what is the different with their version and ours...
Click to expand...
Click to collapse
will you be happy to port a rom? i will back u up man
---------- Post added at 05:50 AM ---------- Previous post was at 05:24 AM ----------
kzoodroid said:
They would need to be ported over. I kind of remember how to do it with an HTC device (EVO and Incredible had almost the exact same hardware) but Samsung I'm not sure of. Need the Android kitchen up and running on your pc to do it. With an HTC device it was pretty much just taking the boot img file off the device with the ROM you want to port and putting it into the other device. There were step by step instructions somewhere on here but I can't find them.
Click to expand...
Click to collapse
can u not give it a go at porting the rom over we would all love 2 see ics running on p6200
jmar8124 said:
will you be happy to port a rom? i will back u up man
---------- Post added at 05:50 AM ---------- Previous post was at 05:24 AM ----------
can u not give it a go at porting the rom over we would all love 2 see ics running on p6200
Click to expand...
Click to collapse
For ICS to run on our tabs you would need an ICS kernel, I don't believe the current one will work. My Incredible had to use an EVO ICS kernel in order to use an ICS ROM. The kernel from the 7.7 could be modified since they have similar hardware but I believe you have to have the source code available to do it. I also do not know how to make kernels though there is a tutorial on xda somewhere.
I am also not familar with the my tab or Samsungs software architecture enough to experiment with mine just yet. The only way I know how to make ROMs is using a ROM.zip file found in an RUU, you can use a nandroid backup but they tend to be buggy. The android kitchen pulls the needed images (boot, system, recovery) out of the ROM.zip file (or nandroid backup) to use in building ROMs.
I would suggest that anyone who really wants ROMs for this thing head over to Chef Central on XDA and start learning how to do it themselves. It took me the better part of a day getting the andoid kitchen up and running on my windows laptop and it is a good learning experience. There is a step by step tutoirial on how to get the andoid kitchen installed and how to build roms.
Chef Central link:
http://forum.xda-developers.com/forumdisplay.php?f=613
edan1979 said:
i'm playing around with 7.7 touchwiz... because they can delete the unused page... and we cant... wth samsung... want to see what is the different with their version and ours...
Click to expand...
Click to collapse
Please let us know and change our TouchWiz... to me, there's a lot of unused page of home screen.
Thanks.
jmar8124 said:
will you be happy to port a rom? i will back u up man
Click to expand...
Click to collapse
only can playing around with simple thing... no source code... kind of hard... my day job already killing me...
Yeah, I've got the kitchen running on an Ubuntu VM on my PC. I've only used it for my inc though. I guess what I hadn't realized was that Samsung never released the code for our device. Its a shame, I wish I would have looked that up before I decided on this tab. Do any other Samsung devices have similar architecture, besides the already mentioned 7.7?
Sent from my Droid Incredible using XDA App
LauraSakura said:
I guess what I hadn't realized was that Samsung never released the code for our device. Its a shame, I wish I would have looked that up before I decided on this tab.
Sent from my Droid Incredible using XDA App
Click to expand...
Click to collapse
i feel like i made the exact same mistake. has samsung ever released source codes due to owners demanding it? i know they don't have much reason to do so, but i was just wondering if it's happened in the past before.
foliage green said:
i feel like i made the exact same mistake. has samsung ever released source codes due to owners demanding it? i know they don't have much reason to do so, but i was just wondering if it's happened in the past before.
Click to expand...
Click to collapse
I would love to know the answer to that as well..
Sent from my Incredible using Tapatalk
LauraSakura said:
I would love to know the answer to that as well..
Sent from my Incredible using Tapatalk
Click to expand...
Click to collapse
ye and me....
i think peolpe are worrying to much about this device and i do know that a honeycomb rom can be made but no one will even attempt it its pathetic
oh well il be trying it soon super joe to the rescue haha....

Hacks for WIND Mobile Samsung Galaxy S 4G?

I picked up a WIND Samsung Galaxy S 4G today. I looked in the Android Dev thread here and I don't see anything specifically for this phone.
The model number is T-959W so I don't want to try anything with hacks/roms etc meant for the T-Mobile version.
I'd be happy to supply a dump of my phone for any devs who want to play around and help us here in the great white north!
Thanks
System dump would be nice if you can provide it. I'd advice against installing any mods you found here. Good thing you're cautious
Great, thanks! I have never done a dump before so I'll have to look into how to do it. I will let you know when I do.
I see it has 8 gig internal, we only got 2 there's a tutorial somewhere for system dumps, let me find you the link.
You need to be rooted I believe.
m.youtube.com/#/watch?desktop_uri=/watch?v=UWs6PKnDtFk&v=UWs6PKnDtFk&gl=US
Sent from my SPH-D710 using Tapatalk
Source files found
I found the following source files from opensource.samsung.com
SGH-T959W_NA_Opensource.zip
SGH-T959W_NA_GB_Opensource.zip
Will these help XDA with support for the Wind SGS4G?
Sure but idk if our devs are gonna build you guys stuff. Also, go to sampro.pl, it is a polish site so use Google chrome to translate it, then create an account for the site, go firmware downloads for your model if you see. If you do, then post a link to the latest version.
Sent from my SGH-T959V using xda premium
959w was not listed on the site (did not register).
Sent from my SGH-T959W using xda app-developers app
Imaging phone
I have heard that there may be an update in August. It may be prudent to wait for this update before capturing a ROM image, in case important fixes are made.
I guess a good question would be whether anyone has had any experience flashing T-Mobile SGH-959v ROMs on to this device.
Another avenue could be to ask someone inside Samsung whether they changed much between models.
bminuk said:
I found the following source files from opensource.samsung.com
SGH-T959W_NA_Opensource.zip
SGH-T959W_NA_GB_Opensource.zip
Will these help XDA with support for the Wind SGS4G?
Click to expand...
Click to collapse
Absolutely! I'm currently taking a little break (gotta find a job... like two weeks ago.), but when the dust settles, I'll take a little look at the source and see if we can help out.
What you could start with is a diff between the SGH-T959V-TMB_GB_Opensource.zip and the SGH-T959W_NA_GB_Opensource.zip drops.
I'd be willing to look into giving you guys something fun to work with.
I'll do a series of diffs tonight on the T959W stock kernel source and the T959V sources (stock and our CM kernel).
I have Telus S4G, which is T959P. However I've never had a problem using T959V roms,
Sent from my SGH-T959V using xda app-developers app
Another potential problem
I have been hearing on the web (in these forums and on the SuperOneClick page) that the 959W is not being successfully rooted in the usual ways. Has anyone had luck with this?
endee said:
I have Telus S4G, which is T959P. However I've never had a problem using T959V roms,
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
You really shouldn't flash roms not made for your phone. If they contain bootloaders, you could brick your phone.
Hey T959W people. Looked at the source and things are looking pretty close. I'm not saying to run off and flash our stuff, but I need some info and someone with the big kahunas to try flashing some stuff.
Please be running linux. I can't help you with windows problems.
It would also be helpful if you have a usb download mode jig.
You can get one here:
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-download-mode-jig/
Ok Canadians! I've verified that the SGH-T959W should be exactly the same as the SGH-T959V.
There were some interesting differences between our T959V and T959W that may fix some bugs for us on T959V.
With that said, please... please... please, read all of the instructions for flashing ROMs and Kernels very carefully!
If the rom contains bootloaders, please DO NOT flash them until we can confirm there are no bootloader differences.
Like I said before, it is very common to soft brick your device. It is not the end, and do not worry if you do this. Make sure you get yourself a usb download mode jig here:
bhundven said:
You can get one here:
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-download-mode-jig/
Click to expand...
Click to collapse
This will help you use heimdall or odin to flash stuff to your phone to make everything happy again.
You will only hard brick this device by writing the wrong bootloaders to the phone, which is why I am warning you to not flash bootloaders, for now!
With that, enjoy cm7, cm9, aokp, et alii!
I will also announce this in the android general forum!
http://forum.xda-developers.com/showthread.php?t=1764298
I managed to get my Wind SGH-T959W rooted and up and running with a unofficial CM9 build, but it took a bit of work.
Firstly, I tried just about every one-click solution out there, to no avail. It's possible SOC 1.7 with rattlethecage works, but I didn't have the patience to find out whether I simply had to wait a bit longer.
I followed this guide(whilst clenching every clenchable muscle I could consciously control):
http://www.galaxyforums.net/forum/o...mission-t-mobile-galaxy-s-4g-gingerbread.html
The gist is, Odin 1.7, stock+voodoo for T959V, plus some update that I'm not qualified to describe. That should get you rooted and if that's all you're looking for, you'll have to suffer through a little T-Mobile branding on startup.
Once you got it all rooted, you'd think it'd be a good idea to toss sgs-ics on there, right? Well, no. After installing the 4G variant, it promptly set off into a boot loop which I'm again, unqualified to diagnose. The obvious solution was to try another team's version of ICS, which I indeed found here:
http://forum.xda-developers.com/showthread.php?t=1730954
Barring some missing features, it sounds like a good alternative to sgs-ics. Though I had to go through one additional step, which I really, honestly assure you I was under-qualified to execute. When I tried to load Team Acid's CM9 r3 it gave me an assert on the updater-script, since the hardware didn't match up. Easy. Unzip the package, open up META-INF/com/google/android/updater-script, remove the first check. You know it's the same hardware, you don't need some stinkin' script to tell you it won't work.
So all said and done, I now have a Wind Mobile SGH-T959W running ICS 4.0.4 courtesy of bhundven, the Odin folks, Team Acid, and likely a slew of other contributors.
Thanks folks, and enjoy!
PS, if you want that tarball bhundven, send me a PM with some brief instructions, and hopefully you can help my fellow Winders.
Derpopotamus said:
I managed to get my Wind SGH-T959W rooted and up and running with a unofficial CM9 build, but it took a bit of work.
Click to expand...
Click to collapse
Would have been easy, had you just followed my directions.
Derpopotamus said:
Firstly, I tried just about every one-click solution out there, to no avail. It's possible SOC 1.7 with rattlethecage works, but I didn't have the patience to find out whether I simply had to wait a bit longer.
I followed this guide(whilst clenching every clenchable muscle I could consciously control):
http://www.galaxyforums.net/forum/o...mission-t-mobile-galaxy-s-4g-gingerbread.html
The gist is, Odin 1.7, stock+voodoo for T959V, plus some update that I'm not qualified to describe. That should get you rooted and if that's all you're looking for, you'll have to suffer through a little T-Mobile branding on startup.
Once you got it all rooted, you'd think it'd be a good idea to toss sgs-ics on there, right? Well, no.
Click to expand...
Click to collapse
Duh, and rightfully so. You should not flash anything that was not made for your phone.
As I said before. The SGH-T959V and the SGH-T959W are the same phone, just packaged differently for t-mobile vs. wind.
Derpopotamus said:
After installing the 4G variant, it promptly set off into a boot loop which I'm again, unqualified to diagnose. The obvious solution was to try another team's version of ICS, which I indeed found here:
http://forum.xda-developers.com/showthread.php?t=1730954
Click to expand...
Click to collapse
So, obviously this worked.
Derpopotamus said:
Barring some missing features, it sounds like a good alternative to sgs-ics.
Click to expand...
Click to collapse
:facepalm:
Derpopotamus said:
Though I had to go through one additional step, which I really, honestly assure you I was under-qualified to execute. When I tried to load Team Acid's CM9 r3 it gave me an assert on the updater-script, since the hardware didn't match up. Easy. Unzip the package, open up META-INF/com/google/android/updater-script, remove the first check. You know it's the same hardware, you don't need some stinkin' script to tell you it won't work.
Click to expand...
Click to collapse
We can fix that by adding your OTA Assert to our build. Then this won't happen. Let me fix that.
Thanks for someone finally reporting something useful!
Derpopotamus said:
So all said and done, I now have a Wind Mobile SGH-T959W running ICS 4.0.4 courtesy of bhundven, the Odin folks, Team Acid, and likely a slew of other contributors.
Thanks folks, and enjoy!
PS, if you want that tarball bhundven, send me a PM with some brief instructions, and hopefully you can help my fellow Winders.
Click to expand...
Click to collapse
No pm needed.
Open an account on mediafire.com.
Upload the tarball
click share after the tarball is up
Post your own topic in the general forum so everyone knows where to get it.
Everyone Profits!
One more thing that would be very handy from somone with stock on T959W.
Please:
Code:
adb pull /system/build.prop
edit the file with notepad++(windows), textedit(macosx), or gedit(linux) and put the results on pastebin.com.
Then paste the link in this forum.
THANKS!
Build.prop for stock phone
bhundven said:
One more thing that would be very handy from somone with stock on T959W.
Please:
Code:
adb pull /system/build.prop
edit the file with notepad++(windows), textedit(macosx), or gedit(linux) and put the results on pastebin.com.
Then paste the link in this forum.
THANKS!
Click to expand...
Click to collapse
http://pastebin.com/aTHkkwDJ

Categories

Resources