Related
Hey all,
I'm having some trouble flashing TWRP on my phone. I've been following this guide here. When attempting to install TWRP to get root, however, it won't work. I've tried several different versions of fastboot & mfastboot. Sometimes I get a "bootloader variable not found" error, but most of the time now it exits saying it's successful. However, when I reboot into fastboot mode and then into recovery mode, it's still at the stock recovery. Can someone tell me what I'm doing wrong?
If it helps, my unlock status code shown is 3.
Thanks in advance!
thehockeydude44 said:
Hey all,
I'm having some trouble flashing TWRP on my phone. I've been following this guide here. When attempting to install TWRP to get root, however, it won't work. I've tried several different versions of fastboot & mfastboot. Sometimes I get a "bootloader variable not found" error, but most of the time now it exits saying it's successful. However, when I reboot into fastboot mode and then into recovery mode, it's still at the stock recovery. Can someone tell me what I'm doing wrong?
If it helps, my unlock status code shown is 3.
Thanks in advance!
Click to expand...
Click to collapse
Had the same issue, what I did is rsdlite back to stock and then attempt to flash twrp ,it worked.
Also make sure the twrp download is OK, you may want to re download it
Sent on my Moto X
flashallthetime said:
Had the same issue, what I did is rsdlite back to stock and then attempt to flash twrp ,it worked.
Also make sure the twrp download is OK, you may want to re download it
Sent on my Moto X
Click to expand...
Click to collapse
Forgot to mention I got the OTA as soon as my phone turned on. So go back to stock, root and then do the OTA?
thehockeydude44 said:
Forgot to mention I got the OTA as soon as my phone turned on. So go back to stock, root and then do the OTA?
Click to expand...
Click to collapse
No, ota won't flash with custom recovery.
Which carrier are you on.
Try a factory reset, you will lose all your data etc, so do a backup on your computer
Sent on my Moto X
flashallthetime said:
No, ota won't flash with custom recovery.
Which carrier are you on.
Try a factory reset, you will lose all your data etc, so do a backup on your computer
Sent on my Moto X
Click to expand...
Click to collapse
I didn't think it would... I'm on ATT, with a Dev edition. And no data to backup yet, just got the phone today.
Could you point me to where you got the working .img file?
thehockeydude44 said:
I didn't think it would... I'm on ATT, with a Dev edition. And no data to backup yet, just got the phone today.
Could you point me to where you got the working .img file?
Click to expand...
Click to collapse
Here' s the rsdlite thread http://forum.xda-developers.com/showthread.php?t=2446515
I believe on your op you used another thread, that thread has I believe the link for rsdlite
Here's the firmware thread http://forum.xda-developers.com/showthread.php?t=2538394
Prior to setting up rsdlite make sure you have the latest moto device manager and drivers installed. Also open up the sbf file and find the XML file, open it up and delete the line that has getvar in it
I took the camera 4.2 ota and I could not flash twrp either even though my boot loader is unlocked. I won't take any more ota's , I'll just flash the firmware through rsdlite
Sent on my Moto X
flashallthetime said:
Here' s the rsdlite thread http://forum.xda-developers.com/showthread.php?t=2446515
I believe on your op you used another thread, that thread has I believe the link for rsdlite
Here's the firmware thread http://forum.xda-developers.com/showthread.php?t=2538394
Prior to setting up rsdlite make sure you have the latest moto device manager and drivers installed. Also open up the sbf file and find the XML file, open it up and delete the line that has getvar in it
I took the camera 4.2 ota and I could not flash twrp either even though my boot loader is unlocked. I won't take any more ota's , I'll just flash the firmware through rsdlite
Sent on my Moto X
Click to expand...
Click to collapse
OK, I'll use rsdlite to get back to stock, and then flash the new firmware, and then see if I can flash the twrp.img. I saw the line about deleting the getvar line, so I'll make sure I do that too... thanks for the help, I'll let you know how it goes.
thehockeydude44 said:
OK, I'll use rsdlite to get back to stock, and then flash the new firmware, and then see if I can flash the twrp.img. I saw the line about deleting the getvar line, so I'll make sure I do that too... thanks for the help, I'll let you know how it goes.
Click to expand...
Click to collapse
Just flash the AT&T KitKat 4.4 sbf file, then you're up to date
Sent on my Moto X
flashallthetime said:
Just flash the AT&T KitKat 4.4 sbf file, then you're up to date
Sent on my Moto X
Click to expand...
Click to collapse
It worked! It must have been because of the OTA I got immediately... but flashing the correct 4.4 worked (I downloaded it directly from Motorola, since none of those specifically said GSM Dev Edition (turned out to be the T-Mo one). SuperSU works too, now just to install TiBu and be on my merry way!
thehockeydude44 said:
It worked! It must have been because of the OTA I got immediately... but flashing the correct 4.4 worked (I downloaded it directly from Motorola, since none of those specifically said GSM Dev Edition (turned out to be the T-Mo one). SuperSU works too, now just to install TiBu and be on my merry way!
Click to expand...
Click to collapse
I think all the firmware files are for either retail or developer editions, anyways glad it worked. I have no idea why this happens with the ota's?
Sent from my XT1058 using XDA Premium 4 mobile app
flashallthetime said:
I think all the firmware files are for either retail or developer editions, anyways glad it worked. I have no idea why this happens with the ota's?
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't know either. Might try and figure it out once I'm done with damn finals in 2 weeks.
I just bought a VZW Moto X non-dev edition that already came with unlocked bootloader (the seller told me and i confirmed it). The version is 4.4.2.
I could go into TWRP and install SuperSU v1.93. However, after rebooting, my phone still says it's not rooted. What have I done wrong?
X_Fact0r said:
I just bought a VZW Moto X non-dev edition that already came with unlocked bootloader (the seller told me and i confirmed it). The version is 4.4.2.
I could go into TWRP and install SuperSU v1.93. However, after rebooting, my phone still says it's not rooted. What have I done wrong?
Click to expand...
Click to collapse
TWRP does not install SuperSU....it installs "SuperSu Installer".
You need to look in your app drawer and find "SuperSu Installer", and run it. It will give you 2 options to install: choose "Play Store" option. Afterwards, you should be all set.
If you were able to install TWRP, your bootloader is indeed unlocked.
samwathegreat said:
TWRP does not install SuperSU....it installs "SuperSu Installer".
You need to look in your app drawer and find "SuperSu Installer", and run it. It will give you 2 options to install: choose "Play Store" option. Afterwards, you should be all set.
If you were able to install TWRP, your bootloader is indeed unlocked.
Click to expand...
Click to collapse
Hmm interesting. I couldn't find SuperSu Installer in my app drawer. Do I have to go into TWRP and install this file "UPDATE-SuperSU-v1.93.zip" first in order to see SuperSU Installer?
I actually did that too and still could not find SuperSU Installer. Any help is appreciated!
Edit: I guess what I'm trying to ask is how to root my moto X.
X_Fact0r said:
Hmm interesting. I couldn't find SuperSu Installer in my app drawer. Do I have to go into TWRP and install this file "UPDATE-SuperSU-v1.93.zip" first in order to see SuperSU Installer?
I actually did that too and still could not find SuperSU Installer. Any help is appreciated!
Click to expand...
Click to collapse
If you aren't already rooted, when you boot into TWRP and press "REBOOT" and then "SYSTEM", it should pop-up with a message saying something to the effect of: "Your device is not currently rooted. Would you like to install SuperSU-Installer?
Which version of TWRP are you using? AFAIK, only versions 2.6.3.1 and LATER will automatically install SuperSU-Installer for you....
samwathegreat said:
If you aren't already rooted, when you boot into TWRP and press "REBOOT" and then "SYSTEM", it should pop-up with a message saying something to the effect of: "Your device is not currently rooted. Would you like to install SuperSU-Installer?
Which version of TWRP are you using? AFAIK, only versions 2.6.3.1 and LATER will automatically install SuperSU-Installer for you....
Click to expand...
Click to collapse
I have TWRP 2.7.1.1. I just did what you said in TWRP but it rebooted right back to the lockscreen without asking to install SuperSU. By the way, I'm currently on 4.4.2. I'm not sure if that makes any difference.
samwathegreat said:
If you aren't already rooted, when you boot into TWRP and press "REBOOT" and then "SYSTEM", it should pop-up with a message saying something to the effect of: "Your device is not currently rooted. Would you like to install SuperSU-Installer?
Which version of TWRP are you using? AFAIK, only versions 2.6.3.1 and LATER will automatically install SuperSU-Installer for you....
Click to expand...
Click to collapse
This is what mine did too
X_Fact0r said:
I have TWRP 2.7.1.1. I just did what you said in TWRP but it rebooted right back to the lockscreen without asking to install SuperSU. By the way, I'm currently on 4.4.2. I'm not sure if that makes any difference.
Click to expand...
Click to collapse
Ah ha! That must be the issue. The NEW version (2.7.1.1) of TWRP is Official. The previous versions we were using were not from the official TWRP team. It would seem they took out the functionality I was referring to.
We will get you fixed right up though....
Head over to Chainfire's website: http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
And click the download button for the latest version (1.99r4)
Flash the file from TWRP. Now you should be all set
samwathegreat said:
Ah ha! That must be the issue. The NEW version (2.7.1.1) of TWRP is Official. The previous versions we were using were not from the official TWRP team. It would seem they took out the functionality I was referring to.
We will get you fixed right up though....
Head over to Chainfire's website: http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
And click the download button for the latest version (1.99r4)
Flash the file from TWRP. Now you should be all set
Click to expand...
Click to collapse
Just flashed that file from TWRP but still no root access ...Would I be able to just flash the earlier TWRP version and repeat the reboot system step to install supersu installer?
X_Fact0r said:
Just flashed that file from TWRP but still no root access ...Would I be able to just flash the earlier TWRP version and repeat the reboot system step to install supersu installer?
Click to expand...
Click to collapse
Hmmm....do you have an icon for "SuperSU" in your app drawer at all? I haven't seen the flash fail to install SuperSU.
If you can confirm that no icon is present for SuperSU, I can help you with flashing the older version of TWRP and SuperSU. Let me know...
samwathegreat said:
Hmmm....do you have an icon for "SuperSU" in your app drawer at all? I haven't seen the flash fail to install SuperSU.
If you can confirm that no icon is present for SuperSU, I can help you with flashing the older version of TWRP and SuperSU. Let me know...
Click to expand...
Click to collapse
Nope, no SuperSU icon.
X_Fact0r said:
Nope, no SuperSU icon.
Click to expand...
Click to collapse
OK, something strange is going on. I checked the other threads, and the TWRP version you mentioned, and the SuperSU version I linked are the suggested versions, and have been confirmed to work....
Lets assume this is just a fluke...
Download either Flashify or Rashr from the market
(OR just use mfastboot commands...)
And flash TWRP 2.6.3.1 from here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
Afterwards, do as instructed in my earlier posts. Does TWRP offer to install SuperSU Installer?
samwathegreat said:
OK, something strange is going on. I checked the other threads, and the TWRP version you mentioned, and the SuperSU version I linked are the suggested versions, and have been confirmed to work....
Lets assume this is just a fluke...
Download either Flashify or Rashr from the market
(OR just use mfastboot commands...)
And flash TWRP 2.6.3.1 from here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
Afterwards, do as instructed in my earlier posts. Does TWRP offer to install SuperSU Installer?
Click to expand...
Click to collapse
Will do! By the way, on bootloader page, it says "Device is unlocked. Status code: 3"
samwathegreat said:
OK, something strange is going on. I checked the other threads, and the TWRP version you mentioned, and the SuperSU version I linked are the suggested versions, and have been confirmed to work....
Lets assume this is just a fluke...
Download either Flashify or Rashr from the market
(OR just use mfastboot commands...)
And flash TWRP 2.6.3.1 from here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
Afterwards, do as instructed in my earlier posts. Does TWRP offer to install SuperSU Installer?
Click to expand...
Click to collapse
I just downloaded Flashify. It says "for root users." I don't think my phone is rooted though. Will flashify work?
X_Fact0r said:
Will do! By the way, on bootloader page, it says "Device is unlocked. Status code: 3"
Click to expand...
Click to collapse
Great, that means that you are definitely BL-unlocked (Status code: 3 is correct), and you WILL be rooted very soon. Once we get to the bottom of this...
---------- Post added at 07:34 PM ---------- Previous post was at 07:32 PM ----------
X_Fact0r said:
I just downloaded Flashify. It says "for root users." I don't think my phone is rooted though. Will flashify work?
Click to expand...
Click to collapse
Nope...I'm a dumbass (forgot root required to flash recovery from app)
you will have to use mfastboot. Do you have the android SDK and mfastboot binary installed? (On your PC?) Here is a the best guide I have found (if you don't have them): http://mark.cdmaforums.com/ADB.htm
samwathegreat said:
Great, that means that you are definitely BL-unlocked (Status code: 3 is correct), and you WILL be rooted very soon. Once we get to the bottom of this...
---------- Post added at 07:34 PM ---------- Previous post was at 07:32 PM ----------
Nope...I'm a dumbass (forgot root required to flash recovery from app)
you will have to use mfastboot. Do you have the android SDK and mfastboot binary installed?
Click to expand...
Click to collapse
Yes, I do. Just went back to 2.6.3.1. Hit reboot -> system but it didn't ask me to install supersu installer. I must have done something wrong earlier
I opened Flashify and it said the phone had root but it could not access SuperSU.
I have to step away from the computer a bit. I'll be back in a couple hours..
X_Fact0r said:
Yes, I do. Just went back to 2.6.3.1. Hit reboot -> system but it didn't ask me to install supersu installer. I must have done something wrong earlier
I opened Flashify and it said the phone had root but it could not access SuperSU.
I have to step away from the computer a bit. I'll be back in a couple hours..
Click to expand...
Click to collapse
Sure...when you return, try flashing the new version of SuperSU I linked from within the TWRP version you just flashed.
If this doesn't work, I may have a hunch on what MAY be going on. It is possible that the previous owner was using a root exploit + safestrap + MotoWpNoMo originally, then later had the BL unlocked and did not SBF back to stock firmware. This would explain why the updates you are flashing from TWRP are not being applied for some reason.
If you try flashing the new version of SuperSU from the TWRP version you just installed (2.6.3.1), and it STILL does not work, I highly suggest SBFing back to stock 4.4.2.
Follow the "Return to Stock" thread here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
You will download the 4.4.2 VZW SBF from here: http://sbf.droid-developers.org/phone.php?device=0
After you have "SBF'd" back to stock, any changes/exploits that the previous owner had used OR any corruption in the filesystem should be repaired. Afterwards, I almost -guarantee- that the methods I listed early in the thread WILL work.
samwathegreat said:
Sure...when you return, try flashing the new version of SuperSU I linked from within the TWRP version you just flashed.
If this doesn't work, I may have a hunch on what MAY be going on. It is possible that the previous owner was using a root exploit + safestrap + MotoWpNoMo originally, then later had the BL unlocked and did not SBF back to stock firmware. This would explain why the updates you are flashing from TWRP are not being applied for some reason.
If you try flashing the new version of SuperSU from the TWRP version you just installed (2.6.3.1), and it STILL does not work, I highly suggest SBFing back to stock 4.4.2.
Follow the "Return to Stock" thread here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
You will download the 4.4.2 VZW SBF from here: http://sbf.droid-developers.org/phone.php?device=0
After you have "SBF'd" back to stock, any changes/exploits that the previous owner had used OR any corruption in the filesystem should be repaired. Afterwards, I almost -guarantee- that the methods I listed early in the thread WILL work.
Click to expand...
Click to collapse
Many thanks!!!! everything worked properly and my phone is now rooted. Thanks again!!
samwathegreat said:
Sure...when you return, try flashing the new version of SuperSU I linked from within the TWRP version you just flashed.
If this doesn't work, I may have a hunch on what MAY be going on. It is possible that the previous owner was using a root exploit + safestrap + MotoWpNoMo originally, then later had the BL unlocked and did not SBF back to stock firmware. This would explain why the updates you are flashing from TWRP are not being applied for some reason.
If you try flashing the new version of SuperSU from the TWRP version you just installed (2.6.3.1), and it STILL does not work, I highly suggest SBFing back to stock 4.4.2.
Follow the "Return to Stock" thread here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
You will download the 4.4.2 VZW SBF from here: http://sbf.droid-developers.org/phone.php?device=0
After you have "SBF'd" back to stock, any changes/exploits that the previous owner had used OR any corruption in the filesystem should be repaired. Afterwards, I almost -guarantee- that the methods I listed early in the thread WILL work.
Click to expand...
Click to collapse
So I'm trying to install a custom ROM. I have the retail edition VZW Moto X with unlocked bootloader. When I install the ROM, should I follow the instructions for the dev edition or retail edition?
X_Fact0r said:
So I'm trying to install a custom ROM. I have the retail edition VZW Moto X with unlocked bootloader. When I install the ROM, should I follow the instructions for the dev edition or retail edition?
Click to expand...
Click to collapse
You will use dev edition instructions. Now that you are bootloader-unlocked, you own an 'unofficial' dev edition (for all practical purposes).
Have fun
I recently unrooted my Moto X 1053 DevEd (GSM) in order to accept the Lollipop 5.1 OTA. I got the update and it's working great.
Now I want to re-root my phone, but first I want to be sure that I have a copy of stock recovery.img for Lollipop 5.1.
How can I back up recovery.img from my phone without my phone being rooted?
Thanks!
is temp booting custom recovery still possible... I haven't messed around with stuff in a while, but I think if you can temp boot twrp recovery (fastboot boot twrp) you might be able to use it to back up the stock recovery... you should google for more info on that, make sure it doesn't flash instead of boot.
otherwise you can't backup stock recovery without root. it's kind of a catch 22: you want to back up stock recovery before you root, but you can't do that on the device without root.
normally you can get the recovery from the stock firmware zip file. but I don't think Motorola is handing them out for 5.1 yet - if they are then it will be in that file. if not I suppose the next best thing is to rummage through the OTA file. I haven't unzipped it myself but it has to be in there right? some info that might help: the recovery size is 10mb. I can see it with the DiskInfo app, along with its block partition name mmcblk0p34, although it probably won't be named that in the zip file idk... anyway you can find the OTA here: https://drive.google.com/file/d/0B9Eu943ka0GfQVVsdS13eHhZaU0/view?pli=1
That is a really, really helpful post, dtg7. I had hoped Moto would have posted the firmware, but I guess I'm too impatient. As I didn't have a separate copy of the OTA, I'm doing as you suggested and grabbing the OTA from the site you linked to. I'll try to extract the recovery.img file from there. I'll post my results.
Yes, this is a classic catch 22, as you say.
dtg7 said:
I haven't messed around with stuff in a while,...
Click to expand...
Click to collapse
This is precisely my problem. I get semi-proficient with phone stuff every now and then when I'm changing things around, but then I forget almost everything I need to know to do the most basic geek maneuvers. When I had an HTC Sensation, which was a favorite for ROM-makers and modders, I was swapping out the ROM nearly every day between meals. With the Moto X I haven't done this much, maybe because I've gotten older, but mainly because there don't seem to be as many custom ROMs for the Moto X (nor is as much need for them, with Xposed and with a decent stock ROM.
dtg7 said:
anyway you can find the OTA here: https://drive.google.com/file/d/0B9Eu943ka0GfQVVsdS13eHhZaU0/view?pli=1
Click to expand...
Click to collapse
Isn't that a link to KitKat 4.4.4 (i.e., 213.44.1)?
I've got Lollipop 5.1 on my phone, and "About Phone" lists it as 222.21.15.
It's actually system.img from 222.21.15 that I'm trying to get ahold of.
varxx said:
Isn't that a link to KitKat 4.4.4 (i.e., 213.44.1)?
I've got Lollipop 5.1 on my phone, and "About Phone" lists it as 222.21.15.
It's actually system.img from 222.21.15 that I'm trying to get ahold of.
Click to expand...
Click to collapse
Or is this still the case (quoted from elsewhere on this site)?
file name ... references the build your phone must be on to accept the update, not the version of the update itself. That is how Moto has done it for some time now.
Click to expand...
Click to collapse
varxx said:
Or is this still the case (quoted from elsewhere on this site)?
Click to expand...
Click to collapse
yes that is still the case, moto otas refer to the android version you're updating From
that file is what I used to update from 4.4.4 to lollipop
dtg7 said:
yes that is still the case, moto otas refer to the android version you're updating From
that file is what I used to update from 4.4.4 to lollipop
Click to expand...
Click to collapse
Thanks for clarifying this.
varxx said:
Thanks for clarifying this.
Click to expand...
Click to collapse
I'm in the same boat, only I need the recovery to kick off encryption. My process was, test the TWRP lollipop build, backup data with TWRP, flash 4.4.4 stock, OTA upgrade to Lollipop, install TWRP, restore data, can't encrypt now without stock recovery.
AaronCompNetSys said:
I'm in the same boat, only I need the recovery to kick off encryption. My process was, test the TWRP lollipop build, backup data with TWRP, flash 4.4.4 stock, OTA upgrade to Lollipop, install TWRP, restore data, can't encrypt now without stock recovery.
Click to expand...
Click to collapse
I can't find recovery.img in the uncompressed file dtg7 kindly linked above:
https://drive.google.com/file/d/0B9Eu943ka0GfQVVsdS13eHhZaU0/view?pli=1
Maybe I didn't look hard enough.
I *did* find the 4.4.4 recovery.img in the uncompressed file I requested and received from Moto. It seems like Moto sometimes uses the same recovery.img from release to release, but I'd be skittish about using this with stock 5.1 until someone can give it the all-clear. As of right now (27 june 15, 9:00 GMT), Moto hasn't posted stock 5.1.
AaronCompNetSys said:
I'm in the same boat, only I need the recovery to kick off encryption. My process was, test the TWRP lollipop build, backup data with TWRP, flash 4.4.4 stock, OTA upgrade to Lollipop, install TWRP, restore data, can't encrypt now without stock recovery.
Click to expand...
Click to collapse
varxx said:
As of right now (27 june 15, 9:00 GMT), Moto hasn't posted stock 5.1.
Click to expand...
Click to collapse
Looks like the stock XT1053 5.1 firmware is available now. See the links here: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628
dtg7 said:
Looks like the stock XT1053 5.1 firmware is available now. See the links here: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628
Click to expand...
Click to collapse
Thanks! I'm not sure if I want to try flashing just the recovery or not, I've been having lots lof radio active time so I migh full wipe/flash to try to clear that up.
Here is just the recovery from the "tmo_retail_xt1053_5.1_lpa23.12-15.222.21.15.ghost_row.retail.en.us.tgz" file:
https://mega.co.nz/#!WU5WjaqL!109FXTQovfywRxJM67YBH5KHrErNZYILPVyzk4HGK-c
varxx said:
I recently unrooted my Moto X 1053 DevEd (GSM) in order to accept the Lollipop 5.1 OTA. I got the update and it's working great.
Now I want to re-root my phone, but first I want to be sure that I have a copy of stock recovery.img for Lollipop 5.1.
How can I back up recovery.img from my phone without my phone being rooted?
Thanks!
Click to expand...
Click to collapse
Hi, I know there is an official build of CyanogenMod for the Moto X 2014. However there is limited info on what carriers it works on. I would like to know if the builds and methods of installing work on the latest update for the Verizon Moto X 2014. Thank You.
LunarEclipse120 said:
Hi, I know there is an official build of CyanogenMod for the Moto X 2014. However there is limited info on what carriers it works on. I would like to know if the builds and methods of installing work on the latest update for the Verizon Moto X 2014. Thank You.
Click to expand...
Click to collapse
If you unlocked Bootloader, you can install it. But with locked Bootloader, no way to use CM or another custom ROM !
md07 said:
If you unlocked Bootloader, you can install it. But with locked Bootloader, no way to use CM or another custom ROM !
Click to expand...
Click to collapse
Does CDMA data and signal work fine?
LunarEclipse120 said:
Does CDMA data and signal work fine?
Click to expand...
Click to collapse
just unlock bootloader. And eveything will OK. But Verizon.......
md07 said:
just unlock bootloader. And eveything will OK. But Verizon.......
Click to expand...
Click to collapse
What do you mean by but verizon...?
LunarEclipse120 said:
What do you mean by but verizon...?
Click to expand...
Click to collapse
Verizon not allow unlock bootloader !
md07 said:
Verizon not allow unlock bootloader !
Click to expand...
Click to collapse
Ok thanks
I am wondering the same thing, my Verizon xt1096 has an unlocked bootloader, I have tried a couple marshmallow roms with no signal .
Will calls and data work on Cyanogen on Verizon?
If not what about modding a stock marshmallow to work with Verizon?
Thanks
charliepan1 said:
I am wondering the same thing, my Verizon xt1096 has an unlocked bootloader, I have tried a couple marshmallow roms with no signal .
Will calls and data work on Cyanogen on Verizon?
If not what about modding a stock marshmallow to work with Verizon?
Thanks
Click to expand...
Click to collapse
CM13 works fine with Verizon on the xt1096. Your bootloader must be unlocked so that you can flash TWRP as your recovery. You will need to wipe Data and System in TWRP before flashing CM13, it can't be a dirty flash over the stock rom.
charliepan1 said:
I am wondering the same thing, my Verizon xt1096 has an unlocked bootloader, I have tried a couple marshmallow roms with no signal .
Will calls and data work on Cyanogen on Verizon?
If not what about modding a stock marshmallow to work with Verizon?
Thanks
Click to expand...
Click to collapse
How did you get an unlocked bootloader. Isn't that only for pure editions?
At least is there any way to root it?
mikeoswego said:
CM13 works fine with Verizon on the xt1096. Your bootloader must be unlocked so that you can flash TWRP as your recovery. You will need to wipe Data and System in TWRP before flashing CM13, it can't be a dirty flash over the stock rom.
Click to expand...
Click to collapse
Thanks I will give it a try.
---------- Post added at 10:34 PM ---------- Previous post was at 10:30 PM ----------
LunarEclipse120 said:
How did you get an unlocked bootloader. Isn't that only for pure editions?
Click to expand...
Click to collapse
I used Sunshine back when I was on 5.0.
Edited out since after reading a bit more, my post didn't make sense anymore.
Happy New Year all.
Ok well, Imy still unclear on CM installation: if the device has BL unlocked and running a stock MM, then I install twrp with fastboot (then rebbot to recovery), do I still need to root the stock firmware first (flash a modified kernel and SuperSU)?
testkeys said:
Edited out since after reading a bit more, my post didn't make sense anymore.
Happy New Year all.
Ok well, Imy still unclear on CM installation: if the device has BL unlocked and running a stock MM, then I install twrp with fastboot (then rebbot to recovery), do I still need to root the stock firmware first (flash a modified kernel and SuperSU)?
Click to expand...
Click to collapse
No, you don't need to root the stock rom in order to install CM. CM will replace the stock rom.
Once you have TWRP installed, the first thing you want to do is make a TWRP backup, preferably to a USB-OTG drive. Then, you can always restore that backup if something goes wrong. Once you have that backup, you can try rooting the stock rom (only if you want to try it) and if you don't like it, restore the backup. Don't let TWRP do the rooting for you, use TWRP to install the SuperSU using the latest SuperSU for Marshmallow zip file.
To try CM you will have to wipe your phone system and data (not internal storage where your pictures, etc. are stored.) You can then install CM13 and if you don't like it, restore the backup to return to the stock.
Good news, the unlocked bootloader is out! Anyone have troubles with cm13
LunarEclipse120 said:
Good news, the unlocked bootloader is out! Anyone have troubles with cm13
Click to expand...
Click to collapse
Nope, I have flashed 12.1 and 13 with no issues. Love it, just can't get Moto Voice to work....
Bio-Kinetic said:
Nope, I have flashed 12.1 and 13 with no issues. Love it, just can't get Moto Voice to work....
Click to expand...
Click to collapse
Does heads up display still work? Also does the Verizon cell service work fine?
LunarEclipse120 said:
Does heads up display still work? Also does the Verizon cell service work fine?
Click to expand...
Click to collapse
Heads up display works great and works great with verizon cell service. Great ROM
Bio-Kinetic said:
Heads up display works great and works great with verizon cell service. Great ROM
Click to expand...
Click to collapse
Did you unlock the bootloader with the method they released a couple days ago?
LunarEclipse120 said:
Did you unlock the bootloader with the method they released a couple days ago?
Click to expand...
Click to collapse
Yes and it worked like a champ with no issues. Followed it step by step, and it only took 10 min.
Hi all:
After upgrading my unlocked-but-still-rooted Turbo to Motorola stock Marshmallow, my Android Pay no longer works; I get the message about Android not be able to verify etc. From what I understand, SafetyNet now checks for unlocked bootloaders, not just root. Also, from what I understand, Sultanxda found a workaround by modifying the Android kernel, which they have working on the OP3.
Does anyone know if anyone is working on this for the original Turbo, and/or could someone kindly point me in the right direction?
Thanks in advance.
Workaround info: https://www.xda-developers.com/sult...otloader-check-on-latest-cm13-builds-for-op3/
phraxen said:
Hi all:
After upgrading my unlocked-but-still-rooted Turbo to Motorola stock Marshmallow, my Android Pay no longer works; I get the message about Android not be able to verify etc. From what I understand, SafetyNet now checks for unlocked bootloaders, not just root. Also, from what I understand, Sultanxda found a workaround by modifying the Android kernel, which they have working on the OP3.
Does anyone know if anyone is working on this for the original Turbo, and/or could someone kindly point me in the right direction?
Thanks in advance.
Workaround info: https://www.xda-developers.com/sult...otloader-check-on-latest-cm13-builds-for-op3/
Click to expand...
Click to collapse
Some of the CM-based ROMs floating around address this issue, but there is no way to use stock marshmallow with an unlocked bootloader and pass safetynet. So if you want android pay, your options are to stay on SU4TL-49 or install one of the CM-based ROMs that have implemented a workaround.
I got around this issue by using my credit card company's app instead of Android Pay. It allows me to do wireless payments everywhere Android Pay is accepted, but it only checks for root. It does not use safetynet.
Too late for you now, but recently someone in this forum updated to Marshmallow radio, but did NOT flash the Marshmallow bootloader. They were already using custom ROM. Others using that ROM who flashed Marshmallow bootloader no longer pass safetynet, but that person does. The conclusions is an unlocked Marshmallow bootloader or newer is what Safetynet looks for?
And yes, I've flashed both Marshmallow bootloader and radios over both my daily XT1225. I could only test the theory by breaking out my new-in-box third Quark, which have for emergency back-up -- and is which still probably on Kitkat.
While I previously had the older Google Wallet, Android Pay for me is not as important as controlling my own phone as I please. My phones will always be rooted. And in the Moto Quark, unlocking the bootloader is necessary for permanent root, whereas it's not necessary in some other phones -- like LG. But whatever needs to be done to root my phones, I will. And if Android Pay is not possible, so be it. I always carry my wallet when I go out somewhere. Pulling out my phone, pulling out my wallet, what's the difference?
phraxen said:
Hi all:
After upgrading my unlocked-but-still-rooted Turbo to Motorola stock Marshmallow, my Android Pay no longer works; I get the message about Android not be able to verify etc. From what I understand, SafetyNet now checks for unlocked bootloaders, not just root. Also, from what I understand, Sultanxda found a workaround by modifying the Android kernel, which they have working on the OP3.
Does anyone know if anyone is working on this for the original Turbo, and/or could someone kindly point me in the right direction?
Thanks in advance.
Workaround info: https://www.xda-developers.com/sult...otloader-check-on-latest-cm13-builds-for-op3/
Click to expand...
Click to collapse
So actually there is a way to get safetynet working again. All you have to do is flash the SU4TL-49 bootloader and wipe cache. I'll be posting the bootloader separately when I get a chance, but if you don't want to wait that long, download the full firmware package here: https://mega.nz/#!i84inDgI!IM_A_IpLlKfGpC90S2DPB6g9t8rVkhO8heE4o_WpdMI, extract bootloader.img and flash using fastboot.
fastboot flash motoboot bootloader.img
fastboot erase cache
EDIT: Here is a flashable zip that will flash the bootloader for you for those who are so inclined. Make sure to wipe cache and dalvik/art cache in TWRP afterwards: https://mega.nz/#!6logEaIQ!q8qPJw65Upt38Hxiu1JyxErmwbgL7CBzuGzzPC0C9pQ
EDIT 2: And here is the bootloader.img taken from the SU4TL-49 package if fastboot is your weapon of choice: https://mega.nz/#!iogRGIrQ!ixpZGw1cR90jLxe9r8EAt76SGNoSqVqSv1iu0v14QCc
TheSt33v said:
So actually there is a way to get safetynet working again. All you have to do is flash the SU4TL-49 bootloader and wipe cache. I'll be posting the bootloader separately when I get a chance, but if you don't want to wait that long, download the full firmware package here: https://mega.nz/#!i84inDgI!IM_A_IpLlKfGpC90S2DPB6g9t8rVkhO8heE4o_WpdMI, extract bootloader.img and flash using fastboot.
fastboot flash motoboot bootloader.img
Remember to wipe cache afterwards.
Click to expand...
Click to collapse
I'm confused... isn't that downgrading the bootloader?
ChazzMatt said:
I'm confused... isn't that downgrading the bootloader?
Click to expand...
Click to collapse
Yes it is. And as long as your bootloader is unlocked, no harm no foul. I thought that downgrading the bootloader was the one thing that you couldn't do even if it was unlocked, but I just did it and I'm passing safetynet now, so I guess I was wrong.
If anyone wants proof I'm on the SU4TL-49 bootloader, I can take a picture when I get home. I don't know of a way to get a picture of the bootloader screen using only my phone.
TheSt33v said:
Yes it is. And as long as your bootloader is unlocked, no harm no foul. I thought that downgrading the bootloader was the one thing that you couldn't do even if it was unlocked, but I just did it and I'm passing safetynet now, so I guess I was wrong.
Click to expand...
Click to collapse
Learn something new everyday. Wow.
You just can't downgrade a locked bootloader, eh?
Thank you!
When I get home will try Lollipop bootloader on my XT1225.
The custom ROM guys will love this, then.
ChazzMatt said:
Learn something new everyday. Wow.
You just can't downgrade a locked bootloader, eh?
Thank you!
When I get home will try Lollipop bootloader on my XT1225.
The custom ROM guys will love this, then.
Click to expand...
Click to collapse
I seem to remember trying this a long time ago using TWRP, and TWRP was unable to flash the older bootloader. It works fine through fastboot though. I'm going to do some more investigation when I'm not at work to see if I can get TWRP to do this. That would be easier for most people.
Also, I thought the latest iSu already got around this issue. That's what BHB's command line patch thing is for. But it will certainly make things easier!
TheSt33v said:
I seem to remember trying this a long time ago using TWRP, and TWRP was unable to flash the older bootloader. It works fine through fastboot though. I'm going to do some more investigation when I'm not at work to see if I can get TWRP to do this. That would be easier for most people.
Also, I thought the latest iSu already got around this issue. That's what BHB's command line patch thing is for. But it will certainly make things easier!
Click to expand...
Click to collapse
I was on the latest bootloader and just flashed the .47 bootloader because of major radio issues. I flashed from TWRP and have been doing it since the .49 update.
gumbi2647 said:
I was on the latest bootloader and just flashed the .47 bootloader because of major radio issues. I flashed from TWRP and have been doing it since the .49 update.
Click to expand...
Click to collapse
Interesting. I've noticed that TWRP randomly has issues with flashing things on my phone for some reason, and a reboot often fixes the issue. Maybe I just got unlucky that one time, but if that's the case, I'll have a flashable SU4TL-49 bootloader up a few minutes after I get home.
TheSt33v said:
Interesting. I've noticed that TWRP randomly has issues with flashing things on my phone for some reason, and a reboot often fixes the issue. Maybe I just got unlucky that one time, but if that's the case, I'll have a flashable SU4TL-49 bootloader up a few minutes after I get home.
Click to expand...
Click to collapse
IF you can flash through TWRP, then clearing caches is no problem in TWRP. IF we must use ADB, please include instructions to also clear caches that way, in any write-up -- if that's what you mean?
Or you do you mean flash bootloader in ADB, then immediately boot into TWRP and clear caches -- before booting back to system?
ChazzMatt said:
IF you can flash through TWRP, then clearing caches is no problem in TWRP. IF we must use ADB, please include instructions to also clear caches that way, in any write-up -- if that's what you mean?
Or you do you mean flash bootloader in ADB, then immediately boot into TWRP and clear caches -- before booting back to system?
Click to expand...
Click to collapse
ADB is not involved. Only fastboot.
The way I did it on my phone (XT1254 unrooted, unlocked, 100% stock MM) exactly was this:
1. Make note of BL version on bootloader screen.
2. fastboot flash motoboot bootloader.img using the SU4TL-49 bootloader.
3. Reboot bootloader
4. Confirm that the BL version has changed (it did)
5. Reboot to system.
6. Tried safetynet (failed)
7. Reboot to stock MM recovery menu
8. Wipe cache, reboot to system
9. Tried safetynet (passed), added a bunch of cards in Android Pay without issue
I'm assuming that wiping cache using other methods will be just as effective, but I don't know that for sure.
TheSt33v said:
ADB is not involved. Only fastboot.
The way I did it on my phone (unrooted, unlocked, 100% stock MM) exactly was this:
1. Make note of BL version on bootloader screen.
2. fastboot flash motoboot bootloader.img using the SU4TL-49 bootloader.
3. Reboot bootloader
4. Confirm that that BL version has changed (it did)
5. Reboot to system.
6. Tried safetynet (failed)
7. Reboot to stock MM recovery menu
8. Wipe cache, reboot to system
9. Test safetynet (passed)
I'm assuming that wiping cache using other methods will be just as effective, but I don't know that for sure.
Click to expand...
Click to collapse
Which version of TWRP are you using? I heard the 04 update has some issues. I have been on 03 forever.
gumbi2647 said:
Which version of TWRP are you using? I heard the 04 update has some issues. I have been on 03 forever.
Click to expand...
Click to collapse
04, so that could be it.
I post this around XDA, new bootloader add a new prop line
it add
[ro.boot.flash.locked]: [0]
And I patch that with this
https://www.androidfilehost.com/?fid=745425885120696423
with will change that to
[ro.boot.flash.locked]: [1]
Just use adb command
Code:
getprop | grep ro.boot.flash.locked
to check.
and then cts will not fail so is not really need to downgrade for now, There is the chance that Moto will change the boot.img so it can't boot on old bootloader, that did not happens yet on quark but others Moto device is need latest bootloader with latest ROM.
But then again may never be a update from Moto to this device.
So as long Moto did not make another patch flash this in TWRP and test with latest bootloader
https://www.androidfilehost.com/?fid=745425885120696423
of course that will not fix any other CTS fail like xposed or ROOT
So let me know if that helps if not it may be somethings else that can also be patched.
TheSt33v said:
So actually there is a way to get safetynet working again. All you have to do is flash the SU4TL-49 bootloader and wipe cache. I'll be posting the bootloader separately when I get a chance, but if you don't want to wait that long, download the full firmware package here: https://mega.nz/#!i84inDgI!IM_A_IpLlKfGpC90S2DPB6g9t8rVkhO8heE4o_WpdMI, extract bootloader.img and flash using fastboot.
fastboot flash motoboot bootloader.img
fastboot erase cache
Click to expand...
Click to collapse
Thanks for this. I'll give it a shot and let you know how it turns out.
bhb27;70506510So as long Moto did not make another patch flash this in TWRP and test with latest bootloader
[url said:
https://www.androidfilehost.com/?fid=745425885120696423[/url]
of course that will not fix any other CTS fail like xposed or ROOT
So let me know if that helps if not it may be somethings else that can also be patched.
Click to expand...
Click to collapse
Thanks! Flashing that works just fine. So now we have 2 options.
bhb27 said:
I post this around XDA, new bootloader add a new prop line
it add
[ro.boot.flash.locked]: [0]
And I patch that with this
https://www.androidfilehost.com/?fid=745425885120696423
with will change that to
[ro.boot.flash.locked]: [1]
Just use adb command
Code:
getprop | grep ro.boot.flash.locked
to check.
and then cts will not fail so is not really need to downgrade for now, There is the chance that Moto will change the boot.img so it can't boot on old bootloader, that did not happens yet on quark but others Moto device is need latest bootloader with latest ROM.
But then again may never be a update from Moto to this device.
So as long Moto did not make another patch flash this in TWRP and test with latest bootloader
https://www.androidfilehost.com/?fid=745425885120696423
of course that will not fix any other CTS fail like xposed or ROOT
So let me know if that helps if not it may be somethings else that can also be patched.
Click to expand...
Click to collapse
That worked for me. I was able to add a debit card without getting the error.
Thanks to you and TheSt33v.
ChazzMatt said:
IF you can flash through TWRP, then clearing caches is no problem in TWRP. IF we must use ADB, please include instructions to also clear caches that way, in any write-up -- if that's what you mean?
Or you do you mean flash bootloader in ADB, then immediately boot into TWRP and clear caches -- before booting back to system?
Click to expand...
Click to collapse
Have you tried this using TWRP and if so did everything go well
Sent from my XT1254 using Tapatalk
joekitch said:
Have you tried this using TWRP and if so did everything go well
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
I have not personally tried it yet. Someone else can answer if they have?