Just about every rom with than name gives me an error stating - "This package is for moto_msm8960, xt907, scorpion_mini, smq, xt926, vanquish" devices, this is a "mb886" Followed by the rom location and a status 7 right under it. I'm using the Philz Advanced recovery version 6.0.4.4. Is there a workaround to this or will I just have to wait until stock KitKat comes to the Atrix HD?
I believe there's a work around. I'm running a ROM that was built for kk BL but someone has built me the ROM to work jb BL.
RagInCajun00 said:
Just about every rom with than name gives me an error stating - "This package is for moto_msm8960, xt907, scorpion_mini, smq, xt926, vanquish" devices, this is a "mb886" Followed by the rom location and a status 7 right under it. I'm using the Philz Advanced recovery version 6.0.4.4. Is there a workaround to this or will I just have to wait until stock KitKat comes to the Atrix HD?
Click to expand...
Click to collapse
Any "unified" ROM (based on the msm8960 chipset) you're trying to install will not work after July 1st, with the exception of CyanogenMod version M8. Any Nightly you try and flash needs to have been built before 7/1. Try that and see what happens.
If you want to flash any unified ROM built after that date, then either (1) the Atrix HD needs to get the official KitKat update from Mototorola, or (2) a workaround needs to be implemented specifically for our phone.
I believe one of the CM devs (Epinter) was doing that, but YMMV, because it's unclear how long that will continue to be supported.
p.s. Unrelated, but Philz has been updated several times, so you may be inclined to flash a newer version.
quasihellfish said:
Any "unified" ROM (based on the msm8960 chipset) you're trying to install will not work after July 1st, with the exception of CyanogenMod version M8. Any Nightly you try and flash needs to have been built before 7/1. Try that and see what happens.
If you want to flash any unified ROM built after that date, then either (1) the Atrix HD needs to get the official KitKat update from Mototorola, or (2) a workaround needs to be implemented specifically for our phone.
I believe one of the CM devs (Epinter) was doing that, but YMMV, because it's unclear how long that will continue to be supported.
p.s. Unrelated, but Philz has been updated several times, so you may be inclined to flash a newer version.
Click to expand...
Click to collapse
Ahh I'll check around for any updates for the recovery, guess I'll be waiting for the official AHD KitKat to finally come around
RagInCajun00 said:
Ahh I'll check around for any updates for the recovery, guess I'll be waiting for the official AHD KitKat to finally come around
Click to expand...
Click to collapse
Like I said, if you want to try it out, just flash a ROM from before 7/1. I'm running CarbonRom from the 6/30 nightly, and it's great.
http://forum.xda-developers.com/showthread.php?t=2635765
Validus still works
Epinter is still building nightlies for us. You can find them here:
https://goo.im/devs/epinter/
Related
THIS OP IS OUTDATED! WIP!
Hello everybody!
You might or might not have already heard of MultiROM, THE multi-boot mod for the Nexus 7. I have recently found it and have decided to port it for our device.
First of all, it is a very initial release now. Though I have tested multiple cases and didn't find any problem except those in the bug list, bugs can arise. Do have a backup! Also, do read through the whole OP and 2nd post! If you don't understand something, rather read again and/or ask!
For more information on how it works and what it does, I suggest that you read the first few posts in the original thread. Those are very detailed and well-written posts that explain MultiROM in general. Installing roms to USB and Ubuntu/Ubuntu Touch of course doesn't work for our device atm.
Installation
The device must not be encrypted!
You need to flash the modified TWRP recovery that has MultiROM extensions. My version is based on the latest sources with gordon0001's device-specific modifications included. You can keep this recovery if you don't want to use MultiROM anymore and you like TWRP, because the MultiROM extensions don't interfere with other functions, even if the boot sector is not injected.
You have to flash a kernel that is capable of Kexec-hardboot. I compiled iodak's v07 CM kernel and official CM kernel with the patch, choose one of them. I have noticed an approx. 3 sec. vibration at boot with iodak, that's why I have included official CM kernel too.
Finally you have to flash MultiROM.
Links
You can find everything at http://d-h.st/users/Adam77Root/?fld_id=22980#files.
MultiROM_TWRP_X3.zip: The modified TWRP recovery from latest sources with gordon0001's device-specific changes and MultiROM support.
CM_kernel_patched.zip and iodakX3_v07CM_patched.zip: Official and iodak CM kernels with Kexec-hardboot patch.
iodakX3_v07_patched.zip: iodak stock kernel with Kexec-hardboot patch.
MultiROM_P880_v12.zip: The actual MultiROM package. Contains the latest version of Trampoline (the init binary of the system) and MultiROM binaries with all the needed device-specific changes. Even Pong works pretty smooth.
x3_hardboot.diff: Kexec-hardboot patch for 3.1.10 kernel.
mrom_p880.patch: Device-specific changes for Trampoline and MultiROM.
ui.xml: UI layout definition for TWRP for 720x1280 screens with MultiROM additions.
Known bugs
Reboot to recovery doesn't work.
USB tab doesn't do anything. This is because USB host mode (OTG) doesn't work on our device. Will reach out to kholk regarding this.
Sometimes in landscape mode, the default selected rom gets booted on the first touch. This is yet to be investigated.
Changelog
14 August 2013: Initial release
Credits
@Tasssadar for MultiROM, Kexec-hardboot for Nexus 7 and his help with debugging and porting
@mkasick for original Kexec-hardboot implementation
@iodak for his kernel
@gordon0001 for the device-specific TWRP modifications
Every custom modification to devices have risks. Flash these at your own risk!
Have fun and enjoy!
General use
Some notes and instructions regarding general use
For now, I have only provided patched 4.2.2 CM kernels. This means, you have to be on CM or CM-based rom with Android version 4.2.2. Don't try it with stock at the moment in any way. It won't work, but is on the to-do list. As Kexec-hardboot will reach out to devs, it will be supported in every rom ultimately.
In the next two examples, I will refer any official, unofficial, or CM-based roms as CM. Keep this in mind.
I use the word 'injected', because MultiROM is actually injected into the boot partition. It works on any kernel that is capable of doing Kexec-hardboot (and if you don't want to use different kernel (i.e. you will use kernel sharing), it will work on unpatched kernels as well).
I may refer to non-shared kernel method as Kexec(-hardboot) method.
Example scenario of multi-booting CM with CM and kernel sharing
You are on CM with MultiROM-capable recovery, patched kernel and MultiROM-injected and you want to install e.g. CarbonRom as second.
Boot into TWRP, navigate to Advanced->MultiROM and select 'Add ROM'. Since the base rom is CM, you can share the same kernel. It will be faster as there will be no hardboot needed.
The installation steps are easy and it doesn't take more time than a normal installation.
Example scenario of multi-booting CM with CM and different kernel
You are on CM with MultiROM-capable recovery, patched kernel and MultiROM-injected and you want to install e.g. CarbonRom as second.
Boot into TWRP, navigate to Advanced->MultiROM and select 'Add ROM'. Select 'Don't share'.
Continue with installation.
Now, since the target kernel (that is installed with the rom) is very likely not patched, you will have to flash one of my linked kernels to that rom. Do this by selecting 'List roms', selecting the desired rom, than 'Flash ZIP' and flashing one of the kernels I have patched.
You can only share the kernels between the same Android version (i.e. stock base->only stock rom can use shared kernel, 4.2 base->only 4.2 rom can use shared kernel, 4.3 base->only 4.3 rom can use shared kernel, etc.), but this is not the case with the Kexec method. Just keep in mind that for example even if your base rom is CM, for a stock secondary rom you have to flash a stock patched kernel.
The build
Some notes about the build
x3_hardboot.diff: This is the Kexec-hardboot patch for the 3.1.10 kernel. Since it is needed for target kernels as well, I would like to reach out in this post to @arararagi, @demetris_I, @iodak, @kholk, @laufersteppenwolf and @Pesach85 (in no particular order, this is how your threads are in order in Original Android Development forum right now). I and fellow users would be grateful if you could include the patch in the kernel so they can be used as both host and target kernels as well. UPDATE: It doesn't reserve one more megabyte before ram_console from now on.
mrom_p880.patch: This contains all the device-specific patches that are needed to get MultiROM booting and working on the P880. It is built on top of the latest git changes as of today. It also contains some comments about multiple devices compatibility, those are reminders for Tasssadar.
ui.xml: UI layout definition for TWRP for 720x1280 screens with MultiROM additions. Needs to be put into TWRPdir/gui/devices/720x1280/res/. The recovery I have created is based on the latest MultiROM TWRP with @gordon0001's device-specific changes.
You can find links to the upstream MultiROM and MultiROM TWRP in the original thread.
Simply incredible!!! :thumbup:thanks a lot man. I always wanted to try dualboot
Sent from my LG-P880 using xda premium
Awaiting the Patched Stock Kernel to dual boot stock and AOSP Good Work man, hopefully @iodak will be able to patch his kernel by today so i can get modding :3
Nice work man! I have also seen hardboot kernels in the N7 section, but got into the hospital then....
But i will include it for sure when i'm back home
Sent from my Nexus 7 using XDA Premium HD app
tnx for your very nice work
how i can flash twrp ?
i want to flash it on cwm but i cant
edite : thats my fault i am so sorry
penguin449 said:
Awaiting the Patched Stock Kernel to dual boot stock and AOSP Good Work man, hopefully @iodak will be able to patch his kernel by today so i can get modding :3
Click to expand...
Click to collapse
If anybody won't be faster, I will provide it tomorrow.
laufersteppenwolf said:
Nice work man! I have also seen hardboot kernels in the N7 section, but got into the hospital then....
But i will include it for sure when i'm back home
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks! Take your time, rest and get better!
Sent from my LG-P880
Adam77Root said:
If anybody won't be faster, I will provide it tomorrow.
Sent from my LG-P880
Click to expand...
Click to collapse
Don't get me wrong, i would be more then Happy to do it myself, however till my new PC Arrives i wont be able to use a Linux Distro for some time, if there's a method to do this on windows (Natively, can't even run anything in VM's) then point me in the right direction! Sorry for the inconvenience!
penguin449 said:
Don't get me wrong, i would be more then Happy to do it myself, however till my new PC Arrives i wont be able to use a Linux Distro for some time, if there's a method to do this on windows (Natively, can't even run anything in VM's) then point me in the right direction! Sorry for the inconvenience!
Click to expand...
Click to collapse
I didn't get you wrong buddy. I have no problems with making a stock version, just didn't have time for that today.
Sent from my LG-P880
giantic hack
ohhh well the one big giantic hack is coming to our O4X! that`s very nice
thank you for this port and thank you for your fast work? tomorrow with stock and on saturday with android 4.3 ?
Donation sent
Whaaaaaattt?
Just were browsing N7 forum few days ago and saw MultiROM and thought "Ahh these lucky nexus guys, I wanna have it to! " and here we go hahahah
Sent from my OptimusX4HD using xda app-developers app
how can install rom to ext-sd ?
in next version can we have stock rom and miui rom or other custom rom?
tnx
Hey guys, heres iodak stock kernel with kexec patch: https://www.dropbox.com/s/ko752pu1akuvfzh/iodakX3_v07-realms.zip
Btw i theres a problem with the twrp zip package, im gonna try fastboot flash it. Has anyone had success?
Say Whut?
@Adam77Root, you just made me wanna flashing and flashing and flashing one day before I go into vacation, I will try to get some time today and test it!
Thanks so much!
Afro said:
Say Whut?
Adam77Root, you just made me wanna flashing and flashing and flashing one day before I go into vacation, I will try to get some time today and test it!
Thanks so much!
Click to expand...
Click to collapse
You can flash 10 different roms and play with them over your vacation. Thats what vacations are right?
Hehe @JoinTheRealms , you understand me
Wow, I just saw your Iodak Stock Kernel with Kexec patch, verrry nice, now I can use Stock ROMs, too!
Did you already test it?
JoinTheRealms said:
Donation sent
Click to expand...
Click to collapse
Thanks very much!
m.homauon said:
how can install rom to ext-sd ?
in next version can we have stock rom and miui rom or other custom rom?
tnx
Click to expand...
Click to collapse
You can't install to external SD. It could be modified to allow it, but there would be a huge performance decrease. Literally, roms would be lagging too much.
JoinTheRealms said:
Hey guys, heres iodak stock kernel with kexec patch: https://www.dropbox.com/s/ko752pu1akuvfzh/iodakX3_v07-realms.zip
Btw i theres a problem with the twrp zip package, im gonna try fastboot flash it. Has anyone had success?
Click to expand...
Click to collapse
Just was about to reply to your PM.
What kind of problem is with the zip package?
I will update the first posts in the afternoon.
Afro said:
Hehe @JoinTheRealms , you understand me
Wow, I just saw your Iodak Stock Kernel with Kexec patch, verrry nice, now I can use Stock ROMs, too!
Did you already test it?
Click to expand...
Click to collapse
Nah i couldnt get the twrp package to flash so im gonna try with fastboot. But the kernel works, i just swapped the ramdisk from Adam77roots patched kernel with iodak's stock kernel, it should work though
---------- Post added at 07:21 PM ---------- Previous post was at 07:19 PM ----------
Adam77Root said:
Just was about to reply to your PM.
What kind of problem is with the zip package?
I will update the first posts in the afternoon.
Click to expand...
Click to collapse
My twrp failed to flash your twrp.zip package, most likely something on my end though, no one else has reported issues
Hello everybody
I have a Sony Xperia T, and when I got tired of the stock ROM (JB 4.1.2), updated with PC Companion to 4.3, and everything started to go wrong. While daily use, the screen sometimes turned blue and afterwards the phone rebooted. This happened approximately once a week.
Less frequently, the phone shut down and I couldn't turn it on tipically by holding power button for few seconds. Otherwise, I had to press volume up + power keys until first vibration (I read this simulates battery removal) in order to start my phone.
I thought it might be due to the new ROM, so I flashed CM 10.2, but I had the same problem. Recently, I tried with PACMAN ROM (my current firmware), but it could not solve the problem neither.
Few weeks ago I read that this bug might be a kernel issue, but I'm not quite sure. Do you have any idea about what happens? Flashing a new kernel would end the problem? In that case, which one do you recommend? My phone is rooted, bootloader unlocked and CWM v 6.04.
Thanks you all for your time :fingers-crossed:
P.D.: I attach a screenshot with kernel, build, android version...
i dont know why someone would try out pac rom, a rom without a good forum thread support. a rom which seems dead for our phone?
about cyanogenmod, i not use it...so i just can guess: maybe they still not use the new sony 4.3 kernel source...that could be a reason for bluescreens (same pac rom)?
so you have this options:
omnirom official nightlies by tilal6991
omnirom homebuilds by scanno
latest paranoid android by tilal6991
plain AOSP by Rimmer1966
these use new kernel source, no bluescreens, good user experience, daily driver material.
try out and become happy...
you can find them in xperia T forum, just look around
edit:
why you have android version 4.2.2? is that a bug? build date 1.aug 2013?
we have already awesome kitkat (android 4.4.2) roms (list above)^^
immerblind said:
i dont know why someone would try out pac rom, a rom without a good forum thread support. a rom which seems dead for our phone?
about cyanogenmod, i not use it...so i just can guess: maybe they still not use the new sony 4.3 kernel source...that could be a reason for bluescreens (same pac rom)?
so you have this options:
omnirom official nightlies by tilal6991
omnirom homebuilds by scanno
latest paranoid android by tilal6991
plain AOSP by Rimmer1966
these use new kernel source, no bluescreens, good user experience, daily driver material.
try out and become happy...
you can find them in xperia T forum, just look around
edit:
why you have android version 4.2.2? is that a bug? build date 1.aug 2013?
we have already awesome kitkat (android 4.4.2) roms (list above)^^
Click to expand...
Click to collapse
First of all, thank you for your quick reply, I'll take it account
The reason why I tried with CM10.2 and Pacman ROM is that they are not nightlies. I don't totally rely on nightiles because of the many bugs ther're reported. Anyway, I'll try with some of the ROMs above.
Finally, I would like to know if I coud stay with my current ROM and solve my problem only by flashing a new kernel.
Thank you again ^^
you dont rely on nightlies? wrong decision regarding omnirom, all on my above list is daily driver material (even the nightlies)
easy Kernelchange and keep this outdated pac rom with 4.2.2? NO!
its that simple. there is no reason to use such an outdated custom rom, no reason!
Ok, I refused to change kernel, and flashed the third one of the list: "latest paranoid android by tilal6991" (I liked a review about it). However, the problem persists :crying: And that's a pity, because I love how the new ROM looks like
Take a look to the new screenshot of "About phone". The kernel version seems to be different to the one of the last cap. Any idea?
Thanks in advance!
I couple months ago i got my Atrix HD rooted and the guy said all i have to do now is download the roms and flash them. He gave me the procedure which i follow to the neck and it has worked. Now the problem i have is that im trying to upgrade from 4.2.2 to 4.4 (kitkat) but all the custom ROMS fail, i tried the same with a PAC 4.3 rom which worked partially as the apps kept malfunctioning ("blame tyler XYZ has stopped working"). Is it because im using CWM instead of TWRP and if not someone please tell me what am i missing. i really want a stable 4.4 ROM :crying:
Which ROM are you trying to flash? You might be flashing the nightlies after 06/30. After that date, cyanogenmod and others started using the KitKat bootloader for the unified msm8690 builds, the processor architecture that a lot of moto phones share. Unfortunately, the atrix HD hasn't been officially upgraded to KitKat yet from Motorola. Our atrix HD uses the jelly bean bootloader.
So since 6/30, when they switched to the KitKat bootloader, we haven't been able to flash nightlies (with exceptions in AOSB and some CM and CarbonROM builds).
Try flashing a KitKat rom built before 6/30, then get back to us. It should work if you're using cwm, since I'm using cwm 6.0.4.4 and it works fine.
If you flashed the latest cwm that could cause problems too, since I read its also running off the KitKat bootloader.
Dr. Orange said:
Which ROM are you trying to flash? You might be flashing the nightlies after 06/30. After that date, cyanogenmod and others started using the KitKat bootloader for the unified msm8690 builds, the processor architecture that a lot of moto phones share. Unfortunately, the atrix HD hasn't been officially upgraded to KitKat yet from Motorola. Our atrix HD uses the jelly bean bootloader.
So since 6/30, when they switched to the KitKat bootloader, we haven't been able to flash nightlies (with exceptions in AOSB and some CM and CarbonROM builds).
Try flashing a KitKat rom built before 6/30, then get back to us. It should work if you're using cwm, since I'm using cwm 6.0.4.4 and it works fine.
If you flashed the latest cwm that could cause problems too, since I read its also running off the KitKat bootloader.
Click to expand...
Click to collapse
i've tried (cm-11-20140218-NIGHTLY-mb886, pac_moto_msm8960-nightly-20140519 &Gummy-M2.2-06-15-14-NIGHTLY-moto_msm8960) none have worked but im going to try (aokp_moto_msm8960_kitkat_unofficial_2014-04-24.zip) hopefully it works
CWM works well on the Atrix HD so I would stick with that.
Why not start over by flashing back to stock ATT 4.1.1, take the OTA update, flash CWM in fastboot, and flash a custom KK ROM?
audit13 said:
CWM works well on the Atrix HD so I would stick with that.
Why not start over by flashing back to stock ATT 4.1.1, take the OTA update, flash CWM in fastboot, and flash a custom KK ROM?
Click to expand...
Click to collapse
Not a bad idea. Takes time but not much. Try team gummy for 4.4.2 ROM here, make sure you download the M2.0 release, because the M3.0 is KitKat bootloader. Its my daily driver cuz it's light and has pie controls. http://androidhosting.org/Devs/Gummy/moto_msm8960/RELEASE/
99% of the ROMs i've installed haven't worked....I got AOSB to work once....but its not working at all now...I got PXS to boot but kept having FCs.....now nothing gets past the boot logo
audit13 said:
CWM works well on the Atrix HD so I would stick with that.
Why not start over by flashing back to stock ATT 4.1.1, take the OTA update, flash CWM in fastboot, and flash a custom KK ROM?
Click to expand...
Click to collapse
never thought of this...will do :good:
Dr. Orange said:
Which ROM are you trying to flash? You might be flashing the nightlies after 06/30. After that date, cyanogenmod and others started using the KitKat bootloader for the unified msm8690 builds, the processor architecture that a lot of moto phones share.
Click to expand...
Click to collapse
FYI, as of a few days ago, CyanogenMod started officially supporting devices still on the JB bootloader (which includes the Atrix HD). See here: https://download.cyanogenmod.org/?device=moto_msm8960_jbbl
It's what I'm running, and it's great.
Also, if you're having trouble flashing, try using Philz recovery version 6.43.8 (not any later versions). Not sure if CWM supports some of these ROMs or not.
quasihellfish said:
FYI, as of a few days ago, CyanogenMod started officially supporting devices still on the JB bootloader (which includes the Atrix HD). See here: https://download.cyanogenmod.org/?device=moto_msm8960_jbbl
It's what I'm running, and it's great.
Also, if you're having trouble flashing, try using Philz recovery version 6.43.8 (not any later versions). Not sure if CWM supports some of these ROMs or not.
Click to expand...
Click to collapse
Isn't Philz Touch based off CWM?
audit13 said:
Isn't Philz Touch based off CWM?
Click to expand...
Click to collapse
Yes, but I was just trying to say that I know that version of Philz is up to date, and works with KitKat roms. Not sure what version of CWM you were using, or where the support falls. Just a suggestion if you were having issues.
quasihellfish said:
Yes, but I was just trying to say that I know that version of Philz is up to date, and works with KitKat roms. Not sure what version of CWM you were using, or where the support falls. Just a suggestion if you were having issues.
Click to expand...
Click to collapse
I am using the 6.0.4.4 version directly from the Clockworkmod website. I have been using it to flash the latest ROMs with no issues at all. Backup, restore, formatting, etc. work fine in the non-Philz version.
I must admit that Philz is convenient because it automates a lot of functions.
Why is it that any ROM with the MSM8960 name in the thread for Atrix HD ROMs not work for me? ANYTIME I try to flash one, it errors out on me....usually error code 7 or something funky happens....(won't make it past boot screen)....I have tried about 10 ROMs but maybe 3 work...
I have used both CWM Touch and Philz Touch 6 to flash these ROMS...always doing wipes, etc..
Dvdxploitr said:
Why is it that any ROM with the MSM8960 name in the thread for Atrix HD ROMs not work for me? ANYTIME I try to flash one, it errors out on me....usually error code 7 or something funky happens....(won't make it past boot screen)....I have tried about 10 ROMs but maybe 3 work...
I have used both CWM Touch and Philz Touch 6 to flash these ROMS...always doing wipes, etc..
Click to expand...
Click to collapse
I answered in the other thread you started: http://forum.xda-developers.com/atrix-hd/help/jb-kernel-kk-bootloader-t2839673
As for now you can try validus as is the only rom with a work around to work great with jb and kk bootloaders.
TecknoFreak said:
As for now you can try validus as is the only rom with a work around to work great with jb and kk bootloaders.
Click to expand...
Click to collapse
I got Validus 6.0 with JellyBean Bootloader installed...man that thing is FAST!!! I thought my Galaxy Nexus was quick, but the Atrix HD with Validus 6.0 SMOKES it! I'm perfectly happy with that setup!
(I have a good bit of phones so i'm always going back and forth between phones and ROMs)
TecknoFreak said:
As for now you can try validus as is the only rom with a work around to work great with jb and kk bootloaders.
Click to expand...
Click to collapse
Not to knock your valiant work on Validus (never actually tried it), but CM11 has official support for JB bootloaders on this device, as of a few days ago. http://forum.xda-developers.com/showpost.php?p=54567785&postcount=382
Olympus Unofficial OmniROM 4.4.4 PREVIEW test
This is a development thread .
This is a Omni4.4.4 firmware for Atrix. It's not a official Omni.
Quote:
Disclaimer: THIS FIRMWARE IS IN ALPHA STAGE OF DEVELOPMENT.
I'm not responsible by phone bricks of any kind, or any other damage this firmware may cause to you, to your phone or any accessories conected to your phone.
This ROM uses the kernel 3.1.10, from Olympus Kernel Project:http://forum.xda-developers.com/showthread.php?t=2016837
WHAT IS WORKING?
ART
Bluetooth (Instable)
sound
wifi
need more testing...
WHAT ISN'T WORKING?
need more testing...
Battery statistics 100% Unknown
recovery(Thank Zn7mkUKzN1r8aCIV):
http://forum.xda-developers.com/showthread.php?t=2613829
ROM:The new
Wait until the restoration of some of the other bug, hope to help test.
ROM:201408062225
<s>http://d-h.st/iq6 </s>
Requirements:
Clockworkmod or compatible recovery
Atrix 4G with unlocked bootloader
WARNING: I DECLINE ANY RESPONSIBILITY IN DAMAGING YOUR PHONE. YOU ASSUME ALL RISKS IN ANY PROCESS DESCRIBED ON THIS PAGE.
Thanks to all the users for using and debugging.report all bugs here,Thank
I'm fixing the digitizer of my second atrix, definitely i'm going to test it and help you with logs. Keep on the good work.
Best regards.
fengyr said:
Olympus Unofficial OmniROM PREVIEW test
This is a development thread .
This is a Omni4.4.4 firmware for Atrix. It's not a official Omni.
Quote:
Disclaimer: THIS FIRMWARE IS IN ALPHA STAGE OF DEVELOPMENT.
I'm not responsible by phone bricks of any kind, or any other damage this firmware may cause to you, to your phone or any accessories conected to your phone.
This ROM uses the kernel 3.1.10, from Olympus Kernel Project:http://forum.xda-developers.com/showthread.php?t=2016837
WHAT IS WORKING?
ART
Bluetooth
need more testing...
WHAT ISN'T WORKING?
WIFI (Unable to search)
Audio
need more testing...
recovery(Thank Zn7mkUKzN1r8aCIV):
http://forum.xda-developers.com/showthread.php?t=2613829
ROM:http://d-h.st/Dgo
Requirements:
Clockworkmod or compatible recovery
Atrix 4G with unlocked bootloader
WARNING: I DECLINE ANY RESPONSIBILITY IN DAMAGING YOUR PHONE. YOU ASSUME ALL RISKS IN ANY PROCESS DESCRIBED ON THIS PAGE.
Thanks to all the users for using and debugging.report all bugs here,Thank
Click to expand...
Click to collapse
Way cool, will backup can test what's listed as working and see if i can find more of what's not working.
Thanks
Has changed the default language en_US.Update rom url
Not bad!
So I gave this test ROM a try. It's nice to see KitKat running on an Atrix 4G! I'm so excited to see some progress!
However, there are definitely several issues with it. The problems I found are:
Calls/text doesn't work
Mobile data doesn't work (says AT&T 4G but no connection)
SuperSU doesn't appear to work (crashed when opening and wouldn't let an app have root access)
Bluetooth didn't turn on for me (but I see you seemed to get it working, maybe it was just bad luck)
No WIFI (doesn't scan as you stated in the post)
Couldn't test any apps or camera because I couldn't restore my apps without root, and the camera must be a part of gapps now, which I also didn't install.
I was also gonna post some screenshots but it wouldn't let me snapshot (said storage error?)
Just thought I would sum up my experience so far. Thanks for letting us test out this promising new ROM! :good:
why need to test this ROM if K did not update his kernel from GitHub? had all same issues isn't it?
thecjan said:
why need to test this ROM if K did not update his kernel from GitHub? had all same issues isn't it?
Click to expand...
Click to collapse
K's kernels are CM9 and CM10.1 based. This is a CM11 based kernel with a build date of 6 Aug 14
Calls - No go
BT (file transfer) - Go
Wifi - same as OP reported
Battery - same as OP reported (There's no way that after 8 hrs it should still be at 100%)
Speakers/Headphones - No go
Apollo/DSP Manager - Crash
Ravilov's Battery Fix app - scripts not able to be executed
Thanks!!!
Mobile data seems to be working, Bluetooth and superuser. ART included, I'll do more testing later.
thank for the rom!
thecjan said:
why need to test this ROM if K did not update his kernel from GitHub? had all same issues isn't it?
Click to expand...
Click to collapse
Don't be harsh to K, as I was fixing audio segfault in CM 4.4.4, the more I realized most of the audio problem (like Skype, Bluetooth error) is more ROM related than Kernal related. Most of them are due to incompatiblity of hardware HAL files in our unfinished Moto's 4.0 rom...... Of course Mobile Data HAL is sill PAIN IN THE AXX... ...
Zn7mkUKzN1r8aCIV said:
Don't be harsh to K, as I was fixing audio segfault in CM 4.4.4, the more I realized most of the audio problem (like Skype, Bluetooth error) is more ROM related than Kernal related. Most of them are due to incompatiblity of hardware HAL files in our unfinished Moto's 4.0 rom...... Of course Mobile Data HAL is sill PAIN IN THE AXX... ...
Click to expand...
Click to collapse
And what about to use - for now - the old kernel like epinter's CM10?, in XOOM kitkat they use and old 2.x kernel too, the hardware acceleration its not really a problem compared to use and unfinished kernel with more issues to solve.
Anyway we agree that Kristianp is doing it's best work to continue developing the 3.1 kernel, so any negative comentary should not be allowed as most of us are only users and some cooperate with minimal things.
I could boot my second atrix, now time to BL Unlock, root, etc and it's ready to test some KK roms.
It's great to see the "4.4.4" in the settings
Mobile internet works fine.
Kitkat feels quite snappy on this "too old, too slow" hardware.
Thank you so much for keeping the Atrix alive.
Will try to install the Play Store and test out some apps!
cannot wait to try this!
Booted up fine and looks slick. had to do some searching around to find how to switch to ART.
Also had to use Z's recovery_4.3.img... ROM won't install with TWRP.
Wish I could do more testing like battery but it's not feasible at the moment.
Looking forward to other releases to test.
Really love the tons of options available in KK.
phoenixgfx said:
Booted up fine and looks slick. had to do some searching around to find how to switch to ART.
Also had to use Z's recovery_4.3.img... ROM won't install with TWRP.
Wish I could do more testing like battery but it's not feasible at the moment.
Looking forward to other releases to test.
Really love the tons of options available in KK.
Click to expand...
Click to collapse
Which version of TWRP?
palmbeach05 said:
Which version of TWRP?
Click to expand...
Click to collapse
I think 2.6... not so sure.
TWRP 2.6.3 gives errors and aborts installation.
phoenixgfx said:
I think 2.6... not so sure.
Click to expand...
Click to collapse
Basmatek said:
TWRP 2.6.3 gives errors and aborts installation.
Click to expand...
Click to collapse
I believe, based off of what i've seen, 2.6.3.0 is the minimum to flash 4.4 ROMs, but 2.7 is reccommended.
Sent from my MB886 using xda app-developers app
There's no 2.7 for Atrix and apparently there's also no 4ext Recovery, so the only ways are CWM or Z's recovery (will try Z's on Monday or Tuesday)
Sent from my Nexus 7 using XDA Free mobile app
Thank friends test feedback .
Apply a new job,computer is not in my city, so the update rate slow down (my technique is limited).
I look forward to Z 4.4.4
please forgive my terrible english.
Please upload it to a diferrent pleace