Related
Hi there!
First of all, yes, I'm completely new to modding Android phones. Not so new to modding in general though, which makes me question why I made such a nooby mistake... but alas, I now have to ask what many might think to be a nooby question in order to fix said mistake.
Just as the title said, I accidentally installed CWM before flashing my phone, and am now unable to launch into Recovery Mode. I know that there's a way to get it revert it to stock recovery, but as far as I've been able to tell, there's no way to do that without going into the Recovery menu in the first place. Does anybody have an idea what I can do?
My phone can still launch to the firmware (stock firmware, but am planning on installing Cyanogenmod 11), so for now I'm alright but considering the OTHER problems I'm having with the stock firmware, I'd really like a way to get back to my installation ASAP. If I can't, I'll get to my problems with the stock FW later...
-Coover55
Coover55 said:
Hi there!
First of all, yes, I'm completely new to modding Android phones. Not so new to modding in general though, which makes me question why I made such a nooby mistake... but alas, I now have to ask what many might think to be a nooby question in order to fix said mistake.
Just as the title said, I accidentally installed CWM before flashing my phone, and am now unable to launch into Recovery Mode. I know that there's a way to get it revert it to stock recovery, but as far as I've been able to tell, there's no way to do that without going into the Recovery menu in the first place. Does anybody have an idea what I can do?
My phone can still launch to the firmware (stock firmware, but am planning on installing Cyanogenmod 11), so for now I'm alright but considering the OTHER problems I'm having with the stock firmware, I'd really like a way to get back to my installation ASAP. If I can't, I'll get to my problems with the stock FW later...
-Coover55
Click to expand...
Click to collapse
We continue in the other thread
NOTE: This was posted in the past, but I messed up the wording... probably why I didn't get help. I said that I had forgot to flash, but what I forgot to do was to Root my phone. Here's a copy-paste of my previous post, but with fixed wording.
Hi there!
First of all, yes, I'm completely new to modding Android phones. Not so new to modding in general though, which makes me question why I made such a nooby mistake... but alas, I now have to ask what many might think to be a nooby question in order to fix said mistake.
Just as the title said, I accidentally installed CWM before rooting my phone, and am now unable to launch into Recovery Mode. I know that there's a way to get it revert it to stock recovery, but as far as I've been able to tell, there's no way to do that without going into the Recovery menu in the first place. Does anybody have an idea what I can do?
My phone can still launch to the firmware (stock firmware, but am planning on installing Cyanogenmod 11), so for now I'm alright but considering the OTHER problems I'm having with the stock firmware, I'd really like a way to get back to my installation ASAP. If I can't, I'll get to my problems with the stock FW later...
-Coover55
If u remove & insert battery, & then try entering recovery mode(Home+Power keys)...u surely have accessed recovery by now
Coover55 said:
NOTE: This was posted in the past, but I messed up the wording... probably why I didn't get help. I said that I had forgot to flash, but what I forgot to do was to Root my phone. Here's a copy-paste of my previous post, but with fixed wording.
Hi there!
First of all, yes, I'm completely new to modding Android phones. Not so new to modding in general though, which makes me question why I made such a nooby mistake... but alas, I now have to ask what many might think to be a nooby question in order to fix said mistake.
Just as the title said, I accidentally installed CWM before rooting my phone, and am now unable to launch into Recovery Mode. I know that there's a way to get it revert it to stock recovery, but as far as I've been able to tell, there's no way to do that without going into the Recovery menu in the first place. Does anybody have an idea what I can do?
My phone can still launch to the firmware (stock firmware, but am planning on installing Cyanogenmod 11), so for now I'm alright but considering the OTHER problems I'm having with the stock firmware, I'd really like a way to get back to my installation ASAP. If I can't, I'll get to my problems with the stock FW later...
-Coover55
Click to expand...
Click to collapse
Which CWM version did you use? Are you running a Stock rom?
So I finally got me a sweet deal and got a second hand XT1053.
Unlocked its bootloader, then flashed T-Mobile´s 4.4.3 and finally the OTA to 4.4.4, because here in Mexico all I was able to get was 4.4.2.
Now, I want to try custom ROMs, and Ive been reading about the procedure.
As any sane person would, I want a nandroid backup before messing around. Im guessing flashing TWRP will take care of this, like it did with my LG L9, right?
Is it wise to do this on the verge of Android L being ported to our Moto X?
How difficult is it to get the phone to a fully stock state (minus the bootlader, of course)? As far as I know, I only need to flash my nandroid backup then flash the stock recovery. Is it as simple as that?
I read somewhere that flashing custom ROMs messed up with Motorola´s active display/voice control, and I assumed they meant that custom ROMs lacked these features because of their proprietary nature. Am I correct? Or does some kind of unrepairable damage will forever afflict these features, even if I get back to stock?
And lastly, what ROM do you recommend? I´d like the active display feature if possible, guess I can do without it. CM theme chooser would be nice too.
Thanks in advance, eagerly awaiting some answers before I take a step forwards.
Attached a screenshot of my phone´s info.
You are right about everything you've mentioned. Good research done for sure! ?
Do a backup with twrp. And yes, you can restore it and flash the stock recovery and you're good for the OTA.
Aosp/cm roms don't have the Moto features. But yes, you can return to stock and have them again. There's a few stick based custom roms that of course still have the features. The other roms, unless something changed, do come with some bugs unfortunately as well.
Most use stock, with gravity box for customizing.
And in case you missed it.... Never try to downgrade from 4.4.4....or you risk your device bricking. You can flash lower version custom roms, cause they won't try to change the bootloader. But don't downgrade stock firmware. Ever. ?
Enjoy!
Thank you very much!
As soon as I read this I rooted my phone, I´ll check a ROM or two before settling on one for daily use, have heard nice things about krypto´s one.
And yeah, there can never be enough warnings, I´ll treat the T-Mobile stock ROM as if it were my very first one.
One question though, the latest version of T-Mobile firmware is 4.4.3 under http://sbf.droid-developers.org/phone.php?device=0 so Im gussing I should only use my nandroid backup, right?
Thanks in advance!
no_un_bot said:
Thank you very much!
As soon as I read this I rooted my phone, I´ll check a ROM or two before settling on one for daily use, have heard nice things about krypto´s one.
And yeah, there can never be enough warnings, I´ll treat the T-Mobile stock ROM as if it were my very first one.
One question though, the latest version of T-Mobile firmware is 4.4.3 under http://sbf.droid-developers.org/phone.php?device=0 so Im gussing I should only use my nandroid backup, right?
Thanks in advance!
Click to expand...
Click to collapse
Until there's a 4.4.4 SBF, yes. That's the safest bet.
newbie needs details
no_un_bot said:
So I finally got me a sweet deal and got a second hand XT1053.
Unlocked its bootloader, then flashed T-Mobile´s 4.4.3 and finally the OTA to 4.4.4, because here in Mexico all I was able to get was 4.4.2.
Now, I want to try custom ROMs, and Ive been reading about the procedure.
As any sane person would, I want a nandroid backup before messing around. Im guessing flashing TWRP will take care of this, like it did with my LG L9, right?
Is it wise to do this on the verge of Android L being ported to our Moto X?
How difficult is it to get the phone to a fully stock state (minus the bootlader, of course)? As far as I know, I only need to flash my nandroid backup then flash the stock recovery. Is it as simple as that?
I read somewhere that flashing custom ROMs messed up with Motorola´s active display/voice control, and I assumed they meant that custom ROMs lacked these features because of their proprietary nature. Am I correct? Or does some kind of unrepairable damage will forever afflict these features, even if I get back to stock?
And lastly, what ROM do you recommend? I´d like the active display feature if possible, guess I can do without it. CM theme chooser would be nice too.
Thanks in advance, eagerly awaiting some answers before I take a step forwards.
Attached a screenshot of my phone´s info.
Click to expand...
Click to collapse
hello, i a newbie to all of this
i have the same device as yours, how did you do that? details if it not much trouble
sherif2015 said:
hello, i a newbie to all of this
i have the same device as yours, how did you do that? details if it not much trouble
Click to expand...
Click to collapse
Hi there, Im at work and cannot explain in much detail, but when I get home i will help you out.
You can send me a private message if you want me to explain in español.
no_un_bot said:
Thank you very much!
As soon as I read this I rooted my phone, I´ll check a ROM or two before settling on one for daily use, have heard nice things about krypto´s one.
And yeah, there can never be enough warnings, I´ll treat the T-Mobile stock ROM as if it were my very first one.
One question though, the latest version of T-Mobile firmware is 4.4.3 under http://sbf.droid-developers.org/phone.php?device=0 so Im gussing I should only use my nandroid backup, right?
Thanks in advance!
Click to expand...
Click to collapse
SBF.Droid-Developers.org hasn't been updated in a while, at least as far as the X (2013 or 1st Gen edition) Roms.
Another possible source is -> http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1 however, they don't have a 4.4.4 SBF for the XT1053 either.
And you can keep an eye on https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images since Moto should post the 4.4.4 SBF for the Developer Editions. Eventually an XT1053 (GSM) and an XT1060(VZW) 4.4.4 should pop up there, whenever Moto finally gets around to it.
no_un_bot said:
Hi there, Im at work and cannot explain in much detail, but when I get home i will help you out.
You can send me a private message if you want me to explain in español.
Click to expand...
Click to collapse
Hi sorry for bothering you but i really need your help.
English will be fine .
other users might get here so it will be nice to help them as well
thanks for your time
sherif2015 said:
Hi sorry for bothering you but i really need your help.
English will be fine .
other users might get here so it will be nice to help them as well
thanks for your time
Click to expand...
Click to collapse
Alright, guess everything is out there but I don´t mind.
Can you tell me what system version have you got?
Its displayed under Settings > About phone
reply
no_un_bot said:
Alright, guess everything is out there but I don´t mind.
Can you tell me what system version have you got?
Its displayed under Settings > About phone
Click to expand...
Click to collapse
Kitkat 4.4.2 xt1053
same phone, problems loading roms
I have the same phone, I also recently got second hand.
Moto x xt1053 (gsm) carrier unlocked, currently in kitkat4.4.2, running Kangakat 2 rom (came with it), unlocked bootloader, rooted and using SuperSU, newest version of twrp like 2.8 or something like that.
I want to load a custom rom but am having problems, downloaded P.A.C. and AOKP (two i have tried to use) for the device msm8960 using there stable versions not the nightlies. Went into twrp, created backup, factory wiped, flashed rom and g-apps, was "successful" no errors but on reboot of phone it gets stuck in boot loop and won't start up. for the P.A.C i was able to get into twrp and reflash my back up, for the AOKP twrp kept getting stuck on that teamwin image and i could only finally access it by having the usb cable plugged into my computer. I am not a noob, but definately not an expert.
So did you have any luck flashing a new rom to your phone? Does anyone have any advice for me? I really would like to try some different roms.
Thanks
[emoji15]
I hate Tapatalk for all the time spent writing a quick reply and its gone.
Anyways, first of all, make sure you have the latest recovery available, I remember back with my old phone, funky installations happened if you weren't on the latest recovery. I recommend philz one, has support for some pesky partitions that sometimes get messed and other recoveries won't back up.
Now, in my particular case, I first upgraded my 4.4.2 Nextel stock to 4.4.3 T-Mobile stock using RSDLite, then took the OTA to 4.4.4, and until then I figured I'd play with ROMs. Have had no issues other than something I've addressed on another thread and I ultimately fixed.
My suggestion is going back to full stock then doing everything yourself so you know what's actually going on.
You'll have to flash a custom recovery and then root it again but with an unlocked bootloader that's ezpz.
Remember never to downgrade (that is, flashing a lower android version than what you currently run) stock official images (such as the ones from sbf-developers) because you WILL brick your phone. People say you can downgrade when flashing custom ROMs but I wouldn't risk it, and I don't really see why I'd want that.
Double check whatever file you'll try to flash, always use stuff intended for your model, and when that's not possible verify if other users with your model have reported it works for them. As per the version thing, I believe the most recent development unified models under the GHOST parameter but take my words for what they are, that is, my view on things, you should always make one for yourself.
Ask if you don't completely understand a step BEFORE doing it, there's good people willing to help you out.
Best of luck.
My title was abit too long, cause it was copied from a reddit post I made on Cyanogenmod's reddit. R/s means "Receive or Send"
I tried going to Cyanogenmod's Reddit, asking for help with this issue, but there was no luck at all, one user did respond to me and tried to help me out, but hasn't responded for the past 3 days. Looking around for more help, I was directed here to ask. If at all, I'm doing something wrong, can you please tell me.
FYI: My Nexus 6 is using Cyanogenmod 13.0 NIGHTLY, running 6.0.1
Besides that, the reddit post is basically this:
"Please direct me in the correct area, at the moment I don't see much to go to for some help, but I felt like making post.
After a while, I've been using Bell Canada on my phone without any issues, but I never tried voicemails or calls. Recently, trying to get into my telegram account cause they won't send a SMS (For what ever reason), the app offered to call my phone, waiting for the timer to tick down before they call my phone, it just shut it's self off.
I was aware of my phone crashing due to voice mails, cause before I activated my sim card, I had a voicemail that wouldn't go away, trying to view it, the phone would crash. I was hoping this would've been fixed after a couple updates, but it doesn't seem like it was fixed at all. I can't even tell if this issue is my problem (the phone/sim card) or cyanogenmod.
If anyone knows any fixes for this, I'd be really happy, because currently my phone is useless to most things I'd use it for, other than SMS."
On the reddit post, the user that was replying to it did mention something about c-apps not being compatible with Cyanogenmod 13.0 and told me to try to uninstall it, but when I tried to uninstall it through adb, apparently such a directory doesn't exist. I do hope I can get some help here, because I'm currently on a plan with unlimited text and calls, paying alot of money for it, but one feature is completely useless.
--Something I want to add, I tried the same sim card in my HTC One M7 running Android 5.1 with Cyanogenmod 12, calls worked perfectly fine with it.
Please do correct me if I'm doing something wrong, but reading the forum rules, I don't see anything about "bumping", so... Here's my bump.
I haven't had a reply for 5 days now, the possible answer to why my topic wasn't replied to, is most likely because noone knows how to fix this or why this might be happening.
But, I do wish I could get a post or something to show that people do see this, or maybe a post telling me that my issue has a unknown fix.
Edit; I see this rule #5, but, I don't know if that applies to bumping, I don't know how else I could explain my issue. I've explained it the best I've could.
I'm on Bell, and no issues. I don't use CM or CM based Roms though, so the simple way to know if it's rom related is to flash stock, or another non CM based rom.
Other than that, not sure at else to tell you.
Darth said:
I'm on Bell, and no issues. I don't use CM or CM based Roms though, so the simple way to know if it's rom related is to flash stock, or another non CM based rom.
Other than that, not sure at else to tell you.
Click to expand...
Click to collapse
I do feel it might be rom related, because as I said in the post, I tried this with my HTC one m7, with cyanogenmod 12 nightly, not 13, and it worked.
I don't know any other Roms for Nexus 6 and cyanogenmod is the only one I know how to set up.
MoonieHorse said:
I do feel it might be rom related, because as I said in the post, I tried this with my HTC one m7, with cyanogenmod 12 nightly, not 13, and it worked.
I don't know any other Roms for Nexus 6 and cyanogenmod is the only one I know how to set up.
Click to expand...
Click to collapse
The procedure to flash any rom is nearly the same. Or use fastboot to flash a stock image.
Just do a nandroid backup before flashing another rom, to be safe. And pic an aosp rom, not cm based.
MoonieHorse said:
I do feel it might be rom related, because as I said in the post, I tried this with my HTC one m7, with cyanogenmod 12 nightly, not 13, and it worked.
I don't know any other Roms for Nexus 6 and cyanogenmod is the only one I know how to set up.
Click to expand...
Click to collapse
Look in the Nexus 6 Android Development and Nexus 6 Original Android Development subforums, there are tons of options available.
Read over this- [HOW-TO] The Nexus 6 All-In-One Beginner's Guide. A brief guide to clean flashing ROMs. Using TWRP, wipe everything except internal storage (system, data, cache, dalvik). Flash the ROM and then gapps package (some ROMs based on stock don't require gapps so look in the thread). There you go, you have a clean flash of a new ROM.
If you have issues with CM13, try ROMs based off of AOSP like Chroma, Pure Nexus, Dirty Unicorns, AOSiP, etc...
Darth said:
The procedure to flash any rom is nearly the same. Or use fastboot to flash a stock image.
Just do a nandroid backup before flashing another rom, to be safe. And pic an aosp rom, not cm based.
Click to expand...
Click to collapse
I'll keep this in mind for the near future then. I don't really want to flash a different rom on my phone cause of... Well, the known risks of doing so aka possibly turning your phone into a brick or losing all the data.
What I'll do is, I'll hold on abit with Cyanogenmod, see if they release any fixes and go from there, maybe even bump them about said issues to see if this is known or not.
Thank you for your help though, I'm sure I'd come back here again if I needed some help again.
MoonieHorse said:
I'll keep this in mind for the near future then. I don't really want to flash a different rom on my phone cause of... Well, the known risks of doing so aka possibly turning your phone into a brick or losing all the data.
What I'll do is, I'll hold on abit with Cyanogenmod, see if they release any fixes and go from there, maybe even bump them about said issues to see if this is known or not.
Thank you for your help though, I'm sure I'd come back here again if I needed some help again.
Click to expand...
Click to collapse
You will not "brick" flashing a rom. You can have issues, sure, but that's what the nandroid backup is for.
Honestly, if you're that worried, I'd restore the stock image and not tinker with it.
But if you leave it as is, I doubt you'll fix your issue.
Hi,
One of my friends told me not to do OTAs beta updates because it could bootloop my phone.
Last update I flashed the zip and all worked perfectly fine, but I had to re-root my phone and re-uninstall annoying stock apps with titanium backup.
Now I have a question :
Is it really risked to do the update with an OTA download ?
I really don't want to re-root my phone and do all the other stuff that comes with it.
I guess there is a way to do a safe update which keeps my data with the OTA but I need a confirmation about that.
Thanks !
(Original post [here] but probably faster answers on this forum, I guess ?)
I think it is ok with official updates. I have not any issue. Just i have not rooted or etc. All stock
gioyocho said:
I think it is ok with official updates. I have not any issue. Just i have not rooted or etc. All stock
Click to expand...
Click to collapse
Thanks, but I would like to have the advice of somebody with approximatively the same setup as mine, I mean at least with a rooted op3t
If you have all stock, then I can't tell if doing the OTA update will re-stock my phone too
I always have stock phones, because early time when i tried root, unlock btl, install twrp, change rom... sometimes there were wrong things, examle booting only logo and phone make a stone looks like, also custom roms has some bugs and on stock i am sure that everything works good. I do not understan why people starting root, change roms or etc. Use stock always and everything will be ok
gioyocho said:
I always have stock phones, because early time when i tried root, unlock btl, install twrp, change rom... sometimes there were wrong things, examle booting only logo and phone make a stone looks like, also custom roms has some bugs and on stock i am sure that everything works good. I do not understan why people starting root, change roms or etc. Use stock always and everything will be ok
Click to expand...
Click to collapse
U better off using an iPhone
To answer OP, yes you can struck in bootloop.
Remember it's beta version and not stable release.