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
Related
Update: Alright guys, after collaborating with others on the port it seems we have hit a wall. The nexus s doesn't use our adreno egl drivers and instead uses newer drivers. The drivers are needed and we can't call on adreno drivers without errors. Because of this, we are putting a stop currently on development as first and foremost we need the build to be usable. The inc devs seem to have hit the same road block. We need a nexus one dump or source to move forward. Until then. :tips hat:
This is a dev rom. Things are still broken. Please don't play unless you realize this. If your boot hangs, try a dalvik wipe.
Note to devs:
-homescreen still slow (using ns EGL libs right now)
-no sound, sound crashes on boot
-dont have time to test more
-no wifi
-data works (browser force close on google boot)
Gingerbread Download: http://www.brieflygeek.com/downloads/project/gingerbread0321CT.zip
Thanks to the devs on the inc forums!
Patch: http://www.brieflygeek.com/downloads/project/flashpatch.zip
Flash this right after flashing gingerbread, same session
Fix roaming indicator:
http://www.echoblog.net/signed-roaming.zip
Thanks echo
Credits: bcnice20, MagnuSRagnaroK, pseudoremora, echoside, me.
Its missing the permissions. and symlinks
Wrong Section.........This is the EVO section..not nexus s. LOL
swaze said:
Wrong Section.........This is the EVO section..not nexus s. LOL
Click to expand...
Click to collapse
I'm familiar with the sections, this is correct
lithid-cm said:
Its missing the permissions. and symlinks
Click to expand...
Click to collapse
Just saw that.. got excited. I'll keep an eye out and update with a new dump as I see one. Im hopin in the IRC with these guys
Yea but we can use a few things from there...
They could use this to complete that hackey sdk port.
Sent from my supersonic.
good... good... good....
thank you.
barnacles10 said:
I'm familiar with the sections, this is correct
Just saw that.. got excited. I'll keep an eye out and update with a new dump as I see one. Im hopin in the IRC with these guys
Click to expand...
Click to collapse
I was going to work on the port once it was released but if your already looking at it drooling ill let you have at it lol
david279 said:
They could use this to complete that hackey sdk port.
Sent from my supersonic.
Click to expand...
Click to collapse
We could just port the whole thing without the "hacky" sdk
Or that yea.
Sent from my supersonic.
lithid-cm said:
I was going to work on the port once it was released but if your already looking at it drooling ill let you have at it lol
Click to expand...
Click to collapse
Go head, its fun for all. I didn't start this as a personal project, and am happy to update the OP with anything anyone comes across here. BTW, you have post 2.
david279 said:
They could use this to complete that hackey sdk port.
Sent from my supersonic.
Click to expand...
Click to collapse
Oh....lol I didn't know people still did that. HAHAHA
Good luck trying to port this... you're gonna have hell of time. The problem is that us EVO users are currently using 2.2 and the Nexus ROM's are built on 2.3; the lib files and bins will more than like fail if you try to boot.
I would wait until the 2.3 AOSP source is released to try and do a proper boot.
Porting different versions of Android especially from different manufacturers is a huge *****... believe me, I know... right Barnacles?
Edit:: I take back some of what I said... apparently it can be done, with some problems -- looking into right now with some other devs; will update later.
barnacles10 said:
Go head, its fun for all. I didn't start this as a personal project, and am happy to update the OP with anything anyone comes across here. BTW, you have post 2.
Click to expand...
Click to collapse
It should be a project. I am at work right now, but once that good dump comes along... I might just get fired... I want that GB on my evo. NOW hehe
We need source.....maybe today it will be released.
Sent from my supersonic.
david279 said:
We need source.....maybe today it will be released.
Sent from my supersonic.
Click to expand...
Click to collapse
could be google released the kernel source and something else before it was released
pseudoremora said:
Good luck trying to port this... you're gonna have hell of time. The problem is that us EVO users are currently using 2.2 and the Nexus ROM's are built on 2.3; the lib files and bins will more than like fail if you try to boot.
I would wait until the 2.3 AOSP source is released to try and do a proper boot.
Porting different versions of Android especially from different manufacturers is a huge *****... believe me, I know... right Barnacles?
Edit:: I take back some of what I said... apparently it can be done, with some problems -- looking into right now with some other devs; will update later.
Click to expand...
Click to collapse
Yes. hahah
They have it booting on the INC with the help of the sdk I believ
meh, There is always a way.
Cant wait for this....
Is this what you guys are looking for??
http://www.multiupload.com/PYF3KEWW29
Sent from my PC36100 using XDA App
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
guys, no need to harass people, but. We have a hacked kernel, all the libs and files for GB and all sorts of resources for CM7 to work on gs4g. Also, GSII already is getting nightlies. we need to get working on it. Should be hard as there is already a vibrant edition.
airfluip1 said:
guys, no need to harass people, but. We have a hacked kernel, all the libs and files for GB and all sorts of resources for CM7 to work on gs4g. Also, GSII already is getting nightlies. we need to get working on it. Should be hard as there is already a vibrant edition.
Click to expand...
Click to collapse
So what are you waiting for, get to it.
Sent from my SGH-T959V using Tapatalk
Looking forward to it. Let me know if you need me to test anything when you get a beta working.
Sent from my SGH-T959V using XDA Premium App
airfluip1 said:
guys, no need to harass people, but. We have a hacked kernel, all the libs and files for GB and all sorts of resources for CM7 to work on gs4g. Also, GSII already is getting nightlies. we need to get working on it. Should be hard as there is already a vibrant edition.
Click to expand...
Click to collapse
good luck brotha really have u looked around this place lol most of there gingerbreads were ported from other devices... and honstly we have what 4 rom devs des myself krylon whitehawk....
krylon is working on it it will be done when its done..
chcek my thread about cm7 and miui. krylon's working on it and is waiting to sprt out the kernel with honk. give them time
airfluip1 said:
guys, no need to harass people, but. We have a hacked kernel, all the libs and files for GB and all sorts of resources for CM7 to work on gs4g. Also, GSII already is getting nightlies. we need to get working on it. Should be hard as there is already a vibrant edition.
Click to expand...
Click to collapse
Tell me when you get the CM7 kernel compiled, I can test it for you.
CM uses it's own kernel. Not a hacked samsung kernel.
this phone isnt like the vibrant, so stop saying that. different drivers, different RIL's different kernel config.
oh..
AND READ NEXT TIME!
krylon360 said:
CM uses it's own kernel. Not a hacked samsung kernel.
this phone isnt like the vibrant, so stop saying that. different drivers, different RIL's different kernel config.
oh..
AND READ NEXT TIME!
Click to expand...
Click to collapse
pwnage lol!
In your freaking faces ) jkjk but honestly you guys should stop comparing this phone with others, it is its own unit not a copy of something else
krylon360 said:
CM uses it's own kernel. Not a hacked samsung kernel.
this phone isnt like the vibrant, so stop saying that. different drivers, different RIL's different kernel config.
oh..
AND READ NEXT TIME!
Click to expand...
Click to collapse
Sent from my SGH-T959V using XDA App
krylon360 said:
CM uses it's own kernel. Not a hacked samsung kernel.
this phone isnt like the vibrant, so stop saying that. different drivers, different RIL's different kernel config.
oh..
AND READ NEXT TIME!
Click to expand...
Click to collapse
God krylon, myself and the rest of the sgs4g community miss you and want you back terribly
Sent from my SGH-T959V using XDA App
Juls317 said:
God krylon, myself and the rest of the sgs4g community miss you and want you back terribly
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
It's been scientifically proven that he appears every time you mention his name in ANY thread whatsoever.
FBis251 said:
It's been scientifically proven that he appears every time you mention his name in ANY thread whatsoever.
Click to expand...
Click to collapse
he must have some sort of app that gives him a push notification within milliseconds
nah, nothing like that at all.
krylon360 said:
nah, nothing like that at all.
Click to expand...
Click to collapse
I'm gonna hijack the thread for a moment.
Have you looked into the bml partitions for the sgs4g? It seems that we might be able to flash bootloaders using redbend_ua after all. Been poking around with some dumps I made of the files. So far I think bml1 contains the primary bootloader, and 3 or 4 might contain secondary bootloaders. I ran the dumps through strings to see what kinda messages the samsung devs put in there... Yes yes random rambling.
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
I've been slowly working on a JB Sense 4x project for fun. as I learn I go back and make changes here and there hoping that maybe, just maybe, one day it'll boot. As I was working on it yesterday I realized that with my Shift not working there will not be anyway for me to test it so I thought I would ask if anyone is interested in helping. It is a port from the One X. I haven't asked for permission from the original dev to release anything publicly yet (because I don't know if it'll work) so I'll have to pm links for now. Where I am at with this at the moment is the updater script. I've been through the rest of the ROM and think I have a good start but I haven't done anything in the META-INF folder. I am still reading up on how to write my own updater script but I'm not capable yet so those who want to help, this is my immediate need. It would be good for folks to go through the build.prop also. I'm still a little unsure about the changes necessary to go from a GSM ROM to CDMA.
Edit: I probably should have put this in General instead of Q&A. Sorry...
Chad The Pathfinder said:
I've been slowly working on a JB Sense 4x project for fun. as I learn I go back and make changes here and there hoping that maybe, just maybe, one day it'll boot. As I was working on it yesterday I realized that with my Shift not working there will not be anyway for me to test it so I thought I would ask if anyone is interested in helping. It is a port from the One X. I haven't asked for permission from the original dev to release anything publicly yet (because I don't know if it'll work) so I'll have to pm links for now. Where I am at with this at the moment is the updater script. I've been through the rest of the ROM and think I have a good start but I haven't done anything in the META-INF folder. I am still reading up on how to write my own updater script but I'm not capable yet so those who want to help, this is my immediate need. It would be good for folks to go through the build.prop also. I'm still a little unsure about the changes necessary to go from a GSM ROM to CDMA.
Edit: I probably should have put this in General instead of Q&A. Sorry...
Click to expand...
Click to collapse
The problem will continue to be that we don't have a kernel for Sense 4.0, it won't work till we have one... but thanks for putting in the work... do you have your OG yet?
Ive modified Strapped365's new kernel and think it'll work. Ive gotten a port from the One V to boot before with the mod I made.
Edit: This was my starting point. http://forum.xda-developers.com/showthread.php?t=1707177
Chad The Pathfinder said:
Ive modified Strapped365's new kernel and think it'll work. Ive gotten a port from the One V to boot before with the mod I made.
Click to expand...
Click to collapse
Oh OK... I'll look at it if you want. Just put the links up and whoever wants to try their hand it can... it can be a community project lol
I pmed you the link. I'll put it in Development as a wip when I hear back from the Dev who made the ROM...
I'll help out too if you want :good:
Sent from my PG06100
Thanks. I've been given permission from the dev, theDroidfanatic to put it out there publicly and will have it posted today.
Edit: Here's the link.
CNexus said:
I'll help out too if you want :good:
Sent from my PG06100
Click to expand...
Click to collapse
Go for it man, I'm kinda busy with three other projects lol. And a new phone coming today, I doubt I'll get around to it any time soon.
I'll test whenever you need a tester.
Sent from my Nexus 10 using xda app-developers app
My shift has quit completely now so I'm not sure how to proceed but thanks...
Edit: if anybody wants to try to make this work, I'll be glad to help as best as I can!
Chad The Pathfinder said:
My shift has quit completely now so I'm not sure how to proceed but thanks...
Edit: if anybody wants to try to make this work, I'll be glad to help as best as I can!
Click to expand...
Click to collapse
What do you need? I have a working device but the flex/earpiece needs replaced
Sent from my myTouch_4G_Slide using Tapatalk 2
Chad The Pathfinder said:
My shift has quit completely now so I'm not sure how to proceed but thanks...
Edit: if anybody wants to try to make this work, I'll be glad to help as best as I can!
Click to expand...
Click to collapse
If I can find a cheap shift on ebay I'll try and get it for you.
Im eyeying one for 5.50 right now.
and a few others for less than that. :good:
Wow guys that's great. I don't know what's wrong with my shift now. The flexcable was torn almost in half. I'm thinking I may have somehow broken something else putting the new one in. It's got me pretty bummed.