I have been thinking of a side project i can start and since i recently acquired a wave and have a SGS myself it seems like a fun project. I found out that it has a hummingbird processor and may not be much difference from a Galaxy S in terms for hardware. Right now I'm just collecting as much information as i can about the device and what similarities the Wave has to a Samsung Galaxy S i9000.
So throw me what you got, its not an easy task and will need help, i have started another thread to see if i can get some Devs interested in this project and are willing to help in the android section
The idea is to port the Galaxy S i9000 firmware to the Wave that way you still have the samsung feel and since its made for the hummingbird processor. We will first need to see if we can get access to hardware and use that to inject code etc. This is in the research stage as of now.
THIS IS JUST A START AND MAY DIE BEFORE IT EVEN BEGINS. SO DON'T COMPLAIN WHY IT WAS STOPPED. I AM DOING THIS ONLY TO SEE IF I CAN DO IT AND NOTHING MORE.
If only i know C++ language, ican help you but i don't know. I'll follow and wait your results.
Keep going my friend. If you success (i hope) i will pay you to get the firmware!
thanx for starting this. i have visited forums where people are trying to port android on wave. And there biggest problem is bootloader. they cant dissemble it, just want to provide you this info. i will provide more info as soon as i get on any forums. This is the only way i can help, as i am only a application developer.
adfree is working on bootloader. Please, contact him.
@ jebise101
But you read this first?
http://forum.xda-developers.com/showthread.php?t=899535
I9000 stuff is available... but remember Baseband is Infineon... not Qualcomm...
Aplication Processor is identical...
Maybe more luck with Galaxy K M130K Firmware:
http://forum.xda-developers.com/showpost.php?p=12083886&postcount=7
But I can't find Firmware for M130K
Go find Firmware from M130K with BootFiles.
it says original firmware for M130K but not sure
pspmaster. tistory. com/48
looks like it is the firmware you wanted adfree
here is the link righ here easier http://pspmaster.tistory.com/48
use google chrome with this page as it is in korean
Well, if you google M130K-KIES, you can get the firmware via 4share, but the file it got was without the boot.bin :-(. But I'm not sure about the firmware from pspmaster.
whats with this project ?
http://www.androidport.net/
pawlakpl this site androidport.net never end this project becouse no money.
Here is an app someone created i will try it when i get home to see if if i can get it to download the Korean SGS firmware (use to use it all the time back when i had the O2, if anyohne wants to give it a shot feel free
http://www.modaco.com/content/i8000...41/samsung-mobile-firmware-queries-downloads/
cinimini said:
pawlakpl this site androidport.net never end this project becouse no money.
Click to expand...
Click to collapse
But XDA can end a project ?
I've downloaded M130K-HOME-REV04-EA29.tar
Thanx to hsingh56 and mylove90.
As I've searched several hours via Google with no success...
Now I have also Bootloader files from M130K... but looks totally different as I thought...
Anyway... I9000 and M130K have similar folders/files...
factoryfs.rfs.img
Rename into *.img like above. And extract with WinImage for instance...
Then use open eyes.
1.
Few Images are QMG... for PowerOFF QMG Animation...
2.
*.so files
3.
lib\hw
...s5pc110.so
But anyway. As long NOBODY try with JTAG (RIFF BOX) + Wave S8500 + knowledge different combinations. If Boot area is secured?
We will NEVER see Android on Wave...
Best Regards
So the wuestion is....
Whos have JTAG+S8500+Knowledge+Free time to help the bootloader creation?
Yes,boot and sbl is secured(e-fused)
cinimini said:
pawlakpl this site androidport.net never end this project becouse no money.
Click to expand...
Click to collapse
Euhmm. If you guys actually READ The site it shows we are working. Only we PROBALY need IDA. But we're in touch with Dopi from IDA. if things work out we will have the bootloader disassembled within 2 weeks and we can start testing the modified FW from the Galaxy S
ShadowAS1 said:
Euhmm. If you guys actually READ The site it shows we are working. Only we PROBALY need IDA. But we're in touch with Dopi from IDA. if things work out we will have the bootloader disassembled within 2 weeks and we can start testing the modified FW from the Galaxy S
Click to expand...
Click to collapse
Great news! Keep up the good work.
ShadowAS1 said:
Euhmm. If you guys actually READ The site it shows we are working. Only we PROBALY need IDA. But we're in touch with Dopi from IDA. if things work out we will have the bootloader disassembled within 2 weeks and we can start testing the modified FW from the Galaxy S
Click to expand...
Click to collapse
Please, STOP. I won't comment on that nonsense. Let me just say good riddance to you and come back with the results. We already had enough talking and it's time for you to show whether you can distinguish ARMv4, ARMv7, decrypted, encrypted executables and any basics of code signing.
great initiative...keep it up the work and never give up...
Ok i am new to the android os and of course did not read up on unrooting and accepting the ota yes i know dumbass. I have 2 other evo's anyway to copy information off one of my other phones onto ota updated phone to get back to froyo(i know noob question) just thought i would throw that out there to see if anyone smarter than me knows if this is possible
shmoeman said:
Ok i am new to the android os and of course did not read up on unrooting and accepting the ota yes i know dumbass. I have 2 other evo's anyway to copy information off one of my other phones onto ota updated phone to get back to froyo(i know noob question) just thought i would throw that out there to see if anyone smarter than me knows if this is possible
Click to expand...
Click to collapse
Nope, this new update is locked down tight for the moment. You'll have to wait until a new exploit is found before you'll be able to do anything with it.
gb root
i just saw this on another website. Gingerbread’s source code is now available to the public. Jean-Baptiste Quero, an engineer at Google’s Android Open-Source Project (AOSP), posted the announcement early this afternoon on a Google Groups message board, making Android devs the world over a very happy group of people.Quero had warned that it would take several hours for the code to finish pushing to the servers.Also keep in mind that this is just source code. If you don’t know what to do with it, you should probably just wait a day or so, so the speeds aren’t so bad for the various developers who will be putting it to immediate use.
Details: http://thetechjournal.com/electroni...source-code-now-available.xhtml#ixzz1P6RRI2Qm
does this mean we might be able to root again soon?
http://thetechjournal.com/electroni...3-gingerbread-source-code-now-available.xhtml
Greetings all,
I would like to know something that seems to be so simple it hasn't been documented here anywhere.
My question is: How do I build the source provided by Google for my Desire HD?
Yes, there are tutorials, don't point me to them. They either provide you with the AOKP way or the CM way.
I want to build my stuff from scratch.
Is there a generator that will create the necessary file structures for me (in the devices folder)?
Is there a complete list that my rom needs to include in order to make it run on my device (preferably a list of folders I need)?
I know about the vendor files, these are created by a third party. How do I know what vendor files I need to create? How do I know how to name them?
Don't get me wrong, I've used C, C++ and C# for YEARS (I think about 8 now) and I know how to code. I just don't know how to compile android!
It doesn't seem that hard though, I've seen threads where people provide ROMs for the Desire HD without even having the device!
Also, how would I test this and debug it? I don't think it's safe to just flash my rom once I get it compiled to my actual device and possibly brick it.. Can I use an emulator?
I hope you will read this post before answering something alike "Plenty tutorials" or "This can be found everywhere", because it can not. I can only find AOKP or CM ways, I want neither.
Greetings Ultimate-Tester
The only time I know of that this has been achieved for this device is aospX, an ICS ROM on the Inspire 4G forums. It is much harder than you would think. Google does not support this hardware, HTC does. So there was never AOSP source for this device.
Yes, I can imagine how hard it is. As I said I have programming experience, it's just that I don't have it with Android ROMS.
I have built mainly for Windows, also on Ring0 level (which is the lowest level you can get) so I think making drivers is a task I can handle. I am definitely not underestimating it.
Could anyone give me an answer to this line:
Code:
Is there a generator that will create the necessary file structures for me (in the devices folder)?
Is there a complete list that my rom needs to include in order to make it run on my device (preferably a list of folders I need)?
I am very interested in how other people knew what folders to create and what files to put in them. How would the Google Source (envsetup) know which device files to use and what not? Again, can I generate the file structure somehow?
Greetings,,
My suggestion is to use device trees from AOSP-based ROMs that already exist for this device. For example, look in the cfX manifest.xml for Ace-specific stuff (kernel, device, etc.). I personally haven't seriously tried this before, so that's all I can offer.
Okidoki, will do. Then for the last item: Testing.
What will be a safe way to test out my brew?
What will actually happen if I flash a ROM with missing files? I hope there's an underlying catcher that will send something I can see in logcat and fix it that way.. Is this the case, or will I immediately brick my phone once I do something wrong? Do I need to make sure something is 100% there in order to reach my recovery again?
Greetz,,
I'm nor aware of any safety nets. If you're developing, you probably have to be willing to take the risks.
I bought this phone (V 3.6.8) to get re-involved with programming (away for over a decade). It's a nice piece of hardware at an incredibly cheap price. Like everyone here, I am frustrated with a locked bootloader and now no root. While I "try" to get up to speed (a lot to learn!) in the android world, I'll be glad to help in any way I can. Some questions I have:
1. Does anyone know some of the differences in V3.5.0 which can be rooted and V3.6.8 which can't be downgraded to V3.5.0?
2. Has anyone compared the now available source code versions released by Amazon?
3. Does anyone know which source code versions are used with V3.5.0 and V3.6.8 (or is it the same)?
4. Does anyone know if the partition setup for V3.5.0 and V3.6.8 are the same?
I realize there might be more important questions (build.prop issues?), so any help I can get to get started would be appreciated.
Hi
I have asked this before but I haven't gotten the answer and some things have changed.
My goal is to edit the kernel of my device to include rtl8192cu driver.
I have the sources from http://gitgub.com/puresoul/android_kernel_lge_d605 (I hope I got the link right) I am currently stuck at creating the .config file and getting the right files to include the driver. Could anyone help me out, any links to tutorials that actually tell me how to? The guides online are almost all specific to a certain device or their goal is different.