maybe someone more linux savvy can check into this.
a search on our kernel version 2.6.27 thats on the moment brings up a website with a program for a local root vulnerability.
http://www.milw0rm.com/exploits/9545
not sure if it can be compiled for android... Just trying to help
I compiled it, and i am trying to get it to work but its running me into a brick wall. Its weird cause it works on my computer(full linux)... so Ill keep trying
Intresting indeed. I wish i could figure it out, but i dont know anything about linux.
there is some additional info over at ppc geeks here
http://forum.ppcgeeks.com/showthread.php?t=96237
Have you rewritten the x86 assembly instructions for ARM assembly? Also, I tried one of the milw0rm exploits on my Moment...seems they patched the kernel before the release.
I managed to discover a root exploit but its not the same as we are used to thanks to Samsungs stupid RFS aka FAT16 rom file system.
I'm nor knowledgable to make a rom, but hopefully this can be used to redo the rom in yffs2 so that it will work with existing apps, because even if we COULD keep root, stuff doesnt work, like nandroid, or Root Explorer.
http://www.samsungmomentforum.com/how-to/root-access-(finally-achieved!)/
I know many devs frequent xda and with zefie's root expliot maybe someone with the knowledge can create a rom for it in yffs2 using the source code samsung released.
Link: http://phandroid.com/2009/11/24/sprints-moment-open-source-released-by-samsung/
While this may seem like a simple quick "YES" answer, I know there are some differences - because I've unlocked MANY MyTouch(es) - and never seen one NOT find the code to unlock.
This Fender would NOT unlock, that's how I ended up with it.
I'm a long time iPhone user, and want to dabble with Android - so this is my chance. I'd like to root it, and see what's the fuss. But want to make sure it's possible before I try.
Do you want to root it or unlock it? There's a difference between the two.
If you want to unlock it, just buy the unlock code or wait 3 months if you bought it with T-Mobile and they will give you the unlock code so you can use it with any provider that uses a sim card.
If you want to root it, there's two threads that I have seen that I have seen in the development forum that give you a step by step procedures.
Cursordroid has even released a Fender rom with root for when you decide to do this.
any chance of grabbing that music app from it? Looks sweet...
I want to root it, even tho I don't know what advantages that would have yet. I'm an iPhone guy ... have been for a couple years now, so I wanted to see what Android was about now.
What are the real advantages of rooting? (sorry - I know this is major noob stuff)
Everything to get you started about rooting and unlocking is a stickied thread in the "Android Development" sub-forum.
I would not judge Android 1.6 too harshly. Remember that it is not the latest build. For a fairer comparison against the iPhone OS 3, Nexus One's 2.1 or Droid's 2.01 is better.
Of course, you can always install a custom 2.1 ROM like Manup456's, but right now, all Eclair ROMs are a bit buggy, and the GUI is not as smooth as can be.
According to what i'm reading, the fender edition is new hardware - and there is no advantage to rooting yet anyway... because there are no compatible roms yet.
Araltd said:
According to what i'm reading, the fender edition is new hardware - and there is no advantage to rooting yet anyway... because there are no compatible roms yet.
Click to expand...
Click to collapse
check out http://forum.xda-developers.com/showthread.php?t=622530 fender edition root info and the only "fully" working rom
Hey,
I've just recently started Android development and I'm keen to learn as much as I can about the whole system, not just about SDK app development. As such I'm interested in attempting to build my own ROM completely from scratch. I've downloaded the Android Source (and Galaxy S source) and would like to try my luck.
First I've been mucking around creating custom ROMs with the emulator, moving apps from the Galaxy S ROM I dumped from my device onto the stock emulator ROM and testing things out.
Anyway I'm at the point where I'm wondering if it's possible to flash the stock emulator ROM onto a Galaxy S phone? I know the Galaxy S source includes a lot of device specific stuff however I'm not interested in getting the camera, bluetooth or anything hardware specific working just yet.
If I flash a ROM with a stock kernel, drivers etc. onto my phone will it work? Has anyone done this? Will it just brick my phone?
Any help would be appreciated.
Cheers,
Ben
Anyone?
Also, I know people have flashed AOSP ROMs on other phones, does anyone know if they required modifications or whether they are in fact stock ROMs?
nje, can't work. why?
1) different bootloaders
2) different partition layout
3) different (kernel)drivers
4) different vendor setup
etc.
it is possible to flash the emulator image onto a dev device (dream/sapphire) but even then a lot will not work properly!
if you want to learn about the android architecture you should start with building a kernel (there is already a thread about that here) and playing around with stuff like the (file)system and utilities...
Thanks jodue.
Yeah my long term intentions were definitely to build the Galaxy S kernel and any necessary libraries and drivers specifically necessary for the apps I decide to include in a custom ROM.
I was hoping that I'd be able to start out by tweaking a minimalistic/generic ROM (the AOSP default ROM) on my Galaxy S. However, as you've pointed out I'll have to start out with the kernel and all the device specific stuff first.
I've got quite a bit of information on building an Android/linux kernel both from the thread you mentioned and also the official AOSP page. However information on putting together a complete working ROM seems a bit sparse. Does anyone know where I can find some information on the topic?
I'm also curious to learn about the list of things jodue mentioned i.e. Android bootloaders, partition layouts and drivers (generic and Galaxy S specific). I assume detailed information about particular devices and drivers probably isn't available but if anyone even knows where I can learn detailed information about default AOSP ROMs I'd be extremely interested know.
I read couples of threads and realize that if a CM mod is wanted, MS2 must have its bootloader unlock.
Since most work is done in /system partition, why do a bootloader modify is needed?
According to the update.zip, we can modify /system partition already, so why do we need bootloader unlock?
CyanogenMod needs its own kernel.
I guess that, since cyanogen is based on gingerbread now,
it runs with a more up-to-date kernel than the milestone's.
The locked bootloader and the efuse thing prevents updating the kernel.
It's possible that someone, using Cyanogen source, makes a backport running on our kernel, but I think it's a huge work...
However, the clever guys from freemymoto.com have created a hack that is capable of launching an other kernel after the legit one starts.
If salvation comes (Cyanogen alleluia ), it will certainly come from this project.
Actually, the hack works on DroidX, and Droid2. So it is 99.9% sure that with some work, it may run on milestone 2 as well.
So, to get Cyanogen work on MM2, we need :
- A very good developer, with android (of course !), linux kernel and kinit knowledge, able to port freemymoto's hack, and Cyanogen
- Hardware drivers for the Milestone (bluetooth, lan, gsm, 3g, touchscreen...)
If we find the golden dev, I personnally think that CyanogenMod could be out for milestone2 sooner than what most people think...
momus87 said:
CyanogenMod needs its own kernel.
I guess that, since cyanogen is based on gingerbread now,
it runs with a more up-to-date kernel than the milestone's.
The locked bootloader and the efuse thing prevents updating the kernel.
It's possible that someone, using Cyanogen source, makes a backport running on our kernel, but I think it's a huge work...
However, the clever guys from freemymoto.com have created a hack that is capable of launching an other kernel after the legit one starts.
If salvation comes (Cyanogen alleluia ), it will certainly come from this project.
Actually, the hack works on DroidX, and Droid2. So it is 99.9% sure that with some work, it may run on milestone 2 as well.
So, to get Cyanogen work on MM2, we need :
- A very good developer, with android (of course !), linux kernel and kinit knowledge, able to port freemymoto's hack, and Cyanogen
- Hardware drivers for the Milestone (bluetooth, lan, gsm, 3g, touchscreen...)
If we find the golden dev, I personnally think that CyanogenMod could be out for milestone2 sooner than what most people think...
Click to expand...
Click to collapse
I LOVE YOUR REPLY!
Well, this is the first reply to me in this forum.Ya...nobody reply me before...so bad..
Milestone has also a locked bootloader, but a CM7 port running on it. That is what makes me want to do something on my MS2.
I'm a C++ programmer, so I learn everything about this these days.
Thank you, really.
And I think I'd read all the freemymoto.com site RIGHT NOW~~
Well, if you think you can be the golden dev, you just made my day...
If you try this, I (and almost everybody here) will at least help providing the hardware drivers.
But the first step is to make the hack work on MM2...
Edit : For the milestone1, the bootloader security has been compromised using a leaked unofficial rom build,
which lead to custom kernels, without needing a hack like freemymoto's.
In fact, freemymoto's hack is based on a milestone1 project, which was abandoned after the rom leak.
It circumvents both bootloader lock and efuse by starting a second kernel after the first one.
(What I couldn't figure out is what happens of the first one... Still in memory? Still using some ressources?)
I read the site yesterday, however sadly, I don't have any experience about writing drivers of cell phone.
So I just sent a e-mail to them to ask if I can provide any help and what to do.
Hope I can help. I'll try my best.
For about the second kernel...I guess I have to read source to know what happened to them...
Anyway, thank you for your reply. At least I get a way to help^^
I didn't mean that we will have to write the drivers from scratch. But we will have to find them.
Hopefully, most of them are open-source. Wifi/bluetooth per example, is handled by a wl1271 chip. Drivers are available on texas instruments website...
You should get in touch with Pizzaroll, who is also trying to make the hack work on milestone2
It's really good news that there maybe a hack bootloader, i like my mm2 but it is really a pity that no much ROM.
liuyanghejerry...
Polish team try to broke bootloader with Boinc (many computers calculate 1 thing), maybe You and Yours friends can join to project?
In China lives maaaaany peoples, this can be speed up calculations
I don't think that distributed computing is the solution...
Even if the boinc project lets us find the signing key, we will have to do the same for the efuse thing.
The freemymoto's hack is a solution to circumvent both of these protections, and doesn't need any computing.
We only need someone to modify some parts of the code to make it work on Milestone2.
Tomszyn said:
liuyanghejerry...
Polish team try to broke bootloader with Boinc (many computers calculate 1 thing), maybe You and Yours friends can join to project?
In China lives maaaaany peoples, this can be speed up calculations
Click to expand...
Click to collapse
Currently I'm studying kexec method now, thanks to PizzaRoll and momus87's help^^
Well, in fact, I like to program and burn my brain. However, the Boinc method seems not really interesting...
Well Boinc is the best solution if you want to use bruteforce.
But even with a whole army of core i7, bruteforcing a 1024bits key is unthinkable actually...
Is this eFuse thing harder to break than the one used in iPhone? If it is then Mr Jobs should adopt a similar approach.
Here goes, I received a micro velocity Cruz t105 tablet from a friend..its a little tacky. Anyway.being its a little older most of the site links and apps that I can find are outdated.
What I'm asking is. I'm pretty new to the android development. I've seen there a custom ROMs for the device.also I've seen that u can use z4root and abd to modify it. Are these apps android specific.like can i use them on any android device.or do I need to find the correct file for the specific device.
sent from my USTMO HD2 android gingerbread