479 replies to this topic

[gwade12]

So I tried a different cable - voila! or so I thought.. Plugged it into my Mac again. ./fastboot devices and it shows my device. Proceed with the sudo ./flashme.sh. Get through the first two y/n's.. get to the third one (erase userdata), select n, then told it's erasing the data.. what the heck! The phone tries to reboot, but I'm still stuck in the bootloop. However, the andoird file transfer application I downloaded starts going insane telling me it can't connect to the device and to try again. The window just keeps popping up every few seconds. So, it seems I've gotten further, but not as far as I need to be. I sure hope it didn't actually erase the data either. :/

[gwade12]

UPDATE: After unplugging the phone and plugging it back in, it's rebooted and turned on. However, it's just showing the setup wizard. I will post again in a few minutes to let you know if my data was deleted. Hopefully it didn't.

[gwade12]

Looks like it deleted my data anyway.   The only thing he wanted was the pictures and whatnot left on the phone. Even though I selected no, the script still deleted the data. Is there any way to get it back, or is it gone forever?

[gwade12]

Here was the issue.

echo "WARNING: Choosing yes to this option will WIPE YOUR DATA."

read -p "Erase user data? [y/n]: " yesorno

  case "$yesorno" in

     y*)  flashUserData ;;

     n*)  echo "" ;;

       esac

 

fastboot erase userdata

fastboot reboot

echo "Rebooting..."

 

No matter the case, fastboot erase userdata was still run. I guess I should've double checked that. Is there any way to get my data back?

[SamuriHL]

There is not.  Looks like a damn bug.  I'll get it updated when I get a chance.  As I mentioned the other day, this is not the week to have issues with the HoM since I do not have time to do anything about it.  But the data is indeed gone. Stupid bash scripts.

[gwade12]

All good. I appreciate the help. At least the phone is out of that stupid boot loop. No idea why it went into one in the first place. He doesn't even know what rooting a phone is, and it didn't happen during an update or anything. Completely random.

[SamuriHL]

Could be starting to die.  I've seen that happen when the nvram starts to go.  Just something to be aware of and keep an eye on.  Sorry about the data.  I strive for non-data loss so that one pisses me off.  I'll get it fixed, but, I just don't have time to focus on non-work dev right now.

[gwade12]

Like I said, it's all good. $#!+ happens. I know he really wanted his data, but he loved the phone too and wanted it working again.

[pribleton]

Has anyone had any luck finding the firmware 19.5.3?  Every link I've found has been broken.

[gt40racer]

SamuriHL,  You sir are a genius! After RSD Lite refused to acknowledge my phone I thought for sure my Bionic was bricked. HOM 4.1 resurrected it. I'm very impressed and want to thank you for your hard work and programming skills. 

Now if there was a simple way to switch on the GSM radio I could use my Bionic for more than a streaming wifi music player. 

Thanks again!!!

[P_A]

Looks like this post has been inactive for a bit, but I am VERY glad I found this. Follow instructions to a T and worked like a chamed. A million thanks to SamuriHL!

 

My issue was Moto Droid RAZR M stuck in boot. After much searching seemed like an all too common problem. Using HOM phone is booted and no data lost.

[xKroniK13x]

Took my X a round through good old HoM to revert to unmodified stock to get the latest OTA. Works great as always. You da bomb dot com.

Sent from my Moto X 2014 Pure Edition using Tapatalk

[Tippecanoe]

Server not found for:
 

Please Login or Register to see this Hidden Content

 
Thanks
 
 

[spainter]

Please Login or Register to see this Hidden Content

[yeshaya86]

Hi, I posted on the RSD Flasher tool forum earlier. It didn't work on my phone so I just tried with HoM, also without success.

Model: Droid Razr HD XT926

System version: Unknown since it won't boot, presumably last verizon ota.

Filename VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml

 

Fastboot screen:

 

AP Fastboot Flash Mode (S)

10.9B(*) (sha-61146a2, 2014-07-29 08:54:49)

eMMC Info: Size 32GB

 

Device is LOCKED. Status Code: )

 

Battery OK

 

Transfer Mode:

USB Connected

 

 

 

Fastboot Reason: Key pressed

 

flashme.bat content:

 

@echo off

 

::Generated script from the House of Moto 4.1.

::Generated from: VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml.zip

 

PATH=C:\HouseOfMoto\TOOLS\Windows;%PATH%

 

 

:ask_gpt

set choice=

set /p choice=Flash GPT partition? [y/n]: 

if "%choice%"=="y" goto flash_gpt

if "%choice%"=="Y" goto flash_gpt

if "%choice%"=="n" goto end_gpt

if "%choice%"=="N" goto end_gpt

goto ask_gpt

 

:flash_gpt

   fastboot flash partition gpt.bin

 

goto end_gpt

 

:end_gpt

 

fastboot flash sbl1 sbl1.mbn

fastboot flash sbl2 sbl2.mbn

fastboot flash sbl3 sbl3.mbn

fastboot flash rpm rpm.mbn

 

:ask_tz

set choice=

set /p choice=Flash TZ partition? [y/n]: 

if "%choice%"=="y" goto flash_tz

if "%choice%"=="Y" goto flash_tz

if "%choice%"=="n" goto end_tz

if "%choice%"=="N" goto end_tz

goto ask_tz

 

:flash_tz

   fastboot flash tz tz.mbn

 

goto end_tz

 

:end_tz

 

fastboot flash aboot emmc_appsboot.mbn

fastboot flash modem NON-HLOS.bin

fastboot flash fsg fsg.mbn

fastboot erase modemst1

fastboot erase modemst2

fastboot flash logo logo.bin

fastboot flash boot boot.img

fastboot flash recovery recovery.img

fastboot flash system system.img

fastboot erase tombstones

fastboot erase cache

 

echo WARNING: Choosing yes to this option will WIPE YOUR DATA.

:ask_erase

set choice=

set /p choice=Erase userdata partition? [y/n]: 

if "%choice%"=="y" goto flash_userdata

if "%choice%"=="Y" goto flash_userdata

if "%choice%"=="n" goto end_userdata

if "%choice%"=="N" goto end_userdata

goto ask_userdata

 

:flash_userdata

   fastboot erase userdata

 

goto end_userdata

 

:end_userdata

 

fastboot reboot

echo Rebooting...

goto end

 

:end

   echo Thanks for using the House of Moto.

   pause

 

 

flashme.bat output:

 

Flash GPT partition? [y/n]: y

sending 'partition' (32 KB)...

OKAY [  0.020s]

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.330s

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.154s

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.170s

sending 'sbl3' (512 KB)...

OKAY [  0.060s]

writing 'sbl3'...

Failed to erase partition

Failed to flash partition sbl3

FAILED (remote failure)

finished. total time: 0.340s

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.310s

Flash TZ partition? [y/n]: y

sending 'tz' (210 KB)...

OKAY [  0.040s]

writing 'tz'...

Failed to erase partition

Failed to flash partition tz

FAILED (remote failure)

finished. total time: 0.310s

sending 'aboot' (256 KB)...

OKAY [  0.040s]

writing 'aboot'...

Failed to erase partition

Failed to flash partition aboot

FAILED (remote failure)

finished. total time: 0.310s

sending 'modem' (30720 KB)...

OKAY [  2.334s]

writing 'modem'...

Failed to erase partition

Failed to erase partition

Failed to write mmc

FAILED (remote failure)

finished. total time: 2.460s

sending 'fsg' (165 KB)...

OKAY [  0.040s]

writing 'fsg'...

Failed to erase partition

Failed to flash partition fsg

FAILED (remote failure)

finished. total time: 0.170s

erasing 'modemst1'...

Failed to erase partition

FAILED (remote failure)

finished. total time: 0.060s

erasing 'modemst2'...

Failed to erase partition

FAILED (remote failure)

finished. total time: 0.060s

sending 'logo' (854 KB)...

OKAY [  0.090s]

writing 'logo'...

Failed to erase partition

Failed to flash partition logo

FAILED (remote failure)

finished. total time: 0.220s

sending 'boot' (10240 KB)...

OKAY [  0.790s]

writing 'boot'...

Failed to erase partition

Failed to flash partition boot

FAILED (remote failure)

finished. total time: 1.524s

sending 'recovery' (10240 KB)...

OKAY [  0.791s]

writing 'recovery'...

Failed to erase partition

Failed to flash partition recovery

FAILED (remote failure)

finished. total time: 1.531s

sending 'system' (30720 KB)...

OKAY [  2.332s]

writing 'system'...

Failed to erase partition

FAILED (remote failure)

finished. total time: 3.930s

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.060s

WARNING: Choosing yes to this option will WIPE YOUR DATA.

Erase userdata partition? [y/n]: n

rebooting...

 

finished. total time: -0.000s

Rebooting...

Thanks for using the House of Moto.

Press any key to continue . . .

 

 

Generate.log:

 

Custom recovery not found.

Using factory image: VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml.zip

Extracting: gpt.bin

...CRC32 checksum: 1905572778

Extracting: sbl3.mbn

...CRC32 checksum: 3659908926

Extracting: logo.bin

...CRC32 checksum: 321084888

Extracting: sbl2.mbn

...CRC32 checksum: 3090468626

Extracting: emmc_appsboot.mbn

...CRC32 checksum: 90899438

Extracting: fsg.mbn

...CRC32 checksum: 1133177070

Extracting: sbl1.mbn

...CRC32 checksum: 192526102

Extracting: system.img

...CRC32 checksum: 1766757038

Extracting: rpm.mbn

...CRC32 checksum: 2091525295

Extracting: NON-HLOS.bin

...CRC32 checksum: 3098529230

Extracting: tz.mbn

...CRC32 checksum: 622631404

Extracting: recovery.img

...CRC32 checksum: 1159195623

Extracting: boot.img

...CRC32 checksum: 1240879109

Extracting: VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml

...CRC32 checksum: 2272597960

Found VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml

Writing script: C:\HouseOfMoto\MOTO\flashme.bat

 

 

Other info:

Using a USB2.0 port, with Motorola cable. Windows 7 machine and Java 8. I tried with your RSD flasher tool also, didn't work for my device. Any advice or ideas would be very much appreciated. I don't know if it means anything, but even when I selected "open RSD but do not flash", it flashed anyway before I clicked start. Don't know if that has any significance.

Here's that log:

07/08/15 17:52:35  Multi upgrade started for 1 phones

07/08/15 17:52:35  [Device ID: 0] 1/15 flash sbl1 "sbl1.mbn"

07/08/15 17:52:36  ERROR: 1/15 flash sbl1 "sbl1.mbn" -> Phone returned FAIL. - on device ID 0.

07/08/15 17:52:36  [Device ID: 0] 1/15 flash sbl1 "sbl1.mbn" -> Phone returned FAIL.

07/08/15 17:52:36  ERROR: Failed flashing process. - on device ID 0.

07/08/15 17:52:36  Multi upgrade finished.

07/08/15 17:52:45  Multi upgrade started for 1 phones

07/08/15 17:52:45  [Device ID: 0] 1/15 flash sbl1 "sbl1.mbn"

07/08/15 17:52:45  ERROR: 1/15 flash sbl1 "sbl1.mbn" -> Phone returned FAIL. - on device ID 0.

07/08/15 17:52:45  [Device ID: 0] 1/15 flash sbl1 "sbl1.mbn" -> Phone returned FAIL.

07/08/15 17:52:45  ERROR: Failed flashing process. - on device ID 0.

07/08/15 17:52:45  Multi upgrade finished.

 

Thank you for all your help, Yeshaya

[SamuriHL]

This is not such a good sign. I knew you flashed an xt907 successfully with the same setup. I'm not sure what is happening here. We have seen far too many hardware failures in the flash roms on these devices and it could be a hardware failure.

Sent from my Nexus 6 using Tapatalk

[yeshaya86]

Ok. I think I'll try taking it to a data recovery service, to see if something like JTAG is an option. In the meantime I'm reading up on adb sideloading, to see if it's possible to flash a .zip with a new system partition without wiping /data. Fixing this thing is probably beyond the limits of my skills and equipment, but I've definitely learnt a lot about phone infrastructure from trying.

Thank you Samuri, and to Spainter as well, for all the time and effort you put into development and support for these tools, I truly appreciate it.

Yeshaya

[SamuriHL]

Attention Mac/Linux users.  You should test better.  

[amirka28]

hi..to all specially Spainter and samuriHL..thanks for your support and hard working for us..

i did everything you said for my Droid razr hd 4.1.2..but when i used your FXZ ...didnt work and said

 

Custom recovery not found.

Using factory image: VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml.zip

Extracting: VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml

...CRC32 checksum: 1547423210

Found VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml

ERROR: XML script not found in this factory image.  This is not yet supported.

should i try another FXZ?

         

 

[spainter]

 

hi..to all specially Spainter and samuriHL..thanks for your support and hard working for us..

i did everything you said for my Droid razr hd 4.1.2..but when i used your FXZ ...didnt work and said

 

Custom recovery not found.

Using factory image: VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml.zip

Extracting: VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml

...CRC32 checksum: 1547423210

Found VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml

ERROR: XML script not found in this factory image.  This is not yet supported.

should i try another FXZ?

         

 

There was a update to HOM in the last 24 hours you may want to download 1.5 and set it up. You might want to check a different image file. It would make me a bit warry of one that didn't un-zip properly.