[Q] Custom Recovery Only Works By "fastboot boot" topic

SOCIALIZE IT ⇨

I, like others, seem to have an XT1064 (US) hosed by an OTA update to Lollipop. After getting endless com.process.xxx errors, the phone is unusable. I've tried all of the usual fixes -- clear cache, reset, etc. -- but I'm undaunted: unlocked the bootloader and thought I'd install a custom recovery before either restoring the stock ROM or installing one of the many fantastic ROMs posted here (Titan Prime looks great).

There is a hangup: custom recovery will not flash to sd. Fastboot says OKAY after flash operation, but the phone then boots only to the stock recovery ("Android system recovery <3e> LXB22.46-28") after the "no command" screen. Fine, whatever, I can do a "fastboot boot <recovery.img>" but nearly every recommended image (like TWRP2.7.1.1-titan-motog-2014.img for instance) do not boot -- instead it gives a flickering motorola logo). Thankfully, a custom recovery that would not seem to match version does work this way (the "philz_touch_6.58.7-falcon-unofficial.img"). However neither it nor any other will flash to sd. Any suggestions?

Before going on to another ROM I'd feel better if I had a solid recovery in place. It looks like Titan Prime wants TWRP, but I haven't been able to install it. Is this going to be a problem or will a "soft boot" of PhilZ work?

I'm also concerned about my bootloader version -- I haven't been able to deduce if I've got the right one for Lollipop-based ROMs. Fastboot says "AP Fastboot Flash Mode (S) 48.82(*) (sha-e004609, 2014-12-19 14:35:02)"

Any advice from the gurus here is much appreciated!

xda-developers


0 commentaires:

Enregistrer un commentaire