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.
(Since I'm a newbie, I can't post in development forums, so I guess this goes here for now. If this is the wrong place, I apologise.)
I have an Asus Zenpad 8.0 (Z380M/P00A), which doesn't seem to have any support from the custom rom community. This is not surprising as it's a fairly uncommon device, and until recently, Asus has been less than helpful. However, the latest firmware update (supposedly; I haven't pulled the trigger yet) allows the Asus bootloader unlock utility to work on this tablet.
I've wanted to replace Asus's firmware since I bought the thing. I know that it's an uncommon device, so I'll have to do all the work myself. I'm an experienced Linux hacker, so I know how to configure and build kernels, how Linux OS images are constructed, how to read/write C, etc. However, I'm a bit of an Android newbie.
I figured the first step would be to port TeamWin recovery, so I'd have a way out if I brick the thing. But (from what I've been able to find) porting TeamWin requires a working CM or (preferably) Omni port. So it's kinda a chicken and egg problem. Do people just port roms using stock recovery and hope for the best? Or is there a (more involved, I'm sure) way of porting TeamWin that doesn't require an existing port? Or is there some other recovery (I don't know about) that's more standalone?
And then there's the issue of porting the OS itself. For thier part, Asus provides kernel souces, firmware images, and the aforementioned boot loader unlock utility. I imagine to get started, one has to compile a kernel and combine it with binary blobs extracted from the firmware image, but I'm not entirely sure.
I've looked around for porting information, but the guides I found all seem to assume you've got a working device tree from one mod that you want to graft onto another. I couldn't find much about really starting from (nearly) nothing. I'd like to say I'm surprised Google doesn't have something written up, but given how unhelpful I've found a lot of thier Android docs in the past, I'm not.
I'm mostly interested in porting AOSP to start, but I'd be willing to start somewhere else if some other ROM is easier to work with. Anyway, thanks in advance for any suggestions or advice you might have to offer.
Any progress on this? I was able to flash twrp and root my Asus Zenpad 8.0 (Z380M/P00A), but had no luck finding a compatible rom. Did you get to compile one? Thanks!
How would you unlock the bootloader for this device?
It may be obvious to others,but... What (if anything) does the project treble requirement to be able to boot a vanilla Android ROM do to the idea of the OEM locked bootloader?
I know that there are devs working on bringing project Treble to older/non-treble devices, but going forward, will devices shipping with Oreo, P and others in future be able to have OEM locked bootloaders and still meet the requirement of booting a vanilla android image?
I'm interested as I've not felt the need for a custom ROM since KitKat.
David _J_D said:
It may be obvious to others,but... What (if anything) does the project treble requirement to be able to boot a vanilla Android ROM do to the idea of the OEM locked bootloader?
I know that there are devs working on bringing project Treble to older/non-treble devices, but going forward, will devices shipping with Oreo, P and others in future be able to have OEM locked bootloaders and still meet the requirement of booting a vanilla android image?
I'm interested as I've not felt the need for a custom ROM since KitKat.
Click to expand...
Click to collapse
Yes as long as you can unlock the bootloader you can flash other system images to it or do whatever you want with the device.
But with a locked bootloader you cant alter the necessary system partition despite the device is treble partitioned.
PhonyOnXDA said:
Yes as long as you can unlock the bootloader you can flash other system images to it or do whatever you want with the device.
But with a locked bootloader you cant alter the necessary system partition despite the device is treble partitioned.
Click to expand...
Click to collapse
After loading a GSI Treble ROM can the bootloader be relocked?
Hey, long time no see... I had to sell my xperia z3 last night, so I bought this XT1254 Droid Turbo.... Which is on MCG24.25-5-5 Build.... Android version 6.0.1 Security Patch level January 1, 2017....
I searched around here and found some complex methods for twrp and root, so I thought about posting here... I already did root Z3 unlocked it's bootloader and stuf..
So Is there any less complex method for these things? I don't wanna unlock bootloader for camera quality sake but I'd only like to know about rooting, twrp and a fast android 7 custom rom which is fast / battery saver, supports xposed etc if possible.. (Links would be useful, if someone can) So... Please point me in the right direction..
Else i'm staying stock. Thank you very much in advance.
Anyone???
I have a rooted Snapdragon S8 (done by this method) and I want to install LineageOS (or any other non-samsung android build) onto it.
I have searched far and wide on this form an the internet and I have not been able to find a single custom ROM for the Snapdragon S8. Does anyone know of any of these ROMs that exist?
If they do not exist, would it be possible for me to make one? Is there a tutorial or resource to help me with this? I have a decent amount of experience with rather technical programming on the PC (writing Linux kernel code, etc.) so I would not be walking in completely blind to the topic, however, I have never really messed with android before (besides rooting this phone and a couple of Nexus devices).
I apologize if this is a repeated question, like I said, I couldn't find anything.
Thank you in advance for any and all help!
sckzor said:
I have a rooted Snapdragon S8 (done by this method) and I want to install LineageOS (or any other non-samsung android build) onto it.
I have searched far and wide on this form an the internet and I have not been able to find a single custom ROM for the Snapdragon S8. Does anyone know of any of these ROMs that exist?
If they do not exist, would it be possible for me to make one? Is there a tutorial or resource to help me with this? I have a decent amount of experience with rather technical programming on the PC (writing Linux kernel code, etc.) so I would not be walking in completely blind to the topic, however, I have never really messed with android before (besides rooting this phone and a couple of Nexus devices).
I apologize if this is a repeated question, like I said, I couldn't find anything.
Thank you in advance for any and all help!
Click to expand...
Click to collapse
I also have mine with root I have tried with a lineage rom from an s4 but it installs but does not start. Look at the forum, maybe they will help you to achieve one.
ROOT_8_SERIES_AND_OLDER
You can view and join @S8_N8_ROOT right away.
t.me