Jump to content


Photo

RSD Flasher [BETA] WINDOWS ONLY


  • Please log in to reply
417 replies to this topic

#21 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 37,522 posts
  • Current Device(s):Pixel XL

Posted 30 June 2014 - 12:17 PM

Wait wait....you flashed KEEP DATA first, yes?  That's what flashes tz and why it failed.  UNIVERSAL is what you MUST use for downgrading.


5uWEQs7.jpg

 

Non potest esse nisi unus

 


#22 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 37,522 posts
  • Current Device(s):Pixel XL

Posted 30 June 2014 - 12:17 PM

IOW, just so we're clear, this wasn't a tool problem but a user problem.  :p  HEHEHEHE :D


  • cmh714 and strasber like this

5uWEQs7.jpg

 

Non potest esse nisi unus

 


#23 blazin616

blazin616

    n00b

  • Members
  • Pip
  • 5 posts
  • LocationBuckley, MI
  • Current Device(s):Moto Razr HD

Posted 30 June 2014 - 12:37 PM

yeah, it was me! so far its only crashed once since ive been back on jb. 

 

and heres a question of derpness. is there an fxz if i want to return to the terrible times of kitkat? 



#24 blazin616

blazin616

    n00b

  • Members
  • Pip
  • 5 posts
  • LocationBuckley, MI
  • Current Device(s):Moto Razr HD

Posted 30 June 2014 - 12:42 PM

Samuri, i tried flashing the full option first. when that didnt work i tried universal. that was the winning ticket



#25 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 37,522 posts
  • Current Device(s):Pixel XL

Posted 30 June 2014 - 12:52 PM

yeah, it was me! so far its only crashed once since ive been back on jb. 

 

and heres a question of derpness. is there an fxz if i want to return to the terrible times of kitkat? 

 

There is, yes.  The 183 FXZ is posted in the appropriate forum for your HD.  You'll be able to use the KEEP DATA script for that one or you can just use UNIVERSAL again.

 

Samuri, i tried flashing the full option first. when that didnt work i tried universal. that was the winning ticket

 

AH, yea, that's definitely not good.  LOL!  For downgrading it's always the UNIVERSAL script.  But it's a learning thing and you didn't break your phone, so, lesson learned without too much pain.  I added a note in the OP so others can avoid the same fate.

 

What's great, though, is that the tool worked for you.  I assume you found it pretty easy to use?


  • blazin616 likes this

5uWEQs7.jpg

 

Non potest esse nisi unus

 


#26 sk8ingdroid

sk8ingdroid

    Member

  • Dedicated Supporter
  • PipPip
  • 71 posts
  • Current Device(s):Droid Razr MAXXX HD

Posted 02 July 2014 - 01:19 PM

I know its says usb 2.0 only but im gonna be that guy and ask if its possible with 3.0 at all? Thanks



#27 Memnoch73

Memnoch73

    ~The Devil~

  • Smod
  • 5,016 posts
  • Google+:memnoch73@gmail.com
  • LocationRochester, NY
  • Current Device(s):Pixel 3XL

Posted 02 July 2014 - 01:36 PM

I know its says usb 2.0 only but im gonna be that guy and ask if its possible with 3.0 at all? Thanks

 

Possible? maybe... Likely? probably not. We have seen a bunch of people have issues and directly related them to that. You could try it but if you have problems that's gonna be the first variable to change.


  • sk8ingdroid likes this

Bluesig3_zpsfd248ca4.png

 


#28 sk8ingdroid

sk8ingdroid

    Member

  • Dedicated Supporter
  • PipPip
  • 71 posts
  • Current Device(s):Droid Razr MAXXX HD

Posted 02 July 2014 - 01:44 PM

Possible? maybe... Likely? probably not. We have seen a bunch of people have issues and directly related them to that. You could try it but if you have problems that's gonna be the first variable to change.

ok thanks im gonna try it because I've used rsd with same 3.0 im about to use and it worked fine. I'll update what happens.


  • Memnoch73 likes this

#29 sk8ingdroid

sk8ingdroid

    Member

  • Dedicated Supporter
  • PipPip
  • 71 posts
  • Current Device(s):Droid Razr MAXXX HD

Posted 03 July 2014 - 09:46 AM

just tried this on usb 3.0 and rooted and unlocked bootloader worked perfectly.

I did have an issue using the zip file it wasnt opening it I was probably just too impatient lol. I unzipped it my self and used xml and was perfectly fine



#30 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 37,522 posts
  • Current Device(s):Pixel XL

Posted 03 July 2014 - 09:50 AM

It was opening it.  It just takes a while to unzip. So yes, impatience.  lol


5uWEQs7.jpg

 

Non potest esse nisi unus

 


#31 sk8ingdroid

sk8ingdroid

    Member

  • Dedicated Supporter
  • PipPip
  • 71 posts
  • Current Device(s):Droid Razr MAXXX HD

Posted 03 July 2014 - 10:21 AM

It was opening it.  It just takes a while to unzip. So yes, impatience.  lol

thats what I thought lol 



#32 blazin616

blazin616

    n00b

  • Members
  • Pip
  • 5 posts
  • LocationBuckley, MI
  • Current Device(s):Moto Razr HD

Posted 06 July 2014 - 11:03 AM

yes, this tool was very easy to use. absolutely awesome! thank you again for all your hard work!


  • SamuriHL likes this

#33 muppetsuppet

muppetsuppet

    n00b

  • Members
  • Pip
  • 19 posts

Posted 06 July 2014 - 06:10 PM

After using this tool and going back to JB, which worked nicely, Motorola started to push a software update. I delayed as long as I could, but then it just started pushing it to my phone. In order to stop it, I killed the app then quarantined the Updater app using an app called App Quarantine. It's worked so far. 

 

Question is, I'd like to delete the partial new OS download to free up space on my internal memory. I tried wiping the cache partition by pressing up volume, power, but I get stuck on the Andy screen with the red exclamation. Is there a different way to wipe the cache partition now? Or alternately, if I can't do that anymore, any idea where that partial download is located so I can delete it? 



#34 cmh714

cmh714

    Tech Service & Beyond

  • Smod
  • 3,272 posts
  • LocationSoCal
  • Current Device(s):Nexus 6

Posted 06 July 2014 - 06:21 PM

OTA's get downloaded to the cache folder so /cache and you can delete it or move it



#35 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 37,522 posts
  • Current Device(s):Pixel XL

Posted 06 July 2014 - 06:27 PM

You're not "stuck" on the red andy screen. Hold volume up and tap power. On the red andy screen. Sent from my SM-P600 using Tapatalk

5uWEQs7.jpg

 

Non potest esse nisi unus

 


#36 muppetsuppet

muppetsuppet

    n00b

  • Members
  • Pip
  • 19 posts

Posted 06 July 2014 - 06:32 PM

You're not "stuck" on the red andy screen. Hold volume up and tap power. On the red andy screen. Sent from my SM-P600 using Tapatalk

Yeah, I've actually done that and it doesn't do anything. I can only get out of it by pressing all three buttons. It's weird. 



#37 muppetsuppet

muppetsuppet

    n00b

  • Members
  • Pip
  • 19 posts

Posted 06 July 2014 - 06:35 PM

Figured it out. Apparently the method has changed. Once you are on the andy exclamation screen, it's actually press and hold volume down, tap volume up, release volume down. 



#38 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 37,522 posts
  • Current Device(s):Pixel XL

Posted 06 July 2014 - 06:51 PM

Um that's the old recovery method.

Sent from my SM-P600 using Tapatalk


5uWEQs7.jpg

 

Non potest esse nisi unus

 


#39 muppetsuppet

muppetsuppet

    n00b

  • Members
  • Pip
  • 19 posts

Posted 06 July 2014 - 07:11 PM

I'm on 98.30.1.xt907 JB, though I've forgotten which method belonged to which version. Either way, that's what wound up working.

#40 newmojie

newmojie

    n00b

  • Members
  • Pip
  • 3 posts

Posted 08 July 2014 - 02:08 PM

Sam (SamuriHL) - THANK YOU for all you do, I've relied heavily on your work before to tinker with my phone, and it's always saved me when things go wrong. Although now I'm afraid I really messed something up. I used your RSD Generator script to upgrade my xt926 to KK 4.4.2 (stock, from sbf.droid-developers) last week, but wasn't satisfied and kept trying to load CM11. I could never get a custom recovery to take hold, as both CWM and TWRP would supposedly be flashed successfully, only to reboot my phone and find nothing worked. Tinkering around on my phone last night, I accidentally flashed the kernel while poking around Recovery Tools (I think that's what went wrong?). Now the phone is bricked, and won't flash back to stock.  It's unlocked, status code 3. My SWDL log:

 

07/08/14 17:46:11  --------------------------------------------------------------------------------
07/08/14 17:46:11  New Log Started For Software Download.
07/08/14 17:46:11  The FlashLog key is turned off.
07/08/14 17:46:14  000002d4 Phone.cpp 531 0 ERROR Generic failure when sending command.
07/08/14 17:46:14  000002d4 Phone.cpp 1778 0 ERROR GetTechnology failed: ERROR.
07/08/14 17:46:14  000002d4 Phone.cpp 531 0 ERROR Generic failure when sending command.
07/08/14 17:46:14  000002d4 Phone.cpp 1778 0 ERROR GetTechnology failed: ERROR.
07/08/14 17:46:14  000002d4 Phone.cpp 531 0 ERROR Generic failure when sending command.
07/08/14 17:46:14  000002d4 Phone.cpp 1778 0 ERROR GetTechnology failed: ERROR.
07/08/14 17:46:14  000002d4 Phone.cpp 531 0 ERROR Generic failure when sending command.
07/08/14 17:46:14  000002d4 Phone.cpp 1847 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.
07/08/14 17:46:14  000002d4 Phone.cpp 531 0 ERROR Generic failure when sending command.
07/08/14 17:46:14  000002d4 Phone.cpp 2005 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
07/08/14 17:46:14  000002d4 Phone.cpp 531 0 ERROR Generic failure when sending command.
07/08/14 17:46:14  000002d4 Phone.cpp 1975 0 ERROR GetBootVerFlashMode failed: SendTC failed: ERROR.
07/08/14 17:46:14  000002d4 Phone.cpp 531 0 ERROR Generic failure when sending command.
07/08/14 17:46:14  000002d4 Phone.cpp 1894 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.
07/08/14 17:46:14  Multi upgrade started for 1 phones
07/08/14 17:46:14  [Device ID: 0] 1/18 flash partition "gpt.bin"
07/08/14 17:46:14  ERROR: 1/18 flash partition "gpt.bin" -> Phone returned FAIL. - on device ID 0.
07/08/14 17:46:14  [Device ID: 0] 1/18 flash partition "gpt.bin" -> Phone returned FAIL.
07/08/14 17:46:14  ERROR: Failed flashing process. - on device ID 0.
07/08/14 17:46:15  Multi upgrade finished.
07/08/14 17:46:30  --------------------------------------------------------------------------------
07/08/14 17:46:30  New Log Started For Software Download.
07/08/14 17:46:30  The FlashLog key is turned off.
07/08/14 17:46:33  0000350c Phone.cpp 531 0 ERROR Generic failure when sending command.
07/08/14 17:46:33  0000350c Phone.cpp 1778 0 ERROR GetTechnology failed: ERROR.
07/08/14 17:46:33  0000350c Phone.cpp 531 0 ERROR Generic failure when sending command.
07/08/14 17:46:33  0000350c Phone.cpp 1778 0 ERROR GetTechnology failed: ERROR.
07/08/14 17:46:33  0000350c Phone.cpp 531 0 ERROR Generic failure when sending command.
07/08/14 17:46:33  0000350c Phone.cpp 1778 0 ERROR GetTechnology failed: ERROR.
07/08/14 17:46:33  0000350c Phone.cpp 531 0 ERROR Generic failure when sending command.
07/08/14 17:46:33  0000350c Phone.cpp 1847 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.
07/08/14 17:46:33  0000350c Phone.cpp 531 0 ERROR Generic failure when sending command.
07/08/14 17:46:33  0000350c Phone.cpp 2005 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
07/08/14 17:46:33  0000350c Phone.cpp 531 0 ERROR Generic failure when sending command.
07/08/14 17:46:33  0000350c Phone.cpp 1975 0 ERROR GetBootVerFlashMode failed: SendTC failed: ERROR.
07/08/14 17:46:33  0000350c Phone.cpp 531 0 ERROR Generic failure when sending command.
07/08/14 17:46:33  0000350c Phone.cpp 1894 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.
07/08/14 17:46:33  Multi upgrade started for 1 phones
07/08/14 17:46:33  [Device ID: 0] 1/15 flash sbl1 "sbl1.mbn"
07/08/14 17:46:33  ERROR: 1/15 flash sbl1 "sbl1.mbn" -> Phone returned FAIL. - on device ID 0.
07/08/14 17:46:33  [Device ID: 0] 1/15 flash sbl1 "sbl1.mbn" -> Phone returned FAIL.
07/08/14 17:46:33  ERROR: Failed flashing process. - on device ID 0.
07/08/14 17:46:34  Multi upgrade finished.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users