Database Develop

Bootloop after trying to restore w/ Bootstrap

So I was trying to restore back to my stock ROM backup using the boot strap recovery. There weren't any errors during the process of restoring the image but when it was time to boot the phone up it would stay in a bootloop.
I have tried factory reset with the power button and volume buttons but it'd go straight back to the loop.
I am trying really hard to understand this whole adb thing with the sdk program but I have no idea how to use it.
Can anyone please help this noob?

Return to stock - Windows.
FAQ sticky in the Bionic Development forum.

Thanks for the reply. I'll try this out when I come home from work.
Also, I reactivated my droid x until then. Will I need to go to Verizon for a new sim card for my bionic once I can start it up again?

I don't think so, but I am not sure. Have not bootlooped yet myself or had to FXZ.

I believe you may have to go for a new SIM card. The way the Verizon explained it to me when I returned my Charge was when you deactivate from a 4G to 3G only phone, that SIM is lost. However, 4G to 4G is fine.
Wouldn't hurt to try, but a good possibility you will have to.
Sent from my DROID BIONIC using xda premium

idefiler6 said:
I don't think so, but I am not sure. Have not bootlooped yet myself or had to FXZ.
Click to expand...
Click to collapse
About 2 hours after I said this, I bootlooped. Good thing this FXZ method works!!

haha yeah with all the new roms u cant help but to explore.
btw after 5 FAILED flashes I tried one more time with rsdlite and it finally worked!
It took about 20-25 minutes for the whole process to fully boot up my phone but I am very happy and thankful for the people on this forum.
The weird thing is that when it booted up... it booted up to an old restore of UNL3ASH3D. confused but im happy its fully functioning.

You won't need a new SIM card. I did an FXZ restore after I rooted my phone, unrooted it (didn't need to have it rooted because there were no ROMs and no CWM yet) and it wouldn't let me root again so I flashed to stock and it rooted just fine. You will need to flash the radio again though (or at least I did after installing DroidTh3ory's ROM because it kept showing 3G in spots I know i had 4G, worked fine after I flashed).

Safestrap 3.05 help please.

I uninstalled the old version of safestrap, then installed the new version. I can do everything just fine (install, wipe, etc) but when I try to boot from the ROM slots, the phone just sits at a black screen.. I tried flashing Eclipse 3.0 and nothing happens.. help???
Sent from my DROID3 using xda app-developers app

Well eclipse 3.0 hasn't worked for me. The latest cm10,aokp,and aosp boot for me as well as mavrom 4.5 and axiomcs 1.0. Have u tried any other roms aside from eclipse?
Sent from my XT862 using xda app-developers app

Don't think eclipse works with new Safestrap. I have tested CM10, AOKP, AOSP, and Steel Droid. Those 4 all are "working".
Steel Droid is the most stable one i have tried so far, CM10, AOKP and AOSP all lag for me.

Hey guys,
New to Droid 3/ Milestone 3 World here.
I just bought one, actually with the 5.2.390.XT860.Brasil.en.BR version.
I'm not exacly new to flashing roms, and recoveries, but in this case I'm a little confused. Is it possible to use SafeStrap on this one? Or better go for an older version of it?
Thanks in advance.

@Munckster, as long as it is rooted you can install safestrap 3.04 and try if custom roms work for you?? but make sure you have the correct SS3 version!!

bArAbAts said:
@Munckster, as long as it is rooted you can install safestrap 3.04 and try if custom roms work for you?? but make sure you have the correct SS3 version!!
Click to expand...
Click to collapse
I was thinking about trying... Maybe during the weekend..
Thanks for the advice, man!

I took my phone back to stock (from an oldish CM9 that had been working reasonably well for me for some time) so I could install SS3. Made the mistake of letting the phone OTA update itself and then had to find a new root hack before I could get SS3 installed.
Unfortunately the OTA update has messed with the radio, as reinstalling the CM9 I've used for months gets a system where the phone app just crashes.
The kexec cm9 on hash code's download site results in a black screen for me. I have to pull the battery to get the phone back. Funnly enough the old CM9 does boot - and every thing works except the phone.
The latest CM10 does every thing I want (I can live with out the camera) BUT I can't receive calls, the phone app crashes. (But I can MAKE calls!).
This is on GSM BTW, not CDMA where I live.
So i'm busted back down to the 'stock' OS so I can use my phone as a phone
And as a new XDA user I can't post my bug report in the developer thread.

Well,
I installed the 3.0.5 version. Works like a charm! The easiest to use recovery that I ever use.
But the question is: Is it safe to downgrade it?
Sorry about the dumb question.

SS3 can be un-installed pretty easily. Boot your 'stock' OS, then use the SS3 app to remove the 'hijack' and then reboot again. No SS3. Just remember to do it from the 'stock' OS and not one of the others.
Don't do what I did with SS2 - from a non stock OS, remove SS and reboot. Ended up with a phone that never finished booting before it rebooted. Fortunately the emergency recovery mode built into the phone worked to recover it.

matthewgeier said:
The kexec cm9 on hash code's download site results in a black screen for me. I have to pull the battery to get the phone back. Funnly enough the old CM9 does boot - and every thing works except the phone.
The latest CM10 does every thing I want (I can live with out the camera) BUT I can't receive calls, the phone app crashes. (But I can MAKE calls!).
This is on GSM BTW, not CDMA where I live.
So i'm busted back down to the 'stock' OS so I can use my phone as a phone
And as a new XDA user I can't post my bug report in the developer thread.
Click to expand...
Click to collapse
Is the issue you're having that when you're speaking to people on the phone you can't hear anything and they can't hear you? Cause on CM9 there should be no issues with using it as a phone as long as you don't enable bluetooth ever or use buttons on a headset connected to your phone. I haven't tried CM10 yet so I wouldn't know too much about that. Just for some extra info to save your time do not flash Liberty or Eclipse, they don't seem to work. The newest Maverick works fine.

matthewgeier said:
SS3 can be un-installed pretty easily. Boot your 'stock' OS, then use the SS3 app to remove the 'hijack' and then reboot again. No SS3. Just remember to do it from the 'stock' OS and not one of the others.
Don't do what I did with SS2 - from a non stock OS, remove SS and reboot. Ended up with a phone that never finished booting before it rebooted. Fortunately the emergency recovery mode built into the phone worked to recover it.
Click to expand...
Click to collapse
I was going to try from the stock.
I am much more familiar with clockworkmod.
Anyway, thank you for the advice
Sent from my XT860 using xda app-developers app

[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

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] Switching from AOSP ROM (CM11) to Sense 6.0 based ROM

I'm using an HTC One (m7) and I'd like to move from CM11 nightlies to this ROM (http://forum.xda-developers.com/showthread.php?t=2502430). I've read somewhere before that there were preliminary steps I need to follow before going from AOSP back to Sense. I've tried to move to a ViperROM before and somehow ended up wiping all data (even recovery) from my phone. I'd like to prevent that. Any help would be greatly appreciated. Thanks!

I would suggest searching YouTube for QB King77
He has posted many videos that I have personally used to do things like gain s-off, relock boot loader, flash factory RUU back to stock and then the unlock via HTC dev site with links to all you would need. All you need with his videos is a little patience, they are on the money..
Best of luck and DONT WIPE INTERNAL STORAGE, no matter what.
Sent from my HTCONE using Tapatalk

All you need to do is wipe in recovery , and flash the new Rom .
Sent from my HTCONE using Tapatalk

Unfortunately I tried to switch the ROM and lost everything...again. I backed up my previous ROM first, but the install completely wiped out my recovery...again. It said the installation was successful. I did everything I feel I should have done. After the install it asked to reboot. When it rebooted, it went into fastboot and I no longer have access to anything but the bootloader. This has happened before so I know how to fix it now, but it's really annoying not knowing what exactly is happening on my phone.