• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [CDMA] won't update to 4.4.4

bleak

bleak

Member
I get an "error" message after downloading and rebooting. That's all it says; "error." It simply will not update from 4.4.2. It's rooted but no customized ROM's yet. It has about 1.5 gb free space.

At the very least, could someone tell me how to disable the update screen? The one that says "I'm In" and "Maybe Later." It's driving me crazy.
 
If you tell me which flavor you are using (CDMA or International) I will move your question to the appropriate sub-forum where your root-ed phone is discussed.

... Thom
 
You say its rooted. Did you remove or freeze any apps? Also is it the stock recovery or did you install a custom recovery such as clockwork philz or twrp. It won't update if it doesn't have the stock recovery or if some system apps have been removed.
 
timmyh318 said:
You say its rooted. Did you remove or freeze any apps? Also is it the stock recovery or did you install a custom recovery such as clockwork philz or twrp. It won't update if it doesn't have the stock recovery or if some system apps have been removed.
Click to expand...
By "stock recovery" do you mean a backup app? I've been using "Backup Your Mobile." I did delete some google apps though. I don't care if I ever update to 4.4.4; I just want to stop the nag screens. Is there a way to do that? I've been putting off switching to a custom ROM but if that's what it takes, I'll do it. Thanks.
 
Moved.

The problems reported with a root-ed device are almost always because of a change that the user made that introduced a problem, because the "wall" was not there to protect them.

As was already pointed out ... very likely in your case that one or more modules were deleted that must be there for the update to work. The update is a gigantic patch file and if it has a patch for some preinstalled app that was deleted (perhaps by mistake) then the update will fail.

... Thom
 
bleak said:
By "stock recovery" do you mean a backup app? I've been using "Backup Your Mobile." I did delete some google apps though. I don't care if I ever update to 4.4.4; I just want to stop the nag screens. Is there a way to do that? I've been putting off switching to a custom ROM but if that's what it takes, I'll do it. Thanks.
Click to expand...
No a third party recovery is what you use to flash new roms,zip files etc etc on the moto g to root it I believe you have to use a custom recovery to flash the root file so odds are you have a custom recovery and that would be why it don't update. To stop the notification I believe you can use an app such as titanium backup and just freeze the ota app or system update app. That should stop it from looking to see if an update is available.
 
Go here http://androidforums.com/threads/ro...-deodexed-and-unmodified-boost-mobile.837664/
And read, and read and read, and you should solve your problem. You need to flash the partition updater, then whichever 4.4.4 stock ROM you wish. Just read so you don't get yourself in a bad spot like some others have!
Edit: wait a minute, do you have Boost Mobile XT1031 or Verizon XT1028. The link I posted is for Boost only if you have XT1028 I can direct you elsewere. Keep in mind the thread was started with 4.4.2 roms and OP was changed to 4.4.4.
 
Last edited by a moderator:
I read. I watched videos. I reread. I rewatched videos. I f'd up my phone with TWRP. It won't boot; only "missing component motorola.xxx" over and over. Right now, it's in recovery mode. I have a Titanium backup located on a microSD card using the leaf adapter. What should I do? I can't afford another phone. PLEASE HELP. :(:)
 
bleak said:
I read. I watched videos. I reread. I rewatched videos. I f'd up my phone with TWRP. It won't boot; only "missing component motorola.xxx" over and over. Right now, it's in recovery mode. I have a Titanium backup located on a microSD card using the leaf adapter. What should I do? I can't afford another phone. PLEASE HELP. :(:)
Click to expand...
What exactly is going on with your phone? Do you have any backup from a recovery?
Edit: what exactly is it saying when you try to boot, and what exactly did you do to get in this state?
 
At first, it powered up to the home screen but with constant error messages. Then it downloaded Boost packages. But I can't reboot to the home screen now. It just hangs on the opening animation. I don't have a backup from a recovery. I used superboot to root it. Right now, it's in Fastboot flash mode. I tried selecting Factory but that did nothing.
 
Can I use a third party recovery like CWM? Only thing is, I'm on a Mac so I can't use a .bat file. Jeesuz.
 
bleak said:
At first, it powered up to the home screen but with constant error messages. Then it downloaded Boost packages. But I can't reboot to the home screen now. It just hangs on the opening animation. I don't have a backup from a recovery. I used superboot to root it. Right now, it's in Fastboot flash mode. I tried selecting Factory but that did nothing.
Click to expand...
Did you do anything other than use superboot? What did you do to think you screwed something up with TWRP?
 
bleak said:
Can I use a third party recovery like CWM? Only thing is, I'm on a Mac so I can't use a .bat file. Jeesuz.
Click to expand...
I would recommend PhilZ recovery or CWM. TWRP is best for XT1032. You can flash a zip if you can get into TWRP.
 
I selected Recovery from the fastboot menu and it rebooted back to TWRP. So I mounted the phones' directory on my Mac desktop. If that helps. I know I'm stupid; I just need to get my phone back to some kind of working usage.
 
I'm sorry, but it does not help. I'm not sure how mounting your phones directory on your PC would mess anything up, unless you did something else. I'm sorry for all the questions, but I can't help if I don't know exactly what you did. I would say if you can get your phone into recovery, download and install the latest PhilZ or CWM. Next I would download one of SuperR's stock ROMs, either rooted or deodexed, and flash it in recovery. If you were on 4.4.2 firmware, make sure you download and flash the partition updater zip first! This should get you to working 4.4.4 stock.
Edit: while your at it, download the latest stable SuperSu 2.45 zip too to make sure you don't lose root.
 
Messages out of order. Mounting phone directory on Mac didn't hurt anything. I don't really remember EXACTLY what I did in TWRP; only remember trying to backup in it (failed) and... something else

So I copied the CWM image into the TWRP directory and used it to flash the recovery partition. It was "successful" but I can't boot up. Should I have used the root partition?

I'd rather use SuperR's stuff but I have NO IDEA how to use the falcon KXB21.14-L1.57 partition updater first. It's downloaded but what commands do I use? Can you help me with that? Thanks.
 
You need to get the phone into recovery. If the zip is on you leaf, select install zip from USB disk, find the zip and select install. Next do the same with the ROM zip and SuperSu. How exactly did you install CWM? Are you using superboot? I don't know much about that, I read some on it some time ago, but never used it.
 
Have you tried holding power and volume up at the same time to boot into bootloader?
 
I installed CWM by copying it to the TWRP directory on my phone through the Mac's desktop. Then I found the .img file in TWRP and ran it. But I selected the recovery partition; not the boot partition, so now I no longer have TWRP !!!

The power + volume up does nothing except reboot unless I'm doing it wrong.
 
I am confused. You need to make sure you have the volume button pressed all the way or it will just reboot. Have you done this before, and it stopped working now. I have had mine just reboot from not pressing the button all the way a lot, that's why I say this. If it really doesn't work, you must have lost your recovery somehow. I'm not familiar with Mac computers, but what program are you using to put the recovery on your phone?
 
Yeah, I lost the recovery partition somehow.

To put CWM on my phone, I used TWRP (plus the android SDK of course) to mount it on my desktop and just copied the file, but now that TWRP is hosed, I can use the Android File Transfer app. Does the partition .zip have to be run or just put on the phone somewhere? How can I run it? Is it possible to get TWRP back through a terminal window? Is it possible to resurrect my phone through a terminal?
 
If you have adb and fastboot you can name the CWM.img recovery.img if it already isn't and run fastboot flash recovery recovery.img , but to do this you need to get your phone into fastboot by holding down power and volume up. If you didn't mess up the partitions anyway. I'm not sure what your talking about with the SDK and all that. I haven't used the SDK much, and not for anything like this. The partition zip needs to be flashed with CWM.
 
Follow the directions here to get adb and fastboot for your Mac.

http://androidforums.com/threads/adb-guide-updated-2014-11-11.443072/#post-5389081

After you unzip the Mini-SDK and place the sdk-tools folder as instructed, you get a Terminal Window by Finder, Applications, Utility folder, Terminal Window. Double click it.

Open Finder to sdk-tools folder that you unzipped. Do not select any files.

Go to the Terminal and type -

cd

Tap space.

Go to the Finder and drag the sdk-tools folder to the Terminal. Put cursor in Terminal and press return. Then in Terminal, do -

sh sdk.sh

Get the CWM.img file, copy to the sdk-tools folder.

When ready - and I'm only advising on Mac fastboot and adb, nothing else - your command will be -

./fastboot flash recovery CWM.img

If the last term for the file name changes according to the other good advice your getting, follow that.

Hope this helps.


That's if the SDK you have now is giving you trouble.

Android File Transfer on a Mac is just for moving files around.

You can't flash one recovery from another - you have to fastboot flash it.
 
Last edited:
EarlyMon said:
Follow the directions here to get adb and fastboot for your Mac.

http://androidforums.com/threads/adb-guide-updated-2014-11-11.443072/#post-5389081

After you unzip the Mini-SDK and place the sdk-tools folder as instructed, you get a Terminal Window by Finder, Applications, Utility folder, Terminal Window. Double click it.

Open Finder to sdk-tools folder that you unzipped. Do not select any files.

Go to the Terminal and type -

cd

Tap space.

Go to the Finder and drag the sdk-tools folder to the Terminal. Put cursor in Terminal and press return. Then in Terminal, do -

sh sdk.sh

Get the CWM.img file, copy to the sdk-tools folder.

When ready - and I'm only advising on Mac fastboot and adb, nothing else - your command will be -

./fastboot flash recovery CWM.img

If the last term for the file name changes according to the other good advice your getting, follow that.

Hope this helps.


That's if the SDK you have now is giving you trouble.

Android File Transfer on a Mac is just for moving files around.

You can't flash one recovery from another - you have to fastboot flash it.
Click to expand...
Thank you, I was hoping someone would jump in here! I really wanted to help but haven't used a Mac in quite some time.
 
You must log in or register to reply here.
Back
Top Bottom