Hey guys, I do no not own this phone (just picked up a Nexus 5) but, my dad does. He has been waiting for MONTHS to get his hands on this. It is his first Android device and he was able to ditch his work iPhone for it. However, he has been having an absolutely horrible experience:
I was remotely walking him through setup (moto transfer with iCloud to gmail account, etc etc).
- He turned on his phone, set up wifi, entered account credentials, played around for a minute or two.
- After this, he was prompted for an update, I told him to accept it
- After he accepted it, the phone WILL NOT TURN on. It boots to the homescreen, says it is "activating" the device, then it needs to restart.
- When it restarts, he sees the following attached screenshot.
I am assuming this was the Kit Kat update. I know tons of people have had problems with this (yes, I read the forums before posting, even though it is not my device). However, everyone with problems seemed to be rooted/not on stock. He is COMPLETELY stock.
If he chooses to reboot normally, he gets the homescreen, activation, then, it turns off and goes back to the attached screen.
If he chooses recovery, it goes back to this screen.
I'm not sure how an OTA could jack a phone up that was completely stock.. But it has happened.
Is there anything I can do remotely to help him start using his new phone? As I said, he has been excited for months for this phone and now just wants to throw it against the wall.
Is this screenshot the fastboot screen? If so, can I use the "fastboot erase cache" command?
Any *detailed* answers would be greatly appreciated... I'd love to get this working for him ASAP.
Thanks everyone!
View attachment 2415287
This is a pretty horrible out of box experience for something he was so excited about. I'm hoping this is something I can just do while remotely controlling his PC... I feel bad for the guy
fastboot erase cache
and then flash a stock recovery
Enviado desde mi XT1052 usando Tapatalk
waiflih said:
fastboot erase cache
and then flash a stock recovery
Enviado desde mi XT1052 usando Tapatalk
Click to expand...
Click to collapse
Not having this phone myself, how do I flash a recovery if I can't access current recovery or boot? Can I flash with a locked bootloader? Is the screen my dad is seeing the fastboot screen?
Any ideas how a stock out of the box phone would encounter this?
Thanks!
Sorry it's just hard to not have a device and jump into this when there are a million threads and it is completely different than any device I've owned (also I have no hands on time with it).
Thanks again. The more details the better so that I can do this remotely.
Sent from my Nexus 5 using XDA Premium 4 mobile app
yes that screen is fastboot mode, so u can download the files for ur rom here
http://sbf.droid-developers.org/ghost/list.php
and use fastboot to flash only recovery
Enviado desde mi XT1052 usando Tapatalk
Ok. I will have to figure out how to flash sbfs via fastboot then. I'm assuming it is a simple set of commands. I will try and find a tutorial when I am not driving. Thanks
Sent from my Nexus 5 using XDA Premium 4 mobile app
EmperorX said:
Ok. I will have to figure out how to flash sbfs via fastboot then. I'm assuming it is a simple set of commands. I will try and find a tutorial when I am not driving. Thanks
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Which model/carrier of phone does your dad have?
Xatt said:
Which model/carrier of phone does your dad have?
Click to expand...
Click to collapse
He's on Verizon, 16gb.
So confused as to how this happens fresh out of the box. Don't know how it's possible. I'm determined to fix it for him today though so he doesn't have to wait even longer
Sent from my Nexus 5 using XDA Premium 4 mobile app
If he just bought it, why are you messing around with this? Take it back to the retailer you bought it from and tell then what happened... Get a new phone...
AT&T Moto X rocking rooted 4.4
theraffman said:
If he just bought it, why are you messing around with this? Take it back to the retailer you bought it from and tell then what happened... Get a new phone...
AT&T Moto X rocking rooted 4.4
Click to expand...
Click to collapse
He got it customized from MotoMaker... If it's a relatively simple fix (and it's not a hardware issue) I'd rather do it myself so he doesn't have to wait yet again for who knows how long.
Sent from my Nexus 5 using XDA Premium 4 mobile app
waiflih said:
yes that screen is fastboot mode, so u can download the files for ur rom here
http://sbf.droid-developers.org/ghost/list.php
and use fastboot to flash only recovery
Enviado desde mi XT1052 usando Tapatalk
Click to expand...
Click to collapse
I'm assuming I can use any of the builds from verizon there? I'd like to get him to update OTA and see if it works this time or not... Was thinking about flashing one of the three 4.2.2 ones
EmperorX said:
He got it customized from MotoMaker... If it's a relatively simple fix (and it's not a hardware issue) I'd rather do it myself so he doesn't have to wait yet again for who knows how long.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
EmperorX I work for Moto. If you wouldn't mind providing the IMEI I'll get our engineers to take a look. You can PM me. Thanks!
I found this toolkit:
However, i'm assuming the fastboot menu will not work to just flash stock as you need to be in "Android or hboot"
The fastboot screen I took the picture of is not the same thing as hboot correct?
They are interchangeable terms. Hboot refers typically to an HTC bootloader
gunnyman said:
They are interchangeable terms. Hboot refers typically to an HTC bootloader
Click to expand...
Click to collapse
Awesome, looks like I may be able to fix this for him after all. Just need to remotely get androidsdk and adb setup on his computer with RSDlite as backup if this toolkit doesn't work and I *should* be able to make this happen. I think i've got enough info to do this now. Thanks guys!
EmperorX said:
He got it customized from MotoMaker... If it's a relatively simple fix (and it's not a hardware issue) I'd rather do it myself so he doesn't have to wait yet again for who knows how long.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Gotcha, makes sense not to want to go through all that. Sorry this happened to your dad. First I've heard of an issue this big on the moto x.
AT&T Moto X rocking rooted 4.4
theraffman said:
Gotcha, makes sense not to want to go through all that. Sorry this happened to your dad. First I've heard of an issue this big on the moto x.
AT&T Moto X rocking rooted 4.4
Click to expand...
Click to collapse
He was on the phone with Motorola "tier 2" support this morning for 3 hours. Their solution was to order a new phone and expedite shipping and return the old one when it gets here. I'm going to try this way first. They said this happens to "1 in 10,000" people. Lol, he's a lucky guy!
Well, now it's stuck on the fastboot screen with the following error:
No valid PIV block in SP for system
piv validation failed (system)
boot up failed
-__-
EmperorX said:
Well, now it's stuck on the fastboot screen with the following error:
No valid PIV block in SP for system
piv validation failed (system)
boot up failed
-__-
Click to expand...
Click to collapse
Sounds like the phone's partitions are all jacked up. Get a new phone is the solution.
EmperorX said:
Well, now it's stuck on the fastboot screen with the following error:
No valid PIV block in SP for system
piv validation failed (system)
boot up failed
-__-
Click to expand...
Click to collapse
what probably happened was your dad never activated the phone then tried to take an ota or something like that and it got all jacked up. Alternatively, he could have (for some reason) gotten the 4.4 OTA even though the phone was on original stock FW. This could have f'd the phone up if it skipped the 4.2.2 OTA. If you need to help you dad out, download teamviewer or logmein (remote computer access programs) and just guide him through when to plug the phone in etc.
Not sure about the error you are getting but it could be because you are flashing the wrong FW for the phone, possibly an older FW or an updated FW and the order you are flashing it could be causing the error. You can fix this relatively easily if you were more familiar with fastboot. I can try and walk you through some stuff as well on gchat if you need some help. I could also remote into your dads computer and do everything that needs to be done (he could then remove my ability to remote in clearly). All that being said Im fairly busy so just answering some questions for you would be easier but more time consuming for your dad. For starters, you probably should be flashing the 4.2.2 FW found on sbf. it is the middle fw for verizon on the list. You also can probably just use rsdlite since he hasn't set the phone up. It is super easy. Just go to the thread for rsd lite back to 100% stock and you will be good to go. Then make sure he activates and sets the phone up and everything before he takes the OTA this time.
Related
I was attempting to work through applying the .218 update to my droid 4. It was giving me a system validation error while when it was running in recovery. I found a thread that stated I needed to replace the apks and odex's as well as the build.prop. I didn't read it carefully enough as it said to replace *THE* problem ones. My validation error was on the build.prop file, I think.
In any case, I was using root explorer to copy *ALL* the files from a base zip file's app folder into the /system/app folder. Things were going along fine, until the phone app forced closed, then the phone rebooted.
Now I'm boot looping.
What can I do? I don't have any safe straps.
Can't access safestrap? Stock recovery? Adb services?
Sent from my DROID4 using Carrier Pigeons
The Magician Type 0 said:
Can't access safestrap? Stock recovery? Adb services?
Sent from my DROID4 using Carrier Pigeons
Click to expand...
Click to collapse
thanks for the reply...
I don't have safestrap installed on the device, and I've never used it. I don't think that's an option, unless you have something up your sleeve there
As for Stock recovery, I'd love to give it a try, but I don't know how that would work. I can't get to ADB because I can't boot the phone.
I *CAN* get into the bootloader. From there, I can get into recovery, AP Fastboot, BP SBF Flash BP boot... and others.
So, I'm hoping there's some kind of way to push to the device from one of the boot loader options. I've had a Droid 1, and a number of other android devices, but I've never gotten this far into a hole before.
again... thanks for whatever you got
It doesn't look good my friend, not without a SBF to flash. The only thing I can think of off the top of my head would be to try flashing the update again and cross your fingers that you got things in place before the bootloop. However I'm 99.9% sure that won't work. If I find anything else I'll let you now, but at this point you might be a sitting duck.
Sent from my DROID4 using Carrier Pigeons
The Magician Type 0 said:
It doesn't look good my friend, not without a SBF to flash. The only thing I can think of off the top of my head would be to try flashing the update again and cross your fingers that you got things in place before the bootloop. However I'm 99.9% sure that won't work. If I find anything else I'll let you now, but at this point you might be a sitting duck.
Sent from my DROID4 using Carrier Pigeons
Click to expand...
Click to collapse
I have the update on the SD Card, and nope, flashing it results in the same system validation error, and a bootloop.
thanks. Do you think that flashing the RAZR sbf's would get me a booting device? I only got the thing 14 days ago. Maybe I can exchange it
jbeazell said:
I have the update on the SD Card, and nope, flashing it results in the same system validation error, and a bootloop.
thanks. Do you think that flashing the RAZR sbf's would get me a booting device? I only got the thing 14 days ago. Maybe I can exchange it
Click to expand...
Click to collapse
If you're still in the 14 day return window I would try to return it. If it can't get past the bootloader than they won't know you rooted it. Just tell them you tried to do the update and it bootlooped. That's probably you're safest bet.
kwyrt said:
If you're still in the 14 day return window I would try to return it. If it can't get past the bootloader than they won't know you rooted it. Just tell them you tried to do the update and it bootlooped. That's probably you're safest bet.
Click to expand...
Click to collapse
I'm heading down there in a few minutes. Thanks for the help all ! I think I'm getting the razr maxx. My wife has one and the screen on that thing is incredible. I think it's worth losing the keyboard to get that screen... and the battery life. That part is also incredible.
again.. thanks.
BTW, you guys absolutely rock. You've helped me out of some serious holes with my OG Droid and other devices more often than I can count.
Sent from my DROID4 using Tapatalk 2
You can use bp tools to push over a clean system. I believe theres a tutorial somewhere that written for bionic. Just replace that with the droid 4 system. I would extract it from one of the stock roms available and push it thru bp tools.
Sent from my DROID4 using Tapatalk 2
Can you link that tutorial? I'm also trying to figure out how to use adb via stock recovery. Thanks!
Sent from my DROID4 using Carrier Pigeons
http://forum.xda-developers.com/showthread.php?t=1236465
Sent from my Galaxy Nexus using Tapatalk 2
Thanks!
Sent from my DROID4 using Carrier Pigeons
Let me know
Sent from my Galaxy Nexus using Tapatalk 2
It sounds like OP is going to exchange their phone, but could you really just replace the entire /system folder and have it work? (Nothing special with permissions, etc?)
If so, that is definitely something worth knowing...
Yes i believe so.
Sent from my DROID4 using Tapatalk 2
HI ALL,
I have successfully rooted my HTC and Samsung devices before but I am very new to LG phones.
I did root with ioroot22 (worked perfectly).
Then I attempted to install CWM with flashify app.
But in the process I flashed CWM incorrectly (I think)
When I boot phone I am just stuck in fastboot black screen.
Am I screwed? Seems like Sprint TOT or KDZ files are not available yet.
Anyone know what I can do to get phone working again. Any help is very much appreciated
Please note I can get into CWM when I press - & power but can't really do anything beyond that.
re:
Bump
Any solution from anyone?
panduhcub said:
Bump
Any solution from anyone?
Click to expand...
Click to collapse
Have you try factory rest? Power and volume down.
Sent from my LG-D959 using Tapatalk
re
copualt3 said:
Have you try factory rest? Power and volume down.
Sent from my LG-D959 using Tapatalk
Click to expand...
Click to collapse
That just brings me into CWM.
So you are actually able to get into recovery and use it? What happens when you try to make a back up? Does it let you? I know these questions don't help you. I could probably upload the factory recovery and we can try to put it back on in fastboot mode
Sent from my LG-LS995 using XDA Premium 4 mobile app
Seems you should be able to get your kdz file from LG.
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=xxxxxxxxxxxxxxx
Repace xxx with your 15 digit imei.
resultant page has a url about half way down. Use that and it downloads your firmware from LG.
Haven't tried but you could maybe use this installer to reflash:
http://forum.xda-developers.com/showthread.php?t=2134192
Best of luck
there is a thread for return to stock with full instructions and links for files & tools courtesy of hyelton:
http://forum.xda-developers.com/showthread.php?p=50308273
Re: Phone is back. Up and Running!!!!. Thanks wolfgart
justinswidebody said:
So you are actually able to get into recovery and use it? What happens when you try to make a back up? Does it let you? I know these questions don't help you. I could probably upload the factory recovery and we can try to put it back on in fastboot mode
Sent from my LG-LS995 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yea that didnt work, i think i damaged my my OS.
To the other poster, mrphil101, putting my IMEI didnt work on that website. Dont think LG has publicly released the kdz file yet.
Regardless, i was able to bring life back into my phone with the help of a member name, wolfgart. He was able to somehow provide me both the .tot & .dll for my sprint variant.
If you guys need any help on LG phones, he is the man.
How were you able to get in touch with him? I think he is banned from trying to sale the tot files. I would gladly buy the tot file so that we could all have it
Sent from my LG-LS995 using XDA Premium 4 mobile app
panduhcub said:
Yea that didnt work, i think i damaged my my OS.
To the other poster, mrphil101, putting my IMEI didnt work on that website. Dont think LG has publicly released the kdz file yet.
Regardless, i was able to bring life back into my phone with the help of a member name, wolfgart. He was able to somehow provide me both the .tot & .dll for my sprint variant.
If you guys need any help on LG phones, he is the man.
Click to expand...
Click to collapse
to bad...T-mo just released their phones too. Must be a sprint things. ISP's sure can hose things up with their firmwares, all that bloatware crap and untimely updates. I have been on nexus's for a long time; firmware and bootloader locks, I had forgotten how much of a pain they make it. But that said, this is the most satisfied I have been with a stock phone.
justinswidebody said:
How were you able to get in touch with him? I think he is banned from trying to sale the tot files. I would gladly buy the tot file so that we could all have it
Sent from my LG-LS995 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
PM sent
lets solve this out!
panduhcub said:
PM sent
Click to expand...
Click to collapse
I have this same exact issue but with the att g flex. right after rooting my device i also tried the recovery and this black screen came on. i freaked out but after a few times it finally booted up. then i stopped messing with custom recovery. but the other day a software update came on my screen and it did not let me pick whether or not to update it just did it on its own. and said software rebooting. after that is was stuck on the same screen again.
[460] Fastboot mode started
[460] udc_start()
[570]--portchange--
[570]--reset--
[730]--portchange--
[950] fastboot: proccessing commands
if you are rooted you should never take an OTA update..
wase4711 said:
if you are rooted you should never take an OTA update..
Click to expand...
Click to collapse
Mine updated without asking me I pulled my phone out of my pocket and the screen said your phone successfully updated I thoughts oh **** but all was fine still rooted and I'm running the 10l update. I'm on att though.
Sent from my LG-D950 using xda app-developers app
you are definitely lucky; have you rebooted the phone a few times to make sure everything still works normally?
Hello all
Inviato dal mio LG-D802 utilizzando Tapatalk
stuck on fastboot
Pleas help. I am stuck on same fastboot screen. Holding power plus volume down doesn't work. Computer doesn't recognize it when connected. What can I do? Thanks. Oh and it's tmobile.
legnaz said:
Pleas help. I am stuck on same fastboot screen. Holding power plus volume down doesn't work. Computer doesn't recognize it when connected. What can I do? Thanks. Oh and it's tmobile.
Click to expand...
Click to collapse
Sounds dumb but I'll ask anyway have you tried holding power down and volume UP?
Sent from my LG-D950 using XDA Premium 4 mobile app
brittoking said:
Sounds dumb but I'll ask anyway have you tried holding power down and volume UP?
Sent from my LG-D950 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep.
legnaz said:
Yep.
Click to expand...
Click to collapse
this question might even sound dumber? but how do you enter fastboot mode on the lg g flex?
recovery help. sprint variant
I tried to flash twrp for my sprint variant g-flex. it will not boot into recovery so therefore i do not have a recovery i need the offical tot and .dll files so that i can reroot and start from scratch if anybody is willing to help.
Kind of stuck here.
I have VZW developer edition. Rooted, 4.4 with TWRP
Foolishly I accepted the OTA update to 4.4.2, this failed of course but now my phone is constantly rebooting. It stays up for a few minutes then powers back to recovery.
Help !!!
Thanks.
Its a Dev phone just fxz and re-root
Sent from my XT1080 using xda app-developers app
bigv5150 said:
Its a Dev phone just fxz and re-root
Sent from my XT1080 using xda app-developers app
Click to expand...
Click to collapse
If only I had a clue what that meant
homemadehitshow said:
Kind of stuck here.
I have VZW developer edition. Rooted, 4.4 with TWRP
Foolishly I accepted the OTA update to 4.4.2, this failed of course but now my phone is constantly rebooting. It stays up for a few minutes then powers back to recovery.
Help !!!
Thanks.
Click to expand...
Click to collapse
Can you get into the bootloader (hold power + volume down)? If so, you'll probably need to reflash the stock recovery before the update will install.
Thanks, after I stopped panicking and calmed down I was able to flash Stock Recovery and then the next reboot caused the standard update to work. Kind of surprised really, still rooted etc.
Right now phone is working but Wi-Fi indicator is not lit, even though it is using the wi-fi.
Clear cache and dalvik cache?
Sent from my XT1060 using Tapatalk
homemadehitshow said:
Thanks, after I stopped panicking and calmed down I was able to flash Stock Recovery and then the next reboot caused the standard update to work. Kind of surprised really, still rooted etc.
Right now phone is working but Wi-Fi indicator is not lit, even though it is using the wi-fi.
Click to expand...
Click to collapse
Well you have the dev edition, they aren't going to take root from you. Don't know what's up with your wifi, though. When I updated I ended up having to restore a backup and updating again because of several extremely strange problems.
homemadehitshow said:
Thanks, after I stopped panicking and calmed down I was able to flash Stock Recovery and then the next reboot caused the standard update to work. Kind of surprised really, still rooted etc.
Right now phone is working but Wi-Fi indicator is not lit, even though it is using the wi-fi.
Click to expand...
Click to collapse
Disable WiFi and turn it back on right after.
Sent from my Moto X DE
Yep, everything seems to be working again now.
I have blindly followed instructions for flashing etc. using Fasboot but I think I'm finally getting a better feel for what is going on with it.
homemadehitshow said:
Yep, everything seems to be working again now.
I have blindly followed instructions for flashing etc. using Fasboot but I think I'm finally getting a better feel for what is going on with it.
Click to expand...
Click to collapse
Good job taking some initiative. Not as difficult as you thought it'd be right?
the verizon 4.4.2 SBF file is out so any issues anyone is having they can just flash the whole SBF file and be complety stock 4.4.2
enjoy
http://sbf.droid-developers.org/download.php?device=0&file=841
Running a completely stock VZW Moto X on the latest update (4.4.2). Woke up this morning to a half dozen or so app updates, including Active Display and Moto Help. I updated these two, and then an update for Beautiful Widgets started after. My phone then locked up and restarted. Now, it loads through the boot screen and then loads the Verizon screen, then the device goes black. I've tried wiping cache, to no avail. Any suggestions? I've installed the Moto X drivers via the Moto site, but the device isn't being recognized via ADB. I would really really really like to retrieve my files from the phone before doing a full factory reset...
Haven't seen anyone else report this....
Sent from my XT1060 using Tapatalk
Same symptoms on unlocked dev edition
I can't for sure tie it to an update, but the only thing that I did on my Moto X today was enable Motorola Connect. In the ensuing ~3 hours my phone bit it and would get to the Motorola Unlocked Bootloader screen and stop. Tried to boot to custom recovery, but it wouldn't work. Tried reloading TWRP, but gave access error on write but it seems to have fixed it enough to let TWRP open. TWRP showed list of access errors, like the memory had been corrupted. Need to find 4.4.2 image and load it back on via FB, as recovery has no data now.
stastnysnipes26 said:
Haven't seen anyone else report this....
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
omaharper said:
I can't for sure tie it to an update, but the only thing that I did on my Moto X today was enable Motorola Connect. In the ensuing ~3 hours my phone bit it and would get to the Motorola Unlocked Bootloader screen and stop. Tried to boot to custom recovery, but it wouldn't work. Tried reloading TWRP, but gave access error on write but it seems to have fixed it enough to let TWRP open. TWRP showed list of access errors, like the memory had been corrupted. Need to find 4.4.2 image and load it back on via FB, as recovery has no data now.
Click to expand...
Click to collapse
You have a totally separate problem from the OP. I don't have an unlocked boot loader and haven't done a ton of research on the risks of unlocking the consumer edition. 4.4.2 images are posted all around the forums. I would start there.
Sent from my XT1060 using Tapatalk
Thanks. You are right, not the same problem, when my phone soft bricks when I haven't been doing anything to it I get twitchy. I have the DE and have tried (a bunch of times) using RSD Lite and fastboot to push files back to phone, but after reboot everything looks to be reverted back like if WP was enabled, which it isn't. I will take a cruise thru the forums looking for similar issues, but any suggestions would be appreciated
stastnysnipes26 said:
You have a totally separate problem from the OP. I don't have an unlocked boot loader and haven't done a ton of research on the risks of unlocking the consumer edition. 4.4.2 images are posted all around the forums. I would start there.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
omaharper said:
Thanks. You are right, not the same problem, when my phone soft bricks when I haven't been doing anything to it I get twitchy. I have the DE and have tried (a bunch of times) using RSD Lite and fastboot to push files back to phone, but after reboot everything looks to be reverted back like if WP was enabled, which it isn't. I will take a cruise thru the forums looking for similar issues, but any suggestions would be appreciated
Click to expand...
Click to collapse
If you have a Dev edition fast boot stock vzw files, fast boot OEM unlock and reflash SU. simple as that.
Sent from my XT1060 using Tapatalk
Yup. Have gone thru that procedure several times, but phone won't get past the bootloader unlocked screen, and even after flashing stock (with stock recovery partition) TWRP still shows up, so some write to memory isn't sticking. It's very strange, used same procedure on this phone when upgrading to 4.4.2 from 4.2.2 and on other phones with no problem. Since TWRP can't access the flash, I am wondering if I actually have a corrupted memory module. If I can't get things working, I will start a thread. Don't want to hijack this one. Thanks.
stastnysnipes26 said:
If you have a Dev edition fast boot stock vzw files, fast boot OEM unlock and reflash SU. simple as that.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
As an update to the original post...
My phone "magically" booted at some point while it was sitting on my table. It's been working since then, but I tried to restart today and the thing won't boot up again. No idea what causes this and adb still isn't working with the phone in recovery mode.
Well I'm from the old school of if a car won't start you check 3 things spark fuel air. So in the case of our phones I always say fxz if an fxz fails to fix the problem than I lean towards a hardware failure. I have never had an fxz not fix a software issue. And I have bricked more than my fair share of devices several times.
I just did my custom order of the Moto X today. I hope I won't run into any issues. I'm switching from the iPhone 5S.
Sent from my XT1058 using Tapatalk
..
Y
thesandman00 said:
As an update to the original post...
My phone "magically" booted at some point while it was sitting on my table. It's been working since then, but I tried to restart today and the thing won't boot up again. No idea what causes this and adb still isn't working with the phone in recovery mode.
Click to expand...
Click to collapse
Have you tried fastboot?
Also getting the drivers to work can be tricky. You have to install them and then use device manager while you're phone is plugged in to get it working.
Sent from my XT1060 using Tapatalk
Hey guys I have a Moto bought Nexus 6, running on T-Mobile network Sim card and all. Currently the 6 is on 5.0.1 and has been asking me to bump up to 5.1. My phone is stock and rooted. As we all know I can't use the OTA as a result.
I'm here bugging you all because I know there are different builds for the Nexus 6, and they seem carrier specific. So I went and hunted down an M build which supposedly is for Tmo, as we have some specific tweaking.
I downloaded the LMY47M build and I am currently on the LRX22C 5.0.1 build. What I would like to know is it okay for me to go into TWRP and flash the download? Like the way a person would flash a nightly of CM? Is it the same process? If not what do I gotta do?
(On a bus ride so would be nice to have it update while I'm still riding)
Sent from my Nexus 6 using XDA Free mobile app
If the "download" is an OTA, it cannot be flashed from a custom recovery. ...and it will still fail because you're rooted.
Nope I downloaded online and it's sitting in a download folder now
Sent from my Nexus 6 using XDA Free mobile app
dynamo147 said:
Nope I downloaded online and it's sitting in a download folder now
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Let me rephrase, if the file you have downloaded is the same file you would get as an ota, then what i said before.
Very likely it's the same but I can't say for sure.,. So where does that leave me in terms of options?
Sent from my Nexus 6 using XDA Free mobile app
dynamo147 said:
Very likely it's the same but I can't say for sure.,. So where does that leave me in terms of options?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I don't know much about this "M" build and what version it is supposed to flash from. What I do know is there is no full factory image available.
Of everything else is stock on your phone (Including radio) I think the best action would be:
- download the factory image for the version you are on now.
- extract it and fastboot flash the stock recovery and system.img
- do NOT lock your bootloader
Then you should be able to accept the ota or side load it from stock recovery.
Mmm will try this when I get home thanks! Will be back to update Folks!
Also, will flashing the stock image and recovery wipe any of my data?
Sent from my Nexus 6 using XDA Free mobile app
dynamo147 said:
Mmm will try this when I get home thanks! Will be back to update Folks!
Also, will flashing the stock image and recovery wipe any of my data?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Not if you extract it an flash only the system.img
Its flashing the userdata image that wipes data
Yes. I would like to know how to do this also. Is there a difference in flashing the D or E version of 5.1 and then flashing a custom ROM that is built from T-Mobile's update?
Or is there carrier specifics in the different Factory Images?
downloading the img right now, when i get back I will make a little step by step for anyone else curious
dynamo147 said:
downloading the img right now, when i get back I will make a little step by step for anyone else curious
Click to expand...
Click to collapse
Its only 3 steps and I already Gave them earlier in the thread
BossJ said:
Yes. I would like to know how to do this also. Is there a difference in flashing the D or E version of 5.1 and then flashing a custom ROM that is built from T-Mobile's update?
Or is there carrier specifics in the different Factory Images?
Click to expand...
Click to collapse
In my mind in its the radio. you want the radio that comes with the T Mobile version. (if you are on t-mobile obviously) what you flash on top of it for system doesn't matter as long as it supports the radio and is version 5 .1. And as long as what you're flashing doesn't include the radio you are good to go.
So for me as long as I keep the E radio for Verizon I can flash D through M it kind of doesn't matter.
Sent from my Google N6 on VZ
rootSU said:
Its only 3 steps and I already Gave them earlier in the thread
Click to expand...
Click to collapse
Thanks for your replies here. I'm in the same boat as the OP, and have one follow-up question to this thread, if you or anyone could answer --
After doing the steps you mentioned previously -- specifically sideloading/accepting the OTA update, will the bootloader remain unlocked? I'd like to re-root afterwards and keep the user data, though I was under the impression it would actually re-lock the bootloader.
Thanks for any info!
vormund said:
Thanks for your replies here. I'm in the same boat as the OP, and have one follow-up question to this thread, if you or anyone could answer --
After doing the steps you mentioned previously -- specifically sideloading/accepting the OTA update, will the bootloader remain unlocked? I'd like to re-root afterwards and keep the user data, though I was under the impression it would actually re-lock the bootloader.
Thanks for any info!
Click to expand...
Click to collapse
Yes, your bootloader will remain unlocked.
dynamo147 said:
Hey guys I have a Moto bought Nexus 6, running on T-Mobile network Sim card and all. Currently the 6 is on 5.0.1 and has been asking me to bump up to 5.1. My phone is stock and rooted. As we all know I can't use the OTA as a result.
Click to expand...
Click to collapse
Did you ever get this going? I know I procrastinated a bit due to the "unknowns", but finally made it happen (bug off, TMo "5.1 Available" notification!). I ran into a lot of oddities between my phone and computer (running Windows 7) like the phone being an unrecognized device when working with adb sideloads... I ultimately opened the Device Manager and forced the composite ADB driver through for each instance. For me, the rough flow was, starting out with stock but unlocked and rooted,
* flashed stock LRX22C system and recovery images
* used adb to sideload the T-Mobile LMY47M official update
* flashed TWRP
* used adb to sideload SuperSU
* and of course, cleared the dalvik/cache and rebooted
All data in-tact, and my LEDs are still functional (the LEDs are actually the key reason I have it rooted right now... it's insanely stupid that Google blocks these built-in LEDs from being used by those that want them!).
Anyways, if you run into any of those issues, happy to help!
Evolution_Freak said:
Yes, your bootloader will remain unlocked.
Click to expand...
Click to collapse
Thank you...exactly what I needed to know!
Ah yeah I did actually, and I like you, had problems getting the phone recognized with the ADB, also windows 7, which prevented me from slide loading like I wanted to, but nevertheless got all the updates pushed through thnx though!
Sent from my Nexus 6 using XDA Free mobile app