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.
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?
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.
Hello everyone... I have a N6 I got directly from Google Play Store and I am using a VZW sim card... I unlocked, rooted and have TWRP installed but other than that I am still on stock 5.1
Today I got the notification that 5.1.1 update is available to install so I went on Google to get the factory image and update with fastboot so I would not lose data also... but it seems that Google only posted the factory images for Sprint and T-Mobile... So I am not sure how to go about this now... I obviously can't update from OTA but I don't seem to be able to download an appropriate factory image.
Any help is appreciated!
It's the same one as sprint, LMY47Z
Sent from my Nexus 6 using Tapatalk
Before you received the OTA, what build were you running? 47D?
Just bought an at&t variant on craigslist, I did a factory reset and tried to run the 5.1 update and I get an error updating, it downloads update.. then it reboots and starts installing showing the android guy working , then about 20 seconds into it it shows the little android guy on his back with a red exclamation and says error and then proceeds to reboot. Once rebooted it says it failed to update. I'm used to Samsung phones .. hoping there's an odin type option to get a stock 5.1 or rooted stock 5.1 on this guy, any headstart info would be appreciated. thanks
Here is the AT&T 5.0.2 firmware:
http://www.filefactory.com/file/1cekivswpakf/VICTARA_ATT_XT1097_5.0.2_LXE22.46-34_cid1_CFC.xml.zip
If you want to unlock your bootloader or root your phone don't upgrade yet! While you still have 5.0.2, root is possible with mofo and unlocking the bootloader can be done with sunshine. After you upgrade to 5.1 you can't downgrade nor root it. If you unlock it now and root it now, then you can keep root when you go to 5.1. But if you go to 5.1 before that you are screwed and lose the ability to do it forever.
We don't use odin. We have a tool called RSDLite. Search for it on these forums and you will find it and instructions on how to use it.
Sent from my XT1095 using Tapatalk
thanks for the heads up.. Glad I decided to wait and not try to figure out that update.. then not be able to root.
thanks
My phone is completely stock now after I had trouble flashing an OTA on my Metro E5 Plus. It failed(with an error everytime) as I tried to install even after removing root. I flashed a backup, but now I can't even get an OTA prompt, tried to force update. Im stuck on the June security patch. Does anyone know what I can do to force, or flash an update?
Juanito216 said:
My phone is completely stock now after I had trouble flashing an OTA on my Metro E5 Plus. It failed(with an error everytime) as I tried to install even after removing root. I flashed a backup, but now I can't even get an OTA prompt, tried to force update. Im stuck on the June security patch. Does anyone know what I can do to force, or flash an update?
Click to expand...
Click to collapse
If you used a stock firmware it should work. You might ask around if anyone has a twrp backup for your particular model AFTER the ota.