Stopped Android update from Kitkat to Lollipop now Android is No Command :( - Verizon Motorola Droid Turbo Q&A, Help & Troublesh

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.

Related

?? What do i use to ROOT Verizon DE stock.. I am confused..

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..

[Q] Locked bootloader, boot up failed.

Hey, guys.
I have a Moto X Brazil Retail version.
I unlocked the bootloader, but never installed a custom recovery or rom, I was just curious.
Today, I flashed kitkat 4.4.2 and everything was going fine until I received the notification to update to version to 4.4.3.
After installing the 4.4.3 update, the moto x would just boot up to the flashboot screen, with LOCKED bootloader T_T.
I can't hard reset using any means I know. Can you help me?
Thanks.
(I'm on a mac)
leocanela said:
Hey, guys.
I have a Moto X Brazil Retail version.
I unlocked the bootloader, but never installed a custom recovery or rom, I was just curious.
Today, I flashed kitkat 4.4.2 and everything was going fine until I received the notification to update to version to 4.4.3.
After installing the 4.4.3 update, the moto x would just boot up to the flashboot screen, with LOCKED bootloader T_T.
I can't hard reset using any means I know. Can you help me?
Thanks.
(I'm on a mac)
Click to expand...
Click to collapse
what do u mean that u have unlocked the bootloader and now u have bl locked??
from fastboot choose Factory once and then if u get another time fastmode choose another time Factory.
if doesn t work boot into recovery and wipe cache.
He obviously downgraded. He had to have been on 4.4.3 (or higher), unlocked, flashed a custom ROM, decided to go back to stock, and flashed 4.4.2. (downgrade)
That pretty much sum it up?
Everybody PLEASE READ the warnings that downgrade = brick....

Bricked, Unbricked, how to update?

So I was on 4.4.2 before and rooted and wanted to update and followed an old guide which led me to an old link to the toolkit. The result was downgrading to 4.2.2, OTAing, and then bricking. It took me awhile but somehow I flashed the 4.2.2 again and managed to unbrick myself. Now that I can access my phone again how do I update to the newest 4.4.4 without bricking again? I'm a bit afraid of doing anything at this point. Is it possible to just flash a custom rom to avoid it (I'm on developer edition)? Is it safe to RSDlite to 4.4.4 using the right carrier?
edit:
nevermind... I turned the phone off to check the status of the bootloader and saw it was unlocked, did a normal power up. For some reason it said android is updating even though I didn't do any updates and it randomly turned off and now it's completely dead .
Same problem
nvertigo said:
edit:
nevermind... I turned the phone off to check the status of the bootloader and saw it was unlocked, did a normal power up. For some reason it said android is updating even though I didn't do any updates and it randomly turned off and now it's completely dead .
Click to expand...
Click to collapse
My girlfriends phone has the same issue. It received an OTA update on Friday and kept havin problems running programs and rebooting. This morning it was off and when it booted, it couldn't get past the "unlocked bootloader" warning. I could get to the recovery menu but could not run TwRP because it froze at the splash.
I have tried installing a new recovery via faastboot but after it "installs" , it still appears to be the old recovery.
If you can boot the phone to FastbootAP/Bootloader, check the bootloader version on your phone, and get the corresponding SBF version or NEWER.
Example:
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
xx.xx = 4.4 <-- I forgot the bootloader version.
30.B4 = 4.4.2
30.B7 = 4.4.4
using an OLDER version SBF will fail at GPT.BIN and Motoboot.img, or will brick your phone!!!
Flash the SBF by following option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html
Doing this (flashing the latest SBF for your phone/bootloader) should bring everything on your phone back in line, making it safe to take future OTA's

XT1053 with Verizon software after 5.1 OTA: do you know how to solve?

Hi all, I need help.
I have an XT1053 developer edition, gsm. In the past I've unlocked bootloader just to use Xposed on Kitkat, I've never flashed custom roms. Only once an XT1052 stock rom to have italian as language, but since it had a bad radio behaviour I went back to XT1053 stock rom. I've had root but not for long. I have tried also to re-lock the bootloader, but I was never successful since (FAIL: Please run fastboot oem lock begin first!)
With the 5.1 OTA, now I have the right build but with VZW written at the end. In the boot animation, I have the Verizon logo. Thanks to Mark of Motorola Forum Manager, I've had the stock XT1053 5.1 DE software to flash through fastboot, but even if the procedure is successful I cannot get rid of the VERIZON thing. I would like to use RSD Lite but I can't since it doesn't recognize the phone as connected, even if Motorola Device Manager does recognize it and the drivers are installed.
How can I do? Is there a way to really clean completely the phone and install the right software more "deeply"?
Any help will be much appreciate.
Thanks,
Luca

OTA Updates After Unlocking Bootloader on xt1058?

I have an xt1058 which is running Android 4.4.0 build 140.44.5.ghost_att.ATT.en.US. I've downloaded and installed Sunshine and am planning to unlock the bootloader as all tests passed without issue. What I am wondering is, after I do this can I take any OTA updates or will this cause me to lose the bootloader unlock?
Of particular concern is incompatibility between older versions of the bootloader and ROMs based on newer Android versions. I ran into this with my Atrix HD which also had an unlocked bootloader. The bootloader on that device was based on Android 4.3 Jellybean. I could not flash any ROMs for MSM8960 devices which used newer bootloaders, for example I always needed to use CM versions with Jellybean bootloader.
Will I have similar issues with my Moto X once the bootloader is unlocked?
Thanks!
No issues, flash latest XT1058 AT&T ROM, and you are in safety. Once unlocked, bootloader can't be locked by any app, but your hands. And there will be no more OTA for this phone.
Btw, you can use Safestrap (for free) on Android 4.4, it will give you possibility to use any stock ROM up to 4.4.4. If you need CM, or 5.1 stock, then yes, Sunshine only.
Just to be clear, I have now successfully unlocked my bootloader using Sunshine (I see the "warning bootloader unlocked" splash at boot up, and have also booted into bootloader and I see "device is UNLOCKED".
I am currently on build 140.44.5.ghost_att.ATT.en.US which is Android 4.4.
Ultimately what I want to do is get rooted but be running stock 5.1. I don't want to go to a custom ROM right now, but don't want to do anything that would prevent me from doing that later. That's why I unlocked the bootloader now.
I am planning to use this process to root the phone:
https://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738
Once this is done, what is the easiest way to move to stock Android 5.1 but not lose root and bootloader unlock/s-off ?
My advice would be - don't update to 5.1 official, it's very very buggy and you'll want to get rid of it very fast.
The best you can do for this phone atm, if you want anything above 4.4 is to go for Mokee 6. It's nearly perfect MM.

Categories

Resources