Jump to content


Photo

Having issues with flashing recovery


  • Please log in to reply
2 replies to this topic

#1 xopilax

xopilax

    n00b

  • Members
  • Pip
  • 2 posts

Posted 25 October 2014 - 03:29 PM

     I am running an xt926 on KitKat 4.4.2  V183.46.10.  Recently, I rooted with towelroot and used the console command version of motopocalypse to unlock.  All went well and I saw no errors.  In fastboot it states code 3 and that I am indeed unlocked. 

 

  Directly following this, I downloaded the CWM apk and installed it, then, after renaming the default recovery recovery files via ES file explorer, flashed the vanquisher edition of CWM recovery.  Upon reboot into recovery, I get the motorola (Dual core technology) spash as if I were booting up normally, but it persists for minutes.  Eventually it reboots and the phone boots into the os.  I have tried flashing TWRP, as well as the stock recovery but it behaves the same way.  Also, I have tried flasing through the CWM app.  All of these methods state that they are successful but the result is the same: a nonexistent recovery.

 

  It should be noted that I have all of the appropriate drivers, including motorola's and adb, I have a proper root with updated SuperSU binaries, and have accepted the PC and am considered authorized, as shown by adb. I am also using the OEM usb adapter.  Another item worthy of mention is that I have never received the telltale "bootloader unlocked" warning splash screen on bootup.  I can only confirm that it is unlocked through fastboot mode, which works perfectly.  I don't know if this is significant.

 

  I am at my wit's end with this one.  Can anyone here please shed light on this for me?  I am afraid to take any further steps until I have a functional recovery.  Any help is greatly appreciated.



#2 livinginkaos

livinginkaos

    I don't know what I'm doing anymore.....

  • Administrator
  • 15,104 posts
  • Google+:Hangouts - livinginkaos@gmail.com
  • LocationOregon
  • Current Device(s):Samsung S8+ / Pixel XL 128gb / iPhone 7+ 256gb / iPad Pro 12.9" / Samsung Chromrbook Plus / Pixel C / Nexus 6p 128gb / Nexus 6 / Nexus 6 on Fi / Nexus 9 / Moto 360^2 / Nvidia Shield TV Pro / Nvidia Shield Tablet / HTC EVODesign on FreedomPop / Chromecast / Surface Pro 3 i7 / Samsung Tab Pro 12.2 / Lenovo Win8 Tab / Eee Slate / '13 Nexus 7

Posted 25 October 2014 - 03:35 PM

Make sure you have the proper versions for kk. If you are rooted, just use flashify.

sent from my G3


b2wvCBn.png

Sig by livinginkaos
Samsung S8+ / Pixel XL 128gb / iPhone 7+ 256gb / iPad Pro 12.9" / Samsung Chromrbook Plus / Pixel C / Nexus 6p 128gb / Nexus 6 / Nexus 6 on Fi / Nexus 9 / Moto 360^2 / Nvidia Shield TV Pro / Nvidia Shield Tablet / HTC EVODesign on FreedomPop / Chromecast / Surface Pro 3 i7 / Samsung Tab Pro 12.2 / Lenovo Win8 Tab / Eee Slate / '13 Nexus 7


#3 xopilax

xopilax

    n00b

  • Members
  • Pip
  • 2 posts

Posted 25 October 2014 - 04:01 PM

THAT WAS IT!  I had no idea there was a kk specific version!  You are my hero, sir.  My whole reason for having done this is to get back to jellybean.  I simply want to be able to pair HIDs to it to play emulation games and the bluetooth stack, as you surely know, is terribad as of late.  Specifically, I am using a WiiU controller which is confirmed to function. 

 

Will I be able to maintain this recovery if I roll back to JB?  Also, does anyone see an alternative to going that far back in OS software?  I would prefer to not have to, as I do adore staying up to date, but my portable gaming is a bit more important.  ^^

 

  Regardless of all this, I appreciate the help.  You have no idea, how much.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users