I had almost lost hope of getting unlocked bootloader when I saw a new hope with the launch of Galaxy S III.
How many of you know, the Verizon version of this device is locked with the bootloader, while others appear to be unlocked. Even knowing how bad this is, this may be an opportunity for many of the models with locked bootloader have a chance.
What I mean is that, like the S III, we have some defy's around the world with unlocked bootloader (most of them in china so observe here for the XDA). Would I be so foolish to believe that with a device such as the S III target, there is a possibility of unlocking the bootloader by developers? And this means of release could somehow help with the release of the Defy and many other devices with locked bootloader?
Yesterday, motorola mobility rep. posted this on their Google+ page
Motorola ATRIX HD at AT&T will have a locked bootloader to meet requirements; our goal is still to provide a way to unlock the bootloaders on our devices to those who wish to do so, more details will be shared as soon as we can.
Click to expand...
Click to collapse
The question is, what that really means.
popcorp said:
Yesterday, motorola mobility rep. posted this on their Google+ page
The question is, what that really means.
Click to expand...
Click to collapse
Probably another lie from them.
Sent from my ICS Defy
NITRO_100 said:
Probably another lie from them.
Sent from my ICS Defy
Click to expand...
Click to collapse
I do not doubt. Motorola has a terrible historical. But i really enjoy the Defy and wouldn't like to have to change my device to update kernel/android. I'm really wanting to play the fool to believe in fairy tales at the time :laugh:
I want to believe in this fairy tale this time.
I have a RAZR and just got the official ICS on it. I like my defy more than my razr. I wish I could put ICS on here.
iolinux333 said:
I wish I could put ICS on here.
Click to expand...
Click to collapse
Huh? Why not try ICS CM9 from devs Quarx and Epsylon3? Or even better, wait a few days and flash CM10 Jelly Bean...
OT: time to spam their Bootloader discussion forum again:
http://community.developer.motorola...ader-discussion-board/td-p/22108?pubid=987654
Martijn1971 said:
Huh? Why not try ICS CM9 from devs Quarx and Epsylon3? Or even better, wait a few days and flash CM10 Jelly Bean...
OT: time to spam their Bootloader discussion forum again:
http://community.developer.motorola...ader-discussion-board/td-p/22108?pubid=987654
Click to expand...
Click to collapse
Martijn, you know...you can try Quarx end Epsylon3 ROMs. I'm doing this right now, and since we got the dualboot, i'm testing a lot of ROMs. But we have a great problem, our kernel. On Jelly Bean android will receive great improvement on the sdk and with the system, like App stack navigation or Network service. Much of the improvement are done on the system, but some of then could request new implements from the kernel. A example could be the use of the NFC ( Near Field Communications ). It's on the kernel how to initialize on care some IRQ from the hardware. You could build a module to load how to care with NFC from the Android OS, but if it would build on kernel (like it could be from new linux kernels). And things like Dynamic writeback throttling, performance on reading or size limit from file systems
Take a look on this: http://kernelnewbies.org/Linux_3.1
Much things i can do on CM7, using kernel 2.6, like the wiimote, so why this would be news on kernel 3.1? 'Cause there, isn't the OS that is caring the NFC or the wiimotes, but the kernel. A such difference is a example that could make a new version of the Android flow better on our device. And things like this we just get with a bootloader opened.
Quarx end Epsylon3 are doing a great, a extraordinary work! I salute them! But as the Android evolves, they work get even more hard if all that could be on kernel, they have to do with patches or modules on the OS. Praying for a open bootloader isn't just to ensure that we gonna have updates until or device could run it and be moneymaking for the developers, but is a way to ensure that this work will be more easy (and probably faster) to the developers too.
Kazid said:
Martijn, you know...you can try Quarx end Epsylon3 ROMs. I'm doing this right now, and since we got the dualboot, i'm testing a lot of ROMs. But we have a great problem, our kernel. On Jelly Bean android will receive great improvement on the sdk and with the system, like App stack navigation or Network service. Much of the improvement are done on the system, but some of then could request new implements from the kernel. A example could be the use of the NFC ( Near Field Communications ). It's on the kernel how to initialize on care some IRQ from the hardware. You could build a module to load how to care with NFC from the Android OS, but if it would build on kernel (like it could be from new linux kernels). And things like Dynamic writeback throttling, performance on reading or size limit from file systems
Take a look on this: http://kernelnewbies.org/Linux_3.1
Much things i can do on CM7, using kernel 2.6, like the wiimote, so why this would be news on kernel 3.1? 'Cause there, isn't the OS that is caring the NFC or the wiimotes, but the kernel. A such difference is a example that could make a new version of the Android flow better on our device. And things like this we just get with a bootloader opened.
Quarx end Epsylon3 are doing a great, a extraordinary work! I salute them! But as the Android evolves, they work get even more hard if all that could be on kernel, they have to do with patches or modules on the OS. Praying for a open bootloader isn't just to ensure that we gonna have updates until or device could run it and be moneymaking for the developers, but is a way to ensure that this work will be more easy (and probably faster) to the developers too.
Click to expand...
Click to collapse
Opening the bootloader is not the only way to load a new kernel. Kexec was designed exactly for that. It's possible on android -- kholk have got that to work on RAZR already. There were some problem on defy, but I think it is not impossible to fix.
I may be wrong, but can we use the kexec to solve the actual problem with CM10? It won't work for Radio but we can use it for USB/Audio?
Sent from my MB525 using xda app-developers app
t0n0n said:
I may be wrong, but can we use the kexec to solve the actual problem with CM10? It won't work for Radio but we can use it for USB/Audio?
Sent from my MB525 using xda app-developers app
Click to expand...
Click to collapse
As far as what I've read, the radio is burnt completely if we try kexec.
S3nt fr0m my D3fy/w1u1 GB st4BL3
nidhish91 said:
As far as what I've read, the radio is burnt completely if we try kexec.
S3nt fr0m my D3fy/w1u1 GB st4BL3
Click to expand...
Click to collapse
I think it gets not burnt... it just crashes, panics and in consequence the defy(+) reboots.
nidhish91 said:
As far as what I've read, the radio is burnt completely if we try kexec.
S3nt fr0m my D3fy/w1u1 GB st4BL3
Click to expand...
Click to collapse
Thought we could exclude the Radio and use just USB/Audio =/
Didn't they used "burn" just as a expression?
Our Kernel can load modules, can't it reload them? We use a module called mod2 who kicks in after to add to the first module? Or to override the first one. It's a lot like kexec but with the modules, not the kernel.
Sent from my MB525 using xda app-developers app
Kazid said:
I had almost lost hope of getting unlocked bootloader when I saw a new hope with the launch of Galaxy S III.
How many of you know, the Verizon version of this device is locked with the bootloader, while others appear to be unlocked. Even knowing how bad this is, this may be an opportunity for many of the models with locked bootloader have a chance.
What I mean is that, like the S III, we have some defy's around the world with unlocked bootloader (most of them in china so observe here for the XDA). Would I be so foolish to believe that with a device such as the S III target, there is a possibility of unlocking the bootloader by developers? And this means of release could somehow help with the release of the Defy and many other devices with locked bootloader?
Click to expand...
Click to collapse
t0n0n said:
I may be wrong, but can we use the kexec to solve the actual problem with CM10? It won't work for Radio but we can use it for USB/Audio?
Sent from my MB525 using xda app-developers app
Click to expand...
Click to collapse
I remember something called "Project Cheesecake" and "Operation MOSH" from like, a year ago.
Petitions did not save our Defy from a locked bootloader.
Samsung's different. Nearly all Samsung devices have unlocked BL. Nearly all Motorola devices have locked BL.
They tried using oem fastboot on the Defy but it didn't work so well I don't think.
droid_<3er said:
I remember something called "Project Cheesecake" and "Operation MOSH" from like, a year ago.
Petitions did not save our Defy from a locked bootloader.
Click to expand...
Click to collapse
Here's the thread for cheesecake.
Related
So I have a Xperia Play R800x (CDMA). I don't have enough posts, so I can't post in the topic. So I have a few questions about the recent FXP025 and the ROM with it, or whatever it is called .
1. Are all of the stock games still there?
2. Can I restore a previously made Nandroid backup? I think I can, I'm not sure though.
I will update this topic as I have more pop into my mind. thanks guys!
savage24x said:
So I have a Xperia Play R800x (CDMA). I don't have enough posts, so I can't post in the topic. So I have a few questions about the recent FXP025 and the ROM with it, or whatever it is called .
1. Are all of the stock games still there?
2. Can I restore a previously made Nandroid backup? I think I can, I'm not sure though.
I will update this topic as I have more pop into my mind. thanks guys!
Click to expand...
Click to collapse
CM7 includes nothing sony ericsson or google. You can flash the G-Apps as a seperate .zip. But google made them remove there apps from the basic rom along time ago.
You can restore a prevous backup and get back to stock at any time, but remember to flash the right kernel aswell. CM7 wont boot with sony's kernel, and Stock rom wont boot with the CM7 kernel
I can't see the point to CM7 on the Play? just seems like a very basic half finished Android to me with all the apps removed?
The point of CM is to give people a standard Google experience as they intended instead of the highly customized versions of Android that several manufacturers give you, such as Sony Ericsson, Samsung with TouchWiz, HTC with Sense. It's not "half-finished" - just the port for the Xperia Play is. After having used full finished versions of CM on other phones, I don't want anything but CM now.
CM is based on the Android Open Source Platform - AOSP - which means that everything included with it must be open source. Proprietary apps are replaced with open and free apps. Stuff included by various manufacturers are not included unless they are free and open source as well.
Hope that explains things. Give CM7 another shot when the Play version gets closer to being finished.
FK1983 said:
I can't see the point to CM7 on the Play? just seems like a very basic half finished Android to me with all the apps removed?
Click to expand...
Click to collapse
The "Half-finished" Android destroys most official builds in performance and battery life out of the box. Such is my experience with the (still in beta) CM7. The official -368 build is less snappy and a battery hog in comparison to -154, while CM7 tops both in those respects. Once CM7 is in RC2 or stable, you'll see what the point of CyanogenMod is.
Logseman said:
The "Half-finished" Android destroys most official builds in performance and battery life out of the box. Such is my experience with the (still in beta) CM7. The official -368 build is less snappy and a battery hog in comparison to -154, while CM7 tops both in those respects. Once CM7 is in RC2 or stable, you'll see what the point of CyanogenMod is.
Click to expand...
Click to collapse
+1 wait 'till were up to nightly builds. Then you will see what CyanogenMod is all about
ok, thanks guys! I suceeded in flashing the kernel. Now I'm trying to flash the .ftf file... and looks like I'm failing :/ what device do I set it as, and should it be in fastboot?
zerojay said:
The point of CM is to give people a standard Google experience as they intended instead of the highly customized versions of Android that several manufacturers give you, such as Sony Ericsson, Samsung with TouchWiz, HTC with Sense. It's not "half-finished" - just the port for the Xperia Play is. After having used full finished versions of CM on other phones, I don't want anything but CM now.
CM is based on the Android Open Source Platform - AOSP - which means that everything included with it must be open source. Proprietary apps are replaced with open and free apps. Stuff included by various manufacturers are not included unless they are free and open source as well.
Hope that explains things. Give CM7 another shot when the Play version gets closer to being finished.
Click to expand...
Click to collapse
Thanks for explaining!
I will certainly give it a try when it looks "more complete", so apart from the open source part is that the only difference?
Logseman said:
The "Half-finished" Android destroys most official builds in performance and battery life out of the box. Such is my experience with the (still in beta) CM7. The official -368 build is less snappy and a battery hog in comparison to -154, while CM7 tops both in those respects. Once CM7 is in RC2 or stable, you'll see what the point of CyanogenMod is.
Click to expand...
Click to collapse
I wasn't slagging CM7 off by the way, just generally wondered what is considered good about it!
The way I have my Play running now with the latest official SE FW + DoomKernal + recovery + overclocked to a stable 1.8ghz I honestly have never experienced such a fast and snappy device, everything is now instant and buttery smooth, if CM7 can improve on this then I will be impressed but I just can't see how it can....
AndroHero said:
+1 wait 'till were up to nightly builds. Then you will see what CyanogenMod is all about
Click to expand...
Click to collapse
I know you weren't decrying CM, but I've already had 3 Androids with Cyanogen Mod on them. It certainly makes a difference. It's true that some vendors are manning up, updating their phones more frequently and adding exclusive features so CM7 is not as superior as it was before, but it still adds a lot of value. A cheap phone like the ZTE Blade was born to carry CM7, as well as high-end but officially obsolete devices like the Xperia X10.
I used update.zip to go to the CM7 kernel... correct? So I'm going to flash kernel.sin (stock) back and start over, I need to get Flashtool working correctly, it won't recognize my device in fastboot. I've tried 2.9.1 (that's what I remember it was called... there's another number in it) and 3.0.0.0. I can't flash the .ftf file for CM7... help me out guys :/
CM7 comes in two parts: its own special kernel, and the ROM. Flash the kernel, enter recovery, flash the ROM through recovery.
Alright, thanks a lot guys, I finally got it working. I didn't know I had to install gordon gates drivers. thanks again!
I want the benefits of CM7, such as Android 2.3.5, overclocking, and less bloat, but I still want some of the Sony things, such as the xplay launcher, market, and Verizon market to get those few games...
In some of those cases, you'd just need to bring the APK over and install it. In some others, not so much.
zerojay said:
In some of those cases, you'd just need to bring the APK over and install it. In some others, not so much.
Click to expand...
Click to collapse
I'm not sure which dependencies I am missing for the xplay launcher, it won't install the app from titanium backup. I never knew how much I'd miss that interface until it was actually gone
hairdewx said:
I'm not sure which dependencies I am missing for the xplay launcher, it won't install the app from titanium backup. I never knew how much I'd miss that interface until it was actually gone
Click to expand...
Click to collapse
Xplay launcher and playstation pocket app requires the SE framework! you can play the playstation games if you install preinstalledservices.apk but the launchers wont work
AndroHero said:
Xplay launcher and playstation pocket app requires the SE framework! you can play the playstation games if you install preinstalledservices.apk but the launchers wont work
Click to expand...
Click to collapse
Darn, I figured as much.
http://nooooooooooooooo.com/
hairdewx said:
Darn, I figured as much.
http://nooooooooooooooo.com/
Click to expand...
Click to collapse
Lmfao @ that website, Thats getting bookmarked
SEtweak kernel for Xperia S.
Intro:
I know I failed last time (with Play - it was stolen) and left development. But let's be serious this time.
Since it'll take a bit to set up everything again, I've taken DooM's ramdisk (hope you don't mind) for the first test.
Note: I don't have the device so I can't test it. If you want to, you can donate via Donate button on the left.
Sony finally published everything we need to build kernel.
Due to some possible bootloader problems, kernel might not work.
Features:
Codepage 852 (purely selfish reasons )
NLS UTF-8 (Native Language Support)
NTFS support
TUN/CIFS support
Default governor set to 'ondemand'
Prerooted
init.d support
Coming soon:
More governors
Recovery
Download: be patient
Best regards,
Blagus
Cool.
Ive unlocked my bootloader already so ill test it for you.
Im not rooted yet tho. I did have the rooted rom installed form another thread but i was having issues with app crashes so i flashed the stock .67
Hi there,
I hope the kernel wil be pre rooted and have some nice features....
I will try it
I need someone to send me kernel.sin of 6.0.A.3.62 firmware.
Hi there,
You can download it here : https://github.com/DooMLoRD/Xperia-2012-Official-Kernel-Sources and if its not there you can find it here http://eddy.uni-duisburg.de/bin4ry/L...1257-3921).ftf
Blagus said:
I need someone to send me kernel.sin of 6.0.A.3.62 firmware.
Click to expand...
Click to collapse
Im uploading it now for you
Edit:
Done
https://rapidshare.com/files/1187401250/kernel.sin
Don't bother Blagus. At this point, you can't really use a custom boot image due to a bootloader bug.
deovferreira said:
Don't bother Blagus. At this point, you can't really use a custom boot image due to a bootloader bug.
Click to expand...
Click to collapse
Really? Any more info on that?
It seems to affect some units at this point, I know of others which can boot just fine though using the instructions provided by Sony. This is the one thing preventing CM9 porting at this point.
deovferreira said:
It seems to affect some units at this point, I know of others which can boot just fine though using the instructions provided by Sony. This is the one thing preventing CM9 porting at this point.
Click to expand...
Click to collapse
hi defer,
what is the bug exactly?
i faced some issues yesterday when testing out kernels on a users device...
whenever we tried hotbooting the kernel (fastboot boot kernel.elf) the bootloader always returned "Wrong range" even though i used exactly the same ranges as given by Sony....
the test kernels are posted here:
http://forum.xda-developers.com/showthread.php?p=23868276#post23868276
if anyone wants to try them
I don't know the specifics of the bug, but it's in the bootloader it might be anything really, no way to know. However, what happens is that the bootloader is able to boot signed kernel.sin files but not the unsigned kernel.elf
Yep.
I just wish there was stock ICS for the HOV. Vanilla ics rom is close but it still has sense left over.
cm9 is far too unstable, and all my attempts at flashing various roms of JB are instable/not daily driver ready.
There don't seem to be any truly usable roms for this device. Stock sense is the only build in which everything works.
It's either one thing or another. If the camcorder works, the build might not work with simple apps like voxer. If voxer works, then mms won't work. If JB runs perfectly stable, then maybe the camcorder doesn't work. Does a rom that works without bugs like this exist? Here are a list of things I would need in a daily driver rom:
1. Camcorder- I'm a skater and I like to film fun edits of me and my hoodrat friends doing hoodrat things on our skates.
2. MMS - Such a simple necessity.
3. App compatibility -It drives me crazy when my important apps like voxer, instagram, facebook, and launchers lag badly or crash every time I open them
4. LAG - this is why I can't upgrade to JB, I thought provision Rom was AMAZING until I started using my apps (see #3)
5. Simple Multitasking
6. Random reboots - doesn't bother me too much but I could see it happening in some situation where I would need the phone immediately and have to try and explain to someone that "Herp, muh super custom droid phone likes to reboot so you'll just have to wait."
So far the only thing I can think of doing is building a stock ics rom (which I have no idea how to do). Any tips, first timer here.
Right now I just flashed back to stock and am going to run the de-sense tool. Why must OEMs ruin everything we love?
I hate to complain like this and I'm very glad there are devs working on the problems I describe. I guess I'm just venting my frustration. I love this phone but I have spent so much time trying to get a stock android experience that works. I would just buy galaxy nexus or an S3 but I'm a college and pre-paid cheap phones are the only way to fly right now, man. Sorry to sound so negative throughout the post but these are simply my observations in contrast with my needs and wants.
BTW first post on here. Don't hate me plz.
What do you mean CM9 is unstable?
Sent from an awesome phone
ryanlow134 said:
What do you mean CM9 is unstable?
Sent from an awesome phone
Click to expand...
Click to collapse
Exactly cm9 is 100% stable. Do a fill wipe before you flash
Sent from my One V using xda app-developers app
ok thanks! The only cm9 I could find was on the cdma dev forum and it said a number of things including the camcorder didn't work.
...and then I googled it and found exactly what I needed. Flashing now. We'll see how this works. Was there something I'm missing? I looked at this one [CDMA/PRIMOC][ROM] Unofficial CM9 for PrimoC Beta
480p video recording kind of suck but it'll have to do I guess.
Before u go knocking on peoples stuff how about u make a effort to fix it ur self and u can't say well I don't know how. Well sir u know that little company that bought android os yea sell they Also have a easy to use search bar and so does this little site u are on
And last how about u try and talk to the developers by posting in threads and asking if thus is a problem or even try p.m the developers the problem and I know that for sure u never messeaged me about a application messing up on our provisions rom
Thanks for using provisions ROM and do remember have a nice day.
Sent from my PK7630000 using xda app-developers app
Please check user's face. We are not responsible for your 'horrific' experiences while trying custom roms build by us if you are too noob enought to not do a full wipe before you flash a rom.
Thank you and see you in the other side!
1ceb0x said:
you are too noob enought to not do a full wipe before you flash a rom.
Click to expand...
Click to collapse
No. Just because this is my 3rd post doesn't mean I haven't done my homework.
sbkjuggalo said:
And last how about u try and talk to the developers by posting in threads and asking if thus is a problem or even try p.m the developers the problem and I know that for sure u never messeaged me about a application messing up on our provisions rom
Click to expand...
Click to collapse
I did for the Vanilla ICS rom. Sorry about yours but I was going through a series of JB on my device and they all had the same problems with app compatibility/stability.
DrZaiusIsAlive said:
No.
I did for the Vanilla ICS rom. Sorry about yours but I was going through a series of JB on my device and they all had the same problems with app compatibility/stability.
Click to expand...
Click to collapse
Dude before flashing you must wipe your device properly.
Sent from my One V using xda app-developers app
DrZaiusIsAlive said:
No. Just because this is my 3rd post doesn't mean I haven't done my homework.
I did for the Vanilla ICS rom. Sorry about yours but I was going through a series of JB on my device and they all had the same problems with app compatibility/stability.
Click to expand...
Click to collapse
Don't know about comatibility/stability. Using CM10 from Lloir and works flawless for me, and yes, I'm using mms, camcorder, apps of a wide range, and yes, this is my primer and only phone, so I can say that it is stable too. Only camcorder problem I found that autofocus is somehow misbehaving in video recording.
Full wipe is essential for stability if you flash a rom that is based on something else, than the last one you used. I even erase sometimes the sdcards android and secure partitions if must. I tried Lloir's slimbean just this morning and seems promising enough, really thinking about to change to that rom permanently.
Full wipe means:
Factory reset (this will delete cache and dalvik cache - this will also remove the .android_secure folder)
Wipe system
Flash rom
Flash the correct kernel in bootloader
Reboot your phone
Voila, rom without any issues at all!
Don't tell me you did all these and you still have problems with JB and other custom roms. I just don't buy it. Everyone here that uses a custom rom are so enthusiastic about them, they don't even wanna get back on sense. I am having Paranoid Android on my One V from the moment I started making the rom for us, since August. From then onwards, I've only used this rom. I don't think that there are any kind of instability with it, because I test my roms before releasing them so if it was unstable, why should've I used it for more than 4 months now?
1ceb0x said:
Full wipe means:
Factory reset (this will delete cache and dalvik cache - this will also remove the .android_secure folder)
Wipe system
Flash rom
Flash the correct kernel in bootloader
Reboot your phone
why should've I used it for more than 4 months now?
Click to expand...
Click to collapse
1. I do all those. This is is my third android device. I used to have a galaxy tab 2 rom'd with cm10 and it was awesome. But even it had some problems with app compatibility. I got my learning in on that device. I nearly bricked it 3-4 times haha.
2. We use our phones differently. There are probably a ton of apps I use and a ton you don't. I know for sure that draw something is incompatible with JB itself.
I'll probably flash PA soon if some issues pop up with the cm9 build I'm using now.
Draw something is compatible with jellybean no doubt since I installed it on my HOV and it works.
title says it all thanks
Do you want to use anything that requires root? Then yes. You don't? Then no.
I personally do use apps that require root, plus I enjoy having full control over my phones, so I immediately root, unlock the bootloader, and install a custom recovery. But that's not for everyone.
Just use it for a week and see if there's any functionality you miss. Or to put it a different way: when in doubt, no.
well i use xmod b4 but now i cant even if i root my phone cos its x86 i have htc desire x b4 rooted.
but this fone i see a lot of threads "UNOFFICIAL" on rooting, unlocking bootloader, rom and etc... so im 50/50 i dont
want to brick this phone even if its cheap..
t0per666 said:
well i use xmod b4 but now i cant even if i root my phone cos its x86 i have htc desire x b4 rooted.
but this fone i see a lot of threads "UNOFFICIAL" on rooting, unlocking bootloader, rom and etc... so im 50/50 i dont
want to brick this phone even if its cheap..
Click to expand...
Click to collapse
its your choice but i personally would...and the unofficial methods work perfectly fine..im getting the 4GB RAM variant today and as soon as i get it im rooting, unlocking bootloader ,installing my Xposed Modules and stuff.
Depends on why you'd want to root. I like tinkering and using Adaway, so it was a no brainer for me.
smokinjoe2122 said:
Depends on why you'd want to root. I like tinkering and using Adaway, so it was a no brainer for me.
Click to expand...
Click to collapse
adaway is always a must for me when I root its the very first thing I install lol
Its your choice. Like what others mentioned. Depends on what you need.
YES. The bloatware is ridiculous. I'm probably going to write a tutorial on how to do everything start to finish if you're buying a new 551. Not that bad if you have all the files. Really easy, but good grief, are all the tutorials out there now confusing. Most don't even tell you, you need to downgrade... Took me hours to figure it out. Finally, have a debloated rom, root, and busybox installed so I can install Kali Linux
Yeah the bloatwares! But i think im gonna wait till android m has been released thanks all?
t0per666 said:
Yeah the bloatwares! But i think im gonna wait till android m has been released thanks all��
Click to expand...
Click to collapse
Same, I am going to wait until Android M as well. I found that when you root phones b4 they get their "improved" stock firmware, the modem/wifi/bluetooth never seem to flash the same and are always buggy. I am being careful with this phone because it works quite good minus the terrible battery life, but on my OnePlus One, I found a 40% increase in battery life even on the early early Android M roms. Seeing that there is no roms even being worked on for 6.0, I am going to play it safe...after all, some of the bloat can be removed without root. Of course not the annoying ones though
djfirestorm said:
Seeing that there is no roms even being worked on for 6.0, I am going to play it safe...
Click to expand...
Click to collapse
Wrong. Better than just being worked on, an alpha of CM13 has been released today.
kanagawaben said:
Wrong. Better than just being worked on, an alpha of CM13 has been released today.
Click to expand...
Click to collapse
Yep that literally posted about the same time I made the comment lol. But having official firmware for Android M built by ASUS themselves, then having it customized by Asus would be better. I do not mean to insult CM, but I have yet to see a truly stable version of their software. Every phone I have had has shown to have issues with CM based roms. It's not the guys customizing the roms, its just the fact that CM is more universal and not necessarily developed for this specific phone by the original coders. Modded code always has issues, and if it comes out perfect, I hope these big companies pay whoever mods it to perfection and gives them a phat paying job. I want ZenUI, its one of the best non AOSP UI out there IMOP. I only want root to clean out the extras I don't want/need. It has more customization than a phone needs for the most part.
I am waiting also.
Sent from my ASUS_Z00AD using XDA Free mobile app
Hi,
So, cm-13 is very unlikely on our device, but i'll take a look anyway (a slow look as my time is very limited).
Here you'll find my "work" and "help requests".
First, for sure i didn't "worked" on a lot of device, but it's the first one i have with a dedicated partition to the kernel dts.
Code:
/dev/block/platform/hi_mci.0/by-name/dts /dts emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/boot /boot emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/recovery /recovery emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/misc /misc emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/modem /modem emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/modem_dsp /modem_dsp emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/sensorhub /sensorhub emmc defaults recoveryonly
- I wonder if the dts, which is kernel dependent, could be the major problem to get a custom rom version (kk, jb, mm), or even a stock huawei rom, to work from any base rom. I'll try to make some experiment soon.
- I did sync cm-13, and "of course" have cwm recovery working. But whatever i'm trying i can't get screen output on twrp 3.0. Does someone have a clue on this?
- @gabry3795 , do you still have the device ? I would be happy to get your hangout/google nickname if you have any to sometime talk about this device. @codeworkx is of course also welcome for any advice. By the way your cm12.0 github repo (codeworkx) doesn't seem's to be up to date, even if i understand that's it's in a non-working state.
Cpasjuste said:
@codeworkx is of course also welcome for any advice. By the way your cm12.0 github repo (codeworkx) doesn't seem's to be up to date, even if i understand that's it's in a non-working state.
Click to expand...
Click to collapse
You're looking at the wrong account.
https://github.com/honor6-dev
Start recovery and have a look at /tmp/recovery.log.
Hint:
https://github.com/honor6-dev/andro...common/blob/cm-12.1/BoardConfigCommon.mk#L150
https://github.com/CyanogenMod/andr...mmit/7273770a9fedff12ca80135356c52fee06c8aba0
Cpasjuste said:
- @gabry3795 , do you still have the device ? I would be happy to get your hangout/google nickname if you have any to sometime talk about this device. @codeworkx is of course also welcome for any advice. By the way your cm12.0 github repo (codeworkx) doesn't seem's to be up to date, even if i understand that's it's in a non-working state.
Click to expand...
Click to collapse
Yes, I still have this device! I'll write you via pm my nickname.
good luck you guys
i have really nothing to offer ..
but please make this happen ..
Unfortunately I really have no time to play with it this days, I'll try to take a look soon.
Envoyé de mon HUAWEI MT7-L09 en utilisant Tapatalk
Cpasjuste said:
Unfortunately I really have no time to play with it this days, I'll try to take a look soon.
Envoyé de mon HUAWEI MT7-L09 en utilisant Tapatalk
Click to expand...
Click to collapse
pls we wait for a long time:good:
It would be great to se cm no this device. Good luck and hope you make it. I would help if knew anything about programming but unfortanatly i dont
Cm we want... thank you for your interest!! ?
Kzyw said:
Cm we want... thank you for your interest!!
Click to expand...
Click to collapse
+1
why is there not one custom rom for this device?
Motawa88 said:
why is there not one custom rom for this device?
Click to expand...
Click to collapse
because huawei refuses to share their kernel source. suffice it to say, im done with huawei. its a good thing that there are many new phones being released soon. from now on its snapdragon or nothing!
Motawa88 said:
why is there not one custom rom for this device?
Click to expand...
Click to collapse
As I understand there are some crucial files / source codes that Huawei is refusing to release to the public. This alone sounds super dodgy, because isn't Android supposed to be open source? Or can companies "own" a custom version of Android and do this sort of thing?
These files are crucial for creating custom kernels and ROMs, as they have to do with (once again, this is how I interpreted it) how the device handles the CPU and GPU.
Basically, while it is possible to install other ROMs on the device, they'll have to be based on EMUI and its kernels, because it is the only thing that contains these files necessary to make the device run, which makes the entire exercise pointless because EMUI is s*** no matter what form it takes.
I wonder if it wouldn't be possible to simply "extract" this necessary code from the stock kernels / ROMs and implement it in a custom one? I do not know even the slightest thing about programming, so I could just be sounding like an idiot.
Scruffykid said:
I wonder if it wouldn't be possible to simply "extract" this necessary code from the stock kernels / ROMs and implement it in a custom one? I do not know even the slightest thing about programming, so I could just be sounding like an idiot.
Click to expand...
Click to collapse
i too have wondered about this. im sure its possible but it might be far to difficult an endeavor because if it weren't, someone would have attempted it by now. i really miss my nexus 5 with all its custom roms. i suggest that all mate 7 owners get in contact with huawei and demand they comply with the android user agreement. they are technically supposed to give up sources. we could fight, but not unless we unite.
Yes we can! Yes we can! Yes we can!
Scruffykid said:
As I understand there are some crucial files / source codes that Huawei is refusing to release to the public. This alone sounds super dodgy, because isn't Android supposed to be open source? Or can companies "own" a custom version of Android and do this sort of thing?
These files are crucial for creating custom kernels and ROMs, as they have to do with (once again, this is how I interpreted it) how the device handles the CPU and GPU.
Basically, while it is possible to install other ROMs on the device, they'll have to be based on EMUI and its kernels, because it is the only thing that contains these files necessary to make the device run, which makes the entire exercise pointless because EMUI is s*** no matter what form it takes.
I wonder if it wouldn't be possible to simply "extract" this necessary code from the stock kernels / ROMs and implement it in a custom one? I do not know even the slightest thing about programming, so I could just be sounding like an idiot.
Click to expand...
Click to collapse
You're right, extracting stock binary files is an essential part of roms porting but some important files can't be inherited because they are strictly hardware-related, therefore you have to compile the original android source and then "patch" that files for the specific GPU/CPU (starting from android 5 lollipop) with other files given by the vendor of the phone.
gabry3795 said:
...then "patch" that files for the specific GPU/CPU (starting from android 5 lollipop) with other files given by the vendor of the phone.
Click to expand...
Click to collapse
But isn't that the entire problem, the "other files" that have to be supplied by the vendor? Huawei is refusing to release them, and therefore making it impossible to develop custom ROM's.
Or are you saying that it is possible, but there just isn't enough interest in the phone for anyone with the necessary skills to actually go through the trouble?
Scruffykid said:
But isn't that the entire problem, the "other files" that have to be supplied by the vendor? Huawei is refusing to release them, and therefore making it impossible to develop custom ROM's.
Or are you saying that it is possible, but there just isn't enough interest in the phone for anyone with the necessary skills to actually go through the trouble?
Click to expand...
Click to collapse
I'm saying that Huawei must provide that 'patches' (as Qualcomm did, for example) otherwise is impossibile to build a working ROM, this is the problem. We cannot do anything without them.
gabry3795 said:
I'm saying that Huawei must provide that 'patches' (as Qualcomm did, for example) otherwise is impossibile to build a working ROM, this is the problem. We cannot do anything without them.
Click to expand...
Click to collapse
this is why we should all come together so as to put pressure on huawei to release these files. i have been trying for months now but its getting very tiresome. im going to start a twitter account that will hopefully get their attention. i think the problem is that the general public dont know much/anything about custom roms. there should be a custom rom psa for all android users that point out the benefits of custom roms.
droidbot1337 said:
this is why we should all come together so as to put pressure on huawei to release these files. i have been trying for months now but its getting very tiresome. im going to start a twitter account that will hopefully get their attention. i think the problem is that the general public dont know much/anything about custom roms. there should be a custom rom psa for all android users that point out the benefits of custom roms.
Click to expand...
Click to collapse
I agree. If you get that account running let us know here so that we can support it.
Cheers! :good:
---------- Post added at 12:03 PM ---------- Previous post was at 11:32 AM ----------
droidbot1337 said:
because huawei refuses to share their kernel source. suffice it to say, im done with huawei. its a good thing that there are many new phones being released soon. from now on its snapdragon or nothing!
Click to expand...
Click to collapse
Agreed.
Unfortunately I live in a place where just picking up a new phone is not as easy as 123, But I think I'll try and get my hands on a different phone this weekend. Huawei pisses me off.
No source release by Huawei.
No Kirin SOC support would be a huge problem to get it working I think.