Related
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
xd
kal eh said:
Hello, I'm pretty much new to the android scene therefore excuse me for my stupidness on this field
I unlocked my nexus 6, then I rooted it and and then I flashed a custom rom (Euphoria 1.0) with WugFresh's Tool.
Yesterday I tried installing adaway and gave it full root permissions, it asked me to reboot and I did so.
After rebooting I realized that I can't unlock my phone nor do anything else except using the pull down notification bar and having a back button, no middle button nor right button.. The screen just remains black. I tried rebooting in recovery mode but nothing changes.
What do I've to do now?
The device doesn't show up as MTP.
When I enter TWRP now it asks me for a password??
I've a Nandroid backup saved on my HDD and I still have the custom rom ZIP saved as well.
Click to expand...
Click to collapse
Reset your entire phone by flashing the factory image. This can be done with the wugs toolkit as well.
Sent from my Nexus 9 using Tapatalk
scandalousk said:
Reset your entire phone by flashing the factory image. This can be done with the wugs toolkit as well.
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
What would happen if I just restored a Nandroid backup I made? would it still work?
kal eh said:
What would happen if I just restored a Nandroid backup I made? would it still work?
Click to expand...
Click to collapse
It depends. If your phone doesn't work at the moment because something is wrong in the rom, the chance of the same thing happening could happen again. You can try restoring your nandroid and see if that fixes your problem. If not going back to stock is the best way to fix your problem.
Sent from my Nexus 9 using Tapatalk
scandalousk said:
It depends. If your phone doesn't work at the moment because something is wrong in the rom, the chance of the same thing happening could happen again. You can try restoring your nandroid and see if that fixes your problem. If not going back to stock is the best way to fix your problem.
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
XD
I downloaded 5.1 OTA today on T-Mobile. After updating, I had severe issues such as screen going black during calls, ambient display not working, google play services not working, and random reboots.
My phone was working perfect on 5.0.1 so i decided to flash 5.0.1 stock rom. I followed all the exact steps listed in the How-TO page on this website.
Nexus 6 was stuck in a boot loop. I was able to to go into recovery, and do wipe data/factory reset. Now the phone boots up, says "optimizing apps ## / ##" and then reboots again each time.
If I try to go into recovery mode holding power and volume up buttons, nothing happens.
Please Help me. I am new to all this. Is there any way to fix this?
Ok, I just got into recovery mode. I wiped the cache and also wiped data/factory reset. I then clicked reboot system now.
However, the same thing comes up as before (boot loop, android is optimizing apps)
I tried using Nexus Root Toolkit as well, but didn't help. Any suggestions?
starrscream22 said:
Ok, I just got into recovery mode. I wiped the cache and also wiped data/factory reset. I then clicked reboot system now.
However, the same thing comes up as before (boot loop, android is optimizing apps)
I tried using Nexus Root Toolkit as well, but didn't help. Any suggestions?
Click to expand...
Click to collapse
Try downloading the Rom again, and if it has one check the md5. When you go to flash wipe everything except internal storage from the advanced menu. Flash and try again.
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
Try downloading the Rom again, and if it has one check the md5. When you go to flash wipe everything except internal storage from the advanced menu. Flash and try again.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks! I was able to get it working on 5.0.1
My question is, since bootloader can't be downgraded and I am back on stock 5.0.1, will I be able to receive OTA updates or am I going to have to manually update my phone from now on?
Also, my kernel version changed. Before it was January 28 2015 and now its October 24 2014. does this mean anything
Also my total space under storage changed. Before it was like 25gb and now it says 23gb
starrscream22 said:
Thanks! I was able to get it working on 5.0.1
My question is, since bootloader can't be downgraded and I am back on stock 5.0.1, will I be able to receive OTA updates or am I going to have to manually update my phone from now on?
Also, my kernel version changed. Before it was January 28 2015 and now its October 24 2014. does this mean anything
Click to expand...
Click to collapse
I'm quite sure you won't get OTA updates unless you are on the latest version, don't wrote me on that though.
starrscream22 said:
Also my total space under storage changed. Before it was like 25gb and now it says 23gb
Click to expand...
Click to collapse
Only fix I know off for this is back everything up to a computer, boot into boot loader and do fastboot format userdata
Everything will get wiped from your phone so make sure it's all backed up on your computer.
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
I'm quite sure you won't get OTA updates unless you are on the latest version, don't wrote me on that though.
Only fix I know off for this is back everything up to a computer, boot into boot loader and do fastboot format userdata
Everything will get wiped from your phone so make sure it's all backed up on your computer.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you so much! That fixed the storage issue.
5.1.0 (LMY47M) The t-mobile version isn't available on google factory images yet, i hope it will be. i guess i can get OTA updates once that version is posted on google.
i will wait anyways, because my whole reason for doing this was 5.1 cause severe issues whereas 5.0.1 was running perfect. Thanks again.
starrscream22 said:
Thank you so much! That fixed the storage issue.
5.1.0 (LMY47M) The t-mobile version isn't available on google factory images yet, i hope it will be. i guess i can get OTA updates once that version is posted on google.
i will wait anyways, because my whole reason for doing this was 5.1 cause severe issues whereas 5.0.1 was running perfect. Thanks again.
Click to expand...
Click to collapse
No worries man, glad you got it sorted.
Sent from my Nexus 6 using XDA Free mobile app
Title says short part.
Used wugs NRT to downgrade and revert back to LMZ28E and used NRT to root and install twrp,
Tried flashing cm12.1 and it gets to the boot animation and won't boot past that. :-/ the down grade flashed old boorloader and radio and everything....
Don't know what the problem would be.
Advice? Thoughts? Suggestions?
Sent from my Nexus 6 using XDA Free mobile app
Try a factory image?
sookieball said:
Title says short part.
Used wugs NRT to downgrade and revert back to LMZ28E and used NRT to root and install twrp,
Tried flashing cm12.1 and it gets to the boot animation and won't boot past that. :-/ the down grade flashed old boorloader and radio and everything....
Don't know what the problem would be.
Advice? Thoughts? Suggestions?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
advice, thought, or a suggestion.. dont use toolkits until you know what you are actually doing. do things the right way, until you learn how to do it properly. then use all the toolkits you want. the problem is that toolkits dont teach you a single thing, and doing things right on any nexus is very easy.
my suggestion would be to wipe data/system then reflaah cm again.
sookieball said:
Title says short part.
Used wugs NRT to downgrade and revert back to LMZ28E and used NRT to root and install twrp,
Tried flashing cm12.1 and it gets to the boot animation and won't boot past that. :-/ the down grade flashed old boorloader and radio and everything....
Don't know what the problem would be.
Advice? Thoughts? Suggestions?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Junk ROM anyway.. Lol
simms22 said:
advice, thought, or a suggestion.. dont use toolkits until you know what you are actually doing. do things the right way, until you learn how to do it properly. then use all the toolkits you want. the problem is that toolkits dont teach you a single thing, and doing things right on any nexus is very easy.
my suggestion would be to wipe data/system then reflaah cm again.
Click to expand...
Click to collapse
I actually am not a noob,
And I do know how to flash factory images manually using fastboot commands.
I downloaded all necessary files to flash manually.
I did that,
Wouldn't boot past boot animations.
Tried again with tmobile official (from google) files,
Same thing. So last resort was wugs.
Clean flashed cm12.1.
And wouldn't boot.
I appreciate your advice, but don't assume because I didn't succeed on a simple thing as a flash, that one is not familiar with this. The only thing I can think of that would have prevented boot was maybe I had a bad DL of cm.
But unlikely.
Planned on downloading a diff ROM and gapps.
If it doesn't I'll be flashing factory images of LMY47M manually and reroot and recovery and start from there.
Oh and thank you for the wipe/advice.
I did :-/ go fig
Reflashed before I restored backup but no go.
Sent from my Nexus 6 using XDA Free mobile app
sookieball said:
I actually am not a noob,
And I do know how to flash factory images manually using fastboot commands.
I downloaded all necessary files to flash manually.
I did that,
Wouldn't boot past boot animations.
Tried again with tmobile official (from google) files,
Same thing. So last resort was wugs.
Clean flashed cm12.1.
And wouldn't boot.
I appreciate your advice, but don't assume because I didn't succeed on a simple thing as a flash, that one is not familiar with this. The only thing I can think of that would have prevented boot was maybe I had a bad DL of cm.
But unlikely.
Planned on downloading a diff ROM and gapps.
If it doesn't I'll be flashing factory images of LMY47M manually and reroot and recovery and start from there.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Did you downgrade the bootloader back to 5.1.1?
Evolution_Tech said:
Did you downgrade the bootloader back to 5.1.1?
Click to expand...
Click to collapse
Yes, manually first and when it wouldnt* boot past animation, last resort was NRT
So I'm assuming NRT flashed boot loader associated to LMZ28E
Edit: maybe if I downgrade down to 5.0.1? Then reroot and recovery?
Sent from my Nexus 6 using XDA Free mobile app
sookieball said:
Yes, manually first and when it would boot past animation, last resort was NRT
So I'm assuming NRT flashed boot loader associated to LMZ28E
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Do we know for a fact the that we can downgrade the bootloader from m? We learned we couldn't downgrade from 5.1 bootloader.
rootSU said:
Do we know for a fact the that we can downgrade the bootloader from m? We learned we couldn't downgrade from 5.1 bootloader.
Click to expand...
Click to collapse
I reread the thread like 3x.
And it was mentioned that another user used NRT to downgrade successfully.
I thought the same thing, but didn't try it till I read that thread till 4am. This morning decided to take the plunge.
I was thinking also, if I just reflash bootloader and radio and put M back on, then just try manually flashing 5.1?
Sent from my Nexus 6 using XDA Free mobile app
sookieball said:
I actually am not a noob,
And I do know how to flash factory images manually using fastboot commands.
I downloaded all necessary files to flash manually.
I did that,
Wouldn't boot past boot animations.
Tried again with tmobile official (from google) files,
Same thing. So last resort was wugs.
Clean flashed cm12.1.
And wouldn't boot.
I appreciate your advice, but don't assume because I didn't succeed on a simple thing as a flash, that one is not familiar with this. The only thing I can think of that would have prevented boot was maybe I had a bad DL of cm.
But unlikely.
Planned on downloading a diff ROM and gapps.
If it doesn't I'll be flashing factory images of LMY47M manually and reroot and recovery and start from there.
Oh and thank you for the wipe/advice.
I did :-/ go fig
Reflashed before I restored backup but no go.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
i did flash the new bootloader, but i went back and forth from M to terminus(rom) about 5 times yesterday. flaah the new bootloader again, and keep it. you trying to downgrade it might be the issue. btw, i flashed m, and the bootloader, via twrp recovery, its much easier and faster that way. after, i made a backup in recovery. so now all i do to go back and forth is restore the backups.
oh, and i meant you no disrespect. while it doesnt include everyone, most people using toolkits around here are noobs. and they are the ones that usually get stuck. so, i apologize
simms22 said:
i did flaah the new bootloader, but i went back and forth from M to terminus(rom) about 5 times yesterday. flaah the new bootloader again, and keep it. you trying to downgrade it might be the issue. btw, i flashed m, and the bootloader, via twrp recovery, its much easier and faster that way. after, i made a backup in recovery. so now all i do to go back and forth is restore the backups.
Click to expand...
Click to collapse
I think that's where I messed up from the beginning when I flashed M.
I didn't notice the modified boorloader that doesn't force encryption and it was all downhill from there.
That being said,
Should I flash modified boorloader to not force encrypt, and blah blah blah?
Sent from my Nexus 6 using XDA Free mobile app
Disregard
sookieball said:
I think that's where I messed up from the beginning when I flashed M.
I didn't notice the modified boorloader that doesn't force encryption and it was all downhill from there.
That being said,
Should I flash modified boorloader to not force encrypt, and blah blah blah?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
moddified bootloader? huh? there is a modified kernel thats not supposed to force encryption. i did flash it, even though i am encrypted(by choice).
http://forum.xda-developers.com/showthread.php?p=61027468
I'm assuming that's what this is.
Lol I never tried or even downloaded it so not 100% but yeah
Lol **** my bad. Lol its boot.IMG not boorloader hahaha! #nooberror for reals lol
Sent from my Nexus 6 using XDA Free mobile app
sookieball said:
http://forum.xda-developers.com/showthread.php?p=61027468
I'm assuming that's what this is.
Lol I never tried or even downloaded it so not 100% but yeah
Lol **** my bad. Lol its boot.IMG not boorloader hahaha! #nooberror for reals lol
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
thats probably the same one i flashed. btw, in the op he has a twrp flashable version of the bootloader, the kernel, the radio, and the rom.. http://4ndr01d.com/repos/shamu/jdx/
simms22 said:
thats probably the same one i flashed. btw, in the op he has a twrp flashable version of the bootloader, the kernel, the radio, and the rom.. http://4ndr01d.com/repos/shamu/jdx/
Click to expand...
Click to collapse
God I wish it was a faster download link -_- lol
BTW, when I first downloaded and flashed boorloader via twrp (radio also) rebooted twrp to flash ROM, and sdcard was wiped
It shouldn't do that right?
Sent from my Nexus 6 using XDA Free mobile app
sookieball said:
God I wish it was a faster download link -_- lol
BTW, when I first downloaded and flashed boorloader via twrp (radio also) rebooted twrp to flash ROM, and sdcard was wiped
It shouldn't do that right?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
no, it shouldnt unless you accidentally did it yourself. ive seen people do that too often. if you go into the wipe menu, be sure to go into advanced options, where you can pick what you want wiped.or itll wipe everything.
K so everything's downloaded....
Going to flash in a sec all via twrp.
Report back .
Wish me luck lol
Sent from my Nexus 6 using XDA Free mobile app
sookieball said:
K so everything's downloaded....
Going to flash in a sec all via twrp.
Report back .
Wish me luck lol
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
fingers crossed
What cracks me up the most is people that posses limited knowledge about fastboot flashing partition images are just seemingly willy nilly flashing images not really fully understanding what they are doing/flashing. We all have to learn somehow but I wouldn't do it at the expense of flashing a boot loader. If anything went wrong during a boatloader flash you would definitely have an unrecoverable hard brick.
Moral of the story.... People, read the how to's and SLOW down... Think about what you are doing. After reading the above replies its clear to me that people are getting a bit confused with a boot.img and a bootloader.img. its OK guys. Just be careful