Jump to content


Photo

House of Moto [3.2]


  • This topic is locked This topic is locked
1296 replies to this topic

#921 DCLXVI7

DCLXVI7

    n00b

  • Members
  • Pip
  • 6 posts

Posted 01 June 2014 - 05:46 PM

GREAT GOT IT TO WORK!!! THANKS FOR ALL THE HELP!!!

 

was wondering though if there was a root method for the xt926 model for my phone?

like i said i posted the specs of phone and it is locked so was just going to look in forums to see if there is one for the 4.4.2 version



#922 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 44,204 posts
  • Current Device(s):S21 Ultra, Pixel 6

Posted 01 June 2014 - 05:53 PM

Root?  I'm just going to :rolleyes: and direct you to this so you can sob.

 

Please Login or Register to see this Hidden Content


Non potest esse nisi unus


#923 DCLXVI7

DCLXVI7

    n00b

  • Members
  • Pip
  • 6 posts

Posted 01 June 2014 - 10:09 PM

lol yea i already saw this but then theres no unlocking bootloader for kit kat? or is this phones model too old?



#924 livinginkaos

livinginkaos

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

  • Administrator
  • 15,282 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 02 June 2014 - 03:53 AM

The exploit for the unlock of the bootloader for the xt926 was patched several updates ago. Sent from my S-Offed One M8

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


#925 ibolski

ibolski

    Droid Master

  • Dedicated Supporter
  • PipPipPip
  • 535 posts
  • Twitter:iBolski
  • Google+:Ivan Samuelson
  • LocationColumbus, Ohio
  • Current Device(s):Samsung Galaxy S7

Posted 02 June 2014 - 03:55 AM

lol yea i already saw this but then theres no unlocking bootloader for kit kat? or is this phones model too old?

 

Sam must be seething by now. :)

 

To spare you from the wrath of Sam, you cannot unlock it. You have passed the point of no return. 9.16.9 (JB) was the final version that allowed the exploit to unlock the bootloader.

 

Unfortunately, you are stuck with no root option at this point, and there probably won't be one. The only way to root is to have an unlocked bootloader and you are at a point where that is no longer possible. Don't even try to downgrade back to a version before KitKat. If you do, please do not come back here asking for help as you have been warned.


  • Int_Rnd_Pooka likes this

VZW Samsung Galaxy S7 Stock and unrooted running Marshmallow 46A, 32gb Nexus 7 unlocked
2cqd4t2.png


#926 boostedcx

boostedcx

    n00b

  • Members
  • Pip
  • 6 posts

Posted 04 June 2014 - 01:07 PM

Hello, I am trying to unbrick an XT926 using this tool. I am currently struggling with this error when flashing anything with mfastboot/rsd:

 

"failed to read signature for partition aboot"

 

Here is my log from the House of Moto tool:

 

 

Please ensure your phone is:
o] Charged
o] Connected to USB using your OEM cable
o] USB drivers are installed
o] Booted to AP Fastboot mode: [power off, hold volume down and press power]
 
Ready to flash...
Press any key to continue . . .
 
Flashing: FULL_xt926.bat
< waiting for device >
sending 'partition' (32 KB)...
OKAY [  0.022s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
Failed to program partition table
FAILED (remote failure)
finished. total time: 0.258s
sending 'sbl1' (101 KB)...
OKAY [  0.028s]
writing 'sbl1'...
Failed to erase partition
Failed to flash partition sbl1
FAILED (remote failure)
finished. total time: 0.085s
sending 'sbl2' (127 KB)...
OKAY [  0.030s]
writing 'sbl2'...
Failed to erase partition
Failed to flash partition sbl2
FAILED (remote failure)
finished. total time: 0.087s
sending 'sbl3' (512 KB)...
OKAY [  0.058s]
writing 'sbl3'...
Failed to erase partition
Failed to flash partition sbl3
FAILED (remote failure)
finished. total time: 0.265s
sending 'rpm' (140 KB)...
OKAY [  0.030s]
writing 'rpm'...
Failed to erase partition
Failed to flash partition rpm
FAILED (remote failure)
finished. total time: 0.222s
sending 'tz' (210 KB)...
OKAY [  0.035s]
writing 'tz'...
Image size exeeded partition limits
FAILED (remote failure)
finished. total time: 0.076s
sending 'aboot' (256 KB)...
OKAY [  0.038s]
writing 'aboot'...
Failed to erase partition
Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 0.235s
sending 'modem' (30720 KB)...
OKAY [  2.314s]
writing 'modem'...
Failed to erase partition
Failed to erase partition
Failed to write mmc
FAILED (remote failure)
finished. total time: 2.377s
sending 'fsg' (165 KB)...
OKAY [  0.032s]
writing 'fsg'...
Failed to erase partition
Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.090s
erasing 'modemst1'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.050s
erasing 'modemst2'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.051s
sending 'logo' (854 KB)...
OKAY [  0.083s]
writing 'logo'...
Failed to erase partition
Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.140s
sending 'boot' (10240 KB)...
OKAY [  0.797s]
writing 'boot'...
Failed to erase partition
Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.458s
sending 'recovery' (10240 KB)...
OKAY [  0.785s]
writing 'recovery'...
Failed to erase partition
Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.448s
sending 'system' (30720 KB)...
OKAY [  4.363s]
writing 'system'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 5.926s
erasing 'tombstones'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.051s
erasing 'cache'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.051s
erasing 'userdata'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.051s
rebooting...
 
finished. total time: 0.006s
Press any key to continue . . .

 

 

I seem to be having trouble with a corrupted aboot partition. I am able to get to AP Fastboot, but normal boot, recovery, and BP tools all bootloop endlessly. 

 

Thanks in advance for any advice. 



#927 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 44,204 posts
  • Current Device(s):S21 Ultra, Pixel 6

Posted 04 June 2014 - 01:10 PM

How the hell did you get into this condition?  UGH.  I'm not sure if we can fix that or not.  First thing's first, let's make sure you're using a USB 2 port with the original OEM cable that came with the phone.  Latest Moto USB driver installed.  Once that's verified, what FXZ are you attempting to flash?  This may take some work.


Non potest esse nisi unus


#928 boostedcx

boostedcx

    n00b

  • Members
  • Pip
  • 6 posts

Posted 04 June 2014 - 01:24 PM

I bought it like this, so its OK if I'm unable to un-brick. I'm just trying to learn more about repairing these devices. 

 

  • I am using a USB port directly from the back of my motherboard, USB 2.0.
  • I am using the OEM Motorola USB cable.
  • The latest Motorola USB driver package is installed.
  • I am using this FXZ: VRZ_XT926_9.8.1Q-94-1_CFC.xml from this site: 

    Please Login or Register to see this Hidden Content

Thanks again.



#929 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 44,204 posts
  • Current Device(s):S21 Ultra, Pixel 6

Posted 04 June 2014 - 01:31 PM

Have you tried RSD mode?  If not, switch to RSD mode and if it fails again, provide me the contents of the SWDL txt file in the RSD folder.


Non potest esse nisi unus


#930 boostedcx

boostedcx

    n00b

  • Members
  • Pip
  • 6 posts

Posted 04 June 2014 - 01:56 PM

Here is the SWDL contents:

 

06/03/14 18:53:38  --------------------------------------------------------------------------------
06/03/14 18:53:38  New Log Started For Software Download.
06/03/14 18:53:39  The FlashLog key is turned off.
06/03/14 18:53:41  000013e4 Phone.cpp 531 0 ERROR Generic failure when sending command.
06/03/14 18:53:41  000013e4 Phone.cpp 1778 0 ERROR GetTechnology failed: ERROR.
06/03/14 18:53:41  000013e4 Phone.cpp 531 0 ERROR Generic failure when sending command.
06/03/14 18:53:41  000013e4 Phone.cpp 1778 0 ERROR GetTechnology failed: ERROR.
06/03/14 18:53:41  000013e4 Phone.cpp 531 0 ERROR Generic failure when sending command.
06/03/14 18:53:41  000013e4 Phone.cpp 1778 0 ERROR GetTechnology failed: ERROR.
06/03/14 18:53:41  000013e4 Phone.cpp 531 0 ERROR Generic failure when sending command.
06/03/14 18:53:41  000013e4 Phone.cpp 1847 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.
06/03/14 18:53:41  000013e4 Phone.cpp 531 0 ERROR Generic failure when sending command.
06/03/14 18:53:41  000013e4 Phone.cpp 2005 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
06/03/14 18:53:41  000013e4 Phone.cpp 531 0 ERROR Generic failure when sending command.
06/03/14 18:53:41  000013e4 Phone.cpp 1975 0 ERROR GetBootVerFlashMode failed: SendTC failed: ERROR.
06/03/14 18:53:41  000013e4 Phone.cpp 531 0 ERROR Generic failure when sending command.
06/03/14 18:53:41  000013e4 Phone.cpp 1894 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.
06/03/14 18:53:41  Multi upgrade started for 1 phones
06/03/14 18:53:41  [Device ID: 0] 1/17 flash partition "gpt.bin"
06/03/14 18:53:42  ERROR: 1/17 flash partition "gpt.bin" -> Phone returned FAIL. - on device ID 0.
06/03/14 18:53:42  [Device ID: 0] 1/17 flash partition "gpt.bin" -> Phone returned FAIL.
06/03/14 18:53:42  ERROR: Failed flashing process. - on device ID 0.
06/03/14 18:53:42  Multi upgrade finished.
06/03/14 18:53:58  --------------------------------------------------------------------------------
06/03/14 18:53:58  New Log Started For Software Download.
06/03/14 18:53:58  The FlashLog key is turned off.
06/03/14 18:54:01  00001630 Phone.cpp 531 0 ERROR Generic failure when sending command.
06/03/14 18:54:01  00001630 Phone.cpp 1778 0 ERROR GetTechnology failed: ERROR.
06/03/14 18:54:01  00001630 Phone.cpp 531 0 ERROR Generic failure when sending command.
06/03/14 18:54:01  00001630 Phone.cpp 1778 0 ERROR GetTechnology failed: ERROR.
06/03/14 18:54:01  00001630 Phone.cpp 531 0 ERROR Generic failure when sending command.
06/03/14 18:54:01  00001630 Phone.cpp 1778 0 ERROR GetTechnology failed: ERROR.
06/03/14 18:54:01  00001630 Phone.cpp 531 0 ERROR Generic failure when sending command.
06/03/14 18:54:01  00001630 Phone.cpp 1847 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.
06/03/14 18:54:01  00001630 Phone.cpp 531 0 ERROR Generic failure when sending command.
06/03/14 18:54:01  00001630 Phone.cpp 2005 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
06/03/14 18:54:01  00001630 Phone.cpp 531 0 ERROR Generic failure when sending command.
06/03/14 18:54:01  00001630 Phone.cpp 1975 0 ERROR GetBootVerFlashMode failed: SendTC failed: ERROR.
06/03/14 18:54:01  00001630 Phone.cpp 531 0 ERROR Generic failure when sending command.
06/03/14 18:54:01  00001630 Phone.cpp 1894 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.
06/03/14 18:54:01  Multi upgrade started for 1 phones
06/03/14 18:54:01  [Device ID: 0] 1/17 flash partition "gpt.bin"
06/03/14 18:54:01  ERROR: 1/17 flash partition "gpt.bin" -> Phone returned FAIL. - on device ID 0.
06/03/14 18:54:01  [Device ID: 0] 1/17 flash partition "gpt.bin" -> Phone returned FAIL.
06/03/14 18:54:01  ERROR: Failed flashing process. - on device ID 0.
06/03/14 18:54:01  Multi upgrade finished.
06/03/14 18:57:23  --------------------------------------------------------------------------------
06/03/14 18:57:23  New Log Started For Software Download.
06/03/14 18:57:23  The FlashLog key is turned off.
06/03/14 18:57:26  00001ec4 Phone.cpp 531 0 ERROR Generic failure when sending command.
06/03/14 18:57:26  00001ec4 Phone.cpp 1778 0 ERROR GetTechnology failed: ERROR.
06/03/14 18:57:26  00001ec4 Phone.cpp 531 0 ERROR Generic failure when sending command.
06/03/14 18:57:26  00001ec4 Phone.cpp 1778 0 ERROR GetTechnology failed: ERROR.
06/03/14 18:57:26  00001ec4 Phone.cpp 531 0 ERROR Generic failure when sending command.
06/03/14 18:57:26  00001ec4 Phone.cpp 1778 0 ERROR GetTechnology failed: ERROR.
06/03/14 18:57:26  00001ec4 Phone.cpp 531 0 ERROR Generic failure when sending command.
06/03/14 18:57:26  00001ec4 Phone.cpp 1847 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.
06/03/14 18:57:26  00001ec4 Phone.cpp 531 0 ERROR Generic failure when sending command.
06/03/14 18:57:26  00001ec4 Phone.cpp 2005 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
06/03/14 18:57:26  00001ec4 Phone.cpp 531 0 ERROR Generic failure when sending command.
06/03/14 18:57:26  00001ec4 Phone.cpp 1975 0 ERROR GetBootVerFlashMode failed: SendTC failed: ERROR.
06/03/14 18:57:26  00001ec4 Phone.cpp 531 0 ERROR Generic failure when sending command.
06/03/14 18:57:26  00001ec4 Phone.cpp 1894 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.
06/03/14 18:57:26  Multi upgrade started for 1 phones
06/03/14 18:57:26  [Device ID: 0] 1/18 flash partition "gpt.bin"
06/03/14 18:57:26  ERROR: 1/18 flash partition "gpt.bin" -> Phone returned FAIL. - on device ID 0.
06/03/14 18:57:26  [Device ID: 0] 1/18 flash partition "gpt.bin" -> Phone returned FAIL.
06/03/14 18:57:26  ERROR: Failed flashing process. - on device ID 0.
06/03/14 18:57:27  Multi upgrade finished.


#931 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 44,204 posts
  • Current Device(s):S21 Ultra, Pixel 6

Posted 04 June 2014 - 02:09 PM

Alright, we might be able to save the phone but not a chance in hell are we keeping 9.30.1/9.18.94 in the process.  Switch to the 183 KK FXZ and try again with RSD.


Non potest esse nisi unus


#932 livinginkaos

livinginkaos

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

  • Administrator
  • 15,282 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 04 June 2014 - 02:12 PM

Gpt failed. Gotta move up a build. Ninja'd Sent from my S-Offed One M8

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


#933 boostedcx

boostedcx

    n00b

  • Members
  • Pip
  • 6 posts

Posted 04 June 2014 - 02:43 PM

I just downloaded and tried to RSD this file : VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml

 

RSD failed flashing process on 2/20 flash partition gpt.bin phone returned fail. 

 

On the device, I get the same message - failed to read signature for partition aboot..



#934 livinginkaos

livinginkaos

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

  • Administrator
  • 15,282 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 04 June 2014 - 02:57 PM

Ummm, is the battery show low on the fastboot screen?

The other potential you're not likely to like.

Sent from my S-Offed One M8


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


#935 boostedcx

boostedcx

    n00b

  • Members
  • Pip
  • 6 posts

Posted 04 June 2014 - 03:01 PM

I'm using a Motorola Factory Cable, it says Battery OK.



#936 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 44,204 posts
  • Current Device(s):S21 Ultra, Pixel 6

Posted 04 June 2014 - 03:10 PM

Then it's toast.  Someone did something very bad to that phone.


Non potest esse nisi unus


#937 boostedcx

boostedcx

    n00b

  • Members
  • Pip
  • 6 posts

Posted 04 June 2014 - 03:21 PM

Interesting. Here is the description from the eBay auction:

 

This phone has worked great until a recent upgrade ruined it. Even the battery was holding good charge. All parts included, no contract on this phone. The screen works great too and always had a protector on it. A tiny scratch by the word motorolla.  Again, this phone has not been stripped, everything is there and everything worked before the software failed.

 

 

Thanks for your help though! 

 

 

By the way, I have another XT926 that does not boot to AP Fastboot. I cannot get to the "M" logo, but the green LED does light when plugged in. When I plug it into my computer with the factory cable, I get an attempt to install "QHSUSB_DLOAD", but it fails. Does anyone know if these drivers do exist? I would imagine that it would be possible to flash a bootloader on the phone if I was able to access it as a COM port. 



#938 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 44,204 posts
  • Current Device(s):S21 Ultra, Pixel 6

Posted 04 June 2014 - 03:30 PM

QHSUSB_DLOAD means that something went horribly wrong when flashing....most likely they flashed the wrong FXZ and it's perma bricked.  I've never seen anyone recover one from that.  It's possible flashing when the battery is low can fry things, too.  In any case, neither phone is fixable I'm afraid.


Non potest esse nisi unus


#939 Faethor420

Faethor420

    n00b

  • Members
  • Pip
  • 12 posts
  • LocationN. AZ
  • Current Device(s):Droid Bionic

Posted 04 June 2014 - 09:12 PM

Man, Sam, whenever I get frustrated with stupid customers & ignorant users I ways know I can just sit back and catch up on some of your threads & sudd nly my frustrations melt away... I feel for ya man, and I commend you for your patience & resolve! If you ever need to retreat from all this for a few there's a pretty sweet Buddhist temple out in the middle of nowhere near where I live in northern Arizona... Lol

Seriously though, I know I've been a mild PTA for ya a couple times & I apologize, often after reading thread after thread from Google search galore, the data just gets corrupted... Buffer overload, memory hole, call it what you will. Anyway, we're all grateful your here doin what you do. Thanks!

Sent from my DROID RAZR HD using Tapatalk


  • RikRong likes this

#940 ibolski

ibolski

    Droid Master

  • Dedicated Supporter
  • PipPipPip
  • 535 posts
  • Twitter:iBolski
  • Google+:Ivan Samuelson
  • LocationColumbus, Ohio
  • Current Device(s):Samsung Galaxy S7

Posted 05 June 2014 - 03:52 AM

Interesting. Here is the description from the eBay auction:

 

This phone has worked great until a recent upgrade ruined it. Even the battery was holding good charge. All parts included, no contract on this phone. The screen works great too and always had a protector on it. A tiny scratch by the word motorolla.  Again, this phone has not been stripped, everything is there and everything worked before the software failed.

 

 

Thanks for your help though! 

 

 

By the way, I have another XT926 that does not boot to AP Fastboot. I cannot get to the "M" logo, but the green LED does light when plugged in. When I plug it into my computer with the factory cable, I get an attempt to install "QHSUSB_DLOAD", but it fails. Does anyone know if these drivers do exist? I would imagine that it would be possible to flash a bootloader on the phone if I was able to access it as a COM port. 

That description right there would have steered me away from that phone. Never, ever purchase a phone that says "it worked great until..." unless you're looking for spare parts to strip from it.


VZW Samsung Galaxy S7 Stock and unrooted running Marshmallow 46A, 32gb Nexus 7 unlocked
2cqd4t2.png





3 user(s) are reading this topic

0 members, 3 guests, 0 anonymous users