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.
Related
Has anyone seen any mention of modem/TZ/RPM packages so those of us still on AOSP, can flash those and new ROMs and kernels built with new sources when available? Rather than having to go back to stock, update to KK, then pushing the JB aboot to get custom recovery back.
JRJ442 said:
Has anyone seen any mention of modem/TZ/RPM packages so those of us still on AOSP, can flash those and new ROMs and kernels built with new sources when available? Rather than having to go back to stock, update to KK, then pushing the JB aboot to get custom recovery back.
Click to expand...
Click to collapse
Not yet. We will have to see how out plays out the next week of so.
Sent from my VS980 4G using XDA Premium 4 mobile app
JRJ442 said:
Has anyone seen any mention of modem/TZ/RPM packages so those of us still on AOSP, can flash those and new ROMs and kernels built with new sources when available? Rather than having to go back to stock, update to KK, then pushing the JB aboot to get custom recovery back.
Click to expand...
Click to collapse
Depends on whether or not people can figure out a way to put a recovery on 4.4. As it stands right now, there is an issue with Loki and 4.4.
If no one can, then they are going to have to make the new 4.4 builds compatible with the 12b aboot just like roms needed patched for 12b when it first came out.
Sent from my LG-VS980
Post #2 to reach 10 min required posts to participate in Dev Section--yes I have a LG G2 running 24A :good:
Title says it all. I want a stock 4.1.2 ROM but able to flash it though cwm. Does any body know one?
Sent from my ATRIX HD using Tapatalk
topdawg661 said:
Title says it all. I want a stock 4.1.2 ROM but able to flash it though cwm. Does any body know one?
Sent from my ATRIX HD using Tapatalk
Click to expand...
Click to collapse
I'm quite partial to Carbon ROM, however it's Android 4.4.2
Holoblur would be the best AFAIK.
http://forum.xda-developers.com/showthread.php?t=2356624
jaweinre said:
Holoblur would be the best AFAIK.
http://forum.xda-developers.com/showthread.php?t=2356624
Click to expand...
Click to collapse
Would suggest to go for Mexico retail stock one.Its the best stable every seen by me.
Here is a few stock roms flashable with cwm: http://forum.xda-developers.com/showthread.php?t=2209660
Search around the Dev section a bit and try a few out, only you can decide which one is best.
I tried HoloBlur and HoloBlur X,but I kept getting a "Status 7" Error. Anyone have any ideas why? Ive tried everything I could think of. Everything else installs fine.
Status 7 error can occur if you are not running the latest recovery or you have a bad download.
audit13 said:
Status 7 error can occur if you are not running the latest recovery or you have a bad download.
Click to expand...
Click to collapse
Yeah ive got Phil's Touch recovery. works for every other rom I flash,But no stock based Roms,not even BataKang.
Been trying to flash dr87's kernel to the Mahdi ROM (which has been a great ROM thus far), phone ends up getting stuck on LG symbol and starts getting the white lines, at which point I reboot into recovery and just re-flash the ROM. I've read other people have been able to flash it to this ROM with no issues. Wiped Dalvik before flashing. This is the VS98024A. Any thoughts? Heard the combination of this kernel and ROM was really good, would definitely like to try it out.
TheFullSpectrum said:
Been trying to flash dr87's kernel to the Mahdi ROM (which has been a great ROM thus far), phone ends up getting stuck on LG symbol and starts getting the white lines, at which point I reboot into recovery and just re-flash the ROM. I've read other people have been able to flash it to this ROM with no issues. Wiped Dalvik before flashing. This is the VS98024A. Any thoughts? Heard the combination of this kernel and ROM was really good, would definitely like to try it out.
Click to expand...
Click to collapse
The DR's kernel is part of mahdi so not sure why you're trying to flash it.
Sent from my LG-VS980 using Tapatalk
TheFullSpectrum said:
Been trying to flash dr87's kernel to the Mahdi ROM (which has been a great ROM thus far), phone ends up getting stuck on LG symbol and starts getting the white lines, at which point I reboot into recovery and just re-flash the ROM. I've read other people have been able to flash it to this ROM with no issues. Wiped Dalvik before flashing. This is the VS98024A. Any thoughts? Heard the combination of this kernel and ROM was really good, would definitely like to try it out.
Click to expand...
Click to collapse
It's been discovered LG used two different panel types on the G2, check out the explanation in the Furnace thread. You need to use the kernel that matches your panel type. As noted above though, Mahdi has a dr87 kernel in it.
mjones73 said:
It's been discovered LG used two different panel types on the G2, check out the explanation in the Furnace thread. You need to use the kernel that matches your panel type. As noted above though, Mahdi has a dr87 kernel in it.
Click to expand...
Click to collapse
I see, was not aware of that, I will have to look into that more. From my understanding, I believe this specific kernel is different from the one he used for the Mahdi ROM. I did assume that he used that AOSP v7 kernel in the ROM, however that kernel can be OC to 2.8, where the ROMs can be up to 2.5, and I read that some people had flashed that kernel to the ROM as well with good results.
TheFullSpectrum said:
I see, was not aware of that, I will have to look into that more. From my understanding, I believe this specific kernel is different from the one he used for the Mahdi ROM. I did assume that he used that AOSP v7 kernel in the ROM, however that kernel can be OC to 2.8, where the ROMs can be up to 2.5, and I read that some people had flashed that kernel to the ROM as well with good results.
Click to expand...
Click to collapse
I just looked, his AOSP kernel is only for roms running 4.2.2 source under the cover, I'm pretty sure the latest Mahdi is running 4.4.2.
Furnace AOSP should work on Mahdi.
bender_007 has a tool you can install to tell you which panel you have, check his signature - http://forum.xda-developers.com/member.php?u=3279781
mjones73 said:
I just looked, his AOSP kernel is only for roms running 4.2.2 source under the cover, I'm pretty sure the latest Mahdi is running 4.4.2.
Furnace AOSP should work on Mahdi.
bender_007 has a tool you can install to tell you which panel you have, check his signature - http://forum.xda-developers.com/member.php?u=3279781
Click to expand...
Click to collapse
Okay I wasn't sure if v7 was perhaps the update to implement it for 4.4.2, I took it as that from reading the thread title but it does say only for 4.2.2 source. I will have to look into Furnace more, see how it compares to the kernel running in Mahdi. Thank you for the link and all the info!
TheFullSpectrum said:
Been trying to flash dr87's kernel to the Mahdi ROM (which has been a great ROM thus far), phone ends up getting stuck on LG symbol and starts getting the white lines, at which point I reboot into recovery and just re-flash the ROM. I've read other people have been able to flash it to this ROM with no issues. Wiped Dalvik before flashing. This is the VS98024A. Any thoughts? Heard the combination of this kernel and ROM was really good, would definitely like to try it out.
Click to expand...
Click to collapse
furnace 2.2.3 works perfect with mahdi. in fact its made to run on mahdi.
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/
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