Best Answer SamuriHL , 01 October 2014 - 12:00 PM
It can't write to the phone. We've seen this issue before and there's zero way to fix it. I hate to say that, but, this is a very ugly problem. Sorry you went through all that for no solution, but, the phone is basically screwed up at the partition level. And yours is not the only one like that. No one's ever fixed one to my knowledge.
Go to the full post
Member
Posted 01 October 2014 - 11:05 AM
Yes it's hooked up right now in APfastboot but do not know how to tell if Ubuntu can see it or not. I'll take your word for it. Also let me follow that link you just posted and see what it has to say. So it may be the phone itself, perhaps its damaged or my PC is just not down with it.
Android Warrior
Posted 01 October 2014 - 11:06 AM
Under devices you have to make sure the phone is selected. I sent that link so you could scroll down and see the picture of them selecting the device in virtual box so that it connects it to the VM.
Non potest esse nisi unus
Member
Posted 01 October 2014 - 11:11 AM
Yes I see the guide, thank you. I'm following its instructions now. Give me a few to read and perform the steps and I'll post back when that is accomplished. I can tell already I didn't check off the EHCI controller option. So that's a problem right off the get go. More in a few mins...
Android Warrior
Posted 01 October 2014 - 11:14 AM
Take your time. At least we're moving the ball forward. The fastboot problem is at least fixed so once we get the device connected in your VM, we can try running HouseOfMoto again and see if we can get that bad boy flashed.
Non potest esse nisi unus
Member
Posted 01 October 2014 - 11:15 AM
Ok the steps it said to do have been done. It shows as Motorola Inc. Fastboot VANQUISH S [0100]. I had already installed guest additions when I first setup the VM. Here's a screen shot of the VM software so you can see that the phone is now listed in the fliters so it should show up in Ubuntu now.
Member
Posted 01 October 2014 - 11:17 AM
The VM hit a wall upon booting, says I need to install the Oracle VM VirtualBox Extension Pack, for god sakes. Looking into that now.
Android Warrior
Posted 01 October 2014 - 11:25 AM
Once you get it back up, run the ./FXZ_XT926/Linux/fastboot devices command again and show me the output.
Non potest esse nisi unus
Member
Posted 01 October 2014 - 11:26 AM
Ok new stuff happened, installing the extension pack wasn't to hard. Didn't know how to do that but I figured it out. Ubuntu has booted back up and now a notification in Windows popped up saying Virtual Box USB like it had installed a driver or something to that effect. I'm at the desktop about to open terminal. You recon there is anything else of consequence to worry about, such as additional terminal commands to help you verify what I've done or should I just try flash that mofo?
Android Warrior
Posted 01 October 2014 - 11:28 AM
No, see my last post and show me that first.
Non potest esse nisi unus
Member
Posted 01 October 2014 - 11:29 AM
Man I don't understand it, its like this phone is just determined to stay in wacky mode. I noticed after a moment the phone reset itself and went to the moto screen so I unplugged it and put it back in APfastboot mode and reconnected it. Then I tried your command (./FXZ_XT926/Linux/fastboot devices)
A copy and paste from the root directory produced this:
britton@britton-VirtualBox:~$ ./FXZ_XT926/Linux/fastboot devices
bash: ./FXZ_XT926/Linux/fastboot: No such file or directory
britton@britton-VirtualBox:~$
Member
Posted 01 October 2014 - 11:31 AM
No wait, I got it now, I had to be in the correct directory! It shows this now.....
britton@britton-VirtualBox:~$ cd Desktop
britton@britton-VirtualBox:~/Desktop$ dir
HouseOfMoto
britton@britton-VirtualBox:~/Desktop$ cd HouseOfMoto
britton@britton-VirtualBox:~/Desktop/HouseOfMoto$
britton@britton-VirtualBox:~/Desktop/HouseOfMoto$ ./FXZ_XT926/Linux/fastboot devices
no permissions fastboot
britton@britton-VirtualBox:~/Desktop/HouseOfMoto$
This is good right, better than "no file found" at least. What's next master of phones .gif)
Android Warrior
Posted 01 October 2014 - 11:32 AM
How the hell can it not exist given that you just did all the commands I asked you to do to move it to that directory and we tested it. WTF is going on with that thing???
Non potest esse nisi unus
Android Warrior
Posted 01 October 2014 - 11:33 AM
Ok, that's better. Run this:
sudo ./FXZ_XT926/Linux/fastboot devices
Non potest esse nisi unus
Member
Posted 01 October 2014 - 11:36 AM
britton@britton-VirtualBox:~/Desktop/HouseOfMoto$ sudo ./FXZ_XT926/Linux/fastboot devices
[sudo] password for britton:
TA269005DM fastboot
britton@britton-VirtualBox:~/Desktop/HouseOfMoto$
That looks better!! that's what you wanted to see right?
Android Warrior
Posted 01 October 2014 - 11:37 AM
Yes. Finally. Run it and flash that thing.
Non potest esse nisi unus
Gear jammin' S-Mod
Posted 01 October 2014 - 11:39 AM
Feeding my android addiction......... one phone at a time.....
If you are feeling generous and would like to buy me a drink.... coffee
Gear jammin' S-Mod
Posted 01 October 2014 - 11:40 AM
Feeding my android addiction......... one phone at a time.....
If you are feeling generous and would like to buy me a drink.... coffee
Member
Posted 01 October 2014 - 11:40 AM
I knew it was to good to be true, ready for the mega log output from terminal? Here it is, in all it glory....
Please ensure your phone is:
o] Charged
o] Connected to USB 2 using your OEM cable
o] Booted to AP Fastboot mode: [power off, hold volume down and press power]
Ready to flash...
Press enter to continue.
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'partition' (32 KB)...
OKAY [ 0.027s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.344s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'sbl1' (101 KB)...
OKAY [ 0.044s]
writing 'sbl1'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition sbl1
FAILED (remote failure)
finished. total time: 0.175s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'sbl2' (127 KB)...
OKAY [ 0.061s]
writing 'sbl2'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition sbl2
FAILED (remote failure)
finished. total time: 0.184s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'sbl3' (512 KB)...
OKAY [ 0.121s]
writing 'sbl3'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition sbl3
FAILED (remote failure)
finished. total time: 0.401s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'rpm' (140 KB)...
OKAY [ 0.049s]
writing 'rpm'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition rpm
FAILED (remote failure)
finished. total time: 0.307s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'tz' (210 KB)...
OKAY [ 0.066s]
writing 'tz'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition tz
FAILED (remote failure)
finished. total time: 0.327s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'aboot' (256 KB)...
OKAY [ 0.075s]
writing 'aboot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 0.349s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
sending sparse 'modem' (28132 KB)...
OKAY [ 6.906s]
writing 'modem'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 7.034s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'fsg' (165 KB)...
OKAY [ 0.050s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.176s
(bootloader) Variable not supported!
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.058s
(bootloader) Variable not supported!
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.058s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'logo' (854 KB)...
OKAY [ 0.176s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.306s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'boot' (10240 KB)...
OKAY [ 2.186s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 2.918s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (10240 KB)...
OKAY [ 2.197s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 2.934s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1097312864 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1065859680 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1034406496 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1002953312 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 971471456 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 940014176 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 908552800 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 876706400 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 848497248 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 817044064 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 785844832 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 755759712 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 724302432 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 692779616 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 661322336 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 630585952 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 599100000 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 567589472 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 538651232 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 507165280 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 475695712 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 444242528 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 412719712 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 381262432 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 349809248 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 319117920 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 287664736 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 256182880 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 224729696 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 196082272 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 164596320 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 133143136 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 101689952 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 70236768 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 38754912 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 7301728 is not a multiple of the block size 4096
fastboot: ../libsparse/sparse.c:143: write_all_blocks: Assertion `pad >= 0' failed.
FULL.sh: line 16: 2203 Aborted (core dumped) $fastboot flash system system.img
(bootloader) Variable not supported!
erasing 'tombstones'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.059s
(bootloader) Variable not supported!
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.056s
(bootloader) Variable not supported!
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.058s
rebooting...
finished. total time: 0.008s
Press enter to continue.
Basically the same as Windows but with more detail, so what do you think. Not worth the effort at this point?
Member
Posted 01 October 2014 - 11:43 AM
I just want to take a hammer to it now!!! If it was mine I'd have slung it in the trash can already. It's like the phone is just not willing to accept any com activity at all no matter what OS is used. it's in a USB 2.0 port and on the motorola cable as well. Could the phone have gotten a virus on it that made the partition so corrupted that nothing can access it? Or is it just a communication problem? I'm out of ideas, and a bit discouraged to have to have you guys spend so much time trying to help me fix it only to have it do the exact same thing. Goddamnit!! (2014)
Gear jammin' S-Mod
Posted 01 October 2014 - 11:45 AM
Feeding my android addiction......... one phone at a time.....
If you are feeling generous and would like to buy me a drink.... coffee
0 members, 1 guests, 0 anonymous users
