I know on T-mobile you can flash a Verizon ROM, but is it possible with Safestrap ?
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..
I have a Moto x XT1052 (European version).
I unlocked the bootloader, installed the twrp (with mfastboot) and gained the root access from the recovery.
But when I try to flash a new ROM (I tried the PA and the CM) I receive an error:
`This package is for "xt1030, obakem_verizon, xt1053, ghost_retail, xt1055 ecc..." devices; this is a " " `
As you can see is like if the twrp can't get the model of my phone.
Even with the phil cwm I get the same error (error 7).
So I tried to unzip the rom and remove the check of the supported devices but it failed again.
I re-installed the stock retail EU 4.4.2 ROM from http://sbf.droid-developers.org/ but I have always the same problem.
I can't understand why this happen.
AASonyKK said:
I have a Moto x XT1052 (European version).
I unlocked the bootloader, installed the twrp (with mfastboot) and gained the root access from the recovery.
But when I try to flash a new ROM (I tried the PA and the CM) I receive an error:
`This package is for "xt1030, obakem_verizon, xt1053, ghost_retail, xt1055 ecc..." devices; this is a " " `
As you can see is like if the twrp can't get the model of my phone.
Even with the phil cwm I get the same error (error 7).
So I tried to unzip the rom and remove the check of the supported devices but it failed again.
I re-installed the stock retail EU 4.4.2 ROM from http://sbf.droid-developers.org/ but I have always the same problem.
I can't understand why this happen.
Click to expand...
Click to collapse
The problem is that you are trying to flash Roms that aren't compatible with your device. None of those Roms are for the xt1052. The xt1052 has very few custom Roms available.
Completely normal.
samwathegreat said:
The problem is that you are trying to flash Roms that aren't compatible with your device. None of those Roms are for the xt1052. The xt1052 has very few custom Roms available.
Completely normal.
Click to expand...
Click to collapse
Yes this is exactly the problem.
But I re compressed the rom in a wrong way. I retried deleting the check and the CM is stuck in the boot animation but the PA works
For the xt1052 users: for get the PA to work you need to edit the file "updater-script" located in META_INF > COM > GOOGLE > ANDROID removing the text from assert till the semicolon.
Hello!
I've done some reading and having not gotten a satisfactory answer I thought I'd throw my question out to the community.
I'm currently running Twisted Lollipop v7.
I can Odin back to stock 4.4.2 whenever and redo towelroot and install safestrap etc.
I've been unsuccessful at flashing an AOSP rom and wanted to confirm once and for all if it is truly impossible to flash Blisspop or Cyanogenmod or Sonic or any of those I enjoyed on my trusty old S3 onto my unlocked At&T S5 Active.
If it is not possible I will get rid of this unlocked AT&T S5 active and get a used what? The T-mobile variant? The international variant? I just want to be able to flash whatever the hell I want without too much hassle! I do like the phone other than that though!
Looking forward to any advice!
Thanks!
Edbogue
edbogue said:
Hello!
I've done some reading and having not gotten a satisfactory answer I thought I'd throw my question out to the community.
I'm currently running Twisted Lollipop v7.
I can Odin back to stock 4.4.2 whenever and redo towelroot and install safestrap etc.
I've been unsuccessful at flashing an AOSP rom and wanted to confirm once and for all if it is truly impossible to flash Blisspop or Cyanogenmod or Sonic or any of those I enjoyed on my trusty old S3 onto my unlocked At&T S5 Active.
If it is not possible I will get rid of this unlocked AT&T S5 active and get a used what? The T-mobile variant? The international variant? I just want to be able to flash whatever the hell I want without too much hassle! I do like the phone other than that though!
Looking forward to any advice!
Thanks!
Edbogue
Click to expand...
Click to collapse
No you can not flash any AOSP roms on a device that runs safestrap, the bootloader isnt unlocked so you cant install a custom recovery the closest thing to a recovery is safestrap, and with a locked bootloader you can not install kernels which is why you cant install AOSP based roms.
mcmellens said:
No you can not flash any AOSP roms on a device that runs safestrap, the bootloader isnt unlocked so you cant install a custom recovery the closest thing to a recovery is safestrap, and with a locked bootloader you can not install kernels which is why you cant install AOSP based roms.
Click to expand...
Click to collapse
Thank you for your response!
Blues! It's what I suspected. I intend to offload this phone as a result and get another. Which variant would you recommend I get so I can flash happily and not worry about a locked bootloader? The SM-G900F, or what else would you recommend?
Thanks for your help!
Edbogue
edbogue said:
Thank you for your response!
Blues! It's what I suspected. I intend to offload this phone as a result and get another. Which variant would you recommend I get so I can flash happily and not worry about a locked bootloader? The SM-G900F, or what else would you recommend?
Thanks for your help!
Edbogue
Click to expand...
Click to collapse
Any phone that has a carrier would be locked for the most part, i know sprint and maybe t-mobile usually don't lock there bootloaders, but that doesn't mean anything they could still be locked down. Your best bet if your looking to get a new phone for whatever reason stick with the ones straight from samsung the international versions. they usually don't have locked bootloaders.
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.