I have rooted every phone i've had and for some reason the MOTO X is confusing me! The phone is a bone stock developers Ed. 4.2.2 pre camera.
I am confused as to which jcase method to use or if there is another option.
I am guessing PwnMyMoto 1.4.3 verizon. but i'm not sure.
Any help would be fantastic.
Thanks,
J
ejason said:
I have rooted every phone i've had and for some reason the MOTO X is confusing me! The phone is a bone stock developers Ed. 4.2.2 pre camera.
I am confused as to which jcase method to use or if there is another option.
I am guessing PwnMyMoto 1.4.3 verizon. but i'm not sure.
Any help would be fantastic.
Thanks,
J
Click to expand...
Click to collapse
PwnMyMoto and jcase's methods are for locked bootloaders. You first need to unlock your bootloader. Then you need to decide if you want to take the OTA to 4.4 or not because once you upgrade to 4.2.2 post-camera, you can never downgrade to 4.2.2 pre-camera without bricking your device.
If you want to upgrade to 4.4, here are the instructions to unlock and gain root:
[STEP-BY-STEP INSTRUCTIONS] Unlocking and Rooting a Dev Ed Moto X Running Kit Kat
I have read of others who kept the 4.2.2 bootloader and other partitions and just selectively flashed those partitions they wanted as each new upgrade's sbf firmware was released. I don't know what advantages there are to doing that.
ejason said:
I have rooted every phone i've had and for some reason the MOTO X is confusing me! The phone is a bone stock developers Ed. 4.2.2 pre camera.
I am confused as to which jcase method to use or if there is another option.
I am guessing PwnMyMoto 1.4.3 verizon. but i'm not sure.
Any help would be fantastic.
Thanks,
J
Click to expand...
Click to collapse
It's a Developer Edition. Take all the updates available (4.2.2 camera update, 4.4 and now 4.4.2). Get the unlock code from Motorola and unlock your bootloader. Once that is done, flash twrp recovery and then install root via twrp.
Very simple on Dev Editions just because you can unlock the bootloader and flash an alternate recovery (twrp, cwm, etc..).
I agree. Unlock your bootloader (Doesn't void warranty on Developer Edition), flash TWRP recovery, then boot to TWRP and install/flash SuperSU. And it doesn't matter what ROM version you're running. (there is a TWRP for 4.2.2 and one for 4.4/4.4.2).
As mentioned, the bootloader included in the android versions can prevent you from downgrading the rom version. (i.e. bootloader in 4.4.2 prevents you from downgrading to any previous ROM). Why would you want to downgrade? If you have a locked bootloader, you'd want to downgrade to be able to use the root processes needed when you have a locked bootloader. But if you have an unlocked bootloader, because you can flash an alternate recovery (not possible with locked bootloader) and root no matter what ROM version you have installed, the only reason to downgrade would be if you encounter a bug you can't deal with that isn't present in the older roms.
because 4.4.2 fixes the exchange and bluetooth issues, and doesn't introduce anything new, its suggested you update to 4.4.2 if you have an unlocked boot loader (4.4.2 isn't rootable on locked bootloaders and may not be, so its recommended that those with locked bootloaders who want to root stick with 4.4).
KidJoe said:
I agree. Unlock your bootloader (Doesn't void warranty on Developer Edition), flash TWRP recovery, then boot to TWRP and install/flash SuperSU. And it doesn't matter what ROM version you're running. (there is a TWRP for 4.2.2 and one for 4.4/4.4.2).
I didn't know there was a different TWRP for 4.2.2.
As mentioned, the bootloader included in the android versions can prevent you from downgrading the rom version. (i.e. bootloader in 4.4.2 prevents you from downgrading to any previous ROM). Why would you want to downgrade? If you have a locked bootloader, you'd want to downgrade to be able to use the root processes needed when you have a locked bootloader. But if you have an unlocked bootloader, because you can flash an alternate recovery (not possible with locked bootloader) and root no matter what ROM version you have installed, the only reason to downgrade would be if you encounter a bug you can't deal with that isn't present in the older roms.
because 4.4.2 fixes the exchange and bluetooth issues, and doesn't introduce anything new, its suggested you update to 4.4.2 if you have an unlocked boot loader (4.4.2 isn't rootable on locked bootloaders and may not be, so its recommended that those with locked bootloaders who want to root stick with 4.4).
Click to expand...
Click to collapse
From what i have read 4.4.2 isn't rootable at all. Even if you have an unlocked bootloader. Is that correct?
Great info, thanks.
I thought that the Verizon DE already had an unlocked bootloader? Or is it like an HTC where i have to go the the MOTOROLA webite and get a code?
I did something like that for an HTC ONE i have on straight talk. I unlocked the bootloader from the HTC website, then installed TWRP, and then rooted and its running a 4.4.2 ROM that is great.
ejason said:
From what i have read 4.4.2 isn't rootable at all. Even if you have an unlocked bootloader. Is that correct?
Click to expand...
Click to collapse
Incorrect. You can do whatever you want with the DE, regardless of what version of Android you're on.
Sent from my Moto X
ejason said:
I thought that the Verizon DE already had an unlocked bootloader? Or is it like an HTC where i have to go the the MOTOROLA webite and get a code?
Click to expand...
Click to collapse
There are directions on a 1 page pamphlet that came with your VZW DE on how to unlock the bootloader.
Sent from my Dev Edition Moto X
ejason said:
I thought that the Verizon DE already had an unlocked bootloader? Or is it like an HTC where i have to go the the MOTOROLA webite and get a code?
Click to expand...
Click to collapse
It is all in that step-by-step link I gave you above.
Ok, so i have my phone unlocked, updated to 4.4 and for some reason i can not flash the TWRP.
I get the error (bootloader) variable not supported!
Any ideas.
I have tried both mfastboot and fastboot and i get nothing.
I also moved all files into another folder and CD into that folder and still the same error.
Can i install the TWRP with goo manager?
ejason said:
Ok, so i have my phone unlocked, updated to 4.4 and for some reason i can not flash the TWRP.
I get the error (bootloader) variable not supported!
Any ideas.
I have tried both mfastboot and fastboot and i get nothing.
I also moved all files into another folder and CD into that folder and still the same error.
Can i install the TWRP with goo manager?
Click to expand...
Click to collapse
did it finish flashing? mine says that when i flash a recovery also, but it flashes.
after you flash it dont reboot, just go into recovery (volume down to move the selection, volume up to execute)
then select reboot system, and it will ask if you want to root.
ejason said:
ok, so i have my phone unlocked, updated to 4.4 and for some reason i can not flash the twrp.
I get the error (bootloader) variable not supported!
Any ideas.
I have tried both mfastboot and fastboot and i get nothing.
I also moved all files into another folder and cd into that folder and still the same error.
Can i install the twrp with goo manager?
Click to expand...
Click to collapse
ok, thanks for everyones hellp. Done and done..
Hi all, I was wondering if it would be less of a hassle to keep my BL unlocked Moto X stock until Lollipop OTA comes out OR if it might actually be harder to install recovery, root, etc when 5.0 is on the phone? IIRC KK made some changes that caused hassles on rooting, recovery install for some phones. I have Dev Edition, thanks
Although lollipop is making it difficult to root, you would still be able to unlock your BL on lollipop. Since it appears you don't have a need to root right now, I would just wait until lollipop. The reason to wait is if you install a recovery or freeze apps, you won't be able to install OTA until you restore stock recovery etc.
As long as you have an unlocked / unlockable BL, you will always be able to install a custom recovery / root.
PsychoKilla666 said:
Hi all, I was wondering if it would be less of a hassle to keep my BL unlocked Moto X stock until Lollipop OTA comes out OR if it might actually be harder to install recovery, root, etc when 5.0 is on the phone? IIRC KK made some changes that caused hassles on rooting, recovery install for some phones. I have Dev Edition, thanks
Click to expand...
Click to collapse
it depends.
With an unlocked bootloader we should continue to be able to flash a custom recovery, and custom rom.
However, there are several unknowns right now, including when will we see Lollipop for the X? Which variant of the 2013 X (Dev vs ATT vs VZW vs Sprint, etc) will get it first? When will soak tests start? When will the carriers finally push it, etc?
Then we don't know how hard or easy it will be to root. At first a custom kernel was needed to root Lollipop, but now it seems Chainfire has found away around that http://www.androidpolice.com/2014/1...w-to-root-lollipop-without-a-modified-kernel/ Until we see L on a 2013 X, we wont know for sure.
In any case, its always less hassle to keep your phone STOCK if you want to take an OTA. The OTA's need stock recovery on the phone in order to install. Also, diverting from stock can mean changes which will cause the OTA's pre-flash validation checks to fail, and the OTA to not install.
US Cellular is STILL on 4.4.2 lol 5.0 seems a hundred miles away still. Glad I'm unlocked, rooted and stock (Xposed Gravitybox) best combo IMHO.
Hi All,
I have a XT1028 running Android 4.4.2. I unlocked the bootloader with Sunshine and temprooted it with pie, then backed up the phone with nandroid backup to a USB flash stick plugged into an OTG cable with both clockworkmod and TWRP backups.
Question for you all going forward. It seems to me that I have 3 future options here:
1) Run the phone on Android 4.4.2 permanently, and use my rooted apps on it with the pie temproot. I almost never turn off my phone (my job requires it to be on 24x7) This will allow me to take advantage of OTA updates in the future as I assume EVENTUALLY Verizon will release Android 5.x for the Moto G, and EVENTUALLY there will be a root for that which doesn't involve flashing a rom. It's easy enough to disable update notifications and the 4.4.4 OTA update is sitting on the phone right now waiting for the day I let it install. (which may be never)
2) Allow the phone to OTA update itself to Android 4.4.4, then flash SuperSU boot.
3) Say hell with it and flash a custom rom. However, all the instructions I've found out there seem to assume your flashing a custom rom from an SD card, which the Moto G XT1028 does not have. nor does the XT1028's fastboot seem to have the ability to flash from a backup, it seems it can only boot off the recovery partition. So I'm not entirely sure how to do this with an XT1028.
The problem with option 2 & 3 is they break OTA updates. And while there's lots of custom roms for XT1032 and so on - there's very little mention of anyone running them on an XT1028.
I unlocked the bootloder on this phone because I'm looking ahead to the future - Sunshine exists and works right now, there's no guarantee it will 2 years from now - and there's no guarantee that the community will ever find a vulnerability that will allow rooting Android 4.4.3 and later with a locked bootloader. Eventually I'll want to upgrade to 5.x and I may have to flash a custom rom to do it.
Suggestions, catcalls?
I heard lollipop drains battery fast so I tried stopping update midway now my stock kitakat is corrupt. Please advice how to install stock Kitkat in my motorola droid turbo xt1254.
Note my usb debbuging is off in phone settings and the device is not being recognised by RDS Lite even though i tried reinstalling motorola device manager. It says update is N/A.
Thanks in advance
Crunch7
At the very least, you have a lollipop recovery on the phone and will not accept KitKat reinstallation. It is likely that you bricked the phone, but not totally certain. Try putting the phone in fastboot for RSDlite. If you can't do that, you may be SOOL. Once you do get a stock ROM on, unlock the bootloader with 'Sunshine', then you can do about anything you want.
Sent from my XT1254 using Tapatalk
There's three versions of Verizon firmware that can be bootloader unlocked via Sunshine. Make sure you do NOT update to the very latest, which cannot be unlocked. Once bootloader is unlocked you can then downgrade back to Kitkat if you wish.
You can't downgrade bootloader, but with unlocked bootloader you can downgrade firmware. With a locked bootloader you can't downgrade anything.
Hi, I am currently using CM13 on Android M because I wanted Xposed. Recently, I have planned to switch to The Pure Nexus ROM for Android N, but I have been told something disheartening. I was told if I update my bootloader to Android N latest from Google, I will not be able to downgrade the bootloader because it can cause it to brick. Since my backups are for CM13, would I not be able to restore them through TWRP with the new Android N bootloader?
Bootloaders are backwards compatible. The 7 bootloader should work as far back as 5.1.1. You're right though, don't downgrade the bootloader.