Database Develop

Help upgrading to 4.2.2 from 4.0.4

Hello,
I upgraded to an ICS version 4.0.4 awhile ago through this website and it was a pretty painless process. Though recently I've been wanting a new phone, but looked into Bionic's software development and I see that I might be able to hold off if I can install 4.2.2 which seems to improve the phone a lot. Currently i am on system version 6.7.232.xt875, android version 4.0.4, build number 6.7.2-223_dbn_m4-9. I've tried installing safestrap 3.11 to start the process of installing CM 10.1 but it crashes every time I try to run it. Can someone please provide me with a starting path towards upgrading my firmware.
Thank You

oldboy26 said:
Hello,
I upgraded to an ICS version 4.0.4 awhile ago through this website and it was a pretty painless process. Though recently I've been wanting a new phone, but looked into Bionic's software development and I see that I might be able to hold off if I can install 4.2.2 which seems to improve the phone a lot. Currently i am on system version 6.7.232.xt875, android version 4.0.4, build number 6.7.2-223_dbn_m4-9. I've tried installing safestrap 3.11 to start the process of installing CM 10.1 but it crashes every time I try to run it. Can someone please provide me with a starting path towards upgrading my firmware.
Thank You
Click to expand...
Click to collapse
You need to take the stock OTA (4.1) to get CM to run.

[Q] Help with JB OTA and JB ROM

I'm currently running latest Eclipse ICS ROM with SS v3.11. Just started getting "com.process.google.gapps has stopped" and "Google Play services have stopped" error messages nonstop, constant. Tried a couple recommended fixes, didn't work. Had been fine with Eclipse ROM up to this point but decided it's time to upgrade to JB.
So...
Booted in stock ROM slot via SS. Downloaded the OTA update, tried installing 3 different times. Upon reboot, all three times said the update failed.
First question: I assume I need the JB OTA update prior to flashing a JB ROM, correct? If so, any reason why the update is failing to install? Will I have to do anything with root and SS prior to and/or after OTA update?
Second question: Once I get the OTA to install, which Bionic JB ROM has proven most stable? I want few frills, fast, simple, clean. Any recommendations?
Really appreciate any help and advice, thanks as always all!

If anyone's curious, figured it out. Uninstalled recovery in stock rom, saved root with voodoo, installed 4.1.2 OTA manually.

[Q] SYSTEM UI issues; How come I cannot install any "ghost" rom?

PRIMARY QUESTION: I cannot seem to install any "ghost" KitKat or Lollipop ROM on my XT1058. Can anyone please help shed some light on this? I've spent around a combined 12+ hours searching, researching, and tinkering trying to figure this out, but no success. I typically receive a "com.android.systemui" error message or "Unfortunately, System UI has stopped" message. After I acknowledge the message, it pops up again in a second or two. I have to force a shutdown of the phone and recover via TWRP. I've detailed my history and attempts below.
On the CM website, it says something about how "ghost" is a unified OS for every Moto X, except AT&T, since it's not unlockable. With Sunshine, shouldn't I be able to install the "ghost" ROM? Or does it not matter? I hope this isn't a case of, "even though you have an unlocked bootloader, the 'ghost' ROM isn't intended for your version of the phone." If that's true, it looks like all development on the XT1058 has pretty much stopped.
Many thanks, XDA Community, for helping me understand all this!
Secondary Questions:
I recently tried using the feature, "fixing permission" in TWRP thinking it might help with the "ghost" installations. I started getting bootloops when trying to restore to previous ROMs. The only restore that worked was my true original stock backup; the other restore attempts on SlimKat and other stock instances failed. That worries me. While I have successfully restored my phone, does anyone know if I may have screwed up my phone for the long-term?
(Answered by KidJoe; thank you!) Since I unlocked my bootloader at 4.2.2, can I freely upgrade and downgrade stock OSs? i.e., Can I install AT&T's stock 4.4.4 and then downgrade to 4.4.2?
(Answered by KidJoe; thank you!) Why do so many people seem to care to downgrade their stock OS? While I'm sure some may not be happy with some changes that come with upgrades, what could possibly be so "upsetting" that people need to downgrade?
HISTORY
Phone: AT&T Moto X XT1058, non-developer edition
Android: 4.2.2 | No attempt has been made to upgrade the OS beyond 4.2.2
Used Sunshine to unlock the bootloader while still on 4.2.2
Recovery: Installed TWRP v2.8.1.0, and I use TWRP to backup and install old and new ROMs (I think it's version 2.8.3... I never downloaded a version 2.8.1, but that's what the screen says. I'm wondering if the authors just forgot to update the version number in the program.)
Successful ROM installs:
SlimKat build 7 Official, msm8960dt
Cyanogenmod 11 Snapshot M5 msm8960dt (2014-04-05)
Failed ROM installs:
Cyanogenmod 11 Snapshot M12 ghost (2014-11-15)
Cyanogenmod 11 Nightly ghost (2014-12-19)
LiquidSmooth KitKat v3.2 Nightly ghost (2014-10-31)
LiquidSmooth Lollipop v4.0 Nightly ghost (2014-12-20)
Other Notes:
GApps were always installed when available. I also tried not installing them.

cxwong1 said:
Many thanks, XDA Community, for helping me understand all this!
Secondary Questions:
Since I unlocked my bootloader at 4.2.2, can I freely upgrade and downgrade stock OSs? i.e., Can I install AT&T's stock 4.4.4 and then downgrade to 4.4.2?
Why do so many people seem to care to downgrade their stock OS? While I'm sure some may not be happy with some changes that come with upgrades, what could possibly be so "upsetting" that people need to downgrade?
Click to expand...
Click to collapse
I will answer these two....
1. NO you can not. Once you have 4.4.2, 4.4.3 or 4.4.4 on your phone, do NOT attempt to downgrade, even if you have an unlocked bootloader... For more details see what I typed here -> http://forum.xda-developers.com/moto-x/general/4-4-4-downgrade-possibility-t2971847/post57563419 along with the other discussions in that SHORT thread.
2. The older root and write protection disable processes for a Moto X with a locked bootloader (like ATT and Verizon) rely on taking advantage of vulnerabilities in the 4.2.2 w/Camera update rom version, or the 4.4 rom. These processes walk you through downgrading your ROM to 4.2.2 w/Camera update and following a set of steps to upgrade which will keep root and disable write protection. NOTE: It was safe to downgrade from 4.4. to 4.2.2 w/Camera update when following the SlapMyMoto/MotoWpNoMo processes. But that was the only time it was safe!!!!

KidJoe, thank you much!
Does anyone else have any idea about my "systemui" issue?

cxwong1 said:
KidJoe, thank you much!
Does anyone else have any idea about my "systemui" issue?
Click to expand...
Click to collapse
Just got a Moto X 1st gen replacement from Motorola and getting same problem after unlocking/rooting. Have you found a fix for this? Or does anyone know how to fix? Spent all day working on this and its driving me nuts.

syckman said:
Just got a Moto X 1st gen replacement from Motorola and getting same problem after unlocking/rooting. Have you found a fix for this? Or does anyone know how to fix? Spent all day working on this and its driving me nuts.
Click to expand...
Click to collapse
Hey! Nope, I haven't found the answer, unfortunately. I haven't really tried to upgrade my OS since.

cxwong1 said:
PRIMARY QUESTION: I cannot seem to install any "ghost" KitKat or Lollipop ROM on my XT1058. Can anyone please help shed some light on this?
Click to expand...
Click to collapse
I bit the bullet yesterday and paid for the Sunshine bootloader unlock. After replacing the stock bootloader with TWRP and making a backup, I started looking into putting CyanogenMod onto it, as I had just updated a Galaxy Tab 2 7.0 to KitKat (via CyanogenMod 11) last week and it wasn't right that my phone had an older Android build than my tablet. I ran into conflicting information here and elsewhere, but the bottom line:
I have CyanogenMod 11 running on my AT&T Moto X.
More specifically, it's this zipball (remove spaces in next line to bypass the forum's lame link blocking):
https :// download.cyanogenmod.org / get / jenkins / 90775 / cm-11-20141115-SNAPSHOT-M12-ghost.zip
I also tried the latest 12.1 nightly, but while it appears to boot up, it reboots almost as soon as you try to set it up.
One thing that seems to help: before loading any ROM (whether stock, CyanogenMod, or whatever), wipe the flash. I have the ROM and Google Apps files on a flashstick that gets connected through an OTG cable, so I just tell TWRP to wipe everything but OTG storage, restore the ROM, let it boot up, then go back to TWRP to install the Google apps.
(Good thing I had the stock ROM backed up...had to revert to it this morning to back up aCar and Stocard data so I could bring them into CM.)
Starting configuration for my phone: AT&T XT1058, stock 4.4 firmware, rooted with the usual means for doing so, bootloader locked until Sunshine worked its magic.

AOSP ROM Questions (XT1072)

Hello All,
I've just flashed the AOSP ROM for THEA XT1072 and I'm very happy with the results, it's exactly the return to stock I was looking for. However, I have a few questions I hope somebody can kindly answer:
1) Is it possible to re-lock the bootloader once an unofficial ROM has been installed? My device is telling me I need an officially signed ROM and refusing to relock when I do "mfastboot oem lock".
2) What's the update process for installing later builds of the AOSP ROM? Is it just a case of checking back here and re-flashing the whole new image as and when it is released? Or is there an OTA update alternative?
3) Is the current AOSP build 20150828 inclusive of the various security fixes that Google rolled out recently (Stagefright etc.)? I know they were released to AOSP source code but that presumably doesn't guarantee they are in the current THEA 20150828 AOSP build yet.
Thanks
sharkyblunt

sharkyblunt said:
Hello All,
I've just flashed the AOSP ROM for THEA XT1072 and I'm very happy with the results, it's exactly the return to stock I was looking for. However, I have a few questions I hope somebody can kindly answer:
1) Is it possible to re-lock the bootloader once an unofficial ROM has been installed? My device is telling me I need an officially signed ROM and refusing to relock when I do "mfastboot oem lock".
2) What's the update process for installing later builds of the AOSP ROM? Is it just a case of checking back here and re-flashing the whole new image as and when it is released? Or is there an OTA update alternative?
3) Is the current AOSP build 20150828 inclusive of the various security fixes that Google rolled out recently (Stagefright etc.)? I know they were released to AOSP source code but that presumably doesn't guarantee they are in the current THEA 20150828 AOSP build yet.
Thanks
sharkyblunt
Click to expand...
Click to collapse
1. No.
2. Just flash rom without any wipes as there's no OTA functionality.
3. Yes.

Thanks Luk. Great work on this ROM. It flies compared to the stock 5.0.2 and no issues yet.

Only one issue so far, after 24 hours of using it. I'm getting a battery drain whereby Miscellaneous is by far the biggest culprit (currently at 22% since taking it off charge this morning). It was the same yesterday too, and I rebooted it last night just in case it was a hangover from the original flashing, but it's still draining faster than stock 5.0.2 did.

The AOSP-5.1.1-20150905 build is perfect (once I'd erased the modemst1 & modemst2 to get GPS working). No issues whatsoever from me. Great work.
By the way, I'm commenting here as I've not done enough posts to participate in the developers sub-forum.

OnePlus 3T Update or flash a ROM?

Hi! So, for now I'm running OOS 3.5.4 because I hated the 4.0.1 (I downgraded from it). So, now I don't know if updating to 4.1.1 or getting a ROM. I heard a lot of discordant opinions about the new update of OOS and myself didn't like the first nougat update. If I'll flash ROM, what should I flash(without bugs and with a good camera quality, because seems that all the roms have ****ty camera quality)?

Just my take: Asking for advice about the 4.1.1 update vs. custom ROM (and for that matter which custom ROM) is a matter of personal preference. As you've said yourself, opinions on the update are discordant (as will be true for any update). Just because someone gives your a particular response one way or the other, doesn't mean it will be the right answer for you. The only way to conclusively answer the question for yourself, is to try out the update and/or ROMs.
I would generally recommend updating firmware/modem in any case, whether you decide on the official update or a custom ROM. So it may make sense just to do the update (which will also update firmware and modem) then see if you like it. If not, try a custom ROM.
Alternately, even if you opt to go right to a custom ROM (after unlocking bootloader and flashing TWRP), I'd suggest at least flashing one of the updated firmware/modem zips posted in the 3T Guides, News & Discussion section.

redpoint73 said:
Just my take: Asking for advice about the 4.1.1 update vs. custom ROM (and for that matter which custom ROM) is a matter of personal preference. As you've said yourself, opinions on the update are discordant (as will be true for any update). Just because someone gives your a particular response one way or the other, doesn't mean it will be the right answer for you. The only way to conclusively answer the question for yourself, is to try out the update and/or ROMs.
I would generally recommend updating firmware/modem in any case, whether you decide on the official update or a custom ROM. So it may make sense just to do the update (which will also update firmware and modem) then see if you like it. If not, try a custom ROM.
Alternately, even if you opt to go right to a custom ROM (after unlocking bootloader and flashing TWRP), I'd suggest at least flashing one of the updated firmware/modem zips posted in the 3T Guides, News & Discussion section.
Click to expand...
Click to collapse
Thank you. I will probably update then, and if I won't like it I'll go to a custom ROM. Could you suggest me any good/stable ROM out there (especially without bugs and with a good camera quality)? Thanks

_HaZaRD_ said:
Could you suggest me any good/stable ROM out there (especially without bugs and with a good camera quality)?
Click to expand...
Click to collapse
As I already mentioned, what I said about update vs. custom ROM, will also apply to asking for recommendations about a particular custom ROM. It depends on your personal needs and preferences. You have to make the decision yourself.
Further, I'm still on stock 7.1.1, rooted; and haven't tried any custom ROMs on this device yet. So I have no custom ROM recommendations.

redpoint73 said:
As I already mentioned, what I said about update vs. custom ROM, will also apply to asking for recommendations about a particular custom ROM. It depends on your personal needs and preferences. You have to make the decision yourself.
Further, I'm still on stock 7.1.1, rooted; and haven't tried any custom ROMs on this device yet. So I have no custom ROM recommendations.
Click to expand...
Click to collapse
Ok

I updated from 4.0.3 to beta 4 via local, but now I want to go back because of the battery drain problem. I tried several times via adb sideload to flash the zip but I keep getting the same error <cannot read 4.0.4.zip> over and over again. Even after installing the drivers, I got a little yellow exclamation triangle near the driver in device manager. Honestly I'm starting to give up, I think I wiped my phone more than 5 times in order to flash via sideload, only to get the same error continuously. as far as I know, I cannot go back to 4.0.3 via local from beta 4 right?
Please help...