Jump to content


Photo

House of Moto [4.3]


  • Please log in to reply
479 replies to this topic

#341 cisz

cisz

    Member

  • Members
  • PipPip
  • 25 posts
  • Current Device(s):droid razr m XT907

Posted 13 February 2016 - 08:28 AM

Correction: The fastboot screen on the phone says "USB Connected" when the factory cable is plugged in to the computer and the phone. But the computer doesn't seem to be registering it. I tried flashing with HoM and it sits at <waiting for device>.

 

I should add that the computer is able to see the device when plugged in with a non-factory usb cable.

 

Maybe the factory cable is defective?



#342 spainter

spainter

    Droid Oracle

  • Moderator
  • 3,339 posts
  • LocationUtah
  • Current Device(s):Pixel 2 XL, Nexus 6, Moto X Pure Edition, 2013 Moto X DE, Droid Razr Maxx HD, 2013 Nexus 7 LTE, LG G Pad X 8.3

Posted 13 February 2016 - 11:27 AM

Correction: The fastboot screen on the phone says "USB Connected" when the factory cable is plugged in to the computer and the phone. But the computer doesn't seem to be registering it. I tried flashing with HoM and it sits at <waiting for device>.

 

I should add that the computer is able to see the device when plugged in with a non-factory usb cable.

 

Maybe the factory cable is defective?

more than likely it is a driver problem.  download and reinstall the drivers for moto. and you are using a sub 2.0 port directly from the computer not a hub.



#343 cisz

cisz

    Member

  • Members
  • PipPip
  • 25 posts
  • Current Device(s):droid razr m XT907

Posted 13 February 2016 - 02:44 PM

It seems the problem was because I was using a limited user account. When I switched over to an admin account, it worked. Unfortunately, it still failed to write anything using HoM and the 15.1 update of kk.

 

Flash GPT partition? [y/n]: y
sending 'partition' (32 KB)...
OKAY [  0.016s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 0.218s
sending 'sbl1' (101 KB)...
OKAY [  0.016s]
writing 'sbl1'...
Invalid partition name sbl1
FAILED (remote failure)
finished. total time: 0.140s
sending 'sbl2' (126 KB)...
OKAY [  0.016s]
writing 'sbl2'...
Invalid partition name sbl2
FAILED (remote failure)
finished. total time: 0.140s
sending 'sbl3' (512 KB)...
OKAY [  0.047s]
writing 'sbl3'...
Invalid partition name sbl3
FAILED (remote failure)
finished. total time: 0.172s
sending 'rpm' (140 KB)...
OKAY [  0.031s]
writing 'rpm'...
Invalid partition name rpm
FAILED (remote failure)
finished. total time: 0.156s
Flash TZ partition? [y/n]: y
sending 'tz' (210 KB)...
OKAY [  0.030s]
writing 'tz'...
Invalid partition name tz
FAILED (remote failure)
finished. total time: 0.161s
sending 'aboot' (256 KB)...
OKAY [  0.031s]
writing 'aboot'...
Invalid partition name aboot
FAILED (remote failure)
finished. total time: 0.156s
sending 'modem' (30720 KB)...
OKAY [  2.280s]
writing 'modem'...
Unkown partition name modem
FAILED (remote failure)
finished. total time: 2.482s
sending 'fsg' (170 KB)...
OKAY [  0.021s]
writing 'fsg'...
Invalid partition name fsg
FAILED (remote failure)
finished. total time: 0.149s
erasing 'modemst1'...
Invalid partition name modemst1
FAILED (remote failure)
finished. total time: 0.140s
erasing 'modemst2'...
Invalid partition name modemst2
FAILED (remote failure)
finished. total time: 0.121s
sending 'logo' (1709 KB)...
OKAY [  0.140s]
writing 'logo'...
Invalid partition name logo
FAILED (remote failure)
finished. total time: 0.265s
sending 'boot' (10240 KB)...
OKAY [  0.771s]
writing 'boot'...
Invalid partition name boot
FAILED (remote failure)
finished. total time: 0.896s
sending 'recovery' (10240 KB)...
OKAY [  0.758s]
writing 'recovery'...
Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.898s
sending 'system' (30720 KB)...
OKAY [  2.278s]
writing 'system'...
Unkown partition name system
FAILED (remote failure)
finished. total time: 2.410s
erasing 'tombstones'...
Invalid partition name tombstones
FAILED (remote failure)
finished. total time: 0.125s
erasing 'cache'...
Invalid partition name cache
FAILED (remote failure)
finished. total time: 0.125s
WARNING: Choosing yes to this option will WIPE
Erase userdata partition? [y/n]: y
erasing 'userdata'...
Invalid partition name userdata
FAILED (remote failure)
finished. total time: 0.125s
rebooting...

finished. total time: -0.000s
Rebooting...
Thanks for using the House of Moto.
Press any key to continue . . .
 



#344 spainter

spainter

    Droid Oracle

  • Moderator
  • 3,339 posts
  • LocationUtah
  • Current Device(s):Pixel 2 XL, Nexus 6, Moto X Pure Edition, 2013 Moto X DE, Droid Razr Maxx HD, 2013 Nexus 7 LTE, LG G Pad X 8.3

Posted 13 February 2016 - 04:03 PM

Try this source for a fresh download:

Please Login or Register to see this Hidden Content



#345 cisz

cisz

    Member

  • Members
  • PipPip
  • 25 posts
  • Current Device(s):droid razr m XT907

Posted 16 February 2016 - 02:49 AM

Thanks. Tried it, but still have the same problem.

 

When the phone 1st started having a problem and wouldn't boot, I was able to get to the recovery menu and tried using it.  When that didn't help I tried flashing with HoM but didn't realize I needed to put in the snapdragon files for the xt907 - so it flashed with the wrong files. I don't have a clear memory, but it may have been after that that it would no longer go to the recovery menu and would only bring up the flashboot screen.

 

Wondering if this could be the reason it won't flash now?



#346 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 16 February 2016 - 03:23 AM

If you flashed firmware for another device, then you likely will not be able to flash the correct files to your device any more. On the fastboot screen, what does it say for fastboot reason?

Sent from my Nexus 6P using Tapatalk


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


#347 cisz

cisz

    Member

  • Members
  • PipPip
  • 25 posts
  • Current Device(s):droid razr m XT907

Posted 16 February 2016 - 04:23 AM

AP Fastboot Flash Mode (S)
10.9B(*) (sha-61146a2, 2014-07-29 06:20:44)
eMMC info: Size 8GB

Device is LOCKED. Status Code:0

Battery OK

Transfer Mode:
USB Connected

failed to write partition gpt_main
failed to load GPT
CID read failure
Invalid CID status 0x69
No SP partition found
Fastboot Reason: Invalid GPT



#348 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 16 February 2016 - 06:27 PM

Yeah, that's not good. The partition table being out of whack caused by flashing the improper set of fastboot files is generally unrecoverable.

Sent from my Nexus 6P using Tapatalk


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


#349 poloflash

poloflash

    n00b

  • Members
  • Pip
  • 1 posts
  • Current Device(s):motorola droid razr hd

Posted 04 March 2016 - 04:46 PM

This is outstanding loved it I definitely taught my phone was dead  I was stuck on AP Fastboot Flash Mode (S) with all kinds of fail messages for 2 days and try all different flashing methods to get  back to stock and this is the only one that worked perfect and on the first try. Thank you guys you are awesome.   


  • SamuriHL, cmh714 and spainter like this

#350 cisz

cisz

    Member

  • Members
  • PipPip
  • 25 posts
  • Current Device(s):droid razr m XT907

Posted 12 March 2016 - 03:34 AM

If you flashed firmware for another device, then you likely will not be able to flash the correct files to your device any more. On the fastboot screen, what does it say for fastboot reason?

Sent from my Nexus 6P using Tapatalk

I've got this magnetic field eraser that's used to completely erase hard drives. I'm thinking of trying it on the phone and then see if I can re-partition it.



#351 spainter

spainter

    Droid Oracle

  • Moderator
  • 3,339 posts
  • LocationUtah
  • Current Device(s):Pixel 2 XL, Nexus 6, Moto X Pure Edition, 2013 Moto X DE, Droid Razr Maxx HD, 2013 Nexus 7 LTE, LG G Pad X 8.3

Posted 12 March 2016 - 06:06 AM

Only the OEM has access to the files needed to setup the flash memory in the phones.  I have not seen them out in the wild at all.  You have to remember that it is flash memory not a hard drive.  I believe it will destroy the memory chip.



#352 cisz

cisz

    Member

  • Members
  • PipPip
  • 25 posts
  • Current Device(s):droid razr m XT907

Posted 12 March 2016 - 06:32 PM

So it's kind of like a bios chip and they're not putting out anything to reflash it?

 

Would you be able to explain what is happening as far as why flashing with the wrong fastboot files and the partition table being off would make the phone unfixable?

 

Thanks.



#353 spainter

spainter

    Droid Oracle

  • Moderator
  • 3,339 posts
  • LocationUtah
  • Current Device(s):Pixel 2 XL, Nexus 6, Moto X Pure Edition, 2013 Moto X DE, Droid Razr Maxx HD, 2013 Nexus 7 LTE, LG G Pad X 8.3

Posted 12 March 2016 - 08:44 PM

So it's kind of like a bios chip and they're not putting out anything to reflash it?

 

Would you be able to explain what is happening as far as why flashing with the wrong fastboot files and the partition table being off would make the phone unfixable?

 

Thanks.

Using the bios chip is a fair analogy. The bios looks to the cmos for information as to where the system files are located to boot an os. Your phone has a protected section of the memory set aside for the same purpose depending on the chip set the phone uses.  When you flash the wrong firmware the partitioning for the boot and protected areas no longer are readable or are overwritten, removed. Thats why you can never blank out the memory chip with out having the software and files to reload it.  Usually it takes a direct serial link to the motherboard of the phone to re initialize the memory chip. Not from a usb connection.

That is my understanding of it anyway.



#354 mean24gene

mean24gene

    n00b

  • Members
  • Pip
  • 1 posts
  • Current Device(s):LG G5

Posted 13 April 2016 - 08:46 PM

SamuriHL I know this is an old post but Thank You so much man!!!  I followed your directions and I now have life back to my Razr HD XT926.  The phone was stuck in the red eyeball on boot up and fastboot recovery was not working.  The only issue I was having running the HouseOfMoto 4.3 was Security Version Downgraded message failure.  I was using the wrong stock firmware factory images for the XT926.  Since I have a locked bootloader I was unable to put on the jellybean 4.1.1 and downgrade.  I needed to use the KitKat 4.4.2 and boom!  Phone flashed fully, rebooted, got past the red eye, loaded the home screen.  I can use this phone as a backup if my LG G5 runs into any issues...fingers crossed.  You da man!


  • SamuriHL and spainter like this

#355 izoristvhal

izoristvhal

    n00b

  • Members
  • Pip
  • 2 posts

Posted 19 April 2016 - 07:27 PM

SamuriHL I know this is an old post but Thank You so much man!!!  I followed your directions and I now have life back to my Razr HD XT926.  The phone was stuck in the red eyeball on boot up and fastboot recovery was not working.  The only issue I was having running the HouseOfMoto 4.3 was Security Version Downgraded message failure.  I was using the wrong stock firmware factory images for the XT926.  Since I have a locked bootloader I was unable to put on the jellybean 4.1.1 and downgrade.  I needed to use the KitKat 4.4.2 and boom!  Phone flashed fully, rebooted, got past the red eye, loaded the home screen.  I can use this phone as a backup if my LG G5 runs into any issues...fingers crossed.  You da man!

where did you find the 4.4.2 kitkat been trying to get my draid razr maxx hd to work same problem but cant find the correct firmware



#356 spainter

spainter

    Droid Oracle

  • Moderator
  • 3,339 posts
  • LocationUtah
  • Current Device(s):Pixel 2 XL, Nexus 6, Moto X Pure Edition, 2013 Moto X DE, Droid Razr Maxx HD, 2013 Nexus 7 LTE, LG G Pad X 8.3

Posted 19 April 2016 - 07:41 PM

Please Login or Register to see this Hidden Content



#357 izoristvhal

izoristvhal

    n00b

  • Members
  • Pip
  • 2 posts

Posted 19 April 2016 - 10:21 PM

thank you phone is working now thanks to you


  • SamuriHL likes this

#358 efdisaster

efdisaster

    n00b

  • Members
  • Pip
  • 5 posts
  • Twitter:efdisaster

Posted 01 May 2016 - 12:08 PM

I'm getting the same issue as cisz did with repeated "FAILED (remote failure)" on my xt907 which was stuck on the Red M

 

I downloaded FXZ that spainter linked above, but my Fastboot Reason is "Boot menu selected" and it reboots the phone fine after all the script failures and it lists one string on fastboot devices

 

I'm on Mac OS X, it didn't like the "generated by" comments, so I removed those two lines, and I changed MAC OS X to Darwin in the path, but otherwise, I have not messed with the flashme script. 

 

Any ideas?

 

Please Login or Register to see this Hidden Content



#359 SamuriHL

SamuriHL

    Android Warrior

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

Posted 01 May 2016 - 03:05 PM

I'm guessing your mac is usb3.  That's not a good thing in this case.


Non potest esse nisi unus


#360 efdisaster

efdisaster

    n00b

  • Members
  • Pip
  • 5 posts
  • Twitter:efdisaster

Posted 01 May 2016 - 03:13 PM

nope. Mid 2009 Mac Mini. USB2

 

Have definitely used the same machine with HouseOfMoto in the past on a droid bionic, possibly a mini, and maybe an ultra... this is just the last holdout in the family, just reluctantly took the Ultra as a handmedown when their razr m went Red M... but would really like me to try and recover their text message history.

 

I'm guessing your mac is usb3.  That's not a good thing in this case.






2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users