I finally decided to ask a question that's been bugging me for a few days now, with all android development going around in a very impressive pace.
Now I am completly new to kernel concept so don't me too harsh if I said something wrong.
The question: Isn't there really a way to modify/update our kernel since we have locked bootloader?
As far as I understood, most of us are running ICS UI on top of GB kernel (even some on top of Froyo kernel) but this does not give us the advantage of running ICS on it full force and take full advantage of your harware.
I know Endless7 had a method to downgrade kernel, and I thought may be there can be a similar way to upgrade it.
With JB just around the corner, that would be a great improvement IMHO for our device.
Megalith27 said:
I finally decided to ask a question that's been bugging me for a few days now, with all android development going around in a very impressive pace.
Now I am completly new to kernel concept so don't me too harsh if I said something wrong.
The question: Isn't there really a way to modify/update our kernel since we have locked bootloader?
As far as I understood, most of us are running ICS UI on top of GB kernel (even some on top of Froyo kernel) but this does not give us the advantage of running ICS on it full force and take full advantage of your harware.
I know Endless7 had a method to downgrade kernel, and I thought may be there can be a similar way to upgrade it.
With JB just around the corner, that would be a great improvement IMHO for our device.
Click to expand...
Click to collapse
I'm no expert but I think this has to be done by motorola, since the kernel is the one responsible for the hardware management, and given the bootloader is locked we can't put custom kernels in our phone
Caesarivs said:
I'm no expert but I think this has to be done by motorola, since the kernel is the one responsible for the hardware management, and given the bootloader is locked we can't put custom kernels in our phone
Click to expand...
Click to collapse
Thanks for the reply. I do realize that and as Moto stated clearly that MS2 will not see official ICS there is not hope to get it from Moto.
But I thought maybe it can be ported from other device, or some modules, which share same CPU.
I am pretty sure our devs have looked into this but since we even got HWA working lol anything is possible these days.
There is a new bootloader hijacker called kexec which allows loading custom kernels. Hashcode is doing it for the Droid 3, and if I'm not wrong, it's designed specially for Motorola Phones with locked bootloaders. But you have to implement new drivers for video and such, so it's a lot of work.
Sent from my XT860 using xda app-developers app
elleypo Ière
Megalith27 said:
Thanks for the reply. I do realize that and as Moto stated clearly that MS2 will not see official ICS there is not hope to get it from Moto.
But I thought maybe it can be ported from other device, or some modules, which share same CPU.
I am pretty sure our devs have looked into this but since we even got HWA working lol anything is possible these days.
Click to expand...
Click to collapse
The problem is that it's not *only* a "same cpu" problem, it's the whole hardware solution.... camera, sound, gpu, and so on.
It's one of the reasons the dev on MS2 is so "slow", with the locked bootloader, non support from Motorola, the multiple versions (Droid2/Droid2 Global, MS2 EU/CH/NA and so on), getting the hardware to work (specially with newer android like ICS/JB is/was a pain, and most of the work was done "porting" those from the Defy/Atrix and so on who have, somewhat, partially the same hardware and can be adapted.
On top of that, changing the kernel as already said would mean to find a security flaw/hole in the bootloader that could be exploited for that.
(the downgrade solution was patched/fixed with the latest european, and now Latin America bootloader/kernel upgrades if i remember well, hence why most europeans who upgraded to the latest OTA don't really have a working CM7, since it requires to flash fixed sbf and other things to make it work (a patched recovery partition i think)).
But really, having the dev (forgot his name, danthingyabak ) getting full HW acceleration, and a working ICS port and pretty much everything working now, while LA and China starts getting remotely the same versions, we might see more develeoppement coming, since it's no longer "region specific" devs. Maybe even one day Droid 2/Droid 2 Global and MS will share the same developpements, who knows (or, maybe by Miracle, now that Google owns Motorola, maybe one day we will see unlocked bootloaders for all phone yeah i'm dreaming ).
What about us now?!
http://androidcommunity.com/motorola-finally-unlocking-bootloaders-for-real-this-time-20120726/
I hope it's true!
PS. But if it's not about us again, we hope that this method will work even be
xenusr said:
I hope it's true!
PS. But if it's not about us again, we hope that this method will work even be
Click to expand...
Click to collapse
I think that thing was just a false alarm...or early celebration...
Sent from my MotoA953
Looks like we're finally getting there
http://androidcommunity.com/motorol...live-finally-can-unlock-bootloaders-20120817/
Related
So does anybody know if any devs are working to port CM6 over to the X?
Cm6 uses a modified kernel, as of now, I believe we are still limited to only running a stock kernel on the dx else we anger the motorola instant brick bomb.
If they can get around that I think we will start to see work on the cm rom coming over. Otherwise we'll be using roms built for dx with stock kernel.
At least I think that's the case.
Sent from my DROIDX using XDA App
I think it is more a matter that none of TeamDouche has a DX (except for Koush and he pretty much works (almost) exclusively on the custom recovery end of things).
Without a device they don't work on ports. The SGS devices have portions of encrypted code in the bootloader (I think) but, they just don't have a custom kernel for it.
I believe they could port CM over to the DX - but, we have to find a dev that knows what he is doing to volunteer to work on it (and, work with TeamDouche). I wish I knew enough or had enough time to learn. :-(
shaneaus said:
I think it is more a matter that none of TeamDouche has a DX (except for Koush and he pretty much works (almost) exclusively on the custom recovery end of things).
Without a device they don't work on ports. The SGS devices have portions of encrypted code in the bootloader (I think) but, they just don't have a custom kernel for it.
I believe they could port CM over to the DX - but, we have to find a dev that knows what he is doing to volunteer to work on it (and, work with TeamDouche). I wish I knew enough or had enough time to learn. :-(
Click to expand...
Click to collapse
Until the bootloader gets opened up, we will never see a CM6 port.
Sorry to squash anyones hopes, but its best u know now and get over it
Way to many kernel changes for us to have CM6 without an unlocked bootloader. Just not gonna happen... Yet.
Other than these two:
Overclocking
Loading modded roms
I mean let's all be honest, even if you undervolt and remain stable, any overclocking that will allow noticable performance, will have just as much noticable effect on the battery. And these are mobile devices. Battery should be considered top priority, not speed.
And what's the deal with wanting to load all these custom roms? Are they significantly better than stock, Adeo, or gingerblur? What do we need to load a fully custom rom for? Are they lightning fast and extend battery life by 100%? I guess I just don't get it. Deodexing and visual mods can be done without an unlocked bootloader.
Basically what im trying to say is. What is everyone *****ing about?
Sent from my Atrix using XDA App
As far as I know, there is no way to unlock the Atrix's bootloader. It is encrypted. You may check the xda's frontpage, there is news several weeks ago regards to the Moto's bootloader.
mccoy007 said:
As far as I know, there is no way to unlock the Atrix's bootloader. It is encrypted. You may check the xda's frontpage, there is news several weeks ago regards to the Moto's bootloader.
Click to expand...
Click to collapse
I think you missed the purpose of the thread. He is not asking HOW to do it, only WHY you would need to, other then overclocking or loading ROMs.
Honestly, it does make a big difference. Battery life can be very substantially increased in many of these roms. They both over and under clock processors to maximize the life. It's possible to get gingerbread on the inspire right now through custom roms because the boot loader isnt locked. It's possible to completely remove sense, whereas we have to live with motoblur. There really are a lot of reasons. Honestly, look at what Xda is all about, it's android development. Just take a look at the atrix dev forum vs the inspire one. Phones with a strong development community tend to live far longer because they can upgrade the os long after the company stops trying. The original g1 was only officially upgraded to 1.6 (I believe) but Xda has a few 2.2 roms that actually run pretty solid.
Tl:dr the list goes on and on of reasons that you want an accessible boot loader.
Ability to load a custom recovery menu. Nandroid.
it's simple dude. people do it because they can.
Besides the fact you would get work and support from the awesome devs here another good reason would be most phones have their shortcomings.Most of the time this can be fixed in the software.The awesome devs here are able to in most cases get it sorted out within a week or 2 whereas if the phone manufacturer or carrier is gonna do something about it your gonna wait 6 months to get an update. A prime example of this was the rediculously low external and earpiece speaker volume on the inspire.On max volume it was just too low. Now the rom chefs can cook up custom roms with 20% volume increase.
The 2 reasons you want to exclude are the main points. It's like saying "other than drowning; what's the point of learning to swim".
i want android 2.3.3 , can i ? no! i have to wait to an official update from motorola.. why ?!
i want htc sence in motorola , can i ? no !
we love to play and change things.. uman nature
seh6183 said:
Other than these two:
Overclocking
Loading modded roms
I mean let's all be honest, even if you undervolt and remain stable, any overclocking that will allow noticable performance, will have just as much noticable effect on the battery. And these are mobile devices. Battery should be considered top priority, not speed.
And what's the deal with wanting to load all these custom roms? Are they significantly better than stock, Adeo, or gingerblur? What do we need to load a fully custom rom for? Are they lightning fast and extend battery life by 100%? I guess I just don't get it. Deodexing and visual mods can be done without an unlocked bootloader.
Basically what im trying to say is. What is everyone *****ing about?
Sent from my Atrix using XDA App
Click to expand...
Click to collapse
Your first question says "ignoring custom ROMs..." and your second question says "What about custom Roms..." so I'll address the second question.
ROMs. Gingerbread. AOSP. Stock Android. Kernels.
Another consideration in favor of ROMs is the continuation of support by the dev community even after the manufacturer has EOL'ed a product. You still see the Dream (G1) getting roms with new features even though the phone has been effectively dead for a while now.
It is always in the phone manufacturer's and the carrier's best interests to kill off support to get you to buy the newest, latest device.
daveop said:
Just take a look at the atrix dev forum vs the inspire one. Phones with a strong development community tend to live far longer because they can upgrade the os long after the company stops trying.
Click to expand...
Click to collapse
I love my atrix.. but I visited the Inspire 4G dev forums... and.. yeah I got a little bit jealous. lol
I hope the few devs we have don't end up leaving and can crack this bootloader!!!!
s1mpd1ddy said:
I love my atrix.. but I visited the Inspire 4G dev forums... and.. yeah I got a little bit jealous. lol
I hope the few devs we have don't end up leaving and can crack this bootloader!!!!
Click to expand...
Click to collapse
I know what you mean. That's one thing I like/liked about my FUZE: there was a pretty active dev community, at least until the HD2 came out.
I'm planning on getting an Atrix on Monday and this is making me think about getting an Inspire instead. I guess I'll get the Atrix and if it blows I can take it back, get an inspire, and pocket $100.
Wow is this seriously a question?
Nandroid backups, AOSP ROMs like Cyanogen where you get updates every NIGHT if you wish from the source Android build so it'll always be the latest version - no waiting for Motocrap. Battery life is usually way better, TONS of tweaks (being able to tweak my color balance of the screen, gamma levels, haptic feedback behavior, autobrightness levels and thresholds, lockscreen and messaging gestures, etc). That's all before even mentioning performance increases like overclocking, deodexing for themes, ext4 modifications for faster I/O. There's just way too many things to list but if you've never experienced a phone that has custom ROMs (especially Cyanogen) then I can see why you don't miss anything, but if you have, like me, you'll probably never want to settle for an Android phone that doesn't allow custom ROMs.
custom roms is reason enough...like dinan said if you ever used them you would understand. pretty much all the problems that people are having with the atrix could be solved if our devs had access to the bootloader.
I do see the importance of having continued support after moto leaves the phone behind. And it would be nice to have a dev make a rom to fix the coloring on the Atrix screen. Also I didn't realize that updates to custom roms come so often and that they had that much support.
I am starting to see now.
Sent from my Atrix using XDA App
mccoy007 said:
As far as I know, there is no way to unlock the Atrix's bootloader. It is encrypted. You may check the xda's frontpage, there is news several weeks ago regards to the Moto's bootloader.
Click to expand...
Click to collapse
Luckily, there are a few other people working on the bootloader (I hope), as it is signed, not encrypted; there is a difference.
My phone before the Atrix was the TytnII, and the only reason I was able to keep it as long as I did was because of custom ROMS. If they are able to increase the performance of this phone the way they increased the performance of my 300Mhz/128MB RAM TytnII, then I will be giddy as a school-girl.
Do I need an unlocked bootloader? No, I absolutely love my phone the way it is right now, as this is my first Android, so I don't know what else is possible.
Battery life?
I am running a test of a custom kernel for my captivate. I turned off everything and wanted to see how long it would last.
No wifi or data (no sim card installed) it ran idle for 11 days.
Custom Kernel with no wifi or data its going to last about 50 days. (based on current estimate as im still testing it)
Just an FYI, there are devices with locked bootloaders that have custom ROMs. This includes the X10, which has a Gingerbread ROM. The issue is getting a newer Android build to work with a stock kernel. Unlocking the bootloader is key to building custom kernels but there are methods for getting custom ROMs without a custom kernel.
Developer support.
/thread
-Sent from my Galaxy Tab
Athailias said:
Battery life?
I am running a test of a custom kernel for my captivate. I turned off everything and wanted to see how long it would last.
No wifi or data (no sim card installed) it ran idle for 11 days.
Custom Kernel with no wifi or data its going to last about 50 days. (based on current estimate as im still testing it)
Click to expand...
Click to collapse
Well this isn't exactly a real world situation. Who's to say that you're not running the cpu at 1mhz with the screen powered off 24/7. wouldn't you prefer to test under load and real use?
Sent from my Atrix using XDA App
I've got a question I tried to answer myself, but I couldn't resist to post it on the forum.
Is the ICS leak a great step forward for all Atrix users ?
For those who wanted HWA, fingerprint scanner, working camera, of course it is... But is it a step forward for the release of a STABLE CM10 with a STABLE kernel ? This question is more open to a debate than a simple answer.
This leak didn't provide any option for those who have the wrong tegrapart (Mine is OK), or a lapdock, or those who use Chrome and want a generally reliable ROM (Stability, I/O perfs, battery life). They have to make a compromise but we still didn't reach THE ROM(s) that makes everybody happy.
The missing thing to get the ROM(s) that will make us all happy is the kernel source... Why didn't we get it with the ICS leak ? Well let's exclude this question from this thread and maybe talk about it after this debate is (almost) closed.
Personally I'm happy to have this new ROM, it's fast, smooth etc. but my lapdock is still borked so I'm really frustrated not to have this awesome tablet display that works with EVERYTHING but not MOTOROLA's own peripheral... Damn it !
So, what's your case ? Of course you may have found satisfaction with the ICS leak, but are you as frustrated as I am to be this close to the ultimate goal ?
The debate is open, I hope I broke the ice for some people who are in my case and feel like forgotten.
I think that leak does not come with the source code. Thus there will not be any practical improvement right now.
Or, most likely ever. I doubt things will go much farther, and I'm usually the optimistic one
no chance
nope, i think the ics leak was just a one off leak from what motorola actually got round to doing before they abandoned the project, which personally is really bad the roms are just crappy (no offence to developers but the lack of resources means they will always be crappy), everyone says the roms are good but every ics rom iv used is awful, overheating, bugs, battery life sucks, cameras lag, and doesnt compare to a stable cm7 which works completely fine and does everything ics can do anyway.. hmm... i guess everyone just keeps giving themselves false hope, although the possibility of a stable ics is much more than the chance of jellybean & as for the cm10/jellybean thing dont get your hopes up the signs of HWA are non existent and i really dont think they ever will be unless somebody makes a kernel from scratch which for a mobile device would take endless hours of work and testing each boot would probably get your through about 50 atrix phones from hard bricks etc... and i dont think our developers have the time or money to do so... even with donations.
its just not worth it, the atrix is a dying breed if you dont like cm7 then buy a new phone, its that simple, confuses me why everyone acts like cm7 is some sort of bugged crappy software that doesnt work? yet its still a very stable software.
i think everyone should stop concentrating on ICS and jellybean until we actually hear news that will be helpful to creating a stable build and in the mean time focus on improving cm7 with mods and other things, right now cm7 is basically abandoned and the thing its been abandoned for has been on hold for around 3 months.
Pixelguy said:
nope, i think the ics leak was just a one off leak from what motorola actually got round to doing before they abandoned the project, which personally is really bad the roms are just crappy (no offence to developers but the lack of resources means they will always be crappy), everyone says the roms are good but every ics rom iv used is awful, overheating, bugs, battery life sucks, cameras lag, and doesnt compare to a stable cm7 which works completely fine and does everything ics can do anyway.. hmm... i guess everyone just keeps giving themselves false hope, although the possibility of a stable ics is much more than the chance of jellybean & as for the cm10/jellybean thing dont get your hopes up the signs of HWA are non existent and i really dont think they ever will be unless somebody makes a kernel from scratch which for a mobile device would take endless hours of work and testing each boot would probably get your through about 50 atrix phones from hard bricks etc... and i dont think our developers have the time or money to do so... even with donations.
its just not worth it, the atrix is a dying breed if you dont like cm7 then buy a new phone, its that simple, confuses me why everyone acts like cm7 is some sort of bugged crappy software that doesnt work? yet its still a very stable software.
i think everyone should stop concentrating on ICS and jellybean until we actually hear news that will be helpful to creating a stable build and in the mean time focus on improving cm7 with mods and other things, right now cm7 is basically abandoned and the thing its been abandoned for has been on hold for around 3 months.
Click to expand...
Click to collapse
Its not that simple. Once you've had a taste of Android 4.X, its nearly impossible to go back. I'm stuck on Epinter's CM10 because of that, every time I try switching back to a CM7 based rom I find it randomly jittery and with a lot of small annoyances. Both of which I never noticed before trying Joker's CM9.
Even when I switched from CM7 to CM9, I remember CM7 was more or less perfect in its current state. Work stopped on it because there's not much else that can be done with it. Its hit its peak, and for those not spoiled by the more polished versions of Android it is indeed the ideal rom for our device. That does not mean work should stop on ICS/JB, though. The big issue we have is the kernel, of which there are several projects in the works to port kernels from other devices. Its something that'll take (a lot of) time, but long term it'll be much better for our devices than making barely noticeable changes to Gingerbread roms.
With that said, you are right in that the ICS leak is more or less useless without source code. Crappy battery and display issues on some variants of Atrix completely ruin it.
Having the kernel source would solve many issues, but after Motorola abandoned the device it's very unlikely they'll commit any more resources into releasing the half working source code. Of course we'd like to see the source released as it existed under development, but from what I understand, the the source that gets released isn't always exactly the same as what they work with when they compile it and things like extremely helpful comments in the code get removed because of things like NDA's. And although many of the libs and drivers can be extracted from the ROM, the code to use them has been lost.
As it stands, the Atrix Rebirth Project is probably the best chance for seeing a fully functional kernel source for ICS and beyond. But as has been pointed out already, interest in the device has been dying, and even if the project does manage to make it happen, it's not going to happen overnight.
Jotokun said:
Its not that simple. Once you've had a taste of Android 4.X, its nearly impossible to go back. I'm stuck on Epinter's CM10 because of that, every time I try switching back to a CM7 based rom I find it randomly jittery and with a lot of small annoyances. Both of which I never noticed before trying Joker's CM9.
Even when I switched from CM7 to CM9, I remember CM7 was more or less perfect in its current state. Work stopped on it because there's not much else that can be done with it. Its hit its peak, and for those not spoiled by the more polished versions of Android it is indeed the ideal rom for our device. That does not mean work should stop on ICS/JB, though. The big issue we have is the kernel, of which there are several projects in the works to port kernels from other devices. Its something that'll take (a lot of) time, but long term it'll be much better for our devices than making barely noticeable changes to Gingerbread roms.
With that said, you are right in that the ICS leak is more or less useless without source code. Crappy battery and display issues on some variants of Atrix completely ruin it.
Click to expand...
Click to collapse
hmm i used pinters cm10 for a week and went back to MROM cm7 and customised it to my liking with ICS themes and text changers, looks just like ICS runs just as smooth as a buggy JB rom, thats the problem the performance of CM10 roms without HWA is about the same as a good CM7 rom... just with a few features like google now which nobody really uses anyway, although i understand where your coming from when it comes too the UI and animations on JB roms they are very nice but id rather sacrafice them and have a phone that will work 100%
I'm very naive to the inner workings of android
I also returned to mrom from epinters cm 10 and icsrom because of lack of camcorder or terrible battery life.
Now with mrom I have a very smooth launcher and all apps working. I do miss jellybeans nice interface, but what are the more fundamental improvements that gingerbread lacks? Besides feeling outdated and old of course :/
Sent from my MB860 using xda app-developers app
Zero usefulness. Novelty item at best.
It's interesting to read opinion of no-developers is it something useful or not. Only developers could say something about it. Also most of you are so pessimistic, complaining that developing is dying.
xda-developers is for site and forum for developers. If you think that developing is dying, come on, do something about. Join Atrix Rebirth Project, start to learn how to develop kernel and rom. There is a lot of guides here and on Internet. Instead of spending time on forum and waiting that someone else do it for you and for free. If you don't have time to learn, contribute on another way: support developers, donate money or device, try to find solution, use your contacts to get leaked sources...
The easiest way is to buy a new device and start complain after a while
I have been very pleased with the stock GB rom. I have a Nexus 7 and an old HTC Aria, both running the latest version of JB and, other than a more up-to-date appearance, there's really nothing I can't do on the Atrix that I can do on the JB devices.
Its amazing what the developers have been able to do with the HTC Aria. It has very little memory, but they have created virtually unlimited program memory by using an extended partition on the SD card. The Aria also runs JB almost flawlessly.
If JB could run on the Atrix 4G the way it runs on my Aria, I would use it. But from what I've read, it has a long way to go. I am not even sure I would even be able to root my Atrix, which has the latest GB update from Motorola.
Sent from my MB860 using xda app-developers app
Slymayer said:
I've got a question I tried to answer myself, but I couldn't resist to post it on the forum.
Is the ICS leak a great step forward for all Atrix users ?
For those who wanted HWA, fingerprint scanner, working camera, of course it is... But is it a step forward for the release of a STABLE CM10 with a STABLE kernel ? This question is more open to a debate than a simple answer.
This leak didn't provide any option for those who have the wrong tegrapart (Mine is OK), or a lapdock, or those who use Chrome and want a generally reliable ROM (Stability, I/O perfs, battery life). They have to make a compromise but we still didn't reach THE ROM(s) that makes everybody happy.
The missing thing to get the ROM(s) that will make us all happy is the kernel source... Why didn't we get it with the ICS leak ? Well let's exclude this question from this thread and maybe talk about it after this debate is (almost) closed.
Personally I'm happy to have this new ROM, it's fast, smooth etc. but my lapdock is still borked so I'm really frustrated not to have this awesome tablet display that works with EVERYTHING but not MOTOROLA's own peripheral... Damn it !
So, what's your case ? Of course you may have found satisfaction with the ICS leak, but are you as frustrated as I am to be this close to the ultimate goal ?
The debate is open, I hope I broke the ice for some people who are in my case and feel like forgotten.
Click to expand...
Click to collapse
Yeah right ! talking about this leak ... is a >small< step foward !
Just imagine Michael Montuori out of here, Or the Bill ?! epinter !? Faux, or jocker that has made a wonderfull job and the other in the early days of the atrix .... all source code builder out of this atrix family at once !
Well ... Motorola doesnt have a great support for the moment ! as their Blur OS is ****ty slow ! :S
I own a Car dock, A HD Multimedia Dock and a great lapdock !
I approve that this is still frustrating (and i know the devs out there are NOT getting Paid enough for a better work than MOTOROLA itself,) that motorola own product doesnt have support yet ! but still have on a direct DHMI cable straight to the tv !! WTF ?!?!!
Well, its not going to change anything here, i mean this thread ... but .. well .. you know ! YEAH its awkward and " fais chier bordel" hahaha
Our devs are GREAT but unfortunately, we still need that damn MOTO support for their drivers source for the new OS :S
Meanwhile
sathelate said:
Well, its not going to change anything here, i mean this thread ... but .. well .. you know ! YEAH its awkward and " fais chier bordel" hahaha
Click to expand...
Click to collapse
I would even say "Bordel à couilles de constructeur de mes deux !". I'm writing this using my lapock... On my tiny screen, with my main screen at 45° so I can still read what I'm writing. I dreamt about WT3.0 with working LAPDOCK, it would have been so gorgeous, but it's currently not happening. "Nique cette merde !", I'm buying a Windows Phone next year when the ecosystem gets more apps and stuff. The news are getting warmer for this OS ! The amazing keyboard made in WP7/8 will replace my lapdock I use as a keyboard.
Development IS actually dying, look at the Atrix 4G development section where there used to be several ROMs under active development there are now just a few. Nearly everything that can be done has been done with the exception of what the Atrix rebirth project is doing. But there is no guarantee of success. If you have the money or a device to donate to the rebirth project, great, by all means go for it. Maybe one of the other tegra based moto devices might help a bit too. Unfortanately I think it's pretty hard to hold any level of optimism for the device after such a long string of let downs.
Sent from my MB860 using xda app-developers app
I see the ICS leak as interesting but not overly useful.
Now, if they'd also leaked the source code, I don't doubt that the devs could have created a fully-features and stable ICS/JB within a couple of months. However, with no source for such a buggy leak, we're reliant on a few people trying to create a kernel almost from scratch. I wish them well, but I'm not holding my breath...
When you feel like the development is hopeless , waste all of your time and try fixing things yourself get a new phone.
BravoMotorola said:
When you feel like the development is hopeless , waste all of your time and try fixing things yourself get a new phone.
Click to expand...
Click to collapse
Like you? And you think that you're smart. That's exactly what vendors wish, get a new device. Bravo
Edit: With your latest posts in Atrix forum you're the same as maggedo or member with Atrix in name. Ups, you have Motorola
How long N4 will be the best device for you? What I see not so long
I think it's interesting how people work:
First everyone was crying about the fact, that Motorola left us out in the cold and now that we have a actually really good leak, people cry that it's not good enough... That's just sad. The leak is useful and it's a big step into the right direction. A lot of people put in hours of work for you (and for FREE!!!), to make this leak better. All you need is PATIENCE. Be grateful that some devs stick to this EOL-device and provide great work for us.
-Just my 2 cents-
Sent from my MB860 using Tapatalk
BravoMotorola said:
When you feel like the development is hopeless , waste all of your time and try fixing things yourself get a new phone.
Click to expand...
Click to collapse
And... What about people who can't get a new device ? I bought mine like 6 months ago, it was for my birthday and I can't waste money on a newer phone like this.
But there must be some kind of "break-even" ahead.
How many hours of work and energy may be put from the most "valuable brains" into the leak (without having sourcecode), until they must decide: "enough is enough, it just will never turn out as "stable"?
From what I've understood there exists some good chances that maybe some day valuable parts of the XOOM kernel get migrated to the Atrix (see respective thread under development area).
May the last remaining devs of a dying device - whose work I greatly respect and appreciate! - join forces and turn more efforts into porting the xoom?
Greetings, programs! Well my question is not likely something anyone could have a definitive answer for - but I welcome any opinions or ideas. I don't want phone that is locked up against tinkering, but the current "price" of this phone is so tempting. Just about everything I've read tells me I'd really love this phone - the only thing holding me up is my expectation that there will be little to no development done with this phone.
I see that the bootloader seems to have been successfully unlocked? Now that this is the case I wonder if it's likely to be something anyone puts work into as far as developing ROMS/kernels. I'm not expecting Nexus-level activity, but even the hope of something might help me make up my mind (or I may just get a GNex). Thanks,
Merman1983 said:
Greetings, programs! Well my question is not likely something anyone could have a definitive answer for - but I welcome any opinions or ideas. I don't want phone that is locked up against tinkering, but the current "price" of this phone is so tempting. Just about everything I've read tells me I'd really love this phone - the only thing holding me up is my expectation that there will be little to no development done with this phone.
I see that the bootloader seems to have been successfully unlocked? Now that this is the case I wonder if it's likely to be something anyone puts work into as far as developing ROMS/kernels. I'm not expecting Nexus-level activity, but even the hope of something might help me make up my mind (or I may just get a GNex). Thanks,
Click to expand...
Click to collapse
The boot loader is unlockable for the dev edition RAZR m and as for development, safe strap has been released and cm10 alpha has been released. I have no doubt that in the future, more will come out. If ur attracted to this phone, then I highly suggest you get it because of the size and specs.
Sent from my XT907 using xda premium
jarzy00 said:
The boot loader is unlockable for the dev edition RAZR m and as for development, safe strap has been released and cm10 alpha has been released. I have no doubt that in the future, more will come out. If ur attracted to this phone, then I highly suggest you get it because of the size and specs.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
Totally agree with jarzy00 i am coming from evil land apple and this phone feels nice and compact replacing my i4 LMAO
Razr i, Razr M and Razr M XT905 (Future release for Euro market maybe) are one of the few phones left standing with this kind of small foot print.
ever one else moved on to larger screens. And the specs aren't too shaby =)
Ok, I see. My experience with Moto phones are limited, but do I have it right that using the bootstrap method you can flash custom ROMS, but custom kernels are a no go? Still waiting till I make a decision, but every bit of info helps.
Coorect Bootstrap allow you to load that Beta CM10.
(There isn't much support on that yet)
And no custom kernels unless you have the Dev edition
There are AU Edition, US Edition, Dev Edition, And the i (Intel), there are plans for a EU Edition which will be GSM only
Either get it and hand in tight, or look for a DEV
Merman1983 said:
Ok, I see. My experience with Moto phones are limited, but do I have it right that using the bootstrap method you can flash custom ROMS, but custom kernels are a no go? Still waiting till I make a decision, but every bit of info helps.
Click to expand...
Click to collapse
Not sure how far development is on Safestrap for the M, but it will allow custom kernels on locked devices using kexec. The version for the Droid 3 (which has a locked bootloader) allows a 3.x kernel to be run instead of the factory 2.6.x kernel in order for better ICS and newer compatibility. Unless Motorola has patched this kexec bypass then it should be possible to implement on the M.
Thanks guys for this thread. I was possibly looking at this phone, but I don't want to end up with the same situation we had with the bionic. I think I'll skip it until Moto wises up and unlocks the bootloaders.
If you really want some development here, look at the donate thread for getting nytro a razr m so he can develop for the retail version. In terms of safestrap, you could potentially get modify a custom rom. It just takes one rom to iron out the major bugs and people can start deriving from it.
i dont think moto will ever get smart with bootloaders, which is sad because they make quality phones, with unlocked bootloaders i dont think id ever buy another brand. but regardless, we have stable safe strap, just isnt a big flagship device, its not a new phone and with all the new better phones that are cake to unlock, this phone is just looked over and left in the dust, aside from a few very good devs we have working to give us some stuff to play with, we wont see much.
I have been waiting a while to post this because posts like this always get killed, but for a phone with a factory-available bootloader unlock, I am surprised we don't have a modded stock ROM to try out yet. TruPure on the Moto x Pure was awesome, although it altered very little. I know CM is being worked on but given some of the responses in that thread, it could be quite a while.
So aside from that observation, is anyone actively working on something like that and if so, can you post here and let us know how things are coming along? I know we all would be appreciative of the effort.
They're waiting on a full image of the ROM to be released, with all the img, radio, ect.. and other files needed to make it work. Once that drops form ZTE, it's on like some 80s video game reference.
tele_jas said:
They're waiting on a full image of the ROM to be released, with all the img, radio, ect.. and other files needed to make it work. Once that drops form ZTE, it's on like some 80s video game reference.
Click to expand...
Click to collapse
Noob question: Cannot these be taken from images that were extracted from the phone already? Does rom provide that much more?
This is a genuine question, isn't rom just a packed and zipped version of what is on the phone?
mhodak said:
Noob question: Cannot these be taken from images that were extracted from the phone already? Does rom provide that much more?
This is a genuine question, isn't rom just a packed and zipped version of what is on the phone?
Click to expand...
Click to collapse
I was pretty sure that once we got root and bootloader access that this could be done just as you said here. No need for drivers or proprietary anything...although the camera API will be a problem, but I think it's possible right now. I was just wondering why no one has the desire to attempt it. Did the weird release and shipping debacle for the grey phones really make everyone avoid the phone and hamper dev this much? Sort of disappointing if that is the case.
xgerryx said:
I was pretty sure that once we got root and bootloader access that this could be done just as you said here. No need for drivers or proprietary anything...although the camera API will be a problem, but I think it's possible right now. I was just wondering why no one has the desire to attempt it. Did the weird release and shipping debacle for the grey phones really make everyone avoid the phone and hamper dev this much? Sort of disappointing if that is the case.
Click to expand...
Click to collapse
This worries me as well. It appears that there is only one person actively working on a custom ROM. Although things can pick up later, this does not bode well for the future.
mhodak said:
This worries me as well. It appears that there is only one person actively working on a custom ROM. Although things can pick up later, this does not bode well for the future.
Click to expand...
Click to collapse
My thoughts are differently, base on the many issues people are running when trying to get back to stock and the fact they there's 2 B20 versions around (B20 Stock & B20_boot) make things a Little harder to do, like for sample,
I have the B20_boot version and as you can see I uploaded a backup with Xposed debloated and Rooted (I can consider that backup/ Custom ROM) but stock B20 can't use that backup as far as I know... I can easily release a flash able zip base on my backup but (Xposed,Debloated,rooted) but I bet only 5% of the user are using b20_boot.
So till find a way or just way till ZTE release a firmware image we are going to be little stuck with just CM which is getting more stable every day/week
xgerryx said:
I have been waiting a while to post this because posts like this always get killed, but for a phone with a factory-available bootloader unlock, I am surprised we don't have a modded stock ROM to try out yet. TruPure on the Moto x Pure was awesome, although it altered very little. I know CM is being worked on but given some of the responses in that thread, it could be quite a while.
So aside from that observation, is anyone actively working on something like that and if so, can you post here and let us know how things are coming along? I know we all would be appreciative of the effort.
Click to expand...
Click to collapse
First, the Moto X Pure was widely available. It was not shipped out in smaller batches once a month. When it was released, it was available for everyone to purchase. For the Axon 7, the first batch and second small batches of phones sold out during pre-order, and the third batch hasn't even shipped yet. (and it hasn't received a wide release in Europe yet either, think they just had one small batch)
Also, the Moto X Pure had bootloader unlock available at launch. The Axon 7 did not get a bootloader unlock method until August 11th, less than a month ago. (and at this time, there is no bootloader unlock for the European or Chinese models, just the North American model)
And just as a reminder, the Moto X Pure launched in early September. Dev for CM12.1 started in late September. The first custom ROM, an alpha of CM12.1, was released a month later, in the beginning of October.