Create you own custom ROM for i5800 - Galaxy 3 Android Development

I think if there is any developer, he can use this link to make a custom firmware.
The link is from the i9000 and hope that someone made custom ROM for i5800 by using this.
http://forum.xda-developers.com/showpost.php?p=10040444&postcount=1
Originally written by : Nokia7Vista

ok, almost everything matches except where can get the "RomBasics.zip" from the tutorial for my i5800?

Here is the RomBasics.zip for I-5800 this is based on I5800XXJK1 rom "Eclair 2.1"
uploaded to many sites
the download link in the attached text file
Use it at your own risk I won't be hold responsible if you break, damage your phone

HSaber said:
Here is the RomBasics.zip for I-5800 this is based on I5800XXJK1 rom "Eclair 2.1"
uploaded to many sites
the download link in the attached text file
Use it at your own risk I won't be hold responsible if you break, damage your phone
Click to expand...
Click to collapse
Great ! Many thanks for this!

so when the kitchen is ready.. we are good to build roms? how do we port the .32 kernel here and replace this ? will it work if u just replace the zimage? .. i also heard somewhere that playing with the kernel doesnt brik the fon ?

could someone please share rombasics.zip based on FROYO?

masterg0g0 said:
so when the kitchen is ready.. we are good to build roms? how do we port the .32 kernel here and replace this ? will it work if u just replace the zimage? .. i also heard somewhere that playing with the kernel doesnt brik the fon ?
Click to expand...
Click to collapse
It can soft brick the phone.. Meaning the phone may not boot past the i5800(i) screen. If you see that screen, it means that you can't get past the Second Boot Loader (Sbl.bin). Reflashing with a good zImage should fix that problem.
That screen usually means there's an issue with the way the kernel was flashed, or the kernel/initramfs (both are contained in the zImage).

precurse said:
It can soft brick the phone.. Meaning the phone may not boot past the i5800(i) screen. If you see that screen, it means that you can't get past the Second Boot Loader (Sbl.bin). Reflashing with a good zImage should fix that problem.
That screen usually means there's an issue with the way the kernel was flashed, or the kernel/initramfs (both are contained in the zImage).
Click to expand...
Click to collapse
Cool.. i will try to cook my self a rom.. removing and adding what i want ... so i understand that the file inrombasic.zip is eclair ? i cud have done some real developing but my work takes away some time.. so i can only try to cook some rom at d moment.. Happy new yr

Jpf rombasics
anyone have a link for JPF ROMBASICS?

Related

Best ROM-Emulator !?!?!

Hey everybody..
which is the best ROM-Emulator, so i can test the ROM's on my PC before flashing my phone ?
thx
So far I only know of one... and it's from the man himself. do a google search~
http://www.google.com/search?q=wm+6...s=org.mozilla:en-US:official&client=firefox-a
Also, I don't think you can load NBH files through the emulator. There's a size limit. You need to run a kitchen.
Well thx,
i can't chose another OS. I downloaded the Energy-ROM, but when I click on configure at the Emulator, I can't choose another ROM
Can anybody help ???
thx
I think if there would be good running emulator what could take different roms, we would not have so much bricks.
Most of the people would not flash so many roms to try out the best.
I think if u like a diff rom than u have to take the risk of flashing.
schnitzelbrain said:
I think if there would be good running emulator what could take different roms, we would not have so much bricks.
Most of the people would not flash so many roms to try out the best.
I think if u like a diff rom than u have to take the risk of flashing.
Click to expand...
Click to collapse
For the most part, the only people who truly brick their phones are people who can't read and follow instructions. An emulator isn't going to help them. Flashing a rom that doesn't boot is usually not a big deal; it happens frequently when you cook roms. Bricks occur when people flash the wrong hard spl, radio or unlocker. That's pretty much it. Even the guys who post that they flashed a gsm rom onto their sprint touch pro normally recover the phone when they flash a stock rom to it (assuming they figure out how to do it).

Leaked 2.1 for the Eris?

http://forum.xda-developers.com/showthread.php?t=641588
http://imgur.com/AJkH6
It sounds like its a working build, could we use this to our advantage? Like getting the cam working on our current 2.x builds?
Gogogogogogogogo! Please someone port this!
that topic looks soooo sketchy haha
but if its real
Ska8erMush said:
that topic looks soooo sketchy haha
but if its real
Click to expand...
Click to collapse
i read the posts; it seems real. they got it to flash after applying a patch to fix some mismatch, and there's a picture posted.
i'm pretty sure its real.
Looks pretty real to me, kinda wish I had a eris to test it on myself, but oh well. If this turns out to be real it wouldn't be to hard to port because of how close the two phones are right?
justinisyoung said:
i read the posts; it seems real. they got it to flash after applying a patch to fix some mismatch, and there's a picture posted.
i'm pretty sure its real.
Click to expand...
Click to collapse
whoa i should have read the whole topic
now i am super excited!
Some links
Thought I'd try to post these, so you don't have to go look.
Link for 2.1 .zip- Corrupted though
mediafire .com/ ?ycd4wwm12gx
and here's the patch instructions that one of the developers over there made.
zanfur said:
Well, someone might want to try this. I've gotten the unzip errors to go away, but I haven't tested it on an actual device. Anyone want to try? I've uploaded the (very tiny) binary patch. You'll need the bspatch utility (windows port here: ]http:.//sites.inka.de/ tesla/f_others. html#bsdiff). Rename the one you downloaded to something else like PB00IMG-corrupt.zip, and run this:
Code:
bspatch PB00IMG-corrupt.zip PB00IMG.zip eris-eclair.bpatch
That will create a new PB00IMG.zip that is no longer corrupt. Someone test it on a phone and let me know if it works!
Click to expand...
Click to collapse
for now guys, i'd say don't flash this. its definitely risky.
if you open up the file there's a radio img on there, which should make all of us who don't have heros to spare nervous. considering how flashing radios is basically the ONLY way to brick our phones, it's probably a huge risk. i'm not sure if we can even flash this on our phone.
since most of us are probably looking forward to using camera, etc, maybe the kernel img is the one we could try and get working on our 2.1 builds? that's the boot.img, maybe we could try extracting it and signing it instead.
very interesting. im DLing now and gonna take a look at some stuff and see if anything in it is usuable to fix anything.
and i wouldnt flash this if i were you. it should brick your phone. if not tell us lol
I think i peed a little.... This could be HUGE!
one of the screen shots posted shows the kernel as .29...that's what we needed right?
The newly patched rom is here http://thekrtek.net/
Got a good feelin that Christmas is coming early this year, LOL
I sure hope so. Not getting my hopes up but this could be a turning point.
odd.. the system img keeps telling me its corrupted. so i cant extract anything. re downloading i guess..
If anyone gets this to boot without bricking the phone BETA TESTER HERE!
are you using the link in post 99?
Avalaunchmods said:
odd.. the system img keeps telling me its corrupted. so i cant extract anything. re downloading i guess..
Click to expand...
Click to collapse
i extracted it just fine using unyaffs
@avalaunchmods- you have to apply that patch that the eris people came up with.
okay, so i mentioned in my earlier post that we might not want to flash this cause of the ominous presence of the radio.img. or maybe i'm the only one who would feel nervous flashing another radio onto our heros.
like i said, we probably want the boot.img, which is basically the kernel. so i zipped up and signed the boot.img from the leak, and i'm posting it here.
now, i don't have 2.1 installed, and you can flash this at your own risk. of course, i won't have responsibility.
though, the worst that could happen is really just a boot loop. kernels don't really brick phones... at least i don't think so.
for you brave souls out there.
i tried flashing it to a 2.1 rom. it didn't boot. we got some work to do... haha
justinisyoung said:
@avalaunchmods- you have to apply that patch that the eris people came up with.
okay, so i mentioned in my earlier post that we might not want to flash this cause of the ominous presence of the radio.img. or maybe i'm the only one who would feel nervous flashing another radio onto our heros.
like i said, we probably want the boot.img, which is basically the kernel. so i zipped up and signed the boot.img from the leak, and i'm posting it here.
now, i don't have 2.1 installed, and you can flash this at your own risk. of course, i won't have responsibility.
though, the worst that could happen is really just a boot loop. kernels don't really brick phones... at least i don't think so.
for you brave souls out there.
Click to expand...
Click to collapse
you don't need to apply the patch if you aren't flashing it, which we clearly aren't. we're porting it. we're working on porting it to our phones, we don't wanna brick our phones by flashing the radio in that rom

[ROM] [TEST, NOT FOR NOOBS] Rogers Sapphire Sense Port. Android 2.1 Sense. [9/15]

Quick throw-together. I highly reccomend one of pershoot's kernels from here: www.droidbasement.com/db-blog
Please use one of those. They're much more efficient than the king kernel i've included.
Features
Friendstream
Flippy clock (from SMOKI X)
King stuff (twitter.com/kingklick92)
Gapps
A2SD
Sense
Stable
Maps
Pretty
NEEDS A BIG EXT PARTITION AND A SWAP.
Good luck!
http://www.mediafire.com/?soscld37b0q6wiz
THIS IS UNSIGNED, IF YOU AREN'T USING CLOCKWORK, YOU SHOULD FIGURE OUT HOW TO SIGN IT YOURSELF. I'LL RELEASE SIGNED VERSIONS LATER.
EDIT YOU NEED A 114 MB SYSTEM FOR THIS VERSION DUE TO A 25MB BOOT ANIMATION, PLEASE USE MTD UNTIL I FIX IT
i got you bro. once i get my son to sleep ill test. you know anything yet? data/cam/wifi/gps etc? if not its cool, thats what tests are for.
ok, just doing this for people who dont want to sift through for the signed version: not signed by me, boot animation not swapped by me, *******there is a green bar at the bottom for status of install on boot note though, even after the bar is full it will still take a second IF YOU HAVE ADB INSTALLED RUN A LOGCAT, AS LONG AS YOU SEE THINGS MOVING YOU ARE GOOD. ********. let it sit for awhile like usual after it loads (20+ min). you also have to input the tmo apns to get svc.
link to signed version of the rom
http://goo.gl/opI3
tmo apn's:
http://goo.gl/bNtU
will post back a working/not working in a min.
i would also suggest not doing the system update that it says is avail once you get data working.
Love this.
Sent from my HTC Dream using XDA App
Is this compatible with a 32B Sapphire? Or would it be, to the best of your knowledge?
opethfan3 said:
Is this compatible with a 32B Sapphire? Or would it be, to the best of your knowledge?
Click to expand...
Click to collapse
yes this is a port from the 32a rom to 32b. its not signed so you can only flash via clockwork right now. clockwork doesnt require a signiture for it to be able to flash. if you use amon_ra just wait. im booting into linux after i post this now that i have my son asleep and will look into what can possibly be trimmed down then will sign and post up after im done.
ok, decided not to mess with anything, i dont use some stuff but others do, its signed and im gonna test now, just got done doing backup on current rom and will post if it flashes.
need to wait, since i have amon_ra.
Allright!! looking forward to this, I could sign the rom myself but ill wait to see how the rom works for you guys and im also waiting for a class 6 sdcard that I purchased a few days ago... anyways, im gonna try it with the class 4 i have right now after you try it and maybe cut some size
i hate clockwork. and it wont sign for me for some reason. idk why.
can someone please sign this so we can flash.
Good luck, guys. Really interested to see if this works.
im really going to enjoy triming this fat lady and mod a few things
anyone able to sign this thing yet?
Can you make a version that doesn't require an ext partition? Im on a mytouch 3g, should be able to handle it.
can't get it to sign (then again this might be my fault) how about first person to get this signed/flashed uploads some screenshots
btw: i'm using the autosigner
I'm downloading and signin... I replace the bootanimation to one less heavy??
p.s. sorry for my english
edit: I'm uploading to mediafire..if it finish in 5 minutes I give the link...if don't... I must go to work..link tonight..sorry
p.s. I've change the bootanimation..20 mb saved
http://www.megaupload.com/?d=EO5X0HBC
Click to expand...
Click to collapse
I simply signed the original file. gl
Download limit is exited
roalex said:
I simply signed the original file. gl
Click to expand...
Click to collapse
People will need the MTD hack to flash this.
asb123 said:
People will need the MTD hack to flash this.
Click to expand...
Click to collapse
I know, it is pretty easy to do it. I leave it to the devs to play with the size.
asb123 said:
People will need the MTD hack to flash this.
Click to expand...
Click to collapse
No, I take off the bootanimation of 20 MB and replace with one of 640kb... and I don't use MTD partition tonight the link..now I'm @ work...
p.s. I'l make a senseless rom
anyone tested it now? i want results; nothing about uploading elsewhere, signing mtd patch etc;
there are enough threads about it. there is a good working signing tool in xda.. search for it as well as tuts for it;
i think this thread should focus on the rom as it is something very interesting and new.
i wont try it at the moment cause i softbricked my phone with mtd patches.
please tell how the rom is...
EDIT: btw i know that this post is senseless concerning the original topic but i just want that this thread stays focused..

myTouch 3G 32b Official OTA Froyo 2.2 link provided - next stage for us?

Sorry if this is already being discussed in our G1 forums, had a look but one thread created was closed (therefore hope I'm not doing something I shouldn't be by opening this one, apologies if so!)
I found the link for an untouched OTA Froyo update for the myTouch 3G:
http://android.clients.google.com/packages/ota/tmobile_opal/e059adc603a3.signed-opal-ota-60505.e059adc6.zip
I read the forum over there and they talk of perhaps needing another file, as the update supposingly comes in 2 parts. Is it the case that we need a different radio/spl etc? What is the next step for us?
Hopefully one of our genius developers can get this working and ready to flash on our G1's, an official Froyo!
Wohoo!
Well it looks like it's flashable OOTB. It does contain a new radio image, but I'm not sure how that would work with 1.33.2005/whatever safe SPL is...
I guess stage one is removing the radio and flashing?
Then testing the radio with engineering SPLs?
AdrianK said:
Well it looks like it's flashable OOTB. It does contain a new radio image, but I'm not sure how that would work with 1.33.2005/whatever safe SPL is...
I guess stage one is removing the radio and flashing?
Then testing the radio with engineering SPLs?
Click to expand...
Click to collapse
Im not too sure myself, hopefully the Dev's seethis soon and offer their input on how we get this working on our devices!
cd993 said:
Im not too sure myself, hopefully the Dev's seethis soon and offer their input on how we get this working on our devices!
Click to expand...
Click to collapse
Im guessing they are either working on it now or we are the only ones home on a sunday afternoon lol
All the magic (pun intended) seems to be going on in this thread.
From what I've looked at thus far:
The kernel is built from the latest update in ASOP; at a new starting offset. Since the Dream source has no code to backup this alternate offset; and no configuration for trout in the ramdisk the new rom has the boot image will not work.
You can try to take the rom w/o radio/hboot and run it on a CM6 kernel.. this may operate.
As for the radio update.. it works with 1.33.2003/1.33.2005 as any 2.22.x radio however cm6 kernels fails to initialize the 3d graphics region that the radio moved and the phone reboots (RA-Recovery and adp1 1.6 rom boots without issue on the new radio)
Last HBOOT.. its a perfected HBOOT (it will work on the dream with a 2.x radio so dangerSPL rules apply) however if you are not very very careful you can get stuck..
In short at the very least some coding it required to get the same benefits as the Magic users will have.
I'm really excited bout this...perhaps recompiled with latest nightly CM kernel could work....!!!
ezterry said:
From what I've looked at thus far:
The kernel is built from the latest update in ASOP; at a new starting offset. Since the Dream source has no code to backup this alternate offset; and no configuration for trout in the ramdisk the new rom has the boot image will not work.
You can try to take the rom w/o radio/hboot and run it on a CM6 kernel.. this may operate.
As for the radio update.. it works with 1.33.2003/1.33.2005 as any 2.22.x radio however cm6 kernels fails to initialize the 3d graphics region that the radio moved and the phone reboots (RA-Recovery and adp1 1.6 rom boots without issue on the new radio)
Last HBOOT.. its a perfected HBOOT (it will work on the dream with a 2.x radio so dangerSPL rules apply) however if you are not very very careful you can get stuck..
In short at the very least some coding it required to get the same benefits as the Magic users will have.
Click to expand...
Click to collapse
ezterry, join us here http://www.stinto.net/pages/chat.htm?id=4hlqu
and anyone else who wants to/is knowledgable
ezterry said:
From what I've looked at thus far:
The kernel is built from the latest update in ASOP; at a new starting offset. Since the Dream source has no code to backup this alternate offset; and no configuration for trout in the ramdisk the new rom has the boot image will not work.
You can try to take the rom w/o radio/hboot and run it on a CM6 kernel.. this may operate.
As for the radio update.. it works with 1.33.2003/1.33.2005 as any 2.22.x radio however cm6 kernels fails to initialize the 3d graphics region that the radio moved and the phone reboots (RA-Recovery and adp1 1.6 rom boots without issue on the new radio)
Last HBOOT.. its a perfected HBOOT (it will work on the dream with a 2.x radio so dangerSPL rules apply) however if you are not very very careful you can get stuck..
In short at the very least some coding it required to get the same benefits as the Magic users will have.
Click to expand...
Click to collapse
one point of your thing here is wrong. i don't know about the others, they're probably right knowing you.
In the chatroom i posted, I successfully booted this ota with a cm kernel. duh.
I also booted a cm kernel WITH the tmobile-provided ramdisk. weird.
jcarrz1 said:
I also booted a cm kernel WITH the tmobile-provided ramdisk. weird.
Click to expand...
Click to collapse
I'm a bit surprised about this... but all that is needed to correct any issue is a init.trout.rc (seems most of the needed init logic is in init.rc)
we need a working sense ui 2.2 rom with bluetooth and touch focus
ezterry said:
I'm a bit surprised about this... but all that is needed to correct any issue is a init.trout.rc (seems most of the needed init logic is in init.rc)
Click to expand...
Click to collapse
that's it?? and then the tmobile kernel will work on a g1?
XIPRELAY2010 said:
we need a working sense ui 2.2 rom with bluetooth and touch focus
Click to expand...
Click to collapse
I guess i heared theat somwhere...:-D
sorry for OT...
jcarrz1 said:
that's it?? and then the tmobile kernel will work on a g1?
Click to expand...
Click to collapse
no the ramdisk will.. the kernel is compiled without dream support.. and at a different offset than usual.. this will take some poking and re-build from asop to make a similar kernel.. the problem with using the CM kernel is I suspect that there is additional ram make available by the new radio+kernel configuration.
so what do i have to download and what do i have to do with it, to run it on my G1?
ezterry said:
no the ramdisk will.. the kernel is compiled without dream support.. and at a different offset than usual.. this will take some poking and re-build from asop to make a similar kernel.. the problem with using the CM kernel is I suspect that there is additional ram make available by the new radio+kernel configuration.
Click to expand...
Click to collapse
I agree on that speculation... you mean you haven't tried it yet? i thought you did...
jcarrz1 said:
I agree on that speculation... you mean you haven't tried it yet? i thought you did...
Click to expand...
Click to collapse
I tried and failed to boot the kernel on a dream; and I looked at the source code; and noted the new boot offset.. Just booted it with a CM kernel now
Edit: Camera works, seems smooth.. wifi error.. need to inject root
woot, thank you!
XIPRELAY2010 said:
we need a working sense ui 2.2 rom with bluetooth and touch focus
Click to expand...
Click to collapse
No we don't.
ezterry said:
I tried and failed to boot the kernel on a dream; and I looked at the source code; and noted the new boot offset.. Just booted it with a CM kernel now
Edit: Camera works, seems smooth.. wifi error.. need to inject root
Click to expand...
Click to collapse
is there any improvement on memory/memory management with this change?

How to get Latest Builds to cook??

as subject says, were can i get those for htc p4350.. am using trib`s guide to do so.. can anyone pls help me??
You can find the link to my SYS & XIP files in any of my threads.
But, you can use this link:
http://joojoobee666.ppckitchen.org/Kitchens/
&
use this dump sorter:
http://forum.xda-developers.com/attachment.php?attachmentid=331217&d=1274669660
But my SYS & XIP files are already sorted out.
Also, if you've downloaded my kitchen then you won't need any of this at all LOL
Enjoy^>^
Can't wait to try your ROM, Yog..
ya have cooked roms but some went miserable as i don know wat are important files required to run a rom and wat options give wat kind of result like for home plugs i just getting its name and i don know how its visual will be.. i will be glad if u can help me to find it.. i will be a good cooker soon... how to find which versiona build is like, whether its manila or titanium or etc...
My suggestion would be to download my kitchen as you can preload ROMs on there. If you have my kitchen already, click on Load Rom and you'll be brought to .erv files.. Here you can see the types of ROMs that I have premade for teaching purposes. They will show you what's in a manila ROM, a titanium ROM and my other ROMs..
where actually ur config .erv files are saved?? do i need to download them from anywhere as i cant find it in ur kitchen... am waiting for ur reply..
can i get SD version of stock rom as i am getting problem to install ruu version.. i cooked a rom and it is not able to run a ruu, in bootloader it doesnt goes beyond 1%... any suggestion would be really great!!
When you click on Load ROM point the folder/explorer to "Working_Folder\TOOLS\RomSaved"
If you don't see any .erv files in there than you don't have the correct kitchen..
i don have these but i downloaded these but i cant find these files..
can i get SD version of stock rom as i am getting problem to install ruu version.. i cooked a rom and it is not able to run a ruu, in bootloader it doesnt goes beyond 1%... any suggestion would be really great!!
some how i sorted it out.. i have downloaded the kitchen 4xx MB.. it has only 3 XIP and many SYS file version.. is it fine to builde with different versions?
You have to click on HERALD in the drop down menu under DEVICE: and then you'll be able to see all the builds..
oh ****.. am getting soo stupid that i forgot that
Did you get into the bootloader and were you able to flash one of my ROMs?
Tribulattifather said:
Did you get into the bootloader and were you able to flash one of my ROMs?
Click to expand...
Click to collapse
i can flash ur roms but not stock roms.. it hangs up and restarts at 1%.. today am going to give my mobile to service center.. pls pls help me
lol, once you get onto one of my ROMs then you can flash to anything else.
its strange.. i have herald mobile but its not flashing with herald file, but with stock rom of wing mobile....

Categories

Resources