• 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

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...
I downloaded the complete SDK and I'm in the platform-tools directory (in the terminal) with adb and fastboot but no "sh" or "sdk.sh" so there is "No such file or directory" when I try "sh sdk.sh". I've searched for it ("sdk.sh") but it's not there. I also tried it from the SDK->tools directory. Is that some kind of shell command?

I also tried "adb devices" and "fastboot devices" in the platform-tools directory but get "command not found." My moto g is hooked up via usb, it's in fastboot mode and it says "usb connected" so I don't know what the problem is. I had "usb debugging on" when the phone was working. Now I have no idea.

I really appreciate yours and amarc78's help. Just hope I can get it to work again. Thanks.
 
Last edited:
You can flash one recovery from another, I do it all the time. So, you tried selecting recovery on the phone in fastboot mode? It sounds like you don't have the adb drivers installed properly or something like that.
 
Macs don't have or need drivers.

Command not found means you don't have an executable adb or fastboot - or you don't have it in your path.

The sdk.sh is from the Mini-SDK, not what you have.

Instead of

adb devices

Try

./adb devices

Prefix your commands so they're -

./adb

And

./fastboot
 
amarc78 said:
You can flash one recovery from another, I do it all the time. So, you tried selecting recovery on the phone in fastboot mode? It sounds like you don't have the adb drivers installed properly or something like that.
Click to expand...
Yes, I tried selecting "recovery" in fastboot mode several times. It just hangs at the silly animation I loaded with bootbox.
 
EarlyMon said:
Macs don't have or need drivers.

Command not found means you don't have an executable adb or fastboot - or you don't have it in your path.

The sdk.sh is from the Mini-SDK, not what you have.

Instead of

adb devices

Try

./adb devices

Prefix your commands so they're -

./adb

And

./fastboot
Click to expand...
I know that I have to have the right path in the terminal window. I have the mini SDK and sdk.sh is not there. I tried "./sh sdk.sh"... same response. "./adb devices" ran but showed no devices BUT, I ran the fastboot get unlock data command and it returned the unlocking code (!!!) so I guess my Mac is seeing the device !!! Now what do I do?
 
If you got the sdk-tools.zip from my link then you got the Mini-SDK and sdk.sh is definitely in it. Your platform-tools installation indicates that you have the SDK.

Anyway - you have a working adb and fastboot and you know now to prefix the commands with "./" (except for sh commands but you won't be seeing any more of those) so that's all I can do here.
 
OK, I found sdk.sh. I was thinking of the "minimal SDK" not the "mini sdk." Anyway, I ran it and then "./fastboot flash recovery CWM.img" and it completed. On the phone, below the normal fastboot menu, it says...

Fastboot Reason: Volume down key pressed
USB connected
cmd: oem get_unlock_data
cmd: getvar:artition-type:recovery
cmd: getvar:max-download-size
cmd: download:0092b000
cmd: flash:recovery
Mismatched partition size (recovery)

So what I do now?

Edit: I tried rebooting in Recovery but the button/option doesn't work. I can scroll up/down but the up volume button doesn't work on Recovery.

Edit: It finally rebooted in Recovery with the up arrow but still hangs. Shite.
 
Last edited:
i just scanned this briefly, kid just needs to flash CWM or Philz via fastboot, boot into recovery, sideload SuperR's stuff, should be golden.
 
Seraph08 said:
i just scanned this briefly, kid just needs to flash CWM or Philz via fastboot, boot into recovery, sideload SuperR's stuff, should be golden.
Click to expand...
I appreciate the suggestions but I tried both cwm and philz and it just hangs at the boot animation when trying to boot into recovery.
 
You mean SuperR's? No, I haven't. Do you think it would work without the partition patch? You see, I was on 4.4.2 and his doesn't work without the patch. I've been trying to figure out how to run the patch.
 
Is there another recovery I should try before throwing in the towel? One that might work with the 4.4.2 partitions?

edit: never mind. flashed twrp. it worked.
 
Last edited:
So, I sideloaded the partition patch using Philz Touch 6 recovery I guess.

Then I wiped/cleaned to install a new ROM. I then tried both SuperR's full/rooted .zip and deoindexed .zip. The full one will not completely sideload to my moto g. It stops at 92%. I've tried it several times. Deoindexed sideloads and runs but when I reboot, I get the Moto animation and then a gray screen. So nothing.

I tried to push (copy) the full/rooted .zip to three different directories (clockworkmod, TWRP, Download) but when I navigate to them (in Philz recovery), there are no files !!!

I've also tried the Cyanogenmod 12 latest nightly and the latest 11 snapshot <-- that one really should work, shouldn't it? But they both just hang at the boot ani.

I've tried 4.4.2 and 4.4.4 .zips from the XDA forums.

I'm thinking that something is really missing. Duh.

Ordered a new Boost moto g from amazon ($65 free shipping). But if I can get this working I'll just return it.

Wish I could get root access to the adb shell. I can't cd to any directories other than tmp and stuff. If I could, maybe resurrect this baby...

./adb shell (<-mac)
# ls
bla
shite
bitch
tmp
clockworkmod
#cd clockworkmod
/sbin/sh: cd: can't cd to clockworkmod
#cd tmp
#tmp

su ./adb shell
password: [tried the usual stuff including leaving blank]
su: Sorry
 
Last edited:
I'm guessing your phone doesn't have enough internal storage for the files tour trying to push to it. Why don't you use a USB otg. Didn't you mention a Leaf bridge or something earlier. I always backup, restore and install new ROMs from my Leaf micro SD adapter. If you got a recovery on your phone you should not have this much trouble. What are you doing for wiping before you try flashing something?
 
bleak said:
./adb shell (<-mac)
# ls
bla
shite
bitch
tmp
clockworkmod
#cd clockworkmod
/sbin/sh: cd: can't cd to clockworkmod
#cd tmp
#tmp

su ./adb shell
password: [tried the usual stuff including leaving blank]
su: Sorry
Click to expand...

Recovery is in a partition that you can't just cd to.

su ./adb shell

That's not a command.

The command you're trying for - su - won't work because in order to access root, you need to be rooted.

Not sure what you want to do with a root shell.
 
amarc78 said:
What are you doing for wiping before you try flashing something?
Click to expand...
That's a good question and what got me into trouble in the first place. Because I don't know what I'm doing? Because I'm a clean freak with OCD?

I tried SuperR's full/rooted from a microSD and it failed. "symlink: some symlinks failed E: error in falcon_KXB21.14-L1.57_root.zip package."

The CM11 snapshot ran fine from the microSD like it did when sideloaded but it doesn't work for me. I'm going to try this XDA 4.4.4 for the Boost XT1031 from a microSD this time...

Edit: failed to startup. It was "starting applications" for about an hour so I had my hopes up. Only to be let down again. I'm trying [BoostMobile Only] Guide on returning to Stock now. Waiting for second download...
 
Last edited:
EarlyMon said:
Recovery is in a partition that you can't just cd to.

su ./adb shell

That's not a command.

The command you're trying for - su - won't work because in order to access root, you need to be rooted.

Not sure what you want to do with a root shell.
Click to expand...
I was just trying to install the "aroma" file manager into philz. It needs to be in clockworkmod/aroma/ and I can't create dir and put it there. It says "rooted" in philz so I don't understand. Is it because I don't have a fully operational OS? Anyway, I got sidetracked I guess.
 
Of I were you I would stick with PhilZ recovery, but don't mess around with the aroma file manager. It's kind of buggy and although it has gotten me out of a jam a time or two, it's not worth the trouble of using regularly. I'm going to explain how to wipe properly before flashing a ROM. When you first boot to recovery you will see wipe and format options. You want to select clean to install a new ROM. This will wipe system, cache, dalvik cache, and app data. This should be all you need to do then go to install zip from SD or USB depending on where your files are. You may have a bad download with the ROM you tried to flash and the CM ROM might not have worked because you didn't wipe everything properly. So don't throw in the towel just yet. You have a recovery on your phone and you can boot to it so this is a good thing. Just be very careful what you do from here or you will have a brick. The ROM from XDA you mentioned should work fine. I have tried them. I like the optimized stock best because its debloated and has busybox and some other optimizations which make it easier to customize more. The untouched stock is just like out of the box. Just make sure your files are downloaded properly and wipe properly and you should have no trouble flashing a ROM from USB. Good luck!
 
Well, I see you found possibly your last resort. Awesome. I think I can sleep now, LOL. Make sure to make a backup in PhilZ to a USB not internal SD immediately! And make sure it completes, and keep it somewhere safe. Now you know how to mess up your phone and fix it. Get some sleep now!
 
You must log in or register to reply here.
Back
Top Bottom