Background info:
Currently running LMY47I on Nexus 6 unlocked and rooted with TWRP recovery on TMO network. When I updated to 5.1, the process of manual install went without a problem. After a little while, LTE reception was really poor. After doing some research, I realized that LMY47M was the specific release for TMO users and updates access to the 700 MHz band which I think might resolve some of my problems.
The plan:
Downgrade to 5.0.1 LRX22C so I can manually update to 5.1 LMY47M.
The problem:
My Nexus 6 isn't recognized as an ABD device once the bootloader is rebooted (but it is when the device is on and normally booted). I've tried to uninstall and reinstall drivers manually as well as with Wug's Root Toolkit. Still no dice.
Any ideas where I'm going wrong?
nccountrymike said:
Background info:
Currently running LMY47I on Nexus 6 unlocked and rooted with TWRP recovery on TMO network. When I updated to 5.1, the process of manual install went without a problem. After a little while, LTE reception was really poor. After doing some research, I realized that LMY47M was the specific release for TMO users and updates access to the 700 MHz band which I think might resolve some of my problems.
The plan:
Downgrade to 5.0.1 LRX22C so I can manually update to 5.1 LMY47M.
The problem:
My Nexus 6 isn't recognized as an ABD device once the bootloader is rebooted (but it is when the device is on and normally booted). I've tried to uninstall and reinstall drivers manually as well as with Wug's Root Toolkit. Still no dice.
Any ideas where I'm going wrong?
Click to expand...
Click to collapse
ADB is not used while in bootloader. You must use fastboot commands.
nccountrymike said:
Background info:
Currently running LMY47I on Nexus 6 unlocked and rooted with TWRP recovery on TMO network. When I updated to 5.1, the process of manual install went without a problem. After a little while, LTE reception was really poor. After doing some research, I realized that LMY47M was the specific release for TMO users and updates access to the 700 MHz band which I think might resolve some of my problems.
The plan:
Downgrade to 5.0.1 LRX22C so I can manually update to 5.1 LMY47M.
The problem:
My Nexus 6 isn't recognized as an ABD device once the bootloader is rebooted (but it is when the device is on and normally booted). I've tried to uninstall and reinstall drivers manually as well as with Wug's Root Toolkit. Still no dice.
Any ideas where I'm going wrong?
Click to expand...
Click to collapse
1) ADB commands are never recognized in fastboot. The correct command is "fastboot devices".
2) When you downgrade, do not downgrade your bootloader. Going from 5.1 bootloader to 5.0 bootloader then back to 5.1 bootloader could potentially lead to a brick.
3) The only files that the OTA looks at are system.img and boot.img, so these are all you need to fastboot flash.
Thanks all! User error confirmed.
Related
Hello, I would very much appreciate any help provided.
I just got a moto x developer edition gsm. I'll be using it on tmobile.
I've rooted lots of android phones and have never had this many problems. I tried a lot of different things on these forums and have had some success but i'm stuck now.
I was able to unlock the bootloader using motorola's site. I also have TWRP recovery installed (2.6.3.1). Currently the phone has 4.2.2 (build 13.9.0Q2.x-116-x-17-57) and its rooted, working fine.
The moral of the story is that i'm unable to update to 4.4. I've tried the OTA update twice and it downloads fine, then reboots to twrp to install it and it fails, saying something about its not ghost. Although in my system version it does say ghost. I also downloaded the 4.4 rom and manually tried to install it using twrp, also fails.
I'm not totally sure if the rom i'm on now is the same one that the phone came with. The rom that's on it now was obtained from this page:
http://sbf.droid-developers.org/phone.php?device=0
(Android 4.2.2 Blur_Version.139.12.57.ghost_row.Retail.en.US) for t-mobile US
Please help me be able to update to 4.4 and ideally keep root.
Jay10826 said:
Hello, I would very much appreciate any help provided.
I just got a moto x developer edition gsm. I'll be using it on tmobile.
I've rooted lots of android phones and have never had this many problems. I tried a lot of different things on these forums and have had some success but i'm stuck now.
I was able to unlock the bootloader using motorola's site. I also have TWRP recovery installed (2.6.3.1). Currently the phone has 4.2.2 (build 13.9.0Q2.x-116-x-17-57) and its rooted, working fine.
The moral of the story is that i'm unable to update to 4.4. I've tried the OTA update twice and it downloads fine, then reboots to twrp to install it and it fails, saying something about its not ghost. Although in my system version it does say ghost. I also downloaded the 4.4 rom and manually tried to install it using twrp, also fails.
I'm not totally sure if the rom i'm on now is the same one that the phone came with. The rom that's on it now was obtained from this page:
http://sbf.droid-developers.org/phone.php?device=0
(Android 4.2.2 Blur_Version.139.12.57.ghost_row.Retail.en.US) for t-mobile US
Please help me be able to update to 4.4 and ideally keep root.
Click to expand...
Click to collapse
You need to be stock, unrooted, with stock recovery to take the OTA. Use the sbf you have to flash back your stock system and recovery and you should be good to go to accept the update.
Jay10826 said:
The moral of the story is that i'm unable to update to 4.4. I've tried the OTA update twice and it downloads fine, then reboots to twrp to install it and it fails, saying something about its not ghost. Although in my system version it does say ghost. I also downloaded the 4.4 rom and manually tried to install it using twrp, also fails..
Click to expand...
Click to collapse
that is your problem. The OTA installs will not install via 3rd party recovery like TWRP and CWM.
fastboot flash the stock recovery back on your phone and try the OTA.
Thanks for the help guys, going back to completely stock enabled me to get to 4.4. After that luckily I found out that rooting and installing twrp was very simple, unlike all the info i was reading in the developer forum. All set now
Why didn't you flash the official firmware manually using fastboot? Once done, boot into Android and run adb reboot bootloader. Fastboot flash recovery twrp.img, select recovery, adb push su.zip /sdcard/, flash su.zip, adb reboot?
Recently purchased an AT&T XT1097. It was on Android 4.4.4 which I temp rooted with Kingroot and then bootloader unlocked using Sunshine. I'd like to upgrade to 5.1 so I haven't bothered yet with rooting or installing a recovery. Frankly, I'm a wee bit confused by the information I've found in numerous threads on this and other sites simply because it seems the AT&T and Verizon versions of the Moto X 2014 are problematic to work with.
Does having my bootloader unlocked at this point mean that any root method will work on the device? I believe flashing should be a non issue at this point (because the bootloader is unlocked) but will it also allow me to downgrade to 4.4.4 or 5.0.2 if I am not pleased with 5.1? Is using TWRP a good idea or would it be best to manually flash images thru fastboot (which I couldn't do without clear instructions)?
On a related note my device initially reported an available OTA system update but since unlocking via Sunshine I haven't had the notification return. MDM also doesn't see an available update. Is this due to Sunshine or left over vestiges of Kingroot despite having done a FDR?
Further update...
With no replies to my questions I've taken it upon myself to try a few things. Figured out that MDM will not see an available update unless the device can connect with AT&T via wifi at which point it tells me that an update is already in progress because the OTA is downloading to the device. I would prefer to download and flash the full image via MDM but it is refusing to do so. I'm assuming that this may be because the update the phone wants to install is now considered an interim update (5.0.2) and the full image has been pulled from Motorola's or AT&T's servers.
I have been able to successfully root 4.4.4 but have since removed it in the expectation of updating the device shortly. I have also been able to boot a TWRP image in the hopes of doing a backup before making any significant changes but the device becomes unresponsive to touch commands at the write protect warning screen. Any ideas???
I received an OTA and was going to install it. Am using Wug's tool kit to install factory image and unroot/unlock so I could install. Wug's is failing. It could not auto identify my device build number and failed to install factory image. When I checked online, it appears that LYZ28M is a T-mobile image. How can I get it back to factory to update the OTA or get my phone back to a build for Verizon. I have no idea how I manged to install a T-Mobile build on a Verizon device, is that even possible?
Downloading 5.1.1. LVY48i now to see if that will work.
Have been running on 5.0.1 (consumer cellular version). Tried to upgrade to marshmallow following the thread and that's where all problems began. After trying to flash through twrp, lost wifi. Bootloader is unlocked. Now the device is not recognized in ADB/Fastboot either...totally stumped after spending hours on this!! looks like the phone is now an official brick! Any last words of wisdom?
EDIT: painstakingly managed to get back to 5.0.2 stock. Device is root and twrp installed...now is there an official 6.0 version available for xt1064?
I moved my service from Cricket wireless to Verizon and while I do get voice and data, it's been strange. My signal bars keep fluctuating periodically between 0 and 5. Is this a radio issue? Do I need to flash a Verizon specific radio? Also, I recently updated to Nougat.
https://androidfilehost.com/?fid=312978532265362066 is Nougat 7.0 and latest bootloader and radio--flash in TWRP (assuming you're rooted, bootloader unlocked, and has TWRP recovery). If you're stock Nougat then reflash the Nougat image using Wug Fresh Tool: https://www.androidfilehost.com/?fid=24728673521238129 Also try to put in Verizon specific APN (google for settings)
HueyT said:
https://androidfilehost.com/?fid=312978532265362066 is Nougat 7.0 and latest bootloader and radio--flash in TWRP (assuming you're rooted, bootloader unlocked, and has TWRP recovery). If you're stock Nougat then reflash the Nougat image using Wug Fresh Tool: https://www.androidfilehost.com/?fid=24728673521238129 Also try to put in Verizon specific APN (google for settings)
Click to expand...
Click to collapse
Hey thanks a lot for your post. Got a bit busy but I tried the above and it seemed to help. :good: