Related
SEE MY NEXT POST! I Got it, but it boot-loops.
My Friend said his Droid forgets contacts, is loosing texts & was acting up after the 2.2 software update so Verizon replaced it. But only took the battery so he still has it. I could wipe, root, n install CM6 and most likely get it running good right. I'm thinking after a radio and OS reinstall it might be ok.
Is $50 worth it. Where can I get an originally battery? And will the phone still work if I call and register it on another Verizon account?
Thanks for any help.
So worth it....ebay
OK, so I got the Droid and I have it home. I got a battery cover and battery from my friend at verizon.
So, what Recovery options are there for the Droid. I don't know anything about the droid. I've always done things on my Nexus One only. I tried holding X while booting and this is the screen I get
http://twitpic.com/2lpio0
and this Droid has an endless boot-loop. I'm not sure whats wrong atm. or what verizon may have tried to do to fix it for the customer. What should be my first move. How can I boot into the stock recovery and do a factory wipe?
Update. I've loaded SPRecovery ESE81 while following the Cyan Wiki for the Droid. I've tried a Full Wipe, and Cache wipe. It still does an endless boot-loop.. I'm not sure what my next move is from here.
I was going to keep following the Cyan Wiki for the Droid and install the rooted ESE81.update file from the Wiki. But that is 2.1 and I'm pretty sure the phone has 2.2 So the radio's wouldn't match. Or would flashing the ESE81 file from the wiki also do the radio? (if so from there I'd be rooted and can flash some CM6 like I have on my Nexus One). I'm not sure what to do next. I don't know how messed up it is, or what all Verizon did. but for now it boot-loops, and it has SPRecovery ESE81 on it.. What should I do next. What steps should I take?
Thanks for any help!
*Update - I've learned Droid doesn't have Radio mis-match problems. thats only GSM phones, so from here I should just flash the rooted ESE81 and from there flash CM6 right?
double post
Well, something messed up here. I was able to load 2.1 on the phone it booted once, seemed fine and on reboot I'm back to boot loops all over again, tried wipe and reflash. Same thing. I then flashed CM6.0-Droid and now I get the CM boot animation, but it still is having a boot loop. I'm not able to get it to boot into the system other than that one time. WTH.
idea's? oh and how do I charge the Droid without it turning on, when I plug it in, it boots. (N1 doesn't do this)
Try using RSDlite to flash ese81 while in the bootloader screen. (Bootloader - power and up on d-pad)
Sent from my Droid using XDA App
xguntherc said:
idea's? oh and how do I charge the Droid without it turning on, when I plug it in, it boots. (N1 doesn't do this)
Click to expand...
Click to collapse
that is a crazy issue with Motorola. I don't know why they do like that.
my solution is ... charge the battery using external charger
As a quick FYI, I've returned two rooted Revolutions to Verizon with clockwork and both went through just fine. Anyone been charged for returning a rooted phone?
Sent from my VS910 4G using XDA App
returned my bricked rooted+rom'd LG ally without a problem.
Does anyone have the bloatware that came with this device? I will be shipping back my revo to Verizon in exchange for another phone, and I'm back on the stock room, but I'm missing bloatware. Also, how can I get the stock boot image back? I think they'll realize I was rooted when they see the Droid boot animation lol .
Samsuck said:
Does anyone have the bloatware that came with this device? I will be shipping back my revo to Verizon in exchange for another phone, and I'm back on the stock room, but I'm missing bloatware. Also, how can I get the stock boot image back? I think they'll realize I was rooted when they see the Droid boot animation lol .
Click to expand...
Click to collapse
If you have a back up from when you first rooted it should give you the stock boot.img. Then flash the stock rom found in the dev section. Then using revotoolkit.apk reinstall stock recovery. Then gingerbreak to unroot. Then update to zv6 from the about phone area and you should be good to go.
Sent from my VS910 4G using xda premium
crap...
I formatted my SD card recently, and kept my latest backup , but not my original
Is there anything I can do in regards to the boot.img?
Could someone be kind of enough to make a CWR zip file for me?
I'll even pay you $5 bucks or whatever sounds good.
Samsuck said:
crap...
I formatted my SD card recently, and kept my latest backup , but not my original
Is there anything I can do in regards to the boot.img?
Could someone be kind of enough to make a CWR zip file for me?
I'll even pay you $5 bucks or whatever sounds good.
Click to expand...
Click to collapse
My recommendation would be to flash this: http://forum.xda-developers.com/showthread.php?t=1129117
If it gives you the option to update, perhaps you should try that, and it may unroot your phone.
As far as CWM, I doubt the clerks are going to play with recovery... (that's not a guarantee, however).
If you are really desperate and scared, you should use the VZW tool for reflashing the phone, but I AM NOT RECOMMENDING IT. The tool has been known to do bad things to phones that need expert help to undo if not done properly (not only that, it's a pain in the arse).
Can I flash the boot image from that nandroid?
I was going to use the tool to run the downgrade again but I keep getting errors that I was not getting when I first rooted the phone. Mostly .msi installer package errors when selecting the .tot file.
If its in there it should be fine. If not i can make a zip of the stock boot.img when i get home but it will be about 7 central time.
Sent from my VS910 4G using xda premium
Samsuck said:
Can I flash the boot image from that nandroid?
I was going to use the tool to run the downgrade again but I keep getting errors that I was not getting when I first rooted the phone. Mostly .msi installer package errors when selecting the .tot file.
Click to expand...
Click to collapse
I don't think the boot image was included with the earlier ROMs. I *probably* have a few boot images from when I was working with Cubed on CWR, but I don't know which is which, and some of those actually can cause bricks. Boot image was p8? I don't even remember now.
As far as selecting the .tot file, it requires the support files... They come with the LGNPST Store & Lab... they would look like:
LGNPST_GenericModels_Ver_3_0_17_0.msi
I'm not positive which one is the right one as it's been a long time. Sorry this is vague, but I went through the process once, and then never again.
The person whose phone we recovered through this method had an issue after the flash where everything looked kosher, but the data would no longer work (no 3g, 4g, etc), and required Cubed's intervention to repair. So I haven't touched it since.
-mtmichaelson, thanks man, i'll just wait for you to be safe! I can wait. I'll buy you some brewski's.
-Majorpay: Yeah, I'm not too sure I want to play around with that program lol. It worked perfectly when I first rooted the phone, although I had to manually register the .dll but now it doesn't work at all.
Thanks again for all the help guys! ****, you guys have great support for this small Revo community.
Samsuck said:
-mtmichaelson, thanks man, i'll just wait for you to be safe! I can wait. I'll buy you some brewski's.
-Majorpay: Yeah, I'm not too sure I want to play around with that program lol. It worked perfectly when I first rooted the phone, although I had to manually register the .dll but now it doesn't work at all.
Thanks again for all the help guys! ****, you guys have great support for this small Revo community.
Click to expand...
Click to collapse
Alright, here you go! Let me know if there are any problems!
http://www.multiupload.com/X1DIJDNPCV
thanks man! worked perfectly. sent some money your way.
Samsuck said:
thanks man! worked perfectly. sent some money your way.
Click to expand...
Click to collapse
Thank you kind sir!
Sent from my VS910 4G using xda premium
Does anyone have a backup of 6.893?
Typically I am very diligent, but somehow I forgot to make a backup of stock.
I have not switched to any other update. I have read through everything thoroughly and I apologize for failing to follow instructions. With 5 android devices and multiple flashes I have never missed this before. And I realized it as soon as I flashed TH3ORYS rom
From what I gather the easiest and most effective way to get back on track is to flash a stock 6.893 rom make a backup and move on from there.
I appreciate anyone's help!
I am also open to using this thread or creating one in delopment to post the stock roms of every version.
Sent from my DROID BIONIC using xda premium
http://forum.xda-developers.com/showthread.php?t=1279825
Restore the system apps and you'll be back to square one.
Mustang02 said:
http://forum.xda-developers.com/showthread.php?t=1279825
Restore the system apps and you'll be back to square one.
Click to expand...
Click to collapse
Not entirely true. His system will be back to 5.5.886, but his kernel/radio will be his previously upgraded 5.6.893. He is off the upgrade path until he gets the matching system file of 5.6.893. Only then can he continue updating. I just went through this exact thing, used the one step recovery, but went back to .886 and had to beg to find someone to send me a CWR back up of their 5.6.893, which got me back on track.
Oh yeah...nevermind. I completely thought you were wanting stock not the ota. That's what I get for speed reading.
stevessvt said:
Not entirely true. His system will be back to 5.5.886, but his kernel/radio will be his previously upgraded 5.6.893. He is off the upgrade path until he gets the matching system file of 5.6.893. Only then can he continue updating. I just went through this exact thing, used the one step recovery, but went back to .886 and had to beg to find someone to send me a CWR back up of their 5.6.893, which got me back on track.
Click to expand...
Click to collapse
You don't still have this do you? Because I am not above begging!
Sent from my DROID BIONIC using xda premium
I'm afraid I dont, I got back to 5.6.893 then immediately upgraded to 5.7.893 and backed that up, since .6.893 was no good to me any more. I'm sorry.
Someone out there has to have this!
....I hope
Sent from my DROID BIONIC using xda premium
Give this a try. (Can't post links yet)
rootzwiki.com/topic/8562-easily-upgrade-to-57893-and-keep-root/
I'm thinking you will only need steps 1 and 2.
Hope it helps!!
ripper2860 said:
Give this a try. (Can't post links yet)
rootzwiki.com/topic/8562-easily-upgrade-to-57893-and-keep-root/
I'm thinking you will only need steps 1 and 2.
Hope it helps!!
Click to expand...
Click to collapse
Wont it fail because I'm not coming from stock? And if I go all the way back it wont work because ill end up with a hybrid?
Sent from my DROID BIONIC using xda premium
I'm in the same situation. Yes, all attempts to upgrade fail because our sys filed don't match our radio. I need this nandroid as well.
Sent from my DROID BIONIC using Tapatalk
Giving someone a backup made on your device or restoring a backup made on someone else's device is an extremely foolhardy proposition. You are cloning the Android_id from one device to the other, which means that apps that use it as an identifier will push and pull data from both devices without any intervention from the unknowingly affected user.
system img
correct me if im wrong but, all we need is the system img right because im stuck with a hybrid
Does anyone know if restoring my 5.893 back up will work, or create a hybrid? I ask because I think it is the same radios?
Sent from my DROID BIONIC using xda premium
If anyone is just now rooting and starting to make their way up the update ladder I would greatly appreciate it if you would make a backup of 6.893 and send it to me. Thank you!
Sent from my DROID BIONIC using xda premium
Dakota0206 said:
If anyone is just now rooting and starting to make their way up the update ladder I would greatly appreciate it if you would make a backup of 6.893 and send it to me. Thank you!
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Check your pms and please don't share in case there is some of my data still left in the backup. just download all the files and put them in a folder and put in your clockwork backup folder on your sd/ext, probably the best way is to restore with advanced restore and just restore system only.
rgb2448 said:
Check your pms and please don't share in case there is some of my data still left in the backup. just download all the files and put them in a folder and put in your clockwork backup folder on your sd/ext, probably the best way is to restore with advanced restore and just restore system only.
Click to expand...
Click to collapse
Mad thanks!
Sent from my DROID BIONIC using xda premium
Dakota0206 said:
Mad thanks!
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Let me know if it works or you need some more help
I'm in the same boat here too. I hope someone can find a way to fix it soon. I'd really appreciate a backup too, but I understand the concern about data.
Calla969 said:
I'm in the same boat here too. I hope someone can find a way to fix it soon. I'd really appreciate a backup too, but I understand the concern about data.
Click to expand...
Click to collapse
What steps have you done already. and what is your current system and what updates have you done.
rgb2448 said:
Let me know if it works or you need some more help
Click to expand...
Click to collapse
rgb2448 said:
What steps have you done already. and what is your current system and what updates have you done.
Click to expand...
Click to collapse
I have really been through the ringer today. I started off this morning by noticing that I had no data at all. I was on 6.893 and TH3ORYROM 2.1 and have been for a few days with no trouble until today when I lost data. I tried everything to get it back, but nothing. I called VZW to make sure there wasn't a network problem in my area and they suggested that I try everything that I had already done (bat. pull, sim card re-register, turn off LTE radio, etc). When they couldn't fix anything, they wanted to transfer me to tier 2 tech support, but they apparently need to talk to me on a different phone so they can diagnose this one, but I didn't have access to another phone. So I decided I would try to flash one of the updates hoping it would reflash the radio file and wake it up. When I got home, I used the R3L3AS3DRoot to restore to stock and tried to install 7.893, but the update failed. I searched around and tried every method I could to get any of the updates to install, but nothing worked, still no 3g either. Eventually, in my desperate attempt to fix this myself I decided to wipe everything and start over. I wiped the webtop partition. I think that's what really screwed me up, because nothing else I did was any different that what I've done in the past. After wiping everything, I went back to the R3L3AS3DRoot and tried to run it. No matter which option I selected, it seemed to run fine, but I couldn't boot past the fastboot screen. I tried to fxz using RSD Lite, but every flash I tried failed. Then, in a panic, I came across P3's moto-fastboot method used to "get you back on the update path". I ran that and it freaking worked!! Then I figured I'd try to get up to 7.893, but I've tried absolutely everything I can find mention of and nothing works. Every install fails. I am getting some intermittent 3G now though. And to top it all off, I discovered that none of the nandroid backups I've made will restore and most of them don't even exist. I just discovered that I needed to check "use external storage" for the backups to take. I thought I had been covering my ass by making backups, but they weren't valid. Currently I have stock, rooted phone with an intermittent 3G signal. System Version 5.5.886, baseband CDMA_N_03.1C.57RLTEDC_U_05.15.02, kernel [email protected] #1, and build number 5.5.1_84_DBN-55. As I sit now, my plan is to see how it acts tomorrow and if I still have a lot of trouble with data, I will return it to stock unrooted and take it into a Verizon store and see if they will let me try a new SIM card. I don't really know what else to do at this point.
I think I understand how safestrap works (it installs some kind of hijack to boot /preinstall instead of booting /system) but I have been reading a number of users who have bricked their phone...
I basically have the SafeStrap install screen up, but am hesitant to do this...
Just a few questions before I take the plunge
1) Why are so many users having problems with safesrap? I download the Droid3 version 1.08 for use on my Bell Motorola XT860 4G
2) What exactly does safestrap do in the boot loading sequence? If this is not public knowledge (and might be worked out "against" please, no harm, I'm just wondering, so if I could get an idea as how the hijack works, either in the thread or PM that would help greatly)
3) If you restore the original system and disable the hijack, will that really bring me back to complete original stock? What if they patch the boot partition as they did last time?
Thanks for all your help guys! I know a lot of you have been using custom roms, I really want to load up ICS on here, and it's almost ready for prime-time so I just want to be prepared!
First off, I have an XT862 not the XT860. The hijack is a 2nd init hijack. Safestrap does this hijack itself as opposed to with bootstrap where whatever ROM you flash has to do the hijack. Safestrap also as you mentioned uses /preinstall to store /system of the ROM you flash. This means that nothing other than safestrap itself touches your stock /system. This allows safestrap to protect itself so you can always get back to recovery even if there is a bad flash it can't overwrite the hijack and recovery so you can try again.
I also don't remember seeing much of problems with safestrap itself other than a partition size problem. I think I remember seeing that some update took care of that problem. I have seen people having more problems with ROMs on the XT860 than other versions of the phone.
danifunker said:
I think I understand how safestrap works (it installs some kind of hijack to boot /preinstall instead of booting /system) but I have been reading a number of users who have bricked their phone...
I basically have the SafeStrap install screen up, but am hesitant to do this...
Just a few questions before I take the plunge
1) Why are so many users having problems with safesrap? I download the Droid3 version 1.08 for use on my Bell Motorola XT860 4G
2) What exactly does safestrap do in the boot loading sequence? If this is not public knowledge (and might be worked out "against" please, no harm, I'm just wondering, so if I could get an idea as how the hijack works, either in the thread or PM that would help greatly)
3) If you restore the original system and disable the hijack, will that really bring me back to complete original stock? What if they patch the boot partition as they did last time?
Thanks for all your help guys! I know a lot of you have been using custom roms, I really want to load up ICS on here, and it's almost ready for prime-time so I just want to be prepared!
Click to expand...
Click to collapse
First off, the most common problem I have seen people have with safestrap is not understanding what it does and even more common is not knowing how to use it, basically a lot of user error. The previous poster summed up pretty well how it works. Finally, uninstalling safestrap will NOT bring you back to original stock, it will remove itself and the secondary ROM it allowed you to install. Since you have to be rooted to even install it, if you uninstall it you will still be rooted, not stock.
Just so you are clear, you can have whatever ROM you want on your phone BEFORE installing Safestrap and this will become the Safe system by default. You will no longer be able to change this ROM as long as Safestrap is installed. Instead, it allows you to put another ROM, basically a dual-boot, in addition to the original rom you have. Now you have a Safe system and a Non safe system. The Non safe system is the only one Safestrap will allow you to change (and brick for that matter). So if/when you install a ROM that boot loops or crashes, you simply can revert back to your safe system and now your phone works again, neat huh?
AFAIK, he does have the XT860, since the XT862 is the Verizon Droid 3 (3G, not Bell Canada 4G). Also, using it on my 862, I have not been able to brick it. If flashing the experimental system fails, you can just reboot into the Safestrap menu and flash something new. I don't see why it wouldn't work on the 860, as all it does it modify the booting. Any issues would most likely be caused by a ROM flashing issue, not safestrap.
I took the plunge this afternoon... Installed SafeStrap and CM9 nightly on my device... Not sure if everything is working just yet, but will be doing testing throughout the day
No problems were reported with the installation or instructions, so that's great. Thanks a lot!
I'm using a XT860 (Brazilian Vivo, but I'm not sure if it's 4G - LTE - compatible, I know that it works with 3.5G).
I have Safestrap 3.0.5 installed and I'm using all the 4 slots (MavROM, Minimoto, CM9 e CM10). All of then runs well (with their particular issues), none of them caused any trouble on the phone.
Thiago AmP said:
I'm using a XT860 (Brazilian Vivo, but I'm not sure if it's 4G - LTE - compatible, I know that it works with 3.5G).
I have Safestrap 3.0.5 installed and I'm using all the 4 slots (MavROM, Minimoto, CM9 e CM10). All of then runs well (with their particular issues), none of them caused any trouble on the phone.
Click to expand...
Click to collapse
Same here. I'm using it on a Brazilian TIM, no problems at all. I have two active slots( Stock, Gummy 0.90) and two for testing.
It is in fact the best recovery that I've used, so far.
Thiago AmP said:
I'm using a XT860 (Brazilian Vivo, but I'm not sure if it's 4G - LTE - compatible, I know that it works with 3.5G).
I have Safestrap 3.0.5 installed and I'm using all the 4 slots (MavROM, Minimoto, CM9 e CM10). All of then runs well (with their particular issues), none of them caused any trouble on the phone.
Click to expand...
Click to collapse
None of the d3 variants are LTE capable
Sent from my DROID3 using xda premium
Endoroid said:
None of the d3 variants are LTE capable
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
Yeah, I realize that before reviewing its radio specs.
Munckster said:
Same here. I'm using it on a Brazilian TIM, no problems at all. I have two active slots( Stock, Gummy 0.90) and two for testing.
It is in fact the best recovery that I've used, so far.
Click to expand...
Click to collapse
@Munckster
Actually, after trying to acess a SD Card partition with Link2SD, I lost acess to Recovery. I'm stuck on the stock ROM (root keeps on, but SafeStrap 3.05 doesn't work).
Installed Titanium Backup to keep my data safe, but it isn't working too. I'm going to reinstall it later.
I'm afraid that I'll have to uninstall all my root apps, unroot the phone and do all the process again...
I'm very newbie at linux and Android and I'm doing all that by reading (a lot). I'd apreciate if someone could tell how to deal with this problem.
Thiago AmP said:
Yeah, I realize that before reviewing its radio specs.
@Munckster
Actually, after trying to acess a SD Card partition with Link2SD, I lost acess to Recovery. I'm stuck on the stock ROM (root keeps on, but SafeStrap 3.05 doesn't work).
Installed Titanium Backup to keep my data safe, but it isn't working too. I'm going to reinstall it later.
I'm afraid that I'll have to uninstall all my root apps, unroot the phone and do all the process again...
I'm very newbie at linux and Android and I'm doing all that by reading (a lot). I'd apreciate if someone could tell how to deal with this problem.
Click to expand...
Click to collapse
Try shutting the phone off and powering up while holding m, then using vol down select bp tools from the list that appears, and confirm with vol up.
Sent from my DROID3 using xda premium
Endoroid said:
Try shutting the phone off and powering up while holding m, then using vol down select bp tools from the list that appears, and confirm with vol up.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
I've already tried it, but without success... I'll keep searching what to do in this situation...
Thiago AmP said:
Actually, after trying to acess a SD Card partition with Link2SD, I lost acess to Recovery. I'm stuck on the stock ROM (root keeps on, but SafeStrap 3.05 doesn't work).
Installed Titanium Backup to keep my data safe, but it isn't working too. I'm going to reinstall it later.
I'm afraid that I'll have to uninstall all my root apps, unroot the phone and do all the process again...
Click to expand...
Click to collapse
Unrooting seems like overkill. If you are "stuck" on stock, I would just start the Safestrap app. Click the button to uninstall recovery and restart the phone. Then open Safestrap again, click the button to install recovery, and restart the phone. Hopefully the Safestrap menu will show and you can then activate recovery.
So long as you do not erase anything on the internal storage, your slots should still be there.
doogald said:
Unrooting seems like overkill. If you are "stuck" on stock, I would just start the Safestrap app. Click the button to uninstall recovery and restart the phone. Then open Safestrap again, click the button to install recovery, and restart the phone. Hopefully the Safestrap menu will show and you can then activate recovery.
So long as you do not erase anything on the internal storage, your slots should still be there.
Click to expand...
Click to collapse
I've tried it several times before I came with the idea of unroot my phone and redo the process. Here is my dicoveries http://forum.xda-developers.com/showthread.php?t=2082292
I know that it's obvious, but I guess that just few people knew that it would work.
SafeStrap problems
Odd problem, I can't get the menu button to work. In order to get back to my "safe" rom I have to start safestrap,and select uninstall recovery.
Then reboot, and it will bring up my "Safe" rom. If I then go back to SafeStrap, and re-install the recovery, and reboot, it will again bring up SafeStrap, but if I hit Menu, it doesnt' bring up any options it again boots up my non-safe ROM (minimoto 1.6)
Anyone have any ideas...I guess I can try to remove the safestrap directory on the sdcard after I uninstall the recover, and then try to reinstall the App, and try all over again?
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