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

Root [CDMA] Analysis Paralysis

T

tecbench

Lurker
After month of research still a few questions and files to find.
to TWRP or not to TWRP ? - big size difference compared to CWM.
cwm 6.0.5.1 or Philz 6.58.7 -adware in image every image I find my antivirus quarantined every time - this "adware in the app" ?
I understand about the bootloader dif from kit-Kat to lollipop (I'm on 4.4.4)
SuperSU or Other.

Not looking to "MOD" just "ROOT" for now.
I have unlocked bootloader.

My understanding:
flash recovery.
make backup - can stock recovery do this ? I found tutorial once on all functions, now can't find it.
use "mfastboot" not SDK one.
flash some kinda SU "app"

I will thank in advance,
 
Use TWRP.

Use only the TWRP that matches your model exactly. If you need help, ask. Don't experiment, don't not be sure. This is crucial.

Stock recovery can not make backups. It only installs digitally signed Motorola update files, nothing that you can use.

Don't use some fastboot, use ours, it's safe, effective, easy, and correct for Windows, Linux, or Mac.

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

Open a command window to \sdk-tools (assuming that you followed my guidelines), copy the TWRP img there, put your phone in FASTBOOT mode and install TWRP by saying (in the command window) -

fastboot flash recovery name-of-twrp-file.img

Definitely make a backup the instant you finish installing TWRP. Accept the defaults to backup boot, system, and data.

Don't install some sort of superuser - install SuperSU by getting the zip file to your storage while the phone is running normally and install from there later when you're back in TWRP again.

http://forum.xda-developers.com/showthread.php?t=1538053

Don't try for the Play Store install, it's not your desired option.

Check the md5 checksum of the zip file before flashing it. Our Mini-SDK gives you what you need.

Never flash an install file without checking the md5 checksum. If you'd rather check it on your phone, use "AFV File Verifier for Android™"

https://play.google.com/store/apps/details?id=sa.afvx

Ask questions.

Farting around with toolkits and vague guides by people who have done it once and voting in your mind which way to go is surefire way to convert your phone into a paperweight.

(Nothing wrong with CWM or Philz, use them if your specific model version has a problem with TWRP, or if choosing to install a rom requiring one of them. Size isn't the issue, whatever you choose is going to your recovery partition, fixed size at the factory.)

Hope this helps.
 
Thx EarlyMon,
I already have latest Droid SDK installed..and I thought Visual Studio took alot of space! I scaled back from installing everything to just repository, sources, support library, everything for API 19 minus wear. also platform and build tools for 21. the "mfastboot.exe" I have size=521 kb, the fastboot.exe from both the Mini SDK and Droid SDK file size=192 kb. I read on the Moto G forum here that the fastboot.exe that comes with the Droid SDK has some issues with installing some files and to use the "mfastboot.exe"-one from Motorola. On XDA I found a download for ver 4.42 -the521 kb size file. I have UPDATE-SuperSU-v2.46.zip from the thread link you posted.
My phone:
Boost Moto G XT1031 (first gen)
Droid ver 4.4.4
Kernel ver 3.4.42-g09ca493hudsoncm@ilclbld28 #1 Thu Aug 7 21:58:22 CDT 2014
SYS ver 210.12.57.falcon_cdma.Boost.en.US sprint
Build KXB21.14-L1.57
So now it seems all that left to find is TWRP for my phone. I was under impression that it was pretty close to universal. I also am aware of bootloader difference 'tween Kit-Kat and Lollipop.
I'll post how it go's
once again thanks
 
Last edited:
Droid is Verizon brand for primarily Motorola phones.

I can assume that you mean Android SDK? Yes, our Mini-SDK is a multi-platform extraction directly from the Android SDK.

Others with the Boost Moto G have used the Mini-SDK without issues but if you want to use the Motorola version, ok.

Sorry, I don't know how I missed that you're on the Boost version - my bad.

Review the sticky thread, here's a TWRP reported to work -

http://androidforums.com/threads/re...ostmobile-10-16-14.821423/page-6#post-6782944

Other links are there for the other recoveries.

It's essential to get the right custom recovery for your exact model - they aren't universal.
 
The official TWRP is for XT1032. It will work mostly, but it won't flash zips that are only for XT1031. It will tell you the phone is an XT1032 and the file is for XT1031. It will flash universal zips just fine though.
 
Yes, the official TWRP will work. I've used it on my XT1034. While in recovery and plugged into the computer, the computer reads my phone as XT1032, but no biggie. I haven't tried out the latest version of TWRP, but have used the 2.8.1.0 version and it worked just fine on Kit Kat.
 
Thank you guys!
The SDK fastboot gave me problems but the mini SDK from did the trick ! have latest TWRP installed and SuperSU. every root check tool says rooted. now to a little bigger things like getting tether to work. the options light up then error pops up. I'll bring this up in appropriate the thread. once again thanks for having all the right info in the right place with the right people.
 
tecbench said:
Thank you guys!
The SDK fastboot gave me problems but the mini SDK from did the trick ! have latest TWRP installed and SuperSU. every root check tool says rooted. now to a little bigger things like getting tether to work. the options light up then error pops up. I'll bring this up in appropriate the thread. once again thanks for having all the right info in the right place with the right people.
Click to expand...

To get tethering working, change the value of this build.prop line: ro.mot.tether_dun_required=1
from 1 to 0 and reboot and it should work.
 
The tethering on my GSM Moto G worked out of the box. I wonder why it's not on your CDMA version?
 
amarc78 said:
To get tethering working, change the value of this build.prop line: ro.mot.tether_dun_required=1
from 1 to 0 and reboot and it should work.
Click to expand...

yeah found that setting before I found the database entry. I at first thought that was only setting. now tether works for WIFI and Bluetooth. ..... happy camper today ! thanks once again guys and girls !
 
You must log in or register to reply here.
Back
Top Bottom