Database Develop

[Q] Crap! Rooted XT862 stuck at "dual core" boot screen after safestrap

I successfully rooted my XT862 with "DROID 3 easy root script v7.zip"
I installed Droid 3 Recovery Bootstrap and was able to reboot into CWM recovery no problem.
I did some research and decided that Safestrap would be a "safer" option than the stock CWM recovery.
So as per instructions I first uninstalled the Droid 3 Recovery Bootstrap, and rebooted just to be safe before installing Safestrap.
I installed Safestrap and rebooted hoping to see a new bootscreen that would allow me to press the menu button and get into Safestrap's recovery screen so that I could make a back up and get on with using a custom rom.
Instead I am stuck at the Motorola "dual core" boot screen.
I was able to get into the bootloader and from there into stock recovery. From there I hoped that having the stock recovery reset to factory default settings would at least allow me to get back into my phone.
Nope still stuck at the Motorola "dual core" boot screen.
I am assuming I need to get into fastboot from my boot loader and use RSDlite to flash it back to normal before I can continue.
Can someone tell me where I possibly went wrong in my process and where to find a good sfb to flash back to my phone so I can start over?
----------------------
Solved thanks to ChaoticWeaponry and his post thread over here: http://forum.xda-developers.com/showthread.php?t=1339816

Half Dead Motorola X 2nd gen XT1093 with no OS

Hi everyone
i have a motorola x 2nd gen xt1093 us cellular which i believe is in a state of coma cuz there is no OS only access to bootloader and recovery...
heres where it started
1. 5.1 was running perfectly fine but i wanted to convert to pure edition and get os 6.0
2. I unlocked the bootloader and rooted it with kingo
3. I installed twrp 3 and made a backup, it was normal
4. I restored with backup and kept getting stuck at "android is starting, starting apps"
5. I stupidly wiped everything essensially deleting the OS
here is what i have tried so far
1. flashed stock recovery and did factory reset but still cannot go beyond Bootloader Unlocked Warning
2. flashed twrp recovery again, when i enter twrp my devices shows up as media device on computer, tried copying the stock firmware zip file to device but it was too big, adb pushed the stock firmware as update.zip to device, tried installing with twrp but i get the md5 error, is there something wrong with what i downloaded? i downloaded the last one from http://motorolastockrom.blogspot.com/2016/05/moto-g-2nd-gen-stock-firmware-download_32.html does md5 error mean the download is bad? cuz i had resume several times while downloading...
3. sideload option with twrp just keeps trying to start but doesn't
4. flashed philz touch cm recovery, from there tried to sideload but it also failed
5. tried the auto flasher tool by jamesjerss from http://forum.gsmhosting.com/vbb/f78...to-flasher-root-script-v3-1-firmware-1965102/ which actually does seem to install the os from the folder but again i dont go beyond bootloader ulocked warning screen
6. tried RSD lite but it doesnt detect the device even after reinstalling the motorola device manager
please help this stupid
would greatly appreciate

i kept looking around and got the right solution
anyone with a similar experience just to go to http://forum.xda-developers.com/moto-x-2014/help/os-boot-t3384786
that solved my 36hr long misery

Droid Turbo brick

I have had my Droid turbo since launch and as such followed the path the getting root on it for some time. I used Mofo to get root back on android 4.4.4, used it again to upgrade to 5.1 while keeping root, used sunshine to unlock the bootloader when that came out, and finally installed TWRP recovery on it. I had not done much to it since, but had Intended to install cyanogenmod for a while.
Well I thought I would finally get to it this weekend. I made a nandroid back-up with TWRP, copied it to my computer, backed up some files I didn't want to lose, and went ahead and installed the latest version of cyanogenmod 13 for quark (Moto MAXX and Droid Turbo) and the necessary gapps. It all went very well. I booted into cyanogenmod just fine, and signed in to google.
I was in the process of setting things up, like preferences/wallpapers/wigets etc, while google downloaded my apps. Not long after I started doing this, nova launcher would repeatedly crash, as well as cyanogenmod's built in launcher. I got fed up with it and rebooted. But the phone shut down and started acting odd. It would show what looked like the bootloader, but the open android guy was not there, and I had no options at the top. Sometimes it would just say AP Fastboot Flash Mode (Secure) with no other text.
I got it to go to the bootloader after holding down the power and volume down button, and got it to boot to TWRP. But TWRP said there is no OS installed, and it refused to install anything, wipe anything, and TWRP itself crashed after a bit when I left it there to try and use ADB to push my nandroid back up to it.
Now TWRP will not load from the bootloader, and I cannot flash anything. I wanted to just re-flash the stock firmware. So I downloaded fresh copies of it from the root thread here on XDA, but no matter what, i get the error "(bootloader) Failed to erase partition" It does this for anything. I tried flashing TWRP and the fresh system image. I tried following the steps on the root thread that flash things that you need to prepare the phone for the system image, but all attempts to flash fail with the same message.
I also tried using mofo to flash a clean system image. But it just stops and quits at 7%. I have had this problem before, and got around it by using mofo 0.0.2. But I no longer have that version.
I am at a loss here. I need my phone back ASAP. Any help would be much appreciated.

Can't boot to recovery with Safestrap

Why can't I boot to SafeStrap recovery? If I try I just get a dead Android logo until I hard-reset. The only way to access recovery is by running SafeStrap and selecting "Reboot to recovery." That only works if I've got a working OS. If any install goes bad, I have to SBF and rebuild everything from scratch. Is this normal with Droid 4 and SafeStrap 3.75 because of the locked bootloader or is there a fix?

Seems to be a problem specific to the ROM I am using. NM!

X4 1900-1 Android One boot hangs after TWRP restore

After unlockling bootloader and rooting my spare (Blue) X4 XT1900-1 with Magisk (patched boot.img), I attempted to restore /data via TWRP (3.3.1-0 payton) from a backup taken from my other daily driver X4 (Black). Both phones are identical Android One versions on the same build PPWS29.69-39-6-2 Nov. 1 patch. This initially failed with extractTarFork() process ended with ERROR: 255. I am booting TWRP via fastboot, as I am trying to keep the phones as close to stock as possible while having root.
Apparently some of the data.ext4.win00x files in the may have been corrupt or incomplete—I had copied them from the black X4 to my PC via wifi.
I re-copied the Black X4 backup to the Blue X4 folder on SD via PC and did another restore, wiping data & cache. It completed successfully according to TWRP. This time the phone initially went into a bootloop. I tried restoring a TWRP backup taken from Blue X4 just prior to flashing /data, that resulted in the phone hanging on the Android One splash screen but not bootlooping per se. I can get the phone into fastboot, recovery and boot TWRP via fastboot. I’ve tried various wipe and restore protocols, factory reset, flashing the stock unpatched boot.emmc.win, All yield the same Android One hang. Finally tried switching from slot A to slot B (the phone recently had several updates), that gave Error changing bootloader boot slot to B. However, hitting the Back button then shows Current Slot: B. Rebooting, still hangs on Android One. Back in TWRP, changing back to slot A in TWRP gives same error message: Error changing bootloader boot slot to A.
I saw a thread of similar issues with TWRP 3.2.3-1 from 2018, but no definitive fix short of factory flash and no working way to restore only /data.
https://forum.xda-developers.com/moto-x4/help/bootloop-restore-twrp-3-2-3-1-payton-img-t3853419
No mention of TWRP 3.3.1-0 having same issues.
Wondering if the bootloader is somehow borked? Any suggestions on a fix would be great. If I could find a recent X4 factory Pie firmware to flash would that get it working again?
One thing I am unclear on is which, if any, partitions should be mounted/unmounted while TWRP restoring. I’ve done the /data partition migration before on identical devices running MM and below with no issues. This is my first soft brick in 30 or more device unlockings, rootings and ROM flashings the past 7 years. Very humbling.
TWRP log from one of the attempts attached.

Other than Pie on the X4 having 2 sets of partitions and you maybe restoring it to the wrong one, no idea.

Factory FW flash solved boot hang
KrisM22 said:
Other than Pie on the X4 having 2 sets of partitions and you maybe restoring it to the wrong one, no idea.
Click to expand...
Click to collapse
I checked that carefully before restoring, chose the active slot.
Tonight I flashed the latest factory FW and all is good, phone updating now.
The TWRP restore problem is worrisome (what good is a backup you can't restore?) Anyone else out there had bootloops after restoring a TWRP backup on the X4? I've seen posts about similar problems from 2017-2018 on several devices, but I would hope that whatever the problem was has been sorted out.

redwoodie said:
I checked that carefully before restoring, chose the active slot.
Tonight I flashed the latest factory FW and all is good, phone updating now.
The TWRP restore problem is worrisome (what good is a backup you can't restore?) Anyone else out there had bootloops after restoring a TWRP backup on the X4? I've seen posts about similar problems from 2017-2018 on several devices, but I would hope that whatever the problem was has been sorted out.
Click to expand...
Click to collapse
Glad you got it back! Dunno about TWRP - maybe a pre or early Treble problem? Scary!
EDIT: I wonder if maybe stuff like that won't really be sorted for a couple more releases when most folks will be on a full Treble.