Database Develop

[Q] VZN Moto X DE TWRP Bootloop

i looked. i swear. however, can't find anything that addresses my issue or at least i don't recognize it at my issue.
I have a DE Moto X on VZN.
unlocked bootloader
reverted from 4.4 to 4.2.2
flashed TWRP-2.6.3.1-ghost-4.4
Everything was working just fine and i couldn't leave well enough alone. I was screwing around and tried to flash/install/whatever an apk that would invert gmail colors....basically white to black. i'm not sure if it was before or after i did that but i created a backup in case it screwed something up and i wanted to revert. well, i loaded it and nothing happened so i went to restore my device from the backup i had just created and TWRP told me it was complete/successful or something and gave me the option to reboot. i did and now my phone is stuck in a boot loop. i've tried to restore several times to no avail.
i can get into bootloader menu but normal start up starts the boot loop process again. TWRP loads if i go into recovery. phone isn't recognized by RSD Lite. not sure what to do.
Can anyone help or tell me what additional info you need to be able to help?

texaslegend said:
i looked. i swear. however, can't find anything that addresses my issue or at least i don't recognize it at my issue.
I have a DE Moto X on VZN.
unlocked bootloader
reverted from 4.4 to 4.2.2
flashed TWRP-2.6.3.1-ghost-4.4
Everything was working just fine and i couldn't leave well enough alone. I was screwing around and tried to flash/install/whatever an apk that would invert gmail colors....basically white to black. i'm not sure if it was before or after i did that but i created a backup in case it screwed something up and i wanted to revert. well, i loaded it and nothing happened so i went to restore my device from the backup i had just created and TWRP told me it was complete/successful or something and gave me the option to reboot. i did and now my phone is stuck in a boot loop. i've tried to restore several times to no avail.
i can get into bootloader menu but normal start up starts the boot loop process again. TWRP loads if i go into recovery. phone isn't recognized by RSD Lite. not sure what to do.
Can anyone help or tell me what additional info you need to be able to help?
Click to expand...
Click to collapse
So you've tried restoring your nandroid prior to the flash, and still get bootloops, right? Have you tried wiping the caches? You can also try a full wipe and see if that gets you out of the boot loop, and then you can go back and try to restore your nandroid.
If all else fails and you can get into fastboot, there are instructions here on getting back to stock: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images. I would pull my backup from the device first from within TWRP (although if you don't erase userdata it should still be on the phone). You'll have to re-flash TWRP, but that process should get you back to having a working phone.

there might also be a problem with the fact that oyu were running 4.2.2 and using twrp that was built for 4.4. there is a twrp that was built for 4.2.2 so i don't know why you used the one built for 4.4. don't know what the differences are if any that would affect running twrp 4.4 on a 4.2.2 firmware but there may be some major issues.

You could try manually deleting everything with fastboot, then boot into recovery to restore your backup before flashing the 4.2.2 TWRP.

Thanks for the help. I thought I edited my post to say I fixed the problem. Did that with a wipe from the twrp bootloader our whatever that screen is called when you not into recovery.
Thanks
Sent from my XT1060 using xda app-developers app

I am curious as to why you downgraded back to 4.2.2?

Mainly for FoxFi WiFi. I use it on road trips for my kid's iPad and Nabi.
Sent from my XT1060 using xda app-developers app

If you have an unlocked bootloader, why not use one of the available mods with 4.4?

First I guess would be because I didn't know about it. I wasn't really planning on unlocking and rooting to begin with.
I got the DE because at the time I needed a phone it was the only x I could get with 32GB.
Which mood are you talking about I might have to check it out
Sent from my XT1060 using xda app-developers app

texaslegend said:
First I guess would be because I didn't know about it. I wasn't really planning on unlocking and rooting to begin with.
I got the DE because at the time I needed a phone it was the only x I could get with 32GB.
Which mood are you talking about I might have to check it out
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
There's a flashable zip in this thread.
http://forum.xda-developers.com/showthread.php?t=2561560
It's for 4.4 not 4.2 though, don't flash it unless you update.

Make it easy on yourself and use the Xposed module http://forum.xda-developers.com/showthread.php?t=2601859

[Q]Safestrap installs but will not allow me to boot into recovery.

Hi everyone. Not sure anyone will be able to help me, but I figured I'd chance it. I also hope that I'm asking this in the right area. If not I apologize. So I got a Note 3 (AT&T) today. IN LOVE! After doing some reading I used Kingo to root. Everything went great and my phone is now rooted. To confirm this I downloaded root checker from the play store and it confirmed that my phone is definitely rooted.
After some more research I came across safestrap. For the last 2-3 hours I have been trying to install it with zero luck. Basically, after I download the 3.71 apk, installed the apk, followed the prompts and completed the installation safestrap says that the installation was complete. Unfortunately, the state: still shows not installed and I am unable to choose reboot to recovery. It's greyed out and can't be selected. Any chance that anyone knows why this is happening? I have tried just about everything that I can think of and the result has been the same every time. Sorry so long, but this is driving me crazy and I wanted to be thorough with my explanation. Thanks in advance for any help or fixes that you come up with.

thynis said:
Hi everyone. Not sure anyone will be able to help me, but I figured I'd chance it. I also hope that I'm asking this in the right area. If not I apologize. So I got a Note 3 (AT&T) today. IN LOVE! After doing some reading I used Kingo to root. Everything went great and my phone is now rooted. To confirm this I downloaded root checker from the play store and it confirmed that my phone is definitely rooted.
After some more research I came across safestrap. For the last 2-3 hours I have been trying to install it with zero luck. Basically, after I download the 3.71 apk, installed the apk, followed the prompts and completed the installation safestrap says that the installation was complete. Unfortunately, the state: still shows not installed and I am unable to choose reboot to recovery. It's greyed out and can't be selected. Any chance that anyone knows why this is happening? I have tried just about everything that I can think of and the result has been the same every time. Sorry so long, but this is driving me crazy and I wanted to be thorough with my explanation. Thanks in advance for any help or fixes that you come up with.
Click to expand...
Click to collapse
click on safestrap in your app drawer then click install recovery

Vsideo of the issue.
jerrycoffman45 said:
click on safestrap in your app drawer then click install recovery
Click to expand...
Click to collapse
I made a screen recording of what's going on. Not sure sure why I didn't I didn't do this earlier.
youtu.be/FkuiYcFFk2E

thynis said:
I made a screen recording of what's going on. Not sure sure why I didn't I didn't do this earlier.
youtu.be/FkuiYcFFk2E
Click to expand...
Click to collapse
try disabling lookout first

Same result.
Uninstalled Safestrap, Disabled and turned off lookout, and rebooted. After reboot I reinstalled safestrap and tried again. The result was the same. No install and not reboot to recovery after a supposed successful install. Would re-rooting possibly make a difference?

thynis said:
Uninstalled Safestrap, Disabled and turned off lookout, and rebooted. After reboot I reinstalled safestrap and tried again. The result was the same. No install and not reboot to recovery after a supposed successful install. Would re-rooting possibly make a difference?
Click to expand...
Click to collapse
it could lookout has been known to cause problems for kingo try unrooting and start over

Unroot, Re-root, Retry
jerrycoffman45 said:
it could lookout has been known to cause problems for kingo try unrooting and start over
Click to expand...
Click to collapse
So I unrooted using Kingo, re-rooted, reinstalled safestrap, and it is still a no go. Still the same result as the video above. Now I really don't know what to do.

I am at a loss
Sent from my SM-N9005 using Tapatalk

jerrycoffman45 said:
I am at a loss
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Let me go ahead and make it weirder. I just rooted AND installed safestrap on my wife's note 3. It worked perfectly and without any problems. The only difference between our phones, that I'm aware of, is the color. She has white and I have black.
The model number, Android version, baseband version, kernel, and build number are all the same. I would be lying if I said that it isn't making me want to cry.

Mines black and no problems
Sent from my SM-N9005 using Tapatalk

jerrycoffman45 said:
Mines black and no problems
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I'm doing a complete erase of the device now. After it's finish going to root and then *HOPEFULLY* safestrap.

thynis said:
I'm doing a complete erase of the device now. After it's finish going to root and then *HOPEFULLY* safestrap.
Click to expand...
Click to collapse
And now it seems to be stuck at the AT&T loading screen....
I can't win today.

thynis said:
And now it seems to be stuck at the AT&T loading screen....
I can't win today.
Click to expand...
Click to collapse
I booted into Odin, wiped data & caches, rebooted, installed nova launcher, rooted the phone, checked to see if it was rooted (it was), rebooted, installed safestrap.apk, opened safestrap and installed, and..... same thing..... I am now completely out of ideas. It would seem like I am destined to have no custom rom installations.

Maybe a bad download of safestrap other than that I am out of ideas
Sent from my SM-N9005 using Tapatalk

jerrycoffman45 said:
Maybe a bad download of safestrap other than that I am out of ideas
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I actually used the same download that I used on my wife's. I also downloaded earlier versions of safestrap and tried them. Much like you I am out of ideas. Is it possible to use something other then safestrap? Maybe clockwork mod and then install roms manually like I do for my nexus 7? Or is safestrap the only only option due to Knox? Also, Thank you for the help. If for some reason
I stumble upon an answer I'll let you and others know. Pretty clueless at this point though. Thanks again.

jerrycoffman45 said:
Maybe a bad download of safestrap other than that I am out of ideas
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I actually used the same download that I used on my wife's. I also downloaded earlier versions of safestrap and tried them. Much like you I am out of ideas. Is it possible to use something other then safestrap? Maybe clockwork mod and then install roms manually like I do for my nexus 7? Or is safestrap the only only option due to Knox? Also, Thank you for the help. If for some reason
I stumble upon an answer I'll let you and others know. Pretty clueless at this point though. Thanks again.

dude, my wife just got a black N3. this is not very encouraging.
good luck, hope you get it working.

It is the only way because of the locked bootloader there is a way with Odin but it is only one rom Knox raid kit kat version
Sent from my SM-N9005 using Tapatalk

smokarz said:
dude, my wife just got a black N3. this is not very encouraging.
good luck, hope you get it working.
Click to expand...
Click to collapse
I wouldn't be concerned. Whatever it is it seems that it's only my phone. I'm 99.9% positive that it has nothing to do with the color or with the black note being different.

jerrycoffman45 said:
It is the only way because of the locked bootloader there is a way with Odin but it is only one rom Knox raid kit kat version
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
That's what I figured. No biggie though. I am pretty satisfied with root and xposed framework. I've managed to delete and/or disable most of the apps that I don't use our want. I'll try to figure it out again if/when a new version of safestrap is released. Granted, I really don't think that it'll make a difference. My phone seems to have a grudge against safestrap. Oh well. Thanks again!

App Updates - VZW Moto X Dead?!

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

[q] verizon g2 with no recovery and boots to verizon screen help

Hey guys, this is my first post. I recently bought a rooted verizon G2(VS980)and i tried to flash a rom on it. Im a noob, so of course the worst happened. My phone will boot past the LG screen, but then stays at the "verizon" screen. If i try to put it in recovery(i have cwm) it just reboots. I really need a fast fix, im having to use the good ole slll until my jewl is working again. Thanks in advance

Davidmay6 said:
Hey guys, this is my first post. I recently bought a rooted verizon G2(VS980)and i tried to flash a rom on it. Im a noob, so of course the worst happened. My phone will boot past the LG screen, but then stays at the "verizon" screen. If i try to put it in recovery(i have cwm) it just reboots. I really need a fast fix, im having to use the good ole slll until my jewl is working again. Thanks in advance
Click to expand...
Click to collapse
You need to make sure your boot stack and radios are appropriate for the rom you want to flash. The G2 ROM scene is a bit fractured, since CM11 and a good chunk of derivative ROMs are still based on the 12B (4.2) OTA, but some devs are now working with the 24A (4.4) OTA.
If you can get into the bootloader/fastboot, you may be able to flash the appropriate boot stack and recovery from there, if you know what you're doing. The "cleaner" route would be to use TOT or KDZ to get back to stock, and start from scratch.
Sent from my Nexus 7 using Tapatalk

arkolbus said:
You need to make sure your boot stack and radios are appropriate for the rom you want to flash. The G2 ROM scene is a bit fractured, since CM11 and a good chunk of derivative ROMs are still based on the 12B (4.2) OTA, but some devs are now working with the 24A (4.4) OTA.
If you can get into the bootloader/fastboot, you may be able to flash the appropriate boot stack and recovery from there, if you know what you're doing. The "cleaner" route would be to use TOT or KDZ to get back to stock, and start from scratch.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
i can get my phone into download mode, but nothing more. Also, i had 12B and the rom(wich i downloaded from xda) said it was specifically for 12B.

Davidmay6 said:
i can get my phone into download mode, but nothing more. Also, i had 12B and the rom(wich i downloaded from xda) said it was specifically for 12B.
Click to expand...
Click to collapse
Did you make a backup of the rom, prior to installing the new Rom?
Sent from my GT-N5110 using XDA Premium 4 mobile app

evolishesh said:
Did you make a backup of the rom, prior to installing the new Rom?
Sent from my GT-N5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes.

Davidmay6 said:
Yes.
Click to expand...
Click to collapse
If you can't get into recovery, and only download mode, I'd probably go ahead and return to complete stock. The nice thing about this phone is it is easily rooted and rommed again if you want to do that. Plus you'll learn a lot in the process. My two cents. :thumbup:
Edit: When you return to stock, take the Ota to 4.4.2, then root.
Sent from my VS980 4G using XDA Free mobile app

[Q] Rooted/s-on. Can I update anything.

Can I install stock recovery and then try to take a ota to update. Will I loose root and will I loose my rom? Will I be able to reinstall a rom or will I need to reroot?

you can try, you shouldn't loose root or anything but once you have unlocked and flashed stuff I doubt stock recovery will like your system enough to take the update. try this http://forum.xda-developers.com/showthread.php?p=53518227
HOW Change ...... ???
Sent from my SM-T217S using XDA Free mobile app

From my understanding, as long as /system is stock, you can install the stock recovery and then take the OTA. Afterwards, you'll need to re-root your phone. Make a backup of your current setup before you get started. Once you've taken the update and get rooted again, you can always restore your backup.
Sent from my HTC device

Magnum enforcer is correct.
Sent from my 831C using XDA Premium 4 mobile app

I will give it a try this weekend and let you know how it goes.
Edit does not work but thanks for helping me.
Must be the fact that I am s on. We need that s off before we can do anything as far as updating

This one is tricky. I flashed the stock rooted rom from mikmik, I then unrooted and flashed the stock recovery via fast boot. When applying the Ota, it fails because the build.prop is not stock. Comes back with an error like /system/build.prop unexpected.

dilaynie said:
This one is tricky. I flashed the stock rooted rom from mikmik, I then unrooted and flashed the stock recovery via fast boot. When applying the Ota, it fails because the build.prop is not stock. Comes back with an error like /system/build.prop unexpected.
Click to expand...
Click to collapse
I just tried it to and did the same exact thing except I had boot loops as we'll.

when I flashed back to the stock recovery to take the recent OTA, I had a reboot bootloop like every 2-3 minutes, I was ready to throw the phone against a wall, then it hit that I read recently someone else had the same issue, and mentioned a factory reset fixing the issue, yup after a factory reset, the reboot bootloop was gone, I just now rerooted and flashed a backup
sent from HTC M8 using tapatalk

scott_0 said:
when I flashed back to the stock recovery to take the recent OTA, I had a reboot bootloop like every 2-3 minutes, I was ready to throw the phone against a wall, then it hit that I read recently someone else had the same issue, and mentioned a factory reset fixing the issue, yup after a factory reset, the reboot bootloop was gone, I just now rerooted and flashed a backup
sent from HTC M8 using tapatalk
Click to expand...
Click to collapse
But after all that we're you able to update the radio and second did it fix the signal issues?

jdmohn12 said:
But after all that we're you able to update the radio and second did it fix the signal issues?
Click to expand...
Click to collapse
yes, I was able to take the latest OTA, and no, it did not help with my signal at all, my device didn't drop calls or anything, but it has a hard time latching onto lte at times before and after the OTA.......
sent from HTC M8 using tapatalk

Do we know how to get passed the build.prop error?
Sent from my 831C using XDA Free mobile app

this might be a really stupid question (and my first post no less), but does performing a factory reset take me back to stock, unrooted form?
currently i am rooted with S-on, TWRP and Chainfire SU.
i followed a youtube video to root and im basically clueless with regards to doing anything more.
thanks in advance.

Tbaggington said:
this might be a really stupid question (and my first post no less), but does performing a factory reset take me back to stock, unrooted form?
currently i am rooted with S-on, TWRP and Chainfire SU.
i followed a youtube video to root and im basically clueless with regards to doing anything more.
thanks in advance.
Click to expand...
Click to collapse
no, a factory reset will not unroot you, you need to restore a stock backup, then flash stock recovery in fastboot to unroot while s-on
sent from HTC M8 using tapatalk

scott_0 said:
no, a factory reset will not unroot you, you need to restore a stock backup, then flash stock recovery in fastboot to unroot while s-on
sent from HTC M8 using tapatalk
Click to expand...
Click to collapse
Thank you. I saved a stock backup (i think) while rooting so ill see what i can do tonight. fastboot is the white background screen that uses volume buttons to select, right?

Tbaggington said:
Thank you. I saved a stock backup (i think) while rooting so ill see what i can do tonight. fastboot is the white background screen that uses volume buttons to select, right?
Click to expand...
Click to collapse
yes sir, power off the phone completely, hold down power and volume down, select fastboot
sent from HTC M8 using tapatalk

Hey everyone.
I've spent the better of the last three hour scouring the inter webs, Google, and these forums trying to find the answers to my questions - but to no avail (I've found partial answers, but I am afraid a partial answer could lead to a total brick).
Here we go:
I bought one of the first Sprint HTC One M8's through Amazon. Here are the details:
Model: 831C
Android Version 4.4.2
Software Version 1.12.651.17
Unlocked but S-On (Using TWRP)
Naturally, right out of the box I rooted it. However, I did not save the original ROM.
* I want to restore the phone to its original state so I can accept the OTA update and hopefully address the god-awful cell signal.
I've found a lot of stock recoveries online, but none that match 1.12.651.17.
Do I need to find that specific recovery to flash to my phone? Will another one work (e.g. 1.54.654.13)?
I've never worried about saving my stock recovery in the past (been rooting since the HTC Evo days) but it looks like not doing so finally caught up with me.
Thanks in advance.
PS I did find something 1.12.651.17 related here, but how to flash this to my phone (or whether or not it will brick) is beyond me. I've downloaded all 6 files and am waiting to figure out how the heck to get them to my phone.
http://forum.xda-developers.com/showthread.php?t=2736048