Hi Guys,
Is it possible to Run Boot2Gecko on Galaxy S I9000 like with Galaxy S II? ---> Article - http://www.xda-developers.com/developments/mozillas-boot-to-gecko-running-on-a-samsung-galaxy-sii/
Because I am very satisfied with S I9000 and I haven't got enough for S II.
So do Anyone know howto from SII Update.zip to S Update.zip convert?
Would like to try it too .
useful links
Hi Guys,
I've got some Links for People, which are interested like Trojan38
For Developers ---> https://developer.mozilla.org/en/Mozilla/Boot_to_Gecko/Building_B2G_for_Samsung_Galaxy_S2 (This Tutorial is for I9100)
Official Wiki ---> https://wiki.mozilla.org/B2G
I am not clever enough to Understand the Developer's Tutorial, maybe it can be useful for other Guys
____
Yeah! Sounds interesting .
I will a Mozilla OS
that all sound really Great
so I have just to Say "D'accord avec mon ami Trojan38 "
I am either just a noob
I actually also wanted to make a topic about porting boot2gecko (for i9001).
Actually I think it could be done for sure, the original build is at SGS2, which has the same cpu category as the i9000 and i9001 (armeabi-v7a/armeabi)
Also the resolution is HDPI 480x800 which is also fortunate.
I've downloaded the SGS2 version and extracted it, any it's clearly built on the AOSP environment, actually it looks just like a copy of a AOSP GB rom with an other framework then usual. This is why I think we could actually succesfully port it.
I'm kinda afraid to try it tho, since I have zero knowledge about making kernels so i couldn't produce a working kernel, also I find it rather spooky that dalvik will be deleted.
@poster: it's really more then just converting the "update.zip" which is actually an odin image.
I think we have a pretty high change on succeeding when we just port it like we normally do, my concerns are the kernel tho. Really don't know how to fix that
Related
Hi !
I'm really curious about why I can't use ROM for the 10.1 version on 8.9 version of Galaxy Tab.
Except the panel size (10.1 vs 8.9) and battery capacity, there are other hardware differences ?
Any ideas ?
Thanks.
You /can/ use 10.1 ROMs. The 8.9 and 10.1 are virtually identical.
You just need to swap out boot.img and recovery.img AFAIK. And edit build.prop.
Hurrian said:
You /can/ use 10.1 ROMs. The 8.9 and 10.1 are virtually identical.
You just need to swap out boot.img and recovery.img AFAIK. And edit build.prop.
Click to expand...
Click to collapse
can you point me to the right track
what i need to edit the build.prop?
Here, courtesy of alterbridge86.
BTW, Overcome 2.0.0 is a P75xx ROM ported to P73xx, if you'd want to start on that.
http://forum.xda-developers.com/showpost.php?p=18872241&postcount=48
Thinking about the same thing.There is much less rom on the 73xx section, . Is anyone here would like to give more detail on these?
Hurrian said:
Here, courtesy of alterbridge86.
BTW, Overcome 2.0.0 is a P75xx ROM ported to P73xx, if you'd want to start on that.
http://forum.xda-developers.com/showpost.php?p=18872241&postcount=48
Click to expand...
Click to collapse
thanks, will start to learn on this
I hope good theme'rs get the 8.9 soon. I wish i had the talent to do it
Actually, I don't think it's as simple as that post from alterbridge - that was quite early on in his experimentations with Overcome on the 8.9. I recall from the subsequent release of Overcome that he said that there were other considerations, which is why the camera was flipped in the earlier versions based on 10.1 ROMs. He switched back to 8.9 bases for the 1.2 version for this reason.
Clearly, these issues were resolved as the latest Overcome is now based on a 10.1 base again. However, I think there are a couple of other things needed that aren't articulated in the thread where he was replying to me on the subject. Anyone know for sure what else needs fixing?
i think - the most intresting problem with ROM - support language
How can add/delete longuga in ROM
Loccy said:
Actually, I don't think it's as simple as that post from alterbridge - that was quite early on in his experimentations with Overcome on the 8.9. I recall from the subsequent release of Overcome that he said that there were other considerations, which is why the camera was flipped in the earlier versions based on 10.1 ROMs. He switched back to 8.9 bases for the 1.2 version for this reason.
Clearly, these issues were resolved as the latest Overcome is now based on a 10.1 base again. However, I think there are a couple of other things needed that aren't articulated in the thread where he was replying to me on the subject. Anyone know for sure what else needs fixing?
Click to expand...
Click to collapse
You are right. Is much complicate than what they said. I just did an experiment. I replaced the boot.img in one 7510 custom rom with 7310Overcome 2.0's own boot.img, and changed some word in the build.prop. Put it on my 7310. Luckily ,it boot alright, but when the android welcome page(select your langurge ) show up, the screen did't respond my touch correctly, I need to touch somewhere under the target what I want to touch to make it work.
Looks like there is lots of thing I need to know.
I wonder when the CM ICS rom hits the 10.1 will alterbridge86 be able to work his magic ?
Fingers crossed !!
The true is,it is simple as what they said. My experiment work finally. I replace the boot.img in one custom 7510rom by the one in 7310Overcome2.0.
The tweak of the build.prop is very simple. Just replace all "P7510" by "P7310". Add "ro.sf.hwrotation=90" in the last. And All is done. The little mod Rom work perfectly on my 7310.
But I think the success belong to alterbridge86's boot.img and his work,without that, the rom just showed the Logo, nothing else.
By the way,I am going to investigate what magic alterbridge86 do in the file boot.img. The file size is much small than the stock one(half),and what's the impact. I have lots thing to learn
Might give this a try tomorrow. Would love to try a Vanilla rom on the 8.9.
any luck with the vanilla rom?
Hi friends,
I am proud to join the SGN community. currently my phone is rooted, running on Ginger Bread, kernel version Abyssnote 4.2. Everything just works fine thankful to the developers for their great job and clear instructions. Well, let me not drag it anymore. Has any developer made MIUI ROM based on ICS designed for Galaxy Note? Because previously I used to own a Samsung I9000 and for that model, there was (and still is)a whole bunch of different ROMs with different modifications and tweaks and the list included some MIUI ROMs too which were really cool to look at and fun to use. I just love the themes and those animations on MIUI.After buying this new Samsung Galaxy Note I really hoped I could flash a MIUI based on ICS but unfortunately could't find one here on the forum. I hope my thread sparks some interest in all developers' minds and they come out with a cool ROM for all of us. Thank you for reading my thread patiently. Cheers
Try this link..
http://forum.xda-developers.com/showthread.php?t=1521630
Hi Ranjan.Alva,
Thanks for the link to MIUI based on ICS. I am going to flash and see how it works on Galaxy Note.
I tried that ROM too...well, everything looks fine except that the inbuilt player won't play anything from the external memory card. Funny isn't it? What is the use of flashing a ROM if you have to depend on the internal memory all the time?....Any suggestions???
Saluton al vi,
I decided to come in the Android development with a porting, a thing that, according to what I heard, isn' too difficult to start. I read a bit this guide http://forum.xda-developers.com/showthread.php?t=1598713 and I believe it could be nice and a bit useful to port MIUI v4, since I haven't found any versions for our Galaxy Tab yet, maybe using CyanogenMod 9 official RC1 as base (since MIUI derivates from CM).
1) From which device should I port MIUI? Galaxy Nexus, Galaxy S2 or anything else?
2) Will I have to change the resolution of every image to adapt a phone ROM to a tablet?
3) Would it be too difficult for a person like me, who have never created or ported a ROM before? Maybe did I misunderstood anything and is a porting a terribly difficult thing? I'm asking this because I've never seen a MIUI porting for Galaxy Tab.
4) If it's too difficult, what should I do to learn?
5) Finally, the obvious question: do I risk bricking my Tab, even if in the ROM there are neither primary nor secondary bootloaders?
I'm sorry if the questions are too many.
http://forum.xda-developers.com/showthread.php?t=1440924
Sorry, but I did it unintentionally, and when I noticed the mistake, I didn't know how to move the thread. Who can do it?
Please, could you be so nice to answer my question, instead?
Sent from my tablet using CyanogenMod 9 RC1
I'll write the post again in the Q&A section. Could you delete this one, please?
Sent from my tablet using CyanogenMod 9 RC1
I was looking into Jelly Bean ROMs here, and I couldn't find anything that's working as I had hoped for.
Or I just didn't look through stuff on here in more detail.
So I was looking at some 'light' ROMs and found SlimBean, but it only seems to support i9000 (as listed here) whereas I'm running i9001.
Here comes the stupid question - would it work or not?
I kind of want to test that out, because the ROMs I used previously didn't have a working microphone (which I kind of needed for making calls) so I'm thinking this one would have a working one and would have a decent amount of Project Butter.
So anyway, what JB ROM would you recommend? It doesn't have to be 'slim', as long as most stuff works on it.
Hi,
most or nearly all roms wont work on your device. I found a nice JB Rom called Mackay Rom for my Samsung Galaxy S.
Its fast and stabil. If you find this Rom for your device, you could try it, he is updating this rom fast and the changes are nice.
Most JB Rom use CM10 as basis so the difference wont be that huge^^
None of the i9001 Jelly Bean ROMs are fully functional at the moment, as you have noticed. i9000 ROMs will not work on i9001, as it is a totally different phone. Only things we have similar is the screen, battery size and the form of the phone, CPU & GPU being different makes it impossible to use the same ROMs.
There is a lot of work to be done and a few talented people doing the work. Just keep on looking in the Galaxy S Plus I9001 Android Development, all progress will be posted in there. Pretty much the only JB rom we have is DoomNEXUS by Doomsday94.
There also is the I9001 Q&A section that these questions should be directed to.
Slim Bean Best one
Hello ,
few days ago i updated my gf's s2 to new JB that was leaked offical samsung but from odin, then i got an idea, cuz i have Captivate Armani I9010 and i was using Remics JB as last rom, cuz it was look rly nice likly s3 rom, but i didn't like aops dialer layout and some more staff and i got idea of porting S2 or even S3 rom to captivate, and i was playing with some tutorials and android kitchen but without lucky, as I have rly bad knowledge of programing thinks , but I'm trying and want to learn more, my point was that maybe its posible to use some custom aops rom as base(ofc if developer agree) and port s2 rom over, i know that to port stock apk's form s2 that i like i need to port aslo framework, but what else?
Is someone with knowledge are up to help me or take this project if it interesting?
Or if this is totally wrong , what is real way to go of port s2 rom to captivate? I'm sure that its posible i saw some video of s2 rom on i9000 with is pritty much same as capativate. (it was GB i think because video is old) but if it able to port one rom there is no difference but what is good way to start.
I am really sorry about my English , its not my main language, and I am interesting in learning as much as i can about android dev.
Ps. OR mabye it would be easy to just port some of apk instead of porting whole rom. (secphone seclaucher secmms seccontacts systemui etc etc)
Greetings.
bg.stefan90 said:
Hello ,
few days ago i updated my gf's s2 to new JB that was leaked offical samsung but from odin, then i got an idea, cuz i have Captivate Armani I9010 and i was using Remics JB as last rom, cuz it was look rly nice likly s3 rom, but i didn't like aops dialer layout and some more staff and i got idea of porting S2 or even S3 rom to captivate, and i was playing with some tutorials and android kitchen but without lucky, as I have rly bad knowledge of programing thinks , but I'm trying and want to learn more, my point was that maybe its posible to use some custom aops rom as base(ofc if developer agree) and port s2 rom over, i know that to port stock apk's form s2 that i like i need to port aslo framework, but what else?
Is someone with knowledge are up to help me or take this project if it interesting?
Or if this is totally wrong , what is real way to go of port s2 rom to captivate? I'm sure that its posible i saw some video of s2 rom on i9000 with is pritty much same as capativate. (it was GB i think because video is old) but if it able to port one rom there is no difference but what is good way to start.
I am really sorry about my English , its not my main language, and I am interesting in learning as much as i can about android dev.
Ps. OR mabye it would be easy to just port some of apk instead of porting whole rom. (secphone seclaucher secmms seccontacts systemui etc etc)
Greetings.
Click to expand...
Click to collapse
The best way to go about porting a ROM would be to ask one of your fav dev and read one hell of a lot!
Theming is fairly easy, you open the app with something like apktool and work your way through (or can use kitchen). As far as porting apps, it would mainly be the framework but you gotta keep in mind functionality that the Cappy doesn't have.
Reading and guides are really your best friends here. It can all be self learnt but it requires a lot of patience, gotta expect some good old headbanging lol
Here's a thread that could help you: http://forum.xda-developers.com/showthread.php?t=916814
Thanks,
I will probably start with port some apks but, as its not that hard job, but should like to learn how to port rom really i was reading some guides with was like its ok for any phone from same generation cpu like armv7 ported and base rom need to be same version, used same manifecture of device . and what i did used deo-dexed s2 rom JB 4.1.1 official one (aslo found one slimed s2 rom 4.1.1 aslo) and tryed few different as base CM10 for cappy was one of them its 4.1.2 but i think there is no big difference i tryed some 4.1.1 roms as base with was work on phone ok but when i made rom trought those guides its stack on bootanimation and logcat just spam that like every apk die
That was one of guides where it's says that it will work for all stock/cm/aokp roms ICS and JB updated.
There are few really easy steps and what i expected is that phone will boot and will be buggy as **** till a lot of tweaks but it didnt even boot ((
PS. I was looking around and i found that there are some custom rom (this was for s2 ) that are based on samsung base not aokp or cm. And they have all features of custom rom with all stock samsung look witch i like and stock phone/dialer/contact/tw/systemui/ etc etc/
My questions is there mabye that kind of rom for captivate or at least i9000 since i think its easier job to port from i9000 then from s2. And what would be base because last fw for cappy or galaxy s is GB, is there any posiblilty to get ISC or JB samsung based rom on this device?
bg.stefan90 said:
Thanks,
I will probably start with port some apks but, as its not that hard job, but should like to learn how to port rom really i was reading some guides with was like its ok for any phone from same generation cpu like armv7 ported and base rom need to be same version, used same manifecture of device . and what i did used deo-dexed s2 rom JB 4.1.1 official one (aslo found one slimed s2 rom 4.1.1 aslo) and tryed few different as base CM10 for cappy was one of them its 4.1.2 but i think there is no big difference i tryed some 4.1.1 roms as base with was work on phone ok but when i made rom trought those guides its stack on bootanimation and logcat just spam that like every apk die
That was one of guides where it's says that it will work for all stock/cm/aokp roms ICS and JB updated.
There are few really easy steps and what i expected is that phone will boot and will be buggy as **** till a lot of tweaks but it didnt even boot ((
PS. I was looking around and i found that there are some custom rom (this was for s2 ) that are based on samsung base not aokp or cm. And they have all features of custom rom with all stock samsung look witch i like and stock phone/dialer/contact/tw/systemui/ etc etc/
My questions is there mabye that kind of rom for captivate or at least i9000 since i think its easier job to port from i9000 then from s2. And what would be base because last fw for cappy or galaxy s is GB, is there any posiblilty to get ISC or JB samsung based rom on this device?
Click to expand...
Click to collapse
They can all be ported, it's mostly framework. Although, I never ported a ROM so I'm not the best one to guide you through this. If I'm not mistaken, there are guides in XDA-U. Also, there are quite a few nice Devs around here that could help you through it.
Thanks, I saw some of those guides some are generic some are on example but i for porting samsung (s2) based rom i need to use some jb base for captivate cm or aokp but there some difference when porting roms even if both base and port are same version JB . Cuz they are not on same base. And i hope it is not difficult to make. If it's not hard I would please ask some od dev to give me some guide. On what i have to take care . What to do and i will gief all effort and time to make it working.